yashsingh1/xdaforums huggingface dataset:
[Desire HD Q&A, Help & Troubleshooting] jkoljo:
Then follow the instructions in my ENG S-OFF tool thread. Flash Raidroid Stockify Series 1.32.405.6 in clockworkmod before using the tool.
[Desire HD Q&A, Help & Troubleshooting] jamiegoldsworthy:
Figured out maybe

Ok, think I've figured what to do. It involves fastboot and adb drivers, but I cant get the drivers sorted in anyway.

If anyone knows anything let me know, but Ima keep reading into it anyway :)

Cheers

Jamie
[Desire HD Q&A, Help & Troubleshooting] jkoljo:
You can follow radio flash guide (sticky), just replace "fastboot flash radio" with "fastboot flash splash1"
[Desire HD Q&A, Help & Troubleshooting] jamiegoldsworthy:
Where is that sticky? Can you link it...

Does it detail on how to install ADB drivers?

Cheers
[Desire HD Q&A, Help & Troubleshooting] jkoljo:
ADB drivers come with HTC Sync, so install that. Go to sticky roll up thread in android development subforum, and you will find it.
[myTouch 3G Slide Q&A, Help & Troubleshooting] letthebasskick:
im going to get a mytouch 3g slide and was wondering whats a good Sense rom without espresso and that includes live wallpapers and is good with 3D gaming?
[myTouch 3G Slide Q&A, Help & Troubleshooting] etu_aty:
this one right here --> http://xdaforums.com/showthread.php?t=839332

you dont have to do that data2ext thing if you dont want to... its just to make it "faster" if you have a class 6 sd card... so yeah, that one is the best sense rom for the slide :)
[myTouch 3G Slide Q&A, Help & Troubleshooting] SefEXE:
http://xdaforums.com/showthread.php?t=924793

Little ways down there you'll see the sense roms.

That should take care of the 1st 2 prereqs. As far as "good with 3D gaming"... What are you trying to play? The slide can only handle so much. :P

Edit: Or, etu_aty's got it, lol. xP
[myTouch 3G Slide Q&A, Help & Troubleshooting] letthebasskick:
could i use it with my 8GB micro sd (class 4)?
[myTouch 3G Slide Q&A, Help & Troubleshooting] letthebasskick:
is there a cyanogenmod that has a kernel built in that could do 800 mhz for the mytouch 3g slide?
[myTouch 3G Slide Q&A, Help & Troubleshooting] etu_aty:
emm no dont do it xD just flash the rom and you are good to go...

every single rom out there now has overclocked kernel by default, you just need to use setCPU to.. well set your cpu clock speed lol you can go up to 864 but i would recommend staying @825 or @806.. its just more stable in my opinion ;)
[Epic 4G Q&A, Help & Troubleshooting] deano0714:
the android lockscreen seems to think that you messed up when you connect 2 points but you didn't.... it happens every few times you unlock and you have to relock the screen and turn it back on for it to work... im running nebula rom... I hope you guys get what im talking about

Epic
[Epic 4G Q&A, Help & Troubleshooting] d00kiejones:
If you are using setcpu make sure you have it set to conservitive and set your min to 2 and max to max. IMOE if you have min set to low it takes a few seconds to recognize your touching the screen.
[Epic 4G Q&A, Help & Troubleshooting] deano0714:
im not... idk what the problem is it just messes up every once in a while and it wont work untill I relock the screen I think its a problem with DK28 because I've had this issue on other rims to... thanks for the suggestion tho.

Epic
[Epic 4G Q&A, Help & Troubleshooting] d00kiejones:
That is possible I have seen issues where the screen wont respond to touch unless you lock and unlock but I think it was on every version /rom I have tried. Have not yet seen this issue on viperrom (day 5)
[Epic 4G Q&A, Help & Troubleshooting] deano0714:
do you use the android pattern lockscreen? that's what im talking about

Epic
[Epic 4G Q&A, Help & Troubleshooting] d00kiejones:
Yes my old lady is nosey and it drives her nuts that she cant figure out my lock code.
[Epic 4G Q&A, Help & Troubleshooting] d00kiejones:
Some googleing shows a few people having a similar issue does your homescreen freeze also?
[Epic 4G Q&A, Help & Troubleshooting] deano0714:
no my homescreen doesn't freeze that's really the only problem im having with the dk28 rims... I like to have that so other people don't go thru me stuff especially my parents :)

Epic
[Epic 4G Q&A, Help & Troubleshooting] d00kiejones:
Ok seriously its ROMS not RIMS (rims are for your car/glasses) if using swype just type roms and hit space it will add it to your dictionary. Also caps and proper sentence structure will get more people to take you seriously. I dont really care but some of the more knowledgeable people can be Nazi's about that kinda stuff. Also read your typing before you hit send, this is not a txtmsg, it will help others with the same problem. Not trying to be a **** or anything just my $0.02.

As far as I can tell this seems to be an issue with android in general if your homescreen is not freezing also. If homescreen is freezing too sprint should replace the phone. Just Odin back to DI18 before you take it in. Sorry I could not be more helpful on this one.
[Epic 4G Q&A, Help & Troubleshooting] deano0714:
Haha sorry im using the gingerbread keyboard that corrects everything.

Epic
[Epic 4G Q&A, Help & Troubleshooting] d00kiejones:
Gotta say I don't the gingerbread keyboard as much as I like swype.
[Epic 4G Q&A, Help & Troubleshooting] running_the_dream:
I have that problem as well. It has been happening a lot since I've been on Bonsai 2.0.1. Didn't happen much at all on the various Viper roms. And I use an unlock pattern. I have to turn the screen off, then back on and retry before it registers correctly. Strange.
[Epic 4G Q&A, Help & Troubleshooting] deano0714:
Aha so im not the only one good I just didn't want it to be only my phone doing it phew!

Epic
[Epic 4G Q&A, Help & Troubleshooting] d00kiejones:
Didn't look super hard but have you guys tried adding to the bonsai issues page. been trying for like 30 mins and cant get it to duplicate on viper 4.0.3. or the old lady's Epic on nebula. My kids are both on stock DK28 and can get it one out of ten times.

EDIT: Kids are on stock DI18 not DK28.
[Epic 4G Q&A, Help & Troubleshooting] d00kiejones:
Thinking back my moment did the same thing and I was never able to solve it. Any dev's want to chime in on this?
[Galaxy S I9000 Q&A, Help & Troubleshooting] richarddwyer10:
I have had problems downloading from the market, downloads start then they don't install then when I try again downloads wont start untill I restart phone.I've tried reflasing to several roms currently I have darkys 9.2 ,please help me I've been stuck on this problem for a week now

Thank you in advance
[Galaxy S I9000 Q&A, Help & Troubleshooting] Boulbos:
Do they get stuck at "Downloading" without actually being able to see any progress made at the progress bar?
[Galaxy S I9000 Q&A, Help & Troubleshooting] Le Brun:
Did you try clearing the market cache?
[Galaxy S I9000 Q&A, Help & Troubleshooting] richarddwyer10:
It downloads & then it gets stuck,then it wont download at all until i clear cache & restart
[Galaxy S I9000 Q&A, Help & Troubleshooting] richarddwyer10:
I did a reset but the problem seems to be getting worse 20 restarts before market works.i think my phone itself,might need to send it back for waranty but i need a stock rom any ideas???
[Galaxy S I9000 Q&A, Help & Troubleshooting] JJEgan:
Do a search on the market problems first some have posted fixes .

Try factory restore .

If you take it back you need original rom or at least a stock Samsung rom to avoid being charged .

Rom samfirmware.com flash via Odin .

jje
[Galaxy S I9000 Q&A, Help & Troubleshooting] richarddwyer10:
I've just solved it I hope. I changed the sd card and market works some how.I'll see how it goes

Thanks for the response
[Droid Incredible Q&A, Help & Troubleshooting] pd240:
Did anyone flash the new recovery version in rom manager?
[Droid Incredible Q&A, Help & Troubleshooting] ProTekk:
I did. Not sure about changes in the coding but the new UI is nice.
[Droid Incredible Q&A, Help & Troubleshooting] TheWhiteBandito:
I heard it is mainly for 2.3 ROMs and such, is that true? I'm on Magnolia which is 2.2, would I run into any issues?
[Droid Incredible Q&A, Help & Troubleshooting] converge12:
weird.. i flashed the new recovery through rom manager then booted into recovery but still had 2.5 on there..
[Droid Incredible Q&A, Help & Troubleshooting] BMAF:
Flashed it this afternoon, using CM nightly #32. Using ROM manager to backup etc., would give me errors when it got to recovery. Some error about the sd card mounting I think. It would work fine booting to recovery, just not using ROM manager. Think the nightly update tonight might address the issue. Had to flash back to an earlier recovery to use ROM manager.
[Droid Incredible Q&A, Help & Troubleshooting] egeorgia:
Could not install a new rom with it.

sent from my Incredible using Tapa Talk
[Droid Incredible Q&A, Help & Troubleshooting] pd240:
I flashed slayers test kernel with it and it seemed to work fine. Have not tried to run a back up yet.
[Droid Incredible Q&A, Help & Troubleshooting] sabbotage:
Is there a zip to install this new recovery instead of using rom manager? I always remove rom manager from CM7.
[Droid Incredible Q&A, Help & Troubleshooting] converge12:
what is the new UI and why cant i boot into it? im on cm7.
[Droid Incredible Q&A, Help & Troubleshooting] DS36:
its orange now
[Droid Incredible Q&A, Help & Troubleshooting] jskolm:
You can get it from Koush's website

http://www.koushikdutta.com/2010/02/clockwork-recovery-image.html
[Droid Incredible Q&A, Help & Troubleshooting] Drewsipher:
anyone have a changelog?
[Droid Incredible Q&A, Help & Troubleshooting] superchilpil:
It requires some sort of new update script, we use the donut update script so koush is pushing us towards the future with this recovery, it works with any kernel because of it being koush's update script. Some roms might work, ask your favorite developer if it is compatable
[Droid Incredible Q&A, Help & Troubleshooting] Epicardium:
Darnit! Flashed it and now I can't install any font packs anymore. I guess it has something to do with the update script. Going back to a previous version if I can figure out how.
[Droid Incredible Q&A, Help & Troubleshooting] Drewsipher:
well... my I'm running cm7 so I knew I'd be well done in his hands... Multi-touch not working?
[Droid Incredible Q&A, Help & Troubleshooting] converge12:
anyone with an idea as to why i cant boot into it?
[Droid Incredible Q&A, Help & Troubleshooting] dustinb17:
I can't either
[Droid Incredible Q&A, Help & Troubleshooting] Homan13PSU:
Running CM 7 nightly #25. Flashed the 3.0.5 and I couldn't boot into Recovery. Just reverted to 2.5.1.2, guess we'll have to wait until something gets patched up in CM.
[Droid Incredible Q&A, Help & Troubleshooting] SteveG12543:
Worked for me. I like the look.

Sent from my Droid Incredible running Myn's Warm Two Point Two RLS5.3.
[Droid Incredible Q&A, Help & Troubleshooting] shmengie:
oh man, i can no longer access recovery. dayum...

i guess i should post some details: updated from 2.7.1.? (2 or 3, whatever) to 3.0.0.5 via free version of rom manager. just happened to have my stock rom loaded at the time.

edit: thx everyone. downloading the zip and reinstalling got me back up and running. yay! thx! i am disappoined, though, that md5 operations still take 15-20 minutes. i was hoping that would be fixed in this release.
[Droid Incredible Q&A, Help & Troubleshooting] dustinb17:
I can't boot into recovery using CM7 30. I'm not overly concerned because it looks like they'll be pushing something into future Incredible builds that will hopefully address it. Guess I'll try again tomorrow.
[Droid Incredible Q&A, Help & Troubleshooting] KGBxxx:
@clockworkmodOnly ext4 devices will be getting 3.0 recoveries. It is not needed otherwise.

That was tweeted today...
[Droid Incredible Q&A, Help & Troubleshooting] d_1000:
Like others have said, I have tried to back up my current setup, but no backup is created.
[Droid Incredible Q&A, Help & Troubleshooting] gadget!:
Works for me, I just done a backup.

Maybe I'm the odd man out, but the new color is really bright! I l liked the old color better.
[Droid Incredible Q&A, Help & Troubleshooting] jesssiii:
Don't care for orange,but worked fine for me. I used Quickboot paid version to boot into recovery though, not ROM Manager.

~Do you REALLY care what radio or kernel I'm using?~
[Droid Incredible Q&A, Help & Troubleshooting] doug piston:
http://dougpiston.com/files/Recovery/recovery-clockwork-3.0.0.5-inc.img_PB31IMG.zip

MD5: 8B3A8E3750CCBD32A0067A3FB02AED18

^^ If you don't use Rom Manager. Flash through Hboot.

Also if you use Rom Manager go into your settings and enable erase recovery, then reflash CW 3.0. Might fix some of the issues. Did for me.
[Droid Incredible Q&A, Help & Troubleshooting] nerogold:
Thanx guys I finally have my trackball speed again.
[Droid Incredible Q&A, Help & Troubleshooting] grifforama:
I'm screwed.

Tried flashing the new incredibly re-engineered.

Didn't work. Something about google deprecating some code....

Tried to reboot, and stuck at boot loop.

Pulled battery, and restore not working.

not. happy. at. all
[Droid Incredible Q&A, Help & Troubleshooting] khanam:
Try flashing previous working recovery through hboot

Sent from my desire z inc port.
[Droid Incredible Q&A, Help & Troubleshooting] MedleHed:
Here is the changelog, but it looks a little behind.

http://gh-pages.clockworkmod.com/ROMManagerManifest/CHANGELOG.txt
[Droid Incredible Q&A, Help & Troubleshooting] MedleHed:
Sequence of events....Using CM7 #32 and the .37 kernel with HAVS and Smartass.

1. Downloaded CM7 #33 using ROM manager then hit cancel when the download was complete. I don't like installing ROMs with ROM manager.

2. Updated my recovery to version 3.0.0.5 using ROM manager.

3. Booted into recovery with ROM manager.

4. Created a nandroid backup in the recovery.

5. Wiped dalvik and cache in the recovery.

6. Installed CM7 #33 in the recovery.

7. Installed the .37 HAVS/Smartass kernel in the recovery.

8. Booted into CM7 #33 on the first try.

No problems whatsoever! This procedure has worked for me every time and I never have problems with boot loops or any other madness. Maybe some of you are not doing the steps in the correct order. Maybe?
[Droid Incredible Q&A, Help & Troubleshooting] mr4r4n:
alls u got to do is when u restart the phone after having tried and failed i re installed the new recovery and got right in
[Droid Incredible Q&A, Help & Troubleshooting] pmdied:
Completely wrecked my phone. Would not let me restore any backups and got hung up on bootscreen constantly.
[Droid Incredible Q&A, Help & Troubleshooting] kynibe:


The same thing is happening to me. I can get into recovery manually but can't flash any rom it just freeze up.
[Droid Incredible Q&A, Help & Troubleshooting] khanam:
Multi touch breaks in this recovery.

Sent from my desire z inc port.
[Droid Incredible Q&A, Help & Troubleshooting] USSENTERNCC1701E:
Seems like that only for ROM Manager not actually for the recoveries.

I updated mine, made a backup just fine, but couldn't flash anything, didn't try a GB. I just went into ROM Manager and flashed and older ClockWorkMod. Only irritation is that not it notifies me of an updated recovery every time I open it, I even disabled check for updates.
[Droid Incredible Q&A, Help & Troubleshooting] kimbrian88:
I try to Install my existing ROMS i've downloaded and since this new recovery took out the script updating or something I can't install any roms anymore. My previous backups don't work either. What do I do?
[Droid Incredible Q&A, Help & Troubleshooting] ihtfp69:
Works here using cm7.

You should be able to flash any rom that uses an updater-script and update-binary. My Roms use them as well as Virtuous and CM. I'm not sure about any other Rom.
[Droid Incredible Q&A, Help & Troubleshooting] NilsP:
My Business Sense Desire Z ROM now uses new updater-script
[Droid Incredible Q&A, Help & Troubleshooting] mikesincredible:
updated to new recovery..immedietly tried flashing CM #33, just hung during the install process..eventually HAD to flash to an earlier version of CWM...oh..i had to use pwr+vol down+menu to get into HBOOT to reflash the earlier version....pwr + vol down didnt work
[Droid Incredible Q&A, Help & Troubleshooting] Lexus One:
FYI, not that I really need it for anything...but MT beyond 2 pts doesn't work for me using CMR 3.0.0.5 and CM7#33 and slayher's 2.6.37.
[Droid Incredible Q&A, Help & Troubleshooting] headcheese:
I tried v3 it worked to flash the newest cm7 nightly. But when I tried to flash a kernel it wouldn't boot up.

Went back to 2.5 and it works. I'm sticking with 2.5 for now.
[Droid Incredible Q&A, Help & Troubleshooting] mikesincredible:
I was having issues with roms not booting...a user on the cm7 topic suggested flashing #33 with previous CWM then update to 3.0.1 after #33 is installed..I did this ....now roms boot and kernels install....might help out somebody with like issues
[Droid Incredible Q&A, Help & Troubleshooting] khanam:
I'm on cm7 33 too with the latest slayher kernel and on multi touch I get just 2. How did you get more than that?
[Droid Incredible Q&A, Help & Troubleshooting] ihtfp69:
You need a modified recovery in addition to that kernel to get more than two touch points.
[Droid Incredible Q&A, Help & Troubleshooting] khanam:
Thanks. Where can I get the modified recovery please? And how would I flash it?
[Droid Incredible Q&A, Help & Troubleshooting] mikesincredible:
Its on the inc development page....something like "multi touch - testers needed" its by chad....flash via hboot... vol down+pwr...it will automatically load the PB31IMG that you download...follow the instructions tho.
[Droid Incredible Q&A, Help & Troubleshooting] khanam:
Thanks mike.
[Droid Incredible Q&A, Help & Troubleshooting] andrix10:
I flashed the 3.x cwm, because its needed for the #35 cm7 nighty

Sent from my cm7 Incredible
[Droid Incredible Q&A, Help & Troubleshooting] sabbotage:
No it's not. #35 will work just fine on the older versions of cwm.
[Droid Incredible Q&A, Help & Troubleshooting] andrix10:
I think u need it for 35 because it includes the new .37 slayer kernel
[Droid Incredible Q&A, Help & Troubleshooting] sabbotage:
No I'm still running cwm 2.5.1.2 and cm7 #35 with slayhers new kernel works just fine.
[Droid Incredible Q&A, Help & Troubleshooting] ACD168:
what ? no..
[Droid Incredible Q&A, Help & Troubleshooting] srh21:
Im having the same issue, now I cant go back to the older version to do anything! I know its not smart but I want to just throw this thing off the wall right now!
[Droid Incredible Q&A, Help & Troubleshooting] tim.ton:
I accidently installed the new version (I was click happy) and can't flash back to a previous version in ROM Manager, so I ended up installing the alternate recovery, whicb is light blue. How can I downgrade back to the original recovery?
[Droid Incredible Q&A, Help & Troubleshooting] USSENTERNCC1701E:
I went to All ClockworkMod Recoveries and kept trying till one worked, ended up being 2.5.1.2
[Droid Incredible Q&A, Help & Troubleshooting] mikesincredible:
can flash Chad's multi touch recovery, it's what I ended up doing. Not for the multitouch but for the sake of finding a recovery...hha...the 2.5.1.2 for me is unable to register for the cm nightly notfication updates...however it still works fine.
[Droid Incredible Q&A, Help & Troubleshooting] Lexus One:
Running CM7#35 & slayher's homebrew kernel. I can't use CMR 3.0.0.5 anymore. It started causing my phone to hang on just a blank screen. Had to battery pull to reboot. Phone would hang again and again. Tried cache and dalvik wipe, fix permissions...nothing would fix this.

I'm back on chad's CMR 2.5.1.8 now, and all is well.
[Droid Incredible Q&A, Help & Troubleshooting] hackules:
Can you explain or link me to the process you used please? I'm stuck with a phone that can only get to hboot and that's it.
[Droid Incredible Q&A, Help & Troubleshooting] tdiman:
Does anyone else have the problem with CWM 3.0.0.5 locking up randomly during a backup?

I had this problem with 2.5.1.2 and had settled on 2.5.0.5, which has always been stable for me.

I've tried installing it via HBOOT, wiping my entire backup directory, etc. It gets to some point in the process, a different point each time, and just hangs.

Frustrating to say the least, although I suppose there's no reason to move to 3.0.0.5 really, other than "I want it."
[Droid Incredible Q&A, Help & Troubleshooting] Droid_JD:
I have this problem too.

Also, the trackball stops working on me randomly. You also?
[Droid Incredible Q&A, Help & Troubleshooting] Echonmix:
Same exact thing happens with me, though I think it could be trolling me because every time I create a Nandroid backup, it gets a little bit farther before the inevitable freeze. Is there any official way to downgrade to an earlier version yet?
[Droid Incredible Q&A, Help & Troubleshooting] tdiman:
Search xda for 2.5.0.5 - you'll find it.

My thoughts are that the problem is either sdcard related or maybe the fact I have a early model (just after the release date). <shrug>
[Droid Incredible Q&A, Help & Troubleshooting] Lexus One:
I just used one of these recovery files from chad: http://xdaforums.com/showpost.php?p=10464756&postcount=1

Put PB31IMG.zip in the root dir of your sd card and then run hboot and select yes to update. Select no when it asks you if you want to reboot. Then select & run Recovery. This should get you into Recovery and enable you to do a nand restore or to load any ROM zip file.
[Droid Incredible Q&A, Help & Troubleshooting] CLeDInc:
Installed 3.0.0.5 and everything that has the new edify script works just fine for me. Backups work just fine too. My only issue is that when restoring a backup it takes for ever to check the md5 sum...is this supposed to happen. It eventually restores perfectly but it takes way longer to check md5 than when I was using 2.5.0.5

Actually I tried restoring and it just stuck at the boot up screen when I resorted the second time
[Droid Incredible Q&A, Help & Troubleshooting] TNS201:
It works fine for me too, but I noticed it was a little slow checking the MD5 and also was slow with backing up too, well the MD5 part.

Other then that it works fine, but noticed even clearing cache partition took a little longer and dalvik cache as well.
[Droid Incredible Q&A, Help & Troubleshooting] JMac024:
Seems like a ton of issues but I just have to try it. I can't not mess with this phone!

I am running CM7 Nightly. 38 .37 Homebrew 19. I will report back my findings.
[Droid Incredible Q&A, Help & Troubleshooting] spin0ut:
I was having a lot of issues with the new version and downgraded. The compression it reads is more for 2.3. Most devs are still using the old compression I believe
[Droid Incredible Q&A, Help & Troubleshooting] JMac024:
Well on reboot nothin. This happened the other day too when going into Hboot. 4 vibrations and black screen, pulling the battery now.
[Droid Incredible Q&A, Help & Troubleshooting] JMac024:
Back up. I like the orange. Wiped Caches, flashed a new nightly. No issues to be found. Sounds like Spin0ut may be onto something.....

I also don't use Rom manager to flash anything, I do it manually, forgot to mention that in my OP
[Droid Incredible Q&A, Help & Troubleshooting] spyder00:
ClockworkMod 3.0.0.5

:confused:I just rooted me DI lastnight and tried installing a Rom with no sucess... I have flashed ClockworkMod 3.0.0.5 right now...Is there no Roms yet for this version?
[Droid Incredible Q&A, Help & Troubleshooting] Lexus One:
I'm stuck for now with CM7#35 and CMR 2.5.1.8. If I upgrade to CM7#39 (and stay with 2.5.1.8) my screen goes blank and the phone locks up. If I stay with CM7#35 and upgrade to CMR 3.0.0.5, then I get the same exact results...blank screen, lockup, and have to pull battery.

So if I nandroid back to #35 and CMR 2.5.1.8, everything appears to work perfectly. No problems.

Any suggestions?
[Droid Incredible Q&A, Help & Troubleshooting] PhillyCheez:
Im using the new Recovery and it works just like before...

I have tested with the Athena ROM only though...

With new recovery...

I have backed up ROM and then restored it to see if it works...

I have downloaded a ROM and flashed it...

Seems to be working like usual for me.