Database Info

[Q] RomManager issues with N1: soft-bricking when creating backup

Hello all,
I have successfully installed CM7 on my Nexus One. However, I have the following problem with CWM: if I ask it to make a backup from within the recovery or from RomManager, CWM (3.0.0.5, latest version available apparently for Nexus One) makes the backup, but after restarting, I am stuck on the CM7 splashscreen: I see the blue Android on his skateboard and the arrow goes around in circles (left it going for 15 minutes just to be sure).
Also, on a sidenote, when I made the initial nandroid backup in CWM from my stock Froyo, after the backup was done I had to go in RomManager and "fix permissions", because all my resident apps kept crashing with "forced close" errors. No idea where that came from. Restoring that backup did the same thing as well. I did not investigate that issue any more though as I was on my way to a CM7 upgrade anyways.
So I now have a perfectly good install of CM7 running, but I am scared of doing a CWM backup. This is far from an ideal situation, and I would love to be able to resolve this
Thanks for any help

Anyone? I really am quite upset with this situation

Use this instead?
http://forum.xda-developers.com/showthread.php?t=611829

Thanks, I will try it... though I have to admit I am nervous at the idea of having to again reinstall everything. Crossing my fingers!

yannack said:
Thanks, I will try it... though I have to admit I am nervous at the idea of having to again reinstall everything. Crossing my fingers!
Click to expand...
Click to collapse
Uh oh? It is just a custom recovery, no need to reinstall everything. You only flash the recovery and do the backup you cannot now with the broken CWM. (For my phone, there are even flashable zip files so you can switch b/w CWM and AmonRA "on the fly" via flash zip from recovery, not sure there are some for N1, try to search. )

Actually, the current problem I have is that after performing a backup, my phone doesn't boot anymore. The only solution I have at that point is to re-flash a complete ROM (flashing the backup doesn't work either), thus losing everything.
In short: making a backup means I then have to format and said backup is unworkable...
Which is why I am nervous at the idea of trying to make such a backup.
On a sidenote, RomManager is indeed able to flash both CWM and RA recoveries for N1 directly, which is quite nice indeed.

yannack said:
Actually, the current problem I have is that after performing a backup, my phone doesn't boot anymore. The only solution I have at that point is to re-flash a complete ROM (flashing the backup doesn't work either), thus losing everything.
In short: making a backup means I then have to format and said backup is unworkable...
Click to expand...
Click to collapse
I still do not understand why all this. Just flash a working recovery from fastboot (should press power and trackball IIRC on your phone). (And obviously do not use CWM to perform backups when it bricks your phone.)
On another note, flashing removery via ROM Manager resulted in bricked phones for many users, would avoid it personally.

Restore TWRP Backup?

Hi, just have a quick question that's been bugging me for a while now. If I have made a full backup using TWRP and I want to restore it, should I:
Fully wipe system and caches and then restore; or just restore right over my current ROM?

****, good question
Sent from my HTC One X using xda app-developers app

Restore takes care of wiping for you.

Piggybacking off the OP, sometimes when I try to restore my TWRP backup it fails, and then the only way I've found to get it working again is to do a boot loader factory reset, and then essentially start from scratch or load an older working backup. No problem, just a minor annoyance. Is there something I'm doing wrong or any advice someone can give me?
Sent from my HTC One X using xda app-developers app

Hydromea said:
Hi, just have a quick question that's been bugging me for a while now. If I have made a full backup using TWRP and I want to restore it, should I:
Fully wipe system and caches and then restore; or just restore right over my current ROM?
Click to expand...
Click to collapse
I always wipe everything before a restore, just in case
Better safe than sorry

Restoring a back up !
When restoring a back up from any recovery wipe everything just as if you were installing a new rom. Factory reset, cache, dalvik cache, system just to be safe. Factory reset wipes data and all cache but not system and if you do a factory reset and then try to wipe I think dalvik again you get an error but no harm done it just will not do it again. I usually do them all and then do the superwipe zip and that willl give you a good piece of mind that it is properly wiped. Also, I have noticed that using the external sd card seems to work best for installing roms or backing up and restoring back ups or anything else like mods or themes. Here is the superwipe zip in case anyone needs it.

Hydromea said:
Hi, just have a quick question that's been bugging me for a while now. If I have made a full backup using TWRP and I want to restore it, should I:
Fully wipe system and caches and then restore; or just restore right over my current ROM?
Click to expand...
Click to collapse
I've done both, but I like not having reinstall all my apps, and reset all my ringtone, and that goes with a full wipe. so when ever i can i flash over. Just make sure your slashing the same rom over the old one.

You shouldn't worry about losing ANYTHING on a backup when you do a factory reset, because the backup houses all of the data and settings anyway.
All you do is Factory Reset, Nandroid>Restore, and your old backup will flash everything the way it was when you did a backup in the first place. Factory Reset is always wise, especially when you're fiddling with different ROM's based on different kernels or systems (AOSP/Sense).

XNine said:
You shouldn't worry about losing ANYTHING on a backup when you do a factory reset, because the backup houses all of the data and settings anyway.
All you do is Factory Reset, Nandroid>Restore, and your old backup will flash everything the way it was when you did a backup in the first place. Factory Reset is always wise, especially when you're fiddling with different ROM's based on different kernels or systems (AOSP/Sense).
Click to expand...
Click to collapse
Ahh, this is true I recant my statement. I was mistakenly thinking about flashing a new ROM over an older version, not a buck-up. I feel stupid.

when restoring a nandroid if you've got the new HBoot I think you have to restore boot.img separately via fastboot. Is that right?

gunnyman said:
when restoring a nandroid if you've got the new HBoot I think you have to restore boot.img separately via fastboot. Is that right?
Click to expand...
Click to collapse
Nope. I just flashed a bunch of roms yesterday and did restores with no issue. I think if your using the stock rooted 2.2 you are correct, but any other rom a restore works fine.

Not Restoring = Bad Idea
Hydromea said:
Hi, just have a quick question that's been bugging me for a while now. If I have made a full backup using TWRP and I want to restore it, should I:
Fully wipe system and caches and then restore; or just restore right over my current ROM?
Click to expand...
Click to collapse
I have made the mistake of not wiping everything (excluding sd card) when changing ROMs or when restoring from a backup. This may be a little different because it was when I was switching to a new ROM on my brother's phone, but I tried to take the lazy way out and not restore everything. I really didn't feel like redownloading everything. I soon learned that this was a mistake, and his "phone" app suddenly disappeared. He was also unable to send or receive texts. This soon made the process even longer than I wished it to be because I needed to go back and restore everything again and get it back to normal.

Error While Restoring using twrp
I took a back up of everything using TWRP and then when i tried to restored its giving me error while restoring system E:Unable to extract tar archive . Please help

Are you trying to restore a backup from a different version of TWRP? For example, currently running 2.7.0.8 but backup was originally made using 2.3.3.1?
Sent from my Evita

error on backup restore twrp
hi i have a nexus 4 running 6.0.1 reserection remix, however when i do a backup on twrp then transfer
it to my pc its fine, but when i restore it it not going as a zip and its giving me this error, could not find meta-inf/com/google/android/update-binary' in the zip file. error installing zip file/sdcard/twrp/backups/01c237769c62991c.zip please help, thanks
Become a member of the w

WOW! After a good 3/4 days of frustration, thinking I had ruined my device, I finally got my TWRP backup to restore.
It's my first time using this software and the restoration process is truly amazing. I mean, my test messages were still there, even my browser history and last page loaded up in chrome were still there. I'm blown away.
The strange thing is that It didn't work when all 3 partitions were selected. When I tried it this way (as per the many step by step instructions that I read) my phone would load up a black screen with just the notification bar visible. I'd see my voicemail, sms, wifi and battery icons at the top, but absolutely nothing else except for a myriad of pop ups that read 'Unfortunately [app name] has stopped working'.
So I bit the bullet and did some trial and error with the partitions.
Turns out that when I only selected 2 of the 3 (I believe they were 'Boot', 'Data' and deselected 'System') everything loaded up just as it was before the backup, except there were only the stock apps available and no google services at all. .....Very odd.
So I did the boot to recovery method before turning the phone off (vol. up - Home - Power) which restarted the phone and strangely brought back EVERYTHING as mentioned at the start of this post.
You can probably understand my confusion here and while I'm VERY happy that it all worked out, I don't understand why it worked with only 2 of the partitions but not with the recommended 3 of them?
Can anyone shed any light on this?
---------- Post added at 01:16 PM ---------- Previous post was at 01:02 PM ----------
debmikeshan said:
hi i have a nexus 4 running 6.0.1 reserection remix, however when i do a backup on twrp then transfer
it to my pc its fine, but when i restore it it not going as a zip and its giving me this error, could not find meta-inf/com/google/android/update-binary' in the zip file. error installing zip file/sdcard/twrp/backups/01c237769c62991c.zip please help, thanks
Become a member of the w
Click to expand...
Click to collapse
Hmmm. I'm definitely no pro at this stuff, in fact i'm very new when it comes to using TWRP, but this is what happened with me.
First of all, the backup that I did was simply a folder of files, not zip.
Transferred that do my PC, wiped my phone with TWRP and replaced the backup folder back into the TWRP/Backup folder. However, after reading up on how to restore on about 10 different android sites/forums, only 1 post shared the most vital piece of information.
You folder has to be in the 'serial' number folder that's located in the 'Backup' folder for TWRP.
When I put my backup folder just into the TWRP/Backup folder, the Restore section would only see the folder itself but the partitions were not available/listed for selection.
Once I placed my Backup folder into the TWRP/Backup/e1oog75 (that alphanumeric name is just a random example made for visual clarity) folder, my partitions were visible and available for selection right away.
Hopefully this helps somewhat.

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.

[Q] rebooting from recovery

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.

[Q] The phone does not start.

I am using CM9 ROM, I don't remember which one because I was flashing it a while ago. Something strange happended to it today. When i try to run my phone it gets stuck at CM9 animation. Tried wipes and fixes from recovery but it didn't work. I would do factory reset but i don't want to lose my apps. They are on my sd card mounted as internal with flashed script. I don't know will I lose them? Help me please.

Przeszczep said:
I am using CM9 ROM, I don't remember which one because I was flashing it a while ago. Something strange happended to it today. When i try to run my phone it gets stuck at CM9 animation. Tried wipes and fixes from recovery but it didn't work. I would do factory reset but i don't want to lose my apps. They are on my sd card mounted as internal with flashed script. I don't know will I lose them? Help me please.
Click to expand...
Click to collapse
I don't think that there is any other method so just do a full wipe
and leave in peace AND YA PRESS THANKS
HAPPY NEW YEAR

Make a backup of your current corrupt rom.
Flash same rom again without wiping anything.. see if that works.
If not..you have nandroid backup img.. take out whatever important data you need.

I made backup, flashed rom and phone runs but there is another problem. When I restore apps from my backup they don't work. When viewed from system settings they look like: com.sketchbook 0,00 B and gray icon with sd card. The same happened to superuser app so I don't even have su rights. Do you have any solution for this or I just have to start with new rom?

Use terminal.. type su..
If your root access is broken you have root it again. There are numerous softwares.. use your pc to retrieve your data from nandroid img. Using titanium to backup app from nandroid backup doesnt work.

I just reinstalled superuser app and it's working. Anyway I think I will just flash a new rom.

Przeszczep said:
I just reinstalled superuser app and it's working. Anyway I think I will just flash a new rom.
Click to expand...
Click to collapse
as I was saying