Develop Bugs

Dumping ROM/creating flashable file

How do you dump an image of the phone's ROM to a file, and is it flashable via Odin when you dump it? If it is not Odin flashable, how do you make it so it can be flashed with Odin?

99% sure this isn't possible.
Closest you will get is doing a backup with ClockWork and then you can restore it to bring the phone back to the identical state it was when you made the backup.
You could probably dump the /system and make a .zip to get a flashable zip file but that's about it.

TheDub said:
99% sure this isn't possible.
Closest you will get is doing a backup with ClockWork and then you can restore it to bring the phone back to the identical state it was when you made the backup.
You could probably dump the /system and make a .zip to get a flashable zip file but that's about it.
Click to expand...
Click to collapse
So how do we get the flashable files, such as "SPH-D700-DI18-8Gb-REL.tar" that we can flash via Odin? My main issue with CWM is for when I'm messing with other ROMS. To date, despite clearing all caches and data multiple times, I've never been able to do a CWM restore without first Odin flashing the base system (Stock DI18 or DK28). Every time I've backed up (say DI18) with CWM, flashed DK28, decided to go back to my original DI18, it would never restore right. It would only do so if I first Odin'ed the stock DI18, then restored the backup.
I'd love to be able to dump my own Odin flashable backup for these purposes.
Now if CWM was a full Nandroid backup that completely re-flashed the ROM top to bottom, that would be different.

SubnetMask said:
So how do we get the flashable files, such as "SPH-D700-DI18-8Gb-REL.tar" that we can flash via Odin? My main issue with CWM is for when I'm messing with other ROMS. To date, despite clearing all caches and data multiple times, I've never been able to do a CWM restore without first Odin flashing the base system (Stock DI18 or DK28). Every time I've backed up (say DI18) with CWM, flashed DK28, decided to go back to my original DI18, it would never restore right. It would only do so if I first Odin'ed the stock DI18, then restored the backup.
I'd love to be able to dump my own Odin flashable backup for these purposes.
Now if CWM was a full Nandroid backup that completely re-flashed the ROM top to bottom, that would be different.
Click to expand...
Click to collapse
Were you making sure to flash a kernel when restoring your backup? Nandroid doesn't backup or restore your kernel. So if you updated to dk28 and then tried to restore back to di18, you would still have the dk28 kernel and would have problems. If you flash a di18 based kernel after restoring your di18 backup, you should be fine. I've found the easiest way to restore a backup is just to reflash the rom and then advanced restore /data. Your data partition is where your apps and settings will be.

[Q] quick CMW3.x.x question

My endgoal is to flashsyndicate to my Epic.
I started with DI18 and flashed (via recovery) to EB13. Which is where I currently am. I would like to us Titanium Backup to save all my data but I need root. Its my understanding that when I run the CMW 3.x.x one click I am going to have to immediately flash to an ext 4 compatible ROM, and therefore lose my EB13 data? I was thinking that I could use noobnl's root, backup with T.B. THEN CMW 3 one click and flash syndicate followed by the dual fs kernel? Is this sound reasoning?

You can go to cwm 3 without flashing an entire rom. You would just need to flash a EXT4 compatible kernel. The cwm ext4 conversion process backs up and restores your data so as long as you flash a ext kernel you should be good to boot into stock then backup then proceed with flashing your rom.
Or you could one click with cwm 2.5 then backup, then run one click with cwm3 and convert. This is what I did.
Sent from my DROID2 GLOBAL using XDA App

Awesome! Thanks for the help

[Q] unable to backup system!

hi guys i recently downgraded my recovery from revolutionary to CWM v2.5.0.7.
now i can't do a backup of my CM 7.2 ROM.
backing up boot...
backing up recovery...
backing up system...
it freezes at backing up system..i waited for 20 mins but it doesn't move a inch..
some apps in my sd n some are in my internal storage.
i also tried upgrading to revolutionary and still the same problem persists..:crying:
Can you guys help me out here?
sorry for my bad english.

eddykuhan said:
hi guys i recently downgraded my recovery from revolutionary to CWM v2.5.0.7.
now i can't do a backup of my CM 7.2 ROM.
backing up boot...
backing up recovery...
backing up system...
it freezes at backing up system..i waited for 20 mins but it doesn't move a inch..
some apps in my sd n some are in my internal storage.
i also tried upgrading to revolutionary and still the same problem persists..:crying:
Can you guys help me out here?
sorry for my bad english.
Click to expand...
Click to collapse
Looks like you're messing up the terms a bit...: "Revolutionary" doesn't really have to do something with your "Recovery" (Clockworkmod). Same goes for "upgrading to revolutionary" - I have no clue what you tried to do there
Let's try to get some useful information:
- If you've downgraded your recovery I assume your phone is rooted and has S-OFF and worked well before?
- for what reason did you downgrade? to flash a radio?
- if yes: did that work well?
I have suggestions what you could do but it would be better if you'd provide above information first

eddykuhan said:
hi guys i recently downgraded my recovery from revolutionary to CWM v2.5.0.7.
now i can't do a backup of my CM 7.2 ROM.
backing up boot...
backing up recovery...
backing up system...
it freezes at backing up system..i waited for 20 mins but it doesn't move a inch..
some apps in my sd n some are in my internal storage.
i also tried upgrading to revolutionary and still the same problem persists..:crying:
Can you guys help me out here?
sorry for my bad english.
Click to expand...
Click to collapse
Clockwork mod and revolutionary are two different things.
Try flashing another CWM version through fastboot or pc49img.zip method. You can find the links in wildfire index thread in development section.
Sent from my HTC Wildfire using XDA

saadislam said:
Clockwork mod and revolutionary are two different things.
Try flashing another CWM version through fastboot or pc49img.zip method. You can find the links in wildfire index thread in development section.
Sent from my HTC Wildfire using XDA
Click to expand...
Click to collapse
i tried the latest version of ClockWorkMod v5.0.2.0.but the same problemstill persists
eventcom said:
Looks like you're messing up the terms a bit...: "Revolutionary" doesn't really have to do something with your "Recovery" (Clockworkmod). Same goes for "upgrading to revolutionary" - I have no clue what you tried to do there
Let's try to get some useful information:
- If you've downgraded your recovery I assume your phone is rooted and has S-OFF and worked well before?
- for what reason did you downgrade? to flash a radio?
- if yes: did that work well?
I have suggestions what you could do but it would be better if you'd provide above information first
Click to expand...
Click to collapse
yes, my phone is rooted and s-offed n work well before this and sorry guys previously I was using ClockWorkMod v3.2.0.0..i downgraded to ClockWorkMod v2.5.0.7 to flash radio..but it didn't succeed..So, i flashed through fastboot method and it succeeded.i was able to do a backup after flashing the radio..all went well and 1 day wen i try 2 make a backup in the same ClockWorkMod v2.5.0.7 it stucked in backing up system..

eddykuhan said:
i tried the latest version of ClockWorkMod v5.0.2.0.but the same problemstill persists
(...)
i was able to do a backup after flashing the radio..all went well
Click to expand...
Click to collapse
I see. I already thought that it doesn't have to do with recovery - just wanted to make sure
I suggest you to try reflashing the ROM first - but better make sure that you avoid leftovers of your current "system":
- put the ROM and gapps (20110828) into root of your sd card
- boot into recovery
- format "system" (in "mounts and storage")
- wipe "cache"
- flash CM7
- flash gapps 20110828
- reboot
try a nandroid backup again afterwards
if this doesn't help either my suggestion would be to do a complete wipe:
- put the ROM and gapps (20110828) into root of your sd card
- boot into recovery
- wipe all / factory reset
- (I usually do an additional format "system", "data" as well - just to make sure)
- wipe "cache"
- wipe "dalvik-cache"
- flash CM7
- flash gapps 20110828
- reboot
see, if everything went ok then reboot in recovery and do a partial restore of your data (backup & restore/advanced)
reboot again (see if everything works) and reboot into recovery again to try your nandroid backup
There's another thing coming to my mind: do you have enough space left on your sdcard? I never had that problem so I'm not sure if CWM spits out an error about that...

Just for the info, Cwm doesnt give any error if low on space. It just keeps going on with backup.
Sent from my HTC Wildfire using XDA

So what you meant was .... you downgraded from revolutionarys cwm version to 2.5.0.7 ? Did you use revolutionary to do this or other method?
You couldn't backup with 2.5.0.7 cwm so upgraded back to revolutionarys version with same backup issues afterwards ?
You upgraded cwm to 5.0.2.0 and your still not able to backup ?
Can you restore a nandroid ?
Do you have custom mtd set up ?
Ive not come across the won't back up issue but have had the same issue during restores after flashing a new cwm ?
Some cwm restores are not compatible with some other cwm versions but your problem is backing up so this can't be the case lol.
Have you got the Rom up and running before trying to back it up,and your NOT wiping anything prior to attempting the back up ?
1st I would try wipe dalvik cache from advanced and format cache from mounts and storage then try a backup.
If that fails........ (your gonna lose your current Rom setup with the following but 1 of these methods should get your cwm functioning again.)
Try restoring an old backup then if that is successful try a backup again as this could just kickstart your cwm backup into gear.
Failing that.........,
then I think your gonna have to do a full wipe and reinstall Rom.
Forum fishing.... Who's biting!

Agreed. This is very strange. Have you flashed anything else we should know about that has anything to do with the system partition? Tweaks ect?
Sent from my HTC Sensation using xda premium

slymobi said:
So what you meant was .... you downgraded from revolutionarys cwm version to 2.5.0.7 ? Did you use revolutionary to do this or other method?
You couldn't backup with 2.5.0.7 cwm so upgraded back to revolutionarys version with same backup issues afterwards ?
You upgraded cwm to 5.0.2.0 and your still not able to backup ?
Can you restore a nandroid ?
Do you have custom mtd set up ?
Ive not come across the won't back up issue but have had the same issue during restores after flashing a new cwm ?
Some cwm restores are not compatible with some other cwm versions but your problem is backing up so this can't be the case lol.
Have you got the Rom up and running before trying to back it up,and your NOT wiping anything prior to attempting the back up ?
1st I would try wipe dalvik cache from advanced and format cache from mounts and storage then try a backup.
If that fails........ (your gonna lose your current Rom setup with the following but 1 of these methods should get your cwm functioning again.)
Try restoring an old backup then if that is successful try a backup again as this could just kickstart your cwm backup into gear.
Failing that.........,
then I think your gonna have to do a full wipe and reinstall Rom.
Forum fishing.... Who's biting!
Click to expand...
Click to collapse
hi,
-after upgraded cwm to 5.0.2.0 and i'm still not able to backup
-im using custom mtd
-in matter fact i can restore my old nandroid backup
the story like this after i restore my old nandroid i cannot do backup same ROM again.
and i also tried to wipe dalvik cache from advanced and format cache from mounts and storage then tried a backup and it still fails..:crying:
guys thanks for your feedback im going to do a full wipe and reinstall Rom.!!

eddykuhan said:
-im using custom mtd
Click to expand...
Click to collapse
just to make sure: have you flashed the bravoboot file after the nandroid backup?
If you did, well, a full wipe might be a good idea anyway - but: have you tried my initial suggestion - to format just system? if this is the point where the nandroid backup fails this could be enough to solve your problem...
- put the ROM and gapps (20110828) into root of your sd card
- boot into recovery
- format "system" (in "mounts and storage")
- wipe "cache"
- flash CM7
- flash gapps 20110828
- flash the bravoboot file
- reboot
If everything works again you could try to do a partial restore of "data" (in CWM / Backup and Restore / Advanced Restore)
But don't forget to flash the bravoboot file after that one again - and better don't try to restore system again - just data (and sd-ext, .android-secure whatever you like)

Maybe you can try to do backup in 3.x.x.x version of cwm? I had similar problem to yours (I was on 2.5.x.x v CWM) and after it everything worked

I currently have the same problem (CWM5028) and have not solved it yet.
Interesting to note is that the time noted in the title for the stalling backup is 3 hours off. A clue to the cause?

cweijden said:
I currently have the same problem (CWM5028) and have not solved it yet.
Interesting to note is that the time noted in the title for the stalling backup is 3 hours off. A clue to the cause?
Click to expand...
Click to collapse
Got it solved... I also use MTD partitioning (http://forum.xda-developers.com/showthread.php?t=1233340) and probably have forgotten to flash a required zip after restoring a backup. According to the instructions this should have left me with a white screen. That didn't happen, but it left me unable backing up my system for a while. After repartitioning as suggested by eventcom I was able to make backups again.

Flashing and restoring between GB and JB

Hi all,
I'm having trouble restoring backups when I go between GB and JB. Sbrissen's lastest Alpha build is the JB I'm using. Everything goes fine with the restore until "Data". Then the restore fails. I mobile odin the EL29 with autoboot into recovery, install the ROM (JB in this example) . I then try to restore a backup I made with the same exact version of CWM from the same exact ROM that I used to create the back up. Maybe a better question is How can I create a JB backup, go back to GB, and return to JB and restore that backup. Cause what I'm doing isn't working.
Thanks

Which GB ROM are you coming from? GB recoveries should be safe so you shouldn't have to Odin to EL29, unless you're on a stock ROM without a custom recovery. Also are you wiping system, data, cache, and dalvik cache prior to restoring your backup?

mwcarnage said:
Which GB ROM are you coming from? GB recoveries should be safe so you shouldn't have to Odin to EL29, unless you're on a stock ROM without a custom recovery. Also are you wiping system, data, cache, and dalvik cache prior to restoring your backup?
Click to expand...
Click to collapse
I'm using the latest Blazer GB Rom. I'm wiping everything also,factory reset,cache,dalvik cache, etc. I have to flash back to GB to update an app that requires my correct serial number to work, JB Roms do not do this at the moment so the app wont work. That is the reason for flashing back to GB (didn't want to mess with ICS for obvious reasons). I'm coming from HTC Evo 4g so things are a little different. On the Epic 4G, I was under the impression you had to use the same recovery to restore that was used to create the backup. Can I just jump back and forth between GB and JB using the nand backup with each others recovery? GB's CWM is 5 and JB's CWM is 6. I didn't think you could because if the backup won't restore with the same CWM is was created with, how would it restore with another version? Still a little foggy on the process E4GT uses.
Thanks

dal320driver said:
I'm using the latest Blazer GB Rom. I'm wiping everything also,factory reset,cache,dalvik cache, etc. I have to flash back to GB to update an app that requires my correct serial number to work, JB Roms do not do this at the moment so the app wont work. That is the reason for flashing back to GB (didn't want to mess with ICS for obvious reasons). I'm coming from HTC Evo 4g so things are a little different. On the Epic 4G, I was under the impression you had to use the same recovery to restore that was used to create the backup. Can I just jump back and forth between GB and JB using the nand backup with each others recovery? GB's CWM is 5 and JB's CWM is 6. I didn't think you could because if the backup won't restore with the same CWM is was created with, how would it restore with another version? Still a little foggy on the process E4GT uses.
Thanks
Click to expand...
Click to collapse
dal320driver said:
Hi all,
I'm having trouble restoring backups when I go between GB and JB. Sbrissen's lastest Alpha build is the JB I'm using. Everything goes fine with the restore until "Data". Then the restore fails. I mobile odin the EL29 with autoboot into recovery, install the ROM (JB in this example) . I then try to restore a backup I made with the same exact version of CWM from the same exact ROM that I used to create the back up. Maybe a better question is How can I create a JB backup, go back to GB, and return to JB and restore that backup. Cause what I'm doing isn't working.
Thanks
Click to expand...
Click to collapse
I've gone from rooted EL29 back to a a JB ROM and restored with no issues. The ROM I use is Paranoid Android. I usually allow my phone to boot then reboot into recovery before restoring. Hopefully this isn't a stupid question, but sometimes things get forgotten/overlooked when flashing ROMs. Anyways, did you flash the JB gapps after flashing the ROM? Just asking since this step was not in your posts.

mwcarnage said:
Which GB ROM are you coming from? GB recoveries should be safe so you shouldn't have to Odin to EL29, unless you're on a stock ROM without a custom recovery. Also are you wiping system, data, cache, and dalvik cache prior to restoring your backup?
Click to expand...
Click to collapse
kmok said:
I've gone from rooted EL29 back to a a JB ROM and restored with no issues. The ROM I use is Paranoid Android. I usually allow my phone to boot then reboot into recovery before restoring. Hopefully this isn't a stupid question, but sometimes things get forgotten/overlooked when flashing ROMs. Anyways, did you flash the JB gapps after flashing the ROM? Just asking since this step was not in your posts.
Click to expand...
Click to collapse
Yes, I flashed JB gapps also. I'm not having trouble re-flashing the ROM's back and forth. . This part is successful. The problem is when I go back into recovery and try to restore a backup (of either ROM just flashed) it isn't working. Sorry for the confusion.
Thanks

dal320driver said:
Yes, I flashed JB gapps also. I'm not having trouble re-flashing the ROM's back and forth. . This part is successful. The problem is when I go back into recovery and try to restore a backup (of either ROM just flashed) it isn't working. Sorry for the confusion.
Thanks
Click to expand...
Click to collapse
Okay, I was just making sure something wasn't forgotten when you were going back to JB this time around. I figured you were able to get the different ROMs working since you were able to make a backup of the JB ROM you were using. AFAIK the different versions of CWM (5 vs 6) shouldn't matter in this situation. Hopefully someone else has had the same problem and will be able to chime in.

CWM6 creates backups differently than CWM5 or most other recoveries. Instead of putting the entire backup in one folder, it has a separate Blobs folder that contains a lot of the data. If the folders get separated, the backup won't get restored correctly. Did you by any chance move the main folder or delete the blobs folder?

Nandroid restore Problem

Hello to all,
I have Arc with ICS .587 installed and rooted, CWM is Also installed. Whenever i try to restore my Backup i end up in bootloop, sometines its restored but somethings are not working like no service, some widgets are Gone, cant get into Phone settings as the setting button is completly gone from phone.
Please can good Samaritan help me
Thanking All in Advance

Do you Wipe Data/Factory Reset/Cache etc before restore?

did you changed kernel?
if you chanege the name of the backup, things will not work.

gabimx said:
did you changed kernel?
if you chanege the name of the backup, things will not work.
Click to expand...
Click to collapse
yes....not change the name of backup...
moreover if you have flashed a zip and it didn't go fine....there is a possibility that the istallation have spoiled the backup or file of kernel...(for all I know it happened to me in this way)

Yes Guys i do make a full wipe before restore, and after making a backup i transfer it to pc for Safe storage, so whenever i need it i transfer it back to cloclworkmod folder

centi50 said:
Yes Guys i do make a full wipe before restore, and after making a backup i transfer it to pc for Safe storage, so whenever i need it i transfer it back to cloclworkmod folder
Click to expand...
Click to collapse
If u flash custom kernel, u need to also flash wifi modules before rebooting after restore...

I dont Flash custom Kernel, everything is stock, by the way My Arc is Bootlocked so customs kernels

While you make backup does cwm show any errors? have you checked the log ? Does the restore process complete without errors ? And do you fix permissions and mount system /data etc before restoring ?

nikufellow said:
While you make backup does cwm show any errors? have you checked the log ? Does the restore process complete without errors ? And do you fix permissions and mount system /data etc before restoring ?
Click to expand...
Click to collapse
Backup Completes without Error, and no i do not Fix permission or Mount System/Data before restore.

centi50 said:
Backup Completes without Error, and no i do not Fix permission or Mount System/Data before restore.
Click to expand...
Click to collapse
Then do it ! and try again .

This is what is happening to me. Lets say am Running on GB Rom e.g X-Gamer, now i want to try lets say Optimax Rom, i backup my Current ROM which is X-Gamer, then i try to restore it to see if its works, and i find that it works. so Flash ICS Original Sony ROM and root it. in the end i Have Sony Stock ROM.587 and CWM installed. So far am ok.
Now i Install ICS based ROM like Optimax or JellySandwhich. Everything goes Fine, so i Backup That ROM too and keep a copy on my Laptop. Now i decide to go to my old backup of X-Gamer, i Boot to recovery do a full wipe + i mount data/system and fix permission as i have CWM 5.5.0.4. which has permission option in it. i continue to restore my X-Gamer Backup. After Finnishing of course without error. i reboot the phone and Bam!!. Bootloop.
I reflash GB.42 with Flashtool, root it and install CWM. Boot to recovery and try to restore my X-Gamer backup, and WOLA!! it's restored.
same with ICS Backup. Reflash Stcok Rom root it and restore the ICS backup i made, and it works.
As i know i may be wrong (am a noob) The backup is a snapshot of the rom, so regardless of what rom someone is running when he restores the Backup, he should be back to that ROM in the backup and not to reflash first the corresponding Stock ROM in order for the Backup to work.
Please somebody help and shade some light

Have you used the same recovery all the time? Switching recoveries can "sometimes" not flash backups properly. Either that or it didn't back it up properly in the first place. TBH there's not much we can can do. The backup is corrupted and for that it is causing bootloops and braking things. All I can suggest to you is to reinstall a fresh install of the ROM and then try an advanced restore of your applications and data just not the Boot.img or the system.img
Sent from my Galaxy Nexus using xda premium

Jessie-James said:
Have you used the same recovery all the time? Switching recoveries can "sometimes" not flash backups properly. Either that or it didn't back it up properly in the first place. TBH there's not much we can can do. The backup is corrupted and for that it is causing bootloops and braking things. All I can suggest to you is to reinstall a fresh install of the ROM and then try an advanced restore of your applications and data just not the Boot.img or the system.img
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I have tried to use same recovery, but same result. restoring backup across different ROM does not work for me it seems. I have to have a working corresponding rom as the backup am trying to Resotre. for example if i want to restore my backup of GB ROM, i have to have a working GB Rom already on Phone. I Can't restore an ICS Rom while my Phone is On GB and vice verser.

centi50 said:
Please somebody help and shade some light
Click to expand...
Click to collapse
Flashing an ftf also flashes the kernel, so restoring a GB backup when you originally installed ICS or vice versa will give you issues as CWM doesn't backup your kernel.

XperienceD said:
Flashing an ftf also flashes the kernel, so restoring a GB backup when you originally installed ICS or vice versa will give you issues as CWM doesn't backup your kernel.
Click to expand...
Click to collapse
Thanks XperienceD for Clarifying. now i undersatnd. Just wanted to ask is it possible to flash A GB Sock Kernel on an ICS ROM or vice versa, then using the backup to restore thru CWM, as this will save time than to reflash the ftf, root it and install CWM just only to restore your backup.

centi50 said:
as this will save time than to reflash the ftf, root it and install CWM just only to restore your backup.
Click to expand...
Click to collapse
This is why it's better to unlock your BL, then it's just a flash of a kernel then restoring your backup.