Many ppl have problems with "black" screens that "stop" working.
my HD: Stock rom, radio, europe location, non modified, non damages.
Screen is just black, but phone,sound and touch panel! work
first time when screen gone black i make hardreset by (unplug touchpen)press vol-up + vol-down + power. after HR screen work again !.
7-14 days ago screen gone black again ... HR dont help, unload&load battery dont help, so i use product Warranty, and now w8 for back HD & summary.
If you have the same problem just post here.
I have the same problem and sent it back for servicing.
Apparently needs to change the whole board.
Looks like there is a defective batch of HD. Reported also by another user.
I have the same problem, sometimes screen goes black about 5-6 times for day,sometimes 2-3 day is ok! im sending back to store
Mine is doing the exact same thing, touch still works fine but screen shows nothing on it. Lucky i had MyMobiler installed so i can see the screen through activesync on my PC
I have this problem too. This is becoming quite a common problem with HD.
I sent mine back for repair where they have to replaced the mainboard.
Definitely a hardware problem. Hope you have warranty.
How will warranty go with a custom (Dutty's) ROM installed?
Was installed using USPL, has never had HardSPL installed on there
Pugsley_21 said:
How will warranty go with a custom (Dutty's) ROM installed?
Was installed using USPL, has never had HardSPL installed on there
Click to expand...
Click to collapse
You won't have warranty with a custom ROM. Did you backup your stock ROM?
Stock ROM can be downloaded from the HTC site, but how to install it without a working screen?
Pugsley_21 said:
Stock ROM can be downloaded from the HTC site, but how to install it without a working screen?
Click to expand...
Click to collapse
I had this problem with black screen though I could still feel vibrations when clicking soft keys etc, so I knew phone was on.
What I did:
Removed battery overnight
Inserted battery and turned on device
Device worked normally again.
If this doesn't work then you definately have a faulty motherboard.
This also means you would be unable to flash custom rom on device. This could void your warranty. However I have heard of people getting phones fixed under warranty with same problem due to HTC not being able to check wther or not you had changed rom beforehand
Hmmm, well currently my phone is back where i bought it, they wanted all packaging so they haven't sent it off yet. I'll get it back tomorrow and try removing the battery overnight, as mine sounds just like yours in that it still turns on but with no screen
According to the HTC site the stock ROM should install as long as activesync can see the phone. So there might be hope in flashing a stock ROM back on before warranty
Pugsley_21 said:
According to the HTC site the stock ROM should install as long as activesync can see the phone. So there might be hope in flashing a stock ROM back on before warranty
Click to expand...
Click to collapse
If your phone turns on and still connects to pc, then yes its possible. Try it and see what happens. You should still be presented with standard flash pop up screen on pc as well as % flashed etc which will change to flashing finished so you know you have completed flash process.
I've found out that MyMobiler will automatically install itself onto the phone when it is plugged into the PC, so there's still hope to see the screen after a reflash. Just need to get my phone back
Went to the shop and managed to flash the stock ROM back onto the phone, after downloading it from the HTC website. Now it's going back (hopefully) to HTC, or possibly Telstra. I'm hoping they send me a new one, as they wanted all of the accessories that came with it, box etc
Yep, same problem here. And mine is also a Telstra T8285. Maybe the bad batch is mostly in those?
Anyway, I have managed to re-load the stock rom with no screen. It's quite easy actually. Just make sure ActiveSync sees the phone, and you're good to go. No need to have to see the screen of the phone.
I'm in the US and was routed to HTC's support here in the US. Of course when I told them the model I have, they said they don't have the parts to repair it here in the US, so I'd have to send it overseas. He said they will contact me from HTC over there within 2 WEEKS. What? So I sit here and wait... blah.
stpete111 said:
Yep, same problem here. And mine is also a Telstra T8285. Maybe the bad batch is mostly in those?
Click to expand...
Click to collapse
btw, mine is also a Telstra T8285 so it definitely seems to be a problematic batch for Australia. Mine took three weeks to return and they replaced the mainboard. So far so good.
Hi,
I have exactly the same issue. The screen is black, but the phone does operate. I can connect it to my PC and even "see" the screen using EveryWAN remote.
The problem is, I have the Energy 6.5 ROM and Hard SPL 1.56 installed, and I cannot flash it back to the stock ROM and SPL, so that I can send it back under warranty.
I have tried 2 ways:
1. Putting it into Bootloader by pressing Vol down and ON - but it is impossible to tell if it actually goes into it because the screen is black, and when I try and run the ROM update utility, it cannot connect (error 260).
It seems like I cannot actually get it into the bootloader. I have tried lots of times...
2. Running the installer from when the phone is on and connected to the PC by activesync. In this method, the update utility gets as far as starting the progress bar, but then the phone seems to disconnect from the PC and again I get connection error 260.
This is really frustrating, any ideas would be greatly appreciated...
stutjones said:
Hi,
I have exactly the same issue. The screen is black, but the phone does operate. I can connect it to my PC and even "see" the screen using EveryWAN remote.
The problem is, I have the Energy 6.5 ROM and Hard SPL 1.56 installed, and I cannot flash it back to the stock ROM and SPL, so that I can send it back under warranty.
I have tried 2 ways:
1. Putting it into Bootloader by pressing Vol down and ON - but it is impossible to tell if it actually goes into it because the screen is black, and when I try and run the ROM update utility, it cannot connect (error 260).
It seems like I cannot actually get it into the bootloader. I have tried lots of times...
2. Running the installer from when the phone is on and connected to the PC by activesync. In this method, the update utility gets as far as starting the progress bar, but then the phone seems to disconnect from the PC and again I get connection error 260.
This is really frustrating, any ideas would be greatly appreciated...
Click to expand...
Click to collapse
What I'd try is running USPL before running RUU
Quote from wiki
ERROR [260] : CONNECTION
This error occurs when the RUU cannot make a connection to the device right before flashing. This typically happens when you try to flash a new SPL to your device. Use Soft-SPL before attempting the RUU again.
Click to expand...
Click to collapse
Thanks for the help Fallen Sparten.
Unfortunately it does not work.
The USPL also cannot find a connection. I think it is because I cannot actually put the phone into the bootloader - It is impossible to tell because the screen is blank. What I can say, is that when I press both the volume down and power key, nothing seems to happen. There is no connection sound from my computer and the RUU does not detect the phone.
I also get the same error if I try and update the phone from an activesync connection. i.e. when the phone is operating normally - I can tell it is operating normally because I can view the files with activesync.
Please any more ideas?
This happened to me as well. Was there some kind of software update that HTC pushed out that affected a few phones?
I see about 10-15 people on here that got hit with the same thing at the same time.
well I've had this issue as well, I have flashed back to stock rom (blind as activesync could see it tho I couldnt so no idea whats gone on)
When I called customer service they barely batted an eye and ahve arranged a replacement to be shippped to me tomorrow.
Be interesting to see what they say (if anything when they get mind back)
Related
Not quite sure what the issue is with this one. Back in the beginning of the year my XDA II fell from waist height when the carry case snap popped open (notebook bag brush across the front catching on the flap). The only noticeable problem after that was that the power button no longer works, so I have to power it on by pressing the phone or address book buttons etc.
About a month and a half after that incident the phone suddenly just stopped getting signal. I was using the standard shipping firmware with a few apps. Soft reset, hard reset both failed to fix the issue, the phone simply will not pick up the network. Interestingly enough if I play with the phone settings and go through the process of manually selecting a network the phone WILL pick up available networks in the area (this kills my idea that the GSM radio failed altogether). For now I've had to switch back to a junk phone as I've been unable to figure this one out. Anyone have any ideas on this one? I'm using T-Mobile for a service provider and I'm based out of California.
Also, does anyone know of a place that can do diagnostic/repairs here in the U.S.? So far my searches have come up empty.
Thanks in advance.
Give this a try:
Reflash the phone with any version of ROM and it should start working fine again. I think the problem is that you're radio firmware somehow got corrupt.
Ok, guess I'll have to give it a try. I've been avoiding trying the slightly riskier stuff as I got this thing via an independant third party, so warranty/support are iffy.
Is there a general release ROM that I should be looking for (using T-Mo in U.S.)? Or should I look to cooking my own (which I'd rather not)?
You can try upgrading the ROM with the same branded one. That shouldn't void the warranty.
I.e. If you've got an O2 device, get the new O2 ROM
Reflashing
I have had a simular problem with hard locking. Finally my phone quit working all together. I went into boot loader mode and flashed it. It's like having a new phone again. So yeah.. I think the ROM's can get corrupt.
Brandon
NeoCole: Looks like you are using T-Mo in the U.S. Mind if I asked what you flashed yours with? Did you use a specific ROM, Radio Stack version etc.?
I'm running an unlocked i-mate (contradictory to my subj title, I know).
Flash it with the T-mobile 1.72 ROM
ROM Version
Well.. I flashed it with the IMATE 1.72 ROM and used most of it's extended ROM. I used the battery Meeter from the Qtek extended rom. I built most of my extended ROM Myself.
I look at T-Mobile's Beta 1.72 ROM like I look at Windows ME. Both should have never happend. I can't count how many times I had a hard reset with the T-Mobile ROM. I'm not sure if it was a combination of the programs I was useing or not. I saw a post that said SBP was possibly causing the problem. So I quit using SBP products. Later I still had to HARD RESET from time to time. Now that I'm running differently, My device has never been so smooth.
Let me know if this helps,
Brandon
Looks like I'm pretty much screwed. Without a working power button I can't do a hard reset into bootloader mode. When I try using a utility app that allows me to do a hard reset I can't hold down the jog dial at the same time. Good times.
*edit: yeah, that would be 'can't' hold down the jog dial.
You don't need to boot into the bootload to perform an upgrade... the upgrade software takes care of everything for you (except the hard reset at the end)
All you need to do is sync through Activesync and then run the upgrade program.
I would (and have!) flash the imate 1.72 ROM. It is very stable for me and HAS improved the battery life of my imate.
As stated above, just start the flash process and it will put the device into bootloader mode and perform the flash. It will need a HR at the end, but since your power button is not working, maybe you could remove the battery, slide the red slide/switch back into place for a few seconds as if the battery were there, then slide it back, put in the battery, slide it back into place and press one of the puttons to turn it on.
Hey . . . it might just work!
imate 1.72 ROM did the trick. After I actually READ all the posts regarding the ROM I realized it came with an installer and got that done. So far so good. Now if I could only find my missing tomtom 3 cd key that went MIA during my last move
Hey, that's fabulous! Welcome back to the world of convergence.
Hi Guys, i have a strange Problem since a couple of days.
The touch HD turns itself off after some minutes. I have to take out the battery and put it back in, otherwise it will not turn on...
i have:
- deactivated automatic shut down in power settings
- deactivated today timeout
- tried hardreset
- tried another rom (currently dutties final)
no success :-(
i have absolutlely no clue what could cause this and how i can fix it...
help is highly appreciated.
hello there , actually maby its a virus or there is problem in SPL
Try to install again the SPL modified and tell me
best regards
ms4cah
unlikely it has anything to do with SPL. it was fine for months, i had not flashed or installed anything.
it seams dead now by the way. i cannot turn it on again.
i also tried a new battery. it doesnt even charge, no light at the power button. nothing.
Surrido said:
unlikely it has anything to do with SPL. it was fine for months, i had not flashed or installed anything.
it seams dead now by the way. i cannot turn it on again.
i also tried a new battery. it doesnt even charge, no light at the power button. nothing.
Click to expand...
Click to collapse
Sounds like a warranty claim
I am getting the same problem!! is there anything i can do to fix this? anyone figured out the reason?
I had this sort of problem.
The HD would hang, then switch off, then to get back on I had to remove the battery for a while. Sometimes it worked after a minute, other times I had to leave the battery disconnected for longer.
So I performed a hard reset and it switched itself off during boot (after successfully resetting).
Battery out for a while.
H/R once more. Again crashed during boot but not at the same point as previous.
Tried a different battery with a full charge - same result.
Tried to re-flash a "very popular" custom ROM with USPL. Got to 1% and error. This was because the HD had crashed..
Tried to flash the official HTC ROM and it got to 15% and error. HD crash.
So I have contacted HTC and they are sending a courier to collect it so they can take a look with a view to repairing it.
The last ROM I successfully loaded about 2 weeks prior to the start of my problems was a custom win mo 6.5 rom. As I couldn’t get it to a stable state - I couldn’t flash the official HTC ROM.
I’ve convinced myself it’s a hardware fault rather than any software damage..
Although I fear I’ll be in for some bad news.
mine too
Hi,
I have the same problem.
Mine was doing hard reset and after a day or two the same problem.
Now I cannot turn it on.
I will send it to htc...
Crossing my fingers.
I had the same problem with mine...
While turned on, it automaticly tryed to turn of, as if something was pressing the on/off buttom. Everytime that message for turning it off poped up and I just couldn't control the on/off button anymore.
I tryed everything and nothing worked. It really seemed a hardware and warranty claim issue. However, since I bought it abroad and it does not have warranty here in Brazil, I just decided to sell it (obviously warning the buyer about the issue) and to buy another one (which is working as a charm).
It is a hardware issue, for sure...
So my HD has been away at HTC for nearly a week, and im currently tracking its return journey, due to land back here at some point this morning.
I have had no contact from HTC so its going to be a suprise as to whether anything has been repaired.
My hope was they couldn't turn it on at all - thus replacing the bits n bobs inside, replacing the main board containing my 6.5 ROM.
So for now im hoping "no news will be good news", but I will update this when I have it back.
... I've the same problem...
Hi, I've the same problem. Do you have any solutions?
Nasher79 said:
So my HD has been away at HTC for nearly a week, and im currently tracking its return journey, due to land back here at some point this morning.
I have had no contact from HTC so its going to be a suprise as to whether anything has been repaired.
My hope was they couldn't turn it on at all - thus replacing the bits n bobs inside, replacing the main board containing my 6.5 ROM.
So for now im hoping "no news will be good news", but I will update this when I have it back.
Click to expand...
Click to collapse
Just recieved delivery. The service report states:
1. Diagnosis
2. Replace Main Board
3. Function Test
Result
Confirms it was a H/W fault and my "flashing" did not effect the warranty status. That may have been because they couldnt get far enough to confirm so.
Mega75 said:
Hi, I've the same problem. Do you have any solutions?
Click to expand...
Click to collapse
Other than a Warranty repair, im afraid not. Try your best to get it back to HTC official software, then report it as no power / cant boot.
Nasher79 said:
Just recieved delivery. The service report states:
1. Diagnosis
2. Replace Main Board
3. Function Test
Result
Confirms it was a H/W fault and my "flashing" did not effect the warranty status. That may have been because they couldnt get far enough to confirm so.
Click to expand...
Click to collapse
Good to know, confirmed h/w issue
i simply deactivated automatic shut down in power settings as mentioned in the first post and unistalled a couple of new programs i had recently installed!!
Not quite sure which of the above worked.. but atleast for now it seems to be working fine!! the screen has not turned off by itself and i have not had to remove battery etc to get it to work again!
I'm not quite sure if the problem is properly fixed but it has been a few days since anything occurred!! so fingers crossed!!
mine was doing this last tuesday, each time i went into my pocket for it, it was turned off, then i hard to do the reset pin or remove the battery, it has been ok since, i just thought, maybe it was me, pushing it in my jeans i might be turning it off.
also using duttys popular 6.5 latest rom, i dont think its fair to blame his rom, as mines ok now, maybe i should reflash it again?? im still waiting for a new version to be released.... JESUS!!! just looked it up to r12, im on r9 .
oh no... no it not..... says to go here, and it will be released here and not on dutty throy???
http://htcpedia.com/forum/forumdisplay.php?f=79
iamdarren said:
mine was doing this last tuesday, each time i went into my pocket for it, it was turned off, then i hard to do the reset pin or remove the battery, it has been ok since, i just thought, maybe it was me, pushing it in my jeans i might be turning it off.
also using duttys popular 6.5 latest rom, i dont think its fair to blame his rom, as mines ok now, maybe i should reflash it again?? im still waiting for a new version to be released.... JESUS!!! just looked it up to r12, im on r9 .
oh no... no it not..... says to go here, and it will be released here and not on dutty throy???
http://htcpedia.com/forum/forumdisplay.php?f=79
Click to expand...
Click to collapse
FYI, Throy is releasing roms exclusively to HTCPedia now, so no future roms will be released on either XDA or www.duttythroy.com
wow!!! i never knew!!!! thats crazy as his own site duttythroy wont be used.
im getting it now, but only 11 when it says 12 is out, either way, i will still flash i love the roms, i will be sure to be on all the site, incase theres another change of heart??
anyway guys i will report if i noticed the shutdown thing happening again with the version. 4mins till downloaded.....
I think theres a couple of different issues here. My own problem was due to faulty parts in the hardware itself. Absolutley nothing to do with any ROM, only reason I mentioned them was because of the invalid warranty possibility.
If your problem was ROM related, Im sure in the relevant ROM thread, there would be many people (everyone) with the same issue. Thats not to say that its not some sort of conflicting software you may have installed after the ROM flash.
Some simple troubleshooting steps:
1. Hard reset - If it still has a problem...
2. Flash Official HTC ROM - If still a problem...
Phone HTC.
All the best, hope you manage to get something to work for you. I know how lost I felt without mine!
Nasher79 said:
I think theres a couple of different issues here. My own problem was due to faulty parts in the hardware itself. Absolutley nothing to do with any ROM, only reason I mentioned them was because of the invalid warranty possibility.
If your problem was ROM related, Im sure in the relevant ROM thread, there would be many people (everyone) with the same issue. Thats not to say that its not some sort of conflicting software you may have installed after the ROM flash.
Some simple troubleshooting steps:
1. Hard reset - If it still has a problem...
2. Flash Official HTC ROM - If still a problem...
Phone HTC.
All the best, hope you manage to get something to work for you. I know how lost I felt without mine!
Click to expand...
Click to collapse
Your exactly right. Some people experience similar symptoms which are rom related others have same problem which is hardware related. One can only be fixed by HTC as motherboard problem, other can be rectified by different means without having to send device back for repairs
Hi again,
Today I have received an sms from HTC service informing me that my HD has a circuit problem and they will fix it without any charge.
I have to wait.
My still under warranty 6900 has a totally black screen. I can see that the backlight is on- it is the actual lcd that is black and the phone will receive calls. (I can't see if it goes to bootloader since the screen is black) Presumably, this has nothing to do with the nsfan6.5 ROM on it.
Verizon CS told me on the phone that if they sent me a warranty replacement then found it to be water (or physically) damaged, they would "have to" bill me for the RETAIL value of the phone. She gave me the option to take it into a verizon store to have a tech first OK the replacement to avoid this possibility. He OK'd it and is should be here shortly.
Is there a way to get it back to stock rom while not being able to read what is on the screen? For that matter, is this even worth doing or will VZW not notice?
PS- I'm trying to decide what ROM to put on the replacement phone- Android is tempting but I think I'm going to wait for the smart people to finish getting stereo bluetooth and standalone GPS all sorted out. I'm sure I'll play with it on the SD card in the meanwhile. Thoughts?
I realized I should add:
On the phone I need to send back, I have the bell (complete with ugly blue start up screen) 3.42.50 radio and whatever nsfan 6.5 build was most recent back then.
To accomplish the flash, I also have a 2gb microsd card (with reader) and have downloaded the stock verizon rom.
Also, the touch screen appears to work (vibrates on touch) however, no amount of guesses with random screen touches could get the phone to connect with activesync or tether (sadly, the last type of connection I made was as a removable drive). In other words, things might not be where they are supposed to be on the screen so telling me to tap at pixel 120x200 (or wherever the "next" or "ok" button might invisibly be) may or may not work.
thanks again!
Enter bootloader - Hold Camera and Power and soft reset.
Connect to usb
Run RUU from stock rom.
dvirus1023 said:
Enter bootloader - Hold Camera and Power and soft reset.
Connect to usb
Run RUU from stock rom.
Click to expand...
Click to collapse
LOL, thanks. I just logged on to say I'd figured it out. It finally dawned on me that 10 months ago i'd noticed (or heard or something) that you didn't need the active sync connection going if you entered bootloader first.
Fantastic. Many thanks.
Just in case someone reads this trying to do the same thing: I saw elsewhere that you need to run imcoke.41 before reflashing with stock ROM so that's what I did.
Correct?
I think you need to run the .40 unlocker, not the .41
.40 is supposed to be overwritable, .41 is not
I've been using .40 before I send back my phones. When I flash the VZW ROM it usually errors out the first time, then you follow the instructions on the screen(pc) and it takes the second time.
scotttr said:
I think you need to run the .40 unlocker, not the .41
.40 is supposed to be overwritable, .41 is not
I've been using .40 before I send back my phones. When I flash the VZW ROM it usually errors out the first time, then you follow the instructions on the screen(pc) and it takes the second time.
Click to expand...
Click to collapse
You're right. I'm hoping it was .40 that I used and just wrote .41 here. Regardless, I already sent it off.
Hey everyone, my hd2 died (original 1.48 rom), I already tried soft reset, hard reset, put out my battery, charge it and everyhting that came to my mind but when i turn it on it wont go further than the first htc image.
Is there anything i cant do or should i just take it back to the shop?
Thanks
I would take it back, even if you do fix it. You don't want a phone that may still have a underlying problem.
Htc HD2 BRICK Need HELP!!!!!!!
I flashed Duttys_Leo_Sense_2.5_5.2.23554.5.5.0_1.72_Multi-Lang_6.5.5_Radio_2.07.51.22.2_V1.2_WWE into tmobile htc hd2 cause i was [email protected]$kin goin Rom happy and didnt double check its compatibility and my screen went blank black, cant power on, cant go into bootloader, and cant hard reset but when i plug it in to my computer it recognizes it as a device without a driver i saw it in the device manager on windows 7 ulitmate. CAN I SAVE MY HTC HD2??
I KILL my htc hd2 (BRICKED)
I used HSPL2_1024_RUN.exe i flashed like 5 roms within 24hrs i was trying them out and this one made killed my hd2.
for those stuck on the htc boot image
take off the back cover of the phone and press the little red button, this will restart the phone
AS SOON AS you press it, press and hold the volume down button this will bring you to the bootloader
connect the phone via usb to your computer and flash a different radio rom (look first which are compatible with your rom)
if this doesnt work, using the same method flash back to your original rom.
hpg said:
I flashed Duttys_Leo_Sense_2.5_5.2.23554.5.5.0_1.72_Multi-Lang_6.5.5_Radio_2.07.51.22.2_V1.2_WWE into tmobile htc hd2 cause i was [email protected]$kin goin Rom happy and didnt double check its compatibility and my screen went blank black, cant power on, cant go into bootloader, and cant hard reset but when i plug it in to my computer it recognizes it as a device without a driver i saw it in the device manager on windows 7 ulitmate. CAN I SAVE MY HTC HD2??
Click to expand...
Click to collapse
for tmous with 1gb rom NEVER flash a radio with .51. in the code.
still haven't seen anyone recover from this. if anyone has please let me know.
Damn it captain!!!!!!
I just got it on the 24th shhhhhhhh....... ummm i just will take it to TMOBILE i hope i can get an other one, they may not have one in stock or they WONT give me another. i will see as soon as the store opens.
Sorry to hear about people's problems. Just remember if you have TMobile
USA there is NOT a way to flash another rom onto the phone..Just give it time the wonderful folks here are working on it. If your still in your 14 day grace period just return the phone to the store and play dumb. You might
have to wait for another phone since apparently they did not anticipate
how many people wanted this phone and sold out quickly. I know I was there
at 6:30 and the second in line and they only had 5!
Anyway, the most important thing you can do here is DO a search!
I KILL my htc hd2 (BRICKED)
BUT I have flashed roms into Tmobiles htc hd2 like TOUCH_X_TREME_23549_TMOUS_2_30_5_49 among others and they worked! i was just try different ones and i PICKED and I BRICKED!!!!!!!!!!!
Damitu said:
Just remember if you have TMobile
USA there is NOT a way to flash another rom onto the phone..
Click to expand...
Click to collapse
sorry? sure about that? seems to me lots of people have successfully flashed their tmous hd2.
It only goes wrong if you
1 - flash a rom based on anything less than 2.10 rom
or
2 - flash a radio with ..51.. in the version number.
I KILL my htc hd2 (BRICKED)
When I take it back do you think tmobile can they tell if i flashed a rom?
hpg said:
When I take it back do you think tmobile can they tell if i flashed a rom?
Click to expand...
Click to collapse
possibly, however its worth a try, there are other people that have reported they got it exchanged. the worst theu can do is send you it back un fixed. They can't keep it and make you pay for the fix.
I KILL my htc hd2 (BRICKED) and the walk of SHAME!!!
Ok well thanks for your GREAT!!! input how can i add you to friends for future epic fail endeavours!!! i encounter.
hpg said:
Ok well thanks for your GREAT!!! input how can i add you to friends for future epic fail endeavours!!! i encounter.
Click to expand...
Click to collapse
hehe, i rarely bother accepting friend requests, this isnt a social networking site!
Just find any post be me, and either click my name or the green button next to my name to PM me.
Shamely going back to tmobile on wed
I went to tmobile last friday they tried to turn it on, pushing reset and taking out the battery so they put me on a list for this coming wed. I still got the bricked one with me they told me to bring it in for a trade. i have tried everything to turn it on but the screen remains BLACK. so i got a BLACK BRICK!!!
Any more ideas?
cgrec92 said:
for those stuck on the htc boot image
take off the back cover of the phone and press the little red button, this will restart the phone
I do not see a little red button under the back cover. I am in the US, just bought phone, slightly used of course, no warranty. It suddenly went dead this afternoon while charging, will sometimes try to power up but will just keep flashing that one screen "stick together" over and over.....
Tried another battery, same thing.
Click to expand...
Click to collapse
Mine is doing the same thing . . . in the US, the reset button is right next to the SD card slot, and it's yellow. Mine wouldn't come on Friday, and I started a web chat with Tmobile to see if they would exchange it, and then it just came back on. They said as long as the white sticker at the top of the battery compartment is still white (proving you didn't get it wet), then they will exchange it. It worked fine for me the rest of the weekend (AFTER I did a hard reset, and got it running great!!). This morning, I locked it while running MobiTV, then I couldn't unlock it, so I pulled the battery. That was 2 hours ago, and it still won't come on . . .
If it doesn't come on before I leave work, I'm taking it to Tmobile tonight!!
UPDATED 20 minutes later: Just came on . . . no rhyme or reason why?? Just started after MULTIPLE times of taking out and putting back battery, SIM, and SD card. Got the same error that I've been getting the last couple months on reboots (services.exe)?? When I did a CleanRAM, it free'd up 3.36MB . . . so SOMETHING was hung up, but nothing was running in the task manager??
Generally, few task managers show what's really going on with the phone's memory. Use an advanced task manager which will allow you to control the actual processes running on your device, Google for the names of those which seem to cause mischief and terminate them (if possible) or try to find a solution.
hpg said:
When I take it back do you think tmobile can they tell if i flashed a rom?
Click to expand...
Click to collapse
Hey I am also Tmobile User and I have flashed a few ROMS luckily I have not Bricked my phone (knock on wood.) I was just wondering how your return went? I have insurance on mine and figured I would just take it back if that happened. I just didn't know if that would work? Did you ever get a new one
Another update . . . used my phone all afternoon, and tried to charge it, and it wouldn't charge??? Luckily, my husband has the same phone, so I checked his with the same charger. Compared the two phones, and the prongs that hit the battery were bent back. I folded them back down, and now it can charge again. Makes me wonder if that is the problem with the phone not coming back on? Maybe putting the battery back in so that it wasn't hitting the prongs has been keeping it from turning back on . . .
Hey guys. I just bought my HD2 today and I have flashed HTC phones before.
This is a TMOBILE 1024LEO phone so I connected it to ActiveSync and installed HSPL 1024. After installing it I loaded the CustomRUU and installed "RUU_Leo_HTC_WWE_1.66.405.2_Radio_Signed_15.30.50.0 7U_2.06.51.07_Ship.exe". This installed 100% and my phone powered off after it was complete. Since then I have not been able to get the phone to respond. I believe I bricked it? But I don't see why I can't even get the bootloader to load when powered off. I've tried holding the volume down button and pressing the power button. Holding the volume down button and pressing the soft reset button. Holding both volume buttons and pressing the power button. None of these get it to respond. Any ideas?
- Frankie
its dead.
flashing a 1.66 rom alone would have been recoverable, but that rom you chose also includes a radio, because it is an official rom, and that radio is 2.06.51.07, , and what happens when you flash a radio with .51. in it?
Correct, brick.
So far no one has been able to fix it, some have taken it back and gotten a replacement.
Sorry to be the harbinger of doom.
(One of the very few actual known ways to really brick the hd2, in spite of the fact that half the daily new threads say 'OMG brick!')
Throw it in the bin?
From the TMOUS HD2 flashing thread...
Not all ROMs are compatible with 1024LEO, including old official ROMS.
Official 1.42 and 1.66 WON'T WORK on LEO1024, because there is no 1024 NAND memory support.
All custom ROMs which ARE NOT BASED ON 2.08+ T-Mobile ROMs WON'T WORK ON 1024LEO.
IMPORTANT: DO NOT flash any Rom unless it states in the 1st post that its compatable with the 1024LEO or the chef confirms its safe to flash on a 1024LEO. If you flash a Rom with a Base version before 2.08 then you will most likely brick your phone. PLEASE BE CAREFUL!!
IF YOU ARENT ABSOLUTELY SURE THEN DONT FLASH IT!!
[...]
IMPORTANT: Do not flash ANY Radio before 2.07.x or the 2.09.51.03 Radio or you could damage your phone!!
IMPORTANT: Make sure the Radio you flash is FULLY compatable with the US HD2 before flashing.
IF YOU ARENT ABSOLUTELY SURE THEN DONT FLASH IT!!
Click to expand...
Click to collapse
You just got a brand new brick. Read the instructions next time...
so there is nothing that I can do to get the phone in bootloader mode even when powered off? I don't understand why that isn't possible.
and btw when I connect the phone to a computer via USB, it tries to install software for "QUALCOMM CDMA TECHNOLOGIES MSM". idk if that helps
Verson said:
so there is nothing that I can do to get the phone in bootloader mode even when powered off? I don't understand why that isn't possible.
and btw when I connect the phone to a computer via USB, it tries to install software for "QUALCOMM CDMA TECHNOLOGIES MSM". idk if that helps
Click to expand...
Click to collapse
all it helps it to confirm that you have the 'it no longer goes to bootloader or power on and shows up as qualcomm (if it shows up at all, some dont) on the PC' problem.
Sorry, but if you look through the tmo us thread there are a few dozen people it has happened to.
here you go, some reading
Verson said:
so there is nothing that I can do to get the phone in bootloader mode even when powered off? I don't understand why that isn't possible.
and btw when I connect the phone to a computer via USB, it tries to install software for "QUALCOMM CDMA TECHNOLOGIES MSM". idk if that helps
Click to expand...
Click to collapse
you could try to flash the shipped rom when that happens not 100 sure....give it back to whereever you brought they will replace it
Verson said:
so there is nothing that I can do to get the phone in bootloader mode even when powered off? I don't understand why that isn't possible.
and btw when I connect the phone to a computer via USB, it tries to install software for "QUALCOMM CDMA TECHNOLOGIES MSM". idk if that helps
Click to expand...
Click to collapse
Nope, it's completely bricked. No ones figured out a way to recover from flashing the wrong radio on the tmous hd2. You're not the first to do it and try to find a fix.
okay guys thanks for the input. I should have been more careful in selecting a ROM! I am taking it back to the tmobile store tomorrow and saying that it just stopped working randomly =D
Verson said:
okay guys thanks for the input. I should have been more careful in selecting a ROM! I am taking it back to the tmobile store tomorrow and saying that it just stopped working randomly =D
Click to expand...
Click to collapse
maybe they won't believe you, but they have no way to prove you're lying, so... even if this kind of attitude will eventually make producers release way stricter warranty policies so in the end maybe everyone will pay for the lightheartedness of the few
or maybe they'll look at their returns pile, figure out how to boot them, leak the process and we can fix it ourselves!
Well if you do brick the phone, their has to be a way to reverse. I'm pretty sure people at HTC know how to do it. I doubt they jus throw these phones away they refurbish it, so there has to be a way to put the stock rom back.
HTC has the bootloader code so they probably have a way to flash it back.
My HD2 turned a few heads at work and a dedicated iPhone owning gadget fan just had to have one. It failed within a day and he returned it for a refund. He was given a new one, and here's my point, had to sign a document agreeing to pay nearly £800 (yes, £800 - that's what the shop charges for a PAYG HD2) if it was later found that the failure was due to abuse, including the use of illegal software. When I read that I was certain they were referring to cooked ROMs. I guess HTC (and the repair shop, perhaps) can tell what's on a phone, even if there isn't a fix and they have to change a board or even throw away the phone. There's a company that can recover iPAQs that have suffered a similar fate. They were doing this before iPAQ 21x cooking became popular. I wonder if such s service exists for HTC devices, or whether such a recovery service is possible with the right tools.
Personally, I'd love to try some of the ROMs on this site but I'm sticking to simple customizations. I'm in no way a WM novice. I just can't justify risking an expensive device. I even avoid official updates if I'm not having problems. Ironically, I've had 4 iPAQs die on me without messing sigh the ROM. I'd be tempting fate.
Anyway, good luck with whatever you decide to do. I hope you get to enjoy an HD2.
My HD2 turned a few heads at work and a dedicated iPhone owning gadget fan just had to have one. It failed within a day and he returned it for a refund. He was given a new one, and here's my point, had to sign a document agreeing to pay nearly £800 (yes, £800 - that's what the shop charges for a PAYG HD2) if it was later found that the failure was due to abuse, including the use of illegal software. When I read that I was certain they were referring to cooked ROMs. I guess HTC (and the repair shop, perhaps) can tell what's on a phone, even if there isn't a fix and they have to change a board or even throw away the phone. There's a company that can recover iPAQs that have suffered a similar fate. They were doing this before iPAQ 21x cooking became popular. I wonder if such s service exists for HTC devices, or whether such a recovery service is possible with the right tools.
Personally, I'd love to try some of the ROMs on this site but I'm sticking to simple customizations. I'm in no way a WM novice. I just can't justify risking an expensive device. I even avoid official updates if I'm not having problems. Ironically, I've had 4 iPAQs die on me without messing sigh the ROM. I'd be tempting fate.
Anyway, good luck with whatever you decide to do. I hope you get to enjoy an HD2.
As long as your PC is attempting to load the Qualcom CDMA driver...
I have a 1024 Tmo HD2 and I always stick to NRGroms from my TP to TP2 and now HD2 (cyanogen is by far the besy for my Nexus or most other android phones). I decided to flash the Artemis Rom and Bricked my device. It worked at first but once the battery died it would start up. So i figured the usb driver must be incompatable because it wouldnt charge. I was able to get Tmo to replace my HD2 device but didnt want to have to pay the $100 charge they charge if they find the device has been tampered with (not only physically, but software too. SSPL, HSPL, custom ROMs, etc.). Been charged before so they do check.
My point is once they sent me the replacement device, I used the new HD2 to charge my battery to see if it was the usb port not charging. Once the new phone charged the battery and I plugged the HD2 into my PC i received the same message saying attempting to install that Qualcomm CDMA message and the driver would not install. I ended up figuring out the issue but it will take having another HD2. Call Tmo and have one sent to you through warranty not insurance and it will be free. I even complained about not having a top quality phone i paid for to use my service and they upgraded to free expedited shipping. So Dial 611 now. Then just get those drivers using the new 1024.
First make sure to turn on the replacement device and open Mobile device center and plug in the device to get the standard driver. Once you get the standard driver, unplug the new HD2 and plug in your bricked device trying to get the same Qual CDMA driver. Now the driver install should complete. Now since you have an incorrect driver id recommend flashing to the Stocl 1024 ROM cause this will update your device to the correct driver and ROM so you wont be charge when you send back your old bricked device.
Now once you reflash your new HD2 just stick to these 2 simple steps.
1. HSPL with the 1024 version (HSPL2_1024_RUN)
2. Only use NRGroms for your Tmo LEO (http://bit.ly/HD2-NRGroms)
If this does not work just send back the HD2 that is bricked and you get a replacement for only $100 charge. Better than having the most awesome paperweight. Also make sure to use the same usb port used to install the primary driver. And dont be afraid to try running the new HSPL on your bricked phone cause that is what actually allowed my bricked phone to comunicate with my PC, then my bootloader driveer installed. I know this is alot of jabber but just ask if you have any questions. My boys brying now so gotta go...
Verson said:
Hey guys. I just bought my HD2 today and I have flashed HTC phones before.
This is a TMOBILE 1024LEO phone so I connected it to ActiveSync and installed HSPL 1024. After installing it I loaded the CustomRUU and installed "RUU_Leo_HTC_WWE_1.66.405.2_Radio_Signed_15.30.50.0 7U_2.06.51.07_Ship.exe". This installed 100% and my phone powered off after it was complete. Since then I have not been able to get the phone to respond. I believe I bricked it? But I don't see why I can't even get the bootloader to load when powered off. I've tried holding the volume down button and pressing the power button. Holding the volume down button and pressing the soft reset button. Holding both volume buttons and pressing the power button. None of these get it to respond. Any ideas?
- Frankie
Click to expand...
Click to collapse
HI GUYS.
i flash my hd2 using the correct software. on my phone it said it had 2.8 soemthing and the program that flash my hd2 flashed it to 2.8
after that i did the custom rom and it completed sucessfully but at the end the phone went off and a message came something about the qwalcomm driver being missing. since yesterday my phone would not power on or even show any signs of being charge. at the time of the flasing and everything i had a 100 percent battery. what can i do. i try to reset it and by accident i did not know which was the reset on the back and accidentally pushed a whole where it says void. im afraid to take it to the store and they would see that whole where it says void has been touched. any suggesions of what to do. thank you