I've got a weird problem. I successfully rooted my new HTC Flyer and installed CWM. When I rooted my new device I only had a very small sd card at hand which I replaced a few days later by a fast 32 GB sd card.
After the replacement I reinstalled CWM 4.0.1.4 but every time I try to do a nandroid backup nothing seems to happen. A progress bar is displayed but there doesn't seem to be any progress.
This is what CWM tells me:
Revolutionary CWM v4.0.1.4
SD Card space free: 25496MB
Backing up boot image...
Backing up recovery image...
Backing up system...
Backing up data...
No /sdcard/.android_secure found. Skipping backup of applications on external storage.
Backing up cache...
No sd-ext found. Skipping backup of sd-ext.
Generating md5 sum...
Backup complete! (obviously not!)
Using file expert I can see .android_secure in /sdcard (probably internal "sd card") but not in sdcard2 (probably my 32 Gb sd card). In /sdcard and /sdcard2 there's adirectory clockworkmod. The first one only contains a directory called download and a file .settings. The latter one contains a directory backup and under it directories for each backup attempt.
The question is: Can I trust these backups in case something is going wrong and I need to do a restore? Given the above error message I doubt that. So my next question is: What can I do to fix the problem?
Thanks in advance.
simulacrum
Yes you can trust the backup.
And what about the above error messages?
they just mean that you have no apps on the sd card. They always throw that error at me. It's fine.
I get the same thing when I do it on my thunderbolt. Go to your SD card under cwm/backup and you will find the backups. They should be named with the date you did it.
Sent from my HTC Mecha using Tapatalk
Hi all
I have rooted my phone using the SAMSUNG GALAXY S3 TOOLKIT V2.0 by mskip. I have been trying to create a backup of the stock rom on my phone, but when I try to in CWM recovery I get error message "error while making a backup image of / data". Can anyone help me with this or tell me how to make a backup of the stock rom.
Cheers in advance
eze
When you do a backup, the .android_secure folder form the external sd is backed up as .android_secure.img (It's hidden in the backup set and not included in the md5 checksum). This always gets backed up, even in an advanced backup where data is excluded.
Then when you try to do a full_restore from this backup, after it restores /data it attemps to restore .android_secure.img and fails formatting the device, which kicks CWM out of the restore function and back to the main menu.
I've not tried it with the sdcard removed. I didn't know it would fall back to the internal sdcard. Easiest way around the issue (for now) is to erase .android_secure.img from your backup folders.the backup folder will be pushed to thr cwm folder in /data/media internal storage and your phone will reeboot into cwm to restore the nandroid backup...If you use samsung toolkit ; the point n5 is the backup and restore entry ,then passes to the point n10 and performs restore \data\media (internal virtual sd card) if the backup is done correctly you will have no problems ...
Cheers for the advice but I used the complete tool kit and made a back up that way.
- CWM 6.0.0.8
- CM9 RC2
1. boot into CWM
2. go to backup and restore
3. selected backup to internal sdcard
4.
Backing up boot image...
Backing up recovery image...
Backing up system...
Freeing space...
Done freeing space.
Error while making a back image of /system!
E:Can't open /tmp/recovery.log
E:Can't open /tmp/recovery.log
5. I tried to reboot... still booting after 15min
6. I tried to install CM9RC2.zip again.
7. go to install zip from sdcard
8. choose zip from internal sdcard
9 .No files found.
Wht dose hell going on???
I just backup my system, Why do you delete anything???
Why?
Pls help me~
THx~ ><"
Its look like corrupted nand. All you can try now is to flash custom kernel or stock rom via odin. Very strange thing.
i9.0.1.3k galaxy imperator
Hi,
I have a Galaxy S2 HD LTE device and i am facing a problem while restoring a backup i created with clockworkmod recovery.
Here is what happens:
1. I boot into recovery and created a backup of my existing ROM (which does not complete actually).
This is what i see...
Backing up system...
Backing up data...
Backing up .android_secure
Backing up cache
No sd-ext found. Skipping backup of sd-ext.
Generating md5 sum...
Backup complete!
Now the problem is that if i restore using this backup i get into bootloops... and the backup never actually works...
Can anybody tell me whats the problem?? My life is becoming a hell coz every time i flash a ROM and not like it. Then i have to start afresh every single time
Thanks.
I may have bricked my S3. Phone is stuck on boot animation. In recovery the next message is displayed:
E: failed to mount /efs (invalid argument)
So there is reason to believe that the efs partion is corrupt. Earlier I did backup efs, but don't remember what backup tool was used. The backup file name is efs.ext4.tar, sized 5.2 MB. I tried flash the tar file with Odin3 (as a CSC file), but Odin crashed after pressing start. What can I do to restore the efs partion??
ROM: I9300XXUGND5_I9300NEEGND1_I9300XXUGNA8_HOME.tar.md5 (same problem after flashing Omega v.58)
I think I cannot use Kies, since my loop counter is 2.
edwinn said:
I may have bricked my S3. Phone is stuck on boot animation. In recovery the next message is displayed:
E: failed to mount /efs (invalid argument)
So there is reason to believe that the efs partion is corrupt. Earlier I did backup efs, but don't remember what backup tool was used. The backup file name is efs.ext4.tar, sized 5.2 MB. I tried flash the tar file with Odin3 (as a CSC file), but Odin crashed after pressing start. What can I do to restore the efs partion??
ROM: I9300XXUGND5_I9300NEEGND1_I9300XXUGNA8_HOME.tar.md5 (same problem after flashing Omega v.58)
I think I cannot use Kies, since my loop counter is 2.
Click to expand...
Click to collapse
u need to use pit file for repartition your internal memory.flash your phone with pit file
ifhi said:
u need to use pit file for repartition your internal memory.flash your phone with pit file
Click to expand...
Click to collapse
Total Bull-sh-it!
Don't do this, @edwinn
You will restore your backup either with terminal command or within the custom recovery. Is it tar only or tar.gz?
tetakpatalked from Nexus 7 flo
edwinn said:
I may have bricked my S3. Phone is stuck on boot animation. In recovery the next message is displayed:
E: failed to mount /efs (invalid argument)
So there is reason to believe that the efs partion is corrupt. Earlier I did backup efs, but don't remember what backup tool was used. The backup file name is efs.ext4.tar, sized 5.2 MB. I tried flash the tar file with Odin3 (as a CSC file), but Odin crashed after pressing start. What can I do to restore the efs partion??
ROM: I9300XXUGND5_I9300NEEGND1_I9300XXUGNA8_HOME.tar.md5 (same problem after flashing Omega v.58)
I think I cannot use Kies, since my loop counter is 2.
Click to expand...
Click to collapse
hello u should flash the tar file via recovery this should restores ur efs backup
tetakpatak said:
Total Bull-sh-it!
Don't do this, @edwinn
You will restore your backup either with terminal command or within the custom recovery. Is it tar only or tar.gz?
tetakpatalked from Nexus 7 flo
Click to expand...
Click to collapse
The efs.ext4.tar file is in a folder called "clockworkmod", together with files like boot.img, system.ext4.tar, nandroid.md5 etc.
So I took the next steps:
installed CWM Touch 6.0.3.2 via Odin
copied entire "clockworkmod" folder tot ext sd card
tried to restore from external sd card
After checking MD5 sums the error "MD5 mismatch!" is displated.
Deleting all data in nandroid.md5 was not succesfull.
Further help would be appreciated.
edwinn said:
The efs.ext4.tar file is in a folder called "clockworkmod", together with files like boot.img, system.ext4.tar, nandroid.md5 etc.
So I took the next steps:
installed CWM Touch 6.0.3.2 via Odin
copied entire "clockworkmod" folder tot ext sd card
tried to restore from external sd card
After checking MD5 sums the error "MD5 mismatch!" is displated.
Deleting all data in nandroid.md5 was not succesfull.
Further help would be appreciated.
Click to expand...
Click to collapse
There have been major changes done in CWM since early 6xxx versions. Do you remember which recovery version number did you use to create your backup? I had myself some perfect backups done with 6.0.2.7 that weren't restorable with 6.0.4.5 due to md5 mismatch.
The chances are good you'll be able to restore it, mate.
tetakpatalked from N7100
tetakpatak said:
There have been major changes done in CWM since early 6xxx versions. Do you remember which recovery version number did you use to create your backup? I had myself some perfect backups done with 6.0.2.7 that weren't restorable with 6.0.4.5 due to md5 mismatch.
The chances are good you'll be able to restore it, mate.
tetakpatalked from N7100
Click to expand...
Click to collapse
I found out that the backup was made with Online Nandroid v9.51 (The recovery.log file says so :victory. No info on the CWM version number. It may have been a very old recovery which had a bug that created nested /0 folders in the file systems after every data wipe. I didn't discover that issue until recently . More info on this bug:
http://forum.xda-developers.com/galaxy-s3/help/storage-emulated-0-0-0-flashing-roms-t2214356
The backup may include the nested /0 folders. Perhaps that is causing the checksum mismatch?? (Since the system folder was formatted afterwards)
Anyway. I tried a new non-touch cwm recovery, version 6.0.4.3. No success.
Would you recommend to proceed with the terminal thing? Thx
edwinn said:
I found out that the backup was made with Online Nandroid v9.51 (The recovery.log file says so :victory. No info on the CWM version number. It may have been a very old recovery which had a bug that created nested /0 folders in the file systems after every data wipe. I didn't discover that issue until recently . More info on this bug:
http://forum.xda-developers.com/galaxy-s3/help/storage-emulated-0-0-0-flashing-roms-t2214356
The backup may include the nested /0 folders. Perhaps that is causing the checksum mismatch?? (Since the system folder was formatted afterwards)
Anyway. I tried a new non-touch cwm recovery, version 6.0.4.3. No success.
Would you recommend to proceed with the terminal thing? Thx
Click to expand...
Click to collapse
I am sure it is possible to disable md5 check
tetakpatalked from P5110