Hi everyone!
Today I attempted to install a ROM for the first time using ROM Manager. I flashed Clockwork Mod Recovery and then downloaded CyanogenMod and tried to install it (pressed Reboot / Install in ROM Manager). My phone then went into Download/Odin mode. It then didn't do anything for ~10 minutes, and after taking out the battery, the phone still went into Download mode. I got it to boot normally by pressing Home + Power + Volume Down and then pressing cancel when it prompted me to enter download mode. However, every time I attempt to boot into recovery, normally or ClockWork, the phone just goes to download mode. I even tried to do a factory reset, and the phone booted again into Download Mode.
Does anyone know how I can fix this?
Thanks!
Vahgi said:
Hi everyone!
Today I attempted to install a ROM for the first time using ROM Manager. I flashed Clockwork Mod Recovery and then downloaded CyanogenMod and tried to install it (pressed Reboot / Install in ROM Manager). My phone then went into Download/Odin mode. It then didn't do anything for ~10 minutes, and after taking out the battery, the phone still went into Download mode. I got it to boot normally by pressing Home + Power + Volume Down and then pressing cancel when it prompted me to enter download mode. However, every time I attempt to boot into recovery, normally or ClockWork, the phone just goes to download mode. I even tried to do a factory reset, and the phone booted again into Download Mode.
Does anyone know how I can fix this?
Thanks!
Click to expand...
Click to collapse
U Can't install any other recovery if your are on MK2 firmware. .... I'm assuming that was your original firmware anyway. ....Since u don't give enough information so we can help you......U soft bricked your phone by installing custom recovery .....U CAN ONLY INSTALL SAFESTRAP RECOVERY .......Follow my thread on post #3 http://forum.xda-developers.com/showthread.php?t=2573080...... Try flashing i337mk2stockrecovery.tar.md5 from Odin....... go to download /Odin mode from your phone since u stuck in there anyway.... open Any ODIN version. .... flash that files on PDA slot. .... It should get your stock Mk2 recovery. .... check this thread by @guut13 http://forum.xda-developers.com/showthread.php?t=2616221 there is alot of information regarding MK2 firmware. .... rooting method. .... List of compatible custom and stock 4.3 firmware. ......Please READ before u damage your phone even more.....If I helped u please hit Thank button. ..... or u can pm me if u need more help ...... Goodluck. ...
Swyped from MK2 Dark Carnage SS Edition
This is not the first time i root an android device but it is the first time im doing it on an S5, nonetheless I am pretty much stuck right now.
I tried to install CF-Auto-Root-klte-kltexx-smg900f.tar using Odin from here, it installed with no problems, but when the phone restarted I get:
RECOVERY BOOTING
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit: recovery
and then it shuts down.
I tried to enter recovery mode by doing power+vol up+menu but nothing happens ?
Can anyone help ?
EDIT: ok, so I did manage to get it running again by flashing openrecovery-twrp-2.8.5.0-gt-klte. This got me past the "Recovery is not seandroid...", but all in all I still didn't manage to get root access...
I passed through a similar situation , all u have to do once u've got the recovery is get the SuperSU flashable zip and flash it and ur done
Here is a direct link : https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?retrieve_file=1
This happened to me also. I am running XXU1BOJ1 . I flashed twrp-2.8.7.0-klte.img and even though it solved getting stuck at recovery, my phone still boots into the standard recovery instead of TWRP when pressing VOLUP+Home+Power. Anyone got ideas?
xmun said:
This happened to me also. I am running XXU1BOJ1 . I flashed twrp-2.8.7.0-klte.img and even though it solved getting stuck at recovery, my phone still boots into the standard recovery instead of TWRP when pressing VOLUP+Home+Power. Anyone got ideas?
Click to expand...
Click to collapse
You don't flash .img - you flash .tar
*Detection* said:
You don't flash .img - you flash .tar
Click to expand...
Click to collapse
I did flash .img.tar actually. Still no effect - boots to regular recovery. Can't figure this out...
i get in the same situation...why still rebooting in original recovery?
i installed this one CF-Auto-Root-klte-kltexx-smg900f.tar with odin with succes but still have
RECOVERY BOOTING
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit: recovery
then when i boot i get a black screen with all application error....the only way to get it back working was to wipe factory reset in original recovery.
what can i do to get it working so i can install custom roms?
thx in avance
seaskyways said:
I passed through a similar situation , all u have to do once u've got the recovery is get the SuperSU flashable zip and flash it and ur done
Here is a direct link : https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?retrieve_file=1
Click to expand...
Click to collapse
I can't seem to get the coustom recovery installed, and after some digging i found this :
manubhargav said:
Actually the problem was that custom recovery(twrp here) was not installed at all, that above mentioned error occurs when you try to install SuperSU.zip from stock recovery<3e>.
This happens because when you flash custom recovery from Odin and allow it to reboot on its own, Samsung's recovery checking script checks if a custom recovery is present and overrides.
To bypass that check you need to take your battery out as soon as the recovery is flashed by Odin ( and before the phone reboots).
As soon as the Odin says PASS you should be ready to take out the battery which will stop it from rebooting,
put back the battery and enter recovery mode directly by pressing and holding Volume Up, Home and Power keys at the same time.
Release all three buttons when Samsung Galaxy S5 screen flickers and the main screen of Recovery mode appears.
This will avoid script checking and will let you to custom recovery directly,there you can install SuperSU or any other zip.
Click to expand...
Click to collapse
The thing is, when i try to do that, and then get into recovery i get
Could not do normal boot.
ODIN MODE.
Any help ? Please ? The bloatware is driving me nuts :crying:
VL4DST3R said:
I can't seem to get the coustom recovery installed, and after some digging i found this :
The thing is, when i try to do that, and then get into recovery i get
Could not do normal boot.
ODIN MODE.
Any help ? Please ? The bloatware is driving me nuts :crying:
Click to expand...
Click to collapse
Maybe your phone is not recognized in Download Mode as corresponding drivers may not be properly installed. So Computer is not able to recognize the phone when in Downlaod mode. Install SM Bus Controllers drivers from Intel from Official driver source.
After setting-up you'll be able to flash TWRP and boot into recovery mode.
---------- Post added at 05:36 AM ---------- Previous post was at 05:32 AM ----------
xmun said:
This happened to me also. I am running XXU1BOJ1 . I flashed twrp-2.8.7.0-klte.img and even though it solved getting stuck at recovery, my phone still boots into the standard recovery instead of TWRP when pressing VOLUP+Home+Power. Anyone got ideas?
Click to expand...
Click to collapse
Actually the problem of custom recovery (TWRPhere) not installed at all, stock recovery<3e> persists after reboot because when you flash custom recovery from Odin and allow it to reboot on its own, Samsung's recovery checking script checks if a custom recovery is present and overrides.
To bypass that check you need to take your battery out as soon as the recovery is flashed by Odin ( and before the phone reboots).
As soon as the Odin says PASS you should be ready to take out the battery which will stop it from rebooting,
Put back the battery and enter recovery mode directly by pressing and holding Volume Up, Home and Power keys at the same time.
Release all three buttons when Samsung Galaxy S5 screen flickers and the main screen of Recovery mode appears.
This will avoid script checking and will let you to custom recovery directly,there you can install SuperSU or any other zip.
manubhargav said:
Maybe your phone is not recognized in Download Mode as corresponding drivers may not be properly installed. So Computer is not able to recognize the phone when in Downlaod mode. Install SM Bus Controllers drivers from Intel from Official driver source.
After setting-up you'll be able to flash TWRP and boot into recovery mode.
Actually the problem of custom recovery (TWRPhere) not installed at all, stock recovery<3e> persists after reboot because when you flash custom recovery from Odin and allow it to reboot on its own, Samsung's recovery checking script checks if a custom recovery is present and overrides.
To bypass that check you need to take your battery out as soon as the recovery is flashed by Odin ( and before the phone reboots).
As soon as the Odin says PASS you should be ready to take out the battery which will stop it from rebooting,
Put back the battery and enter recovery mode directly by pressing and holding Volume Up, Home and Power keys at the same time.
Release all three buttons when Samsung Galaxy S5 screen flickers and the main screen of Recovery mode appears.
This will avoid script checking and will let you to custom recovery directly,there you can install SuperSU or any other zip.
Click to expand...
Click to collapse
The drivers are installed, and Odin sees my phone just fine, also the thing with removing the battery before it restats leads me to the error i mentioned above...
VL4DST3R said:
The drivers are installed, and Odin sees my phone just fine, also the thing with removing the battery before it restats leads me to the error i mentioned above...
Click to expand...
Click to collapse
Ah, So the problem you're facing is NOT getting into recovery mode
There are 2 ways to solve the problem, (1st -> flashing recovery.tar again, 2nd-> flashing stock firmware)
First method:
Enter "Download Mode" by holding down "Volume Down"+ "Home" + "Power" button.
Flash recovery.img again and check if it boots into recovery this time.
Sometimes this may not work and you may need to try flashing firmware
Second method:
Download Firmware from here
Open odin in your PC
Enter "Download mode"
Connect the device to PC using USB
Flash the PDA, BL, AP, CSC etc.
Alternatively, You can flash the firmware using SmartSwitch
manubhargav said:
Ah, So the problem you're facing is NOT getting into recovery mode
Click to expand...
Click to collapse
Oh but it is! That's exactly my problem. Look, here are the 3 outcomes I get regarding the whole recovery menu thing:
Go into the default recovery menu - cant install SuperSU but at least it works.
Install twrp and remove the battery after it finishes transfering and wants to restart, at which point when I go into recovery I get the above error (Could not do normal boot. ODIN MODE.)
Install twrp and let it restart by itself and after it is done, go into recovery only to find it is back to the default one.
VL4DST3R said:
Oh but it is! That's exactly my problem. Look, here are the 3 outcomes I get regarding the whole recovery menu thing:
Go into the default recovery menu - cant install SuperSU but at least it works.
Install twrp and remove the battery after it finishes transfering and wants to restart, at which point when I go into recovery I get the above error (Could not do normal boot. ODIN MODE.)
Install twrp and let it restart by itself and after it is done, go into recovery only to find it is back to the default one.
Click to expand...
Click to collapse
Which Kernel version are you in? Which TWRP version did you try? Install other custom recoveries? On locked bootloader?
Ok, I tried CWM and nothing changed, i get the default recovery menu...
Doing the shut down before it restarts gets me "recovery is not seandorid enforcing"
VL4DST3R said:
Ok, I tried CWM and nothing changed, i get the default recovery menu...
Doing the shut down before it restarts gets me "recovery is not seandorid enforcing"
Click to expand...
Click to collapse
Turn OFF Auto-Reboot option in ODIN and flash the recovery.tar and remove battery and directly boot into recovery mode.
Go into a working custom recovery (CWM or TWRP) and flash SuperSU.zip from the recovery and reboot with ("Fix permissions" if there is such an option, otherwise simply reboot).
manubhargav said:
Turn OFF Auto-Reboot option in ODIN and flash the recovery.tar and remove battery and directly boot into recovery mode.
Go into a working custom recovery (CWM or TWRP) and flash SuperSU.zip from the recovery and reboot with ("Fix permissions" if there is such an option, otherwise simply reboot).
Click to expand...
Click to collapse
Tried that already, and as I said, I can't get a custom recovery working, it either resets to the default one or I get the "recovery is not seandorid enforcing" error.
VL4DST3R said:
Tried that already, and as I said, I can't get a custom recovery working, it either resets to the default one or I get the "recovery is not seandorid enforcing" error.
Click to expand...
Click to collapse
1)
Ah use latest twrp 2.8.70
Ah use latest supersu beta 2.52
Quick download cm12.1 nightly and flash it.
Boot Rom and go into settings/aboutphone/ click build number rapidly.
Developer settings should appear, then go into developers options/ click on "root access" and enable it.
---- now test if its working . however....
2)
If its not working, take yourself back into twrp and flash that supersu beta.
----now test again. However ....
3)
If it doesn't work again .
go back to stock 5.0 rom>>> put twrp on >>> and flash DAT supersu .
now test ya rom again. However.........
4)
If it dont work again ..
go back to stock 4.4 rom>>> put twrp on>>> and flash a random supersu.
now test ya rom again. However.....
5)
if that doesn't work again,
Go back to stock rom through (odin) and restart the process from the top .
btw the "recovery is not seandorid enforcing" is normal . not an error.
GeniusisHere said:
1)
Ah use latest twrp 2.8.70
Ah use latest supersu beta 2.52
Quick download cm12.1 nightly and flash it.
---- now test if its working . however....
2)
----now test again. However ....
3)
If it doesn't work again .
now test ya rom again. However.........
4)
If it dont work again ..
now test ya rom again. However.....
5)
if that doesn't work again, .
Click to expand...
Click to collapse
First of all holy **** what an answer... let's SLOW DOWN a bit first, shall we ?
Secondly you lost me from step 1, I don't want CyanogenMod, I want the default Samsung 5.0 with TouchWiz (contrary to popular belief I actually like it).
Also I would really like to know (from someone that actually knows why this happens) why is it reverting to default recovery and how can I stop it from doing so ? manubhargav had an interesting idea, but sadly it doesn't work for everyone (as someone else mentioned on that other post)
So I'm guessing no one knows the answer to my problem considering almost a moth has passed...
I know that in kitkat the answer was to turn off / disable 'Reactivation Lock' (located under settings>>security and unchecking the box)........
I had heard that Samsung had removed that option in lollipop, but it might be worth checking......it has/had to be disabled BEFORE attempting to flash anything......
http://i.imgur.com/rVnFwJM.jpg
keithross39 said:
I know that in kitkat the answer was to turn off / disable 'Reactivation Lock' (located under settings>>security and unchecking the box)........
I had heard that Samsung had removed that option in lollipop, but it might be worth checking......it has/had to be disabled BEFORE attempting to flash anything......
http://i.imgur.com/rVnFwJM.jpg
Click to expand...
Click to collapse
RL is still there with LP too
A client brought in her phone (S4-i337) that was in recovery mode, at first i thought it was something simple but not really. At first i did a wipe data but it couldn't boot up instead after rebooting, it went back to recovery mode. Surprisingly, this phone boots up normally when you try to boot to download mode. As in, when i press Volume down + Home + Power, instead of it going to download mode, it boots up fully then i happen to use it for until when I restart it. I've updated it to Android 5 using some file that i found on some forum, thought it would help but same case. Members, am out of ideas on what i should do. I've flashed it with Z3X box, but i also get an error, same as Odin. Any help is highly appreciated
What are you flashing to the phone? If it was running a stock 4.4.2 ROM or newer, the bootloader would be locked and AT&T never released a complete Odin firmware flash after 4.1.2.
Hi All,
Got a S5 G900I here that's doing my head in! Stuck in the infamous bootloop at the Samsung logo.
I have been a long time reader of these forums and have prior experience from flashing Samsung phones but this one is driving me mad!
I can put the phone into Download mode without an issue, phone is detected in Odin and I can flash any firmware I try to it (Have tried original 4.4.2 , 5.0 and latest 6.0.1 firmwares from SamMobile). Odin goes through the entire process, reports as "Pass" but then the device goes straight back into the reboot loop and will never fully boot up.
I can also use Odin to push TWRP / CWM / PhilzTouch recoveries, however the device will never boot into the recovery partition. I get the blue "Recovery Booting" message briefly, then the device bootloops again.
Does anyone have any further suggestions to try and get this phone operational again?
I have tried multiple versions of Odin, multiple firmware versions, different computers, different USB cables, different USB ports etc.
I look forward to hearing back from you
Try this :
1. Make sure flash latest recovery with latest ODIN version. Check the official website.
2. Do not let your phone restart after flash recovery with ODIN. Un-check auto reboot on option tab in ODIN. After PASS flash recovery disconnect USB cable then ummm ... I do not know what about your phone .. Mine G900D, I just just pull the battery then I plug it again lol ..: D
3. It should be able to get into recovery after that. If not, it means the recovery type does not match your phone.
andra.soul.catcher said:
1. Make sure flash latest recovery with latest ODIN version. Check the official website.
2. Do not let your phone restart after flash recovery with ODIN. Un-check auto reboot on option tab in ODIN. After PASS flash recovery disconnect USB cable then ummm ... I do not know what about your phone .. Mine G900D, I just just pull the battery then I plug it again lol ..: D
3. It should be able to get into recovery after that. If not, it means the recovery type does not match your phone.
Click to expand...
Click to collapse
Have tried latest stock recovery and latest TWRP recovery using latest ODIN v3.13.1 as well as ODIN v3.09 and v3.10 - No difference whether I uncheck or check auto reboot either
Phone still stuck in a constant reboot loop and never gets to recovery
AS93 said:
Have tried latest stock recovery and latest TWRP recovery using latest ODIN v3.13.1 as well as ODIN v3.09 and v3.10 - No difference whether I uncheck or check auto reboot either
Phone still stuck in a constant reboot loop and never gets to recovery
Click to expand...
Click to collapse
It is important to turn off the phone right after flash recovery on the download screen. I mean really off rather than reboot. unplug the battery do not turn off with the power button. Because when rebooted, recovery will automatically return to stock .. so the recovery you just installed will be erased again. if stock recovery inside is broken you will get bootloop. if it is done and still can not enter recovery .. huum .. I am afraid if it's a hardware problem .. because it's easier to find a suitable recovery than its firmware. if recovery can not be in flash .... it's a long way to go ..
By the way, sorry for ask .. you release the power button when it says "recovery booting" with blue text.. right ..? while continuing to hold the volume up..?
andra.soul.catcher said:
It is important to turn off the phone right after flash recovery on the download screen. I mean really off rather than reboot. unplug the battery do not turn off with the power button. Because when rebooted, recovery will automatically return to stock .. so the recovery you just installed will be erased again. if stock recovery inside is broken you will get bootloop. if it is done and still can not enter recovery .. huum .. I am afraid if it's a hardware problem .. because it's easier to find a suitable recovery than its firmware. if recovery can not be in flash .... it's a long way to go ..
By the way, sorry for ask .. you release the power button when it says "recovery booting" with blue text.. right ..? while continuing to hold the volume up..?
Click to expand...
Click to collapse
Thanks for the quick reply.
Yes when I am booting into recovery mode and can see the blue text "Recovery Booting" in the corner of the screen I let go of the power button - device still boot loops.
Have flashed recovery then removed battery - still cannot get it into recovery.
I have seen some Samsungs have hardware issues with their NAND chips but in these cases there are a lot of errors relating to NAND displayed on the screen when I've seen it be a hardware issue. None of these appear on this phone - convinced it has something to do with software.
I found these threads - exactly the same issue as me, and at the end it says they fixed it by flashing a specific bootloader however I have a G900I and the phone in this thread was a G900F
https://forum.xda-developers.com/galaxy-s5/help/bricked-s5-sm-g900f-boot-to-recovery-t3280926/
https://forum.xda-developers.com/galaxy-s5/help/samsung-s5-sm-g900f-stock-flash-caused-t3771105
https://forum.xda-developers.com/galaxy-s5/help/bricked-s5-sm-g900f-boot-to-recovery-t3280926
Have tried countless different versions of ODIN / recovery / stock firmware , including the "service firmware with the separate files G900IDVU1BOE1_CL4826466_QB4839040_REV00_user_low_ship_MULTI_CERT"
Switched from Sprint to Cricket, MMS messages go in and out, I added the APN settings from Cricket, still goes in and out, so I decided to flash the unlocked firmware from an XDA post. Booting up my phone is stuck in a bootloop at the Samsung welcome to android screen. My phone will go into recovery mode, and I can power it off, I can get into download mode. I can't get into safe mode but I'm about to try again, in recovery mode it says E: failed to mount in recovery mode /system invalid argument. When I turn the phone on, it just goes straight to recovery mode. It will not go into safe mode, it won't go past the Samsung Galaxy S7 Edge Powered by Android Screen. Odin said it flashed Sprint's firmware successfully. Please help me, I'm a stay at home Mom and I have an 8 month old. I need my phone to work asap I would really appreciate it. I am a newbie to flashing roms. Thank you in advance.
if u flash with twrp just go back in recovery mode twrp should open go to restore click select your backup to choose from providing u did back up if not work get your original firmware load it up on odin this usually helps me out but you lose all info contacts apps etc read up some cuz there few more solutions to try first before my way ?? were you flashing with odin or twrp were you trying to root or flash rom etc.