Hello ;D
I have a weird thing with my N910C with 6.0.1. I read a lot about similar problems but i think mine is little different.
My phone is not bootloped. It's rooted ,working normally but i can't install any custom recovery ; c
When i first try to root it with Odin using TWRP nothing really happend so i use CF-Auto-Root and at least it's rooted now.
Next I install TWRP again using TWRP Manager from Google play ,phone is still rooted and working ,but when i try to get into recovery it fails and display "Recovery is not Seandroid Enforcing"
Any suggestions how can i install TWRP or another custom recovery?
Thanks ;D
Mlodszymlody221 said:
Hello ;D
I have a weird thing with my N910C with 6.0.1. I read a lot about similar problems but i think mine is little different.
My phone is not bootloped. It's rooted ,working normally but i can't install any custom recovery ; c
When i first try to root it with Odin using TWRP nothing really happend so i use CF-Auto-Root and at least it's rooted now.
Next I install TWRP again using TWRP Manager from Google play ,phone is still rooted and working ,but when i try to get into recovery it fails and display "Recovery is not Seandroid Enforcing"
Any suggestions how can i install TWRP or another custom recovery?
Thanks ;D
Click to expand...
Click to collapse
You don't need to be worried about the message you're getting (recovery is not seandroid enforcing) it's normal
Don't install the the TWRP from the playstore you need to get the latest build from their website follow the steps and flash it through odin.. cheers
Sent from my SM-N910G using Tapatalk
Amar.B said:
You don't need to be worried about the message you're getting (recovery is not seandroid enforcing) it's normal
Don't install the the TWRP from the playstore you need to get the latest build from their website follow the steps and flash it through odin.. cheers
Sent from my SM-N910G using Tapatalk
Click to expand...
Click to collapse
I've had this issue from installing TWRP from TWRP official app, Then I updated the firmware from Kies as a solution to the same after watching a few videos. I lost the SuperSU binaries and the root, rooted and flashed TWRP from Odin, by downloading the latest build from the TWRP website.
I got the same error message and still
Amar.B said:
You don't need to be worried about the message you're getting (recovery is not seandroid enforcing) it's normal
Don't install the the TWRP from the playstore you need to get the latest build from their website follow the steps and flash it through odin.. cheers
Sent from my SM-N910G using Tapatalk
Click to expand...
Click to collapse
I install TWRP through odin and nothing really happens ; /
No root and no custom recovery ; /
Mlodszymlody221 said:
I install TWRP through odin and nothing really happens ; /
No root and no custom recovery ; /
Click to expand...
Click to collapse
Did you follow the steps!
1st unitck the auto reboot.
When you flash the custom recovery successfully for your device model go to recovery mode immediately.
if you reboot your device normally the stock recovery will replace the custom recovery so make sure to restart into recovery mode after installing the custom recovery via odin.
Sent from my SM-N910G using Tapatalk
Amar.B said:
Did you follow the steps!
1st unitck the auto reboot.
When you flash the custom recovery successfully for your device model go to recovery mode immediately.
if you reboot your device normally the stock recovery will replace the custom recovery so make sure to restart into recovery mode after installing the custom recovery via odin.
Sent from my SM-N910G using Tapatalk
Click to expand...
Click to collapse
Still the same :/
That's why im here ,it's really weird.
I can't go to that custom recovery no matter what im doing ,i watched lots of YT films ,read multiple guides and any of that doesn't work ;/
Only thing working is CF-Auto-Root ,but still don't know how to install recovery ; /
Mlodszymlody221 said:
Still the same :/
That's why im here ,it's really weird.
I can't go to that custom recovery no matter what im doing ,i watched lots of YT films ,read multiple guides and any of that doesn't work ;/
Only thing working is CF-Auto-Root ,but still don't know how to install recovery ; /
Click to expand...
Click to collapse
When you flashed TWRP through odin what did you get! The logcat?
It will be written like this
(Successful 1/faild 0) that means it's been installed successfully
(Successful 0/faild 1) that mean odin faild to install the recovery
Sent from my SM-N910G using Tapatalk
After you flashing recovery through odin as soon as phone begins rebooting pull your battery for at least 25 seconds. I am not sure why it works but it has worked every time i have run into this issue. Also check that you are using the latest version of odin.
Amar.B said:
When you flashed TWRP through odin what did you get! The logcat?
It will be written like this
(Successful 1/faild 0) that means it's been installed successfully
(Successful 0/faild 1) that mean odin faild to install the recovery
Sent from my SM-N910G using Tapatalk
Click to expand...
Click to collapse
All threads completed. (succeed 1 / failed 0) ; /
After using TWRP phone doesn't boot ,Seandroid Enforcing
need to use CF again to start a phone
vegeta21232 said:
After you flashing recovery through odin as soon as phone begins rebooting pull your battery for at least 25 seconds. I am not sure why it works but it has worked every time i have run into this issue. Also check that you are using the latest version of odin.
Click to expand...
Click to collapse
unfortunately still nothing ;c
After a successful install the twrp with odin immediately pull the battery out for 10 sec then put the battery back press the volume up+home button+power button
Try this one and please make sure you are installing the correct version for your device model.
Mlodszymlody221 said:
unfortunately still nothing ;c
Click to expand...
Click to collapse
Sent from my SM-N910G using Tapatalk
Amar.B said:
After a successful install the twrp with odin immediately pull the battery out for 10 sec then put the battery back press the volume up+home button+power button
Try this one and please make sure you are installing the correct version for your device model.
Sent from my SM-N910G using Tapatalk
Click to expand...
Click to collapse
Still the same ,i think i need to go back to 5.0.1 . I have some new update last week and i think this is the problem.
Related
Hi guys,
Yesterday I updated to the new N9005XXUENA6 Leaked KitKat 4.4.2. Didn't really think much of it and finally decided to root the phone.
I rooted the phone with CF-Auto-Root thanks to chainfire. Anyway after that I installed CWM recovery as TWRP haven't really updated it since the new update for note 3.
Now i can get to the CWM recovery and after installing any rom
I tried
1. [JAN-13][hlte][1.2.4] AOSB Project (ProBAM ROM) - The End of The Line ! and then
2. [CM11][4.4.2][N9005][ROM][KERNEL][JAN13] temasek's UNOFFICIAL Build - V33
However, in both cases I get an error:
Kernel is not seandroid enforcing
set warranty bit: kernel
and keeps on boot looping.
I can get into download and recovery but cannot install any custom ROM's.
After a bit of looking around and what i gathered from similar questions,I tried installing a couple of kernels but still its a no go!.
Is it as a result of the new N9005XXUENA6 update? or me doing something idiotic?
P.S: Tried wiping data / factory reset, format partition / system, etc. Cannot find fix permissions in the new CWM however and cannot use TWRP as it just doesn't boot up into the recovery.
Thanks in advance.
Kratumay
kratumay said:
Hi guys,
Yesterday I updated to the new N9005XXUENA6 Leaked KitKat 4.4.2. Didn't really think much of it and finally decided to root the phone.
I rooted the phone with CF-Auto-Root thanks to chainfire. Anyway after that I installed CWM recovery as TWRP haven't really updated it since the new update for note 3.
Now i can get to the CWM recovery and after installing any rom
I tried
1. [JAN-13][hlte][1.2.4] AOSB Project (ProBAM ROM) - The End of The Line ! and then
2. [CM11][4.4.2][N9005][ROM][KERNEL][JAN13] temasek's UNOFFICIAL Build - V33
However, in both cases I get an error:
Kernel is not seandroid enforcing
set warranty bit: kernel
and keeps on boot looping.
I can get into download and recovery but cannot install any custom ROM's.
After a bit of looking around and what i gathered from similar questions,I tried installing a couple of kernels but still its a no go!.
Is it as a result of the new N9005XXUENA6 update? or me doing something idiotic?
P.S: Tried wiping data / factory reset, format partition / system, etc. Cannot find fix permissions in the new CWM however and cannot use TWRP as it just doesn't boot up into the recovery.
Thanks in advance.
Kratumay
Click to expand...
Click to collapse
if you are getting
Kernel is not seandroid enforcing
set warranty bit: kernel
on boot screen thats normal
try flash a rom then flash this straight after http://forum.xda-developers.com/showthread.php?t=2507403
should all work fine
jaythenut said:
if you are getting
Kernel is not seandroid enforcing
set warranty bit: kernel
on boot screen thats normal
try flash a rom then flash this straight after http://forum.xda-developers.com/showthread.php?t=2507403
should all work fine
Click to expand...
Click to collapse
Thanks for the reply,
So once again, I did a factory reset then flashed the rom and then flashed the file you recommended.
Still a no go
Same problem.
kratumay said:
Thanks for the reply,
So once again, I did a factory reset then flashed the rom and then flashed the file you recommended.
Still a no go
Same problem.
Click to expand...
Click to collapse
Based on what I read so far regarding the 4.4.2 update, if you flashed it on your device, there seems to be no way to go back to 4.3 ( I'm not sure if that means custom roms based on 4.3 as well ). Best thing to do is just flash the official 4.4.2 and hang in there until custom roms based on 4.4.2 comes out or people find a way to go back to 4.3. The reason the file from firasusman didn't work is probably because there might be difference in how kit kat deals with efs compared to jellybeans which it was written for in the first place.
Sent from my SM-N9005 using xda app-developers app
You probably are right as it doesn't really work. Anyway I'll keep waiting
Sent from my SM-N9005 using XDA Premium 4 mobile app
same here
Yip you won't be able to go to a lower bootloader than you are on with KK, CM based ROMs are currently running (MJ7) _ will have to wait until the new bootloader is implemented into new(er) builds.
Thanks for that info. Will keep an eye out. Cheers
Sent from my SM-N9005 using XDA Premium 4 mobile app
kratumay said:
Thanks for that info. Will keep an eye out. Cheers
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hi all,
I Have the same error " Recovery is not Seandroid Enforcing " but it's when I try to root my SM-N9005 with the procedure of the SM-9005 (My phone can't be rooted)
(true-android.blogspot.fr/2014/01/root-galaxy-note-3-sm-n9005-lte-running.html)
When I try to restart in recovery mode step 11 in the link :
(11 -Once flashing completed, your Galaxy Note 3 SM-N9005 will reboot. After the phone resets (it vibrates) IMMEDIATELY hold volume up and home buttons to boot into recovery mode. You can operate TWRP recovery using touch.)
This message appears : "Recovery is not Seandroid Enforcing ", and the phone restart, if I stop pushing button, i startup without rooted, If i Continue to push volume up and home buttons, it always boot with Recovery is not Seandroid Enforcing
Have you an idea ?
Thanks
tritri71 said:
Hi all,
I Have the same error " Recovery is not Seandroid Enforcing " but it's when I try to root my SM-N9005 with the procedure of the SM-9005 (My phone can't be rooted)
(true-android.blogspot.fr/2014/01/root-galaxy-note-3-sm-n9005-lte-running.html)
When I try to restart in recovery mode step 11 in the link :
(11 -Once flashing completed, your Galaxy Note 3 SM-N9005 will reboot. After the phone resets (it vibrates) IMMEDIATELY hold volume up and home buttons to boot into recovery mode. You can operate TWRP recovery using touch.)
This message appears : "Recovery is not Seandroid Enforcing ", and the phone restart, if I stop pushing button, i startup without rooted, If i Continue to push volume up and home buttons, it always boot with Recovery is not Seandroid Enforcing
Have you an idea ?
Thanks
Click to expand...
Click to collapse
Before you did this was your 4.4.2 on KitKat working well? Or did you come from 4.3? If you came from a correctly installed 4.4.2 then do go to this thread and start from STEP 8
http://forum.xda-developers.com/showthread.php?t=2614787
download the files required from STEP 8 onwards.
This is CWM recovery and not TWRP. I dont have experience with TWRP.
tritri71 said:
Hi all,
I Have the same error " Recovery is not Seandroid Enforcing " but it's when I try to root my SM-N9005 with the procedure of the SM-9005 (My phone can't be rooted)
(true-android.blogspot.fr/2014/01/root-galaxy-note-3-sm-n9005-lte-running.html)
When I try to restart in recovery mode step 11 in the link :
(11 -Once flashing completed, your Galaxy Note 3 SM-N9005 will reboot. After the phone resets (it vibrates) IMMEDIATELY hold volume up and home buttons to boot into recovery mode. You can operate TWRP recovery using touch.)
This message appears : "Recovery is not Seandroid Enforcing ", and the phone restart, if I stop pushing button, i startup without rooted, If i Continue to push volume up and home buttons, it always boot with Recovery is not Seandroid Enforcing
Have you an idea ?
Thanks
Click to expand...
Click to collapse
I'm assuming you're on 4.3, you have to use this in pda/ap on odin. After flashing phone will restart with android and texts in color. After that it will reboot again to system and you will have root. SEandroid Enforcing is normal if you're rooting you're device. Have you checked with root checker if you have root? Also, once you root your device you will have to flash a custom recovery like cwm or twrp to be able to boot to those recovery.
Hakired said:
Before you did this was your 4.4.2 on KitKat working well? Or did you come from 4.3? If you came from a correctly installed 4.4.2 then do go to this thread and start from STEP 8
http://forum.xda-developers.com/showthread.php?t=2614787
download the files required from STEP 8 onwards.
This is CWM recovery and not TWRP. I dont have experience with TWRP.
Click to expand...
Click to collapse
Thanks a lot !
It Works !
tritri71 said:
Thanks a lot !
It Works !
Click to expand...
Click to collapse
Awesome enjoy kitkat
n9005 cm11 20140226 problems
yesterday i installed cm11 nightly 20140226 on my n9005 via twrp 2.6.3.7 (before i have had 4.3)
it all works fine except 2 little problems:
1. whenever i plug the charger or usb cable to computer, the phone is turned on automatically without pushing the power button.
2. my time & date settings can't be saved, and each time on turning on it goes back to 2013 and 12:00
Thanks in advance to all answers
Same problem
I got the same problem. I have Bobcat 4.3 installed and i'm trying to install Omegarom 4.4.2 but I get stuck in bootloop with '' Kernel is not Seandroid Enforcing ''
Kjetilz said:
I got the same problem. I have Bobcat 4.3 installed and i'm trying to install Omegarom 4.4.2 but I get stuck in bootloop with '' Kernel is not Seandroid Enforcing ''
Click to expand...
Click to collapse
First you will have to update to stock 4.4.2 then you can flash any 4.4.2 roms.
Need some help.Newbie here. I just recently bought a samsung n3 tmobile n900t. I wanted to flash an international ROM to remove those tmobile apps (since im using a different carrier) So I found this ROM here http://forum.xda-developers.com/showthread.php?t=2518249
Installed CWM and flashed the rom. Now i'm in the Kernel is not seandroid enforcing set warranty: kernel loop. What should I do to fix this?
Mediaspot said:
Need some help.Newbie here. I just recently bought a samsung n3 tmobile n900t. I wanted to flash an international ROM to remove those tmobile apps (since im using a different carrier) So I found this ROM here http://forum.xda-developers.com/showthread.php?t=2518249
Installed CWM and flashed the rom. Now i'm in the Kernel is not seandroid enforcing set warranty: kernel loop. What should I do to fix this?
Click to expand...
Click to collapse
The rom you flashed is based on android 4.3, if the phone you bought already have 4.4 then that is probably the cause of the loop. Flash another rom based on 4.4 or download stock firmware from sammobile and flash using odin.
hey_joe said:
The rom you flashed is based on android 4.3, if the phone you bought already have 4.4 then that is probably the cause of the loop. Flash another rom based on 4.4 or download stock firmware from sammobile and flash using odin.
Click to expand...
Click to collapse
I just tried flashing this rom but the same thing. http://forum.xda-developers.com/showthread.php?t=2671039 will try to look for stock firmware and be back with results
I am getting same error but after that phone boots up fine
after I had succesfully rooted my phone, I wanted to install a custom rom.
I am sure I did something wrong ofcource otherwise I wouldn't be here.
#1 Battery in
#2 power on
#3 vibrate
#4 screen on RECOVERY BOOTING
Recovery is NOT SEANDROID ENFORCING
Set Warrenty Bit : recovery
Samsung
GALAXY Note3
SM-N9005
#5 screen off--> reboot -->goto #3
how to brake in the loop so I can use odin ( or whatever ) to install (at least) a normal boot again?
Which custom recovery did you flashed Twrp or Cwm?
Sent from my SM-N900W8 using xda app-developers ap
fwberg said:
after I had succesfully rooted my phone, I wanted to install a custom rom.
I am sure I did something wrong ofcource otherwise I wouldn't be here.
#1 Battery in
#2 power on
#3 vibrate
#4 screen on RECOVERY BOOTING
Recovery is NOT SEANDROID ENFORCING
Set Warrenty Bit : recovery
Samsung
GALAXY Note3
SM-N9005
#5 screen off--> reboot -->goto #3
how to brake in the loop so I can use odin ( or whatever ) to install (at least) a normal boot again?
Click to expand...
Click to collapse
You installed a 4.3 recovery on a 4.4 phone.
Most likely you downloaded the TWRP on the main page and did not download the latest 4.4 compatible one.
Please flash this in Download Mode: http://techerrata.com/bigbiff/hlte-recovery.img.tar
To get into Download Mode, remove the battery, wait a few minutes then put it back, Hold the Download Mode Combination then it would boot directly into Download Mode.
hey nicho, thank you very much
so that was the trick. REMOVE THE BATTERY --> PRESS THE DOWNLOAD KEYS AND HOLD THEM --> THEN ENTER THE BATTERY BACK.
it costed me the whole day yesterday searching for a solution.
at least now I can continue to install a new rom
Thanks man
TWRP
during twrp it told me, there was a newer one. 2.x.x.9
so stupid me, if I had sticked to the plan, nothing would happend.
I used twrp b4 some days ago, for my samsung note 10.1 (2014) without trubbles,
I guess, I overread something
but I'm happy it is all fixed now.
thx for show ur interest
greetz, fred
thank you
nicholaschum said:
You installed a 4.3 recovery on a 4.4 phone.
Most likely you downloaded the TWRP on the main page and did not download the latest 4.4 compatible one.
Please flash this in Download Mode: techerrata.com/bigbiff/hlte-recovery.img.tar
To get into Download Mode, remove the battery, wait a few minutes then put it back, Hold the Download Mode Combination then it would boot directly into Download Mode.
Click to expand...
Click to collapse
this solved my recovery problem, i clicked thank you!!!
nicholaschum said:
You installed a 4.3 recovery on a 4.4 phone.
Most likely you downloaded the TWRP on the main page and did not download the latest 4.4 compatible one.
Please flash this in Download Mode: http://techerrata.com/bigbiff/hlte-recovery.img.tar
To get into Download Mode, remove the battery, wait a few minutes then put it back, Hold the Download Mode Combination then it would boot directly into Download Mode.
Click to expand...
Click to collapse
You just saved my phone i readed so much almost one week 12hours without stop before i try custom recovery,rom and so on.
But well since i decided that im ready to, and first thing i tried to do was custom recovery wich leaded to this problam Now im afraid to enter revovery mode xD
Idiots
You're really the dumbest person I've ever seen in my life. See if this is solution to some kind of problem your beast
Worked for me
Thank you.
remove the battery then press download buttons keep them pressed and put the battery back. choose volume down to continue....
Solution To Loop SM-N900P
I am new to XDA and have only been with android for 6 months but i figure this will help new comers to this issue. Power+Volume Down+Home at the same time to enter download mode. Flash CWM via ODIN. This should work to fix the loop. I found out the hard way but it only took me an hour. I am not sure if this will work if you have not already rooted your phone but it should (since this is the major step in rooting). I believe i deleted my CWM file (accidentally) when i was trying to clear space for my recovery with ROM Manager. Be sure to download the Samsung drivers if you had not already done so during the rooting process.
Hope this helps.
Gives me same error message
But after that it boots into recovery.
Should I proceed installing custom rom or is there anything else to be taken care of
Thanks!
Thank you very much,you save me a lot of trouble.
hey_joe said:
Which custom recovery did you flashed Twrp or Cwm?
Sent from my SM-N900W8 using xda app-developers ap
Click to expand...
Click to collapse
hey joe im getting the same problem but im using the note 3 SM-N900W8 and I flash the CWM straight from the app and not using odin. My phone is already rooted using towelroot
billygun118 said:
hey joe im getting the same problem but im using the note 3 SM-N900W8 and I flash the CWM straight from the app and not using odin. My phone is already rooted using towelroot
Click to expand...
Click to collapse
Which android os do you have on your phone and which cwm version did you flashed?
hey_joe said:
Which android os do you have on your phone and which cwm version did you flashed?
Click to expand...
Click to collapse
im using version 4.4.2 jellybean. The rom manager is v5. 5.3.7/ current recovery 6.0.4.6
billygun118 said:
im using version 4.4.2 jellybean. The rom manager is v5. 5.3.7/ current recovery 6.0.4.6
Click to expand...
Click to collapse
Based on my experience, using rom manager to flash recovery always results in a problem. I suggest you use odin to flash this in download mode.
Btw, 4.4.2 is Kitkat
hey_joe said:
Based on my experience, using rom manager to flash recovery always results in a problem. I suggest you use odin to flash this in download mode.
Btw, 4.4.2 is Kitkat
Click to expand...
Click to collapse
should I root my phone first using cf-root. Then flash the cwm recovery. What happens if I get stuck in a bootloop after flashing the recovery
billygun118 said:
should I root my phone first using cf-root. Then flash the cwm recovery. What happens if I get stuck in a bootloop after flashing the recovery
Click to expand...
Click to collapse
The way I did this is, first install the cwm recovery then flash cf-root after. You can always use odin to flash back the original firmware.
hey_joe said:
The way I did this is, first install the cwm recovery then flash cf-root after. You can always use odin to flash back the original firmware.
Click to expand...
Click to collapse
so there is nothing else I have to do before flashing the recovery?
what boxes should be checkmarked in odin
billygun118 said:
so there is nothing else I have to do before flashing the recovery?
what boxes should be checkmarked in odin
Click to expand...
Click to collapse
Just make sure reactivation lock is off.
When you first start odin, F.Reset Time and Auto Reboot are ticked off so let them be and make sure only those are checked and nothing else.
You probably know this but just to make sure, load the recovery on the AP slot before hitting start.
I'm a noob to all this so I really need your help
When i try to boot up recovery I get:
Recovery is not seandroid enforcing. It starts to reboot and the same thing.
If I boot into download mode and cancel, it boots up properly.
Then when I go into ROM manager and select a different recovery like twrp (was using CWM before) and it boots I get the same message!
I'd like to be able to download roms and all that fun stuff but I'm not sure what to do. I still have SU permission
Is there anyway to flash a new recovery through Odin or factory reset the whole device and recovery?
Sent from my SM-N900W8 using XDA Premium 4 mobile app
itsraining said:
I'm a noob to all this so I really need your help
When i try to boot up recovery I get:
Recovery is not seandroid enforcing. It starts to reboot and the same thing.
If I boot into download mode and cancel, it boots up properly.
Then when I go into ROM manager and select a different recovery like twrp (was using CWM before) and it boots I get the same message!
I'd like to be able to download roms and all that fun stuff but I'm not sure what to do. I still have SU permission
Is there anyway to flash a new recovery through Odin or factory reset the whole device and recovery?
Sent from my SM-N900W8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If you are using custom kernel, it will show that. Aaanndd its normal.
Sent from my SM-N9005 using XDA Premium 4 mobile app
itsraining said:
I'm a noob to all this so I really need your help
When i try to boot up recovery I get:
Recovery is not seandroid enforcing. It starts to reboot and the same thing.
If I boot into download mode and cancel, it boots up properly.
Then when I go into ROM manager and select a different recovery like twrp (was using CWM before) and it boots I get the same message!
I'd like to be able to download roms and all that fun stuff but I'm not sure what to do. I still have SU permission
Is there anyway to flash a new recovery through Odin or factory reset the whole device and recovery?
Sent from my SM-N900W8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It is normal to get seandroid enforcing for recovery as you changing the samsung recovery, if you want to get back to normal you can flash samsung firmware via odin, if you want to flash custom rom, flash it on ur cwm recovery. Btw did you install correct version of CWM? If its not, download correct cwm and reflash. It will be fine.
Okay so its normal to get the seandroid enforcing but I still can't access CWM recovery.
I have some more information that might help.
I have the note 3 SM N900W8 but I got my root from the 9005 version which works great. The 900W8 root method had some bugs.
I tried reflashing root and it brought me back to the stock recovery of the 9005
Was wondering maybe I should install the 9005 CWM recovery?
Sent from my SM-N900W8 using XDA Premium 4 mobile app
itsraining said:
Okay so its normal to get the seandroid enforcing but I still can't access CWM recovery.
I have some more information that might help.
I have the note 3 SM N900W8 but I got my root from the 9005 version which works great. The 900W8 root method had some bugs.
I tried reflashing root and it brought me back to the stock recovery of the 9005
Was wondering maybe I should install the 9005 CWM recovery?
Sent from my SM-N900W8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
TWRP 2.7.0.0.
http://goo.im/devs/OpenRecovery/hltecan
Latest one on the bottom.
Choose the .tar file and flash it in Odin.
Still annoyed with red text......
I used towelroot on my SM-N900W8 Note 3 cuz I cont have a PC to use for Odin, and I don't have friends to borrow a laptop from... ;PP.
Anyway, after much wrestling with CWM, I tried TWRP and had success finally getting the thing to boot to recovery, and installing CM 11. HOWEVER THROUGH IT ALL, ROOT CHECKER INSISTED I DID NOT HAVE ROOT ACCESS. ??
I downloaded TWRP, and the firmware, the ROM and GAPPS and flashed the whole thing through TWRP.... all the while having no root access..... whatever.
The device works fine, but on every re-boot I still get the line "seandroid not enforcing". Also, I was playing with Ultimate Screenshot, and got the error a bunch of times that I did not have root access, despite SU, Busybox, and Titanium Backup working fine...... I dunno what is up with this ....
Should I flash another kernel???... I'm an amatuer at all this so I'm a little lost.
Thanks to all the geeks here for the great info!!!!
r46624 said:
I used towelroot on my SM-N900W8 Note 3 cuz I cont have a PC to use for Odin...
Click to expand...
Click to collapse
You won't get rid of the seandroid not enforcing, it's because of the custom recovery and it's normal.
You have to enable root access in the developers options in settings. Next time do some more reading, it won't hurt you.
Sent from my N9005
Dejan Sathanas said:
You won't get rid of the seandroid not enforcing, it's because of the custom recovery and it's normal.
You have to enable root access in the developers options in settings. Next time do some more reading, it won't hurt you.
Sent from my N9005
Click to expand...
Click to collapse
No that is true, more reading never hurt anyone. Of course then again neither has having manners.
Incidentally I've resolved the problem, regarding having "half root". It would appear I'll just get used to the annoying red text.
hello guys,
i bought a used galaxy s5 from someone running Poland Android lollipop 5.0 and it shows the model as SM-G900F When i try to root it with CF-Auto-Root-klte-kltedx-smg900f It gets stuck on the boot screen saying
"1. RECOVERY BOOTING (in blue),
2. RECOVERY IS NOT SEANDROID ENFORCING (red)
3. Set Warranty Bit: recovery (yellow)"
i googled alot and flashed Phillz recovery which removed the error above but when i go to recovery its the stock recovery? .... I cant install twrp-2.8.7.0-klte.img.tar Either because after flashing it when i go to recovery its stock recovery again. Activation lock is off, SE for Android status is "enforing" does this mean this phone has a locked bootloader? Maybe this phone was on At&T, Sprint or Verizon and the last owner flashed 900f firmware on it to make it look carrier free but it maybe a carrier phoone? Please help me i am very very frustrated right now. i dont even know what recovery is seandroid enforcing means.....:crying::crying::crying:
dork997 said:
hello guys,
i bought a used galaxy s5 from someone running Poland Android lollipop 5.0 and it shows the model as SM-G900F When i try to root it with CF-Auto-Root-klte-kltedx-smg900f It gets stuck on the boot screen saying
"1. RECOVERY BOOTING (in blue),
2. RECOVERY IS NOT SEANDROID ENFORCING (red)
3. Set Warranty Bit: recovery (yellow)"
i googled alot and flashed Phillz recovery which removed the error above but when i go to recovery its the stock recovery? .... I cant install twrp-2.8.7.0-klte.img.tar Either because after flashing it when i go to recovery its stock recovery again. Activation lock is off, SE for Android status is "enforing" does this mean this phone has a locked bootloader? Maybe this phone was on At&T, Sprint or Verizon and the last owner flashed 900f firmware on it to make it look carrier free but it maybe a carrier phoone? Please help me i am very very frustrated right now. i dont even know what recovery is seandroid enforcing means.....:crying::crying::crying:
Click to expand...
Click to collapse
Akalsemann said:
Ok guys, try this.
1. Download philz kernel that matches your modem number. I think philz_touch_6.26.6-klte.tar.md5 works good.
2. Put it in ODIN on PDA/AP
3. Uncheck "Auto Reboot" and make sure Re-Partition is NOT CHECKED (keep F. Reset time)
4. Flash
5. It will say RESET on Odin and nothing further when it is done so just wait 2-3 minutes when RESET appears to be entirely sure that the procedure is done.
6. Pull out phones battery.
7. Put it back in and now go into Recovery directly (Vol up+home+power)
8. ???
9. Profit
Hopefully this might work, i think i did the same
Click to expand...
Click to collapse
Try that
Akalsemann said:
Try that
Click to expand...
Click to collapse
Kindly note that i am able to boot fine now, but the recovery wont stick and whenever i try to root this seandroid error happens
Did u do the following steps correctly
it should work bro
Been there
done the same process
thanx again Akalsemann
vinura kithmal said:
Did u do the following steps correctly
it should work bro
Been there
done the same process
thanx again Akalsemann
Click to expand...
Click to collapse
yes i entered philz recovery > selected format to install new rom > now stuck on samsung logo maybe it removed rom files. Now downloading flash roms from sammobile. Dont know if it will let me root it or not. can u please explain what this error is and why is it caused?
dork997 said:
Kindly note that i am able to boot fine now, but the recovery wont stick and whenever i try to root this seandroid error happens
Click to expand...
Click to collapse
You need to just boot into download mode (voldown+home+power) then push volup to enter download mode
Use Odin to flash trwp 2.8.6.0 tar file in AP spot
Download a pre rooted rom of your choice for g900f
Place on sd card
Reboot to twrp by holding volup+home+power immediately during start of boot
Flash the rom you just downloaded
Now you'll be rooted
(That's what I did in order to get my phone rooted after installing the newest stock lollipop ota)
Sent from my SM-G900F using Tapatalk
dork997 said:
yes i entered philz recovery > selected format to install new rom > now stuck on samsung logo maybe it removed rom files. Now downloading flash roms from sammobile. Dont know if it will let me root it or not. can u please explain what this error is and why is it caused?
Click to expand...
Click to collapse
Common bro
u haven't rooted your device,
u have to flash the supersu zip to get the root access
http://download.chainfire.eu/supersu
first download this file and place it in your device storage,once u pull the battry off and put it back in go straightly to the recovery
select install zip and flash the supersu.zip
then reboot it,after the first boot then go to the recovery and
install your custom rom
Swimguy14 said:
You need to just boot into download mode (voldown+home+power) then push volup to enter download mode
Use Odin to flash trwp 2.8.6.0 tar file in AP spot
Download a pre rooted rom of your choice for g900f
Place on sd card
Reboot to twrp by holding volup+home+power immediately during start of boot
Flash the rom you just downloaded
Now you'll be rooted
(That's what I did in order to get my phone rooted after installing the newest stock lollipop ota)
Sent from my SM-G900F using Tapatalk
Click to expand...
Click to collapse
vinura kithmal said:
Common bro
u haven't rooted your device,
u have to flash the supersu zip to get the root access
http://download.chainfire.eu/supersu
first download this file and place it in your device storage,once u pull the battry off and put it back in go straightly to the recovery
select install zip and flash the supersu.zip
then reboot it,after the first boot then go to the recovery and
install your custom rom
Click to expand...
Click to collapse
I followed instructions given earlier to install philz recovery, i opened it by booting into it immediately i selected format for new rom install. after that i am stuck on samsung logo i think the old rom is now deleted. Now i am downloading fresh 5.0.2 UK from sammobile i will download it and try to root it normally with flashing CF ROOT via odin. if it does not work then i will do what u guys said. I dont know if TWRP will work by the same method (booting immediately into recovery) but philz recovery did. And i will also try flashing a prerooted Rom. What i dont understand is that why is this happening in the first place? i had an alpha before i could enter into TWRP normally i rooted it with CF AUTO root normally...no errors or anything why is this happening on my S5? the last owner must have done something weird with it ...i am trying to figure out why is this happening in the first place. Appreciate ur feedback.
I also dont know why this is happening
and yeah
i had all the galaxy S series upto S5 and this the only device that is not rooting with CF-auto root
the latest updates from samsung may have done something i dnt knw
and eralier mentioned method worked 100% for me and i did root my device like that
And last owner may b or may not done anything with it because my device is a brand new and still i had that issue
Hi guys.
I bought a g900f and now im trying to root it. i downloaded cf autoroot like a always do on all my samsungs but when i flash it via odin it freezes when it boots up. It doesent even run the root script.
it just says: recovery booting.. recovery is not seandroid enforcing. set warranty bit : recovery.
plaease help me
do you flashed twrp?
Sent from my Galaxy S5 using Tapatalk
I have troed this to. But no luck. I Wang to try to download and flash original firmware and try it again with clean sheets can some please lead me in the direction for downloading it. Please not sammobil
chrb1985 said:
I have troed this to. But no luck. I Wang to try to download and flash original firmware and try it again with clean sheets can some please lead me in the direction for downloading it. Please not sammobil
Click to expand...
Click to collapse
Did you flashed twrp on Ur device?
for install cfautoroot you must install twrp.tar on your PC (download from here https://dl.twrp.me/klte/twrp-3.0.2-2-klte.img.tar). then you must flash it via odin.
to flash it make sure you installed your device drivers on PC and enabled USB debugging in developer options.
then boot your phone in downloading mode by pressing power+home+volume down button. then connect your phone to the PC. open odin app and choose the recovery.tar you install from the link i gave you. flash it and wait until finish(maybe 2 or 3 min) and then reboot your device to recovery by pressing power+home+volume up button. flash your cfautoroot and enjoy [emoji5] .
Sent from my Galaxy S5 using Tapatalk
Okay. Where do I get this file cfautoroot ? I manages to install twrp now I just need this file your talking about
chrb1985 said:
Okay. Where do I get this file cfautoroot ? I manages to install twrp now I just need this file your talking about
Click to expand...
Click to collapse
from here bro
https://download.chainfire.eu/397/CF-Root/CF-Auto-Root/CF-Auto-Root-klte-kltexx-smg900f.zip
Sent from my Galaxy S5 using Tapatalk
All right thnx bit isn't that file for Odin?
I extracted boot.IMG from the .tar.md5 and flashed it with twrp. It works now thanx a lot for the help
chrb1985 said:
I extracted boot.IMG from the .tar.md5 and flashed it with twrp. It works now thanx a lot for the help
Click to expand...
Click to collapse
welcome bro :*
Sent from my Galaxy S5 using Tapatalk
chrb1985 said:
Hi guys.
I bought a g900f and now im trying to root it. i downloaded cf autoroot like a always do on all my samsungs but when i flash it via odin it freezes when it boots up. It doesent even run the root script.
it just says: recovery booting.. recovery is not seandroid enforcing. set warranty bit : recovery.
plaease help me
Click to expand...
Click to collapse
I get the same exact thing on a sm-g900t3 (Galaxy S5 - tmobile, north America) Oddly enough I can get https://twrp.me/devices/samsunggalaxys5qualcomm.html installed no problem, but whenever I try to install root, either the supersu.zip via twrp or chainfire's autoroot directly from his site, it just bootloops into recovery.
WestCoastSunset said:
I get the same exact thing on a sm-g900t3 (Galaxy S5 - tmobile, north America) Oddly enough I can get https://twrp.me/devices/samsunggalaxys5qualcomm.html installed no problem, but whenever I try to install root, either the supersu.zip via twrp or chainfire's autoroot directly from his site, it just bootloops into recovery.
Click to expand...
Click to collapse
bro try to use kingroot tool for pc
Sent from my Galaxy S5 using Tapatalk
I actually got it working, by installing a different version of supersu. The one I had was an update-supersu. I then found the full version and it worked. It did reboot itself a couple of times. The cf autoroot did not work for me at all. I opened it up in 7-zip and only saw cache and recovery, nothing related to supersu. I would like to tell anyone that the roms from sammobile did work, but I had to try a couple of them before i found the one which would flash properly.
If you extract the boot.IMG (or recovery.IMG I don't remember but not cach.ext4) and flash it via TWRP it does the trick. That's what worked for me.