yashsingh1/xdaforums huggingface dataset:
[Droid Incredible Android Development] AdhvanIt:
Since you've got a thread over here, ill bring my issues to it as well.

All of the ROM scripts I've looked at mount /system prior to formatting and flashing the ROM. I've tried it both ways-mounted and not-the recovery will not completely format the partition. I've had no issues until the 3 series recoveries, and have been running android since it launched.

While running 3.0.0.8, I'm getting various oddities. Themes screwing up and putting images in the wrong places, old wallpapers showing up as default on a clean ROM flash, etc. Right down to it booting up and then just locking up and rebooting after a clean flash. Push back 2.5.0.5 and zero issues.

If user error is to blame here, please explain where?

Boot to recovery>wipe data>flash ROM>reboot=issues

Boot to recovery>flash kernel>reboot=stuck at splash screen

Boot to recovery and flash that same kernel four more times consecutively, and it works.

Boot to recovery to restore perfectly working backup-restore succeeds but I go into a boot loop when I try to reboot.

If you recall, I'm the one that found the twitter feed between @koush and @dougpiston about erase previous recovery. Fixed a few issues, but two devices later, I'm back to those issues.

I have tried wiping all partitions. I've tried flashing over from one ROM to its latest build. I've tried everything that worked perfectly fine with Amon RA, and the 2 series clockwork recoveries. Nothing works.

If you'd like, when I get home I can give you exact steps I take and more detail on what happens.

Edit: I don't use CWM. I do everything manually. The only time I've installed it was to enable erase previous recovery. Otherwise, I typically flash recovery through Hboot. I've also RUUd back to stock and re-rooted. As well as had two warranty devices. Same issues.

Edit2: I also seem to recall you have multiple issues with CWM 3.0.0.5. Not trying to start an argument, just saying this.. If a piece of software is installed properly (by properly, I mean the way it should be done according to its developers), and has issues that make it unusable without hacking it in some way shape or form, then the software is not production quality and should not be released without specifically stating that it's an alpha or beta software.

I will admit that I misread the ROM scripts as they do not mount the partition until after the format. However, having done it without, and then trying with mounting, it makes no difference. The recovery is not formatting properly on my device.

via Evervolv GB
[Droid Incredible Android Development] XideXL:
Looks like I was wrong in thinking it was finally time to upgrade :(

I made my first backup with 3.0.0.8 today, and when I tried to restore I ended up in a boot loop. I tried restoring to a previous backup that I have successfully used several times before and I also got put into a boot loop with that. Guess it's back to 2.x series for me
[Droid Incredible Android Development] jbdan:
I have mixed feelings on CWM 3.0.0.8 my phone has never acted up like this on 2.5.0.5 which I was on for months.

I posted this in Q&A forum but check this out:

I've been on 3.0.0.8 for 2 weeks or so, flashed many ROMS/kernels made backups etc...I've

never

had one backup restore correctly with 3.0.0.8. I do everything manually never used ROM manager except to upgrade this recovery

When I upgraded CWM to 3.0.0.8 I chose "erase old recovery" and 2.5.0.5 was no more I'm in the orange.

3 days ago I flashed a newer radio (to 11.19 from 7.28) and after the last 3 days on 11.19 I was getting "time without signal" which I never got with 7.28

So I flash radio back to 7.28 today. All is well. My phone was low on juice so I plugged it up, powered off, and a bump charge till green so I could wipe batt stats (I loaded bleks new GB kernel last night). I powered on to get into recovery and low and behold there is CWM 2.5.0.5 in all green.

ROM Manager says I have 3.0.0.8, but I just booted into recovery again to see 2.5.0.5 in all green.

Maybe it's a good thing I'm reverted back to 2.5.0.5 without doing anything :)
[Droid Incredible Android Development] tdiman:
Out of curiosity, were you restoring across ROM versions (e.g. Skyraider to CM, AOSP to Sense, etc.)? If this is the case, you might try wiping Dalvik/Cache after the restore but before rebooting.
[Droid Incredible Android Development] tdiman:
There are two interesting things going on here that are obscure, but I do not believe either of them is related to a faulty recovery.

The first is that the radio file you used had the 2.5.0.5 recovery packed into it. The same thing happened to me when I downgraded to the 7.28 radio (I'm using it now). Not sure why whomever packed it did this, but its not a big deal.

Since you downgraded, the reason that RM shows 3.0.0.8 is a little more nuanced. In the clockworkmod folder there is a file named .settings. When you install a new recovery via ROM Manager, RM writes the version of the recovery to that file. It does not read it directly from the recovery. Further, sometimes RM will figure out the version you do have installed, such as if you manually installed an older 3.0.0.5 version, but if and only if RM knows that recovery exists in the first place by having it available to install.

In essence, it is a cosmetic issue with Rom Manager that you are seeing. You could manually go into .settings (probably) and change it to anything you want and it will show up.

I would recommend you upgrade back to 3.0.0.8 unless you're having other issues.

-tdiman
[Droid Incredible Android Development] tdiman:
Slayher did identify an issue with 3.0.0.5 related to wiping system that was corrected in 3.0.0.8 as far as we know.

I'll admit that there seem to be a lot of issues here and I am not familiar with the causes of all of them, but I'll take a stab. First, I believe you should treat 3.0.0.8 as a clean slate from 3.0.0.5, which as you point out I and others had tons of issues with. It was broken and shouldn't have been released. I learned a lot in debugging that problem which ultimately I never fixed, but I did assist by recompiling 3.0.0.5 from source and showing that many of the problems went away instantly and pointed this out to koush on IRC. Next, slayher identified a problem related to wiping /system that was fixed, and that is how we got to 3.0.0.8. Koush is being conservative saying that 3.0.0.8 is stable, but it is far more stable than 5 ever was.

There is a lot of misinformation that gets spread in these threads (especially the giant CM7 thread). There are also a lot of young/new people out there who have a genuine desire to be part of the community but are playing catch up with all of the linux/hardware/android information that is needed to truly understand what is going on (heck I ran slackware in 1997 and have been on linux since and I'm still playing catchup). These people are sometimes too quick to rush to judgement. In the past couple of weeks I've tried to carve out a small niche related to CWM and help people with it, and correct misinformation and point people here where I can. In the specific case of my user error comment, I was responding to the specifics of the post given the information in it. Many people would have taken that example as truth without trying it out. I simply repeated the example and showed that in fact it performed as expected. I'm not about to conclude CWM3.0.0.8 is bug free, only that many/most of the problems people have are correctable.

Now, to the specific details

First, I think it is good that you are avoiding RM. I use it for quick one off backups, but other than that I'm convinced it adds a layer of complexity and potential problems that I like to avoid.

On your newest phone, are these problems with 3.0.0.8? Are you wiping cache and dalvik when you install new kernels? And finally, are you often switching between sense/AOSP or between major ROM versions?
[Droid Incredible Android Development] AdhvanIt:
Here is what I've done so far this morning to end up with issues..

While running Evervolv 1.0.2b1...

Boot into CWR 3.0.0.8>perform nandroid backup>clear data>flash Redemption ROM 2.4>setup. This gave me no problems.

Boot into CWR 3.0.0.8>nand backup>nand restore of Evervolv backup that was performed just a little bit ago>boot loop

Boot into CWR 3.0.0.8>clear data>restore older (several times confirmed working) nand backup>boot loop

Boot into CWR 3.0.0.8>clear data>flash Evervolv 1.0.2b1>flash Gapps>reboot>no issues, but..... my wallpaper was there from when i was running Evervolv earlier. This wallpaper is the default wallpaper in my theme.

Boot into CWR 3.0.0.8>flash Tiamat 3.1.5>reboot>stuck at splash screen

Boot into CWR 3.0.0.8>proceed to flash the same kernel countless times>reboot>all is good

FYI. I've heard from a number of developers that clearing cache and dalvik makes no difference with a kernel. I've never done it and never had an issue. To me it's as useful as wiping data four times before and after every ROM flash like some people do. Waste of three seconds.. But yes, I've tried it since these issues to no avail.

Boot into CWR 3.0.0.8>flash this theme that I use every time I flash CM7 or Evervolv with no issues>clear cache>reboot>my debugging icon is now a battery_charge_anim icon, battery icons are way off, along with nearly every image that is contained in that framework.

Power down>boot into Hboot with CWR 2.5.0.5 on the root of my SDcard in PB31IMG.zip>flash>reboot recovery>restore nand backup of Evervolv that was just created earlier on CWR 3.0.0.8>reboot>my system is exactly how it should be after restoring that.

I have about 10 backups on my SDcard of various ROMs. This is just one instance of 3.0.0.8 screwing up like this. Its happened with a number of new ROM flashes, kernel flashes, etc.

My first thought was user error. Second thought was still user error, and my third was hardware compatibility. Although I've been around android far longer than most of the users you'll find here, I still make mistakes and do not know nearly what I feel like I should given my experiences. I'm willing to make every attempt possible at getting something to work before deeming an issue that should be brought to someones attention. Unfortunately, by the time that arrives, I tend to get hostile about the software because I've spent so much time screwing with it thinking I was doing something wrong..

Honestly, I've tried enough times that at this point I'd usually be stubborn and not even flash the recovery again. However, I love that the soft keys are enabled, and damn that orange is so much sexier than the green. Between those and the added power down from recovery option, I love it.

Really hope we can get it working for me.
[Droid Incredible Android Development] jbdan:
Much appreciated response thank you and will take the advice :)
[Droid Incredible Android Development] XideXL:
Nope, my current ROM and both backups are SkyRaider 3.5. After reverting to cwm 2.5.1.2, I was able to successfully restore my old backup as well as the new one created with 3.0.0.8, so basically 3.0.0.8 can create backups with no problem but it can't restore anything.

Sent from my Droid Incredible
[Droid Incredible Android Development] burnmatoaka:
found in your PMs... lol :p

I'm just joshing, but I do want to point out that I told you wrong, the twitter stream was actually between @clockworkmod (not @koush) and @dougpiston. Subtle, but I hate passing around erroneous information. sorry about that. ;)

but sorry for your troubles, AdhvanIt, really. have you really had 3 different dincs since cwm3 dropped? were they AMOLED? SLCD? both? and didn't you have cwm3 working for you for a while after we figured out the RM erase recovery fix? did it all go bad after the 3.0.0.5 update? (cuz that was fuct)

the only other variable I can possibly fathom that you didn't mention is your sd card. have you swapped it out and/or reformatted to eliminate that as a factor? given your success with other recoveries this seems almost silly, but 3 different phones?!!!? the flaw could be so tiny and specific to cwm3 that you wouldn't otherwise notice. it just seems so improbable your specific issue is solely the fault of cwm3 given the thousands of other satisfied 3.0.0.8 users, myself included. remember how OP had a dirty fix for one of the earlier cmw3 that involved sd swapping? correct me here, tdiman or did you work that out with koush for the latest recoveries?

as a last (maybe best) resort, would you be willing to hit up the Man himself for the sake of the dinc community? tidman did and helped us all out a ton. koush can actually be responsive it turns out. the dinc is getting on in age and we need capable/knowledge peeps such as yourself riding these devs, cuz I don't know about ya'll, I can't be upgrading hardware every 8 months.

cheers!
[Droid Incredible Android Development] AdhvanIt:
Ha. You are correct, sir. Found in my PM from the help of another user.

And it did seem to work for a bit after the first time doing that, but the more tests I ran, the more unstable and inconsistent I found it to be.

The issues my device were sent back for were unrelated. Screws coming out of the back with void stickers on them, that one they sent had a camera that didn't work and this one works perfectly. Even OC stable at 1.22ghz.

I did try a new SDcard. Well.... an old one. But fresh fat32 format and still had funny things happening.

I may have to see if I can get in touch with koush. I love my dinc, and like you, also cannot afford to buy a new device every six months or so.

via Evervolv GB

EDIT: I thanked you for the above post since you did indeed point that twitter feed out before you were able to post in the dev section. I did give you credit when I posted it though. I assume you saw that. =P
[Droid Incredible Android Development] tdiman:
The fix I thought I had didn't really work. It let me back up without locking up, but restores never worked. And eventually the backups started hanging again. It was the recompile and 3.0.0.6 that finally fixed this for me (which is still in the OP, you're more than willing to try it).

I'd go to IRC to do it if you take this route. I agree, I'm at a loss here as to what's going on. IRC is much, much easier than twitter b/c its realtime, although you may have to hang around awhile. My only advice is that he's abrasive if he feels attacked, so stay focused :)
[Droid Incredible Android Development] tdiman:
Good luck and let us know how it goes. I too plan on having the DINC for at least 2 years, so have a vested interest in keeping the updates coming out until I move on.
[Droid Incredible Android Development] tdiman:
Another thought. You could use the advanced features of CWM to try and pin down the error. It isn't guaranteed to work, but if it does it will certainly help with debugging.

Step 1: Install 3.0.0.8

Step 2: Boot into CWM. Restore a known working ROM that bootloops or has issues with 3.0.0.8.

Step 4: Reboot and verify that it has issues. Reboot twice for good measure, sometimes the first reboot doesn't work on the best of days.

Step 5: Reboot back into CWM. Use mounts and storage and format /boot only.

Step 6: Used advanced restore to restore /boot only. See if that fixes the problem. Keep trying with other partitions, one at a time, until you (hopefully) find one that works. If you can show this repeatably fixes your problem, you have a 99% chance of getting someone's attention whom has the knowhow to institute a fix.

-tdiman
[Droid Incredible Android Development] AdhvanIt:
Thanks for the advice. Ill give it a shot and report back.

P.s. just tried your 3.0.0.6 build and a restore ran through just fine. But you said this still has wipe issues, right?

Edit: FC issues...... trying the manual wipe/restore of each partition now.
[Droid Incredible Android Development] tdiman:
Interesting re: 3.0.0.6.

Slayher and koush found an issue with wiping prior to installing a ROM that was fixed in 3.0.0.7, then 3.0.0.8 addressed some SLCD compatibility issues. I do not know if the wiping problem was a RM specific thing or a general CWM thing. I never ran into it.

Out of curiosity, try 3.0.0.8 after 3.0.0.6 again, maybe it will work now? I'll leave 3006 up for you and others to try.
[Droid Incredible Android Development] AdhvanIt:
I'm restoring the full backup now with 3.0.0.8

I'm curious.. How would one go about formatting the recovery partition?
[Droid Incredible Android Development] tdiman:
You need to boot to a ROM (not recovery) and access the phone via adb.

There's a utility, /system/bin/erase_image, that will do it. at least on CM7 it is there.
[Droid Incredible Android Development] burnmatoaka:
I have SLCD and 3.0.0.7 sent me back to the mystery screen of yore. I got my DInc in late Oct'10 and was rooted by mid-Nov. Recovery for me was the black screen with two thin vertical white bars on the edges that freaked me out until my flash finished and rebooted. RomManager was pretty much MANDATORY for me. lulz... what a n00b!

Tried 3.0.0.7 cuz I want that freakin' multi-touch fix, DAMMIT!!! Any of you AMOLED guys have success with that? I guess I could TRY pushing a kernel through the darkness via ADB, but I haven't had too much luck getting it to talk to my dinc while in recovery lately. Haven't had time/need to look into it. Besides, I think while my luck is good, I'd best not tweek my 3.0.0.8 too much until we get this nonsense straightened out.

Oh, please do. I'm rather troubled by this whole thing. I haven't had wicked-bad issues like you guys, but I've definitely had a CM7 wallpaper load up after a full wipe and install of a Sense ROM. I even think that TB was showing some CM7 system files still on the phone, like Update Notification, or something. Oh, and I did think it was odd when I got a prompt to enable CM anonymous bug reporting after I wiped and installed IncrediblyReEngineered. Crazy.

And seriously, no worries about the citation. I was just giving you ****, but I did want to correct that thing about which twitter account koush was using. That night was kind of a blur. But thanks for my first "thanks." :) I will admit, I did go drop two junk posts in tdiman's other thread re:this**** just to meet the 10 post quota so that I could bust your ballz a little bit.

OT: can't wait to drop in on the CM7 nightlies thread and ask what's changed in the latest nightly since RC2. [teehee!!!]

EDIT: And THANKS to you in advance for helping to debug this sucker for us... sucks it has to be you, though. At least you know what you're doing, I'm still pretty helpless when it comes down to all this hard-core Linux business. I'm learning, though. Android has seriously turned me on to brave new worlds encompassed by the GNU/Linux computing environment. I installed Ubuntu on my AspireOne just this week, can't believe it took me this long.
[Droid Incredible Android Development] jesssiii:
Using 3.0.0.8 without issue for a week or so, running CM Nightly #14. Updated to #17, made backup. Later that day was having bootloop and went to install earlier #14 backup only to find it was gone. Gone. All but 3 were gone and one of those 3 was unusable. I was at work and my only backups were my original nandroid after rooting and Jager's AOSP, which I used.

This never happened before updating Clockworkmod so im concerned, though I realize it may not be the problem. But I have a fairly new sd card. Backups I've made since seem fine but haven't used them yet.
[Droid Incredible Android Development] doug piston:
For those that want/have a need for it, I have 3.0.0.8 in a PB31IMG up on my site.
[Droid Incredible Android Development] tdiman:
OP updated, thanks doug!
[Droid Incredible Android Development] jdmba:
Official Thread

As noted by the OP, this is not an official thread, just someone who thinks people should be upgrading to v3.x.x.x instead of sticking on v2.x.x.x.

Does anyone know where the official thread is? I am trying to get information on whether v3.0.0.8 properly wipes (although I suspect it does not). I am pretty sure I discovered this past weekend that v2.5.1.2 does not either.
[Droid Incredible Android Development] tdiman:
By official, I assume you'd mean something koush started and/or monitors, and there is not one, hence the need for somewhere on xda to collect information. I originally titled this is unofficial because I compiled a custom version of CWM and did not want people to think it was something that was released by the developers.

There's been bugs identified in the earlier cwm versions that have been fixed since 2.5.1.2. As far as I know 3.0.0.8 properly wipes and I've done some basic testing on this subject using the partitions menu and verifying that formatting actually works, although ROM installation scripts vary.

If you provide more detail with 3.0.0.8 we can help diagnose or at least give direction. I'm not sure that finding bugs in 2.5.1.2 is helpful at this point, as there's no one who is going to fix them.
[Droid Incredible Android Development] jdmba:
Not bug hunting v2. I agree that no one will fix them. I just noted after a bizarre hard reset that when I went into v2.5.1.2, did all the wipes including going back and factory reset (within cwm ... Not hboot) and then restored a nandroid, an email account which was wrong in the nandroid but subsequently fixed by me was still fixed after the nandroid restore. It should have restored to the wrong account. And when I say all wipes I mean dalvik then wipe data, then factory. Three different wipe types.
[Droid Incredible Android Development] AdhvanIt:
Over the last few days, I've done a number of different things. Not sure exactly what fixed it, but no issues with 3.0.0.8 anymore...

Could ROM manager not be invoking the erase_image script properly when having "erase recovery" checked? Or does it use its own script instead of the ROMs script? Maybe a fault in there somewhere.....

via Evervolv GB
[Droid Incredible Android Development] JoeyBert:
Can someone modify the Gingerbread keyboard to be flashable in 3.X?

found here: http://xdaforums.com/showpost.php?p=9636144&postcount=63
[Droid Incredible Android Development] sarge201:
I have tried everything in this thread! If I don't run cmr 2.5.1.2 on my Dinc it will not wipe and I get massive fc's! This one is a hardware rev 3.

Dinc running Magnolia 1.3/incedikernel/and BnB theme!
[Droid Incredible Android Development] Ruggerxpunk:
*edited* Nevermind.
[Droid Incredible Android Development] jdmba:
I still think it is a little strange that koush has rom manager pushing 3005 when it is the position that 3005 is crazy buggy and 3008 is the fix. 3008 us under alternative. Just very very odd.
[Droid Incredible Android Development] tdiman:
I'm not sure of the details of how ROM manager communicates with CWM recovery, but I'm glad its working. Something you did certainly helped.
[Droid Incredible Android Development] tdiman:
You are more likely to get help if you post this in the Droid Incredible Apps forum - I bet people there have more experience with the scripts.
[Droid Incredible Android Development] tdiman:
Hi sarge,

First, I'd suggest you go through some of the steps in the OP, including ensuring you have wipe recovery checked and making sure you are installing 3.0.0.8, not 3.0.0.5.

Some more detail on exactly the steps you are taking including CWM version, whether or not you are wiping, manual install vs. install through ROM manager, etc. would be necessary for us to help you get it working.
[Droid Incredible Android Development] tdiman:
Good point. I think koush doesn't have an inc anymore and relies on us (the community) to give him feedback on such things. I'll try giving him some feedback and see what happens :)
[Droid Incredible Android Development] burnmatoaka:
I don't understand why flashing recoveries through HBOOT would not have accomplished the same thing as "erase recovery" in ROM manager.

Hooray for your good fortunes, though.
[Droid Incredible Android Development] sarge201:
Ok, just did a complete wipe of my Dinc. Downloaded the new version of Rom manager. Updated to 3.0.0.8. It's now working perfect!
[Droid Incredible Android Development] tdiman:
That's great to hear sarge, well done.