Database Users

[Q] Loop booting after installing CWM

I installed the latest version of CWM after finally rooting my Note 3 (N900T). Now, when I try to boot into recovery, it does the infamous loop boot with the message "RECOVERY IS NOT SEANDROID ENFORCING". I essentially have to pull the battery, reboot into Download Mode, then hit Volume down to boot up.
Did I miss something in the process?

osutuba said:
I installed the latest version of CWM after finally rooting my Note 3 (N900T). Now, when I try to boot into recovery, it does the infamous loop boot with the message "RECOVERY IS NOT SEANDROID ENFORCING". I essentially have to pull the battery, reboot into Download Mode, then hit Volume down to boot up.
Did I miss something in the process?
Click to expand...
Click to collapse
Use TWRP.
http://www.techerrata.com/browse/twrp2/hltetmo
Flash depending on your firmware (4.3 or 4.4)

nicholaschum said:
Use TWRP.
http://www.techerrata.com/browse/twrp2/hltetmo
Flash depending on your firmware (4.3 or 4.4)
Click to expand...
Click to collapse
I have TWRP installed already (I see it as an option in CWM), but I got the same result.

osutuba said:
I have TWRP installed already (I see it as an option in CWM), but I got the same result.
Click to expand...
Click to collapse
Use Odin to flash twrp. Get it from:
4.4 http://www.techerrata.com/file/twrp2/hlte/openrecovery-twrp-2.8.0.2-hlte-4.4.img.tar
4.3 http://www.techerrata.com/file/twrp2/hlte/openrecovery-twrp-2.8.0.2-hlte-4.3.img.tar
After it is working add a touch of class: [THEME][SGN3] TWRP Holofied - Black / Dark / Light / Play / XDA [10/09/14]

[Q] Soft bricked Samsung S5 G900F

Hello everyone,
I had a Samsung S5 G900F from stock with Lollipop, and tried to root and change recovery with ODIN, first downloaded CF root, which ODIN said pass but on reboot said system error, and then downloaded twrp recovery which ODIN also said passed.
After, couldn't restart phone, couldn't go to recovery, no light when charging, through that had hard bricked phone. Removed battery went to dinner and after tried again, and was able to to to download mode, phone charges, and I am able to go to twrp recovery, but before it says
RECOVERY BOOTING...
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit: recovery
And when I reboot or start phone it stays in samsung s logo.
Can someone help?
Thanks

RECOVERY BOOTING...
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit: recovery
is normal - mine does that with TWRP too
Boot to TWRP, clear CACHE - Reboot
If that fails, factory reset from TWRP and try booting again
If that fails
Grab a custom ROM / Gapps, copy to MicroSD Card, boot to TWRP Recovery, wipe SYSTEM / DATA / CACHES - Flash ROM, Flash Gapps, Reboot
Or Grab a stock ROM from sammobile and flash from ODIN

*Detection* said:
RECOVERY BOOTING...
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit: recovery
is normal - mine does that with TWRP too
Boot to TWRP, clear CACHE - Reboot
If that fails, factory reset from TWRP and try booting again
If that fails
Grab a custom ROM / Gapps, copy to MicroSD Card, boot to TWRP Recovery, wipe SYSTEM / DATA / CACHES - Flash ROM, Flash Gapps, Reboot
Or Grab a stock ROM from sammobile and flash from ODIN
Click to expand...
Click to collapse
Tks I will try the last option. The others, already had done and still same situation. Already had download a CM12 ROM and gapps just needed to install to try. So will try the last option and give a feedback later. Tks again.

*Detection* said:
RECOVERY BOOTING...
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit: recovery
is normal - mine does that with TWRP too
Boot to TWRP, clear CACHE - Reboot
If that fails, factory reset from TWRP and try booting again
If that fails
Grab a custom ROM / Gapps, copy to MicroSD Card, boot to TWRP Recovery, wipe SYSTEM / DATA / CACHES - Flash ROM, Flash Gapps, Reboot
Or Grab a stock ROM from sammobile and flash from ODIN
Click to expand...
Click to collapse
It worked, flashed CM12 and gapps and its working.
Tks for the help.

Great

zzzferino said:
Hello everyone,
I had a Samsung S5 G900F from stock with Lollipop, and tried to root and change recovery with ODIN, first downloaded CF root, which ODIN said pass but on reboot said system error, and then downloaded twrp recovery which ODIN also said passed.
After, couldn't restart phone, couldn't go to recovery, no light when charging, through that had hard bricked phone. Removed battery went to dinner and after tried again, and was able to to to download mode, phone charges, and I am able to go to twrp recovery, but before it says
RECOVERY BOOTING...
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit: recovery
And when I reboot or start phone it stays in samsung s logo.
Can someone help?
Thanks
Click to expand...
Click to collapse
This is a knox error.
There are 3 ways to remove this:
1. Flash stock recovery (This is easier if you can get your hands on a stock recovery)
2. Delete knox (This is hard as there are duplicates)
3. Using Android terminal emulator
type: su (enter)
pm disable com.sec.knox.seandroid
Note: The third may not work. (I think it depends on the version idk)
Also try a custom ROM with knox removed.

Samsung Galaxy S5 SM-G900F 5.0 stuck during root

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

[Solved]Recovery is not seandroid enforcing [G900F]

Hi. I have a problem with my S5 model: G900F, lollipop 5.0 Official
I was trying to root my device using this thread
But when I flashed the TWRP recovery (the one for G900F) I cant access recovery anymore
When trying to boot to recovery there is a error on the screen : Recovery is not seandroid enforcing
Anyone knows why this happened and how can I fix this? pls help...
UPDATE:
Solution that worked for me:
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
Click to expand...
Click to collapse

Can you boot to android? If you're trying to boot into recovery holding the volume key, and it's not working, you can try it via an app, there are plenty of apps like ROM Manager which can reboot your phone directly into recovery mode.

neverbeenfrustrated said:
Can you boot to android? If you're trying to boot into recovery holding the volume key, and it's not working, you can try it via an app, there are plenty of apps like ROM Manager which can reboot your phone directly into recovery mode.
Click to expand...
Click to collapse
yes I can boot to android. I tried Rom manager app but when I select reboot into recovery it gives error:
"An error occurred while attempting to run privileged commands!"

Did you have your Reactivation Lock turned off before flashing TWRP? The red text saying RECOVERY IS NOT SEANDROID ENFORCING is normal as you are using a custom recovery.

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
Hope this helps.
http://i.imgur.com/rVnFwJM.jpg

Vineen said:
Did you have your Reactivation Lock turned off before flashing TWRP? The red text saying RECOVERY IS NOT SEANDROID ENFORCING is normal as you are using a custom recovery.
Click to expand...
Click to collapse
Yes It was off

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
Click to expand...
Click to collapse
It Worked! :laugh: Thanks for your help.. After I flashed TWRP 2.8.7.0 It booted to recovery successfully... Thank you very much:victory:

kronu said:
It Worked! :laugh: Thanks for your help.. After I flashed TWRP 2.8.7.0 It booted to recovery successfully... Thank you very much:victory:
Click to expand...
Click to collapse
Good job fella.....Enjoy the freedom of root.....
http://i.imgur.com/rVnFwJM.jpg

Why my Samsung Galaxy J500-FN doesn't boot into TWRP recovery?

Hello,
I just now flashed TWRP 3.0.2.0 on my Samsung J500FN. When i press VolDown+Home+Power, it outputs me with "Recovery is not SEANDROID enforcing", then the screen starts to turn greenish. I tried multiple versions of TWRP built for that device, the results are the same.
Any idea why that is happening?

redlv said:
Hello,
I just now flashed TWRP 3.0.2.0 on my Samsung J500FN. When i press VolDown+Home+Power, it outputs me with "Recovery is not SEANDROID enforcing", then the screen starts to turn greenish. I tried multiple versions of TWRP built for that device, the results are the same.
Any idea why that is happening?
Click to expand...
Click to collapse
Did you flash the correct TWRP according to the android version which you're using?
TWRP 5.1.1: http://forum.xda-developers.com/galaxy-j5/development/recovery-samsung-galaxy-j5-t3468844.
TWRP 6.0.1: http://forum.xda-developers.com/galaxy-j5/development/recovery-samsung-galaxy-j500f-t3416960 .

#Henkate said:
Did you flash the correct TWRP according to the android version which you're using?
TWRP 5.1.1: http://forum.xda-developers.com/galaxy-j5/development/recovery-samsung-galaxy-j5-t3468844.
TWRP 6.0.1: http://forum.xda-developers.com/galaxy-j5/development/recovery-samsung-galaxy-j500f-t3416960 .
Click to expand...
Click to collapse
I did that but nothing

androidtutorials said:
i did that but nothing
Click to expand...
Click to collapse
its finished ?

Odin
http://odindownload.com/download/Odin3_v3.12.3.zip
Recovery
https://www.androidfilehost.com/?fid=312968872162493093
Make sure your following this are enable
developer option
OEM unlock
USB debugging
Also make sure your sure "Device Security" is deactivated in Smart Manager
Procress
1-in odin Untick Auto reboot option.
2-After flushing twrp by Odin, remove the battery and insert it again .
3- press volume up+ home+power button to go to twrt.
once flashing process is done unplug your usb then remove your battery wait for sometime
Insert battery then try to boot your phone in recovery mode.
it work for me..