Alright, so here's the deal. I came into possession of a Euro HD2 recently. I have been using my personal TMo HD2 for a year or two. The problem with the Euro one I was given is that it refuses to boot past the splash screen. Here's a breakdown of everything I've tried so far to restore it.
The device boots into the bootloader without any problems. I initially loaded HSPL 3.03 onto it. It was originally on SPL 2.08. I've done a task29 on it several times with the RUU and device reporting it as a success. After this, I've also flashed a few radios to make sure the radio partition was fine. When trying to flash a ROM, it will either finish all the way and then boot to the secondary splash, where it stops booting, or it stops the flashing process at 3%.
I'm thinking that the NAND may be corrupted, but I'm not entirely sure. I don't have access to JTAG, so that isn't an option. If I can't fix this one, then it's not a big deal. I'll just scrap it for parts. It would be nice to have a second HD2 to sell or give to a dev, or even to use as a backup.
The bootloader reads as follows
PB81120 HX-B3
SPL-2.08.HSPL 8G XE
0x05
CotullaHSPL 0x30
It will not accept a ROM image via SD. I can see the screen flash to the gray SD loading screen for a split second before it returns to the RGB bootloader. Currently using a 16GB SD card. I'm going to use a 1GB card in a few minutes to check that the size isn't an issue.
SD flash needs 4gb or smaller card
samsamuel said:
SD flash needs 4gb or smaller card
Click to expand...
Click to collapse
Sorry for the late reply. I had to acquire a smaller SD card. I've just used a 1GB microSD card. The update seems to have gone through. It hangs at gray screen where it says UPDATE SUCCESSFUL. I left it there for 10 minutes. On my 1024Leo, it always reboots on its own after this. I had to pull the battery on this one to make it reset. Then it does the same thing as before where it just hangs at the splash screen when I try to boot it normally.
Any other suggestions I might try before ordering a replacement board?
Does it vibrate before it gets stuck and feel hot?
5800xm_user said:
Does it vibrate before it gets stuck and feel hot?
Click to expand...
Click to collapse
It vibrates while powering on, but does not move past the primary splash screen. It does not heat up any noticeable amount.
this might sound crazy/silly but freezer the phone for couple min and see if that will work or freeze it and reinstall the rom. I had that issue with my second HD2 were I HSPL, radio, maglr & flash rom, reboot and would get stuck at splash screen. Searched & searched and found a thread with a member with the same problem I had and resolved it by using ice pack while installing the rom. I gave it a try and it worked for me.
5800xm_user said:
this might sound crazy/silly but freezer the phone for couple min and see if that will work or freeze it and reinstall the rom. I had that issue with my second HD2 were I HSPL, radio, maglr & flash rom, reboot and would get stuck at splash screen. Searched & searched and found a thread with a member with the same problem I had and resolved it by using ice pack while installing the rom. I gave it a try and it worked for me.
Click to expand...
Click to collapse
Hmmm.... That does sound crazy. Lol
So, you mean you put it in the freezer or under an ice pack while flashing or before?
What temperature does the phone have while you flash it? I had an HD2 hat always got stuck flashing. It suffered from freezings due to overheating, and during flashing room temperature was enough to kill it. I put it in the fridge for half an hour and was able to flash it back to stock then(through sd). Got it replaced from my provider.
Sent from my NexusHD2 using XDA App
jacket08 said:
What temperature does the phone have while you flash it? I had an HD2 hat always got stuck flashing. It suffered from freezings due to overheating, and during flashing room temperature was enough to kill it. I put it in Thema fridge for half an hour and was able to flash it back to stock then(through sd). Got it replaced from my provider.
Sent from my NexusHD2 using XDA App
Click to expand...
Click to collapse
I guess it couldn't hurt. It's just a spare device for me anyway. I didn't notice any heating up on the device at all during flashing this one.
Upon further inspection, I believe this might actually be a T-Mobile 1024Leo based on the model numbers being the same on both my personal TMo HD2 and this dead one. Someone did replace the screen on it at some point.
i put the phone on top of the ice pack while flashing
5800xm_user said:
i put the phone on top of the ice pack while flashing
Click to expand...
Click to collapse
I don't have an ice pack handy, but I did throw it in the freezer for about 30 minutes. I then took it out and put it on a pack of frozen okra. It's flashing via SD right now. Hopefully it actually boots this time...
You have got to be kidding me.......
It worked....
I honestly cannot believe that this just happened....
the flash worked when chilled = good! that's great news.
the flash worked when chilled = oh no! that's terrible! you (almost certainly) have failing hardware.
Fingers crossed it was a one-off corruption that is now fixed, but if i were you id get some rom working and then stay away from flashing anything.
samsamuel said:
the flash worked when chilled = good! that's great news.
the flash worked when chilled = oh no! that's terrible! you (almost certainly) have failing hardware.
Fingers crossed it was a one-off corruption that is now fixed, but if i were you id get some rom working and then stay away from flashing anything.
Click to expand...
Click to collapse
Well, it's just a backup device. I did confirm that it is the 1024Leo and not the 512 model. I'm going to see if I am able to flash again now. If it hangs again, I might just give it away to someone. We'll see. I might be able to score a TMo unit with a broken screen for cheap and repair this one. Thanks for the help, guys.
Ugh. Back to square one. It is certainly hardware related. I had it sitting next to me plugged in to my laptop. It rebooted to the splash screen again and is now stuck. At least I know how to fix it.
Alright, so I made some time to open this thing up. I found that there was no thermal tape left on the inside above the heatsink for the CPU. I ordered some small extra thermal tape that should arrive in a few days. If it helps at all, I'll update the thread.
I'm not particularly optimistic about this solution, but the alternative is to superheat the CPU to reconnect the disconnected contacts. I'm going for the safer, simpler, and cheaper solution. If this doesn't work, then I will probably just purchase a damaged HD2 and swap the parts.
Here is a link to a similar thread in which they discussed possible solutions to your problem. I hope it helps.
I read that reheating the cpu might work with adding thermal compound to cool it might work. I was gonna do it but i need to buy screen/digitizer first before I open it. Glad it worked out
jacket08 said:
Here is a link to a similar thread in which they discussed possible solutions to your problem. I hope it helps.
Click to expand...
Click to collapse
Yep. I saw that thread last night. I added some thermal paste to the CPU, but didn't notice a change. Reheating the CPU would be the way to fix it. It's kind of along the same lines as the Red Ring of Death on the Xbox 360. The CPU got so hot at one point, that the solder points to the board were terminated. Cooling the board shrinks the spaces, allowing for the contacts to touch again and work until it reheats.
I'm probably just going to get a replacement main board.
5800xm_user said:
I read that reheating the cpu might work with adding thermal compound to cool it might work. I was gonna do it but i need to buy screen/digitizer first before I open it. Glad it worked out
Click to expand...
Click to collapse
Yea, adding thermal compound helps a bit. It lasts about 40-60 minutes longer than without it. It isn't a permanent fix, though. Once it gets this bad, replacing the board is the safest method to do. Cooling it down will give you enough time to backup your data to transfer over to another device or board.
Related
Guys, I need a bit of advice please.
After an accidentally botched radio install (phone fell and disconnected from USB whilst flashing), my HD2 won't boot. It gets stuck on the multi-coloured 'initial screen' (for want of a better expression) with 'SPL-1.42.HPSL XE CotullaHSPL' on it.
I'm looking to do one of two things, either rescue it, or, PREFERABLY kill it completely so that the device does not even boot to that screen. I know that sounds like a strange preference, but that would be ideal for me. Have you got any suggestions at all guys?
If you want to send it back and get a new one, then you definetly have to remove HSPL. Get HSPL2 and try to flash 1.42.0000. If it works, your problem is solved! Simply take it to customer service, complain about it not booting all of a sudden and you`ll either get a new one or get yours fixed.
However... if you fail removing HSPL and have no other option available, try and microwave it, literally. Put it in a microwave oven until it refuses to boot, then take it back to customer service complaining about how it suddely stopped working.
Best of luck!
Quite LITERALLY put it in the microwave and turn the microwave on?? For how long? Won't it just 'melt' the innerds, or blow up?
Yep. I did this to mine in 10 second intervals. The first time nothing happened, it just got hot. The second time, the vibrations stopped working. The third time nothing. The fourth time the screen started to fail (but STILL booted into the bootloader). The fifth time it only booted with a white screen and I stopped, as I had acheived what I wanted and the screen was already pretty damaged.
Thanks, a very, er, interesting suggestion. However I want the phone to look the same, i.e undamaged! But be bricked. If it's not possible, then I'll have to try and rescue the poor thing .
Best decision you could take. Hope you succeed!
spireite_uk said:
Guys, I need a bit of advice please.
After an accidentally botched radio install (phone fell and disconnected from USB whilst flashing), my HD2 won't boot. It gets stuck on the multi-coloured 'initial screen' (for want of a better expression) with 'SPL-1.42.HPSL XE CotullaHSPL' on it.
I'm looking to do one of two things, either rescue it, or, PREFERABLY kill it completely so that the device does not even boot to that screen. I know that sounds like a strange preference, but that would be ideal for me. Have you got any suggestions at all guys?
Click to expand...
Click to collapse
Does it show USB on the bootloader(multi-color) screen?
If it does you can flash a new radio/rom and maybe fix it ...
Or Flash from SDcard
I've managed to flash it to stock 1.43 from SD card, which appears to have also removed the HSPL. This is a win. However, I would still like to brick the phone so I can get a brand new replacement... I really could use a sure fire (but safe, and does not cause hw damage) brick method.
hspl, task29, remove hspl. you`ll get a white htc logo screen without the ability to enter bootloader.
However, I would still like to brick the phone so I can get a brand new replacement... I really could use a sure fire (but safe, and does not cause hw damage) brick method.
A friend (and yes - it was actually an friend and not me!) allegedly did this:
He took the socket from the end of an extension lead, put the plug into the mains socket and then VERY CARFULLY and very briefly touched the bare Live and Neutral wires onto the battery terminals in the phone.
240V into the circuit board apparently did the trick
**** Disclaimer ****
I think he was very silly to do this cos he could've hurt himself so please don't follow his example!
**** End Of Disclaimer ****
Hmm, yes, a method that doesn't involve microwaves or 240 volts would be preferable .
spireite_uk said:
I've managed to flash it to stock 1.43 from SD card, which appears to have also removed the HSPL. This is a win. However, I would still like to brick the phone so I can get a brand new replacement... I really could use a sure fire (but safe, and does not cause hw damage) brick method.
Click to expand...
Click to collapse
This kind of talks (insurance fraud) is illegal.
Thread closed.
Ive had 2 HD2's and its been the same problem for both.
No matter what rom i use on my hd2 it ALWAYS freezes(I was having the same issues with my first hd2 but eventually the screen on it stopped working and i sent it back for warranty and got a new one)
Ive flashed 2 other hd2's that belong to some friends and i did the exact same thing to their phones that i did to mine and they dont have any issue.
I dont know what to do and why am i the unlucky one
Please XDA Community i come to you for Guidance! I know this phone can be amazing but why is it being so stubborn!
Can it be SD related?
Does the area beneath the battery shell, behind the phone, feel particularly hot? If so, it's likely overheating (HTC calls it a current leakage... something?) and if you're under warranty you may wish to send it back.
Otherwise, there are fixes (suck as devising your own extra heatsink, reflowing the solder).... but it's non-trivial.
Does it freezes while using any particular applications, and what happens when it freezes???? I mean does it get to normal by itself or you have to pull the battery out and restart your HD2.
I am asking this because I was also having the same issue with my previous HD2, and then I came across this post
http://forum.xda-developers.com/showthread.php?t=1189544
which explains a lot about bad blocks which affect the android build.
DutchMaster117 said:
Ive had 2 HD2's and its been the same problem for both.
No matter what rom i use on my hd2 it ALWAYS freezes(I was having the same issues with my first hd2 but eventually the screen on it stopped working and i sent it back for warranty and got a new one)
Ive flashed 2 other hd2's that belong to some friends and i did the exact same thing to their phones that i did to mine and they dont have any issue.
I dont know what to do and why am i the unlucky one
Please XDA Community i come to you for Guidance! I know this phone can be amazing but why is it being so stubborn!
Can it be SD related?
Click to expand...
Click to collapse
dude, u need to give the detail of your problem, when and how it freezes. Cuz there are lot of problems by which a phone can be freezed up.
hstr said:
dude, u need to give the detail of your problem, when and how it freezes. Cuz there are lot of problems by which a phone can be freezed up.
Click to expand...
Click to collapse
yea sorry im just at the point where idk what else to do.
Lemme be more specific about this.
Theres times where it would actually boot up to where i can make a call but only for less than a couple minutes most of the time. There are times where i get lucky and it stays on for a good while ( couple hours ) and it'll stay that way as long as i dont use it. It freezes up starting up just about any app so i have this odd feeling it might be my sd card. But then i dont understand why the next thing happens. After i remove the battery and put it back in and boot either 1 of the 3 happens.
1) 1EFATAL HIT 1
2) Gets stuck on Go go go
3) gets stuck after go go go when rom tries to boot up.
Only thing i can do to get it to boot up again is take the battery out and leave it out for a good 10-15 minutes.
I tried Task29 and reinstalling magldr, cwr, and Rafdroid Rom and i still get the same crap
The Phone gets a little warm under the cover sometimes but its right were the micro sd is located
I'm having the same problem. My HD2 will freeze if I play games on it causing me to pull out the battery and when I boot it up, sometimes it will freeze at the MAGLDR screen, will freeze as soon as the rom boots. Right now my phone seems stable and I'm only using it for texting and making calls and nothing else for the fear of damaging the phone any further. I have a TMOUS phone btw.
DutchMaster117 said:
yea sorry im just at the point where idk what else to do.
Lemme be more specific about this.
Theres times where it would actually boot up to where i can make a call but only for less than a couple minutes most of the time. There are times where i get lucky and it stays on for a good while ( couple hours ) and it'll stay that way as long as i dont use it. It freezes up starting up just about any app so i have this odd feeling it might be my sd card. But then i dont understand why the next thing happens. After i remove the battery and put it back in and boot either 1 of the 3 happens.
1) 1EFATAL HIT 1
2) Gets stuck on Go go go
3) gets stuck after go go go when rom tries to boot up.
Only thing i can do to get it to boot up again is take the battery out and leave it out for a good 10-15 minutes.
I tried Task29 and reinstalling magldr, cwr, and Rafdroid Rom and i still get the same crap
The Phone gets a little warm under the cover sometimes but its right were the micro sd is located
Click to expand...
Click to collapse
Last question to u, that when u had ur stock windows rom in ur mobile , does any thing happened like this.
if not, then the problem is not in your mobile or sdcard, the problem is in the method u are intalling by.
1)try to get back to windows mobile.
2)install hardspl4 - 2.08 (not Hardspl3 - 2.08)
3)install magldr 1.13 (not magldr 1.11)
4)install clockworldmod recovery 3.0.0.5 (if ur rom is a cwm rom.)
5)Now flash the rom.
6)give it a try, if not any issue, then
7)push the thanks button. .. lol
hstr said:
Last question to u, that when u had ur stock windows rom in ur mobile , does any thing happened like this.
if not, then the problem is not in your mobile or sdcard, the problem is in the method u are intalling by.
1)try to get back to windows mobile.
2)install hardspl4 - 2.08 (not Hardspl3 - 2.08)
3)install magldr 1.13 (not magldr 1.11)
4)install clockworldmod recovery 3.0.0.5 (if ur rom is a cwm rom.)
5)Now flash the rom.
6)give it a try, if not any issue, then
7)push the thanks button. .. lol
Click to expand...
Click to collapse
That's actually the same thing I do.
Alright I know this might sound ridiculous but it seemed to work ( so far ). After 6 hours of trying to get this phone to work I decided to try something I saw on another thread. I got an icepack and did a complete install while having the phone on the icepack to keep it from getting warm. To my suprise it worked... I'm using my phone now with no issues yet and its been about 12 hours and it hasn't frozen yet. Although it did do a random reboot once ( I have a few bad blocks so I'm guessing that might be the reason). But Yea this worked for me some how. I'll update on any issues I get as soon as I can.
Sent from my HD2 using XDA Premium App
Same problem for me. My hd2 always freezes with any sense ui android build. MIUI and Nexus HD rom works fine.
My simple advise is... reinstal windows. And try again.
This worked for me when i started with the HD2.
Sent from my mercury using XDA App
Hi I had the same problem, but I sent my phone for repairs and it never froze again. According to HTC they just replaced the main board. But before I did that I actually flashed the official RUU (windows 6.5), and it continued to freeze, so I was quite sure it was a hardware problem. Indeed after repairs my phone didn't freeze anymore.
Sent from my HD2 using XDA App
DutchMaster117 said:
Ive had 2 HD2's and its been the same problem for both.
No matter what rom i use on my hd2 it ALWAYS freezes(I was having the same issues with my first hd2 but eventually the screen on it stopped working and i sent it back for warranty and got a new one)
Ive flashed 2 other hd2's that belong to some friends and i did the exact same thing to their phones that i did to mine and they dont have any issue.
I dont know what to do and why am i the unlucky one
Please XDA Community i come to you for Guidance! I know this phone can be amazing but why is it being so stubborn!
Can it be SD related?
Click to expand...
Click to collapse
I also had 2 x HD2 which did this.
Froze when got to hot, or if using gps or mobile data.
Sold it 2 weeks ago, now own Desire HD and it's BRILLIANT!!
So now ive been running rafdroid on the phone without an sd and it runs.. but laggy since theres almost no space left in phone and it isnt getting hot. It only gets hot when it operates with the SD inside.
anyone know anything about that?
same problem
i have the exact same issues. the phone freezes every time it boots, be it magdlr nand, sd, wm 6.5 anything. however my old hd2 had no problems at allbut i broke it changing the screen digitizer and lcd.
(the white plastic on the connector that connects the lcd and digitizer to the main board broke.)
im pretty sure the reboots are mother board related but i don't know if telling tmobile or htc that will do anything because the phone is old. (i got this other hd2 from a guy on craigslist.)
I had the same freezing problem with my HD2. After all the research I've done, none of them worked. Then i put the phone into the freezer for a minute and took an ice pack, placed it on the back of the phone where CPU is located. While holding the ice pack, I re installed the ROM and at the and freezing issues were solved. It never froze again.
I hope this solves your problem too.
oztorque said:
I had the same freezing problem with my HD2. After all the research I've done, none of them worked. Then i put the phone into the freezer for a minute and took an ice pack, placed it on the back of the phone where CPU is located. While holding the ice pack, I re installed the ROM and at the and freezing issues were solved. It never froze again.
I hope this solves your problem too.
Click to expand...
Click to collapse
I want to ask whether this cooling trial fixed freezing problem forever? suppose if u use your set for more than for hour streaming over wifi? never it got freeze again?
The best solution that you can flash back to WinMo 6.5 and run Android from SD Card.
I have the same issue... but...
Make a complete instalation with an ice pack?? Are u joking me?? It works??
well... i have not to lose... i will report if i try it...
I flashed stock rom and run android from sdcard. but when i press Haret.exe is going to HTC green logo and after restarting. some solution?
Similar problem
I have a similar problem. But with two different phones.
I bought LG Optimus One about two years ago. After a few months, some freezes appeared... I've sent it to manufacturer three times and every time they changed some parts... but nothing have helped. I've made some experiments (another battery, SIM card, MicroSD card, custom ROMs) and than I realized, that the problem occurs only while the mobile internet is ON.
This summer, my friend offered me used HTC HD2 and I bought it. He used to have Android there with no problems. After a few weeks, the freezes occured again. And again: I can surf internet all day by wifi with no problems, but when I tunr on the mobile internet (MI), the phone freezes. The back cover of battery is a bit hot, but this appears while long using the phone too without MI (without freezes).
I've tried almost everything to solve this problem: changed SIM card, changed SD card, everytime with flash of the newest ROM... nothing helped.
I'm not sure if the problems with LG OO and HTC HD2 have the same reason, but I can't believe I can buy two phones with similar problems without transfering them.
What aboutthat crazy plan of flashing with ice cooling? Does it work afret a few months too?
PS: Sorry for my English
Last night, I noticed that ROM Manager had an update in the Android market
(512mb LEO with Typhoon Cyanogenmod). I hit the update button, and walked away for a while while my phone did its thing, as usual.
I returned about 15 minutes after and noticed that my HD2 was off. I could not, however, turn it back on.
Removing and replacing the battery did not help. The phone wouldn't charge via the wall socket.
My linux PC will not detect it (I checked my dmesg log when plugging in and turning on)
I left the battery out overnight, plugged the phone into the wall, put the battery inside. No luck.
I checked the battery voltage with a multimeter, and it reads about 3.9v.
I don't think it's the battery. I think my HD2 is somehow bricked! Is there anything I can do?
It's not under warranty any more, but if I send it for repair, do you think they will deny it (because it has Android on it)?
Enlighten me with your wisdom, XDA! I don't want to say goodbye to this amazing device!
xebozone said:
Last night, I noticed that ROM Manager had an update in the Android market
(512mb LEO with Typhoon Cyanogenmod). I hit the update button, and walked away for a while while my phone did its thing, as usual.
I returned about 15 minutes after and noticed that my HD2 was off. I could not, however, turn it back on.
Removing and replacing the battery did not help. The phone wouldn't charge via the wall socket.
My linux PC will not detect it (I checked my dmesg log when plugging in and turning on)
I left the battery out overnight, plugged the phone into the wall, put the battery inside. No luck.
I checked the battery voltage with a multimeter, and it reads about 3.9v.
I don't think it's the battery. I think my HD2 is somehow bricked! Is there anything I can do?
It's not under warranty any more, but if I send it for repair, do you think they will deny it (because it has Android on it).
Enlighten me with your wisdom, XDA! I don't want to say goodbye to this amazing device!
Click to expand...
Click to collapse
Did you try holding the volume down button and turning on the phone....
It should take you to the tri colored screen...
If you get there the phone is not bricked
casemandan said:
Did you try holding the volume down button and turning on the phone....
It should take you to the tri colored screen...
If you get there the phone is not bricked
Click to expand...
Click to collapse
Yes I have tried that. Alas, nothing...
Do you recon they will fix it even if Android was on it?
xebozone said:
Yes I have tried that. Alas, nothing...
Do you recon they will fix it even if Android was on it?
Click to expand...
Click to collapse
It is a little late for me to mention this, seeing as you have sent your HD2 in for repairs all ready. But your power/end button may have stopped working, if you still had the your HD2 you could try pressing the reset button by the SD card slot and see if the device booted up then. But that is not an option now.
If all you did was update ROM Manager via the Android Market. Then it should not have bricked your HD2 in any shape form or fashion. Further more it should not have caused your HD2 to turn off either. I mean when you are running NAND Android on the HD2 you are pretty safe from bricking your HD2 because both MAGLDR, cLK, and the actual Android ROM is flashed to the ROM partition of the NAND memory and never touches the real SPL bootloader partition of the HD2.
Plus did you check your battery pins before sending it in? One might have been bent slightly. Or it could have been dirty battery terminals not allowing a good connection.
Point is I very much highly doubt your HD2 was bricked. You probably just missed judged your situation is all. As far as will they fix it? If you are willing to pay the fee they charge then yes.
T-Macgnolia said:
It is a little late for me to mention this, seeing as you have sent your HD2 in for repairs all ready. But your power/end button may have stopped working, if you still had the your HD2 you could try pressing the reset button by the SD card slot and see if the device booted up then. But that is not an option now.
If all you did was update ROM Manager via the Android Market. Then it should not have bricked your HD2 in any shape form or fashion. Further more it should not have caused your HD2 to turn off either. I mean when you are running NAND Android on the HD2 you are pretty safe from bricking your HD2 because both MAGLDR, cLK, and the actual Android ROM is flashed to the ROM partition of the NAND memory and never touches the real SPL bootloader partition of the HD2.
Plus did you check your battery pins before sending it in? One might have been bent slightly. Or it could have been dirty battery terminals not allowing a good connection.
Point is I very much highly doubt your HD2 was bricked. You probably just missed judged your situation is all. As far as will they fix it? If you are willing to pay the fee they charge then yes.
Click to expand...
Click to collapse
Hah. I don't know where you assumed that I have already sent it in. I'm the kind of person who tried to fix it myself first
Pressing the reset button doesn't do anything. I tried holding it down while inserting the battery too, and nothing,
The battery pins do not appear to be bent or dirty. I gently pushed them upright, and down, and scraped the surface gently in case there was any layers of dirt, still nothing.
I have a sibling with an HD2. I can test the batteries later.
Do you think somehow, the NAND can be worn from multiple reads/writes until it dies? It is flash memory after all, and that last write from the update could have pushed it...
xebozone said:
Hah. I don't know where you assumed that I have already sent it in. I'm the kind of person who tried to fix it myself first
Pressing the reset button doesn't do anything. I tried holding it down while inserting the battery too, and nothing,
The battery pins do not appear to be bent or dirty. I gently pushed them upright, and down, and scraped the surface gently in case there was any layers of dirt, still nothing.
I have a sibling with an HD2. I can test the batteries later.
Do you think somehow, the NAND can be worn from multiple reads/writes until it dies? It is flash memory after all, and that last write from the update could have pushed it...
Click to expand...
Click to collapse
Hmmm sorry I thought you had sent it in for repair already. Guess I miss read that, my bad man.
Yes NAND chips are rated for only a number of flashes. But that number is very high. I can not remember the exact numbers right now but hey that is what google is for right? But you did not flash a ROM you just uninstalled a app and then installed the updated version of that app. But then again I guess when you install or uninstall a app it is performing a some what similar action. Still though flashing a ROM is flashing a ROM, and installing a app is installing a app. One is a a lot different than the other.
My money is with your battery being bad. I mean like I said updating your ROM Manager should not have caused your HD2 to turn off at all. Try your sibling's battery and report back, I really hope that fixes it for you.
I haven't actually installed any Android ROM myself. But I did lots of WinMo ROM updates. What strikes me is that you installed a new ROM through the Android Market. Is that a normal procedure to upgrade an Android ROM on the HD2?
T-Macgnolia said:
Hmmm sorry I thought you had sent it in for repair already. Guess I miss read that, my bad man.
Yes NAND chips are rated for only a number of flashes. But that number is very high. I can not remember the exact numbers right now but hey that is what google is for right? But you did not flash a ROM you just uninstalled a app and then installed the updated version of that app. But then again I guess when you install or uninstall a app it is performing a some what similar action. Still though flashing a ROM is flashing a ROM, and installing a app is installing a app. One is a a lot different than the other.
My money is with your battery being bad. I mean like I said updating your ROM Manager should not have caused your HD2 to turn off at all. Try your sibling's battery and report back, I really hope that fixes it for you.
Click to expand...
Click to collapse
Hmm... I have an interesting development.
I tried my sibling's battery, and it didn't help, but what I did notice is that the phone vibrates slightly when I turn it on (as it should), but it does so very weakly. So weakly that I need to put my ear against the phone to hear it.
I don't think it's the LCD, because the charging light still doesn't work.
It probably needs a new mobo.
Any suggestions before I take it in for repair?
Cenobite_ said:
I haven't actually installed any Android ROM myself. But I did lots of WinMo ROM updates. What strikes me is that you installed a new ROM through the Android Market. Is that a normal procedure to upgrade an Android ROM on the HD2?
Click to expand...
Click to collapse
No, I didn't install a ROM on the market. It's an app called ROM Manager
xebozone said:
Hmm... I have an interesting development.
I tried my sibling's battery, and it didn't help, but what I did notice is that the phone vibrates slightly when I turn it on (as it should), but it does so very weakly. So weakly that I need to put my ear against the phone to hear it.
I don't think it's the LCD, because the charging light still doesn't work.
It probably needs a new mobo.
Any suggestions before I take it in for repair?
Click to expand...
Click to collapse
Yeah I agree with you it sort of sounds like something in the main board has malfunctioned. My guess is the processor or the NAND chip one. I would just send it in for repair if I was you. Maybe your HD2 just finally died, I know it sucks. But if you are willing to pay for the repair then you should be back up and running in no time. I am assuming you plan to send it to HTC for repair right? If for some reason they do give you a hassle about Android being on your HD2 and will not repair it. Then contact me I might know somewhere you can get a new main board put in it.
I got my HD2 back today.
Apparently it's not worth fixing...
I also got robbed today... Just my luck.
I cannot afford any other phones atm, but what do u think would make a good candidate replacement for the future? I don't think any other phone has the same kind of mod-ability and support here at XDA, but I would be delighted if you could prove me wrong.
My friend has a Galaxy S2, which is cool, but it doesn't have notification LED :/
Is there much hacking/dev on the GS2?
had not used my hd2 in two months turned it on and it was just a white screen with no htc logo, couldnt get magldr... nothing. i was able to get splash screen so i decided to try flash back to windows 6.5 to start again, i tried sd card (leoimg.nbh) method which failed aster 10% or so .. so i tried pc method that failed after 1% , tried sd card again and again then it failed saying not allowed! when i went into bootloader mode it now says spl-1.42.0000 ... hspl is gone! still i cant flash winmo rom pc\sd method and hspl 2 keeps failing also,
If i boot the phone normally i just get a triangle
If anyone has any ideas how to get anything working on this please help
i have a tmobile UK phone
"Not allow" and "get triangle" and "hspl gone" tells us that a rom you tried to flash from SD card was not the correct rom for your phones region/carrier.
When you started the flash hspl was there so the checks were bypassed,,, next hspl was removed (spl is the first part to flash) then the flash restarts, but of course hspl is gone so the checks aren't bypassed so they fail and you get a triangle.
thanks for the reply, thats what a thought but where to go from here hspl2 just wont work iv tried the correct rom from htc for uk tmobile but it dont get past 0% , the first one was from xda and is indeed different, the problem is where to go from here? this must have happened to someone else, ive been trying to get this to work for two days now and searched a lot but cant seem to find anything that will flash... any ideas??
wooooohoooo ..... had nothing to loose so tried ruu \ pc method over and over and over finally it flashed win mo 6.5 ... man windows suck lol.
if anyone having this problem this is how i did it, tried flashing the ruu using pc, got same as before it just got stuck on 0% , dissconeted the cable then i got the dissconected error with "view document" and "recovery" options i then just followed the recovery options and it flashed winmo
hopefully this helps someone!!!
thats not a good sign. Failing failing failing then working, and also flashes hanging at around 8% - 10% (your first post) often point to radio failing and/or caused by / because of overheating hardware.
If flashing problems persist, try chilling teh phone for twenty minutes in the freezer (sim battery and sd out) and if it flashes ok when you take it out, its heat issues.
samsamuel said:
thats not a good sign. Failing failing failing then working, and also flashes hanging at around 8% - 10% (your first post) often point to radio failing and/or caused by / because of overheating hardware.
If flashing problems persist, try chilling teh phone for twenty minutes in the freezer (sim battery and sd out) and if it flashes ok when you take it out, its heat issues.
Click to expand...
Click to collapse
I would try to give better advice than just saying to put it in the freezer. I can't wait to hear someone reading this and doing it. Then pulling their phone out, connecting it, and seeing it go pop fizzle as the motherboard shorts out through all the condensation that got collected on it in the freezer.
bipinsen said:
I would try to give better advice than just saying to put it in the freezer. I can't wait to hear someone reading this and doing it. Then pulling their phone out, connecting it, and seeing it go pop fizzle as the motherboard shorts out through all the condensation that got collected on it in the freezer.
Click to expand...
Click to collapse
have you not read around the hd2 section yet? there are hundreds of posts/threads talking about chilling the phone to get past a stuck flash.
Google 'xda hd2 freezer'
well....... im with you and this being hardware issue,
i did
task29
flashed radio
flashed maglder
flashed cwm 150
flashed rom (that needed 150)
all working ok for few hours put it in my pocket , then when i took it out i had a white screen
at least rebooting it i get android back. its out of warrenty now so i guess this is the end of the road for it, had this phone for over 2 years now and tbh its had a lot of stick, its had android on it from july 2010 when it was darkstone \ mattc days, i only brought it out of retirement coz me galaxy nexus is off for replacement (stock(hardware issue))
thanks for your input,
rip hd2!!!!!!!!!!!!!
samsamuel said:
have you not read around the hd2 section yet? there are hundreds of posts/threads talking about chilling the phone to get past a stuck flash.
Google 'xda hd2 freezer'
Click to expand...
Click to collapse
I've also read that in response to having the digitizer go dead and dropping the phone in water. Doesn't mean when giving the advice one shouldn't also give a few words of warning. Have you actually ever done this? I have. This advice has been around for years, and crops up across a variety of electronic devices. Try Googling "hard drive freezer fix" or "ipad freezer fix." Just because it shows up as hits on Google doesn't mean that the physics of the potential problems change.
bipinsen said:
Doesn't mean when giving the advice one shouldn't also give a few words of warning.
Click to expand...
Click to collapse
ahh see now you're touching on the dilemma as to whether one should simply offer a suggestion, or whether one should always assume the reader is stupid and offer not only suggestions, but hand-hold the reader through the process. (an assumption i despise, BTW, why should everything be aimed at the lowest common denominator? If someone offered me a suggestion, i'd take their answer and read around the subject, if someone else chooses not to do that and just blindly leap into the unknown, based on a single response, that's their lookout)
Have you actually ever done this? I have.
Click to expand...
Click to collapse
Yea, a coupla times.
This advice has been around for years, and crops up across a variety of electronic devices.
Click to expand...
Click to collapse
Pretty much anything that can overheat, in fact.
Try Googling "hard drive freezer fix" or "ipad freezer fix." Just because it shows up as hits on Google doesn't mean that the physics of the potential problems change.
Click to expand...
Click to collapse
I suspect that if you did the maths, you would find the moisture level of air in a freezer to be several times lower than , for example, the air in a sweaty pocket on a warm day, so the chances of condensation are pretty slim. Compared to all the other 'potential problems' this phone faces, condensation from being in the freezer is pretty low on the list.
Hi folks!
My HTC HD2 running on NexusHD2 ICS w/ HWA v.2.4 nand. My issue is that the phone has a random reboot issue. It won't fully boot into the OS.
Here are my attempts at this which I got from hours of searching through the forums:
1. Reflashed the rom several times.
2. Flashed typhoon gingerbread rom.
3. Task29
4. Reflashed stock rom winmo 6.5 (which still won't boot)
5. I did the fridge test. It boots successfully, but after a couple of minutes of use it goes back into a reboot cycle.
6. I tried booting ICS from SD using magldr.
I read up on bad nand blocks. Could it be that? How can I check and fix this? I also feel that this is a hardware issue (overheating cpu?) experienced by many people. I really hope it isn't because I believe there is not fix around this. Any help would be great. Thanks
If the freezer trick worked then yes it is more than likely the CPU overheating and the CPU has started to separate from the BGA matrix which in turn will not let the device boot. If you are skilled enough to try it and feel lucky you can try the the steps in this thread. But if not you will have to replace the mainboard. Sorry to have to tell you bad news.
T-Macgnolia said:
If the freezer trick worked then yes it is more than likely the CPU overheating and the CPU has started to separate from the BGA matrix which in turn will not let the device boot. If you are skilled enough to try it and feel lucky you can try the the steps in this thread. But if not you will have to replace the mainboard. Sorry to have to tell you bad news.
Click to expand...
Click to collapse
Thanks. I was worried it might be that. I saw that thread before, but that is beyond my capability. I noticed that putting it in the fridge certainly helps, but there are a majority of times that despite the phone being cool it will not boot successfully. Do you know of any other things I might be able to do? Thanks for the help!
Have you checked that the battery pins are connected correctly? If they lose contact (due to being bent out of shape or likewise) the phone won't have any power and obviously will turn off
I'm new here, but try to do a clean install a run the phone for a couple of hours/days without install any other application, see if that help
Good luck
Sent from my HTC HD2 using xda premium
The battery pin is not bent. I had the random reboot issue before and bending the pin back solved the issue. Unfortunately, it's not that again. :/ I'm thinking of waiting a couple of hours, doing a clean wipe, and flashing another gingerbread rom. Thanks for the suggestions!