yashsingh1/xdaforums huggingface dataset:
[Droid Incredible Android Development] KGBxxx:
Link please. Almost done blazing. Need entertainment lol
[Droid Incredible Android Development] SoCalSpecialist:
just google Sumlee Anderson.
[Droid Incredible Android Development] donnyp1:
Dude, i want sum.
[Droid Incredible Android Development] SoCalSpecialist:
yea..**** hit the fan ASAP as soon as we all found out lol
[Droid Incredible Android Development] donnyp1:
Need to take her out for drinks n get her ****ty!
[Vega General] mutasim:
Check this post out here.

Hope this helps someone that knows what they're doing.
[Vega General] dagbro:
Just be patient. All Vegans obviously want to lick the Honeycomb as soon as possible, but the devs aren't helped by us "regulars" whining about it.

If anyone's working on this, i'm pretty sure they already know what to look for. In other words - linking to various HC port threads isn't going to solve anything.
[EVO 4G General] detcup4evr:
Just noticed this today, and not that it is really a big deal more of just a weird thing. I am wondering if anyone has encountered this and if so if there is a fix.

I noticed the when i dial *2 I get a force close and it basically kills the phone, I have to reboot to get it performing right again. I don't get that if I dial *3 or *7 or any other number. Everything else works fine

I have made a number of enhancements to my Phone so any of them could of been the cause since I never use *2:

Recovery: RA 2.2.2

Rom: Stock 3.70

HBoot: 2.10

PRI: 1.90_003

Removed Proxy For Internet (Helped with Xbox Live)

Suspecting one of these might of broke it:

Kernel: 2.6.32.27 Netarchy-toast mod 4.3.1 bfs-havs-nosbc

Circle Battery Mod

Thanks

**Opps Looks like I Put this in General, I ment to Put in Q&A Sorry**
[EVO 4G General] nukedukem:
What rom are you using? There is an apk needed for it to work. iirc it's named sprint provider or something. It's usually removed as bloat.
[EVO 4G General] mattykinsx:
I believe its espt.apk
[EVO 4G General] flying_low:
It's called Sprint Zone
[EVO 4G General] kd0axs:
Here's the apk:

http://db.tt/Dr2lmkW

Sent from my HTC EVO 4G with Tapatalk
[EVO 4G General] detcup4evr:
Thanks!! Looks like I uninstalled it a while ago, not thinking it did anything usefull. Thanks again!!
[Galaxy S I9000 Q&A, Help & Troubleshooting] Machpants:
Hi All,

When I got my Galaxy S many months ago, just after UK launch, I then did a mod for the OS to run off the SD Card. I was happy with the speed and how it worked so intended to leave it as it is. However the SD card has crapped out on me so now I have a brick! I cannot even remember which version of the mod it was, there were so many at the time and I didn't intend to remove it. I am pretty sure it was the Mimocan fix from here: http://xdaforums.com/showthread.php?t=724251. So how do I get the phone back to working stock, so I can start again?

Thanks in advance

noob with dead phone :)
[Droid Incredible Android Development] Deleted member 2776902:
Thank you :D 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?
[Droid Incredible Android Development] tdiman:
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.
[Droid Incredible Android Development] meazz1:
I tried the above CWR and my recovery screen is all black with white boarder on each sides.
[Droid Incredible Android Development] tdiman:
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.
[Droid Incredible Android Development] lllboredlll:
dont pull it booted on my device and ROM.... i'll do some extensive testing and report back
[Droid Incredible Android Development] shoman24v:
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.
[Droid Incredible Android Development] lllboredlll:
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
[Droid Incredible Android Development] shoman24v:
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.
[Droid Incredible Android Development] tdiman:
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.

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.
[Droid Incredible Android Development] tdiman:
Thank you for testing this! I've updating the OP with notes from both you and bored. And made the disclaimer larger with more *** :)
[Droid Incredible Android Development] shoman24v:
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.
[Droid Incredible Android Development] tdiman:
Just in case someone comes along late to the party, please note the above information added to the OP.
[Droid Incredible Android Development] jdmba:
Is it true that v2.5.x.x nandroid backups will not restore under v3.0.x.x clockwork recovery?
[Droid Incredible Android Development] khanam:
no. thats not correct - i have restored a bunch without issues.
[Droid Incredible Android Development] LifTeD_JK:
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.
[Droid Incredible Android Development] tdiman:
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.
[Droid Incredible Android Development] mikeymop:
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
[Droid Incredible Android Development] thelunchboxosu:
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.
[Droid Incredible Android Development] tdiman:
3008 is in there now also. Fast scrolling is back. I don't know if the glitch with some slcds is fixed.
[Droid Incredible Android Development] Heathsrow:
tdiman, I sent you a Private message with some questions about CWM and CM7 Nightly's. Any help would greatly appreciated!
[Droid Incredible Android Development] tdiman:
I updated the OP in this thread to reflect the new focus of the thread as well as address some of the good questions you had in the PM.
[Droid Incredible Android Development] khanam:
We should get the broken multi-touch repaired in CWR3 too now that we got koush to look at the other issues
[Droid Incredible Android Development] tdiman:
I would encourage anyone whom is interested in getting multitouch support working to learn how to build CWM themselves. This is the fastest, and likely the only, way to get it incorporated in CWM. Once the changes are submitted for review your contribution can be distributed to the thousands out there whom use the inc.

I believe that multitouch support is related to the recovery kernel, which is a good place to start.

It would be a great project for someone whom wants to become more involved in the community.
[Droid Incredible Android Development] meazz1:
Just flashed 3.0.0.8 via ROM manager.

Looks good, no problem for me, I am using SLCD.

I am liking the yellow/orange look.
[Droid Incredible Android Development] tdiman:
Great, its looking like the SLCD issues have been worked out.
[Droid Incredible Android Development] phaze one:
SLCD here. 3.0.0.8 works fine.
[Droid Incredible Android Development] tdiman:
Great!

So far I haven't heard any negatives about 3.0.0.8, hopefully people will realize the importance of upgrading.
[Droid Incredible Android Development] hachamacha:
I'm curious about what the CWM kernel (required for it's own functionality) has to do with how the installed /boot/* kernel behaves when phone is booted sans CWM?

I can see it does change some things, because I was using a ziggy kernel with the usual ziggy wifi module. After installing 3.0.0.8 via flash_image (once) and also via RM, I realized that the wifi module reported "incompatible with kernel version", so apparently there is interplay. It seems wrong to me, but maybe its obvious and I don't see it. Those modules are off setting in /system/bin/modules/ and should have nothing to do with whatever kernel is in CWM when CWM isn't invoked at startup.

To repair that, I just had to reinstall the same kernel using 3.0.0.8. Now it's fine. So I guess I'm wondering why the kernel used in CWM would affect multi-touch?

I'm willing to grab the sources, but probably am already involved in enough open source projects and other things to warrant an investigation of this one.

Thanks and any help appreciated --
[Droid Incredible Android Development] tdiman:
I think it has something to do with the way the recovery flashes the kernel, not anything with the recovery itself. according to the multitouch threads, you have to install the enabled recovery, then re-flash a multitouch kernel.

chad0989 may know specifically what fixes need to be implemented.

See http://xdaforums.com/showthread.php?t=906721
[Droid Incredible Android Development] hachamacha:
OK: I'll check with chad. Thanks tdi.
[Droid Incredible Android Development] jamor414:
I'm confused can somebody help?

I wiped and flashed Warm Z RLS1 a few days ago on Clockwork 2.5.05.

I just set everything up and just found out that a Clockwork 3 is available.

What am I supposed to do?

Update the recovery through ROM manager and then reflash the ROM? Do I have to do a data wipe?

What are the steps I need to take and do I need to start from scratch (i.e. wipe) since I just spent all the time setting up the new ROM on Clockwork 2?
[Droid Incredible Android Development] tdiman:
The android OS (Warm-Z) is independent of the recovery. They reside in different areas on the phone and do different things.

Thus, when you update a recovery, this will not affect Warm Z at all! That makes this process mostly painless.

Go into ROM Manager. Press menu and go to settings, and make sure "erase previous" is ON. Then, upgrade to 3.0.0.8 through ROM Manager. Boot into recovery to make sure it works.

The only errors I've seen are that some people have to repeat the process to get it installed. After you boot into recovery and make sure the upgrade was applied, then just boot back into your Warm Z ROM and be happy knowing you're running the latest and greatest recovery.
[Droid Incredible Android Development] jamor414:
Thank you - it wasn't working at first but I didn't have the "erase previous" checked.

Appreciate it!
[Droid Incredible Android Development] jamor414:
nevermind..
[Droid Incredible Android Development] tdiman:
No problem, Well done getting it all set up.

Rooting your phone is a commitment to constantly having to do little things like this to keep your phone working. Thats the fun part :)
[Droid Incredible Android Development] lllboredlll:
i did forget to mention one thing though...

great work on putting this together and it is definetly appreciated

i've come to find that cwm isn't as big of an issue as rom manager is....it still isnt wiping properly when flashing via rom manager but that has nothing to do with your files
[Droid Incredible Android Development] tdiman:
Even with CWM 3.0.0.8? This was the bug that slayher identified that was fixed after I built 3.0.0.6.

Make sure you have the newest CWM and ROM Manager. If it is something you can repeatably show let us know here.
[Droid Incredible Android Development] Shiftyshadee:
Soo.... Should I be using 3.0.0.8 with my amoled Inc ? I'm a bit confused by all of this.

Sent from my SCH-I800
[Droid Incredible Android Development] tdiman:
Yes, absolutely. The only problems that people used to have were with SLCD screens, but even those have been resolved.

As the OP says, make sure you have wipe previous recovery checked off in the ROM Manager settings and then go to 3008.

Let us know if you have any issues upgrading.
[Droid Incredible Android Development] hgoldner:
I'm still hearing folks prefer the 2.5.x.x flash method for even currently updated ROM's due to issues with 3.x.x.x.

I'm concerned when in the first post in the thread you warn that "CWM2 IS NO LONGER SUPPORTED AND MAY BREAK AT ANY TIME."

Not trolling, but can we make that 3.x.x.x works for everybody as nicely as 2 did before we force folks to "upgrade?"

Just sayin'.
[Droid Incredible Android Development] Shiftyshadee:
Thank you very much sir

Sent from my SCH-I800
[Droid Incredible Android Development] tdiman:
I don't think you are trolling at all, these are good points.

I am not the developer or even A developer, therefore when I say that CWM2 is no longer supported, I am making a factual statement based on a decision made by the developers (koush, mainly).

Since 3.0.0.8 series the only negatives I've been hearing have been related to things mentioned in the OP, most of them resolvable (by wiping correctly, reinstalling), although some not (inability to flash zip files using the cupcake scripts). I have yet to find someone who has gone through all of these steps and still has a broken CWM.

With the massive number of people rooting their phones daily, there's also a lot of people that need help with some of the details, things that it took some of us months of tinkering to figure out (ADB, flash_image, where to find old CWMs, etc.).

My goal is to promote people to switch because there's a lot of misinformation going on related to CWM. I recognize that not everyone may want to, which is why I also went through the trouble of posting the downgrade procedure, which is a major frequently asked question in various places in this forum.

Everyone is always free to make their own decisions. You may be fine never upgrading to the 3 series CWM (it is *required* on many new phones).

However, for example, I recently reformatted my entire phone over to ext4 partitions and saw significant performance boosts (this is how the Nexus S does things), and this type of upgrade would not be possible with CWM2.
[Droid Incredible Android Development] jdmba:
Just noticed that rom manger is back to pushing 3.0.0.5. Yikes!
[Droid Incredible Android Development] Dat108Kat:
720p video recording works but playback is choppy :(
[Droid Incredible Android Development] 00McD00:
Have to go down to the bottom where is says "All ClockworkMod Recoveries" and 3.0.0.8 is in there.
[Droid Incredible Android Development] jdmba:
Nope

Ha ... not the point though ... Koush is pushing 3.0.0.5 instead; I wonder why.
[Droid Incredible Android Development] tdiman:
There was some uncertainty early on that 3008 would fix the slcd issues, so my guess is that he's rolling it out slowly.
[Droid Incredible Android Development] SirBindy:
Even when I flash in recovery and manually wipe cache/dalvik, I don't get a clean wipe. I boot into whatever rom it is that I installed, and all of my old shortcuts/widgets are there still. Every time, I get a mishmash of 2 roms. Happens with 3.0.0.5 and 3.0.0.8.
[Droid Incredible Android Development] CUViper:
For a clean wipe, you have to clear /data too.
[Droid Incredible Android Development] XideXL:
I've been using 2.5.0.5 for the longest time because of all the problems I've been hearing of. After hearing feedback on 3.0.0.8 I thought it was finally the right time to update.

I just tried installing 3.0.0.8 from rom manager with no success. I had erase recovery checked and tried to reboot into recovery after it "successfully flashed recovery" and was just stuck in hboot and had to reboot.

I read many people have had to try twice, so I tried flashing again with no luck, then restarted and tried flashing twice and unchecking erase recovery before rebooting which didn't work either. Since 3.0.0.5 is listed as the newest version currently, is it possible 3.0.0.8 was removed for some reason but still has the link there?

Sent from my Droid Incredible
[Droid Incredible Android Development] tdiman:
3.0.0.5 is listed as the latest because there was some question as to whether or not 3.0.0.8 worked on SLCD. It does, but koush has yet to convert the links over to have it show 3.0.0.8 as the latest. Nonetheless, you should be able to install 3.0.0.8.

I haven't heard of this much trouble getting it installed before. I would try installing AMON-RA and reboot into recovery, make sure it works, then go back to RM and install 3.0.0.8. Make sure wipe previous recovery is checked for the entire time.

You could also install it manually using the method described in the OP or build your own PB31IMG.zip.

Keep us posted.
[Droid Incredible Android Development] gonzlobo:
I backup daily for CM7 nightlies. Every so often, I get the following error (see photo) each and every time (regardless of ROM or CWM). It always locks up on 'file' 19605.

It seems to me that there's a problem with SD-EXT, but according to Astro, the partition is empty. The only way to clear the fault is to reformat SD-EXT.

Any ideas what's going on (and am I breaking anything by reformatting)?* The phone seems to be fine.
[Droid Incredible Android Development] pete_kowalski83:
Is there ANYONE that has had problems running cwm 3008 on AMOLED??
[Droid Incredible Android Development] XideXL:
Got it to install with a PB31IMG.zip, I was just lazy at the time and didn't feel like doing that. It's odd though, amon-ra didn't flash through rom manager either. I think it has something to do with SR3.5. For some reason when I do a backup or install through rom manager it doesn't reboot into recovery by itself, but when I reboot into recovery afterwards the process starts. I could never figure out why, but it's only on this rom.

Anyway, all is well now. Haven't really used it yet though, so no feedback here.

Sent from my Droid Incredible
[Droid Incredible Android Development] tdiman:
Are you asking because you're having problems, or because you want to know if you should upgrade?

We can help you with both questions if you could be a bit more specific.
[Droid Incredible Android Development] tdiman:
Its unfortunately you had to go the PB31IMG route, as thats a hassle, but its good that it worked.

With previous CWM versions I was having the same issue as you were, with having to boot manually into recovery, but then the automated scripts taking over. So far I haven't seen it with 3.0.0.8 (crossing fingers).

There very well could be a compatibility issue with SR. I haven't used it since last fall, so I'm not up to date on that one.
[Droid Incredible Android Development] mwelch16:
I'm also having issues installing 3.x recovery. I checked the erase previous, installed Amon OK, but any clockwork install I try errors. I originally Rooted with Unrevoked.
[Droid Incredible Android Development] tdiman:
Which ROM are you running?

Please describe the errors?

Also, it may be worth trying the PB31IMG method described in the OP. This has worked for others.

With a little more detail I bet we can help.

-Michael
[Droid Incredible Android Development] gadget!:
I have ran across this issue several times, uninstall ROM Manager and then re-install it and I'll bet it fixes it, it has worked for me every time.
[Droid Incredible Android Development] mwelch16:
I'm running Warm Z. I'm going to All ClockworkMod Recoveries. It doesn't matter which I choose. I get "An error occurred while flashing your recovery."
[Droid Incredible Android Development] mwelch16:
So, it just worked for me. The only change was that I was charging. Would the battery level cause the problem I was having?
[Droid Incredible Android Development] ikediggety:
so glad it's not just me.
[Droid Incredible Android Development] mwelch16:
The one I got to work was 3.0.0.5. After that I was able to go to 3.0.0.8. Like I said, I have no idea why it decided to work. I'm beginning to think the download wasn't available for some reason.
[Droid Incredible Android Development] tdiman:
It seems unlikely to me that CWM would know anything about battery level, but I suppose anything is possible. It is good you got 3.0.0.8 installed and I bet from here on out things will be less glitchy.
[Droid Incredible Android Development] tdiman:
Hi ikediggety,

What problems are you having specifically?

So far in this thread if you go through it you'll see we have a 100% track record of getting CWM 3.0.0.8 installed with a little trial and error. I'm sure we can help.