Related
If you put spaces in the name of your backup file in ROM Manager you will get a Md5sum error when restoring your backup.
To fix, boot back into your current ROM and using Root Explorer or an equivalent file manager, remove the spaces and try again under recovery. Should work now, unless you truly have a corrupted file....
Also I do not recommend Rom Manager on the SGS2. A lot of people complain about bad backups and problems with flashing or restoring!
There have been problems with some roms and Rom Manager because the CWM recovery that Rom Monager "flashes" is not a real recovery. It is only an update.zip file placed on the internal SD card of the phone. The real CWM is the one that is combined with your kernal.
However, for those flashing CM7 nightlies, it is still a useful tool as it makes downloading and flashing new updates almost a one click and fool proof exercise. Importantly, Rom Manager makes sure that the files (including restoring your backups) are not corrupted or incomplete through the MD5sum check. Not sure if real CWM kernals do the same so I like to use Rom Manager to make sure nothing goes wrong.
For those having difficulty booting into proper recovery from Rom Manager, there is a free app called Quick Reboot which works well.
anyone else having this happen?
makes backups ok but wont restore anything freezes at the white htc screen
You need to run your backups and recovery from within CWM. See Absolute_Zero's thread in the Development section for more info (last post).
Happened to me yesterday.
I thought I had corrupted my backups ...
Its not working for me no matter what i try any ideas?
Same problem here, just had to restore and couldnt. backups always made directly from recovery.
There are a lot of reports on this recently
http://forum.xda-developers.com/showthread.php?t=1179386
Visit the above link and revert back to an older recovery if you have backup from recovery pre-5.x, if not flash a rom from scratch. It will load up, just did it myself.
CWR 5.0.1.0 seems to work fine as I've said. I've restored backups from CWR4 which someone suspected to be the problem. It's not as I just did it with 3 different older backups to confirm and subsequently restored to my present backup all using RomManager (since that was more than likely what most users with problems were using).
I will continue testing a few scenarios but as of right now, I can't reproduce the problem. I'm not saying it doesn't exist. I just can't reproduce it without more details.
If you're still having problems AND you've updated to the latest RomManager (4.4.0.5 at this time) AND confirmed you've flashed the lastest CWR (5.0.1.0 at this time) then pastebin your /sdcard/clockworkmod/report.log for someone to look at.
Edit:
I suppose I should mention (although it should be clear) that if you restore a backup you no longer have the updated version of RM so you will need to update it again before it will work with your current recovery.
as far as i can tell gb sense roms with the 3.0 sense seem to be the common issue as far as not restoreing. and it is definitly a known issue... something about a ext3 or ext4 partion or some crap.....
Perhaps it's just backups of Sense-based roms in general. I haven't run Sense since 2hrs after I bought the thing so all the backups I was trying that worked perfectly fine were all aosp. This makes the most "sense" of anything I've heard so far. It may have something to do with the partition format being included in the images now so CWR5 restores older backups without that detail. I have a hard time believing koush wouldn't have included some way to handle those though.
I went back to my old recovery
Sent from my tbolt running ShiftTh3ory AOSP
It seems to be the ext4 not supported
i will also add that backups made on 5x recoveries will restore on 4x as long as its not from a ext4.
i hope that makes some kinda sense to somebody but these are the facts.
So it seems that the ext4 is just not supported on the 5x recovery. I just hope they are working on it and are aware of it
Yes, after several restore attempts of a couple sense roms using 5.0.1.0 I hang at the splash screen.
So today I installed 2 roms from scratch after not being able to restore prior backups created with with 4.x. After each fresh install today I booted into recovery and performed a backup using 5.0.1.0 (RM says that is the version installed).
Recovery will NOT restore the fresh 5.x backups either. Backup and restore were of sense roms.
Just successfully performed a restore of an aosp based rom while writing this post.
Can you see if ext4 partitions can be mounted in adb shell in recovery?
Also, are sense roms ext3 or ext4? What is the exact error?
Can someone pull a /tmp/recovery.log after a failed restore and pastebin it?
I believe I just fixed this in 5.0.2.1. Let me know.
Koush said:
I believe I just fixed this in 5.0.2.1. Let me know.
Click to expand...
Click to collapse
Koush,
The backups in 5.0.2.1 have the Cache, Data and System img files in zip format which is not the format of my other backup's made with the older versions of CWM.
Do you expect 5.0.2.1 to be able to restore the older backups or just ones made in 5.0.2.1?
Yes the last version fixed the mounting issue 5.0.2.1 is what you want!
Thanks Koush
Older backups restore just fine. Happy Days
I've encountered weird problem: The phone doesn't boot (got stuck on bootanimation) after nandroid recovery from CWM. I've tried recoverying it over fresh install of same ROM or over formated partitions, but neither of it works. I'm using CWM v5.0.2.0 and trying to recover hephappys PRE4.
Is this caused by some incompatibility of CWM and ICS?
No, cwm 5.0.2.0 is working with ICS, using it currently (haven't tried using backup/restore, but it shouldn't cause any problems imo).
So, what exactly are you doing? Trying to restore an earlier cm9 backup? Try wiping all, including system and boot, before restoring.
Sent from my LG-P500 using XDA
Yes, I've made backup before messing with my ROM and it just fails to recover. I've already tried to wipe everything.
Is there any tool for viewing backup files on Windows? I guess that the file is somehow broken.
Is there any way how to get calls and sms from this raw data?
Here is boot logcat: https://gist.github.com/2603614
Jirrick said:
I've encountered weird problem: The phone doesn't boot (got stuck on bootanimation) after nandroid recovery from CWM. I've tried recoverying it over fresh install of same ROM or over formated partitions, but neither of it works. I'm using CWM v5.0.2.0 and trying to recover hephappys PRE4.
Is this caused by some incompatibility of CWM and ICS?
Click to expand...
Click to collapse
have the same issue with cwm...
recommand u to use amonra...gwtting best with it
When I was on cm9 and restored my cm7 backup=same thing(yes, I wiped everything)
Well, that backup image is somehow corrupted as it cant be correctly deployed. At least I've managed to extract SMS, the rest is not so important for me.
CWM is pretty much useless when it creates backups which can't be used for recovery...
I don't think that there is a specific problem with CWM and ICS- I have been making backups and recovering quite often ICS builds (including hephappy's pre4) in the last weeks, no problems so far (knock on wood ).
Do you have other/older backups that you can try to recover and see if you get stuck at bootloop?
What about reinstalling the build from scratch- just to see that everything boots? You can later try either restoring your original backup (the one causing you problems), or using TiB or similar applications that can extract applications+data from nand backups.
Could the backup file got corrupted somehow? I don't remember CWM having some inherent checking of md5 before restoring backups (I could be mistaken, as I have never had a bad nandbackup with the P500 phone so never noticed anything weird). For example, I used to have an HTC MT4G with 4ext touch recovery which would always check md5sum and let the user know if backup was corrupted, and I did got a corrupted backup file once.
Back to topic- If anything else fails and you can't recover, maybe try to copy the backup to a different sdcard? Perhaps it's a shot in the dark but worth trying, just in case the problem is in sdcard?
Older backups are only CM7 and they are working flawlessly. I don't know what happened, but it wasn't byte-level error as MD5 check passed on that image. It's more likely the recovery "forgot"/wasn't able to recover some files in /data partition.
Later I've tried to install some fresh ICS, did some changes (configuration + apps), backuped, wiped partitions, then restored and everything worked , so it's definitely not a general CWM problem. It's probably a bad luck, when you really need the backup, it just corrupt itself to annoy you...
As I wrote, I've managed to retrive my SMS and that's enough for me. I don't trust that image so I will install fresh apps via Appbrain and do the new setting by myself (I wanted to make some chcnges to phone configuration, this is just the right moment) .
I have never had much luck with the CWM recovery system. It's really buggy and sometimes only restores select partitions. Or if it couldn't mount the drive at the time of backing up, sometimes it just refuses to tell you or tells you but you have to start the backup over..
Like said above, I would try Amonra. It's a far better recovery and it has almost no bugs to speak of
Cheers mate.
On my phone SDCard, (not the external) I have a folder, \clockworkmod\blobs that is 1.3GB big and has 2300+ folders in it. I went looking for what blobs are & they seem to be code parts. I have used CF-Root from Chainfire and I think that installed a CWM - are these files related to that or can I delete them?
I'm running the latest JB leak DLI5 and CF-Root, other than that, there's ROM TOolbox Pro but I don't see why that would have cwm files. I did have another clockworkmod (it gave a better Recovery menu so if anyone knows which it was I'd like to know ) a while back but have reset/wiped prior to flashing JB.
Those blobs are your nandroid backup, if you delete them your backup will be gone.
"It's all in the game yo, all in the game..." - Omar Little
The blobs method is the newer way in which cwm makes the backups.. The backup folder contains the links to the actual files in the blobs folder.. So only the files which have changed between two backups are saved in the blobs folder.. It is the smarter and efficient way of backing up..
However if don't want this to happen.. You can change the backup type to tar from blob before making the backups.. If you are using touch recovery..
Cwm automatically frees up space or deletes the redundant/unnecessary files before every backup..
Moral of the story.. Don't touch the blobs..
You have been zooo==>ted
Sankuverrymuchness... Didn't want to clean them before knowing and they have survived 3 different JB installs so figured I'd ask.
Touch Recovery - is that the one in ROM Manager? I located the download I had used before - it was RM and has the CWM Touch flash option so I figure it was that I used before.
Back on subject, now that I have changed by phone, I plan to do another Nandroid. From the replies, if I don't care to keep the old BU, I can remove these ones and run the nandroid BU and it will re-create the blobs with all my new system/apps/etc?
(I'm trying to keep the phone as clean as possible so I figure I might need to remove the old Nandroid files before making one that backs up my current setup?)
You will find the touch recovery 6.0.1.2 in the original development section . You will have to flash the recovery via odin. Don't delete the blobs.. Just go boot into recovery and go to backup and restore.. From there delete the backup your want to remove.. Cwm will free up the unused space on next backup.. Or I believe the is also an option to free up space there..
But if you had made the earlier backup using non touch recovery 5.x..You will have to use this recovery to delete your backup.. As touch version will not see this backup..
Don't delete the backups manually.. Or if you want to really do it just delete the backup folder from clockworkmod/backup.. Don't ever touch the blobs..
You have been zooo==>ted
Again, thanks Zoot... I did as you suggested and now the Blobs in the SDCard are gone and I have a fresh set over on the external card. I also made a zip of my system which I presume means I now have a ROM file that can be flashed at a later time to put things back to how they are now?
Journyman16 said:
Again, thanks Zoot... I did as you suggested and now the Blobs in the SDCard are gone and I have a fresh set over on the external card. I also made a zip of my system which I presume means I now have a ROM file that can be flashed at a later time to put things back to how they are now?
Click to expand...
Click to collapse
yes you can flash that zip as any custom ROM..
Hey guys,
I have a little problem I can't find a solution to by searching.
I have a GS3 i9300 rooted with CF-Root-SGS3-v6.4.
When rooting, a version of CWM was installed (5.something).
Later, when installing af custom rom, I followed instructions and updated to a newer CWM (6.0.1.2):
http://forum.xda-developers.com/showthread.php?t=1719744
Later, I was thinking about restoring my original system backup, which I had made with the older CWM version right after rooting.
The new CWM can't restore my older backup. It can't recognize the file, not even when I copy it manually to the new CWM folder.
How can I solve this problem?
Do I need to install an older CWM again?
If yes, then one more question: As I said, my original CWM was installed when rooting. Can someone give me a download just for the CWM tar file included in the mentioned CF-Root?
Thanks a lot in advanced,
Agoston
Replace with older CWM root .
From Original Development section .
jje
still not recognizing + weird directory tree
After trying out three custom ROMs and after updating CWM, my system directory is rather weird. Besides the usual system folders, there is a "0" folder, that contains another set of system folders, and another "0" folder, containing the same. Also, my free internal storage as good as disappeared, from 8 GB to 1 GB. So, it looks like I have several systems on each other?!
How can I reduce this weird directory tree to just one? Do I need to wipe the SD-card?!
And by the way, I rooted the device again through Odin, and the old CWM is now installed again. Still though, it can't recognize the old backup.
As you probably imagine, I am hesitating to format SD-card, especially if CWM can't restore my factory ROM.
Can anyone help?
Thanks!
szaboagoston said:
Still though, it can't recognize the old backup.
Click to expand...
Click to collapse
I copied the backup directory manually to the "most superficial" CWM folder, and now trying system restore. I'ts not easy with four (!) different CWM directories.
Unfortunately I got an "error restoring data" message, and the phone is stuck in Samsung logo when booting.
Also, when trying to do a factory reset, I get the message: "error mounting /sd-card/.android_secure!"
Could this be because there is not enough space or something?!
If someone could help me with how to proceed, I would appreciate it!
Thanks.
Okay, the issue is solved. I admit, I might have been a little inpatient. Despite the "error restoring data" message, the stock factory system booted after a few tries - I might not have waited long enough. It seems that these "Folder 0"s were all just security copies of the old systems, and of course consumed a lot of hard disc space, so I just deleted them. Haven't met any negative consequences so far. I just got scared because of the error message and the too long boot time. Also this phenomenon with "Folder 0"s is not something I met before on other devices.