[Q] Prolly need partitioning, need advice. Tf101g

Search This thread
By:
Advanced…
tihimasmo

tihimasmo

Senior Member
Oct 16, 2011
504
80
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
 
Last edited:
gee one

gee one

Senior Member
Jul 29, 2010
1,979
866
linux command line
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
 
Last edited:
  • Like
Reactions: tihimasmo
tihimasmo

tihimasmo

Senior Member
Oct 16, 2011
504
80
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.
 
Last edited:
gee one

gee one

Senior Member
Jul 29, 2010
1,979
866
linux command line
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!
 
tihimasmo

tihimasmo

Senior Member
Oct 16, 2011
504
80
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.
 
gee one

gee one

Senior Member
Jul 29, 2010
1,979
866
linux command line
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.
 
  • Like
Reactions: tihimasmo
tihimasmo

tihimasmo

Senior Member
Oct 16, 2011
504
80
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?
 
gee one

gee one

Senior Member
Jul 29, 2010
1,979
866
linux command line
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
 
  • Like
Reactions: tihimasmo
tihimasmo

tihimasmo

Senior Member
Oct 16, 2011
504
80
Lol. Don't cut urself man. I might need your help again :)

I'll try later when kids asleep.
 
tihimasmo

tihimasmo

Senior Member
Oct 16, 2011
504
80
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?
 
gee one

gee one

Senior Member
Jul 29, 2010
1,979
866
linux command line
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.
 
  • Like
Reactions: tihimasmo
gee one

gee one

Senior Member
Jul 29, 2010
1,979
866
linux command line
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.
 
Last edited:
  • Like
Reactions: tihimasmo
tihimasmo

tihimasmo

Senior Member
Oct 16, 2011
504
80
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.
 
tihimasmo

tihimasmo

Senior Member
Oct 16, 2011
504
80
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.
 
tihimasmo

tihimasmo

Senior Member
Oct 16, 2011
504
80
I get invalid argument on that command.

What if we forget cwm and try format to default partinioning and push stock?
 
gee one

gee one

Senior Member
Jul 29, 2010
1,979
866
linux command line
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.
 
tihimasmo

tihimasmo

Senior Member
Oct 16, 2011
504
80
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://xdaforums.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.
 
Last edited:
You must log in or register to reply here.

Similar threads

lilstevie
[Q&A] Ubuntu on the Transformer (eMMC install)
Replies
2K
Views
572K
P
parad1me
J
Need help upgrading my TF101
Replies
9
Views
38K
QkTreasures
QkTreasures
prendomiao
[Q] Windows on Asus TF101
Replies
24
Views
61K
Fjcnd
Fjcnd
lujo_zgb
[Q] TF101 wont charge - connect charger
Replies
36
Views
59K
H
hoang51
Thing O Doom
[HELP-THREAD] The Ask-Doom thread! (Need help? New? Ask here!) -Give help too!-
Replies
314
Views
46K
C
CaputoAntonio

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 1
    gee one
    gee one
    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
    View
    1
    gee one
    gee one
    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.
    View
    1
    gee one
    gee one
    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
    View
    1
    gee one
    gee one
    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.
    View
    1
    gee one
    gee one
    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.
    View

New posts