Was that last part for me? I've already redownloaded the ota, verified md5, put US_epad-user-9.4.2.11.1 on the internal storage, and when it reboots, it starts with the blue bar at the bottom, then goes to the android with the red triangle.
[TOOL][Updated 5.9.12]viperMOD PrimeTime v4.6 | Auto Root/Unroot/Busybox/CMW Flash!
- Thread starter -viperboy-
- Start date
-
- Tags
- development
Was that last part for me? I've already redownloaded the ota, verified md5, put US_epad-user-9.4.2.11.1 on the internal storage, and when it reboots, it starts with the blue bar at the bottom, then goes to the android with the red triangle.
Welcome
That doesn't work, apparently.
Anyone that cannot root with PrimeTime v4, please come to my IRC channel now so I can try a few things with you. It's #viperROM on freenode. Here is a quick link for you...
http://webchat.freenode.net/
Don't forget the # before viperROM!
For everyone getting errors, please run these few things from adb and get me the output. Please paste it into pastebin.com and post the link:
Code:adb shell ls -l /system/bin ls -l /system/xbin
Thanks
here is mine: http://pastebin.com/MxbuEV0F
sorry for delay, had to get some sleep (quite some time difference between us)
Thanks to my IRC testers, I have a fix for all those who can't root! dr-mcq (not sure if that is his name on XDA or just IRC name) tested and confirmed working. He was on .11 and couldn't root, so I am having just a few more people test for me. Expect an update here shortly
EDIT: Bottom line of the rooting problem is su remaining in /system/bin with wrong perms. Just needed to delete it first before trying to put a fresh su in there. In some cases, there was a symlink of su in /system/xbin that was causing issues. Both of these have been addressed and the code to root using this latest method is much improved.
dr-mcq (not sure if that is his name on XDA or just IRC name) tested and confirmed working. He was on .11 and couldn't root, so I am having just a few more people test for me. Expect an update here shortly EDIT: Bottom line of the rooting problem is su remaining in /system/bin with wrong perms. Just needed to delete it first before trying to put a fresh su in there. In some cases, there was a symlink of su in /system/xbin that was causing issues. Both of these have been addressed and the code to root using this latest method is much improved.
Last edited:
Updated to v4.1! Confirmed with 3 testers in IRC that the latest method is working! The problem some people were having is that a copy of su remained in /system/bin (or sometimes /system/xbin) with the wrong permissions.
Because Asus' toolbox is pretty weak (toolbox holds all of the commands the tablet knows), there were some limitations that I had to overcome. Stock, you can't even do a copy or grep (a type of filter and find) so the method I was using was to "cat" su from /data/local to /system/bin (cat essentially reads su, but I direct the output into /system/bin - hence, creating the file and basically doing a copy). The problem was that if su already existed in /system/bin, it couldn't make the su file in /system/bin and su still didn't have the right permissions. While I could have just done a permission change (chmod), I find it better to remove, push a fresh su, and then set permissions. And we couldn't use busybox because that requires us to have root FIRST!
This is why you really want busybox and why PrimeTime installs it for you Makes everything alot easier and you will need it down the line anyway, especially if you want to use viperControl and other tools that are eventually coming
If you have any problems, please post here but I believe this to be very solid. I will eventually rewrite all of PrimeTime so it is more efficient. Instead of performing alot of the operations from within Windows, I will make all of that into scripts that run on the Prime. I am much better with bash scripting anyway and can do more with it, making the program more efficient and adding in error checking as well as some other enhancements.
As always, enjoy everyone
Because Asus' toolbox is pretty weak (toolbox holds all of the commands the tablet knows), there were some limitations that I had to overcome. Stock, you can't even do a copy or grep (a type of filter and find) so the method I was using was to "cat" su from /data/local to /system/bin (cat essentially reads su, but I direct the output into /system/bin - hence, creating the file and basically doing a copy). The problem was that if su already existed in /system/bin, it couldn't make the su file in /system/bin and su still didn't have the right permissions. While I could have just done a permission change (chmod), I find it better to remove, push a fresh su, and then set permissions. And we couldn't use busybox because that requires us to have root FIRST!
This is why you really want busybox and why PrimeTime installs it for you
Makes everything alot easier and you will need it down the line anyway, especially if you want to use viperControl and other tools that are eventually coming If you have any problems, please post here but I believe this to be very solid. I will eventually rewrite all of PrimeTime so it is more efficient. Instead of performing alot of the operations from within Windows, I will make all of that into scripts that run on the Prime. I am much better with bash scripting anyway and can do more with it, making the program more efficient and adding in error checking as well as some other enhancements.
As always, enjoy everyone
Last edited:
Fixed. Thanks again for testing and THANK YOU VERY MUCH for your donation
very kind of you, sir.
You were pretty damn close. I just explained in more technical detail lol the problem that people were having was wrong perms on /system/bin/su (and in rare cases, /system/xbin/su was symlinked and causing issues too).
I figured after I read your OP I'd give it a try. Plus I hate ADB work I can never get the file system to do what I want. So it was all or nothing going off on a hunch.
I knew it was the su being stuck in there. I did some testing when ecooce was uhhh not allowed here on the epic and made some personal roms and themes of my own.
Epicurean roms until I got my Photon.
Minor Derail
BTW have you talked to Shabby or JokerSaxx about helping with the bootloader issue on the Photon.
I'm not sure if you do much kernel work but once we unlock there is no more 4G the wimax keys won't pass and I think Joker figured out it was a issue in the kernel
Last edited:
I know zilch about the Photon, man. I wouldn't mind getting one to dev on, but I know nothing about it. Sorry!
ViperMod 4.1 won't work for me
Hello,
First sorry for my bad english as i'm french newbie...
First i've rooted my prime under ww 9.2.4.7 and it works perfect. Badly i've updated with OTA WW 9.4.2.11 without rootkeeping
I just try your vipermod 4.1 but no luck with it, as the prompy box said "cannot oinstall" etc...
I have checked the drivers numerous time, and tried on various pc under seven or xp.
Could you help me please ???
Thanks in advance
Hello,
First sorry for my bad english as i'm french newbie...
First i've rooted my prime under ww 9.2.4.7 and it works perfect. Badly i've updated with OTA WW 9.4.2.11 without rootkeeping
I just try your vipermod 4.1 but no luck with it, as the prompy box said "cannot oinstall" etc...
I have checked the drivers numerous time, and tried on various pc under seven or xp.
Could you help me please ???
Thanks in advance
You might add to the instructions to not just download rootkeeper, but actually use it to back up root as well. A few people seemed to have gotten tripped up assuming rootkeeper had them covered without any action after installing or simply opening the app.
I ran eveything but I dont think it did anything...shoudl it reboot on its own after root script is done, or do I have to reboot it?
I can "adb devices" and see the ATP so I am guessing I dont need to load teh drivers....?
EDIT ** It just spits out " adb an unrecognized command"
I have USB Debugging on and I have killed Asus Sync, and Splash top
I can "adb devices" and see the ATP so I am guessing I dont need to load teh drivers....?
EDIT ** It just spits out " adb an unrecognized command"
I have USB Debugging on and I have killed Asus Sync, and Splash top
Last edited:
Hello,
First sorry for my bad english as i'm french newbie...
First i've rooted my prime under ww 9.2.4.7 and it works perfect. Badly i've updated with OTA WW 9.4.2.11 without rootkeeping
I just try your vipermod 4.1 but no luck with it, as the prompy box said "cannot oinstall" etc...
I have checked the drivers numerous time, and tried on various pc under seven or xp.
Could you help me please ???
Thanks in advance
Can you get me a full log of where and what the erros are?
no Linux version yet, sir. I will try to get to that tonight. And no, you won't end up with a brick.
I will edit it, but I would figure it's common sense to open up an app you downloaded to see what it says...
It should reboot for you. If it's giving you an error about adb, are you sure you extracted the files all to one place? You need to extract the whole .zip to a folder and run the .exe, you can't just run the .exe itself.
Sent from my SPH-D710 using Tapatalk
All set now.
once I unzipped the .zip over to a folder it worked fine...my bad!
Thanks, cant wait to see what comes for this device in the future!
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
394
I do not have a TF101 anymore, but it has been reported that you can root the latest ICS update via option 1. Do so at your own risk! And PLEASE don't flash recovery if you're not on a Prime. That option is ONLY for TF201's!!
THIS WILL NOT ROOT .21 AT THIS TIME!!
Introducing viperMOD PrimeTime! An automated rooting program for your Asus Transformer Prime TF201 (ICS or HC supported) and the Asus Transformer TF101. It is very simple and easy to use with extra features that other root methods don't have. Works on Prime's that lost root with the ICS OTA! Now, here is how it works...
- Download the .zip
- Plug in your Transformer and make sure to install the drivers located in the included .zip (unless you can already adb into your device, then no need for drivers)
- Kill Asus Sync and Splashtop! - very important!!
- Make sure you have NO OTHER ANDROID DEVICES connected via USB!
- If on Linux, you may need to do "chmod a+x /path/to/primetime/primetime.sh" (no quotes)
- Run the viperMOD PrimeTime.exe and choose an option.
- After rooting, download OTA Root Keeper from the Market!
- ???
- Profit?
It's as simple as that! I have tested this about 30 times (both rooting and unrooting) and it works just fine! I would HIGHLY recommend downloading Voodoo Root Keeper!! Any issues or questions, please feel free to post here! Enjoy your rooted Prime
Things you should NOT do!
- Try to root with the Transformer in the dock
- Use a USB extension cable
- Not download OTA Root Keeper
- Not follow directions
Updated 5.9.12 - v4.6
- Replaced OLD CWM recovery with latest TWRP 2.1
- Fixed sparkym3's donate link
HC root based on NachoRoot by jcase and TeamAndIRC.
ICS root based on TPSparkyRoot by sparkym3.
Latest ICS root based on https://github.com/saurik/mempodroid by Saurik.
Download
Windows (v4.6): Main Link, Mirror 1, Mirror 2
Linux/Unix (v4.1 - update coming soon!): http://bit.ly/PrimeTime_v4_1_Linux68ChangelogCode:[B][I][U][SIZE="4"][COLOR="Red"]Updated 2.22 - v4.5[/COLOR][/SIZE][/U][/I][/B] [LIST] [*][*]Added Asus Unlock Tool install and automated CWM flash [/LIST] [B][I][U][SIZE="4"][COLOR="Red"]Updated 1.25 - v4.1[/COLOR][/SIZE][/U][/I][/B] [LIST] [*]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. [/LIST] [B][I][U][SIZE="4"][COLOR="Red"]Updated 1.24 - v4[/COLOR][/SIZE][/U][/I][/B] [LIST] [*]Support latest OTA (.11) and up! This should (hopefully) stick around a while because of the exploit used! [*]Code clean up [*][B]TIP:[/B] I would recommend just updating to .11.1 from [URL="http://xdaforums.com/showthread.php?t=1452933"]here[/URL] (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 :) [/LIST] [B][I][U][SIZE="4"][COLOR="Red"]Updated 1.22[/COLOR][/SIZE][/U][/I][/B] [LIST] [*]Added Linux/Unix version [/LIST] [B][I][U][SIZE="4"][COLOR="Red"]Updated 1.12 - v3.1[/COLOR][/SIZE][/U][/I][/B] [LIST] [*]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?) [/LIST] [B][I][U][SIZE="4"][COLOR="Red"]Updated 1.12 - v3[/COLOR][/SIZE][/U][/I][/B] [LIST] [*]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] [/LIST] [B][I][U][SIZE="4"][COLOR="Red"]Updated 1.10 - v2[/COLOR][/SIZE][/U][/I][/B] [LIST] [*]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 [/LIST] [B][I][U][SIZE="4"][COLOR="Red"]Updated 1.4 - v1[/COLOR][/SIZE][/U][/I][/B] [list] [*]Initial Release [/list]
FAQ
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:
If you still need help with the driver install, this video tutorial might help.
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.5Updated to v4.5! Installs the Asus Unlock Tool (you will get an error if you already have it installed, ignore it) and automatically flashes CWM! I've had 3 reports of this working, you guys should have no issues!
I do intend to update to v5 and overhaul the entire program. Do things a little bit better and more efficiently. But that won't be for a little bit, as everything is working. I just want to do it since it's a little bit messy as it is right now.
Enjoy5Updated to v3! Get your automated ICS root on!! Please post feedback so that I know how it's working and PLEASE let me know if you're on ICS or HC (build number, please!). If someone has a good write-up or post with driver install info, that would be great. I would like to put it in the 2nd post for users who need help!5
Firts I downloaded the unlock tool here.
http://xdaforums.com/showthread.php?t=1510760
Than you have to set up ADB.
See here.
http://www.youtube.com/watch?v=ZY4KSrgi-rE
After that you install CWM with method one from this thread.
http://xdaforums.com/showthread.php?t=1576937
and than flah root files from this thread
http://goo-inside.me/superuser/Super...ghi-signed.zip
And than you are finished and rooted.
