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.
Related
I am having a problem flashing cwm/twrp via odin. It gets thru passed. But when i reboot to recovery it wont show the right recovery. And it shows the dead android logo with an open stomach. I wanted to flashed a custom recovery via odin and flash super su to gain root. Problem is i cant flash a custom recovery via odin. Can someone help me? Tia. Im currently in version mj1 . N7005.
Sent from my SM-N9005 using XDA Premium 4 mobile app
PierreTech said:
I am having a problem flashing cwm/twrp via odin. It gets thru passed. But when i reboot to recovery it wont show the right recovery. And it shows the dead android logo with an open stomach. I wanted to flashed a custom recovery via odin and flash super su to gain root. Problem is i cant flash a custom recovery via odin. Can someone help me? Tia. Im currently in version mj1 . N7005.
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
http://galaxynote3root.com/galaxy-note-3-root/how-to-root-galaxy-note-3/
have a look here
Same problem here.
PierreTech said:
I am having a problem flashing cwm/twrp via odin. It gets thru passed. But when i reboot to recovery it wont show the right recovery. And it shows the dead android logo with an open stomach. I wanted to flashed a custom recovery via odin and flash super su to gain root. Problem is i cant flash a custom recovery via odin. Can someone help me? Tia. Im currently in version mj1 . N7005.
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hey there. I'm having the same problem. Followed Max's guide on galaxynote3root.com. I receive the successful and passed message in Odin each time but it appears to go into stock recovery I've used cwm and twrp before and know what it looks like, however, no joy. I messaged Max to get his thoughts my Note is the Sprint version. So close I know it.
I used to have Verizon Gs3 and played a lot with Custom Roms.
Recently changed to Sprint Gs4.
I am on L720VPUEMK2 baseband.(Most recent Stock 4.3)
I did root my device by flashing CF-Auto-Root and Phil Touch Wiz 5.18.2 ( ODIN mode)
Here comes the challenge:
When I try to flash any custom rom using Recovery mode I am getting stuck at Boot screen with error.
Funny thing is If i use Cyanogen Mod Installer directly from My Laptop to flash 10.2 version.
I am guessing it has some thing to do with Samsung Knox Boot Loader.
Can some one help me with getting around this to flash custom Rom?
its been my experience with philz recovery once you factory reset you have to go into power menu and reboot into recovery again and then flash rom
loumoli said:
its been my experience with philz recovery once you factory reset you have to go into power menu and reboot into recovery again and then flash rom
Click to expand...
Click to collapse
So you are saying that Once I flash the Rom
1. Go back to Recovery and Do a factory Reset
2. Re-Flash the Desired Rom.
I tried this too.
Its not just Philz Recovery. I user CWM Recovery as well and having similar issues.
[email protected] said:
I used to have Verizon Gs3 and played a lot with Custom Roms.
Recently changed to Sprint Gs4.
I am on L720VPUEMK2 baseband.(Most recent Stock 4.3)
I did root my device by flashing CF-Auto-Root and Phil Touch Wiz 5.18.2 ( ODIN mode)
Here comes the challenge:
When I try to flash any custom rom using Recovery mode I am getting stuck at Boot screen with error.
Funny thing is If i use Cyanogen Mod Installer directly from My Laptop to flash 10.2 version.
I am guessing it has some thing to do with Samsung Knox Boot Loader.
Can some one help me with getting around this to flash custom Rom?
Click to expand...
Click to collapse
Use PC Odin to flash Philz latest recovery.
But in Odin don't check the "Auto Reboot". When Odin is finished unplug the phone and hard power it off or batter pull.
Edited for clarity - Meant AutoReboot
leaderbuilder said:
Use PC Odin to flash Philz latest recovery.
But in Odin don't check the f.reset. When Odin is finished unplug the phone and hard power it off or batter pull.
Click to expand...
Click to collapse
i will give this a try today after work.
Will let you know
[email protected] said:
i will give this a try today after work.
Will let you know
Click to expand...
Click to collapse
Meant - "Auto Reboot". Didn't have enough coffee yet.
leaderbuilder said:
Meant - "Auto Reboot". Didn't have enough coffee yet.
Click to expand...
Click to collapse
So when i did install custom Rom I am stuck on Samsung Galaxy s4 Screen
With Error
KERNeL IS NOT SEANDROID ENFORCING ( RED color)
Set Warranty Bit : Kernel (Yellow Color)
Its about 10 Minutes now and I will leave it that way for 1 more hour.
Update: its been 30 mins and am still stuck in that screen.
I'm curious as to what ends up happening with this. I was reading how to flash a custom rom, by using Clockworkmod Recovery.
It looks like the CWM is flashed in via ODIN after the root as a .tar.md5, then you factory reset/wipe data, then wipe cache, then wipe davilk cache, then install from .zip extSDcard. It seemed simple enough, and I have the same model as you, but it appears there are hang ups that you are having which I'll wait until I try it.
I also have stock ROM and MK2 GS4 with Sprint.
[email protected] said:
So when i did install custom Rom I am stuck on Samsung Galaxy s4 Screen
With Error
KERNeL IS NOT SEANDROID ENFORCING ( RED color)
Set Warranty Bit : Kernel (Yellow Color)
Its about 10 Minutes now and I will leave it that way for 1 more hour.
Update: its been 30 mins and am still stuck in that screen.
Click to expand...
Click to collapse
Reflash a ROM
Sent from my SPH-L720 using Tapatalk
daniel4653 said:
Reflash a ROM
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
Did So. And no changes.
Stuck in The same screen.
[email protected] said:
Did So. And no changes.
Stuck in The same screen.
Click to expand...
Click to collapse
Forgot you have to wipe data. And fdont flash any kernel or anything like that.
Sent from my SPH-L720 using Tapatalk
[email protected] said:
I used to have Verizon Gs3 and played a lot with Custom Roms.
Recently changed to Sprint Gs4.
I am on L720VPUEMK2 baseband.(Most recent Stock 4.3)
I did root my device by flashing CF-Auto-Root and Phil Touch Wiz 5.18.2 ( ODIN mode)
Here comes the challenge:
When I try to flash any custom rom using Recovery mode I am getting stuck at Boot screen with error.
Funny thing is If i use Cyanogen Mod Installer directly from My Laptop to flash 10.2 version.
I am guessing it has some thing to do with Samsung Knox Boot Loader.
Can some one help me with getting around this to flash custom Rom?
Click to expand...
Click to collapse
make sure to wipe delvic and cache and what is the error, it sounds like a bad download possibly
deneid310 said:
make sure to wipe delvic and cache and what is the error, it sounds like a bad download possibly
Click to expand...
Click to collapse
No you get that error when you trip Knox. Well at least it did for me.
Sent from my SPH-L720 using Tapatalk
daniel4653 said:
No you get that error when you trip Knox. Well at least it did for me.
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
How did you Pass that?
[email protected] said:
How did you Pass that?
Click to expand...
Click to collapse
By rooting with saferoot in Verizon forum or kingo app
Sent from my SPH-L720 using Tapatalk
daniel4653 said:
By rooting with saferoot in Verizon forum or kingo app
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
If you root with safe root you are correct, you won't trip the knox warranty flag. But you can't install a custom rom without flashing a custom recovery which is what actually trips the knox flag not root. So safe root is only good if you are going to run stock rooted and not install a custom rom.
[email protected] said:
How did you Pass that?
Click to expand...
Click to collapse
My sprint s4 with Philz does the same exact thing, gets stuck at the same screen. Sometimes it takes a few then boots up , other times I have to manually reboot it.
I've tried many things myself and still this problem confines.
I've asked in other threads about this but no one had an idea of way.
The phone was on MK2, rooted with CF Auto, and has latest Philz.
I'll be checking in here to see if we can fix this... If it's even fixable. I think it has to do with Knox /new security.. But I'm no programmer so maybe a pro can chime in.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Hoping for some experts to help us.. May be a video on how to root of MK2 version And flash custom Rom will help us..
Sent from Sprint GS4
Recovery is not Seandroid Enforcing
Hello all Xda members, I think I need some help with rooting Galaxy Note 3 because I am having some problems which makes me very very sick While everybody with this phone root easily I am stuck at the start screen and it does not boot.In this screen It says
RECOVERY BOOTING...
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit: recovery
I've used Odin 1.85 to CF Auto Root this device. It says "PASS" on the program , but after the device stucks on the screen I mentioned above .It does not boot after that ; nothing loads too.
I really need someone to save me from this .
Recovery is not Seandroid Enforcing
:crying::crying::crying:
suffer178 said:
Recovery is not Seandroid Enforcing
Hello all Xda members, I think I need some help with rooting Galaxy Note 3 because I am having some problems which makes me very very sick While everybody with this phone root easily I am stuck at the start screen and it does not boot.In this screen It says
RECOVERY BOOTING...
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit: recovery
I've used Odin 1.85 to CF Auto Root this device. It says "PASS" on the program , but after the device stucks on the screen I mentioned above .It does not boot after that ; nothing loads too.
I really need someone to save me from this .
Recovery is not Seandroid Enforcing
:crying::crying::crying:
Click to expand...
Click to collapse
Recovery is not Seandroid Enforcing is normal.
Take your battery out and try to get into recovery, then reboot. If not just reflash CF auto root again...make sure you have the right version also, the latest one is for Kitkat not jelly bean!!
And learn your lesson too... READ before you mess around with your device...especially if you are gonna post about being upset and sick due to your own error
EDIT: PS Read THIS
suffer178 said:
Recovery is not Seandroid Enforcing
Hello all Xda members, I think I need some help with rooting Galaxy Note 3 because I am having some problems which makes me very very sick While everybody with this phone root easily I am stuck at the start screen and it does not boot.In this screen It says
RECOVERY BOOTING...
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit: recovery
I've used Odin 1.85 to CF Auto Root this device. It says "PASS" on the program , but after the device stucks on the screen I mentioned above .It does not boot after that ; nothing loads too.
I really need someone to save me from this .
Recovery is not Seandroid Enforcing
:crying::crying::crying:
Click to expand...
Click to collapse
When u flash the auto root, try unticking auto reboot. Then manually reboot when they say restart on odin
Sent from my SM-N9005 using XDA Premium 4 mobile app
Also make sure you have the right version of CF Auto Root. I had the same problem but realised I downloaded the version that only works on 4.4 bootloaders.
qbix08 said:
Also make sure you have the right version of CF Auto Root. I had the same problem but realised I downloaded the version that only works on 4.4 bootloaders.
Click to expand...
Click to collapse
Thats why! So im gonna grab it from the official topic: http://forum.xda-developers.com/showthread.php?t=2466423
thanks for all your reply. my apologies for posting this into wrong section
ive done all of your suggestions. but im still stuck on the seandroid recovery again. or am i missing something?
i hope someone will help me. thanks..
suffer178 said:
thanks for all your reply. my apologies for posting this into wrong section
ive done all of your suggestions. but im still stuck on the seandroid recovery again. or am i missing something?
i hope someone will help me. thanks..
Click to expand...
Click to collapse
SEAndroid recovery will stay as long as you have rooted/installed a custom recovery. It is nothing at all to worry about.. Want rid of it? flash stock no root, no custom recovery. Back to 100% Official status again.
I just dropped the HERP A DERP DOH!
--
Double check you have the right CF, untick Auto-reboot in ODIN (Use 1.85) - Run it, then once it goes to PASS in ODIN, reboot your device manually
suffer178 said:
thanks for all your reply. my apologies for posting this into wrong section
ive done all of your suggestions. but im still stuck on the seandroid recovery again. or am i missing something?
i hope someone will help me. thanks..
Click to expand...
Click to collapse
Try flashing stock firmware. Make sure correct one. Then if can bootup. Flash custom recovery first instead of rooting. See if able to enter recovery mode. If can then proceed to install auto root , using the manual reboot method. If it fails reflash autoroot again.
Sent from my SM-N9005 using XDA Premium 4 mobile app
x3PoohBear said:
Try flashing stock firmware. Make sure correct one. Then if can bootup. Flash custom recovery first instead of rooting. See if able to enter recovery mode. If can then proceed to install auto root , using the manual reboot method. If it fails reflash autoroot again.
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I had the same problem and tried many recovery files outthere til finally i restored the phone, i am not an expert to be honest but i did all the steps above and i always end up in " Recovery is not Seandroid Enforcing"
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.
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.