I ran a nandroid restore of a previous backup on my phone, it restored OK, I then rebooted the phone and it's only going to the HTC boot screen and no further. Anyone else run into problems?
philip_g said:
I ran a nandroid restore of a previous backup on my phone, it restored OK, I then rebooted the phone and it's only going to the HTC boot screen and no further. Anyone else run into problems?
Click to expand...
Click to collapse
<shrug> Backup corrupted. Restore a different backup.
posguy99 said:
<shrug> Backup corrupted. Restore a different backup.
Click to expand...
Click to collapse
only one I got, I have a copy of it on another computer guess I'll try that tomorrow
that failing I'll go back to fresh rom and then use that RUU_Hero_C_Sprint_1.29.651.1_signed_release.exe file and see if it'll work.
alright so I can flash it back to fresh 1.0
I can not restore the nandroid backup I made nor the copy I made to my computer
I can not run ruu to restore it
does anyone have a zip of the factory rom anywhere?
I need to un root and flash this back to stock
grrrnt just today the new ruu was posted, that works
I had a similar issue. Try formating your card via recovery, enable mass storage copy your backup over and try again.
Had a similar experience. Decided to remove my SD card, and everything worked fine. Reformatted the card and has been fine since then. No idea what would cause that to happen, but it has and it will.
Related
Asking because I never had reboot before and after restoring with Nandroid I get reboots and some errors in navigation
nandroid doesn't change kernel, recovery, baseband or radio.
it does restore everything else.
zaduma said:
nandroid doesn't change kernel, recovery, baseband or radio.
it does restore everything else.
Click to expand...
Click to collapse
I didn't change any of that....just applied lag fix and then did nandroid restore. Never had a reboot issue before......I have to say that restore point was NEW flash odin install with root, before I had original unflashed phone.
kolyan said:
I didn't change any of that....just applied lag fix and then did nandroid restore. Never had a reboot issue before......I have to say that restore point was NEW flash odin install with root, before I had original unflashed phone.
Click to expand...
Click to collapse
Can you clarify what you did there? Not sure I understand.
I'm trying to determine whether or not a lag fix (ext2 loopback file) will survive a nandroid backup/restore onto a new stock phone. I'm thinking that the safest thing would be to backup with Titanium, undo the lag fix, make a nandroid backup and restore onto the new phone. THEN, apply the lag fix to the new phone.
Perhaps I should leave this nandroid backup out of it altogether with these lag fixes. It seems we are asking for trouble. At least with Titanium, most everything will be backed up anyway. And then, they can be restored onto a bare, lag fixed phone.
EDIT: It appears there are several who are having problems restoring a Tit backup after a lag fix, which really makes no sense as to why that would happen.
Installed fresh rom with odin. Did one click root. Installed all my apps from market and removed bloatware. Backedup. Then done lag fix and then undone it, but just in case also done nadroid restore.
Personally and I do mean personally before I do anything out of the ordinary like Lag fixes or hacking away at any of my files I create a Backup via Clockwork. Of course they live on my SD card, but I also back them up onto a PC at home. With my G1 it would trash the SD card all the time for some odd reason so it was smart to rebuild the partion via RA_Recovery and then just copy over the Nandroid backups and flash away.
Always inportant to tag each backup with a quick discription to make sure you know what is what because dates do get confusing.
2010-08-09-Time-BFR-Lag = 2010-08-09-Time-Before Lag Fix
So if I screw things up I can easily restore to that point because one reason or another I'm not going to be happy. Heck if I decide I'm not to sure about a fix I create another backup 2010-08-09-Time-AFR-Lag = 2010-08-09-Time-After Lag Fix
I now can test before and after and restore back and forth constantly until I decide what I want or where I want to stay.
Heck the first thing I did after I installed ClockWork was a backup, which would put me right back at Stock minus some of the bloat apps.
My phone wont boot, so can i install a rom from clockworkrecovery?
agy1995 said:
My phone wont boot, so can i install a rom from clockworkrecovery?
Click to expand...
Click to collapse
Won't boot in what way? Can you get into fastboot and/or recovery? Since you're asking about CWM, I'm assuming you can get into it.
If you did a Nandroid backup (the main point of CWM for me), you could try just restoring it. If you didn't, I'd try a wipe all settings and then reboot. You should be able to get back to a virgin state on the main OS that way.
I can get into it, the problem is i erase all data on my phone. Thanks in advance!
???
Is there any way i can get my phone back up and running restoring everything from clockworkmod?
agy1995 said:
I can get into it, the problem is i erase all data on my phone. Thanks in advance!
Click to expand...
Click to collapse
agy1995 said:
Is there any way i can get my phone back up and running restoring everything from clockworkmod?
Click to expand...
Click to collapse
I'm still confused what your problem is.
You say the phone won't boot, but then you talk about erased data.
What exactly did you do to the phone? What was the last few things you did before you "broke" it?
What happens when you try to boot the phone (ie., it's powered off and you press the power button)? How far in the boot process does it go?
If your problem is that the phone boots but all your data is gone, there's no way to get back unless it auto-syncs down from Google, or you used a backup program like Titanium, or you made a nandroid backup in CWM.
If you made a nandroid, you should just be able to boot into CWM, select backup and restore and then restore your backup.
This is what happened....
I tried to replace my fonts in system that are supposed to work on a different phone. Then when i tried to boot up the phone was stuck on the silver google logo. Now, after that i went into clock work recovery and formated everything in the mounts and storage menu. After reinstalling the phones boot img, my phone freezes at the google logo. I can still get into the clockworkmod recovery. I never backed it up, but tried to use a nandroid someone posted online but i get a md5 mismatch.
Again, thank you for all your help!
agy1995 said:
I tried to replace my fonts in system that are supposed to work on a different phone. Then when i tried to boot up the phone was stuck on the silver google logo. Now, after that i went into clock work recovery and formated everything in the mounts and storage menu. After reinstalling the phones boot img, my phone freezes at the google logo. I can still get into the clockworkmod recovery. I never backed it up, but tried to use a nandroid someone posted online but i get a md5 mismatch.
Again, thank you for all your help!
Click to expand...
Click to collapse
The Modaco rom(http://forum.xda-developers.com/showthread.php?t=883985) should work just fine. Put it on the USB storage then in Clockwork go to "Install from zip."
i have a problem almost like that but my rom manager open but wont even backup current rom or anything, my titanium back doesn't backup either. it said i could not acquire root privileges, this app will not work, please vertify that you rom is rooted and includes busybox, i have busybox and it's rooted. i guess this happen when i update the google update last night from rom manager. what should i do
willyalmanzar said:
i have a problem almost like that but my rom manager open but wont even backup current rom or anything, my titanium back doesn't backup either. it said i could not acquire root privileges, this app will not work, please vertify that you rom is rooted and includes busybox, i have busybox and it's rooted. i guess this happen when i update the google update last night from rom manager. what should i do
Click to expand...
Click to collapse
Known issue. There is a thread in the Development section(http://forum.xda-developers.com/showthread.php?t=884499). The OTA "broke root."
Ouch. Now I understand.
In the future, always make a nandroid backup before messing around with things, easiest way to recover.
I see you're looking for help in this thread. Maybe they can help you.
You could also try flashing Doc's or Paul's roms also in that section.
rom
I tried that custom rom... still didnt work. Im going to give it another shot!
agy1995 said:
I tried that custom rom... still didnt work. Im going to give it another shot!
Click to expand...
Click to collapse
Did you wipe/factory reset before attempting to install? I realize that you're pretty much wiped at the moment, but always best to start with that.
unremarked said:
Did you wipe/factory reset before attempting to install? I realize that you're pretty much wiped at the moment, but always best to start with that.
Click to expand...
Click to collapse
I did that + i am using version 3.0 clockwork. Still frozen on the google screen.
agy1995 said:
I did that + i am using version 3.0 clockwork. Still frozen on the google screen.
Click to expand...
Click to collapse
You've tried another NAND backup, besides the one that MD5 mismatched, yar? Be careful not to rename it, as that can cause the mismatch.
Nope
Nope i didnt try any...
Do i have to rename it to update.zip?
Do i have to rename it to update.zip?
agy1995 said:
Do i have to rename it to update.zip?
Click to expand...
Click to collapse
The custom rom? No, you just go into recovery, wipe/factory reset, install from SD card, then navigate to where you put the .zip on the SD card.
I see you did try the 2.3.1 NAND backup in the development section. Try downloading it again on your PC, unzip it, then place the new folder on the clockworkmod's backup folder on your SD card. Again, do not rename it.
Im trying it now.
Im trying it now.
agy1995 said:
Im trying it now.
Click to expand...
Click to collapse
Be warned that if you do get the NAND to restore, you may lose clockwork recovery. I know I did when I first tried to use it.
Don't panic though, because you can fastboot flash clockwork back on from the bootloader.
I am pushing the files....
I am pushing the files....
Hey all,
When I had my Windows mobile phone, I could use Sprite Backup to make a backup that basically acted as an image that I could store on the SD Card. I could then do anything possible to my phone, and then I could simply restore the image, and it went back to the EXACT state it was when i took the image - registry, ALL apps, messages, icons, etc..., just like a 100% hard drive image.
I have Sprite backup on my Samsung Epic now, and was wondering if it acted the same way?
That is, if I install a custom rom, I would like to be able to factory restore it, then apply the backup to take it back to the exact state it was.
Is this how it works?
Thanks,
Matt!
It's called a nand backup and one of the benefits of rooting
Sent from my SPH-D700 using XDA App
Great,
I'm rooted, so I'll. Check it out....
Thanks!
Get the one click root and recovery. Once you have clockwork mod you can do a full backup. Also you can do an "advanced restore" and just restore your /data.
I have found that sometimes a restore doesn't work correctly and I have to reflash the rom and just restore /data to put my apps and settings back.
A word of warning, sometimes when you flash an old /data to a new rom it causes issues with programs. Personally, I have had very few issues doing it, even when moving between 2.1 and 2.2.1, but ymmv.
Hi All,
I am now running Amon-Ra 2.3 recovery, as soon as i flashed the img to the phone i did my stock backup. Now when I went to restore it, nada. Telling me Oooops. and to check the recovery log.
I know I have seen this little update everytime I go to bootloader for the 36img. thing. it says no img. then asks me if i want to start update. I did do the update the first time when I did my Stock backup.
So now I assume I am screwed or I need to stay rooted.
Any Help is appreciated
soon as i flashed the img to the phone i did my stock backup.
Click to expand...
Click to collapse
You did what?
Assuming you deleted the 36img.thing after you rooted/unrooted not sure where your going with the question. Sounds like you had a bad nand backup, or corrupted. Hopefully it is just that and you can still flash the rom again. If that is the case...backup your SD card on your computer if you still can, and then check it on your computer with an adapter for errors. While your at it and were able to back up the card...partition it again before copying it back. What brand/type of SD card was/is it anyway?
EDIT: Second thought..sounds like you are trying to unroot your phone and you wiped everything before applying the 36img.thingy. If so... just a little more work ahead of you. Give an RUU a try through boot loader, should clear things up.
@ dpilcher
I am still rooted, deleted the 36.img (Amon Ra). Yes you are correct bad backup and lost my backups. Loaded up Kingsrom Unleashed last night and its doing fine. Not trying to go unrooted, just thought i was in a world of heap that my stock backup is gone?
Also after copying my files to my computer do I run something to check for errors on just the card?
Or would it be easy to just format the card, reinstall my roms on the card? Then put it back in the phone?
I recently rooted my phone and tried a few different roms. I'm currently on cyanogen mod 10.2. I used cwm to backup my original ROM. I copied the backup file to my computer and uploaded it to my dropbox. I formatted my SD card since it had a lot of junk on it. I copies them back and now they aren't being recognized. This is my original stock ROM and since this is my first time rooting I really want to keep a stock ROM on hand for easy access incase I mess something up and need my phone to work properly. Thanks for any help. Its also a Samsung s4 i337m from fido.
can you see the backup and it's just not letting you restore it or can you not see the backup at all?
i'll tell you to keep researching and troubleshooting but if all else fails, odin back to stock, reroot, install cwm and make a new stock backup again.
Its not appearing in cwm at all unless i have a restore that was on it post format and not copied off the computer. Like if I make a backup of my current ROM the stock one will appear and just hang in checking md5. If there are no backups other than the original stock one it isn't being recognized. Also it worked before I formatteebthe SD card.
when you formatted the card and then replaced the cwm backup, where did you place the backup?
for example: 0/clockworkmod/backup, /clockworkmod/backup, etc.
if you make a backup now, where does it save the new one?
i'm just running through the bases here.
Sorry I don't know the exact locatiotion but I just dragged and dropped the "Clockworkmod" That cwm created when I made my first restore to my PC. Formatted the SD card and just dragged and dropped it back to the SD card. The new restore saves in the same folder also.
i'm assuming they're both in something like sdcard1, extSdCard or external_sd /clockworkmod/backup.
if so, and you didnt change cwm versions (i.e. from 6.0.3.6 to 6.0.4.4), then something may have been corrupted when moving the backup folder back and forth.
Yes that seems about right. I didn't change anything on cwm, unless my ROMs did. If it is corrupted will it just hang indefinitely or is there a chance it can work? And is there any other way to do a restore?
i'm no recovery expert but if your backup is corrupt than i dont imagine there's a fix for it.
i accidentally deleted my stock backup a couple phones ago. in order to have a fully stock backup on the sd card again (in the event i needed/wanted to restore to the original factory setup), i had to odin back to the stock firmware and start over.
Do you know any good guides on how to do that?
michael74195 said:
Do you know any good guides on how to do that?
Click to expand...
Click to collapse
Try to re-downloading from drop box. Could have gotten corrupted during the download process.
Download it straight from dropbox to the SD card through the phone?
michael74195 said:
Download it straight from dropbox to the SD card through the phone?
Click to expand...
Click to collapse
yup
Alright I will try it when I get home so I don't kill my data.
michael74195 said:
Alright I will try it when I get home so I don't kill my data.
Click to expand...
Click to collapse
true story.
report back. cheers
Nope, no luck. It just hangs at checking MD5 Sums. I tried the backup i made for foxhound 2.0 and it did the same thing.
edit: It worked it was just hanging for a good 15 minutes though.
michael74195 said:
Nope, no luck. It just hangs at checking MD5 Sums. I tried the backup i made for foxhound 2.0 and it did the same thing.
Click to expand...
Click to collapse
Can you have cwm not check for the md5? It's been awhile since I've used cwm. I use twrp.
Edit, doesn't look like you can. I just flashed cwm to see. Was the foxhound nandroid one you just made and it still doesn't restore?
jd1639 said:
Was the foxhound nandroid one you just made and it still doesn't restore?
Click to expand...
Click to collapse
yeah, thats what i was gonna ask: if you've made one just now and tried restoring it.
Ok thanks for the help but the problem resolved itself after letting ti hang until it did something. It worked after about 15 minutes.
edit: I just rooted the phone a few days ago and I'm all new to this, so i figured after it not doing anything for 5 mins with the dead android on the screen was bad. Thanks for the help.
michael74195 said:
Ok thanks for the help but the problem resolved itself after letting ti hang until it did something. It worked after about 15 minutes.
edit: I just rooted the phone a few days ago and I'm all new to this, so i figured after it not doing anything for 5 mins with the dead android on the screen was bad. Thanks for the help.
Click to expand...
Click to collapse
Good, yea a restore and reboot can take longer than you think. And waiting seems like forever when you're expecting it to boot. You'll get used to it.