Develop Bugs

[Q] Note 3 KitKat Knox 0x0 root here?

Found this German page just off of Google with what appears to have a guide on rooting kitkat without voiding knox...
http://www.mobtivity.com/de/news/galaxy-note-3-update-auf-android-kitkat-mit-root-und-knox-0x0.html
I posted the link in another thread as well, but figure a new thread will give it some more attention.
Not sure if this would even work on the T-Mobile note 3.
I've never personally rooted before, but planning to once a knox friendly method has been confirmed for KitKat!

Interesting. Going to have to look into the original No-Knox Trip thread too.

SUCCESS! 4.4.2 KitKat Rooted with Knox 0x0!
Success! Followed the German guide in the link and now I have 4.4.2 KitKat Rooted with Knox 0x0! Below is the bootloader file that I created and used.
Dreamgun said:
Found this German page just off of Google with what appears to have a guide on rooting kitkat without voiding knox...
http://www.mobtivity.com/de/news/galaxy-note-3-update-auf-android-kitkat-mit-root-und-knox-0x0.html
I posted the link in another thread as well, but figure a new thread will give it some more attention.
Not sure if this would even work on the T-Mobile note 3.
I've never personally rooted before, but planning to once a knox friendly method has been confirmed for KitKat!
Click to expand...
Click to collapse

joetzzz said:
Success! Followed the German guide in the link and now I have 4.4.2 KitKat Rooted with Knox 0x0! Below is the bootloader file that I created and used.
Click to expand...
Click to collapse
Awesome stuff haha. I wonder how this roots without voiding knox

I wonder if there were more successes?

joetzzz said:
Success! Followed the German guide in the link and now I have 4.4.2 KitKat Rooted with Knox 0x0! Below is the bootloader file that I created and used.
Click to expand...
Click to collapse
Could you post us a picture of your phone with the proof....seeing is believing.

joetzzz said:
Success! Followed the German guide in the link and now I have 4.4.2 KitKat Rooted with Knox 0x0! Below is the bootloader file that I created and used.
Click to expand...
Click to collapse
So you followed every step and just used the bootloader file you uploaded instead of theirs and you are now rooted with KNOX 0x0? Not that I dont believe you, but can you show a screen shot of this please?

My words are my proof, my friend. It's too much trouble for me right now to have to take picture of the Download mode screen. Sorry.
Muffycheeks said:
Could you post us a picture
of your phone with the proof....seeing is believing.
Click to expand...
Click to collapse

Dreamgun said:
Found this German page just off of Google with what appears to have a guide on rooting kitkat without voiding knox...
http://www.mobtivity.com/de/news/galaxy-note-3-update-auf-android-kitkat-mit-root-und-knox-0x0.html
I posted the link in another thread as well, but figure a new thread will give it some more attention.
Not sure if this would even work on the T-Mobile note 3.
I've never personally rooted before, but planning to once a knox friendly method has been confirmed for KitKat!
Click to expand...
Click to collapse
THIS IS T-Mobile Note 3 Forum, why are saying: "Not sure if this would even work on the T-Mobile note 3" ???
wrong forum...

Yes. Just follow the steps. The trickiest part is the extracting bootloader. I had to open the command prompt, go to the folder, and run the batch file, instead of running it directly from Windows explorer. That's why I posted the file here for others to benefit.
droidkevlar said:
So you followed every step and just used the bootloader file you uploaded instead of theirs and you are now rooted with KNOX 0x0? Not that I dont believe you, but can you show a screen shot of this please?
Click to expand...
Click to collapse
---------- Post added at 03:48 PM ---------- Previous post was at 03:37 PM ----------
I confirm that it works on my T-Mobile Note 3 SM-N900T.
belozeroff said:
THIS IS T-Mobile Note 3 Forum, why are saying: "Not sure if this would even work on the T-Mobile note 3" ???
wrong forum...
Click to expand...
Click to collapse

Just to clarify
This method has been used for some time here... http://forum.xda-developers.com/showthread.php?t=2522729&page=69
Also, this is not a 4.4 root method, rather it takes advantage of root while on 4.3 (ex. Root de la vega). So if you already installed the 4.4 bootloader, you have to wait for something else to come along.
You use mobile odin pro (which requires you already have root) to flash the 4.4 ROM while injecting root into it, however mobile odin pro never touches the bootloader and so if you stop there, you can't boot back into your phone. It's a soft brick. You need to update to the 4.4 bootloader using Odin on the desktop after using MOP to flash the ROM.
I tried this the day the update came out and got stuck on the booting recovery screen after I flashed my own 4.4 extracted bootloader. I was forced to Odin to the complete 4.4 and I am stuck with no root unless I auto-cf and lose knox.

effortless said:
This method has been used for some time here... http://forum.xda-developers.com/showthread.php?t=2522729&page=69
Also, this is not a 4.4 root method, rather it takes advantage of root while on 4.3 (ex. Root de la vega). So if you already installed the 4.4 bootloader, you have to wait for something else to come along.
You use mobile odin pro (which requires you already have root) to flash the 4.4 ROM while injecting root into it, however mobile odin pro never touches the bootloader and so if you stop there, you can't boot back into your phone. It's a soft brick. You need to update to the 4.4 bootloader using Odin on the desktop after using MOP to flash the ROM.
I tried this the day the update came out and got stuck on the booting recovery screen after I flashed my own 4.4 extracted bootloader. I was forced to Odin to the complete 4.4 and I am stuck with no root unless I auto-cf and lose knox.
Click to expand...
Click to collapse
So what your saying is, this doesnt work like the person before you said, correct?

I think my bootloader file wasn't created right. This should technically work if the bootloader is correct. It's for preserving a rooted 4.3 to 4.4, not rooting 4.4.
Sent from my SM-N900T using Tapatalk

What's the best and easiest way to to create a bootloader file? I need one for different version of note 3. Any issues since using this method? Like spen or force closes or anything?
Sent from my SM-N900R4 using Tapatalk

The tool in the German guide is supposed to be able to create a bootloader from any rom, given you have the md5 file from Sammobile. Use Google translate if you can't read German.
droidhead36 said:
What's the best and easiest way to to create a bootloader file? I need one for different version of note 3. Any issues since using this method? Like spen or force closes or anything?
Sent from my SM-N900R4 using Tapatalk
Click to expand...
Click to collapse

Ok it works. Pretty easy instruction. Knox still 0x0. But I had to spend $4.99 to buy Mobile Odin Pro.

Things are getting a little confusing... I think this needs an english guide with requirements that people can follow and understand. Q_Q

Dreamgun said:
Things are getting a little confusing... I think this needs an english guide with requirements that people can follow and understand. Q_Q
Click to expand...
Click to collapse
Agreed. Someone that has done this, can you make a quick guide on how to do this exactly coming from 4.3?

I followed the guide and got to 4.4 with root access and KNOX is still on 0x0.
1. I got the initial root on 4.3 with root_de_la_vega and used regionaway to unlock the device as I am currently using my N900T with ATT.
2. Followed all the steps to create the bootloader file after getting the stock firmware for 4.4.
3. Followed the instructions as described on the page using google translater via chrome.
4. After applying the firmware using mobile odin pro...the device gets stuck at recovery booting.
5. Took off the battery for a few and then finally made it to download mode.
6. Tried to use the BL option, but the version of ODIN I had didn't provide an option to choose the BL.
7. Download the ODIN from the instruction page and that provided the option to load the BL i created using the method.
8. Finally the device booted, and I still have root access with KNOW 0x0 and running on 4.4 as well.
Let me know if you need the bootloader file I created and I shall upload the same.
Hope this helps.

Confirmed working; did this yesterday following the instructions, step by step like on the website mentioned; started from 4.3 rooted with Root de la Vega 0x0 Knox flag, unpacked tar.md5 file, created bootloader with the script provided, flashed firmware from Mobile Odin (need to be careful to select after flash option to download mode before you click flash now), then flashed the bootloader I've created using the Odin version provided in the link; everything went smooth, no softbricks, got to keep all my apps and settings, now my phone is running 4.4.2 and is rooted with the Knox flag untouched, 0x0. Only issue I've seen so far is that my default email application keeps FC-ing, can't use it.

help to root my SM-P605

hello
i know that there is many threads asking the best way to root SM-P605
but i found that it can triger my knox so here is my tablet info. so any one can sujest me the best way to root my tablet without triger knox
AP: P605XXUBMJA
CP: P605XXUBMJ4
CSC: P605OJVBMK1
THANKS,

There is no way to root p605 without trigering knox.

crissx said:
There is no way to root p605 without trigering knox.
Click to expand...
Click to collapse
what is the problem if knox trigred
only warranty
if it is no problem
but can i update my tablet manually if any update come ?

Yes, only warranty problem. And you can update manually. I have a p605, rooted, knox 0x1, i really don't care about waranty . Root is good.

so universal RDLV or CF auto root is suitable for me
which is better

mohands said:
so universal RDLV or CF auto root is suitable for me
which is better
Click to expand...
Click to collapse
CF-autoroot is easier, just flash with PC ODIN. Just make sure it is for the P605(Quallcom) and not the P600/601(Exynos). Different CPU's means a working tab or a brick...

ultramag69 said:
CF-autoroot is easier, just flash with PC ODIN. Just make sure it is for the P605(Quallcom) and not the P600/601(Exynos). Different CPU's means a working tab or a brick...
Click to expand...
Click to collapse
thanks alot finished

mohands said:
thanks alot finished
Click to expand...
Click to collapse
Just in time for Kitkat to be released and it's a whole different ballgame....
If you do upgrade, I found it easiest to Flash Kitkat with PC ODIN, let it boot. (If you have a bootloop or screen hangs, reflash stock JB rom on without root as the KK bootloader hasn't been flashed).
Flash the cf-Autoroot for the SM-P905 (you'll need to do a search) - let boot..Go to phone and enter *#2263# and update the wacom drivers. It may take a little while to access the menu.
Flash this tar for normal P605 recovery - http://forum.xda-developers.com/attachment.php?attachmentid=2776284&d=1401701658
Flash Twrp 2.7.0.1 found at post #772 on this thread - http://forum.xda-developers.com/showthread.php?t=2515656&page=78
You now have a rooted Note 10.1 2014 on Kitkat with TWRP recovery. (if your sd card ios formatted exFAT you won't be able to save the backups to the external sd card but Fat32 seems to work).
This was how I did it, whether you need to use the P905 autoroot is needed or not is up to you, you might be able to cut out a heap by just flashing TWRP 2.7.0.1 and allowing it to insert root, didn't work for me but I had already rooted with P905 root..
Happy flashing...

[Q] rooting SGH-T999 with Skipsoft

I've read as much as I can and I just need a little more help. I want to be able to root my T-Mobile Galaxy S3, SGH-T999.
1. Is there any other way to pull files from /data/data without rooting?
2. Can I just do a simple root and then later root with CWM or TWRP using another option?
3. I thought rooted was rooted, what is the need for "insecure boot"? Is that the only way to get a file image backup of my partitions?
4. None of the rooting options in the Skipsoft Android Toolkit wipe the device, correct?
5. Is the only way to be able to "recover" back to stock by installing a "custom recovery"?
All of the options include "custom recovery". What if I just want to root the device and install a custom recovery later? Or it custom recovery included in all the options so I can get back to stock if I mess up? Thanks!

I am not sure why you'd need to go to such extent.
By your question on Insecure Kernel, I assume, you have Stock 4.3 update. If so, please flash SuperSU Zip via Custom Recovery. You can Also flash Root66 of 4.3 (UVUEMJC ) to get Root as well. None of these methods are destructive and make you loose your data.
As to your other questions, /data/data should be accessible read only to Good File explorers such as ES File Explorer. My Backup Pro should be able to backup those files too. Insecure boot is needed to root as SELINUX Enforcing will not let you have Stable Root. Best Flash ATT Insecure Kernel Posted on this sub forum. I don't understand what you mean by "Recover to Stock".

can't do anything without root
I tried ES File explorer and 2 others, they show /data/data as blank. Most everywhere I've looked says you have to have root

In that case please post your Current Android version and what you see under Baseband. What step we take next depends on this information.

rooting galaxy
perseus71 said:
in that case please post your current android version and what you see under baseband. What step we take next depends on this information.
Click to expand...
Click to collapse
4.3, t999uvuenc2

fdecker said:
4.3, t999uvuenc2
Click to expand...
Click to collapse
Root 66 Will not work you will need Auto Root, CWM/TWRP and Update SuperSU for a complete root.
CF-Auto-Root-d2tmo-d2tmo-sght999.tar
openrecovery-twrp-2.7.0.0-d2tmo
UPDATE-SuperSU-v1.93
DE-SAMSUNGNIZER_KNOX_REMOVAL_SCRIPT_V1.0
For a suceed root and Knox remove.

Thanks!
jmberumenb said:
Root 66 Will not work you will need Auto Root, CWM/TWRP and Update SuperSU for a complete root.
CF-Auto-Root-d2tmo-d2tmo-sght999.tar
openrecovery-twrp-2.7.0.0-d2tmo
UPDATE-SuperSU-v1.93
DE-SAMSUNGNIZER_KNOX_REMOVAL_SCRIPT_V1.0
For a suceed root and Knox remove.
Click to expand...
Click to collapse
Thanks, this is great. I rooted the same model phone that was on OS 4.1.2 by uploading root66 with Odin and it worked in one step. I see now that root66 is not the way to go on the 4.3 phone just yet. I will follow your tips. I see too that I have to get rid of Knox and make sure the recovery partition does not get reset. Think I should put busybox out there too, or with TWRP and SuperSU do I have all I need?
Thank you very much for your help!

fdecker said:
Thanks, this is great. I rooted the same model phone that was on OS 4.1.2 by uploading root66 with Odin and it worked in one step. I see now that root66 is not the way to go on the 4.3 phone just yet. I will follow your tips. I see too that I have to get rid of Knox and make sure the recovery partition does not get reset. Think I should put busybox out there too, or with TWRP and SuperSU do I have all I need?
Thank you very much for your help!
Click to expand...
Click to collapse
I used the TWRP and SuperSU method no problems so far.

TWRP and SuperSU
jmberumenb said:
I used the TWRP and SuperSU method no problems so far.
Click to expand...
Click to collapse
I'll give that a try then.

busybox?
One last question: Would you load busybox as well?

fdecker said:
One last question: Would you load busybox as well?
Click to expand...
Click to collapse
Nah I wouldn't unless its required by your Rom or something.

[GUIDE] how to root Sph-L710/L710T S3 4.4.2 (updated as of 8/19/2015)

I'm sorry i had the wrong links and because of this i had miss information. So i formally apologize by updating with the proper links.
this first method doesn't work with the Sph-L710T or the Sph-L710 on NJ2/NJ3
First method: You can root the stock 4.4.2 ND8/NDC:laugh:
1st. Make sure your on 4.4.2 ND8 or NDC
2nd. Download Towel Root
3rd. Place Towel Root in sdcard or internal storage
4th. With any file manager find and install Towel Root
5th. Open Towel Root and well root
6th. Go to play store and download https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=en and also https://play.google.com/store/apps/details?id=stericson.busybox&hl=en let super user update the binary
7th. Flash any recovery you want {personally i went with PhilZ Touch (this was before PhilZ had a root Option)}
8th. Enjoy your rooted stock 4.4.2 ND8/NDC
Down below is one more way too root Stock ND8/NDC/NJ2/NJ3 or NF4/OA3 (L710T) and basically any other update
(link to the almighty ODIN)
Second Method: mostly recommended
1st. Odin flash TWRP
2nd. In Odin choose PDA, PA or AP then select the TWRP Tar you just downloaded
3rd. Make sure Auto reboot is unchecked (also at this time your s3 should be in download mode)
4th. Hit start and let Odin let it finish!!
5th. Hold power button to turn off your S3, after it turns off about 10 seconds later it will turn back on to the battery charging screen so before that quickly hold Volume+ and Home, to boot into recovery
6th. now your in TWRP
7th. so to root your stock rom with TWRP flash the following file SuperSU.zip by Chain fire (pro tip. Install any other custom recovery the same way I did for TWRP above if it is in .tar format)
and here is Philz recovery for the D2Lte 6.48.4 ( which you must flash in TWRP)
and here is TWRP that was made specifically for the D2Rephersher/triband/L710T TWRP (which you must flash in a recovery)
Third method Most recent.
Hidyman said:
This is in reference to Samsung Galaxy S3 for Boost Mobile SPH-L710.
Just want to let anyone out there that updated their Boost S3 to L710VPUC0J1 know that you can still root and/or ROM your phone.
Use the instructions to (use Odin to) update the recovery to TWRP first (in the second set of instructions). I had trouble trying to go right to PhilZ Recovery (which I believe is based off of ClockWorkMod). I Had to do the TWRP (twrp-2.8.7.0-d2spr.img.tar) first.
It was the only way to get it to actually accept the recovery, not sure why, maybe because the latest Samsung firmware fixed an exploit or two.
This is an older phone, but it is still a viable one.
I hope this helps someone out there.
It took me a while to figure this quandary out.
As always this WILL flag KNOX, but I'm sure this won't be an issue at this date and time (8/2016).
Click to expand...
Click to collapse

work on ND8 rom? sprint phone?

Tekone said:
work on ND8 rom? sprint phone?
Click to expand...
Click to collapse
i want to say yes but towel root does come with a warning that it might brick your device.....but i want to say yes since most things that can be done to the ND8 can be done to the NDC and also in reverse order.....so try it and report back it will be good to know if it works on both bootloaders

Sprint S3 Android 4.4.2 ND8-It works!
I just used this method to root my Sprint S3 running Android 4.4.2 and ND8, since my USB port is on the fritz, and it worked successfully. I have root, and was able to do a full apps backup with Titanium Backup, and gained root access in ES File Explorer. Next, download and install a custom backup. Thanks, great job, and could not have been made easier to do!

oops
Rooted the phone in one click. Unfortunately, I lost all data (no 3G or 4G connection). Did I goof? I'm looking in the stickies and can't seem to find an answer. I'd appreciate any help I can get.

henhun said:
Rooted the phone in one click. Unfortunately, I lost all data (no 3G or 4G connection). Did I goof? I'm looking in the stickies and can't seem to find an answer. I'd appreciate any help I can get.
Click to expand...
Click to collapse
ND8 or NDC? have you tried updating your profile/PRL?

6th_Hokage said:
ND8 or NDC? have you tried updating your profile/PRL?
Click to expand...
Click to collapse
Ya know. People keep talking about ND8 and ND___. I have no idea what that means. I know I should be embarrassed.
UPDATE: FIGURED IT OUT, BASEBAND VERSION. GOTCHA. IT IS NDC.
I was JUST coming back to update my post. I DID update the PRL and restarted my phone. That seems to have done the trick. Thank GOD I got my data connection back!! It worked. Even though I found the info somewhere else, thank you so much for the quick reply. PRL update fixes the problem. You're awesome.

I used it before i had a custom recovery. And on reboot i wouldnt have root. After i ran it root checker told me i was rooted then reboot killed. I installed philz and all was ok
Sent from my SPH-L710 using XDA Free mobile app

jbnorton0524 said:
I used it before i had a custom recovery. And on reboot i wouldnt have root. After i ran it root checker told me i was rooted then reboot killed. I installed philz and all was ok
Sent from my SPH-L710 using XDA Free mobile app
Click to expand...
Click to collapse
many users of basically the same phone report different things with every root method out there. If it worked for you that's great tell other users what you did for it to work and if it didn't work, then ask for help and you will get help; some people don't have success with any method while others do with all of the methods.....my phone falls under every method.....

Successful Towelroot on VM Galaxy S3 4.4.2.NDC
6th_Hokage said:
you can root the stock 4.4.2
first step make sure your on 4.4.2
second step download Towel Root
third step place Towel Root in sdcard or internal storage
fourth step with any file manager find and install Towel Root
fifth step root
sixth step go to play store and download Superuser (Chainfire) and also Busy Box (Stericson) let super user update the binary
seventh step flash any recovery you want personally i went with Philliz Touch
eighth step if you want flash a custom rom now if not enjoy your rooted stock 4.4.2
Click to expand...
Click to collapse
Straight forward, fast and easy. I did notice the following:
1) Updating binary reported it did not successfully install. I've seen this before on other devices, but everything worked well. Ext SD and Camera all OK. Everything works fine so far - Titanium, Nandroid, Root Browser, etc.
2) At one point, I was directed to install Busy Box. Having done this on other devices, I said "Yes" and installed it.
3) I see that my device now shows Device Status as Custom ( was Normal before, if I remember correctly). Is this due to Busy Box?
4) Is Device Status the only way to know the KNOX Status? I see no yellow triangle as I did on my Galaxy Reverb.
5) I got a Google warning to uninstall Towelroot since it is usafe and a security exploit. I understand that.
I would like to verify the KNOX status and if tripped in the Towelroot process, to let potential users know of that possibility.
Thank You! And thanks to everyone who has continued to work on keeping root free!
Dave

dave260 said:
Straight forward, fast and easy. I did notice the following:
1) Updating binary reported it did not successfully install. I've seen this before on other devices, but everything worked well. Ext SD and Camera all OK. Everything works fine so far - Titanium, Nandroid, Root Browser, etc.
2) At one point, I was directed to install Busy Box. Having done this on other devices, I said "Yes" and installed it.
3) I see that my device now shows Device Status as Custom ( was Normal before, if I remember correctly). Is this due to Busy Box?
4) Is Device Status the only way to know the KNOX Status? I see no yellow triangle as I did on my Galaxy Reverb.
5) I got a Google warning to uninstall Towelroot since it is unsafe and a security exploit. I understand that.
I would like to verify the KNOX status and if tripped in the Towelroot process, to let potential users know of that possibility.
Thank You! And thanks to everyone who has continued to work on keeping root free!
Dave
Click to expand...
Click to collapse
Knox only notifies Samsung that your device isn't stock anymore not necessarily rooted like with a custom recovery and then flashed mods and what not but if you Odin the stock rom it resets the counters so Samsung will never know....and that i have noticed TowelRoot doesn't trip that counter.....only the recoveries and when you update the binary (<---completely forgot to fix that) you must hit the option normal not TWRP/CWM

churninern said:
I just used this method to root my Sprint S3 running Android 4.4.2 and ND8, since my USB port is on the fritz, and it worked successfully. I have root, and was able to do a full apps backup with Titanium Backup, and gained root access in ES File Explorer. Next, download and install a custom backup. Thanks, great job, and could not have been made easier to do!
Click to expand...
Click to collapse
That's great news because same boat here. It worked on 4.3 as well.
I had the phone hacked before and something must not be fully stock so the Ota fails.
I downloaded a package and mobile odin should flash it properly and then I can root it with this again and install a nice modified TouchWiz rom.

Darkangels6sic6 said:
That's great news because same boat here. It worked on 4.3 as well.
I had the phone hacked before and something must not be fully stock so the Ota fails.
I downloaded a package and mobile odin should flash it properly and then I can root it with this again and install a nice modified TouchWiz rom.
Click to expand...
Click to collapse
just a quick add on Mobile Odin and stock ND8/NDC don't mix at all

Knox Counter and "Device Status"
6th_Hokage said:
Knox only notifies Samsung that your device isn't stock anymore not necessarily rooted like with a custom recovery and then flashed mods and what not but if you Odin the stock rom it resets the counters so Samsung will never know....and that i have noticed TowelRoot doesn't trip that counter.....only the recoveries and when you update the recovery you must hit the option normal not TWRP/CWM
Click to expand...
Click to collapse
Thanks for your response. I may be over thinking these indicators. All I did was Towelroot, successfully. On the phone, the "About Device, Status" now says CUSTOM (was "Official"). The Knox counter according to app "Phone Info" shows Knox Counter at 0x0. As you said, since the counter is not tripped, should be no problem on warranty. So then Device Status CUSTOM is not a problem? I'm not really worried about warranty at this point, but I think I'll hold off further mods for another 6 moths.
Thanks again for your help!

6th_Hokage said:
just a quick add on Mobile Odin and stock ND8/NDC don't mix at all
Click to expand...
Click to collapse
Thanks. I tried the md8 and mk3 "mk3 is what it's on". Both just restart and get stuck on splash screen :/.
I have to go to download mode and and restart it that way to boot system back up.
Do you have any other suggestion. I'm not sure what part of the system is altered. It seems like a stock recovery and it's stock firmware "now rooted". Maybe the kernel.
I can't use USB at all.
I'm guessing maybe I should install twrp. Then install a stock zip or try out a 4.3 rom that way. I would like to get to md8 one way or another. Most md8 Roms want you to odin or flash an md8 base.

Darkangels6sic6 said:
Thanks. I tried the ND8 and MK3 "MK3 is what it's on". Both just restart and get stuck on splash screen :/.
I have to go to download mode and and restart it that way to boot system back up.
Do you have any other suggestion. I'm not sure what part of the system is altered. It seems like a stock recovery and it's stock firmware "now rooted". Maybe the kernel.
I can't use USB at all
I'm guessing maybe I should install TWRP. Then install a stock zip or try out a 4.3 rom that way. I would like to get to md8 one way or another. Most ND8 Roms want you to Odin or flash an md8 base.
Click to expand...
Click to collapse
cause they need the ND8 base to work as intended...my suggestion would be to get the usb port on your phone fixed but i don't know how expensive that will be

6th_Hokage said:
just a quick add on Mobile Odin and stock ND8/NDC don't mix at all
Click to expand...
Click to collapse
6th_Hokage said:
cause they need the ND8 base to work as intended...my suggestion would be to get the usb port on your phone fixed but i don't know how expensive that will be
Click to expand...
Click to collapse
I was afraid you would say that.

Holy crap. May I say, I am quite impressed. I never planned on rooting my S3 (I like it that much!) but this just looked so damn easy to do and it was!
For the curious! I have a Virgin Mobile S3, and I'm on Kitkat 4.4.2, baseband NDC. Verified root with Root Checker Basic. No problems with mobile data.
Many thank yous, 6th_Hokage!

strangelady said:
Holy crap. May I say, I am quite impressed. I never planned on rooting my S3 (I like it that much!) but this just looked so damn easy to do and it was!
For the curious! I have a Virgin Mobile S3, and I'm on Kitkat 4.4.2, baseband NDC. Verified root with Root Checker Basic. No problems with mobile data.
Many thank yous, 6th_Hokage!
Click to expand...
Click to collapse
your welcome strangelady and if you want check out the links in my signature area for other cool stuff

added two more t=root methods

[Q] I747MVLUFNF2 Root

So I recently updated to the I747MVLUFNF2 update in Kies from the I747MVLUFNE6 Update and I can't seem to root it using towelroot (I keep getting a phone unsupported message). Is there another method to root the phone without tripping KNOX?

Not without tripping the Warranty Bit, no. But most of the older methods of rooting will still work.

DocHoliday77 said:
Not without tripping the Warranty Bit, no. But most of the older methods of rooting will still work.
Click to expand...
Click to collapse
I understand once I root it with CF Auto Root then the warranty bit is tripped, but does this prevent me from using my phone with kies to update or backup? Or what exactly happens?

It just means you cannot use Knox for secured storage. The vast majority of us hate knox anyway so you might actually call this a win!
Of course it also means they can refuse warranty services, but most never need this, and many have reported their warranty being honored regardless.
Otherwise, it has no other effect on how you use your device, flash roms, root, etc.

I have the same issue.
I don't care about knox... but rooting it with the other ways that I know installs the super user app properly but then the SU app keeps crashing... I was assuming it was because of knox but now I'm not sure anymore, tried to reset it and to reflash the rom twice and every time it did the same thing...
Do you have any ideas why that might be happening?
I really would need a solution as I hate unrooted 4.4.2... :S
Thank you!

After rooting, you should be able to open SuperSU and it'll update its binary if needed and will disable knox.
Did you do that part?

I did try to update SU... The result was the same... the SU app would crash when I tried to launch it, before it even gives you the screen to disable knox... Trying to download the slightly older I747MVLUFNE6 which hopefully will root better...

You cant downgrade firmware. You could flash a rom, but i dont think that's what you were getting at.
How did you try to root? Have you tried using the oldest method we've got? Seems to never fail when others do!
Flash custom recovery with Odin.
From recovery flash the SuperSU update zip. You can find it by going to chainfires thread. (Its also in my sig bit I haven't added the very latest version yet)

Yeah, I realized my stupidity after posting the last message... I was thinking of flashing the older rom in... but that would have crapped out...
Finally got it to work...
Thought I had tried it before... but now I kind of doubt myself >.>
Reflashed the same version of the rom ... Found a really old version of auto-root, flashed it in... then I could update SuperSU and it disabled Knox...
Should have tried a bit harder before posting... sorry about that...
Thank you very much for your help.

Bob Terwilliger said:
Yeah, I realized my stupidity after posting the last message... I was thinking of flashing the older rom in... but that would have crapped out...
Finally got it to work...
Thought I had tried it before... but now I kind of doubt myself >.>
Reflashed the same version of the rom ... Found a really old version of auto-root, flashed it in... then I could update SuperSU and it disabled Knox...
Should have tried a bit harder before posting... sorry about that...
Thank you very much for your help.
Click to expand...
Click to collapse
Hi Bob
please witch version of auto-root have you use ?

The one I used was hard to find. Most people only post a link to Chainfire's website when making a rooting tutorial. This was a problem because Chainfire updated his official auto-root release with the latest SuperSU apk, making it impossible to update...
http : // androidxda . com / root - samsung - galaxy - s 3 - sgh-i747m
(can't post links yet, apparently...remove all spaces from previous line after copying it to address bar)
The guy from the above website decided to go the longer way of uploading an auto-root that he re-zipped himself. Not sure why he did that but it was perfect for what I needed.
Just download and unzip the auto-root that he provided and you'll be able to root your 4.4.2 SGH-I747M.

Bob Terwilliger said:
The one I used was hard to find. Most people only post a link to Chainfire's website when making a rooting tutorial. This was a problem because Chainfire updated his official auto-root release with the latest SuperSU apk, making it impossible to update...
http : // androidxda . com / root - samsung - galaxy - s 3 - sgh-i747m
(can't post links yet, apparently...remove all spaces from previous line after copying it to address bar)
The guy from the above website decided to go the longer way of uploading an auto-root that he re-zipped himself. Not sure why he did that but it was perfect for what I needed.
Just download and unzip the auto-root that he provided and you'll be able to root your 4.4.2 SGH-I747M.
Click to expand...
Click to collapse
Using the zip you provided, which version of SU did you use?

The auto-root tar in the zip the guy provided on his site is dated 2014-2-27 11:13.

Bob Terwilliger said:
The auto-root tar in the zip the guy provided on his site is dated 2014-2-27 11:13.
Click to expand...
Click to collapse
i have tried this one but it doesn't solve my problem, SuperSU crashed when it start, i don't understand what is the cause :crying:

It'll work... SuperSU crashing is normal... you need to go to the play store and update SuperSU... after that you'll be able to run the app and disable Knox.

Bob Terwilliger said:
It'll work... SuperSU crashing is normal... you need to go to the play store and update SuperSU... after that you'll be able to run the app and disable Knox.
Click to expand...
Click to collapse
thanks bob, i discover that the problem was about the I747MVLUFNF2 rom, so I changed it by I747MVLUFNE6 and all ok now
thank you again :good:

I did the opposite. I flashed the latest version of CF-Auto-Root from http://autoroot.chainfire.eu/. SuperSU was crashing, so I re-flashed the latest version of SuperSU (v2.01) from http://download.chainfire.eu/supersu and it worked fine after that. This was on the I747MVLUFNF2 ROM.

DocHoliday77 said:
Not without tripping the Warranty Bit, no. But most of the older methods of rooting will still work.
Click to expand...
Click to collapse
I've also updated to the latest firmware for gs3-1747m and tried to root using these new rooting tools that are on the device itself. Can you elaborate on an older version that would work on the device? My data pins on the mico-usb port were damaged, so I cannot transfer any data with a PC. Can't use Odin or other devices that require USB debugging
Thanks!

If Towelroot doesn't work, there is no other way to root without using Odin and a PC.
Sent from my SAMSUNG-SGH-T999 using Tapatalk

hey
aryan.yazdani said:
I've also updated to the latest firmware for gs3-1747m and tried to root using these new rooting tools that are on the device itself. Can you elaborate on an older version that would work on the device? My data pins on the mico-usb port were damaged, so I cannot transfer any data with a PC. Can't use Odin or other devices that require USB debugging
Thanks!
Click to expand...
Click to collapse
Actually... PM me, I'll tell you how I did it.