Related
i am using NfiniteFx45 stock ROM De-odexed (Hero.C.Sprint_2.27.651.6-3.A2SD.2.7U-3_signed) i updated to Recovery RA 1.6.2 so i can backup nandroid + ext. (I saw instructions that said to update to RA 1.6.2 if you had an earlier version, so I did. now everytime i try to do a nandroid backup + ext i get error: run 'nandroid-backup.sh' in adb. when i open command prompt and run nandroid-backup.sh it says i have to list a command {-b{--backup etc. thats where im lost. dont know how to enter it i entered -b (didn't work) entered --backup (didn't work). can someone assist me please?!?
I am using a2sd also.
I don't think you can do the nandroid+ext with amon ra recovery. Try just a standard nandroid.
You could also try clockwork mod recovery.
Sent from my HERO200 using XDA App
Try putting the recovery img on the root of your SD card ( make sure to name it properly ) power down ur device then reboot into recovery holding the home and power button then plug your phone into ur computer/laptop then from adb reflash the recovery might work for you good luck
Root-Hack-Mod-Always™
if that doesn't work i would strongly suggest ClockworkMod Recovery. I've been using it for months now with no problem.
First I would suggest posting in the right section. This is a question and rules say don't post questions in this section. Its a very huge thread posted above saying this.
Don't be lazy next time and read rules.
But I would suggest clockwork mod recovery.
Sent from my HERO200 using XDA App
Thanks guys, even the forum cop.
Sent from my HERO200 using XDA App
t12icky0 said:
First I would suggest posting in the right section. This is a question and rules say don't post questions in this section. Its a very huge thread posted above saying this.
Don't be lazy next time and read rules.
But I would suggest clockwork mod recovery.
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
I will next time
Clockwork Mod = Fail
Did u try what I suggested it might work?
Root-Hack-Mod-Always™
bodyshop said:
i am using NfiniteFx45 stock ROM De-odexed (Hero.C.Sprint_2.27.651.6-3.A2SD.2.7U-3_signed) i updated to Recovery RA 1.6.2 so i can backup nandroid + ext. (I saw instructions that said to update to RA 1.6.2 if you had an earlier version, so I did. now everytime i try to do a nandroid backup + ext i get error: run 'nandroid-backup.sh' in adb. when i open command prompt and run nandroid-backup.sh it says i have to list a command {-b{--backup etc. thats where im lost. dont know how to enter it i entered -b (didn't work) entered --backup (didn't work). can someone assist me please?!?
I am using a2sd also.
Click to expand...
Click to collapse
Most times when you get that error, it means there isn't enough space on your SD card to make the backup. Do you have at least 300 MB free on your card? You may even need more than that if you are trying to do nand + ext. That could possibly be the reason for your error if you don't have enough space.
I got the same error before I updated to Darch's Amon RA 1.7
http://darchroms.pocketdevelopers.com/recoveries/RA-Darchstar.img
chromiumleaf said:
Most times when you get that error, it means there isn't enough space on your SD card to make the backup. Do you have at least 300 MB free on your card? You may even need more than that if you are trying to do nand + ext. That could possibly be the reason for your error if you don't have enough space.
Click to expand...
Click to collapse
yes second that one actually...i had only 200mb free from having 2 nandroids on my sd card..deleted one and had around 375mb and it worked great. must have 300mb in order for all the Temp folders/files to work.
add144 said:
I got the same error before I updated to Darch's Amon RA 1.7
http://darchroms.pocketdevelopers.com/recoveries/RA-Darchstar.img
Click to expand...
Click to collapse
My fav. recovery so far, but I'm using Darch's Godspeed now because he recommended it for Darktremor a2sd.
I usually get that error when I try to nand +ext, with full batt and lotsa memory on card and in phone. I've gotten it simply nand-ing w/ low batt too. I've put it down to a lack of understanding regarding Darktremor and a2sd in general.
With NFX Hero I get constant "android media" f.c.s and have no access to much of anything on sd. Usually run one of Darch's cm6s.
Ezintn said:
My fav. recovery so far, but I'm using Darch's Godspeed now because he recommended it for Darktremor a2sd.
I usually get that error when I try to nand +ext, with full batt and lotsa memory on card and in phone. I've gotten it simply nand-ing w/ low batt too. I've put it down to a lack of understanding regarding Darktremor and a2sd in general.
With NFX Hero I get constant "android media" f.c.s and have no access to much of anything on sd. Usually run one of Darch's cm6s.
Click to expand...
Click to collapse
Drarch's 1.7 amon RA is slightly newer than Godspeed, ad it's also overclocked. I'd check it out, it's pretty good IMO
So can a nandroid + ext backup be done with RA 1.5.2? Thats the only reason i even changed the Recovery to RA 1.6.2 because this post http://forum.xda-developers.com/showpost.php?p=7054986&postcount=7 Said you needed to switch to 1.6.2 id you didnt have it. I just want to upgrade my SDcard from 2GB to 8GB.
Just make sure you have more then 30% battery and decent space left on your SD card. Sometimes recoverys are corrupt but rarely. I use clockwork recovery. Don't freak either lol. You should have a working backup on your comp ^_^
Sent from my HERO200 using XDA App
theimpaler747 said:
Drarch's 1.7 amon RA is slightly newer than Godspeed, ad it's also overclocked. I'd check it out, it's pretty good IMO
Click to expand...
Click to collapse
Switching back, thanks!
Ezintn said:
Switching back, thanks!
Click to expand...
Click to collapse
No problem, let me know if you need any more help
feefeeboomboom said:
Just make sure you have more then 30% battery and decent space left on your SD card. Sometimes recoverys are corrupt but rarely. I use clockwork recovery. Don't freak either lol. You should have a working backup on your comp ^_^
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
OK so i was trying to switch recoverys for nothing. I figured if there was the option for nandroid backup + ext on the recovery then it should work. I mean i don't think developers would put an option that doesn't work, they'd just omit it right? Im still kind of new and this post says u need RA 1.6.2, if you dont have it get it. that's why i thought it wouldn't work. They should update that information.
Nand+ext 2 or 3 times w/ Darch's RA 1.7, no errors - thanks theimpaler747!
Often I can avoid old data by checking post dates, but sometimes that gets confusing, it's great when dev.s keep their instructions up-to-date! So what's the best a2sd to use w/cm6 builds? native? Darktremor (with out dated directions)? This stuff can change fast !
I tried Prime 1.6r2 ROM (Was on Revolver 1.3) and did a CWM backup right before I flashed Prime and then decided to go back to revolver, I ran the restore and it appears that It did not restore the Kernel or the BOOT partition. I had to reflash the Revolver to get back. I have a Viewsonic G tablet and the CWM backup/restore does everything except SDCARD and RECOVERY partition. I thought that CWM backup/Restore for the Transformer would work the same. Is this normal?
brookfield said:
I tried Prime 1.6r2 ROM (Was on Revolver 1.3) and did a CWM backup right before I flashed Prime and then decided to go back to revolver, I ran the restore and it appears that It did not restore the Kernel or the BOOT partition. I had to reflash the Revolver to get back. I have a Viewsonic G tablet and the CWM backup/restore does everything except SDCARD and RECOVERY partition. I thought that CWM backup/Restore for the Transformer would work the same. Is this normal?
Click to expand...
Click to collapse
I don't know anything about Prime or Revolver, but I know that CWM should backup/restore a kernel (or boot.img). If it didn't, it would be chaos in kernel + userspace land, because /system/lib/modules must match the kernel, and it sounds like it's restoring /system/... no problem.
You should be able to figure this out by looking at the list of modules supplied with the kernel in Prime vs. Revolver, then go to root explorer, nav to /system/lib/modules, and see which it matches, then for example, try a 'modprobe {modulename}.ko (like .. cifs.ko) (e.g. modprobe cifs), and if you get a version conflict, you are , for some reason, messed up. Well:: I don't know if those ROM's supply modprobe, so use insmod if they don't. (you could easily do this from adb shell, or onboard from terminal emulator).
I would just use nvflash to backup and restore the kernel in case cwm is messed up on your box.
Just to add to what I mentioned:: I think that if you just try to restore a kernel (/boot) then you'll have the trouble I mentioned above as well, unless the builder decided to link all the 'module functionality' right into it.
Here is what happened. I was on Revolver 1.3 and Over-clocked to 1.504 via SetCPU and all was great. I then wanted to try Prime 1.6r2 and flashed it. When i ran SetCPU it only allowed me to go to 1000Mhz (No overclock! I realized that I would need to install a OC Kernel if I wanted to OC). I played with it for a while and decided to go back to Revolver 1.3. I had done a CWM Backup before I flashed Prime 1.6r2 and so I though that all I needed to do was do a CWM restore which I did. After re-boot, I ran SetCPU as I assmed I was back to Revolver 1.3 and it still did not allow any Over Clock. Strange?? I then re-flashed the Revolver Roms and I was able to Over clock again. When CWM backup is run, SYSTEM, DATA and CACHE area the only partitions I see being backed up (No boot) Since many of the ROM flash boot (Or at least they say they are) I assumed the CWM backup would also backup the Boot Image. I am not sure where "KERNEL"s are stored (I am guessing SYSTEM) so not sure why I am getting the results I am getting.
Update:
when back and read up on the CWM Recovery Backup/Restore and found this line on the first page...
Nandroid backups and restores don't touch the boot or recovery partitions.
So Mystery is solved Since it appears that flashing a Kernel is flashing the boot partition not the /System as I assumed.
Maybe nice to have an option CWM backup/restore to backup the /boot as well.
brookfield said:
Update:
when back and read up on the CWM Recovery Backup/Restore and found this line on the first page...
Nandroid backups and restores don't touch the boot or recovery partitions.
Click to expand...
Click to collapse
That's news to me and I also verified you're correct on my TF. I also looked back at my phone and it used to make 'recovery' and 'boot' backups as well as the other 3. I just guessed that it still did, but you're right. I haven't looked at advanced restore yet where I used to be able to restore any of those partitions, but it won't matter since they're not being backed up.
Since I got this TF a week ago or so, I've been using nvflash for the entire backups in addition to cwm now & then. In the days where cwm backed up everything, the restores worked fine and were much less hassle. Possibly , since cwm is open source, we could fix it to do the entire backup, (not really sure). You could use the little tutorial in the DEV section to use NVFLASH to extract from a 3.2 blob the kernel and package it as a boot.img file. This is either flash-able via nvflash or possibly even restorable by advanced CWM, not sure once again. Thanks for the info.
hachamacha said:
That's news to me and I also verified you're correct on my TF. I also looked back at my phone and it used to make 'recovery' and 'boot' backups as well as the other 3. I just guessed that it still did, but you're right. I haven't looked at advanced restore yet where I used to be able to restore any of those partitions, but it won't matter since they're not being backed up.
Since I got this TF a week ago or so, I've been using nvflash for the entire backups in addition to cwm now & then. In the days where cwm backed up everything, the restores worked fine and were much less hassle. Possibly , since cwm is open source, we could fix it to do the entire backup, (not really sure). You could use the little tutorial in the DEV section to use NVFLASH to extract from a 3.2 blob the kernel and package it as a boot.img file. This is either flash-able via nvflash or possibly even restorable by advanced CWM, not sure once again. Thanks for the info.
Click to expand...
Click to collapse
CWM .img files are in yaffs format, so they aren't the same as nvflash images. Google code has an unyaffs tool. There is also a mkyaffs2image tool. I haven't tried yaffing a directory and flashing it via CWM, but it sounds like it should work. There might be issues with persmissions, pids, and md5sums.
Nvflash images are more like dd dumps. Some of the partitions are actually ext3/4 file systems that you can mount. "file *" in the backup directory should provide 15 mins of entertainment. I usually mount them ro so that the journal doesn't get messed up.
I wonder if it is just an issue where the author of CWM for the transformer can just add the /boot to the list of partitons that are backed up. Is the /boot partition in a format that CWM cannot process and that it why it is skipped? I own a G-Tablet and it does backup the /boot. I will post to the CWM thread and ask what would be involved. My main issue is that so many people believe that this Nandroid backup is for everything and in the case of the Asus Transformer it is not! Most users would find using NVFlash as the backup method to be a PITA as you would have to attached to a PC configured for NVFlash feach time you wanted to backup and/or restore.
Update: I asked the question in the CWM thread. Will update when I hear anything.
Sent from my Transformer TF101 using Tapatalk
Also, I don't that nvflash will restore the data partition. All the images that I have are blank!
sent from my cyanogen(mod) vision
Hi,
I checked through many threads to see if anyone had a similar problem but couldn't find anything unfortunately.
Background :
I was running a Lite'ning ROM on my Samsung Galaxy S2. You're probably familiar with this ROM, but for those who aren't it gets flashed with ODIN and comes rooted and pre-installed with CWM.
I forget which version of Lite'ning ROM it was, but I am fairly certain it was pre-1.5 as the bundled CWM was definitely version 3.x.x.x (later versions I found had 4.x.x.x and 5.x.x.x).
I wanted to try a version of GalnetMIUI for something a bit different and hadn't changed ROMs in quite some time, so I booted into CWM 3.x.x.x (maybe 3.0.0.2?) and did a backup to the internal SD. This came in at around 1.4 GB and comprised of 4 files :
cache.img
data.img
nandroid.md5
system.img
I copied these to my PC too, just in case they somehow got erased from my phone.
Once I'd done this, I then copied the new ROM .zip file (latest version of GalnetMIUI) to the root of the internal SD, booted the phone into CWM, wiped user data and Dalvik cache, then proceeded to install it.
The problem :
I can't get my apps or data back. I was under the false impression that my Google account was automatically backing this up for me, and would restore everything once logged in as it had in the past (factory resets etc.). So once this didn't happen, I tried using CWM to revert back to how things were before installing the new ROM but although the restore appears to work I end up with issues.
I've tried a number of different ROMs and they either get stuck in 'boot loops' or a black screen after running through the restore procedure. I've tried restoring just data via the 'Advanced' option but this doesn't help.
I was under the impression that I'd be able to fully restore the ROM backup if I needed to, and have the phone running exactly how it was prior to messing around. It would seem this is not the case.
In desperation I tried flashing every Lite'ning ROM from version 1.0 to 4.2, restoring my backup each time but as mentioned I always get boot issues.
Have I lost my data? I hope not, as I had 'To Do' lists and all sorts of things that would cause problems if they were not retrievable. I realise this is a lack of knowledge and foresight on my part. I'm thinking now that I should have run Titanium Backup prior to this, and not assumed that CWM was going to provide a complete solution.
Hope all this makes sense and if any of you have the time to read through and offer advice it would be greatly appreciated. I am currently running a very pretty and slick GalnetMIUI without any of my data!
Thanks in advance.
download cwm 2.5.x.x its better
[email protected] said:
download cwm 2.5.x.x its better
Click to expand...
Click to collapse
Thanks for that, I'll give it a go tonight after work. Am I right in thinking that if it doesn't work I can extract the individual files and insert them manually to get my app data back?
OK, so after hours of searching I'm still no wiser as to how to install CWM 2.5.1.2
I found a zip file that was apparently version 2.5.1.2 but when I tried to install it from inside CWM 5.0.2.6 (included with GalnetMIUI) it sometimes gives an error, sometimes it reboots CWM and sometimes it simply says it has successfully installed (it lies). No matter what it says or does, it doesn't seem to actually replace version 5.0.2.6 with the older one and every time I do the three-finger boot it loads up the latest version like nothing changed.
I'm just so lost. All I want to do is restore my old backup, get my data back and move on. Please someone help me before I go insane from all this research!
[EDIT] In case any more information is needed, my exact procedure for installing version 2.5.1.2 of CWM went like this :
Download 2.5.1.2 zip file
Copy zip file to root folder on internal SD
Boot into CWM 5.0.2.6
Select "install zip from sdcard"
Select "choose zip from sdcard"
Navigate to 2.5.1.2 zip file, select and confirm
Can anyone help me at all?
In particular I'd like to know how I can downgrade to CWM 2.5.1.2 or similar in order to give [email protected]'s suggestion a go.
Failing that, if anyone has any suggestions whatsoever about how I can get my backup data restored it would be greatly appreciated. After spending some time with MIUI - in particular the Galnet ICS build - I have nothing but praise, but I really have to get my data back!
You should be able to downgrade through ROM manager. Go to "All Clockwork Mod Recoveries" and just flash one that is not 5.x.x. Any backup not made with version 5 will not work with the new version So if you can flash one that is version 2, 3 or 4 you should be good to go. If that doesn't work you can fastboot flash it. There are guides on how to do that.
Wait.....did you mount /system before installing the CWM zip ?
Sent from my GT-S5830 using XDA App
Sorry for the delayed reply, for some reason I didn't get an email notification that my thread had been updated.
lowandbehold said:
You should be able to downgrade through ROM manager. Go to "All Clockwork Mod Recoveries" and just flash one that is not 5.x.x. Any backup not made with version 5 will not work with the new version So if you can flash one that is version 2, 3 or 4 you should be good to go. If that doesn't work you can fastboot flash it. There are guides on how to do that.
Click to expand...
Click to collapse
For some reason, when I select "All ClockworkMod Recoveries" the only two options are 4.0.1.4 and v4.0.1.4. I'll have to look into "fastboot" flashing as I've never heard of that.
By the way, if I boot into CWM via ROM Manager the version that loads is 4.0.1.5, but if I perform the three-button combo when switching my device on I get version 5.0.2.6.
EmoBoiix3 said:
Wait.....did you mount /system before installing the CWM zip ?
Sent from my GT-S5830 using XDA App
Click to expand...
Click to collapse
I didn't, is that something I should try?
Edit - Just tried this and at first it rebooted CWM and the version number hadn't changed. Doing this again yielded me the following error with no change in version number :
Code:
E:Error in /sdcard/CM V 2.5.1.2_update.zip
(Status 0)
Installation aborted.
I found out that I can extract the contents of my backed up .img files using unyaffs.exe.
Unless I'm doing something wrong, it would appear that my backup is corrupt somehow. When trying to extract data.img, it processes for a while and does bring back a lot of files but I also get the following :
Code:
read image file
: Bad file descriptor
read image file
: Bad file descriptor
data.img is around 1.2GB but the files I extract only amount to around 190MB.
It would appear that I don't have my contacts database in there which is annoying as for some reason there were quite a few that didn't get synced to Google's servers.
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
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