Database Develop

[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.

[Q] CWM Restore after flashing custom ROM

Hi there,
I have a rooted N7000 running original Android v 2.3.6
I want to flash (test) it with a custom ROM.
I made a full backup of my current system (via CWM backup)
Now, when I flash a (new Android 4) custom ROM, will it then be possible to restore the old v2.3.6 image that I made, using CWM?
Other question: Do I need to take care of what type Kernal version I have
I have 2.6.35.7-N7000XXKKA-CL726566
Baseband-version is N7000XXkk5
Thanks for your reply.
Rene

jbin said:
Hi there,
I have a rooted N7000 running original Android v 2.3.6
I want to flash (test) it with a custom ROM.
I made a full backup of my current system (via CWM backup)
Now, when I flash a (new Android 4) custom ROM, will it then be possible to restore the old v2.3.6 image that I made, using CWM?
Other question: Do I need to take care of what type Kernal version I have
I have 2.6.35.7-N7000XXKKA-CL726566
Baseband-version is N7000XXkk5
Thanks for your reply.
Rene
Click to expand...
Click to collapse
nothing to worry about, that is what backup is intended to do.
the only thing you have to watch that you're on safe kernel like philZ when wiping data in stock ics or jb (read sticky threads)
example: if you are on philz kernel and runing ics or jb, when you restore your backup of gb, you restore your gb kernel, system, data etc, just like backing home

djoni_gitara said:
nothing to worry about, that is what backup is intended to do.
the only thing you have to watch that you're on safe kernel like philZ when wiping data in stock ics or jb (read sticky threads)
example: if you are on philz kernel and runing ics or jb, when you restore your backup of gb, you restore your gb kernel, system, data etc, just like backing home
Click to expand...
Click to collapse
OK, Thanks for the reply. So if I understand correctly:
1. I make a backup of my current ROM (Image via CWM) and put it in a safe place.
2. I can flash any custom ROM, and test/play with them.
3. Afterwards I can put back my old ROM again via CWM restore.
4. Reboot, and I'm back in the old state.
Is this right?
Can I flash ROMs by using CWM also (using zip files) or do I need to flash, using Odin?
I actually do not understand your remark about philZ, can you explain a bit more about what that means.
Thanks for your help so far
Rene

jbin said:
OK, Thanks for the reply. So if I understand correctly:
1. I make a backup of my current ROM (Image via CWM) and put it in a safe place.
2. I can flash any custom ROM, and test/play with them.
3. Afterwards I can put back my old ROM again via CWM restore.
4. Reboot, and I'm back in the old state.
Is this right?
Can I flash ROMs by using CWM also (using zip files) or do I need to flash, using Odin?
I actually do not understand your remark about philZ, can you explain a bit more about what that means.
Thanks for your help so far
Rene
Click to expand...
Click to collapse
Since you are going to try custom rom, you need not to worry about emmc brickbug, since they will be using a safe kernel..but double check before flashing...so, if you are on Stock ICS kernel, you should NOT wipe/factory reset..if you do, you will brick your phone..you can just go through couple of sticky threads to know abt emmc brickbug, if you are not aware of that..whatever the steps you have mentioned above are correct..but when you flash a custom rom, follow the instructions mentioned in the Custom rom OP...

Shyam said:
Since you are going to try custom rom, you need not to worry about emmc brickbug, since they will be using a safe kernel..but double check before flashing...so, if you are on Stock ICS kernel, you should NOT wipe/factory reset..if you do, you will brick your phone..you can just go through couple of sticky threads to know abt emmc brickbug, if you are not aware of that..whatever the steps you have mentioned above are correct..but when you flash a custom rom, follow the instructions mentioned in the Custom rom OP...
Click to expand...
Click to collapse
+1
jbin said:
OK, Thanks for the reply. So if I understand correctly:
1. I make a backup of my current ROM (Image via CWM) and put it in a safe place.
2. I can flash any custom ROM, and test/play with them.
3. Afterwards I can put back my old ROM again via CWM restore.
4. Reboot, and I'm back in the old state.
Is this right?
Can I flash ROMs by using CWM also (using zip files) or do I need to flash, using Odin?
I actually do not understand your remark about philZ, can you explain a bit more about what that means.
Thanks for your help so far
Rene
Click to expand...
Click to collapse
1. Yes, copy your /clockworkmod to your pc (just for double safety) dont cut it or move it, you need it on your internal sd card always, if you wanted to restore it again... and dont rename it (you will end up with message md5 missmatch!)
2. of course
3. Every new custom kernel like Philz kernel ( for ICS TW and JB TW) http://forum.xda-developers.com/showthread.php?t=1901191
or hydracore (not working on TW JB, but works on all other) http://forum.xda-developers.com/showthread.php?t=1749863
have built in CWM 6.x.x.x , You can recognize them by the gray background in CWM recovery. (there is no need to install independet CWM or something else, like you do on your stock GB kernel)
They are built in almost every custom rom, and these kernel are safe for wipe.
3.1 . So if you flashed new custom TW ics or jb, and after playing with them, you want back to your nandroid backup, just go boot in recovery (now you see a grey background CWM6) do all the wipes (in my experience the best way is: (advanced > wipe dalvik cache, go back > wipe cache, then wipe/data factory reset, then go into mounts and storage > format cache,system,data and preload , dont format emmc and sd card. go back into backup/restore > restore from (internal sd card or some other place depends on where you place your backup)
4. of course, when youo see a message backup complete, reboot it

[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

Big problems after nandroid restore!

So I flashed CM11 on my dads phone, first taking a backup of the rooted stock that was on there. Now when I restore the backup (after full wipe) It freezes and crashes all the time!. It seems as soon as I touch the phone it stops responding to my touch. However the phone still makes the bubble/water sounds when i hit menu key. Please, please help since this is my dads phone.

Samsung TW based roms stock some apps in the /preload partition so did you use Philz recovery to make nandroid backup and check include preload (located in restore and backup => misc nandroid settings )?
if not then your backup is incomplete and flashing stock rom via odin3 is the best way to revert back.
Sent from my GT-N7000 using xda premium

ASMI1 said:
Samsung TW based roms stock some apps in the /preload partition so did you use Philz recovery to make nandroid backup and check include preload (located in restore and backup => misc nandroid settings )?
if not then your backup is incomplete and flashing stock rom via odin3 is the best way to revert back.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Ah, my backup doesn't include preload. If I reverted to stock via Odin, would I still be able to restore just data?
Sent from my CM-powered Sensation

ShadowCodeGaming said:
Ah, my backup doesn't include preload. If I reverted to stock via Odin, would I still be able to restore just data?
Sent from my CM-powered Sensation
Click to expand...
Click to collapse
After flashing using Odin, rooting using Philz kernel to get cwm, you can do an advanced restore of just data. It might not restore 100% data but should restore enough.
PS. Preload is only used if you had JB earlier.

[Q] Questions before flashing custom ROM

I am planning to flash a custom rom on my phone (for the first time).
Model : Xperia SP(C5302)
Build : 12.1.A.1.205 (Stock) running JB 4.3 with LB
I have rooted my phone using the towelroot method and installed supersu. I have also installed custom recovery from here http://forum.xda-developers.com/showthread.php?t=2649923
I am planning to flash this custom rom http://forum.xda-developers.com/xperia-sp/development/cyanogenmod-11-locked-bootloader-users-t2868398
So I have a few questions that I am not clear about(even after searching the forums). And sorry if they are dumb. I really want to understand as much as possible before flashing roms.:fingers-crossed:
1. After reading the thread of my recovery, from what I understand, the recoveries are installed in /system. But on OP of the custom rom, I am about to install, there is an instruction to format /system before flashing the rom. So my question is if I format the /system partition, won’t my recoveries be removed (by the recoveries itself) before I even flash the rom?
2. Also will the recovery still be available to me if say I enter bootloop for some reason during flashing the rom?(asking for the same reason as above that is wiping my /system should also remove my recoveries)
3. Does CM 11 come with any inbuilt custom recovery? If not can I install the one I am already using (assuming installing a custom rom will remove my installed recoveries)?
4. Say I screw up during the flashing procedure. So if I want to rectify this I should first flash the stock .205 ftf, root, install a recovery again and then restore using the nandroid backup. Am I correct?
5. Is it necessary to wipe cache and dalvik cache before flashing rom? I see this instruction in some roms but not in others. And dalvik should be wiped after flashing rom and gapps, right?
6. Should I install supersu again after I flash the rom. I read in an article that it causes problems with CM. As far as I know CM11 comes pre-installed with superuser. But it also supposedly causes some problems.
7. Is it safe to restore user app+data, messages and contacts backed up using Titanium backup on a newly flashed rom? I have seen conflicted views on this.
Click to expand...
Click to collapse
And that’s it for my questions (for now at least... ).
A Big Thanks in advance for all your helpful answers

Prat92 said:
I am planning to flash a custom rom on my phone (for the first time).
Model : Xperia SP(C5302)
Build : 12.1.A.1.205 (Stock) running JB 4.3 with LB
I have rooted my phone using the towelroot method and installed supersu. I have also installed custom recovery from here http://forum.xda-developers.com/showthread.php?t=2649923
I am planning to flash this custom rom http://forum.xda-developers.com/xperia-sp/development/cyanogenmod-11-locked-bootloader-users-t2868398
So I have a few questions that I am not clear about(even after searching the forums). And sorry if they are dumb. I really want to understand as much as possible before flashing roms.:fingers-crossed:
And that’s it for my questions (for now at least... ).
A Big Thanks in advance for all your helpful answers
Click to expand...
Click to collapse
First of all, I am only explaining the one I know about
1. Well, wiping the system will remove the recovery. That's why you'll have to flash the ROM after wiping the system. Do not ever reboot the phone after wiping the system but haven't yet flashed the ROM zip, else you'll have to do more work to flash the Stock ROM. This is due to the fact your phone does not have an OS to boot into! When flashing the ROM zip, the recovery will be automatically installed.
2. This is based on luck, most of time you'll end up unable to boot into anything. A fix is to flash the Stock ROM again.
3. Every ROM has recovery built with it (unless stated otherwise in the thread)! Upon flashing, it will be automatically installed too.
4. The methods you mentioned is correct. However, only restore the nandroid backup if you want to stay on stock. You could always retry to flash the ROM again. Nandroid backup is an image backup of your android. If you restore your nandroid backup, you'll end up with your previous version of android (like the way before you started flashing the ROM)
5. Wiping /cache and dalvik-cache is a really good practise! It doesn't really matter when you will need to wipe them, but personally I wipe them all before flashing the ROM. Wiping /data and performing a factory reset through recovery is recommended if you're coming from a different ROM. That's why backing up user apps through TiB (Titanium Backup) is recommended for you to easily get your installed apps back. Remember, nandroid backup and apps backup from TiB is different to each other.
6. No, this might cause extreme conflicts. No, I am using SuperUser as long as I have used CM. It never fails to give root permission at all despite the hatred I sense in some apps that overly-recommends SuperSU.
7. Of course it is very safe to restore them backups with TiB. However, based on my experience, messages and contacts were unable to be restored due to the difference in ROM version. I don't know if anyone else faces the same problem as mine. As of this, I really recommend your contacts to be synced with Google.
Heads up!
Based on this post, the dev of the ROM you wanted to flash, MrSteve555, recommends PhilZ when flashing the ROM.

TechnoSparks said:
First of all, I am only explaining the one I know about
1. Well, wiping the system will remove the recovery. That's why you'll have to flash the ROM after wiping the system. Do not ever reboot the phone after wiping the system but haven't yet flashed the ROM zip, else you'll have to do more work to flash the Stock ROM. This is due to the fact your phone does not have an OS to boot into! When flashing the ROM zip, the recovery will be automatically installed.
2. This is based on luck, most of time you'll end up unable to boot into anything. A fix is to flash the Stock ROM again.
3. Every ROM has recovery built with it (unless stated otherwise in the thread)! Upon flashing, it will be automatically installed too.
4. The methods you mentioned is correct. However, only restore the nandroid backup if you want to stay on stock. You could always retry to flash the ROM again. Nandroid backup is an image backup of your android. If you restore your nandroid backup, you'll end up with your previous version of android (like the way before you started flashing the ROM)
5. Wiping /cache and dalvik-cache is a really good practise! It doesn't really matter when you will need to wipe them, but personally I wipe them all before flashing the ROM. Wiping /data and performing a factory reset through recovery is recommended if you're coming from a different ROM. That's why backing up user apps through TiB (Titanium Backup) is recommended for you to easily get your installed apps back. Remember, nandroid backup and apps backup from TiB is different to each other.
6. No, this might cause extreme conflicts. No, I am using SuperUser as long as I have used CM. It never fails to give root permission at all despite the hatred I sense in some apps that overly-recommends SuperSU.
7. Of course it is very safe to restore them backups with TiB. However, based on my experience, messages and contacts were unable to be restored due to the difference in ROM version. I don't know if anyone else faces the same problem as mine. As of this, I really recommend your contacts to be synced with Google.
Heads up!
Based on this post, the dev of the ROM you wanted to flash, MrSteve555, recommends PhilZ when flashing the ROM.
Click to expand...
Click to collapse
Thanks for such detailed answers. That cleared most of my doubts
Just some last few questions(promise!)
1. If wiping /system does remove the recovery before I install the rom, how is it possible to access it even to flash the rom? Shouldn't it like just close right when I wipe /system. Or does it not work like that?
2. Just to be sure the nandroid backup I made on my stock rom won't work if I later try to flash it through recovery while using CM,right?

Prat92 said:
Thanks for such detailed answers. That cleared most of my doubts
Just some last few questions(promise!)
1. If wiping /system does remove the recovery before I install the rom, how is it possible to access it even to flash the rom? Shouldn't it like just close right when I wipe /system. Or does it not work like that?
2. Just to be sure the nandroid backup I made on my stock rom won't work if I later try to flash it through recovery while using CM,right?
Click to expand...
Click to collapse
1. Wiping system wont close the recovery at all. It still runs and you can still navigate within it. But remember do not reboot unless you've flashed the ROM! The mechanism of how the magic works is yet to be acknowledged. So I can't tell why it doesn't closes upon wipe. My best guess here is that the recovery might be running on a temporary partition perhaps. I hope a developer see this post and explains the magic.
2. Nandroid backup works all the time (if they are no errors when you are creating them). Nandroid backup is simply a backup of your whole device. If you're on CM, restoring nandroid backup will get your phone back to the way when you attempted the nandroid backup (stock ROM, rooted, and triple recoveries installed). Nandroid backup is useful when you're about to try something that may damage your ROM, without doing so much work to restore your device.
Say, you created a nandroid backup in cwm in which Cyanogenmod was installed. And then you flashed something afterwards. If that "something" damages the ROM and gives you bootloop, you can simply flash Stock ROM, root it again, install recoveries again, and restore the nandroid backup. Then, voilà, cyanogenmod is back. This will simplify your work rather than flash CM again, then gapps, then restore your apps and all those other things that will consume so much time
So a new nandroid backup will backup the whole device, in a form of an image.