Database Users

[Q]

Hi,
probably not the first time the question is ask... but!
I flash with cyanfox rom, the phone reset and stard loading with the cafox logo.... but nothing happend....
why I restart my phone,
this appear:
kernel is not seandroid enforcing
set warranty bit kernel
I try few things but nothing... the cyanfox start but wont load
what can i do??
Samsung S4 sgh-I337M
alex

Have you tried redownloading and clean flashing?
Sent from my Nexus 5 using Tapatalk

Bootloop! Need help, please!

Hello. This morning I decided to install a custom ROM on my S4 i9505. I installed Clockwork Recovery, installed CM12.1, but few hours after, I decided to go back to stock ROM, which I backed up entirely through Clockwork. After everything was restored, I booted up and my phone was stuck at SAMSUNG glowing screen. I managed to go back to recovery and tried to reinstall CM12.1 from backup but that didn't helped me eighter.......CM12.1 gets stuck ever earlier......at Samsung GT-i9505 screen and shows on top of the screen "kernel is not seandroid enforcing". What should I do now? Is this a "pretty" common problem or I'm fked? In this situation can I flash back stock ROM through ODIN?
Thanks in advice,
Andrei.

Solved bootloop, but now there is no Wi-fi
I've solved 1 stupid I did, I need to solve another one. I've told you guys that this morning I've installed Clockwork recovery. Now my Wi-Fi is not working and I think I changed the kernel this morning. Anyone can help me?
Thanks in advice.

Flash the ROM again. Sometimes it takes a couple flashes for the modem to properly work.

Strephon Alkhalikoi said:
Flash the ROM again. Sometimes it takes a couple flashes for the modem to properly work.
Click to expand...
Click to collapse
Solved the problem. Thanks for the help. Flashed another stock firmware and everything works.

Faulty hardware?

Recently I've been having problems with random lag spikes, reboots and suddenly the screen just going black. This has gradually started happening more and more. Sometimes I've also gotten a boot fail screen wich resets the phone into download mode, other times I've gotten a kernel panic message stating eMMC read fail. To get the phone running again I often have to try several reboots and pull the battery for a couple of seconds. The battery is brand new as I just replaced my old battery that was starting to instantly deplete at around 20%.
It seems like a couple of other people has had this issue.
I've been using the same debloated stock root rom for the past 3-4 months, and it has worked fine, until recently when these problems started occurring. I suspected the source of the problem was xposed modules or an app wreaking havoc on the device. First I tried uninstalling xposed through TWRP, but the problems still occured. Then I tried to do a factory reset through the settings menu, but oddly the phone just restarted without performing any reset. So i figured I had to do a wipe via TWRP, but I got some kind of mounting error. After installing TWRP v3 I managed to wipe and install a new rom.
I tried these roms but the problem still presists after several tries of flashes and wipes.
http://forum.xda-developers.com/note-4/snapdragon-dev/rom-kyubi-rom-note-5-t3220106
http://forum.xda-developers.com/note-4/snapdragon-dev/kyubi-rom-port-n5-n910f-coj3-v5-t3254964
The last thing I have yet to try is to do a clean stock flash through Odin, but chances seem dim as evidence points towards some kind of hardware failure. Flash chip maybe?
If it actually is hardware failure I have the problem of having modified the phone, so even if I go back to a stock unrooted rom the "Kernel is not seandroid enforcing" and "Set warranty bit: kernel" text will still show up during boot. If I am correct there is still no way to remove this, right? Luckily Norwegian laws are quite lenient when it comes hardware fault warranty, with up to 4 years of warranty for phones.
Will the service shop immediatly dismiss phones if they detected a modified system, even if it's 100% guaranteed that the problem is hardware failure? Has anyone had any experience with this?
I know a friend of mine got his rooted Nexus 5 replaced, but that didn't turn on at all, so I think they just replaced it without checking.

lameplx said:
Recently I've been having problems with random lag spikes, reboots and suddenly the screen just going black. This has gradually started happening more and more. Sometimes I've also gotten a boot fail screen wich resets the phone into download mode, other times I've gotten a kernel panic message stating eMMC read fail. To get the phone running again I often have to try several reboots and pull the battery for a couple of seconds. The battery is brand new as I just replaced my old battery that was starting to instantly deplete at around 20%.
It seems like a couple of other people has had this issue.
I've been using the same debloated stock root rom for the past 3-4 months, and it has worked fine, until recently when these problems started occurring. I suspected the source of the problem was xposed modules or an app wreaking havoc on the device. First I tried uninstalling xposed through TWRP, but the problems still occured. Then I tried to do a factory reset through the settings menu, but oddly the phone just restarted without performing any reset. So i figured I had to do a wipe via TWRP, but I got some kind of mounting error. After installing TWRP v3 I managed to wipe and install a new rom.
I tried these roms but the problem still presists after several tries of flashes and wipes.
http://forum.xda-developers.com/note-4/snapdragon-dev/rom-kyubi-rom-note-5-t3220106
http://forum.xda-developers.com/note-4/snapdragon-dev/kyubi-rom-port-n5-n910f-coj3-v5-t3254964
The last thing I have yet to try is to do a clean stock flash through Odin, but chances seem dim as evidence points towards some kind of hardware failure. Flash chip maybe?
If it actually is hardware failure I have the problem of having modified the phone, so even if I go back to a stock unrooted rom the "Kernel is not seandroid enforcing" and "Set warranty bit: kernel" text will still show up during boot. If I am correct there is still no way to remove this, right? Luckily Norwegian laws are quite lenient when it comes hardware fault warranty, with up to 4 years of warranty for phones.
Will the service shop immediatly dismiss phones if they detected a modified system, even if it's 100% guaranteed that the problem is hardware failure? Has anyone had any experience with this?
I know a friend of mine got his rooted Nexus 5 replaced, but that didn't turn on at all, so I think they just replaced it without checking.
Click to expand...
Click to collapse
if you flash stock unrooted firmware with odin it will no longer display "kernel or recovery are not seandroid enforcing" or "set warranty bit kernel" ....but the service center if they boot into download mode and check knox counter will be able to find out if the phone has been rooted previously because once knox counter changes from 0x0 to 0x1 after rooting there is noway to reset it back to 0x0.

dork997 said:
if you flash stock unrooted firmware with odin it will no longer display "kernel or recovery are not seandroid enforcing" or "set warranty bit kernel" ....but the service center if they boot into download mode and check knox counter will be able to find out if the phone has been rooted previously because once knox counter changes from 0x0 to 0x1 after rooting there is noway to reset it back to 0x0.
Click to expand...
Click to collapse
Yeah, just remembered that after flashing stock room through Odin just now. It's been a while since I've been on stock
I will give the stock rom a go for a couple of hours to see if the problems persists.

Seems like the issue still are there after Odin flash.
Could re-partitioning with a pit file help?
http://forum.xda-developers.com/not...te-4-pit-files-repartiton-f-g-c-t-w8-t3282641

SuperSU in app update failed - every app stopped working

I hope I'm posting this at the right place. I have to start off by saying that I'm almost a complete noob regarding rooting and things that have to do with it. I rooted my phone about 6 months ago I think and the reason why I did that was only because I wanted to be able to freeze down some apps with titanumbackup. Since it's been such a long time ago I've forgotten almost all those steps I did when I rooted my phone.
Anyways back to the issue. So today I got a notification from SuperSU saying that it needed to update. I didn't think too much about it so I just followed the notification and updated it. When I started SuperSU I got 2 choices. Either updating normal or by TWRP/CWM. The dumb me just pressed TWRP/CWM for no reason and the phone rebooted into recovery mode. A lot of text started scrolling down at the bottom left corner and when it finally stopped it said something along the line with update failed. I pressed "reboot the system now" from the list and after that my phone rebooted. The samsung logo popped out as usual but after that the screen was completely black. Then I got a lot of popups telling me that this and that app stopped working. Contacts stopped working, whatsupp stopped working, messenger stopped working etc. Like all the apps stopped working.
So I've been trying to google a solution to this but it doesn't seem like someone has had the exact same problem. I've been trying to research things about rooting and such again to see if it can help me someway but I don't think I can't fix this problem by doing just that, so therefore I'm writing this to see if you guys can help me since you have waaay more experience than me when it comes to rooting. I've tried flashing CF-Auto-Root-jflte-jfltexx-gti9505 again using odin but the problem stays. I've tried updating to the latest stable SuperSU by downloading the zip file and putting it on the sd card and then using recovery mode but it didn't work either (I got an error E: signature verification failed). So after reading about the error I tried flashing a CWM but everytime I do that with odin I either get a FAIL or I keep getting the messages (Added, removed, added, removed). I download kies to get the drivers but it didn't help. and now when I try to boot into recovery mode my phone just keep rebooting.
I really don't know what to do now guys so I hope you guys can help me out :crying:
My phone:
Samsung galaxy s4 GT-I9505
Rooted with CF-Auto-Root-jflte-jfltexx-gti9505.tar

durantala said:
I hope I'm posting this at the right place. I have to start off by saying that I'm almost a complete noob regarding rooting and things that have to do with it. I rooted my phone about 6 months ago I think and the reason why I did that was only because I wanted to be able to freeze down some apps with titanumbackup. Since it's been such a long time ago I've forgotten almost all those steps I did when I rooted my phone.
Anyways back to the issue. So today I got a notification from SuperSU saying that it needed to update. I didn't think too much about it so I just followed the notification and updated it. When I started SuperSU I got 2 choices. Either updating normal or by TWRP/CWM. The dumb me just pressed TWRP/CWM for no reason and the phone rebooted into recovery mode. A lot of text started scrolling down at the bottom left corner and when it finally stopped it said something along the line with update failed. I pressed "reboot the system now" from the list and after that my phone rebooted. The samsung logo popped out as usual but after that the screen was completely black. Then I got a lot of popups telling me that this and that app stopped working. Contacts stopped working, whatsupp stopped working, messenger stopped working etc. Like all the apps stopped working.
So I've been trying to google a solution to this but it doesn't seem like someone has had the exact same problem. I've been trying to research things about rooting and such again to see if it can help me someway but I don't think I can't fix this problem by doing just that, so therefore I'm writing this to see if you guys can help me since you have waaay more experience than me when it comes to rooting. I've tried flashing CF-Auto-Root-jflte-jfltexx-gti9505 again using odin but the problem stays. I've tried updating to the latest stable SuperSU by downloading the zip file and putting it on the sd card and then using recovery mode but it didn't work either (I got an error E: signature verification failed). So after reading about the error I tried flashing a CWM but everytime I do that with odin I either get a FAIL or I keep getting the messages (Added, removed, added, removed). I download kies to get the drivers but it didn't help. and now when I try to boot into recovery mode my phone just keep rebooting.
I really don't know what to do now guys so I hope you guys can help me out :crying:
My phone:
Samsung galaxy s4 GT-I9505
Rooted with CF-Auto-Root-jflte-jfltexx-gti9505.tar
Click to expand...
Click to collapse
Did you try to just uninstall supersu and redownload it from the play store?

Lennyz1988 said:
Did you try to just uninstall supersu and redownload it from the play store?
Click to expand...
Click to collapse
When I boot up the phone the screen is totally black. The only thing that shows are those popups (a lot of them) that tells me that this and that app stopped working. :/

durantala said:
When I boot up the phone the screen is totally black. The only thing that shows are those popups (a lot of them) that tells me that this and that app stopped working. :/
Click to expand...
Click to collapse
Right now I don't see any other choice than flashing a stock rom.
Or you could try reflashing the recovery.
Make sure you are using the back USB ports and the original cable. Odin is quite sensitive with this.

Failed to install superman rom. S7 Edge

Hey im back to android but I cant get the custom rom to boot. It keeps saying (Kernel is not SEANDROID ENFORCING) and it just stays there. I tried all the kernels from inside the rom(aroma) but non of them boot. I installed the nougat BL and Modem... maybe someone can tell me what im doing wrong. Sorry for my english.
EDIT: okay now with the stock kernel (KERNEL IS NOT SEANDROID ENFORCING) is gone but its still stuck at samsung galaxy s7 edge powered by android screen.

hi,i'm in the same problem.did you find how to solve it?

Kernel is not seandroid solved
After many times trying to install this rom and all the time getting stuck on boot logo and with kernel bla bla bla.i want to say first that other roms installed nice and easy.so in the menu aroma ,when you try to install you have option to install magisk or supersu.everytime i tried was left on magisk but after many many times being not succesfull i choose supersu instead and this time worked .after losing my time with this rom ,also crash and reboot when i tried to call somebody (first time in 10 years) and also the battery consumtion is very bad.20% in 1 1/2 hours.