ive been rooted for quite some time, and never have had trouble with pulling backups form clockwork recovery. last night i made a backup of my CM7.0.3 that i was using for a while to try out virtuous unity. today on my lunch break at work i attempted to load the backup and i was getting that error message.
i did a "superwipe for g2" right before i tried to recover.
then i attempted to recover my stock rom i have had for months an i got the same error message. any ideas? the only thing i could think of is a few days ago i cleared out a HUGE cache in my clockwork from my SD to clear up my card. could that be it? any help would be appreciated.
bump.
someone please give me some help! i would really appreciate it.
i attempted this
http://forum.xda-developers.com/showpost.php?p=11768066&postcount=2965
but go no response and still had a md5 mismatch.
Had that issue before... The back up process didn't go right unfortunately. I would recommend you to download another Rom and transfer it to your SD card.
Sent from my HTC Vision using XDA Premium App
what do you mean by that?
PatrickHuey said:
what do you mean by that?
Click to expand...
Click to collapse
Well it rarely happens. I remember when I got the same error and told somebody in XDA they told me that during the back up process clockwork didn't back it up correctly which leads you not being able to restore your back up. Had virtuous 2.2 back then, good thing was I had 2 back ups just in case so I was able to restore a later version of my back up.
Sent from my HTC Vision using XDA Premium App
Did you by any chance change the name of the folder of the backup? I once 'annotated' the default date-time format that Clockworkmod uses with something more meaningful to me, but found that it breaks the MD5 check.
I'm just asking on the off-chance because changing the folder name back to what it was when the backup was made will fix it, if that's the case.
Good luck.
Yeah I did, but I hadn't had any problems with renaming it with it before. I attempted to change it back to a default name and that didn't work. Is there anyway to try and recover my backup, or just my data?
Sent from my HTC Vision using XDA Premium App
I also had this problem before when switching between cyanogen and a Sense ROM. The way I fixed it was I downloaded, wiped and installed a fresh new cyanogen ROM. After it was installed I was able to restore my old backup from CWM.
ill have to give that a try. thankyou sir.
I would like to do a complete back up of the kernel, rom, apps, data, etc. and move it all over to another Nexus 7.
Is it possible to do a complete backup and restore via USB? Backup to Desktop, and then restore into the new 7?
If so, what is the best way?
Thanks!
If you use an older version of cwm (pre 6.x.x.x) it will create a single backup file instead of the current system with the blobs folder. However I would be very wary of moving one backup to another
Sent from my Nexus 7 using xda premium
brianjr1 said:
If you use an older version of cwm (pre 6.x.x.x) it will create a single backup file instead of the current system with the blobs folder. However I would be very wary of moving one backup to another
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Let me explain. I am replacing my Nexus 7 with a new one, and don't want to have to set it all up again because it's perfect right now
No clean way to do this? I have to just rebuild it all over again on the new 7?
If you are rooted, you can almost do it that easy, but you would need to unlock and root the new device first, install recovery and then move the saved nandroid backup to the new device and use recovery to restore that and you would have a copy of your old device on the new one.
The last time I did that,I was up and running on the new device in about 15-20 mins.
http://forum.xda-developers.com/showthread.php?p=29550640
If you are not rooted, there is another method, but I've never actually tried doing it, so I don't know how well it works.
Sent from my Nexus 7
krelvinaz said:
If you are rooted, you can almost do it that easy, but you would need to unlock and root the new device first, install recovery and then move the saved nandroid backup to the new device and use recovery to restore that and you would have a copy of your old device on the new one.
The last time I did that,I was up and running on the new device in about 15-20 mins.
http://forum.xda-developers.com/showthread.php?p=29550640
If you are not rooted, there is another method, but I've never actually tried doing it, so I don't know how well it works.
Sent from my Nexus 7
Click to expand...
Click to collapse
Thanks. That helps alot. I am rooted so should be good to go. I was not aware that the nandroid file could be saved and restored to a new device.
Sent from my Nexus 7 using xda app-developers app
On my Android phone, Nandroid does not back up the internal (/emmc) data nor the /sdcard data. Does it back up EVERYTHING on the Nexus 7?
I remember putting CWM on my N7 but I then decided to switch because CWM caused me problems by making more and more subfolders in /0 . Has that problem been fixed or adressed? And has it happened to you? I want to hop on back to CWM because TWRP isn't doing the job for me on most things.
iAndropple said:
I remember putting CWM on my N7 but I then decided to switch because CWM caused me problems by making more and more subfolders in /0 . Has that problem been fixed or adressed? And has it happened to you? I want to hop on back to CWM because TWRP isn't doing the job for me on most things.
Click to expand...
Click to collapse
Twrp for me is much better than CM. Try the latest twrp. They just updated 2 days ago I think.
iAndropple said:
I want to hop on back to CWM because TWRP isn't doing the job for me on most things.
Click to expand...
Click to collapse
I haven't used CWM yet so I can't confirm nor deny what you say, but your post would be much more valuable to me (and I suppose others, too) if you could please BE SPECIFIC.
The phrase "most things" provides zero useful details.
Thanks
Well i am currently using CWM flashed using the rom manager app. Then flashed it to manually flash Cwm touch recovery. Working a-ok for me. In case it helps i am on v6.0.2.3
Sent from my Nexus 7 using xda app-developers app
So I was playing Family Fued last night on my phone and pressed the home button. After doing so, my phone screen turned black and became unresponsive so I held the power button and rebooted. Upon booting the phone got stuck on the boot animation.
So I tried dirty flashing my ROM, gapps, and kernel. The phone booted then got stuck on the Starting Apps toast with a continuous progress wheel. I tried a combination of wiping caches and dirty flashing to no avail. I was running francos kernel with -75 UV, but flashed a kernel without UV to be sure. I'm still unable to get past the starting apps toast when I restore to the backup I made.
I just want to get it to boot so I can retrieve some important text messages. Any help is appreciated. Thanks in advance.
Sent from my Nexus 4 using xda premium
If you're getting as far as the starting apps dialog, you should be able to get a logcat of the boot process, which will go a long way in diagnosing the problem, and if it is recoverable.
I'm thinking either a framework file got corrupted, or even more likely, your data partition is corrupted and upon bootup, dalvik can't write to /data/dalvik-cache while attempting to "optimize" apps, and it therefore hangs.
This is all just conjecture of course, and I could be completely wrong, but a log will surely help.
JsChiSurf said:
If you're getting as far as the starting apps dialog, you should be able to get a logcat of the boot process, which will go a long way in diagnosing the problem, and if it is recoverable.
I'm thinking either a framework file got corrupted, or even more likely, your data partition is corrupted and upon bootup, dalvik can't write to /data/dalvik-cache while attempting to "optimize" apps, and it therefore hangs.
This is all just conjecture of course, and I could be completely wrong, but a log will surely help.
Click to expand...
Click to collapse
How would I pull the log cat? Also, is there a way I could salvage corrupted data?
Sent from my Nexus 4 using xda premium
nbeebe24 said:
How would I pull the log cat? Also, is there a way I could salvage corrupted data?
Click to expand...
Click to collapse
You need to stream the output of logcat via (assuming windows) your command prompt console using adb:
adb logcat > log.txt
Then upload the log.txt file for review. That's the best place to start and see what it says.
JsChiSurf said:
You need to stream the output of logcat via (assuming windows) your command prompt console using adb:
adb logcat > log.txt
Then upload the log.txt file for review. That's the best place to start and see what it says.
Click to expand...
Click to collapse
Okay I'll pull the log when I get home. Are you able to read those?
Sent from my Nexus 4 using xda premium
I've read a logcat or two in my day
Sent from my Nexus 4 using xda app-developers app
JsChiSurf said:
I've read a logcat or two in my day
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Do I have to wait until the cursor in the command prompt stops blinking to give you the log?
nbeebe24 said:
So I was playing Family Fued last night on my phone and pressed the home button. After doing so, my phone screen turned black and became unresponsive so I held the power button and rebooted. Upon booting the phone got stuck on the boot animation.
So I tried dirty flashing my ROM, gapps, and kernel. The phone booted then got stuck on the Starting Apps toast with a continuous progress wheel. I tried a combination of wiping caches and dirty flashing to no avail. I was running francos kernel with -75 UV, but flashed a kernel without UV to be sure. I'm still unable to get past the starting apps toast when I restore to the backup I made.
I just want to get it to boot so I can retrieve some important text messages. Any help is appreciated. Thanks in advance.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
The last time I was stuck in Starting APps, I did a factory data reset in Recovery Mode, and it worked.
Here's what I got so far http://pastebin.com/pf3b5gc8
opticaldh said:
The last time I was stuck in Starting APps, I did a factory data reset in Recovery Mode, and it worked.
Click to expand...
Click to collapse
That defeats the purpose of trying to recover my text messages. It boots fine from other back ups and fresh installs but not from the particular backup I started a thread about.
Sent from my Nexus 4 using xda premium
Titanium backup pro allows you to restore text message from android backups.
Not sure if the free version does it but I did find two other apps that are free that you can try.
1)app extractor (found on google play)
2) nand manager http://forum.xda-developers.com/showthread.php?p=35367320#post35367320
Sent from my Nexus 4 using xda app-developers app
Titanium or any other app, at this point, won't do any good at this point since the phone won't boot up all the way
The logs definitely show things look pretty FUBAR'ed. Though not optimistic, the first thing I'd try is to reboot to recovery and click 'fix permissions' via the 'Advanced' tab (assuming TWRP), and see if that does anything.
If that doesn't help any, and you don't care about trying to continue down the path of getting the ROM to boot, and all you do care about (mostly) is saving your text messages, assuming they are still there, what I would do is, from recovery, adb pull the data folder where the mms/sms/call log database is stored, do a full wipe, install a fresh rom, and then after first boot, reboot back to recovery and restore the data you pulled (this is all titanium is doing anyway).
You could even make a nandroid of your current bad setup if the above didn't work for some reason.
To get the current data for mms/sms/calls, first, reboot to recovery:
Code:
adb reboot recovery
Via your command prompt, make a directory in the same folder from where you are running adb, and then change into it, as follows:
Code:
mkdir com.android.providers.telephony
cd com.android.providers.telephony
Then, while still in recovery mode, pull your data:
Code:
adb pull /data/data/com.android.providers.telephony .
After you've successfully pulled your data, wipe the phone completely, install your new ROM, gapps, etc, and let it boot up completely, then reboot back to recovery again. Once back up in recovery, push the data back to the phone.
(make sure you are still inside the 'com.android.providers.telephony' directory you created via your command prompt)
Code:
adb push . /data/data/com.android.providers.telephony
That should restore you previous database, cache, etc.
Reboot the phone and cross your fingers
That's what I was essentially suggesting, but I didn't know how to manually do it.
From his current ROM that works he could use tb or the other two apps to restore just his SMS from his nandroid backup
Sent from my Nexus 4 using xda app-developers app
marsdta said:
That's what I was essentially suggesting, but I didn't know how to manually do it.
From his current ROM that works he could use tb or the other two apps to restore just his SMS from his nandroid backup
Click to expand...
Click to collapse
Problem is, he doesn't have a current ROM that works.
But, he could first wipe and install a fresh ROM all together, and then install Titanium, and use it to restore the above referenced data from a Nandroid.
Though, he'd FIRST have to/want to Nandroid the current bad ROM in order to make sure the nandroid has the most current data, else any new text messages would be lost since the previous nanadroid.
After doing all of that, it'd be much simpler/quicker to just follow the instructions provided above
All of this, of course, is based on bailing on the current ROM, but for the sake of challenge, I'd love to try and get it going as well, based on making changes and following the impact via logcat.
Well I feel dumb. I mixed up a couple threads that were talking about the same thing. Only in the other they did have a nandroid.
I should not be responding when I'm half asleep.
Edit - maybe I didn't mix up but its now I've only been up maybe for a bit. Had to drive brother to school. But reread his op and this caught my eye " I'm still unable to get past the starting apps toast when I restore to the backup I made."
So he does have a current nandroid of the bad ROM?
Sent from my Nexus 4 using xda app-developers app
marsdta said:
Well I feel dumb. I mixed up a couple threads that were talking about the same thing. Only in the other they did have a nandroid.
I should not be responding when I'm half asleep.
Click to expand...
Click to collapse
No worries, the concept / principle is still sound We're all here to help!
JsChiSurf said:
No worries, the concept / principle is still sound We're all here to help!
Click to expand...
Click to collapse
Now I'm getting "Error while restoring /system" when I try to restore my derped backup
nbeebe24 said:
Now I'm getting "Error while restoring /system" when I try to restore my derped backup
Click to expand...
Click to collapse
Why are you trying to restore your derped backup? Did you already wipe and update to a fresh ROM?
JsChiSurf said:
Why are you trying to restore your derped backup? Did you already wipe and update to a fresh ROM?
Click to expand...
Click to collapse
Yes, I'm already running a fresh install. I'm a little confused by your instructions above. Which setup am I pulling the telephony data from? The bad nandroid?
Sent from my Nexus 4 using xda premium
nbeebe24 said:
Yes, I'm already running a fresh install. I'm a little confused by your instructions above. Which setup am I pulling the telephony data from? The bad nandroid?
Click to expand...
Click to collapse
Last I read, you never got past the starting apps dialog, so all of my instructions are based on the fact that that's where you're at.
If you've already make a nandroid of the bad version and are up and running on a new ROM, this process changes.
In this case, what I would do is pull the the data partition nandroid file (in your TWRP/BACKUPS folder), "data.ext4.win", off of your sdcard, add the ".tar" extension (this is all these files are):
data.ext4.win.tar
Then open the above file with WinRAR, navigate to the same /data/data/com.android.providers.telephony/ folder referenced in my previous instructions and pull the content out of the .tar.
Then, go into recovery and use adb to push the contents of the "/data/data/com.android.providers.telephony" that you extracted from the .tar file and push back to your phone.
Or, if you use titanium, as mentioned above, you could try and extract it right out of the nandroid file directly while the new ROM is running.
I have a t-mobile g2 d801, I rooted then backed up my efs with freegee then installed nrg ROM. I decided to see if the restore efs would work so I used freegee to restore it. Then I flashed the latest stock rooted ROM and now I'm getting a reboot about 30 seconds after the Os boots a date my imei is gone. Please help
Sent from my SM-P600 using XDA Premium 4 mobile app
I can't give you specific help to fix this, but, I can advise that you make an extra backup of your EFS. Copy it off of your phone if possible. If not, just copy it to a different partition on your phone, so you have more than 1 copy in more than 1 place.
If you attempt to return to stock with T-Mobile flashing tool all the data on your phone will be erased. So moving a copy of the EFS backup off your phone is the first thing you want to do. If you can use ADB with the phone you can get a copy of it off your phone.
After that, I'd wait for someone with specific knowledge of this problem to assist you in fixing it. Assuming the backup of your EFS file is good, you will be able to fix your phone.
DornoDiosMio said:
I can't give you specific help to fix this, but, I can advise that you make an extra backup of your EFS. Copy it off of your phone if possible. If not, just copy it to a different partition on your phone, so you have more than 1 copy in more than 1 place.
If you attempt to return to stock with T-Mobile flashing tool all the data on your phone will be erased. So moving a copy of the EFS backup off your phone is the first thing you want to do. If you can use ADB with the phone you can get a copy of it off your phone.
After that, I'd wait for someone with specific knowledge of this problem to assist you in fixing it. Assuming the backup of your EFS file is good, you will be able to fix your phone.
Click to expand...
Click to collapse
thanks, i think the backup is still there but i dont know where freegee puts it.i am thinking if i can push the freegee apk to the rom i can restore from there, cane someone post a copy of freegee apk? also can someone tell me where freegee puts the backups. thanks
Ok, i found my where my backups are, any help on how to restore them would be great.
Sent from my SM-P600 using XDA Premium 4 mobile app
Freegee doesnt work, all i get is a blank white or black screen and then a reboot when i launch the app
Sent from my SM-P600 using XDA Premium 4 mobile app
JMM2009 said:
Freegee doesnt work, all i get is a blank white or black screen and then a reboot when i launch the app
Sent from my SM-P600 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm in the same boat. I have my efs1 and efs2 img files, but no idea what to do with them. Any help is sincerely appreciated.
Sent from my LG-D800 using Tapatalk
EDIT: Autoprime listed this method for restoring efs
autoprime said:
If flashable zip wasn't created or to manually restore efs img files run the following commands using adb shell while in recovery:
dd if=/sdcard/EFS_Backup/efs1.img of=/dev/block/platform/msm_sdcc.1/by-name/modemst1
dd if=/sdcard/EFS_Backup/efs2.img of=/dev/block/platform/msm_sdcc.1/by-name/modemst2
Click to expand...
Click to collapse
I tried that, but still have "0" as my imei. Perhaps this method could work for someone else in this thread?
freegee doesnt work, then you probably lost root
also try when wifi on
contact freegee maker with log. you may have found a bug.
try rooting again
Sent from my LG-D802 using xda app-developers app