Greetings.
I am sure there is an answer on XDA but an hour of Googling has got me stumped. Please point me to the right answer.
Starting point
Rooted N900T, stock rom, stock recovery.
What I did
Installed ROM Manager
Told ROM Manager to install the latest CWM for my phone. Completed with no errors.
Tried to boot into recovery with the standard "hold power, vol down, and home" but I could never get into recovery. It would look like it would start to boot into recovery then it would reset and boot into the regular ROM.
Then I told ROM Manager to reboot me into recovery.
Then it went badly... I am stuck in a boot loop that continuously shows going into recovery, then samsung logo, then repeat.
I have pulled the battery, tried to go into download mode, tried connecting USB, tried Odin.
What I want is a working phone. I would like to back up the stock rom and go to CM12 nightlies but for now I will just take a working phone.
Please help,
David
think I found the answer at http://forum.xda-developers.com/showthread.php?t=2666432
At least I got out of the loop, not fixed but progress.
That worked, the only other piece of info you might need if someone else has this problem is that there is no PDA button on the latest version Odin, it is called AP
I wanted to completely reformat my phone as my phone was buggy with Cyanogen Mod 12, so I formated everything.
The problem is that my PC was not detecting the drivers when in recovery mode, so I couldn't side-load with ADB, and I have no way of getting a .zip on to it.
I tried re-installing the clockwork mod using ODIN but it would just crash the application. I then tried heimdall and that said it installed it (I was hoping that it would fix adb)
Now I can't boot in to the clockwork mode recovery as it just instantly turns the phone off, however I can just boot normally in to the Galaxy S4 logo screen.
When I'm in the logo screen I do have access to ADB, however my phone is unathorised and I have no way to authorise it.
How can I A) fix clockwork recovery so it works again and B) put a zip on the phone or fix ADB detecting my device in recovery?
If you can get into download mode, flash a full stock ROM via Odin and start again
DSA said:
If you can get into download mode, flash a full stock ROM via Odin and start again
Click to expand...
Click to collapse
That worked great, thanks.
no probs, i find it to be a pretty good fall back in case of issues (just annoying reinstalling games etc..)
Hi, just bought an S5 G900F (international version)... and i wanted to install a custom recovery than root.. than flash rom. Im experienced in this matter... but ... im having all sorts of odd problems. I tried several reocvery (openrecovery, twrp, philztouch)... non stick when i reboot?
I tried several times... odin says everything installed fine.
I wanted to install cf-root... i did it win odin and when phone restarted it says: "recovery booting.... recovery is not seandoird enforcing ... set warranty bit : recovery
Who can help me??
PS Im on lollipop 5.0 if it makes any difference. All attempts were realized with different versions of odin
People have success with TWRP 2.8.7.0 and ODIN 3.10.6
Then SuperSU from TWRP if it sticks
http://forum.xda-developers.com/showthread.php?t=2727406
Tried no luck. I simply get the stock recovery all the time after restart
daniel_cassian said:
Tried no luck. I simply get the stock recovery all the time after restart
Click to expand...
Click to collapse
Try unchecking "Auto reboot" in ODIN, and once the flash has finished, pull the battery, replace and boot into recovery
just tried it... still no go (... do you think i would have more success trying from adb?
Lol this phone has smth against me.
Tried adb: as long as i have it in "desktop" mode adb devices finds it; as soon as i adb reboot bootloader, using the fastbootdevices... adb doesnt see it anymore... so i cant proceed to the flashig
I know you know what you're doing when it comes to this stuff, as you said
But just to make sure, can you post the exact step by steps you're using to try and flash CF Auto-Root and TWRP etc with ODIN?
Yes of course. As i doesn't work for me... i (even) hope im doing something wrong, so we can get to the bottom of this.
So, installed S5 drivers, Enabled usb debuggin in phone (dev menu). Put phone in dl mode (vl dwn+power+home), open odin, select at AP the recovery (tried about 3 recoveries, older versions and newer ones, twrp, phil, open). I have both (by default) checked auto reboot and f-reset time... connect phone with usb cables (tried 2) (connected directly to mb, no extension)... hit start... get the pass message.. phone resets... goes into android. I power off, go to recovery mode (vl up+power+home) and... i get the stock recovery every single time.
Tried something wierd... flashed through Odin CF-root first (with intention to flash after twrp ... as it says phone needs to be rooted first)... it flashes ok (odin says pass, successful 1), reboot (or go to recovery mode)... i get that seandroid error.
Tried to to with with apps from android as well... it doesnt let me.. obviously as most ask phone to be rooted.
What am I missing?
Those are the correct steps, it definitely should have flashed
Doing this from a native PC yes? Ive seen people trying it from Macs and it fails every time
Only thing I can think of right now is try using a different PC
You don't need USB debugging enabled for flashing with ODIN, download mode has no idea what settings you have enabled in Android
Like your method, I just do this:
Samsung Drivers (KIES3 installs them for you anyway)
Vol Down & Home & Power for Download Mode
Connect phone to PC USB
Leave ODIN defaults set (3.09 or 3.10.6)
Select CF-Auto-Root-klte-kltexx-smg900f.tar.md5 in AP/PDA section of ODIN
Wait for it to become ready
Hit start
Phone reboots, and I have root
You could try factory resetting the phone, and trying again, see if that does anything, or at least clear the caches from stock recovery first
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
So, i tried to flash twrp on my galaxy a40 through odin, i did it step by step as it should be done, odin said pass, but it didnt. I rebooted, and it immediately booted into download mode, again and again, whenever i tried to reboot. I tried everything i know i could try, but nothing works. Is there any way to get the twrp on it? Thanks.
Have you enabled USB debugging and OEM unlocked the phone (in the settings)?
What phone do you have? You need to flash original rom via odin. I think that your phone is bricked.
it often happens quiet it can be solved very simply by installing the patched Vendor if you want I can send you the vendor that you will have to flash it with odin and then restart the phone and return to download mode and flash TWRP from the official website
Alexmalek836316 said:
So, i tried to flash twrp on my galaxy a40 through odin, i did it step by step as it should be done, odin said pass, but it didnt. I rebooted, and it immediately booted into download mode, again and again, whenever i tried to reboot. I tried everything i know i could try, but nothing works. Is there any way to get the twrp on it? Thanks.
Click to expand...
Click to collapse
have you installed vbmeta?
the phone behaves similarly without vbmeta installed.
.