Related
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.
my one s recently developed a strange issue, where if i try to run a nandroid backup, it will mostly finish, then reboot itself without fully completing the process, leaving me with a bunk backup and stuck on one rom for now. also, and the more important of my 2 concerns, is that i don't know if it will do this during a rom flash, nor do i want to find out, seeing as i have no current working backup. doe's anyone have any ideas as to how i could fix this?
mercenaryhmster said:
my one s recently developed a strange issue, where if i try to run a nandroid backup, it will mostly finish, then reboot itself without fully completing the process, leaving me with a bunk backup and stuck on one rom for now. also, and the more important of my 2 concerns, is that i don't know if it will do this during a rom flash, nor do i want to find out, seeing as i have no current working backup. doe's anyone have any ideas as to how i could fix this?
Click to expand...
Click to collapse
At a guess you got a high Hboot so that means when you restore its not restoring the boot.img. You need to flash that in fastboot.
Darknites said:
At a guess you got a high Hboot so that means when you restore its not restoring the boot.img. You need to flash that in fastboot.
Click to expand...
Click to collapse
nope, i have hboot 1.06, and either way that wouldn't, and shouldn't, cause a nandroid to fail during backup, nor for the phone to reboot by itself.
mercenaryhmster said:
nope, i have hboot 1.06, and either way that wouldn't, and shouldn't, cause a nandroid to fail during backup, nor for the phone to reboot by itself.
Click to expand...
Click to collapse
Oh if you mean you cant make a backup try a newer recovery or if its already up to date try an old one.
Edit, just to add I use TWRP 2.2.2.0 and it works fine.
Darknites said:
Oh if you mean you cant make a backup try a newer recovery or if its already up to date try an old one.
Edit, just to add I use TWRP 2.2.2.0 and it works fine.
Click to expand...
Click to collapse
tried using twrp 2.3, 2.2, cwm touch, regular cwm, does it on all of them.
mercenaryhmster said:
tried using twrp 2.3, 2.2, cwm touch, regular cwm, does it on all of them.
Click to expand...
Click to collapse
Not sure then sorry.
Do you have enough free space on your sdcard partition?
You can also try (un?)mounting /data and /system before you start the backup.
Just as an update, I solved my problem. It seems that there were some corrupted files on my data partition, and they were causing nandroid to fail and reboot randomly. So, since I was planning on wiping anyway, I wiped and set up viper again, and successfully made a nandroid after.
hi everyone,
i have just rooted my lava iris 454(ICS 4.0.4). i am very happy with my engineering (thanks to those members who helped me).
now before going to try custom ROM's i want to make a back up of company provided ROM.
SO, somebody please give me step by step instructions :
1) how can i backup my ROM.
2) After installing custom ROM how can i restore my backup ROM.
please somebody help me. i will be grateful.
aakashing said:
hi everyone,
i have just rooted my lava iris 454(ICS 4.0.4). i am very happy with my engineering (thanks to those members who helped me).
now before going to try custom ROM's i want to make a back up of company provided ROM.
SO, somebody please give me step by step instructions :
1) how can i backup my ROM.
2) After installing custom ROM how can i restore my backup ROM.
please somebody help me. i will be grateful.
Click to expand...
Click to collapse
You can install ROM Manager from PlayStore and use Clockworkmod to backup your ROM. Or you could also backup your rom by entering your device's recovery. You can trigger it by pressing a specific combination (Volume Up, Volume Down or both alternatively - depends on your device) of buttons while the device is switching on.
You can find elaborate explanations here: http://forum.xda-developers.com/showthread.php?t=1587607
Hope I helped.
In a nutshell, what you are looking for is called a making nandroid backup. There are many programs which can accomplish this. My favorite is 4EXT recovery, which you can download from the play store. It does require you have root to install 4EXT! After you have a program such as 4EXT or ClockworkMod which can make nandroid backups, then you can save them and restore them in the future. This is how you can return your phone to the exact way it was when you make the backup.
thank you for advising me 4EXT recovery and ROM Manager.
What about titanium backup?
i made a backup(i hope so) by Titanium backup, by selecting the option "Backup all user apps and system data".
my questions are:
1) is that enough for back up?
2) how can i restore it after installing a new rom?
3) in between the process of installing if my phone become dead or blank how it will possible to access titanium backup?
oh its so much complicated. plz any developer help me.
thanks in advance.
installed ROM Manager Premium v5.0.2.7
if select
1) "Flash CWM Recovery"
asks to confirm ph model-> select iris 454 -> says "it does not have an official supported CWM yet. Have u installed a cwm based recovery manually?" -> if i select "yes," 2 option comes for confirm version cmw 2.x and cmw 3.x -> after selecting one of those nothing happen.
2) Backup current ROM
displays "new backup name..." -> if i click OK the system reboot. -> in reboot process an android symbol comes and suddenly it lay down like a wounded man. -> system hangs ->only removing battery makes it solve.
Yes, that's enough backup. You have backed up all your system data and applications. So you can restore your phone's last known working state.
After installing a new ROM, you can download Titanium Backup from PlayStore and use it to restore everything.
Note: Some ROM's don't have PlayStore available in their package in which case you'd have to download the gapps package separately and flash it too while flashing the ROM.
You cannot use Titanium Backup if your phone doesn't come alive. You'd have to restore the stock ROM or flash some other known-to-be-working ROM. You can then restore your stuff.
Sent from my LiveWithWalkman
I've never used a nandroid backup, I usually do a backup with go backup (sms,phone log,wifi passwords and apps with preferences) which is an easy and intuitive app. If something fails i have a tested rom which i flash before do anything else.
Why it's better to do a nandroid backup and not just this??
Voldizard said:
Yes, that's enough backup. You have backed up all your system data and applications. So you can restore your phone's last known working state.
After installing a new ROM, you can download Titanium Backup from PlayStore and use it to restore everything.
Note: Some ROM's don't have PlayStore available in their package in which case you'd have to download the gapps package separately and flash it too while flashing the ROM.
You cannot use Titanium Backup if your phone doesn't come alive. You'd have to restore the stock ROM or flash some other known-to-be-working ROM. You can then restore your stuff.
Sent from my LiveWithWalkman
Click to expand...
Click to collapse
thnx dear.
titanium backup is enough for me.
but now what about" if your phone doesn't come alive"? how should i restore the stock ROM if it is unavailable?
can i make stock rom or make a back up of stock rom? how?
Sewrizer said:
this means that your device is not supported by CWM recovery so there is not much to do, unless your stock recovery can perform the same tasks as CWM. for instance sgs2 recovery mode only allows you to install zip and to wipe cache and factory reset.
On the other hand there is a risky method you may try but i am not sure whether it would work. Install odin on your PC or mobile odin on your device and look for a kernel which has CWM recovery in it. THIS IS A RISKY OPERATION SO THINK BEFORE YOU DO THIS. I'm saying this because i bricked my sgs2 and the only way i could make it work was to restore, but again, you need CWM to restore. good luck.
hit thanks if i helped or reply/ send me a PM if you need further details.
Click to expand...
Click to collapse
"for instance sgs2 recovery mode only allows you to install zip and to wipe cache and factory reset"
unable to understand this.
i want to try with other rom (because custom rom unavailable for my device); if it fails how should i make alive my phone?
is it possible to recover the company provided rom?
plz response.
thanks in adv.
aakashing said:
thnx dear.
titanium backup is enough for me.
but now what about" if your phone doesn't come alive"? how should i restore the stock ROM if it is unavailable?
can i make stock rom or make a back up of stock rom? how?
Click to expand...
Click to collapse
You can find the entire procedure for backing up your Stock ROM here: http://androidadvices.com/backup-stock-rom-clockworkmod-rom-manager/
In order to restore Stock ROM, turn off your phone, boot your phone into recovery and use the restore option in the screen you see.
Sewrizer said:
Can you put your phone in recovery mode? I if so, take a picture of it and post it in a reply.
Sent from Area 51 using my Samsung Galaxy i9100p
Click to expand...
Click to collapse
when i press power+ vol down key in booting time it displays Factory mode.
Under this heading the sub menus come like this (i dont know whether it is recovery mode or not.)
Full test
Item test
Test Report
Clear eMMC
Version
Reboot
is it enough info? otherwise ill shoot a photo.
plz make some way-out bro.
it sounds like you need to flash a custom recovery on your thing first
tsomclovin said:
it sounds like you need to flash a custom recovery on your thing first
Click to expand...
Click to collapse
whats that man?
whats d process?
i badly need to solve that.
thanks in advance.
I made a backup with the stock "android recovery 3e". Anyway to extract it? It's a ".backup" file and I can't open it whatever i try. It's not a nandroid backup, but with an "backup" extension. I've been searching for three days now and so far haven't found anything. There were some other threads with the same topic too but no solution was posted. Any help would be greatly appreciated, thanks.
How big is the file?
orangekid said:
How big is the file?
Click to expand...
Click to collapse
It's about 3gb.
Blufloyd said:
It's about 3gb.
Click to expand...
Click to collapse
Can you use the same recovery to restore this nandroid file or is that not an option?
I am not finding anything on actually extracting it..
orangekid said:
Can you use the same recovery to restore this nandroid file or is that not an option?
I am not finding anything on actually extracting it..
Click to expand...
Click to collapse
It's not a nandroid file. I can restore it but it's not much of a help cause I forgot my lock pattern with wifi and data off. Debugging was not enabled and it's a new phone didn't even root it yet. I thought i'll just backup everything, factory reset and then extract my data from the backup file.
Now back to the point, i know there doesn't seem to be any way to extract it. Never made a backup with the stock android recovery before. I just needed to recover some imp photographs. Xda was my last resort lol.
Blufloyd said:
It's not a nandroid file. I can restore it but it's not much of a help cause I forgot my lock pattern with wifi and data off. Debugging was not enabled and it's a new phone didn't even root it yet. I thought i'll just backup everything, factory reset and then extract my data from the backup file.
Now back to the point, i know there doesn't seem to be any way to extract it. Never made a backup with the stock android recovery before. I just needed to recover some imp photographs. Xda was my last resort lol.
Click to expand...
Click to collapse
Is there any way at all to root it once you restore it? If it's a full system backup then it's a "nandroid" (which means a ROM backup whether stock or custom).
But yeah can't seem to find any way to extract it, only hope is to restore it and try to do something with the ROM.
orangekid said:
Is there any way at all to root it once you restore it? If it's a full system backup then it's a "nandroid" (which means a ROM backup whether stock or custom).
But yeah can't seem to find any way to extract it, only hope is to restore it and try to do something with the ROM.
Click to expand...
Click to collapse
Idk, aren't nandroid files .tar or .zip? I was thinking of doing that. But i had some doubts. Like will the custom recovery be able to restore this file? Because I'm pretty sure i've never seen a .backup file in cwm or twrp.
Blufloyd said:
Idk, aren't nandroid files .tar or .zip? I was thinking of doing that. But i had some doubts. Like will the custom recovery be able to restore this file? Because I'm pretty sure i've never seen a .backup file in cwm or twrp.
Click to expand...
Click to collapse
"nandroid" just means a ROM backup, doesn't matter which recovery or what the extension is.
I mean anything is worth a try at this point. I doubt any recovery will recognize it, but I am thinking use the recovery that made the file to restore it, THEN root that ROM if you can somehow. What phone do you have? Most older Samsung phones can be rooted in Odin regardless of the actual ROM state etc...
edit: moved to Android Q&A forum too...
orangekid said:
"nandroid" just means a ROM backup, doesn't matter which recovery or what the extension is.
I mean anything is worth a try at this point. I doubt any recovery will recognize it, but I am thinking use the recovery that made the file to restore it, THEN root that ROM if you can somehow. What phone do you have? Most older Samsung phones can be rooted in Odin regardless of the actual ROM state etc...
edit: moved to Android Q&A forum too...
Click to expand...
Click to collapse
No I can't root it after restoring. I'm locked out and there's nothing I can do about it. It's HTC desire 816g.
Hi everyone,
I'm a noob to the OPO and also a bit of a noob to backing up and restoring individual partitions, although I have some experience with flashing the Nexus 5 and Z3C with B2GOS and /e/.
I'd like to put Ubuntu Touch on my OPO. I'd like to make sure I can return the phone to stock afterwards, if needed (e.g., I want to sell it as stock). I was thinking of taking partition images with TWRP first, will this be sufficient? I see there's a tool for backing up the EFS as well, so I suppose I should do that.
Or maybe I need to do nothing! Will it be sufficient just to reflash stock firmware when I want to return to stock? If a combination of both flashing stock firmware and TWRP images, EFS backup, what order does it need to be done in?
Thanks for your help in advance.
Cheers
madb1lly said:
Hi everyone,
I'm a noob to the OPO and also a bit of a noob to backing up and restoring individual partitions, although I have some experience with flashing the Nexus 5 and Z3C with B2GOS and /e/.
I'd like to put Ubuntu Touch on my OPO. I'd like to make sure I can return the phone to stock afterwards, if needed (e.g., I want to sell it as stock). I was thinking of taking partition images with TWRP first, will this be sufficient? I see there's a tool for backing up the EFS as well, so I suppose I should do that.
Or maybe I need to do nothing! Will it be sufficient just to reflash stock firmware when I want to return to stock? If a combination of both flashing stock firmware and TWRP images, EFS backup, what order does it need to be done in?
Thanks for your help in advance.
Cheers
Click to expand...
Click to collapse
Hi,
I don't have much time at the moment. I tested Ubuntu Touch just a few weeks ago. Some (not all) bacon users have broken Wlan. I'm one of them. Because of that I went back to Android. So it's possible.
It was a bit tricky. Of course I recommend a full nandroid backup. Copy it to a save place (for example your PC). Don't change any partitions on your phone during installation.
To go back (if I'm remembering wright):
- flash latest recovery via fastboot
- reboot in recovery (for me it was still the Ubuntu recovery)
- anywhere there was an option to boot Android
- take this option and you will reboot in the Android recovery
- there you can restore your previous backup
Hope I could help. If you try Ubuntu Touch, please report, of Wlan works for you.
Good luck. And add said: I don't really remember the whole procedure, so at your own risk.
Hi!
Gaukler_Faun said:
Hi,
I don't have much time at the moment. I tested Ubuntu Touch just a few weeks ago. Some (not all) bacon users have broken Wlan. I'm one of them. Because of that I went back to Android. So it's possible.
It was a bit tricky. Of course I recommend a full nandroid backup. Copy it to a save place (for example your PC). Don't change any partitions on your phone during installation.
To go back (if I'm remembering wright):
- flash latest recovery via fastboot
- reboot in recovery (for me it was still the Ubuntu recovery)
- anywhere there was an option to boot Android
- take this option and you will reboot in the Android recovery
- there you can restore your previous backup
Hope I could help. If you try Ubuntu Touch, please report, of Wlan works for you.
Good luck. And add said: I don't really remember the whole procedure, so at your own risk.
Click to expand...
Click to collapse
Thanks for the tip about WLAN, I didn't know about that. If I have any issues I'll post here and in the UBPorts forum.
Okay, a full Nandroid backup I can do. But don't I have to flash TWRP to the recovery partition to do that? If so, do I need to backup the recovery partition somehow first?
Thanks
madb1lly said:
Hi!
Thanks for the tip about WLAN, I didn't know about that. If I have any issues I'll post here and in the UBPorts forum.
Okay, a full Nandroid backup I can do. But don't I have to flash TWRP to the recovery partition to do that? If so, do I need to backup the recovery partition somehow first?
Thanks
Click to expand...
Click to collapse
No, I don't think you need. It would be good to have the original recovery file... But I never backed up my original recoveries. One of the first things I make with a new phone is flashing twrp. So I would just download the latest image for Bacon and flash it via fastboot.
I recommend to back up your personal data (pictures, documents, ...) ton tour PC. Who knows.
Gaukler_Faun said:
No, I don't think you need. It would be good to have the original recovery file... But I never backed up my original recoveries. One of the first things I make with a new phone is flashing twrp. So I would just download the latest image for Bacon and flash it via fastboot.
I recommend to back up your personal data (pictures, documents, ...) ton tour PC. Who knows.
Click to expand...
Click to collapse
Thanks, that's helpful. I don't actually know how to backup the recovery partition other than using root access and presumably some ADB command, so if it's not needed then that's good news. I will of course backup my data first, but a reminder is always a good thing!
Cheers