What's the latest version available?
I'm using 5.5.0.4
How do you do an upgrade if necessary...sorry for the noob question.
I just don't want to brick my note with an incorrect CWM.
There is nothing 'wrong' with CWM v5.5.0.4.
You don't need to upgrade.If a ROM requires a different CWM, its usually packaged with the ROM and you just follow the instructions in the OP(ex. CM10 uses v6.x, but that doesn't mean you replace your working CWM v5.x, its fine to not be on the latest CWM).CM10 comes with CWM v6 and its automatically flashed when you flash the CM10 rom with your CWM v5.x
Hope you got all that
Related
I currently have ClockworkMod 2.5 and am trying to upgrade to 3 to install CM&. I currently have Doc's ROM, if that makes any difference.
ROM Manager doesn't give me any options to update to v3.
The CM7 wiki has steps to update for non-rooted users, but I don't think I need to do that.
I am looking for a CWM download to install via Odin. Is this the simplest method?
I've searched this forum as well as the web, and I can't find anything related to the Vibrant.
Any tips would be appreciated...
Do you know that Vibrant has its special sub-forum?
Edit: Yours is Bell's Vibrant. Never mind then. Just flash speedmod kernel.
That's it... Flash a kernel that it has cwm... Isn't depending of the rom.
Escrito desde mi Galaxy S
Have you tried using ROM Manager and selecting Flash Clockwork Recovery?
For me it asked me what phone I was using (select Galaxy S MTD if you want to use CM7) and then asked what version of CMW I wanted. Just choose CWM3.x there and you should be fine. It will tell you that your current phone isn't supported, blah blah, but ignore it.
I'm sure he's going to install CM7, not already installed. Just use speedmod kernel. There's no need for CWM 3. If you got CM7 installed, it's automatically CWM 3.
mawardi said:
I'm sure he's going to install CM7, not already installed. Just use speedmod kernel. There's no need for CWM 3. If you got CM7 installed, it's automatically CWM 3.
Click to expand...
Click to collapse
Actually it is not completely automatic, you still need to flash a CWM3 recovery from inside ROM Manager, otherwise you can't see CM7 Nightlies from ROM Manager.
Thanks all.
I was able to get CM7 on my Bell Galaxy S.
I did try the ROM Manager but I couldn't get it to update CWM. It would try to install from Android recovery 3e, not CWM.
After many loops of stock 2.3.3, Doc's ROM 2.2.1, CM7 Nightly 15, and other steps, I was able to manually flash the nightly 18 using CWM.
For some reason, the update method for stock mentioned on the CM7 Galaxy S didn't work for me. Even after flashing speedmod kernel, I still came up with CWM 2.5.
Also, even with CWM 2.5, I was able to flash nightly build 18. Hope this helps someone else trying to update CWM.
Hi guys, i have a small question.
I have installed back in august in gf's X8 kuya droid and i want to replace it with CM7.1 official. i am kinda lost with unlocked bootloaders and the rest, phone is now rooted with latest kuyadroid xrecovery and CWM 3.XX in it.
As i have it in my mind, the process is to install the new CWM 4.XX in xrecovery and then boot into CWM and flash CM7.1 as normal (wipe data/cache/dalvik and then install zip from sdcard).
Or do i have to do something else ? i also have a backup of the original rom, do i need to restore this and then flash CM?
thank you for your time
Invicta said:
Hi guys, i have a small question.
I have installed back in august in gf's X8 kuya droid and i want to replace it with CM7.1 official. i am kinda lost with unlocked bootloaders and the rest, phone is now rooted with latest kuyadroid xrecovery and CWM 3.XX in it.
As i have it in my mind, the process is to install the new CWM 4.XX in xrecovery and then boot into CWM and flash CM7.1 as normal (wipe data/cache/dalvik and then install zip from sdcard).
Or do i have to do something else ? i also have a backup of the original rom, do i need to restore this and then flash CM?
thank you for your time
Click to expand...
Click to collapse
OK, you need to first unlock your bootloader by following the guide linked below (It is a lot easier than it lookas at first glance, so dont be too scared about it);
http://forum.xda-developers.com/showthread.php?t=1254225
Unlocking the bootloader is the hard part, once you're past this you're laughing.
Now jumping ahead a bit....
Once the phone has an unlocked bootloader, all that is left to do is flash a custom kernel and loader (loader and bootloader being different things as the guide explains). Note that all the the custom kernels have CWM already built in as part of the kernel so you wont need to worry too much about that. Once done, flash the rom and GApps Enjoy super fast Android OS.
NOTE: I had problems using the FlashTool provided by the guide, instead I used the most recent version of FLashTool which is easily found via google.
Good luck!
If you need any further help either reply here or PM me!
Good luck!
Invicta said:
i want to replace it with CM7.1 official.
Click to expand...
Click to collapse
If by "CM7.1 official" you mean the Shakira ROM by the FreeXperia project that's for download on the CyanogenMod website I strongly advise you against it.
The ROM is buggy as hell, feature incomplete AND the "too low volume on calls" hasn't ever been fixed.
If you want to take the trouble to install a custom ROM that needs a custom Kernel I'd rather recommend you nAa's MiniCM7 2.1.9 ROM and nAa v11 Kernel.
Take my word that the FXP CM7 Shakira ROM isn't worth the time and effort.
B.Jay said:
If by "CM7.1 official" you mean the Shakira ROM by the FreeXperia project that's for download on the CyanogenMod website I strongly advise you against it.
The ROM is buggy as hell, feature incomplete AND the "too low volume on calls" hasn't ever been fixed.
If you want to take the trouble to install a custom ROM that needs a custom Kernel I'd rather recommend you nAa's MiniCM7 2.1.9 ROM and nAa v11 Kernel.
Take my word that the FXP CM7 Shakira ROM isn't worth the time and effort.
Click to expand...
Click to collapse
Agreed. I'm running the latest MiniCM7 build with nAa Kernel; It's amazingly stable... B.Jay you're so efficient and helpful.... thumbs up! You've already helped me today and I see you're back helping others!
yeah, i did some research and found that cm7.2 official sucks big time.
I have decided to install kuya's latest 4.5.4 rom, thing is that when i flashed 3.2.175 it installed xrecovery and cwm 3.XX simultaneously, i mean if you choose to reboot it gives you two options
-boot into xrecovery
-boot into CWM
i dont know if 4.5.4 version can be flashed with CWM 3 version or xrecovery, dev. wont mention.
I can even find CWM 4.xx version for this phone, damn....
I have never upgraded CWM version 3 to 4, any guides on how to do it?
Invicta said:
yeah, i did some research and found that cm7.2 official sucks big time.
I have decided to install kuya's latest 4.5.4 rom, thing is that when i flashed 3.2.175 it installed xrecovery and cwm 3.XX simultaneously, i mean if you choose to reboot it gives you two options
-boot into xrecovery
-boot into CWM
i dont know if 4.5.4 version can be flashed with CWM 3 version or xrecovery, dev. wont mention.
I can even find CWM 4.xx version for this phone, damn....
I have never upgraded CWM version 3 to 4, any guides on how to do it?
Click to expand...
Click to collapse
You can flash kuyaDROID 4.5.4 with either version of the recoveries, though using CWM is recommended.
About "CWM and xRecovery": Be glad that you have both as CWM version 3.x.x.x has a bug that creates defective backups. Meaning: you can restore a backup you created, but chances are that your device won't boot. Creating a backup through xRecovery is the safe fall-back here.
At any rate - puppet13th, creator of the "x8Toolbox" and "ODEX (on any ROM)", is currently attempting to make CWM 5 work. I already gave a beta-test version a try, but it locked up at the Sony Ericsson logo.
In short: See the dual recovery installation as a welcome gift, not something that "gives you two reboot options you don't want to have".
Hello. I recently installed Arco's recovery and ICS (cm9), but now I have to install a Gingerbread - based rom. Is Arco's recovery compatible with non - ics roms or do I have to flash the old cwm again?
Thanks.
xMirmo said:
Hello. I recently installed Arco's recovery and ICS (cm9), but now I have to install a Gingerbread - based rom. Is Arco's recovery compatible with non - ics roms or do I have to flash the old cwm again?
Thanks.
Click to expand...
Click to collapse
Hello I am using Arco too~~may I ask u that how to install the recovery and ICS?
I rooted Arco already, should I try to unlock the BL and then install an ICS ROM for LT18?
really dun know what to do....
thanks very much~~~
Can you still go to recovery? If you can reflash CM9 to get CWM back. If you don't flash a new kernel with odin
Well... if you install a new ROM your recovery gets lost so you'll have to flash it again anyway.
CWM 6
I've built a new recovery. Could someone test it? Here is the link: https://docs.google.com/file/d/0BwlE_OdJFnPgLUdUcG55R0dUMGs/edit#
You can flash it using broodplank's Quick Flasher or with dd command. Flash it at your own risk.
I have an untouched Note running stock ICS 4.03 -- Kernel 3.0.15-N7000XXLPY ...). I'd like to be able to safely flash a custom ROM, avoiding the brick bug. I've been digging through a lot of threads, but some uncertainties remain.
Here's what I'm about to do: I'll get the Philz kernel matching my current rom (this would be PhilZ-cwm6-XXLPY-XEN-v3.99, right?), boot into stock recovery, flash the .zip from the sd card, and boom, I'll have a safe kernel with root and CWM to flash any ROM from. Is this about the right plan?
2 more specific questions:
1. The matching Philz kernel was posted under the headline "Update to all ICS 4.0.4 kernels from 3.71 ---> 3.99" in the Philz kernel thread. But I'm running 4.03. So is this the right kernel for me?
2. Will the ROM I install after that have to match the Philz kernel in some way? I'm thinking of getting the Official CM 10.1 from the nightlies thread.
Thanks so much!!
That's the right plan
1. The correct rom is found under rom build which is the last in the section where you found the kernel version. The 4.0.4 also works with 4.0.3 so it's ok.
2. No the new rom will install a new kernel. Philz won't work with cm as philz is Samsung kernels repacked for safety and recovery..
Thanks, man.
Just to clarify: once I'm done flashing CM 10.1 from the philz kernel, I will no longer be running the philz kernel, but the CM kernel? Is there a reason why I can't go directly to flashing CM 10.1 from the stock rom and recovery, skipping the Philz kernel part (if I refrain from wiping in the stock recovery, when the faulty stock ICS is still on there)?
loxdp said:
Thanks, man.
Just to clarify: once I'm done flashing CM 10.1 from the philz kernel, I will no longer be running the philz kernel, but the CM kernel? Is there a reason why I can't go directly to flashing CM 10.1 from the stock rom and recovery, skipping the Philz kernel part (if I refrain from wiping in the stock recovery, when the faulty stock ICS is still on there)?
Click to expand...
Click to collapse
Correct me if I'm wrong but I don't think you can flash CM 10.1 from stock recovery.
Philz kernel comes with CWM recovery which provides more functionality than the stock recovery.
For example you can do a nandroid backup (basically a snapshot of your current phone system) so if you ever flash a rom that you don't like or something screws up, you can just restore your backup.
I think your first priority should just be flashing a safe kernel (Philz) and only then should you be looking into flashing custom roms.
loxdp said:
Thanks, man.
Just to clarify: once I'm done flashing CM 10.1 from the philz kernel, I will no longer be running the philz kernel, but the CM kernel? Is there a reason why I can't go directly to flashing CM 10.1 from the stock rom and recovery, skipping the Philz kernel part (if I refrain from wiping in the stock recovery, when the faulty stock ICS is still on there)?
Click to expand...
Click to collapse
Custom rom can only be installed using Cwm
OK, thanks for your help guys. I just flashed the Philz kernel following to the instructions and all is well. CWM is working, and I appear to have root access in my old stock ROM.
But in the phone info, the kernel version is unchanged. It stil says: "3.0.15-N7000xxlpy-cl474507 [email protected] # 3 SMP PREEMT Fri May 4 04" -- which is the exac same thing it said before I flashed the kernel.
How can I verify if I'm actually running the safe Philz kernel now?
PhilZ Kernel are only modded kernel, so they aren't change and stock kernels. And so you won't see a description made by PhilZ but only the normal information of the original kernel.
To be sure: boot into recovery and check the CWM version and compare it with the infos in PhilZ thread.
But you told already that you do not have the stock recovery, so everything is ok.
Thanks ThaiDai. The fact that I had moved successfully from stock recovery to CWM was already a strong hint that things worked out.
I wanted to make extra sure, so before flashing the first custom ROM I went into CWM, made a backup of the stock samsung, and then took this script right here to examine the operating kernel (boot.img in the backup folder) for the brick bug: http://forum.xda-developers.com/showthread.php?t=1807995 -- the script returned that the kernel was safe.
So I went on to flash CM 10.1 and I'm a happy camper now! This forum is a great place for getting help, you guys are terrific!
I decided to flash CM10 stable build on my AT&T captivate.....i am rooted and install rom manager and flashed CWM recovery thru ROM MANAGER and when i boot in recovery there is no option for installing zips from SD card....HELP ME PLEASE!!
PLEASE GIVE ME ANOTHER RECOVERY....:crying:
LaKsHaY1997 said:
I decided to flash CM10 stable build on my AT&T captivate.....i am rooted and install rom manager and flashed CWM recovery thru ROM MANAGER and when i boot in recovery there is no option for installing zips from SD card....HELP ME PLEASE!!
PLEASE GIVE ME ANOTHER RECOVERY....:crying:
Click to expand...
Click to collapse
you are still running stock recovery.
ROM Manager doesn't work on Captivate phone at all. You need to read stickies in the captivate forums, then use Odin or Helmdall app on your pc to flash via usb.
your first step should be to uninstall rom manager.
then read about rooting and flashing roms in the stickies in the Captivate fotums. I recommend you do this instead of someone giving you a link to single thread.
if you will flash a stock Gingerbread kk4 rom after rooting your phone, then flash the Corn 7.06 kernel, you will have the recovery menu that allows you to flash Jelly Bean roms.
reading the stickies will help you understand what you are doing, reduce the chance that you have any problems, and help you understand how to recover if you do have any problems.
my first ever flash failed and because I had read the threads, it only took a couple of minutes to recover. reading the threads before is good.
Sent from my SGH-I897 running JB CM10.1 Nightly April 8, 2013.