[Q] Rooted? I can't flash any roms though. - Eee Pad Transformer Q&A, Help & Troubleshooting

TF101. 16GB
As far as I know I am rooted. When I boot into recovery it is using ClockworkMod Recovery v3.0.2.8
Android version 3.1
Build Number
HMJ37.US_epad-8.4.4.5-20110527
Anytime I try to flash any rom I get an error 7.
What am I doing wrong? Anymore information needed to help?

ls3mach said:
TF101. 16GB
As far as I know I am rooted. When I boot into recovery it is using ClockworkMod Recovery v3.0.2.8
Android version 3.1
Build Number
HMJ37.US_epad-8.4.4.5-20110527
Anytime I try to flash any rom I get an error 7.
What am I doing wrong? Anymore information needed to help?
Click to expand...
Click to collapse
are you verifying the MD5SUM of the OS post pushing it to the SdCard.

neidlinger said:
are you verifying the MD5SUM of the OS post pushing it to the SdCard.
Click to expand...
Click to collapse
I have not. I have tried multiple sources and roms (stock and modded). I can't get any to flash.

Well, I accidentally wiped my tablet. That didn't help. The exact error is
assert failed: write_raw_image(" /tmp/blob", "staging")
E:Error in /sdcard/ASUS/Update/US_epad-User-8.6.5.21.zi[
(status 7)
Installation aborted.

ls3mach said:
Well, I accidentally wiped my tablet. That didn't help. The exact error is
assert failed: write_raw_image(" /tmp/blob", "staging")
E:Error in /sdcard/ASUS/Update/US_epad-User-8.6.5.21.zi[
(status 7)
Installation aborted.
Click to expand...
Click to collapse
are you extracting the OS are leaving it in a .zip

neidlinger said:
are you extracting the OS are leaving it in a .zip
Click to expand...
Click to collapse
It is in a zip format. When I insert my SD card into my TF101 it recognizes that it has a system file on the card.

ls3mach said:
It is in a zip format. When I insert my SD card into my TF101 it recognizes that it has a system file on the card.
Click to expand...
Click to collapse
If it's the stock ROM, you actually have to unzip it after download to get to another zip file inside.

ls3mach said:
Well, I accidentally wiped my tablet. That didn't help. The exact error is
assert failed: write_raw_image(" /tmp/blob", "staging")
E:Error in /sdcard/ASUS/Update/US_epad-User-8.6.5.21.zi[
(status 7)
Installation aborted.
Click to expand...
Click to collapse
Some versions of cwm don't have the staging partition mounted. Go into mounts and see if there is an option to mount staging (might as well mount system while you are at it).
If there is no option to mount staging, use adb and type
mkdir /staging (it might already exist?)
mount /dev/block/mmcblk0p4 /staging
The last chars above are zero pee four- don't mess it up!
Then re-flash the rom.
If you don't have adb in recovery, then either repackage the rom or get a recovery that has it, although I'm not sure which ones will- I think roach's 3.2.0.1 will work, but you have to mount the partitions through the menu.
sent from my cyanogen(mod) vision

gee one said:
Some versions of cwm don't have the staging partition mounted. Go into mounts and see if there is an option to mount staging (might as well mount system while you are at it).
If there is no option to mount staging, use adb and type
mkdir /staging (it might already exist?)
mount /dev/block/mmcblk0p4 /staging
The last chars above are zero pee four- don't mess it up!
Then re-flash the rom.
If you don't have adb in recovery, then either repackage the rom or get a recovery that has it, although I'm not sure which ones will- I think roach's 3.2.0.1 will work, but you have to mount the partitions through the menu.
sent from my cyanogen(mod) vision
Click to expand...
Click to collapse
It has the option to mount
/system
/cache
/data
/sdcard
I mounted all of them and tried to flash a stock rom, which has been extracted from the original zip to the (what I believe to be) update zip. Is there a way to update my CWM to one that doesn't have this issue?

baseballfanz said:
If it's the stock ROM, you actually have to unzip it after download to get to another zip file inside.
Click to expand...
Click to collapse
I am pretty sure I have done that. It is recognizing that their is a system file when the card is inserted.

ls3mach said:
It has the option to mount
/system
/cache
/data
/sdcard
I mounted all of them and tried to flash a stock rom, which has been extracted from the original zip to the (what I believe to be) update zip. Is there a way to update my CWM to one that doesn't have this issue?
Click to expand...
Click to collapse
You could try the Team Rouge recovery but I don't know if it will help or not

ls3mach said:
It has the option to mount
/system
/cache
/data
/sdcard
I mounted all of them and tried to flash a stock rom, which has been extracted from the original zip to the (what I believe to be) update zip. Is there a way to update my CWM to one that doesn't have this issue?
Click to expand...
Click to collapse
You can mount via adb or extract the ramdisk from cwm and add staging partition to the etc/recovery.fstab
I'm not sure which versions of cwm have staging. As I said, I think roach's 3.2.0.1 has it. I'm actually using a modded version of his, but I won't post it because it will probably cause more bootloops and headaches.
sent from my cyanogen(mod) vision

You could also flash a rom that doesn't use the staging partition.
sent from my cyanogen(mod) vision

gee one said:
You could also flash a rom that doesn't use the staging partition.
sent from my cyanogen(mod) vision
Click to expand...
Click to collapse
I tried to flash the new ICS rom, but it wouldn't load for me either. Are you sure this is a staging issue? Also, why can't I flash the stock ROMs? After I get a new one loaded is this going to be a continuing issue?

gee one said:
Some versions of cwm don't have the staging partition mounted. Go into mounts and see if there is an option to mount staging (might as well mount system while you are at it).
If there is no option to mount staging, use adb and type
mkdir /staging (it might already exist?)
mount /dev/block/mmcblk0p4 /staging
The last chars above are zero pee four- don't mess it up!
Then re-flash the rom.
If you don't have adb in recovery, then either repackage the rom or get a recovery that has it, although I'm not sure which ones will- I think roach's 3.2.0.1 will work, but you have to mount the partitions through the menu.
sent from my cyanogen(mod) vision
Click to expand...
Click to collapse
I have the SDK installed and updated. How do I make those ADB commands work? I am in PROMPT and the correct folder. Sorry, I don't use this program often and haven't since I installed the mod originally and I have had my TF101 since they were new.

ls3mach said:
I have the SDK installed and updated. How do I make those ADB commands work? I am in PROMPT and the correct folder. Sorry, I don't use this program often and haven't since I installed the mod originally and I have had my TF101 since they were new.
Click to expand...
Click to collapse
The stock roms usually use the staging partition, the custom roms are hit or miss, so this could potentially be a recurring issue.
rom the command line prompt, type:
adb devices - if all is well, you'll see you tf's serial number
adb shell
su
mkdir /staging - you'll get an error if it already exists, which is fine
mount /dev/block/mmcblk0p4 /staging
exit
Then mount system in cwm and flash your rom.
Good luck
sent from my cyanogen(mod) vision

baseballfanz said:
You could try the Team Rouge recovery but I don't know if it will help or not
Click to expand...
Click to collapse
Well, that worked to flash, but now I get the Android goon when I try to get into recovery.

It sounds like it worked- if you were flashing the 86521 stock rom, it has a stock recovery on it.
You should receive the ICS update now. There is an ICS root exploit in the dev section by rhcp012345, if you want to root.
sent from my cyanogen(mod) vision

gee one said:
It sounds like it worked- if you were flashing the 86521 stock rom, it has a stock recovery on it.
You should receive the ICS update now. There is an ICS root exploit in the dev section by rhcp012345, if you want to root.
sent from my cyanogen(mod) vision
Click to expand...
Click to collapse
It did. I appreciate the help everyone. Now to get my HBoot1.5 EVO3d working. My previous one gave up the ghost

gee one said:
The stock roms usually use the staging partition, the custom roms are hit or miss, so this could potentially be a recurring issue.
rom the command line prompt, type:
adb devices - if all is well, you'll see you tf's serial number
adb shell
su
mkdir /staging - you'll get an error if it already exists, which is fine
mount /dev/block/mmcblk0p4 /staging
exit
Then mount system in cwm and flash your rom.
Good luck
sent from my cyanogen(mod) vision
Click to expand...
Click to collapse
I tried....but.....
N:\3\3>adb shell
~ # mkdir /staging
mkdir /staging
mkdir: can't create directory '/staging': File exists
~ # mount /dev/block/mmcblk0p4 /staging
mount /dev/block/mmcblk0p4 /staging
mount: mounting /dev/block/mmcblk0p4 on /staging failed: Invalid argument
~ #
Ivalid argument...any idea?

Related

[Q] Enrcyption Support for ClockWorkMod Recovery

Hello,
i have just installed the official stock ICS 4.0.3 Rom to my Nexus S and everything was really fine... until i tried to root it. As someone who tries to take security seriously, i immediately encrypted the device using the tools provided by ics (works ok).
but unfortunatly it's now not possible anymore to mount /sdcard while in recovery, which makes rooting and installing updates impossible (or is there any other way? eg. fastboot?).
therefore my question: will clockworkmod recovery support ics encrypted devices in the (near) future? i know its gonna be a p.i.a. to type a password with only the volume buttons, but hey
i like the encryption and would like to keep it, but not beeing able to use recovery like before is a big drawback...
greetings
Georg
Same for me.
Hope to see encryption support in clockworkmod soon.
I bought Rom manager premium even if I never flash from rm just to support the developers... hope they will be able to get it sorted out
Op -- I'm interested in this for when my phone (EVO 3D) finally gets ICS. Will you post an update to this thread if you hear anything?
BTW, with TWRP getting touchscreen support, it can't be too much longer before CWM gets touchscreen since I think the guys in TWRP were going to start contributing to CWM, from what I've heard anyway. So that would solve the password typing problem.
Georg, thanks for asking this question as I've been wondering the same exact thing. Hopefully we'll get a good answer soon.
Alternatives for ClockworkMod Recovery
I encrypted my device (the Exchange account I added required it) n... now I cant do anything in recovery ... it wont mount the drive ... any suggestions for a replacement ...
thanks ...
mrosensweig said:
I encrypted my device (the Exchange account I added required it) n... now I cant do anything in recovery ... it wont mount the drive ... any suggestions for a replacement ...
thanks ...
Click to expand...
Click to collapse
Its because the way encryption works you have to boot and enter code, that's the whole point, no recovery can do it atm
Sent from my ice cream powered Nexus S
small update:
nothing new on the subject, but i didnt check out the new touch recovery (anyone tried it yet?).
in the mean time i went back to an unencrypted CM9...
I didn't read anything about encryption so did not upgraded to the touch recovery yet
you should lock the bootloader if someone is nagging you
jomir said:
small update:
nothing new on the subject, but i didnt check out the new touch recovery (anyone tried it yet?).
in the mean time i went back to an unencrypted CM9...
Click to expand...
Click to collapse
Jomir, what was the procedure you used to get back to CM9? Is it possible to repartition, erasing the encrypted partitions so a new rom can be flashed? How?
Thx,
rmsilva
rmsilva123 said:
Jomir, what was the procedure you used to get back to CM9? Is it possible to repartition, erasing the encrypted partitions so a new rom can be flashed? How?
Thx,
rmsilva
Click to expand...
Click to collapse
Restore a backup or do a clean install(format boot, system, cache and data)
Sent from my ice cream powered Nexus S
DarkhShadow said:
Restore a backup or do a clean install(format boot, system, cache and data)
Sent from my ice cream powered Nexus S
Click to expand...
Click to collapse
Thanks for the reply, DarkhShadow. The problem is that CWM can't wipe or format these partitions, since it can't mount /sdcard (which is encrypted). If I could only access the external sdcard from within CWM, I could just wipe everything and then install a new rom. But since it can't mount /sdcard, I can't access sd-ext. nvflash is not an option, since my TF101 is B90. Is there a way to either restore the stock recovery (overwrite CWM) or boot from the external SD so I can run a script such as "super wipe full" (http://forum.xda-developers.com/showthread.php?t=1245892)? Maybe there's a way to run the wipe script through adb? If I can just format the partitions (which is what the script does), then CWM would be able to mount /sdcard and, consequently, the external SD and I can flash a new rom (such as revolution HD 3.0.1).
Thanks,
rmsilva
Honestly idk then, try a factory reset on phone(ie booted up) and then maybe it will be unencrypted?
Sent from my ice cream powered Nexus S
The funny thing is that stock recovery on an encrypted phone can write to the disk, but only from a warm reboot (perhaps the kernel stays resident?).
When I say write to disk I say apply the leaked OTA update, 4.0.4 for the VZ Gnex. And correct me if I am wrong, it's writing and mounting the disk, no?
Anyhow, this is done from stock recovery which is open source. So you ask yourself, why can't Koush support mounting the disk from a warm recovery state reboot? Maybe he doesn't know this?
DarkhShadow said:
Its because the way encryption works you have to boot and enter code, that's the whole point, no recovery can do it atm
Sent from my ice cream powered Nexus S
Click to expand...
Click to collapse
rmsilva123 said:
Jomir, what was the procedure you used to get back to CM9? Is it possible to repartition, erasing the encrypted partitions so a new rom can be flashed? How?
Thx,
rmsilva
Click to expand...
Click to collapse
i did a factory reset (from the settings menu), installed recovery per adb/fastboot and installed cm9 from sdcard in recovery.
Use tmpfs to install a new ROM in crypted system
Hello Everyone
To flash a new ROM you can do as follows:
boot in Recovery
format cache partition
from your PC use adb to mount /sdcard as tmpfs:
adb shell mount -t tmpfs none /sdcard​
put your ROM on the (fake) sdcard
adb push <your rom> /sdcard​
use the recovery to flesh the ROM as usual
This worked form me.
Sorry to be late...
What about a nandroid backup or restore? How big is /cache?
orcruin said:
Hello Everyone
To flash a new ROM you can do as follows:
boot in Recovery
format cache partition
from your PC use adb to mount /sdcard as tmpfs:
adb shell mount -t tmpfs none /sdcard​
put your ROM on the (fake) sdcard
adb push <your rom> /sdcard​
use the recovery to flesh the ROM as usual
This worked form me.
Sorry to be late...
Click to expand...
Click to collapse
Sorry I didn't try with a nandroid backup but I think it is too big to fit the device memory...
You can backup data inside the sd partiton (phone up and running, just to don't lose data...), boot into recovery, format sdcard partition, mount it, put the backup in the sdcard and after install the nandroid backup...
I think that it could work but I am not sure. If after formatting the sdcard you can mount it, the task is done. You can put the backup on it using adb push and flash using recovery.
If you try please give me some news.
Regards
orcruin said:
Hello Everyone
To flash a new ROM you can do as follows:
boot in Recovery
format cache partition
from your PC use adb to mount /sdcard as tmpfs:
adb shell mount -t tmpfs none /sdcard​
put your ROM on the (fake) sdcard
adb push <your rom> /sdcard​
use the recovery to flesh the ROM as usual
This worked form me.
Sorry to be late...
Click to expand...
Click to collapse
I'm kind of a noob when it comes to adb. What is that process doing exactly? How big is the fake sdcard? I want to make sure I understand all the implications before I dive in. Of course I need HTC to release a ICS ROM first. ;-)
thx1200 said:
I'm kind of a noob when it comes to adb. What is that process doing exactly? How big is the fake sdcard? I want to make sure I understand all the implications before I dive in. Of course I need HTC to release a ICS ROM first. ;-)
Click to expand...
Click to collapse
First it formats the cache partition. Then mount the /sdcard so that you can access it from your pc. After you mount the /sdcard, you can put your rom zip into it. After the zip has been transferred into /sdcard, you can flash the zip as usual.
Since nexus s doesn't have sdcard slot, it mounts the internal storage as '/sdcard' to treat it like a sdcard, thus 'fake' sdcard. The 'fake' sdcard is around 13GB.

Only CWM on my TF101G B90...

Hi all,
I'm here because I need your help...
Days ago I installed on my TF101G the recovery CWM 5.8.1.8...
now I can just go into recovery mode and if I try to mount /data I receive the message "no location found"...
how can I push a Rom on my TF to try to install it?
thanks in advance for your help
how to flash a ROM
The ROM to be flashed must be cwm flashable, you cannot flash official firmware unless it is repacked to be cwm flashable.
Your ROM must be a zip file, do not unzip it.
Copy (or adb push) the ROM to /sdcard/
Reboot tab into recovery.
Follow cwm flash instructions. There are many such a manual available on-line, one of them is:
http://www.addictivetips.com/mobile...-and-how-to-use-it-on-android-complete-guide/
You can just jump to section "apply update from sdcard", which tells you how to use cwm recovery to flash a ROM
One thing you should pay attention is:
if the ROM to be flashed is only a update to your current ROM, do not do any wipe work.
If it is a new ROM, you must do the wipe.
You can also try this....
hi Fenice82,
read this forum
http://forum.xda-developers.com/showthread.php?t=1213723
and read message 1 and 313 for mounting and the adb commands for sending cmw flash file to your internal card of your TF.
Make sure you have the cwm flashable rom file on you computer in the adb dir.
good luck.
I'm hege again...
thk nlheiz for your post...
I push the rom in my TF... I tried different location...
data/media
or
data
or
system
or
sdcard
or
sdcard/rom
if I go in adb shell and I use command mkdir to make a new folder like system,data,sdcard I see the the file already exist...
but my tf "can't mount /sdcard/" and at the same time if i try to mount /data from recovery I see the message
"Error mounting /data!"
what can I do now?
edit... maybe this can help you...
via ADB shell
mount data
mount: mounting /dev/block/mmcblk0p7 on /data failed: Invalid argument
How about restore stock recovery and ROM? Here is a recent guide for root/unroot/downgrading:
http://forum.xda-developers.com/showthread.php?t=1622628
I don't have experience with cwm 5.8.1.8, I stayed on 3.2.0.1 because it is possible to flash from external sdcards.
cold you try this:
put our tablet into cwm (volume - plus power and when asked volume +) and connect it to usb on pc.
then on your pc:
adb devices
this should give you a serial number back.....
then try this:
to mount the internal sdcard so that you can push a new rom- use
adb shell
mount /dev/block/mmcblk0p7 /data/
ls /sdcard/
exit
then from your pc, type:
adb push /path/to/your/rom.zip /data/media
I found this here http://forum.xda-developers.com/showthread.php?p=23256536 in post 3......
let me know if this works
e154037 said:
How about restore stock recovery and ROM? Here is a recent guide for root/unroot/downgrading:
http://forum.xda-developers.com/showthread.php?t=1622628
Click to expand...
Click to collapse
thk man... with method 3 I installed new recovery and with it I installed the official update, from external storage, that recovery my tablet...pdate
before official update I tried to install other custom rom but I incurred in encryption problem... with official after the fist boot it automatically resolved the problem
I'm very happy
thk again

Easy fix for experienced user

I have access to recovery on my TF300T, I also have access to fastboot.
I can switch between Clockword and TWRP recoveries at any time.
I can not get a rom to load on my tabet. the recovery does not recognize external SD cards so I can not put a rom on that.
When I use fastboot to flash the default ASUS rom from their support website it does not boot it?
How could I have possibly bricked my device when I have access to both recovery and fastboot ?
Not sure I completely get what ur say in,but have u tried to put the ROM on ur internal storage and flash?
evolving said:
Not sure I completely get what ur say in,but have u tried to put the ROM on ur internal storage and flash?
Click to expand...
Click to collapse
The recovery does not give me the option to mount my internal storage to my PC so I can put roms on it, is there any other way to get roms on the internal storage?
Btw I am running the latest version of TWRP openrecovery-twrp-2.3.1.0-tf300t-JB.blob
Download the ROM on your tablet then boot into recovery go to downloads and it should b there.unless I'm just not getting what you are saying
Restore the backup to the ROM you were using before. As far as why the ROM won't boot, gatta talk to the dev.
He was trying to flash hydro 4.1 while already being on jb.
Sent from my PG86100 using xda premium
comzee said:
I can not get a rom to load on my tabet.
Click to expand...
Click to collapse
evolving said:
Download the ROM on your tablet then boot into recovery go to downloads and it should b there.unless I'm just not getting what you are saying
Click to expand...
Click to collapse
The problem is I can ONLY boot into recovery or fastboot. I can not get a ROM to load on my device.
I little back story. When I originally bought the tablet I immediately upgraded it to JB 4.1 stock rom. After that upgrade was done I downloaded and installed ASUS official boot-loader unlock-er. I then installed TWRP recovery and it was like that stable for months. Just recently (yesterday) I tried to install HYDRO rom and it would not load that rom. I tried using the TWRP backup I created but that did not work either. So I still have full access to both recovery and fastboot, I just can't get any ROM ZIP files into the flash of the device to install with TWRP. When I use FASTBOOT to install the stock ASUS rom it will not boot either.
OK I was like has he never flashed a ROM before I gotcha..
is it possible to use ADB PUSH to put a rom on my internal storage ?
comzee said:
is it possible to use ADB PUSH to put a rom on my internal storage ?
Click to expand...
Click to collapse
adb push blob /sdcard/
adb shell
su
dd if=/sdcard/blob of=/dev/block/mmcblk0p4
adb reboot
I would consider using the proper stock blob here ( jb for jb bootloader or ics for ics bootloader ). It can be had by unzipping a stock update.
If su fails try without.
mmcblk0p4 is staging and used by asus to update, etc.
1 /system ext4 /dev/block/mmcblk0p1 (null)
2 /cache ext4 /dev/block/mmcblk0p2 (null)
3 /misc emmc /dev/block/mmcblk0p3 (null)
4 /staging ext3 /dev/block/mmcblk0p4 (null)
5 /data ext4 /dev/block/mmcblk0p8 (null)
6 /external_sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
I:Internal path defined: '/data/media'
I:External path defined: '/external_sdcard'
tobdaryl said:
adb push blob /sdcard/
adb shell
su
dd if=/sdcard/blob of=/dev/block/mmcblk0p4
adb reboot
Click to expand...
Click to collapse
Do I type this in verbatim?
tobdaryl said:
I would consider using the proper stock blob here ( jb for jb bootloader or ics for ics bootloader ). It can be had by unzipping a stock update.
If su fails try without.
mmcblk0p4 is staging and used by asus to update, etc.
Click to expand...
Click to collapse
I have the blob file from the asus update zip. What is the blob file for / what is it?
tobdaryl said:
1 /system ext4 /dev/block/mmcblk0p1 (null)
2 /cache ext4 /dev/block/mmcblk0p2 (null)
3 /misc emmc /dev/block/mmcblk0p3 (null)
4 /staging ext3 /dev/block/mmcblk0p4 (null)
5 /data ext4 /dev/block/mmcblk0p8 (null)
6 /external_sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
I:Internal path defined: '/data/media'
I:External path defined: '/external_sdcard'
Click to expand...
Click to collapse
NO idea what any of that means.
comzee said:
Do I type this in verbatim?
I have the blob file from the asus update zip. What is the blob file for / what is it?
NO idea what any of that means.
Click to expand...
Click to collapse
The yes you can type exactly. This assumes the file to push is located in the directory with adb.
The blob file is everything required to put your unit back to stock ( all required partitions ). (you will loose root and your custom recovery).
You could just use the adb push to place a flashable zip on your internal sdcard and flash with twrp or cwm.
The remainder of the info would be if you needed the partition designations and mounts so you would be able custom formulate what you wished to do. You can just forget it exists.
You could just
adb push yourfilename /sdcard/
and then flash with your recovery!
this could be a stock flashable rom or one of the custom roms (remember the bootloader must match ICS or JB of what you have installed in your unit).
Sorry I confused you!
tobdaryl said:
The yes you can type exactly. This assumes the file to push is located in the directory with adb.
The blob file is everything required to put your unit back to stock ( all required partitions ). (you will loose root and your custom recovery).
You could just use the adb push to place a flashable zip on your internal sdcard and flash with twrp or cwm.
The remainder of the info would be if you needed the partition designations and mounts so you would be able custom formulate what you wished to do. You can just forget it exists.
You could just
adb push yourfilename /sdcard/
and then flash with your recovery!
this could be a stock flashable rom or one of the custom roms (remember the bootloader must match ICS or JB of what you have installed in your unit).
Sorry I confused you!
Click to expand...
Click to collapse
yea that worked, I also got help from this LINK
on a side note, now that I have ASUS stock rom "US_epaduser_10_4_2_13_UpdateLauncher.zip" and TWRP 2.3.1.0 (newest).
is it possible to http://get.cm/?device=tf300t install those without any hitches, Like if I download the rom located at that link put it on my sd card and use TWRP to flash it, with what I currently am running will that work?
comzee said:
yea that worked, I also got help from this LINK
on a side note, now that I have ASUS stock rom "US_epaduser_10_4_2_13_UpdateLauncher.zip" and TWRP 2.3.1.0 (newest).
is it possible to http://get.cm/?device=tf300t install those without any hitches, Like if I download the rom located at that link put it on my sd card and use TWRP to flash it, with what I currently am running will that work?
Click to expand...
Click to collapse
I'm glad you are working again.
I showed adb instead of fastboot because that was your request.
In theory yes CM10 nightlies should be ok OP shows JB ( everything has issues sometimes ). Nightlies for yesterday may work great and be totally broken today that is the nature of nightlies. No stable release for CM10 on tf300 shown. I have not used that rom. I have seen posts saying it is not for jb bootloader and others saying it is.
I would read some of the posts asking for help and try to make a decision from there.
I believe I looked at the source a short time back and saw it was based on 2.6 kernel. I decided from there to go another route. Don't quote that as I could be mistaken. Maybe I should look again, sometime.
Good Luck!
I'm not into over clocking. I would look at clean rom and hydro jb. I have used both and they are good daily drivers. No fluff, they just work!
search for the tool adb pusher here on xda. Then go to recovery. Now open adb pusher and you can send the file you like to your internal space.
mikaole said:
search for the tool adb pusher here on xda. Then go to recovery. Now open adb pusher and you can send the file you like to your internal space.
Click to expand...
Click to collapse
Thanks!
OP has moved beyond the posted issue and is trying to decide on a non stock rom.
Suggestions?

bricked device?

hi,
I tried upgrading my tf300t from cm10.1 to cm10.2 . after a few failed attempts during which I am not exectly sure what I did wrong i got the device into a condition in which it only boots directly into CWM v6.0.2.3 without any option to do anything else. pressing power+volume down does not stop it from directly booting into recovery.
inside the recovery it says:
"E:Can't mount / cache/recovery/command/
E:Can't mount / cache/recovery/log/
E:Can't open / cache/recovery/log/
E:Can't mount / cache/recovery/last_log/
E:Can't open / cache/recovery/last_log/",
and i cannot mount any partition on the device. trying to access it from fastboot\adb has not been successful.
Any help would be appreciated.
thanks a lot,
guy
I now recall that at some point after trying to flash cm10.2 didn't work I tried flashing the offical asus firmware blob. after that the device successfully booted but when I tried to return to the recovery mode I still could not mount the /data partition. after that I tried some more flashing which brought me to the current situation.
new development -
after installing the universal naked driver i was able to boot into the boot loader using adb and I even can boot the device to the os, though no change when inside the recovery mode. if the device reboots it automatically goes into recovery and to reboot it I have to use adb again.
Ghtm said:
new development -
after installing the universal naked driver i was able to boot into the boot loader using adb and I even can boot the device to the os, though no change when inside the recovery mode. if the device reboots it automatically goes into recovery and to reboot it I have to use adb again.
Click to expand...
Click to collapse
Flash the updated stock ROM again via fastboot to reset it back to stock. then flash the correct TWRP and then flash the CM 10.2 ROM you wanted.
cmendonc2 said:
Flash the updated stock ROM again via fastboot to reset it back to stock. then flash the correct TWRP and then flash the CM 10.2 ROM you wanted.
Click to expand...
Click to collapse
how do i flash a rom using fastboot?
Ghtm said:
how do i flash a rom using fastboot?
Click to expand...
Click to collapse
like this:
http://www.theandroidsoul.com/how-to-restore-asus-transformer-tf300t-back-to-stock/
Code:
fastboot -i 0x0B05 flash system blob
cmendonc2 said:
like this:
Code:
fastboot -i 0x0B05 flash system blob
Click to expand...
Click to collapse
I've tried that and the device does not seem to be responding to the idea. in fact I dont think it gets anything I've tried to flash at all. the files do transfer but do not seem to install. after starting a flash with fastboot the device stops responding.
Ghtm said:
I've tried that and the device does not seem to be responding to the idea. in fact I dont think it gets anything I've tried to flash at all. the files do transfer but do not seem to install. after starting a flash with fastboot the device stops responding.
Click to expand...
Click to collapse
plus, the bootloader screen does not show the usb icon at all. I am flashing when the device is in the bootloader.
at the bootloader screen there is a message: "key driver not found"
Ghtm said:
I've tried that and the device does not seem to be responding to the idea. in fact I dont think it gets anything I've tried to flash at all. the files do transfer but do not seem to install. after starting a flash with fastboot the device stops responding.
Click to expand...
Click to collapse
OK you said it can boot into Android though. Use terminal emulator to install the TWRP and then flash the stock ROM from inside TWRP. Just make sure the TWRP matches your bootloader.
---------- Post added at 04:52 PM ---------- Previous post was at 04:51 PM ----------
Ghtm said:
plus, the bootloader screen does not show the usb icon at all. I am flashing when the device is in the bootloader.
at the bootloader screen there is a message: "key driver not found"
Click to expand...
Click to collapse
That means you are on the 4.2.1 or 4.2.2 bootloader. That bootloader doesnt have a USB icon, it goes directly to fastboot if it is detected and that is completely normal.
cmendonc2 said:
OK you said it can boot into Android though. Use terminal emulator to install the TWRP and then flash the stock ROM from inside TWRP. Just make sure the TWRP matches your bootloader.
---------- Post added at 04:52 PM ---------- Previous post was at 04:51 PM ----------
That means you are on the 4.2.1 or 4.2.2 bootloader. That bootloader doesnt have a USB icon, it goes directly to fastboot if it is detected and that is completely normal.
Click to expand...
Click to collapse
it says permission denied (cause i do not have root access?)
Ghtm said:
it says permission denied (cause i do not have root access?)
Click to expand...
Click to collapse
Oh i thought you still had CM10.1 on it. Can you flash ROMs from that CWM or is the /data thing messing it up.
cmendonc2 said:
Oh i thought you still had CM10.1 on it. Can you flash ROMs from that CWM or is the /data thing messing it up.
Click to expand...
Click to collapse
the /data prevents me from accessing anything on the sdcard so i cant flash anything from inside the recovery itself.
so, after doing as the guy in this thread - http://forum.xda-developers.com/showthread.php?t=2425581 says, I managed to make the device successfully reboot to the os by default and even make it reinstall the stock rom and than twrp recovery. the problem no is when entering recovery, it asks for a password which i do not know. when choosing cancel it gets me in but now it displays:
"E: unable to find partition size for /misc
E: unable to find partition size for /staging
E: unable to find partition size for /data
E: unable to find partition size for /recovery
E: unable to find partition size for /boot
updating partition details...
E: unable to mount /system
E: unable to mount /cache
E: unable to mount /cache
E:TWFunc::copy_log -- cant open destination log file: /cache/recovery/log
E:unable to set emmc bootloader message
E: unable to mount /cache"
when trying to install a different rom the recovery mode fails to access the internal/external sdcard.
thanks in advance,
guy
Ghtm said:
so, after doing as the guy in this thread - http://forum.xda-developers.com/showthread.php?t=2425581 says, I managed to make the device successfully reboot to the os by default and even make it reinstall the stock rom and than twrp recovery. the problem no is when entering recovery, it asks for a password which i do not know. when choosing cancel it gets me in but now it displays:
"E: unable to find partition size for /misc
E: unable to find partition size for /staging
E: unable to find partition size for /data
E: unable to find partition size for /recovery
E: unable to find partition size for /boot
updating partition details...
E: unable to mount /system
E: unable to mount /cache
E: unable to mount /cache
E:TWFunc::copy_log -- cant open destination log file: /cache/recovery/log
E:unable to set emmc bootloader message
E: unable to mount /cache"
when trying to install a different rom the recovery mode fails to access the internal/external sdcard.
thanks in advance,
guy
Click to expand...
Click to collapse
that means you probably flashed the wrong version of TWRP. Are you on the stock 10.6.1.8 or on a later version of bootloader? Those are different.
cmendonc2 said:
that means you probably flashed the wrong version of TWRP. Are you on the stock 10.6.1.8 or on a later version of bootloader? Those are different.
Click to expand...
Click to collapse
stock rom version 10.6.1.27.5 (build number JOP40D.US_epad-10.6.1.27.5-20130902)
TWRP 2.6.3.0
are those not compatible?
*
trying TWRP 2.5.0.0 or 2.4.2.0 made no difference.
Ghtm said:
stock rom version 10.6.1.27.5 (build number JOP40D.US_epad-10.6.1.27.5-20130902)
TWRP 2.6.3.0
are those not compatible?
*
trying TWRP 2.5.0.0 or 2.4.2.0 made no difference.
Click to expand...
Click to collapse
Using twrp 2.6.3.0 -4.2 ? Or -jb?
cmendonc2 said:
Using twrp 2.6.3.0 -4.2 ? Or -jb?
Click to expand...
Click to collapse
I do not remeber which I've tried. which one should it be?
*
I tried them both again. both require a password at start and both fail mounting the partitions, showing
"E: unable to find partition size for /misc
E: unable to find partition size for /staging
E: unable to find partition size for /data
E: unable to find partition size for /recovery
E: unable to find partition size for /boot
updating partition details...
E: unable to mount /system
E: unable to mount /cache
E: unable to mount /cache
E:TWFunc::copy_log -- cant open destination log file: /cache/recovery/log
E:unable to set emmc bootloader message
E: unable to mount /cache"
Ghtm said:
I do not remeber which I've tried. which one should it be?
*
I tried them both again. both require a password at start and both fail mounting the partitions, showing
"E: unable to find partition size for /misc
E: unable to find partition size for /staging
E: unable to find partition size for /data
E: unable to find partition size for /recovery
E: unable to find partition size for /boot
updating partition details...
E: unable to mount /system
E: unable to mount /cache
E: unable to mount /cache
E:TWFunc::copy_log -- cant open destination log file: /cache/recovery/log
E:unable to set emmc bootloader message
E: unable to mount /cache"
Click to expand...
Click to collapse
Use the 4.2 one. The jb will result in a very bad brick.
cmendonc2 said:
Use the 4.2 one. The jb will result in a very bad brick.
Click to expand...
Click to collapse
seems to be working! thank you very much, I really appreciate the help! :laugh::victory:
Ghtm said:
seems to be working! thank you very much, I really appreciate the help! :laugh::victory:
Click to expand...
Click to collapse
No problem, Merry Christmas!

Bootloop + E:unable to mount /data

Moderator Notes: I was asked to sticky this thread as it seems to be a recurring issue and a couple of fixes are in the posts.
Sorry my bad english am latin.
Hi guys first thread here and i need your help. Here s the thing, i was using my tf700, browsering, and the tablet goes off, i tried start up and a bootloop appears. So i go to Recovery (latest TWRP) and i tried to flash a ROM (latest crombi kk), like always i tried to wipe cache and dav bfore flash it but that proces seems to fail, and a couple of messages like unable to mount /data unable to mount /system appears, first time happening, i never had troubles with the tablet. So i tried to get fastboot mode and run the fastboot erase cach command (i read in a forum dat some guy did that and work for him), so i download the adb fastboot files, i connect the tf700 to my laptop (windows 7 64bit) and a installing drivers message and i wait and the driver that is called Transformer did not install, i dont know where to get those drivers, i found a file Asus usb drivers and bla bla but when i unzip the file i get 3 folders and no .exe or installer. So i tried to continue and i enter fastboot mode in the tablet and connect usb tablet-pc, and now another driver installing message appears, now is a driver called Fastboot, so i wait anda again the driver did not install correctly. So i continue and open cmd and tried the comman for erase cache, and only appears the WAITING FOR DEVICE text. i donw know waht to do, i also tried flashing again a ROM, bt only bootloop, trie again to wipe cache and dav but is only unable to mount /data. Any ideas ????
formobicho said:
Sorry my bad english am latin.
Hi guys first thread here and i need your help. Here s the thing, i was using my tf700, browsering, and the tablet goes off, i tried start up and a bootloop appears. So i go to Recovery (latest TWRP) and i tried to flash a ROM (latest crombi kk), like always i tried to wipe cache and dav bfore flash it but that proces seems to fail, and a couple of messages like unable to mount /data unable to mount /system appears, first time happening, i never had troubles with the tablet. So i tried to get fastboot mode and run the fastboot erase cach command (i read in a forum dat some guy did that and work for him), so i download the adb fastboot files, i connect the tf700 to my laptop (windows 7 64bit) and a installing drivers message and i wait and the driver that is called Transformer did not install, i dont know where to get those drivers, i found a file Asus usb drivers and bla bla but when i unzip the file i get 3 folders and no .exe or installer. So i tried to continue and i enter fastboot mode in the tablet and connect usb tablet-pc, and now another driver installing message appears, now is a driver called Fastboot, so i wait anda again the driver did not install correctly. So i continue and open cmd and tried the comman for erase cache, and only appears the WAITING FOR DEVICE text. i donw know waht to do, i also tried flashing again a ROM, bt only bootloop, trie again to wipe cache and dav but is only unable to mount /data. Any ideas ????
Click to expand...
Click to collapse
More likely your data partition got corrupted.
Try wiping it or formatting /data in TWRP to see if that helps? You will lose everything if you don't have backups.
sbdags said:
More likely your data partition got corrupted.
Try wiping it or formatting /data in TWRP to see if that helps? You will lose everything if you don't have backups.
Click to expand...
Click to collapse
i already tried that, wiping (cache, dav, system, ata, factoty reset) anything gives the unable to mount /data error.
formobicho said:
i already tried that, wiping (cache, dav, system, ata, factoty reset) anything gives the unable to mount /data error.
Click to expand...
Click to collapse
You'll need to manually format it using the terminal in TWRP
Make sure data is umounted then run this command. Make sure you have charged it as well or leave it plugged in.
It can take a number of hours to complete.
Code:
mke2fs -T ext4 /dev/block/mmcblk0p8
sbdags said:
You'll need to manually format it using the terminal in TWRP
Make sure data is umounted then run this command. Make sure you have charged it as well or leave it plugged in.
It can take a number of hours to complete.
Code:
mke2fs -T ext4 /dev/block/mmcblk0p8
Click to expand...
Click to collapse
first of all is an honor chat with the legend sbdags!!! second can u guide me step by step. i did enter in twrp and go to advanced then terminal command then a selection menu appear and said browse to starting folder and a list of folder appears and a botton with Select Folder, wich folder i must select now? i tried just hit the select folder button and then i put the command taht u said and in the terminal said mke2fs 1.41.14 (22-dec-2010) nothing more and nothing happen
sbdags said:
You'll need to manually format it using the terminal in TWRP
Make sure data is umounted then run this command. Make sure you have charged it as well or leave it plugged in.
It can take a number of hours to complete.
Code:
mke2fs -T ext4 /dev/block/mmcblk0p8
Click to expand...
Click to collapse
Thank you so much sbdags.
You're a life save thought I had softbricked my tf700
Muchas gracias
formobicho said:
first of all is an honor chat with the legend sbdags!!! second can u guide me step by step. i did enter in twrp and go to advanced then terminal command then a selection menu appear and said browse to starting folder and a list of folder appears and a botton with Select Folder, wich folder i must select now? i tried just hit the select folder button and then i put the command taht u said and in the terminal said mke2fs 1.41.14 (22-dec-2010) nothing more and nothing happen
Click to expand...
Click to collapse
Did you unmount data first?
---------- Post added at 07:25 AM ---------- Previous post was at 07:24 AM ----------
chukkie said:
Thank you so much sbdags.
You're a life save thought I had softbricked my tf700
Muchas gracias
Click to expand...
Click to collapse
You are welcome!
EDIT - somehow the format finally took.. after 5 or 6 reboots.. very strange
okay, i hate to bump this thread. but i have been searching for a few nights and i cannot find a solution. i am having the same problem as OP.
Essentially, my tablet was interrupted mid format. I believe my data partition is corrupted. I can access recovery/fastboot and the tablet accepts commands from my PC. i have TWRP 2.7.1.1 on the tablet right now.
i tried what sdbags said:
You'll need to manually format it using the terminal in TWRP
Make sure data is umounted then run this command. Make sure you have charged it as well or leave it plugged in.
It can take a number of hours to complete.
Code:
mke2fs -T ext4 /dev/block/mmcblk0p8
Click to expand...
Click to collapse
this did not work. i got the same "mke2fs 1.41.14 (22-dec-2010)" output, and then the tablet rebooted back into TWRP over again. (data was not mounted, i cannot mount it at all)
some more output from my tablets TWRP console:
Code:
e:could not mount/data and unable to find crypto footer.
e:unable to mount '/data'
e:unable to recreate /data/media folder/
updating partition details...
e:unable to mount '/data'
e:unable to mount internal storage.
e:unable to mount /data/media during gui startup
full selinux support is present.
e:unable to mount /data/,edia/twrp/.twrps when trying to read settings file.
e:unable to mount '/data'
is there another way to fix my corrupted partition?
this did not work. i got the same "mke2fs 1.41.14 (22-dec-2010)" output, and then the tablet rebooted back into TWRP over again. (data was not mounted, i cannot mount it at all)
Click to expand...
Click to collapse
I have exactly same situation
edit: after running this command
mke2fs -T ext4 /dev/block/mmcblk0p8
Click to expand...
Click to collapse
it prompt
Starting Path : /external_sd
Click to expand...
Click to collapse
and there is also button "KILL" when I hit enter it prompt : /dev/block/mmcblk0p8 is appereatly in use by the system: Will not make a file system here!
Any advice? (sry for being this big noob!)
Code:
adb shell
killall -19 recovery
make_ext4fs /dev/block/mmcblk0p8
reboot
Type in those commands via a usb connection to your device whilst it is in recovery.
sbdags said:
Code:
adb shell
killall -19 recovery
make_ext4fs /dev/block/mmcblk0p8
reboot
Type in those commands via a usb connection to your device whilst it is in recovery.
Click to expand...
Click to collapse
Wouw thanks for so fast reply :highfive:.
But I think I'll disepoint you "usb debugging is disabled"
---------------------------------------------------------------------------------------------------------------
Any way I can reinstall stock from fastboot? damn it......
brinza said:
Wouw thanks for so fast reply :highfive:.
But I think I'll disepoint you "usb debugging is disabled"
---------------------------------------------------------------------------------------------------------------
Any way I can reinstall stock from fastboot? damn it......
Click to expand...
Click to collapse
No idea how when and after what exactly but the installation of stock rom started by itself after couple of reboots and couple of command i tried. (I had a file : US_epad-user-10.6.1.14.10.zip on my SD card
sbdags said:
Code:
adb shell
killall -19 recovery
make_ext4fs /dev/block/mmcblk0p8
reboot
Type in those commands via a usb connection to your device whilst it is in recovery.
Click to expand...
Click to collapse
Probably a Bad Idea - you should unmount /data before formatting. Then it should also not hurt to keep the recovery running.
Unbrick my TF 700t
Accidentally, bricking my tablet
I try Advance and Terminal Command with TRWP at tablet, it did not work
but when I try with command from PC (desktop), it works like a charm. I was able to see internal storage
from that just re install Custom ROM. Thank alot to sdbag
Thanks
sbdags said:
Code:
adb shell
killall -19 recovery
make_ext4fs /dev/block/mmcblk0p8
reboot
Type in those commands via a usb connection to your device whilst it is in recovery.
Click to expand...
Click to collapse
Wow. you are a life saver. that worked for me.
player50 said:
Wow. you are a life saver. that worked for me.
Click to expand...
Click to collapse
Glad it worked. Everyone should keep those commands handy
Thanks a lot...
After a long research I have found your thread.
I have almost given up looking for this damn issue...
At last, It became real! You are a real life saver.
sbdags help!
1) i dont know how to unmount data .
2) when i click advanced then terminal command it opens- Browse to starting folder and gives the file manager kind of view.
3) so i tried using adb on computer
the first three command work(i think but the third gives this error not enough space) .
please suggest a solution. thank you in advance
device moto g xt1033
i tried downgrading from lollipop 5.0 brasilian to kitkat but it wont go past warning bootloader unlocked screen. when i flash cm from twrp, it gives 3 errors
E:/ unable to mount '/data'
E:/ unable to mount '/cache'
E:/ unable to mount internal storage
then when i start it just keeps on loading on cm logo
should i create a separate thread for all this?
'
SemiNoob314 said:
1) i dont know how to unmount data .
2) when i click advanced then terminal command it opens- Browse to starting folder and gives the file manager kind of view.
3) so i tried using adb on computer
the first three command work(i think but the third gives this error not enough space) .
please suggest a solution. thank you in advance
device moto g xt1033
i tried downgrading from lollipop 5.0 brasilian to kitkat but it wont go past warning bootloader unlocked screen. when i flash cm from twrp, it gives 3 errors
E:/ unable to mount '/data'
E:/ unable to mount '/cache'
E:/ unable to mount internal storage
then when i start it just keeps on loading on cm logo
should i create a separate thread for all this?
'
Click to expand...
Click to collapse
Question: Why don't you care to read the short thread from beginning?
das chaos said:
Question: Why don't you care to read the short thread from beginning?
Click to expand...
Click to collapse
i am really sorry if the earlier comment came out as rude.
actually i did all of those steps, using the command terminal, using adb from pc but none of them worked, all of them had some problem

Categories

Resources