Database Users

[Q] Stuck w/ Set Warranty Bit: Kernel & S4 Logo

Hey folks,
One of the forum moderators pointed me at this thread ( http://forum.xda-developers.com/showthread.php?t=2586586 ) as a suggestion to getting a ROM for my S4 that would alleviate the com.android.phone process crashes I had with other ROMS.
After flashing jfltespr_mk2_deodexed from micro-sd card through the Team Win recovery, my phone is now stuck at the Samsung Galaxy S4 logo screen with (Set Warranty Bit: Kernel) in the upper left.
Having looked through numerous threads on this issue, it seems there's a number of different remedies, from reflashing to simply powercycling.
There wasn't anything that was of much use in http://forum.xda-developers.com/showthread.php?t=2527706 either.
I have odin, and can boot into Team Win Recovery, or download mode. Suggestions/tips/ideas would be appreciated. Thanks.

Seems like you already have Knox tripped. And those warnings are because Knox detected modified files on your phone at boot up. I would suggest to odinto stock MK2
Sent from my SPH-L720 using Tapatalk

Go to this post and download the full stock mk2 tar file. Once downloaded extract the tar file from the zip file and install it using Odin 3.09 for best results. This will bring your phone to full stock unrooted. This should fix your phone problems. It is best to start with a clean slate. If you are still getting the force closes, then something on your data partition is causing your problem and you will need to do a factory reset after installing the tar file.
After you are up and running with no errors then you can re root your phone. I like safe root. It is quick and easy. Just Google Safe Root for Sprint Galaxy S4 and you will find it.
If this doesn't fix your phone than it might be hardware related. Also, just to be sure, make sure you don't have the L720T version of our phone. Because if you do, that is your problem.
http://forum.xda-developers.com/showpost.php?p=49213024
Sent from my icrap 2 using Tapatalk HD

That thread has a huge KNOX warning. I was hoping to ditch the Sprint bloatware.
Am I interpreting things right that I'm basically screwed for non-stock ROM's now?
Also, I have an SPH-L720
On the download rom screen, it reports KNOX KERNEL LOCK as 0x0, KNOX WARRANTY VOID as 0d?
cruise350 said:
Go to this post and download the full stock mk2 tar file. Once downloaded extract the tar file from the zip file and install it using Odin 3.09 for best results. This will bring your phone to full stock unrooted. This should fix your phone problems. It is best to start with a clean slate. If you are still getting the force closes, then something on your data partition is causing your problem and you will need to do a factory reset after installing the tar file.
After you are up and running with no errors then you can re root your phone. I like safe root. It is quick and easy. Just Google Safe Root for Sprint Galaxy S4 and you will find it.
If this doesn't fix your phone than it might be hardware related. Also, just to be sure, make sure you don't have the L720T version of our phone. Because if you do, that is your problem.
http://forum.xda-developers.com/showpost.php?p=49213024
Sent from my icrap 2 using Tapatalk HD
Click to expand...
Click to collapse

dearastronomer said:
That thread has a huge KNOX warning. I was hoping to ditch the Sprint bloatware.
Am I interpreting things right that I'm basically screwed for non-stock ROM's now?
Also, I have an SPH-L720
On the download rom screen, it reports KNOX KERNEL LOCK as 0x0, KNOX WARRANTY VOID as 0d?
Click to expand...
Click to collapse
You're not screwed for non stock ROMs, IF you don't mind tripping the knox 'counter'. If you follow @cruise350 advice you'll be back to Stock. then root (with SafeRoot maybe; search it's here or CF-Auto Root) you could then install a custom recovery (using GooManager or by Odining one), then flash away.
BUT you are going to trip the Knox counter by using a custom recovery.
Please spend a little (actually a lot) of time reading and understanding how things work on this phone and you'll really enjoy it and get the most out of it with as little frustration as possible.
Good luck

From the advice in this thread I was able to get back to stock ROM w/ root (CF-Auto-Root). Thanks for the tips, and for being patient.
I'm going to do some reading on Knox, because I'm getting conflicting reports on the ability to remove it.
leaderbuilder said:
You're not screwed for non stock ROMs, IF you don't mind tripping the knox 'counter'. If you follow @cruise350 advice you'll be back to Stock. then root (with SafeRoot maybe; search it's here or CF-Auto Root) you could then install a custom recovery (using GooManager or by Odining one), then flash away.
BUT you are going to trip the Knox counter by using a custom recovery.
Please spend a little (actually a lot) of time reading and understanding how things work on this phone and you'll really enjoy it and get the most out of it with as little frustration as possible.
Good luck
Click to expand...
Click to collapse

I still can't figure out what the big deal is people have about knox. It does not effect you at all if it is tripped unless you plan on sending your phone to Samsung for warranty service. It does not prevent you from running custom roms, installing mods, or using your phone to its full functionality. It is a secure container program for corporations and government agencies that require more security for access to their networks and information. If your company is not requiring you to have a secure phone, than it means nothing. It is easily disabled or removed. The main difference in our phones after MJA firmware is Samsung made it so we can't downgrade the bootloader any more. This was so they could fully implement the knox container to prevent downgrading to older non knox bootloaders thus skirting the knox security. The warranty flag that it trips is the knox warranty flag, which purpose is to let your IT department know that you have tampered with your phone and can no longer be guaranteed to provide the secure container. It also lets Samsung know you have tampered with your phone which may violate your warranty.

cruise350 said:
I still can't figure out what the big deal is people have about knox. It does not effect you at all if it is tripped unless you plan on sending your phone to Samsung for warranty service. It does not prevent you from running custom roms, installing mods, or using your phone to its full functionality. It is a secure container program for corporations and government agencies that require more security for access to their networks and information. If your company is not requiring you to have a secure phone, than it means nothing. It is easily disabled or removed. The main difference in our phones after MJA firmware is Samsung made it so we can't downgrade the bootloader any more. This was so they could fully implement the knox container to prevent downgrading to older non knox bootloaders thus skirting the knox security. The warranty flag that it trips is the knox warranty flag, which purpose is to let your IT department know that you have tampered with your phone and can no longer be guaranteed to provide the secure container. It also lets Samsung know you have tampered with your phone which may violate your warranty.
Click to expand...
Click to collapse
True but it lock the bootloader from what I’m hearing
Hence stopping the installation of custom roms

Need help with rooting Rogers Galaxy S4 I337M

So first off, I am have a lot of questions that I might as well ask.
First, will rooting my Rogers Samsung Galaxy S4 I337m mess anything up with the carrier? Like, will i still be able to call and text, etc?
Secondly, can my carrier track that I have a rooted phone?
And this is the most important question, how do I actually root this phone? Most of the methods I have tried don't work because the security app "KNOX" keeps denying access for the root to happen. I have tried many ways to remove KNOX from the phone, but none of them work....So how do I actually root this phone without having KNOX shut me down?
Anyways, thanks for the help!

Pellisco said:
So first off, I am have a lot of questions that I might as well ask.
First, will rooting my Rogers Samsung Galaxy S4 I337m mess anything up with the carrier? Like, will i still be able to call and text, etc?
Secondly, can my carrier track that I have a rooted phone?
And this is the most important question, how do I actually root this phone? Most of the methods I have tried don't work because the security app "KNOX" keeps denying access for the root to happen. I have tried many ways to remove KNOX from the phone, but none of them work....So how do I actually root this phone without having KNOX shut me down?
Anyways, thanks for the help!
Click to expand...
Click to collapse
So ...based on the question, and the fact that this is your first post, it appears you have a fair bit of reading to get through before doing it but yes the phone does everything rooted as it did before, you just have access to the whole file system (which means you will have the ability to break things that were "roped off for your protection" before rooting)
No your carrier doesn't know or care you are rooted... unless you do break something and bring it in asking them to fix it, then they will tell you you broke it yourself tough luck. (unless of course you reverse everything back to stock first)
FIRST read all (really... read all of it) of the 2nd and 3rd thread in "AT&T Samsung Galaxy S 4 General"
[GUIDE][INFO] The beginner's info thread (aka. the noob helper) and [HOW-TO] The ULTIMATE All-In-One Guide - I337M & MDL - MF3 - MK2
Then you can root. The "CF Auto-root" method works perfectly on all the Canadian carrier versions (they only differ in carrier bloat.), then install a custom recovery, then install a good backup utility, I suggest TiBu (which will also allow you to remove Knox).
Good luck.

robinsonj said:
So ...based on the question, and the fact that this is your first post, it appears you have a fair bit of reading to get through before doing it but yes the phone does everything rooted as it did before, you just have access to the whole file system (which means you will have the ability to break things that were "roped off for your protection" before rooting)
No your carrier doesn't know or care you are rooted... unless you do break something and bring it in asking them to fix it, then they will tell you you broke it yourself tough luck. (unless of course you reverse everything back to stock first)
FIRST read all (really... read all of it) of the 2nd and 3rd thread in "AT&T Samsung Galaxy S 4 General"
[GUIDE][INFO] The beginner's info thread (aka. the noob helper) and [HOW-TO] The ULTIMATE All-In-One Guide - I337M & MDL - MF3 - MK2
Then you can root. The "CF Auto-root" method works perfectly on all the Canadian carrier versions (they only differ in carrier bloat.), then install a custom recovery, then install a good backup utility, I suggest TiBu (which will also allow you to remove Knox).
Good luck.
Click to expand...
Click to collapse
Yes, I know this is my first post, and you may think I don't know much about rooting, but I have had some experience in the past. I did root my Samsung Galaxy Tab 2, first time I soft bricked it, then actually got to root and stuff to work, so I have some knowledge on what I am doing.
Those two threads that you have linked me, I have looked over and learn't some stuff from them. I have also downloaded CF Auto-Root for the I337m version. I know how to work it, through using Odin and download mode, exact same way I rooted my tablet.
I just have one more question though, rooting it with odin through download mode, that bypasses KNOX and allows the root to work? Cause if I tried rooting with any program like motochopper, KNOX would block it.

Pellisco said:
Yes, I know this is my first post, and you may think I don't know much about rooting, but I have had some experience in the past. I did root my Samsung Galaxy Tab 2, first time I soft bricked it, then actually got to root and stuff to work, so I have some knowledge on what I am doing.
Those two threads that you have linked me, I have looked over and learn't some stuff from them. I have also downloaded CF Auto-Root for the I337m version. I know how to work it, through using Odin and download mode, exact same way I rooted my tablet.
I just have one more question though, rooting it with odin through download mode, that bypasses KNOX and allows the root to work? Cause if I tried rooting with any program like motochopper, KNOX would block it.
Click to expand...
Click to collapse
OK just didn't want you to brick your phone by not really understanding Odin... It is writing to the system partition and has been known to make a mess if the wrong files are dropped in the bootloader or if a download is interrupted.
I'm afraid all I really know about KNOX is from reading about the problems with the 1.x implementation and that the latest was supposed to be the solution for BYOD in a secure enterprise...
I Odined CF Auto-Root and had no issues whatsoever... I'm pretty sure KNOX can only run inside the OS, so in download mode you're outside of where it can interfere with anything. After the root and a custom recovery the first thing I did was freeze all KNOX and "enterprise" files just in case.

robinsonj said:
OK just didn't want you to brick your phone by not really understanding Odin... It is writing to the system partition and has been known to make a mess if the wrong files are dropped in the bootloader or if a download is interrupted.
I'm afraid all I really know about KNOX is from reading about the problems with the 1.x implementation and that the latest was supposed to be the solution for BYOD in a secure enterprise...
I Odined CF Auto-Root and had no issues whatsoever... I'm pretty sure KNOX can only run inside the OS, so in download mode you're outside of where it can interfere with anything. After the root and a custom recovery the first thing I did was freeze all KNOX and "enterprise" files just in case.
Click to expand...
Click to collapse
Okay. Hopefully KNOX doesn't interfere with anything. I also noticed in download mode:
Product Name: SGH-I337M
Current Binary: Samsung Official
System Status: Custom
KNOX Kernel Lock: 0x0
KNOX Warranty Void: 0x0
CSB-CONFIG-LSB: 0x20
Write Protection: Enable
eMMC Burst Mode: Enabled
So which ones trip when I root it? I know that the 'Current Binary' will trip if I install a custom rom, but, what about the KNOX stuff? I know that the Warranty Void will then turn to '0x1' and I think the kernel lock will change too, but not 100% sure.
Also, what about Write Protection? Will that have anything to do with writing new software onto the phone and will block it?

Pellisco said:
Okay. Hopefully KNOX doesn't interfere with anything. I also noticed in download mode:
Product Name: SGH-I337M
Current Binary: Samsung Official
System Status: Custom
KNOX Kernel Lock: 0x0
KNOX Warranty Void: 0x0
CSB-CONFIG-LSB: 0x20
Write Protection: Enable
eMMC Burst Mode: Enabled
So which ones trip when I root it? I know that the 'Current Binary' will trip if I install a custom rom, but, what about the KNOX stuff? I know that the Warranty Void will then turn to '0x1' and I think the kernel lock will change too, but not 100% sure.
Also, what about Write Protection? Will that have anything to do with writing new software onto the phone and will block it?
Click to expand...
Click to collapse
You may want to look at the top of this page.... http://autoroot.chainfire.eu/ states CF-auto root will trip Knox warranty... if your rooting, you should install a custom recovery and do a nand backup before you do anything else root without backup can have some ill side effects if you mess around with your files/apps... ie delete something that is critical.... of coruse custom recovery trips something else too I forget what it was but I am sure it's been discussed a couple times throughout the forum.... all I can say is read lots.... most times someone can get you out of a jam but I prefer not to go there in the first place.. so I read before I do.... most here will tell you it's the best way.... pay close attention to those who have messed up... good indication of what not to do....

One other thing I noticed was that there are locked boot loaders on certain devices.
So I have been wondering, does the Rogers Samsung Galaxy S4 come with a locked boot loader? Cause if it does, and I try and root my phone, there is a high chance that it will brick the device.

Rooting my SGS4

Dear XDA,
I come from the HTC One forum and I've sold since I've had camera issues numberous of times.
I decided to switch to an SGS 4, currently on 4.4.2. I have the i9505xxufnb9 variant.
I have a question regarding root.
1. I do not have knox installed yet, should I install it or leave it as it be when using CF-auto root? I'm currently on 4.4.2.
2. Is CF auto root compatible with my variant?
3. What version of Odin should I be running? I guess this is the most important. I don't want a sketchy Odin.exe that comes pre-set up. It might have some setting on that erases something that is crucial for my device.
4. Is there some sort of bootloader unlock I need to do first? My device is unbranded GT9505 version with the above written variant.
5. How likely am I to brick my device? I mean I come from the HTC one forum which was fairly easy. Setup fastboot and unlocking the bootloader did the job.
6. I came to understand it WILL trigger knox, does it mean voided warranty here in the Netherlands?
7. I understand that SuperSU has an option to unroot at any given time. When I want to return to stock for say warranty purposes, Can I download triangleaway, run it, and then unroot using SU app?
Thank you so much for your time!!

No one?

Cf autoroot comes with correct odin, if you do not have Knox don't install it, (you automatically get it if you took an ota). And no bootloader unlock is needed almost all Samsung devices come with an unlocked bootloader, and the only way you'll brick your device is if you flash something not meant for your phone or if you have knox and try downgrading your firmware...
And if you do have knox, rooting will permanently flag your device as modified with no way of going back. If you don't have knox you can use triangle away to reset the flash counter.
Sent from my GT-I9505 using Tapatalk

aryehzev said:
Cf autoroot comes with correct odin, if you do not have Knox don't install it, (you automatically get it if you took an ota). And no bootloader unlock is needed almost all Samsung devices come with an unlocked bootloader, and the only way you'll brick your device is if you flash something not meant for your phone or if you have knox and try downgrading your firmware...
And if you do have knox, rooting will permanently flag your device as modified with no way of going back. If you don't have knox you can use triangle away to reset the flash counter.
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
I'll make sure to give you your thanks tomorrow . I also got alot of help from the ask everything thread, thank you!

[Q] Galaxy S4 VE (I9515) - Root, bootloader status and ROMs

Hello,
I've was forced to create a post about that because there is almost nothing of use that can be found about that phone in the internet.
I need to know how to check the bootloader status on this device so i can safely root it, and if there are any working ROMs. I've found out that it is possible to install 9505 roms on that phone, however the touch and other crucial features do not work while using them.
Cheers, Paweł.
Thanks in advance, i appreciate Your help!

Go into download mode and if you see Knox warranty void you have new bootloader.this has nothing hover to do with safe root or not.you can still however root the device.but counter will be tripped if flashing custom recovery and kernel.

LastStandingDroid said:
Go into download mode and if you see Knox warranty void you have new bootloader.this has nothing hover to do with safe root or not.you can still however root the device.but counter will be tripped if flashing custom recovery and kernel.
Click to expand...
Click to collapse
Oh thanks! :good: I will do so. But about that safe root. I wanted to use the CF Auto Root for that and it was said there that if the device has a locked bootloader it will brick if i'll try to unlock the root access.
Should i try another way to root my device or give it a try and see what happens if i'll root it using cf auto root. I know that almost none or all ways to root the device are not safe, but following some of them have higher chances of success than others that's what i meant by safe root.

Zebbro said:
Oh thanks! :good: I will do so. But about that safe root. I wanted to use the CF Auto Root for that and it was said there that if the device has a locked bootloader it will brick if i'll try to unlock the root access.
Should i try another way to root my device or give it a try and see what happens if i'll root it using cf auto root. I know that almost none or all ways to root the device are not safe, but following some of them have higher chances of success than others that's what i meant by safe root.
Click to expand...
Click to collapse
All the info, rooting recoveries, roms available so far for i9515
http://forum.xda-developers.com/galaxy-s4/general/i9515-value-edition-roms-development-t3002535

Zebbro said:
Oh thanks! :good: I will do so. But about that safe root. I wanted to use the CF Auto Root for that and it was said there that if the device has a locked bootloader it will brick if i'll try to unlock the root access.
Should i try another way to root my device or give it a try and see what happens if i'll root it using cf auto root. I know that almost none or all ways to root the device are not safe, but following some of them have higher chances of success than others that's what i meant by safe root.
Click to expand...
Click to collapse
I think you have misunderstood or misread.or users haven't understand that root is still possible. It isn't locked in any way. The bootloader still let's you flash custom kernels etc.
Rooting with cf root shouldn't and has never bricked your phone on newer recoveries. The bootloader isn't locked in the way of flashing in Odin you can still flash custom kernels and recoveries but it will trip the Knox counter.
However: tripping Knox will cause you being unable to use Knox apps from Samsung and might void your warranty.
Users have told different reports about them being tripped and got warranty and some haven't. I'm not sure if this lies in 3rd party repair centers repairing the phone even if it's tripped. I'm sure Samsung service center is against it.
I'd be 100% sure that my phone carrier would repair it no matter the status since it doesn't go trough Samsung service at first.
However to gain root you should try towelroot it's a one click apk and it won't trip Knox unless you flash a custom kernel or recovery.

Stock recovery?

OK, so I'm new to this ROM-flashing stuff, and would like to install TWRP on my S4. The problem is, Samsung runs these trade-up programs every so often, so I do eventually plan on restoring the S4 to its original recovery. I was able to find an article from 2013 about the S4's stock recovery, and it also provided a download link to the recovery, but my question is, since that was released was 4.3 JB was the newest version, will that be an issue if the device is running 5.0 Lollipop instead? Basically my question is: did the Lollipop/KitKat update come with a new version of the recovery mode that is required to run these versions? Or is the recovery never updated throughout a device's lifetime?

You should consider this first:
Flashing a custom recovery will trip Knox.
The question now is: Will Samsung accept the phone if Knox is 0x1?
As you may or may not know, Knox status 0x1 is permanent. So even if you return to a stock recovery, Knox will still be 0x1.

GDReaper said:
You should consider this first:
Flashing a custom recovery will trip Knox.
The question now is: Will Samsung accept the phone if Knox is 0x1?
As you may or may not know, Knox status 0x1 is permanent. So even if you return to a stock recovery, Knox will still be 0x1.
Click to expand...
Click to collapse
They're unlikely to check that part. They look at the device, call the secret code to test the mic, camera, display etc, and it's marked good to go. Heck, I highly doubt they'll even notice if I was running TWRP, but just to play it safe.