Hello,
not sure if this was posted before, but i have came across an issue with my htc hd2, after installing the new rom on my device, it refuse to respond on any touch. the only features to work on the device are the hard buttons. i have rebooted the device, removed the battery but cannot do anything on the screen, i cannot slide to unlock or answer calls using the touch.
urgent help needed.
thanks
if its an issue as serious as that, try a different rom/radio combination!
sounds like you might need to send it to HTC Care!
meanwhile, use something like pocket controller to control your device from your pc. you could also try and install spb pocket plus and restart in safe mode?!
Best of luck!
I did try different radio, but its not updating, i had 2.05 and i tried installing 2.07 no changes, i tried different rom still no difference....i did sent in my phone to htc care, but they replied back stating the boot driver is not loading up for the device and they would have to replace the mainboard for the amount of $400. any best suggestions.
im sure the device isnt bricked, its detectable by my computer, i can power it up and answer my calls...
Related
Thanks in advance if anyone can come up with something that helps... I can't imagine what that might be though!
This morning I had a stock Mogul... original ROM, no hacks, even had the Sprint S/W on it. It worked fine.
I downloaded the new Sprint ROM 3.35.651.2 and ran it. While running the Mogul rebooted, went to bootloader, then failed. It was then stuck in bootloader mode. I read up and found that a successful flash should bring it out gracefully so didn't troubleshoot much. I tried a couple of times more to no effect. It was still in bootloader mode.
I then downloaded the old 2.17.651.0 ROM from HTC and that wouldn't work either. Still in boot loader mode.
I read somewhere that a guy got the 3.16.651.0 leaked ROM to update even when the others would not. So, I downloaded and tried it. Everything looked good! It was loading the ROM, the bar went across the screen to 100% and then...
nothing. A black screen. Vista loaded some new drivers and seemed to know there was a USB device attached but I couldn't connect to it in any useful way through Explorer and it didn't show up in the Mobile Device Center.
I thought I'd try flashing it again but since the screen was black I was just guessing. I did a hard reset (both soft keys plus soft reset button) and I got nothing... not even the same connection I'd had after the 3.16 update.
Now, I plug in the device and get no USB connect sound or notification in Windows. I get a orange light on the right LED for maybe 15 seconds then it goes out. Other than that one brief LED the thing is a brick as far as I can tell.
Any ideas? I plan on taking it in to Sprint tomorrow and telling them they bricked my phone with their update if I can't figure anything out tonight.
Thanks!
First POSSIBLY legitimate brick story I've seen.
Have you tried holding down power and camera while pressing reset to see if you can get back to bootloader?
Geckotek said:
First POSSIBLY legitimate brick story I've seen.
Have you tried holding down power and camera while pressing reset to see if you can get back to bootloader?
Click to expand...
Click to collapse
Yes.
FYI... I just left the battery out for about 5 minutes (what the heck, worth a try right?) and put it back in. I get no lights, buttons do nothing, soft & hard reset do nothing, forced bootloader does nothing. The only way I can get the phone to do anything is to plug it in to a USB cable. The orange light comes on for about 15 seconds then goes out. The computer never recognized there is a new USB device attached.
I loaded many custom ROMs on my old 6700 and never had a problem. I leave my new 6800 alone and wait for the upgraded stock ROM and look what happens! Guess I shoulda used a custom ROM instead, eh?
lol sounds like a legitimate "brick" to me. Very strange, and congrats on your new mogul paperweight (i also have one that was a victim of water) haha, good for holding things down on the windy days.
Yup, bricked.
Sprint couldn't figure out how to unbrick it and just gave me a new phone. The new one upgraded nicely and now I have GPS!
Everyone enjoy the upgrade!
same problem
no need to retype what you said. i had the EXACT same problem. phone was completely bricked and continued to crash at 11%. I went to my local store (i work for sprint, and i know a smart tech there) and was told it was kaput. Hard reset, tried to reload other roms, the whole 9 yards. It's a goner, and now i have a new mogul in my hand. I'm afraid to try it again. I'm running vista, and im wondering if that's the problem.
Anyone with vista have the same bricking problem? Is it an issue to directly upgrade from factory rom to the 3.35? My old brick had the current 2.17 or whatever... HALP
Vista
The first time I tried the update I connected the Mogul to my Vista Business 64bit Thinkpad T61p.
The second time I tried it (on the new Mogul) was from my Vista Business 32bit desktop (white box).
I don't know if that helps or not. The second time went smoothly.
On another note... an entertaining one... while I was in the Sprint store today waiting for their tech to confirm that the phone was bricked another guy came in with a Mogul and complained of the same thing. I took the last Mogul they had in stock. Poor guy. I hope they get more soon... there are a lot of people who want GPS and are upgrading their phones. That means there are gonna be some more bricks I'd think.
Hey guys Im a noob and im having a bit of problems
Im stuck in the bootloader screen
TITA100 MFG
SPL-2.40 Olipro
CPLD-9
My comp has windows vista premium so instead of activesync i have windows device center 6.1 I have unclicked allow USB connections
but i think my comp doesnt recognize that they the phone is connected at all although i do here the sound that lets me know that a usb device is connected
exitbl.exe doesn't work keeps telling me
cannot open USB port
Please make sure that USB connection in Activesync is disabled
Also make sure that your USB cable is properly connected
if it helps im on a bell phone
Hey I've been having this problem with my Titan. I have Keys 1.31 rom and every once and awhile when I turn on my Titan it gets stuck on the the windows mobile start screen. Im able to get my phone working again if I reflash Keys rom.
So far this has happened 3 times in the past month.
Any ideas on what could be causing this?
Bell 6800
Keys 1.31 ROM
3.35 radio
Just for future reference...never has your phone been a brick. A bricked phone is just that...a brick, a paperweight, won't do anything at all. It can't be turned on, it can't boot, it can't be reflashed or fixed. It's obvious you're having a problem with something, but I constantly see people on a daily basis saying their phone is bricked when in actuality, very very few people have actually bricked phones.
Sorry, but I have no idea. You're apparently alone in facing this.
Have you tried reflashing to another third party or stock radio/ROM combination to help rule software or a bad flashing out as a cause?
mrfantastic said:
Hey I've been having this problem with my Titan. I have Keys 1.31 rom and every once and awhile when I turn on my Titan it gets stuck on the the windows mobile start screen. Im able to get my phone working again if I reflash Keys rom.
So far this has happened 3 times in the past month.
Any ideas on what could be causing this?
Bell 6800
Keys 1.31 ROM
3.35 radio
Click to expand...
Click to collapse
What bootloader are you running? Maybe a bad install of the bootloader?
no, that's not a possibility, the bootloader isn't like a copy of Windows... besides, it's getting stuck on the windows mobile logo, that means its at the kernel.
my advice is to dump that ROM and flash something else.
Olipro said:
my advice is to dump that ROM and flash something else.
Click to expand...
Click to collapse
In case that is interpreted negatively, quite a few are using builds from my kitchen and he's been quite alone in reporting this.
Sorry, I just had to chime in to defend my work.
That said, if one is facing such problems the first avenue to problem solving is not to keep flashing the same radio/build of an OS ROM into perpetuity. Mix things up. Isolate.
I'm not saying i'm 100% positive on this one, but sounds like to me he's using some kind of software that is coded poorly, or something that is corrupting his kernel or the necessary files that boot the os. Sounds like the phone is getting hung up right when it's trying to execute these files at boot.
My advice to you, that is if you want to keep using key's rom, is to create a CLEAN rom, and don't install any software. Run it for a while clean and see if the problem goes away...if that's the case, you need to re-evaluate which software you use.
HTC home. The silly green screen that says windows mobile? Yeah, HTC home is causing it to fail to boot, this has been covered before.
This is a very misleading title for this post. You can't unbrick a true 'brick' - unless it was a brick because you left the battery out.
A true 'brick' can't ever be turned on. It's a dead paperweight. So, there's no chance of unbricking it.
Flashed Keys rom to few phones....never had a problem !
I used olipro 2.40
Right now the phone is fine, it appears to happen randomly, Keys rom is great otherwise (no insult intended). What was meant by the problem with HTC home?
HTC home. The silly green screen that says windows mobile? Yeah, HTC home is causing it to fail to boot, this has been covered before.
Click to expand...
Click to collapse
The windows mobile splash screen or the "silly green screen that says windows mobile" as you put it is not HTC Home. It is not HTC Home that is causing him to lock up at boot time.
To the OP, read my post, it's some piece of software that is causing your lockup. Guaranteed, if you make a clean rom (no software installed except the rom, with nothing cooked into it) I bet you see your problems go away. I then would install each piece of software one by one testing to see if you see the lockups after each one.
help
Can Any One Tell Me How To Go Back To WM 6.0 From WM6.1 I'm HAVING More Problems Then I Want With 6.1 But I Have No Idea How To Change It Back.
kaos29205 said:
Can Any One Tell Me How To Go Back To WM 6.0 From WM6.1 I'm HAVING More Problems Then I Want With 6.1 But I Have No Idea How To Change It Back.
Click to expand...
Click to collapse
Kaos,
You will find you get more answers by posting in the appropriate thread. This is not a WM6 thread so chances are that most ppl would ignore your post.
As you are probably on dcd 3.0.x, I have answered your question over there in the dcd 3.0.4 thread. http://forum.xda-developers.com/showpost.php?p=2177772&postcount=459
Apart from the fact that your are more likey to recieve an answer when posting in the correct thread, it will also help others with the same problem find the answer wheb they do a SEARCH.
Also another good place to find general information is in the titan wiki (see the sticky at the top of the titan upgrading section).
Lastly, you could try starting a new thread if you just cant seem to find the appropriate place to get your answer.
Hi everyone!
I would just like to receive some user experience since I haven't found anything on the net or forums.
The thing is, my HD2 (HSPL 3, Radio 2.12.50, ROM Energy 6.5), after months of tests and fun, freezed as usual (like a normal WinMo) but this time did not start up after a battery removal ( or a soft reset button).
The first two startups were followed by an 8 vibrates code than nothing. I've removed a battery and tried to boot again but this time nothing happened.
The only action I can hear is the starting of the vibration motor while trying a Hard reset. No charging, no leds are working nothing.
Seems that BIOS encounters an error and stops, but where can I find to what error the 8 vibs code is related?
Any help, resolved identical story or information would be highly appreciated.
bootloader is work ?
Hi, thanks for your reply,
Can't exactly tell you if the boot is summarized before or after a bootloader starts.
From my point of view, it seems that he freezes on some BIOS check.
I tried to boot in both normal mode and hard reset but he freezes even before the screen is loaded. He only starts to vibrate (makes a little noise) than nothing.
I hope it's a hardware problem not some junky app that damaged the BIOS (if any)/xSPL so that I can even try to use my guarantee hoping that they will not know what kind of OS I have on it.
Regards
I've had the same issue but I think mine vibrated 7 times. After pulling the battery and letting it cool a few min it fired up fine.
TKhawk01 said:
I've had the same issue but I think mine vibrated 7 times. After pulling the battery and letting it cool a few min it fired up fine.
Click to expand...
Click to collapse
Yeah, seems it is some kind of an overheating issue. I've tried to cooled it down but seems that the heat already damaged something.
I've put it on reparation under warranty. Just crossing fingers they will not find out about the cooked ROM or the HSPL that was on it..
Anyway, thanks for helps guys. Will keep you updated about the resolution if any.
Regards
I too have this issue.
1 vibration when phone powers on, followed by 7 vibrations in a row (8 in total)
It seems to happen whenever I use Android for extended periods of time (15min+ Android freezes and then when resetting it occurs) and is becoming more frequent.
Worked out that it was heat related, but not sure if its worth restoring windows and returning for warranty repair. Are there any easy ways to replicate in Windows? How did you go cthulhu0dyssey with the warranty repair did it solve your issues?
Also can anyone point me into the right direction on the easiest way to restore windows on the device, if that is what I end up having to do?
SPL: 2.08.HSPL (HSPL3)
ROM: Energy Leo COM2
Radio: 2.15.50.14
Android: MCCM SE V3.4 (SD) (http://forum.xda-developers.com/showthread.php?t=841644)
mullaly said:
I too have this issue.
1 vibration when phone powers on, followed by 7 vibrations in a row (8 in total)
It seems to happen whenever I use Android for extended periods of time (15min+ Android freezes and then when resetting it occurs) and is becoming more frequent.
Worked out that it was heat related, but not sure if its worth restoring windows and returning for warranty repair. Are there any easy ways to replicate in Windows? How did you go cthulhu0dyssey with the warranty repair did it solve your issues?
Also can anyone point me into the right direction on the easiest way to restore windows on the device, if that is what I end up having to do?
Click to expand...
Click to collapse
Would be really convenient to try helping you with this problem if you specify your ROM, Radio, SPL, Android version/type (SD/NAND).
[The Punisher] said:
Would be really convenient to try helping you with this problem if you specify your ROM, Radio, SPL, Android version/type (SD/NAND).
Click to expand...
Click to collapse
Sorry, knew I forgot something, edited original post. Another thing to add is that when it happens if I pull the battery out and wait a couple of mins it powers on fine and boots into Windows/Android with no problems.
Just thought I'd send a follow up post.
I removed Android and loaded back windows mobile. After a while it just keeps rebooting until the phone will no longer turn on until it cools down.
Heat seems to be the cause. Guess its back to the shop!
Just thought I'd add an additional comment to say I got the phone back from repair, reinstalled android and now the problem has gone away.
Update here!
Hi guys,
Same here, Leo came back form the repair (completely new hardware + SPL 3.03) saying that there was an known issue with one conductor. Whatever...
Was glad to find out Cotulla rolled-out HSPL 4 so I can finally enjoy Android from internal memory, though I hope overheating issues were solved 'cos I don't think they'll give me a warranty repair for the 4th time ...
Hey guys this is my first post in the forums, and an unfortunate one at that !!
First of all I'd like to say thanks to anyone who can help a sister out , and thanks to all the people who contribute to XDA and it's awesome community.
Here is the issue, I was trying to switch the TP2 from Sprint to T-mobile services, followed directions as said and now the phone will not turn on at all.
However the phone is still being detected in device manager as an unknown device and it says Qualcomm CDMA technologies msm. I have tried installing the driver, with no results.
It will not go into boot loader, and it will not hard reset, I've tried every combination of pushing buttons I can think of, even the small little reset button.
Is this phone bricked?
Or is there a miracle that I can get it to work properly again?
EDIT: The strangest thing is that if the battery, sim, and sdcard are out the phone led will blink for a split second when connected usb to pc or a charger.
Okay,
I just got this HD2 as a replacement two weeks ago and was doing fine except it was going dead each night- so they sent me a new battery.
I put in the battery this morning (54% chg) and was syncing/charging the HD2 when I got the message that due to some server problem (I don't even use a server) the entire phone would have to be re-synced. It happedned on my other phone some but not yet on this one. When I deleted the PC from Activesync, the phone looked like it did a hard reset, opening screens about keyboard etc, came up and no programs were apparent. When I looked at programs list, they were still there so I started executing them and they woulset back up.
On reset for one of these the HD2 got stuck at the second "stick together" screen, the one after the radio info had gone. I've tried pulling the cards, battery plugging it in, checked the battery pins, etc but it will not get past the Stick Together screen. I've seached myself blue but cannot find anything similar.
Any assistance would be GREATLY appreciated.
Thank you,
OZ
1. Send it back if possible
2. Hard reset via volume keys - have you tried?
3. Flash new rom (stock or custom)
Give em a try!
Sent from my HTC HD2 using XDA App
Yeah sounds like you need to do a hard reset.if this does not fix your problem flsh a new ROM.
Had to Master Reset...
Thanks you very much for your help.
I finally did a master reset using the buttons as recommended. No further toubles so far, but I have no idea what caused it to begin with...could happen again.
Considering a new ROM for sure. I've liked this stock T-mo more than I thought as I formerly did the ROM-a-week thing with previous phones.
The Voice command and random volume problems are the only real issues I can think of that would cause me to try a new one, but they are bad enough that I am looking. Any suggestions?
OZ
DisneyF1 said:
Thanks you very much for your help.
I finally did a master reset using the buttons as recommended. No further toubles so far, but I have no idea what caused it to begin with...could happen again.
Considering a new ROM for sure. I've liked this stock T-mo more than I thought as I formerly did the ROM-a-week thing with previous phones.
The Voice command and random volume problems are the only real issues I can think of that would cause me to try a new one, but they are bad enough that I am looking. Any suggestions?
OZ
Click to expand...
Click to collapse
1. Remove the battery cover.
2. Remove the battery
3. Waiting for 5-10 minutes
4. Put the battery on.
5. HTC HD2 will Boot to W.M 6.5 nomarl.
Notes: Recommend you use HTC Default instead HTC Sense . HTC HD2 will works please.
Goodluck !