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.
I always have used clockwork mod to flash roms and backup and restore my roms so I have a fair amount of backups and my stock rooted back up also is on clockwork mod. I wanted to see if i liked TWRP recovery so I flashed it and used it a little bit made one back up of king kang rom and then went back to clockwork mod. After I did that I tried to use clockwork again and all of my backups which I had made will not restore. Some of them have the message "md5 mismatch" others say "error restoring system" and other say "error restoring data". before this happened i had never had a single problem restoring any of my backups and I have at least 10 backups of mostly different roms which I have restored successfully before. I'm just trying to find out if there's a solution to my problem to get my backups to restore again. Appreciate any and all advice or suggestions.
I know if you rename the backups that will cause the md5 error. Maybe you should try deleting the twrp backup and any files or folders that go with twrp. Not sure if this will do the trick but its worth a shot. Hope you figure it out good luck.
I have a i747M GS3 and I wiped the internal storage. I am using twrp and made a backup. When trying to restore the backup, it does so successfully, but will not boot (goes straight to download mode). I tried using the adb sideload mode in twrp but that fails. Also tried mounting the sd card from the mount section of twrp but the phone does not come up on the computer. Essentially there are no files on the internal storage, besides a TWRP folder which I assume was auto-created when it tried to restore the backup. I have ROM files on my external card but when trying to flash those I get a "unable to open .zip" error. At this point I cannot do anything with the phone. Any help would be appreciated.
Using TWRP 2.6.0.0 and trying to flash an AOSP 4.2.2 ROM, and also tried a 4.1.2 TW ROM just to make sure.
Thanks.
nicthemartian said:
I have a i747M GS3 and I wiped the internal storage. I am using twrp and made a backup. When trying to restore the backup, it does so successfully, but will not boot (goes straight to download mode). I tried using the adb sideload mode in twrp but that fails. Also tried mounting the sd card from the mount section of twrp but the phone does not come up on the computer. Essentially there are no files on the internal storage, besides a TWRP folder which I assume was auto-created when it tried to restore the backup. I have ROM files on my external card but when trying to flash those I get a "unable to open .zip" error. At this point I cannot do anything with the phone. Any help would be appreciated.
Using TWRP 2.6.0.0 and trying to flash an AOSP 4.2.2 ROM, and also tried a 4.1.2 TW ROM just to make sure.
Thanks.
Click to expand...
Click to collapse
if its connecting in download mode
u should flash stock rom via odin.
if u don't knw how to then reply!
Thanks
prantoroy said:
if its connecting in download mode
u should flash stock rom via odin.
if u don't knw how to then reply!
Click to expand...
Click to collapse
That is exactly what I did. I got it back to a point where it is functioning but unfortunately the ROM backup (the one made with teamwin) just will not restore. I am trying to see if I can get the cwm backup I made restored. Otherwise I will just have to start from scratch with the ROM I had before (Illusion 2.1 beta - awesome btw). Thanks for the speedy reply
nicthemartian said:
That is exactly what I did. I got it back to a point where it is functioning but unfortunately the ROM backup (the one made with teamwin) just will not restore. I am trying to see if I can get the cwm backup I made restored. Otherwise I will just have to start from scratch with the ROM I had before (Illusion 2.1 beta - awesome btw). Thanks for the speedy reply
Click to expand...
Click to collapse
you should do it!
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!
Hey there guys, im having trouble restoring my Rom backups through twrp recovery since im on cm 12.1 i had done nandroid backups of my stock and cm12 Roms. The other day i tried going back to previous rom but when i go to twrp/ restore option...there is nothing even though i have the backup folders in my external sd. I tried moving the folders to internal storage also to check if it shows in twrp but nothing there....what do i do, help me cuz this is essential for changing Roms and stuff.
Well I think I got the reason behind it. When the system partition is wiped, the backup that is created before the system being wiped is not read. I tried it my self, I flashed cm 12.1 doing it fail proof method (wiping cache/dalvik/data and SYSTEM partitions)and before flashing the ROM I did a nandroid back up which when I went in the restore option in twrp was there before flashing the ROM . once I flashed the ROM, after everything gets booted and all I go to twrp, even though I have the backup folders I just doesn't show in twrp restore. That's what I've figured. Is this really the reason or there's something else being it.....?
Sent from my SM-N9005 using XDA Free mobile app