NOTE: If you are running JB (Android version 4.1.x), the following root exploits below will not work; they were designed for ICS. You'll have to wait for a new root exploit for JB. If you already rooted on ICS AND have a unlocked bootloader and recovery, you can safely take the JB update. You will lose root but not your custom recovery. Therefore, after you are on JB, you can flash a rooted stock ROM to get your root back.
Others have had success with this too and report that after root, you may need to manually run the Superuser app once.
The above gets you root access to the filesystem, but if you want to flash custom recoveries, kernels, ROMs, etc, you'll need to unlock the bootloader. This site details how:
On my win7 x64 PC, when I first plugged in the tablet via the supplied proprietary USB cable, my computer was able to install the correct drivers. I did not need to install the drivers that was included on that root thread.
Only setting I actually needed to change was to allow "Unknown Sources" (the setting that allows you to sideload 3rd party apps). USB debugging was on by default.
Ran the .BAT file, chose option 1, pressed enter a couple of times after each device restart, and I was rooted. Pretty easy.
As for unlocking the bootloader, the instructions on the linked site could not be clearer. Unlocked in a couple of minutes.
Device(s): HTC Evo 4g LTE, HTC 3vo(no longer have), HTC EVO (not activated)
Carrier: Sprint
Thanks: 20,674
Thanked 11,007 Times in 7,153 Posts
oh nice. gonna root this baby tonight.
__________________ “The Guide is definitive. Reality is frequently inaccurate.”.......Hitchhiker's Guide to the Universe
“I seldom end up where I wanted to go, but almost always end up where I need to be.”.......Douglas Adams
Device(s): HTC Evo 4g LTE, HTC 3vo(no longer have), HTC EVO (not activated)
Carrier: Sprint
Thanks: 20,674
Thanked 11,007 Times in 7,153 Posts
well i have been having the hardest time trying to get the drivers to install properly on my laptop. later tonight or tomorrow i will try it on my desktop.
As for unlocking the bootloader, the instructions on the linked site could not be clearer. Unlocked in a couple of minutes.
I hope HTC takes note of Asus' method. I have yet to unlock my bootloader (I'm mostly waiting for official Jelly Bean), but I was relieved to see that Asus made an app to unlock their bootloader and it's easy as pie to run.
I hope HTC takes note of Asus' method. I have yet to unlock my bootloader (I'm mostly waiting for official Jelly Bean), but I was relieved to see that Asus made an app to unlock their bootloader and it's easy as pie to run.
Yea, that's one of the reasons I love Asus (they also make kick-ass motherboards!)
Had a minor issue with the drivers because it didn't seem to like my nexus 7 asus drivers, but was easily fixed. Custom rom list seems kinda small at the moment so I guess I'll hold off on unlocking.
__________________
If something needs attention, Report it .
If someone helped you, hit to show it.
Rooting now, deciding on whether I want to unlock or not - I just got it so I might want to keep the warranty around especially as it seems that when I am typing typing stuff sometimes it seems to automagically move the cursor or else delete some of what I have typed....
Rooting now, deciding on whether I want to unlock or not - I just got it so I might want to keep the warranty around especially as it seems that when I am typing typing stuff sometimes it seems to automagically move the cursor or else delete some of what I have typed....
accidental brushes on the touchpad maybe? You can try disabling it for a while and see if that 'fixes' things. button to disable it is the 4th button from the left, top row.
Definitely not that b/c Every time I have noticed it I am holding both corners of the lapdock. It seems to be happening less and less now but ...it's as if the entire lapdock is wired for touch capabilities lol...
Step 2 - Rooting...
For this step, ignore any error messages that say "File not found"
Unable to chmod /data/local/debugfs: No such file or directory
/system/bin/sh: can't open /data/local/debugfsinput: No such file or directory
rm failed for /data/local/tmp, Permission denied
failed on '/data/local/tmp.bak' - No such file or directory
rm failed for /data/local/su, No such file or directory
rm failed for /data/local/debugfs, No such file or directory
rm failed for /data/local/debugfsinput, No such file or directory
Rebooting...
Once your devices has finished restarting,
Press any key to continue . . .
Code:
Rooting FAILED! You may want to try running this tool again.
Your device region may not be supported if you see this message again.
Press any key to continue . . .
This has happened to me every time I have tried to root with the Infinity Root files.
Using DebugfxRoot_Generic_v2.3, I inisitally get the following:
Code:
Step 1 - Pushing files...
failed to copy 'debugfs' to '/data/local//debugfs': Permission denied
failed to copy 'su' to '/data/local//su': Permission denied
failed to copy 'debugfsinput' to '/data/local//debugfsinput': Permission denied
failed on '/data/local/tmp' - Permission denied
link failed File exists
Rebooting...
Once your devices has finished restarting,
Press any key to continue . . .
After Infinity reboots, however, I get this (same as before):
Code:
Step 2 - Rooting...
For this step, ignore any error messages that say "File not found"
Unable to chmod /data/local/debugfs: No such file or directory
/system/bin/sh: can't open /data/local/debugfsinput: No such file or directory
rm failed for /data/local/tmp, Permission denied
failed on '/data/local/tmp.bak' - No such file or directory
rm failed for /data/local/su, No such file or directory
rm failed for /data/local/debugfs, No such file or directory
rm failed for /data/local/debugfsinput, No such file or directory
Rebooting...
Once your devices has finished restarting,
Press any key to continue . . .
And finally,
Code:
Testing superuser...
Yields
A big blank screen. I'm gonna run it manually and see what happens and why.
Mind you both of these methods were ICS specific, but I thought I would try them out to see if we could. Alas, we cannot. At XDA one user reported that roting prior to JB should be fine, but I was already rooted and lost root when JB was installed. I'm now looking for new information.
New Asus infinity TF700T firmware update rejected this root method
As new firmware update arrives a few days ago (10/07/2012), this method doesn't work on the TF700T. I have error message after the last reboot right after [testing superuser] saying.
[Rooting Failed! You may want to try running this tool again. Your device region may not be supported if you see this message again. ]
It used to work before but not now. Other than reverting back to previous ICS, is there any other way to adapt to new firmware update?
Thanks.