So I get this text on the left top corner of the device along with Set Warranty Bit:Kernel below it, whenever I restart my phone or turn it on after shutting down. So far this hasn't caused any apparent problems such as bootloops or anything else, device works perfectly fine. I just wanna know if this is supposed to be there after Rooting & flashing a custom ROM or if this is only on my phone? Googling it associates this with bootloops which I'm not facing here.
yaseershahid said:
So I get this text on the left top corner of the device along with Set Warranty Bit:Kernel below it, whenever I restart my phone or turn it on after shutting down. So far this hasn't caused any apparent problems such as bootloops or anything else, device works perfectly fine. I just wanna know if this is supposed to be there after Rooting & flashing a custom ROM or if this is only on my phone? Googling it associates this with bootloops which I'm not facing here.
Click to expand...
Click to collapse
It's a warning issued by newer bootloaders of Sammy devices when the kernel is not signed by samsung. It does not harm and you should live with it.
Related
So yesterday I was attempting to play with some ROMs on my phone, and tried a couple of the Google Edition KitKat ROMs. The install process went normally, but after bootup, both ROMs I tried were giving an error repeatedly for com.android.phone after the phone booted up. So I OK'd through the error messages whenever it would pop up, and eventually force closed through app manager, and put the phone into airplane mode so it would stop popping up so I could check out the ROM. Volume was working at the time because I remember notification sounds while I was messing around. Once I had my fun, I went back into CWM, wiped, and restored to my normal ROM which is PAC Man 4.2.2. Restore process seemed to go fine.
Now this morning I attempted to turn on Pandora as I was getting ready for work, and it kept auto forwarding through each song and was acting weird. So I tried Google Play Music, and it force closed and gave a DSP Manager not responding error. So I tried Apollo, and same thing happened. Rebooted a few times, tried to reinstall DSP, Music, and Apollo, and the same thing was happening. I also noticed I had no notification sounds and if I try to change my sounds, I cant hear the preview. Finally, if I try to make a call by clicking on the Phone icon, I can see my call history, contacts, etc, but if I try to call out, the screen goes black. The call does go through though, but there is nothing on the screen and I cant hear anything.
So I went back to an even older restore I had saved, and even a STOCK GS4 rooted restore I had, and the problems persisted. So for the hell of it, I tried to restore back to stock unrooted image but then I remembered I couldnt because of Knox, and the phone got stuck in download mode while trying to ODIN. Eventually I was able to get back to my latest restore of PAC Man but the problems persist.
What could the issue be? Its happening no matter what ROM Im using. But I do not think its a hardware problem or I likely wouldnt have all the quirky things happening on the phone apps (I dont think?). Is there something in the firmware or bootloader that would make the volume/phone functions not work? When it got stuck in ODIN download mode could that have screwed something up? Any help is apprecated.
I dunno if u void ur warranty but i think yes, but this isnt important now (take a look in your download mode knox 0x0 (ok) or knox 0x1(void). I think the best u can do:
- Download one ROM (flashable in RECOVERY) that no **** ur warranty if ur KNOX still 0x0 (in the case KNOX is 0x1, download any good rom for your device)
- Copy it to your External SD card
- Go to CUSTOM RECOVERY
- Wipe all
- Install the .zip file
- Enjoy!
I already know the warranty is voided and I'm not concerned with the Knox stuff, I've already been through all that. I accidentally upgraded to 4.3 bootloader in the past but thankfully had a custom recovery already installed so I'm OK with that. I'm just trying to figure out what may have caused the volume and app issues and how to resolve.
Any other ideas? I'd really like to avoid getting a new phone that might have Knox installed out of the box and be stuck with a stock phone.
Just realized it will not play youtube app and Chrome browser videos either, just crashes, and the handsfree camera feature screws up taking pictures so I have to disable that feature. Something isnt right.
Hi,
My N910F has recently been acting weirdly. It either randomly reboots itself, or just freezes for several seconds when switching screens or scrolling/tapping buttons. This started a couple of weeks ago on stock 5.0.1 (this version, I think) running Emotion kernel. This was running fine for a while; I didn't flash any new mods during this time, although I did switch between AEL kernel and Emotion once or twice without much success.
Thinking it was just one of those situations that called for a clean slate; I backed up my important stuff, booted into TWRP to wipe all partitions, then flashed stock 5.1.1 via Odin (this version, which I'm currently running). But even before I rooted it once again the phone was displaying the same aforementioned symptoms, both during and after going through the built-in setup wizard. This behaviour continued after flashing TWRP and AEL kernel v8.2, which I'm currently on at the moment. If it makes any difference I've also noticed that the lower my battery level, the more often it reboots itself. The battery level also "yo-yos" sometimes, usually at lower levels.
I've uploaded the relevant logs as advised elsewhere for anyone who can decipher them, as I otherwise don't know what to look for. This includes my last three kmsg dumpstate logs (just in case it's a slightly different cause each time), as well as my logcat and dmesg files (whatever they are lol) which I got using the SysLog app.
Any help would be appreciated, and if you need any more info please let me know.
Thanks .
*bump*
I have the same problem. Help would be highly appreciated. : )
*bump*
[UPDATE]: Once or twice when it's crashed as above, it would try and boot again but then reboot into download mode with the following text at the top of the screen above all the other info:
Code:
Could not do normal boot.
ddi: mmc_read failed
If I then pull the battery and turn it on again, it boots up as normal (at least until the next crash). Is this something that can be fixed with a fresh flash in Odin (or some other method), or is my phone on the way to its death?
Got the same issue + loses Wifi password after random reboot. Sent the phone back to the operator I bought it from 1 week ago and they did a repair. They replaced the USB-flex, did a firmware upgrade(?? ..was already updated to latest) and sent it back. I got it this morning and at first the phone now works fine and no more "mmc_read fail". But after some time the random reboots started again. Not so often now but still 4 times over the day and twice the wifi-password is lost and I had to retype it. Now I'm on the fence and just waiting for the first mmc_read fail" to happen before I complain and send it back for a second repair. I can not imagine this beeing beeing other than a hardware fail coming from a weak spot on the phone. I got the impression many people has the same issue and it really comes to life after upgrading to 5.1.1.
I also think the problem at the service shop ist that they just do a quick system test on a clean wiped phone and can't find the issue and think the phone is fine. After reinstalling my 200 apps and setting up my phone all over again, the workload causes the issue to reappear and I now have to ask the service shop for a deeper check. They accepted this as a warranty fix all though my phone has a knox trip (0-1)x4...
I've also faced random reboots on Lollipop. How i solved that? Simple. I downgraded to Kitkat. Lollipop still having lots of battery drains and bugs even on 5.1.1
[UPDATE]
I've decided to go through my network provider to get a replacement sent out to me, which they were happy to do after going through their line of questioning over the phone ("have you tried turning it off and on again", "did you try taking out your memory card and see if that helped", "did you try doing a factory reset", etc). They say it will get here tomorrow so fingers crossed for the replacement.
The ddi mmc_read fail has not reappeared yet..
It's strange.. Lately the random reboots are not wiping my wifi passwords anymore, but now after every random reboot the multiwindow is enabled and I've got to untick it in quick settings..
Latest: It seems that the random reboot may come from heavy account sync workload. I did have 5 Google accounts syncing on my phone + 6 excange accounts and when i disabled syncing alltogether the phone ran a lot smoother and the reboots stoped. So i deleted all Google accounts except my main account and for now thing seems to be fairly stable. I've also uninstalled all for me unimportant 3'rd party apps, reducing 3'rd party app count from aprx 200 to 150..
If things develop further I'll come back with more
Sent from my ****in' phone!
Thanks fot starting this thread Jointfcfan...i am using 910P and have same issue of your post 1 and 4!!!!
Loosing hope on Samsung, it is really frustrating...
Tried cleaning cash, dalvic, reboots, on latest 5.1.1 k version...frozen all not neede games and apps ...only 1 google and 1 exchange account no auto sync
At next stage while rebooting it sometime going an error stating kernel panic and i have to pull battery to restart
Replacing USB-flex board at service shop has cured the "ddi. mmc_read fail" boot issue for good.
So to me it seems that when many people experiences this, the USB-flex board may have a built in design flaw making it a weak spot on the Note 4.
Also I found that the phone works A LOT smoother if using Nova launcher instead of TW. Random reboot count is way down and phone works almost normally. Still some lag, mostly when unlocking screen, but reboots happens only 2-3 times a day now. Still random rebooting enables "multi window" option every time..
I've also rooted the phone now using CF-autoroot. I've flashed Philz CWM recovery and using it to install Wanam Xposed. So now I can run Greenify properly in Xposed mode and automaticly hibernate apps including system apps..
NB! Be aware, flashing root and custom recovery trips Knox counter 0x1 permanently and MAY void warranty
I have also mailed my operator asking them to take in the phone a second time for check/repair, alt. replacing the phone. I guess when they did system check 1st. time without issues after replacing the USB-flex, it was done when phone was reset to factory and under no significant workload.
Sent from my ****in' phone!
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
My XT1575 just decided to go into a bootloop a week ago on its own, literally. I was just checking traffic on Google maps when I noticed it started to lock up. Finally, I see the Motorola splash screen, and that was the beginning of it. Went into recovery mode and tried a factory reset, clear cache partition, etc. but no luck. I've tried everything under Android 6.0 here but it continues to bootloop no matter what I do.
It's not rooted and the bootloader is locked, so I don't think I can even install TWRP or any custom recovery. I have never even though of enabling USB debugging so that's out of the question. What's odd is after trying all sorts of things, sometimes, after the phone has been off for a while I would power it on and it would actually boot into the Welcome screen. Shortly after that though, it locks up and starts bootlooping again. I don't know what else I can do about this or if it's recoverable. I hope someone can help. If it's of any significance, when in recovery mode, at the top I see what I think is the firmware it's currently on -- motorola/clark_retus/clark 6.0/MPHS24.49-18-4/5. Please help!
Update - After having my XT1575 powered off overnight, I powered it on this morning and it was able boot all the way into the Welcome screen, setup, etc. Right away I went and turned on USB Debugging and Allow OEM unlock. Tried rebooting and again it fails to boot. What's weird is it randomly seems to boot when it wants, and something must be corrupt but I just don't know what it could be. Does anyone have any ideas?
Don't unlock the bootloader.
If it is locked and behaving that way you should be able to get a warranty fix out of Lenovorola. If you unlock the bootloader you void your warranty, and they might choose to not honor it even if you say the problem started before.
Painful and slow as it might be, I'd recommend working with the manufacturer on this one.
jason2678 said:
Don't unlock the bootloader.
If it is locked and behaving that way you should be able to get a warranty fix out of Lenovorola. If you unlock the bootloader you void your warranty, and they might choose to not honor it even if you say the problem started before.
Painful and slow as it might be, I'd recommend working with the manufacturer on this one.
Click to expand...
Click to collapse
Yes undo what you just did an follow this guy
jason2678 said:
Don't unlock the bootloader.
If it is locked and behaving that way you should be able to get a warranty fix out of Lenovorola. If you unlock the bootloader you void your warranty, and they might choose to not honor it even if you say the problem started before.
Painful and slow as it might be, I'd recommend working with the manufacturer on this one.
Click to expand...
Click to collapse
I'm afraid it's too late for the bootloader, since it was one of the things I was trying out of desperation. After trying fastboot flashing the stock firmwares, I still get bootloops and strangely enough I was able to use the phone the other day for several hours before it started bootlooping again Thing is, it seems to behave differently at random times. Sometimes it makes it all the way up to the "Android is upgrading" screen but then freezes and reboots.. Other times it locks up at the Motorola splash screen and reboots.. And sometimes it even boots all the way up, is usable for a little bit, then begins bootlooping on its own.
I'm just wondering if something is corrupt software-wise (boot? system? etc?) or if it's a hardware issue. How do I even tell at this point?
iflyimpilot said:
I'm afraid it's too late for the bootloader, since it was one of the things I was trying out of desperation. After trying fastboot flashing the stock firmwares, I still get bootloops and strangely enough I was able to use the phone the other day for several hours before it started bootlooping again Thing is, it seems to behave differently at random times. Sometimes it makes it all the way up to the "Android is upgrading" screen but then freezes and reboots.. Other times it locks up at the Motorola splash screen and reboots.. And sometimes it even boots all the way up, is usable for a little bit, then begins bootlooping on its own.
I'm just wondering if something is corrupt software-wise (boot? system? etc?) or if it's a hardware issue. How do I even tell at this point?
Click to expand...
Click to collapse
The random nature of what you're describing does sound like hardware. Consider a full restore where you fastboot flash everything back to stock of you haven't already.
Check logs. See if you're getting anything in last_kmsg. Use an app like syslog if you aren't used to pulling them, though you might have to use adb if you aren't getting through boot all the time.
jason2678 said:
The random nature of what you're describing does sound like hardware. Consider a full restore where you fastboot flash everything back to stock of you haven't already.
Check logs. See if you're getting anything in last_kmsg. Use an app like syslog if you aren't used to pulling them, though you might have to use adb if you aren't getting through boot all the time.
Click to expand...
Click to collapse
Thanks for replying. I've tried fastboot flashing everything and even going into recovery and clearing cache partition as well as doing a factory data reset. I'm afraid it may very well be hardware. I'll try your suggestion about the logs.
Is 'last_kmsg' a line I should be looking for in the log? If so, what would I need to see in order to determine whether or not it's a hardware problem?
iflyimpilot said:
Thanks for replying. I've tried fastboot flashing everything and even going into recovery and clearing cache partition as well as doing a factory data reset. I'm afraid it may very well be hardware. I'll try your suggestion about the logs.
Is 'last_kmsg' a line I should be looking for in the log? If so, what would I need to see in order to determine whether or not it's a hardware problem?
Click to expand...
Click to collapse
/proc/last_kmsg is a log file that should get written to if a kernel panic causes a reboot in theory. In practice I find it is often blank even after a random reboot.
iflyimpilot said:
I'm afraid it's too late for the bootloader, since it was one of the things I was trying out of desperation. After trying fastboot flashing the stock firmwares, I still get bootloops and strangely enough I was able to use the phone the other day for several hours before it started bootlooping again Thing is, it seems to behave differently at random times. Sometimes it makes it all the way up to the "Android is upgrading" screen but then freezes and reboots.. Other times it locks up at the Motorola splash screen and reboots.. And sometimes it even boots all the way up, is usable for a little bit, then begins bootlooping on its own.
I'm just wondering if something is corrupt software-wise (boot? system? etc?) or if it's a hardware issue. How do I even tell at this point?
Click to expand...
Click to collapse
going by that logic the thing that you should have done was get a factory image from moto and flash to stock using moto tools if that failed at fixing it then send into moto it might not be lost yet but the more you progress the more less likely to replace the phone moto is...
it sounds like something is going bad could be ram emmc or the soc
What i would do is get into discussions with lenovo to see if they can get you fixed up. if you unlocked the bl they know be straight with them. if you get nowhere and no rom you load can fix it sell as parts replace at your expense...
I rooted my J5 (SM-J500FN) yesterday the first time. Since then I reflashed the CF-Auto-Root file about 5 times because my phone got stuck at the bootup screen (on the top of the screen it said in yellow: Set Warranty Bit : kernel). This was due to Samsung KNOX which I somehow was able to deactivate it. After trying many times I now can restart my phone consistently without any bootloops (the yellow text is still there).
My problem now is that after about 3 minutes runtime root checker doesnt detect my device as rooted. SuperSU writes that my device isnt rooted. After a restart root works again for maximum 5 minutes. Im really puzzled because I never experienced someting like that befor and I have no clue how to solve this...
-Toby
Toby9 said:
I rooted my J5 (SM-J500FN) yesterday the first time. Since then I reflashed the CF-Auto-Root file about 5 times because my phone got stuck at the bootup screen (on the top of the screen it said in yellow: Set Warranty Bit : kernel). This was due to Samsung KNOX which I somehow was able to deactivate it. After trying many times I now can restart my phone consistently without any bootloops (the yellow text is still there).
My problem now is that after about 3 minutes runtime root checker doesnt detect my device as rooted. SuperSU writes that my device isnt rooted. After a restart root works again for maximum 5 minutes. Im really puzzled because I never experienced someting like that befor and I have no clue how to solve this...
-Toby
Click to expand...
Click to collapse
Happened to me too in the summer...
CF-autoroot isn't really good... Try the old method of flashing SuperSU trough a recovery (TWRP). this should work with no bugs, no matter what.
That yellow text above the screen: "Set Warranty Bit: kernel" is all good. It indicates that your device is rooted by indirectly saying that the system has been modified. I think that some repair app in the phone is restoring files after startup which makes you lose root after a couple of minutes. I suggest you try flashing with TWRP (custom recovery).
Thank you both. I flashed the SuperSU zip and now it is working perfectly.