I been having an issue trying to create a backup using Rom manager but have not been able to create one that will allow me to recover through recovery. all backup file were being created as IMG but all recently I've noticed Cache, data and system no longer have the extension IMG, it now has extension .ext3.tar is this correct? Is there a way for me to recover using these files?
Starting with version 5, Clockworkmod Recovery uses a new (faster) file format, which uses tar. The new recovery should work with older backup files, but the old CMR won't work with newer backups.
Have you actually tried restoring one, or are you just assuming that because it's different it won't work? It should work fine, as long as you have the newer CMR currently installed. If you restored an older backup, it could have also restored an older version of CMR, which would then prevent you from restoring a newer backup.
You can update CMR from within ROM Manager, and then should be able to restore newer backups.
You can also download the CMR .img file from http://www.clockworkmod.com/recovery_images.html and install it using the fastboot utility. This thread has info on how to do that, but has links to the older version of CMR.
Thank you for replying. Looks like when i was backing up, i was using an updated backup and would try to restore with an older apk attached to the custom rom.
I just created a backup and was able to restore it without any issues. Thanks again for showing me the light
Found this thread through a Google search and just thought I'd add my 2 cents.
I used Bionic Recovery Bootstrapper to install CWM recovery (v4.0.1.5). Later, I used ROM Manager to flash the updated recovery (v5.0.2.5). Made some backups. Flashed old recovery using Bionic Recovery Bootstrapper again and tried to restore the new ext3.tar backups I made.
ROM Manager has trouble rebooting to recovery, but Bionic Recovery Bootstrapper can still reboot to the recovery, even though it was the one installed with ROM Manager.
Thanks for shedding some light on this. I am going to reinstall ROM Manager, flash new recovery, reboot to it using the reboot button of Bionic Recovery Bootstrapper app, and restore my backup!
Edit: ROM Manager doesn't have problems booting into recovery anymore (not sure what I must've been doing wrong previously) so I guess I am not even going to use Bionic Bootstrapper anymore, since ROM Manager downloads the most recent version every time.
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.
Installed Safestrap for my first time. Opened app, installed recovery, rebooted and hit menu button when I saw Motorola screen. Nothing happened and it rebooted normally. What am I doing wrong?
You are rooted, correct?
Indeed. Bootstrap isn't installed either. I feel like a noob, but it seems simple to use yet it won't work. I'm trying to install a custom ROM and it gives the link to the Safestrap apk so I know it's the right apk.
JDunc said:
Indeed. Bootstrap isn't installed either. I feel like a noob, but it seems simple to use yet it won't work. I'm trying to install a custom ROM and it gives the link to the Safestrap apk so I know it's the right apk.
Click to expand...
Click to collapse
If your on ics make sure ur using safe strap 2.0
Sent from my DROID SPYDER using xda app-developers app
error while restoring /systemorig!
I just updated my razr CDMA X912to ICS (OTA 6.16.211) and used the DroidRaxrUtility 1.7 (thanks mattlgroff!) to root and install safestrap 2.0. I am going through the motions of backing up and restoring but keep getting the error "error while restoring /systemorig!"
I dont feel confident to add a custom rom on my safe system until i know I can restore on my non-safe system.
Steps taken:
-reboot into recovery (safe system :disabled)
-create backup
-reboot
-make subtle changes to wallpaper and add a few apps
-reboot into recovery (safe system: disabled)
-restore for ext-sd
-locate back up made and confirm restore.
it checks the md5 sum and then begins to restore /systemorig and eventually fails.
Update: I had to do a full wipe and recovery using the blur 6.12.181 stock image. now i am able to restore safestrap backups. I used Mattlgroff's 1.7 utility, option 1
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 notice a lot of horrendous things happening when your cwm backup verison is different from the rom manager/recovery manager's version. I mean we're talking two releases right next to each other. Does TWRP resolve this conflict?
All cwm backups are backwards compatible with each other
Sent from my LG-E970 using xda app-developers app
Something else I'd inquire about I have two backups I will switch between (inverted regular to see which one I like)
If I install the recovery openscript in goo manager for twrp backup it will replace clockwork no? If it does my question would be since I can't restore clockwork backups through twrp, how would I restore that second backup or add twrp to it/ in that rom too?
trying to conceptually understand the transition here thanks
I installed TWRP 2.6.0.1 as one guides suggested.
I used it to do backups and install the Google rom (that has all a sort of problems). So I waned to go back to my backup but they were not showing in the backup list even if I could them under /sdcar/TWRP/BACKUP/...
After backing up another file I can see the new file.
I installed ROM Toolkit that can see the old backups but it fails to install them because try to get them from /internal_sd/ (or it was /external_sd ?) instead of /sdcard
What is going on?
Did I installed the wrong TWRP or what?
Moved to Q & A, please don't post something in development forums unless you are releasing something.
Camicia said:
I installed TWRP 2.6.0.1 as one guides suggested.
I used it to do backups and install the Google rom (that has all a sort of problems). So I waned to go back to my backup but they were not showing in the backup list even if I could them under /sdcar/TWRP/BACKUP/...
After backing up another file I can see the new file.
I installed ROM Toolkit that can see the old backups but it fails to install them because try to get them from /internal_sd/ (or it was /external_sd ?) instead of /sdcard
What is going on?
Did I installed the wrong TWRP or what?
Click to expand...
Click to collapse
What I did was create a new backup using twrp then I used my file explorer to find the twrp folder and found where the new backup was made. I then moved over my old backup into that folder and when rebooted into recovery it found it
Sent from my HTC One using xda app-developers app
Most likely it's in 0/TWRP or /data/media/TWRP
Sent from my HTC One using Tapatalk 4 Beta