Hi All....
Please can someone help me.
I flashed Official KitKat 4.4.2 Poland. Rooted with CF.
Everything ran smooth as butter.
But then I tried flashing TWRP with GOO-Manager Open Recovery Script. It said recovery has been installed successfully.
When I rebooted it opens the recovery load screen, saying:
Recovery Booting...
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit: recovery
I cannot go into download mode to flash CWM with Odin.
Any suggestions?
Thanks
Jaquesels5 said:
Hi All....
Please can someone help me.
I flashed Official KitKat 4.4.2 Poland. Rooted with CF.
Everything ran smooth as butter.
But then I tried flashing TWRP with GOO-Manager Open Recovery Script. It said recovery has been installed successfully.
When I rebooted it opens the recovery load screen, saying:
Recovery Booting...
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit: recovery
I cannot go into download mode to flash CWM with Odin.
Any suggestions?
Thanks
Click to expand...
Click to collapse
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit: recovery
is normal
twrp does not work yet
pull the battery out then hold down power vol home it should go into download mode
make sure you have the right cwm for 4.4.2
jaythenut said:
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit: recovery
is normal
twrp does not work yet
pull the battery out then hold down power vol home it should go into download mode
make sure you have the right cwm for 4.4.2
Click to expand...
Click to collapse
Champion:good:
Jaquesels5 said:
Champion:good:
Click to expand...
Click to collapse
guess it worked
goodo
jaythenut said:
guess it worked
goodo
Click to expand...
Click to collapse
It's weird, I initially did remove the battery, and held the Volume down, Home, and Power in but didn't work. Then removed the battery again, but held down the same buttons for a few seconds before replacing the battery, then leaving everything inserted the battery again and powered up using the same method and then went into download mode.
Weird, but glad it worked.
There is an unofficial kk compatible twrp version made by wootever. Look at the n3 custom kernel thread. Dont flash it if you are still on the old bootloader !
Gesendet von meinem SM-N9005
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
Heya
I got a Samsung Galaxy S5-G900F and I can't root it
I tried to flash cf auto root with odin but each time it ended with "recovery is not seandroid enforcing" and forcing me to remove the battery and turn on the phone normally.
I tried to flash a custom recovery (like twrp and philz) but it ended with "recovery is not seandroid enforcing" too...
Can someone help me please ?
My phone informations :
Product Name : kltexx
Bootloader Version : G900FXXU1BOJ1
PDA Version : G900FXXU1BOJ1
CSC Version : G900FROM1BOJ1
Baseband Version : G900FXXU1BOJ1
Build Number : LRX21T.G900FXXU1BOJ1
Can you boot into the recovery in the first place? The "Recovery is not seandroid enforcing" message is normal
Frost009 said:
Can you boot into the recovery in the first place? The "Recovery is not seandroid enforcing" message is normal
Click to expand...
Click to collapse
Yup I can but it's the original recovery (Android system recovery <3e> LRX21T.G900FXXU1BOJ1)
I have these options :
_reboot system now
_apply update from ADB
_apply update from external storage
_apply update from cache
_wipe data/factory reset
_wipe cache partition
_reboot to bootloader
_power down
_view logs
and that's all
This is the only method that seems to work......Follow exactly....
1) deactivate 'Reactivation Lock'
2) boot into download mode
3) flash TWRP 2.8.7.0 specifically this version.
4) DO NOT allow phone to boot, instead..
5) boot directly into recovery
6) flash SuperSU zip
7) boot device as normal
TWRP 2.8.7.0
http://forum.xda-developers.com/showthread.php?t=2727406
superSU zip
http://forum.xda-developers.com/showthread.php?t=1538053
Hope this helps.
http://i.imgur.com/rVnFwJM.jpg
keithross39 said:
This is the only method that seems to work......Follow exactly....
1) deactivate 'Reactivation Lock'
2) boot into download mode
3) flash TWRP 2.8.7.0 specifically this version.
4) DO NOT allow phone to boot, instead..
5) boot directly into recovery
6) flash SuperSU zip
7) boot device as normal
TWRP 2.8.7.0
http://forum.xda-developers.com/showthread.php?t=2727406
superSU zip
http://forum.xda-developers.com/showthread.php?t=1538053
Hope this helps.
http://i.imgur.com/rVnFwJM.jpg
Click to expand...
Click to collapse
Okay I'll try that, but how do I don't allow the phone to boot after flashing with Odin?
Because last time I tried (with reboot option on Odin unchecked) I ended with "Recovery is not seandroid enforced".
We agree that to boot in new custom recovery, it's Volume up + home button + power button?
BlueStream said:
Okay I'll try that, but how do I don't allow the phone to boot after flashing with Odin?
Because last time I tried (with reboot option on Odin unchecked) I ended with "Recovery is not seandroid enforced".
We agree that to boot in new custom recovery, it's Volume up + home button + power button?
Click to expand...
Click to collapse
Pull the battery after flashing, then put it back in and Vol Up, Home, Power to boot to recovery
Make sure you have SuperSU.zip on MicroSD in the phone already
Thank you all !!! My s5 is actually rooted !
Now does anyone know how to install Xposed for the S5 on Lollipop (stock rom) ?
Don't think it works too well on stock TW ROMs, heard of boot loops and such but not tried it myself
Yeah....it works well on KitKat firmwares, but not on Lollipop firmwares (that is one of the reasons I've not upgraded to LP)
It *can* be used with LP, but it's WAY more complicated than normal just to get xposed installer to work.....and that's without trying to figure out which modules are waiting to be updated......
http://i.imgur.com/rVnFwJM.jpg
Got the phone recently. Here's what I did with it so far besides all the automatic updates:
1. Unlocked sim
2. Rooted using Kingroot after OEM unlocking
3. Installed TWRP using Odin
OS: 5.1.1
TWRP 2.8.7.0
Somewhere in there something went wrong, and I'm getting the "Recovery is not seandroid enforcing; Set Warranty Bit: kernel" error message on boot screen. Also, every time I reboot the device, it keeps booting to TWRP.
Please help.
srk999 said:
Got the phone recently. Here's what I did with it so far besides all the automatic updates:
1. Unlocked sim
2. Rooted using Kingroot after OEM unlocking
3. Installed TWRP using Odin
OS: 5.1.1
TWRP 2.8.7.0
Somewhere in there something went wrong, and I'm getting the "Recovery is not seandroid enforcing; Set Warranty Bit: kernel" error message on boot screen. Also, every time I reboot the device, it keeps booting to TWRP.
Please help.
Click to expand...
Click to collapse
I think it is Normal when you flash TWRP recovery....every time pyou reboot it will boot you to recovery mode then reboot again......The Seandroid enforcing is normal when u have a other recovery than stock recovery
_followers_ said:
I think it is Normal when you flash TWRP recovery....every time pyou reboot it will boot you to recovery mode then reboot again......The Seandroid enforcing is normal when u have a other recovery than stock recovery
Click to expand...
Click to collapse
does that make the phone stuck in a boot loop or its usable after these 2 reboots?
transgressor01 said:
does that make the phone stuck in a boot loop or its usable after these 2 reboots?
Click to expand...
Click to collapse
It is usable after to reboots, First boot to recovery then boot again :good:
I have the same problem and hve no idea what to do. Help!
_followers_ said:
It is usable after to reboots, First boot to recovery then boot again :good:
Click to expand...
Click to collapse
Mine says recovery is not seandroid enforcing and set warrinty bit recovery. I dont know the first step. Please help me. I need my phone.
You should look for the official rom,
Hello,
I decided to try and root my phone yesterday in order to use flux and the AdAway for my Samsung Galaxy Note 3 SM-N9007. However when i used Odin instead of saying "Pass" it was saying "Reset". As it was my first time doing anything like this, I unplugged my phone which seemed to have been the wrong move. My phone would vibrate once or twice and then reboot to show me the Samsung logo and the words "Recovery is not Seandroid forcing". It would show that screen for approximately 2 seconds where it turns off and repeats the process. Whilst off for that period of time I cannot enter recovery mode. However I can enter the download mode (vol. down + power). I have researched a bit on what to do however I am still a bit unsure.
*It seems the main problem is I can not enter recovery mode at all. As the logo shows it just turns off instantly and then turns back on getting stuck in a loop.
What I gathered online.
- Download the stock firmware for it. (The file I'm downloading is roughly 1.3 gb)
- Load the file the same way I tried to root the phone.
Is this correct? Could I get some assistance please?
Thank you
I have managed to resolve the error by loading in the stock firmware with Odin.
Heize_July said:
I have managed to resolve the error by loading in the stock firmware with Odin.
Click to expand...
Click to collapse
Just so you know, it's normal for the message: "Recovery is not Seandroid forcing" to appear when you root the phone.
Also, if you unplugged the phone after it said "Pass", then theoretically you shouldn't have a problem.
So the steps for a successful root would be:
1. Flash stock
2. Flash custom recovery (TWRP)
3. Flash superSU.zip file from custom recovery
And you should now be rooted
ShaDisNX255 said:
Just so you know, it's normal for the message: "Recovery is not Seandroid forcing" to appear when you root the phone.
Also, if you unplugged the phone after it said "Pass", then theoretically you shouldn't have a problem.
So the steps for a successful root would be:
1. Flash stock
2. Flash custom recovery (TWRP)
3. Flash superSU.zip file from custom recovery
And you should now be rooted
Click to expand...
Click to collapse
Yea I made the mistake of choosing the wrong CFRoot file. The one I installed was for Android version 4.3 whereas my device was 5.0. After retrying I manged to get the root to work. Thanks anyways!