yashsingh1/xdaforums huggingface dataset:
[Eee Pad Transformer General] simonplexus:
I threw down a quick and nasty guide to using the PERI recoveryblob and superuser zip file to root the TF101 from linux. I havent ran windows in a long time so thought this may helps someone who is in a similar position. Thanks Thing O Doom for the great work!

http://xdaforums.com/showthread.php?t=2331078
[Eee Pad Transformer General] d3l1:
Can we update to TWRP 2.5.0.0 ourselfs? Goo.Im still has the old 2.3.2.3 blob. My Tab is already rooted thx to PERI, but updating the Recovery would be nice.
[Eee Pad Transformer General] jazzruby:
Yes, check here:

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

-JR-
[Eee Pad Transformer General] tboheeren:
Can anybody tell me if this will work on my B60 TF101 with IML74K.WW_epad-9.2.1.27-20120616? The OP and readme are a bit unclear about .27...

gz
[Eee Pad Transformer General] frederuco:
Yes, it will most definitely work on that firmware.
[Eee Pad Transformer General] HeathicusF:
I can report that PERI V0.42, with TWRP 2.5.0.0 worked perfectly on my wife's TF101 that was stock, unrooted, 9.2.1.27.

Thanks!
[Eee Pad Transformer General] kyleumat:
Serious issues

Hi, I am in serious trouble. I am afraid, I have softbricked my slider sl101.

Running the PERI tool V.04 - I have got to messages that permission is denied and the tablet won´t boot into recovery. Please find two of the screen messages below.

After pressing "Y" in the tools commands...

And then ...

A boot into recovery does not take place. The last screen is..

As you can see above, it is possible to access the slider using adb commands. One more thing: when I type "adb shell" - I will get the "$" sign instead of "#"!

Any ideas? Any hints to solve the problem would be highly appreciated. Thanks in advance, Kai
[Eee Pad Transformer General] jazzruby:
Hi kyleumat,

OK, since you can drop into a shell, run the following commands 1 line at a time:

adb shell
rmdir /data/local/tmp
ln -s /dev/block/mmcblk0p4 /data/local/tmp
exit
adb reboot

Now you need to push some files to the device for processing.

Extract the 'recoveryblob' from OneclickrecoveryV0.4.2.zip

Download Koush's (ClockworkMod dev) Superuser - I've attached a flashable zip.

Make sure they're in the same folder as adb.exe

adb push recoveryblob /sdcard
adb push superuser.zip /sdcard
adb shell
dd if=/sdcard/recoveryblob of=/dev/block/mmcblk0p4
adb reboot

Your custom recovery should be installed now; let's cleanup so you can manually reboot and flash superuser.zip

adb shell rm /data/local/tmp
adb kill-server

Shutdown your device and reboot recovery and flash the superuser.zip that we pushed to /sdcard

HTH,

note: [MENTION=4537017]Thing O Doom[/MENTION] - the Superuser included in PERI is very outdated (and possibly broken in JB), you should include Koush's new Superuser - open source and free 4-ever

GitHub: https://github.com/koush/Superuser

Play Store: https://play.google.com/store/apps/details?id=com.koushikdutta.superuser

-JR-

md5: d4abd6a6fd4483580785361cd1805827 - superuser.zip
[Eee Pad Transformer General] frederuco:
Also, if you want to use a different recovery such as TWRP, just grab that recovery blob instead of CWM. I highly recommend TWRP 2.3.2.3 or the beta 2.5.0.0 unless you plan on using the ARHD ROM.
[Eee Pad Transformer General] jazzruby:
The latest PERI -OneclickrecoveryV0.4.2.zip- already includes 2.5.0.0 (recoveryblob)

Check the OP

-JR-
[Eee Pad Transformer General] kyleumat:
Hi, thank you so much for the quick response and your suggested solution. The problem I have is - as soon as I type in "adb shell" I get the "$" symbol in the next line and all efforts seem to be useless as permission denied is returnd after typing any commands.

In the end the following messages are displayed and nothing has changed so far - (it is only possible to push the files to the sdcard)

Any further suggestions? Thanks for your support. Kai
[Eee Pad Transformer General] kyleumat:
Still serious issues - Slider SL101 won´t boot

Hi experts,

I haven´t gone any further in the meantime. I did manage to access the slider via APX on another PC! But I don´t know which stock image to flash back to the device. I have various clockworkmod backup files on the external SD card. Is it possible to copy them back to the device using adb commands? And then boot from them?

Booting into recovery mode still shows the Android figure and a yellow triangle. :(

Any ideas? Any helpful suggestions would be very welcome! Thanks, Kai
[Eee Pad Transformer General] frederuco:
SL101 and APX does not help because the Secure Boot Key (SBK) is not known for the SL101 so NVFlash is useless.

You have stock recovery installed (dead droid with the ! over him). You will need to get a custom recovery installed via ADB (using commands or PERI) before the CWM backups will help.

Since you have stock recovery, you could put the stock firmware update on an external SD (unzip it once, it will still be a zip) and boot to recovery and it should trigger flashing the stock firmware.

And yes, you can use adb to push files to the internal.

From a command prompt with ADB working to your SL101:

adb push c:\File1.zip /sdcard/

This will push the file so you will get a /sdcard/File1.zip file in the internal memory. You can repeat for as many files as there is space for on the internal memory.
[Eee Pad Transformer General] jazzruby:
Hi kyleumat,

Like frederuco posted; you need to get back to a 'working' system to take advantage of the exploit.

You can download the firmware for the Eee Pad Slider SL101 (this is your device, right?) from:

http://www.asus.com/Tablets_Mobile/Eee_Pad_Slider_SL101/#support_Download_32

Choose 'Android' as the OS and the correct SKU/country firmware

The SOP for installing via ExternalSD (pdf)

http://dlcdnet.asus.com/pub/ASUS/EeePAD/TF201/e7203_TF201_Update_SOP.pdf

What you want is the 'Firmware Update Launcher' not the FOTA.

Although it suggest working from within the system, it should still trigger the update when booting to recovery as long as the zip file is at the root of the ExternalSD.

-JR-
[Eee Pad Transformer General] kyleumat:
Thanks. But I see a white triangle with a yellow ! in it and underneath the little green android.

Pushing files like that will return "is a directory".

So doesn´t work either. :(

---------- Post added at 05:44 PM ---------- Previous post was at 05:39 PM ----------

Thank you. Yes, it is the Eee Pad Slider SL 101. I have tried that: download the firmware (unzip it once), put it on external sd card, put it in the dead slider and boot into recovery. At the end I am still stuck with the EePad Logo (ans the ASUS logo below) and nothing happens. Well, I have tried different firmware versions - but the recovery image still was not recognised.
[Eee Pad Transformer General] jazzruby:
Hi kyleumat,

You need to be a little more specific;

Copied the zip file - US_epad-user-9.2.1.27.1.zip to the root of ExternalSDcard

Place the SDcard back in the device and boot recovery

What happens? Any indication it's flashing? (progress bar, etc...)

Reboot the system; again what happens? Any indication it's building the system up. If so, did you wait long enough?

"but the recovery image still was not recognised" - HUH?

-JR-
[Eee Pad Transformer General] kyleumat:
Hi jazzruby,

yes sure. I have tried as well the US firmware as the other versions WW_epad_user_9_2-1_27.zip and TW_epad_user_9_2-1_27.zip.

After placing the sd card back to the SL101 and booting into recovery, it shows the package (box with the arrow coming out of it) and the android figure - while a progress bar is shown.

After a while the screen turns black and the SL 101 boots again - and stops displaying the Eee Pad logo screen and does not boot any futher - i.e. does not boot the tablet.

What do you suggest? How long do I have to wait (when the first start screen is displayed)?
[Eee Pad Transformer General] jazzruby:
OK so recovery succeeded in flashing (copying the blob to the staging partition), what happens next?

Upon (re)boot, this blob in the 'staging' partition is copied to the device creating the 'system' structure (thin progress bar).

When completed, now your 'data' (userdata) partition will be built-up (dalvik-cache, libs and configs for system apps, etc...); maybe ~5-10 min total depending on how much bloat

Did everything go as I describe above?

-JR-
[Eee Pad Transformer General] kyleumat:
Hi jazzruby,

I have posted some (rather bad) pictures to make clear what´s going on on the screen:

After booting into recovery the following screen appears... (box with arrow and green android figure; progress bar below

Which ends up with ...

Or when sometimes the recovery progress runs through (first image) using another firmware file and the SL101 boots again, it hangs up forever showing this screen...

See what I mean? It seems nothing is being build - no file system no structure...
[Eee Pad Transformer General] jazzruby:
Boot to recovery, connect to your PC/Laptop and adb into the shell and run these commands:

adb shell

df

ls -la

ls -l /dev/block/platform/sdhci-tegra.2/by-name/

Copy/Paste the result for each command separately wrapping them in code tags.

-JR-
[Eee Pad Transformer General] kyleumat:
This is the result for <df>

<

c:\Programme\android\android-sdk\platform-tools>adb shell

* daemon not running. starting it now on port 5037 *

* daemon started successfully *

$ df

df

Filesystem Size Used Free Blksize

/dev 360M 48K 360M 4096

/mnt/asec 360M 0K 360M 4096

/mnt/obb 360M 0K 360M 4096

/system 503M 338M 165M 4096

/cache 521M 8M 512M 4096

/data 26G 172M 26G 4096

/storage/sdcard0 26G 172M 26G 4096

>

This is the result for <ls -la>

<

$ ls -la

ls -la

drwxr-xr-x root root 2013-06-26 19:24 acct

drwxrwx--x system cache 2013-06-26 16:06 cache

dr-x------ root root 2013-06-26 19:24 config

lrwxrwxrwx root root 2013-06-26 19:24 d -> /sys/kernel/debug

drwxrwx--x system system 2013-06-26 19:25 data

-rw-r--r-- root root 116 1970-01-01 00:00 default.prop

drwxr-xr-x root root 2013-06-26 19:24 dev

lrwxrwxrwx root root 2013-06-26 19:24 etc -> /system/etc

-rw-r----- root root 829 1970-01-01 00:00 fstab.ventana

-rwxr-x--- root root 105280 1970-01-01 00:00 init

-rwxr-x--- root root 1223 1970-01-01 00:00 init.cm.rc

-rwxr-x--- root root 2344 1970-01-01 00:00 init.goldfish.rc

-rwxr-x--- root root 17938 1970-01-01 00:00 init.rc

-rwxr-x--- root root 1637 1970-01-01 00:00 init.trace.rc

-rwxr-x--- root root 3915 1970-01-01 00:00 init.usb.rc

-rwxr-x--- root root 58 1970-01-01 00:00 init.ventana.keyboard.rc

-rwxr-x--- root root 8107 1970-01-01 00:00 init.ventana.rc

-rwxr-x--- root root 2982 1970-01-01 00:00 init.ventana.usb.rc

drwxrwxr-x root system 2013-06-26 19:24 mnt

dr-xr-xr-x root root 1970-01-01 00:02 proc

drwx------ root root 2013-06-09 18:28 root

drwxr-x--- root root 1970-01-01 00:00 sbin

lrwxrwxrwx root root 2013-06-26 19:24 sdcard -> /storage/sdcard

0

d---r-x--- system 1028 2013-06-26 19:24 storage

drwxr-xr-x root root 2013-06-26 19:24 sys

drwxr-xr-x root root 1970-01-01 00:00 system

-rw-r--r-- root root 272 1970-01-01 00:00 ueventd.goldfish.rc

-rw-r--r-- root root 5075 1970-01-01 00:00 ueventd.rc

-rw-r--r-- root root 1407 1970-01-01 00:00 ueventd.ventana.rc

lrwxrwxrwx root root 2013-06-26 19:24 vendor -> /system/vendor

>

This is the result for <ls -l /dev/block/platform/sdhci-tegra.2/by-name/>

<

$ -l /dev/block/platform/sdhci-tegra.2/by-name/

-l /dev/block/platform/sdhci-tegra.2/by-name/

-l: permission denied

$

>

Kind regards, Kai
[Eee Pad Transformer General] Thing O Doom:
I'm going to assume you've tried coldbooting after flashing the US FW for your slider,

I'm confused as to why it's not taking anything or why it softbricked in the first place..

JR and Fred have already suggested anything I would have, and aside from manually running commands until the exploit works and cold booting I have nothing left to add.

[MENTION=2805755]jazzruby[/MENTION] I've always preferred SuperSU over superuser tbh, should I still include superuser over supersu? I haven't really messed with either in a bit as I've been using whatever comes with the ROM that I flash on my devices.

EDIT: Also maybe from the coldboot menu choose wipe system and reflash stock via stock recovery then coldboot, that could work..
[Eee Pad Transformer General] jazzruby:
I haven't used SuperSU in a while but Koush's new Superuser is rock solid and is my first and only choice for su/root access control (it's on all my devices).

From the Play Store Description:

-JR-
[Eee Pad Transformer General] frederuco:
I'm a big fan of Koush's SuperUser over chainfire's version and SuperSU.
[Eee Pad Transformer General] mcKidney:
I am having troubles doing the root proccess:

Windows 7 64bit

TF101 (Encrypted)

Android 4.0.3

IML74K.WW_epad-9.2.1.27-20120615

First error I get after installing drivers:

ADB server didnt ACK

*failed to start a daemon*

Device reboots

ADB server didnt ACK

*failed to start a daemon*

Device reboots

No I do not want to push SU zip

Reboot does not start (Power off and then recovery kernel)

Blue Bar for recovery, laying android with alert

Nothing happens 5-10 minutes. Soft reset into normal boot without root access

Repeated 2 to be sure - I cannot wipe cash.

Anybody willing to help me?
[Eee Pad Transformer General] zachf714:
I think it is because your tab is encrypted
[Eee Pad Transformer General] frederuco:
Agreed. Try decrypting (factory reset).
[Eee Pad Transformer General] hemphunter:
Hello,

i used RomManager to install CWM (now i know that tf101g and RM wont work)

after alot of reading i came across this tool to unbrick my tf101g but it wont work.

all i get is this:

List of devices attached

0123456789ABCDEF recovery

If you see your device here this will work, if not fix adb.

Drücken Sie eine beliebige Taste . . .

running fix...

dd: writing '/dev/block/mmcblk0p3': No space left on device

4097+0 records in

4096+0 records out

2097152 bytes (2.0MB) copied, 0.367049 seconds, 5.4MB/s

rebooting tab, if at any step it doesn't reboot turn off and turn back on

Once back into an adb possible state continue...

Drücken Sie eine beliebige Taste . . .

Pushing new recovery...

1330 KB/s (4835404 bytes in 3.549s)

Running wolf's exploit...

mv: can't rename '/data/local/tmp': No such file or directory

Going...

ln: /data/local/tmp: No such file or directory

Done!

Now lets reboot your TF again...

Continue when back into ADB again...

Drücken Sie eine beliebige Taste . . .

Flashing new recovery...

dd: can't open '/sdcard/recoveryblob': No such file or directory

Done!

Continue to reboot your tab, do the button combination to test recovery.

(Hold volume-down as it's rebooting and press vol-up to enter recovery)

any advice would be great =)
[Eee Pad Transformer General] Dude360:
Moved to other thread
[Eee Pad Transformer General] Thing O Doom:
3 errors that would keep it from working for sure. Please don't use ROM manager :/ I have a big warning thread about it.

Try manually running the commands peri runs, (edit the bat to see them)

Make sure adb is working properly still.

I have no idea, this is extremely weird o.e...

RR = Random reboots, randomly (Not just sleep.)

SOD = Sleep of Death, tablet screen goes blank and processor runs hot during sleep, draining the battery totally.
[Eee Pad Transformer General] Dude360:
Moved to other thread

Root-wise, the tool worked spot one, I have root and TWRP so very much appreciated!!!
[Eee Pad Transformer General] hemphunter:
Thanks Thing O Doom,

i managed to flash TWRP with the adb commands and im able to start it but it has the same problem CWM had ... cant mount /data

so i cant flash a new rom =/ any idea how to fix this?
[Eee Pad Transformer General] mcKidney:
Completely clean settings this time (Run as a admin....)

First log with error:

Zerg rushing device.
Just kidding... Running Exploit..
adb server is out of date. killing...
* daemon started successfully *
adb server is out of date. killing...
* daemon started successfully *
Going...
adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
adb server is out of date. killing...
* daemon started successfully *
Done!
Now lets reboot your TF!
adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon

Now the device was not rebooted by the script, so I did cold boot manually.

Lets continue:

This happens on the next step. possibly a result of the previous issue:

______ _ _____ _ _ _____ _ _ _____
1 ____1 1 /\ / ____1 1 1 1_ _1 \ 1 1/ ____1
1 1__ 1 1 / \ 1 (___ 1 1__1 1 1 1 1 \1 1 1 __
1 __1 1 1 / /\ \ \___ \1 __ 1 1 1 1 . ` 1 1 1_ 1
1 1 1 1____ / ____ \ ____) 1 1 1 1_1 1_1 1\ 1 1__1 1
1_1 1______/_/ \_\_____/1_1 1_1_____1_1 \_1\_____1

Let your TF *TOTALLY* reboot.
Now we flash the recovery. I hope it is not offended.
DO NOT UNPLUG DURING THIS PROCESS!!!!!!!
If you do, you might have a *Very* shiny paperweight.
Continue? (Y/N) y
Starting... This will take awhile...
adb server is out of date. killing...
* daemon started successfully *
/dev/block/mmcblk0p4: cannot open for write: Permission denied
adb server is out of date. killing...
* daemon started successfully *
Done! You should see some reported #s above.

Now we reboot the TF again, you'll see a blue bar.
It will take awhile to fill, then you have recovery!
adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon

Note: The script is running from a administrator privileged cmd line.

Now again doing manual cold boot.

Wrong paste, the ROOT screen, successfully pushing the zip file.

Rebooting into recovery:

Blue bar into alert icon (as expected since the new recovery was never written)

So I Cold Booted back to system.

Anybody with another suggestion?

PS: the colors are really annoying :D Poor users without the ability to change them :P
[Eee Pad Transformer General] mcKidney:
A) I changed the colors :P I just wanted to state that. Especially on low color/brightness screens

B) Can you point me in direction of a newer versions of adb?

After analyzing the BAT file I discovered the probable cause - adb reboot is not working correctly in the script.

But when I run the same command manually in the same cmd line it works fine. Now this may not be the cause. I will test it now.

EDIT: It is not only adb reboot. its every command that requires rebooting abd process on your PC.

What happens its: Internal timer is too short and the process is not yet running and the whole command dies.

- As to my knowledge the timer cannot be set.

- success rate is about 75% on my PC.

- restarting the adb process using suggested command does not improve the success rate.

- Not every time you get an error message. Sometimes it just dies without any notice.

So what I did is I edited the BAT script in a set of closed loops and check if every command was executed correctly and now I have the recovery blob on my TF.

It seems that every one of the runs I did failed at one step so it never finished correctly.
[Eee Pad Transformer General] Thing O Doom:
http://developer.android.com/sdk/index.html
[Eee Pad Transformer General] Dude360:
Apologies to inadvertently hijack the thread so have moved posts to new one.
[Eee Pad Transformer General] steve1221:
Hi there,

I've just got a new 101 which is running Android 3.2.1. Am I safe to use this to root and install recovery or do I let it install the .27 update its just download on its own and then run this??

I've rooted a number of phone's but this is my first tab and I don't want to mess it up right at the start!!

Thanks
[Eee Pad Transformer General] Thing O Doom:
Install the update then run the tool c:
[Eee Pad Transformer General] steve1221:
Great, many thanks...
[Eee Pad Transformer General] droidstyle:
Just wanted to say thanks for the instructions...picked up a tf101 on the cheap and had it rooted, recovery, and rom'd in about 20min...lol
[Eee Pad Transformer General] tsch:
Worked perfectly even on Ubuntu. I just used the commands from the .bat file.

Thanks a lot :thumbup:
[Eee Pad Transformer General] zachf714:
A good question for the thread even though I can put together an sh file for ThingODoom .. Is it possible to run bat files in wine, I don't have wine because it removes other programs I need
[Eee Pad Transformer General] tsch:
It is possible to run batch files, but afaik it would run the emulated versions of fastboot and adb which is not what you have installed and intended. Problems on the USB side would also be possible - I'm not sure how wine handles USD devices.
[Eee Pad Transformer General] mltaylo3:
Thing o doom, this worked great on my tf101, many thanks. Please be patient as I ask for help for my ailing tf201. Situation is this, it was rooted with cwm recovery and ics rom. Tried to take jb ota (5 year old did it, but I take the blame, as it should be), which sent it into bootloop. I don't know if I have a hard or soft brick, but if I bold vol down and pwr, I get to a screen shows "rck", android, usb icon, and wipe data. If I choose rck, a blue line briefly appears, then the android fellow falls over with the red triangle. Will peri work and if so, where can I get that recovery blob you speak of in your original post?
[Eee Pad Transformer General] Thing O Doom:
Note for linux users: http://xdaforums.com/showthread.php?t=2331078

He also made a .sh file for it c:

Show to see it:

Thanks to simonplexus for doing that for me :D"""
[Eee Pad Transformer General] Thing O Doom:
JB breaks peri's exploit, so if the ROM updated to jb fully I can't help it.

I recommend NvFlash if you've set it up prior, otherwise use adb to try to run wolf's exploit I suppose.
[Eee Pad Transformer General] yasere:
after many trials and seemingly successful steps,,,,,boot into recovery is still impossible and have to reboot into cold boot every time

My device is TF101G SPK 3 ROM STOCK 9.2.2.6

ANY HELP PLEASE?
[Eee Pad Transformer General] frederuco:
Do you get the dead droid (stock recovery) when trying to boot recovery?

I guess I am a little confused. Does your device boot to the stock ROM normally, or does it hang and you have to do a cold boot to get it to boot the ROM...

And, does your PC see your tablet via ADB? Did you enable USB Debugging in the Developer Settings?
[Eee Pad Transformer General] yasere:
still hangs

my pc recognized tf,,,,,,,,,,,pushing recovery and flashing successful,,,,,,,,,,,and yet,,,,,it requires cold boot and no recovery seems to be installed
[Eee Pad Transformer General] ahoslc:
So I have my tablet back to stock latest from Asus website how do I root and install custom recovery? I tried using the tool and everything looks good but I can't boot into TWRP?
[Eee Pad Transformer General] Thing O Doom:
Can I see PERI's output, b/c it should work if no errors are shown?

Again, can I see the output of the tool?

Make sure drivers an debugging are right, etc. I need more information
[Eee Pad Transformer General] ahoslc:
I got it working I am just unable to flash any roms in recovery now for some reason from internal or external says bad install I tried multiple cm 10 images.
[Eee Pad Transformer General] frederuco:
What version of TWRP are you using and what error message is TWRP saying?
[Eee Pad Transformer General] ahoslc:
I was using the latest from Goomanager and the message was saying bad installation. Tried 3 different CM10 roms all the same message.
[Eee Pad Transformer General] frederuco:
Did the ROMs have md5 checksums you could verify that they were good downloads?

Also, did you use ROM Manager to install CWM before you installed TWRP?

Honestly, the only time I remember TWRP not installing ROMs is when the file was bad.
[Eee Pad Transformer General] yasere:
Output pictures are too large

Thanks for concern

I printed all the output screens but pics are too large to upload,however here are the results

-screen one I choose u to unbrick

-screen 2 prints that permission denied at partition mk something

-after rebooting(cold reboot) flashing is running OK

-two successive screens related to flashing with result DONE

then can't reboot,,can't boot into recovery,,,can't start normally,just cold boot

sorry for inconvenience