My EVO 3D backup consists of the following:
.android_secure.vfat
cache.ext4
data.ext4
recovery.img
boot.img
system.ext4
I had created the backup using Rom Manager. Now when I am trying to restore the same using rom manager, the mobile restarts, shows some process and nothing really happens. When I am try to do a recovery using CWM, I get the following error:
system.img not found
data.img not found
cache.img not found.
What should I do?
Any help would be appreciated as I have no clue regarding this.
nikhilnaik said:
My EVO 3D backup consists of the following:
.android_secure.vfat
cache.ext4
data.ext4
recovery.img
boot.img
system.ext4
I had created the backup using Rom Manager. Now when I am trying to restore the same using rom manager, the mobile restarts, shows some process and nothing really happens. When I am try to do a recovery using CWM, I get the following error:
system.img not found
data.img not found
cache.img not found.
What should I do?
Click to expand...
Click to collapse
Flash 4EXT recovery and then try to restore. I dont think this format of backup is compatible with cwm recovery
Related
I have a couple questions about CWM and backups:
Is there a difference between flashing update.zip and installing a zip from the sdcard in CWM?
Also, let's say I make a change to boot.img and system.img and something goes wrong. Instead of flashing the backups of those two images from my computer to my phone using fastboot, can I just place them both in a zip file and install it from CWM? Would I need to include any other files?
How come a nandroid backup makes a system.ext4.tar and not a system.img? How do I turn that into a system.img?
How come I need unyaffs to read cache, data, and system.img files? I thought the filesystem was ext4 and not YAFFS?
Flashing an update.zip looks for a file on the root of your sd called that and flashes it. Installing a zip let's you choose.
You need to put a few more files into the zip. An update script and binary
Update to romracers recovery and you can do an advanced restore just using certain parts of a nandroid.
That recovery also makes.. Img files rather than tars
sent from my Atrix via XDA premium
marko! said:
Flashing an update.zip looks for a file on the root of your sd called that and flashes it. Installing a zip let's you choose.
You need to put a few more files into the zip. An update script and binary
Update to romracers recovery and you can do an advanced restore just using certain parts of a nandroid.
That recovery also makes.. Img files rather than tars
sent from my Atrix via XDA premium
Click to expand...
Click to collapse
So I found some links about the update-script and I'll be reading those shortly, but after skimming them I didn't see any mention of the binary. Is the binary an executable version of the same script or something else? Any links?
So what your saying is I could just skip the update.zip stuff, extract the images from the zip, and use advanced restore to flash each image? Obviously more work but it's good to know if these two processes are equivalent.
Actually, I just made a recovery using romracer's CWM and boot and recovery are .img files while cache, data, and system are ext4.tar files. pds is .ext3.tar and .android_secure is .vfat.tar. So do you really get system files as .img files? And if so, what's wrong with my CWM? If not, the original question holds: why doesn't CWM make an image of each partition, and instead use a tar? For compression? How would I make this a flashable .img file?
And also the last question about ext4 and YAFFS is still there. Thanks.
Most of those I'm really not sure. The update binary is the same for every zip. Just grab it from a rom or theme
I would go with the cwm zips. Way easier once you get them working.
sent from my Atrix via XDA premium
gsingh2011 said:
Actually, I just made a recovery using romracer's CWM and boot and recovery are .img files while cache, data, and system are ext4.tar files. pds is .ext3.tar and .android_secure is .vfat.tar. So do you really get system files as .img files? And if so, what's wrong with my CWM? If not, the original question holds: why doesn't CWM make an image of each partition, and instead use a tar? For compression? How would I make this a flashable .img file?
Click to expand...
Click to collapse
I was just looking at this too. My old recoveries from before atrix4.1 was released were all .img files and the post atrix4.1 backups are .ext3.tar (except for boot.img and recovery.img). I'm on a stock deodexed GB ROM, so I don't have any ext4 partitions. I think he changed this with the newest update so CWM can recognize the ext type and mount them appropriately.
This post should hopefully clarify a bit more than I can. I'm relatively new to all this so I'm still learning different aspects of modding. I'm guessing you have some ext4's because you're running one of the newer custom ROM's?
Hi,
I currently own a rooted SGS2,
I rooted it yesterday and it has Superuser and CMW.
I am trying to flash İCS REMİX ROM V7.1 XXLP2 4.0.3 resurrection
Ive downloaded and put it into phone/clockworkmod/backup folder (or whever it is supposed to be)
when i reboot my phone into CMW recovery mode and i choose to restoe the downloaded custom Rom, it says it cannot find system.img cache.img etc etc.. and then it says it has skipped the restore process.
when i checked the folder that i downloaded from İCS REMİX ROM V7.1 XXLP2 4.0.3 resurrection, all the files are in .tar format except the boot.img
anyone know how to solve this??
Some1 just had same problem, and I thinkbthe files are in tar format so if they are, learn more about flashing.
Sent from my GT-I9100 using XDA App
CWM backup
It is a CWM backup, you have to put the zip file you get after unrar in the folder sdcard/clockworkmod/backup. DO NOT UNZIP
I did that, and after I unrar-ed the downloaded file, I got a folder containing tar files , one md5 file and a boot.img
I also had some trouble restoring this ROM and what worked for me was to get a standard 4.0.3 ROM that you can install from zip from the sdcard and then only do the restore from the backup as they say in the intro of that thread.
Hope this helps
Bobgnarley said:
I also had some trouble restoring this ROM and what worked for me was to get a standard 4.0.3 ROM that you can install from zip from the sdcard and then only do the restore from the backup as they say in the intro of that thread.
Hope this helps
Click to expand...
Click to collapse
I currently do have a different 4.0.3 Rom installed from zip on my Galaxy s2,
so what you did was you did a restore from backup with ICS remix rom 7.1??
Yes I unzipped the File and copied the folder to the clockworkmod/backup folder. Then boot into cwm go backup and restore and restore from that date folder. Thanks to Wescrip and all the dev on that thread. They've done an awesome job so far.
Sent from my GT-I9100 using xda premium
Bobgnarley said:
Yes I unzipped the File and copied the folder to the clockworkmod/backup folder. Then boot into cwm go backup and restore and restore from that date folder. Thanks to Wescrip and all the dev on that thread. They've done an awesome job so far.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
I did exactly what you mentioned above, however I get error messages such as data.img not found cache.img not found,... then it says it's skpped it all and the restoration process becomes aborted...
is it because the files in the folder are in .tar format not .img?
That might be a problem with the Kernel or the CWM version you using. Not too sure.
What I can tell you is these are the steps I followed and they worked 100% for me.
1. For the first ROM i installed I downloaded this one - http://downloadandroidrom.com/file/GalaxyS2/roms/CM9ICS/update-cm-9-SGS2-01122012-signed.zip
(Thanks to max at galaxy S2root.com for the link)
2. I did a full wipe and factory reset from CWM and then installed this zip file from sdcard.
3. I booted my phone and let it start up. Then switch off again and go into CWM.
4. Then chose restore from backup and restore (as you will see CWM is now 5.5.x.x which might have a influence not sure)
5. Let it start up and bob's your uncle.
Edit : just fyi there seems to be a problem with the cwm that comes with that rom as it doesn't read the sdcard and I couldn't restore from it. So either you must flash a new cwm from odin when you want to restore to your old rom or install the first rom again so you have a working one and then restore.
Hi
I've got a HUAWEI u8815 phone stuck in boot loop - I can use Fastboot to flash BOOT.IMG and RECOVERY.IMG to it fine.
Thing is I need to flash a SYSTEM.IMG but the only backup of the System is a CWM backup that is not in *.IMG format.
It has
- system.ext4.dup
- blobs (folder - containing loads of folders and files)
Question is can I make a SYSTEM.IMG from these files... or flash the blobs - but if so how?
I'm very stuck so any help appreciated.
Thanks
giblet
Fixed - by using Fastboot to update to latest ClockworkMod Recovery v6.0.2.7 that allowed me to access the file system by mounting the SD cards... I was sweating for a bit.
I've nandroid backup of my stock rom. and i want to make cwm flashable zip using kitchen. What file should I copy in the working folder of kitchen?
I only copied system and boot.img file. Should i copy anything else?
These are the files
boot.img
cache.ext4
data.ext4
nandroid.md5
recovery.txt
system.ext4
uboot.img
Click to expand...
Click to collapse
mrtaim3 said:
I've nandroid backup of my stock rom. and i want to make cwm flashable zip using kitchen. What file should I copy in the working folder of kitchen?
I only copied system and boot.img file. Should i copy anything else?
These are the files
Click to expand...
Click to collapse
The steps can vary somewhat depending on the device. I'm assuming it's some sort of a Chinese device, most likely a tablet, with the uboot file... What's wrong with just having the nandroid? It's not like you can't share that with others if you're needing to.
es0tericcha0s said:
The steps can vary somewhat depending on the device. I'm assuming it's some sort of a Chinese device, most likely a tablet, with the uboot file... What's wrong with just having the nandroid? It's not like you can't share that with others if you're needing to.
Click to expand...
Click to collapse
Its not about sharing. I've just bricket my phone. But i had a nandroid backup. I restored it but nothing happened. So i made a cwm flashable zip using kitchen and included only system.ext4 file and boot.img file. and i stuck at boot loop. I think i'm doing something wrong. i just wanted to ask if uboot.img is essential for cwm flashable zip?
mrtaim3 said:
Its not about sharing. I've just bricket my phone. But i had a nandroid backup. I restored it but nothing happened. So i made a cwm flashable zip using kitchen and included only system.ext4 file and boot.img file. and i stuck at boot loop. I think i'm doing something wrong. i just wanted to ask if uboot.img is essential for cwm flashable zip?
Click to expand...
Click to collapse
Well, if a nandroid didn't work, then not likely that making a flashable CWM zip with the same files would make any difference. You might just need to flash the stock firmware and start over.
So I'm used to doing backup of devices in TWRP but it seems that nandroid is the way you do it with these. I downloaded and ran a backup to SD Card. I chose the option for TWRP backup, will that allow me to do a restore of the image I created here from recovery or would i need to install TWRP recovery to recover? If I chose the backup type Clockworkmod would that be restoreable from stock recovery? The directory it created is only 1.6GB w/o compression which doesn't seem right to me.
I did read the idiots guide to root first BTW.
Thanks guys.
Tried to do a recovery restore using optin recover system from backup but I have no idea the path it is looking for, it doesn't say just says no system.img so ignore. So it appears nandroid creates a system.ext4.tar so I suppose I could decompress this and see if there is a system.img file that the recovery is looking for and put it in the root of the sdcard if recovery is actually looking /external_sd.
Anyone have any input?
Dave