Updated 2.22 - v4.5
Updated 1.25 - v4.1
- Added Asus Unlock Tool install and automated CWM flash
Updated 1.24 - v4
- Fixed an issue where people couldn't root, even on latest OTA. The problem was a copy of su in /system/bin (or in some cases /system/xbin) that had the wrong permissions. The fix is to remove it, repush, and set correct permissions on it.
Updated 1.12 - v3.1
- Support latest OTA (.11) and up! This should (hopefully) stick around a while because of the exploit used!
- Code clean up
- TIP: I would recommend just updating to .11.1 from here (make sure you download the large 300+MB file) and follow those directions and then try rooting. That is what I did and v4 worked on that just fine :)
Updated 1.12 - v3
- Added a line of code to (hopefully) fix failed rooting. This was likely caused by root failing and not undoing the code (my script has always done that on a failed root, I assume most people who are having problems now did it by hand before?)
Updated 1.10 - v2
- Supports ICS root method (as well as alt. root method, used on TF101 and Prime's on HC)
- Better busybox install
- Better su binary and Superuser app removal (checks /data for Superuser if you updated it in Market)
- More code enhancements and cleanup
- Added donate menu [because you guys love us :D]
Updated 1.4 - v1
- Name changed to PrimeTime (thanks xda user whose name I need to find!)
- Installs busybox upon rooting
- Fix bug where superuser and binary weren't removed
- Removes superuser.apk from /data/app if updated from Market
- Gives you sysro and sysrw (type that into a terminal/adb shell for quick rw/ro /system)
- Code enhancements and cleanup
Q. Do I need ADB?
A. Yes, but you don't need to set it up or anything. I have packaged it as part of the .exe and it should work just fine.
Q. Will I not be able to OTA?
A. No, rooting doesn't affect OTA whatsoever. It's actually reverse - OTA affects root. You will still get update notifications when updates drops, but you WILL loose root if you update. Download Voodoo Root Keeper to keep root if you take the next OTA!
The only way rooting would possibly affect an OTA is if, once rooted, you delete the certificates and modify the build.prop (and other things) that don't allow the OTAs to come through.
Q. Will this work on ICS and/or HC?
A. Yes, it now supports both. The ICS root method may work on HC Prime's and TF101's but I haven't gotten reports on that yet.
Q. The program doesn't do anything! WTF?!
A. Did you enable USB Debugging like the program told you too? [Settings > Developer Options] I hope you also installed the drivers, since the program told you to do that too. Once that is all set, the program will continue. If you're still having issues, please try this:
Originally Posted by Swiftks
Here's what I did to resolve the auto driver install by Windows 7, which does not allow for adb interface:
1) Turn USB Debugging ON (Settings -> Developer Options)
2) Allow installation of non-market apps (Settings -> Security -> Unknown Sources)
3) Uncheck Launch ASUS Sync (Settings -> Accounts & sync)
PC (Windows 7 x64):
4) Connect Prime to PC via USB & drivers automatically installed. *Note: Prime is only visible under "Portable Devices" in Device Manager.
5) Download the ViperMod .zip for Windows from the OP.
6) In Device Manager, right click on Transformer Prime TF201 (under portable devices), and choose Update Driver Software.
7) Choose Browse My Computer for Driver Software.
8) Choose Let Me Pick A List of Device Drivers on My Computer
9) If you see MTP USB Device on the next screen under ASUS Android MTP Device, choose it and click next. If you don't see this, then maybe try selecting "Have Disk" and pointing to the drivers folder in ViperMod (MTP file perhaps??).
10) Windows will install driver and and you should now also see a separate tier under Device Manager labeled, ASUS Android Devices -> ASUS Android Composite ADB Interface. If you see this you are good to go and can run the adb vipermod root process.
If you still need help with the driver install, this video tutorial
Q. Why add busybox and Superuser.apk to /system? I don't want that ****!
A. Sorry I can't please you. Busybox is important because it adds many commands to the device that it doesn't have (it doesn't have basic commands like 'copy' or 'grep' [a type of find]). When you install ROMs on other devices, you have busybox. It will be necessary to things I have coming down the pipe
As far as Superuser getting installed to /system, you'd have to go out of your way to uninstall it. In /data, it's easy to uninstall and if you master reset, root wouldn't work because there is no app, upon reboot, that would manage apps requesting root access.