Database Info

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.

DEV help, or experienced tweakers (MIUI, CleanROM)

Trying various ROMs before i decide on one to get settled in to.
1. MIUI 2012.09.14
- flashed ok, rebooted, stuck on startup animation doesnt boot.
(downloading 2012.09.29)
2. CleanROM
- flashed ok, rebooted ok, error; "com.android.phone has stopped working" before i get past lock screen.
This happens another 2 - 4 times while im trying to get thru phone setup.
Before eventually it boots back to startup animation, and repeats the process.
3. CNA
- flashed ok, rebooted ok, loaded semi ok before multiple errors;
Unfortunately phone has stopped.
Messaging has stopped.
System UI has stopped working.
Any ideas? I was kinda keen to see all of of these ROMs operate.

Wobzy said:
Trying various ROMs before i decide on one to get settled in to.
1. MIUI 2012.09.14
- flashed ok, rebooted, stuck on startup animation doesnt boot.
(downloading 2012.09.29)
2. CleanROM
- flashed ok, rebooted ok, error; "com.android.phone has stopped working" before i get past lock screen.
This happens another 2 - 4 times while im trying to get thru phone setup.
Before eventually it boots back to startup animation, and repeats the process.
3. CNA
- flashed ok, rebooted ok, loaded semi ok before multiple errors;
Unfortunately phone has stopped.
Messaging has stopped.
System UI has stopped working.
Any ideas? I was kinda keen to see all of of these ROMs operate.
Click to expand...
Click to collapse
1) you must be on newer hboot and need to flash boot.IMG via fast boot manually.
2) you need to do a factory data reset then reflash.
3) Same as number 2.
Sent from my One X using xda app-developers app

h8rift said:
1) you must be on newer hboot and need to flash boot.IMG via fast boot manually.
2) you need to do a factory data reset then reflash.
3) Same as number 2.
Click to expand...
Click to collapse
Cheers bud, awesome.
The steps only said wipe, and someone had told me factory reset only works on stock ROM?
Incorrect?
And forgive my ignorance, hboot?

Ok heres where im at;
- reset to bootloader
- factory reset
- booted to twrp
- wipe system (not sdcard)
- install (no roms, no backup of stock - sdcard is wiped)
kinda panicked a little.
- mounted as usb
- copied roms from laptop back to sdcard
- install (still no roms)
getting more panicked.
- create partition intending to copy roms over again
- roms mysteriously just appear on sdcard after partition created
- installed cna, had one error of unfortunately system ui has stopped working, but no reoccurence.

Never factory reset or clear storage or any of that in hboot. You were supposed to factory reset in twrp. Factory reset in twrp clears data,cache,dalvik it does not wipe your storage.

All of those must of been dirty flashes ...just USB mount in twrp. And copy a rom over

DvineLord said:
Never factory reset or clear storage or any of that in hboot. You were supposed to factory reset in twrp. Factory reset in twrp clears data,cache,dalvik it does not wipe your storage.
Click to expand...
Click to collapse
****. Thanks.
The partition i created to backup and hold roms was 2gb.
In file manager & when mounted as usb i can see the files i copied over as well as the standard sdcard folders.
But i cant see any evidence of a partition.
Only when i check my available space my total sdcard is now 24gb.
Can u help me understand also how i couldnt see the copied files until i created the partition in recovery?

I did some bootloader wipes and recovery wipes, ended up messing up storage bad. Had to ruu in the end.

DvineLord said:
I did some bootloader wipes and recovery wipes, ended up messing up storage bad. Had to ruu in the end.
Click to expand...
Click to collapse
Ok i searched and downloaded the RUU based on my hboot info;
- RUU Evita UL Telstra WWE 1.89. 841.9 Radio 0.18c.32.09.01 10.9 3a.32.20L release 266699 signed .exe
Just in case i've left anything out or anyone wants to jump in, this is the story;
Brand new stock Telstra HTC One XL (Australia)
Unlocked & rooted, TWRP recovery.
Backed up stock.
Installed a few different ROMs before deciding on one.
Accidentally reset factory from hboot instead of twrp.
Lost stock ROM back up.
Mounted USB & copied custom ROMs back across to sdcard.
Files did not appear on sdcard.
Decided to partition and try again.
On sucessful partition, suddenly all files became visible, despite partition warning "all files will be deleted"
Flashed Viper XL successfully.
SDcard total storage reading as 24gb (32gb stock)
1. if i have done anything to reduce my available storage i want to get it back.
2. id like to go back to stock rom and basically start from scratch with clean stock backup and clean storage.
I found a link to the ATT One X stock rom on the US HTC support site.
I cant find anything similar on the AU site for the One XL.
On the xda thread the link was located on, i read that i have to re-lock my bootloader, thats fine theres a tutoriall, but i need to find the stock rom.
That tutorial however didnt mention anything about RUU.
Will ruu enable me to do this internally?
Thanks in advance.

All sorted, RUU is at 15% thx for the help.

There is a 1.89 being hosted in the football ruu collection and other places if you havent found it already, dont run the at&t 2.20 ruu.

[Q] CWM didn't restore, stuck at splash

Hi,
So I used the Revolutionary method to s-off and root my phone - this was successful. I then made a full backup using Titanium and a few other things like SMS and contact backups, which are on my laptop now.
I then installed SVHD v1.7.4 using Clockworkmod v4.0.1.4. It ran fine, but try as I might I couldn't load my contacts and SMS back into it. So I tried to restore is back to the stock rom by going into Clockwork's Recovery, wiping cache, data and system.
When I tried to restore to a previous point, it gave me an error message saying system.img, data.img and so on not found, so all restore has been skipped. Now I'm stuck at the 3 splash screen. I can still get into the bootloader though, and can potentially install SVHD again as it's still on the SD card.
A quick search through the forums shows users with similar problems from 2012, but I'm afraid of buggering up my phone further so I'm hoping someone could be so kind as to walk me through what I need to do.

xTheLostProphetx said:
Hi,
So I used the Revolutionary method to s-off and root my phone - this was successful. I then made a full backup using Titanium and a few other things like SMS and contact backups, which are on my laptop now.
I then installed SVHD v1.7.4 using Clockworkmod v4.0.1.4. It ran fine, but try as I might I couldn't load my contacts and SMS back into it. So I tried to restore is back to the stock rom by going into Clockwork's Recovery, wiping cache, data and system.
When I tried to restore to a previous point, it gave me an error message saying system.img, data.img and so on not found, so all restore has been skipped. Now I'm stuck at the 3 splash screen. I can still get into the bootloader though.
A quick search through the forums shows users with similar problems from 2012, but I'm afraid of buggering up my phone further so I'm hoping someone could be so kind as to walk me through what I need to do.
Click to expand...
Click to collapse
Have you make a nandroid backup
in recovery?- sorry i didn`t see it mentioned,...
if you haven`t, then there is nothing to restore...
system ( the whole nand image ) could only be restored,
when it was previously been written...
try to mount sd card- while in recovery,
and look for: Clockworkmod/backups/.....
if there is nothing, i`m afraid you`re ......

asgardr said:
Have you make a nandroid backup
in recovery?- sorry i didn`t see it mentioned,...
if you haven`t, then there is nothing to restore...
system ( the whole nand image ) could only be restored,
when it was previously been written...
try to mount sd card- while in recovery,
and look for: Clockworkmod/backups/.....
if there is nothing, i`m afraid you`re ......
Click to expand...
Click to collapse
Ah sorry, I forgot to mention. Yes, I have two backups in CWM. Neither of which seem to work.

xTheLostProphetx said:
Ah sorry, I forgot to mention. Yes, I have two backups in CWM. Neither of which seem to work.
Click to expand...
Click to collapse
have you been changing recovery version lattely?
what i mean is: if you have, then try to revert back
to the version you used to create nandroid with,
and if you haven`t, then try to grab 4ext recovery-
possibly newest release you can put your hands on,
and try to restore nandroid from there...
...there is also a tool called:
< CWM2update.zip.creator > by @ss429842,
that may partly be a cure for your trouble- perhaps....

asgardr said:
have you been changing recovery version lattely?
what i mean is: if you have, then try to revert back
to the version you used to create nandroid with,
and if you haven`t, then try to grab 4ext recovery-
possibly newest release you can put your hands on,
and try to restore nandroid from there...
...there is also a tool called:
< CWM2update.zip.creator > by @ss429842,
that may partly be a cure for your trouble- perhaps....
Click to expand...
Click to collapse
I don't think I've changed the recovery version, no. But I clearly did something very wrong. I couldn't access my SD card as it's internal and I was afraid I was stuck.
What I've done instead is find the SVHD zip file and installed that. Hopefully this will work and I can at least turn my phone on and proceed from there. It sucks being a noob!

TF 300T Partitions

Hey there!
I'm hoping that someone can help me out. My nephew who's a wanna-be geek was going to update my ROM (which didn't to be done really, but he wanted to show me what he was able to do). He went and downloaded the latest CM 11, rebooted and went into TWRP 2.7.0.1, did a factory reset, an advanced wipe, and did the Format Data. When he did that, it got stuck in a loop. Nothing happened. He tried to install the ROM he downloaded, and NOTHING! Long story short, by him doing the Format Data, he wiped out my partitions. TWRP, no matter what I try to do tells me it's unable to mount 'data' or 'media' etc. etc. Which is leading me to believe I have no partitions left. I've tried installing the latest update from Asus, and no dice. I've tried restoring backups that I have on my micro SD, and that's not working.
Can someone please help me and tell me how to fix this? Can I get my partitions back? I'm really hoping that I don't have to send this tablet off to Asus in Dallas, TX to have it repaired.
I'm using a loaner tablet from a rental store, hoping I can get my TF 300 fixed.
Any help is deeply and sincerely appreciated.
Omega
Sent from my SM-P600 using Tapatalk

I was about to suggest you look in the correct forum, but I see you posted there as well. Anyway, your partitions are probably okay, they have just been wiped out, that doesn't mean you lost them. Have you tried reflashing the recovery? Were you able to flash anything with said recovery before that? Wiping the partitions in the recovery shouldn't have any effect on the flashing functionality, no matter which partitions were selected (except for sdcard, since that's where the ZIPs are stored), so there might be a problem with the recovery itself. Are you sure you have the correct one for your device?

Duchman said:
I was about to suggest you look in the correct forum, but I see you posted there as well. Anyway, your partitions are probably okay, they have just been wiped out, that doesn't mean you lost them. Have you tried reflashing the recovery? Were you able to flash anything with said recovery before that? Wiping the partitions in the recovery shouldn't have any effect on the flashing functionality, no matter which partitions were selected (except for sdcard, since that's where the ZIPs are stored), so there might be a problem with the recovery itself. Are you sure you have the correct one for your device?
Click to expand...
Click to collapse
Hey there Duchman ...
Thanks for your reply. I have tried reflashing the recovery like you suggested. And after that tried to reinstall CM11.Afterwards reflashing the recovery it says “Unable to mount data." I don't know if I need to flash a more recent version of TWRP, if that would even help.
Before all of this happened I could flash almost any ROM of my choice as long as it was KitKat supported. All of my backups and restores are kept on my micro SD so they aren't accidentally deleted. As far as I know it's the correct version of TWRP. It's worked for me so far, ever since I updated to KitKat.
Sent from my SM-P600 using Tapatalk

Omega Recon said:
Hey there Duchman ...
Thanks for your reply. I have tried reflashing the recovery like you suggested. And after that tried to reinstall CM11.Afterwards reflashing the recovery it says “Unable to mount data." I don't know if I need to flash a more recent version of TWRP, if that would even help.
Before all of this happened I could flash almost any ROM of my choice as long as it was KitKat supported. All of my backups and restores are kept on my micro SD so they aren't accidentally deleted. As far as I know it's the correct version of TWRP. It's worked for me so far, ever since I updated to KitKat.
Sent from my SM-P600 using Tapatalk
Click to expand...
Click to collapse
You could try flashing a newer recovery first, I think 2.7.1.0 is available for your device. Also try doing a hard reset by cold booting - here's a how-to: https://www.youtube.com/watch?v=oTU38Ewh8qo (wipe the cache afterwards)
If that doesn't help, reverting to stock is probably your best option. Try this: http://forum.xda-developers.com/showthread.php?t=1757077 (be sure to grab the correct firmware and back up your files)
Have you tried installing any other custom ROM? Does it give you the same error when you try to restore your backup?

Here's what I've come across so far. I did the reset, and that did nothing.
Tried to flash the stock version, after a few seconds, TWRP popped up with FAILED.
I've tried flashing Omni ROM. It will flash, load up, and gets stuck at the boot screen or boot animation. This happens with just about every ROM I try to flash.
Been looking for TWRP 2.7.1.0. I'm not seeing it listed on TWRPs site. Where can I get a copy? Thanks!
Sent from my SM-P600 using Tapatalk

Here you go: http://forum.xda-developers.com/showthread.php?t=2772093
Also do try flashing another recovery, PhilZ for instance: http://forum.xda-developers.com/showthread.php?t=2597860
Did you try wiping all of the partitions again?

Can't revert back to install normal ROMs after trying to flash Metallic ROM

Please Help
I was in miui ROM then I tried flashing Metallium ROM, after I flashed it, it booted up but, it wasn't restoring my previous apps, so I skip that part, but then when I got to the home screen I wasn't able to access my stuffs in my phone memory.
So I thought maybe I need to change the data to f2fs, so I went to the recovery and did and flashed the Metallic ROM again, but this time it didn't boot at all, there was a bootloop and I could get past the start up screen.
I tried my older ROMs the one that I had, but it's all giving me the same response now, I have switch before but I never have had this problem. Please help, how do I flash other lollipop ROM again.

Maybe changing to f2fs and doing a factory reset. If that doesn't help, flash stock ROM via fastboot.

kennylrmsailo said:
Please Help
I was in miui ROM then I tried flashing Metallium ROM, after I flashed it, it booted up but, it wasn't restoring my previous apps, so I skip that part, but then when I got to the home screen I wasn't able to access my stuffs in my phone memory.
So I thought maybe I need to change the data to f2fs, so I went to the recovery and did and flashed the Metallic ROM again, but this time it didn't boot at all, there was a bootloop and I could get past the start up screen.
I tried my older ROMs the one that I had, but it's all giving me the same response now, I have switch before but I never have had this problem. Please help, how do I flash other lollipop ROM again.
Click to expand...
Click to collapse
Anyone out there? Need help desperately.
Anyone?

samuelcr93 said:
Maybe changing to f2fs and doing a factory reset. If that doesn't help, flash stock ROM via fastboot.
Click to expand...
Click to collapse
Yeah that might work but I'm kinda looking for a solution where I don't have to flash the stock again because I lost all my moto g stuffs some months back.
And another thing is that when I flash MIUI its working fine again and I'm able to access all the file in my phone storage also. Any suggestions?

Mmmm if you are using TWRP you could connect the phone to the PC and make a backup while you are in recover mode. Then format again data partition to f2fs and make a factory reset including internal storage and finally flash your ROM and restore your files.
But if that is not working then the only option is flashing Stock ROM
If MIUI is still booting it means that your data partition is still ext4