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

Root [OUDHS] Soft Brick and CWM recovery support

I have the same issue as meche334.
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 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?
NOTE: I have not Activated the phone yet (not sure that makes a difference)

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
 
lgoptimusv5 said:
I have the same issue as meche334.
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 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?
NOTE: I have not Activated the phone yet (not sure that makes a difference)

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
Click to expand...


Greetings! Yes, the way these 'new' GSR's are acting, one would surmise that is the case...and I had a theory that had to with the new Galaxy Ring phone that VM is offering; that because the hardware between them was so similar, that the rooting method for the Ring would work for the Reverb...but AF member Nychus tried and reported that it did not work. Oh well, so much for theories!
 
Here's the rooting methods Ive tried so far:
Obviously most recent JB Root method flashing cwm-test-8.tar via Odin304 w/battery pull
Framaroot-1.5.1
Framaroot-1.5.2
Ministro II v9.5 + Poot
z4root.1.3.0

Manually trying to Root via adb with:
psneuter (GB based)
gingerbreak
zergRush
pwn (From Motochopper)
fakebackup.ab method from other Samsung device (Didn't work as it needed a compromised Kernel to allow SU adb shell)

Never get to CWM or Stock Recovery, thus not able to root either.

I notice a difference in behavior when flashing TWRP designed for other phones:
cwm-test-8 will get past Samsung/Booting Recovery screen and seem to load, but then flash blue screen briefly, and nothing.
Flashing TWRPs (Not designed for Reverb) will actually hang at the Samsung/Booting Recovery screen, and never load.
Flashing the reverb-stock-recovery.tar does almost the same thing as CWM-test8, just minus the brief blue screen
This leads me to believe we may need a New CWM for the new JB412 Pre-Installed Reverbs
Or perhaps the kernel is different.
I have the boot.img from Stock JB ZJones.
I wonder if flashing that via Odin would the phone still boot? and if so, normal Root method would work?
Will not try this until I'm sure I have the original boot.img from this current SGR with JB preInstalled.

???Can Someone verify the Kernel version on their OTA Updated JB Reverb???
???Can Someone verify the Hardware version on their OTA Updated JB Reverb???
 
OK, the spec.'s you're lookin' for verification on....on MY phone are identical to yours. Granted, up until an hour ago, I had a custom rom. What I did, was restore my phone to DEAD STOCK ICS 4.0.4, re-flashed the stock recovery, reboot and let it update OTA to 4.1.2.
I have been trying to get you a screenshot, but for some reason the upload is not working...something about manually resizing...blah, blah. So if I can get it to work, I'll post it up for 'ya.
 
Man, every time I get a full post ready for acquiring a partition table in regard to getting root on OotB JB SGRvrbs, I keep remembering that its irrelevant because we have nothing to compare the partition table to. Though, this is something that I will do the moment I get root - it could easily be necessary, is currently lacking, and thanks to a post by ktb83 and working with giantpune we were able to generate a partition table for the OE.

I'm on board with the kernel theory - granted, it's all I can think of right now as to being the culprit here. I'll be looking into the process of how CWM is backported to devices, too.
 
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???
Different partition table needs new Kernel/Recovery???
???IS THIS THE CHANGE THAT CRIPPLED OUR CURRENT CWM-TEST8???
 
soxtober05
So you're now running OTA JB 4.1.2?
And the Kernel version # is the same as my OutOfBox JB 4.1.2?
Kernel Version
3.0.31-1175366
se.infra@SEP-129 #1
Tue Apr 30 02:46:07 KST 2013

THANKS
 
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???
Different partition table needs new Kernel/Recovery???
???IS THIS THE CHANGE THAT CRIPPLED OUR CURRENT CWM-TEST8???
Click to expand...

I noticed that too, that it does say that they come with 4GB, and I'm guessing this is easily a typo (my own Rvrb has 2GB), or that all of the bloatware is taking up the extra space.

Regardless, no - a different partition table is not related to getting root as I mentioned before. However, it would prove that something is different between the OotB JB Rvrbs and the ones with the OTA JB update. Lastly, the size of the /data partition has nothing to do with the /recovery partition - they're completely separate, unless this phone is different concerning partitions.
 
lgoptimusv5 said:
soxtober05
So you're now running OTA JB 4.1.2?
And the Kernel version # is the same as my OutOfBox JB 4.1.2?
Kernel Version
3.0.31-1175366
se.infra@SEP-129 #1
Tue Apr 30 02:46:07 KST 2013

THANKS
Click to expand...
I was up until late last night. After the last time I posted to you, I attempted to flash back to my original rom, but wound up with the same problem as the new Reverb users. I have a post on the 'all things root' board if you want to read more...
 
mjm_pd said:
I'll give it a go.

Will report back...
Click to expand...

Odin Failure: (All options unchecked, used PDA button)
200e71c223f6690ef35f22a78b2ea427 *reverb_cwm_test_10.tar

<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> reverb_cwm_test_10.img
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
 
xInterlopeRx said:
can you join irc for a few minutes?

EDIT: NVM, same link different files. Go again as it pleases you.
Click to expand...

No go...

82c8a39bf8554b547f9c776b4b094d6d *reverb_cwm_test_10a.tar

<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> reverb_cwm_test_10.img
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
 
xInterlopeRx said:
It's failing because of the way the .tar is made. Problem is, I've been doing it the same way for 18 months...

http://www.oudhitsquad.com/android/Samsung/SPH-M950/mod/recovery/reverb_cwm_test_10.tar

DON'T MOCK ME HENRIETTA!

Just in case, I did it OVER over. Thanks for trying. Make sure your cables and connections are good, I've seen stranger things.
Click to expand...

Thanks, will try again tonight. I'll try another cable and the old ver 8 since I know that was flashing before.
 
mjm_pd said:
Thanks, will try again tonight. I'll try another cable and the old ver 8 since I know that was flashing before.
Click to expand...

OK, this one flashed without error.

However, for me it behaves just like version 8.

After the recovery flash, I pull the cable and battery.
After replacing the battery, I hold vol up & power.
Once "SAMSUNG" appears, release power only (I've tried holding longer).
Phone continues normal boot (Samsung swirl logo), so I pull battery.

On the second attempt, I see the text at the top
"boot to recovery mode by key", the screen flashes and then goes blank.

I can never get it to do anything but a normal boot on the first attempt after flashing.

Thanks.
 
xInterlopeRx said:
Second attempt: when the screen goes blank, does it stay that way until you do something, like pull the battery or long hold the power button? Do you have adb perchance? Can you try using adb during that black screen?

You can use these binaries for ADB, etc...

http://www.oudhitsquad.com/android/tools/adb_fb_gnu.7z

If you need instructions, just holla!
Click to expand...

Screen stays blank until I pull the battery.
While in this state, if I plug in the usb cable, the computer detects nothing.
 
Well, you might actually be IN recovery with no video support. If you can try ADB and verify ANY connection at all that would be a nice start.
 
xInterlopeRx said:
Well, you might actually be IN recovery with no video support. If you can try ADB and verify ANY connection at all that would be a nice start.
Click to expand...

Windows is not detecting any devices while the phone is in this state, so
adb sees nothing...

D:\Programs\Android>adb devices
List of devices attached
 
xInterlopeRx said:
It's failing because of the way the .tar is made. Problem is, I've been doing it the same way for 18 months...

http://www.oudhitsquad.com/android/Samsung/SPH-M950/mod/recovery/reverb_cwm_test_10.tar

DON'T MOCK ME HENRIETTA!

Just in case, I did it OVER over. Thanks for trying. Make sure your cables and connections are good, I've seen stranger things.
Click to expand...

Also gave this one a shot, running OTB Jelly Bean. Resulted in something odd, where it would boot, show the Samsung logo, then sit at a blank screen. All of this with or without the recovery key combo. Had to flash v8 and let it re-install stock recovery to fix.
 
You must log in or register to reply here.
Back
Top Bottom