Related
I am new with rooting my phone. I have used Rooted phones before, I followed http://forum.xda-developers.com/showthread.php?t=2258633 Motochopper how to. I ran into a problem. I click the superuser app that was installed onto my phone, and it tells me that "The Superuser binary (su) must be updated. Please choose an installation method. Recovery mode installation is recommended for HTC devices." I click install and it tells me there was an error. I would like to root my phone along with potentially installing CWM so that I can easily install Cyanogenmod when they release a stable verison for the S4. Also would love to install titanium backup along with some Adfree apps.
Any help would be very much appreciated.
OK, so it looks like you already have it rooted.
When super SU asks that question, dont install via CWM, tell it to just install normally.
Once you have SuperSU working, Download Rom Manager from the play store and install CWM Recovery right from within the ROM Manager app.
It will give you the option to pick between two types of CWM(ClockWorkMod). The Touch version, like its name gives you the ability to use the touch screen and not only the volume up/down + Power button.
Telling it to install normally causes it to just tell me there was an error, it also tells me it is out of date as well. Titanium Backup tells me that it cant get root access and I was never asked about it.
OK, so your phone is not rooted then.
Your going to have to try rooting it again or flashing an already rooted rom with Odin.
I just tried it again, this time it said failure after the install of the superuser.apk. I just read that one of the later updates by samsung can make it harder to root. I just got my phone and i was fully updated. What Roms, are already rooted for the S4. I am actually enjoying some of the default apps that came with the phone.
Wicked (and most ROMs that don't include the [STOCK] tag) are pre-rooted...but you'll need to ODIN a custom recovery first then flash the ROM.
If you want to stay on rooted stock, follow the steps in the "root May 7 MDL" thread to ODIN a rooted kernel, and you'll be good to go.
(You don't need root access to get a custom recovery flashed)
Basically, any of your options are pretty straightforward, but they're going to involve Odin-ing stuff.
So there isn't really a way to just root my phone without installing a custom rom?
There was before the second update, with the second update rooting got just a little bit more steps
Sent from my SGH-M919 using xda premium
movieaddict said:
There was before the second update, with the second update rooting got just a little bit more steps
Sent from my SGH-M919 using xda premium
Click to expand...
Click to collapse
So is there a way to keep it stock but root it? What are the other steps I would have to take. Why does Samsung not like people rooting their phones, I thought carriers were the ones that hated people rooting their phones
Spud37 said:
So is there a way to keep it stock but root it? What are the other steps I would have to take. Why does Samsung not like people rooting their phones, I thought carriers were the ones that hated people rooting their phones
Click to expand...
Click to collapse
Are you still on the MDB firmware or have you done any over the air updates? Specifically the May 7 update which is MDL. Motochopper is specifically for then older firmware (MDB) and it won't work if you are already on the updated. MDL firmware. In which case you would have to follow these instructions to acquire root.
http://forum.xda-developers.com/showthread.php?p=41162041
I usually use a market app called root checker to quickly check if I do have root.
And yes you can be rooted on stock.
Sent from my SGH-M919
lazaro17 said:
Are you still on the MDB firmware or have you done any over the air updates? Specifically the May 7 update which is MDL. Motochopper is specifically for then older firmware (MDB) and it won't work if you are already on the updated. MDL firmware. In which case you would have to follow these instructions to acquire root.
http://forum.xda-developers.com/showthread.php?p=41162041
I usually use a market app called root checker to quickly check if I do have root.
And yes you can be rooted on stock.
Sent from my SGH-M919
Click to expand...
Click to collapse
Root checker says no root. I believe it does have that over the air update installed. T Mobile updated it when they gave me the phone, because they thought I didn't really know anything about phones. I assume this means I have to follow another method to root my phone?
If you have the MDL update you have to root using the steps listed here:
http://forum.xda-developers.com/showthread.php?t=2268880
Easily done, just a few more steps.
ronin4740 said:
If you have the MDL update you have to root using the steps listed here:
http://forum.xda-developers.com/showthread.php?t=2268880
Easily done, just a few more steps.
Click to expand...
Click to collapse
This is going to sound like a dumb question but from reading all of that I need to use ODIN to install the ROOT_M919?UVUAMDL onto the phone? that should root the phone and allow me to install ROM Manager and install CWM from there right?
Also would doing this delete everything I have on my phone right now?
Spud37 said:
This is going to sound like a dumb question but from reading all of that I need to use ODIN to install the ROOT_M919?UVUAMDL onto the phone? that should root the phone and allow me to install ROM Manager and install CWM from there right?
Also would doing this delete everything I have on my phone right now?
Click to expand...
Click to collapse
No, you use Odin to install one of the recoveries. You use the recovery to install the zip ROOT_M919?UVUAMD. Personally I didn't use that file. I installed the kernel in recovery and SuperSU in recovery. And no, it won't delete things on your phone.
Atmazzz said:
No, you use Odin to install one of the recoveries. You use the recovery to install the zip ROOT_M919?UVUAMD. Personally I didn't use that file. I installed the kernel in recovery and SuperSU in recovery. And no, it won't delete things on your phone.
Click to expand...
Click to collapse
Thank you so much, I am about to go and do this. I will use the kernel you suggested since that looks like a better option, after flashing the kernal should i reboot and just use it normally for a bit and then go to recovery and flash SuperSU?
EDIT: The steps on the thread for ODIN are for installing a rooted ROM, I am assuming its still the same steps for installing a recovery instead of a rooted ROM
Spud37 said:
after flashing the kernal should i reboot and just use it normally for a bit and then go to recovery and flash SuperSU?
Click to expand...
Click to collapse
If I remember right I just flashed them both at the same time. Just make sure you do the kernel first.
---------- Post added at 02:01 PM ---------- Previous post was at 01:59 PM ----------
Spud37 said:
EDIT: The steps on the thread for ODIN are for installing a rooted ROM, I am assuming its still the same steps for installing a recovery instead of a rooted ROM
Click to expand...
Click to collapse
The steps for Odin are for the stock rom, but yes, you use it the same way for a recovery.
Atmazzz said:
If I remember right I just flashed them both at the same time. Just make sure you do the kernel first.
---------- Post added at 02:01 PM ---------- Previous post was at 01:59 PM ----------
The steps for Odin are for the stock rom, but yes, you use it the same way for a recovery.
Click to expand...
Click to collapse
Okay I didn't get any error using ODIN, however when I try and boot into CWM using Volume Up + Power it just goes to android recovery. Which doesn't have any of the options I need. Am I just booting up the wrong way, or did I do something wrong. I tried both the touch version and the non-touch version
Spud37 said:
Okay I didn't get any error using ODIN, however when I try and boot into CWM using Volume Up + Power it just goes to android recovery. Which doesn't have any of the options I need. Am I just booting up the wrong way, or did I do something wrong. I tried both the touch version and the non-touch version
Click to expand...
Click to collapse
2 options. uncheck auto reboot in Odin. When Odin is done, unplug your phone, pull your battery, then boot into recovery. Or .. when Odin is done and it reboots your phone, keep holding volume up to get to recovery.
Atmazzz said:
2 options. uncheck auto reboot in Odin. When Odin is done, unplug your phone, pull your battery, then boot into recovery. Or .. when Odin is done and it reboots your phone, keep holding volume up to get to recovery.
Click to expand...
Click to collapse
Thank You so much. However it now seems like I have both Super User and SuperSU installed.
How did you root? Did you install the ROOT_M919?UVUAMDL zip and install SuperSU?
|Guide|How-To| Root & Install Custom Recovery for 4.3 / 4.4 Update |16 July 2014 |
Warning: Following any of these instructions will void your warranty, and could possibly cause irreparable harm to your device (i.e. bricked). If you do not understand these risks, stop here and do not proceed. If you do not know how to use Odin, stop here and do not proceed. I am not responsible for anything that happens to your device. YOU chose to follow this guide.
If you have not updated to 4.3, go here.
If you have not updated to 4.4, go here.
Finally, there is no guarantee that either method will work for you.
Root Method #1:
The first thing you should try is CF-Autoroot since this has worked for many users.
If you successfully root with this method, you can simply install Goo Manager or ROM Manager and install recovery.
This method failed for me after many attempts.
Edit:
Here is some potentially useful info for root method #1 from ansonantonym.
Root Method #2:
1) Reboot in to download mode
2) Flash TWRP with Odin via PDA
3) Reboot to recovery then flash SuperSu and the Knox Remover
4) Reboot
5) Download SuperSu from the Play Store
6) Open SuperSu and update the binary when prompted
7) Reboot
8) Enjoy rooted 4.3/4/4
Downloads:
Odin
TWRP (Odin flashable tar)
SuperSu (v1.65)
SuperSu (v2.01)
DE-SAMSUNGNIZER_KNOX_REMOVAL_SCRIPT_V1.0
If you found another method that worked for you, please post here so that others may benefit.
If you are uncertain about any of the steps above, please ask your questions here before proceeding.
Please be sure to thank Chainfire, Dees_Troy, and Kaito95.
*****
Noob here, first off I unrooted a while ago, then took the ota 4.3, is the bootloader locked? Cause according to the cf auto root site if your bootloader is locked you'll probably brick your phone if you flash the auto root? Also do these steps have to be in order? I tried rooting by other means and installing supersu first, wouldn't work so I removed knox with the script, and then updated supersu in the play store and still nothing, can I try to flash cf auto root now and then update supersu in the play store? Thanks a million, need this thing rooted
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
jeremyds45 said:
Noob here, first off I unrooted a while ago, then took the ota 4.3, is the bootloader locked? Cause according to the cf auto root site if your bootloader is locked you'll probably brick your phone if you flash the auto root? Also do these steps have to be in order? I tried rooting by other means and installing supersu first, wouldn't work so I removed knox with the script, and then updated supersu in the play store and still nothing, can I try to flash cf auto root now and then update supersu in the play store? Thanks a million, need this thing rooted
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Well, I'm not bricked, so I think that answers your question about the bootloader.
Do you have a custom recovery installed? I assume so since you say you flashed the Knox remover script. If you do have a custom recovery installed, just flash the SuperSu zip, then update in the Play Store.
upndwn4par said:
Well, I'm not bricked, so I think that answers your question about the bootloader.
Do you have a custom recovery installed? I assume so since you say you flashed the Knox remover script. If you do have a custom recovery installed, just flash the SuperSu zip, then update in the Play Store.
Click to expand...
Click to collapse
Ah it is so nice to have root again... Thank you so much for putting up with a noob.
Crazy events of a noob that lead me to root
Installed ota 4.3
Tried to root and install superuser by odin and then custom recovery to flash
Root didn't happen because of knox
Could only get to CWM custom recovery if it was right after odin and battery pull?...
Flashed the script to remove knox, which did remove knox
Tried the same root method as above and no root access
Tried supersu and then updating in play with no success
Changed security update settings etc nothing
Reset delvik, cache, permissions, etc nothing
Different root method and files for odin, and custom recovery stuck
Used files from this thread, went into custom recovery and flashed supersu
Installed supersu from play store...
Updated the binary using custom recovery
Rebooted...
ROOT access, all root applications work fine and root sticks even after reboots
I never messed with cf auto root method
THANK you guys for your time effort and sharing, helps noobs out like me a lot!
Sweet! I've missed root since I upgraded using the OTA file you provided. Looking forward to much other great things coming from you
Thank You
upndwn4par said:
Warning: Following any of these instructions will void your warranty, and could possibly cause irreparable harm to your device (i.e. bricked). If you do not understand these risks, stop here and do not proceed. If you do not know how to use Odin, stop here and do not proceed. I am not responsible for anything that happens to your device. YOU chose to follow this guide.
If you have not updated to 4.3, go here. Make sure you understand the risks and uncertainties described in the OP.
Finally, there is no guarantee that either method will work for you.
Root Method #1:
The first thing you should try is CF-Autoroot since this has worked for many users.
If you successfully root with this method, you can simply install Goo Manager or ROM Manager and install recovery.
This method failed for me after many attempts.
Root Method #2:
1) Reboot in to download mode
2) Flash TWRP with Odin via PDA
3) Reboot to recovery and flash SuperSu.
4) Flash the Knox Remover
5) Reboot
6) Download SuperSu from the Play Store
7) Update the binary when prompted
8) Reboot
8) Enjoy 4.3
Downloads:
Odin
TWRP (Odin flashable tar)
UpdateSuperSu
If you found another method that worked for you, please post here so that others may benefit.
If you are uncertain about any of the steps above, please ask your questions here before proceeding.
*****
Click to expand...
Click to collapse
Method two absolutely worked. Thank you so much. I was scared to flash TWRP but knowing you did it gave me the courage. Have full root and happy
questions about this root
Hi, I'm a little nervous with this root but I need the root as the phone is useless without it.
I have the [email protected] galaxy s3 I747 will all these files work with it im just double checking.
Also do you flash the knox remover the same way as you flash other things with the pda button?
Will I still be able to do factory restores?
Also I saw that knox remover removes a lot of apps, Can you install these deleted apps from the market if you need too?
THanks please let me know asap.
THANKS!!!! your a lifesaver didn't know how much longer i could take without root
Dunno where you guys got your 4.3 update from and how you got it working but I did the OTA and Root just does not want to stick. I used knox remover and Cf auto root but it loses root after a restart. SuperSu never opens and crashes as soon as you open it. I have a feeling Cf auto root is just not compatible for the ota 4.3 i747??
bkong said:
Dunno where you guys got your 4.3 update from and how you got it working but I did the OTA and Root just does not want to stick. I used knox remover and Cf auto root but it loses root after a restart. SuperSu never opens and crashes as soon as you open it. I have a feeling Cf auto root is just not compatible for the ota 4.3 i747??
Click to expand...
Click to collapse
use the TWRP method worked perfected for me
Thanks
PimpMyPC said:
Hi, I'm a little nervous with this root but I need the root as the phone is useless without it.
I have the [email protected] galaxy s3 I747 will all these files work with it im just double checking.
Also do you flash the knox remover the same way as you flash other things with the pda button?
Will I still be able to do factory restores?
Also I saw that knox remover removes a lot of apps, Can you install these deleted apps from the market if you need too?
THanks please let me know asap.
Click to expand...
Click to collapse
The second method worked great. I believe (and the way that worked for me) that you use your custom recovery to flash the knox script, not using Odin and pda. I don't think it removed anything other than knox, there is a different script for removing knox and att bloatware. Should still be able to factory reset... But can't guarantee that.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Root & Knox
When you go to Settings/More tab/Security/Device Administrators, You have KNOX and Android Device Manage. Both are unchecked on mine. So does that mean Knox is not working if unchecked and safe to try to Root?????
tailgunner9 said:
When you go to Settings/More tab/Security/Device Administrators, You have KNOX and Android Device Manage. Both are unchecked on mine. So does that mean Knox is not working if unchecked and safe to try to Root?????
Click to expand...
Click to collapse
Those settings are just for granting device administrator privileges. If unchecked, Knox is still doing it's thing, just not at an administrative level.
Yes, it is safe to try and root.
I have Android Device Manager as admin. That way if I ever lose my device I can just log in to the Play Store and locate and / or wipe the device.
To do this just flash the recovery.img file using odin and clicking the pda button correct?
Is there a way to freeze Knox instead of deleting it in the event I would want to go back to full stock?
After you are rooted, use an app like Titanium Backup(pro) or My Backup pro. Both will freeze it.
Root
If some of you out there use Root Method #2 and it works well and No problems, Please post and let us all know. Thanks
tailgunner9 said:
If some of you out there use Root Method #2 and it works well and No problems, Please post and let us all know. Thanks
Click to expand...
Click to collapse
I tried method 1 and failed.
Then tried method 2, but using a CMW tar that was posted yesterday.
I seem to be rooted!
So far no issues.. Just need to get everything setup as I had it in the leak.
indymx said:
I tried method 1 and failed.
Then tried method 2, but using a CMW tar that was posted yesterday.
I seem to be rooted!
So far no issues.. Just need to get everything setup as I had it in the leak.
Click to expand...
Click to collapse
Thanks indymx, may get the nerve up to try it on my AT&T S3. Let me know if you run into any problems. Guess Rom Manager and other programs that require Root are working Ok and you have rebooted few times to be sure it keeps Root?? Have Happy Thanksgiving.
I tried this method and I got a Knox warranty void http://forum.xda-dev...555&postcount=1 . Not OP's fault,i'm sure it was my error.
Being I got the void anyway,I wiped and installed KIES_HOME_I317UCALJ2_I317ATTALJ2_215287_REV04_user _low_ship.tar.md5. It downgraded my BL to 4.1, then I rooted and flashed Slimbean 4.3 (with TWRP) with success. It counted against my binary download,but didn't trip knox again (Dont know if KNOX trips more then once). The only thing I did was used root explorer and deleted all Knox. Then I froze what was left with Titaniam.
EDIT
OK now I successfuly flashed the latest Slimkat with no problems what so ever. Still no trouble with Knox or bootloader. I have all backups of what I had installed if devs want to look and confirm what I have said is true.
Is this supposed to be possible or was people scared of tripping knox ????
BR7fan said:
I tried this method and I got a Knox warranty void http://forum.xda-dev...555&postcount=1 . Not OP's fault,i'm sure it was my error.
Being I got the void anyway,I wiped and installed KIES_HOME_I317UCALJ2_I317ATTALJ2_215287_REV04_user _low_ship.tar.md5. It downgraded my BL to 4.1, then I rooted and flashed Slimbean 4.3 (with TWRP) with success. It counted against my binary download,but didn't trip knox again (Dont know if KNOX trips more then once). The only thing I did was used root explorer and deleted all Knox. Then I froze what was left with Titaniam.
EDIT
OK now I successfuly flashed the latest Slimkat with no problems what so ever. Still no trouble with Knox or bootloader. I have all backups of what I had installed if devs want to look and confirm what I have said is true.
Is this supposed to be possible or was people scared of tripping knox ????
Click to expand...
Click to collapse
Link didn't work, so I couldn't see what you did....
You can check to see if Knox is tripped by turning off phone.
Once it’s off, you need to press this button combination: volume down, power button and home button. Keep them pressed until the download mode shows up. Once you’re there, you will be required to press volume up to enter the download mode or volume down to cancel and reboot the device. Press Up.
Upper left will show flash counts and last line will show if Knox is tripped.
Also to check which bootloader you are on:
search in play store - android system info - look in buildinfo
also there is an app called info - look in os
I should be in bed now..... I think this is right, open Android Terminal; type getprop ro.bootloader. That should tell you what bootloader you are on also.
I'm curious....
dicksteele said:
link didn't work, so i couldn't see what you did....
You can check to see if knox is tripped by turning off phone.
Once it’s off, you need to press this button combination: Volume down, power button and home button. Keep them pressed until the download mode shows up. Once you’re there, you will be required to press volume up to enter the download mode or volume down to cancel and reboot the device. Press up.
Upper left will show flash counts and last line will show if knox is tripped.
Also to check which bootloader you are on:
Search in play store - android system info - look in buildinfo
also there is an app called info - look in os
i should be in bed now..... I think this is right, open android terminal; type getprop ro.bootloader. That should tell you what bootloader you are on also.
I'm curious....
Click to expand...
Click to collapse
13i7ucubmk6
Knox is tripped. It happened when I was trying to downgrade using one of members method. But I did it by just installing the old att firmware
forum.xda-developers.com/showthread.php?t=2502464
BR7fan said:
13i7ucubmk6
Knox is tripped. It happened when I was trying to downgrade using one of members method. But I did it by just installing the old att firmware
forum.xda-developers.com/showthread.php?t=2502464
Click to expand...
Click to collapse
Interesting. Which firmware was it?
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
dicksteele said:
interesting. Which firmware was it?
Sent from my samsung-sgh-i317 using xda premium 4 mobile app
Click to expand...
Click to collapse
_i317attalj2_215287_rev04
this is the problem I've been having: Copy and pasted from a thread I created.
So I have a AT&T Samsung Galaxy Note 2 that as of 5 hours ago was completely stock and running android 4.3 (the official one from AT&T). I got bored last night and decided I wanted to root my phone (something I hadn't yet done in the entire year I had my phone). So I looked up how to root, read the instructions all the way (I thought my research was complete). I rooted using the CF auto method. After doing that I flashed TWRP using ODIN. I also downloaded Titanium Backup, Rom Manager & My Backup Root. I tried to use all three of these applications to make a backup of my device so that I could flash the custom Rom I wanted without losing all my information. That is when my troubles began.
Whenever I tried to access any of these apps I got a pop up saying Unfortunately, SuperSU has stopped and a notification stating An attempt to access a secure area on your phone without authorization has been blocked. None of the apps would run either and just kept freezing or loading forever.Thinking I'd done something wrong I repeated the root process all over again. I still kept getting the same notifications though. I typed in the unauthorized access notification message into google and discovered about Knox. Doing some tinkering of my own I went to settings (more tab)>>security>>device administrators>> unchecked knox>>deactivate. After deactivating Knox I once again tried to gain root access and had no success. I followed the advice from previous threads and tried to change all Knox.apk files to knox.apk.bak using Explorer, I downloaded Android terminal and tried to delete knox via the command line su pm... That also did nothing. I went to the market and tried to download the SuperSU app by CHAINFIRE, it wouldn't work as it already says the app is installed but offers me no updating options. I also downloaded the Update SuperSU zip file and tried to flash it. My phone wont boot into recovery though so that hasn't gotten me anywhere. Downloaded Rom Manager and GooManager to try to get into recovery mode and still no success. later flashed philz_touch via ODIN as people who had similar problems had posted about it working for them. Didn't work for me. Flashed TWRP again using ODIN and am now just scratching my head trying to figure out how to fix this issue.
I'm personally not worried much about the warranty stuff but am more concerned with the fact that I can't root my phone. All I want is to be able to load a custom rom (MIUI v5) onto my phone. Any and all help would be greatly appreciated.... If you've seen someone else with an issue like mine please just redirect me to the proper thread then.
p.s. I also tried running the root verify app and it got stuck on a loading page.
When I power my phone off and boot into recovery mode (or whatever its called) my stats read as:
ODIN MODE
Product name: SGH-I317
Custom Binary Download: Yes (7 counts) - this is from all my attempts to reroot and flash different recoveries
Current Binary: Custom
System Status: Custom
Knox Warranty Void: 1
AP SWAEV: A2
Ladyfinesse08 said:
this is the problem I've been having: Copy and pasted from a thread I created.
So I have a AT&T Samsung Galaxy Note 2 that as of 5 hours ago was completely stock and running android 4.3 (the official one from AT&T). I got bored last night and decided I wanted to root my phone (something I hadn't yet done in the entire year I had my phone). So I looked up how to root, read the instructions all the way (I thought my research was complete). I rooted using the CF auto method. After doing that I flashed TWRP using ODIN. I also downloaded Titanium Backup, Rom Manager & My Backup Root. I tried to use all three of these applications to make a backup of my device so that I could flash the custom Rom I wanted without losing all my information. That is when my troubles began.
Whenever I tried to access any of these apps I got a pop up saying Unfortunately, SuperSU has stopped and a notification stating An attempt to access a secure area on your phone without authorization has been blocked. None of the apps would run either and just kept freezing or loading forever.Thinking I'd done something wrong I repeated the root process all over again. I still kept getting the same notifications though. I typed in the unauthorized access notification message into google and discovered about Knox. Doing some tinkering of my own I went to settings (more tab)>>security>>device administrators>> unchecked knox>>deactivate. After deactivating Knox I once again tried to gain root access and had no success. I followed the advice from previous threads and tried to change all Knox.apk files to knox.apk.bak using Explorer, I downloaded Android terminal and tried to delete knox via the command line su pm... That also did nothing. I went to the market and tried to download the SuperSU app by CHAINFIRE, it wouldn't work as it already says the app is installed but offers me no updating options. I also downloaded the Update SuperSU zip file and tried to flash it. My phone wont boot into recovery though so that hasn't gotten me anywhere. Downloaded Rom Manager and GooManager to try to get into recovery mode and still no success. later flashed philz_touch via ODIN as people who had similar problems had posted about it working for them. Didn't work for me. Flashed TWRP again using ODIN and am now just scratching my head trying to figure out how to fix this issue.
I'm personally not worried much about the warranty stuff but am more concerned with the fact that I can't root my phone. All I want is to be able to load a custom rom (MIUI v5) onto my phone. Any and all help would be greatly appreciated.... If you've seen someone else with an issue like mine please just redirect me to the proper thread then.
p.s. I also tried running the root verify app and it got stuck on a loading page.
When I power my phone off and boot into recovery mode (or whatever its called) my stats read as:
ODIN MODE
Product name: SGH-I317
Custom Binary Download: Yes (7 counts) - this is from all my attempts to reroot and flash different recoveries
Current Binary: Custom
System Status: Custom
Knox Warranty Void: 1
AP SWAEV: A2
Click to expand...
Click to collapse
I think I'm tracking.....
First try going to settings, More, them go to application manager.
Remove super su. Go back to Google Play and download latest supersu.
Superuser executable does not get deleted when removing supersu app
See if that works
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
or flash download.chainfire.eu/282/SuperSU/ SuperSu with TWRP
BR7fan said:
or flash download.chainfire.eu/282/SuperSU/ SuperSu with TWRP
Click to expand...
Click to collapse
That looks better.
I looked at updater script and it deletes old stuff first before installing.
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
dicksteele said:
I think I'm tracking.....
First try going to settings, More, them go to application manager.
Remove super su. Go back to Google Play and download latest supersu.
Superuser executable does not get deleted when removing supersu app
See if that works
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks so much for your help. I tried doing what you said. When I go to SuperSU application under application manager it won't allow me to reomove it. All I can do is Turn it OFF. When If I go to the play market after turning it off the only option I get is to enable it again. Looking under App Info though it's showing that I'm on version 1.93 of SuperSu. I think from all the stuff I've been reading I'm supposed to be on version 1.95.
As for flashing it your TWRP I can't because I can't load into recovery mode with TWRP. The only thing thats working for me is ODIN. Not sure if there's a way to flash from ODIN or not but I personally don't know of one (I'm new to ODIN).
Ladyfinesse08 said:
Thanks so much for your help. I tried doing what you said. When I go to SuperSU application under application manager it won't allow me to reomove it. All I can do is Turn it OFF. When If I go to the play market after turning it off the only option I get is to enable it again. Looking under App Info though it's showing that I'm on version 1.93 of SuperSu. I think from all the stuff I've been reading I'm supposed to be on version 1.95.
As for flashing it your TWRP I can't because I can't load into recovery mode with TWRP. The only thing thats working for me is ODIN. Not sure if there's a way to flash from ODIN or not but I personally don't know of one (I'm new to ODIN).
Click to expand...
Click to collapse
http://goo.im/devs/OpenRecovery/t0lteatt/openrecovery-twrp-2.6.3.1-t0lteatt.img.tar
Here's a copy to flash in ODIN. If you can't boot into recovery after this, there are other things we can try from ODIN.
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
BR7fan said:
_i317attalj2_215287_rev04
Click to expand...
Click to collapse
K. I understand now. I think.
You were on MK6, the 4.3 OTA bootloader.
You tried flashing seanz MJ4 4.3 Leak bootloader and Knox didn't appreciate that.
You could still ODIN back to the LJ2 because it doesn't include a bootloader.
dicksteele said:
K. I understand now. I think.
You were on MK6, the 4.3 OTA bootloader.
You tried flashing seanz MJ4 4.3 Leak bootloader and Knox didn't appreciate that.
You could still ODIN back to the LJ2 because it doesn't include a bootloader.
Click to expand...
Click to collapse
I dont want to falsh back. What had me puzzled is that I thought that with knox you couldnt flash any rom because of secure bootloader. I am able to flash what ever I want with out any extra steps. Its like it was before knox came around.
BR7fan said:
I dont want to falsh back. What had me puzzled is that I thought that with knox you couldnt flash any rom because of secure bootloader. I am able to flash what ever I want with out any extra steps. Its like it was before knox came around.
Click to expand...
Click to collapse
Knox wasn't/isn't as restrictive as we imagined. It's more of an annoyance.
Biggest annoyance is not being able to flash older bootloaders, and the easily viewable notice that Knox had been tripped.
We've had it long enough to know our limitations
Man's got to know his limitations.
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
I opened the box on my new Galaxy Tab 12.2 SM-T900 today. I immediately rooted it with CF-Auto-Root-v2wifi-v2wifixx-smt900.zip. That worked fine. But before I rooted it there was a notification of an OTA update, so I unrooted and did the OTA update. That went fine as well. But then I attempted to root using the same file, odin got stuck at writing the cache. I tried it several times, but no go.
Having run out of time, I pulled the battery and set it aside to deal with tomorrow. It would be great if some one could point me to the correct image to flash to bring the device back to life.
As background, my last Samsung device was a Vibrant that I flashed repeatedly. Back then I didn't need to select a ROM, as there was a dev section full of them. Now I need a pointer to the correct firmware, and maybe some words of wisdom. I think the original firmware was NB5, and the OTA was ND2. I'm afraid that I was too excited to b quite organized enough to write this stuff down.
I'm uncertain whether I would prefer to flash back to the original and root, or flash to the newer firmware and wait and hope for the root issue to be resolved by Chainfire. Suggestions?
Try flashing the recovery from sm-p900 from this post, the one with the filename ending with "b3", then try to root agajn. Should work after that.
http://forum.xda-developers.com/showthread.php?p=50492301
If not, install Kies 3 and do an emergency restore. It will ask for your serial# and download the correct rom and flash it back to stock
Sent from my SM-P900 using Tapatalk
dodo99x said:
Try flashing the recovery from sm-p900 from this post, the one with the filename ending with "b3", then try to root agajn. Should work after that.
http://forum.xda-developers.com/showthread.php?p=50492301
Click to expand...
Click to collapse
Thanks! I'll give that a shot. But a question before I do something really dumb. Where does this recovery tar file go in odin? PDA?
Yep always PDA
Sent from my SM-P900 using Tapatalk
Worked! I now have rooted KOT49H.T900UEUAND4.
Good stuff
Sent from my SM-P900 using Tapatalk
OK. Here comes the "but". It turns out that I cannot connect over SSL. Wifi works, I have an IP, I can brows non-secure websites. But I cannlt connect to anything https, nor will apps like Google Play connect.
Do we think this is related, or should i start a new thread?
UPDATE: I wiped data and now all is fine. The really interesting thing that I've noticed is that the Device Status is showing as "Official".
JJMT - you are rooted and it says official? Can you go through the exact steps you used please? Is KNOX enabled?
gbr357 said:
JJMT - you are rooted and it says official? Can you go through the exact steps you used please? Is KNOX enabled?
Click to expand...
Click to collapse
Yes. I am rooted and it says official. What's more, it checks for updates, although who knows what will happen when one shows up.
What I have is the ND4 firmware with the NB5 recovery. To get to this state:
1. OTA to ND4.
2. Boot into download mode. Flash the NB3 recovery. (P900XXUANB3-RecoveryImg.tar) It will reboot automatically.
3. Boot into download mode. Flash the root file. (CF-Auto-Root-v2wifi-v2wifixx-smt900.tar.md5). It will reboot automatically.
4. Boot into recovery mode. Wipe data/factory reset.
I believe at this point we are done. If you do this and it doesn't come up "official", then there must be something peculiar in the back-story. I am happy to answer questions.
UDATE: Forgot to mention - KNOX was disabled by SuperSU.
Thanks for the instructions. OTA done. I am going to give the rest a shot later tonight. I wonder though if using the B5 recovery for the T900 wouldn't be safer. It was posted later in the same thread referenced above by TweakerL (post #344 pg35). Going to give that a shot vice using the P900 recovery. What do you think?
gbr357 said:
Thanks for the instructions. OTA done. I am going to give the rest a shot later tonight. I wonder though if using the B5 recovery for the T900 wouldn't be safer. It was posted later in the same thread referenced above by TweakerL (post #344 pg35). Going to give that a shot vice using the P900 recovery. What do you think?
Click to expand...
Click to collapse
I think I would have done that if I had known there was a B5 recovery image available. The guidance that I was given was to flash the B3 image from the P900. And that *did* work fine. Before there was a root flash for the T900, people were using the P900 root with success. Don't know that there is much difference. In the end, either way, you will end up with a B5 recovery image, as that is what Chainfire included in the T900 root file.
Well I got everything ready and instead of flashing the B5 image, I just flashed the root image from Chainfire. I didn't even think about what I was doing because that's such a normal process. Anyway, everything went off without a hitch. Rooted and rebooted in 10 seconds. Device now says custom however and I can't check for updates. That's fine though because all I wanted was root and I have ND4.
gbr357 said:
Well I got everything ready and instead of flashing the B5 image, I just flashed the root image from Chainfire. I didn't even think about what I was doing because that's such a normal process. Anyway, everything went off without a hitch. Rooted and rebooted in 10 seconds. Device now says custom however and I can't check for updates. That's fine though because all I wanted was root and I have ND4.
Click to expand...
Click to collapse
Which file from Chainfire did you flash? Was it CF-Auto-Root-v2wifi-v2wifixx-smt900.zip? For me, flashing that after OTAing to ND4 left me unable to boot. Maybe that got fixed in the past couple of day?
Yes it was that file off chainfire's site. Either something got fixed or the fact that I wasn't rooted before the OTA??
gbr357 said:
Yes it was that file off chainfire's site. Either something got fixed or the fact that I wasn't rooted before the OTA??
Click to expand...
Click to collapse
Well. technically I wasn't rooted either. I completely removed root with SuperSU.Is your recovery NB5?
JJMT said:
I opened the box on my new Galaxy Tab 12.2 SM-T900 today. I immediately rooted it with CF-Auto-Root-v2wifi-v2wifixx-smt900.zip. That worked fine. But before I rooted it there was a notification of an OTA update, so I unrooted and did the OTA update. That went fine as well. But then I attempted to root using the same file, odin got stuck at writing the cache. I tried it several times, but no go.
Having run out of time, I pulled the battery and set it aside to deal with tomorrow. It would be great if some one could point me to the correct image to flash to bring the device back to life.
As background, my last Samsung device was a Vibrant that I flashed repeatedly. Back then I didn't need to select a ROM, as there was a dev section full of them. Now I need a pointer to the correct firmware, and maybe some words of wisdom. I think the original firmware was NB5, and the OTA was ND2. I'm afraid that I was too excited to b quite organized enough to write this stuff down.
I'm uncertain whether I would prefer to flash back to the original and root, or flash to the newer firmware and wait and hope for the root issue to be resolved by Chainfire. Suggestions?
Click to expand...
Click to collapse
That's the problem I've been writing about for a week. The new OTA update (t900ueuand4) doesn't work with auto-root and crashes exactly where yours did.
---------- Post added at 11:28 PM ---------- Previous post was at 11:25 PM ----------
gbr357 said:
Yes it was that file off chainfire's site. Either something got fixed or the fact that I wasn't rooted before the OTA??
Click to expand...
Click to collapse
Can you give me the link for the new chainfire file that must have been re-written in the last 2 days
---------- Post added at 11:32 PM ---------- Previous post was at 11:28 PM ----------
gbr357 said:
Yes it was that file off chainfire's site. Either something got fixed or the fact that I wasn't rooted before the OTA??
Click to expand...
Click to collapse
Just re-downloaded the chainfire file and it's identical to the file I got 10 days ago dated May 10th. If you had success flashing it with the firmware t900ueuand4 installed at the time of rooting, then I'll give it a shot too.
JJMT said:
Yes. I am rooted and it says official. What's more, it checks for updates, although who knows what will happen when one shows up.
What I have is the ND4 firmware with the NB5 recovery. To get to this state:
1. OTA to ND4.
2. Boot into download mode. Flash the NB3 recovery. (P900XXUANB3-RecoveryImg.tar) It will reboot automatically.
3. Boot into download mode. Flash the root file. (CF-Auto-Root-v2wifi-v2wifixx-smt900.tar.md5). It will reboot automatically.
4. Boot into recovery mode. Wipe data/factory reset.
I believe at this point we are done. If you do this and it doesn't come up "official", then there must be something peculiar in the back-story. I am happy to answer questions.
UDATE: Forgot to mention - KNOX was disabled by SuperSU.
Click to expand...
Click to collapse
All I had to do, was stop after 3. Didn't require a factory reset. Everything is great
The same here. Used the Note 12 recovery mod to unbrick the tablet.
Flashed the CF-Auto-Root-v2wifi-v2wifixx-smt900.tar.md5 and it works. :good:
Now oor Samsung tablet pro 12.2 is rooted.
dodo99x said:
Try flashing the recovery from sm-p900 from this post, the one with the filename ending with "b3", then try to root agajn. Should work after that.
http://forum.xda-developers.com/showthread.php?p=50492301
If not, install Kies 3 and do an emergency restore. It will ask for your serial# and download the correct rom and flash it back to stock
Sent from my SM-P900 using Tapatalk
Click to expand...
Click to collapse
I ran into a similar issue except my device came up to an error regarding firmware upgrade failed, use kies to recover. I could not get this to work with kies 3. Searching the threads, I found your post. Worked beautifully. The failed attempt did trip Knox. Not sure I care.
Thanks!
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