Database Users

HD2 keeps crashing/hardresetting itself...

first things first: the hd2 is my very first windows mobile device. i've already read the wiki and searched the forum/the internet for help, but i didn't find a solution for my problem. i'm also not a newcomer when it comes to flashing (i've gained some experience from my psp/wii/nokia n82/creative zen).
so i got my htc hd2 a few days ago and one of the first things i tried was flashing a rom (i didn't like the t-mobile branding).
i had absolutely no problems installing hspl (this forum was very informative) and flashing the artemis rom (i strictly followed the instructions), which i found in the rom developement sub forum. since everything seemed to work fine, i started adding my contacts and some applications, still no problems.
but after a while one of the apps seemed to have crashed and the phone became unresponsive.
i removed the battery and turned my phone back on, but it was stuck in the boot screen (the very first screen on which it says "r g d" in red at the bottom). since i didn't know what to do, i simply flashed the artemis rom another time and so the story repeats: at first everything worked fine and after a while the phone got stuck again.
after 4 tries i decided to switch to the shock star r9 rom (also found on xda), which also seemed to work fine at first, but it didn't take long for the phone to freeze again. i took out the battery again and turned the phone back on. this time (to my surprise) it didn't get stuck on bootup, but instead it (automatically) performed a hard reset. the phone now does a hardreset everytime i turn it back on, which makes it pretty much unusable...
since i'm getting REALLY tired of adding my email accounts/favorites/application shortcuts (by now i'm just installing them on the sd card, so i don't have to reinstall them)/facebook associations for my contacts/etc and i thought i'd better ask for help.
does anyone know what causes this issue and/or how i can solve this problem? help would be appreciated!
and since i'm here, what should i use to backup my phone (once it's running perfectly)? i already tried pim backup (sadly it doesn't create a backup of everything) and spb backup (freezes on registry recovery). would it be possible to create a rom that contains ALL of my information (settings/contacts/favorites/applications/registry tweaks/...)?
tl;dr:
my hd2 automatically performs a hardreset on bootup, how do i fix it?
please ignore any grammar errors, i'm tired and not a native english speaker

I have the same problem exactly regarding self-hard-reset. I still did not find any reasonable cause for this problem which is starting really to push on my nerves

This sounds to me like a corrupt file system, which can happen after ROM flashes. I would try this:
http://forum.xda-developers.com/showthread.php?t=644781

@Moandal: thanks for the answer. i just flashed the shock star rom again and the phone boots up normally again. but i really doubt that it will stay like this, unless i know what caused the problem. next time it happens, i'll try the program from your link.
but if i'm not mistaken, that program also hardresets the phone (correct me, if i'm wrong), so i could just flash a rom instead and that's what i'm trying to prevent (as i said, i don't want to have to enter my personal stuff again and again and again...).
what exactly could cause a corrupt file system? could it be a problem with the rom(s) or am i just doing something completely wrong?

A "simple" custom ROM flash only overwrites the ROM's contents without prior erasing, which on the HD2 has been found to sometimes cause trouble like the continuous hard resets you've suffered.
The solution is a full erase of the ROM before flashing the new ROM, which this mtty command does. So, you obviously can't do it without hard resetting/reflashing.

@kilrah: ok, that made things much clearer. i'm going to use the program posted above and flash the rom again, i hope that will fix future issues.
thanks for the fast help, guys

I had the same issues, at first I thought it was the artiums rom but having done MTTY walkthrough I'm 1 week into the Miri rom without much issues (apart from the odd program crash)

since it started pretty much straight away on the first rom, id be a little concerned that it might be an issue with the phone.
if it continues after you mtty/task 29 then id flash back to stock, including spl, and monitor that for a few days.
Code:

@samsamuel: since my last post the phone crashed only once (i was using opera 9.7 when it became unresponsive again), but this time it didn't perform a hard reset!
the main issue seems to be solved and that's good enough, for the time being.
if the problem occurs again, i'll follow your advice.

opera 9.7 - have you moved the cache to the memory card? I've had a lot of freezes the last few days with opera 9 7, turns out it was cos the cache was on the sd card (default 2 gig that came with it).
moved the cache to the phone yesterday, not a crash in 30 hours.

no, but i was actually going to. won't do it now, obviously

please help cause it went crash and hardreset by itself over again..... how can I fix this??

Missing radio rom?

Hello,
I have an XV6700 that for almost 5 months now was running WM 6.5 flawlessly. I worked for a company that forces a passcode on the device. Now I never had an issue with the passcode until yesterday. Even though I kept entering it it assumed that I wasnt and after 5 attempts it hard wiped the phone. Which that doesn't bother me. But I have noticed since the wipe I cannot enable the phone radio any more and when it boots where it says R= theres nothing there. So basically I have a big ugly PDA right now. I have tried to flash to a different WM6.5 rom and the same thing happens. I tried to flash to the 1.43 radio but with the RUU that came with it, it did not want to flash and when I tried the RUU from the 6.5 rom I had it just errored out when I tried to update. Any help making my phone a phone again would be greatly appreciated!

Repeated MAGLDR 1EFATAL HIT Errror after Task29 + radio flash

I had been running WP7 on my HD2 (TMOUS) for a while now. I had been running MAGLDR and although I noticed some bugs, I never had any real issues. Recently I flashed MAGLDR v1.13 on my device and continued not having issues. Then one day suddenly my device started rebooting on boot up (this had happened a couple times before) at DFT screen. I figured it was probably bugs in my SD card formatting. At some point the DFT screen froze once while I was at work and I pulled the battery. After I put it back in I got a FATAL HIT ERROR (of which type I don't remember, but I'm pretty sure it was 1E). Now I came home and did a task 29 and then I tried to flash clockworkmod and that's when I started getting the 1EFATAL HIT error on AD RECOVERY boot. I've done this literally 20 times and it either hangs or doesn't boot or restarts, or MAGLDR loads with a black screen and only title info on top. I also tried reflashing HSPL3 and that didn't fix the issue. I also tried flashing a stock 2.12...50 radio and it froze at 96% and so I had to flash HSPL3 back (the only one I could get to work). I also tried to flash an energyrom but it just hung at boot. I've also tried 2 different computers and 2 different cords.
Has anybody figured out how to fix this? I feel like this is a corruption/partitioning issue that task29 just doesn't seem to fix. I've seen about 10-15 threads with the exact same but no one has seemed to resolve it.

metroidnemesis13 said:
I had been running WP7 on my HD2 (TMOUS) for a while now. I had been running MAGLDR and although I noticed some bugs, I never had any real issues. Recently I flashed MAGLDR v1.13 on my device and continued not having issues. Then one day suddenly my device started rebooting on boot up (this had happened a couple times before) at DFT screen. I figured it was probably bugs in my SD card formatting. At some point the DFT screen froze once while I was at work and I pulled the battery. After I put it back in I got a FATAL HIT ERROR (of which type I don't remember, but I'm pretty sure it was 1E). Now I came home and did a task 29 and then I tried to flash clockworkmod and that's when I started getting the 1EFATAL HIT error on AD RECOVERY boot. I've done this literally 20 times and it either hangs or doesn't boot or restarts, or MAGLDR loads with a black screen and only title info on top. I also tried reflashing HSPL3 and that didn't fix the issue. I also tried flashing a stock 2.12...50 radio and it froze at 96% and so I had to flash HSPL3 back (the only one I could get to work). I also tried to flash an energyrom but it just hung at boot. I've also tried 2 different computers and 2 different cords.
Has anybody figured out how to fix this? I feel like this is a corruption/partitioning issue that task29 just doesn't seem to fix. I've seen about 10-15 threads with the exact same but no one has seemed to resolve it.
Click to expand...
Click to collapse
Mate, can you go into boot loader?
If yes, have you tried to reflash stock winmo rom using sd card method?
What is the result?
I m really curious because it might be there is damage or defect in The NAND, which can be known by the existance of bad blocks. If this is the case, task 29 is not really helpful.
My hd2 has bad blocks in the NAND, and now, I can't flash Android. Luckily, I still can use winmo rom all these bad blocks, IMO, is due to my excessive flashing habit in the past
Too check whether there is bad block, I flashed recovery via cLK method ( using command line in dos prompt) it can show you what happen during flashing..
Good luck mate

See, I thought it might have had an issue with the NAND blocks but the thing is practically new and all I flashed was WP7 ever so I doubt it's hardware. I think task 29 doesn't get all the blocks like you said. And yeah, I can get into the bootloader. I can boot into MAGLDR usually.
Do you have bad blocks? And after flashing back to winmo did you try flashing MAGLDR and then AD RECOVERY or WP7?
My thoughts were if I flashed a stock WM ROM, it would erase that part of the NAND and then I could go back to flashing.

I flashed it back to stock 3.14 (radio, everything was flashed back to stock) and it works like a charm. No unusual crashing or reboots so far.
NVM, just had one but it was a freeze and then it rebooted and now it's stuck at stick together. Will try restart. May be because battery is really low.
1:47:
Now it just keeps booting and restarting lol! I'm gonna try a task 29 and then wipe it again.
Wait now it booted. And then it restarted again. it seems to be getting closer and closer to booting.
1:50
Just booted into SPL to flash again and it says that it's still CotullaHSPL. I thought that the SPL was wiped with the method I used... Will come back to this forum later, have to do stuff. (going to trade my other HD2 for a Nexus S!)

Any news on this? Still having the same issue. Anyone resolved this yet?

I've been having the exact same issue, which I believe was initially caused by overheating.
I've had this phone for almost a year, and have gone through a handful of Android builds, both SD and NAND (more recently). Lately it has been having issues with high temperatures, to the point where I would have to hold it against an ice pack in order to make calls or use the internet. The phone would not operate if the internal temperature was over 93 degrees. If it passed the 93 degree mark, it would freeze, and gradually get hotter until I removed the battery.
I've been good about keeping it cool, and barely using it (other than texting), until it froze during a phone call. I turned it off for an hour and a half, and when trying to reboot, I would get the Fatal Hit 1E error. I've tried re-flashing, downloading new ROMS, and most of what the OP has said, and the error persists..
Is there any update on this issue?

I don't think my problem was caused by heat. What OS are you running?

My last OS was Ultimate Droid 3.3, which I upgraded to around the end of April. I was still getting the freezing issues in the OS I used before that, which I had since January, but was discontinued shortly after I installed it.
My last option is trying to go back to stock Windows mobile.

Let me know how this goes. I tried restoring stock winmo and it still had restarting issues.

i had same problem... lucky me i fix it
if any one of you has warranty immediately go for it, if not than read this thread.
Solving the thermal problems of HD2 or other snapdragon powered devices

My phone is fairly lukewarm when this happens. I don't think it has to do with overheating. It's never been that hot. Also it's under warranty until December so I'm probably just going to send it in if I can't software flash it. It also restarts on boot, before it can even get hot at all.

I think I'm going to try this later today. You guys should too and let me know if it gets you anywhere.
http://forum.xda-developers.com/showthread.php?t=908915&page=2

[Q] Corrupted Radio, every reinstall ends in a whitescreen sooner or later

Ahoy, beloved XDA!
I never thought I'd end up posting something like this, but it seems that my phone is near-screwed as of this last month. I've held off jumping the question for as long as I could, but one failure after another has lead me to this.
My HTC HD2 has become unstable. It first manifested in my phone shutting down at random and getting stuck on a white screen (while nothing had changed for months), and now it can never hold a fresh installation down for longer than a day.
I've done multiple fresh from-the-ground-up installs. I installed the stock ROM through my microSD-card, which will fail 24/25 times before finally allowing the Radio to be overwritten.
The steps I take:
Reinstall stock through SD-card
Install HSPL
Task24
Install Radio 2.15.50.14
Install MAGLDR
Install CWM
Flash ROM
The Task24 step also includes Radio installation, though skipping the additional radio installation step doesn't change the outcome.
Completing these steps usually allows me to use my phone for about half a day or so before it begins to randomly freeze or reboot, ultimately leading to the phone never getting past the white screen.
Is there anything I can try to do to get things fixed?

Try to use the phone in Stock mode (Winmo stock) and see if you face the same symptoms, just to eliminate the hardware defect possibility .

Ah yes, I intended to do this earlier but looking at WinMo made me a bit too impatient to wait with installing Android.
I'll do so now and I'll keep you updated.

Opinionated HTC HD2

Hello everyone.
Two days ago a friend of me asked if I could install Android on his "new" HTC HD2.
As I installed Android on serval HD2's I said yes, no problem at all.
But once he came to my house and I started working on it only trouble is what came to me.
The HD2 was stock so Windows Mobile was running on it.
I install HSPL4 , no problem.
Flashed the radio, no problem.
Installed cLK, no problem.
Installed recovery : PROBLEM.
The trouble started from there.
The phone did not reboot, even tough it said "rebooting phone"
So what I did is unplug the phone, Task29'd it and did everything over again.
Than, I got an error on the radio installation.
The phone rebooted and when I got to the tri colour screen I was shocked.
It said some kind of "error rom update failed"
After this nothing worked, installing a Radio failed, installing the stock firmware downloaded from HTC failed etc.
Only flashing HSPL4 and Task29 worked, so I tought I was screwed.
I readed many many threads and somewere I got to the "Chill in fridge trick"
So I putted the phone in the freezer for 10minutes, copied the nbh file from the stock Windows Mobile rom to the SD Card and TADAAA! It worked!
So, here I was, back on Windows Mobile, trying again! to install Android.
As long as I kept the phone cold everything worked, also installing cLK and Clockworkmod.
But now here the thing is: Installing and running Cyanogemod is no problem at all, Cyanogenmod boots and run fine.
But when I want to install a sense rom, it works as long as the phone is cold.
When the phone gets to normal temps it stops responding and tries to reboot.
It stays stuck on the boot, and I have to put it in the freezer again to make it work.
This problem only occures with a sense rom!!
Windows Mobile rom doe snot have any problems, also Cyanogenmod does not have any problems.
The phone does still have warranty, but as the phone does not have problem with Windows Mobile I don't think I can send it to HTC for repair, as I think this is a hardware problem.
Does any of you know what I could do in this kind of situation?
Thanks in advance!!!

Oops, Admins, this one is duplicate, I refreshed the page and accidently clicked post thead twice, can you delete this one please? Thanks!

Did you flash magldr?
Sent from my HTC HD2 using Tapatalk

AFAIK HSPL4 is not for Android but only for Windows Mobile.