There was obviously a serious error with one of my phones. I tried everything, task 29, etc. The phone just would not take wph7 completely, but i knew for a fact that the sd card is compatible, but i tried to install wp7 without a sd card. The phone would never get past the first wph screen (after the dft splash screen). Sometimes the phone would not even get to the windows "getting started" screen, sometimes magldr would even hang up, or the pc could not even initialize the partitioning process to install wp7 (still hung at the "USB Flasher mode" prompt). I was ready to send the phone to HTC since I thought there was a problem with the internal memeory.
I then decided to start from scratch: restore the phone to stock(flashed stock rom from sd card, spl2.080000), reset the device once, and then loaded magldr while the phone was synced to my computer(not tri collered screen), then immediately flashed wp7 to the phone.
All is well now.
I think task 29 maybe did not errase the internal memory completely.
Alsu, Radio 2.12.xx.xx works wonderful, and it also gave me a huge improvement in battery life!
No offence but exactly what is the point of this post? And seriously, you were having trouble FLASHING WP7 to your HD2 so considered sending it back to HTC? Dude they would just laugh in your face, flashing voids your warranty.
Why label the thread "NAND Issue" as well, when by your own admission you have no issue at all? Baffling.
This was supposed to be helpful for other people, I have plenty of experience with flashing numerous HTC devices, and own several HD2's. This one had serious trouble taking on wp7, so logically tere was some issue with the internal memory. Flashing the HD2 the other conventional ways (as I flashed the other HD2's) did not work, the phone typicaly rebooted after the DFT splash screen before entering windows, which was indicating obviously a memory issue (independent from the SD card).
For anyonewith issues, MAGLDR 1.13 fixed all of the issues I had. It also got rid of random reboots and non boots of wp7.
Related
i have a tmous hd2.
after installing MAGLDR 1.12 i flashed DFT WM7 to try it out. it was nice but i was having sd card issues so i then flashed NexusHD2-Gingerbread_V2.0 NAND. i was having some trouble with the unlock screen freezing when waking up. hitting the power button a few times seemed to help. then the touch screen stopped working all together. i bought a new sd card for WP7 so i flashed DFT WP7 again, still no touch screen. i flashed a WM6.5 Energy rom, still no touch screen. But i did notice that in the rainbow boot screen while flashing WM6.5, now i cant remember everything exactly, the something {touch} value was N/A. i have been search tooling here for a couple of hours now, starting some googleing, but if anyone has some suggestions/ideas/threads to be directed to i would appreciate it.
*edit ran task 29 and flashed official tmous stock rom. still no touch screen!!
Think I found a solution for 3rd step, I used h**ps://wiki.ubuntu.com/Win32DiskImager to "write" img to bigger card, so far so good. WP7 sees 3.8gb, and I've got around 4gb for android in FAT32...
Booted Darkston superRAM 1.5 from sd
I have a HTC HD2 running a WP7 and (Desire Z sd on my storage card). I am also using Maglrd v1.13 ,HSPL 2.08 and Radio 2.15.50 . Every time I boot into WP7 the bottom 1/3 of the HTC hd2 gets very hot and reboots the device or Freezes the Device, it also gives me an error message below 1EFATAL HIT 1. When I use Magldr v1.13 to boot into Android after the device has cooled down, the device also becomes hot and Android SD Desire Z freezes . This is been happening for a week I also tried other SD ROMs that works and I get the same results. Does anybody have that problem also, and can anyone advise a solution.
Does anyone else HTC HD2 with WP7 Dual boot Overheats?
I have a HTC HD2 running a WP7 and (Desire Z sd on my storage card). I am also using Maglrd v1.13 ,HSPL 2.08 and Radio 2.15.50 . Every time I boot into WP7 the bottom 1/3 of the HTC hd2 gets very hot and reboots the device or Freezes the Device, it also gives me an error message below 1EFATAL HIT 1. When I use Magldr v1.13 to boot into Android after the device has cooled down, the device also becomes hot and Android SD Desire Z freezes . This is been happening for a week I also tried other SD ROMs that works and I get the same results. Does anybody have that problem also, and can anyone advise a solution.
I dual boot fine. Its probably your phone hardware. Flash the stock rom and see if the problem persists to find out for sure.
genesis123 said:
I dual boot fine. Its probably your phone hardware. Flash the stock rom and see if the problem persists to find out for sure.
Click to expand...
Click to collapse
I'm dualbooting and mine is fine... no overheating problems. Maybe try a different sd card... or try reflashing everything and starting over... see if it still happens.
I've Reflashed everything twice, put back the original rom and flash back everything . Used a 8gb sd card and another 16gb SD card same results .Device get warm to hot and become unstable as I stated.
Randy Hoover said:
I've Reflashed everything twice, put back the original rom and flash back everything . Used a 8gb sd card and another 16gb SD card same results .Device get warm to hot and become unstable as I stated.
Click to expand...
Click to collapse
Are you using an original HD2 battery? It's possible there's something wrong with the battery. Does it overheat no matter what you do... even if you just leave it in standby? Or is it with intense use? Have you tried just installing an android rom and see if it does it? Does it only happen when you dualboot? Maybe try using magldr 1.12 instead and see if that makes a difference?
I will use it three to seven minutes For example on WP7; Phone Call= reset,all other application = freeze or reset and resets twice while booting into WP7.IN Android All application freezes. I am beginning to think that the HD2 is faulty .
Randy Hoover said:
I will use it three to seven minutes For example on WP7; Phone Call= reset,all other application = freeze or reset and resets twice while booting into WP7.IN Android All application freezes. I am beginning to think that the HD2 is faulty .
Click to expand...
Click to collapse
Probably it is from the sound of it, did your phone overheat before you put
android on your sd card? if so then get that warranty to work cause it seems like
now is the good time.
I'm also having the 1Efatal hit 1 error
Hd2 t9193 none branded I don't know what to do I've tried the stock Rom and it won't go in I might be using wrong one help plz
This sounds familiar...
Advice: be VERY careful here. I believe I busted my LEO's digitizer by ignoring this overheating issue. The screen's responsiveness will start getting erratic, and evetually it will give up.
Good luck
I've tried search engine,ive tried everything but my phone still wont boot up:
Im currently using HSPL2.08 and my phone was just fine installing Imilka's Desire HD Ram NAND version yesterday...Installed the rom via clockworkmod and it was just fine..but then yesterday my phone freeze so i pull out the battery..then when i started to boot up the phone again...at Magldr v1.13 the phone shows FatalHit error while loading ROM..Im using radio v2.15 btw
Stuff that I've tried to fix:
Tried Task29,Reflashed WinMo 6.5 stock rom v1.66,tried reinstall magldr v1.13 even tried v1.11 and tried using other radio,using 2 different sim cards and SD cards,tried flashing via USB(TriColour Boot) and SD...EVERYTHING!!
T~T I really dont know what to do...Please help...at this phone i just want my HD2 to be able to boot up again no matter what OS..just want my phone back..
more data needed.
it looks like you're saying it loads HSPL 2.08 then loads magldr then when it tries to load the ROM it gives the fatal thing right?
so what happens after you flash a winmo ROM? does it hang? where? what exactly happens when you turn on your phone? have you tried flashing stock WM6.5?
Yup the fatal error appear on magldr v.1.13
Ive tried task29..
Then when i tried install windows stock 6.5 it stuck on the white htc screen without any red letters on the bottom like usual..
It looks is a risk to do flashes, I have HTC HD2 and I'd lile to installa Android on Nand, but I'm scared by the possibles problems
flawlessx92 said:
I've tried search engine,ive tried everything but my phone still wont boot up:
Im currently using HSPL2.08 and my phone was just fine installing Imilka's Desire HD Ram NAND version yesterday...Installed the rom via clockworkmod and it was just fine..but then yesterday my phone freeze so i pull out the battery..then when i started to boot up the phone again...at Magldr v1.13 the phone shows FatalHit error while loading ROM..Im using radio v2.15 btw
Stuff that I've tried to fix:
Tried Task29,Reflashed WinMo 6.5 stock rom v1.66,tried reinstall magldr v1.13 even tried v1.11 and tried using other radio,using 2 different sim cards and SD cards,tried flashing via USB(TriColour Boot) and SD...EVERYTHING!!
T~T I really dont know what to do...Please help...at this phone i just want my HD2 to be able to boot up again no matter what OS..just want my phone back..
Click to expand...
Click to collapse
I had the same problem. I tried every imaginable solution and nothing would work. I flashed WinMo from the bootloader screen, and SD card and it would sometimes load, but would freeze or hang up most of the time during boot. I tried flashing a DFT ROM, and it would boot about 20% of the time, and hang the rest. When it would boot, it would freeze once it got warm.
Luckily my phone was still under warranty.
fra1977 said:
It looks is a risk to do flashes, I have HTC HD2 and I'd lile to installa Android on Nand, but I'm scared by the possibles problems
Click to expand...
Click to collapse
The statistics are in your favor. If you were to compare all of the times that our HD2's have been flashed versus the amount that have been bricked, it would probably be less than 1% that have been bricked. IMO, Android is so much better than WinMo that it's well worth the risk.
....................
I have the same problem. After trying everything, now it sometimes boots into windows but after a while it suddenly stops working and reboots and sucks on white htc screen....
Tomorrow it will go back for warranty...
does anyone knows how this fatal hit error happens? I used the phone without problems for over 2 weeks with android on nand, before the problems started.
Sent from my HTC HD2 using Tapatalk
I think that this is the problem that made us wait too long for MAGLDR.. cotulla thought that he fixed it but looks like he didin't... i think the bootloader has overwroten the SPL..
Can you guys give more details about your HD2s like "When have you bought it" "which screen you have" ?
flawlessx92 said:
I've tried search engine,ive tried everything but my phone still wont boot up:
Im currently using HSPL2.08 and my phone was just fine installing Imilka's Desire HD Ram NAND version yesterday...Installed the rom via clockworkmod and it was just fine..but then yesterday my phone freeze so i pull out the battery..then when i started to boot up the phone again...at Magldr v1.13 the phone shows FatalHit error while loading ROM..Im using radio v2.15 btw
Stuff that I've tried to fix:
Tried Task29,Reflashed WinMo 6.5 stock rom v1.66,tried reinstall magldr v1.13 even tried v1.11 and tried using other radio,using 2 different sim cards and SD cards,tried flashing via USB(TriColour Boot) and SD...EVERYTHING!!
T~T I really dont know what to do...Please help...at this phone i just want my HD2 to be able to boot up again no matter what OS..just want my phone back..
Click to expand...
Click to collapse
It seems to me like many bad blocks on NAND...
How to verify that:
1) flash cLK (chose a partitioning your prefer)
2) via cmd run the following commands
Code:
fastboot erase boot
fastboot erase recovery
fastboot erase system
fastboot erase cache
fastboot erase userdata
If you have bad blocks it will show up in console of cLK
It will look like this
[6521] can't erase block @ 3424
[6521] bad block @ 3424 (or something like that)
You need to have adb drivers installed and fastboot.exe for the commands. If you don't have download them from here
Put the in a folder i.e. c:\android
navigate with cmd there and run the commands.
CWM can recognize bad blocks and skip them, therefore if you have many in each partition you can create larger partitions for /boot and /system and your phone will work properly until you decide to send it for repair.
If i remember well each block is 128KB
MAGLDR v1.13 on my HTC HD2
i have installed MAGLDR v1.13 on my HTC HD2
Phone have rebooted after installation finished, but DFT MAGLDR Bootloader have not loaded after these(
now i see only a white screan with the green text: ''HTC'' on it
please can somebody help me?
Ps : i had the correct radio ROM
HSPL 3.03
Radio 2.15
Same problem here, it seems the problem is with HD2 1024mem.. Tmous?? will CLK installation will solve? anyone with more suggestion? I would really really appreciate..my hd2 is laying on table for 2 weeks now with no solution
Ive noticed the fatal hit error on the hd2s with those tiny dots in the screen.
sent from my Nexus S
teutakarakashi said:
i have installed MAGLDR v1.13 on my HTC HD2
Phone have rebooted after installation finished, but DFT MAGLDR Bootloader have not loaded after these(
now i see only a white screan with the green text: ''HTC'' on it
please can somebody help me?
Ps : i had the correct radio ROM
HSPL 3.03
Radio 2.15
Click to expand...
Click to collapse
Your problem is wrong hspl.Magldr works only with hspl 2.08
sent from my hd2 using ics
WorldWide60 said:
The statistics are in your favor. If you were to compare all of the times that our HD2's have been flashed versus the amount that have been bricked, it would probably be less than 1% that have been bricked. IMO, Android is so much better than WinMo that it's well worth the risk.
Click to expand...
Click to collapse
agree with that
Did a hd2 the other day. Fatal hit error popped up. Done hundreds of hd2s. Bricked 2. On the particular hd2 i booted into magldr and did a reset. Had to reboot bout 20x to finally work. When it finally booted the touch was unresponsive. After another 10 or so reboots it finally stuck. Easy phone to mod but highest brick rating for me. I flash phones for a living so i know what im doing. Ive bricked my own g1 learning back in 09 and bricked 2 hd2s in 2011. There must be certain hd2s that dont accept the flash. Ive noticed the hd2s with the dots in the screen have been the only ones that give a hard time. Are theres the euro version? I only flash android on them not keep up with its development.
sent from my Sensation
Since this week I have a really big problem with my HD2.
November last year I started to install Android on my HD2, first on the SD card and then finally on the Nand (everything went well). Last week I installed one of the latest version and working just fine for one week it stagnated. I had to remove the battery, because nothing worked anymore. After that I got only the white starting screen with HTC and then nothing…
First I run Task29 and flashed it, HSPL, Radio, MAGLDR and then ClockworkMod Recovery. The result was that sometimes the white HTC starting screen popped up, tough I kept the power button pushed down, and sometimes I could enter the MAGLDR. If I finally got into the MAGLDR and tried to recover a backup or try to do a fresh/new install. I formatted the SD with the Panasonic SDformatter, but it didn’t had any effect. Finally I flashed the HD2 back to WM6.5 and the HD2 start working again (not very well). After this I tried to install Android on the SD card, but now the HD2 keep stagnates in the white HTC starting screen and nothing else works..
ROM: Boyppc Ginger 2.3.4 HoneyComB V27, with 150Mb system partition and an 1Gb ext2 partition on the SD card.
Is this a software or a hardware problem? Or both?
Can somebody please help me, because I have no clue how to repair this???
Best regards,
Janha,
OK. It's not me who have the problem and I may not provide you enough information. However, I will try as much as I can to get the info from the man who has the problem.
A friend of mine got an used HD2, with stock WinMo. The fist thing he did was of course hard-reset it. Aaand the system got ****ed up. He couldn't boot it sometimes (had a grey screen, he said with some weird text under, like Boot_W_PWE_KEY_PRESSED or BOOTUP_W_WARM_RESET after trying to install sth, few times it managed to boot up but lagged so much). I ignored it and wanted to do task29, radio, magldr, android. First thing - HSPL. Downloaded HSPL4, installed HSPL 2.08 fine. Then - Task29 + Radio. And nothing. ROM Code Error. After few tries, HTC logo and progress bar showed up. Task29 is stuck on 96% though and then displays an exclamation mark in a triangle.
After a restart, grey screen is still present.
We can't install magldr as well (dat error again).
What could go wrong?
try use HSPL3 cuz HSPL4 is for wp7 mango but not for HD2 Leo
Demo3827 said:
try use HSPL3 cuz HSPL4 is for wp7 mango but not for HD2 Leo
Click to expand...
Click to collapse
You need to study more.
OK, so we managed to install magldr on 11th? try and on 21st try we managed to boot Android from SD.
I'm pretty sure that NAND is damaged (NAND Android and WP7 couldn't boot at all, 1E FATAL HIT, same was with Android SD, but after many tries it booted), but when the phone hangs up after trying to play Angry Birds (so much that only thing he could do was to pull out the battery) and sometimes hangs up just for a while without a particular reason means that something else is damaged as well?
Boot loader
Has he tried booting into the boot loader.
Hold the down volume button and the power key at the same time.
If he gets a multi-colored screen then he is not bricked.
By 'bricked' I mean unusable because of physical damage that doesn't allow to run the phone properly.
Oh. Also he managed to install and boot WP7. It will return a 'Fatal hit' if it won't have enough break without a battey. It boots only after few mins turned off (which makes installing cabs almost impossible D: )... It was bought used, I think it had fallen and few more components were damaged...