Develop Bugs

[Q] Cannot boot to recovery (on two completely separate phones).

I flashed CM10 onto my phone a couple weeks ago, everything went smoothly. Today, I reverted back to stock and locked the bootloader so that I could receive the stock JellyBean update. Well I download the update, reboot phone into fastboot, attempt to go into recovery and I get the red triangle !. I know this is an issue with the phone apparently not finding a recovery boot but why didn't my reverting to stock reinstall the stock recovery? Does anyone have any guides they suggest to get stock recovery back? (I've found a few but thought I would ask).
Now, this is understandable that my phone can't boot into recovery since I flashed CM recovery onto it and whatnot, but I attempted to boot into recovery on my girlfriends phone (same phone, NEVER BEEN UNLOCKED OR FLASHED) and it can't boot into recovery either... Is something going on here or am I just missing a huge piece of the puzzle? I don't really want to have to flash anything on my girlfriends phone to fix it, she's not into the tinkering and would rather not have her data reset. Any help would be appreciated.
And for the record, I did a search to figure this out but at the very least I can only find solutions for people who have flashed CM or similar and nothing pertaining to the problem my girlfriend's phone has.

Tried reflashing recovery already? How did you "revert" to stock?
Sent from my Galaxy Nexus using xda app-developers app

nktje said:
Tried reflashing recovery already? How did you "revert" to stock?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Used this method:
http://forum.xda-developers.com/showthread.php?t=1848566
It worked, I'm on stock ICS, but I didn't do ANYTHING after booting into ICS again and attempting to install JB and booting into recovery. Did I miss something? How do I "flash recovery"?

Unzip the factory image you get from developers.google.com/android/nexus/images
Then use fastboot to flash the recovery.
EDIT: red triangle doesn't necessarily mean the recovery is broken. It's just the way it is. If you wish to flash a 3rd party ROM you'll need to flash a 3rd party recovery.
Sent from my Galaxy Nexus using xda app-developers app

I think you are confusing a few things here. First off, the Android with the red triangle IS the stock recovery main screen. (If you want to flash the update manually, you need CWM -- go into fastboot mode and type: fastboot flash name-of-recovery.img, where name-of-recovery is the recovery that you downloaded and want to flash.) Second, you need the stock recovery for an update to install over-the-air, but you need a custom recovery if you want to flash it manually.

Muffinabus said:
Today, I reverted back to stock and locked the bootloader so that I could receive the stock JellyBean update.
Click to expand...
Click to collapse
this happened. you installed stock recovery when you reverted, whats the surprise?
and you dont need to relock bootloader to successfully update through ota. seems to me know the op needs to refine his searching skills.
nktje said:
EDIT: red triangle doesn't necessarily mean the recovery is broken. It's just the way it is. If you wish to flash a 3rd party ROM you'll need to flash a 3rd party recovery.
Click to expand...
Click to collapse
just press vol up+power to bring up the stock recovery menu.
edit: damn efrant, i got this man
sent from my i9250

nktje said:
Unzip the factory image you get from developers.google.com/android/nexus/images
Then use fastboot to flash the recovery.
EDIT: red triangle doesn't necessarily mean the recovery is broken. It's just the way it is. If you wish to flash a 3rd party ROM you'll need to flash a 3rd party recovery.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
So in the context of my girlfriend's phone where nothing has been done to it in the 4 months she's had it, why would it be giving the recovery error? Also, does flashing the recovery wipe the phone?
It's funny too because I just got the JB OTA but I'd still like to get this figured out.

Muffinabus said:
So in the context of my girlfriend's phone where nothing has been done to it in the 4 months she's had it, why would it be giving the recovery error? Also, does flashing the recovery wipe the phone?
It's funny too because I just got the JB OTA but I'd still like to get this figured out.
Click to expand...
Click to collapse
run the update manually (found on the Update link on efrants sig) through cwm, that should give you a more detailed description of whats going on.
flashing a recovery doesn't wipe the device. unlocking will, btw. its not an error, its the stock recovery!
sent from my i9250

bk201doesntexist said:
run the update manually (found on the Update link on efrants sig) through cwm, that should give you a more detailed description of whats going on.
flashing a recovery doesn't wipe the device. unlocking will, btw. its not an error, its the stock recovery!
sent from my i9250
Click to expand...
Click to collapse
Alright, I think I got it... so the android with the red ! triangle IS stock recovery? I just remember on my Nexus S being able to boot into recovery and load up a stock .zip update manually without any custom recovery mod. Is this not possible on the Galaxy Nexus then? So what does the stock recovery DO other than sit there and reboot after a minute?

Muffinabus said:
Alright, I think I got it... so the android with the red ! triangle IS stock recovery?
Click to expand...
Click to collapse
Correct! As was mentioned by bk201doesntexist, hold power and press volume up to access the menu.
Muffinabus said:
I just remember on my Nexus S being able to boot into recovery and load up a stock .zip update manually without any custom recovery mod. Is this not possible on the Galaxy Nexus then?
Click to expand...
Click to collapse
No, that does not work on the GNex.
Muffinabus said:
So what does the stock recovery DO other than sit there and reboot after a minute?
Click to expand...
Click to collapse
Have a look at the menu, and you can see the options.

efrant said:
Correct! As was mentioned by bk201doesntexist, hold power and press volume up to access the menu.
No, that does not work on the GNex.
Have a look at the menu, and you can see the options.
Click to expand...
Click to collapse
Thank you! I feel like an idiot now. I honestly thought it'd be the same as the Nexus S where you were able to do this...

[Q] Cant flash CWM

I'm trying to get cwm recovery on my htc ove v VM. I have unlocked boot loader and rooted successfully. When i fast boot the recovery image, it says sending writhing and done. When I reboot and try to boot cwm it just stays on the htc screen with the red letters, is this normal? I should think not. I'm sure this has happened to someone else I just need a solution. Any advice would be great.

Hi
CWM is not recommended for CDMA AFAIK
Use TWRP for CDMA instead
max

i4cbj45 said:
I'm trying to get cwm recovery on my htc ove v VM. I have unlocked boot loader and rooted successfully. When i fast boot the recovery image, it says sending writhing and done. When I reboot and try to boot cwm it just stays on the htc screen with the red letters, is this normal? I should think not. I'm sure this has happened to someone else I just need a solution. Any advice would be great.
Click to expand...
Click to collapse
check ur commands it shud be
fastboot flash recovery recovery.img
and check if the image is not broken TWRP 3.0 is come use that!

I got it
cybervibin said:
check ur commands it shud be
fastboot flash recovery recovery.img
and check if the image is not broken TWRP 3.0 is come use that!
Click to expand...
Click to collapse
I got CWM flashed using the android ultimate tool found on this site. Before that nothing worked. The only minor thing is that you have to scroll through the cwm menus three times to get to where you can select with the power button, but then it works fine. I've made my nandroid backup. But haven't flashed a rom yet... kinda nervous about getting into that one, But if you guys have any suggestions about STABLE roms, that would be helpful as well. Thanks,

i4cbj45 said:
I got CWM flashed using the android ultimate tool found on this site. Before that nothing worked. The only minor thing is that you have to scroll through the cwm menus three times to get to where you can select with the power button, but then it works fine. I've made my nandroid backup. But haven't flashed a rom yet... kinda nervous about getting into that one, But if you guys have any suggestions about STABLE roms, that would be helpful as well. Thanks,
Click to expand...
Click to collapse
I don't believe in those all on one Tools,i prefer to do it manually...Cause if u screw up u know where u went wrong.....and check out cm9 its almost stable...i used to use it....i like it....don't be nervous ... flashing is awesome
Sent from my One V using xda app-developers app

[Q] S-Off Recovery problem

Hello! Hi, I'm kinda new to all of this, and I downloaded all of this today. I've been reading a lot and watching a lot of videos, yet I nothing really seems to fix my devices problem.
I have a HTC One on the Verizon carrier and I have just recently S-Off'd it using Rumrunner (I used the Rom checker to make sure it was unlocked and it even says it is whenever i enter bootloader). Although I was successfully able to unlock my device, I seem to have trouble with entering into recovery mode. Whenever I try to go into Recovery mode, my device reads "Entering Recovery mode" in pink at the top for about 10-20 seconds. Then all of a sudden it just goes black and it reboots as if I had never even chosen to go into recovery mode. I don't know if this holds any significance, but I've noticed that my boot up logo only has "HTC ONE" on it, the writing "simply beautiful" is now removed.
I have tried using cmd and ADB to clear the cache, I've tried using ClockManager from Rom Manager, and I've tried multiple times on regular mode. None of them really seem to work and I don't really understand why. Can anyone please offer me some suggestions? Thank you.
Seriously I only want a transparent theme for my HTC One that's all LOL

@Cinestra hey so I'm also kind of new to this but I can try to help. So what custom recovery did you flash?

Chilidog said:
@Cinestra hey so I'm also kind of new to this but I can try to help. So what custom recovery did you flash?
Click to expand...
Click to collapse
I think the person didn't flash one. Flash twrp through fastboot. Don't use ROM manager cwm is getting old
Sent from my HTC6500LVW using xda app-developers app

cstrife999 said:
I think the person didn't flash one. Flash twrp through fastboot. Don't use ROM manager cwm is getting old
Sent from my HTC6500LVW using xda app-developers app
Click to expand...
Click to collapse
Hello, thank you i very much appreciate your advice. I did not try flashing yet.
I just tried to flash TWRP by using Fastboot and the CMD. However I still get no luck. I entered everything in the command prompt fine and it responded nicely. However, whenever I try to go to Recovery mode, the screen just says "entering recovery mode...." and then just turns black 15 seconds later and reboots again :S

Cinestra said:
Hello, thank you i very much appreciate your advice. I did not try flashing yet.
I just tried to flash TWRP by using Fastboot and the CMD. However I still get no luck. I entered everything in the command prompt fine and it responded nicely. However, whenever I try to go to Recovery mode, the screen just says "entering recovery mode...." and then just turns black 15 seconds later and reboots again :S
Click to expand...
Click to collapse
Hmm... That is strange indeed...
Sent from my HTC6500LVW using xda app-developers app

I had the same problem and discovered that when i enter stock recovery, when the black screen appears, i had to press power+vol up to get it to show up. You may have to press them several times to get the timing right. Hope that helps!

cstrife999 said:
I think the person didn't flash one. Flash twrp through fastboot. Don't use ROM manager cwm is getting old
Sent from my HTC6500LVW using xda app-developers app
Click to expand...
Click to collapse
when I got my phone back from sonic, twrp wouldn't install for me so I had to use CWM.
OP should probably try both and make sure he's following the instructions here:
http://forum.xda-developers.com/showpost.php?p=45513789&postcount=2

I'm quite new to rooting as well. Seems we are having the same problem. I was able to get beaups' s-off exploit to work without any problems. When I load into HBoot it says the phone is unlocked and I've also used a Root Checker to determine the phone is rooted.
My next step was to try and install TWRP using fastboot. I ran a command prompt window using administrator rights during the whole process. Everything seemed to install just as it should. The problem is when I try to boot into recovery I'm having the same problem as Cinestra. I simply get the HTC logo screen with "Entering Recovery..." in pink letters at the top of the screen for around 15 seconds, then it reboots as if it would normally and restart the phone as usual. I have tried to reinstall the custom recovery step by step, using 'fastboot erase cache' before and after as well as using an older version of TWRP just in case that would help. Again, everything seems to install just fine but I still can not boot into recovery. I've also tried to see if the GooManager app would be of some help, but that is also not working for me.
I've since also tried flashing CWM but the same situation occurs. Install seems fine but no luck booting into recovery. ROM Manager was a no go as well.
I just can't figure this out. I've tried different cables, deleted and reinstalled HTC drivers/adb/fastboot, and multiple recovery images. I just gave beasleyj62's suggestion of holding down the power/volume down buttons after it goes to black when it starts to restart but that just put me into a bootloop sadly. Had to hold down the power button a few times to get it to boot correctly again. Any help on this would be greatly appreciated. Cheers.
I would also just like to add a little more info on my device in case this will help troubleshoot this. I'm using a Verizon HTC One with Software Number 1.10.605.10.

Same problem here. Tried flashing from fastboot, using goomanager, using rom manager, and from within the terminal emulator (can't find the command now but i think it was on the TWRP site).
Fastboot gives every indication it works, goomanager and rom manager give an error, and the emulator method appeared to work.
Tried to fastboot both TWRP and clockworkmod but neither worked.
At work right now but still investigating...
*edit: goomanager error states 'no recoveries found for your device.'

carassius-one said:
Same problem here. Tried flashing from fastboot, using goomanager, using rom manager, and from within the terminal emulator (can't find the command now but i think it was on the TWRP site).
Fastboot gives every indication it works, goomanager and rom manager give an error, and the emulator method appeared to work.
Tried to fastboot both TWRP and clockworkmod but neither worked.
At work right now but still investigating...
*edit: goomanager error states 'no recoveries found for your device.'
Click to expand...
Click to collapse
ROM manager and goomanager are not supported you have to flash Twrp or CWM via fastboot
Sent from my HTC6500LVW using XDA Premium 4 mobile app
---------- Post added at 09:58 AM ---------- Previous post was at 09:54 AM ----------
I wonder if you guys are having problems because you tried to use rom manager or goomanager and it messed something up...
Sent from my HTC6500LVW using XDA Premium 4 mobile app

Chilidog said:
ROM manager and goomanager are not supported you have to flash Twrp or CWM via fastboot
Click to expand...
Click to collapse
Thanks. That answers that part of the question.

Chilidog said:
ROM manager and goomanager are not supported you have to flash Twrp or CWM via fastboot
Sent from my HTC6500LVW using XDA Premium 4 mobile app
---------- Post added at 09:58 AM ---------- Previous post was at 09:54 AM ----------
I wonder if you guys are having problems because you tried to use rom manager or goomanager and it messed something up...
Sent from my HTC6500LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Didn't realize they weren't supported. Sadly, I don't think they are the culprit here. I tried to flash using fastboot first. I attempted it with 'openrecovery-twrp-2.6.3.0-m7.img' first then with the older version 'openrecovery-twrp-2.6.1.0-m7.img' next. It was the same issue with both. I didn't attempt using GooManager until after I had used fastboot, though GooManager just failed to initialize the install. I mean it didn't even run or change anything as far as I can tell, and simply gave an error back saying "No recoveries were found for your advice".
Did the same thing with CWM and ROM Manager. I installed CWM from fastboot. Only after seeing the same thing happen when I tried to install TWRP did I give ROM Manager a shot. This also just gave an error message without initializing any install. Thanks for the input though.

Prizm432 said:
Didn't realize they weren't supported. Sadly, I don't think they are the culprit here. I tried to flash using fastboot first. I attempted it with 'openrecovery-twrp-2.6.3.0-m7.img' first then with the older version 'openrecovery-twrp-2.6.1.0-m7.img' next. It was the same issue with both. I didn't attempt using GooManager until after I had used fastboot, though GooManager just failed to initialize the install. I mean it didn't even run or change anything as far as I can tell, and simply gave an error back saying "No recoveries were found for your advice".
Did the same thing with CWM and ROM Manager. I installed CWM from fastboot. Only after seeing the same thing happen when I tried to install TWRP did I give ROM Manager a shot. This also just gave an error message without initializing any install. Thanks for the input though.
Click to expand...
Click to collapse
Yeah...I tried the fastboot method first too, for both TWRP and CWM. I really doubt that is the problem.

Two thoughts:
1. Did you have any issues during the S-OFF? How many pours did it take? My thoughts here are that the S-OFF wasn't, for whatever reason, fully clean, which may suggest that you relock and S-ON your phone, and reapply Rumrunner.
2. Did you flash with the decrypted RUU? I would flash the phone with that (the link is somewhere in this subforum) and then try to flash a recovery image.
carassius-one said:
Yeah...I tried the fastboot method first too, for both TWRP and CWM. I really doubt that is the problem.
Click to expand...
Click to collapse

godhamba said:
Two thoughts:
1. Did you have any issues during the S-OFF? How many pours did it take? My thoughts here are that the S-OFF wasn't, for whatever reason, fully clean, which may suggest that you relock and S-ON your phone, and reapply Rumrunner.
2. Did you flash with the decrypted RUU? I would flash the phone with that (the link is somewhere in this subforum) and then try to flash a recovery image.
Click to expand...
Click to collapse
1. I think it was 3 or 4 pours. Seemed to work flawlessly.
2. Still trying to learn which includes learning what an ruu is. Maybe that is my problem. I ran rumrunner and then have been trying to flash a recovery ever since...with no other steps.

godhamba said:
Two thoughts:
1. Did you have any issues during the S-OFF? How many pours did it take? My thoughts here are that the S-OFF wasn't, for whatever reason, fully clean, which may suggest that you relock and S-ON your phone, and reapply Rumrunner.
2. Did you flash with the decrypted RUU? I would flash the phone with that (the link is somewhere in this subforum) and then try to flash a recovery image.
Click to expand...
Click to collapse
1. Nope, I had no issues while doing the S-Off. It took 3 pours for me.
2. I haven't used any RUU for this. So you suggest going back to S-On and locked, then using the RUU? Sorry, still new to the whole process so just want to be clear on procedure. Yeah, I've been considering going back to complete stock and starting from scratch again. I'll give that a go later tonight if I can't come up with anything else.
Thanks.

No, no. The only RUU available is a decrypted one, which can only be flashed while S-OFF. So the ideas I put down were distinct, and not steps. My thought is that either (i) you return yourself to full stock and non-root as is explained in a thread in this subforum, or alternatively, (ii) flash the RUU to get a fully untouched setup (the RUU contains the factory "rom", bootloader and recovery and will return it to being fresh from the factory) on the device and then flash the recovery.
Prizm432 said:
1. Nope, I had no issues while doing the S-Off. It took 3 pours for me.
2. I haven't used any RUU for this. So you suggest going back to S-On and locked, then using the RUU? Sorry, still new to the whole process so just want to be clear on procedure. Yeah, I've been considering going back to complete stock and starting from scratch again. I'll give that a go later tonight if I can't come up with anything else.
Thanks.
Click to expand...
Click to collapse

Cinestra said:
I just tried to flash TWRP by using Fastboot and the CMD. However I still get no luck. I entered everything in the command prompt fine and it responded nicely. However, whenever I try to go to Recovery mode, the screen just says "entering recovery mode...." and then just turns black 15 seconds later and reboots again :S
Click to expand...
Click to collapse
I had the same problem and yesterday I posted my fix in this Forum's TWRP thread.
I had been using
openrecovery-twrp-2.6.3.0-m7.img
What I really needed was
openrecovery-twrp-2.6.3.0-m7vzw.img
Go here: http://goo.im/devs/Flyhalf205/M7VZW/openrecovery-twrp-2.6.3.0-m7vzw.img

beasleyj62 said:
I had the same problem and discovered that when i enter stock recovery, when the black screen appears, i had to press power+vol up to get it to show up. You may have to press them several times to get the timing right. Hope that helps!
Click to expand...
Click to collapse
Thanks for your solution, unfortunately though, it doesn't seem to work.
jpradley said:
I had the same problem and yesterday I posted my fix in this Forum's TWRP thread.
I had been using
openrecovery-twrp-2.6.3.0-m7.img
What I really needed was
openrecovery-twrp-2.6.3.0-m7vzw.img
Click to expand...
Click to collapse
Hmm alright so you suggest flash this other version of TWRP instead? That would make sense because the link looks like it's specialized for Verizon. I will try that out today!
godhamba said:
Two thoughts:
1. Did you have any issues during the S-OFF? How many pours did it take? My thoughts here are that the S-OFF wasn't, for whatever reason, fully clean, which may suggest that you relock and S-ON your phone, and reapply Rumrunner.
2. Did you flash with the decrypted RUU? I would flash the phone with that (the link is somewhere in this subforum) and then try to flash a recovery image.
Click to expand...
Click to collapse
1. It took me about 3 pours. That is an interesting thought and I think it may very well be valid, but I would prefer not to reset or relock my device though.
2. I have not decrypted RUU yet because I was unfamiliar with the term. I may try this if the new TWRP code does not work

@Prizm432 it looks like you are flashing the wrong Twrp zip. It has to end in m7vzw.zip
Sent from my HTC6500LVW using XDA Premium 4 mobile app

Can't flash a recovery ROM to HTC One Verizon

I might be doing something wrong but I can't flash any recovery ROMs to my HTC One. I used rumrunner S-off today and gained root access with my stock ROM. I tried using command prompt to flash a TWRP recovery ROM, and it only worked once but now whenever I try to do it it says either "cannot load image" or gives me a partition error.
I tried going into recovery with the one I flashed and when it says entering recovery mode it either goes into a continuous reboot cycle or proceeds to the lockscreen. I tried using flashify today too and it says my device isn't compatible with any of the recovery ROMs.
Please help, I'm so frustrated and all I want to do is flash Android Revolution to my HTC! Also, was I supposed to factory reset my phone before all this? Because I still have all my apps, photos, data, etc.
P.S. I'm a noob at this stuff so I might be doing something wrong.

Try Flashify from the play store. Put the recovery on the Flashify app and flash if.
sent from my HTC One

jbh00jh said:
Try Flashify from the play store. Put the recovery on the Flashify app and flash if.
sent from my HTC One
Click to expand...
Click to collapse
No luck. Flashify won't install anything

ak074 said:
we will need more information about what all you've been trying and the results.
s-off was successful?
bootloader locked/unlocked?
what are you typing into the cmd prompt?
result from that cmd?
where did you get the recovery from? are you sure it's for the vzw htc one?
etc...
Click to expand...
Click to collapse
S-off was successful.
Bootloader is unlocked (And somehow the phone became rooted in the process)
cmd prompt: fastboot flash recovery recovery.img
cmd prompt kept saying something about unable to load the image
Got the recovery from ClockWork Mod - It is Verizon HTC One version
Thank you guys for your concern but I figured it all out. I used an all-in-one toolkit and it flashed my recovery without a problem. Now I have a Nandroid backup for stock rooted ROM, and flashed BoneStock onto my device! It is all working great and my battery life rocks!

shadowskaya said:
No luck. Flashify won't install anything
Click to expand...
Click to collapse
OK first off make sure the recovery you are trying to flash ends in m7vzw.img second, Flashify doesn't work for everyone so you might have to do it from adb on your computer. And finally, there is no android revolution rom for the Verizon htc one.

The developer of Flashify has a thread in Android developing and hacking/ apps and games / Flashify. Sometimes these threads have updates posted before the play store does. Start at the back of the thread and read toward the beginning,find the latest info faster (about a 25 page thread).
Sent from my Galaxy Tab 10.1

shadowskaya said:
Thank you guys for your concern but I figured it all out. I used an all-in-one toolkit and it flashed my recovery without a problem. Now I have a Nandroid backup for stock rooted ROM, and flashed BoneStock onto my device! It is all working great and my battery life rocks!
Click to expand...
Click to collapse
You should try to do these things without using all-in-one kits. It's best to know what was done in case something goes wrong in the future. My guess is you were most likely trying to flash the wrong recovery.
Well, at least you're up and running!

karn101 said:
You should try to do these things without using all-in-one kits. It's best to know what was done in case something goes wrong in the future. My guess is you were most likely trying to flash the wrong recovery.
Well, at least you're up and running!
Click to expand...
Click to collapse
Thank you for the tip, I will remember that the next time I flash a recovery to something. It was the correct recovery, but for some reason the fastboot and adb wouldn't flash it. Maybe I just needed a reboot of pc or something...

Had the same issue after s-off with twrp. Ended up flashing cwm touch instead and it works just as well. Although I do miss twrp.
Sent from my One using XDA Premium 4 mobile app

[Q] Can't Boot - Tough Question

Hey there. So I'm new to XDA but not so much to flashing and what not. I often, however, do dumb tests that fail and brick my phone, but I always get it back. This one is a little tougher. Here are the details:
-HTC One (M8) T-Mobile
-Phone was unlocked and rooted (still unlocked, not sure about rooted), but S-On.
-Tried flashing a kernel with S-On. Turned out to be packaged in a recovery. Didn't go so well. Turning the device on always went straight to Fastboot mode.
-Eventually got Philz recovery installed. Tried sideloading a nandroid backup. No avail. Still booting straight to fastboot.
Any ideas? Not a genius, but I know my way around. Is there any 100% complete refresh coming straight from Fastboot?

What exactly did you try to flash?
Sent from my HTC One_M8 using Tapatalk

djmatt604 said:
What exactly did you try to flash?
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
The new OTA update first. When that didn't work, I tried flashing the stock kernel back.

Go here, read, try it.
Look at last few posts as well concerning tmo
http://forum.xda-developers.com/showthread.php?p=52242287

umjammerlammy said:
Go here, read, try it.
Look at last few posts as well concerning tmo
http://forum.xda-developers.com/showthread.php?p=52242287
Click to expand...
Click to collapse
I haven't read the thread in that link, but in my experience when it boots straight to recovery it means the boot image is corrupt or missing. Not sure if you can do this with s-on, but to get back to normal I flashed twrp then downloaded and flashed a stock nandroid backup, then flashed an OTA via TWRP. After that everything was back to normal.

ashyx said:
I haven't read the thread in that link, but in my experience when it boots straight to recovery it means the boot image is corrupt or missing. Not sure if you can do this with s-on, but to get back to normal I flashed twrp then downloaded and flashed a stock nandroid backup, then flashed an OTA via TWRP. After that everything was back to normal.
Click to expand...
Click to collapse
Ah, yes.
This also would work.
Most likely he's got OS-