yashsingh1/xdaforums huggingface dataset:
[Droid Incredible Android Development] AdhvanIt:
I know it's a little off topic, but... Will someone please verify that this is the correct MD5sum for the CWM 3.0.0.5 .img file?

c11ebec92c3439c33fb8eb9337dc2e83

I'm having so many issues (mostly flashing CM7 nightlies and MODs for them) that I'm almost positive my recovery is borked.
[Droid Incredible Android Development] sabbotage:
yep thats what i'm getting here :)
[Droid Incredible Android Development] rsarno:
I have same question. And i dont know how to read merge log lol
[Droid Incredible Android Development] tim.ton:
Why are there so many CM7 threads? Seems like this should be the official one.
[Droid Incredible Android Development] past_pluto:
No there should be 2. One for the RC folks and one for us nightly folks.
[Droid Incredible Android Development] userjf:
Updating shouldn't be a hassle. Just download with Rom Manager, takes about 5 minutes, then reboot into recovery and flash, takes about 5 minutes.

Clear cache and dalvik and you are done.

Total time about 10 minutes, depending on download speed, and you don't lose anything. I, along with many other people, have been doing this for some time with no issues.
[Droid Incredible Android Development] AdhvanIt:
so koush just released a borked recovery.

thanks for the confirmation!
[Droid Incredible Android Development] userjf:
Not necessarily...

I am unable to reproduce any problems when flashing the zip mods through cwm3 recovery or through Rom Manager.

Many other people have reported the same success with the new Rom Manager and cwm3.

Works for me every time I test it.
[Droid Incredible Android Development] andrix10:
I never had issues with cwm 3, or any flashing of kernels, nighties, maybe I'm just lucky
[Droid Incredible Android Development] bobby janow:
^^ Me too. (userjf) I think if you just follow procedures systematically then it will work. Although I do believe that there is different hardware out there so that might come into play as well.
[Droid Incredible Android Development] domesdkg:
I haven't had any problems either, been flashing over since Crackflashers
[Droid Incredible Android Development] ssick92:
Ya before build 35(?) I think it was when we needed to update CWM, I would just download the roms through Rom manager and install, no wipe, no nothing. But now with CWM 3, I cannot for the life of me get this thing to finish a nandroid backup, so I haven't been using ROM Manager at all to update to the newer builds.

I have confirmed the md5sum of the download, I have flahshed it manually through recovery, but I still cannot get this thing to finish a nandroid backup. Kinda makes me skeptical about trying new ROMs and such. I'll try 1 more manual flash of CWM 3.0.0.5 and see if that works.

BTW Build 40 seems to work fine for me, no FC's or anything yet.
[Droid Incredible Android Development] userjf:
Strange that it doesn't work for some people. By the way, CWM3 is NOT required. Not one has to update to it for the current nightlies...
[Droid Incredible Android Development] elpeterson:
just to confirm. the appbrain fast web installer not working has nothing to do with this ROM, its an issue with the new market correct?
[Droid Incredible Android Development] AdhvanIt:
following procedures has nothing to do with it... ive been running a rooted android device since they gained root on the g1, have had five others, and have never had issues like this.. 2.5.0.5 ran perfectly. i also know that CWM recoveries are prone to issues. corrupting files, and even bricking some devices (namely the eris).

this morning, i RUU'd, formatted SD and re-rooted. downloaded new CWM recovery and verified MD5sum. same things happening.

im curious though. i know that userjf shows in his sig SLCD... what screen type do others without issues have? i have an original amoled.. could something have been changed (accidentally?) that require slcd for proper operation?

mine will show the backup as successful, but will not restore. md5 mismatch every time, regardless of whether backup and restore are done through recovery or RM.

EDIT: I just recreated the MD5sum using adb. CWM3 still gives me MD5 mismatch error. so that at least confirms the recovery is borked there.

it also fails installation. even when done correctly through recovery, ive been getting stuck at the splash screen, and logcat shows a constant loop. though this doesnt happen every time, its at least 7 out of 10 times that it does happen. even after RUU and re-root....

you are correct... but when youre putting out mods for people, you should have a similar environment set up-even if only for testing. otherwise youre unlikely to be able to reproduce errors.

Pons, sorry for hijacking your thread here....
[Droid Incredible Android Development] ssick92:
Oh well then I'll stick with one of the older versions. 1 more question, from Rom Manager, CWM 2.5.0.2 is the only older version I can flash. Will this old of a CWM be an issue with flashing these nightlies? And is there anywhere I can manually download the latest recovery before 3.x
[Droid Incredible Android Development] MedleHed:
I haven't had any problems either. I'd really like to know what people are really doing with their Inc's to get these problems. Outside of wonky hardware if you install things properly you shouldn't have any issues.

Edit: I have an AMOLED screen.
[Droid Incredible Android Development] userjf:
These nightlys have been using the same update script for almost a year. So whatever you could have used almost a year ago to flahs, you can still use it now if you wanted to.
[Droid Incredible Android Development] jesssiii:
That problem seems fixed for me in #39, but still can't access phone storage, only SD. It's bugging me enough I switched to a senseless rom. Is that common to all aosp or just CM7? Perhaps because it's reverse engineered 2.3?

OCD Battery Syndrome:

>100%=worry

>90%=depression

>80%=anxiety

>70%=panic-charge ASAP!
[Droid Incredible Android Development] AdhvanIt:
evervolv reads both just fine.
[Droid Incredible Android Development] bobby janow:
Yeah, that's why I said that different versions of hardware might come into play. I have an original amoled as well so it's probably not that tree you want to bark up.

And since you completely rerooted then it really can only be hardware related. Just trying to think this logically through.
[Droid Incredible Android Development] JLO155:
Anyone know if the RC1 Data Throttle Remover works on Nightly #40?
[Droid Incredible Android Development] AdhvanIt:
uh. that would imply that software cant have issues. which software issues are far more likely, and wonky hardware would have shown itself well before now i think. ive had my inc since july.

not saying that user error cant be a factor. just that given the experience ive had with android and HTC devices, and the steps i take prior to installation of ANYTHING.. its unlikely in my case.

kicked my theory to the dirt.
[Droid Incredible Android Development] sabbotage:
I have an SLCD Inc, and I first rooted with CWM 2.5.0.5 and when 2.5.1.2 came out I downloaded the update.zip and flashed it through hboot. I don't use rom manager either. I always remove it from the rom before I flash it. When CWM 3 came out I downloaded the update.zip for it and flashed it through hboot right over top of 2.5.1.2. I've had no problems yet making or restoring nandroid backups, or flashing updates for that matter.

It doesn't appear that any process works better than others. Everyone will do the updates differently if they are given different options for doing it. I like to do updates through hboot or recovery simply because it seems to give me more control over what i'm doing. It seems like different model phones like different ways of doing things though. Sucks that you cant get yours to work right. I'd like to know what it was when you get it figured out though :)
[Droid Incredible Android Development] AdhvanIt:
im still unsure that it would be hardware related, honestly. the same software (though all fresh downloads) was re-installed after re-root. theres no reason that the recovery wouldnt be used in consideration as ive not had any issues prior to flashing it.

by no means am i saying that the hardware isnt the culprit, im just not convinced as ive had no issues until flashing this recovery.
[Droid Incredible Android Development] elpeterson:
once i connect i can access everything; internal, SD, partition without any problems.

no idea about the rom specific question though
[Droid Incredible Android Development] toosurreal01:
When you turn on USB storage it mounts both drives (internal and SD card)
[Droid Incredible Android Development] CUViper:
The emmc and sdcard storage should both work. If you mean that your pc can't see one, and it's Windows, then try removing the phone drivers so it can redetect it.

Only the initial gingerbread ROMs with people hacking stuff from other phones could be called "reverse engineered" - CyanogenMod is built from the real 2.3 source code.
[Droid Incredible Android Development] tdiman:
User error is often the problem, but not always. I would like to point you to a fix that I finally discovered for a cwm3 problem (actually its been happening for anything > 2.5.0.5). Its difficult to describe this as anything other than a problem with the recovery itself.

http://xdaforums.com/showthread.php?t=959512

I have an AMOLED and I ordered the DINC shortly after release date. Everyone says they're knowledgeable here, but I've been running linux based machines for 14 years and writing code for 17, I know what I'm doing.
[Droid Incredible Android Development] sunder74:
I've been around Android equally as long and have had more devices than I care to mention. (Mildly obsessed) anyway I have both an slcd and an amoled and have the same issues and can also confirm the md5 sum mismatch. I would venture to agree the recovery is borked. (It's why I preferred AmonRA for the longest.)
[Droid Incredible Android Development] localceleb:
What's "RC1.5"?
[Droid Incredible Android Development] sunder74:
Just the op joshing a bit... building up to RC 2. ;-)
[Droid Incredible Android Development] tdiman:
I was getting this too once I solved the backup-hang problem.

Try running fix permissions from the CWM3 recovery (not ROM Manager). Re-run a backup and try restoring it.

I couldn't restore an old backup this way, but new backups seem to be restoring now.
[Droid Incredible Android Development] elpeterson:
a search might help you out

it was the OPs way of adding some humor into a mixup with RC1 came out for the Inc
[Droid Incredible Android Development] userjf:
Are you saying that fix-permissions fixed your md5 problems completely???
[Droid Incredible Android Development] Futur Innovations:
So is it confirmed that #40 will fix the sdcard mounting problem (the freezing issue)?
[Droid Incredible Android Development] mystics7:
Can #40 be flashed over RC1 or is a wipe needed?
[Droid Incredible Android Development] AdhvanIt:
Not the issue. Read a few posts back. CWM3 is unable to read (or reproduce its own) MD5.

via Evervolv GB
[Droid Incredible Android Development] AdhvanIt:
Very strange........ ill give it a shot though.

via Evervolv GB
[Droid Incredible Android Development] tdiman:
Well its like I fix one problem and something else comes up, so yes and no.

First I couldn't successfully complete a backup. Now I can.

Then I couldn't restore b/c of md5 mismatch. Now I can get past the md5 check.

However, the restore process is hanging on "Restoring data...".

So I'm hopeful that I can get this working, but not convinced 3.0.0.5 is salvageable at this point.
[Droid Incredible Android Development] userjf:
Both issues, locking up and getting invalid md5's, could be related. They both seem to indicate an issue with data transfer. Whether its hardware or software (probably software), something is causing corruption making invalid md5's or lockups.

That solution on that link, however, seemed quite wonky.
[Droid Incredible Android Development] sunder74:
Yeah just ran through the process you described and I'm hanging at the data restore also. I've emailed Koush and messaged him via Twitter to no avail ... but lol we can hardly get a change log much less a reply on a buggy recovery.
[Droid Incredible Android Development] userjf:
I hope you get a reply from koush, but I've written him multiple times in the past and have never received any answer... and that was for an issue with the PAID version of Rom Manager! I would think he would at least reply to paying people.
[Droid Incredible Android Development] Teksu:
I get the random freeze when mounding my usb storage, doesn't happen often. When it does happen i can turn the screen on and off with the power button but nothing else responds, it just hangs there with the "mount or cancel" screen. A battery pull is the only way to get the phone to respond to other commands. but the next time i try right after the reboot it works.

annoying, but not a deal breaker, if i'm mounting my sdcard for usb im usually gonna reboot it anyway, and cm7 boots pretty quick anyway

no problems with cwr 3.0.0.5 here. i can wipe, backup, restore and flash everything on my amoled dinc. I never use rom manager for anything i don't have to. always download the latest builds with my windows box and drop them on to my sdcard and reboot into recovery with the power button long press - reboot - recovery
[Droid Incredible Android Development] userjf:
What about a difference in SDCards. Maybe certain sizes are suspectible to corruption. that could explain why it is so random.

I use the 2GB card that came with my phone.
[Droid Incredible Android Development] AdhvanIt:
16gb sandisk

via Evervolv GB
[Droid Incredible Android Development] userjf:
Can you do the 3-button reset instead of battery pull? Getting to the battery is no fun.
[Droid Incredible Android Development] tdiman:
This is a very strong possibility and so far probably the largest source of variability between all of us that could explain for the differences in ROM Manager.
[Droid Incredible Android Development] Teksu:
16gb samsung card i stole from my wives' Fasacinate

i gave her the 8gb sandisk i had bought for my inc

I never remember that i can do that, i'll try next time it happens. but i rock my dinc nude so its not much of a hassle to pull my batt.
[Droid Incredible Android Development] driphter:
posted a data throttle remover for rc1.5 #40. also posted a version for rc1. enjoy
[Droid Incredible Android Development] buya97:
just downloaded nightly 40, and now whenever I try to install a program it comes up unsuccessful, it doesnt matter what the program is
[Droid Incredible Android Development] PvilleComp:
You guy’s were getting me worried so I ran some tests as well:

AMOLED

CWR 3.0.0.5

8GB Kingston SD

Stock CM kernel 2.6.37-cyanogenmod+slayher@homebrewed#1

Stock Radio 2.15.00.7.28

I backed up CM7 #40 through recovery, restored an RC1 backup I made last night (also made in recovery) and it restored OK. Reboot into recovery and restored #40 and it restored OK.

I did run a fix permissions from ROM Manager back on #36 but have not run it since and never from recovery.

I hate to suggest it because it will be a time suck, but you might want to rebuild from HBOOT up clean. Just a thought. Hope my tests help in diagnosing this.

On the bright side I did get to look at my “Lady in Red” boot screen more often then usual – so I got that going for me… which is nice!
[Droid Incredible Android Development] Teksu:
Thanks!

been using you work since back in the 9630 days. i miss bbm, been having some issues with gtalk not receiving messages. i have to check my gmail throughout the day to make sure i havent missed anything.

Sorry for getting off topic, just wanted to give a shout out :cool:
[Droid Incredible Android Development] driphter:
haha thanks! You might want to go into settings>applications>manage applications> and then press ALL at the top . . . then scroll to the bottom and click clear data.

never hurts to try that. Usually clearing cache on gapps fixes things like that so do the same for gmail, but do cache and not data.

hope this helps!
[Droid Incredible Android Development] elpeterson:
whoa whoa whoa, what is this three button reset? i have an innocase active so its like pulling three backs off to get to the battery
[Droid Incredible Android Development] userjf:
Power button + one of the vol buttons + trackball button.

It's like ctrl+alt+del :)

Hint: Go ahead and try it before you need it so you will be sure of how it works.
[Droid Incredible Android Development] MMBosstones86:
Clear data/cache and force close the market from settings. Worked for me
[Droid Incredible Android Development] cu-n-az:
SegoeUI Font?

A while back when I was running SkyRaider ROMs I got to really like the Segoe UI font. I still have the ZIP file that I used to flash it with. I don't really understand much about the mechanics of fonts, but do you think that if I got you that ZIP file you could somehow re-make it into one that would work with CM7? Thanks in advance... :)
[Droid Incredible Android Development] ssick92:
Well it seems like flashing an older recovery, then back to 3.0.0.5 fixed my nandroid issues. I successfully backed up a ROM and then restored it afterwards. Just reflashing CWM didnt fix it, however flashing to an older version, then back to the new one did seem to fix me problems.
[Droid Incredible Android Development] buya97:
thanks for the market problem, now a new one as arisen, google voice force closes as well now, tried to clear data and it still does it
[Droid Incredible Android Development] sabbotage:
Yeah I could do that. PM me a link to the zip and I can make it.
[Droid Incredible Android Development] ksidirt:
I can't get my car stereo to find my phone via BT, but my phone finds my stereo (So I can't pair them). Any advice?

Is it kernel related?
[Droid Incredible Android Development] TreyDaPrince:
I am getting FC's left and right. I wiped everything, even fixed permissions and everything is still force closing. I mean everyhthing! Even when I try to uninstall apps to re-install the phone reboots. I've tried both CM Nightly 40 and CM7. Both do the same.

Any suggestions?
[Droid Incredible Android Development] football0552:
Same here
[Droid Incredible Android Development] ksidirt:
Did you use Rom manager to install this?
[Droid Incredible Android Development] AdhvanIt:
How are you flashing the ROMs?

via Evervolv GB
[Droid Incredible Android Development] TreyDaPrince:
First time I did, second time, I didn't. Even though I wasn't coming from a nightly.
[Droid Incredible Android Development] cam30era:
What car? I've had no problem paring BT on CM7 with both a GM and a Ford. I assume you made your phone discoverable in BT settings?
[Droid Incredible Android Development] JLO155:
Thanks Driphter! The Data Throttle Remover is awesome! Appreciate all the hard-work in keeping these up to date!
[Droid Incredible Android Development] ksidirt:
Its a Ford. Kenwood stereo. And yes I did.

It worked fine yesterday when I was on SkyRaider. Hmmmm.
[Droid Incredible Android Development] cam30era:
I try fixing permissions. If that doesn't work try reinstalling from recovery, not ROM manager
[Droid Incredible Android Development] jbeezybaby:
Ok so a question.... I've been flashing for a bit and always wipe the cache before the install. Does it really matter or is one method preferable to the other.
[Droid Incredible Android Development] SynisterWolf:
I have a 32gb king and I havent had a problem yet.

Sent from my sexy assistance (HTC Incredible cm7)
[Droid Incredible Android Development] Atlas.rouge:
I didn't wipe cache/dalvik... nothing is wrong yet... should I be worried? Lol

Sent from my HTC Incredible running CM7.
[Droid Incredible Android Development] SynisterWolf:
I wouldn't until a problem shows up. I don't wipe either and haven't found an issue.

Sent from my sexy assistance (HTC Incredible cm7)
[Droid Incredible Android Development] GatorsUF:
How come when I turn the screen on it takes about one or two seconds to get to the right brightness? Its always a bit dim at first.
[Droid Incredible Android Development] ksidirt:
Do you have auto brightness on?

If so, that's why.
[Droid Incredible Android Development] spidey81:
Been pairing mine fine with a Kenwood excelon using several different kernels and nightlies since before RC0. I always flash through recovery wiping cache and dalvik before hand. Also fix permissions before first boot and after through RM, then reboot.
[Droid Incredible Android Development] bboyle:
I flashed with CM 3.0, no problems. Like the new features.

I also pair with a Parrot bluetooth in my car, no problems there either.
[Droid Incredible Android Development] MedleHed:
16 GB Patriot. I thought I heard there was a problem with the 16 GB sandisk chips. Must research!
[Droid Incredible Android Development] SynisterWolf:
Does anyone have the new update.zip template for cwm3.0 I have something I need to flash.

Sent from my sexy assistance (HTC Incredible cm7)
[Droid Incredible Android Development] jesssiii:
Ok, thanks. I used to be able as well, couldn't remember when exactly it changed. Could it be a driver issue? I'll try reinstalling them later.

OCD Battery Syndrome:

>100%=worry

>90%=depression

>80%=anxiety

>70%=panic-charge ASAP!
[Droid Incredible Android Development] jesssiii:
Have it, check PM's.

Sent from my ADR6300
[Droid Incredible Android Development] michael28:
I downloaded CM7.0.0 RC1 and I am getting a lot of force closes on gmail, facebook and other apps. I also get a force close on settings when I attempt to change the ringtone. Anyone have any idea why this is happening? I did a full wipe and nandroid backup
[Droid Incredible Android Development] dspcap:
I am new to CM7 and nightlies... love it so far. I have a couple of dumb questions.

1. #40 came after CM7 RC1 and has some fixes?

2. Has anyone else noticed that sometimes when they turn the phone on from sleep, they have to press the top button a few times to get the phone on?

3. Any reason we can't load the nightlies from ROM Manager?

4. I downloaded a mattyg battery for #40 and after about an hour, it reverted back to the old battery bar. Should I just assume that since the nightlies are beta's, these things just sometimes happen?

I am sure these have been answered somewhere, but I don't have time to read 540 pages :-) I've read about 40 or so and learned a lot.

Thanks
[Droid Incredible Android Development] past_pluto:
LOL I always feel like my battery is really at 70 when it says 100 b/c anything under 30 and it's a full blown panic attack.
[Droid Incredible Android Development] Incredible510:
I had the same problem. Go in ROM Manager and select Fix Permissions. After you reboot alot of the apps should work.

Once you do this a couple times most of the apps should work. I still have issues with a couple, like Hadcent SMS.

EDIT: Uninstalled than reinstalled the apps that were still FCing and they now work.
[Droid Incredible Android Development] Atlas.rouge:
Lol same here. The thing I worry about is when it drops like 3-5% in under a minute. THAT'S when I start crackflashing and loading old builds.

Of course, I find out that if I wait 2-3 days, the kernel gets used to the battery wear-tear and I actually get good battery life...I have ROM Tourette's lol.
[Droid Incredible Android Development] SynisterWolf:
Sent from my sexy assistance (HTC Incredible cm7)
[Droid Incredible Android Development] ksidirt:
That was it. Thank you.

I also needed to go onto my stereo and reset my device list.
[Droid Incredible Android Development] Pons:
Cleaned up the OP a lil bit. Still a WIP (mainly because I am never satisfied with anything, hence me flashing nightlies). Any ideas for improvement, let me know.
[Droid Incredible Android Development] meazz1:
Running CM7 #40.

ROM manager has not been working right lately starting from build #35.

I have seen many posts about the issue.

Below is my log of the ROM mgr in Clockworkmod folder in the sd card.

It seems that the update.zip has problem. When can I download a fresh copy of this file from?