are there any risks to flashing my hd2 too often? and how long does they phone usually last before it breaks down from normal use?
Sent from my HTC HD2 using XDA App
bbot3k said:
are there any risks to flashing my hd2 too often? and how long does they phone usually last before it breaks down from normal use?
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
I've flashed different WM6.5, Android, and WP7 roms probably over 100 times (not including all the radio flashes) and mine is running great with no issues. Everything works fine and I've had the phone for about a year. It's different for each individual unit but I wouldn't worry.
I've flashed mine at least hundred times with different OS-s (WM, WP7, Android SD, NAND...) and it's still 100% OK!
It's not how many times you flash it, It's how well you do the flash and how good the files are.
So if you read before you flash and you flash trusted files your device shall live for decades .
But if you always ignore the "Warnings" and flash untrusted files carelessly, your device may not see the day light of tomorrow .
-By trusted files I mean files compatible with your device and from a known developer
-By reading I mean reading thoroughly the entire post, and check the replies as well as they always contain first known issues .
- I remember a guy who has just bought his HD2, he wanted to install a custom ROM, he was told to upgrade his radio, after he did his device wouldn't boot. It turned out he flashed the incompatible radio for a Tmous .
The first thing I ever flashed was a custom 6.5 ROM on my Diamond about 2 years ago. I probably read like 20 threads and rechecked my files 10 times before I flashed the unlocker and the ROM. I've flashed custom firmware on many WM, android, and iphones since then and always read exactly what I need to do before I do it. You do see threads where someone flashed a CDMA hspl on a GSM device and vice versa or .51 radio on a tmousa HD2, or a froyo radio when not supposed to on an Evo or Incredible or something and brick their phones.
I think you'll be fine, just make sure you do the research and it's actually pretty easy not to do the stupid thing if you're paying attention.
orangekid said:
I've flashed different WM6.5, Android, and WP7 roms probably over 100 times (not including all the radio flashes) and mine is running great with no issues. Everything works fine and I've had the phone for about a year. It's different for each individual unit but I wouldn't worry.
Click to expand...
Click to collapse
I don't think that NAND Android and WP7 count, since they're flashed through MagLoader ?
kawazaki said:
I don't think that NAND Android and WP7 count, since they're flashed through MagLoader ?
Click to expand...
Click to collapse
true, you can only really brick by flashing a bad radio or bootloader.
Sorry for bringing this back up, I was about to make a new topic, but I figure lets keep it together.
Anyway arent there only so many writes that can be made to these chips? I mean, they were basically designed without this in mind. They knew for updates, but thats like twice a year, maybe 3 or 4 max. Not 100 times a month.
Please excuse me if I am wrong. But arent they basically like a SSD? Ive read they will last only so long because of the number of writes they limit then the cells die. Maybe we dont have cells, but still write times?
IDK, Im just not flashing as much as I used to, trying to keep it to a minimum. Havnt heard of anyone saying it wont flash anymore yet, so thats a good sign. Maybe the writes are in the millions?
Just some thoughts I had...
PS. I also noticed in one of my recovery.log files, it found bad blocks or sectors or something. Thats a bad sign of something...
theslam08 said:
Sorry for bringing this back up, I was about to make a new topic, but I figure lets keep it together.
Anyway arent there only so many writes that can be made to these chips? I mean, they were basically designed without this in mind. They knew for updates, but thats like twice a year, maybe 3 or 4 max. Not 100 times a month.
Please excuse me if I am wrong. But arent they basically like a SSD? Ive read they will last only so long because of the number of writes they limit then the cells die. Maybe we dont have cells, but still write times?
IDK, Im just not flashing as much as I used to, trying to keep it to a minimum. Havnt heard of anyone saying it wont flash anymore yet, so thats a good sign. Maybe the writes are in the millions?
Just some thoughts I had...
PS. I also noticed in one of my recovery.log files, it found bad blocks or sectors or something. Thats a bad sign of something...
Click to expand...
Click to collapse
That discussion is ongoing since the flashing thing ever exists... at least, updating your ROM with software from HTC or your network operator is technically the same thing...
I have read several times that those memory chips can stand like 1000 flashing processes, but I have never ever flashed any device that many times. With my HD2, I am probably, like many others in this thread, at 100 different ROMs, including WP7 and Android, in the meantime.
when you actually flash your device, you simply write some nand memory blocks with some data. The same thing happens when you..let's say..install any app to the phone's memory. theslam08 is talking about the comparison between nand memory and ssd hard drives. Yes, they are the same thing in almost every aspect.
Because i happen to have studied nand flash chip datasheets from different manufacturers i can tell you some things. The internal memory of a phone is managed dynamically. Therefore, when you flash a rom, it will not be written on the exact same memory blocks as the one before. Different apps you install will also have different positions. Also, the flash controller chip (i believe it to be an atmega 32-64 microcontroller - for hd2) also makes sure that no individual block gets overwritten more often than other.
The only things that always have the same memory addresses on the chip itself are the steppingstone, ipl-spl chain and rom headers. If they are not in the exact same position the snapdragon chip cannot read them, it's hardwired to search for them in that exact spot. So if there were a real risk to flashing, these software parts would be most vulnerable. How much? Well, if i am to quote samsung and it's KS series nand chips (about 2007 generation, now things are better) each memory block should withstand about 100.000 write operations under normal conditions. Please take note that read operations doesn't count since they don't actually change the state of the memory block. This would signal that you can technically flash the ipl/spl (or hard spl) about 100.000 times.
About the rom itself, since it's not written on the exact physical block each time (the nand memory controller prevents this) it should be possible to reflash it, in theory, some million times. Actually the flash itself is a pretty basic file copy operation, the rom content is copied to the nand memory and then it is run from there. If you think flashing can damage the phone in time.. well think of the temporary processes involved when simply ..running the phone. Various temp files are written, other files are modified, apps are installed and create their own registry settings (if we talk about win mobile) those keys generate another write cycles, the temp files yet another write cycle and so on. By comparison, the actual flash operation generates fewer write cycles then.. let's say, about 10 phone soft resets or couple of days of normal - light usage.
Don't worry about that. About nand memory performance and write cycles.. another example.. i have a 8gb cf card onto a netbook motherboard. The cf (compact flash) card, is mounted as a hard drive and the OS - windows xp, boots form it and it's been run along with some applications. That's A LOT of write cycles. However even the cheapest 8gb card - the one being used, managed to withstand one year of usage in this pattern although consumer grade cf cards are NOT made to run OS's from them. Even now the card shows no damage/corrupt blocks/dead blocks.
I've been using windows mobile pda's/smartphones for some 12 years, servicing them for about 8 years and in the later times i've begun flashing by jtag or other low level ways. I haven't yet seen a device with dead memory blocks .. that have simply died out due to wear&tear. Yes, memory can become corrupted, you can develop bad sectors, but not because of normal usage. Usually you get them if you fail a flash process (disconnect the phone during flashing of sensitive portions of the rom) or as a byproduct of CPU/MCU failure or errors.
facdemol said:
when you actually flash your device, you simply write some nand memory blocks with some data. The same thing happens when you..let's say..install any app to the phone's memory. theslam08 is talking about the comparison between nand memory and ssd hard drives. Yes, they are the same thing in almost every aspect.
Because i happen to have studied nand flash chip datasheets from different manufacturers i can tell you some things. The internal memory of a phone is managed dynamically. Therefore, when you flash a rom, it will not be written on the exact same memory blocks as the one before. Different apps you install will also have different positions. Also, the flash controller chip (i believe it to be an atmega 32-64 microcontroller - for hd2) also makes sure that no individual block gets overwritten more often than other.
The only things that always have the same memory addresses on the chip itself are the steppingstone, ipl-spl chain and rom headers. If they are not in the exact same position the snapdragon chip cannot read them, it's hardwired to search for them in that exact spot. So if there were a real risk to flashing, these software parts would be most vulnerable. How much? Well, if i am to quote samsung and it's KS series nand chips (about 2007 generation, now things are better) each memory block should withstand about 100.000 write operations under normal conditions. Please take note that read operations doesn't count since they don't actually change the state of the memory block. This would signal that you can technically flash the ipl/spl (or hard spl) about 100.000 times.
About the rom itself, since it's not written on the exact physical block each time (the nand memory controller prevents this) it should be possible to reflash it, in theory, some million times. Actually the flash itself is a pretty basic file copy operation, the rom content is copied to the nand memory and then it is run from there. If you think flashing can damage the phone in time.. well think of the temporary processes involved when simply ..running the phone. Various temp files are written, other files are modified, apps are installed and create their own registry settings (if we talk about win mobile) those keys generate another write cycles, the temp files yet another write cycle and so on. By comparison, the actual flash operation generates fewer write cycles then.. let's say, about 10 phone soft resets or couple of days of normal - light usage.
Don't worry about that. About nand memory performance and write cycles.. another example.. i have a 8gb cf card onto a netbook motherboard. The cf (compact flash) card, is mounted as a hard drive and the OS - windows xp, boots form it and it's been run along with some applications. That's A LOT of write cycles. However even the cheapest 8gb card - the one being used, managed to withstand one year of usage in this pattern although consumer grade cf cards are NOT made to run OS's from them. Even now the card shows no damage/corrupt blocks/dead blocks.
I've been using windows mobile pda's/smartphones for some 12 years, servicing them for about 8 years and in the later times i've begun flashing by jtag or other low level ways. I haven't yet seen a device with dead memory blocks .. that have simply died out due to wear&tear. Yes, memory can become corrupted, you can develop bad sectors, but not because of normal usage. Usually you get them if you fail a flash process (disconnect the phone during flashing of sensitive portions of the rom) or as a byproduct of CPU/MCU failure or errors.
Click to expand...
Click to collapse
Thanks for enlighten us
I have some bad blocks in my HD2, I always think that it is due to my excessive flashing habit. I flash almost roms avaiilable since I join xda
Now, it taken its toll. SOme nand android roms fails to flash and boot due to this bad blocks.
However, I still can flash wm 6.5 and runing SD Android without any problems
Cheers
silverwind said:
Thanks for enlighten us
I have some bad blocks in my HD2, I always think that it is due to my excessive flashing habit. I flash almost roms avaiilable since I join xda
Now, it taken its toll. SOme nand android roms fails to flash and boot due to this bad blocks.
However, I still can flash wm 6.5 and runing SD Android without any problems
Cheers
Click to expand...
Click to collapse
Well afaik, those bad blocks should be re-mapped so that they are not used when flashing roms.
Well thank you for that facdemol!
Its basically like I understood, just didnt really think the actual operation were the same for this chip and ssd. But thats cool, so it should be okay for a long time then .
As for the bad blocks, is there a way to 'chkdsk' on the nand? Do a clean up of the bad blocks or once bad they are always bad? Id like to clean those up. And no, I have never crashed a flash half way, ive only recently had some boot loops, thinking the bad blocks arent helping...
normally, the nand memory controller deploys error correction algorithms. On top of that, a technology similar to SMART (for hard disks) is used to both level out the wear of each particular memory cell and also to remove broken ones (either the ones that fail over time due to various reasons or due to manufacture errors). The MCU (microcontroller) also has a small internal memory used to keep a track on the situation of the memory blocks inside the nand chip. If for whatever reasons, some of them fail, the MCU will log this inside it's memory and also mark those sectors as "bad" thus preventing any write to them. At this stage the user won't see any problems with the NAND, yet. Once the MCU memory is full, further nand memory sectors that die out, won't be recorded and managed, therefore will appear as visible. In contrast with hard disks, were you can actually isolate those sectors and prevent them from being written, phone's don't do this, or more precisely their OS's don't support this feature. So, when you flash a phone with bad memory blocks, data will be written there but it won't be read at the next restart. So comes occasional restarts or freezes. If you're "lucky" you can get a bad memory block in the area where the ipl/spl resides. This is an end game scenario, since the ipl can't be "moved" around the nand memory.
You cannot effectively map the broken sectors of a nand memory once the mcu unit's memory is full. Those are here to stay. The only way i know involves jtag and some really fancy software tools that load a small program intro the phone's ram memory. That program runs from there and allows for a full nand memory checkup.
you probably have more chance of the god damn crappy micro usb or touchscreen breaking first
Yeah, I charge my HD2 multiple times in a day because I use it so much.
Wonder how long my phone will last. Got it brand new a couple of months ago
ive had my hd2 since it came out in nov09 and its been charged every single night bar probably about 2 weeks worth of time, and never had an issue with anything going wrong
silverwind said:
Thanks for enlighten us
I have some bad blocks in my HD2, I always think that it is due to my excessive flashing habit. I flash almost roms avaiilable since I join xda
Now, it taken its toll. SOme nand android roms fails to flash and boot due to this bad blocks.
However, I still can flash wm 6.5 and runing SD Android without any problems
Cheers
Click to expand...
Click to collapse
hey, I have a HD2 with bad memory NAND blocks and know my HD2 will not boot up but do you have any suggestions because i really do like the phone but it just won't boot?
kawazaki said:
It's not how many times you flash it, It's how well you do the flash and how good the files are.
So if you read before you flash and you flash trusted files your device shall live for decades .
But if you always ignore the "Warnings" and flash untrusted files carelessly, your device may not see the day light of tomorrow .
-By trusted files I mean files compatible with your device and from a known developer
-By reading I mean reading thoroughly the entire post, and check the replies as well as they always contain first known issues .
- I remember a guy who has just bought his HD2, he wanted to install a custom ROM, he was told to upgrade his radio, after he did his device wouldn't boot. It turned out he flashed the incompatible radio for a Tmous .
Click to expand...
Click to collapse
Is there anything you can do for that because i think i did that to my HD2 if you plz message me back because my HD2 wont boot and i really do need this phone so if you can help plz do?
If your getting bad blocks and its giving you headaches and you have zero issues with the ipl/spl then just switch to SD android builds
they might work a tiny bit slower but at least you can still use the phone happily.
My phones almost a year old now, but i did not use it for nearly 4 months coz I got a desire. Sold that on ebay and gone back to the HD2 when magldr came out. I go by 2 simple rules...
Dont flash the radio/spl if you have no bloody reason to. there's only 1 good radio and that's the normal 2.15 HSPL. the fact that those NAND blocks are so critical means dont touch unless its majorly important to do so.
Secondly, make sure you dont let any rogue processes in android go into a massive file write fit of frenzy, and disable logging in apps that log allot to internal NAND or change it to log to the SD Card.
More often your touch input will fail, or those buttons will fail.
Dont worry about abusing the daylight out of the battery, its worth $1 and can be replaced anytime, but don't abuse that precious usb port.... treat it well and blow some air into it once in a while.
1 more tip, dont use car chargers they dont filter well and the last thing you need is a high voltage surge going into the phone, instead what i did is buy a sinewave invertor and then run an ac charger from that and i get the added benefit of sometimes bring a power board and can run the kids dvd player indefinetly and charge other phones... laptops.... GPS Navman.
Related
Hi there, I have joined this Forum as I have spent the last week reading through heaps of threads, and while I have learnt a bit, I am at a point where I need some help.
I got a HTC T-Mobile HD2 for less than half price with the intention of running Android OS. I got it for this price as it has the freezing issues. I don't think it is in warranty and the box and CD didn't come with it.
I think it must be a US T-Mobile, as it has the Coming Together screen when it is turned on. Most of the time, that is all it gets to. It has a green talk button and red off button. The resets do nothing.
I have read that these phones are often returned to HTC as they are defective, they get hot and don't work. The one I got doesn't get hot. When it does boot up, it has Transformers and Transformers2 loaded into the memory. It will play but after a short time it goes black and resets.
Does this phone seem repairable? If so, please tell me where to start as I have been totally confused here.
Here is some of the details I got off it when it was booted up.
CPU Qualcomm (R)
Speed 1024 Mhz
Ram 576MB
Flash Size 1024 MB
Data Bus 32 Bit
Storage Size 689.61
Bluetooth Version 2.1/2.1 ERD
WM 6.5
OS version 5.2.21892 (21892.5.0.89)
Manilla Version 2.5.20121412.2
ROM Version 2.13.531.1 (90963)
ROM date 04/28/10
Radio 2.10.50.26
Protocol version 15.39.50.07U
Total Storage 689.61MB
Used 76.52MB
Free 613.09MB
Total Program 458.74MB
Used Program 172.52MB
Free Program 286.19
SD Card
Total 7571.20MB
Used 1419.18MB
Free 6152.02MB
Thanks for any help here.
98% of the time it's the software. Flash a new STOCK rom and see if the problem persists.
98% hardware problem, not software.
Okay will flash a new stock ram, as I have nothing to lose here. Back to searching on how to achieve this!
StarScreamx said:
98% hardware problem, not software.
Click to expand...
Click to collapse
That's quite helpful, isn't it?
My expieriences vary from StarScreamX's ones. Indeed it might be a good idea to flash the stock rom which was made for your HD2. Back in the days of WM 6.5 it solved some weird problems permanently. You might even reflash your original HSPL, only to flash the fitting version again. I repeated those steps several times, just to wipe out eventually made errors.
The other point is, that some errors occur because of certain hardware-combinations, not because of the components themselves. It might be the SD-Card or even the way you formatted it. Best expieriences I've made with using Fat32 64kb cluster size. Seemed to speed up the whole OS.
My last suggestion is to try several builds. Android can be far different from Android. For examle Sense, ADW, MIUI are all pretty good, but have their own advantages. While I first refused MIUI for its similiarities to iOS, I stuck with it before I switched to WP7 some Weeks ago.
Try the builds and take your time, there certainly is one, that runs great on YOUR hardware.
Anyway, Good Luck!
kyliekwong said:
Hi there, I have joined this Forum as I have spent the last week reading through heaps of threads, and while I have learnt a bit, I am at a point where I need some help.
I got a HTC T-Mobile HD2 for less than half price with the intention of running Android OS. I got it for this price as it has the freezing issues. I don't think it is in warranty and the box and CD didn't come with it.
I think it must be a US T-Mobile, as it has the Coming Together screen when it is turned on. Most of the time, that is all it gets to. It has a green talk button and red off button. The resets do nothing.
I have read that these phones are often returned to HTC as they are defective, they get hot and don't work. The one I got doesn't get hot. When it does boot up, it has Transformers and Transformers2 loaded into the memory. It will play but after a short time it goes black and resets.
Does this phone seem repairable? If so, please tell me where to start as I have been totally confused here.
Here is some of the details I got off it when it was booted up.
CPU Qualcomm (R)
Speed 1024 Mhz
Ram 576MB
Flash Size 1024 MB
Data Bus 32 Bit
Storage Size 689.61
Bluetooth Version 2.1/2.1 ERD
WM 6.5
OS version 5.2.21892 (21892.5.0.89)
Manilla Version 2.5.20121412.2
ROM Version 2.13.531.1 (90963)
ROM date 04/28/10
Radio 2.10.50.26
Protocol version 15.39.50.07U
Total Storage 689.61MB
Used 76.52MB
Free 613.09MB
Total Program 458.74MB
Used Program 172.52MB
Free Program 286.19
SD Card
Total 7571.20MB
Used 1419.18MB
Free 6152.02MB
Thanks for any help here.
Click to expand...
Click to collapse
I think it might be a hardware issue my Hd2 has the same issues & I jst finished restorting it back to stock so i cld snd for repair. Once its stock SPL, original ROM try running it with out an SD card, try running w/out SIM card & if you still have issued most likely ur stuck w a bad HD2
After heaps of searching and learning, interesting and rewarding when you put some effort into it, I loaded a stock ROM, removed the SD card, hard reset, it made no difference to the freezing and booting up issues.
If left for about 10 minutes the Stick Together screen got these numbers at the bottom, then it would boot up...sometimes but it always reset itself after looking intothe menu and then it would not reboot.
So I did more reading, and with my confidence up after achieving my first stock ROM flash, I thought I would try ANDROID.
I used the TUT Flashing your first ROM on Leo 1024 thread. Installed the HPSL 1.11, successfully.
Then I installed the MAGLDR program.
Then I installed the ROM - [TMOUS][LEO1024][DFT/CWM]CMYLXGO's Stock Desire HD(2)[KERNEL:MDJ 10.4OC] which seems to be the most 1024 friendly and least taxing ROM on the CPU.
It worked so far. I did the Root task as explained, although I dunno if I was needed to. But at least the phone boots up for more than 3 minutes. I give it a Hard Reset and it is now on charge.
It will not boot up if it crashes, have to wait. Maybe this will settle down after a while.
Anyhow, I love this ROM, it has made the phone SO FAST it is incredible. That is until it crashes. I LOVE the HTC HD2 phone, it is just awesome.
i dunno what to do, stick with this perhaps suspect dodgey phone, that could let me down at the most inconvienent time. What I will do is give it a chance today, after charging. It is a really hot day here, over 120F so if handles that it will handle anything. If it fails, I notice that Ebay have free insetion fees this Weekend, and I may get rid of it and let someone else have a turn at it, and just get one that is not a bad one.
Anyhow sorry for boring all the experts with my phone problems, I did try my hardest to search and learn it myself, and this is a great forum, and I am gonna keep at this with this phone now or my next one. These Custom ROM's are just awesome.
I'm glad you're finally enjoying it.
Just remember, the way you use/abuse your phone could have an adverse effect on its condition. If it gets too hot:
--try to see if you have programs running in the background.
--don't use a case if you're watching a 2hr movie through SD card (really, how's that heat going to escape?)
--watch wifi usage
--leave the phone in a well-ventilated space
...things of that nature, etc.
I'm not saying there's no such thing as hardware issue, but symptoms like those are a lot more clear-cut than a phone overheating and restarting.
In my case I'm confident its hardware related. I had mine and my wife's phones loaded with the same ROM. My phone continues to die in my hands while hers hums along with no problems at all.
So my HD2 freezes constantly. I don't have the unlock freezing issue nor the black screen freezing issue. My phone will just freeze quite constantly. Doesn't matter if I'm just doing a message, online, or it's just sitting there doing nothing. It will freeze and will have to remove the battery and restart it. I've reinstalled MAGLDR, CWM, and tried several ROMS and it still doesn't make a difference. I remove the battery and have to let it cool for around an hour just to turn it on and be able to use it for a period of time.
Any suggestions out there? Could the battery be bad? The hardware? I constantly use Task Killer and Data Eraser to make sure there aren't unnecessary programs running. I've narrowed my app collection to just the necessary ones that I need. Still doesn't make a difference. Any programs out there that would help with this issue in any way. Would repartitioning my SD card help at all. I have pretty much everything on my SD card as well so the hardware shouldn't be overloaded at all.
Any help would be greatly appreciated.
Thanks!
check here
LOADS of people are having this problem including myself.
As long as Mobile Data and Gps are OFF, I have no freezing issues.
BUT, if I turn on Mobile date or Gps, or both, then GAME OVER.....it freezes within seconds.
It's not your battery, or SD card and don't listen to the muppets who repeat themselves by saying "do a task29" coz it doesn't work.
I've tried 5 different SD card, got 2 hd2's, task29, over 100 roms, different radios etc etc.
Never used to happen on SD builds, only Nand.
if i had the cash, i'd smash my hd2 against the wall and get a Android native phone.
this aint ever gonna be solved.
matt
freeridindirtbiker said:
So my HD2 freezes constantly. I don't have the unlock freezing issue nor the black screen freezing issue. My phone will just freeze quite constantly. Doesn't matter if I'm just doing a message, online, or it's just sitting there doing nothing. It will freeze and will have to remove the battery and restart it. I've reinstalled MAGLDR, CWM, and tried several ROMS and it still doesn't make a difference. I remove the battery and have to let it cool for around an hour just to turn it on and be able to use it for a period of time.
Any suggestions out there? Could the battery be bad? The hardware? I constantly use Task Killer and Data Eraser to make sure there aren't unnecessary programs running. I've narrowed my app collection to just the necessary ones that I need. Still doesn't make a difference. Any programs out there that would help with this issue in any way. Would repartitioning my SD card help at all. I have pretty much everything on my SD card as well so the hardware shouldn't be overloaded at all.
Any help would be greatly appreciated.
Thanks!
Click to expand...
Click to collapse
Hi,
It might be worth trying to flash an original ROM and seeing if the same thing occurs in WinMo.
Have you properly formatted card? (overwrite with size adjustment)
Which rom are you using?
Does it do it on multiple roms?
Have you done a task29?
have you tried a different radio version?
TheATHEiST said:
Have you properly formatted card? (overwrite with size adjustment)
Which rom are you using?
Does it do it on multiple roms?
Have you done a task29?
have you tried a different radio version?
Click to expand...
Click to collapse
I've tried all those things. I'm using the Nexus 2 Gingerbread ROM by tytung. I've tried winmo roms, android, etc. I've done task 29 several times. Different radios as well. It doesn't make a difference at all. I found a thread that might be the culmination of it all. If anyone else is having problems like I am, take a look at this thread. It's definitely the motherboard overheating and freezing/and or shutting itself off.
http://forum.xda-developers.com/showthread.php?t=982454
Luckily, I pay insurance through t-mobile so I will be picking up a new HD2 pretty soon.
I had a similar problem, but mine came about under different circumstances. I smashed my HD2 against a wall for whatever personal reasons that you shouldn't care about, anyway, so I ordered a replacement display. When I installed the display the phone would freeze just as described by OP. I found that disabling GPS and WiFi allowed me to use it for a longer time, but if I ever so much as applied any pressure to the display (rather than just lightly touching it) the screen would freeze and sometimes it would just straight shut off until it didn't turn back on at all (this was barely the first day after installation). I opened the phone and tested, found out that the LCD flex cable had a defect to it where if it was bent (the position it's supposed to be in once the phone is assembled) the display would "short out" and with the cable fully extended no problems would be present, even after applying pressure to the display or any of the other internal components.
I'm sending my LCD back for a replacement and hopefully the new one will work fine. I've read that some LCD's cause the HD2 to freeze and I think I was unlucky enough to receive one such. I need the phone to hold on long enough until I get my contract renewal May 2012. I'm surviving on my Dream right now and I'm going through Angry Birds withdrawal...
Compatible-Bad Hardware-Insurance Questions
freeridindirtbiker said:
I've tried all those things. I'm using the Nexus 2 Gingerbread ROM by tytung. I've tried winmo roms, android, etc. I've done task 29 several times. Different radios as well. It doesn't make a difference at all. I found a thread that might be the culmination of it all. If anyone else is having problems like I am, take a look at this thread. It's definitely the motherboard overheating and freezing/and or shutting itself off.
http://forum.xda-developers.com/showthread.php?t=982454
Luckily, I pay insurance through t-mobile so I will be picking up a new HD2 pretty soon.
Click to expand...
Click to collapse
I have similar issue. Could use advice. Please.
My HD2 is about a year old. Decided to try android on the sd.
Device: HTC HD2 TMOUSA
Radio: 2.10.50.26 (Original) NOW flashed to 2.15.50.14
SPL: 2.10.xxxx (Original) NOW HSLP 2.08.0000
Android Rom: SD AmeriCanAndroid AOSP HD2 GB234 CM71
WM Rom: 2.13.531.1 (Original)
ACA seemed ok but would freeze randomly. So I flashed the radio to the 50.14. Seemed a little better but still a few freezes in android. Thought I would try the partition to improve the sd card performance. can't tell if it helped or not to many freeze ups to use android during the day. NOW my winmo side it giving me random reboots. It gets hot reboots, especially bad if using gps. I know overheating is part of the issue because during the middle of the day in my car without A/C it is terrible.
I also have an OTTERBOX Defend which has kept the phone looking great but is a really pain with on all the battery removal with the freeze ups.
I have read that this can be a mainboard issue, but how can I tell if it is or not?
Could the radio and winmo rom be incompatible?
Should I flash the winmo rom to a more compatible android rom?
Should I send it in since I have TMO insurance? (Anyone know if there is a deductible if you didn't lose the phone?)
I have also noticed the on the winmo side it reboots less if I turn htc sense off.
Not sure if I should go back to a different radio or send it in?
Are the insurance replacements refurbished or new? do they have the same issue?
Thanks for any expertise you care to share.
Had similar problems with Tmous HD2. Problems were really bad in Winmo; aca worked somewhat better. Read forums, tried standard "solutions". With time the problems got to the point where the HD2 would not boot unless it had been placed in the refrigerator for 5 minutes.
Did T-Mobile warranty exchange in April. Replacement was refurb (arrives without battery or sd card, used old one), but looked fine. Had a week to test "new" phone, before sending the old one back. Replacment phone works much better. In Winmo, gps, videos, sense no longer cause reboots; aca also works great.
Hope this helps...
TheATHEiST said:
Have you properly formatted card? (overwrite with size adjustment)
Which rom are you using?
Does it do it on multiple roms?
Have you done a task29?
have you tried a different radio version?
Click to expand...
Click to collapse
Exactly as my post from a few days ago predicted..."task 29"
FFS.
So... uh... I know you're disappointed, maybe even angry that with all those FAQs there are still some guys who don't understand everything.
I bought my HD2 today (or maybe I got it today, but ordered it few days ago). It was used before, but as far as I could tell, nothing was done there - stock ROM, SPL 1.42.000, radio 2.07.51.22_2. The first thing I wanted to do was to install Android, so I read some guides here, HardSPL'd to 2.08.hspl, then I saw that I'd have to upgrade my radio. BUT! I've read that you can brick your phone by installing wrong radio and there was no answer to...
FIRST QUESTION: What radio(s) can I upgrade to without fear of bricking my precious?
SECOND QUESTION: What are the differences between radios and why the one with top number isn't the best?
THIRD QUESTION: When I'll eventually install new radio, how do I know if it's worse or better than previous one? Is there a fast and efficient way to check it? I don't use my phone as a calling device too often (average 1 call and 0.5 sms a day), so it would take ages to detect all flaws by using it as always.
And without going into any details, can you say - why would I install Android on SD? From what I've heard and read, NAND version is faster (and I haven't heard anything else).
Oh. Please, don't kill me because I'm a newbie I have some experience with jailbreaking iPods and installing ROMs on HTC Artemis, but with HD2 things I'm for now like "I'd better not touch it, I paid so much for this phone, so I don't want to brick it ".
If something is unclear, just ask.
1) If you have a tmobile HD2 you can flash any radio with the third set of numbers being .50 as long as it's above 2.08.50, you cannot flash any radio where those numbers are .51.
example:
2.10.51.xx = brick
2.07.50 = brick
2.11.50 = safe
etc...
If you do not have a tmobile US version, you're safe with the radios I stated above not to flash.
For Android, only use 2.10.50 and above, I've had nothing but problems with older radios.
2) They communicate slightly differently with your hardware. The "newer" might have better battery life for some, or better reception with Android but not WP7. The truth is no one knows exactly what aspect of which radio is better, you have to just flash them and find out. Newer does not always mean better (although I do like 2.15.50 the most).
3) There's no fast way to check this, other than maybe on the 2.11.50 radio you had only Edge with terrible speeds, then flash 2.12.50 and suddenly you see H everywhere (I've had that happen). Also you might see more bars immediately. For battery life you can have Current Widget (Android) which will show your battery drain. One radio might show 2ma and the other might have 10ma for some reason, obviously the 2ma will give you longer battery life (this is in standby)
But there are so many factors. Which ROM, kernel, mod, apps all effect stuff on your device. Different radios work better in different regions too.
What I would recommend is use 2.15.50 for Android and 2.12.50 for WP7
But play around and see what you think!
Spaqin said:
So... uh... I know you're disappointed, maybe even angry that with all those FAQs there are still some guys who don't understand everything.
I bought my HD2 today (or maybe I got it today, but ordered it few days ago). It was used before, but as far as I could tell, nothing was done there - stock ROM, SPL 1.42.000, radio 2.07.51.22_2. The first thing I wanted to do was to install Android, so I read some guides here, HardSPL'd to 2.08.hspl, then I saw that I'd have to upgrade my radio. BUT! I've read that you can brick your phone by installing wrong radio and there was no answer to...
First, Congratulations
FIRST QUESTION: What radio(s) can I upgrade to without fear of bricking my precious?
Depends, is your device the european version or the T-Mobile's Version? (Are the Talk and Hang-up button Coloured with green and red? and do you see "T-Mobile"'s logo ontop of your device?)
The radio's that supposedly won't kill your device must meet those two conditions:
1- The radio must be above 2.08 .. (2.09 or 2.10 .... 2.15)
2- The radio SHOULD NOT have "51" in it's tag (i.e. this radio "2.04.51_55_8 will brick your device )
SECOND QUESTION: What are the differences between radios and why the one with top number isn't the best?
Because Radio's efficiency depends on where you live, some people use the latest and it gives them very good reception .. others on different places might get poor receptions.
THIRD QUESTION: When I'll eventually install new radio, how do I know if it's worse or better than previous one? Is there a fast and efficient way to check it? I don't use my phone as a calling device too often (average 1 call and 0.5 sms a day), so it would take ages to detect all flaws by using it as always.
Well, I don't think there is another way beside monitoring your reception and your data losses .. Just keep an eye on your signal bar and/or your call (drops) (despite cLK/PPP)
And without going into any details, can you say - why would I install Android on SD? From what I've heard and read, NAND version is faster (and I haven't heard anything else).
Some people prefer to have Windows Phone 7 on their NAND, yet they want to play with Android sometimes so it becomes a win win . Furthermore, SD cards are easier to deal ith in term of modifications.
I don't think NAND builds are faster, both have same speed (you just have to pick the right rom for you )
Oh. Please, don't kill me because I'm a newbie I have some experience with jailbreaking iPods and installing ROMs on HTC Artemis, but with HD2 things I'm for now like "I'd better not touch it, I paid so much for this phone, so I don't want to brick it ".
(we won't kill you )
If something is unclear, just ask.
Click to expand...
Click to collapse
Omg, I need to recharge my battery
EDIT:
Well, Orangekid was faster, i think
Thanks for the replies, guys!
My device is the european version (no coloured buttons and no logo, bought at Polish store with no simlock). So it looks like I should be safe with all radios, right? There's no way that something may screw up by itself? As I said, my HD2 isn't new and I don't know much about device's history. Is there something I should check?
Sorry if I ask too many questions... I'm just amazed with the phone (everything else seems to be so little now and I wouldn't want to break anything.
About NAND and SD versions of Android - well, I've heard that you need to wait very long to wake up the phone from standby (I mean it's not instant definitely) on SD version, but with playing with NAND you could break something more easily.
Spaqin said:
Thanks for the replies, guys!
My device is the european version (no coloured buttons and no logo, bought at Polish store with no simlock). So it looks like I should be safe with all radios, right? There's no way that something may screw up by itself? As I said, my HD2 isn't new and I don't know much about device's history. Is there something I should check?
Sorry if I ask too many questions... I'm just amazed with the phone (everything seems to be so little and I wouldn't want to break anything.
About NAND and SD versions of Android - well, I've heard that you need to wait very long to wake up the phone from standby (I mean it's not instant definitely) on SD version, but with playing with NAND you could break something more easily.
Click to expand...
Click to collapse
NP, better to ask a bunch of questions than brick your device.
you do not have a tmobile US version, so those .51 and below 2.08.50 radios will not brick your phone, however Android doesn't like anything below 2.10.50 and does some stupid ****.
as far as wake-up from SD lag, doesn't happen on my SD rom, so I wouldn't worry about that. This ROM:
http://forum.xda-developers.com/showthread.php?t=957652
is awesome, and performs just as well or better than any NAND rom I've used. Since I use WP7 in NAND, I stick to that ACA SD ROM and I love it.
Marvlesz said:
The radio's that supposedly won't kill your device must meet those two conditions:
1- The radio must be above 2.08 .. (2.09 or 2.10 .... 2.15)
2- The radio SHOULD NOT have "51" in it's tag (i.e. this radio "2.04.51_55_8 will brick your device )
Click to expand...
Click to collapse
#2 isn't the best example because even if that radio was .50 it would brick a tmous device.
orangekid said:
#2 isn't the best example because even if that radio was .50 it would brick a tmous device.
Click to expand...
Click to collapse
I know
.04 and .05 can have .50 yet brick devices .. that's why I said above .08
thnks !
Marvlesz said:
I know
.04 and .05 can have .50 yet brick devices .. that's why I said above .08
thnks !
Click to expand...
Click to collapse
No worries, good write-up.
The more often we tell people this stuff hopefully the less "oh **** I bricked my tmous hd2" threads.
So ALL the radios should work? Does updating radio require WinMo, or can it be done without it?
Anyway, it looks like I won't bother much with NAND Android. I'll just leave WinMo 6.5 for now, maybe later I'll be able to understand this magldr thing (for now all the descriptions are like 'it's something that allows you to boot other OS from NAND', but I have no clue how does it work).
Spaqin said:
So ALL the radios should work? Does updating radio require WinMo, or can it be done without it?
Anyway, it looks like I won't bother much with NAND Android. I'll just leave WinMo 6.5 for now, maybe later I'll be able to understand this magldr thing (for now all the descriptions are like 'it's something that allows you to boot other OS from NAND', but I have no clue how does it work).
Click to expand...
Click to collapse
Yes, you're safe from radio brick, but i wouldn't bother with any radio below 2.10.xx
You can flash the radio from HSPL (hold the volume down button and power on) or from WinMo with an activesync connection.
MAGLDR is a second bootloader that sits on top of HSPL and allows you to:
1) boot WP7
2) boot Android recovery
3) boot Adroid NAND
4) boot android SD without having to boot winmo first
5) play tetris from your bootloader
Flashing MAGLDR is very safe and very easy, same process as flashing a radio. You can't do anything with or from magldr that will brick your phone because it loads after HSPL so worst case is you boot into HSPL and flash stock or reflash magdlr.
about nand or sd:
some people like to dual-boot either winmo or Android. This will give you the option to run one or the other. If you decide to go the sd route then you might want to check a program called RunDroid found here. It makes it make the process of booting different builds a lot more simple and easier I feel.
About radio:
I know a lot of people seem to say stay above 2.10 but I've seen a small increase using 2.08.50. This will/can be different for you so i would suggest to try them to see what gives you the best signal. Start with the newest or maybe even 2.15.50.
About testing signal strength:
For a good way to get a fairly accurate reading on signal I would go into settings, about phone, then network. Look at the signal you have, I would suggest to leave your phone in one place and don't try to move it. Get the readings maybe 3-5 times over a few mins, I'd think the longer the better. Then flash a new radio. The closer to a positive number the better. Low signal for me normally means around -108 while good for me is around 89. (It's normal to show negative when you have poor signal.) This is a little more accurate I feel then trying to see how bars you have. Infact one radio over another may only show a small increase and not enough to generate a full bar so just play around and see what works best for where you live.
Every damn time I reboot this hand set I loose everything on the memory card....what a crock of dog doings......
Hope to god the OTA comes soon and fixes this as I have another 22 months of this before I can go back to HTC and a decent phone...
I knew I should have waited for the sensation or even the Galaxy s2
so very peeved now
UNless anyone knows how to stop it formating the memory on every boot I am going to have to resurect my Hero, at least that "just works"(tm)
are you talking about a sd card you bought? if so plug it into a pc and do a FULL format on it either it somehow got corrupted or the card took a crap, or the phone doesnt like that brand of sd card if you are talking about the internal memory on the phone itself either try and reload orginal firmware and if that doesnt do it send it for warranty
Internal memory NOT SD card....I arent that thick to muddle them up
It isnt like it's every time I reboot, just sometimes......
I assume you mean factory reset for "reload firmware" it's a thought but one I rather not have to mess about with....mainy cos I cant remember the motoblur login password AND when you press "fogoten password" it tell you to phone custard services...but with no helpful number or who's custard services to ring (moto or Orange).....
As for Warantee, going to be tricky as I arent in the UK for another 7 weeks (arent on land for another 6 come to think about it!)
LOL, i am sorry but that's a really really funny issue.
Anyway, whatever is happening - it's not the Atrixe's fault.
I have never seen anyone having an issue like this.
I have took the first week to set / mod my Atrix up according to my needs (running hand made mod of a stock ROM), and for me it's the perfect phone I ever dreamed about.
Anyway, back to your problem, have you done been doing some modding?
Try to remember what you did with the phone exactly before the problem started?
deech said:
Internal memory NOT SD card....I arent that thick to muddle them up
It isnt like it's every time I reboot, just sometimes......
I assume you mean factory reset for "reload firmware" it's a thought but one I rather not have to mess about with....mainy cos I cant remember the motoblur login password AND when you press "fogoten password" it tell you to phone custard services...but with no helpful number or who's custard services to ring (moto or Orange).....
As for Warantee, going to be tricky as I arent in the UK for another 7 weeks (arent on land for another 6 come to think about it!)
Click to expand...
Click to collapse
Hi,
Plug phone into PC.
Format (not quick) both drives that show up in "my computer", or "computer".
Cheers!
Just so you know, you can skip MotoBlur. I bought a second hand Atrix and the guy left his MotoBlur account in, so I had to. Search around to find the instructions if you're really interested.
if you have to just use another email address and register for motoblur again
Right I'll try formatting it AGAIN...
The only thing I did (a long time ago) was use ginger break but when part 1 of the Orange OTA came out it killed GB so never bothered again, at the time I though i had lost stuff but then hadnt......Most anoying. Rebooted today and it lost all the internal memory again, but not the SD card.
Bloody anoying if you cant trust your phone to power cycle without back up the memory first...about as much use a t*t's on a frog
Anyway will try to format both cards (again) and see if that helps!
deech said:
Right I'll try formatting it AGAIN...
The only thing I did (a long time ago) was use ginger break but when part 1 of the Orange OTA came out it killed GB so never bothered again, at the time I though i had lost stuff but then hadnt......Most anoying. Rebooted today and it lost all the internal memory again, but not the SD card.
Bloody anoying if you cant trust your phone to power cycle without back up the memory first...about as much use a t*t's on a frog
Anyway will try to format both cards (again) and see if that helps!
Click to expand...
Click to collapse
If i were you i'd factory restore first.
I doubt the problem is in the SD card needing to be formatted.
however formating the SD card has thrown up some oddness....2GB card reporting in as 1.4GB when formatting in WIndows, so got phone to format the card it self, then all of a sudden it reports 1.89GB (which is close to enough 2GB), so now re-formatting again in windows and try again.....
Failing that it's factory reset time, which will have to wait till I get back to UK as I cant DL my apps on this connection (way to limited satalite internet!)
Thanks all, and ayone with any other ideas would be muchly appreciated
deech said:
however formating the SD card has thrown up some oddness....2GB card reporting in as 1.4GB when formatting in WIndows, so got phone to format the card it self, then all of a sudden it reports 1.89GB (which is close to enough 2GB), so now re-formatting again in windows and try again.....
Click to expand...
Click to collapse
Regardin the bold part -it's showing everything correctly. 2GB in reality is around 1.89GB - that's a common marketing lie for selling flash memory and hard drives.
Yeah I knew / figured that..hence the comment near enough...and considerabley closer than the 1.48 it was reporting initially...maybe GB left somthing behind.....Odd, only used it once then the OTA pre-update thingy that Orange sent broke it, so i didnt bother again, and probs wont, still miffed about it though!
Plan to reboot it a few times over the next few days and see if we have a fix or not, there aint alot I can do from here (on a ship in the middle of nowhere!) hey and ho...
thanks all
xploited said:
Regardin the bold part -it's showing everything correctly. 2GB in reality is around 1.89GB - that's a common marketing lie for selling flash memory and hard drives.
Click to expand...
Click to collapse
This statement is 100% wrong!
Instead of explaining myself, please follow this link:
http://www.reely.com/darren/Guides/Reported%20Hard%20Drive%20Capacity/
CaelanT said:
This statement is 100% wrong!
Instead of explaining myself, please follow this link:
http://www.reely.com/darren/Guides/Reported%20Hard%20Drive%20Capacity/
Click to expand...
Click to collapse
Ok.... I've read a bunch of articles explaining things the way that manufacturers "round up" the number to make it look like higher capacity than it actually is.
But this is the first time i've read something like this. And its sort of sounds fishy.
How does the number of kilobytes change depending on the power? The hard drive either has a certain number of kilobytes or it doesn't. If the manufacturers are using a higher power, when there really isn't that many bytes, then indeed they are lying.
xploited said:
Ok.... I've read a bunch of articles explaining things the way that manufacturers "round up" the number to make it look like higher capacity than it actually is.
But this is the first time i've read something like this. And its sort of sounds fishy.
How does the number of kilobytes change depending on the power? The hard drive either has a certain number of kilobytes or it doesn't. If the manufacturers are using a higher power, when there really isn't that many bytes, then indeed they are lying.
Click to expand...
Click to collapse
Its just a different definition of what a kilobyte is. I say a KB is 1000 and you say its 1024, who is right? Of course manufacturers will go for the one that means less actual capacity per KB, and the OS guys go for their binary value because they are nerds who think and breathe in it, but that doesn't mean that either definition is inherently better than the other.
And if you are still having that problem I would return it within the 30 days and get a new one. Sounds like you might have some bad flash on your phone
daneren2005 said:
Its just a different definition of what a kilobyte is. I say a KB is 1000 and you say its 1024, who is right? Of course manufacturers will go for the one that means less actual capacity per KB, and the OS guys go for their binary value because they are nerds who think and breathe in it, but that doesn't mean that either definition is inherently better than the other.
Click to expand...
Click to collapse
Well, excuse me, KB = 1024. If manufacturers are trying to say it's 1000, then indeed, they are lying. Kilobyte has always been 1024, OS interprets it as 1024, if i download a 1 gig movie, it's gonna count to the power of 2, not 10.
So yes, manufacturers are kind of lying.
daneren2005 said:
And if you are still having that problem I would return it within the 30 days and get a new one. Sounds like you might have some bad flash on your phone
Click to expand...
Click to collapse
that would be a good feat, seeing as there are 22 months left on contract, he has already apparently used 2 months already.
It sounds like something in the OTA didn't install correctly. If you don't want to unlock your phone, I would take it to the Carrier, and have them reflash the ROM for you. That's the first time that I've seen a problem like that, so that is an odd occurrence. I wouldn't be so quick to damn the phone because of an odd occurrence, that same thing could have happened to an HTC, an iPhone, a Blackberry, or whatever.
mrphil101 said:
that would be a good feat, seeing as there are 22 months left on contract, he has already apparently used 2 months already.
Click to expand...
Click to collapse
That and I am quite litererally all at sea with no shops for 1000's of miles
Ok guys, I need your help. I picked up a T-Mobile HD2 from a friend for $40 who said "it won't boot". Being the experience Android user that I am I decided to give it a try, but I am at my wits end. Here is the sitch:
1. The phone is stuck at the "Stick Together" screen.
2. The bootload WORKS, to a point. It sometimes give a black screen when connected to the computer and a flashing tool is polling the USB.
3. I can flash all different WinMO roms from the bootloader, even HSPL, but still no boot.
4. Sometimes, when the ROM and SPL info come up in the bottom left, the phone will chug at the boot logo for a second, then strange graphical glitches start to appear on the screen. Similar to flashing an i9100 kernel on captivate, but not exactly.
This phone is a hackers dream, or more specifically my dream phone. Please help me get it back to working. I am not stingy; if there person who can get this to work and has a donation link... well... you know.
I have already:
Flashed the ship rom.
Used Task29
Flashed the current TMO rom.
Installed MAGLDR -> bootloader cannot make it to MAGLDR, even holding button.
EDIT: I also can't get it to recognize or flash roms from the SD card. All I have is a 4GB SDHC.
i can't figure out for sure if it's hardware or software that's been failing you. Since i'm more experienced with hardware i'll try to figure out a cause should the problem turn out to be hardware based after all.
1. nand memory corruption. the nand memory is made out of individual memory blocks, linked in a matrix mode and controlled by a memory ...controller (pretty logical i guess ). NAND memory is organized at a logical level in a way very similar to the classical electromagnetic drives (normal hdd's). I mean, blocks, sectors etc. If a memory sector gets damaged, it will produce something called a "bad" memory block. Again, similar to HDD's. But, different to HDD's where you can remap the memory regions and isolate bad blocks, you cannot do this to a flash chip inside a phone. At least not using standard tools or software. These tests are made only once by the manufacturer when the motherboard itself is being build. So, if your nand memory get's corrupted the phone itself won't "know" it since the individual damaged blocks can't be "marked" as damaged for the software to see and avoid placing data over there.
What happens is that you flash a rom, it may complete to 100% and from the bootloader "point of view" data was written over the flash memory. But when you attempt reading data from the damaged sectors, you'll get either nothing or corrupted readings. A more worse situation is when the boadloader itself resides over the damaged memory areas. If this is the case, even bootloader operations will behave erratic - bootloader lock-ups, freezes, strange screens etc.
I've seen phones with similar behavior that will react just like that. Sometime you can flash them, sometime not and when you flash them, they will stick to some random screen or simply freeze since the OS loading process halted with some random error when the corrupted data was read. I only managed to fix this by means of JTAG, a pretty low level debugging tool that requires a direct interface between the cpu and a pc. A memory diagnostic is loaded into the RAM memory and executes from there, it's purpose being to remap the NAND memory. It cannot be done from inside the NAND memory itself just like you cannot simply format the windows drive on a pc, while still being logged in on windows.
But, it's nasty business, service center kind of business.
2. CPU I/O failure. If you look into my signature here on xda, you'll find a link about hd2's cpu and overheating. That problem can in turn cause your problems - also saw this kind of stuff happening to a hd2. In fact is easier to determine if this is the cause. While i won't repeat myself again about how heat cause dilatation in the chip's soldering and how this affects the cpu operations, you can try a simple test. Place a sd card with some rom on it in the phone then place the phone in a bag, then place the bag in the fridge for about an hour. After that (while still keeping the phone in the bag and in the fridge interior) power on the phone, go to the bootloader and try to flash the rom from the sd card. Let the phone in the fridge during flashing and after it restarts. If you can't load a rom from the sd card, try using usb, the ideea is that the phone must remain as cold as possible during the whole process. Check to see if you notice any improvements - phone booting up, different errors or something different in any way from what you noticed so far. If this is the case, that topic from my signature would describe your problem in more detail. If not, we need to look further.
These should be my main suspects. Try to check #2 and reply with some results.
First of all, thank you for the information. I am actually very experienced reflowing PS3 and Xbox 360's, so I will try the refrigerator experiment, and if that succeeds I will disassemble the phone and reflow it in my reflow station. I find (seriously, not joking) that a reflow and (after cooling) a good 10 minutes in the oven on "warm" gets everything nice and settled.
Do you know if they used lead-free solder in the HD2? I'm not sure if phones also fall under RoHS.
yep, i think it's lead free, can't say for sure. But by the way it reacts to heat.. it seems so.
If you try the fridge/freezer, try to get the hd2 as cold as possible while preventing any condensation occurring on it - those transparent zip bags can help, that's what i use for example.
I had the EXACT same problem for a version that I bought off from a NY store (jr.com), it was a t-mobile version, tried everything, just to return it after 8 hours of my purchase.
Looking again for buying another hd2.
EDIT: looking online for hours and hours in vain, I concluded that it was a hardware issue due to some versions of the hd2 as someone explained earlier here.
I reflowed the motherboard and the phone now works.
I think its official, the"Stick Together" screen is the new RROD / YLOD.
good to hear. my hd2 was broken in the same way as yours. fixed it the same way, works as good as new even now.
Well, at least you know what to do if it happens again