Develop Bugs

Failure to restore image from clockword mod

This seems to keep happening to me but if i backup a rom after setting it up how i like, i can see the files in the clockword mod folder but when i go to restore it it complains to me that the boot image is missing and fails constantly. I am using clockwork mod acsrecovery v1.0.0.5. and running thunderhawk 3.3 currently. What i do is choose (pre-rom wipe) then go to backup and restore, choose my restore image and go. From there it does some file checking and errors out about the boot img. file.
Thanks for any help.

Bml or Mtd?
Sent from my SPH-D700 using Tapatalk

This should be in Q&A. He must be on BML because MTD installs CWM 5.027MTD.
OP I would switch to CWM 5.027 and try it again. Don't rename the backups.

kennyglass123 said:
This should be in Q&A. He must be on BML because MTD installs CWM 5.027MTD.
OP I would switch to CWM 5.027 and try it again. Don't rename the backups.
Click to expand...
Click to collapse
im still fairly new so i dont know the difference between BML and MTD, sorry. I DID however read some issues with acs recovery and backups from here and qbkings video and how you should upgrade to 5.0.2.7 which i just did. Im backing up the rom through rom manager now and will give another go. Thanks.
edit: question, before restoring a backup does cache and dalvik need to be wiped?

looks like acs recovery was the problem. i just restored(with rom manager) a clean gb rom backup i made a little while back and it worked and right now the thunderhawk restore backup is moving along just fine with no errors. Thanks guys.

nyr35blue said:
looks like acs recovery was the problem. i just restored(with rom manager) a clean gb rom backup i made a little while back and it worked and right now the thunderhawk restore backup is moving along just fine with no errors. Thanks guys.
Click to expand...
Click to collapse
You are welcome. And no you don't have to wipe before restoring backups, it should overwrite everything.

Please help me!! Error while retoring data

I am stuck in restoring earlier date in recovery goes like this below
checking md5 sums
erasing boot before restore
restoring boot image
restoring system
restoring data
error while restoring /data!
I HAD TO WIPE IT AND USED A GNEX TOOLKIT TO REFLASH THE ORIGINAL MYSID TORO AND START FROM STOCK ANDROID ICS AGAIN... I LEARNED A VALUABLE LESSON TODAY AND I THANK EVERYONE WHO OFFERED THEIR HELP.... IT WAS MUCH APPRECIATED THANK YOU ALL... A NOOB NAMED ERIC

Cheetah1971 said:
I am stuck in restoring earlier date in recovery goes like this below
checking md5 sums
erasing boot before restore
restoring boot image
restoring system
restoring data
error while restoring /data!
Click to expand...
Click to collapse
Are you using TWRP or CWM? Have you updated to the latest?
I think TWRP can restore CWM, so if you're on CWM, install TWRP then try restoring. Worth a shot.

danielsaenz said:
Are you using TWRP or CWM? Have you updated to the latest?
I think TWRP can restore CWM, so if you're on CWM, install TWRP then try restoring. Worth a shot.
Click to expand...
Click to collapse
Backups are different formats so I dont believe either recovery will restore the others backups.

how can i get twrp? I am using CWM v6.0.1.0..
danielsaenz said:
Are you using TWRP or CWM? Have you updated to the latest?
I think TWRP can restore CWM, so if you're on CWM, install TWRP then try restoring. Worth a shot.
Click to expand...
Click to collapse
I am a noob for sure and I am using a VZ GNEX if this info helps and thank you so much for replying..Should I find it online on my desktop and download it? because my phone won't restore right now..
again thanks for answering my problem.

is there any hope for me do you think?
mbh87 said:
Backups are different formats so I dont believe either recovery will restore the others backups.
Click to expand...
Click to collapse
Thanks for responding and do you think there's any hope for me getting my VZ GNEX back up and running?

Try a different backup or just start fresh and don't use a backup.

is your backup more than 2GB?

Error while restoring /system

i created a nandroid backup using Qcom toolkit. now when i go to restore it using CWM i get an error "Error while restoring /system!" at which point i need to reflash the current rom on the phone in order to boot again. What could be causing this? im running jellybro and the nandroid is of the stock rom rooted with cwm. Thankyou for any help.

MegaNoob said:
i created a nandroid backup using Qcom toolkit. now when i go to restore it using CWM i get an error "Error while restoring /system!" at which point i need to reflash the current rom on the phone in order to boot again. What could be causing this? im running jellybro and the nandroid is of the stock rom rooted with cwm. Thankyou for any help.
I just got in the same boat and now I can't even connect to ODIN properly... Anyoone out there have any ideas?
Click to expand...
Click to collapse

[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.

failed to mount /system structure needs cleaning

Hi,
I have this kind error after restoring nandroid backup?
Any fix advice?
I tried substractum theme, then it messed up something and everything freezes. Then i went in twrp and flashed substract recivery zip but sill everything was still strange. Then i dexided restore my 2 days old nandroid backup and I get this kind of error.
I have rooted. 5.0.4.
Right now i have this recovered nandroid backup and looks like everything is working but why this error.
I got same error when i flash kernel (structure needs cleaning), like in picture

Mairo said:
Hi,
I have this kind error after restoring nandroid backup?
Any fix advice?
I tried substractum theme, then it messed up something and everything freezes. Then i went in twrp and flashed substract recivery zip but sill everything was still strange. Then i dexided restore my 2 days old nandroid backup and I get this kind of error.
I have rooted. 5.0.4.
Right now i have this recovered nandroid backup and looks like everything is working but why this error.
I got same error when i flash kernel (structure needs cleaning), like in picture
Click to expand...
Click to collapse
Hey bud,
I had the same issue when restoring my nandroid backup and I fixed it by doing the following:
1. Wipe the system partition only
2. Remount it as 'ext 4'
3. Restore the system partition from your nandroid backup
If that doesn't work then try a different version of TWRP (Standard, Blu or codworkx)
Edit: I've seen some people asking some more questions surrounding this issue. For newer devices with A/B partitions I'm unsure what to do in most of these cases.
'Magellon1991' posted their findings regarding the 'vendor' and 'system' partitions.
As for anything further, this is beyond my knowledge - I simply stumbled across this initial solution by trial and error and it is likely a little outdated by now.
Best of luck!

Ok. I will try it later.
Edit: looks like it fixed problem. So thaks BenisMusical!

BenisMusical said:
Hey bud,
I had the same issue when restoring my nandroid backup and I fixed it by doing the following:
1. Wipe the system partition only
2. Remount it as ext 4
3. Restore the system partition from your nandroid backup
If that doesn't work then try a different version of TWRP (Standard, Blu or codworkx)
Click to expand...
Click to collapse
Thanks so much for posting this. Only fix I found that actually worked

Work in ZX1
Shaneee said:
Thanks so much for posting this. Only fix I found that actually worked
Click to expand...
Click to collapse
But not at once. First, the format of the "system" and "vendor" sections, after restoring only the "system" and "vendor", and then the "image and image systems and image vendor", and then restoring the OEM, otherwise it was a bootlope without OEM

BenisMusical said:
Hey bud,
I had the same issue when restoring my nandroid backup and I fixed it by doing the following:
1. Wipe the system partition only
2. Remount it as ext 4
3. Restore the system partition from your nandroid backup
If that doesn't work then try a different version of TWRP (Standard, Blu or codworkx)
Click to expand...
Click to collapse
Same issue occuring for me. I have tried restoring multiple backups but same error every time. I can boot into the system by flashing the rom file and then restoring the data. But why cant i restore TWRP backup??

BenisMusical said:
Hey bud,
I had the same issue when restoring my nandroid backup and I fixed it by doing the following:
1. Wipe the system partition only
2. Remount it as ext 4
3. Restore the system partition from your nandroid backup
If that doesn't work then try a different version of TWRP (Standard, Blu or codworkx)
Click to expand...
Click to collapse
Awesome post, thanks a lot.
It worked perfectly.

This was lifesaver!

I did what BenisMusical recommended. Additionally I have to flash the last image. Without there was the boot loop...

BenisMusical said:
Hey bud,
I had the same issue when restoring my nandroid backup and I fixed it by doing the following:
1. Wipe the system partition only
2. Remount it as ext 4
3. Restore the system partition from your nandroid backup
If that doesn't work then try a different version of TWRP (Standard, Blu or codworkx)
Click to expand...
Click to collapse
Logged in just to say thank you. Did what you told down to the letter, and I got my data back. Thanks again!

i have a error failed to mount cust (structure need cleaning)
how to fix this?

BenisMusical said:
Hey bud,
I had the same issue when restoring my nandroid backup and I fixed it by doing the following:
1. Wipe the system partition only
2. Remount it as ext 4
3. Restore the system partition from your nandroid backup
If that doesn't work then try a different version of TWRP (Standard, Blu or codworkx)
Click to expand...
Click to collapse
Benis,
I'm a Crisis Counselor.
I need my rooted Note 9 for house visits.
I am SOL without my phone 'cause I can't navigate/make phone calls.
I am in your debt. Anything you need, I will get you...
Actually, I can't go that far, but I want to give you a heartfelt THANK YOU, and a firm, anti-COVID, handshake.
Thanks Pal.

Didn't work for me sadly. I use Treble and I just restored data, flashed the original vendor zip and system.img (Not the one from the backup - as well as magisk) and it worked again.

BenisMusical said:
Hey bud,
I had the same issue when restoring my nandroid backup and I fixed it by doing the following:
1. Wipe the system partition only
2. Remount it as 'ext 4'
3. Restore the system partition from your nandroid backup
If that doesn't work then try a different version of TWRP (Standard, Blu or codworkx)
Edit: I've seen some people asking some more questions surrounding this issue. For newer devices with A/B partitions I'm unsure what to do in most of these cases.
'Magellon1991' posted their findings regarding the 'vendor' and 'system' partitions.
As for anything further, this is beyond my knowledge - I simply stumbled across this initial solution by trial and error and it is likely a little outdated by now.
Best of luck!
Click to expand...
Click to collapse
absolute legend worked for me