Hi guys,
looking for some help I trying to root and install a custom ROM on my phone (J500FNXXU1BPH1)(6.0.1)
I have installed twrp but on boot i get set warranty bit: recovery and kernel is not seandroid enforcing then the phone crashes with fading pixels.
If i boot in with the recovery sequence it will load twrp and let me move around inside but anything i do do not have effect on the boot.
WelshY1987 said:
Hi guys,
looking for some help I trying to root and install a custom ROM on my phone (J500FNXXU1BPH1)(6.0.1)
I have installed twrp but on boot i get set warranty bit: recovery and kernel is not seandroid enforcing then the phone crashes with fading pixels.
If i boot in with the recovery sequence it will load twrp and let me move around inside but anything i do do not have effect on the boot.
Click to expand...
Click to collapse
Go to this thread-https://forum.xda-developers.com/galaxy-j5/development/recovery-samsung-galaxy-j5-t3468844 and download recovery of your model
aarush.chaurasiya said:
Go to this thread-https://forum.xda-developers.com/galaxy-j5/development/recovery-samsung-galaxy-j5-t3468844 and download recovery of your model
Click to expand...
Click to collapse
that is the one i'm using j500FN
WelshY1987 said:
that is the one i'm using j500FN
Click to expand...
Click to collapse
That's for Android 5.1..1 you need this one [RECOVERY] [TWRP-3.0.2-0] Samsung Galaxy J5 [MM][Android 6.0.1]
About the "seandroid enforcing" just ignore it, it's because your rom was modified.
American_Jesus said:
That's for Android 5.1..1 you need this one [RECOVERY] [TWRP-3.0.2-0] Samsung Galaxy J5 [MM][Android 6.0.1]
About the "seandroid enforcing" just ignore it, it's because your rom was modified.
Click to expand...
Click to collapse
even with that one it's still booting and glitch crashing unless i boot into download or recovery. It even do the pixel fade with the 2 errors on top just by plugging in charger and not even turning it on
WelshY1987 said:
even with that one it's still booting and glitch crashing unless i boot into download or recovery. It even do the pixel fade with the 2 errors on top just by plugging in charger and not even turning it on
Click to expand...
Click to collapse
Working after flashing official rom and TWRP, BUT can't flash other roms (update process ended with ERROR: 7
WelshY1987 said:
Working after flashing official rom and TWRP, BUT can't flash other roms (update process ended with ERROR: 7
Click to expand...
Click to collapse
Check if your flashing the right ROM for your phone model.
Status 7 error is caused while the ROM’s updater script file checks to see if the phone model of your phone is compatible with the ROM you are installing
Click to expand...
Click to collapse
American_Jesus said:
Check if your flashing the right ROM for your phone model.
Click to expand...
Click to collapse
i have tried with 2 rom downgrading to 5.1
https://forum.xda-developers.com/ga...m-cyanogenmod-13-0-samsung-galaxy-j5-t3519580
and 6.0.1
https://forum.xda-developers.com/galaxy-j5/development/p-resurrectionremix-v5-7-4-t3497445
WelshY1987 said:
i have tried with 2 rom downgrading to 5.1
https://forum.xda-developers.com/ga...m-cyanogenmod-13-0-samsung-galaxy-j5-t3519580
and 6.0.1
https://forum.xda-developers.com/galaxy-j5/development/p-resurrectionremix-v5-7-4-t3497445
Click to expand...
Click to collapse
Post your problem on ROMs thread, CM13 installation works fine, but you need firmware from 5.1.1 and TWRP for the 5.1.1 .
You need the right TWRP for your current firmware, like if CM13 uses firmware from 5.1.1 you need to 1st downgrade to Android 5.1.1 and then install TWRP for 5.1.1.
Same for rom that uses other firmware version
Try flashing stock using TWRP recovery. If you have a PC, you can enable MTP in the Mount menu in TWRP and connect it to PC and then move the firmware file and install it using TWRP again.
Alternatively, you can boot into download mode (Vol. Down+Home+Lock Screen simultaneously) and install the stock firmware using ODIN.
You can also create a backup of your apps in TWRP so that you can restore them after you have installed stock firmware.
Ready to help if you need more elaborate steps or any other information.
Had completely same problem with My bootloader. I just downgraded to 5.1 stock with Odin and flashed twrp by Nick Verse. After that I had no problems flashing any roms.
WelshY1987 said:
Hi guys,
looking for some help I trying to root and install a custom ROM on my phone (J500FNXXU1BPH1)(6.0.1)
I have installed twrp but on boot i get set warranty bit: recovery and kernel is not seandroid enforcing then the phone crashes with fading pixels.
If i boot in with the recovery sequence it will load twrp and let me move around inside but anything i do do not have effect on the boot.
Click to expand...
Click to collapse
Have you reflaahed the stock firmware set up all the phone and then reflash the recovery ? This could fix
Related
When i boot in to Recovery i get this message. Recovery is not seandroid enforcing. I dont belive its something i shuld be worried about but just to be on the safe site. i will like some kind on confamation on this.
Can i just go ahead and flass custom rom / kernel and it will go away or do i have to flash another Recovery ?
Thanks in advanced
nyvang101 said:
When i boot in to Recovery i get this message. Recovery is not seandroid enforcing. I dont belive its something i shuld be worried about but just to be on the safe site. i will like some kind on confamation on this.
Can i just go ahead and flass custom rom / kernel and it will go away or do i have to flash another Recovery ?
Thanks in advanced
Click to expand...
Click to collapse
1. On what ROM are you?
2. What's stopping you from flashing via odin/heimdall?
spamtrash said:
1. On what ROM are you?
2. What's stopping you from flashing via odin/heimdall?
Click to expand...
Click to collapse
Well im on stock rom just rooted the phone. and flashed custom recovery.
This message shows in the top left conor when i Boot in to revocery.
stock rom 4.3 from samsung
nyvang101 said:
Well im on stock rom just rooted the phone. and flashed custom recovery.
This message shows in the top left conor when i Boot in to revocery.
stock rom 4.3 from samsung
Click to expand...
Click to collapse
If it only appears when u boot in recovery is the normal coz u changed the STOCK recovery for this custom one. If u flash other KERNEL the logo appears when u boot the phone. Anyway now u can flash KERNEL/ROM that u prefer
Recovery is not seandroid enforcing Knox set to 0x1
Hi guys, Just had the same messages on booting : KERNEL/RECOVERY IS NOT SEANDROID ENFORCING and Knox set to 0x1
First, DO NOT FLASH OLDER ANDROID VERSION (4.2.2 / 4.1.2) OVER THE ANDROID 4.3 UPDATE
If ever its done already and you need to Unbrick your samsung device, read the following post to restore :
Just had the same messages on booting : KERNEL/RECOVERY IS NOT SEANDROID ENFORCING and Knox set to 0x1
just after I flashed 4.2.2 based Custom Rom using an OTG cable/FlashDrive over Android 4.3 Stock and/or Custom Roms.
I had these at boot in red and yellow : Warranty void and Knox set to 0x1. But in About device, Android version went from 4.3 to 4.2.2 then i tryied some different custom kernels but nothing to do, wifi keeps crashing plus i had these bootup messages. I did FULLY wipe/restore the device to stock android 4.3 on my SGH-I337M phone using odinv3.09 and I337MVLUEMK6_I337MOYAEMK6_I337MVLUEMK6_HOME.tar.md5
file and it worked after something like the 3rd try, why the importance to FULLY wipe system, data, dalvik cache, cache using a custom Recovery before starting the restore
I dont recommend to flash older android version over The update 4.3. It was such a waste of time to restore it!
Just saying, if you guys had the same issue, your phone ISNT bricked, It took me around 15 hours to find and download Odin and Samsung stock 4.3 firmware plus ReRoot and flash it with odin... ive used my OTG cable to flash kernels or to restore from backups and now, my phone
is FIXED :good:
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
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
Hello guys, I need your help, I am really a noob in rooting and decided to give it a go with CF AUTO ROOT, and I downloaded the correct files, everything was correct, I started the method and it said "PASS" Now the phone is stuck in a bootloop and it says
recovery booting..
recovery is not seandroid enforcing
set warranty bit: recovery then restarts again, I AM COUNTING ON YOUR GOOD GRACES, PLEASE HELP ME!!!!!!
TheDon772 said:
Hello guys, I need your help, I am really a noob in rooting and decided to give it a go with CF AUTO ROOT, and I downloaded the correct files, everything was correct, I started the method and it said "PASS" Now the phone is stuck in a bootloop and it says
recovery booting..
recovery is not seandroid enforcing
set warranty bit: recovery then restarts again, I AM COUNTING ON YOUR GOOD GRACES, PLEASE HELP ME!!!!!!
Click to expand...
Click to collapse
Can you put it in download mode? Have you tried the button combo (power + vol up + home) to go into recovery?
harry9991 said:
Can you put it in download mode? Have you tried the button combo (power + vol up + home) to go into recovery?
Click to expand...
Click to collapse
I can put it in download mode but it does not boot to recovery mode...
TheDon772 said:
I can put it in download mode but it does not boot to recovery mode...
Click to expand...
Click to collapse
Have you tried flashing a custom recovery from Download mode? I'd give that a go then flash a custom ROM (I assume you still want a custom ROM?)
harry9991 said:
Have you tried flashing a custom recovery from Download mode? I'd give that a go then flash a custom ROM (I assume you still want a custom ROM?)
Click to expand...
Click to collapse
I thought rooting was mandatory in order to flash custom recovery?.... Harry you look like a professional in this, please give me a step-by-step solution, since logically it seems the problem is in the recovery? Maybe I deleted it since I can't boot to it.... I have to root then flash recovery then flash rom, right?
TheDon772 said:
I thought rooting was mandatory in order to flash custom recovery?.... Harry you look like a professional in this, please give me a step-by-step solution, since logically it seems the problem is in the recovery? Maybe I deleted it since I can't boot to it.... I have to root then flash recovery then flash rom, right?
Click to expand...
Click to collapse
Recovery comes after rooting IIRC (I rooted mine ~1 year ago so it's a bit fuzzy) so if your rooting was successful then a custom recovery flash should be possible (TWRP recommended)
harry9991 said:
Recovery comes after rooting IIRC (I rooted mine ~1 year ago so it's a bit fuzzy) so if your rooting was successful then a custom recovery flash should be possible (TWRP recommended)
Click to expand...
Click to collapse
Looks like it's not successful since it's not booting to android.. It just boots the loading screen, types the sentences I put in bold, and restarts again...... What to do? Flash a stock rom via odin?
TheDon772 said:
Looks like it's not successful since it's not booting to android.. It just boots the loading screen, types the sentences I put in bold, and restarts again...... What to do? Flash a stock rom via odin?
Click to expand...
Click to collapse
Stock ROM via Odin would be the safest route IMO, make sure you use the correct stock ROM for your device (there are numerous variations)
harry9991 said:
Stock ROM via Odin would be the safest route IMO, make sure you use the correct stock ROM for your device (there are numerous variations)
Click to expand...
Click to collapse
I found a stock rom, 5.0.1 lollipop Germany (DBT), I will try. hopefully it works!!
Just Download twrp twrp-2.8.7.0-trltexx.img from https://dl.twrp.me/trltecan/ put your phone in download mode, connect to odin, select the downloaded twrp in CP and flash it. no more bootloops.
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.