Need help with rooting Rogers Galaxy S4 I337M - AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin

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.

Related

[Q] Do I have Knox or not?

So I have a problem guys, I'm going to tell you all the long story, I just recently bought a S4 from Telcel in México, LTE edition, the model is SGH-I337M, and came with build I337MUMUAMG1, 4.2.2.
I was anxious to tinker with it, so first thing I did as soon as I came home was rooting it with CF-Auto-Root, everything until that point was smooth sailing, but I couldn't make the I337M version of Philz Touch Recovery to flash via Odin, so I flashed the GT-i9505 version and IT WORKED, it booted to recovery normally, rebooted to system, etc. So I thought "oh boy, I'm ready to go". But before that, I read that for data & Wi-Fi to work properly in 4.3 Custom Roms I had to flash the 4.3 modem.bin file via Odin, so I did that. No OTA, no 4.3 Stock Rom, only the modem-bin file. The modem version never changed in the "About Device" tab to "I337MVLUEMK6" like it was supposed to do, it stayed as "I337MUMAMB2" but I also read that was normal so I didn't think about it much.
After that I went into recovery with my ready-to-flash files in my SD, wipe my system/data/cache/etc without making a Backup because that's how retarded I am and try to flash my ROM only to get it aborted every time due to "assert failed: getprop("ro.product.device") == "jfltecan" ||" issues, so I assumed it had to do with me using the GT-i9505 version of Philz Touch with a I337M Canadian Custom ROM. I shat bricks for a while because I had wiped my system and I had no backup, so I just turned my phone off, downloaded the "I337MUMUAMG1" Telcel Stock Rom, turned on my phone in Download Mode and flashed it via Odin while I prayed.
It worked, it booted, everything was alright with the world again (but not so much on my pants where tons of bricks were shat), I had voided my warranty but whatever, I was gonna Root and Triangle Away that thing to make my phone fully stock again, so I get ready to do exactly that, get my phone into Download Mode, and Root it with CF-Auto-Root, again, it worked, it booted, and had the SuperSU icon, smooth sailing again, OR SO I THOUGHT.
I open SuperSU to update dem binaries and a pop-up emerges saying that Samsung Knox had been detected and if I want to attempt to disable it. Oh boy, I was not ready for this, I hadn't recovered from the last shatbricking session, and now my pants were a national disaster area. Anyway, I also read that using Triangle Away with a Knox enabled phone was a highway to a very expensive paperweight, so thankfully I was smart enough to don't try it.
As I kept shatting bricks I decide to reflash the Stock "I337MUMUAMG1" Telcel Rom via Odin to keep my phone as safe and near stock as possible, everything worked, and now I'm running the "I337MUMUAMG1" build, with no root, stock, with yellow triangle and apparently, Knox. :crying:
I got curious about it, so I went into Download Mode to search for the Knox Warranty Void Flag... But I didn't got it, neither the Warranty Bit. On Download Mode I get only the Usual:
ODIN MODE
PRODUCT NAME: SGH-I337M
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: OFFICIAL
USB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
And I don't have any Knox apps on my drawer, but they appear on the "Application Manager -> All" menu, so I'm confused as hell, and since I can't check my Bootloader version I can't know if I have Knox on my bootloader or only on my Rom. And I'm way to scared to try anything, and also scared about OTAs and updates since I don't know the state of my phone. Any help on this?
tl;dr: Got brand new SGH-I337M with I337MUMUAMG1 as Stock. Rooted, Flashed Philz Touch for GT-i9505, Flashed 4.3 modem.bin only, Tried to flash Custom Rom, messed up, Flashed Stock I337MUMUAMG1 again, Rooted, got Knox popup upon opening SuperSU for the first time, shat bricks, Flashed Stock I337MUMUAMG1 again to be as stock as posible. If I boot into download mode I don't get Knox Warranty Void Flag in the Download Mode, don't have Knox apps on my App Drawer but I see them on the Application Manager -> All. Too scared to try anything until I know if I have Knox enabled on my Bootloader or only Knox Apps on my Rom.
Any help with this will be greatly appreciated, many thanks in advance, and thanks for reading.
EDIT: FORGOT ABOUT SOMETHING. After Flashing Stock I337MUMUAMG1 For the second time after getting the Knox warning popup on SuperSU, I got an OTA, couldn't cancel it but I don't know if it changed anything, since my build number was it was I337MUMUAMG1 still, it was a 250mb file.
sounds like you have knox yes. As to why it doesnt show in download mode, I can only speculate that when you flashed back to 4.2.2 the recovery was replaced with a pre-knox variant. If you're seeing knox in app manager>all as you mentioned, then you have knox yep. I have the same, just a shortcut, then knox crap in app manager> all.
Interestingly, I came from gummy 1.1, with root and CWM recovery. However since i was rooted, i couldnt obtain the 4.3 update OTA. So, I downloaded the 4.3 stock, flashed with odin (auto-reboot/f reset selected) and my knox shows 0x0. Granted I don't have root, but my main reason for this was battery life, which sucked balls on 4.2.2 rogers variant. 4.3 rogers variant is MUCH improved. I'm actually getting better life out of the stock fw, then i was with gummy 1.1. I hear all these horror stories, but I have yet to have a single app crash on 4.3 stock (i do miss xposed tho)
I haven't' re-flashed and tripped KNOX because it isn't just some security crap samsung threw on to stop custom recoveries/kernel's etc. It's actually Samsungs corporate solution for BYOD policies. The whole reason it blows the fuse, isnt just to stop warranties either, it's to communicate with exchange/corporate policies and let exchange/network know that your device is secure and following corporate policies. We all know android and linux are one in the same, adding this now gives samsung the ability to sell a managment suite (like BES in blackberry world) that uses knox for remote wipes/locks/factory reset/anti-theft. granted these exist already, but in a basic state. Look for these to be expanded on shortly.
If you blow your efuse, and use active sync , your going to be up **** creek shortly. I'm going to wait until this is defeated. Yes Knox is a hardware based efuse (the flag), but make no mistake, it is software solution and thus can be exploited. Patience is key here, imho. Just wait until the knox based sys admin tool is released for admins. anyone with a tripped flag is going to have a problem (if in business world). Sorry if I ran on a bit there, but yes, it sure seems you have knox and you should treat the device as though you do.
oh and the new SSO functionality is provided by knox, so if you can't use it, no single sign on for you i'm afraid.
http://www.samsung.com/global/business/mobile/solution/security/samsung-knox
Certain KNOX elements are present in 4.2.2 builds, however, the entire KNOX implementation (Kernel and KNOX suite) are only on 4.3 builds. More than likely, the version of SuperSU you are using detected that those certain KNOX apks (from 4.2.2) are on your phone and reported the "Samsung KNOX has been detected..." message.
scott14719 said:
Certain KNOX elements are present in 4.2.2 builds, however, the entire KNOX implementation (Kernel and KNOX suite) are only on 4.3 builds. More than likely, the version of SuperSU you are using detected that those certain KNOX apks (from 4.2.2) are on your phone and reported the "Samsung KNOX has been detected..." message.
Click to expand...
Click to collapse
So that means there is no Knox in my boot loader so I can reset my triangle counter to be as stock as possible to keep my warranty?
Aelyus said:
So that means there is no Knox in my boot loader so I can reset my triangle counter to be as stock as possible to keep my warranty?
Click to expand...
Click to collapse
I have no idea about resetting the triangle counter. I've never needed to do it, so I can't help you there.
Guys, I have a question related to this.
I have I9195L (Latin version of S4 mini) and I have read about knox software which may cause issues to rom flashers like me (I used to have S Advance and tried many roms until it died)
When I enter into flash mode, I noticed that there was no knox flag at all (like the ones I saw on some other users shots), so my question is, do
Do I have that knox crap or not?
I do realized that I have some knox software installed, like knox store (I didnt touched anything of this just in case).
Can I safely try other ROMs, including Cyanogen mod?
I have rooted using the safe method posted somewhere around here in the forums.
BTW: I have stock rom... for the moment...
Please let me know.
Thank you in advance.
Aelyus said:
So that means there is no Knox in my boot loader so I can reset my triangle counter to be as stock as possible to keep my warranty?
Click to expand...
Click to collapse
Yes. However, the best way to keep knox untripped to return for warranty is to simply flash the stock fw via odin. Poof, root gone, and check the f reset flag to reset the flash counter safely. You also have same scenario I did. I was running gummy 1.1 (back in nov) when 4.3 ota was released, so I flashed 4.3 via odin and knox is still 0x0. Kingo will root 4.3 and keep knox at 0x0, it did for my i377m and a coworkers as well. You can use wanam to fake official and keep ota updates for the upcoming kitkat update. Just be prepared to flash it via odin, as nobody really knows how supersu in survival mode will react to the 4.4.2 update ota. Only stipulation is you CANNOT run a custom recovery without tripping knox, or a custom rom. So I simply use xposed + wanam and customize the TW firmware that way. I have root, I have my warranty, and I can rip out any bloat I care to. HTH.
Guys, cyanogen does trip Knox and Odin does not trip Knox?
Enviado desde mi GT-I9195L mediante Tapatalk
cenovita said:
Guys, cyanogen does trip Knox and Odin does not trip Knox?
Enviado desde mi GT-I9195L mediante Tapatalk
Click to expand...
Click to collapse
Cyanogen trips knox yes. Odin will not, provided you arent attempting to downgrade to say, 4.2.2 from 4.3. Once on a knox "infected" bootloader, cant downgrade without knox tripping.
Sent from my SGH-I337M
azuziel said:
Cyanogen trips knox yes. Odin will not, provided you arent attempting to downgrade to say, 4.2.2 from 4.3. Once on a knox "infected" bootloader, cant downgrade without knox tripping.
Sent from my SGH-I337M
Click to expand...
Click to collapse
Thank you very much for your response.
Final question, if I don't have Knox in my loader (I don't see the flag in Odin mode) I can install cyanogen and go back to stock (4.2.2) if I want to and the guaranty should be fine, right?
Enviado desde mi GT-I9195L mediante Tapatalk
cenovita said:
Thank you very much for your response.
Final question, if I don't have Knox in my loader (I don't see the flag in Odin mode) I can install cyanogen and go back to stock (4.2.2) if I want to and the guaranty should be fine, right?
Enviado desde mi GT-I9195L mediante Tapatalk
Click to expand...
Click to collapse
Provided you dont see any knox lines while in download mode, or odin mode, yes.
Sent from my SGH-I337M
azuziel said:
Provided you dont see any knox lines while in download mode, or odin mode, yes.
Sent from my SGH-I337M
Click to expand...
Click to collapse
Nope, no lines related to Knox in download mode.
Thank you!
Enviado desde mi GT-I9195L mediante Tapatalk

[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

Please Help Guys

Hi Guys,
I'm basically knox free im on 4.2.2, can anyone give me
a: a brief guide to easiest way of rooting and installing a recovery i.e TW or CWM, hopefully one click solution?
b: If I go onto 4.4 kitkat will I have to have a knox bootloader even with a custom rom?, if so is 4.4 worth it?.
c: &
d:Mod Edit removed due to asking for best ROM ( not allowed on xda)
At the moment main thing I want to do is safely root and install recovery without triggering knox as I want the chance to install custom roms and not void my warranty as I can always use triangle away at a later date.
BTW have done a lot of reading but want to be 100% sure and would really like some experienced advice.
Many thanks
Mav
a) Use Saferoot -> HERE
b) TWRP -> All info HERE
c) and d) Try it by yourself. Read the rules of XDA too :highfive:
Thanks
but a few things, will rooting cause the knox to come on?, as im confused also how do i know if my bootloader is locked or not?, if it does make the bootloader custom can I change it back?.
Thanks
Mod Edit
You may continue with this thread , but please do not ask for best ROMS.
Saferoot , AFAIK , does not trip knox flag
malybru
Forum Moderator
maverick7777 said:
Thanks
but a few things, will rooting cause the knox to come on?, as im confused also how do i know if my bootloader is locked or not?, if it does make the bootloader custom can I change it back?.
Thanks
Click to expand...
Click to collapse
If you have an old bootloader you won't even have KNOX on it, lucky you.
If you have the new bootloader, it comes with KNOX.
You can check if you have a new or old bootloader by putting your phone in Download mode (Volume down + Home + Power buttons).
If the the top left corner is syas stuff like "KNOX warenty" etc. you have the new one.
Rooting using saferoot as mentioned earlier will not trigger KNOX anyways.
Installing a custom Recovery as well as installing a custom ROM will trigger KNOX (if you indeed have the new bootloader with KNOX offcourse).

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.

Categories

Resources