Problem: I flashed newer versions of CWM (5.5 and 6.0.2) and TWRP 2.3.3 in prep for trying CM11. Neither recovery seems to be able to create a Nandroid of CM7. They both hang about 25% into the job.
So I'm not sure I'll have a valid backup, I'm not sure I'll be able to restore my current Nandroid, and I'm not sure I'll be able to flash a new ROM. Before I do anything else, can someone point me to a known working recovery for CM7.2?
Thanks!
If Nandroid fails, try online nandroid or titanium backup. If those fail, then just try using TWRP 2.6.3 off SD (I couldn't get it to work from EMMC), and backup/install from there. If no backup options work, just try not backing up; you can always just use repart.img to restore to 1.4.2.
I eventually found a flashable zip of CWM 5.0.2.8 and was able to flash it sucessfully. Booted to recovery and was able to make a full Nandroid. Enough for now, I'll fool with CM11 another day.
Related
Am I able to nandroid restore from MIUI to something with voodoo and vice versa?
I believe you have to odin back to stock first.
the restores are done from CWM so i think yes?
nandroid doesnt back-up the kernel i dont think so you need to flash a kernel thats compatible with whatever rom you backed-up or i think it'll bootloop
using nandroid to go between different CM7/MIUI roms will work (for the most part, as CWM will actually backup the kernel for those). However, you can't use nandroid to go between CM7/MIUI and samsung roms.
Hello there guys.
I've done a full backup with clockwork but if i try to restore it i get a error message about the boot image...i can't restore it. now i was able to restore system..data..and so on via advanced restore...i get no boot animation but the system is up an running. i can't get the wifi to work...what can i do now?
I used a clockwork 4.0.1.4 with root enabled..i flashed it whit Odin.
Thanks guys
forgot to mention I own a Galaxy S 2
Flash a clean stock rom as your backup is corrupt.
jje
Same issue
I took a full backup with CWM (4.0.0.2) to test a Kitchen ROM. After getting it to work I wanted to switch back to my standard ROM (CF-Root KE7), but it failed with the boot image ("error flashing boot image").
If the backup was corrupt I would expect the MD5 to fail, but it didn't. Like the OP I was able to restore all the other items one by one, which now gives me a Frankenstein ROM: KE7 with the Kitchen-selected Kernel (Ninphetamine) and baseband (KH1).
I'll flash a new stock ROM with CF-Root again, but I am doubting CWM now.
Hi guys! After flashing siyah kernel 2.6.13 i cant finish a nandroid backup with the customized cwm. Does anyone have the same thing? Any ideas how to solve it?
When I run into troubles like this I've just put a kernel on that I knew did work, made the backup, and made sure that I had the desired kernel to flash back to after a restore, so basically I've substituted to get around this sort of thing.
It seems, though, that the kernels are getting more and more temperamental about which ones will flash each other by CWM recently. Siyah isnt as friendly anymore for whatever teason. Because of this I've been using mobile Odin and pulling the tar files out of CWM zips as this works regardless.
Enough space on the sdcard?
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 been using JB I9100XWLSN_I9100OXXLS8_NEE for several months without problem. Rooted, with PhilZ-cwm6-XWLSN-OXX-4.92.3-signed.
3 days ago I updated to I9100XWMS1_I9100NEELS1_NEE with no problems. Today the phone stuck and when I booted into recovery I saw the default recovery not Philz. So I flashed it again (the newer version)
But I had a boot loop, so I tried to restore nandroid backup, it didn't work.
I tried to reinstall earlier ROM (LSN) but it gave errors.
Now I can only boot to Philz recovery without doing anything.
How can I restore the phone to anything which works, so that I can root it again.
Back to stock via Odin/download mode, re-root your phone, restore nandroid or reflash custom rom/kernel & start again from scratch.
I did as you said. Flashed the earlier ROM with ODIN but still cannot boot. I just read the Galaxy S II logo at the start and the phone will not start.
Boot into recovery - factory reset ?
Edit - Failing that, search for Hopper8's 'Odin troubleshooting' thread. There's a link to a 3 part firmware in that thread, try flashing that via Odin if you can't factory reset or it doesn't work.
All right, trying.
Well I booted, thanks. If you don't mind, can you guide me further? I'll just write what I intend to do:
1- Boot into recovery and flash Philz again.
2-Using Philz, will try to restore Nandroid backup. I had copied the backup to my computer. As Philz had errors restoring the backup, I copied the one on the computer to SD card, but the MD5 had changed. So I had to disable MD5 check in Philz. Is it normal to change after copying?
Yep those steps make sense. Simply copying a nandroid from your PC back to your phone (I've done this in the past) shouldn't normally change the MD5. The only way the MD5 would change is if any of the files/directories are different in any way.
I guess you're only going to find out if this makes any difference when you try to restore the backup.
Unfortunately, the backup did not work. You need this once in a while and it fails... So dissappointing. I will have to install everything manually. Lots of backup to put into the trash!
Thanks a lot.
Maybe see what you can salvage from the nandroids you have with some of the various apps on GP that allow you to extract files from nandroids (Nandroid Browser, etc) ?
OK. I'll give a try. It would be quite an help if I rescued some.
I also have a Titanium Backup. I'll check if it does most of the job.
Yep, you should be able to get most of your apps/settings back easily with Ti given you'll be restoring them to the same rom/kernel setup. Just remember not to restore system apps or settings. Hopefully you'll be able to pull other stuff out of your nandroids (contacts/call logs/sms/calendar/etc) with those apps I mentioned if you don't have those backed up to Google/elsewhere.
Actually, I just need Call logs and SMS. Most of other stuff are already online, no problem with Contacts, etc.
I had an earlier backup of SMS but will see whether it works or not.
If Nandroid Browser saves these, all will be OK.
I restored almost everything. Just some hours spent.
Thanks again.
Good job, glad you got everything working as it should again. I know doing everything from scratch is a pain, I did a completely clean install on an I9505 on Friday night which took a few hours. You're welcome