Note 3 n9005 series issues - Galaxy Note 3 Q&A, Help & Troubleshooting

1. Every time i try to install a kernel i get " kernel not seandroid enforcing " and a boot loop
2. Everytimw i reboot my system , i lose the downloaded keyboard
3. I cant also install any roms
Will reflashing the stock rom fix these problems
BOA1
Am currently on lolipop 5.0

Here you go. Everything you need ?
http://forum.xda-developers.com/showthread.php?t=2609767
Skickat från min SM-N920C via Tapatalk

mahmoodinho98 said:
1. Every time i try to install a kernel i get " kernel not seandroid enforcing " and a boot loop
2. Everytimw i reboot my system , i lose the downloaded keyboard
3. I cant also install any roms
Will reflashing the stock rom fix these problems
BOA1
Am currently on lolipop 5.0
Click to expand...
Click to collapse
So after flash the lollipop stock Rom is that any problem on it?

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

[Q] Samsung Galaxy Note 3 (SM-N9005) TouchWiz 4.4.2 to Cyanogenmod 11 problems

so i was running cyanogenmod 11 official nightly when i saw a leaked 4.4.2 touchwiz rom for my note 3 i went ahead and installed it to see what was different after i was done checking out the rom i decided i would go back to cyanogenmod 11 so i went to my pc and opened odin 3.0.9 and flashed philz clockworkmod recovery on my note 3 then i tried to reboot into recovery only to be greated by: "recovery booting..... recovery is not seandroid enforcing set warranty bit : recovery" and then it just bootlooped so i removed the battery and waited 10 seconds then i put it back in and it booted into system i tried going back into recovery but the same thing happend so i decided to install a different version of the recovery so i installed chenglu clockworkmod recovery this time it only sayed: "recovery booting..... set warranty bit : recovery" and then it booted into recovery i did a factory reset and then tried to flash the cyanogenmod 11 zip file but it sayed that the zip was for hltexx and my device is a hlte i know for a fact that this is not true and my device is the SM-N9005 hltexx but anyway it aborted the installation i tried to find a way to disable this model verification but to no avail now i'm stuck on touchwiz 4.4.2 and can't even downgrade to 4.3 can someone help me find a way out of this mess thank you in advance
This has been said already once on leaked 4.4.2 you can't go back to 4.3 or cm11 4.4 try reading threads it helps
Sent from my SM-N9005 using XDA Premium HD app
XSkullVenomX said:
so i was running cyanogenmod 11 official nightly when i saw a leaked 4.4.2 touchwiz rom for my note 3 i went ahead and installed it to see what was different after i was done checking out the rom i decided i would go back to cyanogenmod 11 so i went to my pc and opened odin 3.0.9 and flashed philz clockworkmod recovery on my note 3 then i tried to reboot into recovery only to be greated by: "recovery booting..... recovery is not seandroid enforcing set warranty bit : recovery" and then it just bootlooped so i removed the battery and waited 10 seconds then i put it back in and it booted into system i tried going back into recovery but the same thing happend so i decided to install a different version of the recovery so i installed chenglu clockworkmod recovery this time it only sayed: "recovery booting..... set warranty bit : recovery" and then it booted into recovery i did a factory reset and then tried to flash the cyanogenmod 11 zip file but it sayed that the zip was for hltexx and my device is a hlte i know for a fact that this is not true and my device is the SM-N9005 hltexx but anyway it aborted the installation i tried to find a way to disable this model verification but to no avail now i'm stuck on touchwiz 4.4.2 and can't even downgrade to 4.3 can someone help me find a way out of this mess thank you in advance
Click to expand...
Click to collapse
You're currently stuck at 4.4.2 and the only custom recovery that seems to be working is this one. Give it a try.
I was in the same situation yesterday. Download the official Samsung KitKat, boot your phone into download mode and flash it via Odin again. After auto reboot you should be good. Then if you want you can flash the latest KitKat CWM and a few custom roms based on official Samsung KitKat. At this very moment, CM builds are not supported by the new bootloader. Don't flash them again.
Gesendet von meinem SM-N9005 mit Tapatalk
ouankou said:
I was in the same situation yesterday. Download the official Samsung KitKat, boot your phone into download mode and flash it via Odin again. After auto reboot you should be good. Then if you want you can flash the latest KitKat CWM and a few custom roms based on official Samsung KitKat. At this very moment, CM builds are not supported by the new bootloader. Don't flash them again.
Gesendet von meinem SM-N9005 mit Tapatalk
Click to expand...
Click to collapse
So I should wait for future cyanogenmod builds or am I stuck forever on touchwiz?
I'm asking myself the same thing...crap I flashed that so fast , even if it works not too bad CM will always be best.
XSkullVenomX said:
So I should wait for future cyanogenmod builds or am I stuck forever on touchwiz?
Click to expand...
Click to collapse
I think the CM guys will solve this boot loader problem finally. Just wait for a while. During this time you could search some simplistic custom rom based on Samsung stock one, which are also pretty good.

Weird Seandroid enforcing problem after root

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.

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