Related
Dash Bricked Need Help!!!
I tried using a the google mail java app on my tmobile dash. It froze up on me, and when i turned it back on it just stays at the "tmobile" splash screen. I have tried using the soft key and power button reset but it doesnt work. What's weird is that it wont power down unless I take the battery out. It powers on, shows the tmobile splash screen, then freezes. Is there any other way to reset it or is it totally bricked? I bought it new off craiglslist so tmobile wont replace it for me cause I'm using it unlocked on cingular.
The power key reset should work. Could you be doing it wrong?
I was facing the same problem but after doing hard reset (Power Off, Press 2 soft key, Press Power On Key for 2 seconds then release soft key) worked fine. Seems timing is very important, try and try.
Help, i think i bricked my phone!
I was installing the WM6 Update released on this website, everything was going fine when i saw that my lil' cousin' disconnected my phone while i moved away from the PC (he pulled the phone altogether).
Now my phone is stuck in the bootloader mode screen (tricolor, blue green/red i think). It detects USB (it says USB on the bottom of the screen whenever i connect it). Is there a fix for it for the DASH? I read the wiki about a fix for a similar problem for the Hermes, but that didnt work for mine.
Can anybody help me please?!
Mine's a T-Mobile Dash with the stock rom from T-Mobile.
remove and reinsert the battery
if that does not work paperweight thats how i ruined my cingular 2125
Oh god, all this brickage makes me too scared to update. Can anyone direct me to where I can find how to backup my current setup so that I could reload it if something went wrong or I didnt like the Beta WM6?
MrLuna said:
I was installing the WM6 Update released on this website, everything was going fine when i saw that my lil' cousin' disconnected my phone while i moved away from the PC (he pulled the phone altogether).
Now my phone is stuck in the bootloader mode screen (tricolor, blue green/red i think). It detects USB (it says USB on the bottom of the screen whenever i connect it). Is there a fix for it for the DASH? I read the wiki about a fix for a similar problem for the Hermes, but that didnt work for mine.
Can anybody help me please?!
Mine's a T-Mobile Dash with the stock rom from T-Mobile.
Click to expand...
Click to collapse
Just try the flash again and it should start working. I had my computer bluescreen while I was flashing an SDA and got to the tricolor screen. It flashed fine after trying again. If its not detecting right. Pop out the battery on the phone and restart your computer and attempt the flash again. Shouldn't be a problem. Definitely scary though. I don't think you can brick these unless you mess up the bootloader perhaps...
ANyone know How do I manually put my Dash in Bootloader mode?
deemota said:
ANyone know How do I manually put my Dash in Bootloader mode?
Click to expand...
Click to collapse
power off, hold the camera key beside Space Tab for about 3 sec, and then press power key while still pressing the cam key.
You are a GOD. Thanks.
you have no idea why it gives you warnings not to run any programs or disconnect while the ruu is updating you think they just give you warning messages because the htc techs have nothing better to do????????
Blackforge said:
Just try the flash again and it should start working. I had my computer bluescreen while I was flashing an SDA and got to the tricolor screen. It flashed fine after trying again. If its not detecting right. Pop out the battery on the phone and restart your computer and attempt the flash again. Shouldn't be a problem. Definitely scary though. I don't think you can brick these unless you mess up the bootloader perhaps...
Click to expand...
Click to collapse
Well, tried that, but the computer doesnt detect the phone, meaning it wont connect to ActiveSync. Since it won't connect to activesync the program wont install it on the phone since it can't find it.
Good thing i have insurance. Bad thing i'm trying again as soon as i get the replacement
Are there any alternatives though? Maybe i can fix it before i send this one back.
restart your computer again..
This is from HTC Q&A
Q: I use RUU to update and failed, and my device always boots in three-color mode and cannot enter CE OS anymore, what should I do now?
A: If the update process has failed, you will see that your device will always boot in three-color mode. It's normal and can be recovered. Please follow the instructions below to reset your device and to establish a connection with the computer.
1. Disconnect your Mobile Device from the USB cradle/cable.
2. Reset your Mobile Device.
3. Reconnect your Mobile Device to the USB cradle/cable.
4. Check that the communication cradle/cable is connected properly.
5. Return to the ROM Update Utility.
Note: You should ignore the ActiveSync connection.
WM6: Endless Bootup Loop
A few days before the official TMobile WM6 update came out I download the widely posted leaked version. The Dash started acting up during bootup one day, so I reflashed with the TMobile WM6. Now the same thing just started, and the device can't be used.
When powered on it does the quick vibrate, TMobile screen, Windows Mobile Screen, TMobile screen again, with power up 'jingle', then it just shuts off and starts the bootup sequence again. Endlessly.
Have tried removing the battery, etc. Has anyone else run into this? Any ideas of a keypress combo or something I can press during bootup that might jump-start it??? Thanks!
Take out the microSD card and the unit should boot properly. Mine was fixed with a new SIM card, but a new device may also be needed.
Wound up doing a hard reset. I had tried taking out the microSD card, then it would just hang on the TMobile screen. I also tried rebooting without the SIM card in, then it would do the loop thing. I'm thinking it must be related to software loading during the boot, and the only program I have on the microSD card that loads during bootup is FizzWeather.
rabilancia said:
Take out the microSD card and the unit should boot properly. Mine was fixed with a new SIM card, but a new device may also be needed.
Click to expand...
Click to collapse
I think this may at times be related to an auto-install file being present.
If you hold down the "end" key during boot-up it seems to prevent the cycling.
Thanks, will keep that in mind if it happens again. By 'end' key, do you mean the red phone icon key that you hang up on a call with?
robertgbl said:
I think this may at times be related to an auto-install file being present.
If you hold down the "end" key during boot-up it seems to prevent the cycling.
Click to expand...
Click to collapse
dear friends ,
my phone has shut down and only when you take out the battery and put it back in after which you press any button on the phone it comes on and shows the htc logo after which it displays the following
ipl 3.07.001
spl 3.07.000
gsm 02.69.90
os 3.7.0.0
remains on for about 5-6 seconds and goes off
have tried to enter the boot loader mode by pressing the record button and reset button but it continous to behave in the same manner as mentioned above .
also when i try to charge the phone it shows only a red light
hoping someone can offer a solution to my problem
thanks and regards
I'd also be interested to know about this as my MDA Compact III has just done exactly the same thing.
have you guys tried flashing...that could kill it if not done propertly....but i doubt,the led is on,splash screen appears...info appears...what were last few things you did
according to spl os and ipl you flashed artemis touch 4.02 if i'm not wrong...or maybe tom's v5...try reflashing the same rom or just try a hardreset
Interesting...I've recently flashed the same ROM (v4.02)
I am certain I followed all the instructions about USPL and its been working fine for about a week...then it just went blank!
Will try re-flashing and/or a hard reset.
Thanks for the advice.
mrd5477 said:
Interesting...I've recently flashed the same ROM (v4.02)
I am certain I followed all the instructions about USPL and its been working fine for about a week...then it just went blank!
Will try re-flashing and/or a hard reset.
Thanks for the advice.
Click to expand...
Click to collapse
well...if it worked i'm sure you installed some app or deleted some files...so the system doesn't work...
if so hr will help
dear friends,
took the device in for repairs the fault was with the power circuit board which had to be changed as`informed to me by the technician
i now remember a few months ago the power button stopped working and a few days before the phone went bad it would work intermittently but there was no spring in the button hence it would have to be pressed quite hard for it to work i feel that this loose power button caused the power circuit to fail also my sd card was spoilt and the same had to be replaced
cast me appx in usd 30 for the repairs
thanks
I recently tried to unlock my uncle's Diamond. I used Hard SPL1.4 from this site, and it finished that successfully. After restarting, I went through the whole screen calibration and so on, then I went to the kitchen to get some food. By the time I got back, the Diamond wouldn't start at all. I haven't tried a hard reset, but I don't think that would do me any good since the phone doesn't start up at all. Is there anything I can do? Or will I have to tell my uncle I ****ed his phone..
Just a quick detail, I did notice that after it started up again, the area next to the SIM card slot heated up quite a bit. I don't know if that's related, but I figured I'd tell you anyway.
The Hard SPL of choice is the 1.93. Any who, try and place the device into bootloader mode (tri-colour screen).
Hard Reset Your Device:
• Soft reset button and hold the vol. down + Circle button until u see the grey screen. REMEMBER THIS WILL ERASE EVERYTHING SAVED ON THIS ROM (i.e. contacts, calender, etc.)
Bootlaoder Mode:
• Soft reset and hold the volume down until u see the tri screen
Do you see the Hard spl 1.40? if yes, then just a hard reset and see what happens
IF none of the above worked, take out the BATTERY for a bit and try the above options all over again.
Hi, thought i would add to this thread.
Mine also did this, it worked fine for a week with Windows Revolution 6.5 rom then it randomly turned off and refuses to turn on.
Bootloader mode / hard / soft reset none work.
Hey guys, I'm normally silent in these forums 'cause I've never had a brick, just by reading correctly. This problem I'm having isn't a flashing brick! What happened is the following:
I know that the DHD in combi with my BT car radio is somewhat difficult (because of bad HTC coding). It seems that when I have my facebook friends in my contacts that the DHD starts slowing down and eventually hang when connected to the radio, because my radio tries to get every contact including it's info. Normally I do not sync my FB contacts with my DHD however I must have mistakingly done this.
Today I connected to my car radio and after getting out of the car my DHD showed that it was still connected (a sign that my DHD had the hang problem again). I turned of BT (took a hell of a time) and contiued on. When I came back I tried connecting the DHD again, however when I pushed the BT checkmark in settings it showed BT on, but no BT connection came up. So I went into BT settings only to find that BT wasn't turned on, then in the BT settings I checked turn BT on.
At that moment my DHD hang instantly, no inputs were registered at all. I waited a few minutes but nothing changed (I could still see the screen frozen at turning on BT). So I took out the battery and reinserted it, but when a pushed the power, the phone vibrated thrice and then did not boot, but only showed a flashing amber led.
I have rooted, S-offed and did the whole shebang to flash my DHD once. This was a long time ago and I haven't had any problems, all was OK. So at first I tried to search the forums, what might have happened. No post seems to be the same as my problem, because everyone is having these problems after an incorrect flash (my flash was correct, cause I've been using the ROM for more than 4 months!). Still I tried the solutions given in these posts (enter fastboot and flash again).
But it seems my DHD won't go into fastboot. When I hold VOLdown&power my DHD vibrates 5 times and shows a steady green led. So I thought maybe flashing a new ROM resolves the problem. If I cycle the battery and then connect is to my computer, my DHD goes into Clockwork recovery. From there I flased a new ROM to my DHD (update.zip method), but to no avail. I've factoryresetted, cleared al data, wiped battery stats, all to no avail...
As of this moment I'm at the end of my knowledge, I've done everything I know could have helped, but nothing did. Therefore I'm asking you, the Oracle of XDA (users), please does anyone have any clue what happened to my DHD and if so, how do I resolve the problem!
Thanks in advance for every little motivation/obligation you show be giving me your insights!
Info:
ROM: Android Revolution HD 2.0.9
CWM Recovery: 2.5.1.3
I've allready wiped battery stats as per this topic!
Additional thoughts: Might a hardware fault be the reason? Because it happened after some problems with BT, and also because I'm still able to correctly flash new ROMS with CWM though the problem remains?
Allright, so nobody know an answer I'm guessing... I've started the replacement process with my insurance company. However I'd still would like it if someone would know what the heck I did wrong...
Have you tried flashing a new radio, as that is what controls the hardware?
All a new ROM will do is update the RIL, not the radio.
http://forum.xda-developers.com/showthread.php?t=896597
Sent from my Desire HD using Tapatalk
It does more than likely seem like a hardware fault so it cant really be solved with software changes. Although I still would have tried to flash an RUU which updates basically everything on the phone to bare stock.
Use an RUU via your pc (v2.36 or lower so you can root it again) to restore to an out of the box state.
Allright guys, thanks for your ideas! I'm however experiencing problems trying your idea's. fFashing a radio or flashing a stock rom are not possible, because I need a connection with my computer. This connection is not possible, if I start the phone normally (or with vol down) I get the amber flashing light or the green steady light. Both do not connect to my pc, I get some device "Qualcomm CDMA Technologies MSN" for which windows can't find any drivers. When I let the DHD go into QWM recovery, the RUU won't find the DHD.
So I've tried extracting the RUU rom en putting this on the SDCARD of the DHD, but when I try to install it via CWM Recovery it says that it's an invalid file...
I actually bricked mine on purpose, and the thing that happened when it got bricked was that no lights and no life at all we're visible on the phone...
Atleast you get shakes and lights, thats a good sign!
Sadly i don't know what has to be done to restore it, but maybe Jkoljo does, PM him about your problem, if you get an assistance and some solving, write back here for your solution for others to use in the future!
They hang out in the Android Revolution HD IRC Channel, thats where i would go tbh.. Live support ftw!
Edit: While reading your above statement, it seems your drivers may be faulty in windows, redownload HTC Sync from htc.com, install, reboot, and try again.
The "Qualcomm CDMA ..." notification on the PC is a sign for the Qualcomm service mode. Also the 3 vibrates and the orange light is an indicator for that. You can enter this mode by pressing vol+ and power your device.
Stupid question, but is it possible that your vol+ button is stuck or something like that?
And you said you're able to enter CWM? how? I'm asking because you said you can't enter the bootloader.
I'll do some research when i get home today.
Meanwhile Try if ADB/Fastboot sees your phone
Edit: just checked my theory of the broken vol+ button: i held down my vol + button, took my battery out, reinserted it and powered up my phone. Result: 3 vibrates and a flashing orange light.
Then i did the same, but held down vol - ( vol+ still pressed). Result: your second phenomenon: a few vibrates and the green light stays on.
So I think this proves my theory because this is exactly what you described
I suggest you to play a bit with the vol+ button. Maybe the button will work again then
Sent from my Desire HD using Tapatalk
Well, I'm gonna fire up IRC then and try get some help. It's indeed not bricked as far as I'm guessing cause I do indeed have lights and I'm able to boot into CWM!
Flussen said:
The "Qualcomm CDMA ..." notification on the PC is a sign for the Qualcomm service mode. Also the 3 vibrates and the orange light is an indicator for that. You can enter this mode by pressing vol+ and power your device.
Stupid question, but is it possible that your vol+ button is stuck or something like that?
And you said you're able to enter CWM? how? I'm asking because you said you can't enter the bootloader.
I'll do some research when i get home today.
Meanwhile Try if ADB/Fastboot sees your phone
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
Right I'm guessing this is my problem! Just two days prior to resetting I started having problems with my VOL+ button (wouldn't work, only VOL- worked). So I'm guessing my hardware VOL+ button is broken and stuck to pressed...?
To answer your question about CWM: When I take out the battery so the phone is powered down, then reinsert the battery, connect the phone to the adapter or my computer (without pressing the power button), the phone boots into CWM after about 1 minute!
So after consolidating all the answers I'm guessing this is my problem: Hardware VOL+ is constantly pressed, therefore the phone boots consequently into Qualcomm service mode. Everything seems to be OK (flashing able to CWM), though just this little VOL+ problem puts my phone into an unusable brick...
The problem is that I'm not able to repair this myself (when I would try this, I'm guessing I'll break the seals therefore my insurance won't pay)... Anyone an idea how to circumvent the VOL+ button problem, without opening up my phone?
bdacier said:
Well, I'm gonna fire up IRC then and try get some help. It's indeed not bricked as far as I'm guessing cause I do indeed have lights and I'm able to boot into CWM!
Right I'm guessing this is my problem! Just two days prior to resetting I started having problems with my VOL+ button (wouldn't work, only VOL- worked). So I'm guessing my hardware VOL+ button is broken and stuck to pressed...?
To answer your question about CWM: When I take out the battery so the phone is powered down, then reinsert the battery, connect the phone to the adapter or my computer (without pressing the power button), the phone boots into CWM after about 1 minute!
So after consolidating all the answers I'm guessing this is my problem: Hardware VOL+ is constantly pressed, therefore the phone boots consequently into Qualcomm service mode. Everything seems to be OK (flashing able to CWM), though just this little VOL+ problem puts my phone into an unusable brick...
The problem is that I'm not able to repair this myself (when I would try this, I'm guessing I'll break the seals therefore my insurance won't pay)... Anyone an idea how to circumvent the VOL+ button problem, without opening up my phone?
Click to expand...
Click to collapse
Do you have needles at home? The ones you use when you repair cloth.. Try using one very carefully behind the volume +, you could also take a bit of A4 Paper, cut out some of it and make it fit between the gap of the Volume button, and try getting dirt out of there.
Allright, I've tried cleaning the VOL+ key but it still won't work. As a matter of fact I can feel a little "click" when pressing the VOL+ key, so I'm guessing the mechanical part of the key is working correctly. However when in CWM I can only use the VOL- key to switch thru the options, VOL+ is not registered by the phone. Therefore my assumption is that the there's a problem on the PCB with the VOL+ key, ergo a hardware fault... Insurance has been called and I'm up for a switch, now let's hope the insurance doesn't figure out I've rooted and installed another ROM than stock!
At least I wan't to thank all of you who've tried to help me! My ego has been saved, knowing it's indeed a hardware fault .
Cant you use adb within cwm to adb reboot bootloader?
Sent from my Desire HD using Tapatalk
bdacier said:
Allright, I've tried cleaning the VOL+ key but it still won't work. As a matter of fact I can feel a little "click" when pressing the VOL+ key, so I'm guessing the mechanical part of the key is working correctly. However when in CWM I can only use the VOL- key to switch thru the options, VOL+ is not registered by the phone. Therefore my assumption is that the there's a problem on the PCB with the VOL+ key, ergo a hardware fault... Insurance has been called and I'm up for a switch, now let's hope the insurance doesn't figure out I've rooted and installed another ROM than stock!
At least I wan't to thank all of you who've tried to help me! My ego has been saved, knowing it's indeed a hardware fault .
Click to expand...
Click to collapse
I've got the exact same problem! I don't have insurance on it though. And, im a day late for warranty.
What am i supposed to do? Any suggestions? Will htc deny my request to fix it coz it had a custom firmware?
Any help of any sort is appreciated.
I had exactly the same problem, and I'm sorry to say that I had to have it repaired. My button would also "click", but not register.
Maybe if you are buy a new power button from eBay?
Realising this is an old thread, but still:
I was just experiencing the same problem after I did a reboot to let one of my friends borrow my DHD to turn off the PIN code check on his SIM.
It started with the blinking lights (black screen), then I pulled the battery and found that my DHD was only accessible through ADB in recovery mode.
Did a couple of "ADB reboot" without any success, then tried using "ADB reboot recovery", which seemed to work (still black screen though), and then I did a "ADB reboot".
Back to normal!
hi , i had this issue too , its bcz of the moisture ur cell phone has absorb and as HTC desire HD very sensitive with its volume rocker area , the first thing that will be affected with moisture is ur volumer rocker circuit , try making it dry with a hair dryer blower or place ur phone in a rice sack for a day .
i am sure it will work .
Hi there.
My partner recently tried to update his HTC one m8 Telstra phone. The screen got stuck on "android is upgrading" starting apps. With a little blue loading circle going round and round. Eventually his phone went flat and now the phone will not load past the HTC one powered by android screen. Have tried pressing volume - and power button to go into boot loader and the same thing happens. If I select recovery a little red triangle appears. Have wiped cache. Still no change. If I do factory reset, it goes through the process of "optimizing apps" and then gets stuck on android is upgrading screen etc.
My partner is even more technologically ignorant that I am so he has never done any back ups or anything .
SD card slot does not work (as he ran over his phone last year) however phone has functioned normally for the most part, up until he attempted to update. Please help if possible.
If it is not hardware problem .. only possible to fix it if the bootloader is unlocked.
Why ? because there is no Telstra RUU available, you can only fix it with a nandroid backup
To get to bootloader, press & hold both power + volume up buttons until the screen turns black, release both buttons and press & hold volume down button only to get to hboot. Then select "fastboot" on the menu to get to bootloader screen.
Can you tell what's written on bootloader ? Is it LOCKED, UNLOCKED or RELOCKED ?
Thank you for replying.
Ok so firstly, how do I tell if it's a hardware problem.?
Secondly, although the phone displays a Telstra icon upon startup, my Optus SIM card, well any carrier SIM card really, works in the phone, therefore would it be possible to use another RUU? (What on earth is an RUU?) And nandroid??? Please explain what all these terms mean, if you don't mind of course.
Because his phone screen is damaged from running over it last year, it is hard to see all the information. I'm fairly certain it is still S-on though. Is there any way I could view the boot loader details on a laptop?
I have tried the fastboot option and it still returns to HTC one screen.
How do I get a nandroid back up? Is the phone at all fixable in your opinion? I don't believe it's hard bricked from what I've managed to learn so far, though I could be wrong, as it still goes through the cycle of "optimizing apps" and attempts to start apps after selecting factory reset in boot loader.
I apologise for my lack of knowledge and ignorance on this matter and I appreciate all your help
A lot of your questions are answered here : http://forum.xda-developers.com/showthread.php?p=52484527
I don't say it is really hardware problem, I say if it is not then it is fixable by restoring correct software.
That's why it is important to get to bootloader because most info are available there.
I want you to give the details of what's written there before I can guide you further.
Those details will tell whether that's a Telstra device, whether the device was rooted which may explain the problem and so on.
If you can't get the right button combination works as I mentioned above, then you need to switch it off (maybe let the battery runs out), charge it for a few hours. Take out from charger then press & hold volume down (read again above I mentioned volume up & volume down because which volume button is important) then connect to PC or charger (this comes after you press & hold volume down button not before)
No bootloader .. not possible to fix (unless it is send to HTC centre)
I am able to get to the boot loader screen (I googled so much before posting on here) but most of the information is blacked out due to the screen being wrecked. I will try and gather as much information from what I can see and post here when I get home and I will also try and upload a picture.
Do you have any advice on how I would determine if the issue is due to hardware?
I will provide further information shortly and once again I'm am sincerely grateful for all your help.
Not easy to know it's a hardware issue when it is still can boot-up but bootloop.
hard brick means no response at all (still sometime it is due to no battery)
Ok so here a few photos of the boot loader screen, the fast boot screen and the recovery mode screen. Please bear in mind a lot of (possibly vital) information is not viewable due to screen damage that happened last year.
The most important detail that I need to know is not visible there.
Really need to know whether the bootloader is LOCKED, UNLOCKED or RELOCKED because that portion is blank out with the damage screen.
What you can try ... while on fastboot/bootloader screen (your pic #1), try to install TWRP recovery
Download TWRP 2.8.7.0 from here : https://dl.twrp.me/m8/
Make sure your PC has the required drivers, ADB/fastboot - if not sure, install these :
http://forum.xda-developers.com/showpost.php?p=64926362&postcount=4
After connecting the device to PC, install the TWRP recovery with command :
fastboot flash recovery twrp-2.8.7.0-m8.img
advise the outcome, if it successful then it is easier to fix the problem.
Ok thanks. I'll download those things and then try that. From what I've learnt so far, I'm pretty certain the boot loader is locked. He got the phone brand new and has done nothing further than change his ringtone, screen display and lock screen. He's worse at technological stuff than I am lol.