So this may be general knowledge, but I couldn't find anything on this here or other forums. I recently did the CWM update on my Prime to 5.8 and then when I tried to do a restore I was getting error mismatches and restores were failing.
After searching the forum here there are some fixes over in the EVO4G and Desire forums but they were not applicable.
Turns out the fix for this is easy, install any ROM that works enough to get to the market, install ROM Manager and downgrade CWM to the version that was in place when you did the backup. As soon as I did that I was able to restore my old images.
Interesting note, 5.5.0.4 restores both the original backup and the backup done with the newer version of CWM, but CWM will not load the older backups.
Cheers,
Peter
Related
At first I made a backup of the stock state of my gT-p7500 once I got root.
Lately I installed Overcome 2.3.1 and it brings the new CWM 5.5.0.4.
I am trying to restore the STOCK backup, it seems to pass the md5sum and all but when it gets to the restore of the system, data it does nothing.
Previous CWM version I had when I did the backup was 4.0.0.4 which is the one ROM Manager installs.
Any tips apreciated. Thank you.
--
Solution:
Through ROM Manager there is a new CWM version available v5.8.3.1 which seems to address this issue and now the restore is working.
Hi there,
I bought a new i9100 to replace my broken i9100 (screen smashed into pieces).
I took a CWM backup of the old one, and have copied it into the CWM backup directory on the new i9100. ( something like : /sdcard/clockworkmod/backup/<date> )
Can I just reboot into CWM and then attempt to restore the backup? Both devices are i9100 gsm 16Gb versions.
Regards.
if you used the search function, you would have found another thread asking the same question.
short answer is yes.
I did search , but still missed it. Thank-you for replying. I thought it would work but had to verify here.
Actually the short answer is Yes if you are careful. THe backup has to be from the same CWM version as I just discovered.
I just tried it.
CMW v 5.5.0.4
Current installed with stock Samsung ICS.
Restore from known working CMW backup for CM10.1.
Results:
Checking MD5 sums...
Erasing boot before restore...
Restoring boot image...
Restoring system...
Error while restoring /system...
Now that a later version of CMW is installed one has to reboot into CWM again, and then run the restore again.
Some background info: I got my phone used, so the rooting and stuff was done for me.
When I got the phone, the top of the recovery said Semaphore CWM 6.something, I don't know what I did to it but now the recovery says CWM based recovery. I also notice that fix permissions is not there anymore, there is probably more things missing that I never noticed. My question is, How do I get back to the original Clockworkmod?
Also, does anyone want to give me the basics on flashing stuff? I see people talking about Titanium Backup and ROM Manager. Every time I want to make a backup I just go into the recovery and make a backup there. What's ROM Manager? What's the best way to do this kind of stuff?
EDIT: I just booted back into recovery since a while (when I flashed my current rom) and noticed that it's back to normal. It says Semaphore CWM Recovery 6.0.3.8, when it used to say CWM-based recovery 6.0.3.6. Back then, it also gave me a warning called Warning: no file_contexts. That's gone now, should I have anything to worry about?
oneupe1even said:
Some background info: I got my phone used, so the rooting and stuff was done for me.
When I got the phone, the top of the recovery said Semaphore CWM 6.something, I don't know what I did to it but now the recovery says CWM based recovery. I also notice that fix permissions is not there anymore, there is probably more things missing that I never noticed. My question is, How do I get back to the original Clockworkmod?
Also, does anyone want to give me the basics on flashing stuff? I see people talking about Titanium Backup and ROM Manager. Every time I want to make a backup I just go into the recovery and make a backup there. What's ROM Manager? What's the best way to do this kind of stuff?
EDIT: I just booted back into recovery since a while (when I flashed my current rom) and noticed that it's back to normal. It says Semaphore CWM Recovery 6.0.3.8, when it used to say CWM-based recovery 6.0.3.6. Back then, it also gave me a warning called Warning: no file_contexts. That's gone now, should I have anything to worry about?
Click to expand...
Click to collapse
Usually your ROM comes pre-packaged with a version of recovery.
ROMs that use the Semaphore kernel also generally come pre-packaged with a modified version of Clockworkmod recovery designed to compliment the kernel.
for reference:
if your recovery says: CWM recovery X.X.X.X then its usually the official version
Semaphore CWM Recovery 6.0.3.8 is a modified version for use with Semaphore kernel
CWM-based recovery 6.0.3.6 - is a modified version likely for use with another kernel (They dont always specify)
I would recommend just sticking with whatever version comes with your ROM.
there is rarely a need to change it.
ROM manager is an App that makes flashing clockworkmod recovery easy as well as downloading and flashing ROMs.
but for the most part if you know how to use recovery already your probably better off doing stuff manually in my opinion.
Titanium backup - is an app that lets you back up and restore all of your installed apps and data.
so for instance if you wanted to install a new ROM. you could back your apps and data up with Titanium backup and then install your new ROM and even wipe user data and still be able to get all of your apps back just as they were before you switched ROMs.
in comparison a nandroid backup (the backup done through recovery) backs up everything including your current ROM so restoring from that would also restore whatever ROM you were using when you made the backup.
as an example if you do both a Nandroid and Titanium backup while running android 2.3
then you decide to update to android 4.1
after the update if you restore from the nandroid backup you will be back at android 2.3 with all of your apps and everything back the way it was.
if you restore from a titanium backup you'll still be on android 4.1 but you'll have all your apps back as they were before.
I have downloaded and tried to install several different ROMs on Vibrant T959 . I recently managed to get back to stock 2.1 ROM with ODIN and it works fine. As I understand it I need an older version of ClockworkMod so I have CWM 2.5.1.2 installed .
All attempts to flash a new ROM fail with "Error.....(Status 0) Installation aborted.
Maybe I am missing a step here? Do I need to go to 2.2 first?
Thanks.
Update.....
So I Found an older ROM I once installed it was "Bionics" looks like "Team Whiskey" which did install .
From there I was able to install ROM Manager and update Clockwork Recovery (Updated to 2.5.1.3) . When I tried to initiate a ROM flash from clockwork recovery The error was something like
This Package is for "vibrant.vibrantmtd.SGH-T959" devicethis is a "".
I also notice that google play simply calls this device "phone" , but there is no SIM installed and could the lack of SIM cause any of this?
I have old EFS backups of both locked and unlocked states but I thought this was just IMEI . The IMEI does appear to be intact.
I think the vibrant has an identity crisis
markosjal said:
Update.....
So I Found an older ROM I once installed it was "Bionics" looks like "Team Whiskey" which did install .
From there I was able to install ROM Manager and update Clockwork Recovery (Updated to 2.5.1.3) . When I tried to initiate a ROM flash from clockwork recovery The error was something like
This Package is for "vibrant.vibrantmtd.SGH-T959" devicethis is a "".
I also notice that google play simply calls this device "phone" , but there is no SIM installed and could the lack of SIM cause any of this?
I have old EFS backups of both locked and unlocked states but I thought this was just IMEI . The IMEI does appear to be intact.
I think the vibrant has an identity crisis
Click to expand...
Click to collapse
you might check the build.prop in your/system folder and see what it shows as the device name next to ro.product.model=
some roms change it to i9000 which would not pass the check some flashable zips have to make sure you are flashing them on the right phone.
or in this case it might even be blank or have some odd characters which would cause no name to display.
I would try re-flashing the rom which should replace the build.prop with a clean copy from that rom and then try to flash the new rom.
if that doesn't work it can be edited but I would only do that as a last resort.
on a side note error 0 means the wrong update script type was used (Amend or Edify)
Amend is the older one and Edify the newer.
you either needed a newer or older version of clockworkmod or a rom that used the other type of script.
I know you got that part fixed already by chance but I thought it might help to know what happened just in case it comes up again.
Actually i worked this out , although thanks for the reply. your reply prompted me to post my findings here to help the next poor sap with the same issue.
I installed a bunch of useless efs backup and restore apps which none would work with the efs backup I had previously made . I then installed the original galaxy s unlock app which did restore the efs backup.
Apparently the efs partition was buggered . I had several different backups and found the original locked efs then unlocked it.
I now have omni ROM 5.1.1 installed on my vibrant.
BTW if you install omni ROM 5.1.1 the recommended Google apps packages do not install, but I found another package that did install and also do not use the launcher in omni ROM (launcher 3 ?) It is buggy. The Google launcher was in the Google apps package I installed and it is far better than the omni ROM bundled launcher. I can not say that I like either of them however the seem so ordinary.
Help!
I'm trying out a series of ROMs and now am faced with a puzzle. After wiping CM13 (system and all), I'm trying to flash an @amaces AOSP Marshmallow build, but TWRP is giving me grief saying it can't flash an older OS over a newer one.
It says the previous CM13 OS was dated 2017 (I don't think so....) while the one I am trying to flash is dated 2016 (yes, the @amaces ROM was posted in 2016).
So...I thought I had truly wiped the system. How can it know anything about a "previous" ROM?
Edit: Ugh. So I think this is because the CM12 and CM13 ROMs changed the partition table? Or they changed something and I need to get back to stock. Unfortunately my stock backup is gone (8gb). I've looked at all the various restores and they rely on files that no longer exist or are behind so many layers of pop-ups and -unders that it doesn't seem safe to wait and hope the download will eventually start. Succulent has a series of flashable zips to "restore" a tablet to stock, but if there has been a partition change, will his zips fix that?! I have the nooktablet_1_4_3_update.zip, but have no idea if that is even useful. It certainly can't be flashed with CWM or TWRP.
Edit-Edit: OK, I learned something(s). Apparently the issue was the version of TWRP I was using. I tried an older version and I was able to flash one of @amaces ROMs, but I also did manage to take the tablet back to stock using nooktablet_1_4_3_update.zip. It turns out that you can't flash that successfully with TWRP--at least not the versions I had. But I did have CWM 6.0.5.1 from succulent as altboot on my SD card. That was able to flash the zip and restore to stock. Good to know since everything else is gone. And, yes this time I also made a CWM stock backup and put it somewhere safe