Related
Hi,
I hope that my experience could help other persons that fall in my situation.
After a try of CM, I couldn't restore my stock backup anymore, the phone hanged up in the lg boot screen.
There were no problems about ext4 partition or wiping or fixing permission.
I was thinking to do a NVflash procedure, but i gave another try: using old modaco CWM recovery. I overwrited CWM 4.2.0.2, performed a wipe, installed the modaco zip ext4->ext3 (i didn't remember if i was ext 3 or 4) and then restore my STOCK backup: EVERYTHING WAS FINE!!!
Maybe there's a problem in the newest CWM during restore a backup, i don't know, but in this way i could restore my original firmware.
Hope that this could be usefull.
Did you do your stock backup with modaco CWM? It has different MD5 checksum than the CWM. Might be the case why you can't restore your backup.
No, I did the stock backup with the original CWM.
I think that the problem is in the restore procedure of the original CWM (4.2.0.2), in fact also the CM restore is impossible, only if you install the zip immediately after the restore. Instead... hangs up.
I find when that happens the best method is to reflash the rom your restoring and just restore the data from your nandroid backup. Always works for me.
confirm this issue with cm & nandroid restore
-----------
This is true, restore and then install the rom. But how if your restore is the stock rom? NVflash? It's not the same.
Fortunally, Modaco CWM solve it without this procedure.
Thanks!!
This solve my problem with my stock nandroid restore. I downgrade CWM to 3.1.4 (did the backup with 3.2.8 version) and now works perfect!!
Finally i could restore my stock rom.
my solution was...
1. nandroid backup of mcr
2. full wipe & installed cm7
3. nandroid restore of mcr
4. installed mcr without wipe (this solved bootloop after restoring)
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.
Hi,
I have the Touchpad installed with Milaq's nightly build 08/25 and the jb-app 2013/03 build.
Is there a way to update to latest Milaq's nightly build and latest jb-app 2013/08/12 without resetting the configuration in Touchpad and will have to re-install all the apps and their config/settings?
I was thinking to install the update via CWM-Clockmod, but afraid that I will have to re-install and reconfig all the apps.
Thanks,
Well, if nothing else, an app like MyBackup Root will be able to save all of your apks+their data. Plenty of other apps do it too, that is just the one I've used. Good luck.
You can try a dirty flash, meaning that you only wipe cache and dalvik (not system or data) when you flash it in recovery. Make sure to do a nandroid first.
There shouldn't be any issues when flashing the new nightly from the recovery (CWM or TWRP). Just remember to wipe cache and Dalvik cache before rebooting to CM.
I did an dirty update to the newest cm10.2 nightly coming from cm10.1 - no bad issues so far.
Be sure to make a backup of your old rom and simply try
Currently on cm 10.1.3 stable, planning on flashing cm 10.2 snapshot. I know I need to flash the rom then the updated gapps, but when recovering apps via titanium do I restore the gapp data? Or do I have to remove them from my titanium backup before restoring
oddjob727 said:
Currently on cm 10.1.3 stable, planning on flashing cm 10.2 snapshot. I know I need to flash the rom then the updated gapps, but when recovering apps via titanium do I restore the gapp data? Or do I have to remove them from my titanium backup before restoring
Click to expand...
Click to collapse
Since you are flashing a completely different version of cyanogenmod -ie going from 4.2 to 4.3-, you MUST flash the gapps for 4.3-, I remember accidentally flashing the wrong one with the aokp rom, and it didnt work right, either it kept crashing the systemui framework, or it just kept bootlooping. Now if you wanted to restore your gapps from titanium backup, that also wont work, because again you need the gapps for 4.3. I forget why it wont work, it just doesnt lol.
PS. Now if you wanted to just restore the data from the gapps, I am not sure if that would work, so you could try perhaps backing up the rom after updating then attempt to restore, if it doesnt work then obviously restore your rom backup.
Hope that helps.
matinm90 said:
Since you are flashing a completely different version of cyanogenmod -ie going from 4.2 to 4.3-, you MUST flash the gapps for 4.3-, I remember accidentally flashing the wrong one with the aokp rom, and it didnt work right, either it kept crashing the systemui framework, or it just kept bootlooping. Now if you wanted to restore your gapps from titanium backup, that also wont work, because again you need the gapps for 4.3. I forget why it wont work, it just doesnt lol.
PS. Now if you wanted to just restore the data from the gapps, I am not sure if that would work, so you could try perhaps backing up the rom after updating then attempt to restore, if it doesnt work then obviously restore your rom backup.
Hope that helps.
Click to expand...
Click to collapse
thanks for the info, ended up switching to stock with goodies
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.