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.
Hi there,
Its been couple of months that my phone froze during web browsing. And when I pull the battery out and reinserted, the phone would go through the booting and either freezes right after 123456 go go go or it would freeze during the Android Logo loading. It would take me many battery pull outs and re inserts to get it back on. During this time, I ran Hyperdroid 2.3.4 on NAND with Mgldr 1.13.
yesterday I tried to reinstall the OS, i task29, reflash the radio to 2.15... and reinstalled mgldr1.13. I have chosen Typhoon's 2.3.5 NAND CWM. After the installation, the same problem of not being able to go past 1234 go go go persists. I tried to pull out the battery again and after few try i managed to log in to Android.
It seems, the longer the battery is out, the more effective it is in booting the OS. I am seriously concerned about HW issue. Please help me identify the problem.
Thanks
Did you try installing the stock Winmob ... then doing a clean android installation (complete with re-installing the HSPL)?
I am going to do that next. It seems, all freezing during normal operation happens when I am browsing on Edge (my phone is incompatible with 3G on the network i am).
Secondary note, when I remove battery and reinsert, not only I cant make it back to Android boot but also, when I load up Mgldr Recovery, the AD Recovery function also does not load beyond 12345...
I am going to load a WinMo 6.5 ROM probably NRG's and reinstall HSPL.
Parsian86 said:
I am going to do that next. It seems, all freezing during normal operation happens when I am browsing on Edge (my phone is incompatible with 3G on the network i am).
Secondary note, when I remove battery and reinsert, not only I cant make it back to Android boot but also, when I load up Mgldr Recovery, the AD Recovery function also does not load beyond 12345...
I am going to load a WinMo 6.5 ROM probably NRG's and reinstall HSPL.
Click to expand...
Click to collapse
as I said before... use the stock windows, not the cooked ones (you can get it off the HTCs website)...
maybe,,, make sure you have the right partion size for your rom. check your roms page, it should say what size you need. if you have the wrong size, your phone can do all kinds of stupid things. speaking from my own screw up thinking i had the right size,,,
Sorry for the late response. I am now flashing it with STOCK ROM. I couldnt first find on HTC thats why I went and download the NRG's ROM. Today I just found that HTC pulled the ROM and now they are only available on T-mobile website so eventually I got it and now installing it. I will update about the progress
Thanks
So I downloaded the ROM and put my phone into HSPL screen by pressing volume. I open the .exe file (ROM) and set it to install. However, during the installation, the process gets stock around 18% and I waited it out couple of times for more than 10 minutes and does not go pass that.
I tried to Task29 it and re-flash it but the problem maintains.
UPDATE: I re run HSPL and restore to SPL 2.8... and then run the Stock Rom installation. This time, it finished the installation however, when it booted up, it got stock on the pink logo "stick together"... I tried to hard reset by holding the Up and Down Volume and when i did it, and when through the manufacturing reset process, the problem maintains. I cannot get into Stock WinMo.
Thanks
My phone has the exact same problem. Doesn't anybody have a solution for this?
Hello folks, I appear to have gotten into bother during a rom flash. After successfully installing a MAGLDR nand rom via CWM, the first boot of said rom just gives me the frozen splash screen without animation and the boot does not complete. Happens the same with three different roms.
I suspected somewhere further back in the boot process was at fault so I reflashed a known working radio rom, but problem still persists.
Despite a LOT of reading I can't see much about freezes at this point in the boot process on MAGLDR roms.
Bits that work - HSPL rainbow boot screen happily comes up, Task 29 works, magldr reinstalls and works fine, CWM perfect. Installs roms from SD (freshly reformatted) and appears to be ready to go, until boot actually begins then... splash screen freeze.
I have redownloaded various versions of everything to ensure no issues with corrupt files. I have also used different SD cards and ensured freshly formatted FAT32.
If it helps anyone, I have previously used NDT CM7 12.1 for about a month with zero problems.
Any other less obvious stuff I'm missing?
I'm off to bed so will be approx 7 hours from post time when I start responding. In the meantime I've put MAGLDR 1.10 on the phone so at least it can charge!
Many thanks in advance for reading.
Replying to self with update:
Installed OzRom Winmo 6.5 via the tried and trusted CustomRUU method, and it appears to work perfectly. What is winmo doing that android nand roms don't? I assumed if there had been bad blocks on the nand the much larger windows mobile rom would have covered this, and thus failed on boot.
At least opens the door to using an SD build till I can troubleshoot. Odder and odder.
Forgive my ignorance, but if the CustomRUU flash method still works for me, are there any modern android roms that don't need MAGLDR or clk?
Again, many thanks.
drachers said:
Replying to self with update:
Installed OzRom Winmo 6.5 via the tried and trusted CustomRUU method, and it appears to work perfectly. What is winmo doing that android nand roms don't? I assumed if there had been bad blocks on the nand the much larger windows mobile rom would have covered this, and thus failed on boot.
At least opens the door to using an SD build till I can troubleshoot. Odder and odder.
Forgive my ignorance, but if the CustomRUU flash method still works for me, are there any modern android roms that don't need MAGLDR or clk?
Again, many thanks.
Click to expand...
Click to collapse
How long have you been leaving the ROM on the boot screen? A first install of an Android ROM can take anywhere up to and over 15 mins for first boot. I also remember one when installing a hyperdroid ROM I had to restart the phone once to get passed boot splash.
I'd recommend flashing a popular ROM, leaving it for 20 mins, restarting and leaving another 20 mins. What do you have to lose? Just remember magldr doesn't have charge while off capabilities!
Also check your partition sizes and layout (you have to edit flash.cfg for magldr builds, partition sizes depend on the rom you pick but will be specified in the ROM thread).
Thanks for the reply. Each time I left the rom on the boot screen for a good half hour, and in one case an hour. I have installed NDT 12.1 and the newer v16 successfully before, so I know what sort of timescales are involved. I also had a go at an earlier Typhoon build. Naturally I used only the recovery sizes specified in each rom's own thread, using versions of MAG/CWM specified there, and Task 29 beforehand.
I have an update to all this, however. Previously I said Winmo installed, but now it is bugging out to all hell. This might fit my "bad blocks in nand" hypothesis, perhaps the files covering the bad area are less critical than the ones in each android build, and Winmo just crosses its fingers and tries to boot anyway!
In any case, if I can get an SD android build running I'll cut my losses and stick with whatever works.
Cheers again, hopefully this random screed of info will help people. Seems to be if all else fails, try winmo.
Well this one's a doozy of sorts, I'll try to be brief but any advice or assistance is welcome. Got a TMOUS HD2 on Saturday, it "worked" for a bit of time with the stock WinMo6.5 on it (no, I didn't care to look at the version, etc) and after having it for a few minutes to verify everything from a hardware perspective was working, I set out to do the usual process to get Android on it. I just wanted to get a CM7.2 build on it, preferably the actual CM7.2 and not a more customized ROM.
I have done the following:
- HSPL 2.08 - check, successful (as noted on the bootloader screen), done using HSPL4
- Task29 - check, successful (as far as I can tell), done from bootloader (VolDown+Power, Task29 provided by doloop single exe)
- Radio installed: 2.15.50.14 TMOUS (yes, it's the TMOUS version), check, successful (as far as I can tell), done from HD2Toolkit 4.2.0.1
- MAGLDR 1.1.3, check, successful, done from bootloader (DFT_LEO_MAGLDR113_DAF installer)
Now, at that point it was basically blank, obviously, so I decided to try and get CWM installed and that's when everything seems to have gone wrong. I get the FATAL HIT1 errors, it won't get past that. I read a post in the hundreds if not thousands I've been reading over where someone suggested when that error comes up, do the VolUp+VolDown+Power and do the reset - it only takes a half second since the device is already blank but some people reported in posts that it seemed to fix the FATAL HIT1 error and got CWM to actually load.
Didn't help in my situation. So I decided to start over at that point and flash the stock TMOUS 2.13.531.1 nbh (downloaded direct from T-Mobile, extension changed to zip, RUU_signed.nbh extracted to microSD card and renamed to leoimg.nbh) and attempting to do it from the bootloader.
At this point that aspect starts to work but it gets to about 8% (the same place it gets when using the actual T-Mobile ROMUpdateUtility method in Windows) and then dies. But the difference with using the microSD card method is that it tells me the following:
RADIO_V2 - RSA FAIL
in big red letters so I'm suspecting there's something going on with the radio that's just not kosher with the installer. I'm not sure how to proceed at this point - I'd like to get the HD2 functional again, preferably getting the stable CM7.2 ROM on it (not a big huge fan of ICS and JB is simply not my choice right now on the HD).
Problem is I don't know how to proceed at this point. If I can get it back to the stock WM6.5 that's fine for the time being so the device works, then I'll see what's going on with getting Android on it later, but I figure I'd rather ask a question or two, or three, before sitting here flashing radio after radio not being sure just what's going on and how best to get this issue resolved.
As noted, any advice or suggestions is welcome. I'm still trying various things at this time, including figuring out which radio to fall back to and test but, it's not going well so far.
loads of threads about this, my name for it is 'stuck radio' but it can also affect the spl too. Basically, there is corruption somewhere in the first area of nand, where the spl and radio live. whether thats software corruption (pray that it is, you may just stand a chance) or hardware corruption, you can't tell. the fact that magldr flashed would suggest its not as critical as normal, , some people get rsa radio fail and nothing at all works, no task 29, changing spl doesnt work, nothung at all. Often something seems to work (hspl gives success, for instance) but nothing actually changes after reboot.
So, first thing to try is - phone into a baggie, baggie into freezer, 20 / 30 mins later get it out, and real quick get the sd card in there already with the tmous stock rom as leoimg.nbh on there, and straight into bootloader, , see if it flashes past the radio section (the radio is flashed at roughly 6 - 10%, thats why you;re hanging at 8%, , 8% or 9% are the main reported percentages , lower % seems to involve the spl more (as you would expect, it is the first thing to be flashed)
There have been a few successes using teh freezer trick, and also a few more where JTAG has fixed it, but as often as not it never gets fixed.
failing that, see if you can flash a custom winmo 6.5 rom, because although the radio is failing to flash, it may still be in working order, and since custom roms dont include a radio, it may well flash, giving you at least a partially working phone.
Yah, the more I dig into it the more it's obvious there's an issue with the radio (like, duh ). I'm attempting to flash that Dutty's Leo Sense 2.5 that I saw mentioned in several posts by people that said they had success getting the device working at least to some degree - I grabbed the ROM, extracted the contents, copied the nbh to the microSD card, renamed it to leoimg.nbh, and at the moment it's just crossing the 50% point so, that is some progress at least (probably because it doesn't have a radio as you stated).
Will see what happens, but it is frustrating to appear to be able to do everything but actually get the radio flashed. HSPL flashes work after the reboot, Task29 always works (or appears to), MAGLDR only gives me issues when I try to get into AD Recovery from time to time, and so on. The usual HD2 issues I suppose.
This is my 5th HD2 and I'd like to get it working just like the others I've owned - none of them had anything like this much difficulty with getting Android (or anything at all) working properly so, maybe my luck ran out when I decided to get this one, who knows.
While I normally always find the TMOUS version of the HD2 here in pawn shops in Vegas, in the past week there have been 4 or 5 international unbranded models that popped up but, I avoid 'em since I believe the TMOUS variant is the better choice. Got this one for $75 and swapped a decent battery from one of the international ones when the clerk wasn't looking.
So much for that idea, either way (from microSD card or from Custom_RUU) the Dutty's ROM just hangs at the white/pink "stick together" screen and does nothing else. I then attempted to do a regular install of the stock TMOUS ROM again, no dice.
Geez... this stuff sucks sometimes.
Still hoping, of course.
ah thats a shame. the only other thing that comes to mind is seeing one or two threads with teh same problem where the poster simply tried again and again with the various versions of the (correct!) stock rom, and suddenly it flashed, and once teh radio was replaced it all worked again. I would have thought though that if it were going to do that, the freezer trick would also have worked.
I'd definitely try the three released stock tmous roms, , 2.10, 2.13 and 3.14, anbd perhaps some of the lower ones, too, , , see the 't mobile test & stock roms' thread in the tmous section DO NOT flash the first few, since the first one will brick it, and the next two or three have manufacturing spls, which can prove dificult to remove. (Not that you have anything to lose.)
flash from sd card., no point messing with the .exe, , more likely to work from sd card.
Heres a thought, , , forget the internal nand completely, , set up an ext4 partition, and then using sd card based recovery, flash an android rom using nativeSD. So long as magldr can be succesfully pointed at an sd card folder, you needn't use teh nand at all.
Dammit, no luck with any SD or NativeSD either. It simply won't ever get past the GO GO GO! event, no matter what I do. Tried several different recoveries (accessed from MAGLDR) and every time they just stick at GO GO GO! and never do anything past that. It DOES note the SD card is there, MAGLDR can access it to load the kernel, but it always ends up stuck at GO GO GO! and that's that. I was thinking if I could just get some type of recovery loaded (TWRP, CWM, I don't care) then perhaps I could do something more but, it's just a NO GO GO GO!
I did find that leodiag.nbh thing and gave that a shot, the diagnostic portion won't start because of the radio timing out (go figure, with the bad radio flash) so that won't even run, and the reset function doesn't either as it only sees the microSD card and still won't work.
It's like I feel like I'm missing one single thing that could turn it all around but, I'm tired of messing with it. Found the suggestion to hold in the reset button (mine is white, never seen a yellow or red one so...) and then turn the power on but it never does a reboot no matter how long I wait with the reset button still depressed.
Guess it's just not gonna happen this time...
yea unfortunately that's very often the way these turn out. the radio is blocking flashes from happening, and android from loading.
Do make sure you've given the freezer trick a good chance before you give up, i've read threads where the flash suddenly took after several attempts, (however in all fairness, if the freezer trick does help, it is usually indicative of hardware overheating problems anyway)
Well, against my better judgment but having enough experience (read: decades) with consumer electronics I figure the freezer thing - since it does actually work with hard drives in some situations - couldn't hurt.
Sure enough, after only about 2 minutes in the freezer (laying on some frozen food) I gave the SD update a shot and sure enough it finished, and after taking it out of the freezer a few minutes later, it booted into Windows Mobile just fine but, of course, then comes the letdown.
It froze up (not literally in terms of temperature), rebooted, then rebooted again before it got back into Windows Mobile, then on the 3rd reboot it just stopped and was stuck at the "stick together" screen where it simply won't get past.
So, obviously this one is suffering from the overheating issue, and I don't have access to an SMD oven or a proper heat gun (not that I'm going to go that far to revive it), so it's on craigslist for sale as-is presently. Funny thing is I've had 23 people respond for it since I know and they know and we here at XDA know all about how popular the HD2 is, even one like this one with potential good parts for use in some other one.
Let's hope someone actually shows up with cash, could use it for bills.
Thanks for the information, sam.
By the way would someone have a spare volume button ?
Sent from my HTC HD2 using xda app-developers app