Database Info

Can't Mount Data, Cache or Failed PU

I wanted to start this thread so we can a place where everyone who discovers this issue, comes here and posts on what they did, how they managed to recover from it, and what steps they have taken on preventing this from happening.
I've been lurking around and it seems as if it's the users with the gfree method thats it's only happening too.
I wanna keep track how it happens, as the glacier isn't the only one that suffers from this but it's been happening quite often these past few days. Thanks
Please state how it happen, what rom you flashed and or nandroid backup and if you pulled your battery during a flashing, wiping session.
I can confirm that we're not the only ones that this is happening too. G2 users are also having the same exact problem. There seems to be a really good chance of why this is happening because of different emmc chips and or drivers, i'll be looking through irc logs and put out a summary here for all.
And also, check this out. I know our devices varies from the G2 quite a bit, but then again we're using the same rooting method and exploit so it makes sense to check some stuff from there. http://forum.xda-developers.com/showthread.php?p=13234526

I am sorry if I sound like a nood , but I am a noob:© . I used the gfree mathed to root my phone, didn't run into the problem you are discrubing. Mybe I didn't quite get it.
Sent from my HTC Glacier using XDA Premium App

ummm yea.... happened to me today and after trying basically everything (nandroid restore, flash rom via zip, flash official rom via bootloader etc.) nothing worked
It happened when i was using Virtous Fusion and decided to flash back my Cyanogenmod 7 backup. I has the latest clockworkmod 3.0.2.4, Cleared data / cache and ran the restore... after it was done, i rebooted and noticed that it would not go past the Mytouch splash screen... went back to recovery via the vol down + power combo only to be greeted with...
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
Nandroid backups dont flash, zip roms flash (or it seems) but doesnt boot, i get errors when i try to wipe, flashing official rom via bootloader gives me the dreaded FAIL-PU after most steps, so yea... im boned lol
Apparently there is a chance to restore if u got the engineering bootloader but i did not at the time. I did root via gfree since the visionary method refused to gain s-off

I wonder if it has something to do with restoring after clearing data/cache instead of directly restoring... I've never cleared those before a restore and I have never had an issue. let's get some other people in here to test that theory.

kimbernator said:
I wonder if it has something to do with restoring after clearing data/cache instead of directly restoring... I've never cleared those before a restore and I have never had an issue. let's get some other people in here to test that theory.
Click to expand...
Click to collapse
You should be clearing data and cache before restores. There are a lot of things in /data that do not carry over well when changing ROMs. I wonder if it's something to do with ClockworkMod 3.x recoveries.

here you go this is my experience:
http://forum.xda-developers.com/showpost.php?p=13709837&postcount=22

All the users who had this trouble Were rooted with gfree. Any users with the first s-off method?
_ice_ said:
here you go this is my experience:
http://forum.xda-developers.com/showpost.php?p=13709837&postcount=22
Click to expand...
Click to collapse
Sent from my HTC Glacier using XDA App

mike21pr said:
It happened when i was using Virtous Fusion and decided to flash back my Cyanogenmod 7 backup. I has the latest clockworkmod 3.0.2.4, Cleared data / cache and ran the restore...
Click to expand...
Click to collapse
You know you should do a factory reset via the recovery image prior to flashing any new ROM. ESP when coming from a 2.2 ROM to a 2.3 ROM.
I wonder if that is what is causing the problem. The Clockwork ROM Manager doesn't wipe everything the "factory reset" in the recovery image itself.

neidlinger said:
You know you should do a factory reset via the recovery image prior to flashing any new ROM. ESP when coming from a 2.2 ROM to a 2.3 ROM.
I wonder if that is what is causing the problem. The Clockwork ROM Manager doesn't wipe everything the "factory reset" in the recovery image itself.
Click to expand...
Click to collapse
You don't mean do the "factory reset" on the HBOOT screen do you?
So.. going from say a 2.2.1 stock to 2.3.3, do... (through clockworkmod recovery screen NOT ROM MANAGER APP)
1. wipe data/factory reset
2. wipe cache partition
3. wipe dalvik (optional?)

If you don't use Rom mamaher to load your Roms , would you run in to the same problem.?
Sent from my HTC Glacier using XDA Premium App

h22aboi said:
You don't mean do the "factory reset" on the HBOOT screen do you?
So.. going from say a 2.2.1 stock to 2.3.3, do... (through clockworkmod recovery screen NOT ROM MANAGER APP)
1. wipe data/factory reset
2. wipe cache partition
3. wipe dalvik (optional?)
Click to expand...
Click to collapse
Wipe data factory reset is broken in cwm 3.0.2.4 it hangs when it comes to /data or /cache especially if you have a cooked rom flashed before from an amateur developer.
I noticed that /data or /cache sometimes do not mount properly thus leaving behind corrupted files.
So my advice is to use the advanced format menu in cwm.
1. Wipe dalvik
2.mount /cache, wipe /cache
3. Wait for it, then mount /system, wipe /system
4. mount /data and wipe /data <--- last
Also because some roms come w autowipe feature sometimes when it tries to wipe an already wiped partitions then sectors get corrupted. So if the rom has auto wipe feature built in. You do not need to wipe /system or /data
Sent from my HTC Glacier using XDA App

jdkoren said:
You should be clearing data and cache before restores. There are a lot of things in /data that do not carry over well when changing ROMs. I wonder if it's something to do with ClockworkMod 3.x recoveries.
Click to expand...
Click to collapse
Restoring clears those partitions by itself. I've always been taught that it's only necessary to clear those partitions when you install a new rom, but restoring does it all by itself. I've restored probably more than 15 times without any clearing and it works fine.
Also, I didn't use gfree, and I might not if people get these errors when they do.

Yeah, this is my third mytouch, and this is the only one I used gfree on. I remember with my second one I didn't use the gfree method and I flashed and did everything without any of these risks. Im stilling leaning towards the gfree method being the culprit for the recovery errors.
kimbernator said:
Restoring clears those partitions by itself. I've always been taught that it's only necessary to clear those partitions when you install a new rom, but restoring does it all by itself. I've restored probably more than 15 times without any clearing and it works fine.
Also, I didn't use gfree, and I might not if people get these errors when they do.
Click to expand...
Click to collapse
Sent from my HTC Glacier using XDA App

xdviper said:
Yeah, this is my third mytouch, and this is the only one I used gfree on. I remember with my second one I didn't use the gfree method and I flashed and did everything without any of these risks. Im stilling leaning towards the gfree method being the culprit for the recovery errors.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
yes sir, that could be another factor. gfree is mainly for CID unlock and "true root" but thing is true root isn't required... every other rom flashes -.- gfree also alters your dev block partition which can cause issues.

This thing has me a little worried.
I used the gfree method from the CM Wiki for the Glacier. I have s-off and hboot .85, but I am a bit more hestitant now to flash different roms seeing as how many people are having problems. However, I don't like Rom Manager and never use it. I always go through CWR to flash so is that better? And I am on 3.0.0.6.

FYI, according to trueblue_drew he says to do this as far as wiping your stuff on flashing one of his roms...
This is how you should wipe:
Main Recovery Menu:
1. Wipe data / factory reset
2. wipe cache partition
Advanced Recovery Menu:
3. Wipe Dalvik Cache
Mounts and Storage Recovery Menu:
4. Format System
Sent from my HTC Glacier using XDA

I got the fail PU error a week ago. I was on an miui rom and was restoring a backup I had of cm7. When I rebooted after the restore the phone would not load past the splash screen. I booted back into recovery and noticed the E: Can't mount/cache errors. I tried to flash a new rom but when I would reboot it would not go past the splash screen still. That's when I looked up the problem. I then tried to restore with the PD15IMG, but got the fail PU errors. I then read that you need the part7backup on the sd card if you are going to use the PD15IMG. So I did and stilll got the fail PU errors, but this time it was stuck loading the radio. I pulled the battery. Would not even turn on after that.
I too had rooted with the gfree method and had the engineering bootloader.
I called T-mobile to replace the phone since it wouldn't even turn on anymore. Took 2 hours to get them to send a replacement with free shipping. They accidentally sent me 2. Two separate boxes, same shipping number. At least now I have a backup. I already rooted one. I did not use the gfree method this time.

Since it seems to be a gfree problem, should I go to stock and re-root the phone using another method??

tilt4life2 said:
Since it seems to be a gfree problem, should I go to stock and re-root the phone using another method??
Click to expand...
Click to collapse
Well, that's what I'm probably going to end up doing as well. This is my third replacement and the first method to root didn't stick, so I ended up rooting with gfree. I am going to unroot and try rooting with the first method which is here http://theunlockr.com/2010/12/10/how-to-gain-permanent-root-and-s-off-on-the-t-mobile-mytouch-4g-htc-glacier/ but the thing is, if it doesn't stick, we're back at gfree.
Anyone know any G2 users that have/had this problem? We're using the same rooting method so there should be a couple people who faced this.

Alright well I've been reading logs from G2_Root channel from April 26th and so on, and it looks like the G2 has two different types of the emmc chip. Gfree powers off this chip and then initializes the chip again in order to get around the write protection. I remember before we had root access on the G2 (before I traded for a mytouch) I would lurk around the irc channel and read progress. I remember having to get the chip to power on in order to get around the write protection.
Now it looks like while the phone is being used, or booting up and or trying tto read or write from emmc the chip suddenly dies. This is what causes us to get force closes, freezes and not being able to get past the splash screen and also explains the recovery not being able to mount partitions.
We're going to need people to join in the G2 channel preferably ones who still have their defective phones to get some data off it.
Again, this is a very vague summary of what I've been able to read off the irc logs.
Why the G2? Because we're using the same gfree method to root our phones and with our phones dying it makes sense.
I think, they have already ruled out recovery and the Eng hboot to be culprit but this is just too early in the game to determine.
Here's a thread from the G2 side, if anyone still has this problem with their cache not being to mount please check out post #13.
I'll look.around more and see what I find from the G2 side.
http://forum.xda-developers.com/showthread.php?t=1039504
Sent from my HTC Glacier using XDA App

[THINKTNK] Getting faux GingerAOSP running on (broken?) G2X's!

So after trying, and trying, and trying some more to get Faux's Roms/Kernels to run on my G2x. I know a handful of other people are having the same issues.
Due to the lack of efforts on trying to get this to work other than "Get a new device" (which I refuse to believe that its the release date of the phones that can't do it) I would like to give a bit of info about what i've done so far, and start a think tank to get those of us who want to run this great rom a future where we CAN run it!
So that being said;
When faux first released the AOSP gingerbread and I flashed it, I HAVE had it running. Something between the most recent updates, and the Clockwork recovery updates caused me to not be able to. SO
I put my phone back to complete stock 100%
Then rooted the phone.
flashed the original clockwork recovery ( orange color one ) (EXTERNAL not INTERNAL)
copied over faux AOSP latest, gapps, and ext4 kernel
wiped data
wiped cash
wiped dalvik
format /system
installed from SD faux AOSP, then flashed gapps
rebooted
(went to LG screen, then went black, then lit-up, then black again)
pulled battery (went back into recovery)
I've tried full wipe/format then flashing aosp with and without gapps, and fixed permissions, and tried it without fixing permissions. NOTHING.
Any other ideas from anyone else who can't get it to work, or maybe couldn't but then figured out how?

check the md5 checksum of the ROM

worker1 said:
check the md5 checksum of the ROM
Click to expand...
Click to collapse
you wanna give me more info about how to do that and what it is?

javolin13 said:
you wanna give me more info about how to do that and what it is?
Click to expand...
Click to collapse
Md5 checksum is a unique string if numbers that you compare to ensure that you did not download a corrupt file.
Most rom cookers will provide an md5 that you can compare against.
Google md5 checksum for freeware to generate the number.

diablos991 said:
Md5 checksum is a unique string if numbers that you compare to ensure that you did not download a corrupt file.
Most rom cookers will provide an md5 that you can compare against.
Google md5 checksum for freeware to generate the number.
Click to expand...
Click to collapse
Thanks for the reply, i'll give this a check

So after downloading the 1.2.0 file again, and comparing the MD5 checksum's are both the same:
MD5 checksum: 295e1224a85794ec354e69906432c560

Mine worked right away. I went from stock to eb froyo to cm7 then to this. I did the usual wipes prior to installing. I'm using the ext4 red text recovery.
Not sure if it matters but try cm7 then wipe then install this rom?
G2x with faux AOSP

tackleberry said:
Mine worked right away. I went from stock to eb froyo to cm7 then to this. I did the usual wipes prior to installing. I'm using the ext4 red text recovery.
Not sure if it matters but try cm7 then wipe then install this rom?
G2x with faux AOSP
Click to expand...
Click to collapse
Testing now.

After trying, now it no longer goes to the black screen. I flashed cm7, then wiped ALL again, and reflashed AOSP ginger 1.2.1, rebooted, and it is stuck now at the LG screen and does nothing ( I waited for 10 minutes at the LG screen )

did you flash the ext4 kernel after you flashed the rom? if you have ext4 partitioned and you flash a rom with an ext3 kernel it will boot hang until you install a kernel that uses ext4...
easiest way to solve this is restore the stock nandroid, which uses ext3 and start all over with whatever you want, in your case from there wipe everything, flash rom, then flash whatever ext4 kernel you want...

JHaste said:
did you flash the ext4 kernel after you flashed the rom? if you have ext4 partitioned and you flash a rom with an ext3 kernel it will boot hang until you install a kernel that uses ext4...
easiest way to solve this is restore the stock nandroid, which uses ext3 and start all over with whatever you want, in your case from there wipe everything, flash rom, then flash whatever ext4 kernel you want...
Click to expand...
Click to collapse
Latest update:
I flashed CM7 back on the phone, using red cw recovery, then tried the latest faux cm7 kernel which has ext4 and it would not boot, it hung at LG, then went to a black screen.
did a full wipe again, and didn't flash the kernel, and the phone boots fine with cm7
so whatever the issue is, it seems to be only with things faux is cooking/building ( i've flashed EVERY rom for g2x and they all work fine except faux )

javolin13 said:
Latest update:
I flashed CM7 back on the phone, using red cw recovery, then tried the latest faux cm7 kernel which has ext4 and it would not boot, it hung at LG, then went to a black screen.
did a full wipe again, and didn't flash the kernel, and the phone boots fine with cm7
so whatever the issue is, it seems to be only with things faux is cooking/building ( i've flashed EVERY rom for g2x and they all work fine except faux )
Click to expand...
Click to collapse
When you say "full wipe" are you formatting /system as well?

sryan1983 said:
When you say "full wipe" are you formatting /system as well?
Click to expand...
Click to collapse
Yes that is correct full wipe;
wipe data
wipe cash
wipe dalvik
format /system

hmmm sounds like a kernel incompatibility of some sort... i dont have everything on my phone right now to try and recreate the situation or else id help you out... i will check tomorrow and if you have not figured it out i will see what i can do...
for now, nandroid back to complete stock and start from there and see if that fixes anything...

JHaste said:
hmmm sounds like a kernel incompatibility of some sort... i dont have everything on my phone right now to try and recreate the situation or else id help you out... i will check tomorrow and if you have not figured it out i will see what i can do...
for now, nandroid back to complete stock and start from there and see if that fixes anything...
Click to expand...
Click to collapse
Thanks for your input, i've already went to 100% stock, and rooted, put cw recovery (red) on and wiped everything, then flashed faux and gapps, and it didn't work.

intriguing. I was thinking it was a hardware change that did it. Have you tried the Trinity kernel? I am guessing that something must be changed in the hardware between ones that work and ones that don't. I have run every version of this ROM since day 1 without a single issue with booting. That includes all kernels as well.

javolin13 said:
Thanks for your input, i've already went to 100% stock, and rooted, put cw recovery (red) on and wiped everything, then flashed faux and gapps, and it didn't work.
Click to expand...
Click to collapse
I am in the EXACT same boat.
I've flashed every possible rom and it loads without fail. Anything faux and it locks at the LG boot screen.
Trinity kernel loads just fine as well as all the stock ones.

Wow I'm so dumb... after you flash the rom then do a wipe and then flash the kernel of your choice...

javolin13 said:
Thanks for your input, i've already went to 100% stock, and rooted, put cw recovery (red) on and wiped everything, then flashed faux and gapps, and it didn't work.
Click to expand...
Click to collapse
You need to flash 0.1.1 ext4 kernel if you are using CW recovery *RED*. Faux's AOSP rom only comes with ext3 built-in. You have to flash ext4 kernel after flashing rom then GApps.

JHaste
"Wow I'm so dumb... after you flash the rom then do a wipe and then flash the kernel of your choice"
-flash the ROM then do a wipe, then flash the kernel???? What was the point in flashing the ROM then?

Transformer stuck in constant boot loop

I'm not sure what happened to my tablet. I really can't seem to figure it out. I was using it last night before I went to sleep, and I just closed it away (I have the keyboard dock), and packed it in the case this morning for work. When I took it out to use it at work it had already been stuck in a boot loop. I have wiped, and reinstalled 3 different roms on it since. It's still doing the same thing. Is there anything else I can do? What could have caused this?

I know that you've tried to flash several ROMs, but please check if you've done all the steps described below:
Copy ROM to /sdcard
Reboot in recovery
Wipe /system, /cache and dalvik-cache
Install ROM
Reboot and see if it works
If not, you might also want to delete /data, but make sure you backup it first (you can do that with a nandroid) and use /external_sd to store the ROM (just in case).

You can also try restoring your nandroid backup.

VibrantWind said:
You can also try restoring your nandroid backup.
Click to expand...
Click to collapse
I have tried both. When I flashed the original backup back onto the tablet I got the same result. I have completely wiped all data as far as I know. I even went a step further and formatted my sd card to ensure none of the ROM files were corrupt, then placed them back on the card. Is there even more data I can delete other than the system wipe/cache/dalvic cache?

wipe staging
wipe battery stats
ummmmm yeah those are the only 2 not listed and are not all that usefull to you
Do you have nvflash ? If so i would do a complete wipe ie format everything even recovery etc then flash a nvflash rom then restore my nandroid if i knew the integrity of it was good
Sent from my Transformer TF101 using xda premium

theres a Super wipe I use in mikes Android Revolution HD thread..
I have used this before to fix a few problems I was having..
Check "how to flash" section for it
http://forum.xda-developers.com/showthread.php?t=1245892

I had the same thing happen to me. Just boot loop out of the blue. It was sitting at home charging, came home to it boot looping.
I tried re-flashing the rom I was on (prime) and flashing other roms and nothing worked.
I had to use the super-wipe script to get it working.

fone_fanatic said:
I had the same thing happen to me. Just boot loop out of the blue. It was sitting at home charging, came home to it boot looping.
I tried re-flashing the rom I was on (prime) and flashing other roms and nothing worked.
I had to use the super-wipe script to get it working.
Click to expand...
Click to collapse
I have tried the Revolutionary Rom, and after it wipes and installs, and reboots it just says at the Asus eEE screen. What on earth could I have possibly done? Is the super wipe something that can be manually done, or does this only occur while installing the rom?

Holy Canoli, I think I may have forgot one step.....one second..."tinkering"...
Edit: update, I'm not going to tell anyone what I forgot to do after the super wipe (which is a godsend), but alas, my Transformer is functional again. Thanks guys!

MrAutomatic said:
Holy Canoli, I think I may have forgot one step.....one second..."tinkering"...
Edit: update, I'm not going to tell anyone what I forgot to do after the super wipe (which is a godsend), but alas, my Transformer is functional again. Thanks guys!
Click to expand...
Click to collapse
Let me guess... You flashed super-wipe, but didn't install any ROM after...

Don't worry, we're here to help, not judge!
AzureusPT said:
Let me guess... You flashed super-wipe, but didn't install any ROM after...
Click to expand...
Click to collapse
My bet is on that as well! haha
Not going to lie.. I've done that before.

Recovery Issue with both CWM and TWRP

I posted this in Q&A, but no replies led me to post here as well.
Hi. I've been using this Xoom for a couple weeks now, and just started having this problem yesterday.
Before I noticed the promblem I was on EOS 3 Wingman. I had TWRP 2.2.2.0 as recovery.
I wanted to give CM10 nightlies a shot. Downloaded the ROM and GAPPS through Goo. I tried to flash the CM10 ROM and GApps zip through the Goo interface. Xoom rebooted and instead of installing, I just got a contantly repeating error saying the install failed.
Eventually I rebooted the xoom and went into recovery. I tried to wipe data and it said it couldn't be mounted. Same error for wiping system, cache, etc...
Rebooted xoom and the EOS 3 rom was still working fine, I downloaded [Recovery] ClockworkMod 3.2.0.0 (R4c) Modded for Internal media [UPDATED 10/6]" and flash via adb. rebooted to recovery and tried wipe. same issue. nothing could be wiped. everything said "failure mounting <applicable partition>".
I tried flahing rogue recovery and got the same thing. I said screw it and rebooted back into EOS and it's been working fine. EOS was updated last night to 143, so i downloaded and tried to install through goo. I got the repeating errors again. Rebooted into recovery and still got the errors where it seems like none of the partitions are writeable.
I WAS able to install the EOS update directly through recovery.
Has anyone ever seen this behavior before and know how to fix it? I can't even export logs in the 2 CWM recoveries because they fail when trying to write the log file.
If I try to install an update through goo, it reboots to recover and just keeps scrolling "An Update Error has occured".
I can reboot to recovery and install the zip from there directly with no issue.
Here is the log for the failed data wipe...
I:mke2fs command: mke2fs -t ext4 -m 0 /dev/block/mmcblk0p10
mke2fs 1.41.12 (17-May-2010)
/dev/block/mmcblk0p10 is apparently in use by the system; will not make a filesystem here!
E:Unable to format data.
* Verifying filesystems...
I:=> Let's update filesystem types via verifyFst aka blkid, command: 'blkid'.
* Verifying partition sizes...
Ievice has /data/media
I:Total used space on /data is: 5122715648
I:Total in /data/media is: 3962468352
I:Actual data used: 1160247296
du: /data/media/.android_secure: No such file or directory|
once in recovery, if I try to format data, it says "Unable to format data". Log

Well I can't help, I'm in the same boat...hoping to get some insight from any responses you might get.

grey.ghost said:
Well I can't help, I'm in the same boat...hoping to get some insight from any responses you might get.
Click to expand...
Click to collapse
It's extremely unusual to get no responses to an issue like these here at XDA. leads me to believe it might be a very uncommon problem. The folks here are usually on the ball about any issue that has even arisen before.
That being said, I am going to try to flash the stock RUU back on from this link...
http://developer.motorola.com/produ...utm_source=supportforums&utm_term=unlockboard
After I finish, I re-root/unlock.
I'll let you know how it goes.

I'll let you know if I come up with something as well. So far I've managed to erase the sd card and maintain a constant boot loop.

Flashing all of the stock img, relocking, and unlocking again didn't do ****.
Found an original MZ600 SBF, which is what I need for verizon 3g xoom, I'm installing this via RSD Lite to see if it blows away whatever is causing the issue.

I was able to wipe the entire system and use adb to repeat the unlock and root steps. So far so good. I'm using the CWM 3.2.0.0 recovery image right now though. I have at least been able to get into a clean copy of a ROM and no bootloops yet. Can't restore data off old Nandroids, so I'm about to update to the newer CWM based recovery image and see if that will help.

I think I'm OK now.
I installed the SBF. Let all of the OTA updates come in including the ICS update where my 3g stops.
flashed the ROGUE recovery from fastboot.
I was able to format all partitions and install and boot CM9 nightly.

Me too, i was sweating hard for a bit, but was able to go through the entire process from stock, unlock, root, rogue recovery and then flashed CNA. Got that working without boot loops or fc and then advance restored data from a previous nandroid through rogue to get it back. A couple of apps had to be redownloaded from the market, but it looks as if I'm back in business. I want to try TWRP, but every time I do something screws up, so I think I'll stop trying.
Thanks for the help.

grey.ghost said:
Me too, i was sweating hard for a bit, but was able to go through the entire process from stock, unlock, root, rogue recovery and then flashed CNA. Got that working without boot loops or fc and then advance restored data from a previous nandroid through rogue to get it back. A couple of apps had to be redownloaded from the market, but it looks as if I'm back in business. I want to try TWRP, but every time I do something screws up, so I think I'll stop trying.
Thanks for the help.
Click to expand...
Click to collapse
Are you installing Twrp from goo manager. Cause I have not had any issues with the goo manager download. But did have issues with the zip file here on xda. I dont kknow if it is worth a try but that is how I did it.
Sent from my Xoom using xda app-developers app

Well sense this is a twrp related issue I would think u would have asked in my thread where I released the port for twrp to Xoom,
Having said that, at one point n time there was a note n the open about open script recovery. But its is also buried in the thread too. So I will answer your question and also presume a few things... and please correct me if I am wrong anywhere.
Once u set the download path in goo app to /data/media/goomanager/ and downloaded a ROM, clicked flash ROM, and entered recovery once u saw all the E/ update error u manually rebooted the Xoom and did not let the script finish installing the ROM? If I am correct that so far. That's what cause your additional problems. You basically rebooted recover while mid install of a ROM.
Now as stated it the twrp thread for Xoom, these errors are false errors and should be ignored. To add it the reassurance that they are intact false errors, from goo app select to flash a ROM again and simple allow the script to finish and then the tablet will reboot on its own when it is finished with the script. And you will be greeted with your new ROM you just successfully flashed.
Again let me know if I am wrong on assuming you forced a reboot mid install ( aka while u saw all the errors)
Sent from my Nexus 7 using Tapatalk 2

runandhide05 said:
Well sense this is a twrp related issue I would think u would have asked in my thread where I released the port for twrp to Xoom,
Having said that, at one point n time there was a note n the open about open script recovery. But its is also buried in the thread too. So I will answer your question and also presume a few things... and please correct me if I am wrong anywhere.
Once u set the download path in goo app to /data/media/goomanager/ and downloaded a ROM, clicked flash ROM, and entered recovery once u saw all the E/ update error u manually rebooted the Xoom and did not let the script finish installing the ROM? If I am correct that so far. That's what cause your additional problems. You basically rebooted recover while mid install of a ROM.
Now as stated it the twrp thread for Xoom, these errors are false errors and should be ignored. To add it the reassurance that they are intact false errors, from goo app select to flash a ROM again and simple allow the script to finish and then the tablet will reboot on its own when it is finished with the script. And you will be greeted with your new ROM you just successfully flashed.
Again let me know if I am wrong on assuming you forced a reboot mid install ( aka while u saw all the errors)
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
No, after pushing the TWRP recovery to the Xoom using adp, I would clean install a ROM and get one of two results....1) the ROM would run for a few seconds and then reboot, or 2) the ROM would run, but everything would fc. Fixing permissions, wiping everything, etc., wouldn't help the issue. No matter what I tried under TWRP, those were the results. I ended up having to start from scratch to negate whatever it was that was making the xoom go funky. Once I pushed rogue and followed the same process, I was back in business.
Sent from my Xoom using Tapatalk 2

Corrupt internal SD Card

Hi Folks.
Ok here is my situation, I have a rooted and unlocked TF700.
I flashed Zeus 4 and all worked well, then flashed (after full wipe) PARANOIDANDROID 2.15 and again everything was great,
Yesterday I flashed Baked Bean 4 (again after a full wipe) and apart from some SD issues all seemed ok,
I then decided to restore my TWRP backup of Zeus as I needed to use my 64gig msd card.
After a full wipe and restore Zeus started up but the dpi was messed up (160) I think (way small)
I was seeing loads of FC's and file manager showed my internal SD as being empty. Rebooted to recovery and tried the "Format Data" option
It failed right away with this message "E: Unable to format data."
I have tried flashing the stock .26 rom via TWRP and I have the same issue, dpi set to 160 and internal sd not mounted.
It seems my Internal sd is corrupt
What is the procedure to reformat it via ADB or fastboot? (I have searched but the results I found relate to other devices and I dont want to simply follow instructions that might cause further harm to my TF700)
I have followed the NVflash brick proof procedure and have all relevant files backed up (I did this before flashing the last 2 roms)
Please can some one point me in the right direction
Thanks a lot
Jules

I always wipe cache, system, internal, davic and then do a factory reset.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app

When you said that you tried to flash the stock .26 you meant installing not restoring a backup, right? What rom you have on your device right now?

Pretoriano80 said:
When you said that you tried to flash the stock .26 you meant installing not restoring a backup, right. What rom you have on your device right now?
Click to expand...
Click to collapse
Yip extracted the zip from the zip file and copied it to my ext sd and flashed it via TWRP
I have an unusable Zeus4,
Im about to try a full wipe again and then flash .26 again
EDIT
After flashing .26 and selecting reboot I get the "No OS installed! Are you sure you wish to reboot?" message

Looks like the system partition is corrupted, but i'm not sure. I think you should come here on IRC and maybe someone with more experience will help you - - http://webchat.freenode.net/?channels=asus-transformer

Thanks so much Pretoriano80!
With his help on IRC I was able to solve the problem,
In the end I had to return to complete stock, It seems CM10 caused some problems,
You are a a legend dude Thanks!!
:good:

ZaJules said:
Thanks so much Pretoriano80!
With his help on IRC I was able to solve the problem,
In the end I had to return to complete stock, It seems CM10 caused some problems,
You are a a legend dude Thanks!!
:good:
Click to expand...
Click to collapse
This same thing happened to me with my Prime when I was getting ready to send it off for RMA because of a broken HDMI port. Since I was unlocked I was advised to restore to stock before sending it in. However, before I got the chance to do that I started getting the "E: Unable to format data." error that you were. I ended up erasing all partitions from fastboot and putting a note in the box that it wouldn't boot after an OTA. I managed to get away with it and wasn't charged for fixing it
For future reference it would be really helpful to know how you fixed this. Did you do something like what is in this thread: http://forum.xda-developers.com/showthread.php?t=1803343.
Did you ever figure out how CM10 messed up your Infinity? I was running CM9 on my Prime when I got this error. Thanks!

It's hard to say if it was CM10 (or any other custom rom) or TWRP to mess the things up but we managed to get back to stock by replacing the twrp with CWM recovery and installing a modified .30 update package. Was a tricky one but we didn't had to mess with the partitions and that's good.

Pretoriano80 said:
It's hard to say if it was CM10 (or any other custom rom) or TWRP to mess the things up but we managed to get back to stock by replacing the twrp with CWM recovery and installing a modified .30 update package. Was a tricky one but we didn't had to mess with the partitions and that's good.
Click to expand...
Click to collapse
Why did you switch to CWM? Do you have any thoughts on the advantages and disadvantages of TWRP vs CWM?

paddycr said:
Why did you switch to CWM? Do you have any thoughts on the advantages and disadvantages of TWRP vs CWM?
Click to expand...
Click to collapse
Switched to CWM just to make sure it wasn't twrp recovery that somehow was failing to flash the partitions correctly. Tbh so far both do their job and both share the same limitation so far, meaning both fail to restore the boot partition (kernel) so in order to restore successfully (from a nandroid backup) you need to flash the right kernel after restoring is done. Otherwise i like TWRP better and never had issues with it, but i miss the advanced option from CWM, the one that let you format each partition individually.

Pretoriano80 said:
Switched to CWM just to make sure it wasn't twrp recovery that somehow was failing to flash the partitions correctly. Tbh so far both do their job and both share the same limitation so far, meaning both fail to restore the boot partition (kernel) so in order to restore successfully (from a nandroid backup) you need to flash the right kernel after restoring is done. Otherwise i like TWRP better and never had issues with it, but i miss the advanced option from CWM, the one that let you format each partition individually.
Click to expand...
Click to collapse
I'm not certain what you're referring to here. I've restored many times from different TWRP backups (for each custom rom that successfully boots and is half-decent, I make and keep a backup in case I want to jump around and try new things) and I've never had any issues. I am still on the .26 firmware update because I plan to do the nvflash thing. Are you saying that between Zeus v4 (ICS) and various Jelly Bean roms I've been on the same kernel? I gues I just haven't checked.
Anyway, I really love the TWRP recovery and use it with Xoom and Nexus 7 as well. It's so easy to use and always has been reliable.

okantomi said:
I'm not certain what you're referring to here. I've restored many times from different TWRP backups (for each custom rom that successfully boots and is half-decent, I make and keep a backup in case I want to jump around and try new things) and I've never had any issues. I am still on the .26 firmware update because I plan to do the nvflash thing. Are you saying that between Zeus v4 (ICS) and various Jelly Bean roms I've been on the same kernel? I gues I just haven't checked.
Anyway, I really love the TWRP recovery and use it with Xoom and Nexus 7 as well. It's so easy to use and always has been reliable.
Click to expand...
Click to collapse
For me moving between various roms by just restoring a backup never worked like it should. Let's say i'm on CM10 and i want to restore from a stock rom backup, the restore process is done, after reboot the device gets stuck to the first Asus screen and will stay there. Now if i get back to recovery and flash an update. zip containing the stock kernel the device will boot just fine, so definitely the boot image doesn't get restored in my case (with . 26 bootloader ).
Edit: @okantomi: You are using the internal storage or a MicroSD for backup / restoring? I'm really curious how this could work for some and not work for others, i mean same device, same recovery, same bootloader version...

Pretoriano80 said:
For me moving between various roms by just restoring a backup never worked like it should. Let's say i'm on CM10 and i want to restore from a stock rom backup, the restore process is done, after reboot the device gets stuck to the first Asus screen and will stay there. Now if i get back to recovery and flash an update. zip containing the stock kernel the device will boot just fine, so definitely the boot image doesn't get restored in my case (with . 26 bootloader ).
Edit: @okantomi: You are using the internal storage or a MicroSD for backup / restoring? I'm really curious how this could work for some and not work for others, i mean same device, same recovery, same bootloader version...
Click to expand...
Click to collapse
Ok, I only flash a new zip from the internal storage...made myself a "Flashworthy" folder which I keep stocked with newest versions of roms/gapps. I save my TWRP backups to my external microsdcard, as well as my TiBu backups. I have never had a problem restoring from TWRP this way, honestly.

okantomi said:
Ok, I only flash a new zip from the internal storage...made myself a "Flashworthy" folder which I keep stocked with newest versions of roms/gapps. I save my TWRP backups to my external microsdcard, as well as my TiBu backups. I have never had a problem restoring from TWRP this way, honestly.
Click to expand...
Click to collapse
Well, in this case i really have no clue why restoring works for some users but not for all.Dees_Troy, the dev behind Twrp recovery told me that .26 bootloader is to blame for the recovery failing to restore the boot partition, but looks like you have that bootloader version and restoring works good for you... interesting.

Pretoriano80 said:
Well, in this case i really have no clue why restoring works for some users but not for all.Dees_Troy, the dev behind Twrp recovery told me that .26 bootloader is to blame for the recovery failing to restore the boot partition, but looks like you have that bootloader version and restoring works good for you... interesting.
Click to expand...
Click to collapse
It is a mystery. Is there any other info that might be relevant to see why the difference in results? I ask because I would like to understand this device better, as well as potentially help others.

okantomi said:
It is a mystery. Is there any other info that might be relevant to see why the difference in results? I ask because I would like to understand this device better, as well as potentially help others.
Click to expand...
Click to collapse
I don't know, maybe the twrp version and the backup options, like if you are using compression or not, which partitions do you backup (boot, system, data, recovery, cache)...

Pretoriano80 said:
I don't know, maybe the twrp version and the backup options, like if you are using compression or not, which partitions do you backup (boot, system, data, recovery, cache)...
Click to expand...
Click to collapse
I'm using TWRP 2.2.2.1, I back up boot, system and data only, and I don't use compression.