Related
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
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'm sorry i know it's against the rules to be starting a new thread but it's been a week i've been asking for help and no one noticed. This is just a try to come noticed.
I installed task 29 on my blackstone. I had olinex 1.56 installed and later did the task29 with radio 1.13, 1.14 and 1.17 After successfully doing it i went on step 2 that is installing a clean rom. I tried these roms
blackSTONEhengeHyPerSlim_4_1
RUU_TOUCH_HD_MARYONE_23148_WWE_191110
WWE_1.56.405.1_Radio_52.62.25.Shipped ROm
RUU_BlackStone_HTC_WWE_1.56.405.1_Radio_52.62.25.34_1.13.25.24_Ship(3)
They get installed but after i store the contacts and everything it gets stuck if kept for like half an hr. The screen doesn't respond but power button and the volume button works.
I took my phone to a repair center and they couldn't fix it. So please help me i've just got only one phone.
I don't mean to offend any moderators by this but i'm just asking for your help. Thank You
Try reinstalling stock ROM after Task 29.
Restore ONLY contacts, and then try using device for several days.
DO NOT install any other software!!!
If it works, then problem is in some data or software you're restoring.
If not, restore original SPL and original ROM and try again.
If it does not work... and service can not help you... then sorry...
Hello i did reinstall the stock rom after task 29 and i was using pimbackup for restoring but that freezed my phone so i installed the stock rom again and thought of not using it. Did that but nothing much helped.
I hope believe these are the correct shipped roms
WWE_1.56.405.1_Radio_52.62.25.Shipped ROm
RUU_BlackStone_HTC_WWE_1.56.405.1_Radio_52.62.25.3 4_1.13.25.24_Ship(3)
Everything on xda has worked like wonders for me. Be it android on any other rom but right after task29 nothing seems to be working on my phone.
One thing i've noticed after installing any rom after task29 is if i get to the bootloader it gets me to a 1 sec white screen saying no image found. I hope what's causing a problem.
Do you understand WHAT Task 29 is?
It formats the partition drive of your device where the ROM resides. Meaning, it wipes any data regarding ROM.
So of course it would say "No image found".
I don't know which ROM is stock for your device. Try to update ROM via HTC site.
If lucky, it will suggest / let you find adequate ROM.
For my device it's 1.56.407.2 (German)!
If unlucky, it will say "Not supported" or something like that - then go for Orange 1.59.61.2 ROM.
And you might try one 1.5x ROM flash WITHOUT Task 29...
Just try installing stock ROM by stock RUU with USB cable. It will format data for you so you do not need any task 29 before flashing. If it doesn't work, try NOT restoring your contacts.
Thanks will do it and keep yu updated with it..
simplistian said:
Just try installing stock ROM by stock RUU with USB cable. It will format data for you so you do not need any task 29 before flashing. If it doesn't work, try NOT restoring your contacts.
Click to expand...
Click to collapse
Thanks i tried installing the stock rom like you told me but then got stuck on the screen alignment screen. I later installed blackSTONEhengeHyPerSlim_4_1 and now it's responding to every touch. Thanks alot. I hope this stays like this and yes instead of restoring i forwarded all the contacts through bluetooth. Owe you a BiiiiiiiiiiiiG thanks..
Too soon to be happy as same again..I don't think there should be a problem with touch as it works fine for first 1hr but right after something gets stored by something i mean contacts it stops reponding after sometime. The volume and power button work all fine. I can't make out the problem. Any ideas or suggestions. Shall i make a video and post ??
FIRST you have to make it work with factory settings - stock SPL and stock ROM.
After that flash what you like...
I think you have to follow Bodisson's suggestion, do everything as stock and retest without restoring anything. If it still failed...... you should have it repaired
Good luck!!
I had a very bad flash when I first tried Cloudy 0.7.
Unstable and freezing clock in TouchFLO (but NOT system clock!), crashing programs, very slow satelite lock with radio 1.17 on, sudden autolocking/unlocking...
So I did Task29, put on stock ROM (latest German 6.1), after that latest Orange to get newer radio, and after that Cloudy's 0.7.
Now I'm happy so far...
And I'll stick with radio 1.14 for now since it uses a bit less battery than 1.17...
Bodisson said:
I had a very bad flash when I first tried Cloudy 0.7.
Unstable and freezing clock in TouchFLO (but NOT system clock!), crashing programs, very slow satelite lock with radio 1.17 on, sudden autolocking/unlocking...
So I did Task29, put on stock ROM (latest German 6.1), after that latest Orange to get newer radio, and after that Cloudy's 0.7.
Now I'm happy so far...
And I'll stick with radio 1.14 for now since it uses a bit less battery than 1.17...
Click to expand...
Click to collapse
Glad to see somebody researching things out and settling on a radio he prefers due to performance rather than those just going for latest
I totally agree with spartan on this one. It's better to stick with old one's for performance rather than having problems with the latest one's. My device is working better than before but it does get stuck. I'm using stock rom with 6.1 and want to switch to 6.5 so looking for some compatible 6.5 rom with radio 1.14 maybe
Bodisson can you tell me all what you're using bro so that i can tr it on with my device.
kulwant said:
I totally agree with spartan on this one. It's better to stick with old one's for performance rather than having problems with the latest one's. My device is working better than before but it does get stuck. I'm using stock rom with 6.1 and want to switch to 6.5 so looking for some compatible 6.5 rom with radio 1.14 maybe
Bodisson can you tell me all what you're using bro so that i can tr it on with my device.
Click to expand...
Click to collapse
All rom's should work with each radio to be honest. Glad your device is working better, though still a little baffled why you're still having difficulties
EDIT - You are on a wm6.1 rom. Is the rom based on 1.56+, if not you may need to revert to HSPL 1.14
I know it got me bedazzled as well as i've flashed couple of times before but never faced any such difficulties. I even tried android on my phone and everything worked like charm. RUU_BlackStone_HTC_WWE_1.56.405.1_Radio_52.62.25.34_1.13.25.24_Ship is what i'm using at the moment. I did try to flash it again with a 6.5 version rom but still gets stuck. The phone does get stuck once in a while if it is kept unused for a while so don't exactly know how to go on about it.
P.S: I know how hard it is to control things as an admin as i myself run a group. Photography in my case. Cheers
kulwant said:
I know it got me bedazzled as well as i've flashed couple of times before but never faced any such difficulties. I even tried android on my phone and everything worked like charm. RUU_BlackStone_HTC_WWE_1.56.405.1_Radio_52.62.25.34_1.13.25.24_Ship is what i'm using at the moment. I did try to flash it again with a 6.5 version rom but still gets stuck. The phone does get stuck once in a while if it is kept unused for a while so don't exactly know how to go on about it.
P.S: I know how hard it is to control things as an admin as i myself run a group. Photography in my case. Cheers
Click to expand...
Click to collapse
I'm baffled but still want to get to the bottom of your issue and would appreciate any help from other members who may have idea's on how to solve your issue. From what I've read everything you have done is correct, but I don't like being stumped!!
If we start from the start, we may get to the bottom of this........
Ok it all started when i tried installing task 29. I flashed my blackSTONEhengeHyPerSlim_4_1 rom thinking task 29 will work awesomely fast with some newer version as it'll get installed as the default rom.
My phone started freezing like anything right after i flashed it with task 29. Right now my device is running on 1.56.405.1(43972) WWE and 1.13.25.24 rom and freezes again once in a while.
Just waiting for some miracle to make it work fine again.
kulwant said:
Ok it all started when i tried installing task 29. I flashed my blackSTONEhengeHyPerSlim_4_1 rom thinking task 29 will work awesomely fast with some newer version as it'll get installed as the default rom.
My phone started freezing like anything right after i flashed it with task 29. Right now my device is running on 1.56.405.1(43972) WWE and 1.13.25.24 rom and freezes again once in a while.
Just waiting for some miracle to make it work fine again.
Click to expand...
Click to collapse
Well as you know a T29 formats device so you need to flash a rom or you'll be stuck at boot screen. Before you do a T29 it states you must have HSPL on your device first. Now from what I've read you did have HSPL on first and your T29 worked as you where stuck at boot screen afterwards.
I'm assuming you turned device off, booted into bootloader then flashed youir rom (blackSTONEhengeHyPerSlim_4_1) which is based on 1.56+ as was your HSPL.
This all seems correct so I'm not sure what went wrong.
Is above all correct?
Did you try a T29 again and flash different rom or did you just flash different rom over existing?
I did task 29 on blackSTONEhengeHyPerSlim_4_1 and tried installing RUU_TOUCH_HD_MARYONE_23148_WWE_191110 in this process i started task 29 first and flashed it with radio 1.14 by placing the radio and task29 in same folder. Once done it got stuck with windows mobility. After that i restarted on bootloader once again and flashed it with RUU_TOUCH_HD_MARYONE_23148_WWE_191110 . It does get installed but then freezes on configuring device for first time use and then freezes big time on the screen for alignment. I had 1.56 installed before flashing with task 29. If the whole thing bypasses the align screen the rom will keep freezing big time.
That's been the whole issue.
kulwant said:
I did task 29 on blackSTONEhengeHyPerSlim_4_1 and tried installing RUU_TOUCH_HD_MARYONE_23148_WWE_191110 in this process i started task 29 first and flashed it with radio 1.14 by placing the radio and task29 in same folder. Once done it got stuck with windows mobility. After that i restarted on bootloader once again and flashed it with RUU_TOUCH_HD_MARYONE_23148_WWE_191110 . It does get installed but then freezes on configuring device for first time use and then freezes big time on the screen for alignment. I had 1.56 installed before flashing with task 29. If the whole thing bypasses the align screen the rom will keep freezing big time.
That's been the whole issue.
Click to expand...
Click to collapse
Right, I never put any files in same folder as it only confuses flashing process and can cause issues. I.e. put T29 in its own folder, radio 1.14 in its own folder and then rom in another folder.
Do a T29 and when its complete, I.e. stuck in smart mobility screen. Then you take out battery to turn phone off. After this put phone into bootloader and flash rom. Then flash radio after it as a lot of roms have a radio file included
...........................
Sent from the improved version of Tapatalk, better known as Forum Runner
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