yashsingh1/xdaforums huggingface dataset:
[Eee Pad Transformer General] limezone:
I was really hoping I could fix this myself, but unfortunately I need to ask for help.

I found myself in this situation like all of you on Saturday night. I was trying to flash Revolver 4 and I inadvertently flashed a fresh clockwork recovery from ROM Manager, and then the fun began.

I have been playing with my phones (X10a, Captivate, & Inspire) for well over a year and I got the TF for xmas, and have been playing with it ever since. I'm not exactly a newbie. But, I have never had a need for ADB, so until now I've never installed it.

I have now installed ADB, but I can't seem to get it to find the transformer. I've downloaded the drivers, and installed ASUS sync.

When it's in the android OS and I plug the TF into the PC I get nothing . When it's plugged in and I'm in the borked 5.5.0.4 recovery, the PC sees the TF and tries to install the drivers but can't.

suggestions please, thank you.

All I want to do is push the one command and have this episode behind me. I have been losing sleep since it happened. I respect and appreciate everything the devs do, and I take full responsibility for the things I do to my devices. And I have been really beating myself up over this ever since I did it. Thank you all in advance for your help.
[Eee Pad Transformer General] duongdn:
Are you able to cold boot into your rom? If so, just download android terminal from the market and use that to push the commands.
[Eee Pad Transformer General] gee one:
Probably the easiest way out is to head to the command line. You can download a terminal app from the market and use that to type the commands. You won't need to connect via adb, but I think you will need superuser/su. I use android term by jackpal, someone else referenced terminal ide, which seems like it would work too.

The terminal commands will be the same:

su

echo boot | dd of=dev...... etc...

reboot

Just remember that cwm 5.5.0.4 sees the internal sdcard, so put any roms you want to flash in there. You'll probably want to flash a rom straight away since whatever is sitting in your staging partition will flash on reboot.
[Eee Pad Transformer General] Shadow-Nexus:
Hey guys i need serious help here!

so here is my situation

i was in the middle of flashing a new rom when i noticed the recovery glitch

so when i finally cold booted in to the rom since it didnt install completely it broke root

so know i cant do the commands in terminal emulator and when i try to type them trhough recovery my pc doesnt recognize my transformer

Please help guys im really desperate!
[Eee Pad Transformer General] gee one:
Are you desperate enough to flash something that I just cooked up and haven't tested?

It might break your TF worse than it is now or it might fix it. I haven't tested it at all.
[Eee Pad Transformer General] Shadow-Nexus:
What is it?
[Eee Pad Transformer General] gee one:
OK- I tested it "a little" and it didn't break my TF outright and actually seemed to fix the problem.

It's a small flashable zip- so no terminal commands required. You will have to figure out how to get it to the internal sdcard, but it seems like you have rom access still.

PM if you want to test it.

Edit: I did limited testing in roach's 3.2.0.1- the version I am using is vulnerable to recovery bootloops. I did confirm that it stops the bootloops AND it has the added benefit of not wiping out completely the misc/ partition. Just the first 80 bytes.

The zip file just uses busybox to run this command "dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=1 count=80"

There are no fingerprint checks, so only flash this on a TF101. I don't know how other devices use the mmcblk0p3 partition, so flashing this on other devices, including the prime or the tf101G, might have grave consequences.

fingerprint checks removed - you're on your own

by flashing this zip file, you are assuming
all risk, liabilities, and damages, which may include
but are not limited to loss of data, loss of hair,
loss of social life, loss of ipad, rashes, night sweats,
tremors, body odor, and explosive indigestion.

ALLL WARRANTIES REGARDING MERCHANTABILITY OR FITNESS OF PURPOSE,
EXPRESSED OR IMPLIED, ARE DISCLAIMED.

If anything goes wrong, it's your own fault
[Eee Pad Transformer General] feisty_noodle:
gee one,

I think we already established that blanking just the 5th byte is sufficient to disrupt the interpretation of the string by the bootloader.

I have seen the entire string 'boot-recovery' blanked out (0x0) by Rogue recovery on boot (without touching the downstream data).

So, maybe you can be even more conservative and just touch a byte or two at 0 offset. That way there is nothing that can go wrong (I know, "famous last words").
[Eee Pad Transformer General] limezone:
I had thought of the terminal app just before I posted my disparate plea.

That seems to have done the trick. I can boot up normally and I can get into recovery (roach's 3.2.0.1), so I think my long nightmare may be over. Thank you, thank you, thank you.
[Eee Pad Transformer General] cabraswell:
If you'll use the drivers posted here they should work and allow you to use adb. I had to use these just a couple of days ago while the TF was in CWM and they worked great. Hope this helps!
[Eee Pad Transformer General] xandr115:
Thanks guys! I was stuck on this because I didn't see/read the instructions on the 1st screen (when you boot w/ pwr+voldn) to press volup within 5 seconds to get into the bad CWM, so I could flash the good CWM, then ran the dd command in terminal emulator and voila. Again, much appreciation.
[Eee Pad Transformer General] Trinicki:
i need some help ...

i have read numerous threads on what to do if my device is stuck in recovery loop... i have roach's updated recovery zip, tf101-r2 in a folder in my internal share and i understand i need to run the command to get the previous recovery removed.

adb shell dd if=/dev/zero of=/dev/block/mmcblk0p3

i cannot connect my laptop to the tf101, its not recognized no matter what ive done. Unistalled the Asus ADB Interface via device manager and then reinstalled using Naked drivers. tablet shows up as MTP USB device but always "cannot start (error 10)"

i tried to run the command via Terminal on tablet but "device not found"

any suggestions?
[Eee Pad Transformer General] partio:
can you boot in androd os ?
[Eee Pad Transformer General] Trinicki:
yes, i can boot into EOS nightly 4.

i got wireless to connect and i did try to install Team Rogue recovery in hopes that would help but im guessing i still have to clear out recovery 5504(?)

continues to recovery loop
[Eee Pad Transformer General] partio:
boot in 5504 recovery and install the new recovery you have in internal sd.

dont press reboot system now , make a cold boot , power button+volume down and wait .

after booting the android os , run terminal emulator , and type:

su

echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0

reboot

then , tf will reboot and you can see now the bar progres updating recovery
[Eee Pad Transformer General] Trinicki:
thank you, good to go
[Eee Pad Transformer General] PaliFarkas:
Maybe I will help someone. It really works. It is copy-paste from shell after I solved my reboot problem.

C:\android-sdk\platform-tools>adb shell

/ $ su

su

/ # mount -o rw,remount -t yaffs2 /dev/block/mmcblk0p3 /system

mount -o rw,remount -t yaffs2 /dev/block/mmcblk0p3 /system

/ # dd if=/dev/zero of=/dev/block/mmcblk0p3

dd if=/dev/zero of=/dev/block/mmcblk0p3

/dev/block/mmcblk0p3: write error: No space left on device

4097+0 records in

4096+0 records out

2097152 bytes transferred in 0.641 secs (3271687 bytes/sec)

/ # dd of=/dev/block/mmcblk0p3 bs=1 seek=0

dd of=/dev/block/mmcblk0p3 bs=1 seek=0
[Eee Pad Transformer General] gee one:
That obviously works, but you are also erasing anything else that might be in /misc. Using bs=1 count=80 might be safer.

sent from my android tablet
[Eee Pad Transformer General] Muskoka:
Thank you so much, worked for me on C10 serial number.
[Eee Pad Transformer General] FatGuyWithWifi:
whats the code to push something to your sd card

also my clockwork wont read any changes to my sd card so what code would i use to force it to flash the new recovery or w/e
[Eee Pad Transformer General] Kaine16:
I love u sir
[Eee Pad Transformer General] partio:
recovery 5504 recognizes only the internal memory.

if you cant start the operating system , but you can get adb ,rename the new recovery you want to install to recovery.zip , and put it in the adb.exe folder .

I think the folder visible in the internal memory is /data/media

tried first:

adb push recovery.zip /data/media

now checks in 5504 install from zip tab if it appears your new recovery.zip

install it

adb again :

adb shell

echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0

reboot
[Eee Pad Transformer General] pmdied:
fwiw- I got stuck in the recovery bootloop AFTER installing AOKP which DID NOT have gapps pre-installed. After installing everything and then doing an older titanium backup, including system + data + apps is when I ran into problems.

See, after deciding to return to my nandroid backup of CNA I got stuck in the bootloop mode. I'm not sure what the exact sequence of events where but I think doing a system restore might have put corrupt data on my pad.

To fix, I installed CNA (which had gapps in it) and then cold booted to Android which then booted up to CNA. Let me know if I can clarify this for anyone in a similar situation.

Again, my thoughts were that titanium was the culprit here but I could be wrong..
[Eee Pad Transformer General] Dan_Brutal:
I was ****ting bricks until I saw your post. Thanks for the info!!!:D:D
[Eee Pad Transformer General] yakabud:
It worked

Yes! Tried it with Terminal, did exactly what it says. Now I'm out of ClockWork boot-loop.
[Eee Pad Transformer General] DanDem:
My TF got stuck in Recovery Loop, please help.

Tried this:

adb push cr.zip /data/media

where cr.zip is ClockworkMod Recovery 5.5.0.4 roach-tf101-r2

Got this:

failed to copy 'cr.zip' to '/data/media/cr.zip': Permission denied

This command

echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0

returns

/dev/block/mmcblk0p3: cannot open for write: Permission denied

Please let me know what to do, thank you in advance.
[Eee Pad Transformer General] partio:
are you sure you have the cr.zip in the same folder as the adb.exe?

to run the echo command .... first you have to have root privileges.

first type adb shell, and if you get the # symbol are already a root, then type the command echo .....
[Eee Pad Transformer General] DanDem:
Ok, first problem fixed by usin Root explorer and Set Permission on /media/ to 777

(R/W) to all.

after it file copied and I was able to flash it.

For adb shell I get "$" instead "#" but not sure right now will confirm late.
[Eee Pad Transformer General] partio:
root explorer ?

if you can boot into android system , no needed adb , use the other method

boot in 5504 recovery and install the new recovery you have now in internal sd.

dont press reboot system now , make a cold boot , power button+volume down and wait .

after booting the android os , run terminal emulator , and type:

su

echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0

reboot
[Eee Pad Transformer General] DanDem:
Let me make all my steps clear:

1. Power On TF, will boot into Recovery

2. Select Install zip. in my case cr.zip ClockworkMod Recovery 5.5.0.4 roach-tf101-r2

3. Power button+volume down and wait

4. How to run terminal emulator ? adb emu?

5. su

echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0

reboot
[Eee Pad Transformer General] partio:
first af all , have you installed superuser.app ?

go to market , download and install : superuser and terminal emulator.

run terminal , and type su , superuser app ask to you if allow or not , allow.

if this work ok , and you see # , make the steps in your post above.
[Eee Pad Transformer General] baseballfanz:
After booting back into the OS download terminal emulator from Play Store.

https://play.google.com/store/apps/...251bGwsMSwyLDEsImphY2twYWwuYW5kcm9pZHRlcm0iXQ..

Opem TE and type in SU, you should get a # after which type in the rest of

the command in step 5
[Eee Pad Transformer General] DanDem:
partio & baseballfanz !!!

Thank you so much, TF is back to normal. :)
[Eee Pad Transformer General] partio:
ok , anyway, you should install another recovery, 5504 recognizes only the internal memory

what was your problem in the end ? superuser ?

could be useful to leave your testimony, for people who enter with your same problem and situation
[Eee Pad Transformer General] zhawk777:
Recovery 5.5.04

I used these instructions on a US Version Rooted Revolver 4.0.3 Rom after I accidentally flashed recovery through ROM manager. I re-flashed Rogue Recovery ver. 1.3.0 (which I had prior to the accident) from the internal SD Card. Then I cold-booted using the by pressing power and then holding volume down until it brought me to APX mode. When I got back into the ROM I used the terminal emulator app, and typed the command provided by gee one, character for character and it worked like a charm. I have yet to run into a situation I haven't been able to either solve myself, or research and solve with the help of the loud and proud Android community! Thanks
[Eee Pad Transformer General] brando56894:
IDK what I'm doing wrong but I can't get the fix to work. I tried it in W7 but ADB wouldn't work in recovery since I didn't know where to get the recovery drivers. So I booted to Linux Mint and attempted it from there but this is what I get:

$ ./adb shell echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
dd: opening `/dev/block/mmcblk0p3': Permission denied
$ ./adb shell
~ # su
/sbin/sh: su: not found

I'm pretty adept at Linux and Android/rooting in general (4th Android device) but this problem baffles me! :confused:

edit: apparently I had to do it from within the shell...
[Eee Pad Transformer General] vp-flash:
I try to make "adb push ...." i get an erro "device not found". I dont understand why this happens becauce if i execute "adb devices" i see my device in result list.

I try many commands but or give this error or give me permission denied like the previous post. I don't know what i can do to recovery my asus tf101 :(
[Eee Pad Transformer General] klutch:
were do i get the recovery zip for my TF201 this is been for a min my TF is acting like that and i am braking my head here since i came from vacation this happen help a brother out here cuz i know we r family here (links or info plz)
[Eee Pad Transformer General] brando56894:
@VP: the "device not found" error isn't about the TF itself but either the source or destination device. IIRC you don't need to prefix adb push with adb shell

@klutch: I'm not sure if the 101 zips will work for the 201 but if they do search for cwm or clockwork in the dev section.
[Eee Pad Transformer General] klutch:
i mean i am not going risk it putting a file from another transformer i rather find the one for mines but being on hold n wait for any answers is ganna be pain in the ass to wait but then again dont know if they do share the same files :(
[Eee Pad Transformer General] vp-flash:
What i can do to remove this app from my tablet?

If i format system folder in Clockworkmod, after i can install a clear rom? thanks
[Eee Pad Transformer General] feisty_noodle:
You might want to explain a little. What are you trying to do exactly?
[Eee Pad Transformer General] bskbeast:
have the same problem. tryed to install the driver but it is no signed so it wont install.
[Eee Pad Transformer General] partio:
well , i have a big problem.

a friend with this problem , after trying for himself, has come to me with the problem.

the situation is:

cant boot into system , i think he tried to install a new rom and now stuck on the screen of eepad if i make a coldboot.

adb is workin right , i can push the new recovery , and ls /data/media show me the recovery.zip .

but , in recovery , install zip from sdcard give me a error :cant mount sdcard.

if i try , mounts and storage , mount data , give me the same error .

any idea ??
[Eee Pad Transformer General] feisty_noodle:
Do you see anything else in /data/media ?

I think you may be writing into the /data/media directory when you push, instead of writing to the partition.

The problem is that the partition is not mounted immediately as recovery starts.

The /data/media directory is just a mount point, and it needs to be empty to be useful.

Try this:

1) reboot recovery

2) go to "install zip from sdcard" and make sure you succeed in reading the contents of that directory

3) exit out of the "install zip from sdcard" menu option

4) push the file using adb

5) try to go back in and you should see the zipfile you want to flash

good luck
[Eee Pad Transformer General] partio:
in recovery mode , if i go to install zip from sdcard , give me a error : cant mount sdcard.

then , adb devices

123456abcd recovery , something like that

adb push recovery.zip /data/media succeed

adb ls /data/media , show me the recovery.zip and two more files in /data/media

close adb , go to recovery , but install from sdcard give me a cant mount sdcard
[Eee Pad Transformer General] DanDem:
I think I had a problem with Recovery installed by ROM Manager.
[Eee Pad Transformer General] gee one:
what does "mount" and "cat /etc/recovery.fstab" show in recovery?

I think you might have to mount the data partition manually.
[Eee Pad Transformer General] feisty_noodle:
It gives you that when you reboot the recovery? From the very start?
[Eee Pad Transformer General] partio:
dont understand , show in recovery?

---------- Post added at 03:32 AM ---------- Previous post was at 03:31 AM ----------

yep , reboot into recovery and "cant mount sdcard" when try to install from sdcard
[Eee Pad Transformer General] feisty_noodle:
When you are connected in adb, type 'mount' and paste the result here, in the forum.

Also, paste the result of 'cat /etc/recovery.fstab'

Also, after a fresh restart paste the result of 'ls /data/media'

This will make it more clear what is going on.
[Eee Pad Transformer General] partio:
ok , I have no access to the tablet until tomorrow morning, here in Spain is now 3.37

see you tomorrow with news
[Eee Pad Transformer General] Kalx007:
i am so dead !

I am stuck.

a) i have CWM5.5.0.4 on my WW tf101G

b) i can go to recovery mode

c) since i wiped uo my ROM i cannot boot up

d) i dont have any ROM-s or other version Recoverys on my internal SD

e) can not access external SD (5.5.0.4)

f) my version sticker is missing from my eeepad (can not confirm version)

...

what are my options?

can i somehow access my internal sd?

how to boot up in APX?

last time i had so much pain in my head was back in ealry 90´s. when i was building COVOX for my 386.
[Eee Pad Transformer General] partio:
C:\Users\ROBERYBEA>adb ls /data/media

000041ed 00000000 4f6b1a6a .

000041ed 00000000 4f6b1a6a ..

C:\Users\ROBERYBEA>adb push recovery.zip /data/media

1319 KB/s (4679199 bytes in 3.463s)

C:\Users\ROBERYBEA>adb ls /data/media

000041ed 00000000 4f6b1ae3 .

000041ed 00000000 4f6b1a6a ..

000081b6 0047661f 4f6915c8 recovery.zip

C:\Users\ROBERYBEA>

C:\Users\ROBERYBEA>adb shell

~ # mount

mount

rootfs on / type rootfs (rw)

tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)

devpts on /dev/pts type devpts (rw,relatime,mode=600)

proc on /proc type proc (rw,relatime)

sysfs on /sys type sysfs (rw,relatime)

/dev/block/mmcblk0p2 on /cache type ext4 (rw,nosuid,nodev,relatime,user_xattr,ac

l,barrier=1,data=ordered)

~ #

C:\Users\ROBERYBEA>adb shell

~ # cat /etc/recovery.fstab

cat /etc/recovery.fstab

# mount point fstype device

/system ext4 /dev/block/mmcblk0p1

/cache ext4 /dev/block/mmcblk0p2

/staging ext3 /dev/block/mmcblk0p4

/data ext4 /dev/block/mmcblk0p7

~ #

how can i mount data ?

mount ext4 /dev/block/mmcblk0p7 /data wait noatime nosuid nodev ??

or simply

mount ext4 /dev/block/mmcblk0p7 /data
[Eee Pad Transformer General] partio:
apx mode is for work with nvflash , only for sbk1 (b60 models and some b70)

volumeup + power and plug to your pc , i think you will see the drivers installation .

try nvflash , if you get error , your tablet not compatible.

if you get adb from recovery , you can use adb for this.
[Eee Pad Transformer General] gee one:
I'm not completely sure, but it will be something like

mount /dev/block/mmcblk0p7 /data

Or

mount /dev/block/mmcblk1p1 /sdcard

You have to mount it where cwm will look for it, which I thought was /sdcard ? You also might need "mkdir /sdcard" to create the mountpoint first. It won't be permanent since it will just create the dir on the tmp fs. The critical thing is to create a mount point that cwm will see and push your rom to it.

sent from my cyanogen(mod) vision
[Eee Pad Transformer General] partio:
I'm doing this through a remote desktop, I have not the tablet , uff

i think , this recovery only see /data/media

go to try first /sdcard

then :

adb shell

mkdir /sdcard

mount /dev/block/mmcblk1p1 /sdcard

push recovery.zip /sdcard

and try to install zip in recovery tab

right?
[Eee Pad Transformer General] gee one:
That seems ok, but keep in mind you want to use whatever cwm is expecting to find.

sent from my cyanogen(mod) vision
[Eee Pad Transformer General] partio:
C:\Users\ROBERYBEA>adb shell

~ # mount /dev/block/mmcblk0p7 /data

mount /dev/block/mmcblk0p7 /data

mount: mounting /dev/block/mmcblk0p7 on /data failed: Invalid argument

~ #

C:\Users\ROBERYBEA>adb push recovery.zip /sdcard

1318 KB/s (4679199 bytes in 3.464s)

C:\Users\ROBERYBEA>adb shell

~ # ls /sdcard

ls /sdcard

/sdcard

~ #

and , from recovery the same error tryng install zip from sdcard , cant mount

if i try remount -a , give me a error mounting /data
[Eee Pad Transformer General] gee one:
Did your friend do a wipe or superwipe? If /data is not formatted, then it won't mount because there is no file system.

If he wiped it, it will need to be formatted first. This could be done through cwm or adb, depending on what is available.

sent from my cyanogen(mod) vision
[Eee Pad Transformer General] Headcase_Fargone:
Just came across this thread after posting in another about this exact issue. Is there a fix for this that doesn't involve ADB yet? I've never messed with any of that before...
[Eee Pad Transformer General] partio:
Yesterday I said the same thing, and he said he had made the wipes from recovery and from the screen coldboot

i think , from recovery only option is format sdcard , not individually

how to do format /data from adb?

well , I do it all from beginning , wipes from recovery , wipe data factory from asus coldboot screen , and then :

adb shell

mount

and try to mount /data if not

---------- Post added at 07:03 PM ---------- Previous post was at 06:58 PM ----------

adb is needed , at least to push the new recovery you need to flas . to the internal sdcard
[Eee Pad Transformer General] feisty_noodle:
If you are on US or WW, then flash this (@gee one made it especially for this case):

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

If you don't have a way to deliver it to your internal sdcard partition (i.e. you cannot cold-boot), you still will have to set up ADB and get your hands dirty.
[Eee Pad Transformer General] Headcase_Fargone:
I can cold-boot fine. I'll try this as soon as I get home. Here, have a thanks.
[Eee Pad Transformer General] feisty_noodle:
This seems wrong.

You intended to copy file recovery.zip to a directory /sdcard.

Instead, you copied file recovery.zip to a file /sdcard.

This is what you need to do:

1) reboot the system into recovery. this will clear all the mess and you will end up with a clean recovery loaded in the ramdisk

2) go into the recovery menu and select "install zip from sdcard"

3) select "choose zip from card". at this point you should see a listing of the internal sdcard or get an error of some kind. If you see a listing, that means that the sdcard was mounted on /sdcard (which is actually a symbolic link to /mnt/sdcard or something).

If you succeed, you should be able to push to internal; otherwise, report your error messages here.

Remember, when recovery starts the internal sdcard is not mounted!

Do not push anything or you will write files that will mess things up.