Database Info

help rooting CDMA Hero on windows 7 64 bit

I have been following the unlock instructions on these posts on how to unlock the Hero, but I am having some trouble. When to comes to making the adb shell, it just doesn't do it. It shows a dollar sign and says that the request is denied. I just don't get what I'm doing wrong. Are there extra steps for me because there are x86 files? If I have to put the android sdk into the program files x86 folder, how would I enter that into the commander? Any help would be appreciated guys, this is driving me crazy.

OK so you get to the dollar sign. What do you do then?

Kamar234 said:
I have been following the unlock instructions on these posts on how to unlock the Hero, but I am having some trouble. When to comes to making the adb shell, it just doesn't do it. It shows a dollar sign and says that the request is denied. I just don't get what I'm doing wrong. Are there extra steps for me because there are x86 files? If I have to put the android sdk into the program files x86 folder, how would I enter that into the commander? Any help would be appreciated guys, this is driving me crazy.
Click to expand...
Click to collapse
Just extract the sdk so its a folder. Then go to Start->Run-> type cmd.exe in the box that opens. Now navigate to where you extracted the sdk folder. If you extracted it straight onto the c:\ drive at top level, you'd do something like this:
Code:
cd c:\android-sdk\tools
That will get you into the directory that has adb.exe
Now follow the instructions in the "how to root" thread.

I can get down to the point where I execute the adp push and all the lines come up saying that the adp is restarted and there is obviously a command that is executed.
adb shell
chmod 0755 /data/local/asroot2
this part is when it says access is denied. I follow everything perfectly, but I just don't get it.

Oh, easy.
Type "su" and hit enter.
The dollar sign prompt indicates you are running as a regular user. Run su and it will give you a # prompt indicating you are running as root.
Then do the chmod.

It specifically says after entering this line
/data/local/asroot2 /system/bin/sh
system cannot find the path specified. Any ideas?

so when the dollar sign comes up, just type su and hit enter, that's it?

Kamar234 said:
It specifically says after entering this line
/data/local/asroot2 /system/bin/sh
system cannot find the path specified. Any ideas?
Click to expand...
Click to collapse
Are you sure the asroot2 file has been copied over to your phone? What I did is extract asroot2 into the tools folder, so that I could just say adb push asroot2 /data/local/
My suggestion is to make sure the file is in /data/local/
Also, here is the full thing taken from the other thread:
Code:
adb push /directory_you_placed_asroot2/asroot2 /data/local/
adb shell
chmod 0755 /data/local/asroot2
/data/local/asroot2 /system/bin/sh
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/bin
cat sh > su
chmod 4755 su

Yup, I put it in the tool folder within the android sdk. I am using the 1.5 sdk as well.

I just really can't understand what I'm doing wrong

Do:
ls -al /data/local
Do you see asroot there?

it says not found. I entered it by the dollar sign

Kamar234 said:
it says not found. I entered it by the dollar sign
Click to expand...
Click to collapse
That means the file isn't copied over. You need to do the adb push line again, and make sure it copies the file over.

how do I do that? Is there a something that it does or says to let you know it has copied over?

Kamar234 said:
how do I do that? Is there a something that it does or says to let you know it has copied over?
Click to expand...
Click to collapse
The first line here:
Code:
adb push /directory_you_placed_asroot2/asroot2 /data/local/
That puts the asroot2 file into your phone's /data/local/ directory.
This line gets you into your phone's shell:
Code:
adb shell
AT THIS POINT, you should see a $ dollar sign. This means you are in your phone.
This line will let you check that asroot2 has been copied over:
Code:
ls -al /data/local
This line gives the file you just copied over, permission to execute/run:
Code:
chmod 0755 /data/local/asroot2
This line runs the file you copied over:
Code:
/data/local/asroot2 /system/bin/sh
This line mounts your file system on your phone as writable:
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system

I am also running windows 7 through vmware fusion, do you think that would make a difference.

Kamar234 said:
I am also running windows 7 through vmware fusion, do you think that would make a difference.
Click to expand...
Click to collapse
I don't know, I don't think it should. Can you type everything in and then paste us your results?

Type pwd and hit enter.
What do you see?

Thank you so much for all your help everyone. I think I may have finally gotten it. If I am installing an app that needs root access, will it install at all if the phone isn't rooted?

Return to stock firmware HTC ChaCha

Hi
I tried SuperOSR for a few months now, but i really want to use the camera so therefor i want to return to stock firmware.
I used this thread:
http://forum.xda-developers.com/showthread.php?t=1164468
Now the problem is, when i download stockrecovery and install it to the SDCARD and then i try to update it via CWM, it says:
Error in sdcard/stockrecovery.zip (Status 0) and then it stops, what now?

To flash stock recovery back you need to rename it to PH06img.zip.

and if you wanted to go back to stock rom alone, you dont need stock recovery. Just download the stock rom and install the RUU

If you want to flash the stock recovery, here is one:
File name: recovery.img
File will remain active for: 24 Hrs
Link: http://www.streamfile.com/myid/sA81KohsAsgN
(if some1 could mirror it, I can't seem to access any file sharing from here)
place the file in your sdcard (don't change the name), and flash from CWM recovery using adb:
c:\somedir\> adb shell
$ su
# mount /sdcard
# cd /sdcard
# flash_image recovery recovery.img

Adlx u went from clique to chacha development?
Sent from my LT15i using XDA App

zainthesnipe said:
Adlx u went from clique to chacha development?
Sent from my LT15i using XDA App
Click to expand...
Click to collapse
lol, yeah, I started with the Cliq, then Cliq XT, Defy, and now I'm working on CM7/SuperOSR for the Chacha, check http://forum.xda-developers.com/showthread.php?t=1291232
You got a Chacha?

adlx.xda said:
(if some1 could mirror it, I can't seem to access any file sharing from here)
Click to expand...
Click to collapse
Up on http://alex.swtesting.ro/downloads/ or http://swtesting.ro/alex/downloads/ for unlimited time.

when i type mount sdcard,adb show me this:
$ mount sdcard
mount sdcard
Usage: mount [-r] [-w] [-o options] [-t type] device directory
whats wrong?
and its all of this comands:
$ mount sdcard
mount sdcard
Usage: mount [-r] [-w] [-o options] [-t type] device directory
$ cd /sdcard
cd /sdcard
$ flash_image recovery recovery.img
flash_image recovery recovery.img
flash_image: permission denied

ok, sorry about that, my mistake
Try that:
c:\somedir\> adb shell
$ su
# mount /sdcard
# cd /sdcard
# flash_image recovery recovery.img

all of my phone:
C:\Users\Pasha\Desktop\adb\adb>adb shell
adb server is out of date. killing...
* daemon started successfully *
$ su
su
# mount sdcard
mount sdcard
Usage: mount [-r] [-w] [-o options] [-t type] device directory
# cd /sdcard
cd /sdcard
# flash_image recovery recovery.img
flash_image recovery recovery.img
flash_image: not found
#
file not found but i placed recovery.img into root of my sdcard!

From your post you're missing a / in "mount /sdcard".

not found again..
$ su
su
# mount /sdcard
mount /sdcard
Usage: mount [-r] [-w] [-o options] [-t type] device directory
# cd /sdcard
cd /sdcard
# flash_image recovery recovery.img
flash_image recovery recovery.img
flash_image: not found
#

The only thing that worked to get stock recovery was to change back to OTA firmware, which i downloaded on the 2nd page. Then i updated to OTA1.54 (official from HTC) and then i put CWM on it again to root my device.
All the other methodes like, use recovery.zip etc. etc. do not work the phone gives error 0 and hangs

Justphemy said:
flash_image: not found
[/COLOR]
Click to expand...
Click to collapse
Damn it! I thought CWM had flash_image...

help
pongzor said:
The only thing that worked to get stock recovery was to change back to OTA firmware, which i downloaded on the 2nd page. Then i updated to OTA1.54 (official from HTC) and then i put CWM on it again to root my device.
All the other methodes like, use recovery.zip etc. etc. do not work the phone gives error 0 and hangs
Click to expand...
Click to collapse
Could you write step by step how to back to stock revocery or show which file should I download, please

That should be a useful guide I agree

Hello all: since I've messing with this, too, and I found this site (link) where it's explained how to put the flash_image utility and how to flash the recovery image by using adb.
I will quote it:
flash_image is a small utility to be used on the device that allows you to re-write system partitions with image files. If you don't have it, it can be found here: http://cyanogen-files.carneeki.net/flash_image.zip (Unzip it)
You will need to install flash_image on the device, this requires the use of the SDK. So if you do not have the SDK installed, do it now.
Then go to the tools directory in the SDK,
Code:
example: cd c:\android-sdk-windows\tools
or
Code:
example: cd ~/android-sdk-linux/tools
At this point you will need to use your command line or terminal on your PC to access ADB, if you do not know how to use ADB and it is causing you to unsuccessfully perform these actions please read one of the many guides on ADB, also if the device is not recognized, you may need to uninstall HTC sync and install the ADB USB drivers in the SDK after downloading them from the setup program. (You will also need to turn on USB debugging on the device, in Settings/Applications/Development)
From command prompt or terminal:
Copy flash_image to the sdcard on the device
Code:
adb push flash_image /sdcard/
To use flash_image to flash a recovery image called recovery.img in the root of your sd card
Code:
adb shell
su [/CODE]
Temporarily allow app to run from the sdcard (use mount to find the correct device for your sdcard, ie: the /dev/block/BLAH part)
Code:
mount -o remount,exec /dev/block//vold/179:1 /sdcard
cd /sdcard
./flash_image recovery /sdcard/recovery.img
Click to expand...
Click to collapse
I hope it works for you. It did for me.

adlx.xda said:
If you want to flash the stock recovery, here is one:
File name: recovery.img
File will remain active for: 24 Hrs
Link: http://www.streamfile.com/myid/sA81KohsAsgN
(if some1 could mirror it, I can't seem to access any file sharing from here)
place the file in your sdcard (don't change the name), and flash from CWM recovery using adb:
c:\somedir\> adb shell
$ su
# mount /sdcard
# cd /sdcard
# flash_image recovery recovery.img
Click to expand...
Click to collapse
Hi !
When i write su and press enter it's says permission denied
tokafondo said:
Hello all: since I've messing with this, too, and I found this site (link) where it's explained how to put the flash_image utility and how to flash the recovery image by using adb.
I will quote it:
I hope it works for you. It did for me.
Click to expand...
Click to collapse
tokafondo said:
Hello all: since I've messing with this, too, and I found this site (link) where it's explained how to put the flash_image utility and how to flash the recovery image by using adb.
I will quote it:
I hope it works for you. It did for me.
Click to expand...
Click to collapse
C:\Fastboot>adb shell
$ mount -o remount, exect /dev/block//vold/179:1 /sdcard
mount -o remount, exect /dev/block//vold/179:1 /sdcard
Usage: mount [-r] [-w] [-o options] [-t type] device directory
$ cd /sdcard
cd /sdcard
$ ./flash_image recovery /sd/card/recovery.img
./flash_image recovery /sd/card/recovery.img
./flash_image: not found
$ ./flashimage.zip recovery /sdcard/recovery.img
./flashimage.zip recovery /sdcard/recovery.img
./flashimage.zip: not found
$ ./flash_image.zip recovery /sdcard/recovery.img
./flash_image.zip recovery /sdcard/recovery.img
./flash_image.zip: permission denied
Anybody a little help ...

[q] is there a way to access system files through recovery/bootloader?

whenever i turn my phone, i get an error that says the com.android.sdksetup application failed or something like that and when forced to close, it would just show up again.
as a result, i'm stuck in that infinite loop, i can only access recovery (3e) and the bootloader. I've tried a factory reset but that only erases user data. Since it runs on 3e recovery, I get signature verification errors when trying to flash to a different rom. I was wondering if there's any way I can access the system files through any of these two modes? the phone is the Gooapple 3g

I dont know about your specific phone, but i managed to get a bit of info from a google search
I believe what yo want to be doing is flashing a recovery that allows you ADB write access to /system (if your recovery doesnt already - try 'adb remount' or 'adb shell mount -o remount,rw /system')
You may need the PdaNetA302.exe file from http://www.alcatel-mobilephones.com/...iew/full/25287 to use USB ADB
This thread may be useful: http://forum.xda-developers.com/showthread.php?t=1252195
the clockworkmod recovery section may be useful as cwm allows read/write access to the /system partition via ADB:
INSTALL CLOCKWORK RECOVERY (orange lantern recovery)
Flashing custom recovery image:
{Non ADB method}
1) Download flash_image and place it on the root of your SD card: http://db.tt/flHRxiG
2) Download recovery.img to the root of your SD card: http://db.tt/uy56zhj
3) Open Terminal Emulator and issue these commands:
Code:
$ su
# cp /sdcard/flash_image /system/bin
# chmod 747 /system/bin/flash_image
# flash_image recovery /sdcard/recovery.img
4) If you see a bunch of successful on your screen then it has flashed properly.
{ADB method}
1) Open up command prompt and issue these commands:
Code:
C:\Users\Your_Name> cd ..
C:\Users> cd ..
2) Navigate to your installed Android SDK (Mine is under the Program Files (x86) folder):
Code:
C:\> cd Program Files (x86)
C:\Program Files (x86)> cd Android/android-sdk/platform-tools
3) Connect your device to your computer and make sure you have USB Debugging enabled on your phone.
4) Issue this command to verify that your computer recognizes your phone:
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools> adb devices
5) If you see your phones serial then it is connected.
6) Download flash_image and place it in the platform-tools folder: http://db.tt/flHRxiG
7) Download the recovery.img and place it on the root of your SD card: http://db.tt/uy56zhj
8) Issue these commands in command prompt:
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools> adb push flash_image /system/bin
C:\Program Files (x86)\Android\android-sdk\platform-tools> adb shell chmod 747 /system/bin/flash_image
C:\Program Files (x86)\Android\android-sdk\platform-tools> adb shell
# flash_image recovery /sdcard/recovery.img
9) If you see a bunch of successful on your screen then it has flashed properly.
boot into recovery, hold home whilst powering on, after 5 long seconds, let go of home and then push home again, you will need to put the volume/menu-back toggle to "volume" mode and according to deepakpitrola333, you need to cycle the list 3 times using volume to allow selection.
Video by mayiandjay;
http://www.youtube.com/watch?v=B_dX9Ruoljo

[Q] Prolly need partitioning, need advice. Tf101g

To those of you who followed link here: don't rush ahead and execute adb command. Read the thread in its entirety, since it contains typos and trial n error.
Gl, hf
Hi. I've been stupid. U may flame me but plz also provide some advice to swallow it with.
I followed bad advice and flashed cwm 5xxxx. After that tried to run superwipe, which got stuck after a few steps. To my horror i realized i had run it from internal. Of course it wiped itself and i got stuck mid-partinioning i think.
Since cwm don't read ext sd i tried to push new recovery via easyflasher, but i can't seem to get a driver that lets my pc interact with the device.
Instead discovered i have adb acess if connected when device is in cwm. From there tried to run PERI v 0.4. At first step, trying to push recovery i get a message of no space available. I think this is due to borked partitioning with superwipe. I guess I can repartition with cwm, but now I've messed so much up I don't wanna do anything more without proper advice.
Thanks

bump

If you have adb access, then use it to push a new rom.
"adb push {shiny new rom or recovery} /sdcard/"
You might have to change /sdcard/ to whatever cwm 5x uses?
Then you can just flash it from cwm.
EDIT: I just saw that you have the tf101G - it might work, but you probably have to find the right rom or recovery.
sent from my transformer

gee one said:
If you have adb access, then use it to push a new rom.
"adb push {shiny new rom or recovery} /sdcard/"
You might have to change /sdcard/ to whatever cwm 5x uses?
Then you can just flash it from cwm.
EDIT: I just saw that you have the tf101G - it might work, but you probably have to find the right rom or recovery.
sent from my transformer
Click to expand...
Click to collapse
Good advice, problem is that im not very savvy. How do i execute that command and what if i need to repartition the internal sd?
When running oneclickrecovery i get following prompts:
Uh-oh! I'm softbricked or have a recovery-bootloop! D:
Never fear sir and/or madam! PERI is here! -trips-
Adb needs to be fully working for this to work properly.
Note that this will wipe your current recovery.
Also note that this may not work, don't taze me bro!
Run? Close if you want to cancel.
Press any key to continue . . .
List of devices attached
0123456789ABCDEF recovery
If you see your device here this will work, if not fix adb.
Press any key to continue . . .
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.345431 seconds, 5.8MB/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...
Press any key to continue . . .
Pushing new recovery...
1331 KB/s (4599884 bytes in 3.374s)
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...
Press any key to continue . . .
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)
Press any key to continue . . .
Hopefully that fixed everything!
Press any key to continue . . .
Of course nothing was fixed and I still have cwm 5xxx which can't flash from ext sd. If I can only get another recovery I can flash any rom and that's that.
In device manager the device shows up as android adb interface when booted into cwm. I also have a device named android composite adb interface, but with a warning sign on it.
This is getting tiresome...
Edit: tried using quick adb pusher, but get message that i cant mount as r/w. In cwm cant mount data or sdcard/.android_secure.
Fun thing is I dont have root either.

It looks like your partitions are unformatted.
I think you need to get to a root shell via adb in recovery
- put your phone on recovery and plug into your computer
- type "adb remount" (you might get an error) then type "adb shell"
- you'll be in a terminal shell
- type "mount" to see how/what your sdcard is doing. Look for the line that has /sdcard on it. It might be something like /dev/block/mmcblk0p1 mounted at /sdcard blah blah...
- now to format your sdcard, type "mke2fs /dev/blah/whereever/your/sdcard/is/mounted/from/above"
- allow it to complete and type "exit". you might have to reboot your tab to get everything to remount
- once your tqab is back in recovery, type on your computer "adb push [some new recovery that uses the external sdcard or a new rom] /sdcard"
- if you have recovery bootloops, google around, there is a fix that wipes the reboot command from the misc partition. You can type it from an adb shell it's something like "dd if=/dev/block/zero of=/be/carefule/because/you/have/a/tf101G bs=1 count=13"
- Google is your friend. Linux is your friend. This is a bit of a high level overview, so you'll have to fill in the details yourself. Keep in mind that I don't have a tf101G and I never tried this before (a benefit of never using superwipe!)
Good luck!

OK. I'd like to try the method u describe but as I mentioned I'm really not tech savvy. I don't even know how to get to the point where I type "adb remount". Do I just open a cmd prompt? Tried that - didn't work.
I have downloaded sdk manager for when I did some stuff with my phone earlier and have the basic packages installed.

Are you on Windows? I think it's a path issue. You either need to put everything in the same folder and run everything from there or put adb in your path. I don't use Windows, so that's probably the best advice I can give you. "which adb" and "echo $PATH" probably won't work in Windows like they do in linux.

Ehm.. too techie answer for me to comprehend.
Yes I'm on win 7.
Put what in same folder as what?
Run from there by right clicking empty space in folder and choosing cmd?
What do you mean by putting adb in my path?

For some reason, lots of people on windows just put the recovery/rom and adb in the same folder and run it from there in the command prompt. Put it all in one place and use the cd command in the terminal to get there.
sent while running with scissors

Lol. Don't cut urself man. I might need your help again
I'll try later when kids asleep.

Allright. Learning curve is steep but im clinging on to it:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb remount
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
remount failed: Success
C:\Program Files (x86)\Android\android-sdk\platform-tools>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)
~ # mke2fs /dev/block/mmcblk0p2
mke2fs /dev/block/mmcblk0p2
mke2fs 1.41.11 (14-Mar-2010)
/dev/block/mmcblk0p2 is apparently in use by the system; will not make a filesys
tem here!
~ # exit
exit
C:\Program Files (x86)\Android\android-sdk\platform-tools>
Any ideas?

You're almost there... You're /cache partition is already formatted (ext4) Be careful since you can really mess things up with the wrong commands or mis-typed commands.
It looks like you need to mount your sdcard manually. I'm not sure which partition it is. I'll check the stock rom in a little while- I have to run some errands while it downloads.

OK, I downloaded the stock rom and had a look at the /etc/recovery.fstab file in the stock recovery. Should be what we need.
Put your tablet in recovery. Then, in a windows terminal, type "adb remount" and then "adb shell" This wil put you into an android terminal. I don't know if you need read/write permissions in CWM? Who knows? Typing commands in here is the same as typing commands on your tablet (if anyone used the command line any more).
type "ls /dev/block/" and you should see a long list of - look for mmcblk1p1 or mmcblk1. It will probably be the first one.
type "ls /" and look for /sdcard. If it's not there type "mkdir /sdcard" This step creates the mount point if it doesn't exist.
Now type "mount /dev/mmcblk1p1 /sdcard" - Substitute whichever one is in your /dev/block directory from above.
EDIT: If you get errors that it's not formatted or "specify the type" then we'll have to format it first. "mke2fs /dev/block/mmcblk1p1"
Now, in a different windows terminal, type "adb push [a new rom/recovery] /sdcard/"
In CWM, you should be able to flash whatever you pushed there.
If it flashes, but you get bootloops or boot back into CWM, you probably have the dreaded CWM bootloops. You can fix that by typing "dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=1 count=15" in the terminal as the first step after "adb shell" For this you will need root access (with the # prompt, not $) Type "su" if you don't ahve the # prompt. It might work? Note that this is experimental and wipes out a bit of your misc partition. I have no idea of what else is on there, so there might be unintended consequences.

C:\Program Files (x86)\Android\android-sdk\platform-tools>adb remount
remount failed: Success
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
~ # ls /dev/block/
ls /dev/block/
loop0 loop3 loop6 mmcblk0p1 mmcblk0p4 mmcblk0p7 platform
loop1 loop4 loop7 mmcblk0p2 mmcblk0p5 mmcblk1
loop2 loop5 mmcblk0 mmcblk0p3 mmcblk0p6 mmcblk1p1
~ # 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
~ # mount /dev/mmcblk1p1 /sdcard
mount /dev/mmcblk1p1 /sdcard
mount: mounting /dev/mmcblk1p1 on /sdcard failed: No such file or directory
~ #
I tried pushing anyway, but can't still mount sdcard on cwm from pad interface.
As for the sdcard contents, I have nothing there that can't be deleted.

use "mount /dev/block/mmcblk1p1 /sdcard" No need to repeat the ls commands.

Sorry for not answering rapidly. Baby chose this night to be at his worst.
First
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb remount
remount failed: Success
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
~ # mount /dev/block/mmcblk1p1 /sdcard
mount /dev/block/mmcblk1p1 /sdcard
~ #
New cmd
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb push cwm-6.0.1.2-t
ouch-external.zip /sdcard/
1332 KB/s (5070063 bytes in 3.715s)
C:\Program Files (x86)\Android\android-sdk\platform-tools>
Can't mount sdcard frow cwm. Can I also flash new rck manually?
Tried reboot and mounting again manually, but cwm won't mount.

Maybe try "mount /dev/block/mmcblk1 /sdcard" ???

I get invalid argument on that command.
What if we forget cwm and try format to default partinioning and push stock?

You could try pushing the stock rom to your tablet and then flashing it via the staging partition. The rom is about 522M, so you might need the sd card, but otherwise, you can push it anywhere it will fit. Staging partition is /dev/block/mmcblk0p4. Google around, the info is certainly in this forum. As long as you can get a root shell via adb, you can flash it. The stock rom is on the Asus sight. Just keep unzipping it until you see the blob file.
Of course, you can flash anything you want via the staging partition, if it's packed in a blob format. You might consider flashing a rooted rom instead of the stock.

I have stock on hd. Shall I mount staging via same commands as i mounted sdcard? Push there via adb. Then what command to flash the blob? The blob has no file extension. Shall i keep it that way?
Edit: ok i tried to unpack the recoveryblob from my desired version of cwm, but tool stopped working during process of writing recoveryblob.sos. I got the tool here http://forum.xda-developers.com/showpost.php?p=21620550&postcount=24
Next problem:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb remount
remount failed: Success
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
~ # mount /dev/block/mmcblk0p4
mount /dev/block/mmcblk0p4
mount: can't find /dev/block/mmcblk0p4 in /etc/fstab
~ #
Edit 2: I finally managed to get apx working if it somehow can help.

[Q] (vold.fstab) storage is messed up \O/

I edit ( vold.fstab ) for swaping sdcard with external_sdcard .
but now my tab dose not show any storage ?
tab: karbonn tornado

problem resolved
Flash with stock rom, and its done :good:
Download any stock rom from here :
androidxda(.)com/download-karbonn-stock-rom-models
:victory:

or you can change it with ADB PULL
Here some text which i find on net :
Download the Android Debug Bridge from here, and extract the contents (to the same directory).
Connect your device to your computer using the USB cable and open up a command prompt (Windows logo key + R, type cmd and press Enter).
Once that is open, type the following commands:
cd <entire path to adb.exe file>
adb shell
su
mount -o remount,rw /system (if that doesn't work: mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system)
exit
exit
adb push <path to original file> /system.etc/vold.fstab
adb reboot
That will grant root, mount the system as writeable and then push the original file and overwrite the modified one (and reboot your device).
Click to expand...
Click to collapse
I don't know about Android Commander, but a simpler way (in my opinion) would be to use ADB. You may have already installed the Android SDK (if not, go here). I assume that you don't have modified your System Path.
Move your vold.fstab to C:\Program Files\Android\android-sdk\platform-tools or C:\Program Files (x86)\Android\android-sdk\platform-tools
Go to the android-sdk folder, shift+right click on platform-tools and choose "Open command prompt here"
Next steps depends if you have a custom rom (a) or not (b) (see comments).
We take root privilege:
a) If your device is 4.0 or above, type adb root
b) Type adb shell then su
We make /system writeable:
a) adb remount
b) mount -o remount,rw /system then exit
adb push vold.fstab /system
adb reboot
This should do the trick.
Click to expand...
Click to collapse
to pull (read) should not need root.
adb pull /system/etc/vold.fstab
or
adb pull /etc/vold.fstab
what output did you get?
_____________________________________________________
adb pull /etc/vold.fstab
edit vold.fstab and change the following line:
dev_mount usbdisk /mnt/usbdisk auto /devices/platform/tegra-ehci
to
dev_mount usbdisk /mnt/usbOTG auto /devices/platform/tegra-ehci
save the file, and go back to the command line
adb remount
adb push vold.fstab /etc/vold.fstab
abd reboot
Click to expand...
Click to collapse
But i dont get any of em