yashsingh1/xdaforums huggingface dataset:
[Eee Pad Transformer Android Development] Petarsson:
maybe, but i am still using it for backups, as i did not want to install a custom recovery due to asus-updates for a long time...

anyway, i have tried a cm9-rom just for fun, because i thought, that i could return to my previous state, as i have a full backup...

but when i tried to restore a backup, it did not boot, but got stuck at the asus bootanimation...same result with various former backups, no way to get it running...

interestingly, the custom recovery remains (althouh i have a recovery-backup as well of course), so i was able to return to the cm9-rom, but due to battery-reasons, i want back to stock...any hints, what mistake i make, or how i can restore my backups otherwise?

thanks in advance...
[Eee Pad Transformer Android Development] lawsonmh15:
Has anyone confirmed this works with the TF300T?
[Eee Pad Transformer Android Development] brk:
So, great news, Ryaman84 and his team have made a new tool for using nvflash with B70+ pad.

So, when windows binaries are released, I'll update this tool to v8 with this new feature.
[Eee Pad Transformer Android Development] brk:
New version SBK v1 & SBK v2 here: http://xdaforums.com/showthread.php?t=1688447
[Eee Pad Transformer Android Development] shoehopper:
can someone point me to a .img for Roach's CWM 3.2.0.1..? For whatever reason once I've gone to the touch CWM I can't revert to any other CWM via CWM.. it says they flash successful, but when I reload CWM/reboot I go back to the same version.

The only success I've had is via nvflash and I cannot find the .img for these older CWM's that recognize external microSD anywhere.

Thanks,
[Eee Pad Transformer Android Development] cbrox:
here you go.

link to roach's recovery thread

http://xdaforums.com/showpost.php?p=16557195&postcount=1

link to a recovery loop fix that also works that doesn't involve NV flashing

http://xdaforums.com/showpost.php?p=29632231&postcount=3
[Eee Pad Transformer Android Development] poging22:
This is also useful for rooting and installing cwm http://www.transformerforums.com/fo...x-bootloops-soft-bricks-all-ics-firmware.html
[Eee Pad Transformer Android Development] :
Does this work for the memo 10.1?
[Eee Pad Transformer Android Development] ahoslc:
So I got it rooted and it installed recovery. Now I can't for the life of me install any roms I tried 3 different CM 10 roms all say failed when trying to install from External or Internal any ideas?
[Eee Pad Transformer Android Development] bfmetcalf:
What recovery are you using? and how did you install it?
[Eee Pad Transformer Android Development] ahoslc:
I first tried using the cwm that came with Rootkit that didn't work then I installed the latest TWRP from Goomanager.
[Eee Pad Transformer Android Development] bfmetcalf:
yeah, CWM on the tf101 is not compatible with jellybean ROM's so you definitely want TWRP. Have you tried other ROM's other than CM?
[Eee Pad Transformer Android Development] ahoslc:
No I just tried 3 different versions of cm10
[Eee Pad Transformer Android Development] bfmetcalf:
Try KatKiss, if that doesn't boot, then I would say something is pretty wrong.

What is the error you are getting by the way?
[Eee Pad Transformer Android Development] ahoslc:
It was just telling me bad installation

Do you think installing the cwm from Root kit then installing TWRP from Goomanager did something?
[Eee Pad Transformer Android Development] bfmetcalf:
That shouldn't matter.
[Eee Pad Transformer Android Development] *Detection*:
Try using Easyflasher to install TWRP incase your mixture of CWM and TWRP installs have broken something

btw CWM is not advised to use any more, it has bricked a few TFs trying to flash JB ROMs
[Eee Pad Transformer Android Development] ahoslc:
Also I picked install insecure boot image is this correct?

Should I just use the version of TWRP included in Easyflasher?
[Eee Pad Transformer Android Development] bfmetcalf:
You do have an origional transformer TF101 and not a TF300 or something else correct?
[Eee Pad Transformer Android Development] ahoslc:
Correct
[Eee Pad Transformer Android Development] bfmetcalf:
I would just use easy flasher and use the TWRP it has in it. Should work.
[Eee Pad Transformer Android Development] fmcneely:
Quick note to say THANK YOU and to all who participated in discussions here. I successfully rooted my TF101 with only a few issues, all of which were resolved with further reading. It was a fun learning experience.
[Eee Pad Transformer Android Development] Draeconix:
Other download sites?

Are there any other download links for 7.1 that don't force me to download and install a download manager?
[Eee Pad Transformer Android Development] jdagreek:
version and file download

I am trying to download ver 5 when I download it ... it states that it is ver 6 and it will not unzip ...

???
[Eee Pad Transformer Android Development] donow1204:
can't download from V5 link, can someone help please.
[Eee Pad Transformer Android Development] brk:
v5 updated
[Eee Pad Transformer Android Development] Bazzz66:
So that would be option 4 for a ww TF, then delete all apps that have something to do with root-access
[Eee Pad Transformer Android Development] yawyu:
mee to....

help me please
[Eee Pad Transformer Android Development] kingwp1:
I'm having a problem unzipping the V5beta2. Download works fine, but Winrar says something like "unknown method in <filename>" it lists this error for every file in the archive.
[Eee Pad Transformer Android Development] ondoy1943:
It is a corrupted zip file; |op| needs to re-upload the file.
[Eee Pad Transformer Android Development] donow1204:
Same here, corrupted zip file; nothing to zip. :(
[Eee Pad Transformer Android Development] yawyu:
unzip by 7-ZIP only
[Eee Pad Transformer Android Development] kingwp1:
Thanks, yawyu. I installed 7zip and the archive extracted flawlessly
[Eee Pad Transformer Android Development] nextelbuddy:
i was able to install the APX driver no problem. Windows 7 does detect and show APX is running fine now.

my TF101 has screen off but its in APX mode however ADB doesnt recognize it still.

i tried rebooting it the normal desktop screen as well as booting into APX mode by holding the Vol UP and Power button and hearing my computer make the sound but my screen remaining off.

i dont understand why ADB Devices doesnt show this device listed, i tried using the script and manually using Command prompt to run ADB Devices and both just show blank for devices and does not list anything.
[Eee Pad Transformer Android Development] jro2020:
okay so stupid question but can i use this to root 3.2 without installing clockwork? Or do I have to install clockwork with this.
[Eee Pad Transformer Android Development] kingwp1:
I'm running Windows XP, but I had this same issue. Try using the batch script anyway. I had success with it even when ADB wouldn't list the device. As long as you're sure you're in APX mode, you'll know the script is working because the tablet screen will say something like "entering nvidia flash recovery mode."
[Eee Pad Transformer Android Development] kingwp1:
You can root without installing the recovery. It gives you yes/no questions throughout the process.
[Eee Pad Transformer Android Development] RayYung:
I fix my rooting by reflash Official 84411 with stock recovery and run this script again. Now I have a rooted 84411 but I can't get into recovery anymore.

I think I might have accidentally flash the stock bootloader into my eeePad. Anyone can help me fix it? Thank you,
[Eee Pad Transformer Android Development] Pink_Panther2121:
Question: I was rooted on 8.4.4.11 and want everything stock again, so i installed Stock us Boot.img and Recovery.img and my TF would not boot. Installed root US boot.img and recovery.img and it booted fine.... Did i do something wrong?
[Eee Pad Transformer Android Development] jdagreek:
not sure what is going on I had downloaded a file that was tf_rotkit_v6.zip today the file is tf_rootkitv5_b2.zip and the 5b2 file works no zip will unzip the v6 sand I used winzip to unzip the 5b2
[Eee Pad Transformer Android Development] ondoy1943:
The correct file is v5.b2. Something wrong with it though, as it can't be unzipped by the embedded windows 7 zip unpacker. Use 7-zip to unpack and repack if needed. The repacked file now appears to be okay, and can be unpacked by windows 7.
[Eee Pad Transformer Android Development] jdagreek:
US Version worked !!!

Worked GREAT for some people they may not understand when they need to reboot and when you reboot then you need to shut down and restart again in APX mode.

BIG Thumbs up !!!
[Eee Pad Transformer Android Development] Speedstra:
WW 3.2 installed from 8.4.4.111

Hi,

I had rooted stock 8.4.4.11 WW (no CWM) and this morning checked for firmware update to 3.2 with success. Did not downgrade to unrooted state but upgraded to HC 3.2 WW (8.6.5.7) with no problems, nothing lost except root rights after upgrade. Waiting for the dev's to do the magic on WW 3.2 to get rooted again.

Greetz,

Speedstra
[Eee Pad Transformer Android Development] Speedstra:
Boot image for developers

OK,

here's a boot image of WW HC 3.2 (8.6.5.7) for people to work with. Downloaded with option 3 of the batch file,

Greetz,

Speedstra

EDIT: obviously this the unrooted stock version of 8.6.5.7. boot.img
[Eee Pad Transformer Android Development] Disket:
Rooted from stock 3.2 TW with no problems using the v6 files.

Could you add in an option to revert to stock in the batch file for TW as well.
[Eee Pad Transformer Android Development] Speedstra:
mmm,

I noticed quite a difference in filesize between the back-up 8.6.5.7 boot.img that I made (8192KB) and the rooted WW version (3434KB). How is that possible and will this give problems when I attempt to flash the 8.6.5.7 WW rooted boot image? I already noticed Kireas bricked his TF101 in an attempt...

Greetz,

Speedy
[Eee Pad Transformer Android Development] brk:
If you check the other root boot.img (TW and US) you'll that the size is very similar. Since you have the stock boot.img (thanks for sending it) if the root boot.img doesn't work (I think it will) you can always flash stock back.

Please give your feedback. Thanks.
[Eee Pad Transformer Android Development] Speedstra:
Unfortunately the TF101 went into a bootloop on the initial bootscreen after flashing the rooted boot image. I was able to regain control with the backed-up boot image. So the modified boor image doesn't work for me.

Greetz,

Speedstra
[Eee Pad Transformer Android Development] brk:
Thanks for your feedback. I'm at work so I cannot test it. I'll revert script to previous version and I'll prepare a new unsecure boot.img
[Eee Pad Transformer Android Development] ondoy1943:
This post could be of interest to those who have problems in cwm:

http://xdaforums.com/showpost.php?p=16227879&postcount=9
[Eee Pad Transformer Android Development] brk:
Added new update: v5beta4

I've rebuild WW HC3.2 unsecure boot.img, it should work fine (cannot test, do not have my pad with me).

Added also options to restore stock boot.img

Can somebody test this new ww root boot.img and tell me if it work? Thanks.
[Eee Pad Transformer Android Development] Speedstra:
ok,

flashed the latest version in v5 beta4, TF101 rebooted ok but was not rooted. Reloading SU and superuser.apk did not help.

Greetz,

Speedstra

EDIT: default.prop shows ro.secure=0, maybe that helps......
[Eee Pad Transformer Android Development] Bazzz66:
So if I understand correct when you have only rooted 8.4.4.11 and you have stock recovery you can update to 3.2 without any problems.

Just install the update provided over OTA.

After that just follow root procedure
[Eee Pad Transformer Android Development] Speedstra:
Yes,

that worked for me, but I was unable to re-root the TF so far.

Greetz,

Speedstra
[Eee Pad Transformer Android Development] brk:
Sorry, v5 beta4 script had a bug in root HC3.2 WW . Fixed that in beta5.
[Eee Pad Transformer Android Development] brk:
Yes, that is one way. The other is to boot in CWM recovery and flash Roach .zip HC3.2 Update. No need to re-root using this way.
[Eee Pad Transformer Android Development] Speedstra:
Still unable to acquire root with v5 beta 5

Greetz,

Speedstra
[Eee Pad Transformer Android Development] brk:
Why? What's wrong? Show me your build.prop
[Eee Pad Transformer Android Development] Speedstra:
her's the build.prop

greetz,

Speedy
[Eee Pad Transformer Android Development] RayYung:
I rooted my 8.4.4.11US with the boot.img, su, superuser.ark and busybox here and works. After I apply Roach's 8.6.5.6 US, I lost root.

I reinstall su, superuser.ark and busybox from here(v5b2) and still won't work. so I flashed boot.img frin v5b2, no luck. I try v6(yes, somehow I got it 2 days ago), still don't work. Any idea what went wrong and what should I do now?

I now have 8.6.5.6 US with boot.img, su and busybox from this post, updated superuser.ark(2.3.6.3). Rootcheck says busybox is working but no root.

Thanks you any help,
[Eee Pad Transformer Android Development] brk:
Checked and rechecked and everything should be fine, did you install superuser.apk (option 7) and busybox (option 8) via adb? Is your pad detected by adb?
[Eee Pad Transformer Android Development] brk:
Hi,

V6 was a typo, it was v5 beta1.

It's strange that you lost root installing Roach's update. I've checked the update and it reapplies root.

It's also strange that you say that cannot root with this method, because several users have reported success.

I cannot give you more support now, but later today I'll try to find what is not working or if everything is working fine.
[Eee Pad Transformer Android Development] RayYung:
Thanks for looking into it, please let me know if you need any information.

Is there any different between your 8656 boot.img and Roach's? and do you have other method to deploy the su? ( I *think* my su is not install correctly since superuser can't tell the version and it won't update itself)

Thanks again,
[Eee Pad Transformer Android Development] Speedstra:
Attached screenshot of outcome of running rootcheck. It appears not all is well, but some indication of root access.

Greetz,

Speedy
[Eee Pad Transformer Android Development] miguel.netreg:
stuck in boot mode

after I rooted my EeePad I updated with the OTA (WW) and now seem to get stuck on boot with 'Asus Eee Pad' or in restore mode, which is just stuck at 'unpacking files'

Will this Pure Root help reflash the rom and get me back on track with my upgrade?

Thanks a bunch for any guidance you may have! :confused:

EDIT: resolved. Still on 8.4.4.11 though with Prime 1.6
[Eee Pad Transformer Android Development] brk:
Can you use programs that need root, like titanium backup?
[Eee Pad Transformer Android Development] Speedstra:
No,

all programs that require root won't get root access. Root explorer is able to display root directory, copy works and further only read access. Rootcheck says Busybox installed properly
[Eee Pad Transformer Android Development] mailvamsi:
Thanks for the script. It worked on my US HC3.2. Couple of things were not clear for me but made it work.

* Selecting option 9 did not install superuser & busybox

* Connected again in ADB mode and used options 7 & 8 to get the full root functionality.
[Eee Pad Transformer Android Development] Speedstra:
still no root in 3.2

In my continueing struggle to get root rights in HC 3.2 I rolled back to an NVflash full back-up I had made of 8.4.4.11. That worked fine. Then I installed CWM via option 1 in the batch file. Worked fine too. Via CWM I installed the package Roach made to go to WW 8.6.5.7 from 8.4.4.11 via CWM. Update worked ok! But guess what? I lost root rights again applying that update. I'm in the same state again as mentioned earlier in this thread. Help!

Greetz,

Speedy
[Eee Pad Transformer Android Development] RayYung:
brk,

If it help you diagnose. I got the same screen as Speedstra when I run rootcheck and I have the same problem running programs need root.
[Eee Pad Transformer Android Development] ptitneo:
Same as Speedstra for me too (same results in root check). I'm on WW 3.2.
[Eee Pad Transformer Android Development] ptitneo:
... aaand after reading mailvamsi's comment, reinstalling superuser.apk with option 7 of your batch fixed the issue :)

I didn't think it was necessary since the app remained after the OTA upgrade from 3.1 (which was rooted with pure root as well - no cwm)

Thanks :)
[Eee Pad Transformer Android Development] xxxman999:
I did quite a bit of reading already. The problem is... the more I read, the more confusing I get. Can this method root my TF?

US 3.2 stock

8.6.5.6

Thx in advance.
[Eee Pad Transformer Android Development] nivron:
Yes, it will. Make sure to choose Option 9 though. I chose option 2 and got bootloops. I reset it then chose option 9. Smooth sailing from there.
[Eee Pad Transformer Android Development] xxxman999:
Thx for your response. Option 9 it is. I gotta have root have 3 hrs of ownership. Also looking forward to custom roms in near future.
[Eee Pad Transformer Android Development] brk:
Updated version to beta6 (will become final when I get stock US HC3.2 boot.img).

Version 6 will not have option to root HC3.1 8.4.4.11 (it makes no sense not to update to HC3.2)

Guys, please read the post before jumping to try to root your pad. Try to understand what you are doing. Read the menu form top to bottom before selecting and option, because maybe what you want isn't in the top of the menu!
[Eee Pad Transformer Android Development] nicandris:
can you upload somewhere else please? this is really slow! try multiupload!
[Eee Pad Transformer Android Development] brk:
Multiupload mirror available in 1st post ;)
[Eee Pad Transformer Android Development] nicandris:
just tested it, works on my 8.6.5.6 also ;)
[Eee Pad Transformer Android Development] lazerus06:
It appears this worked for me, lets me boot into clockwork recovery but my problem is that when i try to flash an update(netflix) it wont let me mount the sd card. Is there something else i need to do to mount the internal storage?
[Eee Pad Transformer Android Development] brk:
rootcheck is not compatible with ASUS Transformer.

V6 is working fine even if rootcheck gives some errors.
[Eee Pad Transformer Android Development] brk:
Try in the recovery thread. I cannot help you with that.
[Eee Pad Transformer Android Development] hardy81:
This method messed up my device. Had to reinstall stock after an unbootable device (booted to a screen of colourful mess of lines). Menu option to return to stock boot.img installed with the same end result.

ww 8.6.5.7 -> perhaps not supported yet?

Recommend a modded rom instead, safer.

After this mess cannot get 3.2 again, for some reason, as OTA... and it's not available as a download yet from Asus. Guess I have to wait then.
[Eee Pad Transformer Android Development] xxxman999:
Successfully rooted my TF today with this method. THX, BRK. just awesome!

US 3.2 Stock

8.6.5.6

Root win APX mode (option 9)

Reboot TF

re-run the script (option 7 and option 8 to install superuser and busybox)
[Eee Pad Transformer Android Development] krazyazy:
US HC3.2 stock boot and recovery

Hey brk,

If needed, I've uploaded the stock boot.img and recovery.img for HC3.2 US. Hope I did it correctly, I followed the directions in the Transformer pure root thread.

http://www.multiupload.com/5AQSVS5KGR
[Eee Pad Transformer Android Development] RayYung:
brk,

I finally get a rooted 8.6.5.6 on my pad. I didn't end up using you root method to root it but I did use you script and files to finish it.

Here the step I used to un-stuck my pad:

1)I install 8.4.4.11 Stock recovery from your script

2)put the OFFICIAL Asus 8.4.4.11 zip file on MicroSD

3)use stock recovery to flash the Official 8.4.4.11

4)flash 84411 recovery from here: http://xdaforums.com/showpost.php?p=16227326&postcount=8

5)flash Roach2010's 3.2zip

6)Done!! EDIT: (or not...)

Thank you for your file and your help.

EDIT: Almost forgot the last step ?!

6)use your script to flash 8656 CWM recovery ONLY

7) Really Done
[Eee Pad Transformer Android Development] jdjozwia:
so if i am reading this correctly i can root my stock 3.2 8656 using this guide?
[Eee Pad Transformer Android Development] Disket:
Yup, worked for me :D
[Eee Pad Transformer Android Development] brk:
I've used my script to root my pad and IT WORKS FINE! It works for US, WW and TW pads. Has I sayd before, If it doesn't work for you, i because you made some error in the process. Read the 1st post again, read FAQ again.
[Eee Pad Transformer Android Development] Speedstra:
Umm,

I'm pretty sure I followed your batch file as intended but did not acquire root. I think there was something screwed up in the set-up of my TF101 somehow. I finally re-installed everything with a clean install of 8.4.4.5 from scratch, manually applied all the updates (no OTA), then rooted ok, re-installed all my apps with TB and now everything is sweet and dandy. Brk, thanks for all your efforts.

Greetz,

Speedstra
[Eee Pad Transformer Android Development] philseven:
can any one tell me where to find this information inside the system folder I did everything else correct but could not find that when i unziped the live cd for windows 7 64. I am looking for the usbpcdriver in tf_rootkit folder.

in wizard select to find yourself the driver 5.4. Point driver update to usbpcdriver in tf_rootkit folder
[Eee Pad Transformer Android Development] brk:
:confused::confused::confused::confused::confused::confused:

what do you want with system folder?

:confused::confused::confused::confused::confused::confused:

why do you need the live cd for windows 7 64?

:confused::confused::confused::confused::confused::confused:

I think you should read and read again the 1st post and other posts in this forum before trying to do anything else.

Here is the step by step guide to find usbdriver folder:

1. download the zip file available in the 1st post of this thread

2. copy the downloaded zip file to your pc desktop

3. unzip file that you have downloaded and copied to desktop

4. there is your tf_rootkit folder

5. inside there is a usbpcdriver folder
[Eee Pad Transformer Android Development] rustak:
Successfully used v5b6 to root a stock WW 3.2/8.6.5.7, thanks!

Any reason why the WW version in the menu references 8.6.5.6 instead of 8.6.5.7, or just a typo?
[Eee Pad Transformer Android Development] brk:
just a typo.
[Eee Pad Transformer Android Development] davey1412:
Thank You

Thank you very much! 3.2 WW Rooted as easy as pie! :D
[Eee Pad Transformer Android Development] philseven:
Okay misunderstood my bad thanks. Thanks so much for your help I could have bricked my tf what an IDIOT. Thanks again so much that's what happens when you rush
[Eee Pad Transformer Android Development] musicalwoods:
I successfully rooted US 3.2 via this method, but I don't believe I've gained CWM recovery. I'm at a loss on how to install CWM recovery manually now :/
[Eee Pad Transformer Android Development] brk:
Updated to new version with new name.

Now you choose your download to match your pad version. Smaller download, less complicated script, less bugs, less confusion.

Give your feedback.
[Eee Pad Transformer Android Development] brk:
Do you know how to get to recovery?

I can use this same script to reinstall only recovery. When it ask if you want to install root boot.img say no, then say yes to install recovery.
[Eee Pad Transformer Android Development] tdub:
Worked a treat for me too. Thanks!
[Eee Pad Transformer Android Development] Aioria:
Hi to all, I have a stock 3.1 WW, what script I can download for root and for install recovery to my transformer?

Thanks :)
[Eee Pad Transformer Android Development] 2manytoys:
I had to swap my pad out with another (long story) and I can't root the new one. I think I may have this new version (B70) people are talking about??

I get the following now:

Nvflash started

rcm version 0X4

Command send failed (usb write failed)

Any ideas to get root again, thanks.
[Eee Pad Transformer Android Development] T33H00:
Hello

Where Can I get the script for 3.1?