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.
Related
Hello, I have an original ADP1, updated to the latest official HTC images
I have:
radio: ota-radio-2_22_19_26I.zip*
recovery: signed-dream_devphone_userdebug-ota-148830.zip*
I want to be able to install other ROMs, like the ones offered in "Android Development".
There are a lot of guides out there on how to do that, my problem is that I want to do a nandroid backup first, before doing any flashing.
For doing a nandroid backup, I understand that I either
1) need to flash a special recovery image so I don't need a PC to restore the backup,
OR
2) Have busybox installed, and run nandroid.sh from recovery mode.
Correct so far?
I wanted to go with option 2), since I can perform a backup before flashing anything on my device. The only problem is that I don't have busybox installed.
I have seen a busybox build (over here http://benno.id.au/blog/2007/11/14/android-busybox ) which is 1.8MB because it is presumably compiled against libC, and have read here that jesusFreke was building one with bionic.
Is the bionic version anywhere to download? I suspect its in newer roms, but I *do not* want to flash a rom just to have busybox, since i only want busybox so I can perform nandroid updates before doing any flashing.
I understand that after having busybox, I just push it into /usr/xbin, --install, and nandroid will just work?
Anyone got a download to the latest, most stable and complete busybox? I would prefer one compiled for android (linked against bionic, etc..)
(what busybox version do you guys use?)
Thanks for your help and sorry for the LONG POST!
Superken7 said:
Correct so far?
I wanted to go with option 2), since I can perform a backup before flashing anything on my device. The only problem is that I don't have busybox installed.
Click to expand...
Click to collapse
I can't address most of your post, but there's a flaw in your reasoning that might make it a moot point.
Nandroid won't backup the recovery image - only the primary OS and data. So making a backup using Nandroid on your stock device won't be any different than installing a modified recovery, then backing up your device.
Really, installing the recovery is a trivial activity with little* risk of damaging your phone.
*No guarantees in life, but I wouldn't worry one bit about it.
Thanks for the quick answer!
I guess i'll look for a recovery image that fits my needs then
Let me suggest Cyanogen's Recovery 1.3.1 - As far as I know, the only one with both Nandroid backup and restore. Also has USB mount, really handy for loading updates if your device is fubared and you don't have a card reader.
http://forum.xda-developers.com/showthread.php?t=523558
Grr, double post.
Yay thanks!
I guess there are no compatibility problems between recoverys? I mean, just like you need a certain radio version in order to update the SPL, are there any compatibility requirements for that recovery? I don't see any of that in that post, but just in case.. =D
thanks again!! =D
DOUBLE KILL! erm... double post!
I'm not the only one cursed with the double posting, huh?
No, no issues with using any combination of recovery with certain ROMs, SPL, radio, etc.
You're welcome, and good luck.
X10 ?Mini Pro
Works like a charm
when you install titanium backup from the market it will download an actual busybox after first start. maybe you can try this one?
you can use Titanium Backup to update it
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.
Hi guys,
The power button on my nexus one died, and I tried to get the phone replaced by htc singapore.. but all efforts were futile. So they replaced the "Rigid FLex" jacket for free and gave me back the phone..
I dont really have any complaints, other than the power button still feels flimsy and I dont trust it, since it causes a lot of inconvenience.
NOW, can I use the volume key or trackball to wake the phone up ?
Would any of these buttons Die like the power button (are they equally flimsy ? )
Ive been reading on custom-roms which will add trackball-wake-up option..
-Could you point me to the most stable rom? (Im running froyo frf91)
-If rooting is required, could you point me to a newbies guide to rooting..
Thank you
abstrucity said:
Hi guys,
The power button on my nexus one died, and I tried to get the phone replaced by htc singapore.. but all efforts were futile. So they replaced the "Rigid FLex" jacket for free and gave me back the phone..
I dont really have any complaints, other than the power button still feels flimsy and I dont trust it, since it causes a lot of inconvenience.
NOW, can I use the volume key or trackball to wake the phone up ?
Would any of these buttons Die like the power button (are they equally flimsy ? )
Ive been reading on custom-roms which will add trackball-wake-up option..
-Could you point me to the most stable rom? (Im running froyo frf91)
-If rooting is required, could you point me to a newbies guide to rooting..
Thank you
Click to expand...
Click to collapse
cyanogen rom can do trackball wake up...trackball unlock...and pressing menu will lock your phone..
i suggest you to download rom manager from market...
and dont forget to learn about how to unlock and rooting your phone..
or you also can root your phone without unlock your phone...
use search function..you can find a lot resource to root your phone
http://forum.xda-developers.com/forumdisplay.php?f=559
http://forum.xda-developers.com/wiki/index.php?title=Nexus_One
harunjo said:
cyanogen rom can do trackball wake up...trackball unlock...and pressing menu will lock your phone..
i suggest you to download rom manager from market...
and dont forget to learn about how to unlock and rooting your phone..
or you also can root your phone without unlock your phone...
use search function..you can find a lot resource to root your phone
http://forum.xda-developers.com/forumdisplay.php?f=559
http://forum.xda-developers.com/wiki/index.php?title=Nexus_One
Click to expand...
Click to collapse
Thanx..
I did use the search button, but it gave me tonns of threads, with a 100 pages in each..
So I had to start this thread.
My phone is unlocked.. (sim-free)..
There is no SIM-locked Nexus in existence, as mentioned multiple times. "Unlocked" stands for "Unlocked bootloader", doesn't have anything to do with SIM. Yours is locked, since you just got it and never unlocked it.
I suggest you read the Wiki instead of continuing this thread, read all the guides, use 1-click root application and DO NOT use ROM Manager. Learn to install the custom recovery yourself, and to install ROMs using the recovery. Everything is written in the Wiki.
The most stable yet heavily customized Froyo ROM would probably be Enomther's, which I personally use.
Jack_R1 said:
There is no SIM-locked Nexus in existence, as mentioned multiple times. "Unlocked" stands for "Unlocked bootloader", doesn't have anything to do with SIM. Yours is locked, since you just got it and never unlocked it.
I suggest you read the Wiki instead of continuing this thread, read all the guides, use 1-click root application and DO NOT use ROM Manager. Learn to install the custom recovery yourself, and to install ROMs using the recovery. Everything is written in the Wiki.
The most stable yet heavily customized Froyo ROM would probably be Enomther's, which I personally use.
Click to expand...
Click to collapse
Thanks for the clarification.
Hi, i was reading and stumbled on Softroot.
I cannot find more info on it..
Its apparently, temporary rooting.. like jailbreaking..
Can I do a softroot to achieve the track-ball wakeup ?
Use Universal Androot.
There is no "temporary rooting", and rooting isn't equal to jailbreaking, it's a different thing, done for different purposes. Rooting is permanent, otherwise it's worthless. Having 1 session of root access (until reboot) doesn't accomplish anything, unless all you want to do is delete some system application or something of the sort.
@jack_R1
Hi, I used the 1Click Androot app to Root my device. Im backing up apps and settings using titanium backup.
My next step is to flash the custom rom.
Im deciding between Enomthers 2.11.3 NOT Pre_Themed ROM, and Nightly's CM6 for Nexus one..
So to clarify things, I need to
1 rename the Custom rom to Update.zip and paste it to the Root of SD card.
2 Rename the Amon recovery image to recomevry.img and paste to root of SD.
3 Turn on the phone while holding Volume Down
4 Select "BOOTLOADER" from the menu
5 Select "RECOVERY" from the menu
6 Select "Flash update.zip" or "Flash ZIP file"
7 Turn off verification, if such option is presented
8 Select your downloaded ROM image
9 Wait for the flash to finish successfully, if it didn't - do not continue!
10 Return to main recovery menu
11 Select "Wipe"
12 Select "Wipe data / factory reset"
13 Select "Wipe Dalvik cache"
14 Return to main recovery menu
--> Reboot the phone
?
Is there anything missing? please lemme know. I wanna do this asap.
Also, Im already updated to Froyo Radio (v4.06...) so I do no figit with radio .. correct?
-Also, when do I configure SpareParts? (before or after flashing) ?
-What is the difference between pre-themed black text and pre-themed white text? (black notification bar with white text on top)?
Thanks!
You got some things confused.
1. No need to rename it. Using custom recovery lets you flash anything with any name.
2. Since you rooted using 1-click root, you don't have a recovery yet. You need to flash it before you reboot to it. Read and execute: Nexus One Wiki / Recovery Images / Amon_Ra's Recovery / using flash_image method. Link for your convenience. You could also go to Developer section and download the latest 1.8.0.1 Amon_Ra's recovery instead of 1.7.0.1 in the Wiki. I'll update the Wiki to give a choice between the two.
3. Continue your list till the end.
Nothing needed for the radio, if you're already on 4.06.
Spare Parts will appear only after flashing the ROM.
Pre-Themed black text is regular, white text is for black notification bar - just as you wrote.
Personally, I run Enomther's since Froyo is out. Before that I was using CM. You might try them both and see which you like more.
Well, thanks for the reply.. Ill look into it after the ADB hurdle.
Presently, Im stuck at the ADB step..
I got the android sdk package, got nexus one drivers.. but for whatever reason, it wont show my device in cmd prompt..
I have pretty much memorised the adb for beginers guide.. but no luck..
(Im on Win Xp)
This is turning out to be a pain in the rear end..
You don't need ADB to flash recovery.
Follow the guide I've pointed you to.
Return to ADB once you're already on the custom ROM, it won't run away.
Flashing the recovery image was quite a task!
Luckily I googled and stumbled on a thread where YOU mentioned to download and install BusyBox.
So yes, Ive flashed it finally..
Im downloading the Enomthers ROM now.. slow net connection.. will load it in a while if it allows.
Thanx a bunch!
hi..
Done installing custom rom.. it was pretty staright forward once recovery img was flashed.
I would like to add some info, for someone who stumbles on this.
In recovery options,
For backup/Restore.. when you select Nand+Ext, and end up getting 'Error...Run nandroid-mobile.sh', press back to goto the main menu, toggle USB MS (mass storage) on, plug it to the computer, delete the nandroid folder, and try again.
If you still get the error, delete nandroid folder, and this time select 'Nand backup only'. if succesful, proceed to copy the nandroid folder to your computer.
So far Ive installed themed enothmer rom.. and its decent.
Will customize it tomo..
For the time-being, ive noticed one issue/bug .. the LED light blink interval is too quick even on selecting 'Slow'.
Thanx Jack!
You're welcome.
Thanks for reminding about the need for busybox to execute chmod and such. Added to Wiki instructions.
Hi,
Now that Ive successfully flashed a custom rom, and its working fine..
I noticed an update to enomthers rom. (v2.12.2)
I want to flash this rom, so do I have to re-flash recovery? and then flash this new rom?
Or just flash the new rom? but then do I wipe/factory reset and wipe Dalvik cache of the device?
Actually restoring the data (especially mesages and apps) is quite an issue, it takes a while (considering im on EDGE)..
also, is it recommended to make an apps2sd partition on SD card? I did get low memory warning on internal memory.
and last, I just want the black status bar and 'some' custom icons (not all), so is there a way to install these on otherwise stock looking enomther rom?
I know they are some noobish questions but I need answers..
Thanx
You don't touch the recovery once it's flashed, as long as it's working. You just flash the ROM using the recovery that you already installed. And don't do any wipes - so you won't have to restore the data.
Apps2EXT (EXT2 partition for apps on SD card) is great and highly recommended.
You can apply themes, simple as complex, using morphs.
Hi Guys,
Need your opinions again.
I was extremely satisfied with Enomthers 2.14.4 rom, till the update notifiation appeared.
Ive waited long enough for an update from Enom, but he has his reasons, and I dont see an update in the pipeline.
So I need to get a new rom & it should have have trackball wake up/vol keys wakeup (cant afford to break the power key).
Also Gingerbread, and Apps2SD (+).
Now Ive come across two roms,
a) Nightly's CM rom
b) GRI40, system dump + unmodified stock n rooted rom.
So which one should I get?
Also whats the difference between nightlys CM rom and CM rom ?
Also, I see I need to update the radio, so this has to be done before flashing rom or after?
I have flashed AMON RA's recovery 2.0, do I need to flash anything else?
Remove the update notification and return to being happy.
Sent from my Nexus One using XDA App
Stock GRI40 doesn't have any mod for trackball/volume wake. So for now you're out of options - you have to use a custom compiled AOSP Gingerbread, which point you towards CM7/SuperGinger/Leo's Ginger/etc. Currently none of those are as stable as Enom's (I've tried 2 of them).
I can also suggest flashing FOTAKill (use Google to find, learn and download) and keeping with Enom's. That's what I'm doing now. And after a brief experience with MyTouch 4G, I'm seriously considering flashing Froyo Desire port.
Thanks for the prompt replies. Really appreciate it.
For now I can live with enomthers rom. Its not giving any issues. Its got everything I need, other than gingerbread.
the Gingerbread update is glued to the taskbar, and doesnt pop-up at all (doesnt intervene/hinder ) in regular operations.
So ill patiently wait as well
thanks again guys!
I hope mods can make this sticky.
Do not use ClockworkMod Recovery 3.0.0.5 to create partitions for SD-EXT. There is a bug with clockworkmod recovery that create faulty partition resulting in data corruption. This prevent a2sd+ from working properly, any attempts to fix a2sd without recreating SD-EXT can corrupt apps and market data.
So please use RA Recovery v2.2.1 for partitioning SD until this bug is plugged.
Yeah, it's old news though.
If you must use CWM use an older version or one of the few modified version floating around.
Just so you know it's not just for partitioning clockwork mod 3.X is unstable in allot of ways some people get away with using it but that's usually the people who flash stuff like max once a month or that just install cm then stop even booting into recovery so I suggest everyone to go either to Amon RA or clockwork mod 2.5.1.4 (which is the latest 2.X clockwork mod recovery).
baseballfanz said:
Yeah, it's old news though.
If you must use CWM use an older version or one of the few modified version floating around.
Click to expand...
Click to collapse
Unfortunately, this news is not visible to people who are new to using CWM. I think making this sticky will be helpful to new users. I had to do several forum hunts the whole day yesterday just to figure out what was breaking A2SD+ on MIUI.
jazzaddict said:
Unfortunately, this news is not visible to people who are new to using CWM. I think making this sticky will be helpful to new users. I had to do several forum hunts the whole day yesterday just to figure out what was breaking A2SD+ on MIUI.
Click to expand...
Click to collapse
I have to say it's true that this is common knowledge to people who spend some time on forums but to noobs and people who are just following a tutorial it's true that this knowledge is not very visible so I think this should either be stickyed or put into the nexus one wiki. Just my 2¢
Disclaimer: You may brick your phone. NOT for AT&T
Reminder: Make sure your phone has enough battery charge to flash this, it's larger than normal.Hi,
Here is a huge CWM zip that restores your Bell phone to stock 2.2.2. I have tested it on my phone several times and it worked perfectly, there is still the chance that something may go wrong, but I am feeling confident in it.
What this does is similar to my app or scripts, it puts my backup of Bell's 2.2.2 partitions on your phone, but instead of using dd, it uses tenfar's CWM and flash_image. Some partitions are HUGE, and take a while, your phone is not locked up.
This has been updated to include the Bell bootloader for 2.2.2 and the radio for 2.2.2.
EDIT: This has been updated again to ram fix the boot and recovery partitions if there is a ram problem.
It writes to partitions 1, 2, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 17. 3 is left out because it's your pds partition, and data and cache have no relevant content. You must factory reset after using this to clear those. So, that's your boot, recovery, system, webtop, cdrom, preinstall, and several other partitions. This is to get back to stock Bell 2.2.2, it's not just a boot/system replacement, if that is a fruitcake, this is a gobstopper.
Please note: This restores your Bell phone to stock condition, that means you won't be unlocked, CWM will be overwritten with the stock recovery. It will be just like you bought it. If you want to keep flashing things in CWM with the unlocked bootloader, then immediately after flashing the stock zip, flash the unlock and fix zip. If you don't then you will have to reflash an unlocked bootloader, and reflash CWM recovery, which is time consuming any annoying, it doesn't mean you will be permanently locked again. I had to spell that out to the folks that don't really understand this stuff. At all.
If you want root after installing this, just install Superuser.apk from the market.
Bell_FR_2.2.2.zip (Froyo not France)
(md5 e431b4cc3ba7e3a27b6aad6982a31066)
Cheers!Oh, I forgot to mention, this is not quite stock, there are su and sudo binaries in /system/bin. Just install Superuser.apk to be rooted. they haven't been a problem for doing an OTA yet, but they are easy enough to remove if it comes up.
unlocked-fixed-Bell-2.2.2.zip
Mirror: unlocked-fixed-Bell-2.2.2.zip
Damn, nice work as always, man! This should come in handy for lots of us Bell Atrix users that feel left out. Lots will appreciate this!
When you say without amnesia are you talking about the bootstrap or are you talking about a user who is using the bell_ihop and then installs cwm and then reboots and looses recovery?
So a 2.3.4 bootloader and radio will work find booting a 2.2.2 bell ?
Will you eventually be able to compile a zip for Bell gingerbread?
IrshaadH said:
Will you eventually be able to compile a zip for Bell gingerbread?
Click to expand...
Click to collapse
the problem would be hosting it, not sure how he would be able to do that.
akurit said:
When you say without amnesia are you talking about the bootstrap or are you talking about a user who is using the bell_ihop and then installs cwm and then reboots and looses recovery?
So a 2.3.4 bootloader and radio will work find booting a 2.2.2 bell ?
Click to expand...
Click to collapse
keeping in mind that this is only for the recovery with unlocked devices, what he means is that the CWM recovery that tenfar put out has a problem with int'l phones (pretty sure it's all int'l) where IN recovery (not just the normal ROM, like the problem we had before) only 300 and some mb of RAM is available. since this zip is over 300mb, it can't all load into your RAM properly with normal recovery.
NFH found this bug, and patched recovery for us so as to fix the RAM problem. the two files attached are fixed recoveries for the two separate MBR versions of int'l devices.
to find what version you should use, connect to phone via ADB and then
Code:
adb shell
su
cat /proc/cmdline
and then search for the part of the output where it says "tegrapart=mbr:" and read that. it should have either "1100" or "d00" somewhere in it, use the CWM zip attached that has your respective output.
hope that clears up your question, if you have any further ask them in here.
IrshaadH said:
Will you eventually be able to compile a zip for Bell gingerbread?
Click to expand...
Click to collapse
Hi,
I believe y2whisper may be working on something like that. The point of getting back to stock 2.2.2 is to be able to apply the final OTA for Bell GB. Certainly something similar can be done for any firmware you want to flash.
Cheers!
i flashed the d00 and I do maintain unlock however no cwm just stock recovery with no menus.
tried it again and it work
but seems like i have to fastboot flash it each time i want to use recovery
akurit said:
i flashed the d00 and I do maintain unlock however no cwm just stock recovery with no menus.
tried it again and it work
but seems like i have to fastboot flash it each time i want to use recovery
Click to expand...
Click to collapse
I know what you are talking about, but I got that with a stock bootloader.
If you are going to be using CWM recovery with this 2.2.2, then flash the boot file for d00 as well, it gives you the ram fix and for some reason it doesn't cause that issue.
Cheers!
Here is an international CWM recovery, it detects the 1100 vs d00 tegraparts and installs the right recovery for it.
CWM_INT_Recovery.zip
(Just use it with whatever CWM recovery you are using now, it will update it with the ram fixed one.)
NFHimself said:
I know what you are talking about, but I got that with a stock bootloader.
If you are going to be using CWM recovery with this 2.2.2, then flash the boot file for d00 as well, it gives you the ram fix and for some reason it doesn't cause that issue.
Cheers!
Here is an international CWM recovery, it detects the 1100 vs d00 tegraparts and installs the right recovery for it.
CWM_INT_Recovery.zip
(Just use it with whatever CWM recovery you are using now, it will update it with the ram fixed one.)
Click to expand...
Click to collapse
ohhh, that's a nicely scripted installer you got there. i think that would be quite handy for int'l users trying to flash custom kernels, is it possible to apply that script to select the correct boot.img out of two for the right tegrapart? if that's possible i think you should hit faux/edgan up with that script and let them apply it to their int'l kernels so users can just use on CWM to install it.
raybond25 said:
ohhh, that's a nicely scripted installer you got there. i think that would be quite handy for int'l users trying to flash custom kernels, is it possible to apply that script to select the correct boot.img out of two for the right tegrapart? if that's possible i think you should hit faux/edgan up with that script and let them apply it to their int'l kernels so users can just use on CWM to install it.
Click to expand...
Click to collapse
Hi,
Sure, it's just replacing the word recovery with boot and having the right boot images in the file.
Cheers!
yes its zipping now. off to bed but tomorrow I will back up my stuff and attempt to flash to see if it works.
@akurit
I forget off the top of my head but there is a file that you just have to delete to prevent that. the file just flashes the old recovery on every reboot. get rid of that and you will be fine.
Awesome work! This makes it much easier to get back to 2.2.2
Its installing now!
now at some point the install stopped and I think I saw it say status 0 and then recovery rebooted. so I am not sure what happened there.
ive rebooted with no problems. and its uploading now. if someone is willing to test this out (a bit difficult for me since I am already on 2.3.4) let me know. and will send you the link. would like to see a proper install before i share it with the masses.
This is why hehee
tenfar said:
......
Please Remove install_recovery.sh located in your /system/etc/ ,so that the recovery will not be overwrite to stock one.........
Click to expand...
Click to collapse
now it remains unlocked and I have recovery even if i reboot... but the ram issue still exists
y2whisper said:
Its installing now!
now at some point the install stopped and I think I saw it say status 0 and then recovery rebooted. so I am not sure what happened there.
ive rebooted with no problems. and its uploading now. if someone is willing to test this out (a bit difficult for me since I am already on 2.3.4) let me know. and will send you the link. would like to see a proper install before i share it with the masses.
Click to expand...
Click to collapse
i could test it for you, i should be able to tell if it works alright or not, since i'm starting from an AT&T build of 2.3.4. would i have to head back to stock Bell using Gobstopper before i use your package too? i got a whole buncha time on my hands this week, so i should be able to test it however you want.
anyone try flashing the bootloader and radio?
kevnb said:
anyone try flashing the bootloader and radio?
Click to expand...
Click to collapse
Hi,
I have tested it, no problems, but went back to IHOP and the ram-fixed bootloader for 2.2.2 in the OP so recovery will work.
Also, the file install_recovery.sh located in your /system/etc/ doesn't exist in the Gobstopper, so that isn't causing recovery to be generated by patching boot.
Cheers!
So its when flashing the webtop that the install stops with the error code. when i boot up all is ok but a reboot later and recovery is gone (as in you select it and it just boots into android). reflashing cwm recovery fixes that.
I have tried swapping the webtop files to no avail. going to keep trying. any ideas are welcome
y2whisper said:
So its when flashing the webtop that the install stops with the error code. when i boot up all is ok but a reboot later and recovery is gone (as in you select it and it just boots into android). reflashing cwm recovery fixes that.
I have tried swapping the webtop files to no avail. going to keep trying. any ideas are welcome
Click to expand...
Click to collapse
Hi,
What recovery are you using, if it's not ram fixed you are going to run into situations where you don't have enough space to flash it.
Cheers!
ahhhh.
you know i was wondering if that was it. I even repackaged the recovery thinking it would be the cause.
I don't believe I was ram fixed at the time of the backup. So I am thinking either, have custom recovery flashed in that spot, or change the order to where recovery gets flashed after.