Database Develop

Nandroid backup of rooted stock ROM

I've made a nandroid backup of my rooted stock Rom with cyanogen recovery and flashed Modacos FR15 wich worked retty good for me. But after some testing i wanted to change back to my stock Rom. After doing backup of the Modaco I wiped and restored the stock rom backup which refused to boot. I restored the modaco Rom which worked perfect. Any ideas what the reason could be? BTW md5 check before restore was all fine and no errors on restore.
Sent from my LG-P990 using XDA App

Did you wipe everything? Also Dalvik cache? It worked for me tho, what kind of version are you using for CWM?

CWM is 3.0.2.8 (latest version which i installed via ROM Manager) - as I said - other backups of CM Nightly and Modaco FR15 worked without probs. But I made 2 Backups of my rooted Stock ROM v10c which refuse to boot after restore :/
Wiped all except Dalvik - I thought Dalvik gets wiped when doing Wipe Data / Factory Reset ... but I will try again with wiping Dalvik too.

I tried again to restore this time with dalvik wipe - but no change - boot hangs at the LG logo with the grey/blue loading-bar, the bar is moving some seconds and then stops and nothing happens. :/

try to press power+vol down to reset the phone to factory default. see if it can help...

I've had similar problem.
phone wont boot.
Only way I found out, you can see here:
http://android.modaco.com/content/l...rom-release-v10b-dated-1300166062-15-03-2011/
but you will loose everything what is on your phone

The reason it won't work, is because MCR converts the file system to ext4 (which CM7 can cope with). To revert to stock, you need ext3 - either
1. Use this to convert back to ext3 and immediately restore the backup (don't reboot or it will go fubar) http://android.modaco.com/content/l...3-for-converting-your-device-er-back-to-ext3/
2. Use nvflash to restore the stock 10b, then flash Clockwork, and then restore your backup.
The choice is yours .

[Q] SOLVED - Cannot restore Nandroid backups. Phone stuck on LG screen.

I have seen the same issue on other models forum but could not answer my problem.
Whenever I restore a Nandroid backup using either ROM manager or CWM recovery, all goes fine but on reboot I am stuck on the 2nd LG logo.
The only fix I found is to restore the ROM, pull the battery, boot into recovery, re-install CM7 from the SD card.
This happens will ALL the backups I made while on CM7.
I can however restore and boot the original LG ROM I backed-up after rooting my phone.
Am I doing something wrong?
Thanks.
LG Optimus 2x
CM7 nightly 39 (but had the same with previous versions)
ROM manager premium 4.3.1.3
CWM recovery 3.0.2.8

Try wiping all caches (including dalvik in advanced) and fix permissions. Also you can try CWM 3.2.0.x (you have to install it manually, Rom Manager does not let me download it)

If u restoring nandroid backup of cm7, flash cm7 rom after u completed restoring backup then u reboot.
1. Restore nandroid backup
2. Flash cm7 rom
3. Reboot

I did wipe all, but it did not help.
I am not sure about CWM 3.2.0.1. I will give it a try.
mikee2185 said:
Try wiping all caches (including dalvik in advanced) and fix permissions. Also you can try CWM 3.2.0.x (you have to install it manually, Rom Manager does not let me download it)
Click to expand...
Click to collapse

Thanks.
This is what I am doing, but why do I need to reflash CM7 after a nandroid restore?
temasek said:
If u restoring nandroid backup of cm7, flash cm7 rom after u completed restoring backup then u reboot.
1. Restore nandroid backup
2. Flash cm7 rom
3. Reboot
Click to expand...
Click to collapse

I did a nandroid with my fr17, restored it and it wouldn't boot correctly, so i reflashed it without the wipe and it worked, maybe some system file wernt correctly backed up, hope this helps
Sent from my LG-P990 using XDA App

It was a problem with the boot image not restoring properly (or at all perhaps), this should be fixed on CWM 3.2.0.1 (and possibly 3.2.0.0)

Thank you Rusty (and mikee2185).
Installed your 3.2.0.1 and it worked fine!
Cheers.
Rusty! said:
It was a problem with the boot image not restoring properly (or at all perhaps), this should be fixed on CWM 3.2.0.1 (and possibly 3.2.0.0)
Click to expand...
Click to collapse

Great both of you rusty & pa64. I was facing the same problem with stock ROM restore with a certain version of CWM recovery. Rusty's 3.2.0.1 saved the day for me and restored successfully from the same backup which the other CWM version failed. Thanked both of you.

thanks temasek
it worked.

[SOLVED] Am I bricked? PLEASE help me :(

Hi guys. I'm quite a noob, but have a good experience on flashing without be bricked (CM9, CM10, Crash, Paranoid...), but I have a problem.
I will explain to you step-by-step what I've done with my Note, so I wish some of you could help me.
1) I was running JB Crash ROM with PhilZ kernel.
2) Some apps got Force Close too often, so I went on Rom Manager and, after a look into the "Fix permissions" description ("It will fix some force closes" or something like that), I decided to give it a try and I tapped on it.
3) After that, my homescreen became unusable, because "TouchWiz Home" got EVERY TIME force closed without reason. Everything else worked fine, so I deciced to boot into CWM recovery to restore a nandroid backup of the same ROM.
4) Instead of tapping "restore", I tapped "backup" (my fault) and it started without possibility of get back. I got something like 200 Mb of free space, so in every case it will never have had success. My Note stucked at this point, so I decided to reboot manually (vol up+home+power) into recovery. Finally I tried to "restore" but I get this message: "ERROR WHILE RESTORING /SYSTEM".
5) I tried to reboot my Note, but it stucks at "Samsung Galaxy Note GT-N7000" screen without going on.
The good news is that it can go without problems into recovery and into download mode. What can I do? Flashing from CWM, for example, CM9 can fix this?
Please help me thanks!

1. Boot into CWM
2. Wipe data, dalvik and cache
3. Format system
4. Reflash your ROM
Don't use rom manager it's not compatible ....

friedje said:
1. Boot into CWM
2. Wipe data, dalvik and cache
3. Format system
4. Reflash your ROM
Don't use rom manager it's not compatible ....
Click to expand...
Click to collapse
After formatting /system, can I try to restore my nandroid backup? Or I have to necessary reflash my ROM? In that case, it's the same thing make it via CWM or via ODIN PC? I'm still on PhilZ recovery, which is safe I guess!
Anyway, thanks for your help

Via CWM or Odin, depends if you have your rom in the zip or the md5.tar format.
I would reflash to be clean. It's a bit more work in restoring your apps and data
afterwards, but at least you don't restore any messed up files.

if you can still access CMW and Download Mode then you probably are not brick... try fresh install through pc odin.. safe method no need to worry about bricking by fullwiping on unsafe kernel or raising triagle or binary counter whatsoever.. if you wanna play safe then PC ODIN and after that you can root your rom

Thank you guys, now I'm on stock ICS flashed via PC Odin and everything works fine I knew I was 99% not-bricked (still recovery and download mode avaiable), but I was a little scared too.
Thank you again!

glad you solved it.. :good:

[Q] I need some help to get back to Ultimate XXLSZ

I was using Ultimate ROM XXLSZ_JB_4.1.2_v5.2 without any problems apart from poor battery performance.
However, I attempted to install Rocket ROM-V1-XXLSZ and have now got myself into trouble.
I followed the instructions to flash the latest XXLSZ-OXA cwm kernel and then flashed the Rocket ROM. It worked ok but I would like to return to the Ultimate ROM and kernel I had before.
I have a pevious full Nandroid backup of the phone (made with ROM Manager Premium) of the Ultimate ROM and the PhilZ kernel it came with but cannot restore it. I get the error "MD5 Mismatch" and the restore aborts.
Even if I reflash the original Ultimate ROM with all the usual wipes, the XXLSZ-OXA cwm kernel is still there and I still can't restore from the Nandroid backup. I tried re-flashing PhilZ 3.1 kernel separately and then the Ultimate ROM file but this didn't work either. The kernel is still the same.
Can anyone tell me how to either
1. completely wipe the phone so I can install Ultimate ROM AND the built-in PhilZ 3.1 kernel.
OR
2. get the phone to the point where I can restore from my Nandroid backup which I assume will restore the earlier version of the ROM at the same time.
I hope I've explained the situation clearly enough.
Thanks in advance.
Trevor

Install a cm kernel then wipe your phone then install a fresh ultimate rom and later on advance restore the data
Sent from my GT-N7000 using Tapatalk 2

Go to cwm/backup and restore/misc nandroid setting/ untick md5 check. And try to restore again
Sent from my GT-N7000 using xda premium

You don't want to restore your nandroid. It is a bad backup.
In philz recovery go to mounts and storage. Format system data preload cache. Them go to advanced from main page and wipe dalvik
Flash ROM. Guaranteed to work.
Sent from my Samsung Galaxy SV using Tapatalk 3

Thanks. I know I can flash the ROM again but I was hoping to learn why the Nandroid backup no longer works.
Since posting, I gave up trying to restore the Nandroid backup, did all the usual wipes, re-flashed the Ultimate ROM and re-installed all my apps from scratch so my phone is more or less back to normal (Incidentally, I notice that no matter how many times I do this, all my music and photos are still there even though they're stored on the internal sd card. Dunno why).
Most of the ROMs I've tried have the kernel built in so all I needed to do was do the usual wipes and then flash. If I didn't like the ROM, I just wiped again and restored the Nandroid backup using CWM (Vol Up + Menu + Power) and the phone was back to its previous state.
The only thing I did different this time, as per the Rocket ROM instructions, was flash a kernel first. I may have done something wrong with that step or messed it up somehow. Even when I flashed an earlier version of the PhilZ kernel, the restore still didn't work. I've still a lot to learn about ROMs and Kernels, I guess.
As I said, I have successfully restored from Nandroid backups many times before this without any problem after experimenting with different custom ROMs. Can I ask you why Nandroid is a bad backup? Is it a problem with ROM Manager?
(One problem I've always had with ROM Manager is that if I choose to write the backup to the external sd card, it falls over with error messages. If I choose the option to backup to the internal card, it works but writes the BACKUP TO THE EXT CARD ANYWAY! I cannot get a reply from the dev about this).
Is there a better, more reliable backup method you'd recommend that does the same thing as the Nandroid?
I notice that different ROM managers use different CWM Recovery versions ie ROM Manager Reboot Recovery = 6.0.1.2, ROM Toolbox Rebooter = CWM 6.0.2.8 (same as Vol Up + Menu + Power). Could that be part of the problem?
Sorry for the long winded post.
Trevor
asf58967 said:
You don't want to restore your nandroid. It is a bad backup.
In philz recovery go to mounts and storage. Format system data preload cache. Them go to advanced from main page and wipe dalvik
Flash ROM. Guaranteed to work.
Sent from my Samsung Galaxy SV using Tapatalk 3
Click to expand...
Click to collapse

[Q] Series of forced-close[s] during system startup following nandroid restore

Hello then!
The situation is as follows:
- Done a nandroid backup using a certain kernel and CWM
- Installed various ROMs
- Trying to restore my original ROM, using the same kernel and CWM version that created it
- The system boots, showing the startup animation (in this case the cellphone carrier animation, after the Samsung logo) and gets stuck, vibrating every once in a while like in forced-closes.
My guess is that some system process crashes or fails to start, dragging the rest of the system with it. I just don't know why it would happen after a nandroid recovery with the same kernel and CWM version, factory wipe, formatting etc.
- Tried a factory reset + cache wipe + dalvik cache wipe
- Tried formatting the various partitions and re-partitioning using a 512 PIT file
- Tried flashing similar (slightly earlier or later) ROMs through Odin, then restoring
I do have a Titanium backup in place, but not an Odin-flashable version of this ROM, so this isn't the end of the world, but it will force me to switch a ROM at an odd timing if I don't solve this.
Any ideas?

tempnick said:
Hello then!
The situation is as follows:
- Done a nandroid backup using a certain kernel and CWM
- Installed various ROMs
- Trying to restore my original ROM, using the same kernel and CWM version that created it
- The system boots, showing the startup animation (in this case the cellphone carrier animation, after the Samsung logo) and gets stuck, vibrating every once in a while like in forced-closes.
My guess is that some system process crashes or fails to start, dragging the rest of the system with it. I just don't know why it would happen after a nandroid recovery with the same kernel and CWM version, factory wipe, formatting etc.
- Tried a factory reset + cache wipe + dalvik cache wipe
- Tried formatting the various partitions and re-partitioning using a 512 PIT file
- Tried flashing similar (slightly earlier or later) ROMs through Odin, then restoring
I do have a Titanium backup in place, but not an Odin-flashable version of this ROM, so this isn't the end of the world, but it will force me to switch a ROM at an odd timing if I don't solve this.
Any ideas?
Click to expand...
Click to collapse
Yes , you must flash the same version of android how the nandroid is.
When Nandroid is made while using ICS 4.0.4 then flash a 4.0.4 based rom then you can restore it.

SOLVED
kevinrus123 said:
Yes , you must flash the same version of android how the nandroid is.
When Nandroid is made while using ICS 4.0.4 then flash a 4.0.4 based rom then you can restore it.
Click to expand...
Click to collapse
That much I already know.
What finally solved it is this procedure: It seems that the carrier ROM that I had (in a *.tar file) wasn't enough for resetting the device, and flashing one of the ROMs listed in this thread did the job. I then flashed the carrier ROM and the CF-Root kernel, which I had before, and successfully restored everything from my nandroid backup.

tempnick said:
That much I already know.
What finally solved it is this procedure: It seems that the carrier ROM that I had (in a *.tar file) wasn't enough for resetting the device, and flashing one of the ROMs listed in this thread did the job. I then flashed the carrier ROM and the CF-Root kernel, which I had before, and successfully restored everything from my nandroid backup.
Click to expand...
Click to collapse
Nice to hear that it's fixed now