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
Related
I decided to partition my SD card today because i needed more space for my apps. I used ROM Manager to do the work. Everything went fine until it booted up. Now I'm stuck on the HTC screen. I read that the boot takes a while but I've been waiting for over an hour. I've also tried to pull the battery out and restart but I'm still stuck on that same screen. Anyone know how to fix this?
I do have this problem. I have to remove the SD card in order to boot successfully and reformat it to FAT32.
what rom you use?
I used to flash whitetigerdk v0.4 and got that problem but now I downgrade to v0.3 and problem's gone
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
Whenever I try to boot up an Android SD ROM through MAGLDR, it all seems to go right until it gets to the lock screen and then, the phone freezes. Always in the same spot where I can see the wallpaper, the date and time, the No Service sign and "Preparing SD card" on the status bar on top. This same thing happens with all ROM's, so it's not ROM specific. Also, I have had a ROM installed since before this started happening and that one runs fine. It's only new ones as they try to boot up for the first time.
I was wondering if anyone has any idea of what could be causing this and how I can fix it without having to repartition the entire SD card again, reinstall WP7, etc. That's a lot of work. I have even tried formatting the partition and that didn't work.
Thanks in advance.
Solution
For anyone else having this problem, my solution was to DELETE (formatting wasn't enough) the Android partition, then recreating it and then installing my ROM. That way, I did not mess up the WP7 installation.
Hi, I was running Android on my HD2 for almost 9 months, currently HyperDroid5.5.2. Till now, without any problem whatsoever. Suddenly, when I checked my phone this morning it didn't respond. So I waited a while, then tried pulling the battery. Booting got stuck at Android logo. No problem I thought, I periodically do nandroid backups just in case. Tried to restore it - stuck at restoring data. Then I tried advanced restore, only boot and system... either of them didn't work. After this, I decided to reinstall from scratch - task29, radio, magldr, cwm. The ROM installation got stuck again. So I tried flashing stock SPL and stock ROM from HTC site. SPL okay, ROM not. Got error 262 from the RUU. Tried searching the forum but there is so much stuff that it's impossible to get through. So please don't bash me from beeing a noob. Can anyone please help?
Edit: After the phone finally accepted WM back, I want to put Android back on it... ROM installation gets stuck at restoring Batterystats.bin... any ideas?
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