Hi everybody,
I've been playing with my HD2 for a while (almost one year) and I'm experimenting my very first problem.
Currently under NDT MIUI v4.1 rom by Langthang, my phone is randomly freezing or hotbooting (rebooting without passing by mgldr).
I've tryed flashing ICS beta roms two days ago, the problem started at this point.
The OS was rebooting on his own without warning, even at the first boot after flashing.
Then I came back to stable releases.
And another problem appeared, the phone is getting stuck in mgldr (while booting on nanf or recovery)
I'm wondering if the nand isn't damaged as I've flash several other roms and the problem remain. I've also wipe and flash everythings needed more than once, without any impacts on it.
I'm running out of solutions, I think I will do a RMA and try to get a brand new as the phone is still under garantee if I don't fix it before the end of the holydays.
Someone got a idea on this ?
P.S : and Happy Xmas
P.S 2 : same problem under official WinMo 6.5 with 2.08SPL
have you fully task 29, reinstall winmo, and than hspl, than task 29 again and flash magdlr/ or clk. as that removes alot of the bad blocks associated with constant flashin.
Well, I've done : task29, SPL 2.08, WinMo, task29, HSPL 2.08 then mgldr/cwm.
I cleared some space on the internal storage, freezes and hotboots seems to have disappeared.
Anyway, I'll try later these operations in the order you said to see if it'll fix that.
Thanks for the answer
How old is your SIM card? I had been having increasing problems the past several months, which couldn't be solved by anything - task 29, revert to stock WinMo, reinstall HSPL, even tried flashing stock voltages.
A few days ago I activated a new SIM card, and all of my problems seem to be solved!
I have the same SIM card since 2 years or so. But I can't figure out how I'll explain to my operator that the SIM is dead
For unknows reasons, the phone seems to run well after having cleared almost 50mb of app on the nand. I'll try to fill it once more to see if freezes comes back.
Re SIM Card:
At least in the USA, there is no need to explain why SIM card is dead. I happened to have a brand new card (came with my HD2) which was never activated. All I did was call customer service and they activated it for me over the phone, no questions asked. If they give you trouble just tell them you lost the old one.
Also, they should be cheap to buy if you need. T-mobile sells SIM cards online for US $10.
Well, I've done steps by steps what tecle suggested me, and it works great so far.
I'll contact my operator to see if they can replace my SIM
Related
Recently, my phone has become very unreliable and crashes, requiring a soft reset, every few hours.
And to make things much worse, the phone never wants to turn back on again. I have to take the battery out, replace it, and try to turn it on again, about 20 times before it actually vibrates and turns on.
Happens on several ROMs, including 1.66 with stock bootloader, so I'm pretty convinced its gone defective.
Also the phone has a habit of getting very warm when it crashes, and the battery doesn't last very long at all.
Had the phone since the start of December, so what are my options in sorting this out? Bought from mobiles.co.uk
Will Vodafone replace it, as I've heard they no longer stock the HD2, and offer Nexus One as a replacement. Is the nexus one worth having? I don't know much about Android.
sound like you have flashed several roms? you should give mtty a try. find the mtty sticky in the rom development section.
Sorry but what does MTTY actually do?
different roms are different lengths.when you flash a new rom it doesn't erase the old one just flashes over the top.this can leave data from the old rom "sticking out"past the end if the new rom, leading to instability.
mtty formats the rom memory ready for a new rom.
I always perform a hard reset after flashing, so will this still have affected me?
Hard reset doesn't wipe the rom chip. It just reloads the rom from scratch.
Mtty may not help you, yours may be a different issue, but instability and boot problems are symptoms of exactly what mtty prevents.
samsamuel said:
different roms are different lengths.when you flash a new rom it doesn't erase the old one just flashes over the top.this can leave data from the old rom "sticking out"past the end if the new rom, leading to instability.
mtty formats the rom memory ready for a new rom.
Click to expand...
Click to collapse
Thanks for that! Despite endless threads re: MTTY, this is the first simple explanation I've seen.
If you are running apps installed to mem card then try a boot without the card.
The heating up sound like a result of "hard work" by the phone and if you run apps from mem card the current draw is significantly increased.
If this is the prob then don't install anything to mem card that you don't have to. They have been known to cause exactly the symptoms that you report + more apps on card and greater access to them reduces the overall speed of operation which can cause freezes and resets!
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??
Trying to get some help regarding my HTC HD2 Leo for Tmobile. For some reason any windows rom i flash, it will always crash. It will either crash on its own during boot up,after boot up, while im doing something on it, or while i have it locked in my pocket. My phone worked fine before i tried to flash a new windows rom and install a new Android. I went over the steps i did before my phone started being jacked up, i cant seem to figure out what i did wrong.
What i did before the problem:
-Clear storage under windows
- Task 29, held the volume button down once it hit 100%, this put it into boot loader again.
- I flashed the windows rom that was used by dark-stone on his site. ( which i cant post since im new or something) <<< i was trying to use same windows build as him and update my android that he put out on Oct 17th.
- Once my windows rom flashed and it booted up is when it started screwing up, freezing, shutting off by its self after boot, not booting up once i would restart it and also if i left the phone on the tmobile screen it would vibrate like 5-6 times then stop
What i have tried since my issues:
- I tried to flash my old windows roms, with many others that i had before that worked fine. All of these i tried gave me same problems
- i tried to update to the new T-Mobile update that posted on October 20th, and i also tried old version of tmobiles stock roms. Same issues again
- I tried re doing task29, tried new radios, resets of all sorts
I do have HSPL on my phone, always have since i first started flashing roms.
At this point i have a windows rom that can last me couple hours without crashing, so i can text and call. However its really annoying since the phone seems to be fine i doubt i bricked it since it lets me flash new roms and radios. Should i just take off HSPL and reset everything and get this HD2 exchanged, or does anyone by any chance have a way of helping my figure this out, or have any suggestions i could try.
Its keeping me from using windows and even better android
Thank you
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
Hi guys sorry if this is in the wrong place, i'm new on here and have read loads of the threads on my problem but so far no luck. Firstly the spec of my phone:
Unbranded HTC HD2
SPL-2.08.HSPL
magldr v1.13
Backed up everything a few days ago and now on trying to use that backup the new kernel I have flashed doesn't agree with the backup and doesn't go any further.
What i'm trying to do is flash JellyBean to the phone as the original stock rom was getting unstable but now i'm beginning to think it may be the hardware thats unstable.
Anyway what i've done is factory reset, wipe cache, partition sd card, 32mb and 512mb I've tried installing the rom and kernel on NAND only, that is fine up until the htc boot screen with the rusty android robot and then hangs and reboots.
I've tried SD card only and that only gets to go go go and then stops.
I've tried NAND and SD card and that gets to rusty robot and hangs and reboots.
My battery is fully charged.
Just incase its of any use the reason why i wanted to update was that the wifi had stopped working and occasionally the phone would hang on the android robot and reboot for no reason, I found removing the SD solved the problem. Thought it may be the same here so i removed the SD card on the NAND attempt but that didn't change a thing.
Help would be much appreciated.
Many thanks
Dan