I tried to install the CWM Recovery using Odin. Device gets stuck in BootLoop with......
1. RECOVERY BOOTING (in blue),
2. RECOVERY IS NOT SEANDROID ENFORCING (red)
3. Set Warranty Bit: recovery (yellow)
Cant Boot in download mode
It isnt recognized by the pc, odin or kies
Havet find a clear answer in previous posts. Any help?
luisjo2k said:
I tried to install the CWM Recovery using Odin. Device gets stuck in BootLoop with......
1. RECOVERY BOOTING (in blue),
2. RECOVERY IS NOT SEANDROID ENFORCING (red)
3. Set Warranty Bit: recovery (yellow)
Cant Boot in download mode
It isnt recognized by the pc, odin or kies
Havet find a clear answer in previous posts. Any help?
Click to expand...
Click to collapse
I am in this situation right now as well after flashing CWM recovery via ODIN. Hopefully someone has an answer. Did you find anything?
Try to overwrite your recovery with Philz Touch. It's working perfect for G900 variants so far:
Philz Touch Recovery Download
babygau said:
Try to overwrite your recovery with Philz Touch. It's working perfect for G900 variants so
Click to expand...
Click to collapse
I was finally able to get the phone into download mode by pulling the battery so I just pushed TWRP to it to fix the CWM issues. I'll check out Philz Touch as well though. Thanks.
knoxrents said:
I was finally able to get the phone into download mode by pulling the battery so I just pushed TWRP to it to fix the CWM issues. I'll check out Philz Touch as well though. Thanks.
Click to expand...
Click to collapse
Great!
IMO, Philz Touch is more beatiful and more functional than TWRP
Hi guys - I had this same issue today. I'd also installed CWM and tried to go into recovery mode via ROM Manager when it happened.
Looked around and after finding this thread I managed to flash with Philz Touch and got it to boot. Managed to get it into recovery mode and run this new Philz Touch version of CWM and do a backup. However just before it got into CWM it still came up with:
1. RECOVERY BOOTING (in blue),
2. RECOVERY IS NOT SEANDROID ENFORCING (red)
3. Set Warranty Bit: recovery (yellow)
Then loaded into CWM whereas before flashing Philz it was just looping. Is there a way I can stop it from coming up with this?
jeemer said:
Hi guys - I had this same issue today. I'd also installed CWM and tried to go into recovery mode via ROM Manager when it happened.
Looked around and after finding this thread I managed to flash with Philz Touch and got it to boot. Managed to get it into recovery mode and run this new Philz Touch version of CWM and do a backup. However just before it got into CWM it still came up with:
1. RECOVERY BOOTING (in blue),
2. RECOVERY IS NOT SEANDROID ENFORCING (red)
3. Set Warranty Bit: recovery (yellow)
Then loaded into CWM whereas before flashing Philz it was just looping. Is there a way I can stop it from coming up with this?
Click to expand...
Click to collapse
I'm using TWRP and the same thing comes up. It only comes up for a few seconds so I just don't worry about it. With CWM recovery, it was locked on that screen.
knoxrents said:
I was finally able to get the phone into download mode by pulling the battery so I just pushed TWRP to it to fix the CWM issues. I'll check out Philz Touch as well though. Thanks.
Click to expand...
Click to collapse
I have the same problem but when I pull the battery, then reinstall it I get the same result, I need help in a major way this is a brand new company phone
Noebody said:
I have the same problem but when I pull the battery, then reinstall it I get the same result, I need help in a major way this is a brand new company phone
Click to expand...
Click to collapse
I fixed it!!!
..
S5 set warranty bit recovery (G900i)
I know that philz recovery is best solutino but when I am going to download philz it's giving this error:
Hello,
Unfortunately, as of this time, the main portions of goo.im have been disabled. Due to a finance issue, our CDN account has been suspended, and all files stored on it are effectively non-accessible. Due to some RL issues on my(Alexander)'s part, once goo started actively losing money 6 months ago, I had changed jobs a bit to help support goo. Unfortunately, this wasn't enough combined with some other issues that crept up on me. Due to this, I'm formally shutting down Goo. There is an offer in to take over the files and hosting from a generous sponsor, however, until the financial issues are sorted out, they are unable to adsorb Goo. It's been my pleasure to serve files for you all for the past couple of years, and I wish everyone good luck into the future.
-- Snipa/Alexander Blair
If you have picked up a sponor account within the last two months, please reach out to us if you'd like a refund. It may take some time, but we'll do our best to get these processed and sent out. -- Thanks for everyone who's supported us over the years.
Noebody said:
I fixed it!!!
Click to expand...
Click to collapse
How? Same problem here.
jdrch said:
How? Same problem here.
Click to expand...
Click to collapse
I just saw this, and honestly I don't remember. Remind me what's happening and maybe it'll jog my memory
Related
Dear all, I recently tried rooting my device (i5905) and run into some trouble. Here is what I did:
1) I followed this guide a guide called how-to-root-galaxy-s4-using-twrp-method such that I now have a working TWRP installed.
2) When I rebooted I noticed the message "SuperSu has stopped". I found out that I was using an old version of SuperSu (0.99) and updated the version through the play store. After that I was able to open the App but it said that it wasn't set up correctly - I don't remember the exact message.
3) I closed SuperSu, downloaded the newest version from the web to my device and installed the zip file with TWRP. Unfortunately, this brought me back to the state where every time I want to start the App I get the error "Unfortunately, SuperSu has stopped".
4) Some people claimed that it could be a Knox issue, even though I never got any security warning, I decided to download a "Knox" remover script which I ran through TWRP. This removed Knox (it is no longer listed under Apps) but it does not stop the error message from SuperSu poping up.
5) I'm unable to update SuperSu because I'm already on the newest version and I can't remove it either.
Any ideas how I should progress?
Thank you very much!
Try touch philz method
RubbaBand said:
Try touch philz method
Click to expand...
Click to collapse
Could you give a little bit more context on why I should try this and what it would fix? I'm new to this so I don't have a lot of knowledge.
Also couldn't that give me some problem because I already installed TWRP...
S4 have alot of updates NB3, NB4, NC1, NC2, elc...
Some of the updates lets the method you want to use useless
The touch philz custom recovery lets you root your device from recovery
You chould try it out
RubbaBand said:
S4 have alot of updates NB3, NB4, NC1, NC2, elc...
Some of the updates lets the method you want to use useless
The touch philz custom recovery lets you root your device from recovery
You chould try it out
Click to expand...
Click to collapse
Okay so I would assume I just follow these instructions:
http://forum.xda-developers.com/showthread.php?p=39433857#post39433857
Then I ignore the fact that I already installed TWRP and just install it? And once I installed it, there will be an option to root without using SuperSu?
Thanks.
After going to recovery go to philz options > reroot
The system will be rooted
If you didnt find SuperSu after boot
Download it from google play
RubbaBand said:
After going to recovery go to philz options > reroot
The system will be rooted
If you didnt find SuperSu after boot
Download it from google play
Click to expand...
Click to collapse
Sorry but I have trouble following the instructions. I downloaded Odin 309 and was able to put Philz Recovery on my phone. I restarted my phone and it seems like I'm unable to enter the recovery mode. I hold down all three keys (VolUp) and the blue font in the corner appears but after a few second the phone just shuts down. I'm still able to boot normal, just not into recovery mode. I thought it might be because of my low battery but even after charging (70%) the problem persists.
I also noted that it was hard to get into Download mode (needed 3 attempts). Maybe removing Knox caused some problems - although it should really affect this? Any ideas?
Sy1vus said:
Sorry but I have trouble following the instructions. I downloaded Odin 309 and was able to put Philz Recovery on my phone. I restarted my phone and it seems like I'm unable to enter the recovery mode. I hold down all three keys (VolUp) and the blue font in the corner appears but after a few second the phone just shuts down. I'm still able to boot normal, just not into recovery mode. I thought it might be because of my low battery but even after charging (70%) the problem persists.
I also noted that it was hard to get into Download mode (needed 3 attempts). Maybe removing Knox caused some problems - although it should really affect this? Any ideas?
Click to expand...
Click to collapse
Just hold volume up & power buttons til it says booting recovery then release both & should boot up ? I occasionally have probably entering recovery but that always works
11calcal said:
Just hold volume up & power buttons til it says booting recovery then release both & should boot up ? I occasionally have probably entering recovery but that always works
Click to expand...
Click to collapse
I did exactly that, somehow it worked after the 11th try - seriously. But thanks!!
I downloaded SuperSu from the play store. It now ask me to install the SU binary. Should I click "Normal" or "TWRP/CWM"?
Thanks once again!
Hit normal !!
Hello all, long time lurker, first time poster
I was wondering if there is currently a way to get a custom recovery on my phone without the use of a computer. I was able to root my phone using towel root, and first thing I did was install Rom Manager and start to make a nandroid backup until I got:
" RECOVERY BOOTING...
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit: recovery"
So I went into download mode, hit cancel and was able to boot into android but to this day I am unable to get into recovery, stock or custom. Due to my current complicated situation I do not have access to a computer and was hoping there was a work around to allow me to implement a custom recovery without a pc. I want to be able to make a nandroid backup, flash zips into the OS, and possibly experiment with other roms... I have tried looking into this myself but the only thing I came up with us an app called "Flashing Tool", though I don't know whether that will allow me to do what I want it to. Oh, and I don't care about Knox being flagged by the way.
So ladies and gentlemen of the Xda community, I beg for your assistance and would greatly appreciate any answers you can give me.
My phone is a T-Mobile Note 3, rooted stock Kit Kat rom, any other info needed just let me know.
Brooklynyte said:
Hello all, long time lurker, first time poster
I was wondering if there is currently a way to get a custom recovery on my phone without the use of a computer. I was able to root my phone using towel root, and first thing I did was install Rom Manager and start to make a nandroid backup until I got:
" RECOVERY BOOTING...
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit: recovery"
Click to expand...
Click to collapse
That is the standard message while recovery is booting. How long did you wait?
FeralFire said:
That is the standard message while recovery is booting. How long did you wait?
Click to expand...
Click to collapse
After that message it just restarts into a boot loop showing that message over and over until I pull the battery, boot into download mode and then hit cancel so the phone boots up normally. Currently I do not have a recovery menu at all, not stock, and not custom.
Brooklynyte said:
After that message it just restarts into a boot loop showing that message over and over until I pull the battery, boot into download mode and then hit cancel so the phone boots up normally. Currently I do not have a recovery menu at all, not stock, and not custom.
Click to expand...
Click to collapse
Ok, try mobile odin.
FeralFire said:
Ok, try mobile odin.
Click to expand...
Click to collapse
Ok, installed Mobile Odin, first thing it said was to make sure I have the proper boot loader or it could result in a soft brick. Now it shows me the different partitions, one of them being "recovery"... Now what file exactly should I be using? Do I flash it to that partition or do I just use the" Open file" option? Can you guide me through it at all? I appreciate all your help thus far!
Edit: I believe I found the correct file to flash... Please correct me if I'm wrong but being that I have the T-Mobile version of the Note 3, my boot loader should not be locked right? So I should be able to flash this file *n9005-cwm-recovery-6.0.4.7-kk(0125).tar* using mobile odin, and all should be good, right? I would post the link but I'm a new user and cant... But this is the description of the file: SM-N9005/SM-N900T/SM-N900P Qualcomm Note 3 – CWM Recovery -*Download*-*Credits*(Also works for T-Mobile/Sprint)
Brooklynyte said:
Ok, installed Mobile Odin, first thing it said was to make sure I have the proper boot loader or it could result in a soft brick. Now it shows me the different partitions, one of them being "recovery"... Now what file exactly should I be using? Do I flash it to that partition or do I just use the" Open file" option? Can you guide me through it at all? I appreciate all your help thus far!
Click to expand...
Click to collapse
I have never personally used Mobile Odin, but you need to flash the recovery's tar file in the software.
FeralFire said:
I have never personally used Mobile Odin, but you need to flash the recovery's tar file in the software.
Click to expand...
Click to collapse
You my dear friend, have my everlasting gratitude! I now have a working cwm recovery! Maybe I should make a quick guide to show how to root and flash custom recovery without a computer... Lord knows I could have used a guide like that. Thank you Feral....
Brooklynyte said:
You my dear friend, have my everlasting gratitude! I now have a working cwm recovery! Maybe I should make a quick guide to show how to root and flash custom recovery without a computer... Lord knows I could have used a guide like that. Thank you Feral....
Click to expand...
Click to collapse
Just press the thanks button.
And you are welcome.
Hello,
I've rooted my phone using the towelroot method and everything seems to be ok. I checked my root status and it came back clean. Got the SuperSU and installed the binary. Now the problem is, I have a bad recovery. Everytime I go to install a ROM from SD, or use ROM manager to install a rom, my phone boots into recovery but I get the "Could Not Boot Normal" - Odin Mode
Downloading... Do not turn off target! And it just hangs there. I'm able to reboot using vol down + home + power and cancelling the "download" - but there shouldn't be anything to download - the ROM is on my SD card. Does this mean that I have a curropted recovery? I currently have both ClockworkMod and TWRP installed. I can't seem to get rid of one or the other.
Any recommendations? I really want to throw a 4.4.3 Rom on this device.
Thanks in advance.
You cannot instal custom ROM from stock recovery.
You need to have custom recovery (CWM, TWRP...) but this step void knox to 0x1.
fant0m88 said:
Hello,
I've rooted my phone using the towelroot method and everything seems to be ok. I checked my root status and it came back clean. Got the SuperSU and installed the binary. Now the problem is, I have a bad recovery. Everytime I go to install a ROM from SD, or use ROM manager to install a rom, my phone boots into recovery but I get the "Could Not Boot Normal" - Odin Mode
Downloading... Do not turn off target! And it just hangs there. I'm able to reboot using vol down + home + power and cancelling the "download" - but there shouldn't be anything to download - the ROM is on my SD card. Does this mean that I have a curropted recovery? I currently have both ClockworkMod and TWRP installed. I can't seem to get rid of one or the other.
Any recommendations? I really want to throw a 4.4.3 Rom on this device.
Thanks in advance.
Click to expand...
Click to collapse
verny94 said:
You cannot instal custom ROM from stock recovery.
You need to have custom recovery (CWM, TWRP...) but this step void knox to 0x1.
Click to expand...
Click to collapse
And if you install a custom recovery you will void your warranty......
EDIT sorry i did not read the last part of the reply of verny94
HI guys,
Thanks for the replies, though I'm not sure I understand them. I have two recoveries installed, according to Rom Manager - Clockworkd and TWRP. Are these the stock recoveries? I guess I thought that's all I needed. I'm not concerned about the warranty too much.
fant0m88 said:
HI guys,
Thanks for the replies, though I'm not sure I understand them. I have two recoveries installed, according to Rom Manager - Clockworkd and TWRP. Are these the stock recoveries? I guess I thought that's all I needed. I'm not concerned about the warranty too much.
Click to expand...
Click to collapse
Hi,
When you enter in recovery , which one you see?
MAX 404 said:
Hi,
When you enter in recovery , which one you see?
Click to expand...
Click to collapse
Thanks for the reply! When I go to ROM Manager and select "Reboot into Recovery" it asks if I want to boot into Clockworkmod. I hit yes, and the phone reboots, but then goes to the this (attached) page and stays there. Then I have to do Vol down Home Power to cancel the "download" to boot normally.
I had a Droid Eris and HTC Thunderbold that I successfully rooted back in their day - but this one click towelroot seems to have screwed me up a little - though to be fair, the majority of fault probably rests at my feet.
fant0m88 said:
Thanks for the reply! When I go to ROM Manager and select "Reboot into Recovery" it asks if I want to boot into Clockworkmod. I hit yes, and the phone reboots, but then goes to the this (attached) page and stays there. Then I have to do Vol down Home Power to cancel the "download" to boot normally.
I had a Droid Eris and HTC Thunderbold that I successfully rooted back in their day - but this one click towelroot seems to have screwed me up a little - though to be fair, the majority of fault probably rests at my feet.
Click to expand...
Click to collapse
Do not use any Managers etc. They´ve made a lot of problems.
If you don´t have problem with warranty use CF-Auto-Root. Towelroot is good only for people who wants warranty.
CWM or TWRP flash via Odin and you will see
verny94 said:
Do not use any Managers etc. They´ve made a lot of problems.
If you don´t have problem with warranty use CF-Auto-Root. Towelroot is good only for people who wants warranty.
CWM or TWRP flash via Odin and you will see
Click to expand...
Click to collapse
Great, thanks for the tip. Should I un-root the phone then? I have the option in the toolbox. Unroot then re-root using the Odin method?
Thanks again!
fant0m88 said:
Thanks for the reply! When I go to ROM Manager and select "Reboot into Recovery" it asks if I want to boot into Clockworkmod. I hit yes, and the phone reboots, but then goes to the this (attached) page and stays there. Then I have to do Vol down Home Power to cancel the "download" to boot normally.
I had a Droid Eris and HTC Thunderbold that I successfully rooted back in their day - but this one click towelroot seems to have screwed me up a little - though to be fair, the majority of fault probably rests at my feet.
Click to expand...
Click to collapse
Hi mate,
That is not recovery mode , you are in download mode ( flashing with Odin)
Check here
http://axeetech.com/2013/07/29/how-...xy-s4-gt-i9500-int-and-gt-i9505/#.U7wlpvl5NQE
Try to get into recovery to see which one you have
fant0m88 said:
Great, thanks for the tip. Should I un-root the phone then? I have the option in the toolbox. Unroot then re-root using the Odin method?
Thanks again!
Click to expand...
Click to collapse
For thanks there is a button Yep you wrote it wright.
Also as MAX 404 said check your recovery. It´s the last flashed one
fant0m88 said:
Hello,
I've rooted my phone using the towelroot method and everything seems to be ok. I checked my root status and it came back clean. Got the SuperSU and installed the binary. Now the problem is, I have a bad recovery. Everytime I go to install a ROM from SD, or use ROM manager to install a rom, my phone boots into recovery but I get the "Could Not Boot Normal" - Odin Mode
Downloading... Do not turn off target! And it just hangs there. I'm able to reboot using vol down + home + power and cancelling the "download" - but there shouldn't be anything to download - the ROM is on my SD card. Does this mean that I have a curropted recovery? I currently have both ClockworkMod and TWRP installed. I can't seem to get rid of one or the other.
Any recommendations? I really want to throw a 4.4.3 Rom on this device.
Thanks in advance.
Click to expand...
Click to collapse
I'm currently having the same problem and my recovery mode always sends me to Odin mode. Were you able to fix it in any way?
Hello Guys,
I need your help. I tryed to install TWRP like it is showed in this video. https://www.youtube.com/watch?v=gAaK6m38ntw&feature=youtu.be
My phone stucks in the booting screen shown in 2:36
I don´t know what to do now
Taking battery out from phone and turning it on dind´t helped
I made a backup of my recovery with the app and I have the backup file on my computer
Well after trying a lot I went into the odin mode and accidently pressed volume down so my phone restarts. It actually restared but I still can´t go into recovery mode. Any suggestions what to do? I still have the backup of my stuck recovery on my phone and PC
BTW: I want the custom recovery to perform a nandroid backup, is it possible to do it without? I am coming from Nexus where you need it to do
Which version of TWRP did you install? If you installed 2.8.5.0, replace it with 2.8.4.0 via Odin and you'll be fine.
Strephon Alkhalikoi said:
Which version of TWRP did you install? If you installed 2.8.5.0, replace it with 2.8.4.0 via Odin and you'll be fine.
Click to expand...
Click to collapse
Yes it was 2.8.5.0 . Is there any issue with that version of TWRP?
Other than the obvious?
2.8.5.0 hasn't worked on the I9505 since release. Every time you try booting into TWRP, it hangs on the splash screen as you described. It's something that I believe has been brought to the developer's attention, but you may want to do the same.
2.8.4.0 hasn't had these problems. The main difference between the two is that 2.8.5.0 upscales or downscales theme resources to fit the screen size. Something in that code is reacting with the S4 and causing it to hang when trying to enter recovery.
Strephon Alkhalikoi said:
Other than the obvious?
2.8.5.0 hasn't worked on the I9505 since release. Every time you try booting into TWRP, it hangs on the splash screen as you described. It's something that I believe has been brought to the developer's attention, but you may want to do the same.
2.8.4.0 hasn't had these problems. The main difference between the two is that 2.8.5.0 upscales or downscales theme resources to fit the screen size. Something in that code is reacting with the S4 and causing it to hang when trying to enter recovery.
Click to expand...
Click to collapse
Oh, Okay I thought it was my own fault and not the one of the developers. Thank you man
BTW: Can I use the app shown in the video to flash TWRP instead of using Odin?
I'd use TWRP Manager instead. It allows you to select which recovery to install.
Ok, so I finally decided to try installing Philz recovery on my GS4. I tried it with the recovery's unified build through CWM Touch, and I didn't use the Loki Doki zip file to patch it. It seemed to boot up just fine, but when I tried restarting the phone and have it automatically boot into Philz using the Cyanogen reboot menu, it brought up the unauthorized software screen with the message on the top left saying "Secure Fail: Kernel". I could not get to the recovery or boot into Android because every time I tried turning it on to just boot into Android, it tries to start Philz. I'd really hate the experience of going back to stock to fix this, so I tried finding a different solution...
And just as I was typing this I found out that I can, in fact, still boot into Android by holding down the down and home buttons, then saying no to the download mode confirmation with down. I think my problem with installing Philz was just that I didn't use Loki Doki because I've seen that CWM Touch doesn't Loki automatically when I first tried flashing the Alucard kernel, and I didn't use the Loki Doki zip file when flashing Philz. I'd appreciate some confirmation and any extra info on what happened here before I try again, as well as whether or not stock recovery images include updates to the bootloader, cause I'd hate to accidentally get stuck with a more restrictive updated one if I ever have to use the one I found.
I'll check this thread tomorrow seeing as it's almost 4am here and my brain has nearly gone full derp after hours of researching this :silly:
AnitaMedic said:
Ok, so I finally decided to try installing Philz recovery on my GS4. I tried it with the recovery's unified build through CWM Touch, and I didn't use the Loki Doki zip file to patch it. It seemed to boot up just fine, but when I tried restarting the phone and have it automatically boot into Philz using the Cyanogen reboot menu, it brought up the unauthorized software screen with the message on the top left saying "Secure Fail: Kernel". I could not get to the recovery or boot into Android because every time I tried turning it on to just boot into Android, it tries to start Philz. I'd really hate the experience of going back to stock to fix this, so I tried finding a different solution...
And just as I was typing this I found out that I can, in fact, still boot into Android by holding down the down and home buttons, then saying no to the download mode confirmation with down. I think my problem with installing Philz was just that I didn't use Loki Doki because I've seen that CWM Touch doesn't Loki automatically when I first tried flashing the Alucard kernel, and I didn't use the Loki Doki zip file when flashing Philz. I'd appreciate some confirmation and any extra info on what happened here before I try again, as well as whether or not stock recovery images include updates to the bootloader, cause I'd hate to accidentally get stuck with a more restrictive updated one if I ever have to use the one I found.
I'll check this thread tomorrow seeing as it's almost 4am here and my brain has nearly gone full derp after hours of researching this :silly:
Click to expand...
Click to collapse
Stock recovery files won't update bootloader, just make sure to use the correct one for your bootloader. It should only be a matter of loki, just make sure you follow specific install instructions.
Sent from my SGH-I337