Related
I am getting this error when ever I try to do a nand restore : Error: run ' nandroid-mobile.sh restore ' via adb!
I am running amon ra 1.8, I have the latest sprint lovers installed running 3.70, new radios, pri 1.90. Hboot 79. I've succesfully backed up and restored nands in the past but now I get this error. I've tried to backup and then immediately try to restore the backup and I get the same error so its not a corrupt backup. I have more than 6gb available on my sd card and am fully charged. I've looked in other threads and haven't found an answer. Any help is appreciated since I'm flying without a net when I flash if I can't restore my nand.
Run the command from adb shell, and it'll tell you what's wrong. Duh.
In other words, do what it tells you to do. Is it really so hard to follow instructions?
Hey man had the same problem. I was on miui and I went back to sense to update profile and flashed the new radio combo so I made a nandroid of miui first and then when I tried to restore that same back up I got the same error that you got. I'm not positive but I think that it has something to do with flashing the new radio and then switching to aosp rom. I ended up having to reflash miui and then every thing went back to working normally.
Sent from my PC36100 using XDA App
nandroid won't work if battery is low, I think if it's less than 30% charged, might want to try charging it before restoring to see if it helps...
I've had this happen with a full battery. The couple of times I had it happen I just wiped cache and dalvik. Rebooted back up, then gone back into recovery and then was able to restore the nand backup. Might give that a shot.
Nefariouss said:
I've had this happen with a full battery. The couple of times I had it happen I just wiped cache and dalvik. Rebooted back up, then gone back into recovery and then was able to restore the nand backup. Might give that a shot.
Click to expand...
Click to collapse
I had the same problem and what nefariouss is saying might work. Also, once i wiped several times and then completely turned the phone off and booted back into recovery and then it would restore. Another time i reflashed the rom that i was trying to restore and once it booted i went back to recovery, wiped all and then it would restore. Hope that helps. Just keep messing with it. I know its a pain but eventually it will restore.
Sent from my PC36100 using XDA App
if your sd card didnt partion properly this will happen.
save everything on your sd.
reboot into recovery
repartition sd card.
read that a few people running clockwork recovery have this issue frequently.
Delete Spaces!
If you are trying to flash a file in recovery that has spaces in it, it will not flash and will give you that error. so 'Fresh Evo.zip' won't work, but FreshEvo.zip will work.
FML, ignore this post please. I was a bit stupid.
Sorry for bumping, I have the same problem on my Optimus One p500
Sorry for bumping but I'm really worried about my phone. I have the same problem on my Optimus One and I've tried stuff mentioned above with NO success. Is there maybe another way to restore stock Froyo or to get this working?? I'm a total noob by the way..
antiother said:
.... Is there maybe another way to restore stock Froyo or to get this working?? I'm a total noob by the way..
Click to expand...
Click to collapse
Download and flash this. It is a rooted stock rom (Froyo) that has NOT been deodexed. In other words, it is THE stock HTC sense rom (3.70) that will allow you to maintain root privileges. While in recovery, wipe EVERYTHING in the wipe menu EXCEPT the SD card BEFORE flashing.
posting & replying via the XDA Premium app.
This happened to me and I tried everything listed. Reformatted my SD card. Copied everything back and nand restore finished first time. Polly unrelated but the only thing different was I had upgraded my RA recovery after I had made the backup.
wampuscat said:
This happened to me and I tried everything listed. Reformatted my SD card. Copied everything back and nand restore finished first time. Polly unrelated but the only thing different was I had upgraded my RA recovery after I had made the backup.
Click to expand...
Click to collapse
Same thing happened to me after I updated Amon Ra recovery after doing a nandroid backup. Desire wouldn't boot and got stuck on white screen. Tried to do the backup using ADB but each time I got to the last step it failed. So I tried clearing Dalvik cache etc and finally wiped my card using recovery. After a couple of attempts, I was able to restore the last nandroid backup. Big relief.
i need help!!! i have the same problem of the whole error run nandroid-mobile.sh.. via adb. ive scoured the internet and havent solved my problem. i tried doing the cmd prompt thing and i found the latest backup, put into the cmd prompt but this is what i got.
error: /sdcard/nandroid/mem=477M/BCDEAS-20120130-0411/nandroid.md5 not found,
nnot verify backup data
/ # /sdcard/nandroid/mem=477M/BCDEAS-20120130-0411
/sdcard/nandroid/mem=477M/BCDEAS-20120130-0411
/sbin/sh: /sdcard/nandroid/mem=477M/BCDEAS-20120130-0411: Permission denied
/ #
and i rebooted and have no idea what to do. someone help. i have the nandroid backup saved to my computer as well in case something like this would happen, and if i could restore, things would be fine!!! i dont understand this, i created a nanroid backup and its not corrupt but i can restore it! wth, im lost and confused and i have lots of data on that nandroid backup. someone please help. i partitioned my sd card and lost everything so all i have is the nandroid backup and my original rom, Cyangon MOD 7 is running right now bc i lost all my data, so im at the beginning. PLEASE HELP!
Delete spaces
I was facing similar problem but thanks to @hecklbrg, It did the trick. Cheers.
always when i create a nandroid, after restoring it doesn't go further than the HTC logo screen which appears after starting, the 4th nandroid backup which didn't work:S
Recovery Amon -RA 2.0.0
S-ON
Is it because of my recovery?
TopGear63z said:
always when i create a nandroid, after restoring it doesn't go further than the HTC logo screen which appears after starting, the 4th nandroid backup which didn't work:S
Recovery Amon -RA 2.0.0
S-ON
Is it because of my recovery?
Click to expand...
Click to collapse
Are you doing a full wipe ie factory reset, wipe cache, wipe battery stats before restoring?
stringer7 said:
Are you doing a full wipe ie factory reset, wipe cache, wipe battery stats before restoring?
Click to expand...
Click to collapse
yes but the weird thing is my device gets usb bricked after every restore, i always perform full wipes before restoring
.. problem solved with usb brick nevermind
but still nandroid backups annoy me a lot
TopGear63z said:
yes but the weird thing is my device gets usb bricked after every restore, i always perform full wipes before restoring
Click to expand...
Click to collapse
Strange... Is it worth downloading the latest version of your rom again and reflashing it?
Or could there be a problem with your recovery image, maybe its worth reflashing that also?
stringer7 said:
Strange... Is it worth downloading the latest version of your rom again and reflashing it?
Or could there be a problem with your recovery image, maybe its worth reflashing that also?
Click to expand...
Click to collapse
Did both, still thanks for you help just never going to restore a nandroid again always resulting into usb brick
TopGear63z said:
Did both, still thanks for you help just never going to restore a nandroid again always resulting into usb brick
Click to expand...
Click to collapse
No worries, hope someone can help, there must be a fix.
Last suggestion, new sd card?
TopGear63z said:
always when i create a nandroid, after restoring it doesn't go further than the HTC logo screen which appears after starting, the 4th nandroid backup which didn't work:S
Recovery Amon -RA 2.0.0
S-ON
Is it because of my recovery?
Click to expand...
Click to collapse
Maybe you have an ext partition for your apps and/or data on your sd card which you do not backup?
Sent from my HTC Desire using XDA App
Not sure if this is relevant but I bricked my Desire when I did a Nandroid of a recent Starburst rom. I can't remember which version now unfortunately but it offered data2sd. It's my understanding that performing the Nandroid backup was a bad mistake as the rom had moved vital parts of the phone system to the SD card and the Nandroid backup ignored that as it doesn't see it as a vital part to backup.
A subsequent reboot after doing the Nandroid resulted in the phone booting so far, rebooting, booting less far, rebooting and ultimately, SD card not recognised. Many hours spent learning Fastboot stuff fixed that, then I had a USB brick. Yet more hours ensued and eventually I fixed that too.
I've backed up and even transferred my current rom (Insert Coin CM7) to another SD card tonight with no issues at all but this isn't using data2sd. The speed gains on d2sd were great but I'm wary of using such a thing again as I'm pretty certain that that is how mine died after a Nandroid backup.
Parva4 said:
Not sure if this is relevant but I bricked my Desire when I did a Nandroid of a recent Starburst rom. I can't remember which version now unfortunately but it offered data2sd. It's my understanding that performing the Nandroid backup was a bad mistake as the rom had moved vital parts of the phone system to the SD card and the Nandroid backup ignored that as it doesn't see it as a vital part to backup.
A subsequent reboot after doing the Nandroid resulted in the phone booting so far, rebooting, booting less far, rebooting and ultimately, SD card not recognised. Many hours spent learning Fastboot stuff fixed that, then I had a USB brick. Yet more hours ensued and eventually I fixed that too.
I've backed up and even transferred my current rom (Insert Coin CM7) to another SD card tonight with no issues at all but this isn't using data2sd. The speed gains on d2sd were great but I'm wary of using such a thing again as I'm pretty certain that that is how mine died after a Nandroid backup.
Click to expand...
Click to collapse
I used data2sd but that didn't work at all, starburst was slow as hell, i have to say i moved a lot of things to sd, not ext not only in android.secure, that could be the problem, but if i don't do that i don't have enough space on my internal
Thanks,, i think that i now know what my problem is
MatDrOiD said:
Maybe you have an ext partition for your apps and/or data on your sd card which you do not backup?
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
No that isn't it i always backup nand+ext
I'm on the Mikg 2.1 + 3.0 rom, and ran into a problem trying to restore my backup after briefly trying out another rom. Using AmonRA, after restoring my backup it loads like normal but when the lockscreen comes up there is no ring or way to unlock the phone. Does anybody know what happened? Is my backup no good? Going to have to reload the stock rom to get back into my phone.
Thanks
joelthebassplayer said:
I'm on the Mikg 2.1 + 3.0 rom, and ran into a problem trying to restore my backup after briefly trying out another rom. Using AmonRA, after restoring my backup it loads like normal but when the lockscreen comes up there is no ring or way to unlock the phone. Does anybody know what happened? Is my backup no good? Going to have to reload the stock rom to get back into my phone.
Thanks
Click to expand...
Click to collapse
Just flash the rom over your setup now, fastest way to fix it for right now. Or boot back into recovery and wipe cache/dalvik
I guess I will switch back to clockwork recovery since I have used it to restore my stock backup before. Don't know what happened to this backup that I made on AmonRA, but if it doesn't work I won't be using it anymore.
I'm having the same problem. I have done multiple nandroid backups with Amon_Ra that are not restoring properly...
I don't flash over anything critical, but it's becoming an inconvienience.
Are you saying that CWM is not doing this?
I hae only used amon ra after rooting with no problems. Might be a bad recovery. Just my 2cents.
joelthebassplayer said:
I'm on the Mikg 2.1 + 3.0 rom, and ran into a problem trying to restore my backup after briefly trying out another rom. Using AmonRA, after restoring my backup it loads like normal but when the lockscreen comes up there is no ring or way to unlock the phone. Does anybody know what happened? Is my backup no good? Going to have to reload the stock rom to get back into my phone.
Thanks
Click to expand...
Click to collapse
Same problem here. I did a full wipe before restoring and wonder if that was the problem. Did you do a full wipe before restoring?
stealthl said:
Same problem here. I did a full wipe before restoring and wonder if that was the problem. Did you do a full wipe before restoring?
Click to expand...
Click to collapse
All of you guys are using Amon and having restore issues.. Not something I have really ever heard of. Is it a 32gb card
After I restored I was missing market. Running deck 1.3
Sent From My Pocket
Mine is a 16gb card. I couldn't unlock the phone after restore. There was no unlock ring. Running mik 2.5
I have the same issue. 32gb card. Amon-ra. fortunately clockwork works. Unfortunately I have to use clockwork. I even reformatted and repartitioned. Still no luck
We're comin from a pure power source.
I've also restored from Amon Ra and had weird things missing.
Mistress of Mischief
holy crap im having the same issues. I did a nandroid restore with amon ra 2.3 and now even after a full WIPE I cannot get the same rom that I had restored at one point working again. Market app is missing. WTF?
Not sure what's going on exactly. However, I have noticed that's get weird restores when I wipe the .Android directory and don't back it up. That has all my sdcard programs. That winner explain the missing ring, but maybe the market.
how do I switch from amon ra to clockworkmod? and which is the latest & greatest version?
I wanna give it a try just for the heck
350zx6r said:
how do I switch from amon ra to clockworkmod? and which is the latest & greatest version?
I wanna give it a try just for the heck
Click to expand...
Click to collapse
I used ROM manager from market when I wanted to try it out.
350zx6r said:
how do I switch from amon ra to clockworkmod? and which is the latest & greatest version?
I wanna give it a try just for the heck
Click to expand...
Click to collapse
Go to the dev section, search clockworkmod and it'll come out; the latest version is 5.0.2 I believe. You can also download rom manager from the market.
should i be able to just flash it using rom manager? I just wanna give it a try to see if I can sort this issue im having. thx everyone!
Hey guys,
I have kind of a serious issue right now. I used Touch Recovery 5.8.0.2 and made a full backup today of my whole ROM (2.5GB) before trying out some mods which eventually didn't work. So I decided to wipe and restore the backup I made. No matter what I do I cannot get it to restore my data partition properly. I keep getting "Error while restoring /data!" message, however it does the boot image and system fine but doesn't continue to cache and sd-ext because of the failed data. Whenever I boot it up, some of my apps are missing from the home screen and practically all of them are not working when I launch them (force close). I also get boot up error of Google+ force close, among a bunch of other issues. This is happening even when I try to restore an older backup as well. My device is not working state right now and although I can just restore the stock images to get it working again, it is urgent that I restore my data ASAP! I tried wiping several times and even using the non-touch 5.5.0.4 recovery to restore and same thing keeps happening.
Any help would be highly appreciated!
Please don't tell me my backup is corrupt
Update 1: Eventually I gave up and started from scratch but I have confirmed already this happened on a fresh backup as well, at this time we are trying to figure out what is causing this so I can go back to safely backing up and restoring backups.
Update 2: We have test builds of TWRP Recovery that may have resolved this issue! We need testers!
Please see this post: Link Here
Update 3: We have test builds of ClockworkMod Recovery 6 that may have resolved this issue as well! We need testers!
Please see this post: Link Here
***Always see last few posts on the thread for updates on what we discovered just in case I don't update the OP***
Unfortunately I also have the same error today!
Please help us out.
JayantSparda said:
Unfortunately I also have the same error today!
Please help us out.
Click to expand...
Click to collapse
is your phone encrypted?
are you running stock recovery?
are you running a stock Rom?
have you done a factory reset yet?
Hi Spectre85,
My phone did fine yesterday, I was running AOPK Milestone 3 with FAUX123 kernel.
But when I woke up, my phone looked like it's battery was emtpy.
- When I plugged the phone with the charger, I started the phone again.
- Unfortunately my phone keep looping at the Google screen over and over.
So I pulled the battery and put the battery back again in the phone.
- I went to the bootloader and went to CWM recovery.
Deleted Data, Cache and Dalvike cache.
- Tried to retrieve my backup rom, but keep getting this "Error while restoring /data!" message.
I've tried to install other roms as well, but I still keep getting the bootloop at the Google screen.
Have you guys have any advice for me?
spectre85 said:
is your phone encrypted?
are you running stock recovery?
are you running a stock Rom?
have you done a factory reset yet?
Click to expand...
Click to collapse
For me, no, no (CWM Touch 5.8.0.2), yes (stock rooted 4.0.4), no but my goal is to restore my data not erase it.
I had this happen to me before, what I did was flash a factory image through fast boot and it was fine after.
Sent from my Galaxy Nexus using xda premium
Thanks guys..I flashed the factory image through Fastboot mode and the phone works perfectly again! Too bad I lost all my data, but I'm happier that I have my phone fully functional again
You can't access your backup right? There's no way you can copy the file to your desktop?
mohitrocks said:
You can't access your backup right? There's no way you can copy the file to your desktop?
Click to expand...
Click to collapse
I did copy it. I have full access to the file. Also, just fyi my goal here is not just to get to working state (I'm aware of the stock images) but to actually recover my data. My phone is currently on stock images completely blank and working now.
Fast boot flash the nand images just like u did the stock ones.
Sent from my Galaxy Nexus
bwcorvus said:
Fast boot flash the nand images just like u did the stock ones.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Nanadroid files can be flashed in fastboot? Are you sure? First time I'm hearing this. Doesn't fastboot need .img files? These are .tar files.
Open it up and see if its image...sorry all my recoveries use images.
Sent from my Galaxy Nexus
bwcorvus said:
Open it up and see if its image...sorry all my recoveries use images.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
I guess it depends on the recovery version you use. I remember older versions actually had .img files. However 5.5.0.4 and Touch 5.8.0.2 both have ext4.tar files.
Which version of recovery do you use?
If you have root, you can restore your data partition using Titanium Backup. Use "Export from Nandroid Backup" within TB, select the nandroid backup and then select all apps that you want to restore
Immix said:
If you have root, you can restore your data partition using Titanium Backup. Use "Export from Nandroid Backup" within TB, select the nandroid backup and then select all apps that you want to restore
Click to expand...
Click to collapse
Interesting...will this include settings as well like my home screen icon/widget layout, wallpaper, etc?
open1your1eyes0 said:
Interesting...will this include settings as well like my home screen icon/widget layout, wallpaper, etc?
Click to expand...
Click to collapse
Yes. Titanium Backup can restore all your system apps as well as downloaded apps from a nandroid backup. Not as clean as a nandroid restore from CWM but essentially the same thing. But try to see if Titanium Backup can extract your nandroid backup. It all depends on what exactly went wrong with your nandroid backup to begin with. I don't think it restores cache. So not sure about wallpaper.
Immix said:
Yes. Titanium Backup can restore all your system apps as well as downloaded apps from a nandroid backup. Not as clean as a nandroid restore from CWM but essentially the same thing. But try to see if Titanium Backup can extract your nandroid backup. It all depends on what exactly went wrong with your nandroid backup to begin with. I don't think it restores cache. So not sure about wallpaper.
Click to expand...
Click to collapse
You're right. This works great for restore data to select apps (got my notes and game saves back). I think the icon layout is held in the launcher settings, I'm about to try and restore the data to the launcher app and see what happens. I'm making a CWM backup of first of my current state (that's assuming this backup will actually work).
EDIT: Yes! That did it! Widgets position weren't saved but it's ok I only had a few so I manually put them back. Thank you! I never knew TB had the ability to work with nandroid backups.
I guess this now just leaves me figuring out what went wrong with the CWM backup. It happened twice (I have two backups from the same day that won't restore). Does anyone else use CWM Touch 5.8.0.2 and have successful backups? I would experiment to see if it works now but I don't want to end up with a corrupt backup and redo everything again.
Yes with me its the same thing my data its corrupt is even worse every time I do a nanobackup and restarted my phone the phone freezes on the boot logo and I have to go back to recovery trying to use my backups but I can't so I have to flash a new from again and start from the beginning again!!!! Anybody here has the same experience with that ???
So AGAIN, I'm having the same issue. This time on a recovery 5.5.0.4 that used to work for me when I originally got my phone. I think either my data partition might be too big or something but this really needs to fixed pronto. Anyone know how to contact Koush directly in regards to this matter?
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.