[TOOL]"1-Click Transformer Root"-Root/Unroot/cwm/stock rec-TF101(G)/201/300T(G)/SL101

justmara · Jun 8, 2012

win7 x64. cannot connect adb. manually installed drivers (ignoring the warning that the driver is not signed) but "adb devices" shows it offline.
and sure whole root process fails without adb working properly 8(
after and hour of dances with abd kill/start, changing device usb debug settings and etc i finally plugged usb cable to other usb port.. it worked!
but only partially:

Connected to recovery...Doing step 4.
Usage: mount [-r] [-w] [-o options] [-t type] device directory

Installing su....

Installing Voodoo RootKeeper compatible su backup....

Installing busybox...
/system/bin/sh: cannot create /null: Read-only file system

Waiting for device after reboot...
Connected...Verifying if it all worked...

ERROR: su NOT OK.
ERROR: Busybox NOT OK.
ERROR: su backup NOT OK.
All done.

so CWM is installed. but no root 8(

carrige · Jun 8, 2012

I'm trying to flash my WW 9.2.1.24 TF101 to the get 'basic' root (i.e. the first method).

The output screen has been stuck on Step 2 - "Flashing CWM recovery..." for a good 15 minutes. Should I be worried? The tab is fully booted and working, but I don't know where an incomplete process will leave it.

Should I wait longer or close the tool and start again?

//EDIT//

I closed the tool, rebooted the tab and changed USB port. It booted up fine, and I ran the tool from the beginning. It powered straight through - no problems whatsoever. Root! Thanks OP!

idcrisis · Jun 8, 2012

justmara said:
so CWM is installed. but no root 8(

Hi, you can run the tool again. Let me know how it goes.

Else please change the first line of the batch file to:

@echo on

and rerun the tool. Also please change the DOS window buffer to 1000 or something large. Then you can capture the entire output and send it across.

Also what's your tablet model and firmware version?

justmara · Jun 8, 2012

idcrisis said:
Hi, you can run the tool again. Let me know how it goes.

Else please change the first line of the batch file to:

@echo on

and rerun the tool. Also please change the DOS window buffer to 1000 or something large. Then you can capture the entire output and send it across.

Sorry, I've ended up booting to CWM and installing CM9 with root and other bonuses =)

idcrisis said:
Also what's your tablet model and firmware version?

TF101G BB0K.. with 9.2.2.4 TW rom.
your tool installed CWM so I can install any rom needed now. so im fine 8) dont think i'm ready to revert to stock rom and try all this another time

razielreaver · Jun 8, 2012

i have a problem too, pls take a look and try to help me

hi, i hawe problem too, can u take a look for my log file?

(log is attached)

where i did a wrong steps?

pls manage me to a right way

thanx

idcrisis · Jun 8, 2012

justmara said:
Sorry, I've ended up booting to CWM and installing CM9 with root and other bonuses =)

TF101G BB0K.. with 9.2.2.4 TW rom.
your tool installed CWM so I can install any rom needed now. so im fine 8) dont think i'm ready to revert to stock rom and try all this another time

Great! Thanks for your feedback. I will look into the checks which check for recovery/normal bootup.

BTW, if you want stock recovery to enable OTAs you can run the tool again it'll give you a menu this time and you can choose to install the stock Asus recovery alone and do nothing else, no need to flash an entire stock rom.

Cheers!

idcrisis · Jun 8, 2012

razielreaver said:
hi, i hawe problem too, can u take a look for my log file?

(log is attached)

where i did a wrong steps?

pls manage me to a right way

thanx

Hi, please download the current version of the tool and run it. Your logs show you are running the older version of the tool.

Sorry, will start versioing some time soon as soon as I get around 20 successful feedbacks...

Also the ADB from this tool is constantly getting killed by another ADB from somewhere. If you can please kill all other instances of ADB anywhere ( don't have an ADB shell open while the tool is running) and if you can please replace all versions of the following files in your whole system:

adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll

with the ones provided with this tool.

Let us know how it goes.

asortix · Jun 8, 2012

Hi;
I have some problem with my asus transformer tf101G FW:9.2.2.4
can you look my log text? thanks for helping..

idcrisis · Jun 8, 2012

Hi guys,

I have updated the tool version to be somewhat more resilient to ADB version problems from external sources.

Plus a few other improvements based on latest feedback.

Please try it out.

Cheers!

asortix · Jun 8, 2012

i got it

Thank you so much...

phigafr · Jun 8, 2012

hi
is it working for TF201 V .21 too?

idcrisis · Jun 9, 2012

Nope, I've put in some checks so it will not continue if it detects a Prime.

But I believe the principle works if you're on an unlocked bootloader:

http://xdaforums.com/showthread.php?t=1622628&highlight=recovery-clockwork

http://www.androidauthority.com/transformer-prime-install-touch-clockworkmod-recovery-75663/

Since I don't have a Prime and the TF201 has serious brick potential from what I hear I haven't enabled the ability of this tool to attempt it.

Good luck!

shadowjin · Jun 9, 2012

finnally

Im not new to rooting or recoveries. Ive also rooted my transformer before but reverted to stock before the new update. This works flawlessly and installs Rogue recovery which doesn't boot loop from restarts. Also rooted my device in one sitting. Thank you!! (thanks was given)

In the past I used ViperMOD primetime to root and installed rogue recovery. I had my unit rooted just stock recovery and made the mistake of downloading clockwork mod from the playstore and Flashed from within the app. This caused my recovery to boot loop into recovery when restarted and some how prevented me from installing a different recovery. Long story short, I went back to stock using APX than used your "1-click-transformer root tool" and it worked perfectly and installed the correct recovery that doesn't boot loop.

Easy and painless. On a random note I own the first generation of tf101.

Edited for feedback: The only thing I noticed is that it doesn't allow me to add a new recovery after using this exploit. This isnt a big deal because its the correct recovery that prevents boot loops (Rogue CWM). When I tried flashing Rogue CWM touch it did the same as ROM Manager ClockworkMod from the playstore. (prevented me from installing another recovery) minus the boot loop into recovery.

regardless, it works flawlessly. But seams to not allow you to switch recoveries. Again, its not a big deal because its the anti boot loop version.

idcrisis · Jun 9, 2012

shadowjin said:
The only thing I noticed is that it doesn't allow me to add a new recovery after using this exploit.

Hi,

Thanks a lot for taking the time to provide a detailed feedback. It is highly appreciated.

As far as other recoveries as concerned, I see no reason why others can't be installed over this one. I am doing it quite frequently to try and figure out which ones don't suffer from the bootloops etc that you mention.

I am also not sure what you mean by 'prevented me from installing another recovery', but I think it may have something do with the fact that staging partition permissions go back to normal over reboots and flashing a recovery as a normal user won't work.

But you now have root, say you want clockwork-5.8.3.4-tf101.img, so you should be able to do something like:

su -c "dd if=/sdcard/clockwork-5.8.3.4-tf101.img of=/dev/block/mmcblk0p4"

If you don't want to mess around on the tablet, you can use "1-Click Transformer Root" to do it for you, just some behind the scenes changes needed.

Simply rename the 'clockwork-5.8.3.4-tf101.img' to 'recoveryblob' and the

'recovery-clockwork-5.8.3.4-tf101.img.md5sum.txt' to 'recoveryblob.md5'

and replace the corresponding files (with backup) in the 'source' directory of the tool.

Then run the tool and choose option '2. Install CWM recovery. '

This will now go and install the new recovery.

Mind you this particular one and a all 5.5+ I tried had the bootloop problem, so if you come across any updated one from here:

http://download.clockworkmod.com/recoveries/

which doesn't then do let me know and I'll update the tool.

The only permanent solution seems to be to recompile the recovery with a solution along the lines of:

http://xdaforums.com/showthread.php?t=1601942

Another day maybe.

Frankiebay · Jun 9, 2012

The tool does not work, because it does not recognize ICS.
Log see attachment.

I have Windows 7 64bit and Transformer TFT 101 with build 9.2.1.24 and ICS 4.0.3.
Tablet is in USB-Debugging mode.

Can you help me, please?

shadowjin · Jun 9, 2012

idcrisis said:
Hi,

Thanks a lot for taking the time to provide a detailed feedback. It is highly appreciated.

As far as other recoveries as concerned, I see no reason why others can't be installed over this one. I am doing it quite frequently to try and figure out which ones don't suffer from the bootloops etc that you mention.

I am also not sure what you mean by 'prevented me from installing another recovery', but I think it may have something do with the fact that staging partition permissions go back to normal over reboots and flashing a recovery as a normal user won't work.

But you now have root, say you want clockwork-5.8.3.4-tf101.img, so you should be able to do something like:

su -c "dd if=/sdcard/clockwork-5.8.3.4-tf101.img of=/dev/block/mmcblk0p4"

If you don't want to mess around on the tablet, you can use "1-Click Transformer Root" to do it for you, just some behind the scenes changes needed.

Simply rename the 'clockwork-5.8.3.4-tf101.img' to 'recoveryblob' and the

'recovery-clockwork-5.8.3.4-tf101.img.md5sum.txt' to 'recoveryblob.md5'

and replace the corresponding files (with backup) in the 'source' directory of the tool.

Then run the tool and choose option '2. Install CWM recovery. '

This will now go and install the new recovery.

Mind you this particular one and a all 5.5+ I tried had the bootloop problem, so if you come across any updated one from here:

http://download.clockworkmod.com/recoveries/

which doesn't then do let me know and I'll update the tool.

The only permanent solution seems to be to recompile the recovery with a solution along the lines of:

http://xdaforums.com/showthread.php?t=1601942

Another day maybe.

No rush, your tool works and installed the correct version.

The recovery your using in your 1-click Transformer tool is the Rogue XM version 1.3.0 CWM-based v5.0.2.7 from Team Rogue. From here:

http://xdaforums.com/showthread.php?t=1446019

I rooted and installed CWM from your tool, when I went into recovery I noticed it had Rogue installed. There newer version is touch but I originally wanted the non touch version. (in your tool already)

Clockworkmod from the playstore seams to cause a boot-loop into recovery if downloaded and flashed from there app. This is strange because I had read it was patched along time ago.

(I was on stock , stock recovery, rooted with firmware .24) Before I reverted via APX than used your tool.

What I meant to say by "it wont let me change recoveries".

When I tried to flash Rogue's touch version after your exploit, it flashes and says done, after a full reboot than return to recovery.... the non-touch was still installed. I left it alone because its worked in the past before and never caused any bootloops.

Thanks again.

drtomc · Jun 9, 2012

Problems with root

Thanks for this easy method. I am able to get only so far and then I have problems. The process seems to be stuck. The TF101 get stuck at recovery, while the cmd window keeps rolling, with a message 'timeout' is not recognized as an internal or external command, operable program or batch file. Device not found.

Also, an error window (many of them) pops up with the following:
\adb-drivers\dpinst_x64.exe is not a valid win32 application.

Thanks for any advice.

I tried shutting down the TF101 and rebooting to recovery, but I am not able to get back to the recovery screen. I am pressing volume down and power. I get to a screen with an android icon, and a wipe data icon. Eventually it just reboots back to the usual operating system. BTW I am on firmware .24

shadowjin · Jun 10, 2012

drtomc said:
Thanks for this easy method. I am able to get only so far and then I have problems. The process seems to be stuck. The TF101 get stuck at recovery, while the cmd window keeps rolling, with a message 'timeout' is not recognized as an internal or external command, operable program or batch file. Device not found.

Also, an error window (many of them) pops up with the following:
\adb-drivers\dpinst_x64.exe is not a valid win32 application.

Thanks for any advice.

I tried shutting down the TF101 and rebooting to recovery, but I am not able to get back to the recovery screen. I am pressing volume down and power. I get to a screen with an android icon, and a wipe data icon. Eventually it just reboots back to the usual operating system. BTW I am on firmware .24

When you hold down and power there should be numbers and words pop up after a few seconds of it starting.. than you press up ..............that would throw you into recovery. Pressing nothing goes back to android cold boot and data wipe icons.

From what I understand is that your stuck in recovery boot loop. His exploit does a few full reboots before installing recovery and rooting. If your stuck in a recovery bootloop it wont work (since it cant finish the process).

Did you flash any other recovery before using this tool? The reason im asking is because last night I had flashed by mistake CWM (I was rooted) from the playstore and had the same thing. Other root tools couldn't exploit the tf101 because of the recovery boot loop wouldn't let boot up like normal. I ended up using APX to revert to full stock than ran the "1-click Transformer tool" root and install CWM and it worked. It would install Rogue recovery which is CWM based from Team Rogue. If it succeeded it would say "team rogue" with green and white in the recovery instead of the typical CWM.

CWM for the playstore prevented a new recovery to stick after flashing and would boot loop into recovery. Even after saying it flashed correctly with no errors. In laymens term, I was stuck in a continuous loop skipping start up.

If you have alot of apps, go to the store and download apps to SD grey folder with 2 apps inside.. Back them up and move the app backup files to the removal memory. Revert everything via APX mode and use the tool again. It should work. I just did mine a few hours ago and a friends a few minutes ago. It worked again.

---------- Post added at 03:57 PM ---------- Previous post was at 03:48 PM ----------

Frankiebay said:
The tool does not work, because it does not recognize ICS.
Log see attachment.

I have Windows 7 64bit and Transformer TFT 101 with build 9.2.1.24 and ICS 4.0.3.
Tablet is in USB-Debugging mode.

Can you help me, please?

False, I have the same set up Windows 7 64 bit original TF101 1rst gen , exact same build and it worked. I used it again for a buddy of mine to give him root and CWM recovery with the same build and machine. Worked in less than 3 minutes. If you read a few pages back its worked for other people. The log file you added is incomplete by the looks of it it sounds like you wrote it in as it was working.

You will need to plug the device in to your computer , open up a command prompt/terminal
then, CD to your android-sdk/platform-tools/ directory

then, type ./adb logcat

This will give you a live debug log of what's going on in the device. If you need to filter to only see certain lines, use ./adb logcat | grep "something"

Edit: They also have an app that does this.

Hope this helps.

idcrisis · Jun 10, 2012

Frankiebay said:
The tool does not work, because it does not recognize ICS.
Log see attachment.

I have Windows 7 64bit and Transformer TFT 101 with build 9.2.1.24 and ICS 4.0.3.
Tablet is in USB-Debugging mode.

Can you help me, please?

Hi, this is strange. Can you change the first line in the bat file to:

@echo on

and increase the DOS window buffer and send me full output please.

The output before:

'Only ICS tablets supported by this tool. Going to quit now.'

contains the build number as detected by the tool so that should give an indicator as to where the problem lies.

Also, do use the latest version of the tool as exists now. I am updating it almost every day.

Sorry about that, will start versioning after around 20 reports of success and changes are only weekly.

drtomc · Jun 10, 2012

Thanks very much for the quick response. Seems I can get into Rogue recovery, but still not rooted. When I try to start Titanium backup, it says I don't have root privileges.

Sent from my Transformer TF101 using XDA

[TOOL]"1-Click Transformer Root"-Root/Unroot/cwm/stock rec-TF101(G)/201/300T(G)/SL101

Did it work?

Yes

No

Senior Member

Senior Member

Senior Member

Senior Member

New member

Attachments

Senior Member

Senior Member

Member

Attachments

Senior Member

Member

Senior Member

Senior Member

Senior Member

Senior Member

New member

Attachments

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Similar threads

Top Liked Posts