Kernel is not seandroid enforcing in boot screen - Galaxy S 4 Q&A, Help & Troubleshooting

I flashed this custom kernel and when I restarted this message appeared at the top right. Is there a way that I can remove it? Thanks sirs
*Photo not mine but same problem

Install a stock kernel to remove the warning message.

Strephon Alkhalikoi said:
Install a stock kernel to remove the warning message.
Click to expand...
Click to collapse
So it's normal for custom kernels then? Because I want to experiment with this kernel and others too. I won't bother with that message again lol. Thanks

Not only is it normal for custom kernels, it can also occur when installing a stock kernel older than a certain point. For example, when I downgraded my I9505 to Android 4.2.2 to remove the SIM lock that popped back on to the phone, the stock 4.2.2 kernel caused the same warning to appear. Reinstalling Android 4.4.2 after removing the SIM lock caused the warning to disappear.
If you install a custom recovery, you'll see a similar warning when you boot into recovery. This is also normal.

Related

Please help Recovery is not seandroid enforcing

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:

[Q] Kernel is not seandroid enforcing set warranty bit: Kernel - Boot loop ?

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

When flashing new rom, stock at boot screen

Hey,
So I recently acquired a S4 i337m Fido (running 4.3, I1337MVLUEMK6). I tried to root and put TWRP via Odin, didn't end up working (not sure what I did wrong), but managed to root via auto-root and flashed TWRP via Goo Manager.
I have tried twice to put a custom room on, HyperDrive and Paranoid android. I created a nandbackup, then full wiped, and flashed the roms then Gapps and rebooted. Both times, they got stuck on the boot animation (just showing the Samsung Galaxy S4 Logo), with the top left corner saying something about my recovery (when flashed HyperDrive), and something about my kernel when I tried to flash PA. Also, I couldn't get to TWRP on my first 2 tries when flashing HyperDrive (to restore), but got it on my first try with PA.
Any ideas why I am having trouble flashing custom roms?
So what it says on the boot screen logo at top left is:
1. RECOVERY BOOTING (in blue),
2. RECOVERY IS NOT SEANDROID ENFORCING (red)
3. Set Warranty Bit: recovery (yellow)
Cheers, and thanks
Sent from my SGH-I337M using Tapatalk
Miyamato said:
Hey,
So I recently acquired a S4 i337m Fido (running 4.3, I1337MVLUEMK6). I tried to root and put TWRP via Odin, didn't end up working (not sure what I did wrong), but managed to root via auto-root and flashed TWRP via Goo Manager.
I have tried twice to put a custom room on, HyperDrive and Paranoid android. I created a nandbackup, then full wiped, and flashed the roms then Gapps and rebooted. Both times, they got stuck on the boot animation (just showing the Samsung Galaxy S4 Logo), with the top left corner saying something about my recovery (when flashed HyperDrive), and something about my kernel when I tried to flash PA. Also, I couldn't get to TWRP on my first 2 tries when flashing HyperDrive (to restore), but got it on my first try with PA.
Any ideas why I am having trouble flashing custom roms?
So what it says on the boot screen logo at top left is:
1. RECOVERY BOOTING (in blue),
2. RECOVERY IS NOT SEANDROID ENFORCING (red)
3. Set Warranty Bit: recovery (yellow)
Cheers, and thanks
Sent from my SGH-I337M using Tapatalk
Click to expand...
Click to collapse
You need to read a lot more. You can only use safestrap right now. Odin back to MF3 and install safestrap after rooting. Only touchwiz roms using stock kernel will work for you.
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Hey, Thanks for answering. So I have to re flags firmware, and re root, with safestrap correct? After that only tw bases roms with stock kernels will work, or as of right now (current situation) only tw and stock kernels will work?
Sent from my SGH-I337M using Tapatalk
Miyamato said:
Hey, Thanks for answering. So I have to re flags firmware, and re root, with safestrap correct? After that only tw bases roms with stock kernels will work, or as of right now (current situation) only tw and stock kernels will work?
Sent from my SGH-I337M using Tapatalk
Click to expand...
Click to collapse
It appears the first one you flashed Hyperdrive is for ATT at model number is i337 your model is i337m not the same thing.... If it was my phone I would wait for azuziel to reply in the other thread or pm him directly.... you can't use i337 firmware on your phone.... you had and hope still have an unlocked bootloader... this means you don't need safety strap.... talk to azuziel before you get too flash happy.... could save you lots of headaches.....
Your issue is in my Galaxy Tab Pro 10.1 (SM-T525) li (kely. I do is just keep it in low battery state. (Even if you press the power button it wont boot. Dont Charge it!)
And connect it on computer. You will see the only logo of you samsung brand. That is second to the last step. The last step is go it on download mode. By pressing Volume Down+Home Button+Power Button. And click volume up. Now download odin and install the compatible version of TWRP for your phone. And now wait. You will see in odin a Reset *Blue* on top corner of the app that is a good sign. Now if you see a Pass *Green* on the top corner of the app. Your ready to go! It will boot in Normal State!
This Might Helpful!

Did I brick it?

I was trying to remove the knox thing and now it won't go on beyond the Samsung Galaxy S5 custom screen. I have wiped, formated, ect... I have booted into the recovery mode (not safestrap because it does not boot that far. I have tried loading new NI2's NK2's, different kernals and nothing. When trying to load a new rom or kernel, I keep getting a red warnings that the footer is wrong and signature verification failed. Not sure where to go from here. I have gone through the forums and it's all running together now. HELP
Under Android system recovery it has the number KTU84P.G900VVRU1ANI2
I successfully loaded G900V_FirmwareOnly_NI2.tar.md5 with odin and then tried loading optimalrom 12.6 because it worked in the past, but I still get the failed message and the boot stops at the galaxy boot screen.
OK, loaded everything with Odin:
G900V_FirmwareOnly_NI2.tar.md5
G900V_ModemOnly_NI2.tar.md5
ALL_VZW_G900VVRU1ANI2_G900VVZW1ANI2_2525521_REV00_user_low_ship_MULTI_CERT.tar.md5
Now I have my phone back. Now I need to figure out if Knox is back and I need to try to do this again
gr8wing said:
I was trying to remove the knox thing and now it won't go on beyond the Samsung Galaxy S5 custom screen. I have wiped, formated, ect... I have booted into the recovery mode (not safestrap because it does not boot that far. I have tried loading new NI2's NK2's, different kernals and nothing. When trying to load a new rom or kernel, I keep getting a red warnings that the footer is wrong and signature verification failed. Not sure where to go from here. I have gone through the forums and it's all running together now. HELP
Under Android system recovery it has the number KTU84P.G900VVRU1ANI2
I successfully loaded G900V_FirmwareOnly_NI2.tar.md5 with odin and then tried loading optimalrom 12.6 because it worked in the past, but I still get the failed message and the boot stops at the galaxy boot screen.
OK, loaded everything with Odin:
G900V_FirmwareOnly_NI2.tar.md5
G900V_ModemOnly_NI2.tar.md5
ALL_VZW_G900VVRU1ANI2_G900VVZW1ANI2_2525521_REV00_user_low_ship_MULTI_CERT.tar.md5
Now I have my phone back. Now I need to figure out if Knox is back and I need to try to do this again
Click to expand...
Click to collapse
amazing how difficult people make things.. stock recovery will NOT flash custom roms.. if you are on fresh ni2 just odin the ncg kernal in odin, root, install SS and then odin ni2 kernal back.. now with ss installed, download the ROM you want and flash rom.zip in ss and the kernal for it if necessary..
Every custom rom on here is already knox free. Id recommend not trying to remove knox yourself again or else youll screw it up again from the sounds of it.. leave it to the devs to remove it lol.
On a side note, a brick is a phone that doesnt boot at all.. meaning it sits on a black screen and NOTHING at all boots. If you can get into recovery or dl mode then you most likely do not have a hard brick
elliwigy said:
amazing how difficult people make things.. stock recovery will NOT flash custom roms.. if you are on fresh ni2 just odin the ncg kernal in odin, root, install SS and then odin ni2 kernal back.. now with ss installed, download the ROM you want and flash rom.zip in ss and the kernal for it if necessary..
Every custom rom on here is already knox free. Id recommend not trying to remove knox yourself again or else youll screw it up again from the sounds of it.. leave it to the devs to remove it lol.
On a side note, a brick is a phone that doesnt boot at all.. meaning it sits on a black screen and NOTHING at all boots. If you can get into recovery or dl mode then you most likely do not have a hard brick
Click to expand...
Click to collapse
The issue I have been having is the /dev/uinput. I thought it was because of knox, but now I see it's more than that and nobody has made a work around yet. I may be mistaken, but I think I don't have a chance with the uinput.
gr8wing said:
The issue I have been having is the /dev/uinput. I thought it was because of knox, but now I see it's more than that and nobody has made a work around yet. I may be mistaken, but I think I don't have a chance with the uinput.
Click to expand...
Click to collapse
Youre doing too much.. supersu disables knox and uninstaling anything knox related is all you can do.. messing around with stuff you dont know about you WILL end up bricking your phone
gr8wing said:
I was trying to remove the knox thing and now it won't go on beyond the Samsung Galaxy S5 custom screen. I have wiped, formated, ect... I have booted into the recovery mode (not safestrap because it does not boot that far. I have tried loading new NI2's NK2's, different kernals and nothing. When trying to load a new rom or kernel, I keep getting a red warnings that the footer is wrong and signature verification failed. Not sure where to go from here. I have gone through the forums and it's all running together now. HELP
Under Android system recovery it has the number KTU84P.G900VVRU1ANI2
I successfully loaded G900V_FirmwareOnly_NI2.tar.md5 with odin and then tried loading optimalrom 12.6 because it worked in the past, but I still get the failed message and the boot stops at the galaxy boot screen.
OK, loaded everything with Odin:
G900V_FirmwareOnly_NI2.tar.md5
G900V_ModemOnly_NI2.tar.md5
ALL_VZW_G900VVRU1ANI2_G900VVZW1ANI2_2525521_REV00_user_low_ship_MULTI_CERT.tar.md5
Now I have my phone back. Now I need to figure out if Knox is back and I need to try to do this again
Click to expand...
Click to collapse
Where can I download the multi cert file?
ALL_VZW_G900VVRU1ANI2_G900VVZW1ANI2_2525521_REV00_ user_low_ship_MULTI_CERT.tar.md5
I have encountered the exact same problem.
Thanks.
robertb9657 said:
Where can I download the multi cert file?
ALL_VZW_G900VVRU1ANI2_G900VVZW1ANI2_2525521_REV00_ user_low_ship_MULTI_CERT.tar.md5
I have encountered the exact same problem.
Thanks.
Click to expand...
Click to collapse
Here you go!
https://www.androidfilehost.com/?fid=23622183712474060
Tulsadiver and gr8wing you guys are life savers! Thanks so much! I "ODINed" the firmware only, and then the modem only. after the phone downloaded each, it did not get past boot either time, but I was calm and hopeful. I odined the multi cert file and although it took a lot longer than I thought it would, it worked to perfection and my phone is fully functional and back to where it was two days ago.
I had NI2 rooted, then accidentally did the NK2 OTA update, which lost root. I finally got around to rerooting and decided to get rooted lollipop. I now have changed course and will sit happily with rooted NK2 kitkat.
Thanks!

set warranty bit: recovery / kernel is not seandroid enforcing (J500FN)

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

Categories

Resources