Database Users

[Q] [i9500] Burnt by 4.3 (Knox) - Can't root or downgrade - Options?

I am using the International GSM Galaxy s4 (i9500). I am one of the foolish people who rushed into 4.3 (the Russian ROM doing the rounds - I9500XXUEMJ5_I9500SEREMJ5_SER) without doing sufficient research. Initially it wouldn't even boot properly, and apps would keep crashing, but after a factory reset 4.3 is working okay. I knew that the device would get unrooted, but I didn't know Samsung had a giant turd hiding up its sleeve named Knox. Now in Odin Mode it shows "warranty bit" as "1" I have tried rooting, and everything seems to go as per plan, but it doesn't root it. When I boot the phone I get these annoying notifications - "SuperSu attempted to access system on your device without authorisation" and that the attempt was blocked blah blah blah.
Things I have tried:
I have tried rooting it using crossfire (CF-Auto-Root-ja3g-ja3gxx-gti9500), and everything goes smoothly. It downloads it in Odin mode and then goes to the red screen (recovery mode) where all the messages seem to be okay. It then boots up fine. Everything in dandy. But no root. SuperSU says "There is no SU binary installed, and Super SU cannot install it. This is a problem! If you just upgraded to Android 4.3, you need to manually re-root - consult the relevant forums for your device." The only thing I have found on forums / google is to try using the CF-Auto-Root file mentioned before).
I have tried flashing CWM and using the root option in the recovery mode menu. It says it's rooted and asks me to reboot. But same thing - no root.
Frustrated by this, I decided to go back to the way things are (If it ain't broke, don't fix it - stupid me!!!) I downloaded a 4.2.2 stock ROM firmware file which a lot of people online are recommending (INU-I9500XWUBMG5-20130726135330) but now when I try to flash it using Odin 3.9, it gives me a couple of error messages in the box in Odin and on the phone something like "Unsupported Version" comes and then it does nothing. I have to pull out the battery, and no progress.
While Knox is a horrible thing Samsung has done, it will probably not affect my day to day usage, so I am fine waiting for a solution to reset it if and when it ever comes and hope that I don't need to use the warranty or alternatively they don't enforce that stuff here in India (more out of ignorance than goodness of heart)). But not having root on my phone is very tough. Unfortunately I can't use many of my apps that require root (Titanium, Avast etc.) - and I don't see what business it is of Samsung if I want to use legit apps that require root in order to enhance my experience.
What are my options (if any )? I am open to using any other (stable) ROMs like cyanogenmod etc. if that provides a solution. Or do I just have to wait till the geniuses (crossfire etc.) figure it out?

Same problem here. I'm waiting for someone to fix it.

Seems like a lot of people around the world have the same problem as I do. I guess we will have to wait. Meantime, I guess I will try flashing the Indian firmware that just came out today (if only I had waited a day!). The Indian one seems to have Knox too, but I feel kind of like in the walking dead - we are all infected, and can't do **** about it.
I imagine whenever crossfire comes out with the root file for 4.3, it should be applicable for all region 4.3 firmwares?

no problem with root
This is interesting to me because i downloaded the mentioned 4.3 Russia rom and flashed it. After i flashed the cf auto root and now i have root. The only thing i have is i cant seem to install knox which it is saying your device is not authorised to enter knox mode. Not sure but i suspect it is because i have root. In download mode it says custom and warranty is 1.
sorry.. i forgot to mention i have the i-9500 international version.

solved!
I don't know, will it be working on update that installed by OTA, but i know that it works if you flashed update by ODIN. Now i have fully functional rooted russian 4.3 firmware.
First, you must know that this method will void your warranty, because it will activate warranty bit counter.
1. Flash the update and wipe data and cache.
2. Do not setting up your device.
3. Enter to downlod mode again, and flash the cofface recovery.
4. Enter to recovery and install the special Chainfire's supersu for 4.3 (look in attachment of this post.)
5. Reboot and setup your phone, but anyway DON'T TRY to use knox, and if you will see dialog window, where it is written about some protection - decline it every time as you see it!
6. Now, you need to stop knox services in application manager. Just stop all aplications that have "knox", and some agent that hase different name, but same icon.
7. Now you can use root, but you need to uninstall all knox services before reboot, because knox will be running again and block su binary. I used RootAppDelete.

megacrash said:
I don't know, will it be working on update that installed by OTA, but i know that it works if you flashed update by ODIN. Now i have fully functional rooted russian 4.3 firmware.
First, you must know that this method will void your warranty, because it will activate warranty bit counter.
1. Flash the update and wipe data and cache.
2. Do not setting up your device.
3. Enter to downlod mode again, and flash the cofface recovery.
4. Enter to recovery and install the special Chainfire's supersu for 4.3 (look in attachment of this post.)
5. Reboot and setup your phone, but anyway DON'T TRY to use knox, and if you will see dialog window, where it is written about some protection - decline it every time as you see it!
6. Now, you need to stop knox services in application manager. Just stop all aplications that have "knox", and some agent that hase different name, but same icon.
7. Now you can use root, but you need to uninstall all knox services before reboot, because knox will be running again and block su binary. I used RootAppDelete.
Click to expand...
Click to collapse
My friend your post is really helpful but there is a glitch knox is integrated in some system apps so when u try to remove system ui FC's so to stop knox interrupting freeze it with titanium backup cz when u freeze knox this will not crash ur system ui and u can use root even u restart your device purposely as many times you want

nickboy360 said:
My friend your post is really helpful but there is a glitch knox is integrated in some system apps so when u try to remove system ui FC's so to stop knox interrupting freeze it with titanium backup cz when u freeze knox this will not crash ur system ui and u can use root even u restart your device purposely as many times you want
Click to expand...
Click to collapse
still no luck bro ... I have removed all Knox related files through aroma file manager. installed root binary provided by you . installed auto root ... but still no luck
seems some problem with my phone
do I have to do factory reset ?

Yeah... I doubt that method would work. Plus after spending hours manually reinstalling apps and setting up accounts etc. I don't want to factory reset unless it's a sure thing. (Since I don't have root, I can't use Titanium Backup to restore my apps + data).
Is there any news on any method to root the i9500 on 4.3?
I flashed the Indian firmware, and it's working very well! (apart from the Knox b.s.)

4.2.2 downgrade from 4.3 Official Russian
Hi Friends,
I need your help.
I have upgraded to 4.3 Russian FW through ODIN. When i connected to KIES it says 'This device is not supported by KIES"
When i try Firmware upgrade and initialization, it says that it can restore to original firmware MG9. Somewhere here i have read that downgrade is not available. So if try will i brick my device. I would like to go back to original 4.2.2 and wait for official update for Africa as i am from Kenya.
Otherwise 4.3 is very fast and smooth and camera app is working very fast, better battery performance and no hanging.
I will appreciate any help. Thanks

pawandeep said:
still no luck bro ... I have removed all Knox related files through aroma file manager. installed root binary provided by you . installed auto root ... but still no luck
seems some problem with my phone
do I have to do factory reset ?
Click to expand...
Click to collapse
Mate i know there is a problem with 4.3 regarding the root i myself tried and failed to get it rooted search for the latest supersu1.60 zip on google flash with 6.0.4.4 cwm u will get ur device rooted but the warranty bits will increase ... and do not install knox if u do u will find knox counter below warranty bits .... the new boot loader with knox have a efuse kinda stuff so @Chanfire is having little trouble dealing with it...so if u have increased ur warranty bits try this link if it might help u http://forum.xda-developers.com/showthread.php?t=2317105
anyways i m currently sticking to stock mistakely updated to 4.3 now just waiting for some magician to give us a way out...
hope u get what u want and if it works give credits to the OP and just hit the thanks button if it helped...
---------- Post added at 01:10 AM ---------- Previous post was at 01:06 AM ----------
kpanand said:
Hi Friends,
I need your help.
I have upgraded to 4.3 Russian FW through ODIN. When i connected to KIES it says 'This device is not supported by KIES"
When i try Firmware upgrade and initialization, it says that it can restore to original firmware MG9. Somewhere here i have read that downgrade is not available. So if try will i brick my device. I would like to go back to original 4.2.2 and wait for official update for Africa as i am from Kenya.
Otherwise 4.3 is very fast and smooth and camera app is working very fast, better battery performance and no hanging.
I will appreciate any help. Thanks
Click to expand...
Click to collapse
Sir download kies 3 http://www.samsung.com/us/kies/#downloadWindows from here and ur device will be fully functional on 4.3
hit thanks if it helped
---------- Post added at 01:28 AM ---------- Previous post was at 01:10 AM ----------
kpanand said:
Hi Friends,
I need your help.
I have upgraded to 4.3 Russian FW through ODIN. When i connected to KIES it says 'This device is not supported by KIES"
When i try Firmware upgrade and initialization, it says that it can restore to original firmware MG9. Somewhere here i have read that downgrade is not available. So if try will i brick my device. I would like to go back to original 4.2.2 and wait for official update for Africa as i am from Kenya.
Otherwise 4.3 is very fast and smooth and camera app is working very fast, better battery performance and no hanging.
I will appreciate any help. Thanks
Click to expand...
Click to collapse
Sir Try KIES 3 its supports 4.3 andu will be able to use it

VebKr said:
I am using the International GSM Galaxy s4 (i9500). I am one of the foolish people who rushed into 4.3 (the Russian ROM doing the rounds - I9500XXUEMJ5_I9500SEREMJ5_SER) without doing sufficient research. Initially it wouldn't even boot properly, and apps would keep crashing, but after a factory reset 4.3 is working okay. I knew that the device would get unrooted, but I didn't know Samsung had a giant turd hiding up its sleeve named Knox. Now in Odin Mode it shows "warranty bit" as "1" I have tried rooting, and everything seems to go as per plan, but it doesn't root it. When I boot the phone I get these annoying notifications - "SuperSu attempted to access system on your device without authorisation" and that the attempt was blocked blah blah blah.
Things I have tried:
I have tried rooting it using crossfire (CF-Auto-Root-ja3g-ja3gxx-gti9500), and everything goes smoothly. It downloads it in Odin mode and then goes to the red screen (recovery mode) where all the messages seem to be okay. It then boots up fine. Everything in dandy. But no root. SuperSU says "There is no SU binary installed, and Super SU cannot install it. This is a problem! If you just upgraded to Android 4.3, you need to manually re-root - consult the relevant forums for your device." The only thing I have found on forums / google is to try using the CF-Auto-Root file mentioned before).
I have tried flashing CWM and using the root option in the recovery mode menu. It says it's rooted and asks me to reboot. But same thing - no root.
Frustrated by this, I decided to go back to the way things are (If it ain't broke, don't fix it - stupid me!!!) I downloaded a 4.2.2 stock ROM firmware file which a lot of people online are recommending (INU-I9500XWUBMG5-20130726135330) but now when I try to flash it using Odin 3.9, it gives me a couple of error messages in the box in Odin and on the phone something like "Unsupported Version" comes and then it does nothing. I have to pull out the battery, and no progress.
While Knox is a horrible thing Samsung has done, it will probably not affect my day to day usage, so I am fine waiting for a solution to reset it if and when it ever comes and hope that I don't need to use the warranty or alternatively they don't enforce that stuff here in India (more out of ignorance than goodness of heart)). But not having root on my phone is very tough. Unfortunately I can't use many of my apps that require root (Titanium, Avast etc.) - and I don't see what business it is of Samsung if I want to use legit apps that require root in order to enhance my experience.
What are my options (if any )? I am open to using any other (stable) ROMs like cyanogenmod etc. if that provides a solution. Or do I just have to wait till the geniuses (crossfire etc.) figure it out?
Click to expand...
Click to collapse
so sorry to hear that but dont worry ..there is always a solution ...what i did was i followed the instructions while INSTALLING WANAM V 3.0 from : http://wanamlite.com/2013/10/21/wanamlite-xxuemj5-v3-0-android-jb-4-3-xposed/ nd after that everything booted normally and i was having the warranty bit to 1 but it was working perfect and thn i there was an annoying message everytime i opened SUPERSU or some rooted apps...the root was working perfect ..knox was not doing anything to it ..just showing the SECURITY INFORMATION that the app is stopped but in real it wasnt ..so i disabled it by installing TERMINAL EMULATOR from playstore and thn opened it and typed the following :
SU (Enter)
pm disable com.sec.knox.seandroid (Enter)
and its gone ...give it a try and tell me if ur problem is solved ...good luck

i got lucky that i dint upgrade 4.3

ll_r1d0_ll said:
so sorry to hear that but dont worry ..there is always a solution ...what i did was i followed the instructions while INSTALLING WANAM V 3.0 from : http://wanamlite.com/2013/10/21/wanamlite-xxuemj5-v3-0-android-jb-4-3-xposed/ nd after that everything booted normally and i was having the warranty bit to 1 but it was working perfect and thn i there was an annoying message everytime i opened SUPERSU or some rooted apps...the root was working perfect ..knox was not doing anything to it ..just showing the SECURITY INFORMATION that the app is stopped but in real it wasnt ..so i disabled it by installing TERMINAL EMULATOR from playstore and thn opened it and typed the following :
SU (Enter)
pm disable com.sec.knox.seandroid (Enter)
and its gone ...give it a try and tell me if ur problem is solved ...good luck
Click to expand...
Click to collapse
Wouldn't uninstalling Knox completely get rid of the issues as well? Check the steps here: http://www.samsung.com/us/support/howtoguide/N0000005/13093/159642

@ll_r1d0_ll
Thanks a lot man, it really worked, although I have I9500UBUEMJ5, now I have 4.3 and root, thanks.

ll_r1d0_ll said:
so sorry to hear that but dont worry ..there is always a solution ...what i did was i followed the instructions while INSTALLING WANAM V 3.0 from : http://wanamlite.com/2013/10/21/wanamlite-xxuemj5-v3-0-android-jb-4-3-xposed/ nd after that everything booted normally and i was having the warranty bit to 1 but it was working perfect and thn i there was an annoying message everytime i opened SUPERSU or some rooted apps...the root was working perfect ..knox was not doing anything to it ..just showing the SECURITY INFORMATION that the app is stopped but in real it wasnt ..so i disabled it by installing TERMINAL EMULATOR from playstore and thn opened it and typed the following :
SU (Enter)
pm disable com.sec.knox.seandroid (Enter)
and its gone ...give it a try and tell me if ur problem is solved ...good luck
Click to expand...
Click to collapse
Mate i cannot find wanam 3.0 for i9500... this procedure is basically for i9505 when is the ETA for i9500 wanam 4.3 @wanam i know ur working hard on i9500, is there anyway where we can reset warranty bits
Sent from my GT-I9500 using XDA Premium 4 mobile app
---------- Post added at 12:40 AM ---------- Previous post was at 12:37 AM ----------
nickboy360 said:
Mate i cannot find wanam 3.0 for i9500... this procedure is basically for i9505 when is the ETA for i9500 wanam 4.3 @wanam i know ur working hard on i9500, is there anyway where we can reset warranty bits
Sent from my GT-I9500 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sorry i dint checked it throughly ... but y cant i see an updated version in the forum but its on wanam website... :what::what:
Sent from my GT-I9500 using XDA Premium 4 mobile app

dmunera said:
@ll_r1d0_ll
Thanks a lot man, it really worked, although I have I9500UBUEMJ5, now I have 4.3 and root, thanks.
Click to expand...
Click to collapse
ur always welcome
---------- Post added at 12:12 PM ---------- Previous post was at 12:10 PM ----------
nickboy360 said:
Mate i cannot find wanam 3.0 for i9500... this procedure is basically for i9505 when is the ETA for i9500 wanam 4.3 @wanam i know ur working hard on i9500, is there anyway where we can reset warranty bits
Sent from my GT-I9500 using XDA Premium 4 mobile app
---------- Post added at 12:40 AM ---------- Previous post was at 12:37 AM ----------
Sorry i dint checked it throughly ... but y cant i see an updated version in the forum but its on wanam website... :what::what:
Sent from my GT-I9500 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
if u have checked the link i gave u above inside it..it is written that " Welcome to WanamLite Rom for Galaxy S4 I9500" ..I have flashed this rom o my GT I9500 and its working like a charm and it have no idea how to reset the warranty bits and i personally dont care about my warranty
---------- Post added at 12:17 PM ---------- Previous post was at 12:12 PM ----------
ali87 said:
Wouldn't uninstalling Knox completely get rid of the issues as well? Check the steps here: http://www.samsung.com/us/support/howtoguide/N0000005/13093/159642
Click to expand...
Click to collapse
well it depends on your choice i followed the steps given by CHAINFIRE in the I9505 forum

@ll_r1d0_ll mate thanks alot for ur feedback about the rom and when is @indie and @tamirda is releasing their roms beacuse personally i never tried wanam on my previous i9300 n7000 and n7100 ... so if i flash wanamlite v3.1 any problem or bugs till date???
Sent from my GT-I9500 using XDA Premium 4 mobile app

nickboy360 said:
@ll_r1d0_ll mate thanks alot for ur feedback about the rom and when is @indie and @tamirda is releasing their roms beacuse personally i never tried wanam on my previous i9300 n7000 and n7100 ... so if i flash wanamlite v3.1 any problem or bugs till date???
Sent from my GT-I9500 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
i literally have no idea that when they are going to release 4.3 version of their roms :/ ... i was alsoo waiting for their roms but i thought i should give wanam's rom a try and i have found that its great and widout any problem .....i am currently using v3.1 i didnt find any issue i just flashed it over 3.0 and its working perfect !

ASK
VebKr said:
Spoiler: VebKr
I am using the International GSM Galaxy s4 (i9500). I am one of the foolish people who rushed into 4.3 (the Russian ROM doing the rounds - I9500XXUEMJ5_I9500SEREMJ5_SER) without doing sufficient research. Initially it wouldn't even boot properly, and apps would keep crashing, but after a factory reset 4.3 is working okay. I knew that the device would get unrooted, but I didn't know Samsung had a giant turd hiding up its sleeve named Knox. Now in Odin Mode it shows "warranty bit" as "1" I have tried rooting, and everything seems to go as per plan, but it doesn't root it. When I boot the phone I get these annoying notifications - "SuperSu attempted to access system on your device without authorisation" and that the attempt was blocked blah blah blah.
Things I have tried:
I have tried rooting it using crossfire (CF-Auto-Root-ja3g-ja3gxx-gti9500), and everything goes smoothly. It downloads it in Odin mode and then goes to the red screen (recovery mode) where all the messages seem to be okay. It then boots up fine. Everything in dandy. But no root. SuperSU says "There is no SU binary installed, and Super SU cannot install it. This is a problem! If you just upgraded to Android 4.3, you need to manually re-root - consult the relevant forums for your device." The only thing I have found on forums / google is to try using the CF-Auto-Root file mentioned before).
I have tried flashing CWM and using the root option in the recovery mode menu. It says it's rooted and asks me to reboot. But same thing - no root.
Frustrated by this, I decided to go back to the way things are (If it ain't broke, don't fix it - stupid me!!!) I downloaded a 4.2.2 stock ROM firmware file which a lot of people online are recommending (INU-I9500XWUBMG5-20130726135330) but now when I try to flash it using Odin 3.9, it gives me a couple of error messages in the box in Odin and on the phone something like "Unsupported Version" comes and then it does nothing. I have to pull out the battery, and no progress.
While Knox is a horrible thing Samsung has done, it will probably not affect my day to day usage, so I am fine waiting for a solution to reset it if and when it ever comes and hope that I don't need to use the warranty or alternatively they don't enforce that stuff here in India (more out of ignorance than goodness of heart)). But not having root on my phone is very tough. Unfortunately I can't use many of my apps that require root (Titanium, Avast etc.) - and I don't see what business it is of Samsung if I want to use legit apps that require root in order to enhance my experience.
What are my options (if any )? I am open to using any other (stable) ROMs like cyanogenmod etc. if that provides a solution. Or do I just have to wait till the geniuses (crossfire etc.) figure it out?
Click to expand...
Click to collapse
Hi @VebKr, seems like I did same with you, , and now my warranty bit has became 1 already, and I couldn't turn it back to 0, I've searched how to do it, but I couldn't find it. And now, I don't know what to say, but seems like I lost my warranty because of that, I've just bought this phone last month actually. Is there anyone who able to make it back?

engineer24 said:
Hi @VebKr, seems like I did same with you, , and now my warranty bit has became 1 already, and I couldn't turn it back to 0, I've searched how to do it, but I couldn't find it. And now, I don't know what to say, but seems like I lost my warranty because of that, I've just bought this phone last month actually. Is there anyone who able to make it back?
Click to expand...
Click to collapse
Mate you should have read the whole post before flashing the rom frankly now there is nothing you can do as i and @ll_r1d0_ll were discussing about the same so you should have waited for little more time before flashing the wanamlite 3.1 i got a new myself a new s4 so now the old one is having wanamlite which is tremendous i just loved it but still having a second thought on updating my new s4 to custom .. will wait for some time for some of the magician here on xda will turn the wheel, so we might get lucky.

[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

How to Root 4.3 with build MK6

help! please. I am look to root my samsung galaxy S4 Running android 4.3 with the build MK6.
PLEASE HELP?
Thank you

Use this method : http://forum.xda-developers.com/showthread.php?t=2293800

DaveRazr said:
Use this method : http://forum.xda-developers.com/showthread.php?t=2293800
Click to expand...
Click to collapse
Anything that will actually allow the install of a custom recovery?

arrush said:
Anything that will actually allow the install of a custom recovery?
Click to expand...
Click to collapse
There's no "true" custom recovery for phones running MF3 or above. MF3 phones can run Safestrap. MDB/MDL phones still have the ability to boot into a true custom recovery using loki.

Questions and Help issues go in Q&A and Help section
Thread moved
Thanks
FNSM

Mk6 can run cwm and twrp. Rogers unit isnt the same as att bud, happy flashing
Sent from my SGH-I337M
---------- Post added at 12:13 PM ---------- Previous post was at 12:09 PM ----------
jeboo said:
There's no "true" custom recovery for phones running MF3 or above. MF3 phones can run Safestrap. MDB/MDL phones still have the ability to boot into a true custom recovery using loki.
Click to expand...
Click to collapse
This is not the case at all. Mk6 is rogers / canaduan variant, and the bootloader is not locked. Root with cf auto root, and flash cwm or twrp via normal methods. You will trip knox counter, but you can run any recovery u like. MF3 is locked bootloader , mk6 is not.
Sent from my SGH-I337M

azuziel said:
Mk6 can run cwm and twrp. Rogers unit isnt the same as att bud, happy flashing
Sent from my SGH-I337M
---------- Post added at 12:13 PM ---------- Previous post was at 12:09 PM ----------
This is not the case at all. Mk6 is rogers / canaduan variant, and the bootloader is not locked. Root with cf auto root, and flash cwm or twrp via normal methods. You will trip knox counter, but you can run any recovery u like. MF3 is locked bootloader , mk6 is not.
Sent from my SGH-I337M
Click to expand...
Click to collapse
Oops, didn't even realize it was i337m...:silly:

I used kingo app. One touch root. Knox safe. I verified the vroot iemi crap is all removed in new version. After your reboot, update supersu binary via normal method, cancel any knox popups, and choose not to allow supersu to disable knox. Use titanium backup and guides found here to freeze all knox stuff. Then busybox, xposed as normal. Dont install custom recovery if you want to keep knox 0x0. If you dont care, then install cwm/twrp as per normal
Sent from my SGH-I337M

I deleted Knox completely from my phone as well as all the AT&T Bloatware. My phone is better without it.

azuziel said:
I used kingo app. One touch root. Knox safe. I verified the vroot iemi crap is all removed in new version. After your reboot, update supersu binary via normal method, cancel any knox popups, and choose not to allow supersu to disable knox. Use titanium backup and guides found here to freeze all knox stuff. Then busybox, xposed as normal. Dont install custom recovery if you want to keep knox 0x0. If you dont care, then install cwm/twrp as per normal
Sent from my SGH-I337M
Click to expand...
Click to collapse
Thanks a lot for that Kingo App, worked perfectly! I did get that Knox pop-up on 4.3 and I clicked view apps just to check it out.
2 Questions:
Anyways, how do you update supersu binary? There's no option or menu to do so and I didn't get a pop-up.
How do you choose not to allow supersu to disable Knox?
Thanks for the tip about not installing a custom recovery

azuziel said:
I used kingo app. One touch root. Knox safe. I verified the vroot iemi crap is all removed in new version. After your reboot, update supersu binary via normal method, cancel any knox popups, and choose not to allow supersu to disable knox. Use titanium backup and guides found here to freeze all knox stuff. Then busybox, xposed as normal. Dont install custom recovery if you want to keep knox 0x0. If you dont care, then install cwm/twrp as per normal
Sent from my SGH-I337M
Click to expand...
Click to collapse
Do you know if this was resolved then? http://forum.xda-developers.com/showthread.php?t=2460745&page=8 there was more going on behind the scenes than I would like to have.....
http://forum.xda-developers.com/showthread.php?t=2460745&page=8

Ramsey said:
Thanks a lot for that Kingo App, worked perfectly! I did get that Knox pop-up on 4.3 and I clicked view apps just to check it out.
2 Questions:
Anyways, how do you update supersu binary? There's no option or menu to do so and I didn't get a pop-up.
How do you choose not to allow supersu to disable Knox?
Thanks for the tip about not installing a custom recovery
Click to expand...
Click to collapse
regarding knox. It is safe to allow supersu to disable knox, i avoided it thinking it may trip bc wasn't sure how it went about freezing it. I tested, had supersu disable knox, rebooted, good to go.
Did an identical handset today, and failed to root. Did some poking and found out that kies3 appears to interfere with kingo, so uninstall temporarily when running kingo if you have issues.
Once supersu disabkes knox, you can then update the binaries via normal method. Also if kingo gets to the part where it asks about using odin method, say no, or it'll trip knox.unplug, reattach and try again. Had to do it thrice for an i377m i did today.
Heres what i did:
1 - connect usb to phone, and enable developer mode, then be sure to allow the dev prompt to always accept usb from this machine, phone will prompt to allow
2 - click root. Shouldn't get to odin question, id it does, dont allow odin method, restart the process.
3 - on successful root, you will see supersu install, grant it root, and allow it to disable knox.
4 update supersu binariez via normal method (don't need to use cwm/twrp on i377m only), it will prompt, until knox disabled, u wont be able to update binaries
5 - install busybox installer
I havent installed supersu as system app yet, i imagine its also safe to do so.
6 - check knox in download mode and ensure 0x0 for *both* knox codes
7- installed xposed and some modulez, greenify in particular, and enabled, recheck knox, still 0x0
Both phones i did with this method, once kies was removed, rooted BEFORE i had to install any camera exploits, or any other crap from play. If you habe trouble, reload samsung drivers, try another cable (i had a failure using a blackberry usb cable, switched to packaged smasung usb, worked fine), anothet usb, and even another computer. Old pc's with usb 1.1 wont work (well), usb 2/3 does work just fine.
Avoid clockworkmod, twrp, safesteap etc (or any other custom recovery) if you want to keep your warranty. If you dont care, then twrp/cwm work just fine, they will blow the knox efuse tho and set you 0x1. I work in IT and happen to know knox will work with exchange 2015 upon release. It will also screw up new versions of active sync, as your system isn't able meet the security requirements (having knox intact and not blown) of the organizations' corporate knox policies. Look for a bes like sys admin tool that expands on the remote wipe /lockz/ camera images etc, in the coming months. Exchange 2015 is still a ways away, but since you cant undo a blown efuse with any software, understand implications of blowing knox fully, not just warranty. And if you use exchange email, or plan to, keep knox untripped is best advice.
Gage_Hero said:
Do you know if this was resolved then? http://forum.xda-developers.com/showthread.php?t=2460745&page=8 there was more going on behind the scenes than I would like to have.....
http://forum.xda-developers.com/showthread.php?t=2460745&page=8
Click to expand...
Click to collapse
Yes. Ok, kingo is just an interface for all known exploits. The emei sniffing was actually being performed by vroot. Kingo was simply running existing vroot code. I talked to kingo support last week, who assured me that emei check was pulled during latest release, the vroot method is still present, however iz modified to remove those bad lines. When you run kingo, it opens a connection to kingo server to pull each exploit/patch as one method fails, pulls another, then another, as needed. This keeps package small, and allows for on the fly repo updatez on their end without having to re-release a package.
Kingo does not record emei at all any longer, it was vroot doing it, and kingo bc they simply ran vroot method without editing.
So you will see kingo go online to grab each exploit as required, in the new version, but no emei tracking any longer.
Besides the trojan that was used before in vroot, is picked up by avg free, so youd know if it were still doing it. I ran tcpview and tcpdump while flashing root to my device and didnt see any connections to china, any longer.
This can be verified on both odficial Facebook and Twitter account of kingo. Their intention is to at one point to charge a couple bucks for this app, having it exhibit malicious behaviour is bad for business. Youll notice vroot has no support or contact methods. Kingo does.
Sent from my SGH-I337M

Thanks, btw I can't seem to software update after I rooted my phone. It says my software was modified. Does anyone know how I can get it to check for updates? I'm already on 4.3 but I know our S4 will get 4.4 in a few months.
I am still good with Knox, I am at 0x0 for both lines.
Btw, I did freeze Knox in titanium, but not uninstall, just freeze. I did freeze many other apps but nothing dangerous, just normal ones like Travel, google movies, magazines, etc..

Ki Hi
Ramsey said:
Thanks, btw I can't seem to software update after I rooted my phone. It says my software was modified. Does anyone know how I can get it to check for updates? I'm already on 4.3 but I know our S4 will get 4.4 in a few months.
I am still good with Knox, I am at 0x0 for both lines.
Btw, I did freeze Knox in titanium, but not uninstall, just freeze. I did freeze many other apps but nothing dangerous, just normal ones like Travel, google movies, magazines, etc..
Click to expand...
Click to collapse
You cannot update ota when system is modified, there is an xposed module that changes modified to official tho. Not sure if it trips knox, likely. When updates come, unroot, apply, reroot. There are other guides that can be found here to update keepinng root with odin, you'll have to use the search provided.
Feezing with Titanium backup is fine. Supersu doesnt delete knox, it disables knox notifications. The whole point here is not tripping knox. That's why supersu asks if you want to disable knox, and not delete it, bc only disables, knox services still present. Feezing with tb is same result. Just supsrsu is free, tb is paid (for freezing anyway), though if youre on these forums, should be using tb anyway , titanium backup, greenify donation, and tasker are 3 must have root apps. Tasker is great. I use it to auto enable bluetooth and wifi based on gps location, or driving in the car. Lots of youtube vids on tasker if you areny familiat with it.
Sent from my SGH-I337M

There is an alternative to vroot and kingo methods. I was able to root mj6. I saw mk2 rooted as well successfully.
http://forum.xda-developers.com/showthread.php?t=2565758

If it helps any 4.3 MK6 users, I rooted using the download from this site and can confirm that it works:
http://forum.xda-developers.com/showthread.php?t=2565758

ravi_mytouch said:
There is an alternative to vroot and kingo methods. I was able to root mj6. I saw mk2 rooted as well successfully.
http://forum.xda-developers.com/showthread.php?t=2565758
Click to expand...
Click to collapse
Yep it does. Ive used it on a few i377m already. Wasn't available when i did mine. Kingo is relatively safe, latest release is, cant speak for previous or future versions. Kingo is just an interface that uses all known root methods (including vroot, and this method). Just keeps trying dif method til one works. Had this been available, would have used for mine. But it wasn't so setup a segregated lab at work, to test kingo and reports of malware. I didnt see any at that time via tcp dump and tcpview, however that could change since they just rip off other root methods/code to reuse, kingo does i mean. That said if you rooted with kingo, no need to repeat. Root is root (well, full root is full root), and no daemons u dont recognize running.
Sent from my SGH-I337M

Root without tripping knox?

Note 3
AP: N9005XXUBMJ3
CP: N9005XXUBMJ2
CSC: N9005OXXBMJ3
Is there a solution to root it without tripping knox?
Big thx.

lion_sta said:
Note 3
AP: N9005XXUBMJ3
CP: N9005XXUBMJ2
CSC: N9005OXXBMJ3
Is there a solution to root it without tripping knox?
Big thx.
Click to expand...
Click to collapse
The general response around is that there is none (yet).
IMHO it might be interesting if you also connect you phone with USB-debugging mode activated and then you do from a command-line
adb shell
and then
getprop ro.boot.bootloader
If you are not familiar with adb (or you do not have adb and the USB-debugging stuff) but you have a terminal emulator installed on the phone (which you can do from the play store even if you are not rooted) you can try that last command directly in the terminal on the phone.
If the result is something like N9005XXUBMI7 then you can use URDLV.
If not and you are very determined to root at the risk of the knox status we might try some other solutions.

xclub_101 said:
.
Click to expand...
Click to collapse
Did it, and this is what I get.
[email protected]:/ $ adb shell
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
error: device not found
1|[email protected]:/ $ getprop ro.boot.bootloader
N9005XXUBMJ3
[email protected]:/ $
Does this mean that if I were to root I am certainly loosing warranty?
Or people are not 100% sure?

lion_sta said:
Did it, and this is what I get.
[email protected]:/ $ adb shell
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
error: device not found
1|[email protected]:/ $ getprop ro.boot.bootloader
N9005XXUBMJ3
[email protected]:/ $
Does this mean that if I were to root I am certainly loosing warranty?
Or people are not 100% sure?
Click to expand...
Click to collapse
MJ3 bootloader does not let you install any previous ROM/bootloader and MJ3 and later stock ROMs are known to no longer work with URDLV.
I have expressed here:
http://forum.xda-developers.com/showthread.php?t=2642207
the idea that just rooting should be possible without triggering knox, but my Note 3 is already successfully rooted using URDLV with knox 0x0 so for the moment I do not plan in making more tests on this part.
That being said if there are users that are decided to root even at the risk of triggering their knox status I think it might be very interesting to do such tests with a better plan instead of just jumping on CF-root or similar.

OK, I am willing to take some risks, especially since you say that it is ”possible”.
Let me explain why I need the rooting maybe you can advise.
I am region locked without the possibility of going to that region and speaking the 5 mins.
I have read and learned that using the regionlock away tool would remove the loc even after unrooting.
So this is my plan, just root, use the tool, unroot.
What do you think?

lion_sta said:
OK, I am willing to take some risks, especially since you say that it is ”possible”.
Let me explain why I need the rooting maybe you can advise.
I am region locked without the possibility of going to that region and speaking the 5 mins.
I have read and learned that using the regionlock away tool would remove the loc even after unrooting.
So this is my plan, just root, use the tool, unroot.
What do you think?
Click to expand...
Click to collapse
1. If you want people to know that you answered then you should quote them - that way they get a notification
2. Are you only region-lock or also network-locked? Surprisingly if you are network-locked it will be much "knox-safer" (but it will cost in the area of 10-15 EUR or so).
3. Do you have kind of hope for any kind of Samsung warranty?
4. Extra advice "just in case" - disable right now both system updates and security updates.

xclub_101 said:
1. If you want people to know that you answered then you should quote them - that way they get a notification
2. Are you only region-lock or also network-locked? Surprisingly if you are network-locked it will be much "knox-safer" (but it will cost in the area of 10-15 EUR or so).
3. Do you have kind of hope for any kind of Samsung warranty?
4. Extra advice "just in case" - disable right now both system updates and security updates.
Click to expand...
Click to collapse
1. Sorry bout that, been on a forum where it was kindda forbiden.
2. Unfortunately only region locked, tho not 100 % sure.
3. Don't we all? For as long as it is at least "possible"
4. Well, I don't think it is possible. I get this bugging notification every day to install. Have not seen an option to disable.

lion_sta said:
1. Sorry bout that, been on a forum where it was kindda forbiden.
2. Unfortunately only region locked, tho not 100 % sure.
3. Don't we all? For as long as it is at least "possible"
4. Well, I don't think it is possible. I get this bugging notification every day to install. Have not seen an option to disable.
Click to expand...
Click to collapse
2. If you place inside a different SIM (than the network for which is locked) and it directly asks for unlock code it is network-locked. If not it might only be region-locked.
3. As far as I understand Samsung warranties are only offered at best inside the same region for which the lock is present - so if the phone is from UK at best you can hope in a warranty inside EU - but I would not hope too much, most often you also need a warranty certificate filled by an AUTHORIZED Samsung seller; next-best would be some warranty in the same country, but very, very often the warranty comes from the seller himself and there is no other warranty
4. The ROM OTA update should ask you for a country and ask if you agree with the terms, if you say that you do not agree then it should not bother you again. The "security updates" is for a separate setting - in General - Security - "Auto update security". Disable that and get rid of the OTA updates first!
5. Check your precise current kernel version (that is just to clarify where you are) - if it was build after (I believe) October-December 2013 or so you must wipe everything and reinstall the original MJ3 ROM.
6. Then you need to check this thread
http://forum.xda-developers.com/showthread.php?t=2565758
note that from some point on Samsung kernels have fixed that method, this is discussed starting in this post:
http://forum.xda-developers.com/showthread.php?p=48749875#post48749875

xclub_101 said:
2. If you place inside a different SIM (than the network for which is locked) and it directly asks for unlock code it is network-locked. If not it might only be region-locked.
3. As far as I understand Samsung warranties are only offered at best inside the same region for which the lock is present - so if the phone is from UK at best you can hope in a warranty inside EU - but I would not hope too much, most often you also need a warranty certificate filled by an AUTHORIZED Samsung seller; next-best would be some warranty in the same country, but very, very often the warranty comes from the seller himself and there is no other warranty
4. The ROM OTA update should ask you for a country and ask if you agree with the terms, if you say that you do not agree then it should not bother you again. The "security updates" is for a separate setting - in General - Security - "Auto update security". Disable that and get rid of the OTA updates first!
5. Check your precise current kernel version (that is just to clarify where you are) - if it was build after (I believe) October-December 2013 or so you must wipe everything and reinstall the original MJ3 ROM.
6. Then you need to check this thread
http://forum.xda-developers.com/showthread.php?t=2565758
note that from some point on Samsung kernels have fixed that method, this is discussed starting in this post:
http://forum.xda-developers.com/showthread.php?p=48749875#post48749875
Click to expand...
Click to collapse
Before doing the other points please tell me what you think about the point 5 -
2. We should continue as if it was only region locked, because when I bought it it was specified that it was carrier free
3. I am in Moldova, and my sister is in Romania - where the phone is from, close but not close enough it seems.
4. Done
5. Check image
6. In the first thread there, in the list of succesfully rooted devices is not present the Note 3. You are not the only one to have pointed me in that direction. But still want to make sure that it will work on Note 3.

lion_sta said:
Before doing the other points please tell me what you think about the point 5 -
2. We should continue as if it was only region locked, because when I bought it it was specified that it was carrier free
3. I am in Moldova, and my sister is in Romania - where the phone is from, close but not close enough it seems.
4. Done
5. Check image
6. In the first thread there, in the list of succesfully rooted devices is not present the Note 3. You are not the only one to have pointed me in that direction. But still want to make sure that it will work on Note 3.
Click to expand...
Click to collapse
3. Then it makes some sense to keep Knox 0x0 (but be extra-careful with the water, in my experience in many countries Samsung official service dismisses 90% of the claims based on the internal water detectors (plenty of them).
5. IMHO you have a good chance to have saferoot still working. Saferoot from the thread I mentioned above is nice since if it fails it just fails to root but it does not set knox 0x1. Even if it fails as it is now (there is a very small chance that the fix was not in the kernel and you still got it before you disabled the security updates) it might still be worth to wipe everything and then write original MJ3 ROM and try again (this time certainly without any updates, without even connecting the phone on the net).
If you manage to root with MJ3 and keep knox 0x0 IMHO it might be worth to keep the root (and hide it with Wanam xposed) then eventually to go to MJ7 or so (with Mobile Odin Pro). Again - strictly IMHO - 4.4.2 is not yet worth it.

xclub_101 said:
3. Then it makes some sense to keep Knox 0x0 (but be extra-careful with the water, in my experience in many countries Samsung official service dismisses 90% of the claims based on the internal water detectors (plenty of them).
5. IMHO you have a good chance to have saferoot still working. Saferoot from the thread I mentioned above is nice since if it fails it just fails to root but it does not set knox 0x1. Even if it fails as it is now (there is a very small chance that the fix was not in the kernel and you still got it before you disabled the security updates) it might still be worth to wipe everything and then write original MJ3 ROM and try again (this time certainly without any updates, without even connecting the phone on the net).
If you manage to root with MJ3 and keep knox 0x0 IMHO it might be worth to keep the root (and hide it with Wanam xposed) then eventually to go to MJ7 or so (with Mobile Odin Pro). Again - strictly IMHO - 4.4.2 is not yet worth it.
Click to expand...
Click to collapse
3 - thx for the advice.
5. No luck. Now for the next step, how do I wipe and what are the risks? Also how do I find the original MJ3 ROM?

lion_sta said:
3 - thx for the advice.
5. No luck. Now for the next step, how do I wipe and what are the risks? Also how do I find the original MJ3 ROM?
Click to expand...
Click to collapse
A simple wipe is the easy part - you just factory-reset or go in recovery and do a (full) wipe (all data in the phone will be lost). The more complex part would be to find the original ROM - I would guess it could be on a page like this:
http://www.sammobile.com/firmwares/1/?model=SM-N9005&pcode=ROM#firmware
EDIT:
And before going to Odin be 100% certain that you disabled reactivation lock if you ever enabled it. And Odin mode is always involving some risk, read a little around before jumping into it.

lion_sta said:
Note 3
AP: N9005XXUBMJ3
CP: N9005XXUBMJ2
CSC: N9005OXXBMJ3
Is there a solution to root it without tripping knox?
Big thx.
Click to expand...
Click to collapse
Yes. I used Kingo root app for mine, and preserved Knox 0x0. Google it.

shayind4 said:
Yes. I used Kingo root app for mine, and preserved Knox 0x0. Google it.
Click to expand...
Click to collapse
Not working for me, asks to install custom rom.

So, something weird just happened. Did the thing with Kingo root at home, and it told me that my device could not bee rooted without tripping knox.
Drivers - Kies, That app that is telling that an app had to stop because ... - apparently running.
Same app, installed the drivers from Kingo, on its own. I stopped the app ”hat is telling that an app had to stop because ...” but it still appeared during the process.
Result - Succes, I am rooted. Big thx to you all.

lion_sta said:
So, something weird just happened. Did the thing with Kingo root at home, and it told me that my device could not bee rooted without tripping knox.
Drivers - Kies, That app that is telling that an app had to stop because ... - apparently running.
Same app, installed the drivers from Kingo, on its own. I stopped the app ”hat is telling that an app had to stop because ...” but it still appeared during the process.
Result - Succes, I am rooted. Big thx to you all.
Click to expand...
Click to collapse
Did it void the knox status?

buntoo said:
Did it void the knox status?
Click to expand...
Click to collapse
No. BTW it worked with the 1.1.8 while at home I was trying with 1.2.0.
Still, the main reason why I rooted was to get the RegionLock Away and it is not working. Bummer.

lion_sta said:
No. BTW it worked with the 1.1.8 while at home I was trying with 1.2.0.
Still, the main reason why I rooted was to get the RegionLock Away and it is not working. Bummer.
Click to expand...
Click to collapse
unfortunately it doesn't work for the exynos (SM-900)

buntoo said:
unfortunately it doesn't work for the exynos (SM-900)
Click to expand...
Click to collapse
I missread what you said. Was too self centered.

does kingo works on exynos running 4.3?
Sent from my SM-N900 using XDA Premium 4 mobile app

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!