yashsingh1/xdaforums huggingface dataset:
[Droid Incredible Q&A, Help & Troubleshooting] edcypher2k:
doug piston, are you calling me a jackass? if so, why? Because I already didn't know everything like you did... please spare me the bs. You know, not all of us, can know as much as you or others. That's why we, come to these forums, for help! Not to be sh**ted on when we missed a step or two. Sorry, I didn't have all the time in the world, to read every single thread on rooting to make sure I had all steps covered... This reminds me of why Adrenalyne said on his website back in like June of this year, that he decided to leave the Android community and stop dev'ing indefinitely, because he's tired of all the animosity some MODs or devs have on the community users who seek help. He said "whatever happened to people helping each other?!" Taking credit for things, treating inexperienced droid users like crap, or simply not responding to people when asking for help...

If you weren't calling me a jackass... Then, apologies in advance, for me misinterpreting your comment. Otherwise, f**k it, I'm out!!
[Droid Incredible Q&A, Help & Troubleshooting] enlightened79:
I believe Doug was calling himself a jackass, not you. :) If you look you'll see the arrow is pointing to his name, not up to your comment. For the record, he's uber helpful to users across the web but not above admitting he misread a thread. So, deep breaths- no one's saying you're a jackass.
[Droid Incredible Q&A, Help & Troubleshooting] doug piston:
Was at myself. No worries and crack a beer.
[Droid Incredible Q&A, Help & Troubleshooting] edcypher2k:
BIG Oops! Sorry Doug, I was already spun up with other people on other forums, and then thought you were giving me crap too... Sorry dude! I'm glad you didn't get all "e-thug" on me... Appreciate it! I'm cracking a beer as we speak... Ahhhhh. Delicious! Anywho, I do agree with enlightened79, you have been a super helpful person to the community and I was saying to myself, "Doug Piston doesn't seem to be" what I was saying about how Adrenalyne thinks about some of the "bad apples" in the Android community.

Anyway, again, thanks for your helpful posts all over... I have a lot of your threads bookmarked!
[Droid Incredible Q&A, Help & Troubleshooting] mikeymop:
I have a question on the replacementment process with Verizon, you mind if I PM you?
[Droid Incredible Q&A, Help & Troubleshooting] hafler240:
Drivers won't install

I think i'm having this "SLCD bricked" issue. I see that some people's phones actually work but their screen does not. The most i can get out of my phone is the led indicator, it's solid orange in just a few mins after a full night of charging. When I press the power button i get 1 vibration and then i press and hold volume up + power i get 3 vibrations. I've tried booting up in hboot but i cannot see the screen and when i get to step 3 (3.) Check to make sure that ADB can see it by typing adb devices into the command shell you opened earlier) no devices show up in the command prompt. I tried the next step but obviously it says "error: device not found." When I open up my device manager's "other devices" and select "Qualcomm CDMA Technologies MSM" (because that's the device that is recognized when i plug in the phone and attempt to power up) the update fails. And yes, i've tried updating the driver via the "usb_driver" folder in the AndroidSDK folder i downloaded, but no luck. I've also tried the automatic update but that also fails. If you guys could point me in the right direction or help me fix my errors, I could finish these steps and get my phone working.
[Droid Incredible Q&A, Help & Troubleshooting] doug piston:
What did you flash before this? Sounds to me you flashed 2.1 onto a Slcd inc.If this is true there is a fix.
[Droid Incredible Q&A, Help & Troubleshooting] hafler240:
I rooted it but was unrooting. I gave up after about 20hrs of messing with it and took it to verizon. They gave me a brand new one and i was just like yay! I'm not going to root again, it was giving me too many errors; not worth it.
[Droid Incredible Q&A, Help & Troubleshooting] doug piston:
You unrooted by flashing the 2.1 RUU/PB31IMG eh?
[Droid Incredible Q&A, Help & Troubleshooting] hafler240:
I don't really remember man. Wasn't really thinking straight when i did it all. I was running 2.2 rooted it and tried unrooting it following some youtube video.
[Droid Incredible Q&A, Help & Troubleshooting] doug piston:
Well in case you fell like unrooting this one please follow this on how to unroot it correctly

http://dougpiston.com/?p=7
[Droid Incredible Q&A, Help & Troubleshooting] Jobehonda:
The ADB devices not showing the device means usually 2 things.

1. You didnt load the HTC USB Drivers, not the USB Android SDK drivers.

2. You didnt follow the process to get into recovery correctly as its complete time counting to get it to boot into recovery blindly.

Either way, sounds like you just got a new device, but it is possible to fix it.
[Droid Incredible Q&A, Help & Troubleshooting] slobs2:
drivers

where are the drivers located for the adb. are they the same ones on unrevokeds site, cuz if they are I cannot get them to work. I had unrevoked installed, thought I was properly downgrading and installed the amoled firmware so am stuck with a black screen still.
[Droid Incredible Q&A, Help & Troubleshooting] tjamscad:
complete instructions

Thanks to arache0n and Jobehonda who helped me when I thought I had bricked my phone.
[Droid Incredible Q&A, Help & Troubleshooting] Jobehonda:
Should have this loaded:

http://www.htc.com/us/support/droid-incredible-verizon/downloads/

As well as the ADB driver from unrevoked, when ADB is running should show up in device manager as unrecognized, can point it to the ADB drivers you downloaded, or the HTC drivers should overtake and auto install.
[Droid Incredible Q&A, Help & Troubleshooting] bbuchho90:
I need help.... my friend wanted me to root his Dinc for him. I went through the downgrade process in adb using this thread http://xdaforums.com/showthread.php?t=776481&page=20 and got the pb31img file to run in bootloader and everything. When I keyed it to restart after the pb31img update, it shut down and is now just a blank screen. I can hit the power button and get a quick vibrate, but nothing on the screen. Same with vol down+pwr, no screen, and it doesnt even vibrate then. the MOST I can get is the orange LED battery light, if I pull the battery. but as soon as I hit power, the light turns off. I'm trying this method on this thread, but adb fails to recognize the device, if I (adb device) it doesnt list the phone. adb shell obviously says device not found. If anyone has any ideas or suggestions, I'd greatly appreciate it! My friend needs his phone tomorrow morning

EDIT: Fixed. for some reason the first five times i pulled the battery and pressed power, the htc drivers didnt want to install. they finally did and it worked.

Thanks to the OP and his help for sharing this!
[Droid Incredible Q&A, Help & Troubleshooting] alexismc:
no adb devies

hello to everyone, my case is similar to the above but i dont have acces to adb shell probobly because s-on devices with this on mind o dont thing i have to many options, any ways any help it willl be alot of help for me.
[Droid Incredible Q&A, Help & Troubleshooting] syst3merror:
I swear I could cry right now....I'm in the same boat as others on here.

When I just hold power down, it will boot normally (no screen of course) and the bottom buttons will light up. I can press the buttons and feel the haptic feedback and I can adjust the volume and hear the "bonk" sounds as it raises and lowers....so I know the phone is working!

So, I pulled the cord, pulled the battery, plugged the battery back in, plugged the cord back in.

1) Press and hold Volume down and power at the same time for 5 secs. (it started installing adb drivers at this point...successfully) by the clock it shows that I can eject "Android 1.0"

2) I wait about 20-30 secs.

3) I push volume down button 1 time

4) I push power button down 1 time

5) At this point, I feel a quick vibration again (like you would feel during a normal power up) and the icon down by the clock notifying me that something is plugged in DISAPPEARS! Adb devices shows no devices plugged in! :(

What am I doing wrong?!?!? I just got this phone today and should have just let the dang thing be but NOOOOOO. I work on xbox 360s, wiis, computers, I rooted my wifes droid...but THIS phone screws me! :(
[Droid Incredible Q&A, Help & Troubleshooting] Embrace:
:( Oh man, I am in trouble.

I installed some stuff this morning and had it working great. I think I accidently left the PB31IMG on my SD and I installed a metamorph that force rebooted into hboot while I was in the bathroom... came back and the thing was installing! D:

I didn't want to pull as that could cause a permanent brick so I let it go, and bam! No more screen.

I can get into recovery and see the phone in ADB but when I run the RUU it does not seem to find the device. :(

Any tips?
[Droid Incredible Q&A, Help & Troubleshooting] ccbiker:
I appear to have the same situation as some others. Black screen. SLCD version.

As I follow the steps to get into recovery, things appear to go as planned (vibration going from hboot to recovery). Once there, my computer sees only an Unknown Device for which I have not been able to install a driver (HTC/android sdk/the one I used for unrevoked). Obviously, adb devices doesn't show it.

I'm not sure whether it's relevant, but when I attempt a normal boot of the phone (hold power only for 5 sec), there is a quick vibration followed by nothingness. The buttons never become active, no noises ever come from the speaker, and so on.

Also, holding vol up + pwr for 5 sec causes a triple vibration.

That's as much as I can describe, really.

A post I've seen for a similar problem to the one discussed in this thread (I believe) tries to blindly install update.zip from the SD card. I'd like to try that as well, but my issue is how many clicks I need to do. I think I can get to recovery, then wait a bit, hit vol down to highlight install update.zip from sdcard, then iirc there's a confirmation screen.

Like, with:

No

No

No

...

..

YES - install for real

no

...

Idk how many times to hit the vol down to select yes. If anyone can assist me, I'll be quite thankful.
[Droid Incredible Q&A, Help & Troubleshooting] tjamscad:
Do you have the hboot drivers installed? Search for the recovery that works with the slcd. I have found it posted before. But can't rennet where.
[Droid Incredible Q&A, Help & Troubleshooting] ccbiker:
Yes, I had them installed.

Good news is I got it working after sleeping on it and giving it another go.

I had tried this already but either messed up the timing or needed the sd card reformatted (it WAS already FAT32, but had other files on it...)

Anyway, what I did was format my sd card FAT32, put a zip that had a vzw OTA rom/radio/etc and rename it to PB32IMG.zip or whatever, pwr+vol_down for 5-6 seconds, wait 3-5 minutes (the file was around 170MB so I wanted to make sure it loaded), press vol_up to install update, waited another 5+ minutes, then hit vol_up again and it rebooted or did someting... whatever happened, HBOOT showed up on my screen and I about had a heart attack.

For some reason, it said the radio was version 1.00.xxxxx or so, so I ran the update again (another reason was I didn't know why it rebooted into the bootloader instead of starting the phone). This time, when I hit yes to reboot, it came up to the phone like it was when I bought it ten days ago (same radio, rom, kernel, everything as far as I know).

When I tried to get to recovery next, it did the black screen with white lines thing because I accidentally started unrevoked without setting it to use that custom recovery, so I just redid the unrevoked thing with that custom recovery. It's available on the unrevoked site, I believe. Can't remember where I got it, actually.

Anyway, thanks to all the posters in this thread for collectively giving me enough confidence to believe my phone wasn't bricked. :)
[Droid Incredible Q&A, Help & Troubleshooting] MaddDogg3515:
SLCD black screen of death

I have the SLCD black screen of death and i have tried everything i really need some help fixing it i know Jobehonda helped Archeaon guy with his i was hoping to get some help here please feel free to email me or someway so i can get this back up and running
[Droid Incredible Q&A, Help & Troubleshooting] doug piston:
Instead of typing it all out again, you can find your solution here
[Droid Incredible Q&A, Help & Troubleshooting] stuff2music:
Thanks to this thread and many others on xda and of course Doug, I have used A LOT of your advice since jumping into android.
[XPERIA X10 Q&A, Help & Troubleshooting] xGary:
Anyone know how to wipe the Sd card? The reason is that over time, many apps created many folders on my sd card and i want to start fresh for 2.1. So yea...
[XPERIA X10 Q&A, Help & Troubleshooting] SXUsr:
Put it in a card reader and format it, or mount it and format it.
[Vibrant Q&A, Help & Troubleshooting] burgon:
SOLVED: I had the sim in BACKWARDS! the cut corner goes toward the battery. - yes I do feel like a fool.

I was having some probs with crashing so I decided to flash back to stock, re-partition etc.

I followed the instructions from TeamWhiskey to fix a bad install.

So I ran Odin and tried to flash Froyo. It failed. I then tried to flash stock. It failed.

Turned out I was putting the .tar file in the Phone field not the PDA. :eek:

By this time the phone was totally dead, I couldn't get it to respond in any way. Finally I found Eugene's solution of holding the volume button when inserting the battery while connected to USB. That got me in to download mode.

Then I flashed stock with a repartition. That got the phone going, but with a warning: Emergency calls only. Please insert SIM card and restart. I tested my wife's sim card on - same warning.

Then I flashed JI6 - Same problem

Then I flashed through Odin the JI6 modem in the phone field of Odin. I really thought that would work - It didn't.

So any ideas on how to get fix: Emergency calls only. Please insert SIM card and restart

Thanks!
[Vibrant Q&A, Help & Troubleshooting] burgon:
Ok so I just went through all the steps of: xdaforums.com/showthread.php?t=803492 successfully.

But it still doesn't recognize the sim card.

Hasn't someone else run into this?

Thanks
[Vibrant Q&A, Help & Troubleshooting] Sonelone:
Lol. I did the same thing and reading this thread actually helped me.
[Vibrant Q&A, Help & Troubleshooting] beaver2233:
wow thank you so much... :\ i did the exact same thing ...hahahah
[Desire HD General] cyberpedz:
Well I finally decided to be brave and ordered the DHD I have spent weeks swating up on it and all though there are reports of certain issues there pretty much is with most new phones so hey. Anyway I hope I don't regret it but going from a htc magic I would say anything is better.
[Desire HD General] mancuk29:
You won't I'm a real mobile phone techy and the hdh runs rings around all other handsets. Only issue is have is the speaker is too low
[Desire HD General] cyberpedz:
Ye I am the same love mobile phones and android like I say coming from a magic I would imagine the sound has got to be a bit better at least even if its on par that would be fine as that's what I am used to.

http://www.luvdroid.com
[Desire HD General] apprentice:
Totally agree. After 3 weeks of use I can say I honestly made the right choice with this phone and I too am a real phone junkie!

The speaker is the only disappointment for me also. But I love playing my music through my TV/home theatre system via DNLA !

So yeah, you made the right decision.
[Desire HD General] cyberpedz:
Great now I just have the long wait for it, vody has ordered as non in stock so god knows when I will get it. I really hope it is soon though. I hope I get a decent one without the case problems etc but we will see.

http://www.luvdroid.com

Sent from my HTC Magic
[Desire HD General] dr.m0x:
Congratulations on your decision to buy one of the finest handsets available today. :)

Apart from the great hardware spec, and high build quality, the new version of sense is hands down the most user friendly interface I have every experienced. Sense was good before but now it is even better. It really feels like htc have worked very hard to make it live up to it's name.

I have had one for exactly three hours now and enjoying it immensely. I am also enjoying the buzz of being 1337 and exclusive. These phones are normally impossible to get here in New Zealand right now and I hold one of the few in this country in my hand.

I'm going to enjoy the feeling of exclusivity while it lasts. This is the kind of phone android has been needing to take the iphone on head to head against "normal" consumers.
[Desire HD General] combat goofwing:
couldn't agree more, im new to android and i love it and the DHD ,yes there are issues(prox sensor/ youtube crash etc), but i know for a fact that if you went on the samsung page or go on the nexus2 page when its out they all will have a few issues that needed sorted

for me i love sense the fact you can have whatever widgets or apps on whatever page in what ever lay out you want is great, i got it mainly for

web browsing excellent

email and text excellent

games excellent

video play back , still trying to find a convertor that doesn't give me audio out of sync issues but ill solve this one no bother like most devices, file formats can be a nightmare

i came from a HTC TP2 which had the best keyboard of any phone but was let down as it was underpowered and had a resistive screen
[Desire HD General] sanju007:
Congrats

Only the speaker sound it very bad i hope HTC will set the volume higher with a update i hope so

And great phone !!
[Desire HD General] FutureClimax:
I have got mine from yesterday. Uh, time to learn bit more. After 3 years with iPhone in the pocket it will take some time to use to it.

But I am very happy with my choice.

Just checked iPhone and DHD speaker and DHD is far louder than 3GS. Maybe because it has much less bass.
[Desire HD General] cyberpedz:
I now have mine and loving every minute of it. Its a brilliant phone I don't seem to have all the troubles that most report although I have not been able to replicate lag issue I put USB debug on right away. I do think the covers are pretty shocking and they do seem to not be a perfect fit bit I have a silicone case anyway so does not bother me love this phone and can't put it down!
[Desire HD General] krico:
Yeah i should be right. I bought it on eBay and they said that there were 16 in stock so i'll just have to wait.
[Droid X General] bmb2n:
For those of you that felt in love with the Blur Alarm and looking for a way to add it back. I have figured out the missing files beside the apk that goes in the system\app. This has been tested with sucess for Fission ROM v2.0.1.

Adding Blur alarm

system\app\BlurAlarmClock.apk

framework\blur-res.apk

framework\com.motorola.blur.library.utilities.jar

Hope it help.
[Droid X General] braway:
nice,

I prefer the blur alarm over the normal one.

but here is my problem, the dock is DeskClock.apk, which is also the Clock and the alarms,

when I replace it with the Dock.apk, then the dock won't start up,

did you try to do that?

I'm getting the following exception, and have no clue on how to fix that Oo

11-04 00:39:22.031 2063 2063 E AndroidRuntime: java.lang.RuntimeException: Unable to start activity ComponentInfo{com.motorola.dlauncher/com.motorola.dlauncher.DLauncher}: java.lang.SecurityException: Neither user 10048 nor current process has android.permission.DEVICE_POWER.
[Droid X General] bmb2n:
What ROM are you using? I renamed the original DeskClock.apk to DeskClock.bak since I don't have a docking station. May be it has something to do with the dlauncher. I also deleted the original launcher2 and replaced it with launcherpro.apk.
[Droid X General] braway:
Fission 2.0.2

I basically did the same with the DeskClock.apk

but added the Dock.apk from the clean verizon rom (which is basically the "stock" droid2), I guess I'm simply missing something

btw, com.motorola.dlauncher is Dock.apk

I guess something is still missing which would set the missing permission oO
[Droid X General] braway:
got it to work...

if someone cares:

I had to manually modify the /data/system/packages.xml

it should contain something like this:

<package name="com.motorola.dlauncher" codePath="/system/app/Dock.apk" flags="1" ts="1288859615000" version="8" userId="10057">
<sigs count="1">
<cert index="1" />
</sigs>
</package>

userId and ts are probably different

change the cert index to 0 !

reboot (right after it, for example with adb reboot)

after reboot, check that your change is still in this file (should be)

put your phone into the docking station, and the blur dock should start

yay :)
[Droid X General] StDevious:
lol, this default blur alarm app is awesome and best I have seen. I was so surprised at what it wanted me to do when I first woke up to it , lol
[Droid X General] rkrasny:
I am not using fission and I am using Rubix 1.6.

I can only find the bluralarm.apk file and I can't find

framework\blur-res.apk

framework\com.motorola.blur.library.utilities.jar

Do i have to nandroid back to a blurry room to pick these up or are they available somewhere else?

Thanks
[Droid X General] braway:
get the vzw clean rom (or so) from droid2files.com (http://droid2files.com/roms/VZW_2.4.5_Clean_ROM.zip)

everything should be in it...
[Droid X General] rkrasny:
Perfect; thanks much.
[Droid X General] Bakefield2:
Question?

How do I add this to my phone and make it work? Do I need to use ADB and move it to the phone or what? I really liked the blur alarm a lot and would like to get that back if I can. Thanks for any help in advance.