Hi I have taken a few Nandroid backups, using CWM 2.5.1.3. However wheni restore the backups from within CWM, i just get the white HTC boot screen and it never goes any further.
The backups appear to be there ok, and listed with date and time they were made, and they appear to restore successfully. But the phone just never boots up?
Any ideas what i am doing wrong?
Tones1971 said:
Hi I have taken a few Nandroid backups, using CWM 2.5.1.3. However wheni restore the backups from within CWM, i just get the white HTC boot screen and it never goes any further.
The backups appear to be there ok, and listed with date and time they were made, and they appear to restore successfully. But the phone just never boots up?
Any ideas what i am doing wrong?
Click to expand...
Click to collapse
You should wipe everything (data/cache/dalvik cache) before restoring a backup. Try that.
Yes also you can add boot, system and sd-ext (if you use one) before you restore a backup, go to the mounts and storage menu, wipe "boot, system, cache, data, sd-ext, come out of that menu, go to advanced, wipe the dalvik cache too. Also remember if you had alot of apps, 1st boot after the restore can take up to 15 mins, this is because dex-opt and the dalvik vm are busy
Sent from my Desire HD using Tapatalk
Thanks for the replies. Tried all that but still not working for me. Been sat at the white HTC screen for about 30 mins now, doesnt look like the restore has worked again.
Try with usb debugging on
Sent from my Desire HD
Is your CWM 3.0.0.6? if not, update it
Related
So I got Cm7 running using rom manager, used titanium backup to restore apps + system data, then fixed permissions. For the last 10 minutes it's been stuck in the CM7 screen....
What should I do? Can I pull the battery without harm? Does it take that long to boot after fixing permissions?
Edit: pulled the batter and am trying to boot into recovery...going to wipe the dalvik/cache again.
Edit2: same thing for the last 6 minutes....dang. I guess I'll just nandroid in 5 minutes if it doesn't' get out of it.
Edit3: going to nandroid back. I might try it again later flashing from a Zip instead of using rom manager. I probably won't restore system data either next time. If anyone has any suggestions though please post them.
Edit4: not good...phone is bootlooping cyangen screen after nandroid.
Edit5: Cleared factordata, cache, and when I go to clear dalvik I'm getting
e unknown volume for path sd-ext
Any ideas here?
Edit6: I'm reflashing 6.1.2....okay...got through the boot and now I'm setting up the phone.
You may need to wipe everything now and reinstall fresh. Do a search for Calkulin's tools here and download the format all zip and put it on the root of your sdcard. Flash it just like you would a rom from recovery. It will wipe boot, data, cache and system. Then try flashing cm7 from recovery. Usually boot loops happen because of there not being enough space on one of your partitions like system or boot etc.
housry23 said:
You may need to wipe everything now and reinstall fresh. Do a search for Calkulin's tools here and download the format all zip and put it on the root of your sdcard. Flash it just like you would a rom from recovery. It will wipe boot, data, cache and system. Then try flashing cm7 from recovery. Usually boot loops happen because of there not being enough space on one of your partitions like system or boot etc.
Click to expand...
Click to collapse
Will do....I know I had been installing apps to the SD card using CM6 and when I first got CM7 up it said my phone memory was low. I thought it would say on the SD card.
I'll probably try tomorrow again if I get the courage and I most definitely will DL Calkun's tools.
Thanks!
I'm going to guess the nandroid didn't work either because of the phone memory low issue?
I would reccomend re-doing what you did originally, except when restoring with titanium, do NOT restore system settings, only apps and data. That's probably the cause.
teh roxxorz said:
I would reccomend re-doing what you did originally, except when restoring with titanium, do NOT restore system settings, only apps and data. That's probably the cause.
Click to expand...
Click to collapse
Wiped manually, installed from zip, and didn't restore system data. CM7 has been running for about an hour now.
Thanks everyone!
Glad that you got it working man.
Is ANY system data safe to restore from Titanium?
Had the exact same problem myself... I'm restoring my Myn nandroid as we speak, and I'll mess with it more tomorrow.
Does anyone know what (if any) system data is safe to restore from Titanium? I just want my contacts and text messages basically... I don't know exactly what caused the problem from Titanium since I made sure not to check any of the Sense-related items.
For about 20 min after I pulled the battery I couldn't get the phone to do anything except vibrate three times when I tried to get into recovery. Eventually coaxed it into the bootloader where I selected to boot into recovery to nandroid back. Almost had a heart attack!
phsteve said:
Had the exact same problem myself... I'm restoring my Myn nandroid as we speak, and I'll mess with it more tomorrow.
Does anyone know what (if any) system data is safe to restore from Titanium? I just want my contacts and text messages basically... I don't know exactly what caused the problem from Titanium since I made sure not to check any of the Sense-related items.
For about 20 min after I pulled the battery I couldn't get the phone to do anything except vibrate three times when I tried to get into recovery. Eventually coaxed it into the bootloader where I selected to boot into recovery to nandroid back. Almost had a heart attack!
Click to expand...
Click to collapse
You should never restore system settings.
For contacts, open accounts and sync, tap your google account, then sync contacts, and that'll be done.
For texts, people highly recommend sms backup or my backup. Then backup apps and data, then restore only apps and data, and you'll be set.
so i have been using CM7 RC1 w/ stock kernel for a while now, without any issues. i was reading up and wanted to try the new incredikernel though, for the governor rather than using setcpu/juice defender for increased battery life.
so i did a titanium backup, then in Clockwork did a full backup before i started messing with anything. i then mounted to computer to put the kernel on the SD card. i did this, but was confused where to actually put the .zip file so that CW would see it. SD card or internal memory? i've had this issue before.
anyway, i didn't find the .zip when i booted into recovery, so i went to re-mount to USB to move it over to the other directory, and everything seized up on me. trying to mount USB basically froze my phone. re-booting did not fix, when i try to go into CM settings or try to mount USB same freezing would happen.
OK fine, i just did a nandroid backup so i figured it wasn't a big deal since i haven't actually made any changes yet and so i restored. then it would not boot. got stuck at the CM7 bootloader. ****. so i tried an earlier restore point, from a few months ago. that worked (also CM7-RC1 when i first put it on). i didn't wipe cache/dalvik when i tried the first time, so i wiped now and then tried to restore the most recent backup again. still, no luck.
so i've been living with the older restore trying to get everything how it was before. another note, i had installed a battery meter (RC1 did not come with one), and when trying to flash this, got stuck at the same bootloader screen again. another thing to note is that i have been updating CW to the latest version when it is available, but all versions are 3.xx. the latest i think i went from 3.0.0.5 to 3.0.0.8. just trying to include as much info as possible here...
any ideas? it's frustrating because i haven't actually been installing anything new. at this point i just want my phone the way it was, i.e. getting the latest restore point to work. it won't, but older restore versions will work. did CW mess up the backup, is it corrupt? is this a CM7 issue or CW? help please!
if this is in the wrong forum, apologies, it wouldn't let me post in the dev thread due to lack of posts.
Did you do a complete wipe before trying to restore your backups? In recovery, wipe data/factory reset, wipe cache, wipe dalvik cache, format boot, system, data and cache.
Sent from my ADR6300 using XDA App
k_nivesout said:
Did you do a complete wipe before trying to restore your backups? In recovery, wipe data/factory reset, wipe cache, wipe dalvik cache, format boot, system, data and cache.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
i did not do that before. i just tried though, and same result. stuck in CM7 boot loop.
wtf happened to my backup!
That happened to me once. Try this. Save everything on your sd card to your computer. Reformat card. Then put just the nandroid back on card. It might help.
Yeah sounds like it may be an issue with the SD card or your backup..
Sent from my ADR6300 using XDA App
Hello
i have a boot loop after restoring a backup, because after installing 'gapps' to the Cyanogenmod 7, it didn't work anymore
So i went into the Recovery mode to restore the backup.
But after restoring is the splash screen in a booting loop.
What can i do now?
There isn't another backup on my sd card
Is it possible to install another Rom directly from the recovery menu?
hydrano said:
Hello
i have a boot loop after restoring a backup, because after installing 'gapps' to the Cyanogenmod 7, it didn't work anymore
So i went into the Recovery mode to restore the backup.
But after restoring is the splash screen in a booting loop.
What can i do now?
There isn't another backup on my sd card
Is it possible to install another Rom directly from the recovery menu?
Click to expand...
Click to collapse
I had problems with bootloops after restoring nandroid backup - I restored all but part of it in advanced and it worked...
Check out this thread to see if it helps - http://forum.xda-developers.com/showthread.php?t=985452
brandall said:
I had problems with bootloops after restoring nandroid backup - I restored all but part of it in advanced and it worked...
Check out this thread to see if it helps - http://forum.xda-developers.com/showthread.php?t=985452
Click to expand...
Click to collapse
brandall, thankyou, I was in a nandroid-restore-boot-loop and your tip about not restoreing 'boot' saved me too (messinga around with my brothers Desire and I don't want him kicking my ass becaused of needing an unwanted full wipe)
but it's strange that an nandroid of a fully working installation fails when restored :S (had the same HBOOT when backup and restore, and the restore was made 15 minutes after creation :S )
Go into recovery, wipe everything and restore backup.
Swyped from Oxygen with Transparent XDA App
MatDrOiD said:
Go into recovery, wipe everything and restore backup.
Swyped from Oxygen with Transparent XDA App
Click to expand...
Click to collapse
Yes we both did that, but somehow the backup went broken.
I tried wipeing EVERYTHING and restore backup maybe 5 times, but boot loop every time.
So the solution was to wipe and do an advanced restore were you restored ext, system, data and cache.
But NOT restore Boot!
MrPontus said:
Yes we both did that, but somehow the backup went broken.
I tried wipeing EVERYTHING and restore backup maybe 5 times, but boot loop every time.
So the solution was to wipe and do an advanced restore were you restored ext, system, data and cache.
But NOT restore Boot!
Click to expand...
Click to collapse
Just happened to me, not restoring boot finally got me out of the bootloop, thank god. Thanks for that tip
This has never happened before. but because i stupidly deleted my LatinIme.apk trying to install a new one on top of it, I restored my backup using CWM.. to get my keyboard back.... problem is... After it restored it says Restore succesful, and the phone reboots...
Then it sits at the Splash screen and doesnt budge..
How can i fix this?
Gorilla* said:
This has never happened before. but because i stupidly deleted my LatinIme.apk trying to install a new one on top of it, I restored my backup using CWM.. to get my keyboard back.... problem is... After it restored it says Restore succesful, and the phone reboots...
Then it sits at the Splash screen and doesnt budge..
How can i fix this?
Click to expand...
Click to collapse
Did you wipe everything before doing the restore? I would boot to recovery go to advanced and wipe dalvik-cache, then go back to the main menu and go to mounts and storage and format everything except sdcard and emmc. Then restore your backup and see if it works.
if you are using 5.0.2.0 switch back to 3.0.0.8 for cwm. I never had a succesful restore with 5020
So I made a backup through OrangeFox of my A13 AOSP rom (checked every option). Now I tried to restore the backup and the restore goes normally but when I reboot to system it shows Poco logo for couple seconds then reboots to recovery and internal memory is messed up. I formatted data and tried installing the rom then restoring data alone, then data and super system, Ans the result was the same which is the rom animation starts and "starting Android" loading screen appears but never goes away. Any idea on how to get it working?
Thanks in advance
Are you trying to restore the Backup after you formated data/reflashed ROM ?
I trusted TWRP backups twice, and both times it failed.
I think to backup /data, you also have to backup /metadata, because /metadata stores the encryption-key for /data.
I also recommend the app "Swift Backup" from Play Store, it's the best app for backing up apps + appdata, messages, and call history. Requires Root to backup app-data of course.
Aserar said:
So I made a backup through OrangeFox of my A13 AOSP rom (checked every option). Now I tried to restore the backup and the restore goes normally but when I reboot to system it shows Poco logo for couple seconds then reboots to recovery and internal memory is messed up. I formatted data and tried installing the rom then restoring data alone, then data and super system, Ans the result was the same which is the rom animation starts and "starting Android" loading screen appears but never goes away. Any idea on how to get it working?
Thanks in advance
Click to expand...
Click to collapse
Yeah seems like is a tough (or impossible) mission to recover a backup in alioth.
I've done twice too, and both didn't booted too.
And this in twrp skkk, so I guess it's the same thing in all recoveries.
lapirado said:
Yeah seems like is a tough (or impossible) mission to recover a backup in alioth.
I've done twice too, and both didn't booted too.
And this in twrp skkk, so I guess it's the same thing in all recoveries.
Click to expand...
Click to collapse
cyanGalaxy said:
Are you trying to restore the Backup after you formated data/reflashed ROM ?
I trusted TWRP backups twice, and both times it failed.
I think to backup /data, you also have to backup /metadata, because /metadata stores the encryption-key for /data.
I also recommend the app "Swift Backup" from Play Store, it's the best app for backing up apps + appdata, messages, and call history. Requires Root to backup app-data of course.
Click to expand...
Click to collapse
Okay so I figured it out. You basically need to flash the same backed-up rom first and fully boot it to system. This will take care of encryption, then reboot to recovery, then restore your backup (boot/data/super). At this point reboot won't work yet. You need to go back to recovery and reflash the rom again then boot into system. For me it booted once but the status bar was missing. I did a restart and voila! It worked.
Aserar said:
Okay so I figured it out. You basically need to flash the same backed-up rom first and fully boot it to system. This will take care of encryption, then reboot to recovery, then restore your backup (boot/data/super). At this point reboot won't work yet. You need to go back to recovery and reflash the rom again then boot into system. For me it booted once but the status bar was missing. I did a restart and voila! It worked.
Click to expand...
Click to collapse
Thanks for sharing your solution!
Sounds a bit quirky but I'm glad someone got TWRP Backup Restores working!
Man the bloody forced encryption.. i hate it.