As of yesterday (3-29), my CWM backup dates are correct! Did not flash new version, it just started working.
I'm on version 6.0.3.0.
Anybody else have this good fortune?
Related
So I was trying to backup a nandroid of the beta official tmous 2.2. I have two phones, one has the beta official 2.2 and the other stock 2.1. I rooted both, did a titanium backup of both, installed system recovery and ran backup of both. Then I went and loaded the 2.2 backup sd card onto the 2.1 phone and ran system backup and restored the backup. You are probably cringing by now...so it installed the backup and rebooted, and , is now in bootloop on the M logo. Can I somehow restore using the backups, or do I have to flash using rsdlite and use one of the roms on here?
Thanks in advance to any that can help!!! My wife just said she will not buy another phone for me, on my 4th phone within the last year...bricking it is a first though
So that's what you did...
To fix the 2.1 phone you bricked, try restoring the 2.1 nandroid you made.
If I'm correct, Moto's locked bootloader saved you and stopped Recovery from loading the new kernel that's used by FroYo. Which is why you're bootlooping...
If I'm wrong, you'll have to flash the leaked FroYo SBF and restore the FroYo Nandroid you made onto it...
yea, as you know I was trying to make a 2.2 tmous nandroid backup to post on here, but since I'm a noob at this I didn't want to post a possible corrupt nandroid, so I wanted to make sure it was good by trying it out. I couldn't restore the 2.1 nandroid, so I went ahead and flashed the UK 2.34. Thank goodness it worked.
So, now how can I flash the 2.2 nandroid backup onto this UK 2.34 to verify that I made a correct nandroid backup? Is it possible? I am thinking that it would have worked if I wiped data and cashe, wich I forgot to do that the first time...
well, just figured out that wiping didn't have anything to do with it...as I'm back to bootloop. Flashing the 2.34 again
The way you can test your nandroid backup is by booting into recovery, make a backup, wiping the phone, making another backup, and then booting the phone. This will allow you to see what is actually on the backup. Yes you will have to reboot and play around a bit to check, but it should be free and clear of things, at that point reboot into recovery, and restore your rom. That will mean that the second backup you made will be exactly what you just experienced. Hope that helps.
thanks. On a side note, last night when I was researching how to recover, I could have sworn I came across nandroid backups of the tmous 2.2 in the development section...Beach Head...have you looked in there (I think I saw it posted in the thread about the tmous 2.2 OTA update, thought I saw several people post a nandroid backup in the thread). Anyway, I still plan on getting this uploaded as soon as possible, but thought you might want to check in that thread...
You can restore nandroid backup of 2.2 when you are on 2.1. But you will have bootloop. It's beacause you have new kernel (from 2.2) that is not compatibile with bootloader. After restoring nandroid you should try flashing a 2.2tmo_boot only .sbf http://www.mediafire.com/?pkjkk75emk6x83f . Maybe that help. But i really not tested this with tmobile roms. With jboogie mods its working fine. Also remember about gsm fix if you use phone not in US. All 3g fixeS are in this topic http://forum.xda-developers.com/showthread.php?t=944258 . You should use the file with the frequencies of your country. If somethings go wrong you should flash 2.1 rom sbf (version that you are using now).
I am hoping someone can help me with a problem I'm having with my Epic 4G...
Problem:
I am in a bit of a pickle at the moment as everytime I reboot my phone it goes directly to ClockWorkMod (CWM). I was previously on Syndicate Frozen ROM (SFR) 1.0.2 with CWM 3.0.0.x (orange) and attempting to upgrade to SFR 1.2.
Background:
I booted into CWM and made a back up, then loaded SFR 1.2. I got a bunch of FCs, so I reverted back to my back up. I then upgraded to CWM 3.1 (purple) and tried to flash to SFR 1.2 again. This worked, but none of my data was saved.
I decided that I would restore my backup, save my data another way and then re-import it once I had reloaded SFR 1.2. Unfortunately, it looks like trying to load a CWM Orange backup in CWM Purple will result in a failed MD5 checksum.
I reloaded CWM Orange and tried to load my backup and I still get a checksum error. At this point I don't know what else to try.
Anyone have any ideas/sugestions?
Odin back to stock EC05 and try it again from the beginning; that's what I did when I had this issue.
You will loose any apps not on an SD card i believe.
Yep. I had a buddy who is familiar with flashing come by and that is exactly what he did. What a waste of an afternoon! :\
I kept getting the error message: "Error while flashing boot image" until I reinstalled CWM 3.0.0.5. Only then was I able to restore my backup.
Just out of curiosity: if I now upgrade to CWM Purple and then back up will I be able to backup and restore my current version?
TetterkeT said:
Yep. I had a buddy who is familiar with flashing come by and that is exactly what he did. What a waste of an afternoon! :\
I kept getting the error message: "Error while flashing boot image" until I reinstalled CWM 3.0.0.5. Only then was I able to restore my backup.
Just out of curiosity: if I now upgrade to CWM Purple and then back up will I be able to backup and restore my current version?
Click to expand...
Click to collapse
I believe nandroid backups from 3.0.0.5/6 will not work with 3.0.2.5 but 3.0.2.5 nandroids will restore on purple 3.1.0.1. It is best to do a clean install. There are framework changes on 1.2 including the 6 lock mod baked in so restoring data will most likely corrupt your ROM. Best bet is to flash 1.2, then a kernel then install all apps fresh. I use Appbak app to store a list of all installed apps. Then I can fire down the list and install them fresh.
Sent from my SPH-D700 using XDA Premium App
I know that CWM 6.0.1.5 uses blobs folder to store the data, but for some reason it doesn't restore any of the data. it gives me an error saying it can't find data.img when trying to restore. any help would be appreciated!
I haven't tried 6.0.1.5, but on 6.0.1.4 I had similar problems when I had dedup format backups from multiple custom ROMs.
After a point backups refused to be restored in peace. So I changed backup format in the CWM Backup/Restore menu and started keeping tar format backups every now and then to make sure there was some reliable emergency backup.
Sorry that this will not help with your current backup restoration though!
Is this only meant for Nexus 4 ? Or can we flash it for Galaxy Nexus as well ? Reason I ask is because on CWM's official site, it only shows "6.0.1.5" for Galaxy Nexus. I'd like some confirmation before i make the plunge to the latest version.
Thanks.
6.0.1.9 is unofficial and is in the Dev forum, 6.0.1.5 is the current version for the Galaxy Nexus
Hi guys
I'm having g some weird issues I have a gs3 from bell. I rooted it and been flashing all kinds of Roms and never having any issues going back to restoring stable Roms until I decided to try twrp recovery but I noticed that I couldn't restore anything backed up by cwm so I flashed cwm though Rom manager and since then whenever I try to backup a Rom it finishes then when I try to restore them they say md5 mismatch. So after a lot of research I managed to notice that cwm isn't making any nandroid md5 files.
So my question is have I flashed a bad version of cwm through Rom manager or may I have just screwed my phones files somehow I was thinking of uprooting my phone and rerooting it but I don't know if that will fix this. Please help
*deleted*
Good luck
Just so u know i've read through that 3 times already I don't have that issue ... I dOnt have a nandroid md5 like showing up in any of my backups so thanks for nothing if you would have read my post you would have understood That already
solved***** unrooted......rerooted..........backups and restors working fine..........my guess. rom manger`s update of cwm got messed up no more rom manager for me ;p
DLM2583 said:
solved***** unrooted......rerooted..........backups and restors working fine..........my guess. rom manger`s update of cwm got messed up no more rom manager for me ;p
Click to expand...
Click to collapse
Hi, I am still having the same problem as you, and I bought Cwm touch from rom manager and i created a backup and when i restore it it says md5 mistmatch.. So did you get a different older version of cwm? How did you end up using the backup that you couldn't open? Thanks for your help
Hello everyone,
I have rooted and unlocked my bootloader, and installed CWM 6.0.2 I believe (summer 2012). I was using 4.3 Deodexed ROM and decided to upgrade to 4.4, so I mad a nandroid backup through CWM. Then I found out that 4.4 required me to update my CWM to 6.0.4.3, so I did. After upgrading CWM, I was unable to restore my old 6.0.2 backup. Is there any way to restore it, or do I have to downgrade CWM?
If I need to downgrade CWM, can I first perform a backup of my current 4.4 ROM and then downgrade, or is there a chance it will mess with old CWM?
Thanks in advance,
silentz0r
Sorry for bumping, I have noticed that after upgrading CWM, it made new directories into /sdcard and moved my old directories into /sdcard/0. I tried copying the contents of the old CWM directory into the new one (/blobs and /backup) and tried to restore, but still got the same error message notifying me that no backup is found. Is there no way to restore an old CWM backup with newer CWM?
If anyone ever has this problem, I suggest installing ROM Manager. My backups spontaneously started working through ROM Manager (even in CWM recovery). I have no idea why the backup could not be found before, but using this pretty much fixed itself. Marked as Solved.
silentz0r_ said:
If anyone ever has this problem, I suggest installing ROM Manager. My backups spontaneously started working through ROM Manager (even in CWM recovery). I have no idea why the backup could not be found before, but using this pretty much fixed itself. Marked as Solved.
Click to expand...
Click to collapse
Thanks for the heads up!
But shouldn't you just have made a back-up before CWM upgrade, then upgrade CWM, make another backup (just in case) and then install 4.4?
I am still on 4.3 and I will do it this way in the near future.