• 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

The good news: I can patch the old kernel with the patch files and get a good kernel.
The bad news: I don't have an old stock recovery to make it work for that partition.
The good news: My daughter made home made churros today!
The bad news: I don't have a solution just yet. Just ideas and indigestion.
 
Huzzah!

All gnu's are good gnu's!!!!

EDIT: the patch file from the update creates a recovery.img from........dun dun dun dun...the boot.img, not the old recovery.img! who knew?!?!?!

more later.
 
Would you mind flashing the recovery that dofkwldkf posted above? Just as a baseline. And, are you on JBOOB or JBUD (out-of-box or updated)?
 
xInterlopeRx said:
Would you mind flashing the recovery that dofkwldkf posted above? Just as a baseline. And, are you on JBOOB or JBUD (out-of-box or updated)?
Click to expand...

OK, with the "stock" recovery from above:
-Still cannot get recovery to come up on first boot
-On second boot recovery, I get a black screen (not back-lit). This is different then what I called a "blank" screen (back-lit) from before.
-With the black screen, adb works and device list shows "xxxx recovery"
 
So, there is a recovery that has SOME initialization of the device. Backlight and even a HINT of adb are huge clues for me. Sounds like the one I made with the patches has some action. If it says adb devices = recovery xxxxxx then the device IS in recovery, but without display support. Now, I need to find out why it's failing and I just had an idea. I'll compile a zImage with the new kernel source, bind the initramfs to it and use the recovery-from-boot.p to make another tester... But, not tonight.
 
My schizophrenia wouldn't let me alone. Be warned This May Brick Your Device. No one will tease you in the school yard for backing out of the double-dog-dare now. This is very sketchy stuff, like etch-a-sketchy!

http://www.oudhitsquad.com/android/Samsung/SPH-M950/stock/reverb_bootimg.tar <---scary indeed!

http://www.oudhitsquad.com/android/Samsung/SPH-M950/stock/reverb_recovery_patch_2.tar <--based on scary indeed!

If you chose to accept this mission, flash the boot.img and reboot. If it works, continue to phase two of the plan and flash the recovery. No hurry just get it done ASAP.
 
Just to be clear...

For me, only the "stock" recovery above results in a working adb recovery. This is with a black screen, no back light.

All other recoveries result in a blank, back-lit screen and NO adb response (appears frozen).

Also forgot to answer that my phone is ootb jb.
 
xInterlopeRx said:
Ok, cool. With the partially working recovery can you try adb logcat?
Click to expand...

adb logcat
--------- beginning of /dev/log/main
I/ARMAssembler( 103): generated scanline__00000077:03545402_00000000_00000000 [ 30 ipp] (44 ins) at
[0x411a51e8:0x411a5298] in 91553 ns
I/ARMAssembler( 103): generated scanline__00000077:03545402_00000A01_00000000 [ 31 ipp] (52 ins) at
[0x411a52a0:0x411a5370] in 91552 ns
I/ARMAssembler( 103): generated scanline__00000077:03545402_00000A08_00000000 [ 31 ipp] (53 ins) at
[0x411a5378:0x411a544c] in 91553 ns

At this point, I have to break out of adb, not sure if that is normal for logcat in recovery?
(Looks like breaking out of logcat is normal).
 
mjm_pd said:
adb logcat
--------- beginning of /dev/log/main
I/ARMAssembler( 103): generated scanline__00000077:03545402_00000000_00000000 [ 30 ipp] (44 ins) at
[0x411a51e8:0x411a5298] in 91553 ns
I/ARMAssembler( 103): generated scanline__00000077:03545402_00000A01_00000000 [ 31 ipp] (52 ins) at
[0x411a52a0:0x411a5370] in 91552 ns
I/ARMAssembler( 103): generated scanline__00000077:03545402_00000A08_00000000 [ 31 ipp] (53 ins) at
[0x411a5378:0x411a544c] in 91553 ns

At this point, I have to break out of adb, not sure if that is normal for logcat in recovery?
(Looks like breaking out of logcat is normal).
Click to expand...

Yeah, the device actually has TWO adb binaries. One is in the initramfs and gives us logging before system starts, the other is in system. Once the kernel gives control to the system filesystem, initramfs adb dies. You only get these three lines? This is a compiler information line. Maybe you can run it through a few times until you get some lines like "E/error message here" Also, try a few runs using the command "adb shell dmesg" This may seem tedious, but if I knew a more efficient way, I would have done it long ago. Thanks.
 
xInterlopeRx said:
Yeah, the device actually has TWO adb binaries. One is in the initramfs and gives us logging before system starts, the other is in system. Once the kernel gives control to the system filesystem, initramfs adb dies. You only get these three lines? This is a compiler information line. Maybe you can run it through a few times until you get some lines like "E/error message here" Also, try a few runs using the command "adb shell dmesg" This may seem tedious, but if I knew a more efficient way, I would have done it long ago. Thanks.
Click to expand...

No joy for the logcat.
Here is the dmesg...
 

Attachments

If this was taken while trying to boot into recovery, there's this:
<6>[ 0.336639] LCD(r69329) lcdc_r69329_panel_on : Panel on without backlight on

Looks like something breaks backlight. I'll have to do some more investigating.
 
I followed all instructions, i did everything exactly how you said i should do it and it never could go to the IOS because it would restart before i can get there. I dont think it unbricked my phone because its doing exactly what its been doing before i used odin.
 
Minioko said:
I followed all instructions, i did everything exactly how you said i should do it and it never could go to the IOS because it would restart before i can get there. I dont think it unbricked my phone because its doing exactly what its been doing before i used odin.
Click to expand...


Probably this way is obsolete, the Reverb has gone through a couple of firmware updates since this was written.
 
How to install CWM recovery on galaxy Reverb. need help
i have successfully rooted my device i just want to install any custom recovery so i can un-install tuchwiz (hate it) i want to install plain jelly bean. any help would be great
what i have done so far:
root: yes
install custom recovery: working on that
flash a custom rom: not there yet
 
You must log in or register to reply here.
Back
Top Bottom