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.
Related
My wife got an Epic, while I have an EVO. I'm quite familiar with rooting, ROMs, etc. I think I've got all the Epic-specific details down, but I wanted to ask this question to make sure I've got this down.
I plan to use this root method. After that, her phone will be left with a basically stock, 2.2 ROM that uses the EXT4 file system, and Clockwork recovery image. I read that I won't be able to flash new versions of Clockwork from within ROM Manager. From then on, I will need to stick with ROMs designed for the EXT4 file system or both EXT4 and RFS. I assume I flash ROMs and Kernels just like with my EVO: choose my ROM, it will come with a kernel, but I can flash whatever kernel I choose on top of that (as long as my ROM matches my Android type, DK or EB). There are currently no Gingerbread ROMs for the Epic, but when they are released, I should be able to use CM 3.x to flash them.
OK, I would greatly appreciate if someone could just read over that and let me know if I understand anything incorrectly. Also, if someone could tell me if there's a good reason to choose Odin's recovery vs. Clockwork, I would very much appreciate that as well.
Odin Vs. Clockwork
Everything you posted above sounds accurate.
I use Clockwork to flash my ROMs just because it is easier to me (no cables involved). The only time I use Odin is when my phone is bricked. This has happened after installing Samsung updates, but it is very easy to use Odin to restore back to Stock, then flash a new ROM over.
One advantage to Clockwork is that some ROMs support a full backup. I use Bonsai4All and during installation from Clockwork it will backup your information, then restore it. As far as I know, Odin is not capable of any such thing.
Hope this helps...
OK wait, some ROMs support full backup? Why couldn't I do a full nandroid backup with any ROM I'm running from within Clockwork Mod Recovery?
WrlsFanatic said:
OK wait, some ROMs support full backup? Why couldn't I do a full nandroid backup with any ROM I'm running from within Clockwork Mod Recovery?
Click to expand...
Click to collapse
You can use these two zips from within clockwork if you are flashing a rom that doesn't backup/restore for you.
Flash the "backup" before you wipe anything and then after you flash the rom - before you reboot - flash the "restore".
These .zips take care of data/settings/apps. Not actual system items, so they don't seem to cause some of the issues that programs like Titanium Backup cause.
EDIT: It's always good to do a complete backup within Clockwork before flashing ANYTHING new. Roms, zips, etc.!
Awesome! Thanks! I can't believe that Clockwork isn't working any better than that where it has problems backing things up. I know the EVO gets a lot of dev love, but seriously... SO much easier.
Hey, this may seem like a silly question but i would rather ask it than brick my device.
I have rooted and s-off my stock rom, i have installed all my apps and settings and ive got it just the way i like it. i have created a nandroid backup using clockwork mod.
I now want to try Gingervillian rom, ive got titanium backup to install all the apps back and that but what i want to know is:
Will i be able to restore my stock rom from the nandroid backup with all my apps and setting in tact, even though s-off is set and its rooted. i know a read somewhere that flashing a stock rom on a phone with s-off can semi-brick it... so will clockwork recovery do the same?
When you make a 'nandroid' backup via ROM manager/CWM Recovery, it makes essentially a carbon copy of the current setup of your ROM (not your radio, S-Off status, etc.). Literally everything is perfectly as you have it now. It just like doing a full HDD backup of your computer.
When you restore this backup, it simply brings back your ROM from exactly how it was. There is no effect on your root or S-off, or your radio.
So, if you do a nandroid backup, then wipe the device and flash another ROM i.e. Gingervillain, and make a nandroid of that, you can then freely switch back and forth between the 2 (or more) recoveries via ROM manager/CWM Recovery, with no issues.
The issues with bricking as you're referring to are if you for some reason try to somehow flash a non-rooted ROM, which would most definitely cause issues. In order to get back your phone to stock-stock-stock-stock (unroot and S-on), you will need to follow unroot instructions and flash an official unrooted RUU/PC10IMG.zip to get back to everything as it came out of the box.
Hope this helps, let me know if I need to clarify.
thank you very much matey much appreciated!!
Well I'm not sure if this is the right forum, if not please just point me in the right direction. Well after upgrading to Gingerbread (ota) I rooted my phone, I flashed a new kernel and now alot of things are messing up; I cant access wifi, watch videos, take pic/vid, etc etc. I'm just wondering how I can return it back to the original Gingerbread kernel? I just want it to work right again. I guess I didnt backup my phone right because I dont see a backup file.
If you did a backup, boot into recovery and try to restore. Your recovery knows where the backup is stored.
I'm sure there's a download for the stock HTC kernel, but I don't know where. I've really been out of the loop on Sense stuff recently.
Find the stock rooted rom (the odexed version) and download it. Put it on the root of your SD card and boot into recovery. Make a nandroid backup even though your phone is messed up, at least it boots. Wipe cache and dalvik cache then flash the rom. You should be good to go.
If that doesn't work then restore your backup. Backup any apps/data you want to save with Titanium Backup. If you want to save texts, there are apps for that. Then boot into recovery and do a full wipe and flash the rom. You can restore your apps and texts once you have the rom booted and set up.
You flashed an incompatible kernel - probably an AOSP kernel. Next time read a little more about what you're doing and make sure that you fully understand something before you do it.
Sent from my Evo + MIUI using Tapatalk!
It's not hard. You just have to flash a kernel that matches your ROM, be it Sense or AOSP. I'm assuming you're running Sense, so just look for a Sense Kernel.
Put it on your SD Card, clear Dalvik-Cache and Cache and flash the kernel and you should be OK
Mount data in recovery before you flash the kernel. After wiping cache and dalvik, as mentioned earlier
Make sure you are using a Sense Gingerbread kernel. Custom kernels include ChopSuey, Freedom, Golden Monkey and newest PoonSense.
Sent from my PC36100 using xda premium
Check here for the stock kernal
http://forum.xda-developers.com/showthread.php?t=1176545
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.
Hi all,
I'm having trouble restoring backups when I go between GB and JB. Sbrissen's lastest Alpha build is the JB I'm using. Everything goes fine with the restore until "Data". Then the restore fails. I mobile odin the EL29 with autoboot into recovery, install the ROM (JB in this example) . I then try to restore a backup I made with the same exact version of CWM from the same exact ROM that I used to create the back up. Maybe a better question is How can I create a JB backup, go back to GB, and return to JB and restore that backup. Cause what I'm doing isn't working.
Thanks
Which GB ROM are you coming from? GB recoveries should be safe so you shouldn't have to Odin to EL29, unless you're on a stock ROM without a custom recovery. Also are you wiping system, data, cache, and dalvik cache prior to restoring your backup?
mwcarnage said:
Which GB ROM are you coming from? GB recoveries should be safe so you shouldn't have to Odin to EL29, unless you're on a stock ROM without a custom recovery. Also are you wiping system, data, cache, and dalvik cache prior to restoring your backup?
Click to expand...
Click to collapse
I'm using the latest Blazer GB Rom. I'm wiping everything also,factory reset,cache,dalvik cache, etc. I have to flash back to GB to update an app that requires my correct serial number to work, JB Roms do not do this at the moment so the app wont work. That is the reason for flashing back to GB (didn't want to mess with ICS for obvious reasons). I'm coming from HTC Evo 4g so things are a little different. On the Epic 4G, I was under the impression you had to use the same recovery to restore that was used to create the backup. Can I just jump back and forth between GB and JB using the nand backup with each others recovery? GB's CWM is 5 and JB's CWM is 6. I didn't think you could because if the backup won't restore with the same CWM is was created with, how would it restore with another version? Still a little foggy on the process E4GT uses.
Thanks
dal320driver said:
I'm using the latest Blazer GB Rom. I'm wiping everything also,factory reset,cache,dalvik cache, etc. I have to flash back to GB to update an app that requires my correct serial number to work, JB Roms do not do this at the moment so the app wont work. That is the reason for flashing back to GB (didn't want to mess with ICS for obvious reasons). I'm coming from HTC Evo 4g so things are a little different. On the Epic 4G, I was under the impression you had to use the same recovery to restore that was used to create the backup. Can I just jump back and forth between GB and JB using the nand backup with each others recovery? GB's CWM is 5 and JB's CWM is 6. I didn't think you could because if the backup won't restore with the same CWM is was created with, how would it restore with another version? Still a little foggy on the process E4GT uses.
Thanks
Click to expand...
Click to collapse
dal320driver said:
Hi all,
I'm having trouble restoring backups when I go between GB and JB. Sbrissen's lastest Alpha build is the JB I'm using. Everything goes fine with the restore until "Data". Then the restore fails. I mobile odin the EL29 with autoboot into recovery, install the ROM (JB in this example) . I then try to restore a backup I made with the same exact version of CWM from the same exact ROM that I used to create the back up. Maybe a better question is How can I create a JB backup, go back to GB, and return to JB and restore that backup. Cause what I'm doing isn't working.
Thanks
Click to expand...
Click to collapse
I've gone from rooted EL29 back to a a JB ROM and restored with no issues. The ROM I use is Paranoid Android. I usually allow my phone to boot then reboot into recovery before restoring. Hopefully this isn't a stupid question, but sometimes things get forgotten/overlooked when flashing ROMs. Anyways, did you flash the JB gapps after flashing the ROM? Just asking since this step was not in your posts.
mwcarnage said:
Which GB ROM are you coming from? GB recoveries should be safe so you shouldn't have to Odin to EL29, unless you're on a stock ROM without a custom recovery. Also are you wiping system, data, cache, and dalvik cache prior to restoring your backup?
Click to expand...
Click to collapse
kmok said:
I've gone from rooted EL29 back to a a JB ROM and restored with no issues. The ROM I use is Paranoid Android. I usually allow my phone to boot then reboot into recovery before restoring. Hopefully this isn't a stupid question, but sometimes things get forgotten/overlooked when flashing ROMs. Anyways, did you flash the JB gapps after flashing the ROM? Just asking since this step was not in your posts.
Click to expand...
Click to collapse
Yes, I flashed JB gapps also. I'm not having trouble re-flashing the ROM's back and forth. . This part is successful. The problem is when I go back into recovery and try to restore a backup (of either ROM just flashed) it isn't working. Sorry for the confusion.
Thanks
dal320driver said:
Yes, I flashed JB gapps also. I'm not having trouble re-flashing the ROM's back and forth. . This part is successful. The problem is when I go back into recovery and try to restore a backup (of either ROM just flashed) it isn't working. Sorry for the confusion.
Thanks
Click to expand...
Click to collapse
Okay, I was just making sure something wasn't forgotten when you were going back to JB this time around. I figured you were able to get the different ROMs working since you were able to make a backup of the JB ROM you were using. AFAIK the different versions of CWM (5 vs 6) shouldn't matter in this situation. Hopefully someone else has had the same problem and will be able to chime in.
CWM6 creates backups differently than CWM5 or most other recoveries. Instead of putting the entire backup in one folder, it has a separate Blobs folder that contains a lot of the data. If the folders get separated, the backup won't get restored correctly. Did you by any chance move the main folder or delete the blobs folder?