I'm using CM 5.0.5.3 with apps2sd working great and I'm on AR 1.6.2.
What would be the benefit of flashing over that with 1.7? Would I screw anything up?
I assume I use the CM version rather than the "Normal" version but what if I want to try out enomther (my battery life sucks on 5.0.5.3)?
Thanks for the help!
no real reason.. i`m using Rom Manager.. makes things ALOT easier.. try it.. it's on the market
Flashing to an updated Recovery will not mess with the ROM... neither will flashing an updated Radio. The benefit is just that you'll have whatever extra functionality Amon_RA has built into the new version.
qiuness said:
no real reason.. i`m using Rom Manager.. makes things ALOT easier.. try it.. it's on the market
Click to expand...
Click to collapse
Same here...I can do all the same things it just makes it simpler...not to mention I'm lazy
to get support for the ap2d feature in CM 5.0.3
if you tried to wipe your partition it won't work. Also, if you tired to re flash your rom, that part becomes inaccessible and the a2sd feature will be grayed out
Well, I installed ROM Manager and now have the ClockworkMod Recovery installed. It gives me the option to download other non-Cyanogen Roms. I was under the impression that meant I had to wipe everything, Backup with nandroid and Titanium and Install everything fresh. Will the world explode if I install another different ROM from within ROM Manager or will it just not work properly (lots of FC)?
whodatfever said:
Well, I installed ROM Manager and now have the ClockworkMod Recovery installed. It gives me the option to download other non-Cyanogen Roms. I was under the impression that meant I had to wipe everything, Backup with nandroid and Titanium and Install everything fresh. Will the world explode if I install another different ROM from within ROM Manager or will it just not work properly (lots of FC)?
Click to expand...
Click to collapse
a boot loop is the most likely occurrence.
You don't need the "cyan" version either. "Normal" is the same code wise...... I was under same false impression when it was first released.
Clockwork seems lovely but I have had few problems with it. One nand got all screwed up this week that broke my confidence. Amon_RA until Clockwork can be ironed out is what I would suggest (personal preference for all).
tried g-script
i tried the g-script per some other post off another android site and it was a no go. anytips, I do like the rom manager recovery mode although i do need to update my bootloader and my recovery rom.
djsmeadly said:
i tried the g-script per some other post off another android site and it was a no go. anytips, I do like the rom manager recovery mode although i do need to update my bootloader and my recovery rom.
Click to expand...
Click to collapse
Congratulations for digging up a dead thread and bringing it back to life.
Amon RA is at 2.x now.
I'm having issues with downloading a rom. I used the free version and installed the Shadowrom but it wouldn't reboot in it. I bought the premimum version and now when I go to download rom it gives me a list but I get a pop up message of "error occurred while processing the rom list" I don't know what this means, can someone help?
You should contact the dev over this issue. Also it is in a sticky thread that clockwork recovery could possibly brick your device. Just a heads up!
Clockwork no longer replaces AMON_RA .... it actually uses amon to boot into clockwork .... so although everyone wants to bad mouth Clockwork are there any confirmed cases of brick since they fixed the Eris problem ? I can say I have used it a few times on my wifes phone cuz she has trackball issues and Verizon refuses to replace her phone ... and I know for a fact that Amon_RA is still the recovery on her phone unless I boot into Clockwork from the update.zip or from Rom Manager (on her phone i can't use the update zip, trackball problems)
ok, thanks for the heads up. I probably won't even bother then. Is this issue for the app itself or just certain Roms. I definitely don't want to brick my Eris. My friends Droid was bricked a month ago I just unbricked now. I don't want that headache.
Wiping and backup problems have been fixed in CWM3 > 3.0.0.5. If you had trouble before, try again with ROM Manager. Try to flash the recovery at least twice before giving up, or use an alternate method below.
Ensure that "wipe recovery" option in ROM Manager settings is checked. There is no good reason to not have this checked. It should probably be the default. This will not affect your backups.
3.0.0.8 has fixed the SLCD problems. If you get the black screen with white bars, upgrade to 3.0.0.8.
Koush's official answer as to why you can't flash old .zip files with 3x.
Why you should upgrade to CWM 3 series from 2 series
CWM2 IS NO LONGER SUPPORTED AND MAY BREAK AT ANY TIME
ROM Manager won't work with 2 series anymore
support for journaling filesystems. Your data is safer.
pretty orange color
power down from recovery
better partitioning support
may be required for Cyanogenmod in the future. It is not required for the inc as of now.
Why you should not upgrade to CWM3 series
Fear of messing with recovery is not a good excuse
You want to install ROMs from ROM developers that use 2 year old technology and have refused to upgrade their zipping mechanisms (put pressure on them to change their installation scripts)
You like old ROMs that haven't been updated in ages
You are one of the few that the new recoveries don't work on. Ask and someone can probably help you get through this.
WHERE TO GET OLD VERSIONS OF CLOCKWORKMOD:
http://mirror1.kanged.net/recoveries/ - contains img files for all old versions
*http://dougpiston.com/?page_id=85 - contains PB31IMG for flashing through HBOOT, including 2.5.12 and 3.0.0.8. This is the easiest way to manually update recovery.
HOW TO INSTALL IMG FILES
***YOU SHOULD INSTALL THROUGH ROM MANGER IF AT ALL POSSIBLE. TRY TWICE IF IT DOESN'T WORK ON THE FIRST TRY***
Rename the image file you're interested in to recovery.img
OPTION1: ADB
Code:
C:\YOUR_ADB_DIR\>adb shell
$su
$/system/bin/flash_image recovery /sdcard/recovery.img
OPTION2: Android Terminal from phone
Copy the recovery.img to the root of your sd card.
Code:
$su
$/system/bin/flash_image recovery /sdcard/recovery.img
OPTION3: Use PB31IMG.zip
Download specific recoveries from dougpiston.com
If it is not available elsewhere, oll your own PB31IMG.zip
This is not as hard as you think. Download any recovery PB31IMG.zip, such as the one attached to this thread. Replace the recovery.img in the zip file with the one of the desired CWM recovery. Rename to PB31IMG.zip. Place in root of your SDCARD. Reboot into HBOOT. Install.
What to do if you have trouble with CWM3
Check partitions for errors
Try installing through ROM Manager, or installing through one of the alternate methods listed above
make sure wipe recovery is checked in ROM Manager settings.
make sure you have the latest version of ROM Manager. Check in the market.
How to manually wipe recovery partition.
The utility is present in CM7 builds. I cannot vouch for other ROMs. This can also be done easily through fastboot mechanisms, but afaik fastboot is not available for the incredible because there are not leaked engineering HBOOTs.
This should never need to be done except in extreme circumstances.
Code:
$su
$/system/bin/erase_image recovery
How to get into recovery manually w/out ROM Manager
Shut down your phone. Hold down volume down. Press power, keeping volume down held. This is HBOOT. Scroll down to recovery and push the power button again.
HTC Incredible Amend vs. Edify: How to get old ROMs working with CWMv3
Amend and Edify are scripting languages used to write the installation routines for .zip files, including ROMs. Amend is quite old, from the cupcake days, and as such does not have features necessary for modern ROMs. To simplify development, Koush removed amend support with the advent of CWMv3. He had announced that he was going to do this for months. Nonetheless, some older ROMs that are not actively developed anymore may be desirable, and many of these do not use the more modern edify scripting. There is a thread here on how to easily convert amend scripts to edify using amend2edify: http://forum.xda-developers.com/showthread.php?t=903598.
Other sources for help
IRC
#cyanogenmod or #koush - it is recommended you try the solutions noted in this thread first. Self initiative is important, but seek help if you need it.
Who are the people behind CWM:
koush is the primary developer, slayher and CUViper help adapt it to the incredible, I'm sure many others.
How to build Clockworkmod yourself:
http://www.koushikdutta.com/2010/10/porting-clockwork-recovery-to-new.html
EDIT 2/27/11: This thread used to contain info regarding a custom build of CWM3006. It is still attached to this thread, but koush has upgraded CWM to 3008 which contains the 3006 fixes and more.
Click to expand...
Click to collapse
Thank you I haven't really had any problems with 3.0.0.5, but I've seen a lot who have. Maybe this fixes some of the wiping bugs people were having?
BrettApple said:
Thank you I haven't really had any problems with 3.0.0.5, but I've seen a lot who have. Maybe this fixes some of the wiping bugs people were having?
Click to expand...
Click to collapse
It is really odd, as I can install this version and backup/restore fine, then switch back to 3.0.0.5 and backup locks up consistently.
Its true re: the wiping bugs. It seems there's a lot more noise about the 3 series CWM than the 2 series, although I wonder if its just a lot more people are installing it and not quite understanding how cwm/hboot/cm7 interact. Hard to tease it apart.
I'm talking to koush and trying to get him to recompile it and make it official, regardless.
I tried the above CWR and my recovery screen is all black with white boarder on each sides.
meazz1 said:
I tried the above CWR and my recovery screen is all black with white boarder on each sides.
Click to expand...
Click to collapse
Thats quite odd. Try reflashing a working recovery and then back to this one?
What ROM/Radio/Phone (inc slcd or amoled)?
You can also extract the recovery.img out of the zip file and flash it with adb or flash_image.
Let me know please, I'll pull it down if there's consistent problems.
dont pull it booted on my device and ROM.... i'll do some extensive testing and report back
Sounds like this is for AMOLED only
Side note, I looked at an SLCD Incredible today. Noticeable difference in screens. I will say that AMOLED is much brighter and produces better color than SLCD, but SLCD wins hands down in crispness.
ok
1. doesnt show proper version in rom manager
2. will not flash rom via rom manager... probably hook issue
3. works fine in recovery mode
imo if it dont work via rom manager its kind of a deal breaker for me... alot of my users want to use it as well as be able to flashover without having major issues
right now with 3.0.0.5 if you flash via rom manager without a full wipe... chances are... you'll end up wiping and reinstalling because of fc issues
Flashed fine here. In the process of making a back up.
I'm diggin the power-off feature.
I only use RM to DL roms, flashing within RM only breaks ****.
Backup sucessfully made.
lllboredlll said:
ok
1. doesnt show proper version in rom manager
2. will not flash rom via rom manager... probably hook issue
3. works fine in recovery mode
Click to expand...
Click to collapse
1) I believe if a recovery doesn't show up in the clockworkmod available recoveries, it will not show the proper ROM Manager version. Flash 2.5.0.5 and you'll see the same effect.
2) Looking into this now.
3) That's good to hear! Thank you for testing this! This, coincidentally, is primarily how I use CWM as RM has not been stable/consistent for me in ages.
lllboredlll said:
ok
imo if it dont work via rom manager its kind of a deal breaker for me... alot of my users want to use it as well as be able to flashover without having major issues
Click to expand...
Click to collapse
I hear what you're saying.
To get the hooks in place, install 3.0.0.5 first via ROM manager, then go into hboot and install this 3.0.0.6. ROM Manager still thinks you have 3005 and backup/etc. works.
I don't mean this to be production quality, but it should help bridge the gap until koush gets a new version out.
shoman24v said:
Flashed fine here. In the process of making a back up.
I'm diggin the power-off feature.
I only use RM to DL roms, flashing within RM only breaks ****.
Backup sucessfully made.
Click to expand...
Click to collapse
Thank you for testing this! I've updating the OP with notes from both you and bored. And made the disclaimer larger with more ***
No problem. RM still shows 3.0.0.5, but that's not a big deal. I still see the latest nightlies available from RM.
And, like I said, I never flash within RM.
Nor do I recommend that.
tdiman said:
EDIT 2/26/11: This information, as hoped, has been deprecated by the release of CWM 3.0.0.7. You should use that one, because CUViper and koush found more bugs re: the communication between ROM Manager and CWM, as well as the fixes noted below.
Click to expand...
Click to collapse
Just in case someone comes along late to the party, please note the above information added to the OP.
Is it true that v2.5.x.x nandroid backups will not restore under v3.0.x.x clockwork recovery?
Sent from my ADR6300 using XDA App
jdmba said:
Is it true that v2.5.x.x nandroid backups will not restore under v3.0.x.x clockwork recovery?
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
no. thats not correct - i have restored a bunch without issues.
I updated to 3.0.0.5 a few weeks ago when it came out. All seems to work fine for me except I can't restore to a previous version to flash other Roms (well at least from Rom Manager). Many of the other Roms that are out right now are not Edify.
Sorry if this is the wrong thread to post this in.
I've googled changing the Roms to edify myself, but I'm kind of lazy and switching recoveries seemed like it would be the easier route.
I think koush has been trying to gently encourage app developers for months to change over.
If you search this forum you'll find older versions of cwm.
The version number is reporting fine for me..... and i Love the new look of the recovery. I'm missing the fast scrolling from the previous builds, other then that I love it
Anyone notice 3007 disappeared from ROM manager for the DINC, I mean as the newest version that is. It is still in the experimental recoveries.
thelunchboxosu said:
Anyone notice 3007 disappeared from ROM manager for the DINC, I mean as the newest version that is. It is still in the experimental recoveries.
Click to expand...
Click to collapse
3008 is in there now also. Fast scrolling is back. I don't know if the glitch with some slcds is fixed.
i try to install themes to my phone and when install finished when it boots and patern screen appears it shows me a message like sorry we can't load fonts,clock,and other stuff and i don't have any way to see desktop...i must turn off the phone and turn on in the recovery mode and restore it...what its going wrong???
It would be more clear if you mention which firmware you are running, which theme you are trying to flash etc
agree with mjuksel. Most likely an incompatible theme.
sorry.. you have a point...ok so i'm not 100% sure of what i say but i give it a try..i use froyo 2.2.2 with kernel 2.6.32.9 and and the clockworkmod is 4.3.24...if you want you more info tell me..i tried to install the blue elegance theme from here...
CWM 4.3.24 ??? are you sure ??
and your ROM are
Stock ?
Modaco ?
Fear ?
other ?
yes i ckeck it again and its 4.3.24 and its modaco
ok , I don't know this version
try with another version
Hey he mean Rom Manager 4.3.24......
yes thats what i mean..tnx intelmaster...rom manager is 4.3.24...i tried again and no hope...it cant boot because maybe it wont have security copy files....i dont...if you want more ask me something else please tell me where to look...tnx a lot for your help...
you gotta find a theme which is based on the framework of the rom u are using ...
(a theme is nothing else than modified system apps ....)
Hey he mean Rom Manager 4.3.24......
Click to expand...
Click to collapse
OK , Rom Manager and CWM are differents , he say in second post : "...the clockworkmod is 4.3.24..."
Ive got a Touch version of CWM i need to put on a base one that isnt touch.. for a rom..
(wanting to put http://forum.xda-developers.com/showthread.php?t=1595639 on) or, this (http://forum.xda-developers.com/showthread.php?t=1383882 But this one doesnt give me service.. and im unsure of how to fix it,)
One of the versions for the thrill p920 requires a Non touch version of CWM and the version ive got is the touch so i need to somehow switch it from a touch version to the non touch version of cwm...
Baseband is either v21P or v21B.. not 100% sure.. pretty sure its 21P .. anyways, thanks for looking at my thread hopefully i can get this solved asap... (Hating gingerbread for the stupid application bug, (opens 1-12 apps on its own and constantly wastes my battery.. yet i still have awesome battery life.. lol)
Download the ROM manager app from clockwork mod. At the very top it will tell you your current version and the latest version. Regardless of what it says select it and choose your phone type when prompted. It will download and flash after that so be patient and let it work. After it reboots it will state if it has installed correctly or failed. After that you're good to go. Reboot into recovery to make sure everything worked properly.
Sent from my LG-P920 using xda app-developers app