[Q]Major issues with rooting my prime - Asus Eee Pad Transformer Prime

So i have been trying to root my tprime for about a couple days now and i really need some help. Im trying to use Vipers tool (option 1), however every time i try to use it it just gets stuck on "daemon started successfully". Every now and then the script will flip out and tell me that it isnt connected, but that is pretty rare. I'm on 9.4.2.15, have debugging checked, no lockscreen (saw it helps somewhere), device manager recognizes it as "asus transformer prime ADB interface". I have tried 2 different scripts and restarted both my tablet and computer (windows 7 x64) several times. I am at a total loss about what to do next. Any help would be great =).
Also i have deleted splashtop from my computer and made sure that and asussync are not running on my tablet

---

lotsofllamas said:
So i have been trying to root my tprime for about a couple days now and i really need some help. Im trying to use Vipers tool (option 1), however every time i try to use it it just gets stuck on "daemon started successfully". Every now and then the script will flip out and tell me that it isnt connected, but that is pretty rare. I'm on 9.4.2.15, have debugging checked, no lockscreen (saw it helps somewhere), device manager recognizes it as "asus transformer prime ADB interface". I have tried 2 different scripts and restarted both my tablet and computer (windows 7 x64) several times. I am at a total loss about what to do next. Any help would be great =).
Also i have deleted splashtop from my computer and made sure that and asussync are not running on my tablet
Click to expand...
Click to collapse
Update your ADB drivers in device manager with the following
http://forum.xda-developers.com/showthread.php?t=1426502
Make sure USB Debugging is enabled within your TFP's settings (Developer options)
If that does not work then you have done something wrong.
Have a nice day

---

that didnt work >< but i have no idea where i couldve done something wrong...especially since i have had to re-do most steps anyway

---

lotsofllamas said:
that didnt work >< but i have no idea where i couldve done something wrong...especially since i have had to re-do most steps anyway
Click to expand...
Click to collapse
Well if you really want this, I would suggest the following:
We want to verify that your devices is correctly connect with ADB,(assuming you dont have adb set up) so lets set up Android SDK (which is good to do anyway).
http://developer.android.com/sdk/index.html
Download the .exe. Run it. It should create a folder in a location of your choosing, named something like "android-sdk". Browse to that folder, then to the 'tools' sub folder and run the SDK manager, install packages.
Next open the Command Prompt.
For example sake, lets say the location of your AndroidSDK is in the path
Code:
C://users/mike/android-sdk-win/
(Not sure what the sdk folder is actually called)
In the command prompt, enter
Code:
cd /users/mike/android-sdk-win/tools
(again replacing the location and name with the correct ones)
This will change the cmd location to the tools folder.
Then enter
Code:
adb devices
It will then list a device if one exists, if not then your adb drivers are probably not installed correctly.
If you need me to clear anything up, let me know

---

you were right i wasnt connected, im not quite sure how im doing anything wrong
installed the drives said to
unzipped
went into device manager -update driver software -browse -lemme pick -have disk-android_winusb -ok -comes up as ADB interface -next -finishes installing
try to run viperMOD PrimeTime v4.5 (option 1)
stalls on daemon started successfully
i figure if i go into as much detail as possible maybe this can get solved =(

---

lotsofllamas said:
you were right i wasnt connected, im not quite sure how im doing anything wrong
installed the drives said to
unzipped
went into device manager -update driver software -browse -lemme pick -have disk-android_winusb -ok -comes up as ADB interface -next -finishes installing
try to run viperMOD PrimeTime v4.5 (option 1)
stalls on daemon started successfully
i figure if i go into as much detail as possible maybe this can get solved =(
Click to expand...
Click to collapse
Hmm, I am really not sure. Sounds like you have done everything right.
adb devices is showing no devices which means viperMOD will not work.
When you plug the prime into your computer, on your prime,go to the notification bar and hit on the usb notification (not pc sync, the usb one), and when the settings menu opens up, which box is checked? MTP or PTP? if ones not working, try the other
if all else fails,
try it on another computer maybe?

---

lotsofllamas said:
you were right i wasnt connected, im not quite sure how im doing anything wrong
installed the drives said to
unzipped
went into device manager -update driver software -browse -lemme pick -have disk-android_winusb -ok -comes up as ADB interface -next -finishes installing
try to run viperMOD PrimeTime v4.5 (option 1)
stalls on daemon started successfully
i figure if i go into as much detail as possible maybe this can get solved =(
Click to expand...
Click to collapse
I rooted last night on latest version of primetime. I used a very old computer to do it. I had it stall on daemon started successfully at first also. I just unplugged the prime connection to PC and plugged it in again. then restarted the primetime program. worked for me. seems like everything you did is right. I guess sometimes the program acts funny. try to run and if it stalls just unplug connection to PC. close out app. then plug back up. open program and try again. it'll catch. I notice it'll stall if you keep trying to root after repeated ffailed attempts. close out the exe. then try again.

---

demandarin said:
I rooted last night on latest version of primetime. I used a very old computer to do it. I had it stall on daemon started successfully at first also. I just unplugged the prime connection to PC and plugged it in again. then restarted the primetime program. worked for me. seems like everything you did is right. I guess sometimes the program acts funny. try to run and if it stalls just unplug connection to PC. close out app. then plug back up. open program and try again. it'll catch. I notice it'll stall if you keep trying to root after repeated ffailed attempts. close out the exe. then try again.
Click to expand...
Click to collapse
It has nothing to do with the Prime time. As he has said, he got the android sdk setup and confirmed that "adb devices" shows no device, which lends itself to his device or drivers not being installed correctly.
Again, nothing to do with vipermod
everything to do with how he is connected (and i think he tried 'unplugging and replugging')
-------------------------------------
Lets Try this. The following may look intimidating but its very straight forward and after its done you will be more adept at adb and everything else (and hopefully be rooted)
1) Start=> Right Click "My Computer" => Properties => Advance System Settings => Advanced Tab=> Environmental Variables
---In the top box, there should be a "PATH" variable, if so hit edit and go to the end of whatever is there (make sure there is a ';' after whatever is there) and type the path to your android SDK tools folder (same folder you browsed to before in cmd)
My PATH Field looks like this
Code:
C:\Users\Mike\Downloads\android-sdk_r16-windows\android-sdk-windows\platform-tools\; C:\Program Files\Java\jre7\bin
(I also have java linked, this is okay if you do not)
If there is no PATH, just hit 'new'
The above allows you to, from command prompt, type "adb" from anywhere (ie, you dont have to be in the sdk folder which is nice)
EDIT: FLAW: the following app required root womp. I guess keep trying with the USB{
-Go to Device Manager, Uninstall Your TFP, before hitting refresh go to add new devices and select the drivers and what not.
-I will continue to try to think of an alternate method.
}
2)Download and Install this on your prime (NOTE THIS STEP REQUIRES BOTH PRIME AND PC TO BE ON SAME NETWORK)
-This method is ADB over wireless, so you dont need USB to be connected (infact just unplug it for this)
https://market.android.com/details?...251bGwsMSwyLDEsInNpaXIuZXMuYWRiV2lyZWxlc3MiXQ..
Open the app and enable it. Note the "IP: port"
type in your command prompt (again if you did step 1, you can do this from anywhere)
Code:
adb connect <yourip:port>
your ip and port should be listed in that app
=> after that, try
Code:
adb devices
It should be there! this allowed you to bypass usb issues. I dont think you can use vipermod, but there is a more manual method we can use
3) Memphroid Root
(information taken from link below)
http://forum.xda-developers.com/showthread.php?t=1461736
memphroid binary
su binary
save both those files somewhere.. for example sake, make it your desktop in a folder called 'memphroid'
Open command prompt and change to the folder memphroid on your desktop
Code:
cd Desktop/memphroid
(the above assumes command prompt defaults at c:\Users\<yourname>\. if not just type in "dir" to get a list of directories that you can cd to)
you are now in the memphroid folder
assuming you did step 2 correct, you should have already connected with "adb connect"
now enter the following in cmd
Code:
adb push mempodroid /data/local
adb push su /data/local
adb shell
One line at a time, the first 2 push the files to the correct locations, the third one puts you into the 'shell' (basically terminal) of your prime (you should see a # now before where you type)
Then enter
Code:
chmod 777 /data/local/mempodroid
/data/local/mempodroid 0xd9ec 0xaf47 sh
Copy all of that and just paste it at once (i think its both at once, not one line at a time)
then type
Code:
mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
And then here is the rest from that thread. I would just do all of the following except the first two lines starting with 'rm' because you havent rooted before
** IF you have previously rooted your Prime, run the following two commands. They may throw an error that the file a file was not found.
rm /system/bin/su
rm /system/xbin/su
cat /data/local/su > /system/xbin/su
chown 0.0 /system/xbin/su
chmod 06755 /system/xbin/su
rm /data/local/mempodroid
rm /data/local/su
exit
exit
adb reboot
After your Transformer Prime comes up, install Superuser from android market.
Click to expand...
Click to collapse
look to that thread linked for reference. if you neeed anything clarified or help, just post here. Please read my post carefully, following the step. I tried to be as clear as possible. I have never done the memphroid root before but it looks easy enough
Please hit 'Thanks' button, as I have taken the time to help

---

Still not able to get root...just tried Debugfs automated root tool and it stalled at "daemon started successfully" im seriously stumped here...