I have nandroid backed up from cwm 4.02.1 and flashed new cwm 5.02.06 but it wont let me restore from 4.02.01 nandroid back up or vice versa is there any fix for this?
thanks in advance
I made a thread about this a few weeks back and people say that the old backups should be reverse compatible is your on the new version you should be able to restore old back ups from 4.xx. glad I didnt find out the hard way ans read it here..
Can't mount sd card in CWM???
Any ideas on why ver 5.xx CWM won't mount the internal sd card yet version 4.xx* will.
I've flashed kernels that use v4.xx (in my case it is an Orange version of CWM) and can make/restore backups with no problem.
But....if I ODIN or flash a kernel (i.e. Lostkernel) that uses the newer release of CWM, the kernel is there fine but CWM can't mount the sd card!
Related
So, I've decided I'm going to use ROM Manager to flash a previous version of CWM (2.5.1.4). I'm currently running the 3.0.0.2 but feel stuck from all the reports I've been reading about the latest version not being compatible with older hboot and partitions. I'm scared to do anything...
Anyways, while in 3.0.0.0 I did a back up. Is this going to be compatible with the older version or should I do another one after flashing back?
Also, I don't remember it actually saying "nandroid". It just said "backup". This is the same I'm assuming as it took quite a while to do???
Ok, never mind. Apparently I'm trying to flash that older version and it keeps coming back with an error.
Worked for me.
I restore a 2.x.x backup trough 3.x.x and had CWM 2.x.x then after I backed up some apps with titanium backup I went back to the rom I backed up with 3.x.x and all went fine.
Little confusing but yes I believe you can.
Sent from my PC36100 using Tapatalk
If you want 2.5 again go to post #7 in this thread. Put the file on your sd and power down into bootloader. It will scan the card then ask if you want to update, hit volume up for yes and you're done. Thread- http://forum.xda-developers.com/showthread.php?t=894227
Sweet!!! I just flashed back to the older 2.5.x.x CWM and then flashed a ROM with no problems at all. The only thing that's weird is that ROM Manager still says I have CWM 3.0.0.2.
1.) From what I've read, CWM 2.x doesnt handle GB's ext4 partition, and you need 3.x for that. What will I lose/gain if I update to 3.x?
2.) If I do decide to use CWM 3.x, will I still be able to go back to my Froyo's file system?
3.) How do I get back to the nandroid backup of my Froyo 2.2.1? Can I use CWM 3.x as well? Do I just restore the backup I've made? What about the filesystem?
4.) Assuming I can just go back from GB to my Froyo by restoring through the nandroid backup I made, will the custom kernel I've flashed with it also come back with the restore?
I have flashed back and forth between Froyo and GB ROMs using CWM 3.x. If it doesnt work, can't you always reflash CWM 2.x ?
Anyway, you ask too many questions .. Like the rest of us, you should throw caution to the wind and try it out yourself.
i guess im just one of those people.
anyway, thanks for the response. cleared a few things for me.
I don't even flash recovery. That way I can use whatever recovery I want and keep stock recovery so I don't get cwm popping up when I charge and the phone is off.
./fastboot boot recover.img
Someone swyped my idea.
Apologies for what is probably an often asked question, but the search seems to be down at the moment. I'm currently running Ras 2.3 and when I make a nandroid backup of my MIUI, it always runs into an error when trying to restore? I don't even know where to begin looking for solutions to the issue, is this a common thing? Should I just re-flash Ras or something?
Seems the backup was corrupted, reflash your recovery, then make a new one.
Yeah every backup I do seems to get corrupted. I'll try reflashing AmonRa.
thegregbradley said:
Yeah every backup I do seems to get corrupted. I'll try reflashing AmonRa.
Click to expand...
Click to collapse
Let me know how it goes. Also make sure to have at least ~500mb available for a backup.
So I finally re-flashed AmonRa 2.3, and my nandroids STILL show an error! It gets like one dot into resotring and says "oops! an error occurred, check the logs" or something like that. What is happening
first thing would be to check your memory card to see if you have enough space like the post above says. if that doesn't work move the recovery.log via your recovery screen to the sd card and post it here. that should get some questions answered.
edit: also i had this happen to me a couple times when trying to restore it only happened when i changed big things like the radio or the hboot or switching from aosp to sense. that kinda stuff. you might just need to start over and flash a new rom. good thing you used titanium...right? p.s. just relized you were trying to restore not backup so the memory card issue shouldn't apply sry.
I have my MIUI backup so it's not so much of a big deal since that works, but I'd like to have a 100% working nandroid backup in the event that I wanna try out a new rom. Where to I find the recovery log so that I may post it up on here? Thanks for the help guys, I'd be lost without xda
So I just tried moving my recovery log to the SD card and I got the same message, "Oops... something went wrong! Please check the recovery log!"
WTF is going on here?
Potential causes and solutions:
Corrupt SD card. You're screwed, reformat SD card and flash the rom over again.
Corrupt Nandroid file. You're screwed, delete from SD card and flash the rom over again.
Corrupt Recover. Download Rom Manager and re-flash recovery (if you use clockwork, flash alternate then back to clockwork or vice versa if you use amon ra). If this doesn't work, it's likely one of the two above.
However, this is usually the problem when they mess up.
Is there a space in the name of the Nandroid backup? Nandroid backups can NOT EVER have a space in the title. Go into your favorite file manager and remove the space if it has one and it should work just fine.
For example:
MikFroyo 4.61 is NOT an acceptable name. There's a space between the o and the 4.
KonisEliteSeriesIII IS an acceptable name. Notice, there's no spaces.
Hit the thanks button if I helped. Toodles!
Don't use ROM Manager to reflash Amon Ra. Just use the PC36IMG
Trust me on this.
Is it possible that your original nandroids were with clockwork and now that you have updated to amon that they will not work?
Okay so I've re-flashed Amon Ra and reformatted my SD card and I STILL can't get the nandroids to work or my recovery log to move over to the SD card! I've only used Amon Ra for as long as I've been rooted, and nandroids previously worked. Also, these are nandroids that I made within the last 2 weeks or so, they're not old and I have not renamed them. Should I maybe try an older version of AmonRa or something?
OMG I figured it out! Here's the story:
So I bought a new SD card a few weeks back and put it in with just a straight copy of my old SD card in there. This included my nandroid folder. I had been making backups and deleting old backups, but the folder under sdcard/nandroid/HT089HL02240 simply needed to be deleted. I kept sdcard/nandroid, deleted HT089HL02240, then made a new nandroid so that the recovery could simply make this folder itself. Somehow this worked, I don't know why, but it seemed like it might help being that you can't restore nandroids between phones. Perhaps the recovery thought I was attempting to do this, given the SD card switch. Well it works now!
few days ago I just flashed cwm recovery and made a backup for every partition, after that I flashed the cm7.2.
but now when I want to go back to stock, I cannot restore the backup. it seemed that the recovery cannot format the partitions into rfs. (even I used the rfs+ext4 recovery)
anyone has any ideas?
Did you have an ext4 partition when you did the backup? I've experienced problems with the CWM backup a couple of times because it's not getting along well with ext4 partitions so I had to go from scratch a couple of times because I couldn't do a restore. For Galaxy Gio, I would recommend you to use Titanium Backup instead of CWM Recovery from now on if don't want to get into trouble with backups and stuff.
Just flash a new firmware via ODIN.
LegoGabi said:
Just flash a new firmware via ODIN.
Click to expand...
Click to collapse
thanks for replies but my original firmware contains chinese which cannot available here
Try this:
1) flash some stock multi-package firmware (that would format your FS to rfs from ext4); shouldn't matter much what firmware you flash, just something Gingerbread-ish to allow CWM to work, as you only need it to format partitions
2) flash CWM (or install via update.zip method from recovery) that works with stock firmware (I believe it's the one with rfs+ext4 support but you better check in CWM thread)
3) restore your stock ROM backup
Have you checked Samsung firmware websites like samfirmware to see if they had yours?
If not, there are instructions here on creating an Odin flashable backup, which you could do if you have access to another, unmodified Gio.
Otherwise, look into the workings of CWM. You may be capable of DD'ing the nandroid files manually, but don't take my word for it.
thanks everyone who replied, i finally figured out what's wrong.
It turned out to be the problem that no CWM for gio could format the partitions into rfs therefore they kept giving me errors when i tried to restore.
and after some trials, I found that the CWM for CM7 (cwm-v2.zip) can actually restore my backup, but with the system, data, cache formated in ext3. Therefore with the stock kernel, it won't boot.
Final remedy: use CWM for CM7 to restore the backup, then flash a custom kernel for stock rom.
crescal said:
thanks everyone who replied, i finally figured out what's wrong.
It turned out to be the problem that no CWM for gio could format the partitions into rfs therefore they kept giving me errors when i tried to restore.
and after some trials, I found that the CWM for CM7 (cwm-v2.zip) can actually restore my backup, but with the system, data, cache formated in ext3. Therefore with the stock kernel, it won't boot.
Final remedy: use CWM for CM7 to restore the backup, then flash a custom kernel for stock rom.
Click to expand...
Click to collapse
Which kernel? Im in your exact situation, i got the cwm you mention and it restored the back up and flashing the kernel for stock rom with lots of options claiming to support ext4 i get boot loops. If you can tell me what kernel you booted with i will be very grateful. Tomorrow is my daughters bday and i need my korean gio with different wifi hardware to tether to my tablet for ideo chat, which only works with stock. Thank you.
Hello, If I make a Nandroid backup, I know it doesn't back up the custom kernel currently used, but I don't plan on changing the custom kernel (Glitch) ever, so if I were to use that nandroid backup in the future to recover, will I have to reflash the kernel again?
Also, can a Nandroid be converted to zip, and stored on an external SD (that CMW, and Phillz touch can mount and use)?