yashsingh1/xdaforums huggingface dataset:
[Eee Pad Transformer General] partio:
from recovery , install from sdcard allways give me :cant mount sdcard

the folder this recovery open to seek zips is /data/media

/sdcard dont exist , only a test i made

mkdir /sdcard

mount /dev/block/mmcblk1p1 /sdcard

and push here a zip to see if recovery can see this folder
[Eee Pad Transformer General] feisty_noodle:
that sounds like a good plan.

If something fails, I would also try to symlink /sdcard to point to /data/media,

then mount /dev/block/mmcblk1p1 /data/media

and check the file listing again
[Eee Pad Transformer General] partio:
mkdir /sdcard

mount /dev/block/mmcblk1p1 /sdcard

and push here a zip to see if recovery can see this folder

dont work , recovery give me the same error , cant mount sdcard

well , I started from scratch

from recovery :

all wipes , then i tried to format data , error mounting data skipin

then , volumedown+power , wipedata , seems to do ok.

then back to recovery and try to install zip , cant mount data

try format data , error mounting data skiping.

go to adb :

Microsoft Windows [Versión 6.1.7601]

Copyright (c) 2009 Microsoft Corporation. Reservados todos los derechos.

C:\Users\ROBERYBEA>ab devices

"ab" no se reconoce como un comando interno o externo,

programa o archivo por lotes ejecutable.

C:\Users\ROBERYBEA>adb devices

List of devices attached

0123456789ABCDEF recovery

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)

~ # 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

~ # mount /dev/block/mmcblk0p7 /data

mount /dev/block/mmcblk0p7 /data

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

~ # mount /dev/block/mmcblk0p1 /system

mount /dev/block/mmcblk0p1 /system

~ # mount /dev/block/mmcblk0p4 /staging

mount /dev/block/mmcblk0p4 /staging

~ # 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)

/dev/block/mmcblk0p1 on /system type ext4 (rw,relatime,user_xattr,acl,barrier=1,

data=ordered)

/dev/block/mmcblk0p4 on /staging type ext3 (rw,relatime,errors=continue,barrier=

0,data=writeback)

~ # umount /dev/block/mmcblk0p7 /data

umount /dev/block/mmcblk0p7 /data

umount: can't umount /dev/block/mmcblk0p7: Invalid argument

umount: can't umount /data: Invalid argument

~ #

mount before and after

all seems to mount perfect except data
[Eee Pad Transformer General] isinisterx:
My transformer isn't becomming online in adb

everytime i type adb devices it keeps saying that its offline, any way to fix this?
[Eee Pad Transformer General] partio:
try

adb kill-server

and adb devices again

if you are in front usb try to change rear
[Eee Pad Transformer General] isinisterx:
Thank you! Guess adb doesn't like USB 3.0 :P

Thought I lost my Transformer for a minute
[Eee Pad Transformer General] feisty_noodle:
according to your output, /dev/block/mmcblk0p7 of type ext4 is already mounted on /data

Try 'ls /data' and see what's there.

Which recovery is this again? I have never seen these kinds of issues.

Also, a weird question: the user data was never encrypted using the ICS security menu option, right?
[Eee Pad Transformer General] feisty_noodle:
Also, what does the system say when you play with the menu options in the "mounts and storage" section of the CWM main menu?
[Eee Pad Transformer General] partio:
you are looking the cat /etc/recovery.fstab

~ # 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

this is mounted with recovery , only cache

~ # 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)

and then i tried to mount the rest (data , system and staging)

~ # mount /dev/block/mmcblk0p7 /data

mount /dev/block/mmcblk0p7 /data

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

~ # mount /dev/block/mmcblk0p1 /system

mount /dev/block/mmcblk0p1 /system

~ # mount /dev/block/mmcblk0p4 /staging

mount /dev/block/mmcblk0p4 /staging

---------- Post added at 10:40 PM ---------- Previous post was at 10:38 PM ----------

if i try to mount data , cant mount
[Eee Pad Transformer General] feisty_noodle:
Oops. right you are!

Reading too fast.

And what about encryption? never done it, right?

Also, can you mount /dev/block/mmcblk0p7 on a different mountpoint?
[Eee Pad Transformer General] partio:
asking him now .

i think , mounting /dev/block/mmcblk0p7 on a different mountpoint make that recovery cant use it .

without encryption tells me
[Eee Pad Transformer General] feisty_noodle:
This is just to make sure that the partition can be recognized and mounted, in principle.

Check that there is nothing in the /data directory:

'ls -a /data'
[Eee Pad Transformer General] gee one:
My guess is that /data is either encrypted or not formatted as ext4. The other partitions seem ok, although I wonder why the other partitions aren't mounted at startup via fstab?

Would it be possible to zero it out and format it if it is encrypted? Or does the partition table flag it somehow?
[Eee Pad Transformer General] feisty_noodle:
The rumor out there is that only the stock recovery can wipe an encrypted /data partition. I have a hard time imagining what could be so magic about the stock recovery, but I have no test cases.
[Eee Pad Transformer General] partio:
C:\Users\ROBERYBEA>adb shell

~ # ls -a /data

ls -a /data

. .. media

~ #

~ # ls

ls

cache proc system

data res tmp

default.prop root ueventd.goldfish.rc

dev sbin ueventd.rc

etc sdcard ueventd.ventana.rc

init staging

init.rc sys

~ #
[Eee Pad Transformer General] feisty_noodle:
The /data directory should be empty. You should only see '.' and '..'

Try moving /data/media someplace and try mounting again.
[Eee Pad Transformer General] partio:
how to ? command please
[Eee Pad Transformer General] feisty_noodle:
type this:

mv /data/media /media_temp

then verify that it worked:

ls /data

ls /
[Eee Pad Transformer General] partio:
Microsoft Windows [Versión 6.1.7601]

Copyright (c) 2009 Microsoft Corporation. Reservados todos los derechos.

C:\Users\ROBERYBEA>adb devices

List of devices attached

C:\Users\ROBERYBEA>adb devices

List of devices attached

0123456789ABCDEF recovery

C:\Users\ROBERYBEA>adb shell

~ # mv /data/media /media_temp

mv /data/media /media_temp

~ # mount /dev/block/mmcblk0p7 /data

mount /dev/block/mmcblk0p7 /data

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

~ # ls -a /data

ls -a /data

. ..

~ # exit

exit

C:\Users\ROBERYBEA>

well, I'll eat something

proves luck tomorrow with the sparted

can anyone confirm to me that sbin is the right folder for this :

adb push e2fsck /sbin/

adb push resize2fs /sbin/

adb push mke2fs /sbin/

adb push parted /sbin/

adb push sdparted /sbin/

adb push tune2fs /sbin/

adb shell

cd sbin

chmod 0755 e2fsck

chmod 0755 resize2fs

chmod 0755 mke2fs

chmod 0755 parted

chmod 0755 sdparted

chmod 0755 tune2fs

parted /dev/block/mmcblk0 mkfs ext2

when ask number - 7

to see table of partitions command "print"
[Eee Pad Transformer General] feisty_noodle:
sucks.

This is a good reference for repartitioning on Android, if it comes to that:

http://xdaforums.com/showpost.php?p=13971291&postcount=110

Edit:

Also, I don't think you need to push any executables anywhere. The recovery includes busybox, so you should be covered.
[Eee Pad Transformer General] pbaldw10:
@ gee one

You saved my tf, the wife was really getting dark on me for messing it up. I used the command from the terminal on my tf and all is well now. Thanks
[Eee Pad Transformer General] partio:
I think I have it almost

/sbin # chmod 0755 mke2fs

chmod 0755 mke2fs

/sbin # mkfs.ext2 /dev/block/mmcblk0p7

mkfs.ext2 /dev/block/mmcblk0p7

mkfs.ext2: lseek: Value too large for defined data type

/sbin # mke2fs -j /dev/block/mmcblk0p7

mke2fs -j /dev/block/mmcblk0p7

mke2fs 1.41.11 (14-Mar-2010)

Filesystem label=

OS type: Linux

Block size=4096 (log=2)

Fragment size=4096 (log=2)

Stride=0 blocks, Stripe width=0 blocks

877824 inodes, 3508864 blocks

175443 blocks (5.00%) reserved for the super user

First data block=0

Maximum filesystem blocks=3594518528

108 block groups

32768 blocks per group, 32768 fragments per group

8128 inodes per group

Superblock backups stored on blocks:

32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208

Writing inode tables: done

Creating journal (32768 blocks): done

Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 36 mounts or

180 days, whichever comes first. Use tune2fs -c or -i to override.

/sbin # exit

exit

and now:

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)

~ # exit

exit

C:\Users\ROBERYBEA>adb devices

List of devices attached

0123456789ABCDEF recovery

C:\Users\ROBERYBEA>adb shell

~ # mount -a

mount -a

~ # 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)

/dev/block/mmcblk0p7 on /data type ext4 (rw,nodev,noatime,nodiratime,user_xattr,

acl,barrier=1,data=ordered)

/dev/block/mmcblk0p1 on /system type ext4 (rw,relatime,user_xattr,acl,barrier=1,

data=ordered)

~ # exit

exit

The problem now , is that I think is not really ext4, is ext3 , and recovery cant see the folder.

when i try install zip , choose zip from sdcard , it gives me no files to install o something like that.

parted say , its ext3

/sbin # parted /dev/block/mmcblk0p7

parted /dev/block/mmcblk0p7

GNU Parted 1.8.8.1.179-aef3

Using /dev/block/mmcblk0p7

Welcome to GNU Parted! Type 'help' to view a list of commands.

(parted) print

print

print

Model: Unknown (unknown)

Disk /dev/block/mmcblk0p7: 14.4GB

Sector size (logical/physical): 512B/512B

Partition Table: loop

Number Start End Size File system Flags

1 0.00B 14.4GB 14.4GB ext3

(parted)

how can i convert this

maybe:

# tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p7

# e2fsck -pf /dev/block/mmcblk0p7

or

# e2fsck -fD /dev/block/mmcblk0p7
[Eee Pad Transformer General] feisty_noodle:
Looks good.

The internal sdcard space is located in /data/media.

Move the file there and try checking again:

mv /data/recovery.zip /data/media/
[Eee Pad Transformer General] partio:
i pushed recovery.zip in /data and in /data/media at the same time before the ls that i posted above

something is slipping through my fingers

last night browsing around, I found this about 5.5.0.4:

""It made me think about what I did last night when I was discussing the /sdcard mounts and /data partition clears with Yeahha...

Okay, I think I might have figured-out the issue with pushing files to the /sdcard and why it doesn't work at times.

Here's the deal: the /data partition is not mounted until you've navigated to the Apply update from .zip file on SD card menu and you have selected the "choose zip from sdcard" entry!

You'll notice a slight delay the first time you enter that menu--that's when the /data partition is mounted.

So, you can make sure your symlinked /sdcard is mounted by making it to the Choose a zip to apply menu, selecting "+++++Go Back+++++", pushing your .zip file, and then re-selecting "choose zip from sdcard", your file will be present.

I'm thinking that when you push the file to /sdcard or to /data/media too early, i.e., before /data is actually mounted, that file is lost because its actually being done in the ramdisk and not in the proper /data partition.

It all makes sense now, LOL, I'll update my notes and instructions to reflect this.

I should have seen this earlier and it all fits and is consistent with the behavior that I have observed (and re-tested).""

I'll try a little later

my friend is in another part of Spain, and I'm doing this through a remote desktop, is a bit complicated without being physically the tablet
[Eee Pad Transformer General] partio:
this is driving me crazy, I'm running out of ideas.

Well, testing what the previous post:

fresh restart recovery:

attempt to install from zip, zip choose from, and recovery mounted data by itself , and :

ClockworkMod Recovery v5.5.0.4

Couldn't open directory.

Couldn't open directory.

No files found.

go to adb shell , and :

/data # ls -a

ls -a

. app-private dontpanic local misc

.. dalvik-cache drm lost+found property

app data gps media resource-cache

/data # exit

exit

then :

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

1331 KB/s (4679199 bytes in 3.432s)

try install from , choose from , and get the same error

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

1331 KB/s (4679199 bytes in 3.432s)

try install from , choose from , and get the same error

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

1331 KB/s (4679199 bytes in 3.432s)

try install from , choose from , and get the same error

I tried also, rename recovery.zip to update.zip recovery , push to /data/media and to /sdcard and trying to apply update, and get the same error

could be a problem ?

/dev/block/mmcblk0p7 on /data type ext4(rw,nodev,noatime,nodiratime,user_xattr,acl,barrier=1,data=ordered)

in my tablet is:

/dev/block/mmcblk0p7 on /data type ext4 (rw,relatime,barrier=1,data=ordered)
[Eee Pad Transformer General] feisty_noodle:
The recovery should generate a log in /cache.

Check there for useful clues.
[Eee Pad Transformer General] eisdrachen:
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0

this won't be recognized in my adb...
[Eee Pad Transformer General] partio:
my friend is not online , cant test anything now.

I've been doing some tests on my own tablet.

I mounted my external sd as /data

mount /dev/block/mmcblk1p1 /data

adb push recovery.zip /data/media/recovery.zip

go to recovery , install zip from sdcard , install from internal , and there is recovery.zip and my folders on external sdcard.

can not be so easy....

I have not the recovery 5.5.0.4 and my tablet is not sick, I'll have to try it when I can in his.

---------- Post added at 10:11 PM ---------- Previous post was at 10:10 PM ----------

adb shell

then #

put the comand
[Eee Pad Transformer General] eisdrachen:
Thanks! Awesome... And now i need wifi and 3g turned on. :D
[Eee Pad Transformer General] partio:
it worked ....

I mounted the external sd as /data

mount /dev/block/mmcblk1p1 /data

adb push recovery.zip /data/media/recovery.zip

then go to 5.5.0.4 recovery , install , choose , and boom : recovery.zip ¡¡¡

recovery flashed , and rom flashed

I cant believe how easy it was to end , 5.5.0.4 is finally able to read external sd with this cheat.
[Eee Pad Transformer General] dimitarc:
This is the end of my log from nvflash. Now I have a brick. Previously I was able to boot in to the bad 5.5.0.4 recovery. Now its a brick. Not recognized via USB, screen not turning on etc.

Any help guys?

Edit: I can see the device as APX, but I cant update the driver. It says that its already the newest and best. Steel, black screen, cant connect to adb :S

Any help would be awesome.

Edit #2: nvflashtf worked when I tried again. I need to buy someone a pack beer for this. Can I get paypal from the developer?
[Eee Pad Transformer General] partio:
download rogue recovery for nvflash here:

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

unzip , and run download.bat from this rogue folder.

ok , ok , I had not read your second edit
[Eee Pad Transformer General] MysticDeth:
I am having a hard time trying to push the good recovery onto my internal SD Card...I flashed CWM in Rom Manager and then flashed Roaches CWM so I am stuck in a bootloop...I am trying to open adb in platform tools and the program opens with fast writing then closes a second later...My Asus Transformer is connected to CWM recovery v5.5.0.4 and is currently connected to the USB...Can someone here help out this poor noob :D
[Eee Pad Transformer General] muryoh:
This thread (and Roach's fixed version) saved my day. Thanks ;)

MysticDeth, you may need to launch it from a command-line prompt. adb's a command-line tool and will not start a graphic interface. This post looks nice: http://xdaforums.com/showthread.php?t=1265634
[Eee Pad Transformer General] anunna:
anunna

I installed CWM through ROM Manager which messed everything up. I wanted to try a different ROM so I wiped everything and tried to install new ROM but it wouldn't do it...no worries I backed up a couple of hours before anyway so I just needed to restore, only this piece of crap recovery was reading from internal memory and not sdcard. NO BACKUPS NO ROMS etc.

I used adb to push ROMs and different recoveries but nothing worked upon flashing. It didn't seem to do anything this new recovery. I tried all sorts off xda and elsewhere...

The link below is all I needed to do and then install Roach's old recovery again then I could restore everything after having a big shiny table mat for a few days just showing that ****ty recovery page that did nothing. ROM Manager uninstalled and everything fine ahhh deep breaths.

http://xdaforums.com/showpost.php?p=23339963&postcount=249

This did it for me...3rd line in Roach's post

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

Koush is good for most other devices CWM wise but I'm sticking with Roach now on Transformer.
[Eee Pad Transformer General] daedalusbound:
in the OP you should probably mention that the command can be run in a terminal emulator if you can cold boot, it will save some people some time probably

i was able to get a new recovery installed and am no longer getting a recovery bootloop, but i'm not able to access external media, which started when i initially got stuck in the recovery bootloop, and also settings will crash when i try to go to storage settings

has that issue been solved or is it not entirely related? reading the post i'm not really clear on the issue, and i don't want to mess with anything for fear of losing access to my internal sd as well, so if anybody can help, it would be much appreciated!
[Eee Pad Transformer General] partio:
cant access your external memory from recovery, or from your rom?

if you've fixed the loop of recovery, but still with 5.5.0.4, you will not have access to your external memory, this recovery only works with the internal memory ..

if you happen to the system started, could be a problem with your microsd.
[Eee Pad Transformer General] daedalusbound:
I cant access it from the rom, thought it might be related because it started at the same time and the card reads fine on my phone and computer.
[Eee Pad Transformer General] partio:
backup your sdcard data to your pc, format with sdformatter , and try to mount again in your tf.
[Eee Pad Transformer General] :
Argh - I've gotten trapped now

Hi Everyone,

I didn't even know about this problem till a friend with an HTC said I should use clockwordmod app.

Now I'm trapped in the bootloop of 5.5.0.4 but I can't seem to get ADB to find the device!

I'm on windows 7 64 bit with PC sync installed and was able to use ADB through eclipse up until now where "adb devices" returns nothing and device manager seems to indicate a "transformer" device exists but it doesn't know what to do with it and won't accept any drivers for it!

Anyone know where I can get drivers that will work? or am I missing something in the recovery?
[Eee Pad Transformer General] partio:
if you can boot into your rom via coldboot :

1 - download a new cwm from here: http://xdaforums.com/showthread.php?t=1446019 , put the .zip in your INTERNAL memory (5.5.0.4 cant read external sd)

2 - go play store , download and install , terminal emulator.

if you cant via wifi , download here : http://www.freewarelovers.com/android/app/android-terminal-emulator#download , put in your sdcard and install it.

3 - reboot into your bad 5.5.0.4 cwm , install the new cwm through : install zip from sdcard , choose zip from ...

4 - once installed , dont press reboot system now , make a cold boot directly

5 - once you've booted your rom , run terminal emulator.

type : su (if superuser appp ask to you , allow). will give you a #

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

type : exit

type : reboot

your tf restart without cwm loop , and you will see a progress bar installing the new cwm .

Now you can install any new rom from your sdcard usually through cwm.
[Eee Pad Transformer General] ferreinf:
Please post this on the first page, worked flawless .... :-D

Thanks
[Eee Pad Transformer General] cwalker29:
Agreed!!! Thanks a million
[Eee Pad Transformer General] Sean-El:
That CWM link is down. Is it just Roach's v

version of 5.5.0.4? It won't work for me...
[Eee Pad Transformer General] partio:
edited , link working now.

its not roach fixed version of 5.5.0.4 , its Rogue XM Recovery v1.3.0 (CWM-based Recovery v5.0.2.7)
[Eee Pad Transformer General] seas of tears:
Thanks you so much
[Eee Pad Transformer General] partio:
for those without access to the rom, and fail to be recognized the TF as adb interface in Recovey.

download vipermod 4.5 from here:

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

Unzip and you will see a folder "adb drivers".

go to My Computer, Properties, Device Manager.

right click on tf, update driver, browse my computer, choose a list of drivers on my computer, you will see on the corner down "using disk" or something like that (my windows is spanish)

this open a new tab , navigate to your vipermod , adb drvers folder, and select the .inf.

will install the new drivers , and now Your TF will be recognized as adb interface.

usually, the comand prompt opens pointing to your user folder, something like: c :/ user / your user name >

to make it simple, put in this folder adb.exe, the two adb.dlls , and the new recovery renamed to recovery.zip.

ok, our TF already recognized as adb interface and all the files ready, open a command prompt.

on your PC: start, run, and type cmd

1 - then in command prompt , type adb devices

you will see something like that :1234567abcd recovery , if you see 1234567abcd offline , try to change usb port and adb devices again.

2 - type : adb push recovery.zip /data/media

this will upload the recovery to your tf internal memory.

3 - go to your recovery tab in ft , and install this new recovery (should appear now in install zip...,choose from...)

4 - back to your pc command prompt and type : adb shell

This will give you #

5 - type : echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0

6 - type : exit

7 - type : adb reboot

its all , good luck
[Eee Pad Transformer General] horndroid:
I still see people having this problem DAILY. Why is ROM Manager still installing this broken version?
[Eee Pad Transformer General] partio:
dont know , I thought Koush would already removed from the server
[Eee Pad Transformer General] Prograss:
Made my day

Finally, it worked. Great!