• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root cant access cwm or recovery mode for reverb

C

chuckdfour20

Lurker
galaxy reverb wont access cwm but download mode work, going to try usin odin to flash my backup, dont know if im like stacking software or wat no way to format phone from wat i can tell
 
no go on fixing reverb still it is soft bricked i can access download mode but there is no recovery mode or cwm even tho i did install cwm thru odin it did work at one point but trying to flash roms thru odin killed my recovery menu. & no volume up, home & power is not making it load recovery menu, thank u for ur support this is an ongoing thing i wont give up till i fix it or kill it completly :D so anything that helps is much appreciated
 
XAL2 said:
David you have this phone now? Sorry off topic..
Click to expand...

yeah, lost my evo v and didn't have the money for a new one... so i got this phone...
deving on the 3d seems to have slowed down and everything seems to be working on that phone (other than the cam which no one can even dream of fixing)...
and stuff on this toy has barely begun...
 
Right now I can ONLY get into download mode. I tried ADB already. I dont think I tried fastboot assuming that I just wouldn't be able to probably. I can only flash and reflash with ODIN and I can hold the power up and home or menu button for as long as I want, it's not working and it definitively used to. My partitions are extremely messed up right now, I am sure that is the root of the whole issue and a lot of people are having it frankly. I'm glad that I
 
luxedesignnyc said:
Right now I can ONLY get into download mode. I tried ADB already. I dont think I tried fastboot assuming that I just wouldn't be able to probably. I can only flash and reflash with ODIN and I can hold the power up and home or menu button for as long as I want, it's not working and it definitively used to. My partitions are extremely messed up right now, I am sure that is the root of the whole issue and a lot of people are having it frankly. I'm glad that I
Click to expand...

So try fastboot... Same as adb but u type in fastboot reboot recovery...
 
I have the same issue.
Blue flickering on the screen then just turns black and nothing else happens...

I have a newer Samsung Galaxy Reverb SPH-M950 Virgin Mobile that came with JB 4.1.2 pre-installed.
NONE of the Reverb CWM's or Roots for JB are working.
I tried reverb-cwm-test-8 and cwm-touch-iconvmu-signed(cwm6030) for the Reverb with no success. I tried different versions of TWRP made for other Samsung phones, with different results, but still no success.
Odin3v304 does flash the recovery successfully, but the previous CWM's made for the older ICS based Reverbs do not boot when i finally get into Recovery mode with the OutOfBox 4.1.2 Reverbs.
Something has changed with the JB 4.1.2 pre-installed Reverbs that is not allowing the commonly know CWMs to boot in recovery.

I really just want to put an older ICS build on this phone because of the TouchScreenLock issues it has with any JB build...
Disabling Hotword Detection seemed to resolve freezing for now tho...

Anyone had success with newer Samsung Galaxy Reverb SPH-M950 Virgin Mobile that came with JB 4.1.2 pre-installed?
I notice the Kernel Version is dated April 30 of this year...hint?
???Can Someone verify the Kernel version on their OTA Updated JB Reverb???

Pre-Installed JB 4.1.2 Reverb Specs:
Carrier
Virgin Mobile
Mobile Network Type
EvDo-rev.A:8
PRL Version
61009
Model Number
SPH-M950
Android Version
4.1.2 (Out of the Box)
Baseband Version
M950VPBMD6
Kernel Version
3.0.31-1175366
se.infra@SEP-129 #1
Tue Apr 30 02:46:07 KST 2013
Build Number
JZO54K.M950VPBMD6
Hardware Version
M950.07
 
I realized today that my Reverb has only 2GB of INTERNAL STORAGE.
What are the specs on the old Reverbs?
Every site I look at says the specs for Reverb are 4GB INTERNAL STORAGE.
???Can someone verify the INTERNAL STORAGE on their OLD REVERB???
It's been verified that the OTA 412 Kernel and my OutOfBox 412 Kernel version #s are the same...
But Different partition table needs new Kernel/Recovery???
??? IS THIS THE CHANGE THAT CRIPPLED OUR CURRENT CWM-TEST8???
 
lgoptimusv5 said:
I realized today that my Reverb has only 2GB of INTERNAL STORAGE.
What are the specs on the old Reverbs?
Every site I look at says the specs for Reverb are 4GB INTERNAL STORAGE.
???Can someone verify the INTERNAL STORAGE on their OLD REVERB???
It's been verified that the OTA 412 Kernel and my OutOfBox 412 Kernel version #s are the same...
But Different partition table needs new Kernel/Recovery???
??? IS THIS THE CHANGE THAT CRIPPLED OUR CURRENT CWM-TEST8???
Click to expand...

Not sure on answer to 'crippled' part, but can comment on GB question.
Reverb has 4gb. The Samsung design uses 2gb for system and uses the other 2gb as SD card. This is one reason apps2sd will not work on the reverb. When deleting/installing just remember which SD you are using. Internal SD or external SD (micro card). This knowledge is also beneficial for backups.
 
bkttk2 said:
Not sure on answer to 'crippled' part, but can comment on GB question.
Reverb has 4gb. The Samsung design uses 2gb for system and uses the other 2gb as SD card. This is one reason apps2sd will not work on the reverb. When deleting/installing just remember which SD you are using. Internal SD or external SD (micro card). This knowledge is also beneficial for backups.
Click to expand...

Thanks for that info...
Here's what i found on my OutOfBox JB 412 Reverb when I installed TitaniumBackup with NO ROOT:
NOTE this is with all my apps installed referring to free space...

SystemROM 825MB (19.4MB free)
Internal Media 2.20GB (1.36 GB free)
Ext SDcard

Anyone with an older Reverb care to Share their Partition sizes?
 
UPDATE:
I tried flashing CWM-Rush-M830-Final.tar to my OutOfBox JB412 Reverb via Odin.
I got different results than using reverb-cwm-test-8.tar.

Here are the differences:
-Flashing reverb-cwm-test-8.tar results in Brief Blue Flash on screen, then nothing
-Flashing CWM-Rush-M830-Final.tar results in a repeating Blue,Green,Red Flashing screen.

I can never seem to get to Recovery until after the first initial Samsung loads, then flashes black, pull batt before it loads 2nd Samsung logo with swirl, then boot into recovery.
At first i thought I was not loading CWM quick enough, and possibly interrupting the StockRecovery Write process, leading to corrupted stock Recovery boot attempts...
It makes sense the CWM for M830 Rush doesn't work...
But is this an indication that I'm properly getting to Recovery, but CWM-test8 doesnt work?
Or am i just not getting to the CWM recovery in time before it gets overwritten with stock?

Thoughts?
7ban.jpg
 
lgoptimusv5 said:
UPDATE:
I tried flashing CWM-Rush-M830-Final.tar to my OutOfBox JB412 Reverb via Odin.
I got different results than using reverb-cwm-test-8.tar.

Here are the differences:
-Flashing reverb-cwm-test-8.tar results in Brief Blue Flash on screen, then nothing
-Flashing CWM-Rush-M830-Final.tar results in a repeating Blue,Green,Red Flashing screen.

I can never seem to get to Recovery until after the first initial Samsung loads, then flashes black, pull batt before it loads 2nd Samsung logo with swirl, then boot into recovery.
At first i thought I was not loading CWM quick enough, and possibly interrupting the StockRecovery Write process, leading to corrupted stock Recovery boot attempts...
It makes sense the CWM for M830 Rush doesn't work...
But is this an indication that I'm properly getting to Recovery, but CWM-test8 doesnt work?
Or am i just not getting to the CWM recovery in time before it gets overwritten with stock?

Thoughts?
Click to expand...

May not help but when you push the recovery with Odin be sure to uncheck auto-reboot. Just push the file and wait for it to indicate successful. Then disconnect the USB cable and pull the battery. Then place battery and try to go directly into recovery. If successful then you should be able to boot from the CWM recovery. If the phone reboots prior to getting into CWM then you have to restart.

This is the process for the OTA reverbs not sure if it will work for the Out of the box versions.
 
OK, here's a thought; when tyler1998 posted his recovery to Google Drive, people at that time were clamoring for a 'bone stock rom'. Some of the posts seemed (to me) indicate that he was shooting for a .zip file as a finished product...but it wound-up as a recovery instead.
I was just wondering; and let's all be clear on this from the get go...I'M A COMPLETE NOOB, NOT A DEVELOPER...so I know little to nothing about this...it's a hypothesis:

Can these same files for the bone stock 4.0.4 ICS be downloaded into the phone's sd card, and then moved into the phone's /cache folder and flashed like an update with the "update from cache" option in the stock <3e> recovery the same way that we with CWM 8 placed them in the /backup folder? Do you need root to perform this move, or to even access the right folder?

I'm grasping at straws here, peoples. No idea if it'll work, and looking back at my post here, to me it doesn't seem like it could be harmful; so if I sound like a Kindergartener shouting out of turn, don't be afraid to tell me so. I've got pretty thick skin, & take constructive criticism pretty well.

Thoughts?

Peace,
Sox
 
soxtober05 said:
OK, here's a thought; when tyler1998 posted his recovery to Google Drive, people at that time were clamoring for a 'bone stock rom'. Some of the posts seemed (to me) indicate that he was shooting for a .zip file as a finished product...but it wound-up as a recovery instead.
I was just wondering; and let's all be clear on this from the get go...I'M A COMPLETE NOOB, NOT A DEVELOPER...so I know little to nothing about this...it's a hypothesis:

Can these same files for the bone stock 4.0.4 ICS be downloaded into the phone's sd card, and then moved into the phone's /cache folder and flashed like an update with the "update from cache" option in the stock <3e> recovery the same way that we with CWM 8 placed them in the /backup folder? Do you need root to perform this move, or to even access the right folder?

I'm grasping at straws here, peoples. No idea if it'll work, and looking back at my post here, to me it doesn't seem like it could be harmful; so if I sound like a Kindergartener shouting out of turn, don't be afraid to tell me so. I've got pretty thick skin, & take constructive criticism pretty well.

Thoughts?

Peace,
Sox
Click to expand...

Not a bad idea...
Except I broke my OutOfBox Reverb's Stock Recovery when i tried to flash CWM8test.
I'm assuming anyone else who tried has the same issue.

I had a similar 'I'm not a Developer' idea:
Downgrading the Reverb to ICS via .TAR file(s) with Odin.
I've made TAR files with other Recovery.img's in them to test on the Reverb already.
I already have the Stock ICS zip.
I could very well add Root to the Stock ICS Zip, or even to the Stock JB zip, and Flash that via Odin.
But I don't know the specifics enough to put a proper TAR File together.
And doing an OS update via Odin from what i understand is very Risky.

Anyone out there an Odin Expert?
Anyone ever flashed an entire OS with Tar File(s) via Odin successfully?
Or is this idea right out.
Could it really be as simple as creating a Tar file of a Stock ICS or JB Rom with Root built in?
I'm guessing we'd need to find/create the stock OS .IMG File(s), and put that inside the TAR File(s), and flash via Odin...
 
Hmmm; kinda weird that the phone boots and works, but has no working recovery; stock or otherwise...doesn't the OS need the rec. file to boot/work? (please excuse the noob question..)

What about the stock 4.0.4 kernel that Interloper put out there...have you tried flashing that? If not, I'd say give it a whirl; you got nothing to lose, 'n everything to gain, right?

Use Odin to flash the stock kernel, (with the auto reboot off), then flash the CWM 8 right behind it in the same way, then (attempt to) reboot to recovery.
 
soxtober05 said:
Hmmm; kinda weird that the phone boots and works, but has no working recovery; stock or otherwise...doesn't the OS need the rec. file to boot/work? (please excuse the noob question..)
Click to expand...

Nope. The phone requires certain data to be on the /boot partition in order for it to actually boot up. The OS is stored entirely on the /system partition, while the recovery is stored on the /recovery partition. You can manually wipe /recovery and /system both, and the phone will still boot (just not into any OS, until you put an OS onto it; in other words, a ROM) - the partitions are completely separate from eachother. Good question though!
 
You must log in or register to reply here.
Back
Top Bottom