Initial phone stats: DS Mod 1.55.531.3, hboot 1.45.0013, s-on/unlocked via HTC unlocker.
I'm trying to update my own phone to 1.63.531.2 via the PG59IMG.zip file found here, http://forum.xda-developers.com/showpost.php?p=17424340&postcount=24 , but I'm running into problems applying this update and keeping it after restoring a Nandroid backup. It would be a huge amount of work to set up my phone from square one, and I'd like to avoid the process if at all possible.
The steps I've followed (twice, now, with no joy) are the following:
* apply the update through the PG59IMG.zip
* flash CWM 5.0.2.7
* flash Superuser
* restore most recent Nandroid backup
* flash 1.63.531.2 boot image (for wi-fi fix)
And this puts me back at my starting point, with the 1.63.531.2 update not applied.
I know I'm going about this the wrong way, but I can't figure out the correct method to make this work. The fact that I flashed the DS Mod 1.55.531.3 ROM back after unlocking might have something to do with this, however, I just can't nail down why. Really could some help to make this work.
TIA for any suggestions --
--
KingCheetah
hey, real quick, after flashing the 1.63.531.2 update, instead of restoring your full nandoid of 1.55.531.3, go to 'advanced restore', choose that nandroid, and choose only 'restore data'. that will put all your apps and data onto the new update, rather than flashing you all the way back to what you had before.
you could also backup and restore your data with an app called Mybackup Root, or some people use Titanium Backup. I personally like using the advanced data restore in CWM, or else Mybackup.
Yogi, I thought your suggestion would be a smoking gun. However, I'm having the same problem as described in this thread: http://forum.xda-developers.com/showthread.php?p=25431819#post25431819
Might you have any suggestions for addressing the md5 problem? I'm coming up empty...
Thanks for your help --
--
KingChetah
yeah, come to think of it, I've had that problem before as well. did you try what xmc suggested? also, perhaps try the Modaco 4.0.0.9 version of CWM to do the advanced data restore... if my memory serves me, I have had more success overall with that version. unfortunately that's about all I got!
the other sugestion would be to flash your full nandroid, then use Mybackup Root to back everything up. then after updating, DL the app again and restore.
good luck and keep us posted!
yogi2010 said:
yeah, come to think of it, I've had that problem before as well. did you try what xmc suggested?
Click to expand...
Click to collapse
Yes, and for the backup I want to restore, all the md5s are the same between the files and what is listed in the nandroid.md5 file. So, the method XMC suggested really doesn't do anything.
yogi2010 said:
also, perhaps try the Modaco 4.0.0.9 version of CWM to do the advanced data restore... if my memory serves me, I have had more success overall with that version. unfortunately that's about all I got!
Click to expand...
Click to collapse
Hmm, okay, I'll give that a try. Weird that CWM 5.0.2.7 has this problem. Also frustrating.
yogi2010 said:
the other sugestion would be to flash your full nandroid, then use Mybackup Root to back everything up. then after updating, DL the app again and restore.
Click to expand...
Click to collapse
I'll keep this as the last resort, because I'd rather not have to download an app for just this purpose. Nandroid backups have served me fine so far. Call me a minimalist.
I'll try Modaco and see what happens. Thanks much for the idea to try.
--
King Cheetah
Sadness
Using Modaco didn't work. Although the Advanced Restore sees the file and appears to run successfully, it says it can't find a data.img file and an Android.img file, so it doesn't restore the info.
So, I guess it's down to trying Mybackup Root and see what happens. Getting tired of redoing this process over and over.
Why can't things "just work" in these situations?
--
KingCheetah
check the other thread....problems with restoring backup
---------- Post added at 05:11 PM ---------- Previous post was at 05:08 PM ----------
or actually...just flash the data.img through fastboot....its ten times easier
but the data.img in the same directory as adb and fastboot....then run the two commands with your phone in the bootloader
fastboot erase data
fastboot flash data data.img
xmc wildchild22 said:
or actually...just flash the data.img through fastboot....its ten times easier
but the data.img in the same directory as adb and fastboot....then run the two commands with your phone in the bootloader
fastboot erase data
fastboot flash data data.img
Click to expand...
Click to collapse
The problem with this is the file "data.img" doesn't exist in a Nandroid backup. As I stated in my previous message, the Advanced Restore process tossed up a message that the file didn't exist (which is correct).
The files within a given Nandroid backup folder are the following:
.android_secure.vfat.tar
boot.img
cache.ext4.tar
data.ext4.tar
nandroid.md5
recovery.img
system.ext4.tar
From the Advanced Restore problem thread (http://forum.xda-developers.com/showthread.php?t=1624319):
xmc wildchild22 said:
then take the system.img from the 1.63 update and put in replace of the nandroids one....then redo the md5 checksum for the system.img like i had showed before
Click to expand...
Click to collapse
I would love to try this, but since the 1.63 update is a PM59IMG.zip, I can't open it with a zip file manager--it throws up a "central directory not found" error. Unless there's another program besides 7zip that's needed to handle this type of zip file...
Edit: I just realized that, as you can see from the file list above, a Nandroid backup also doesn't have a "system.img" file--it has a "system.ext4.tar," but not "system.img." So being able to pull anything from a PM59IMG.zip file is a moot point at this juncture.
Banging one's head against the keyboard does little constructive good, but it's really tempting at this point --
--
KingCheetah
just try opening it with a plain windows explorer
xmc wildchild22 said:
just try opening it with a plain windows explorer
Click to expand...
Click to collapse
Using the "Explore" option from the right-click context menu in Windows Explorer gives the following error: "The Compressed (zipped) Folder is invalid or corrupted." (Since archive files on my laptop are associated with 7zip, this is the only method by which I can access Win XP's native archive file handling.)
This has been the case with all PM59IMG.zip files--they don't register as normal zip files.
Thanks for the suggestion, though --
--
KingCheetah
hmm...maybe tht zip is corrupted because it works for me....DL this --> http://tinyw.in/Mzg2
Nope, not corrupted because it works just fine to update my phone to 1.63 (as stated before, I've done this twice now). Also, that's the exact same source from whence I downloaded my copy of the file. The PM59MG.zip for 1.55.531.3 gives exactly the same error, and I used that without difficulty as well.
KingCheetah said:
Nope, not corrupted because it works just fine to update my phone to 1.63 (as stated before, I've done this twice now). Also, that's the exact same source from whence I downloaded my copy of the file. The PM59MG.zip for 1.55.531.3 gives exactly the same error, and I used that without difficulty as well.
Click to expand...
Click to collapse
Use winrar to open the PG59IMG.zip files - that's what I used to make all the custom ones with, and also what I used to open the leaked ones we started from.
You won't be able to edit existing leaked ones, because they are locked and have an HTC signature.
Sent from a digital distance.
Thanks for the pointer, Blue, and I'll keep this in mind. But as I added to my previous post (#8), I realized that a Nandroid backup doesn't have a "system.img" file--it has a "system.ext4.tar," but not "system.img." So being able to pull anything from a PM59IMG.zip file is a moot point at this juncture.
I think I'm going to have to wait for a 1.63 ROM that can be installed through CWM rather than the PM59IMG.zip method. The DS Mod 1.55.531.3 worked well for me, and all apps/data were just there after I flashed it. Maybe I just got lucky with the process I followed previously, who knows? (http://forum.xda-developers.com/showthread.php?t=1508406&page=4 post #39)
At any rate, I've got a truly mean headache from working on this all day. Time for a break with a bit of ice on ye old cervical vertebrae.
Thanks again for chiming in --
--
KingCheetah
No prob, didn't read through and shot from the hip on the last post I saw, out at dinner and skimming the forums on smoke breaks
Sent from a digital distance.
does anyone know the deal with the implementation of tar backups? I think that came into play at some point, and I wonder if that has anything to do with anything.
I just checked a backup I made with the Modaco CWM, and the files in it are all .img files, including data. and I know for a fact I have done backups and advanced data restores with that recovery. it would be a hassle, but if you get re-energized you might make the backup and do the restore with Modaco. definitely would be a hassle if it didn't work, but you could also make a backup with Mybackup, and have that ready too, as well as probably have a data.img to try and flash thru fastboot like xmc suggested.
anyway, hopefully we'll get this all sorted out. take it easy!
well .tar are used ever since cwm started working with ext4....maybe imgs are only ext3 or lower or its just inefficient
On that note, I did use the modaco 4.0.0.9 recovery to make the nandroids I pulled the system images from to get the bases from which I de-odexed, and when finished I uploaded to my host and they are the de-odexed bases I posted in dev.
I am pretty sure I went with modaco recovery for that because cwm 5.0.2.7 output tar files and it just saved a step in the process.
If you are working with the .tar files then jump on linux to unarchive them if that's what you are trying to do.
I just ran the deodex process using windows, because the first working deodex tool I found was a windows tool.
Generally I use modaco .9 for nandroids I want to work with in windows, and cwm 5 for nandroids I want to work with in linux.
We're probably leaving the restaurant soon, if we split up I'll actually read back through the thread when I get home and see if I have anything else to add.
Sent from a digital distance.
Yogi, you're brilliant!
yogi2010 said:
I just checked a backup I made with the Modaco CWM, and the files in it are all .img files, including data. and I know for a fact I have done backups and advanced data restores with that recovery.
Click to expand...
Click to collapse
[facepalm] Of course! This is why my Advanced Restore attempt with Modaco failed--because I used the CWM 5.0.2.7 backup, which did not have the files Modaco would have referenced. Duh! I wasn't even thinking along the lines of a file type mismatch between the two recoveries. Baka baka baka...
yogi2010 said:
it would be a hassle, but if you get re-energized you might make the backup and do the restore with Modaco. definitely would be a hassle if it didn't work, but you could also make a backup with Mybackup, and have that ready too, as well as probably have a data.img to try and flash thru fastboot like xmc suggested.
Click to expand...
Click to collapse
At this point, not a hassle, but the best chance to accomplish this thing with a minimum of fuss and bother. I'll give this a shot right after a bit 'o java. Thank you, Yogi, for highlighting something that should have been obvious to me when Modaco gave the error message that "data.img" didn't exist. Oy!
However, this still leaves unanswered the question of why CWM 5.0.2.7 is tossing up the md5 mismatch error when one tries to use Advance Restore, and that files aren't seen by CWM via Advance Restore until one accesses regular Restore. Paperskye is having the exact same problem in this thread: http://forum.xda-developers.com/showthread.php?t=1624319 . Should this be brought to the attention of the CWM devs? It really seems like a rather show-stopping error for CWM...unless Advanced Restore isn't really used with 5.0.2.7 and the MT4GS. There just doesn't seem to be a good reason for the observed behavior.
Many thanks for your encouragement. I'll report back with results on the next try with Modaco --
--
KingCheetah
It's a beautiful thing!
Using Modaco for my backup prior to the update, then Advanced Restore of data afterward = perfect restore of my phone environment with 1.63 on board. Done with as little fuss as I was hoping to encounter. Yogi, you get the prize. The only thing I had to manually put back was my custom boot animation, but that's trivial.
I think I'll just leave Modaco on as my recovery for now, since AR is functional with it and CWM 5.0.2.7 is not. Makes me wonder, from just an everyday backup standpoint, is there any real advantage of CWM over Modaco? I wish there was more information on how the recovery module functions on the CWM website--I'd like to read up on it for educational purposes. Guess I'll do a Google to find more.
So ridiculously happy right now. In a stew of things going wrong, at least something went right.
Big rumbling purr of gratitude --
--
KingCheetah
Related
This version is outdated, please get the latest version here: http://forum.xda-developers.com/showthread.php?t=459830
Hi,
In light of the fastboot flash method I was thinking of a way to be able to keep my current setup as a backup while i experiment with other images. For that I wrote a script that uses adb to dump the data for the boot, recovery, system and data partitions.
When this script is ran, it will dump these images in your current dir.
Boot into recovery mode (home+power) to use.
Requires RC30 v1.2 recovery.img - due to a bug the RC8 v1.2 there is no adb shell. (this script needs adb shell as root + busybox in recovery mode to work).
PLEASE NOTE: I haven't actually flashed the dumps back yet, I will be trying that tomorrow. Brave souls willing to test that do so at their own risk!
Bug reports or own improvements welcome.
infernix, how do i go about running this script from mac terminal?
Pretty interesting stuff.Two questions for you:
1. Where is the restore script...
2. Did you try restoring the created backup?
Thanks,
devsk
korndub said:
infernix, how do i go about running this script from mac terminal?
Click to expand...
Click to collapse
On MacOS 10.5 I had to compile md5sum from http://www.microbrew.org/tools/md5sha1sum/ and then modify the script to replace the call for md5sum --check --status with md5sum --check - --status (note the additional - to specify stdin). After that everything seemed to work properly. Haven't tried flashing it back, however.
nand?
what is nand?
i'm thinking this must be huge because its getting a lot of attention from the big dogs such as JF. from reading, is it like the master software so you can completely wipe the phone then in a sense put everything back on or is that too drastic of a guess?
just curious...
hbguy
http://tinyurl.com/6cb6k8
but in all seriousness NAND is just the flash memory upon which all the system software is installed. This script lets you take a full backup copy of all the various partitions and then, in theory, restore them.
very cool
This is a big advancement wish I had this when I pooched my market app trying to move the cache, I got it to d/l 1 app using the sd as my cache but nuthin but force close on a few dozen attempts, I dunno what I did but I couldn't get the onboard caches to work so I had to hard reset and d/l 33 apps from the market before I went to bed and I'm still fixing sh1t, this would have made my restore much easier, was suprised when I got it that there was no type of backup other than syncing with goog.
I can't wait to see who has the biggest balls and will try to flash one back.
Thanks, I bet the OTA RC30s will be rerooted pretty soon at thus rate.
This is a great contribution.
(Hey google, why not get some of these xda guys on the payroll, this is where all the news about the G1 gets made, I don't think I have seen any G1 hack yet that didn't have its roots right here at xda-dev)
Bhang
Stupid part is I'm so egocentric I think somebody at google/android is gonna read it...duh
Rogue XM Touch Recovery v1.5.0-R1
(CWM-based Recovery v5.0.2.8)
For the Asus Transformer TF101
First off, thank you to...
Team Rogue
Koush
CyanogenMod Team
j-r0dd
Solarnz
Roach2010
All I did slap together all their hard work to make it work on the TF101.
Sources
Rogue Recovery
The source and more info for Rouge Recovery is available in the Xoom release thread from Team Rogue. I have not made any modifications to it to work with the TF101. You can find that thread here:
http://forum.xda-developers.com/showthread.php?t=1235170
The discussion of the touch release in that thread begins here:
http://forum.xda-developers.com/showthread.php?t=1235170&page=13#123
Recovery Kernel
I used the kernel from Roach2010's ClockworkMod Recovery 3.2.0.1 release here:
http://forum.xda-developers.com/showthread.php?t=1213723
Device Tree
Mostly based on AOKP's TF101 device tree, just picked out the parts needed to compile the recovery. Particularly BoardConfig.mk:
https://github.com/rburrow87/android_device_asus_tf101_recoveryonly
Updates
[2012-05-25] 1.5.0-R1 (5028-based)
Updated to Rogue XM Recovery v1.5.0 which is touch-enabled with the same features as before. See the Xoom release thread for more information on Rogue Recovery:
http://forum.xda-developers.com/showthread.php?t=1235170
Can also finally use the boot to recovery option available in some ROMs thanks to the recovery boot loop fix from Roach2010 from here:
http://forum.xda-developers.com/showthread.php?t=1213723
Workaround for small menu targets
http://forum.xda-developers.com/showpost.php?p=26142147&postcount=151
If I can figure out a way to just make the menu items taller, I'll make an update. Otherwise I'm waiting for Rogue to implement it first.
[2012-01-14] 1.3.0-R1 (5027-based)
Original release, non-touch
Info
Mounting as USB storage does not work. (Accessing the tablet or SD card from your computer when plugged in via USB)
Installation
I tested this the best I could, but use at your own risk. I am not liable for data loss, spontaneous combustion, temporal anomalies, or anything in between.
Just flash the attached zip from CWM.
There's also an nvflash version that has the recovery.img in it and will only flash the recovery if you prefer that method. Or just so you don't have to unpack the blob file if you need the recovery.img.
Misc:
I did this because I thought it'd be nice to have a newer recovery for our TF101s, but also because I want to learn to do some sort of development even if it's just building for similar devices. I'm still new to using anything like git or using C/Java like this so don't expect miracles right away if bugs come up! I have some experience with other languages, but not in this kind of application.
Thank you, looks nice. Doing a nand backup right now with it.
there was someone in one of the ics threads, looking for this, they,ll be chuffed to bits.
Sent from my HTC Desire using XDA App
Cam you just rename this img if u wanna flash with nvflash?
Sent from my Dell Streak using Tapatalk
baseballfanz said:
Thank you, looks nice. Doing a nand backup right now with it.
Click to expand...
Click to collapse
Awesome!
will8578 said:
there was someone in one of the ics threads, looking for this, they,ll be chuffed to bits.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
I saw that post! I've been watching that thread and trying it out when there's an update.
80slovechild said:
Cam you just rename this img if u wanna flash with nvflash?
Sent from my Dell Streak using Tapatalk
Click to expand...
Click to collapse
To do that, you have to extract the zip and then unpack the blob file... but I updated the OP with an extra nvflash version that flashes just the recovery and gives you the recovery.img.
Finally...a relatively current back up for the TF!!
THANK YOU!!
Backing up with 3201, then installing this.
Beautiful work!! Works flawlessly!
Finally! A 5.x.x.x CWM recovery
Does this allow flashing from both internal and external?
On my Galaxy Nexus, they also have a touch softkey mod that has softkeys for up, down, back, and select. Not a big deal but something cool to look into if you get bored.
LTE EX Galaxy Nexus - CM9 AOKP
Asus Transformer - Revolver
Can we get a list of features? I've never flashd CWM 5.x.x.x so just curious, and would make a good addition I think..
luna_c666 said:
Can we get a list of features? I've never flashd CWM 5.x.x.x so just curious, and would make a good addition I think..
Click to expand...
Click to collapse
It's basically the same as 3207 with the ability to flash from and back up to internal memory.
And seems a bit more stable.
Worked for me. Way way way better color scheme and it booted quick! Thanks!
wackydroid said:
It's basically the same as 3207 with the ability to flash from and back up to internal memory.
And seems a bit more stable.
Click to expand...
Click to collapse
its definitely not the same as v3.x.... that being said however, simply look at the android_bootable_recovery github to see the differences since v3.x
I think with the latest versions its even possible to use the mount usb with the tablets own MicroSD card where-as in the v3.x tree it wasnt (thanks to v5.x's inclusion of dual mount support, specifically done to support devices with large internal storage)
Still, i have to agree with everyone else, its REALLY nice to finally see a v5.x CWM... using it on my HD2, Evo Shift, and HeroC, it really was a surprising difference from when I was sticking with v3.x
Just awesome!!! Thanks so much!
this needs to be moved to the dev section, but great job!
Sent from my Transformer TF101 using xda premium
Thanks! Installed successfully on two separate rooted B60 TF101's(ARHD 3.2, and Krakd 1.4.2)without any issues. Works great nice job!
New recovery works great!
Just flashed this without any issue. Nice look and feel. Are there more options available under the 'wipe' option, such as ability to wipe only cache or Dalvik cache like the 3.2.0.1 had? I haven't had a chance to look yet and didn't want to chance inadvertently wiping my device. Thanks.
[EDIT] I've now had time to look around and answer my own question. Yes, the other wipe options are there under the wipe menu item. Good to not see that sd card error all the time. So far it seems pretty flawless and better looking, too. I had to reflash my ROM last night and got to put it through it's paces.
Good job and thanks for carrying forward with recovery.
I did notice that at least on mine, I saw no 'connection' between the progress bar when doing a full advanced backup to the plugin SDCARD (normal backup as in the old days), or in other words, no sign of progress despite it working fine. I'm looking around the code to see what might have caused that.
The other interesting change not mentioned is that the backup file format/suffix is now .tar instead of .img. I tried using Titanium to restore an app from the backup with the .tar files, and it worked fine. Is .tar what the current versions of cwm are using?
Lastly: I know that to burn a kernel you have to use blobs on the tf101, so which .tar file contains the kernel blob? (I've not yet analyzed this yet and have assumed that you have to actually burn a kernel afterward to get one in place). What I was wondering is if we could get the equivalent of 'boot.img' from other v5 cwm's that are around, but I suppose ours would have to burn a blob rather than just unpack a .tar file.
EDIT: After reading through the original post about Rogue Recovery, I realized that in the last / prior release notes it mentioned this:
*Progress indication disabled by default again for speed (create /sdcard/clockworkmod/.hidenandroidprogress to enable progress)
Which took care of my initial gripe so check on off to me not reading enough ..
Thanks again --
I tested this by doing a full backup and restore. After the sucesfull backup, I then did the restore which it did restored from backup but wifi got broken and no way to turn was wifi on.
jwilliamf said:
I tested this by doing a full backup and restore. After the sucesfull backup, I then did the restore which it did restored from backup but wifi got broken and no way to turn was wifi on.
Click to expand...
Click to collapse
I also did a back up and restore and my Wifi is fine.
I did not do the advance backup just the regular backup.
Someone else reported this wifi problems using Roach's 3.2.0.1 CWM also.
jwilliamf said:
I tested this by doing a full backup and restore. After the sucesfull backup, I then did the restore which it did restored from backup but wifi got broken and no way to turn was wifi on.
Click to expand...
Click to collapse
Hmm, weird, I'm not sure why the recovery would break that unless it's failing to restore something or possibly failed to back something up. I did several backups and restores when I was checking to see if everything worked and never encountered that. Maybe try restoring the one giving your trouble a couple of times to see if it comes back?
hachamacha said:
Good job and thanks for carrying forward with recovery.
I did notice that at least on mine, I saw no 'connection' between the progress bar when doing a full advanced backup to the plugin SDCARD (normal backup as in the old days), or in other words, no sign of progress despite it working fine. I'm looking around the code to see what might have caused that.
The other interesting change not mentioned is that the backup file format/suffix is now .tar instead of .img. I tried using Titanium to restore an app from the backup with the .tar files, and it worked fine. Is .tar what the current versions of cwm are using?
Lastly: I know that to burn a kernel you have to use blobs on the tf101, so which .tar file contains the kernel blob? (I've not yet analyzed this yet and have assumed that you have to actually burn a kernel afterward to get one in place). What I was wondering is if we could get the equivalent of 'boot.img' from other v5 cwm's that are around, but I suppose ours would have to burn a blob rather than just unpack a .tar file.
EDIT: After reading through the original post about Rogue Recovery, I realized that in the last / prior release notes it mentioned this:
*Progress indication disabled by default again for speed (create /sdcard/clockworkmod/.hidenandroidprogress to enable progress)
Which took care of my initial gripe so check on off to me not reading enough ..
Thanks again --
Click to expand...
Click to collapse
Looks like somewhere around CWM 4 is when the switch to tar was made. It has better the speed along with the ability to back up and restore the correct filesystem. Sounds like the progress thing was added somewhere around then as well.
[ Found here: https[colon]//plus.google[dot]com/103583939320326217147/posts/G4VQuCpR25y Sorry, can't make outside links yet. ]
Looking at a kernel zip, it uses dd to put the blob in /dev/block/mmcblk0p4, which is also where the recovery goes... I clearly need to learn more about what's going on here when flashing a kernel or recovery to the same thing and what the function of the blob is.
Looking in the nandroid backuip system tar though, it grabs the /system/lib/modules folder which some kernel zips add to, so the nandroid is backing that up. I'm not sure if nandroid, at least in its current state, is able to back up or restore the kernel itself because of the whole blob thing?
Hmm, perhaps I should make a feature list instead of just saying look at the Xoom release thread!
This is a general CWM question but I could not find any place better to post on XDA, so excuse this if incorrect location.
I have flashed all the Skyrocket ICS roms in the past few days to see which I liked best. Before I flashed a new one, I would make a CWM backup of the current one. Wanting to easily be able to identify the files, I appended the rom name to the end of the CWM filenames after deleting all the characters after the date, which appeared to be a GMT time stamp. Now, when I try to restore any of those files, I get an MD5 checksum error. I am only assuming that this is due to changing the filename and not some other problem. Anyone have any ideas on how to fix this? TIA.
phoneturf said:
This is a general CWM question but I could not find any place better to post on XDA, so excuse this if incorrect location.
I have flashed all the Skyrocket ICS roms in the past few days to see which I liked best. Before I flashed a new one, I would make a CWM backup of the current one. Wanting to easily be able to identify the files, I appended the rom name to the end of the CWM filenames after deleting all the characters after the date, which appeared to be a GMT time stamp. Now, when I try to restore any of those files, I get an MD5 checksum error. I am only assuming that this is due to changing the filename and not some other problem. Anyone have any ideas on how to fix this? TIA.
Click to expand...
Click to collapse
Are you talking about the folder name? Because that shouldnt affect it. Inside the folder that is created for each backup, there are backup files which dont have any dates/times in the filename itself.
I vaguely remember reading about this, but I can't recall how it was resolved. Try updating your can to 5.5.0.4 Touch or 5.8.1.3 (?? something along those lines) and seeing if that resolves it. Outside if that I must ask the obvious, did u Google "md5 checksum error cwm"?
Are you using the same CWM version as you did when you backed up? If you didnt, then thats one reason. You have to stay on the same CWM version, many of these CWM versions floating around have different fixes in there.
One way around this is to go to Advanced Restore and restore all the IMG files from there.
Dixit
ihtfp69 said:
I figured I would post this fix here in case anyone else ran into this problem. This is assuming you did not change the folder names and let Clockworkmod create them. I haven't had it happen until today, but it's not a nice message to see when you are trying to do a restore.
Code:
Checking MD5 sums...
MD5 mismatch!
Do this to fix:
To fix this problem use the code below. Substitute the final folder name for the backup you need to fix.
Code:
adb shell
# cd /sdcard/clockworkmod/backup/2010-06-29.20.22.53
# rm nandroid.md5
# md5sum *img > nandroid.md5
When that finishes, re-run the restore and everything should be fine.
NOTE: As rpearl stated, there could be something really wrong with your nandroid, so use this tutorial as a learning experience and not a fix-all. In my case, everything was fine after restoring. However, that may not always be the case. Do this with caution.
Click to expand...
Click to collapse
Use this method to potentially fix.
dixit said:
Are you using the same CWM version as you did when you backed up?
Dixit
Click to expand...
Click to collapse
That is correct on most of them. I updated to CWM Touch for the last one, but it did not restore either. To check this out, I just did a backup and without changing the name did a restore and it worked fine. The thing that was odd in the backups that would not restore was that it immediately bombed out of the checksum each time as if it was checking the name itself first.
That is brilliant. I did not realize you could generate the MD5 from ADB and stick it right into the folder. Thanks!
The few times this md5 mis-match has happened to me was because (a) the backup was actually messed up (check folder size) probably due to corruption or (b) my SD card was out of space. I've always renamed my backup set similar to yours (I append the ROM name) and it never affects the restore.
bdbx18 said:
The few times this md5 mis-match has happened to me was because (a) the backup was actually messed up (check folder size) probably due to corruption or (b) my SD card was out of space. I've always renamed my backup set similar to yours (I append the ROM name) and it never affects the restore.
Click to expand...
Click to collapse
Are you using touch or standard CWM? I wonder if this only happens in touch version. I will try this in the next few days.
I changed the name of one of the backups I created with CWM touch and it restored fine using touch. I suppose my earlier problem may have been trying to restore a backup created with old CWM using touch version.
well since you are on the subject cwm touch im making a nanadroid backup of my current ics rom right now as i speak. i started about an hour ago and its still on the backing up data part. when i used the older version to make backups i dont remember it taking this long. have any of you had cwm touch take well its been a little over an hour now? i do have more apps on my phone now than i did the last time i made a backup would that matter? should i just jerk the battery out and go back to the older version of cwm i was using? thanks ahead of time for any advice / help you may give i would appreciate it. im trying to backup this rom cause i want to flash a different modem cause the ics modem form the leak is crap and need a backup in case it dont work..
garydv2002 said:
well since you are on the subject cwm touch im making a nanadroid backup of my current ics rom right now as i speak. i started about an hour ago and its still on the backing up data part. when i used the older version to make backups i dont remember it taking this long. have any of you had cwm touch take well its been a little over an hour now? i do have more apps on my phone now than i did the last time i made a backup would that matter? should i just jerk the battery out and go back to the older version of cwm i was using? thanks ahead of time for any advice / help you may give i would appreciate it. im trying to backup this rom cause i want to flash a different modem cause the ics modem form the leak is crap and need a backup in case it dont work..
Click to expand...
Click to collapse
If you are using sk8erwitskil version of the CWM touch (ClockworkMod TOUCH 5.5.0.4 v3.5) then most likely you didnt follow one of the directions on the front page. This is a known issue. Here it is again. You need to create that file on the location you backing upto.
For CWM to recognize the .hidenandroidprogress file you need to boot into CWM and go to mounts and storage>>mount /sdcard then go back to backup & restore and make a restore and it should work everytime (as long as you do the steps in that order and you have the .hidenandroidprogress file in /sdcard/clockworkmod & /sdcard/external_sd/clockworkmod folders)
There is a known bug in ClockworkMod 5.5.0.4 that long file names can POSSIBLY cause backups to hang. There is a solution/workaround:
•boot into recovery
•try to make a backup (no matter if it passes or fails proceed to next step)
•either through terminal emulator or through adb run the following command EXACTLY:
Code:
touch /sdcard/clockworkmod/.hidenandroidprogress
•if you are backing up to external sdcard then run the following:
Code:
touch /sdcard/external_sd/clockworkmod/.hidenandroidprogress
im using 5.8.1.3 hercules that i got from the dev section. is this a known issue with it to?
garydv2002 said:
im using 5.8.1.3 hercules that i got from the dev section. is this a known issue with it to?
Click to expand...
Click to collapse
Not sure, I used that for awhile but then went back to the other touch and Ive had those two files still in my directories.
I would go ahead and create those two files (one for internal SD and one for external SD if you got one you are using that is) and try it again. Make sure you call that file exactly the way it is, or copy/paste the code identically if you do it through ADB.
Dixit
garydv2002 said:
im using 5.8.1.3 hercules that i got from the dev section. is this a known issue with it to?
Click to expand...
Click to collapse
I use that one, takes less than 5 minutes on my class 10 sd.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Well the crazy thing is after sitting there over an hour waiting I finally took out the battery and even though it never said complete all the files are there but I still don't trust that it made a good backup so I deleted those files tried putting in the code above and it still would not work so I flashed back to version 5.0.2.0 thats not touch and it made a perfect backup in under 2 minutes. Might be one of those it just ain't gonna work right on this specific phone thing or it could be the little green gremlins at it again lol... who knows.. I'll just wait for new version of touch to come along and try it. It won't be long till a newer greater version comes along as fast as technology is going today.. thanks for the help. I'm learning more and more each day from you guys on xda.....
Sent from my SAMSUNG-SGH-I727 using XDA
Not sure if this is the cause of the issue but for nandroid backups you can't make a folder name with spaces otherwise you will get an md5 sum error. Try renaming the folder with underscores instead of spaces
Hello,
I thought of myself as a pretty experienced user, but you never learn enough!
However, I flashed some roms (lollipop) that, probably due to my mistakes, screwed up my file system, to the point that my recovery (latest PhilZ) wasn't able to find its backup anymore. Eventually I solved the problem as I was able to find my backups and use them to revert my phone to the rom I wanted to run (Carbon 4.4.4). But I was really annoyed by the fact that my file system was a bit off and still I was having problems with the recovery. So I decided to begin investigating the possibility to restore my phone to factory default. Before going with it, I tried the soft approach, i.e. I used the soft factory reset available from the settings menu. It all seemed fine and I re-flashed a lollipop rom that suited me.
Now the problem is that, after all the ordeal, I decided to make a new backup and so I did. It appears all fine, my recovery can actually "see" it, but I cannot identify it using a root browser! It seems to have disappeared unless I open the recovery and then I see it there. It is located in a folder that I can, of course, access, but,when I do so, I can't find the file!
I tried to put on my phone an old backup (always a PhilZ one), but when I try to put it on the phone I can't find the Backup folder in the Clockworkmod folder!
Anyone has any idea of what is going on and can give me a suggestion on how to overcome the problem?
Thanks
Luca
PS An alternative would be suggesting how to do a restore from a sideload: I thought I saw a similar option, but I can't seem to find it anymore within the recovery's options! I tried also restoring via NRT, but although all seem to go fine and the software return no failure notice, I can't find the backup file that should have been pushed (successfully) on my device!
Its not a recovery issue. Its an L issue.
Best thing to do would be to wipe data and storage then fastboot flash userdata.IMG
http://forum.xda-developers.com/showthread.php?t=2938749
rootSU said:
Its not a recovery issue. Its an L issue.
Best thing to do would be to wipe data and storage then fastboot flash userdata.IMG
http://forum.xda-developers.com/showthread.php?t=2938749
Click to expand...
Click to collapse
Thanks a lot for your help.
How can I find the img. file to flash?
Would it be ok to just go ahead and start from 0 using this:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
How can fastboot flash an image file? I've never done that before! As I said, been doing this for a while, but never done this before...I think!
Luca
Alas, after reading your post on one-click toolkits, I'm afraid I'm one of those who thinks they can do things, but rely on simple tools to do them. However, I never (almost never) forgot to make a nandroid backup before flashing a new rom and, to be honest, I'm not a flashoolic. I never, ever bricked my phone (got a few bootloops). If I find a rom that suits my need, I stick with it for as long as I can.
The changes between KK and L are such that are beyond my comprehension, but I try hard to solve the problems I have without bugging everyone at the first obstacle. But now, after fidgeting with my phone for 2 days, I had to give up. With a few words, you singled out the reason why I couldn't come on top of this: things change and I was not informed of how much they did!
Luca
Problem partially solved..I think! Now I can see the folder and found my backup!!
I used the restorecon command you suggested. I couldn't make it work using terminal emulator (just did not accept the su command: why I don't really know). Then I thought about using adb shell via pc and, I really surprised myself; I was able to pull it through. I'm not totally brain damaged as I felt when I couldn't even reproduce the command you indicated. It is probably the application that doesn't work. It was my first time with adb shell, so a new thing learned.
However, now I would like to ask you: if I place in the proper folder the backup folder I saved on my pc, will I be able to restore the nandroid backup? I just need some data that I forgot (trivial things, such as text messages and a few app data, like passwords and stuff) but it would be useful.
Thanks once more for your help.
Luca
So I tried my first Nandroid backup today using TWRP and a howtogeek - "How to Back Up and Restore Your Android Phone with TWRP" guide I found off a quick google search.
Basically TWRP, backup(boot,system,data), reboot to android, shut down, twrp-restore then reboot.
When I would reboot after TWRP-restore, it shows the typical bootloader corrupt error msg.
Shuts down again, shows the bootloader msg, then goes into TWRP, asks for my decrypt password, then begins to run an openrecovery script (I think?) of some sort. I then go to reboot my phone again, bang factory reset mode.
I hope I'm not alone here.:cyclops: I'd just really love to be able to backup/image my phone entirely so I can try out a few custom roms, and for general knowledge sake.
thanks!:silly:
mark7807 said:
So I tried my first Nandroid backup today using TWRP and a howtogeek - "How to Back Up and Restore Your Android Phone with TWRP" guide I found off a quick google search.
Basically TWRP, backup(boot,system,data), reboot to android, shut down, twrp-restore then reboot.
When I would reboot after TWRP-restore, it shows the typical bootloader corrupt error msg.
Shuts down again, shows the bootloader msg, then goes into TWRP, asks for my decrypt password, then begins to run an openrecovery script (I think?) of some sort. I then go to reboot my phone again, bang factory reset mode.
I hope I'm not alone here.:cyclops: I'd just really love to be able to backup/image my phone entirely so I can try out a few custom roms, and for general knowledge sake.
thanks!:silly:
Click to expand...
Click to collapse
What version of TWRP have you been using? I understand, RC2 has issues with properly restoring a backup. (RC is release candidate and is not considered fully stable, however, works well enough to flash custom roms and such).
The partitions on the pixel are set up in a more complex way than previously seen on many android phones, which is why there's no perfectly stable version of TWRP yet. You could try using RC1 to see if you get better luck backing up and restoring, however, you should assume that you may run into other issues and be prepared to deal with them should they arise.
exad said:
What version of TWRP have you been using? I understand, RC2 has issues with properly restoring a backup. (RC is release candidate and is not considered fully stable, however, works well enough to flash custom roms and such).
The partitions on the pixel are set up in a more complex way than previously seen on many android phones, which is why there's no perfectly stable version of TWRP yet. You could try using RC1 to see if you get better luck backing up and restoring, however, you should assume that you may run into other issues and be prepared to deal with them should they arise.
Click to expand...
Click to collapse
I'm running 3.1.0-0RC2 so maybe I'll try RC1. Normally I'd just go off and try everything but unfortunately I'm not in a situation I can simply play with my Pixel and potentially brick it leaving me without a phone for who knows how long.
I don't think there would be any harm with playing with RC1 but I'll research a little bit more into it and see what I can find out first. I heard the partitions are split for redundancy(?) for firmware upgrades and dual-booting. That's something all else on it's own as I've REALLY wanted to get my phone ultimately on a Multi-Rom setup but it seems way too complicated for me at the moment to try on my own even though I'm generally good with this stuff..
Thanks exad for the insight. Any other help is greatly appreciated.
mark7807 said:
I'm running 3.1.0-0RC2 so maybe I'll try RC1. Normally I'd just go off and try everything but unfortunately I'm not in a situation I can simply play with my Pixel and potentially brick it leaving me without a phone for who knows how long.
I don't think there would be any harm with playing with RC1 but I'll research a little bit more into it and see what I can find out first. I heard the partitions are split for redundancy(?) for firmware upgrades and dual-booting. That's something all else on it's own as I've REALLY wanted to get my phone ultimately on a Multi-Rom setup but it seems way too complicated for me at the moment to try on my own even though I'm generally good with this stuff..
Thanks exad for the insight. Any other help is greatly appreciated.
Click to expand...
Click to collapse
I would say use RC1 too. I've used it and never had a problem with it other than the occasional failure to decrypt which is no big deal. Just reboot back into recovery. I would add though, instead of backing up system, backup system image. Also vendor image. If you back up system instead of system image you'll more than likely run into battery drain problems. I'm not sure what causes it but it'll cut your battery life down to only several hours. Using system image doesn't cause that problem.
If you should happen to accidentally backup system instead of system image it's not a huge deal to fix it though. If you're on stock just download the factory image that you are currently on, extract the system.img file and flash it using fastboot. If you're on a custom rom, a dirty flash of the rom will fix it.
mark7807 said:
I'm running 3.1.0-0RC2 so maybe I'll try RC1. Normally I'd just go off and try everything but unfortunately I'm not in a situation I can simply play with my Pixel and potentially brick it leaving me without a phone for who knows how long.
I don't think there would be any harm with playing with RC1 but I'll research a little bit more into it and see what I can find out first. I heard the partitions are split for redundancy(?) for firmware upgrades and dual-booting. That's something all else on it's own as I've REALLY wanted to get my phone ultimately on a Multi-Rom setup but it seems way too complicated for me at the moment to try on my own even though I'm generally good with this stuff..
Thanks exad for the insight. Any other help is greatly appreciated.
Click to expand...
Click to collapse
RC1 and backup system image, vendor image, data and boot.
robocuff said:
I would say use RC1 too. I've used it and never had a problem with it other than the occasional failure to decrypt which is no big deal. Just reboot back into recovery. I would add though, instead of backing up system, backup system image. Also vendor image. If you back up system instead of system image you'll more than likely run into battery drain problems. I'm not sure what causes it but it'll cut your battery life down to only several hours. Using system image doesn't cause that problem.
If you should happen to accidentally backup system instead of system image it's not a huge deal to fix it though. If you're on stock just download the factory image that you are currently on, extract the system.img file and flash it using fastboot. If you're on a custom rom, a dirty flash of the rom will fix it.
Click to expand...
Click to collapse
TheBurgh said:
RC1 and backup system image, vendor image, data and boot.
Click to expand...
Click to collapse
Thanks again guys,
I ran a
fastboot boot twrp.zip to boot to what I thought was like a "live cd" version of twrp
with the rc1 .img and .zip in the sdcard directory I installed the .zip
booted my phone and it forces to recovery everytime now.
did I upset something?
I mean at this point, I could factory reset the google pixel all from the very beginning of time. boot/system the whole shabang, but I think this could be a good lesson from me if I could boot back to system out of this..
Okay. I have RC1 on here and have backed up to USB. I'm extremely tired and going to bed. I'll report back on how the restore goes. THANK YOU ALL!!!
mark7807 said:
Thanks again guys,
I ran a
fastboot boot twrp.zip to boot to what I thought was like a "live cd" version of twrp
with the rc1 .img and .zip in the sdcard directory I installed the .zip
booted my phone and it forces to recovery everytime now.
did I upset something?
I mean at this point, I could factory reset the google pixel all from the very beginning of time. boot/system the whole shabang, but I think this could be a good lesson from me if I could boot back to system out of this..
Okay. I have RC1 on here and have backed up to USB. I'm extremely tired and going to bed. I'll report back on how the restore goes. THANK YOU ALL!!!
Click to expand...
Click to collapse
Okay so, I stayed up a little late and tried a restore. I got this error near the end of the restore "extractTarFork() process ended with error: 255" in which resulted in corruption of files and a failed restore. Was I supposed to unmount data? Is there any reason I can't backup all partitions?
mark7807 said:
Okay so, I stayed up a little late and tried a restore. I got this error near the end of the restore "extractTarFork() process ended with error: 255" in which resulted in corruption of files and a failed restore. Was I supposed to unmount data? Is there any reason I can't backup all partitions?
Click to expand...
Click to collapse
Not sure where to direct you at this point. I have always used RC1 and backed up system image, vendor image, data and boot and never had a problem restoring. Someone with better knowledge will come around.
TheBurgh said:
Not sure where to direct you at this point. I have always used RC1 and backed up system image, vendor image, data and boot and never had a problem restoring. Someone with better knowledge will come around.
Click to expand...
Click to collapse
Yeah very strange I did exactly what you told me to do as well. Any changes to partitions I backup if my phone is rooted by chance??
mark7807 said:
Yeah very strange I did exactly what you told me to do as well. Any changes to partitions I backup if my phone is rooted by chance??
Click to expand...
Click to collapse
Not that I am aware of. Mine is rooted and backups have been smooth sailing.
I recently attempted creating a nandroid backup via TWRP on my rooted Pixel and I'm consistently getting an error: 'cannot create [path]\backup file" message from TWRP. Is there a permission issue that I've overlooked here or does anyone have any thoughts as to why my rooted Pixel would be denying TWRP authority to create the backup?
Thanks
What version of twrp ?
I only use rc1, never seen this.
Yep- RC1. I'm thinking it's in 'read only' mode or something because as soon as it attempts to create the folder/file- no-go.
pstgh said:
Yep- RC1. I'm thinking it's in 'read only' mode or something because as soon as it attempts to create the folder/file- no-go.
Click to expand...
Click to collapse
When you boot into TWRP did it ask for your unlock PIN? If it doesn't/didn't, either keep rebooting into recovery or turn the phone off and go back into recovery until TWRP does ask for your encryption PIN. Sometimes TWRP doesn't ask, and without the PIN being entered, it can't write to the internal storage.
If you click "Install" in TWRP and see a bunch of gobbledygook it's because the internal storage is still encrypted so TWRP can't do anything with it.
You could probably use USB OTG through the USB-C connector, though, to do a backup to it, if you need to.
Tried it again and it worked flawlessly.... it seems sort of buggy in that sometimes it presents the 'pattern' security lock that I use and sometimes it doesn't. After booting up in the bootloader and fastbooting the TWRP boot image slowly and methodically, the security pattern came up and all is perfect- thanks.
---------- Post added at 08:37 PM ---------- Previous post was at 08:36 PM ----------
Now I'm wondering how to best move that backup folder (or a copy of it) over to Google Drive? I have root explorer, but not sure if it is capable of mounting to Google Drive.. any thoughts on best practices here would be appreciated.
Thanks
pstgh said:
Tried it again and it worked flawlessly.... it seems sort of buggy in that sometimes it presents the 'pattern' security lock that I use and sometimes it doesn't. After booting up in the bootloader and fastbooting the TWRP boot image slowly and methodically, the security pattern came up and all is perfect- thanks.
---------- Post added at 08:37 PM ---------- Previous post was at 08:36 PM ----------
Now I'm wondering how to best move that backup folder (or a copy of it) over to Google Drive? I have root explorer, but not sure if it is capable of mounting to Google Drive.. any thoughts on best practices here would be appreciated.
Thanks
Click to expand...
Click to collapse
I can't confirm since I've yet to do a successful backup but... Flashify Pro version looks like an option???
also
Anyone know when TWRP 3.1.0-0 will be out for Pixel? Looks like it addresses boot slots which off first glance seems like quite a fundamental feature no?
Thanks... I'm thinking I'll just adb pull the file over to my desktop... not sure.
pstgh said:
Thanks... I'm thinking I'll just adb pull the file over to my desktop... not sure.
Click to expand...
Click to collapse
Root Explorer does have support for Google Drive. In Root Explorer touch the plus sign in the lower right corner and in the menu that opens choose Google Drive tab.
Can get Root Explorer to connect to Google Drive, but when I select all of the backup files from my Pixel's TWRP backup folder, my only choices are to cut or copy them- so I tried both and then RE creates this little clipboard icon that you presumably click on to paste them once you've opened the proper GD folder.... so I tried that and in both cases (cut and copy) it says 'fail'.... ? Thoughts? I've given RE permission to manage folders and files in GD.
pstgh said:
Can get Root Explorer to connect to Google Drive, but when I select all of the backup files from my Pixel's TWRP backup folder, my only choices are to cut or copy them- so I tried both and then RE creates this little clipboard icon that you presumably click on to paste them once you've opened the proper GD folder.... so I tried that and in both cases (cut and copy) it says 'fail'.... ? Thoughts? I've given RE permission to manage folders and files in GD.
Click to expand...
Click to collapse
It sounds like you've got the right idea. Cut will move the files, copy will do just that. You choose one of the two and browse to the Google Drive tab, find the folder you want to use and then use the little clipboard thing to transfer the files to that folder. If that's what you're doing, the only thing I can think of right off the top of my head would be that you don't have enough space left on Google Drive for the size of the files you're trying to transfer. Try a picture or something and see if it takes that. If so, I'd suspect lack of Drive space is the reason it fails.