[ROOT][TOOL]Debugfs automated root [09/18/2012]

---

This tool will root your device based on the debugfs root method developed by miloj.

Just download and unzip everything into a directory; then run RootDebugfs.bat from that directory (if you do not currently have the device drivers for your transformer, they are attached to this post, please install them, please use them to install your device before attempting the process).

Neither ADB nor the SDK need to be installed as all needed files are included in the attachments below (though it won't hurt anything if they are).


Helpful tip:
Make sure no other Android device is connected to your PC


It should look familiar since I took PrimeTime and gutted it, only keeping the menu options. Thanks to viperboy for that.
Original post is in the TF300 thread, http://forum.xda-developers.com/show....php?t=1704209


UPDATE 6/12/2012:
v1.1 - Added donation link for miloj
v1.2 - Fixed bug that caused it to stop while doing "debugfs", to cancel press Ctrl+c
v1.3 - Fixed bug where the id is not returned from the su test
v1.4 - Fixed bug introduced with v1.3
v1.5 - Fixed bug where you don't have to push the apk before calling install

6/13/2012
v1.6 - Fixed messaging (this is a cosmetic change)
v1.7 - Added a remove call on su prior to rooting for those who had root previously and it not longer works
v1.8 - Change the octal permissions to be 6755 instead of 4755

7/2/2012
v1.9 - Update superuser app and binary to the latest version available
XDA uploads are not working currently so I have uploaded the new version to here for now
https://skydrive.live.com/redir?resi...5E3CE960E5!221

8/5/2012
v2.0 - Updated to include a kill for Asus sync as that seemed to be the biggest issue.
I have also made it more generic so that it can root more devices with the same util. This is done by scanning for the system partition automatically, thanks to rightonred for that suggestion. With the attachment labeled "generic" I have removed all asus references and drivers since they were causing issues with me being able to attach the zip to xda. Anybody who needs the drivers can download them from asus or from another xda post.
v2.1 - Added a pause while waiting for the device to restart to alleviate that nuisance.
v2.2 - Added message to ignore "File not found" message when trying to delete old su versions. Also updated message with the generic locations of settings on the tablet.

8/12/2012
v2.3 - Update su binary file (hopefully it may help some of the people with superuser app issues)

ASUS drivers can be downloaded from the ASUS site but some are not provided other than through the sync install. I have extracted out the drivers from that sync install and attached them to this post. These drivers will support most of the Asus Eee Pad family including TF101, TF201, TF300, TF700, ME171(MeMO), A66(Padfone), SL101(Slider), and a couple others.


No longer need a PadFone specific root util as the generic one should work for it as well.

Here is a version I put together for the Gallexy SII (but the generic one attached here should work fine)
http://forum.xda-developers.com/show...87&postcount=3

Latest Supported Versions:
v9.2.1.27 for the TF101 (ICS 4.0.3)
v9.2.2.6 for the TF101G (ICS 4.0.3) (3G version)

v9.4.2.28 for the TF201 (ICS 4.0.3)

v9.4.3.30 for the TF300T (ICS 4.0.3)
v9.4.4.40 for the TF300TG (ICS 4.0.3) (3G version)

v9.4.5.30 for the TF700T (ICS 4.0.3)

v9.18.8.41 for the PadFone (ICS 4.0.3)

These are the latest supported versions as far as I know, if I get any further input I will update this post.


Reported UNsupported Versions
v10.4.2.15 for the TF201 (JB 4.1.1)
v10.4.2.9 for the TF300T (JB 4.1.1)
v10.4.4.16 for the TF700T (JB 4.1.1)
v9.20.1.22 for the PadFone (ICS 4.0.4)

any one confirmed? what's the risk, if it doesnt work?

Currently in progress .... sitting at:

Step 2 - Rooting...
debugfs 1.42 (29-Nov-2011)
debugfs: (shows a flashing cursor)

My Prime has rebooted but still sitting at the above. Is this normal?

OK, now I'm getting nervous .... Anybody wanna help a Noob?

Originally Posted by Aaronneal

any one confirmed? what's the risk, if it doesnt work?

The risk if it doesn't would should just be that you wouldn't have root.

We already have confirmation that the method works (so there should be no risk there). We just don't have confirmation that I didn't make a typo or other mistake when putting it all together.

Originally Posted by Gremlin001

Currently in progress .... sitting at:

Step 2 - Rooting...
debugfs 1.42 (29-Nov-2011)
debugfs: (shows a flashing cursor)

My Prime has rebooted but still sitting at the above. Is this normal?

How long has it been sitting there?

This is one of the points where I wasn't sure about since I had to pass input to debugfs through adb.

Originally Posted by sparkym3

How long has it been sitting there?

This is one of the points where I wasn't sure about since I had to pass input to debugfs through adb.

Currently 7 minutes...

If my memory serves me correctly, this is the point where it can take 10 - 15 minutes. Is that correct?

---------- Post added at 01:27 PM ---------- Previous post was at 01:12 PM ----------

Nope ... left it stalled at "debugfs:" for 20 minutes.

Ctrl-C'd out of the batch file. Doesn't seem to have hurt the Prime.

Originally Posted by Gremlin001

Currently 7 minutes...

If my memory serves me correctly, this is the point where it can take 10 - 15 minutes. Is that correct?

---------- Post added at 01:27 PM ---------- Previous post was at 01:12 PM ----------

Nope ... left it stalled at "debugfs:" for 20 minutes.

Ctrl-C'd out of the batch file. Doesn't seem to have hurt the Prime.

Thats what I was going to tell you. I have an update that I will put up. just forgot to put the absolute location. Please stand by.

Standing by ...

Now?

Now?

How 'bout now??

Maybe now?

Please try again. New version is v1.2