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.
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'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 .
Hi
I'm experiencing these issues during last days:
-Market doesn't download or actualize nothing (Error 492)
-Phone shuts off randomly
-I cannot load CWM recovery
These are my phone specifications:
-V20o Official Leaked Rom
-Horsepower extreme 24BPP RC11 Kernel
-Hp v20o tweaks
-Fast Dormancy Logging fix
-Scrolling Cache Disabler for smoother scrolling
-CWM Touch Custom Recovery installed flashing a zip encountered on xda
I'm experiencing these problems after I installed CM9 beta-rom (and the proper google apps) and then I went back to the V20o doing three wipes and restoring a previous Nandroid Backup
Any suggestion?
Thanks
The problem is I think touch recovery. It contains a bug when your wiping cache. The problem is that after wiping it, it won't rebuild, so this will crash your market and may also cause the other problems.
What you could do is change your recovery.
Thank you very much
So I should not wipe cache when i run a Nandroid restore?
I ask you this 'cause when, after installing CM9 (doing three wipes procedure), i rebooted into recovery to restore Nandroid backup and it seemed to work well. I began to experience problems when I loaded Rom after it.
Anyway is there any chance to reinstall old version CWM without reinstalling the Rom?
scompiani said:
Thank you very much
So I should not wipe cache when i run a Nandroid restore?
I ask you this 'cause when, after installing CM9 (doing three wipes procedure), i rebooted into recovery to restore Nandroid backup and it seemed to work well. I began to experience problems when I loaded Rom after it.
Anyway is there any chance to reinstall old version CWM without reinstalling the Rom?
Click to expand...
Click to collapse
The problem occurs after every cache wipe, because it should rebuild after every wipe and that's the problem.
The easiest way to reinstall a CWM version is using ROM Manager and restore to CWM version 5.0.2.0. I know it's kinda old, but it'll do good enough.
EDIT: If you for some reason really don't like CWM 5.0.2.0, look at this thread: http://forum.xda-developers.com/showthread.php?t=1478995
You can find a flashable zip somewhere of CWM 5.0.2.7
Touch Recovery i had was flashed from that .zip file you're telling me! Anyway i tried to install old CWM version in Rom Manager but it didn't resolve the problem.
I will manage to reinstall everything.
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
Hi there,
I recently rooted and flashed a custom ROM onto my Samsung Galaxy S3 Mini. I'm very new to this thing and find everything quite overwhelming, but I want to learn.
I flashed this ROM - http://forum.xda-developers.com/showthread.php?t=2119219 (the v6 No Wipe version because I was petrified about losing my data if I factory reset), but the phone is now extremely laggy and buggy, so I want to go back to the stock ROM (so I can do a nandroid backup) and then try a different custom ROM like Dmod.
So, my question is, do I have to factory reset my phone to go back to stock? Or can I just flash this file (http://hotfile.com/dl/189271016/833...T-I8190N-BTU-I8190NXXALL6-1356151513.zip.html) using the CWN recovery menu without wiping? I'm asking because my phone keeps giving me an error everytime I try to backup using the CWM Recovery menu.
Thanks and if you need me to explain something in further detail, let me know.
YamiWheeler said:
Hi there,
I recently rooted and flashed a custom ROM onto my Samsung Galaxy S3 Mini. I'm very new to this thing and find everything quite overwhelming, but I want to learn.
I flashed this ROM - http://forum.xda-developers.com/showthread.php?t=2119219 (the v6 No Wipe version because I was petrified about losing my data if I factory reset), but the phone is now extremely laggy and buggy, so I want to go back to the stock ROM (so I can do a nandroid backup) and then try a different custom ROM like Dmod.
So, my question is, do I have to factory reset my phone to go back to stock? Or can I just flash this file (http://hotfile.com/dl/189271016/833...T-I8190N-BTU-I8190NXXALL6-1356151513.zip.html) using the CWN recovery menu without wiping? I'm asking because my phone keeps giving me an error everytime I try to backup using the CWM Recovery menu.
Thanks and if you need me to explain something in further detail, let me know.
Click to expand...
Click to collapse
That firmware is a zipped odin-file. Can't be flashed in CWM.
Make a cwm nandroid backup of your "/data" to your external sd (that's your installed apps)
You can also backup your apps and appdata using titanium backup or similar, for later restore.
Just remember to never backup/restore systemapps.
Backup internal sd to computer just to be sure, if you in any situation have to make a factory reset. Make sure any kind of backup is on your external sd before you make factory reset, or it will be lost forever
YamiWheeler said:
Hi there,
I recently rooted and flashed a custom ROM onto my Samsung Galaxy S3 Mini. I'm very new to this thing and find everything quite overwhelming, but I want to learn.
I flashed this ROM - http://forum.xda-developers.com/showthread.php?t=2119219 (the v6 No Wipe version because I was petrified about losing my data if I factory reset), but the phone is now extremely laggy and buggy, so I want to go back to the stock ROM (so I can do a nandroid backup) and then try a different custom ROM like Dmod.
So, my question is, do I have to factory reset my phone to go back to stock? Or can I just flash this file (http://hotfile.com/dl/189271016/833...T-I8190N-BTU-I8190NXXALL6-1356151513.zip.html) using the CWN recovery menu without wiping? I'm asking because my phone keeps giving me an error everytime I try to backup using the CWM Recovery menu.
Thanks and if you need me to explain something in further detail, let me know.
Click to expand...
Click to collapse
Backup your data in CWM, flash my ROM and restore your data with CWM.
Benzonat0r said:
Backup your data in CWM, flash my ROM and restore your data with CWM.
Click to expand...
Click to collapse
CWM has NO choice to backup/restore only parts of the device. Only a full backup is possible.
This is only in TWRP. Pity! I only use CWM because TWRP makes corrupted backups (three times) for me.
Or is it possible to pick out only DATA from the backup? And what is happen with the dalvik cache, which
consists of the byte-code for all installed apps, optimized for the ROM which created it?
"advanced restore and restore only /data". Is this the way in CWM that you mean @benz?
JackoMJ
Yes that's exactly what I meant, "advanced restore and restore only /data"
You don't have to worry about cache and dalvik because it's automatically created on the initial start.
thx for the information Benz (usefull in the future perhaps),
but i´ve decided to use Titanium Backup.
JackoMJ