Just Installed this version has it was mention it will now preserve the EXT partion that we are using so on recovery it will not downgrade you.
Eg if on a EXT4 it will recovery back to an EXT4.
but i can find any change log to say this is exactly the case, and infact after doing a Backup and looking at the files i see SD-EXT.EX3.tar
But I am using EXT4 so i think it hasn't backup correctly and if i choose to recover i would be formated back to an EXT3.
Anyone can confirm if this is the case or not?
ta
I wanted to use CWM to restore my galaxy tab 10.1 but when I used CWM 5.0 it somehow crapped out restoring data. /system restored fine however. I also tried to use CWM 4.0 and overcome CWM5.1 to restore the same backup but I got the same issue. /system restored fine and it started to restore /data but crapped out somewhere towards the end. What this also did in the process was corrupt the /data partition where CWM would appear to reformat it and odin thought it was ok but the /data partition really wasn't OK as I got several weird side effects. A repartition with PIT file in odin solved the problem. (Almost solved the problem, after the odin flash was done and the tablet ran some initializing script it said /data was corrupted. A formating using STOCK recovery fixed it).
Has anybody figured out a recovery that can properly backup and restore CWM backups? I guess titanium + reflash rom zip is a workable alternative.
PS: reflashing with repartition erases your /sdcard partition.
AAccount said:
I guess titanium + reflash rom zip is a workable alternative.
Click to expand...
Click to collapse
This is what most veterans recommend anyway, as far as I know.
If you can read this it was sent using my GT-P7510.
If you rename your backup folder, make sure you dont use space in folder name
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
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.
So I've finally managed to install a CWM recovery for my spreadtrum phone. Went on to do my first nandroid backup but I noticed near the end of the procedure it said sd-ext partition not found sd-ext not backed up (something to that effect). I know I have an sd-ext partition because I am using link2sd (using fat32 for partitions). My question is what will happen in the event I restore that backup? Will the linked apps in the sd-ext partition need reinstall? Is there any potential problem that may occur if I restore? Thanks in advance.
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