Hello there,
I bought the HTC HD2 and it came with a ROM Version of 3.14 and the Radio was also compatible. I installed MAGLDR and several Android Builts and it worked.
However, the screen frooze in ALL builts and in Windows 6.5. Thus, I thought i have a Hardware problem and need to send it in for Warranty.
Therefore, I looked up the "native" ROM for my build, which is supposed to be this one, which I downloaded directly from HTC.com: RUU_Leo_TMO_DE_1.72.111.4_Radio_CRC_Signed_15.32.50.07U_2.07.51.22_2_Ship
I installed this Version by pressing the Volume button down and the power button to boot into the bootloader. Then I connected the Phone the Computer and followed the Instruction on the Screen.
The first time it installed itself to 100% but after the reboot it got stuck in the T-mobile branded Logo (pink circle).
I tried to reflash the ROM several times, but it always ended at 10%. I also tried flashing the 3.14 version (RUU_Leo_S_HTC_GER_3.14.407.2_Radio_15.42.50.11U_2.15.50.14_LEO_S_Ship),but this one also aborted at 10%.
Lastly, I tried to reflash MAGLDR 1.13, which officially finished at 100% but after the boot, I'm again stuck in the T-mobile logo and it does not enter the magdlr bootloader.
does anyone has any idea?
Rename the official rom to leoimg.nbh stick it on the root of the sd card. Boot into bootloader again and it will flash for you. P.s. DO NOT use the .51 radio if you're on t-mobile US. I doubt you are, but I have to mention it.
Sent from my HD2 NANDroid using XDA App
Thanks for the suggestion. I tried it and it seems to be working. Windows is starting again! you are a live saver. now i can send it in for warranty.
I have another question then. Currently I tried almost all NAND builds running FROYO, with everything working, and supposebly running stable.
However, during all builds I had screen freezes everywhere. Sometimes in the "go go go" screen, or afterwards during the next "HTC-logo", during the "pin-code", after the pin code, during some apps, etc.
First I thought, the build were not stable, but since it happend during all, I now think its the Hardware. Am I correct here, or is there something else I could try?
When I got my phone (windows 6.5) it already had freezes as well. and even when i made hardware resets and froze during the process...
The behaviour you're describing is not normal, and so I would recommend sending it back as it's still under warranty. If it was out of warranty, I'd maybe be tempted to try some things, but there's not much point when htc can fix it.
Sent from my HD2 NANDroid using XDA App
Related
Hi all - I'm in a bit of trouble.
Tried changing the OS to Android and must have made a mistake somewhere along the line.
Was using ROM update utility MAGDLR V1.13 and got as far as updating the ROM Was told that the screen should go black and if it didn't, then I needed to perform a reset.
I did this and now the screen just shows the htc logo on white background.
Irish phone - got it august '10. recently upgraded ROM from HTC site to version 3.14.405.2 but not sure now whether I've wrecked it completely.
Was just sick of WinMo and wanted a change - can anyone help please?
ND
boot into bootloader and start again. do you have hspl? right radio?
get into bootloader. flash magldr. then flash nandroid.
you probably need to downgrade the rom to get to hspl 2.08
Thanks - I got the correct HSPL and installed it on the phone, that part was fine. The problem now is that the handset isn't even acknowledging when it's plugged in. And when I connect via USB, the computer isn't registering any connection to it.
I think it's toast! The only thing I can see is a white background with green htc lettering i.e. welcome screen
Thanks for getting back to me, any other ideas?
Will I be able to reload original windows back on by myself?
Try windows 7 XP sucks doing this kind of stuff
Sent from my Nexus One using XDA App
ndonovan said:
...The only thing I can see is a white background with green htc lettering i.e. welcome screen...
Thanks very much for the response. As above, the handset is completely unresponsive - it's not even showing a "charge" when plugged in.
Any help greatly appreciated
Many thanks
Signed,
Cracking up
Click to expand...
Click to collapse
Can you get to bootloader?
(power on while holding vol. down)........
If so, get to bootloader then connect via usb. The word serial at the bottom of the screen should change to USB. This sometimes takes a few minutes (for me anyway)
Once it reads "USB" flash a WM6.5 Rom in the usual way.......
If you cant get to bootloader then theres a good chance you've somehow borked your device......
Thanks everyone and in particular jsmmcabe and conantroutman
I got into bootloader and I'm trying to reinstall the windows os from there.
will let you know how I get on,
thanks again guys - lifesavers
I should have mentioned that flashing a stock 6.5 rom will wipe HSPL.
If you flash a stock rom then you will need to reinstall HSPL before attempting any MAGLDR/NAND shenanigans... (sheNANDigans?? see what I did there )
If you flash a custom ROM from XDA then your HSPL will be ok......
Also should have mentioned the age old "NO .51. radios on a tmous" advice.........
Good luck.......
Well after all of that I went to Pirate Bay, downloaded an Android 2.2 file, copied it onto my SD card and ran it.
Hey presto, I have an Android Phone!
I cannot begin to tell you how much better it is. It's fast, it doesn't freeze, the whole interface is much cleaner and easier to use.
SNAG ITEM:
Tried doing the same with a friends phone and when activating the copied files from the SD card, the thing just hangs and I have to reset the phone.
Any idea why it worked on mine and not his?
Same phone, bought in Ireland, a week apart. Different mobile operator networks though..... I'm Vodafone, he's O2 - weird, no?
ndonovan said:
Well after all of that I went to Pirate Bay, downloaded an Android 2.2 file, copied it onto my SD card and ran it.
Hey presto, I have an Android Phone!
I cannot begin to tell you how much better it is. It's fast, it doesn't freeze, the whole interface is much cleaner and easier to use.
SNAG ITEM:
Tried doing the same with a friends phone and when activating the copied files from the SD card, the thing just hangs and I have to reset the phone.
Any idea why it worked on mine and not his?
Same phone, bought in Ireland, a week apart. Different mobile operator networks though..... I'm Vodafone, he's O2 - weird, no?
Click to expand...
Click to collapse
Could be its not booting because of an incompatible radio....
must be above 2.08.50..... you can find this info in settings about phone...
Also, why download android from the piratebay???
Everything android related you could possibly need is here on XDA.
Personally Id be suspicious of anything from a site like that. Theres no way of knowing whats in that Rom. I would change to a well used and trusted build from XDA if I were you.
Theres no exact science to getting this running on different phones, what works for one may not work for another......
Problem:
Won't boot into any ROM.
Phone Details at Start:
Telstra HD2, HSPL 2.08, Radio 2.15.50.14, magldr 1.12, Windows Phone 7
Description:
I was running Windows Phone 7 when it decided to crash and restart. However it got stuck in a restarting loop; restart then crash during loading which caused it to restart then crash, etc. Then magldr came up with 1EFATAL HIT 1.
I figured WP7 had somehow corrupted part of the install but nothing I can do seems to fix it.
I have tried:
-Reflashing it with WP7.
-Reflashing it with another WP7 build.
-Reflashing to magldr 1.13 then WP7 again.
But none of these worked so I tried to go for a NAND Android build. However I couldn't get the ClockWork Mod to work. It too failed to boot with the same problem as WP7. Now I just wanted to get the phone in a working state again so I have tried:
-Formatting the SD card
-Reflashing to a custom winmob6.5 build
-Reflashing to a custom winmob6.5 build I had previously used and worked fine
-Changing the Radio to 2.14.50.02 then reflash to a custom wm6.5
-Changing the Radio to 2.12.50.02_02 then reflashing to a custom wm6.5
When I try the custom wm6.5 rom I see the boot screen but it just sits there and goes no further. I have tried installing an old copy of the chunky rom (as it changed the boot screen ) but still just sits at the boot screen.
I have tried redownloading all of the files I'm flashing with in case there was a problem downloading it. Also I have tried using files I already had which were working, but nothing seems to have fixed it.
Some things I have noticed are:
-that all flashings have and still load without error
-that it doesn't have any problems loading into the HSPL
-when ever I tried an install with magldr usb flash (CWM or WP7) it would work but at the end of the flash it said it would restart but never did. I had to remove the battery
-loading into magldr I could select the restart or powerdown option but it would just hang and again I had to remove battery to turn it off
Does anyone have any suggestions as to what I can try to get it fixed? The only things have haven't tried are flashing with a stock rom or reflashing another HSPL. Both of those I though could cause trouble for the currently working HSPL, which if I lost would cause more problems. Currrently I am under the impression it is a hardware failure as no rom (mb6.5, WP7 or CWM) will boot and magldr installed fine but wasn't able to restart the phone.
Check your battery pins to see if they're in anyway bent. If they are, just push them back a little bit with your finger.
Have you tried Task29? I think the only other way would be to flash stock again and start over.
Sent from my HTC Vision using XDA App
Skellyyy said:
Check your battery pins to see if they're in anyway bent. If they are, just push them back a little bit with your finger.
Have you tried Task29? I think the only other way would be to flash stock again and start over.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Yes, I have tried Task29 and then tried installing both magldr then CWM and wm6.5. It however didn't make a different as I still got the same error. Sorry, I forgot to mention this in initial post.
I have also read about the battery pins being bent. I haven't tried it but from what I can see mine are all about the same height and seem pretty straight. When I put in the battery they also seem to be pushed back a bit so I am assuming they are all making contact. I was a bit worried about over extending them but I might give it go if no other option becomes available.
I've seen several times people with a phone that seems to flash, but nothing actually changes.
The only way you can visually test this in your current state is to change spl to something different, and look in bootloader see if it changed, but you said you don't wanna, so.
You can try flashing HSPL 4 and select HSPL 3.03 and see if gbiz is sucessful. If you have HSPL 3.03 in bootloader then you know it is flashing and you can go back to HSPL 2.08. Also you can try flashing your stock Telstra ROM via USB cable and computer as this method will not change your HSPL 2.08 but flashing it via SD card will revert you back to SPL. I think flashing the stock ROM will be your best bet for now.
Well I originally had the energy boot screen and when I flashed to a copy of the chunky rom it changed to its one. I would have thought it was at least partly flashing. Also I have removed with magldr with task29 then reflashed (with magldr) and was able to boot into magldr. So I think the flashing is happening successfully.
I you think reflashing the HSPL could work then I'll give that a try. As I haven't done that yet. If that doesn't work I'll take a look at flashing the Telstra ROM. I know flashing a stock rom is mentioned as a solution but I wasn't sure why I would make the phone work any better than a custom rom with concerns to booting.
Thank you for your suggestions.
Just to cover all bases here, your HD2 is not getting really warm or warmer than usual is it? If so this is a sign of thermal breakdown, but like I said this is just to cover all bases here.
From what I can tell it hasn't been getting any hotter than usual.
Re:"why to use stock instead of custom"
Its because a stock rom flashes everything, spl, splashscreen, radio and rom.
Also, some customs use a secondary splashscreen, which would replace magldr, so if things aren't right, starting over by flashing your correct rom is often advised just to draw a line under the current attempts and start over.
Don't forget that even if the stock flash fails, if you did it from bootloader then Hspl is likely gone, and magldr too, possibly.
Just an update. I flash a Telstra ROM which to my surprise it booted... after a couple of tries. Decided to reboot it to see if it starting up was just luck which it turns out it was. I couldn't get it to start again then it refused to even get into the bootloader. So I am sure enough now that it is a hardware failure and am taking it in for warranty.
Thanks again for the help.
I have been using NAND since the public release on NYE. Most recenly when updating ROMs I had tons of freezing, & still do. Initially i thought it was a problem with the SD and did the panasonic format util & tried booting with no card at all. Same **** happened again. So I thought to flash a stock rom (winmo6.5) and see if there were any problems. I figured let's do a Task29, I even reflashed the radio & HSPL. When I flash an offical or custom ROM its gets to like 53% and then vibrates like 5 times. The process finishes normally, but upon reboot it makes the same 5 vibrates and stays stuck on the "Stick Together" screen. Also I did get OzDroid to fully boot one time, but the screen was unresponsive 100%. I don't know what the deal is, but this is all the stuff I know how to do & after much searching I still don't know what the multiple vibrates mean. I don't know if its time to send it in or what
Try to redownliad another official rom. Maybe it was F'ed up
Already did that. Tried using the SD method using LEOIMG.nbh on the root, by renaming the the official Tmousa .exe to .zip and extracting the RUU_signed.nbh
I got it to boot finally, but when it came to the initial settings screen (picking carriers etc) it got completely unresponsive. I have tried flashing an Energy rom, OzDroid, official tmousa ship rom, t-mobile.com official update rom; All ending in failure. I think UltimateDroid fried it.......i'm gonna cap who ported that crap
Edit:
I got it working again by doing a factory restore (vol+ & vol-) + power, and then flashing the most recent RUU_signed.ngh found in the latest tmousa .exe - Haven't tried to flash magldr or any other roms as I suspect the nand/and/or ram is damaged. We'll see how it goes, it may have been bad sectors or a ****ed up allocation of some kind. Hopefully this fixed it.
Edit2:
It's still ****ed.......tried to install magldr and it works.......sometimes. Sometimes it won't load the recovery at all. Sometimes it boots the android rom all the way and then freezes when it gets to the initial setup screen (which I have also tried bypassing w/the 4 corners method) but it still freezes eventually. Guess this piece is ****ed.
That sucks man. Definitely something wrong
Hehe good luck bro
It's probably user error. I'm almost certain it is as no HD2 will mess up from nand. You should sell it and get a nokia 3595. Leave the smart phones to smart people.
Ok, guys I REALLY NEED HELP WITH MY TMOUS HD2.
I currently have HSPL 2.08 but everytime i go into the bootloader and install a WinMo 6.5 Rom it gets stucked at 8% percent for awhile then goes to 100. After i installed it, it gets stuck on T-Mobile, Stick Together screen with the R G B thing on the bottom.
I had NAND on my HD2 but it keeps freezing in every rom anytime I use data connection, recieve calls, or use browser or anything that uses the Data Or T-Mobile Connection. So i decide to reflash everything starting with Radio, and I recently installed Radio 2.15 something like that in A radio thread somewhere on the forums. I chose that one because im assuming it's the newest one. I flashed it, and removed MAGLDR, and etc. I currently tried using Task29 and flashed stock 2.08 radio but had the same problems. I CANNOT FLASH ANY ROMS. I TRIED REFLASHING MAGLDR AND CWM AND I CANT GET INTO RECOVERY I GET A FATAL ERROR1. Should return the HD2 to T-Mobile? They don't sell the HD2 anymore so i assume HTC will have to give me one. I'm currently deciding the only choice i have is to return my HD2 to T-Mobile. I flashed SPL 2.08 so it's back to stock. I cannot install or load any roms without it being stuck in the T-Mobile screen. Any help? Or i just have to replace it with a new one?
blahblah13233 said:
Ok, guys I REALLY NEED HELP WITH MY TMOUS HD2.
I currently have HSPL 2.08 but everytime i go into the bootloader and install a WinMo 6.5 Rom it gets stucked at 8% percent for awhile then goes to 100. After i installed it, it gets stuck on T-Mobile, Stick Together screen with the R G B thing on the bottom.
I had NAND on my HD2 but it keeps freezing in every rom anytime I use data connection, recieve calls, or use browser or anything that uses the Data Or T-Mobile Connection. So i decide to reflash everything starting with Radio, and I recently installed Radio 2.15 something like that in A radio thread somewhere on the forums. I chose that one because im assuming it's the newest one. I flashed it, and removed MAGLDR, and etc. I currently tried using Task29 and flashed stock 2.08 radio but had the same problems. I CANNOT FLASH ANY ROMS. I TRIED REFLASHING MAGLDR AND CWM AND I CANT GET INTO RECOVERY I GET A FATAL ERROR1. Should return the HD2 to T-Mobile? They don't sell the HD2 anymore so i assume HTC will have to give me one. I'm currently deciding the only choice i have is to return my HD2 to T-Mobile. I flashed SPL 2.08 so it's back to stock. I cannot install or load any roms without it being stuck in the T-Mobile screen. Any help? Or i just have to replace it with a new one?
Click to expand...
Click to collapse
your phone is currently out of warranty, do not send it to HTC.
Download the tmobile stock ROM by going to the tmobile website > support and they will aks you for your IMEI and SN, enter it and it will give you a download for the stock ROM.
Download the ROM, then extract the file.
Take the .nbh file and rename it to LEOIMG.NBH
put that on the root of your 8gb or less SD card, pop it in, get into bootloader, and hit the power button when it tells you to.
IF this fails it sounds like a hardware issue.
Put your phone in a plastic bag and stick it in th fridge for 10 minutes, take it out and reflash as above, after flash call HTC on a warranty claim because your phone will be stock and hence back in warranty.
I've tried that, i only have a 16gb sd card and it works, but it gets stuck in the stick together crap. D:
seems to be cropping up every few days lately, this problem, though it's always been around. 'stuck radio', 'spl wont change ' 'flash fails at 8/9/10%' and variants thereof, , android gives fatal hit, nothing sticks when flashed, and teh phone never gets past teh rgd screen (cos the radio is shafted)
so i cant send it to htc? then wtf..?
blahblah13233 said:
so i cant send it to htc? then wtf..?
Click to expand...
Click to collapse
Well from reading this thread I agree with samsamuel, it sounds like you are having a hardware problem as most of the HD2's that people have that show the symptoms Sam mentioned can not be fixed with software solutions. Bu there is the occasional anomaly that someone manages to bring back to life but even m,ost of them eventually completely get "stuck" and then they are useless.
As for what to do. You can take it or send it somewhere to replace the mainboard for you. Or just buy another HD2. That is it short and sweet.
so whats the update blahblah 13233?
Thanks guys with all the help possible, I went to a T-Mobile store and asked for a replacement, it should be coming in 2 days. I had to pay 5$ Shipping. So when I get my new phone I gotta give my old phone in some container or whatever and mail it to htc or give it to any T-Mobile store Thanks guys with giving me ideas. The people at T-Mobile said it's a hardware problem like the guy stated above. Oh well, I hope it doesn't happen again.
I managed to break my original HD2 a while ago and I've only just decided to replace it. I have another main phone but I loved that I could pretty much do anything with my old HD2. I had a bit of experience with installing cooked ROMs before moving on to installing Android and WP7 on it.
As I had a bit of experience with playing about with software recovery/updates, I decided to buy a phone that was described as "booting to a white screen" off ebay. I thought it would be a fun little hobby to get it working again.
My first few steps would be to get it to stock and start playing with it from scratch.
I booted into the bootloader and tried to flash a stock ROM but it kept freezing at 0%.
I've since managed to change the SPL version from 2.08 HSPL (I could get the phone to boot into MAGDLR 1.13, so they must've been playing with WP7 or Android NAND) to 3.03.
When I try to install the unbranded stock ROM, I get an error telling me that "This Update Utility cannot be used for your PDA Phone." I assume that I'm trying to install unbranded firmware on a branded phone. Is there a way to find out what branding the phone has as I can't get it to boot up? Am I going about this the right way or have I missed something obvious?
Thanks for your help!
EDIT:
I installed 3.03 HSPL to install the stock ROM and it completed the install process. However, after turning it on, it froze on the white HTC screen where it shows the Radio & ROM version. I pulled the battery out and now it freezes on a blank white screen. I'm out of ideas at the moment. Any help would be appreciated :s