Related
Hey again....
so i decided to take my phone to samsung for them to fix this ****
so what i want to do is root the device, use triangle SU and then flash the stock rom
HOWEVER CWM doest root the device....
I'm using odin to flash it, and it does, but then instead of rooting on the device it just goes straight into phone, and the super user app isnt there....
I'm completely lost at this point
Moldat said:
Hey again....
so i decided to take my phone to samsung for them to fix this ****
so what i want to do is root the device, use triangle SU and then flash the stock rom
HOWEVER CWM doest root the device....
I'm using odin to flash it, and it does, but then instead of rooting on the device it just goes straight into phone, and the super user app isnt there....
I'm completely lost at this point
Click to expand...
Click to collapse
try mobile odin to flash rom image that will root fone and put su on it
sloppy1 said:
try mobile odin to flash rom image that will root fone and put su on it
Click to expand...
Click to collapse
mobile odin doesnt work if the device isnt rooted....
Moldat said:
mobile odin doesnt work if the device isnt rooted....
Click to expand...
Click to collapse
Just download:cfautoroot or the root package, and flash it through odin=>pda=>file=>flash! That should root the device
"If i have helped you, just hit the "thanks" button pls"-sent from my GT-N7100...drop some question here in my sticky thread: http://forum.xda-developers.com/showthread.php?t=2055736
well i tried to root using cf auto root, didnt work, instead of rooting after the odin flash it just goes straight into the rom
Moldat said:
well i tried to root using cf auto root, didnt work, instead of rooting after the odin flash it just goes straight into the rom
Click to expand...
Click to collapse
you need to press power button + home button + volume up... once the phone restarts and you see the samsung screen release the buttons and you will be in recovery mode.
So all of sudden, my rooted S3 is not rooted anymore.
I wanted to use Titanium Backup and it says
"Sorry, I could not acquire root privileges. This application will *not* work! Pleasre verify that your ROM is rooted, and try again.
This attempt was made using the "/system/xbin/su" command."
and then I tried my other root applications such as Greenify, App Ops and they are all saying my phone isn't rooted anymore.
I don't understand, I never upgraded my phone after I rooted and I never flashed a different rom and kept the Touchwiz Rom.
I used this guide to root my phone originally:
http://forum.xda-developers.com/showthread.php?t=1771687
My phone is running 4.3 Android (Same Version I used when Rooted in the first place)
Baseband Version: T999UVUEMJC
Please let me know what to do
check if supersu is working properly.
Cronoss said:
check if supersu is working properly.
Click to expand...
Click to collapse
It isn't.
The following message pops up:
"There is no SU binary installed, and SuperSU 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!"
magic132131 said:
It isn't.
The following message pops up:
"There is no SU binary installed, and SuperSU 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!"
Click to expand...
Click to collapse
My suggestion would be to back everything up and re flash root66.
Cronoss said:
My suggestion would be to back everything up and re flash root66.
Click to expand...
Click to collapse
Would I lose all my data?
In terms of re flash root66, that means simply using Odin and re-rooting my phone like I do the first time right? Would it be the same instructions too?
magic132131 said:
Would I lose all my data?
In terms of re flash root66, that means simply using Odin and re-rooting my phone like I do the first time right? Would it be the same instructions too?
Click to expand...
Click to collapse
I'm not sure if you are going to lose your data.. so that's why I said to back everything up, just in case.
And yes.. same method as before from that post.
Befoe you flash again. Try uninstalling then installing supersu again
SoulEater- said:
Befoe you flash again. Try uninstalling then installing supersu again
Click to expand...
Click to collapse
I can't uninstall supersu as it gives me no option to do so. I can only uninstall all updates that were applied but not complete remove and then install it.
I had this happen on my Tmobile Galaxy S3.
I read somewhere else on XDA that you just had to install the latest SuperSU, in zip form, from recovery mode.
I havent posted enough here to be able to post a link, but you can find it on chainfires website.
Then reboot and it should work.
Mine Note II is SGH-I317M with baseband version of I317MVLUCMK5 and KNOX.
I have tried CF-Auto-Root and Root SuperSU but weren't able to root my note II.
I have tried using different version of Odin, reinstalled the USB driver and tried using philz touch and cwm6 root to backup and root.
Nothing worked........Can't even start SuperSU.....
KNOX keep giving me security notice "An attempt to access a secure area on your device without authorisation has been blocked."
I also tried an updated Superuser. Still nothing worked....
Any idea anyone?
Thank you very much.
Stewegg said:
Mine Note II is SGH-I317M with baseband version of I317MVLUCMK5 and KNOX.
I have tried CF-Auto-Root and Root SuperSU but weren't able to root my note II.
I have tried using different version of Odin, reinstalled the USB driver and tried using philz touch and cwm6 root to backup and root.
Nothing worked........Can't even start SuperSU.....
KNOX keep giving me security notice "An attempt to access a secure area on your device without authorisation has been blocked."
I also tried an updated Superuser. Still nothing worked....
Any idea anyone?
Thank you very much.
Click to expand...
Click to collapse
You need to disable knox first
http://forum.xda-developers.com/showthread.php?p=49860203
Stewegg said:
Can't even start SuperSU
Click to expand...
Click to collapse
This is really weird, when I did this to my SGH-I747/M it was updated to stock 4.3 so it had KNOX and I got the same message as you but to disable it, all I did was open SuperSU and it prompts me to disable KNOX and then it's "fully" rooted and I could install a custom recovery after that.
I know it worked on the S3 because it's currently rooted running a custom ROM. Are you using the right version of Odin? I was trying to use 1.85 I think it was and it wasn't working at first, I tried 3.09 and it worked like a dream.
Did you remember to go into the Security Settings and turn off Reactivation Lock? I know this can play a factor when rooting with KNOX.
Also, KNOX never goes away, even though I'm running an AOSP ROM now on the S3, it still shows the KNOX counter with 0x1, even with it disabled. I can also not get any ROM's lower then 4.3 to work anymore so I can no longer run RootBox 4.2.2 on the S3.
I'm not sure if it's just me, or just my phone, but since that KNOX update was already on it when I got the phone used, it will not let me go to any ROM's lower then 4.3
VeeDaub said:
This is really weird, when I did this to my SGH-I747/M it was updated to stock 4.3 so it had KNOX and I got the same message as you but to disable it, all I did was open SuperSU and it prompts me to disable KNOX and then it's "fully" rooted and I could install a custom recovery after that.
I know it worked on the S3 because it's currently rooted running a custom ROM. Are you using the right version of Odin? I was trying to use 1.85 I think it was and it wasn't working at first, I tried 3.09 and it worked like a dream.
Did you remember to go into the Security Settings and turn off Reactivation Lock? I know this can play a factor when rooting with KNOX.
Also, KNOX never goes away, even though I'm running an AOSP ROM now on the S3, it still shows the KNOX counter with 0x1, even with it disabled. I can also not get any ROM's lower then 4.3 to work anymore so I can no longer run RootBox 4.2.2 on the S3.
I'm not sure if it's just me, or just my phone, but since that KNOX update was already on it when I got the phone used, it will not let me go to any ROM's lower then 4.3
Click to expand...
Click to collapse
Where is the Reactivation Lock located?
I can not find it in the Security Settings.
mrevankyle said:
You need to disable knox first
http://forum.xda-developers.com/showthread.php?p=49860203
Click to expand...
Click to collapse
I was following the steps in the post you have posted.
When I tried to flash the DrKetan_MultiTool_AdvanceV5, it gives me an error: E:signature verification failed. and stopped the flash.
Any idea?
Stewegg said:
I was following the steps in the post you have posted.
When I tried to flash the DrKetan_MultiTool_AdvanceV5, it gives me an error: E:signature verification failed. and stopped the flash.
Any idea?
Click to expand...
Click to collapse
hey man i have the same phone as you, just found an easy way to root it after struggling. Just updated to Stock 4.3 Bell Firmware using odin, completely fresh phone.
How to root it:
1. Flash philz recovery in odin "philz_touch_6.19.3-t0lteatt.tar.md5" (Download mode= Vol Down + Home + Power)
2. Reboot back into android once
3. Power off phone
4. Boot into recovery (Vol Up + Home + Power)
5. Goto philz settings->Reroot rom (or something to that effect)
6. Recovery will tell you done, and to reboot and install SuperSU from Play Store
7. Reboot download and install SuperSU from Play Store
8. Open SuperSU it will immediately ask if you would like to disable Knox.. say yes
9. Done
Link to philz recovery tar for our phone i317M
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/t0lteatt/philz_touch_6.19.3-t0lteatt.tar.md5
Does this work?
My wife's Rogers note2 is bone stock running I317MVLUCMK5.
She is paranoid about Knox and possibly killing her phone.
She wants me to get it rooted, but I'm struggling to find a clear cut answer.
Also, it would be better if anyone knows how to (if possible) downgrade to 4.1.2 and start from there... As I know how to do that one like the back of my hand.
Sent from my SGH-I317 using Tapatalk
Stewegg said:
Mine Note II is SGH-I317M with baseband version of I317MVLUCMK5 and KNOX.
I have tried CF-Auto-Root and Root SuperSU but weren't able to root my note II.
I have tried using different version of Odin, reinstalled the USB driver and tried using philz touch and cwm6 root to backup and root.
Nothing worked........Can't even start SuperSU.....
KNOX keep giving me security notice "An attempt to access a secure area on your device without authorisation has been blocked."
I also tried an updated Superuser. Still nothing worked....
Any idea anyone?
Thank you very much.
Click to expand...
Click to collapse
Simple. First get the root. Like the su binary and stuff. once you are rooted get suersu. What I mean by first get root is literally get root through a program or something. After this you will have root but you wont have root access. So get supersu now and launch the app. It will ask to update your su binary. Say yes. then the thing will say something about knox then ask you if you want to try to disable knox. Tap yes and knox should be disabled and your su binary should be updated and working.
I'm exactly in the middle of nowhere .. Try to root with CF method. After the first try and reboot. I got the knox alert "unauthorized, bla, bla" the thing is that I can't get the full root or return to stock. Also when I tried to install knox in order to Uninstaller it, I can't. My phone is not allowed to use knox any more... I already tried to download Su and update it in order to disable knox with no success.... Stupid knox and stupid 4.3:crying:
My phone is I317M Rogers, it run stock 4.3. I followed this guide, http://forum.xda-developers.com/showthread.php?t=2618261 rooted success.
Eun-Hjzjined said:
Does this work?
My wife's Rogers note2 is bone stock running I317MVLUCMK5.
She is paranoid about Knox and possibly killing her phone.
She wants me to get it rooted, but I'm struggling to find a clear cut answer.
Also, it would be better if anyone knows how to (if possible) downgrade to 4.1.2 and start from there... As I know how to do that one like the back of my hand.
Sent from my SGH-I317 using Tapatalk
Click to expand...
Click to collapse
ifentanez said:
I'm exactly in the middle of nowhere .. Try to root with CF method. After the first try and reboot. I got the knox alert "unauthorized, bla, bla" the thing is that I can't get the full root or return to stock. Also when I tried to install knox in order to Uninstaller it, I can't. My phone is not allowed to use knox any more... I already tried to download Su and update it in order to disable knox with no success.... Stupid knox and stupid 4.3:crying:
Click to expand...
Click to collapse
koodiifin said:
hey man i have the same phone as you, just found an easy way to root it after struggling. Just updated to Stock 4.3 Bell Firmware using odin, completely fresh phone.
How to root it:
1. Flash philz recovery in odin "philz_touch_6.19.3-t0lteatt.tar.md5" (Download mode= Vol Down + Home + Power)
2. Reboot back into android once
3. Power off phone
4. Boot into recovery (Vol Up + Home + Power)
5. Goto philz settings->Reroot rom (or something to that effect)
6. Recovery will tell you done, and to reboot and install SuperSU from Play Store
7. Reboot download and install SuperSU from Play Store
8. Open SuperSU it will immediately ask if you would like to disable Knox.. say yes
9. Done
......
Click to expand...
Click to collapse
koodiifin's way worked perfectly!
Thank you koodiifin!
I flashed stock 4.4.2 from sammobile, cf auto root, open su user, disable knox, flashify install TWRP....and then i flashed insane kitkat...i am getting a error kernel is not se android enforcing (in red), set warranty bit: kernel (in yellow) top left corner and it gets stuck on this screen..
Does anyone know how to fix this? I would like to be on a custom kit kat rom rather than the stock version. Thanks.
ab102 said:
I flashed stock 4.4.2 from sammobile, cf auto root, open su user, disable knox, flashify install TWRP....and then i flashed insane kitkat...i am getting a error kernel is not se android enforcing (in red), set warranty bit: kernel (in yellow) top left corner and it gets stuck on this screen..
Does anyone know how to fix this? I would like to be on a custom kit kat rom rather than the stock version. Thanks.
Click to expand...
Click to collapse
Try flashing another kernel through recovery. Sorry I don't have a link. but you will get the se android enforcing message along with set warranty bit. Don't worry about that. The stuck screen is the problem and I've had problems like that after installing a backup and was told to flash a new kernel and that worked.
what kernel should i flash?
ab102 said:
what kernel should i flash?
Click to expand...
Click to collapse
Try the kernels here http://forum.xda-developers.com/showpost.php?p=44314828&postcount=2
The Touchwiz Kit Kat 4.4 kernel should work for you.
i tried that.....didnt work
can someone please help me fix this issue?
At this point all I can think of is to Odin a stock rom back on then root and install custom recovery. put the Insane rom on the phone's sdcard. Boot into recovery, wipe then install via sd card the insane rom. This is how I've done it and it worked. Only time I was getting the boot loop was when I tried to reinstall a nandroid backup I made. Oh, don't worry about disabling knox. I wouldn't go so far as to even do anything else to the stock rom once it's rooted. I wouldn't even answer the Language question it asks when you first boot up.
that didnt work either.....guess im stuck with stock kit kat ...
Did you make sure to do a full wipe before flashing the Insane kk, like Sickness stated?
Sent from an A.I. frequency
Why not post on the insane kk thread so others can see and try to help..just me .02
Im on his rebirth rom and between him(thesickenss) and others the support is unbelievable...im sure youll get farther there
yes i did full wipe..and the reason why I have it on this thread is bc i tried posting in that tread..but other ppls questiosn got in the way..thats why i wanted to open a new thread....so does anyone have any idea how i can get insane kit kat to work.
i flashed the stock 4.4 from sam mobile, then odin cfroot, flashify- TWRP...wipe, factory reset, install insane kit kat
is there a way to ODIN TWRP?..i was using flashify and installed it like that..that way i dont have to mess with the stock at all such as the language screen. Thanks.
ab102 said:
is there a way to ODIN TWRP?..i was using flashify and installed it like that..that way i dont have to mess with the stock at all such as the language screen. Thanks.
Click to expand...
Click to collapse
Yes, flash this tar in odin: (http://techerrata.com/browse/twrp2/jfltetmo Get the newest .tar)
Fenny said:
Yes, flash this tar in odin: (http://techerrata.com/browse/twrp2/jfltetmo Get the newest .tar)
Click to expand...
Click to collapse
ok i did that same error message...this is so frustrating ahhhh!!..also at the end of flashing insane kit kat it asks me..your device does not appear to be rooted, install SU user? i just said do not install, but in the past i have also said install SU user and it still gets stuck..i already rooted the phone via cf auto root..
ab102 said:
ok i did that same error message...this is so frustrating ahhhh!!..also at the end of flashing insane kit kat it asks me..your device does not appear to be rooted, install SU user? i just said do not install, but in the past i have also said install SU user and it still gets stuck..i already rooted the phone via cf auto root..
Click to expand...
Click to collapse
Try wiping /system/ before flashing the zip. I think that insane may not do a /system wipe as part of the install.
Fenny said:
Try wiping /system/ before flashing the zip. I think that insane may not do a /system wipe as part of the install.
Click to expand...
Click to collapse
yup i noticed that and did that this time..still no go...i think i just tripped up knox somehow and theres nothing i can do to fix this..ive searched everywhere .
ab102 said:
yup i noticed that and did that this time..still no go.
Click to expand...
Click to collapse
Try flashing my 1.0 kernel with odin: http://www.cheatersedge.org/android/boot.tar
Fenny said:
Try flashing my 1.0 kernel with odin: http://www.cheatersedge.org/android/boot.tar
Click to expand...
Click to collapse
Nope that did not work either.
ab102 said:
Nope that did not work either.
Click to expand...
Click to collapse
So, it just hangs on the bootloader screen whenever you flash a custom kernel, but it will boot to a custom recovery... does that sound about right?
Fenny said:
So, it just hangs on the bootloader screen whenever you flash a custom kernel, but it will boot to a custom recovery... does that sound about right?
Click to expand...
Click to collapse
yes it hangs on the boot screen and says Kernel is not se android enforcing (in red) below that it says Set Warranty Bit: kernel (in yellow)....for me to go into custom recovery i have to do volume up power and menu buttom, download mode vice versa.
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