Hi all,
the last few days, i did extensive reading concerning the whole matter of downgrading, rooting, s-offing and flashing a custom rom on my new DHD.
All steps are clear to me except one: which version of Clockworkmod Recovery should i use ?
I'm planning on flashing revolution hd where i supposedly can use either 2.5.1.3 or 3.0.0.6.
Am I right in the assumption, that its best to just use 2.5.1.3 since many modifications need this version to work. Where would i get it from ? If i download rom manager from the market, won't it just flash the latest version of CWM recovery (3.0.0.6 or .7) ?
And what makes the unofficial version "2.5.1.2 r2" from paul of modaco forums special ?
One last question: say i create a nandroid backup with 2.5.1.3 and later upgrade to a higher version (3XXX or whatever), will i still be able to restore this previously created nandroid backup ?
sorry if all these questions got answered somewhere else already, i searched but couldn't find any answers to these specific questions.
I'd stick with 2.5.1.3, everything works with it and I think if you create a backup with it and then upgrade to 3.x.x.x then it won't work when returning to your backup.
Personally, I don't see many benefits to using 3.x.x.x at all
Ah sorry, didn't notice your other question, Just download Clockwork and it will get it for you. If it wants to get 3.x.x.x then you can easily find 2.5.1.3 on a google search
thanks for the answers
just noticed that leedroid needs 2XXX, too. so i'll just get the older version.
thx again !
Actually you can restore nandroids from one version with the other. The important thing is which >filesystem< does the rom use.
I tried backing up stock rom with cwm3 and tried restoring but didn't get past boot. Reason was it was restoring it to ext4 partitions, which the stock rom doesn't support.
Then i booted cwm2.5 using fastboot and restored with that instead... no problems.
peace!
so you are saying that cwm2.5 always creates ext3 partitions on restore, and cwm3 creates ext4 ?
if that is the case, can i flash the newest revolution hd roms with cwm2.5 despite the fact that they use ext4 ?
p.s. sorry @ mods for creating this thread in the wrong forum...
-shadeless- said:
so you are saying that cwm2.5 always creates ext3 partitions on restore, and cwm3 creates ext4 ?
if that is the case, can i flash the newest revolution hd roms with cwm2.5 despite the fact that they use ext4 ?
p.s. sorry @ mods for creating this thread in the wrong forum...
Click to expand...
Click to collapse
What I do know is that cwm2.5 supposedly can't mount an existing ext4 partition whereas cwm3 can. Even if cwm2.5 lacked the support the rom you're talking about could still be flashed to ext3 and booted as ext4 (since it's forward compatible). But once it's used with ext4's new features (like extents) you're stuck.
Wiping a partition in cwm3 and then mounting it mounts it as ext4 (according to "adb shell mount". Booting cwm2.5 using fastboot and formatting same partition results in a ext3 partition.
Sorry if I confuse the matter further
Sorry if I confuse the matter further
Click to expand...
Click to collapse
no problem, i think i understand
flashing revolution hd with v2.X will create an ext3 partition, but the files that revoHD is creating later on will be kind of ext4 (does that even make sense?). but when i wipe everything it will be ext3 again, and restoring a CWM2.X backup with CWM2.x shoult be possible, is this correct ?
-shadeless- said:
no problem, i think i understand
flashing revolution hd with v2.X will create an ext3 partition, but the files that revoHD is creating later on will be kind of ext4 (does that even make sense?). but when i wipe everything it will be ext3 again, and restoring a CWM2.X backup with CWM2.x shoult be possible, is this correct ?
Click to expand...
Click to collapse
Sounds right to me Yeah it's a feature of ext4 that you can mount ext3 as ext4 but when you do so using the new features you can't go back (automatically atleast) and the partition is now ext4.
Restoring a 2.x backup with 2.x should always work since 2.x can only make backups of ext3 in the first place...
peace!
you can use 3.0.0.6 for both. Trust me.
Related
I was hoping some of you could decisively wrap up these issues for an Android newb...
ClockworkMod - What is it and what exactly does it do?
Amon RA - How is it different than ClockworkMod?
In ROM Manager, the "Flash Latest Recovery" option shows CWM v3.0.0.4 as my current and v2.6.0.1 as the latest. Why has the version been reverted?
What is a NANDROID backup? I gather that Amon RA makes a NANDROID backup, but CWM does not. Does this mean CWM backups are less thorough?
In the Amon RA recovery console, there is an option for "Nand backup" and another for "Nand + ext backup". What's the difference?
Following up with the previous question: I understand ext is a partition on my phone (I understand that much from using Linux a little). I have not changed the partition since buying the phone - is it recommended that I re-partition? What would be the ideal setup?
That's it for now. I appreciate all the help.
I never received any feedback on this post and I think it was because the title was very generic. Any help you can give would be appreciated.
NoCatharsis said:
ClockworkMod - What is it and what exactly does it do?
Amon RA - How is it different than ClockworkMod?
In ROM Manager, the "Flash Latest Recovery" option shows CWM v3.0.0.4 as my current and v2.6.0.1 as the latest. Why has the version been reverted?
What is a NANDROID backup? I gather that Amon RA makes a NANDROID backup, but CWM does not. Does this mean CWM backups are less thorough?
In the Amon RA recovery console, there is an option for "Nand backup" and another for "Nand + ext backup". What's the difference?
Following up with the previous question: I understand ext is a partition on my phone (I understand that much from using Linux a little). I have not changed the partition since buying the phone - is it recommended that I re-partition? What would be the ideal setup?
Click to expand...
Click to collapse
1. CWM is a custom recovery. It allows you to flash new roms and kernels and make backups of your current setup.
2. Ra is also a custom recovery. I prefer it over CWM. In the old days, if I remember correctly, RA backed up your wimax keys while CWM didn't. Also it was rumored that CWM didn't wipe correctly. Now I think they're pretty much the same. I just like the yellow words over the horrible green that CWM uses.
3. It may have been reverted because of the differences between the partitions on different evos.
4. CWM makes nandroid backups too. They both backup everything. A nandroid backup will back up everything on your phone. It is highly recommended to make a nandroid before you flash anything onto your phone. If it breaks something or bootloops your phone then you can restore that backup and go back to how you were.
5. The nand backs up the phone, the nand+ext backs up the phone and the ext partition on your sd card where your apps are installed.
6. The ext partition is on your sdcard. (IMO) No need for apps2sd unless you have a crazy amount of apps on your phone or you have a bunch of huge games.
NoCatharsis said:
I was hoping some of you could decisively wrap up these issues for an Android newb...
ClockworkMod - What is it and what exactly does it do?
Amon RA - How is it different than ClockworkMod?
In ROM Manager, the "Flash Latest Recovery" option shows CWM v3.0.0.4 as my current and v2.6.0.1 as the latest. Why has the version been reverted?
What is a NANDROID backup? I gather that Amon RA makes a NANDROID backup, but CWM does not. Does this mean CWM backups are less thorough?
In the Amon RA recovery console, there is an option for "Nand backup" and another for "Nand + ext backup". What's the difference?
Following up with the previous question: I understand ext is a partition on my phone (I understand that much from using Linux a little). I have not changed the partition since buying the phone - is it recommended that I re-partition? What would be the ideal setup?
That's it for now. I appreciate all the help.
Click to expand...
Click to collapse
Clockwork is a recovery. It does many different things ex. Flashing, Wiping, Partitioning etc.
RA use to be the only one to back up wimax now clockwork has this feature and with RA you was not able to navigate through folders like clockwork but now you can with the new update.
I'm not sure about the 3rd question.
A nandroid is backing up your entire phone so that you can restore if you run into any problems it backs up everything except your splashscreen or ext partition unless you choose to back that up. RA & Clockwork can perform a nandroid Clockwork didn't have the ability to backup wimax keys(4g).
Nand is everything except your partition you use the ext if you use darktremor a2sd it backs up everything and your partition.
Only repartition if you want to install apps to sd, cache, or dalvik to your sd card saves internal space on the phone.
Hope I helped
Buff McBigstuff said:
1. CWM is a custom recovery. It allows you to flash new roms and kernels and make backups of your current setup.
2. Ra is also a custom recovery. I prefer it over CWM. In the old days, if I remember correctly, RA backed up your wimax keys while CWM didn't. Also it was rumored that CWM didn't wipe correctly. Now I think they're pretty much the same. I just like the yellow words over the horrible green that CWM uses.
3. It may have been reverted because of the differences between the partitions on different evos.
4. CWM makes nandroid backups too. They both backup everything. A nandroid backup will back up everything on your phone. It is highly recommended to make a nandroid before you flash anything onto your phone. If it breaks something or bootloops your phone then you can restore that backup and go back to how you were.
5. The nand backs up the phone, the nand+ext backs up the phone and the ext partition on your sd card where your apps are installed.
6. The ext partition is on your sdcard. (IMO) No need for apps2sd unless you have a crazy amount of apps on your phone or you have a bunch of huge games.
Click to expand...
Click to collapse
Buff nailed it great, I'll explain #3.
Clockworkmod team jumped the gun with their 3.0 recoveries betting that all the developers had switched to the newer edify scripts which appeared with Froyo and are required to script a Gigngerbread rom. The older scripting used ammend which is what 90% of the developers are still using. This made the 3.0 based recovery incompatible with 90% of the roms out there so Cloockwork team had to come up with a backward compatible release and numbered it 2.6.01. This is the version you need unless you are going to install the CM7 roms. 2.6.0.1 is compatible with all hboots, all partitions, and backs up and wipes everything Aman RA does so they are pretty much equal. The difference is if you flash the clockworkmod recovery all the features of rom manager will still work, if you flash aman ra, rom manager is useless.
So then at this stage is one better than the other?
I'm still new to "daily" ROM flashing and liked the ROM Manager but heard that RA was better (have that now)
I'd like the ease of switching between ROMs to figure out likes/dislikes.
ucf.elk said:
So then at this stage is one better than the other?
I'm still new to "daily" ROM flashing and liked the ROM Manager but heard that RA was better (have that now)
I'd like the ease of switching between ROMs to figure out likes/dislikes.
Click to expand...
Click to collapse
About the same now. I actually prefer coming here and reading threads and manually downloading and flashing my roms over rom manager. I like to see screenies and see changelogs and read feedback.
Sent from my nook COLOR.
DesireHD, latest clockwork, latest cm7nightly. When I go into recovery, nandroid backup fails on mounting SYSTEM partition. Any ideas? Tnx.
edit: system is ext4, latest rom manager installs obsolete recovery that doesn't support ext4. bleh.
Galaid said:
DesireHD, latest clockwork, latest cm7nightly. When I go into recovery, nandroid backup fails on mounting SYSTEM partition. Any ideas? Tnx.
edit: system is ext4, latest rom manager installs obsolete recovery that doesn't support ext4. bleh.
Click to expand...
Click to collapse
live and learn people, the OP for the nightly builds tells you to install CWM 3.x, if you ignore this CWM will not function properly, please read the threads before posting problems
Hi guys, I've been trying to flash the CM7 HBOOT over the past few days but can't seem to get it to work. Basically, I used the Fastboot method and it was successful but got stuck on the Splash screen (did wipe cache and dalvik cache and restore nandroid).
The problem is I can't seem to find a guide on how to resize the partition to those in given in the partition tables. Could someone please be kind enough to help me with that?
I've also tried the Bootloader method (with the goldcard) but it doesn't work. It doesn't recognise that the PB99IMG.zip file is there.
Help would be much appreciated!
Hi,
I just posted a "how to" about CM7:
http://forum.xda-developers.com/showpost.php?p=13084241&postcount=17
Perhaps it can help you.
Let me know
steph_htc said:
Hi,
I just posted a "how to" about CM7:
http://forum.xda-developers.com/showpost.php?p=13084241&postcount=17
Perhaps it can help you.
Let me know
Click to expand...
Click to collapse
Awesome man! Just one question. If I use the second method, will it resize the partitions automatically?
If you're looking to resize the partitions yourself so you have a different amount of space for /cache and /data and all that, I have no idea how it's done, but it's clearly possible since people make these different Hboot files.
If you're wondering why you're stuck at the splash screen it's probably because your NANDroid restore is too large for your new partitions. Even if you were running CM7 before you flashed the new partitions your /cache would have been too large to fit in the MUCH smaller (5MB) new partition. You should have (though maybe you did) wiped your cache and dalvik first, then taken an NANDroid back up to have it fit. If you didn't wipe them before taking a back up you will need to just flash the ROM again and not use your backup. Should get you back up and running.
bangrahman said:
Awesome man! Just one question. If I use the second method, will it resize the partitions automatically?
Click to expand...
Click to collapse
If you are referring to the partition on the sd, I don't think so.
You can use the recovery mode to resize your partition (backup your sd card before...)
jordan.harris01 said:
If you're looking to resize the partitions yourself so you have a different amount of space for /cache and /data and all that, I have no idea how it's done, but it's clearly possible since people make these different Hboot files.
If you're wondering why you're stuck at the splash screen it's probably because your NANDroid restore is too large for your new partitions. Even if you were running CM7 before you flashed the new partitions your /cache would have been too large to fit in the MUCH smaller (5MB) new partition. You should have (though maybe you did) wiped your cache and dalvik first, then taken an NANDroid back up to have it fit. If you didn't wipe them before taking a back up you will need to just flash the ROM again and not use your backup. Should get you back up and running.
Click to expand...
Click to collapse
OHHHHH!!! Thank you so much dude. Cleared a lot up for me.
Okay.This is so damn annoying now lol. I've done everything correctly. Wiped everything, flashed cm7 hboot SUCCESSFULLY and restored my nandroid yet it STILL freezes on the splash screen.
I checked the size of the cache partition in my backup etc. and it was only a few kb so clearly small enough to fit in the cache partition of CM7 Hboot. I just don't get why it doesn't work!
steph_htc said:
Hi,
I just posted a "how to" about CM7:
http://forum.xda-developers.com/showpost.php?p=13084241&postcount=17
Perhaps it can help you.
Let me know
Click to expand...
Click to collapse
Great work...fastboot with a GUI - the safe way to flash.
bangrahman said:
Okay.This is so damn annoying now lol. I've done everything correctly. Wiped everything, flashed cm7 hboot SUCCESSFULLY and restored my nandroid yet it STILL freezes on the splash screen.
I checked the size of the cache partition in my backup etc. and it was only a few kb so clearly small enough to fit in the cache partition of CM7 Hboot. I just don't get why it doesn't work!
Click to expand...
Click to collapse
When you flash the cm7 hboot, did you check after the restart that hboot version was CM7?
Instead of restoring your rom could you try to reinstall a CM7 ROM?
Just to check it at least you can have a phone working…
Let me know
you cant restore NANDROID made on stock hboot, while on CM7 hboot, at least not a full restore (all partitions)
steph_htc said:
Hi,
I just posted a "how to" about CM7:
http://forum.xda-developers.com/showpost.php?p=13084241&postcount=17
Perhaps it can help you.
Let me know
Click to expand...
Click to collapse
Exactly what i was looking for!
Thankyou!
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.
So, I'm planning to finally S-OFF, mainly for the extra internal storage, and the extra speed since I won't be needing my ext3 parition any longer, so just to get some things straight -
1) I am currently on the latest Oxygen ROM, is it OK to S-OFF with this ROM?
2) I've made a nandroid backup of my ROM for restore, thing is, once I re-partition without an sd-ext, what happens when restoring the nandroid? Because when restoring, it needs to restore sd-ext... What do I need to do?
Thanks
As far as I know, Oxygen has a built in a2sd enabled when it sees that you have an EXT partition and might mess up Alpharev's (and or Revolutionary's) S-off process accourding to their site. I suggest you flash CM7 rom temporarily then S-Off with this installed since natively it doesn't support A2SD.
I'm not sure about the 2nd question. My logic tells me that I leave the ext, and do a nandrestore because it will obviously look for an ext partition to flash the data files back. The problem is once, restored and rebooted I don't know if there is a command or zip file you can flash to undo the a2sd and transfer the data from the ext to the data partition of the phone.
It would be better to go do a fresh reinstall of the rom and use titanium backup to restore your apps back.
Thanks, I probably will do the long TB restore process.
Re. the ROM issue - Will flashing Leedroid 2.5.0 Froyo ROM be good enough? As it seems to be pretty stock-ish.
Quoting Alpharev.nl
Requirements:
The only requirement right now is that the ROM you're running is rooted.
As techniques such as 'data2ext' have been popping up, these might disturb our finely-tuned flashing process.
Please revert to a rooted stock ROM if possible. Your /data partition is used for temporary storage of important files.
Click to expand...
Click to collapse
For my understanding as long as the ROM doesn't use data2ext, or 'anything'2ext out of the box it's good to go. I've S-off with Cyanogenmod rom on my phone so I can only speak from what I experienced.