yashsingh1/xdaforums huggingface dataset:
[Droid Incredible Android Development] ximfinity:
Bump, thanks TDIman, your suggestion got 3.0.0.8 working for me.
[Droid Incredible Android Development] tdiman:
FWIW, 3.0.0.8 is now the default.
[Droid Incredible Android Development] kzoodroid:
Can't find an answer to this anywhere. With 3.0.0.8 I cannot get into hboot or recovery by pressing volume- and power or volume+ and power. I get 3 or 4 vibrations then nothing but a blank screen and have to pull the battery. I can get into recovery using the power button menu or through ROM Mangager I just can't get into it if the phone is turned off. It works fine with 3.0.0.5 so its an issue with version 8. I have an slcd running CM7 RC2stock kernel.
[Droid Incredible Android Development] tdiman:
In the OP there are some suggestions to use to get 3.0.0.8 flashed correctly.

The primary one is that under ROM Manager settings, you need to make sure that "Erase Recovery" is set to TRUE. This alone will probably solve the issue, and if not let us know what's going on or check the OP.
[Droid Incredible Android Development] kzoodroid:
thank you that was it. i had read through the op, every post in this thread, searched this site, did a google search and couldn't find an answer. then when you said it was in the op i went back and saw it but i still had to read through it twice to find it. getting old i guess.
[Droid Incredible Android Development] kevinb84:
Problem:

I use Rom Manager and it SAYS i'm currently using 3008 but when i go to recovery its really 2.5xx

I use terminal and it says I don't have recovery.img when i know i do

My head is about to explode and any help would be GREATLY appreciated!
[Droid Incredible Android Development] nfiniti9:
Try flashing 3.0.0.5 in other recoveries then back to 3.0.0.8. It seems this fixes some problems.
[Droid Incredible Android Development] kevinb84:
Nothing, I just don't get it. I have to be doing something wrong. I have Hboot 92 is that relevant in any way?
[Droid Incredible Android Development] tdiman:
That is because the 2x recoveries are no longer supported by ROM manager. This does not mean anything for any practical purpose, and can be safely ignored. That said, it is wise to upgrade to 3.0.0.8 due to reasons outlined in the OP.

"slow your roll" and explain what says that :) With a little explanation of both what you are trying to do, and what you are doing when you receive the error, I bet we can help.
[Droid Incredible Android Development] kevinb84:
Roger that!

1. Downloaded the 3.0.0.6 file attached via the OP.

2. Rename the file to just PB31IMG.zip

3. Place on root of SD card

4. Reboot to hboot

5. This is where it is supposed to ask if I want to update correct? It doesn't

6. I still have 2xxx

Hope this helps
[Droid Incredible Android Development] nfiniti9:
Then just manually flash the newest recovery in hboot. Links in first post. Are you using the latest Rom manager?
[Droid Incredible Android Development] tdiman:
The best move is to update using ROM Manager. Make sure that "Erase REcovery" is checked under the options menu. 3.0.0.8 is the standard - 3.0.0.6 is in the OP for historical purposes.

If you need a PB31IMG of 3.0.0.8 go to http://dougpiston.com. The reason that the PB31IMG.zip doesn't work is either your SDCard isn't formatted FAT32, or that you accidentally renamed it PB31IMG.zip.zip, which sometimes occurs in Windows. But try ROM Manager first!
[Droid Incredible Android Development] kevinb84:
I've tried that, unless I'm doing something wrong which is absolutely possible being that I've always manually flashed roms in the past.

1. Open Rom manager

2. Click "Flash ClockworkMod Recovery" - It downloads?

3. Reboot into recovery where it still shows 2xxx
[Droid Incredible Android Development] tdiman:
Is "erase recovery" checked in the ROM Manager settings?

A message comes up that says "Flash Successful" if it worked.

Also, make sure you have the most recent version of ROM Manager.
[Droid Incredible Android Development] kevinb84:
Erase recovery is checked, I'm using 3.0.1.3 of rom manager, it says right now "Successfully flashed ClockworkMod recovery!", and it says current recovery is 3.0.0.8. But when I go into recovery it is 2.5.0.1
[Droid Incredible Android Development] tdiman:
A couple more things to try:

Try flashing Amon-RA from ROM Manager, reboot and make sure it worked, then try flashing 3.0.0.8. Sometimes it requires an alternate recovery to get the bugs out.

The other option, which will almost definitely work.

In the OP there's instructions on how to use the erease_image utility. Boot into your ROM (not recovery) then use erase_image to erase the recovery.

Next, using the directions in the OP, download the 3.0.0.8 img file, and use flash_image to flash the new recovery. It is a little time consuming and detailed, but the OP gives good instructions and it bypasses the other mechanisms with a low-level approach.

I have good confidence that once you get 3.0.0.8 flashed you'll be good as new, but unfortunately some people do have trouble getting it on there, especially it seems when upgrading from early 2 series :/
[Droid Incredible Android Development] kevinb84:
Man, really not having much luck.

I tried using rom manager to flash the alternate recovery. Once again rom manager states that I'm currently using it but sure enough when I reboot to recovery it's still 2xxx.

So I try to erase the recovery and receive this error:

mtd:erase failure at 0x004e0000

It lists an entire page of different numbers but the same erase failure message.

Recovery is still there :/
[Droid Incredible Android Development] hgoldner:
Tech support via proxy, and its limitations

I have all kinds of respect for Koush (especially in light of his recently standing up to Sony), but I am finding this "tech support via proxy" for ClockworkMod a little odd.

I have the 2.5.1.8 version modded by Chad0989 to support multi-touch kernels (like HeyIt'sLou's Kernels) on the Incredible.

My ROM developer is not (yet) using RM (fortunately so far), but has offered a dual path to flash (2.x or 3.x with edify scripts).

If I step up to 3.0.0.8 just to satisfy RM's requirements, am I going to lose multi-touch?
[Droid Incredible Android Development] tdiman:
I have no relationship at all with any of the CWM developers, including koush. You are free to contact him directly to get help if you'd like.

I personally don't see how this is any different than Pons and his CM7 thread (another open source project), Protekk and his nightlies, or any of the various radio, HBOOT or non-developer kernel threads on here.

Anyone is free to contribute to the questions asked here, and the thread contains a lot of answers and advice for common problems. Prior to this thread, information was scattered and difficult to find, if your answer existed at all.

The other aspect is that I'm at home a lot until mid-May, so while I have time to contribute I am, and I'm having fun learning a lot about CWM and linux-applied-to-phones in the process.

You will probably lose multitouch, but you can always try and downgrade if need be, if multitouch is more important to you than CWM3. In either case, if you give it a try, let us know the results.
[Droid Incredible Android Development] tdiman:
Hmm, one possibility is that your phone is S-ON, not S-OFF, in which case you need to re-root.

If that doesn't work, bite the bullet and RUU, which is a way to go back to the stock software that came on the phone and "undo" everything. Be careful, as you need to make sure the RUU you track down supports SLCD.

If that doesn't work, you have a hardware issue, unfortunately, and should either try to get by with what you have, or if your phone is under warranty get it replaced.
[Droid Incredible Android Development] kevinb84:
I'll give re-rooting a shot. Thanks!!
[Droid Incredible Android Development] hgoldner:
Point taken, and thanks for your helpful response. For those interested, I have located this thread in which Koush himself explains in greater detail the difference between CWM 2.5.x.x and 3.x.

Until I absolutely have to do so, or CWM 3.x receives an unqualified bill of health, I'm going to stick with 2.5.1.8. I do thank you again for your support here. I had no intention of diminishing your efforts and contributions to the user community.
[Droid Incredible Android Development] kevinb84:
Thanks tdiman, got it on there finally! I appreciate the help
[Droid Incredible Android Development] gonzlobo:
I'm going to thank you solely because you searched for something. Hopefully it's contagious.
[Droid Incredible Android Development] ACD168:
is anyone else having wiping problems with 3.0.0.8? I had to go back to 3.0.0.7
[Droid Incredible Android Development] tdiman:
What kind of wiping problems?

What's the scenario?
[Droid Incredible Android Development] ACD168:
I loaded skyraider 4.0, nandroided it, then wiped everything twice, dalvik everything, and waited 25 mins and warm Z wouldnt boot, installed 3.0.0.7, wiped twice for save measure and it booted?

I also tried 3 times on 3.0.0.8, just wouldnt work?
[Droid Incredible Android Development] dscribe:
Since 3.0.0.8 was primarily created for the SLCD phones that had problems with 3.0.0.7 and my AMOLED phone had a few quirks with 3.0.0.8, I decided to go back to 3.0.0.7. So far everything has been working smooth as butter. If you have an AMOLED phone, I would personally suggest you stick with 3.0.0.7 until (hopefully) something comes out that works more consistently with both the SLCD and AMOLED phones.
[Droid Incredible Android Development] tdiman:
The way to see what is going on would be to load some ROM, (e.g. skyraider) and then nandroid it.

Boot into CWM 3.0.0.8 and wipe everything just once.

Go into the advanced partitions and mount system, data and boot

Plug the phone into your computer. Navigate to /system, /data and /boot and see what is there.

This will let you know if CWM is doing what it is supposed to.

You can repeat the process with 3.0.0.7 if you like.

Let us know the results. It is this kind of (hopefully repeatable across multiple devices) bug investigation that can prompt a fix.
[Droid Incredible Android Development] jamor414:
I regret upgrading to the 3.x series. Now every time I need to flash a ROM or theme I have to temporarily flash a 2.x for it to work.

Is there any way to permanently go back to 2.x? Nothing uses 3.x..
[Droid Incredible Android Development] ACD168:
I think this is what's going on as I as well am AMOLED... is there anyway to make 3.0.0.7 fast like in 8?
[Droid Incredible Android Development] tdiman:
The OP contains suggestions on 1) fixing 3.x and 2) going back to 2.x

The consensus across the board is that 3.0.0.8 works.
[Droid Incredible Android Development] hgoldner:
The only place I've heard that "consensus" is here. Everywhere else I frequent, the recommendation is to wait until CWM is fixed, and stick with 2.5.x.x. YMMV.
[Droid Incredible Android Development] ACD168:
3.0.0.7 actually is very stable.
[Droid Incredible Android Development] dscribe:
...on AMOLED (non-SLCD) Incredibles
[Droid Incredible Android Development] tdiman:
OKOK, lets see what happens with wiping on my phone.

It is an early series AMOLED, ordered right after the phone started selling.

I run CM7.0.2.1, but that shouldn't matter.

I just booted into CWM3.0.0.8 and did a nandroid backup.

Step 1) Go to Mounts and Storage Menu

Step 2) Click Mount /system

Step 3) Click Mount /data

~ # ls system
ls system
app etc lib tts xbin
bin fonts lost+found usr
build.prop framework media vendor
~ # ls data
ls data
anr dalvik-cache local secure
app data lost+found system
app-private dontpanic misc tmp
backup drm property tombstones

Step 4) Unmount /system

Step 5) Unmount /data

Step 6) Go back to main menu, select wipe data/factory reset

*note* wiping data/factory reset does *NOT* wipe /system. The reason is obvious - if a factory reset wiped system it would leave you with an unbootable OS. It makes sense, but I just noticed this. You can format /system specifically by going in mounts & Storage, which deletes the rest of your ROM stuff not included in the factory reset.

Step 7) Go to mounts and storage menu, mount system, mount data again

~ # ls system
ls system
app etc lib tts xbin
bin fonts lost+found usr
build.prop framework media vendor
~ # ls data
ls data
lost+found

As noted above, all the /data is wiped, but /system (and also /boot) are not.

This is important if you're switching between Sense and AOSP. Perhaps a manual wipe of /system is what you want. This is not built into CWM by default, and it is debatable whether it should be. If previous versions do this, then so be it, it is a reasonable change imo.

If you want to completely wipe your phone and make it unbootable, then go to mounts and storage and format /boot and /system also. It is probably a good idea to do this when switching between all of these custom ROMs, especially because they contain bits and pieces from other devices/Sense versions/etc.

People (not necessary you) may not agree with the way the wiping is handled, but if there's a way for you to keep using the most updated version (and ultimately, you now have the choice of wiping /system or /boot or not (it may not be necessary in a reflash or when you flash a new nightly/RC). And I agree with having a CWM that makes it quite difficult to leave yourself an unbootable device by accidentally wiping everything. Most people don't read XDA or have a clue what's going on with partitions.
[Droid Incredible Android Development] tdiman:
I have noticed something also. When I install Cm7 from ROM Manager, it appears as though system is wiped by the install scripts. However, when I install Cm7 via CWM manually, system is not wiped. More food for thought.

Again, not right or wrong, just "is" and it is good to know how it works.
[Droid Incredible Android Development] dscribe:
Very good information. Thanks. I will go through the extra steps from now on to make sure I get a more complete wipe. It should not be a big deal f the phone is temporarily unbootable so long as one can still get into hboot and/or one is going to reflash a new rom before rebooting, right?
[Droid Incredible Android Development] burnmatoaka:
I've taken to manually wiping /system prior to any fresh install via recovery. It's solved some issues for me. Almost worth recommending as a best practice, except for the problem for those who attempt reboot. It screwed me a couple times before I realized had deleted /boot without replacing it. heh.

Also one more reason ROMmanager is a really great tool for automating the process. I do all my flashing through recovery now, but without RM I would have had to wait months for a compatible CWM before I could flash to my SLCD. I download most ROMs through RM too because it seems to have a pretty good mechanism for maintaining file integrity.

[I for one welcome our new Android overlords ::: DInc::SLDC::x.7.28::CWM3.0.0.8::CM7latest::Chad's latest]
[Droid Incredible Android Development] k_nivesout:
When switching roms I always wipe data/factory reset, wipe cache, wipe dalvik cache, format system, boot, data and cache. Might be a little overkill but I've never had any issues. Using 2.5.1.2 also, just seems to be more solid from what I've read.
[Droid Incredible Android Development] tdiman:
Yes, you are correct. Go ahead and wipe all of those partitions, but do not reboot until you flash whichever ROM you want. If you do reboot, you can still recover.

As long as you can get into HBOOT your phone is not bricked. The only things that can brick a phone, I believe, are 1) hardware failure, 2) flashing a bad radio or 3) flashing a bad HBOOT. Short of those three things there seems to always be a way to recover.

Worst case scenario, as long as you can get into HBOOT, you have these two corrective options: 1) Flash new recovery (if recovery is messed up) and 2) Flash an RUU PB31IMG.zip

Let us know if this helps with your flashing problems.
[Droid Incredible Android Development] tdiman:
In your case, I'd go straight to the partitions menu and format system, boot, data and cache. Although there were bugs with the 2.x series that have been fixed, so you may be correcting for those with your overkill method.

Dalvid-cache, btw, is stored on the data partition, so wiping data also wipes dalvik.
[Droid Incredible Android Development] ACD168:
I agree with you man.. All I can say it my results.. I never had a problem with 3.0.0.8 either and miss the speed.. but I loaed SkyRiader 4.0.. then tried to fresh installl Warm Z and it wouldn't boot.. I tried 3 times no dice, then I instl=alled 3.0.0.7 and the ROM finally booted up.. AMOLED.
[Droid Incredible Android Development] ACD168:
also after using 3.0.0.7 for a day it is MUCH faster at installing everything... nadroid backups, nandroid restore... installing files that have been updated using amend2edify which took forever on 3.0.0.8. I'm sticking with this.....
[Droid Incredible Android Development] tdiman:
My only goal here is to help people upgrade (especially from the 2.x series), dispel misinformation and help people make informed decisions.

I do think that 3.0.0.8 would work if you wiped the partitions in the mounts and storage menu, but nonetheless when there are other informed reasons that compel someone to use earlier versions then I'm all for it.

Edit: I should also point out that Amon Ra was just updated and may be another viable alternative for you, although I have not used it. Thread here.
[Droid Incredible Android Development] k_nivesout:
What are some fixes that have been made from 2.x to 3.x?
[Droid Incredible Android Development] hgoldner:
So, I decided to let myself be persuaded by all the 3.0.0.7 fanboys here to let ROM Manager update my recovery to 3.0.0.7.

Could not get out of HBoot unless I booted normally. Could not get into recovery at all. Ultimately, reflashed Chad0989's 2.5.1.8 and now we're back in business.

Meanwhile, ROM Manager still reports that I have 3.0.0.7 installed, and urges me to update to update to 3.0.0.8.

Seriously underwhelmed.

SUPERCEDED: See post #157 below.
[Droid Incredible Android Development] k_nivesout:
Definitely not encouraging me to update to the 3.x recoveries..
[Droid Incredible Android Development] dreamsafari:
I have exactly the same problem...
[Droid Incredible Android Development] tdiman:
3007 does not work with slcd devices, which is why 3008 was released.

3008 should work for everyone who gives it a chance. This is a good lesson as to why running old versions of CWM is at your own risk.
[Droid Incredible Android Development] hgoldner:
I have a first generation AMOLED Incredible (note from my signature), not an SLCD, so none of that applies to me.

The last thing in the world I would expect is for ROM Manager to get CWM wrong, but it obviously has. I'm toying with doing a straight download of the 3.0.0.7 CWM file and flashing that directly, instead of through ROM Manager (which I don't generally use, and don't trust the backups either, and especially not the wipe mechanism). I have a current Nandroid backup, so it's worth a whirl.

But, fact is, this stuff ought to be a tad more reliable, don't you think? It's just so uncharacteristic of the developer's high standards.
[Droid Incredible Android Development] tdiman:
That surprises me, as this is the first I've heard of that, but nonetheless....

If you'll search around you'll notice that some of the early 3x versions were extremely unreliable. I could not reliably back up with anything prior to 3.0.0.6. A number of people put in quite a bit of effort to iron out the problems, which has stabilized with 3.0.0.8 which is quite excellent.

3.0.0.7 only existed for a few days, it was quickly abandoned when both Koush and Slayher worked out bugs with it. They know it is buggy. They also know there's people (like ACD) might want to run old versions, and respect that, and give them the option to. That is the spirit of open source. It is also understood that running old versions is at your own risk.

If you choose to not run the latest version (currently 3.0.0.8), you alone accept responsibility for any bugs or problems you run into. Koush and slayher put in a lot of time/effort to iron out bugs, and are excellent developers.
[Droid Incredible Android Development] hgoldner:
Well, through direct download I was ultimately able to flash 3.0.0.7. I will roll with that for a little bit and then perhaps kick it up to 3.0.0.8 once I'm comfortable with it.

I'm guessing I *won't* be doing that via ROM Manager (because if it messes up but succeeds in wiping recovery, the rebuild process will just be too unpleasant to contemplate).

EDIT - OK, well, actually I *did* go ahead and get the 3.0.0.8 from Doug Piston's excellent site, and we seem to have 3.0.0.8 running now. However, ROM Manager still thinks I have 3.0.0.7. Go figure....
[Droid Incredible Android Development] tdiman:
dougpiston.com is great, and I do hope that 3.0.0.8 works well for you.

When you flash a recovery with ROM Manager, RM writes the version to a file called

/mnt/sdcard/clockworkmod/.settings

When you do not flash a recovery with RM, that file does not get updated and therefore it reports the wrong recovery version.

You can manually edit that file if you like.
[Droid Incredible Android Development] k_nivesout:
I've just stuck with 2.5.1.2 because it seems like its compatible with more roms mods and themes than 3.x and I've never had a problem with it. If it ain't broke..
[Droid Incredible Android Development] hgoldner:
Thanks, edited that file, but it still says 3.0.0.7 and prompts me to update.

I don't really care what ROM Manager says as long as I'm not using ROM's that use it, but it is an annoying bug. I figure stuff that messes with the system better have everything right, or just don't mess with the system and stick to simple stuff like flying birds and stationary pigs. ;)
[Droid Incredible Android Development] tdiman:
Thanks for reporting back about the .settings change - I suppose I never tried it, but assumed it would work based on some preliminary experimentation.

I feel your pain with ROM Manager. It *is* getting much better, and competition in that area has spurred a bunch of innovation in the past two weeks, which is promising.
[Droid Incredible Android Development] morph3k:
I'm having some problems with backups/restores and I was hoping someone might be able to help.

This is an example of what happens to me:

I test out a different ROM and play for a bit and decide to go back to CM7. So I reboot into recovery, wipe data/factory reset, wipe cache, wipe dalvik then restore my CM7 backup.

It restores and reboots. I then get boot looped. Sometimes it may go to the lock screen then just keep rebooting back to the cm7 logo but usually I never get to the lock screen, it just boot loops. I've already reformatted my SD Card incase that was the problem but apparently it's not.

Anyway what I have to do is restore my backup, reboot, let it boot loop, battery pull and then install the CM7 zip then reboot and it works fine. All of my data is there. So the original restore is restoring stuff but it will never work right I always have to go back into recovery and install the CM7 zip on top of it.

Sorry for such a long post I just wanted to explain in detail what is going on.

P.S. i'm using 3.0.0.8
[Droid Incredible Android Development] hgoldner:
Have you tried using an earlier version of CWM?
[Droid Incredible Android Development] burnmatoaka:
It almost sounds like a crucial bit of somethingsomething that you're wiping is not getting backed-up/restored, but is fixed when you reflash the ROM. Does this happen if you don't wipe anything before restoring your backup of CM7? Restoring a backup without wiping anything shouldn't cause you any problems.

[I for one welcome our new Android overlords ::: DInc::SLDC::x.7.28::CWM3.0.0.8::CM7latest::Chad's latest]