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.
Related
Hi I compiled 4.1.1_r1 Jellybean without errors and tried to install the OTA zip on my GNEX. CWM Touch Recovery complains that it has broken symlinks. I didn't get those problems with 4.0.4_r2.1 ICS before. Is there an app to check md5 or other stuff before I flash a rom? I nearly killed my GNEX because CWM formatted cache and dalivk before failing to install the rom. It also removed boot and system files. Good thing I had a nandroid backup otherwise my phone wouldn't be usable anymore. CWM sometimes complains my nandroid backups have wrong MD5.
So before flashing any rom I would like to check it for errors such as broken symlinks or other stuff that would give CWM problems. Is there such an app?
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..
I recently decided to try MROM (I currently have CM7) so I backed up my current ROM and installed MROM. When I tried to check if I could restore my previous ROM, ROM Manager did not list my latest backups, but instead, listed some really old backups. I checked the clockworkmod folder to see if the latest backups were there and they were. Now, for some reason, ROM Manager was looking in the emmc folder, and not the sdcard (where the latest backups were) and I don't know if there's a way to change where it looks for the backups. I changed the settings to use an external sdcard (I don't know if that would help but I tried) and it didn't help. I then booted into recovery and tried the restore option there and I was able to see my latest backups.
I'm not sure why ROM Manager was unable to see them but booting in recovery worked fine. I want to try MROM (and I know I can restore from the recovery console if I really have to) but I just want to understand why this was happening and if there was another way to restore my backups (ROM Manager saves backups in ext3.tar format and I don't know how to use that with adb).
Don't bother with rom manager. I always get rid of it on every cm rom I try. Its pointless. Your recovery works and its a better option IMO.
Thanks! I would still like to know what's going wrong though, if possible, and also if there's a way to restore a backup saved in ext3.tar format using adb.
mrcountdookoo said:
Thanks! I would still like to know what's going wrong though, if possible
Click to expand...
Click to collapse
Hard to tell. You may never find out. ROM Manager can indeed be weird like that, and is in my opinion unreliable.
mrcountdookoo said:
and also if there's a way to restore a backup saved in ext3.tar format using adb.
Click to expand...
Click to collapse
The backup is a regular TAR archive (as the name suggests). Most recoveries contain the tar tool which you can use to restore the backup.
I'm rooted, cwm recovery from the all in one tool, tying to do a nandroid. When I go into Rom manager it says no recovery available, told it to use existing recovery, it makes its backups up a secure location it says...don't remember the file path...but when I try to restore it gives me md5 mismatch (should note still on just stock rooted) backups through cwm work but the second I open file manager it moves the directory from extsd back to the secure one and no longer works. I took the sd card from my s3 which was rooted and just put it in the s4 without formatting it so I still have my old nandroids on the card from that and I don't know if that's what's causing the problem or if Rom manager just doesn't work for this phone yet...anyone else come across this? I think the multiple cwm directories might be messing with it but what to be sure before I format the card n reload everything I want in it being Rom manager doesn't seem to have this phone in its database yet
Sent from my SCH-I545 using xda premium
Romance manager has never worked completely on most devices. Even people in the S3 threads will tell you not to use it. Do everything from the recovery menus
Wayne Tech Nexus
I always used it on my s3 n never had any problems, only reason I even use it is to rename the backups cuz I end up with so many diff rooms and can't remember which one is which...guess I'm better off just doing it in root explorer to rename n know they're going to work...I can't even find the directory that Rom manager is trying to save them to, doesn't seem to exist anywhere but in the app itself
Sent from my SCH-I545 using xda premium
goomanager
I use goomanager and the backup goes to my ext sdcard,twrp,backups,10cc6657,i like goomanager because lets you choose where do you want the backup in the sdcard0 or ext sdcard.
I have just moved from AOSP ROM into Sense based ROM. I also have backed up every ROM i ever tried using the recovery.
The weird thing is, I can see the backups folders in the recovery but they do not appear when i check them in the file manager apps after booting into the phone. Only one that is visible, that is the stock recovery i made the very first time after i rooted the device. The others are not there.
Does anyone know how to make them appear? I have several backups I want to delete since they are quite space-consuming. Anything is appreciated