Database Info

****ROOT EVO After July 1 OTA Update

I tried every method, read every thread in every forum in an effort to root my EVO. Nothing worked. I was driving myself mad and spending tons of time. I Eventually I came across a post which directed me to XDA Developers Thread ---==={ROOT GUIDE}===--- | 1.47.651.1 ROOT, post 579 by SharkUW . I have used this on my own phone and I don't see a reason why it wouldn't work. I modified some of the instructions to make it clearer. The instructions may not be exact, and there is some seat-of-the-pants involved, but I got it to work. Use it at your own risk.
Prerequisites (follow in order)
Android-SDK developers program. I loaded it to C:
JAVA SE Development (use correct bit – 32 or 64). loaded in C:
Microsoft .NET Framework V 4.0
Reboot your phone and do a factory reset. Erase everything
Set phone to Charge Only and USB debugging
Open the stock browser and sign-in with your PCS phone number. Leave running.
Shutdown the phone, then restart
Make sure ADB is functional on your computer. You should be able to "adb shell" (confirming adb is working, exit shell if you're in it).
Extract the Do_root.zip (link below) and place all these files into the SAME folder as adb.exe. I have not included the appropriate PC36IMG.zip. Get it here. http://forum.xda-developers.com/showthread.php?t=701835 Leave the name as "eng-PC36IMG.zip". Place that in the SAME directory as well as the .zip.
Open a command prompt on your computer. point directory to Android-SDK directory\tools and a list will come up… click on "root.bat” and click RUN.
If it hangs for more than 30 seconds with the browser ****, CTRL+C, yes to kill the bat and just run it again.
Follow the directions. Your phone is going to reboot. It is then going to do a little **** and reboot into the boot loader. Keep track of the Command screen and wait because some steps take a while and there is no way of telling if it’s working. Nothing lasted more than 5 minutes. Eventually it will be in a "bootloader" and ask if you want to reboot. Say Yes with a Volume UP.
The .bat is now done. You have root. (not sure if next part is true) You now need a custom recovery to flash a proper ROM beyond the scope of this guide.
In original instructions but I’ve found the following Recovery step and code is not necessary: Now take the last step and flash the recovery.img that will already be on the root of your sdcard. To do this, after the PC36IMG flash:
Code:
adb shell
cat /sdcard/flash_image > /data/flash_image
chmod 755 /data/flash_image
/data/flash_image recovery /sdcard/recovery.img
To check for root do ADB Shell and should get #.
If you're all advancedy you can put on a different recovery image.
IMPORTANT If you get a message here about "not writing bad block", flash it again until you get 0 errors. I don't know how common it is, but personally my recovery has issues with flashing. Do NOT let that be a bad flash.
Attached Files
do_root.zip (4.07 MB, 49 views)
________________________________________
Last edited by SharkUW; 7th July 2010 at 01:06 AM.

Going to try it tomorrow and hope it works. Thanks

Where are the attached files?

Can't find the do_root.zip file. Seems there is no attachment, please re-post. Thanks.

I tried to attach the do_root.zip file and a link to Toast 2 file. If that doesn't work, go to the referenced post #579 here: http://forum.xda-developers.com/showthread.php?t=718889&page=58.

Have you tried this SimpleRoot? I just did it, and it worked flawlessly.

Vivix729 said:
Have you tried this SimpleRoot? I just did it, and it worked flawlessly.
Click to expand...
Click to collapse
Simpleroot ftw.

mattrb said:
Simpleroot ftw.
Click to expand...
Click to collapse
QFT. I did simple root (I still setup adb and ensured it was working first) and then flashed the rooted Stock 1.47 ROM in about 40 min. I think most people that are running into issues with Simpleroot do not have adb setup properly or they did something inadvertently and need to clear out the files/cache and need to start over from scratch.

gmanvbva said:
QFT. I did simple root (I still setup adb and ensured it was working first) and then flashed the rooted Stock 1.47 ROM in about 40 min. I think most people that are running into issues with Simpleroot do not have adb setup properly or they did something inadvertently and need to clear out the files/cache and need to start over from scratch.
Click to expand...
Click to collapse
I did simple root and it worked fine too. I don't think the issue is adb being setup since he has an adb file in his download.

Update from a few days ago.
Just got a new SDHC card and simpleroot worked. The SDHC that came with my phone died. I placed a spare in there that was a 2gd regular micro and Hboot would not ready the IMG for nothing.
If simple root is not working then it's the Sh!tty card acting up.
Happy ending for me.

I just got my phone yesterday did the ota simpleroot and seems like it worked fine
but now i dont know what to do next
to get custom roms or froyo 2.2 or anything lol

Awesome post |OP|.
My desktop is Windows 7 x64 and doesn't play nicely with the standard tools.
I was forced to adapt your root.bat script to an OSX friendly BASH script.
The only requirement is that you download the android SDK from developer.android.com/sdk/index.html (apparently, I'm too new to post links).
The steps I took to get root:
Unzip the android SDK
follow |OP|'s instructions, unzipping the contens of do_root into [sdk-root]/tools/
unzip the attached bash script to the [sdk-root]/tools/
run my bash script from the [sdk-root] folder instead of root.bat - type "./root.sh" without the double-quotes
Grab a copy of Froyo while your phone is being rooted

The easiest 1.47.651.1 root+nand unlock you'll ever see without a gui (Updated)

Make sure your battery has a decent amount of charge in it, you don't want to run out of juice in the middle of this.
You will need to have the android sdk installed, as you will need to use the adb tool.
Windows users will need to install HTC Sync in order to get the usb driver for the phone installed.
Part 1: In which we find that the Evo spreads easier than a Thai whore during tourist season
Code:
adb shell "rm /data/local/rights/mid.txt"
adb shell "ln -s /dev/mtd/mtd1 /data/local/rights/mid.txt"
adb reboot
Part 2: In which we find that engineers have no personality, but they make one hell of a bootloader
Put the files from Toast's Part 2, for nand unlock onto the sdcard (PC36IMG.zip, mtd-eng.img, recovery.img, flash_image)
then (after making sure the sdcard is remounted to the phone if you used disk mode to xfer the files):
Code:
adb shell "cat /sdcard/flash_image > /data/local/rights/flash_image"
adb shell "chmod 755 /data/local/rights/flash_image"
adb shell "/data/local/rights/flash_image misc /sdcard/mtd-eng.img"
adb reboot bootloader
When asked if you want to update, say yes. Relax for a while, the update takes some time.
When the phone eventually boots back up:
Part 3: In which I find the whore, and make her install a custom recovery
Code:
adb shell "cat /sdcard/flash_image > /data/flash_image"
adb shell "chmod 755 /data/flash_image"
adb shell "/data/flash_image recovery /sdcard/recovery.img"
After this you should be fully rooted with nand unlock.
I highly recommend going through Whitslack's Starting Over method to bring your software and radios up to date.
You're done.
Pity this only came to light a few days before people are going to be upgrading to a new OTA.
No, this will not work for anyone who updated to 2.2.

epic!!! 789

niice!

Nice Find!
At least now people can be rooted prior to the new OTA!

damn it!
___

Sweet! Wish I had that method starting out. Lol.
Sent from my PC36100 using XDA App

does this method really work??

BAttitude7689 said:
does this method really work??
Click to expand...
Click to collapse
Yes it does.

ok, so i have no idea how that works... care to go into it alittle bit more?

khshapiro said:
ok, so i have no idea how that works... care to go into it alittle bit more?
Click to expand...
Click to collapse
The init scripts chmod 777 mid.txt on boot (this means that anyone can do anything to the file basically). By removing the file and linking it to mtd1, the chmod now makes mtd1 accessible by everyone after a reboot, which means that you can go directly to toast's part2 which starts with flashing mtd-eng.img.
Incidentally it appears the droid eris guys have been using this flaw to their advantage for a while as well ;D.

So no, really? What is "root?"
You do fine work, sir

posting in a legendary thread

Couldn't you then just use wits "start over" method for part two to make the process even shorter?

netarchy said:
Part 1:
Code:
adb shell rm /data/local/rights/mid.txt
adb shell ln -s /dev/mtd/mtd1 /data/local/rights/mid.txt
adb reboot
Click to expand...
Click to collapse
What would be more interesting is for someone on the new OTA non-root to see if this exists in the Froyo release. I'll look around for a posting of the OTA update non-rooted and try it on my smashed phone. At least I won't care if that thing looses root.

Could we get a "The easiest 1.47.651.1 root method with nand unlock" for dummies? I have no clue what to do with this code.

You need to use an ADB shell for this using the Android SDK....
I tried to use the Evo-Recovery shell and received permission denied errors.
I am not a DEV by any means, and do not claim any credit for any of this. However, for people who need help, this may offer some assistance -- this is definitely the easiest root method out there.
1. Download and Install Android SDK - Learn Here
http://forum.xda-developers.com/showthread.php?t=694250
2. Open up a Command Prompt by holding windows button & pressing R or by pressing Run and typing CMD.
3. Navigate your way in DOS to the Android SDK folder, then to the Tools Folder
4. Then enter in the code in part 1. After each line press enter...the line will repeat below it.
5. Follow Toasts Part 2 -- Link: http://forum.xda-developers.com/showthread.php?t=701835 -- Video found here: http://www.youtube.com/watch?v=tUXTB0eydwE.
5A. Because you didn't do Toast's Part 1 of Root first (you used an exploit provided by the OP), you will NOT have a NAND Backup. Put the Custom ROM you want to load on your SD card, and after unlocking NAND protection and doing the wipes, load it from the custom recovery in lieu of restoring your NAND backup.
6. You're now rooted w/ NAND Unlocked!
7. I would then suggest going here, and running this so you have a fully rooted, stock ROM with all your radio/wimax up to date: http://forum.xda-developers.com/showthread.php?t=715915.

Anyone know if this method will work on an unrevoked3'd Evo? I am trying to acquire full root and I was going to use SimpleRoot today but if this will work...

Thank you for this! Question about number part 7. YOu suggest running the fully rooted stock 1.47.651.1 afterwards. Would it be a bad idea to Just run the fully rooted stock froyo 3.23.651.3 or even any other custom rom for that matter? i.e OMJ's EVO 2.2 Custom rom? Thanks

regulator207 said:
Couldn't you then just use wits "start over" method for part two to make the process even shorter?
Click to expand...
Click to collapse
No because you need the engineering hboot to flash it since it's not signed by HTC.
Should work on 1.32 or 1.47. Nice.
Someone should test if this still works in the new 2.2 update. Good chance it does.

damit!
justinisyoung said:
damn it!
___
Click to expand...
Click to collapse
Hey! That's what I was gonna say!

[ubuntu Q] Any way to root using Ubuntu?

is there a way to use ubuntu to root the epic? I have ubuntu and I want to root my epic but I can't figure out how to use the one-click method because I can't really use the drivers. I was trying to use the terminal with adb but I don't really know what I am doing.

linux doesnt need drivers i made a one click script for linux ill see if i cant find it
http://www.mediafire.com/?hk59z8j5dve6tgf
download that and run the clickhere.sh it should root you just fine, you may need to make the script and adb executable

You can try following along the run.bat script included in the one click root. I did not need to install any drivers to root using Ubuntu, but I did download the Linux version of the android sdk (from Google) just in case (instead of using the adb included in the one-click-root download.
If you have your android-sdk-linux_x86 directory in ~/Downloads/, and you extracted the one.click.root file into ~/Downloads/ as well, here's what you could do:
cd ~/Downloads/one.click.root
(Now you're in the location of the one click root files.)
Next, type each line of the run.bat file manually. Any time you see "adb" replace it with:
sudo ../android-sdk-linux_x86/tools/adb (command)
You'll need to adapt a bit to your situation, but because most of the adb commands are native to adb and run on the phone, they should work verbatim on your Ubuntu system.
Didn't someone put out a Linux one click root, though?
EDIT: Yes, shabbypenguin did. Looks like he posted it above me before I finished typing my post. Whoops.

Complete Big edit....
I thought I bricked my phone but I didn't. I ended up getting the permanent root. I used this guide http://forum.sdx-developers.com/epic-development/adb-root-exploit-test/
Is there anything special I am missing? like busybox? or remount scripts? not sure what either of those are.

remount allows your system to have rw access with a simple command, busybox.. think of it as an extended shell
the zip i included in my post is based off noobnl's latest version and works fine with linux. i made it while using ubuntu

shabbypenguin said:
linux doesnt need drivers i made a one click script for linux ill see if i cant find it
[snip]
download that and run the clickhere.sh it should root you just fine, you may need to make the script and adb executable
Click to expand...
Click to collapse
Thank you so much for this! ... "You have no chance to survive make your time" means I'm rooted?

i made version 2, its in my sig, will root and install clockwork mod 2.5.1.0

Linux Working on Android

(I'm reposting this under a different title so web searches will bring it up)
I can get Ubuntu 11.04, 11.10 & Debian 6 to mount repeatedly in all sorts of ui updatable configurations using this information:
http://www.nerd65536.com/2011/07/ins...version-2.html
It's a friggin Christmas Miracle! Can't tell you how much time I've wasted working this out, and it all boils down to the sh and run scripts.
So, without further ado, here goes.
!!Make sure you're rooted!!
!!The quotes just tell you what to type. Don't type them!!
1.
Download one of the three builds on the website listed above (or build your own, it should work fine). Extract it from tar.bz2, they should all extract to a linux file, this includes the necessary scripts. Put it on the sd-card on your phone.
2.
Download the new scripts that (Nerd) listed found here: http://ohm.nerd65536.com/android-lin...latest.tar.bz2
And extract them. You'll have another file that says linux. Open it, take the three files inside (install.sh, root-scripts & scripts) and paste them in the linux folder you moved to your sd-card. They will overwrite the ones currently there. These scripts work for sgs4g, the originals did not.
3.
Install the latest BusyBox in both xbin and .bin if it's not already installed (must be rooted), Latest is 1.19.3. Make sure Outside Sources and USB debugging are both enabled in your settings menu. Open your Superuser App and update binaries.
4.
Download a terminal client, like Better Terminal Emulator or Android Terminal Emulator. I use the first. The terminal needs to run the commands as root, especially the linux vnc command as it didn't want to work for me no matter if I started by typing su. Better Terminal Emulator has a check box to always start in root.
5.
Open up your terminal emulator and type su if you are not rooted there. Then change directory to the linux file on the sd-card. run the sh file there.
Like this:
"su"
"cd /sdcard/linux"
"sh install.sh"
If it works, the resulting dialog in terminal won't throw up any problems.
6.
Get back to / on sd by typing in terminal:
"cd /"
You should then have a: / # prompt, which means you are still rooted.
Enter:
"linux"
Which should result in a: [email protected]:/#
This means Linux is running. Congratulations. It should continue to run unless you shut down your phone.
7.
Download a VNC client, like Android VNC Viewer (free) or Remote VNC Pro, which I use. Add a new entry in it, with the following settings:
Host: localhost
Port: 5901
Password: cheesecake
Color: 24-bit
Name: Linux
When that's done save if you can or back out if you can't, and go back to your terminal emulator.
8.
It should still say: [email protected]:/#
If it doesn't, fine, if it does, just go back to root prompt by typing:
"exit"
Which should get you: / #. Then type:
"linux vnc"
Which should run itself and mount the chroot environment. It should tell you your new 'X' desktop is localhost:1, and have a: / # prompt again.
It might also ask you for a password, if so then put whatever password you'll remember in that's longer than 6 characters and verify it. This only happens once.
9.
Go back to your VNC client and if you entered a password in step 8. then edit your listing to your password instead of cheesecake, if not then don't.
Click on the Linux link and BAM! (shameless Emerilism), you're at your Linux desktop which should be running a iceWM desktop interface, which is fast. The LXDE desktop is nicer and if you want that then go into you're terminal and get into the linux shell by typing:
"linux"
And then switch to LXDE by typing:
"apt-get autoremove icewm- lxde+"
Which will run through the removal/ installation, and verify you want to download the <400mb files. Type:
"y"
And give it time to finish. When finished, just go back to your VNC client and hit Linux again, and you will have a nice looking functional desktop, with a cpu load graph on the bottom. I tried using Gnome desktop and Unity 2d, but both of these would install and not fully run with all options. They are heavier and slower, but cool non-the-less. Let me know if anyone has luck with these on Android.
Notes-
You only have to type "linux vnc" once in terminal to start linux every time you boot your phone. Otherwise, just open your VNC client and click on Linux to use it. Easy!
You will want to update and upgrade your linux after install, do so by typing in terminal:
"apt-get update"
"apt-get upgrade"
Also, you might run across a problem if you try to add-apt-repository, that's because that python command is not present. To use it, enable by typing:
"apt-get install python-software-properties"
Also of note, the downloadable linux builds are sized to about 2.15gig on your sd, which is big enough for most. There is a way to resize them which I tried but it gave me trouble in loading. I will try again and see if I can get it to work.
Here's the link from Dangermouse:
http://www.androidfanatic.com/commun...atid=9&id=1610
Thanks to Nerd65536 for the info, write-up and files. He fixed my problem.

You might want to put quote or code tags around all the commands to make them easier to see and read, but good guide! I'll try it out soon since I haven't gotten any linux build to run on my phone in a good while.
Thanks for the post!

I wrote the post noob-style to make it easy for beginners to follow, as I've had to search and test forever to find information that works.
Let me know if you have any problems, I'd be happy to assist. Don't expect you'll have any issues with your knowledge of the os. It works pretty well on the Android system, fun to use.

wasn't this posted ages ago?

No, it's a bleed over from a question post I made under Q&A a week or so ago. I threaded this because I had such a hard time finding a thread with working steps for the Galaxy S under google search. There's not that much new from this post http://www.nerd65536.com/2011/07/in...showComment=1323566336074#c553594301247543088 by Nerd65536 (which took me forever to find and was the only one that worked). Other than that, just a few of my own thoughts and hints on the process.

krylon360 said:
wasn't this posted ages ago?
Click to expand...
Click to collapse
meant to quote not thanks, but anyways, to answer.
There has been a few times this has been posted, but its been many months and this seems like the first the issues have been sorted.
Sent from my SGH-T959V using Tapatalk

Ok, a little more use of Linux builds on my phone and I'm starting to understand why it does or does not work.
Certain kernel builds seem to work well, others not at all. Most of the kernel's I've tried have been problematic, and trying to install the .sh file will fail.
When you install your new kernel (or on your existing one) you need to open your Superuser app which should be there if your phone is rooted. There is a button to update binaries, and they need to be updated. Some builds don't seem to let this work easily and give failure notifications.
Make sure Outside Sources is enabled and USB debugging is too, both are in the settings menu.
Use BusyBox installer to install in both the .bin and .xbin directories, this will not cause any conflicts (or hasn't yet . If this gives you an error, and it will if Superuser did, then either usb debugging has not been selected or the kernel is not playing nice.
Ok, so this kernel by RaverX3X will work for linux, I'm on it now:
http://forum.xda-developers.com/showthread.php?t=1305145
(Thanks for this)

Oh yeah, and Back|Track5 Linux is working too
Fixing the packet injection for the Broadcom now.

sconsylman said:
Oh yeah, and Back|Track5 Linux is working too
Fixing the packet injection for the Broadcom now.
Click to expand...
Click to collapse
. Keep us posted on that. Should be pretty handy.

Wait. why do we need LInux to run on our phone?
Can someone explain?

Android doesn't come with most of what this has:
http://www.backtrack-linux.org/

I know, but why do we need it?
Enlighten me

airfluip1 said:
Wait. why do we need LInux to run on our phone?
Can someone explain?
Click to expand...
Click to collapse
I've seen this comment on every single thread online regarding Linux on Android. It's a joke right?

[Solved] Root TF101 without Windows, possible or not? Yes, it's doable!!!

Hi all!
Was about to purchase a Nexus 7 when I saw a huge discount on the Asus TF101 and decided to take it. How I have a it in front of me proudly informing it has the firmware revision IML74K.WW_epad-9.2.1.27-20120615. BTW, the s/n starts with B50 if it matters.
And now what? Wait for the official JB or root it right now? I usually root all my devices at least to have nandroid + TiBu, even if I don't plan to install any alternative FW.
The problem is it's an ICS 4.0.3 with the problem to enter into recovery mode and I have only a Mac computer, no Windows and no Linux machines around. I read the threads and see every time the Windows tools, nothing for Mac. No root from SD card neither.
Any advice how to root using the Transformer itself or my Mac? And any advice regarding best JB ROM or at least best kernel for stock 4.0.3 ROM with exFAT support? I don't use NTFS because my Macs can't write on and old FAT16 has the famous 4 Gb limit, not good for the movies.
Many thanks in advance.

You could try and install Windows on your Mac to essentially have a dual boot of both OS's. Or you could use something like VMWare (I think that's what it is but I'm like 5% sure) which allows you to run windows without necessarily installing it. Anyway, I suggest, if you can, to go ahead and root your device and install a JB ROM like EOS or CM10 or something.

If it's not possible to do Android modifications on a Macintosh it looks like your only option would be to setup a dual boot with Linux to do your Android Rooting and ROM flashing since I would imagine you would want to avoid having to use Windows for this It would be better to avoid virtual machines to do device modifications and just stick to the dual boot option since support for USB devices is iffy in virtual machines.

Hi all,
Shmi117 said:
You could try and install Windows on your Mac to essentially have a dual boot of both OS's.
Click to expand...
Click to collapse
No chance! I don't like to spend hours installing Windows and all this stuff again !!! :crying:
WCL1990 said:
If it's not possible to do Android modifications on a Macintosh it looks like your only option would be to setup a dual boot with Linux to do your Android Rooting and ROM flashing since I would imagine you would want to avoid having to use Windows for this It would be better to avoid virtual machines to do device modifications and just stick to the dual boot option since support for USB devices is iffy in virtual machines.
Click to expand...
Click to collapse
Basically what Linux can to Mac OS X can do. At least regarding adb and the command line use. The problem is I have found tons of good information about how to do it using Windows, but nothing for Linux nor Mac.
OK, here is the answer. One can root the Asus Eee Pad Transformer TF101 using Mac OS X only!
Developing in next message...

OK, here is the solution. :fingers-crossed:
First of all, I presume the Android SDK for Mac OS X is installed and upgraded.
Next, on the Transformer please go to Settings -> Developer options and activate the USB debugging. Finally, please check this forum thread and download the latest version of PERI. Yes, PERI for Windows 0.4 as of today. Please unzip the downloaded file.
No sorcery or black magic here, I've just learned from the bat file and tried to reproduce the whole procedure manually using adb.
Most Linux users will smile, but I will show the commands the way most Mac OS X user will need to input them. Basically, you don't really know that the shell path is and what "finally add adb to your path" means, right?
1. OK, please open the Finder and go to the directory where the adb executable lives. Something like ~/Downloads/android_sdk/android-sdk-macosx/platform-tools/.
2. Now please open the Terminal.app inside Application/Utilities folder and go to the same directory.
3. Please connect the Transformer to the Mac using the USB cable.
4. First of all, let's see if adb sees the Transformer. Please input
Code:
./adb devices
If everything is OK, you'll see something like this:
Code:
List of devices attached
024640c082db4561 device
5.
Code:
./adb push /Users/YOURUSERNAME/Downloads/OneclickrecoveryV0.4/recoveryblob /sdcard/
Basically you input ./adb push, drag the a.m. file and next input /sdcard/
6.
Code:
./adb shell mv /data/local/tmp /data/local/tmp.bak
7.
Code:
./adb shell exit
8.
Code:
./adb shell ln -s /dev/block/mmcblk0p4 /data/local/tmp
9.
Code:
./adb reboot
Wait while the Transformer reboots.
10.
Code:
./adb shell dd if=/sdcard/recoveryblob of=/dev/block/mmcblk0p4
11.
Code:
./adb shell exit
12.
Code:
./adb reboot
Wait while the Transformer reboots.
13.
Code:
./adb push /Users/YOURUSERNAME/Downloads/OneclickrecoveryV0.4/Superuser-3.0.7-efghi-signed.zip /sdcard/
See #5.
14.
Code:
./adb reboot
Wait while the Transformer reboots.
15. Now please shut down the Transformer manually and boot into recovery. Please hold Power + Volume Down buttons and next confirm with Volume Up button when asked. Rogue XM recovery will boot.
16. Wipe cache, wipe Dalvik cache, next choose Install zip file from internal storage and choose the Superuser-3.0.7-efghi-signed.zip.
17. When it's done, reboot.
18. PROFIT. :good: Your device is rooted with Rogue XM recovery installed.
From there I suggest to install SuperSU and eventually SuperSU Pro as it seems to work better than Superuser and Superuser Elite respectively. You can eventually get rid of Superuser if you wish so, instructions available in this forum thread. As I own both SuperSU Pro and Superuser Elite, I've installed SuperSU and upgraded Superuser, just in case of. You should not mix them, though, thus I've revoked the root permission of Superuser.
Next I've installed Busybox. I don't know if it's the best version for TF101, works well on my GNote.
Finally, let's play with the recovery options courtesy of some awesome developers. :good: We can choose among Rogue XM Touch, CWM classic, CWM 6.x and official or modified TWRP. I've chosen the official TWRP with GooManager.
Next stop, Titanium Backup.
Should you have other recommendations, please do not hesitate.

Thanks a lot friend. I used the same procedure to root my TF101 using Ubuntu Are you using any Customised ROM ? I am using CM10 based ROM built by RaymanFX and it is simply awesome
iLearner said:
OK, here is the solution. :fingers-crossed:
First of all, I presume the Android SDK for Mac OS X is installed and upgraded.
Next, on the Transformer please go to Settings -> Developer options and activate the USB debugging. Finally, please check this forum thread and download the latest version of PERI. Yes, PERI for Windows 0.4 as of today. Please unzip the downloaded file.
No sorcery or black magic here, I've just learned from the bat file and tried to reproduce the whole procedure manually using adb.
Most Linux users will smile, but I will show the commands the way most Mac OS X user will need to input them. Basically, you don't really know that the shell path is and what "finally add adb to your path" means, right?
1. OK, please open the Finder and go to the directory where the adb executable lives. Something like ~/Downloads/android_sdk/android-sdk-macosx/platform-tools/.
2. Now please open the Terminal.app inside Application/Utilities folder and go to the same directory.
3. Please connect the Transformer to the Mac using the USB cable.
4. First of all, let's see if adb sees the Transformer. Please input
Code:
./adb devices
If everything is OK, you'll see something like this:
Code:
List of devices attached
024640c082db4561 device
5.
Code:
./adb push /Users/YOURUSERNAME/Downloads/OneclickrecoveryV0.4/recoveryblob /sdcard/
Basically you input ./adb push, drag the a.m. file and next input /sdcard/
6.
Code:
./adb shell mv /data/local/tmp /data/local/tmp.bak
7.
Code:
./adb shell exit
8.
Code:
./adb shell ln -s /dev/block/mmcblk0p4 /data/local/tmp
9.
Code:
./adb reboot
Wait while the Transformer reboots.
10.
Code:
./adb shell dd if=/sdcard/recoveryblob of=/dev/block/mmcblk0p4
11.
Code:
./adb shell exit
12.
Code:
./adb reboot
Wait while the Transformer reboots.
13.
Code:
./adb push /Users/YOURUSERNAME/Downloads/OneclickrecoveryV0.4/Superuser-3.0.7-efghi-signed.zip /sdcard/
See #5.
14.
Code:
./adb reboot
Wait while the Transformer reboots.
15. Now please shut down the Transformer manually and boot into recovery. Please hold Power + Volume Down buttons and next confirm with Volume Up button when asked. Rogue XM recovery will boot.
16. Wipe cache, wipe Dalvik cache, next choose Install zip file from internal storage and choose the Superuser-3.0.7-efghi-signed.zip.
17. When it's done, reboot.
18. PROFIT. :good: Your device is rooted with Rogue XM recovery installed.
From there I suggest to install SuperSU and eventually SuperSU Pro as it seems to work better than Superuser and Superuser Elite respectively. You can eventually get rid of Superuser if you wish so, instructions available in this forum thread. As I own both SuperSU Pro and Superuser Elite, I've installed SuperSU and upgraded Superuser, just in case of. You should not mix them, though, thus I've revoked the root permission of Superuser.
Next I've installed Busybox. I don't know if it's the best version for TF101, works well on my GNote.
Finally, let's play with the recovery options courtesy of some awesome developers. :good: We can choose among Rogue XM Touch, CWM classic, CWM 6.x and official or modified TWRP. I've chosen the official TWRP with GooManager.
Next stop, Titanium Backup.
Should you have other recommendations, please do not hesitate.
Click to expand...
Click to collapse

Thanks, that worked nicely for me!
One thing I can't figure out yet, though, is how to do a backup - the microsd card doesn't mount at /sdcard/ and backing up to internal storage is not recommended...

Wheelie
Hi!
A linux only solution for B70(+) devices can be found here:
http://androidroot.mobi/2012/05/27/introducing-wheelie-nvflash-for-asus-transformer-tf101-b70/
It is what I used twice so far. Works as it should.
I do not claim credit for anything! I just stumbled upon the solution.

Problem rooting
Hi,
this is my first post on XDA.
After a lot of readings here, I think I have tried everything I could, but my knowledge in rooting is too limited to understand these bugs:
At first, when I tried running these lines on the terminal, I couldn't push the files to /data/local: permission denied.
Then, I tried pushing to /sdcard/ and it worked.
But the next error I get is when linking:
"link failed Function not implemented"
Can you help me please?
My computer is a Mac, so I have tried you method first. I also tried on my Parallel Desktop with Windows 8 and on the PC with Windows 8.1 of my girlfriend, with RootDebugFs.
Here is the description of my Infinity pad:
model: ASUS Transformer Pad TF700T
Android: 4.2.1
Kernel: 3.1.10-g9827b9a, [email protected] #1
Build: JOP40D.WW_epad-10.6.1.14.8
I had the build 14.10 but I found that I should downgrade to 14.8, so I did, but nothing changed.
I also unlocked my tablet by mistake, thinking it would help rooting.
Thanks for your help.
Best,
Yohan.

Just did this!!! Still works!!! Followed your steps. Now the recovery is TWRP 2.5!!! As the peri version changed I checked if the .bat was still doing the same things, and it is!!
Thanks for your tuto! Saved me some time installing W**** ...