[Q] Can't install Radio - HD2 Android Q&A, Help & Troubleshooting and Genera

Hello everybody,
I've been searching the forums for a while now but I can't seem to find a solution.
When I try to install a ROM through clockworks it installs successfully but then hangs on the ROM's splashscreen indefinitely. I have been able to trace down this problem to a stuck radio issue. This also makes me unable to install radio.
I have tried to install it by pasting the .nbh file on the SD-card renaming it to LEOIMG.nbh and then trying to install it with the tricollor screen, it fails at 100% just like the customRUU. Installing de original Windows ROM makes it error out at 8 or 9 percent (radio is the first step so it errors out at that I suppose) depending on the SPL version. When installing through RUU it always gives me the 290 Invalid Command Error (290 Ongeldige opdracht) I have tried multiple HSLP versions and am now using 2.08.HSPL.
When the phone boots up it does not display the 3 lines of red text in lower left corner, normally it displays version number there including radio as far as I know.
I really don't now what to do to solve this problem, I've been at it for more than 8 hours now, does anyone know of a solution?
Thanks, MdR15

MdR15 said:
Hello everybody,
I've been searching the forums for a while now but I can't seem to find a solution.
When I try to install a ROM through clockworks it installs successfully but then hangs on the ROM's splashscreen indefinitely. I have been able to trace down this problem to a stuck radio issue. This also makes me unable to install radio.
I have tried to install it by pasting the .nbh file on the SD-card renaming it to LEOIMG.nbh and then trying to install it with the tricollor screen, it fails at 100% just like the customRUU. Installing de original Windows ROM makes it error out at 8 or 9 percent (radio is the first step so it errors out at that I suppose) depending on the SPL version. When installing through RUU it always gives me the 290 Invalid Command Error (290 Ongeldige opdracht) I have tried multiple HSLP versions and am now using 2.08.HSPL.
When the phone boots up it does not display the 3 lines of red text in lower left corner, normally it displays version number there including radio as far as I know.
I really don't now what to do to solve this problem, I've been at it for more than 8 hours now, does anyone know of a solution?
Thanks, MdR15
Click to expand...
Click to collapse
Hi,
Before starting anything,BACKUP YOUR DATA.
Make sure you have correct MAGLDR ROM for your phone.(TMOUS or EU/INTERNATIONAL)Do NOT unzip it.
Download KSUBEDI's TOOLKIT (Don't forget to thank him for his work)
Open HD2 Installer Toolkit:
Enter bootloader:hold down volume button when you power on phone.When you are on tri-color screen,insert cable to usb.When screen changes from "serial"to "usb",proceed.
Install HSPL 2.08 HSPL.
Wipe using Toolkit Task 29 (Enter bootloader:as above)
Flash radio...download HERE(Enter bootloader:as above)
Install MAGLDR using Toolkit (Enter bootloader:as above)
(when magldr has loaded,power on and enter by holding power button until you see magldr screen.)
Repartition according to ROM requirements.(via number 5 usb flasher)
(when this is done,Go to ad recovery>advanced>Partition SD Card.1024m with 0 swap)Remember: ALL data on your SD Card will be erased!(Therefore,back it up)
Then go to ad recovery and wipe data,cache partition,and dalvik(advanced).
Then go to install zip from sd card
Choose zip from sd card (which you should have placed on the root of your sd card,using a card reader)
After installation,reboot.
Give it time.
Some ROMS take 15-20 minutes to install.

I Already did that, and the point is, the Radio won't install, and as I understand, the rest won't work because of this either.
EDIT: now I have even tried the implausible freezer method (putting the phone in the freezer for a while, this also changes nothing). I really don't know what to do now. I have also found out that it won't let me boot up ROMS installed through the USB flasher in magldr, it then enters an endless loop on the HTC quetly brilliant scene. Help, please.

Doesn't anybody know of a solution? As far as I can tell malybru didn't even read the opening post. The point is: I can't install radio, once I've gotten that installed I will have no problem installing ROM's, I know how that works.
Thanks,
MdR15

MdR15 said:
Doesn't anybody know of a solution? As far as I can tell malybru didn't even read the opening post. The point is: I can't install radio, once I've gotten that installed I will have no problem installing ROM's, I know how that works.
Thanks,
MdR15
Click to expand...
Click to collapse
Hi,
I did read your post,and I thought you were having problems with the order of things.Hence,my post.
Try again to flash an original ROM.
Go to HTC site>support>download>ROM upgrade and choose appropriate ROM upgrade for your phone
Change the .exe to .zip and
Extract with winrar or 7z the RUU_Leo_HTC_****************************_Ship.zip
find the larger *.nbh file and rename it to leoimg.nbh and place this file on an sd card that is 4gb or less.
The correct ROM will contain the correct radio ,which will help with your problem.

sorry, I have tried multiple clean installs, doing everything from the start. But the radio won't install witch is causing this problem. Installing some ROM's via the Dark Forces method makes it boot a single time, then it enters a loop with HTC quietly brilliant. Doing the clockwork method makes it hang on the HTC logo of the ROM, I have already tried to wait for multiple hours, but nothing happens.
I have seen others with this radio issue, getting the 290 error, but none of the solutions there worked for me.
I have, in fact, installed Android ROM's before, but this is the first time something like this happened.

MdR15 said:
sorry, I have tried multiple clean installs, doing everything from the start. But the radio won't install witch is causing this problem. Installing some ROM's via the Dark Forces method makes it boot a single time, then it enters a loop with HTC quietly brilliant. Doing the clockwork method makes it hang on the HTC logo of the ROM, I have already tried to wait for multiple hours, but nothing happens.
I have seen others with this radio issue, getting the 290 error, but none of the solutions there worked for me.
I have, in fact, installed Android ROM's before, but this is the first time something like this happened.
Click to expand...
Click to collapse
Hi,
Another possibility for reboots is a bent battery pin.
Have you checked these?

I have also read about bent battery pins in other threads, the ones in my hd2 aren't bent.
It is called a radio-brick right? Still some people have been able to solve this.
I appreciate you're helping me though

MdR15 said:
I have also read about bent battery pins in other threads, the ones in my hd2 aren't bent.
It is called a radio-brick right? Still some people have been able to solve this.
I appreciate you're helping me though
Click to expand...
Click to collapse
Sorry,I could not help.
Good luck ,anyway.

MdR15 said:
I have also read about bent battery pins in other threads, the ones in my hd2 aren't bent.
It is called a radio-brick right? Still some people have been able to solve this.
I appreciate you're helping me though
Click to expand...
Click to collapse
Appreciations goes very far if there is a "THANKS" involved and seems hes tried helping you i bet he would "APPRECIATE" it if you hit the thanks button

So, nobody knows of a solution?

Now,, I'm in same situation.
I've been used Nandroid for about 8months but there wasn't that kind of big issue.
I think it is caused by battery pin problem during updating procedure.
I can see one of my battery pin has bad contact with the battery.
So, I fixed it, but once it happened nothing works.
As you mentioned, I looked up every post about "Radio-brick"...
but there is no solution,yet.
I'll keep on finding a solution.
If someone find it, please share it.
Thanks in advance.

Good to see I'm not the only one, I hope you have some luck finding something, it would be a shame if our HD2's would become (as in: stay) useless.
Just to make it clearer: most of the things I've said on this thread are the symptoms of the problem, the cause is the radio not being able to install properly, if this can be solved, the other things will go away too.
Thanks

Solution
I solved it!
I found a ROM that works without RADIO!
Click this link.
Use it with Magldr and Clockworksmod (available in the thread) and install. I was suprised to say it worked flawlessly altough you will probably need to reboot a couple of times before the ROM works perfectly (fault in ROM, not radio related).
Good Luck to everybody, I hope this can help you!

In my case, I can't install Maglder again on my HD2
What I can only do is access to the tri-color screen.
When I pluged USB cable to HD2, the text "Serial" goes to "USB".
But any updates fail. It can't be proceeded on my device.
Don't know why, but I've been stuck until now.

Related

[TUT] NAND Android on your HD2

How To Install A NAND Android ROM On Your T-Mobile HD2​
(I am linking to several Original Threads in this tutorial. The "Nice Thing To Do" is hit the "Thanks" button at the bottom of those threads to let the author know we appreciate their help)
mskip wrote an excellent tut over on the Leo forums. I used his instructions to create my own method, which has never given me issues.
My method has been used by others and has a 100% success rate as of this writing.
You MUST be HSPL'd. This is not a joke. If you attempt this method without HSPL, your phone won't boot. I can not help you if you do this. If you have the 3.14 radio, try flashing: this stock ROM before HSPL. Thanks to xmoo for the link! Original thread is here.
Read the following steps. If you're confused, read the explanations below.
(Preparing)
Folder: Create a new folder on your Desktop. I named mine Flash. Put all downloads here.
HSPL: Cotulla's HSPL 3 is located here. (Original thread is here)
Task29: Download the Task29.exe program located here. Unzip it to a new folder. Replace the RUU_Signed.nbh file with your favorite radio. I use 2.15.50.14 (Original thread is here)
MAGLDR: Get MAGLDR 1.11 (or the latest version!) located here. Unzip this to a new folder.
ROM: Visit HD2 NAND Android Development thread here on XDA and download your new ROM. I am currently using this one, but will probably have a different one tomorrow Unzip this to a new folder.
SD Card: Back up everything you want to keep from your SD card, and then format it. Hint: dcim is where your pictures are stored (File System: Fat32, Allocation unit size: 16 kilobytes) Personally, I like to uncheck the "Quick format"; it takes up to an hour but ensures my card is in the best shape possible. Once your format is complete, you may replace your backed up files.
(Flashing)
(*Optional: Remove your SD and SIM cards, if you are paranoid, like me )
Connect your phone via USB to the PC and wait for any drivers to install.
Task29: Navigate to the Task29 folder and right-click on task29.exe and "Run as administrator". Your phone will reboot to the initial flash screen. You will have to reset to Bootloader.
Wait for your PC to update the drivers again.
MAGLDR: Navigate to the MAGDLR folder and right-click on ROMUpdateUtility.exe and "Run as administrator". Your phone will reboot to a new boot screen.
Wait for your PC to update the drivers again.
You should be booted to the new MAGLDR screen and see a series of options. Use your volume rocker to highlight "USB Flash" and press the green call button to select it.
Wait for your PC to update the drivers again.
ROM: Navigate to your new ROM folder and right-click DAF.exe and "Run as administrator".
Congratulations! When your phone reboots, it should start MAGLDR which will immediately boot your new Android NAND ROM!
Now, here are the details about the above instructions. You should only need them if you are confused.
(Preparing)
I use this to keep myself organized. I own several HTC phones and flash them all, so keeping things separate is a must for me.
Having a Hard Secondary Program Loader is a must for any NAND flash, whether it be Windows Mobile or Android. This will void your T-Mobile warranty, but can be fixed by flashing a Stock T-Mobile ROM via your microSD card. Check my sig for the tutorial link on how to do that.
This is the easiest method to do a task 29. The other is using mtty, which is beyond the scope of this tutorial. Task29 completely erases the existing files and partitions, preventing any loose data bits from causing issues with a new flash. You should always Task29 between NAND ROMs.
MAGLDR: A group of devs have been working on a NAND loader for some time and Cotulla and the Dark Forces Team (DAF) were the first to release a working loader. There may be more to come in the future, but this is the first (and has Tetris built in )
You should never ask the "best ROM for my phone" question. Every chef works hard on their build and considers it the best. Every user has their favorite chef and considers them the best. You should shop around to find the one that fits you best.
I consider formatting the SD card a must if I have any data written to it by a ROM. If you have installed Android to your card, you definitely want to do this!
(Flashing)
Your phone will boot into several different modes throughout the process. Each mode may require separate drives for WMDC to talk to it.
To reset to your bootloader, pull the battery and replace it. Hold down the "Volume Down" rocker and press the power (End Call) button. The phone should boot up to the tri-color screen. If it did not, keep trying!
Your PC may not need to search for drivers at this point, but wait and see anyway, just in case
MAGDLR will work as your new bootloader, but you can always access the original tri-color bootloader if you need to.
Don't worry if you get the missing "ADB" driver warning here. Only PCs with the Android SDK properly installed will have this driver.
You must flash your new ROM from the #4 screen via USB. It is the only way and the tri-color Bootloader method won't work here.
Again, you can ignore the missing "ADB" driver if it occurs. See above x2 for explanation.
Some chefs are renaming "DAF.exe" to "Install.exe" or "ANDR_INSTALL.exe". No matter what it's named, it should be the blue icon. See your ROM thread for detailed installation instructions if you get confused here.
Hope this helps!
262 Update Error
I have tried many different options, but none seem to go past the error. It showed white htc, on black background, and 0% update complete; and freeze about 7-10 minutes, then a popup with an update error message display.
[262] Update Error
I am running Energy ROM, with HSPL 2.8
The rest of my software info:
ROM version
27.Dec.2010WWE
ROM Date
08/30/10
Radio Version
2.07.50.27_2
Hardware info:
RAM size
576MB
Flash memory size
1024MB
If you have any suggestion for me, I am greatly appreciated.
Thanks in advanced.
DaraM said:
I have tried many different options, but none seem to go past the error. It showed white htc, on black background, and 0% update complete; and freeze about 7-10 minutes, then a popup with an update error message display.
[262] Update Error
Click to expand...
Click to collapse
Thanks for the plethora of information. In this case, it wasn't needed but most of the time it is
Error 262 means there is a link error between your phone and the PC. Some have solved this by re-installing ActiveSync or Windows Mobile Device Center. Some people said it was solved by simply unplugging the phone and trying a different USB port or cable.
After installing android rom in nand, device continously reboots
I followed all your steps and installed everything (there war an error encountered while installing the rom in the last step) but when my phone boots into android, after about a minute it will just restart itself and continue the same over and over without ever fully going into android.
can you please tell me how to get over this?
parthakolkata1 said:
I followed all your steps and installed everything (there war an error encountered while installing the rom in the last step) but when my phone boots into android, after about a minute it will just restart itself and continue the same over and over without ever fully going into android.
can you please tell me how to get over this?
Click to expand...
Click to collapse
It looks like the Android build you chose is either incompatible or was somehow corrupted when you downloaded it.
I suggest you delete the copy you have on your PC and download a different ROM, and then start over again.
Since there was an error, you don't want to try a fresh install without a task 29 and reinstalling hspl.
If you are using the Euro version of the HD2, don't try to install a TMOUS ROM, and vice versa. If you aren't sure, ask the chef who posted the ROM you want.
Hope this helps!
Radio Version
2.07.50.27_2
I think that the RADIO has to be 2.08.50.xx or a .50 greater.
Hello, I have some problems with my mob.phone HTC HD2: after get all the steps done my mobile stop working, then I tried install windows and tried turn on first time and my phone shows white screan with name HTC and don`t work at all,then i tried reset and Hard reset all setings and turn on again and than screan appears again with name HTC.
When i conect my phone to pc by usb, so my pc can`t find that phone.
Can you help me with this problem.
Thank you.
paulagrace said:
Hello, I have some problems with my mob.phone HTC HD2: after get all the steps done my mobile stop working, then I tried install windows and tried turn on first time and my phone shows white screan with name HTC and don`t work at all,then i tried reset and Hard reset all setings and turn on again and than screan appears again with name HTC.
When i conect my phone to pc by usb, so my pc can`t find that phone.
Can you help me with this problem.
Thank you.
Click to expand...
Click to collapse
One thing that was specified but not in the steps was HSPL. If you don't have that, you can't flash.
After having a bit of problem using the original tut you reference in your first post(basically it got locked on gogogo and a variety of problems thereafter), I am very happy to report that your variation on the method not only worked for me, but worked on the first attempt. And it has thus far done so each time I have tried it since. You cannot imagine my relief after all the frustration I had previously. So just wanted to let you know how helpful I found your post. Thanks!
The only edit I would suggest is that I believe USB Flashing is option 5 now instead of 4.
FWIW I was originally on ROM 2.13.531.1 (90963) WWE with Radio 2.10.50.26(now on 2.14.50.04).
gokun said:
The only edit I would suggest is that I believe USB Flashing is option 5 now instead of 4.
Click to expand...
Click to collapse
I just tried a fresh download of MAGLDR 1.11 and the option is still #4. Did you perchance grab version 1.12?
It would still work, but 1.12 gives you the additional option of installing and Windows 7 Phone ROM.
Yes on MAGLDR the option is 5 instead of 4.
Other than that, and the part about removing your sim and SD card, looks like an excellent guide.
apallohadas said:
Yes on MAGLDR the option is 5 instead of 4.
Other than that, and the part about removing your sim and SD card, looks like an excellent guide.
Click to expand...
Click to collapse
I am updating the tutorial to reflect on the changing menu numbers, thank you!
As far as the SIM and SD card removal, I did mention that this is optional but recommended. Yes, I realize that this is from the early days of flashing and is more than likely not needed, but in my defense this is my own method and I have never, ever had a bad flash. I've owned several HTC phones going back for a few years now and have not bricked a single one. I would consider that a pretty good track record, considering the number of posters who did brick their phone and have no idea what went wrong.
In light of your input, I will re-word the OT to ensure that the "optional" part is clarified.
Oh I totally hear ya.
I've never had a bad flash either. I think that some of the "Brickensteins" just do something wrong and don't mention it (like unplugging the phone mid-flash).
In your favor, I did read in one of the WP7 tutorials that the sd card should be removed, but since I don't plan on flashing that any time soon, I'll leave that wisdom with wiser hands
Thank you very much
HELP
Someone- anyone, I desperately need help. I went to a tmobile store because I was miserable with my HD2 and the man there gave me this website to turn my phone into an android, but i am NOT a tech person and now my phone is totally gone and I have no idea what I did wrong. I am so pissed I even did this. I need someone to help me.
my email is [email protected]
lalablu13 said:
Someone- anyone, I desperately need help. I went to a tmobile store because I was miserable with my HD2 and the man there gave me this website to turn my phone into an android, but i am NOT a tech person and now my phone is totally gone and I have no idea what I did wrong. I am so pissed I even did this. I need someone to help me.
my email is [email protected]
Click to expand...
Click to collapse
Ok do this hold the volume button down while powering on your HD2 and see if the multicolor bootloader screen comes up. If so you are not fubared. If you get bootloader you can save your HD2. Click on my Guide linked in my sig and read it then click the links at the top of my guide if you want to install Android or the link for WP7 if you want to install it. The links I have at the top of my guide are links to very good and extensive guide. If you want come post back here and I or others will help you and if you want to just PM me.
Please Help me...
I followed all your steps.. more then once. But every time I tried, I failed :[
I believe im doing everything right up until i have to connect my phone to run the DAF.exe file. When it says looking for usb, i have my phone connected but it then gives me this error;
Error Description: USB init failed
Info: .\RSPL\RSPL.cpp (723)
I would love to use Android on my HD2.. so can someone help me? ._."
ol3randon said:
I followed all your steps.. more then once. But every time I tried, I failed :[
I believe im doing everything right up until i have to connect my phone to run the DAF.exe file. When it says looking for usb, i have my phone connected but it then gives me this error;
Error Description: USB init failed
Info: .\RSPL\RSPL.cpp (723)
I would love to use Android on my HD2.. so can someone help me? ._."
Click to expand...
Click to collapse
You are using MAGLDR 1.13, not 1.11. On 1.13 (not covered by this tutorial), you have to choose "ROMUpdateUtility.exe", not "DAF.exe".

Wsod htc hd2

Before I start I googled and tried methods I could and all failed.
My phone was working Link Hereperfect with no issues I had installed the DFT LEO Stock Desire NAND Rom.
A week ago it died and I charged it and powered it back up and got the white screen. It wouldnt go away until I pushed the yellow button on the back. Problem solve I would think.
Two days ago on my way to San Francisco it restarted and turned white. I tried all methods I found here and google none work. when I hold the down vol button I do get the 3 color screen and thats it. I attached an picture of what my phone says.
bump please help
isaiah33 said:
bump please help
Click to expand...
Click to collapse
bump for what? You are just stating what happened to your phone.
My boys hd2 did this too... I plan on doing some extensive trouble shooting later this week so ill try to help you out if I can get it fixed. I guess, bottom line is, if you want android, buy an android device. ;-P
Sent from my HTC Glacier using XDA App
help us to help you
@jose makalolot
I like your answer... full of sense
@isaiah33
Do you realize that you didn't ask anything?
Do you post these nice explanations to inform us that stopping a device by removing suddenly its power supply is not good?
Then ok, thanks. Ask for a sticky.
@crx4xharder
If you're boy's phone can only boot in the first level loader... I think a week-end if long enough to make extensive trouble shooting
Ok, I agree I'm not nice... it's just to make you realize that if you want to ask someting... then ask, no need to make us imagine the question you may want someone to answer.
My question is how do I get this fixed? How do I get android back up and running. I want to get rid of this white screen.
isaiah33 said:
My question is how do I get this fixed? How do I get android back up and running. I want to get rid of this white screen.
Click to expand...
Click to collapse
What was the version of MAGLDR you had anyway? The ROM you are/were running is outdated by today's standards anyway.
I would do a task29 and start over. Then flash MAGLDR 1.3, CWM 1.3 and then a new ROM.
isaiah33 said:
My question is how do I get this fixed? How do I get android back up and running. I want to get rid of this white screen.
Click to expand...
Click to collapse
If you get bootloader simply flash a stock WM rom or MAGLDR, whats hard about that?
i tried flashing with task29 but it sticks at 0%
Do not use task29 for your problem. Fortunatly it doesn't "clear" the first level bootloader.
Press the vol-down key.
In boot loader, flash:
a/ a WM6 ROM (to do this you can just put a LEOIMG.nhh on the root of your SD)
b/ MAGLDR (the version you need for the build you want)
If you want to put a DFT build. In MAGLDR (so press "end call" and start the phone... keep end call pressed) choose the option "USB flasher" (something like this.
With DFT (in admin) flash:
a/ a DFT build
b/ CWM
If CWM, boot in MAGLDR, choose "AD Recovery" (for CWM 1.13)
In CWM choose the option to flash a zip build.
That's all... good question, good answer.
All what I said if well expained in diffferent sticky. You will find there a lot of step-by-step or video explanations.
Hope this helps.
He doesn't need to clear the first-level bootloader. You can see from his screenshots that he gets into the bootloader just fine. Task29 will format the NAND storage just as flashing a WinMo ROM does. The RUU does a task29 as part of the flashing process anyway. Doing just a task29 saves the time of flashing the ROM.
Either way, you don't "flash" task29. You run the command via mtty. I'm not sure I understand exactly what you're saying when you "flash" task29 and it stayed at 0%.
What was the meaning of my "Fortunatly"
Clear the first level... brick the phone.
So for you task29 is equivalent to flashing a WM?
With or without radio?
(real question, I really don't know exactly what it's doing...)
I know that it "cleans" the NAND but it's not enough for me.
Anyway, I realize it will be better for me to read the dedicated thread or search on google.
For him I keep my advice to do all (task29, full flash from the beggining including WM). It's useless normally but as he has a problem...
Digital Outcast said:
He doesn't need to clear the first-level bootloader. You can see from his screenshots that he gets into the bootloader just fine. Task29 will format the NAND storage just as flashing a WinMo ROM does. The RUU does a task29 as part of the flashing process anyway. Doing just a task29 saves the time of flashing the ROM.
Either way, you don't "flash" task29. You run the command via mtty. I'm not sure I understand exactly what you're saying when you "flash" task29 and it stayed at 0%.
Click to expand...
Click to collapse
For HD2 "mtty" is not required, there is a task29 nbh.
truc007 said:
Do not use task29 for your problem. Fortunatly it doesn't "clear" the first level bootloader.
Press the vol-down key.
In boot loader, flash:
a/ a WM6 ROM (to do this you can just put a LEOIMG.nhh on the root of your SD)
b/ MAGLDR (the version you need for the build you want)
If you want to put a DFT build. In MAGLDR (so press "end call" and start the phone... keep end call pressed) choose the option "USB flasher" (something like this.
With DFT (in admin) flash:
a/ a DFT build
b/ CWM
If CWM, boot in MAGLDR, choose "AD Recovery" (for CWM 1.13)
In CWM choose the option to flash a zip build.
That's all... good question, good answer.
All what I said if well expained in diffferent sticky. You will find there a lot of step-by-step or video explanations.
Hope this helps.
Click to expand...
Click to collapse
I tried updating the stock rom and it has a issue when it comes to the radio it says Radio Fail. This is the right rom I downloaded it off the tmobile website. I dont know why its failing. If you could help truc007 I am willing to help donate to you if I ge it working.
I couldnt flash the task29 so I ran the commands in mtty and flashed a rom and booted, still wsod...
Just flash back to the original ROM, then update radio, install magldr.
isaiah33 said:
Before I start I googled and tried methods I could and all failed.
My phone was working Link Hereperfect with no issues I had installed the DFT LEO Stock Desire NAND Rom.
A week ago it died and I charged it and powered it back up and got the white screen. It wouldnt go away until I pushed the yellow button on the back. Problem solve I would think.
Two days ago on my way to San Francisco it restarted and turned white. I tried all methods I found here and google none work. when I hold the down vol button I do get the 3 color screen and thats it. I attached an picture of what my phone says.
Click to expand...
Click to collapse
OK, send to me to fix it!

[Q] Potential Brick -- Need help!

Apologies to more experienced users who might be weary of newbie bricks, but I'm sitting here staring at a red, green, blue and white screen, and nothing seems to work. I've read a lot of threads, but haven't found an answer to my dilemma.
I have an HD2 running on T-Mobile USA. My computer is a PC running Windows 7. I'm trying to get Android running using the NAND method.
Currently, I've flashed SPL-3.03 as well as Magldr 1.13 -- which said it completed successfully, but I never got the Magldr menu, just the T-Mobile screen. Frozen. I've tried flashing a variety of different versions of SPL as well as a variety of different versions of Magdlr, based on recommendations in the threads.
When my screen froze on T-Mobile, I tried to reboot, did a soft reset and then a hard reset. Nada.
Any suggestions?
Thanks in advance for your help.
Merlingo11 said:
Apologies to more experienced users who might be weary of newbie bricks, but I'm sitting here staring at a red, green, blue and white screen, and nothing seems to work. I've read a lot of threads, but haven't found an answer to my dilemma.
I have an HD2 running on T-Mobile USA. My computer is a PC running Windows 7. I'm trying to get Android running using the NAND method.
Currently, I've flashed SPL-3.03 as well as Magldr 1.13 -- which said it completed successfully, but I never got the Magldr menu, just the T-Mobile screen. Frozen. I've tried flashing a variety of different versions of SPL as well as a variety of different versions of Magdlr, based on recommendations in the threads.
When my screen froze on T-Mobile, I tried to reboot, did a soft reset and then a hard reset. Nada.
Any suggestions?
Thanks in advance for your help.
Click to expand...
Click to collapse
note, in the first lines of the installation instructions you nee 2.08HSPL - not 3.03 (or any SPL). see here.
so, boot into bootloader. connect to cpu via usb. using hspl4 change to 2.08HSPL (see here for instructions and download). then flash magldr.
and off you go.
Yep that's basically the problem. Nothing will install correctly without 2.08.HSPL so just chose that from the drop down menu and install. Then install MAGLDR using the RomUpdateUtility and voila it'll work.
Thanks for the quick reply. I thought that that might be the problem, but I saw a post saying that SPL-3.03 works OK. My bad.
So, now I've downloaded DFT_LEO_MAGLDR113.DAF.rar, and extracted the files. When right click on the ROMUpdateutility.exe to run it as "Administrator" . . . it doesn't open.
Am I missing something basic?
Thanks!
Give your machine shut down, not just a reboot, power it on again and try it again. The ROM tool should work without ADMIN permissons.
It was that simple. Good to go. Vielen Dank!

[Q] 2 dysfunctional HD2's Dont know what to do anymore

MY PROBLEM IS:​I can't get the HD2 into the bootloader and/or get my PC to recognize the phone via WMDC.
Its just so unresponsive, All its doing is Vibrating constantly/Vibrating patterns/black illuminated screens/ & very rarely, the "Loading please wait" screen with the green android and some other figure I forgot in the bottom right corner. Then on the top it gets stuck on the "aMAGLDR v1.11" and other descriptive words/numbers below it, on the top center.
- INTRO -​
Hi, I'm new to XDA-developers forum, and I have 2 non-working HD2's that have been sitting around for quite some time now.
I've recently tried to get it fixed and get into this type of phone modding, as I can see HD2's are very popular for tweaking software's and such.
I have been searching around the web, more so the XDA forums, for answers to my "Special case" (yes I've seen the video when you first sign up for an account on XDA, quite funny ) of a conundrum...
Anyway, 1 HD2 is fully dysfunctional and shows no sign of life (No vibration/lights) but the lower portion of the back does get warm when I try and charge it. I have no hope for this HD2 and I think its only good for spare parts for someone else.
The other HD2 is "somewhat" functional. Sometimes if I get lucky it vibrates continuously or repetitively.
What I know about the half functioning phone:
Let my friend have it, he did some flashing of the ROM, it stopped working after awhile, and then he gave it back to me because he got another phone.
Sometimes after turning it on, it gets suck on the "aMAGLDR v1.11" screen.
I've searched up "MAGLDR" and know that its some kind of custom bootloader or so.
I've searched up how to update it to "MADLDR v1.13" and update the radio and/or use the "RUU-LEO" file.
I have all those files&programs downloaded and ready to go.
Thank you for reading my thread​
It would be AWESOME if someone could help me, or even inform me of what has happened with it. If you need further answers about my two HD2's please ask me the questions, I would love to try and answer them!
DavisN said:
MY PROBLEM IS:​I can't get the HD2 into the bootloader and/or get my PC to recognize the phone via WMDC.
Its just so unresponsive, All its doing is Vibrating constantly/Vibrating patterns/black illuminated screens/ & very rarely, the "Loading please wait" screen with the green android and some other figure I forgot in the bottom right corner. Then on the top it gets stuck on the "aMAGLDR v1.11" and other descriptive words/numbers below it, on the top center.
- INTRO -​
Hi, I'm new to XDA-developers forum, and I have 2 non-working HD2's that have been sitting around for quite some time now.
I've recently tried to get it fixed and get into this type of phone modding, as I can see HD2's are very popular for tweaking software's and such.
I have been searching around the web, more so the XDA forums, for answers to my "Special case" (yes I've seen the video when you first sign up for an account on XDA, quite funny ) of a conundrum...
Anyway, 1 HD2 is fully dysfunctional and shows no sign of life (No vibration/lights) but the lower portion of the back does get warm when I try and charge it. I have no hope for this HD2 and I think its only good for spare parts for someone else.
The other HD2 is "somewhat" functional. Sometimes if I get lucky it vibrates continuously or repetitively.
What I know about the half functioning phone:
Let my friend have it, he did some flashing of the ROM, it stopped working after awhile, and then he gave it back to me because he got another phone.
Sometimes after turning it on, it gets suck on the "aMAGLDR v1.11" screen.
I've searched up "MAGLDR" and know that its some kind of custom bootloader or so.
I've searched up how to update it to "MADLDR v1.13" and update the radio and/or use the "RUU-LEO" file.
I have all those files&programs downloaded and ready to go.
Thank you for reading my thread​
It would be AWESOME if someone could help me, or even inform me of what has happened with it. If you need further answers about my two HD2's please ask me the questions, I would love to try and answer them!
Click to expand...
Click to collapse
Those repetitive vibrations on starting are not a good sign(usually it means a non/working CPU/motherboard)!
You should flash a stock ROM and see what happens, but I suspect it won't boot up and you'll get again those vibrations: it worth try it and let me know!
Good luck!
Are you able to get to the tricolored screen by holding the power button and the volume down button? If you can get there, you may be able to task29 it and flash it with a new radio. My guess is someone flashed it with the wrong radio. Once it has the correct radio, if there is no hardware damage, it should work again.
I broke my digitizer . I'll be interested in buying the completely dysfunctional one from ya . Send me a pm if you're interested .
Sent from my HTC HD2 using Tapatalk
joshnchen said:
Are you able to get to the tricolored screen by holding the power button and the volume down button? If you can get there, you may be able to task29 it and flash it with a new radio. My guess is someone flashed it with the wrong radio. Once it has the correct radio, if there is no hardware damage, it should work again.
Click to expand...
Click to collapse
Yes, after I posted this thread, I was able to get into the tricolored screen. After that I tried to update the MAGLDR to V1.13, the screen got into the HTC loading screen with a progress bar stuck at 0% then on the computer it says there has been a communication error.
So my problem now is communication from my HD2 to PC, Which is weird because on the tricolored screen, the text switched to USB and I thought I figured it out, but no...communication error.
I am willing to do Task29 but I'm not aware of the risks or precedures.
Ok first off go to here and download the HD2 NAND Toolkit then install it o. Your computer. Next open the toolkit and then connect your HD2 to your computer via USB. Then use the toolkit to run the Task 29. Be warned though the Task 29 will totally delete the ROM partition of the NAND memory in your HD2 so you will not have a ROM on the device then so it will not boot to anything but the bootloader. Next use the Toolkit to flash either a Window's Mobile ROM, MAGLDR, or clk, you can also use it to flash Clockwork Mod Recovery.
T-Macgnolia said:
Ok first off go to here and download the HD2 NAND Toolkit then install it o. Your computer. Next open the toolkit and then connect your HD2 to your computer via USB. Then use the toolkit to run the Task 29. Be warned though the Task 29 will totally delete the ROM partition of the NAND memory in your HD2 so you will not have a ROM on the device then so it will not boot to anything but the bootloader. Next use the Toolkit to flash either a Window's Mobile ROM, MAGLDR, or clk, you can also use it to flash Clockwork Mod Recovery.
Click to expand...
Click to collapse
Ok, I have gotten the Tool kit but I wasn't able to perform task29.
I got a communication error again, I have tried to do task29 twice.
Here are some screenshots...
HD2
So my problem is still with the communication errors I keep getting if I try to do anything.
Is there anything I can do with the Micro SD card?
DavisN said:
So my problem is still with the communication errors I keep getting if I try to do anything.
Is there anything I can do with the Micro SD card?
Click to expand...
Click to collapse
You can run a Task 29 via SD card. You need to go to here and download the Repack by ShaDrac. Then right click the file and unzip it. Then find the .nbh file and rename it to LEOIMG.nbh and place it on the root of your SD card. Then boot into the bootloader and follow the on screen instructions.
T-Macgnolia said:
You can run a Task 29 via SD card. You need to go to here and download the Repack by ShaDrac. Then right click the file and unzip it. Then find the .nbh file and rename it to LEOIMG.nbh and place it on the root of your SD card. Then boot into the bootloader and follow the on screen instructions.
Click to expand...
Click to collapse
The only thing I need to put on the SC card is the LEOIMG.nbh right
DavisN said:
The only thing I need to put on the SC card is the LEOIMG.nbh right
Click to expand...
Click to collapse
Yeah that is it, just copy the .nbh file and rename it to LEOIMG.nbh. Then copy it to the root of your SD card.
Edit: Once the Task 29 is done your HD2 will only boot to the first splash screen and you will be able to boot into the bootloader also. This is because the Task 29 removed the ROM from your HD2 and you will have to re-flash clk or MAGLDR then a recovery and then a Android ROM. Or you can always flash as Windows Mobile ROM.
T-Macgnolia said:
Yeah that is it, just copy the .nbh file and rename it to LEOIMG.nbh. Then copy it to the root of your SD card.
Edit: Once the Task 29 is done your HD2 will only boot to the first splash screen and you will be able to boot into the bootloader also. This is because the Task 29 removed the ROM from your HD2 and you will have to re-flash clk or MAGLDR then a recovery and then a Android ROM. Or you can always flash as Windows Mobile ROM.
Click to expand...
Click to collapse
Alright, I got into boot loader mode, then it goes onto a completely white screen with "Loading..." on the top.
After 5 minutes or so, the screen turns off with no instructions to follow after "Loading...".
I pressed the power button to see if it still works and goes into the old MAGLDR v1.11 screen with no menus/options.
Am I suppose to keep holding the Vol down button or something, I think im doing it wrong
Edit: I charged the phone before trying it again for a few hours and I think it was on the white "Loading..." screen for the whole charge.
I don't know whats wrong with it :d
DavisN said:
Alright, I got into boot loader mode, then it goes onto a completely white screen with "Loading..." on the top.
After 5 minutes or so, the screen turns off with no instructions to follow after "Loading...".
I pressed the power button to see if it still works and goes into the old MAGLDR v1.11 screen with no menus/options.
Am I suppose to keep holding the Vol down button or something, I think im doing it wrong
Edit: I charged the phone before trying it again for a few hours and I think it was on the white "Loading..." screen for the whole charge.
I don't know whats wrong with it :d
Click to expand...
Click to collapse
First off sorry for the lag in response but I went to sleep not long after I posted my last response last night. If you never saw a box appear on the HD2 screen that asks you if you wanted to install the update and to press the power button to do so, then you did not run the Task 29. I am pretty sure you didn't anyway because you said you could still boot into MAGLDR 1.11 and if you had run the Task 29 then MAGLDR would no longer be on your HD2.
When you boot into the bootloader by holding the volume down button down and powering on the HD2 continue to hold the volume button down until you see searching. When you see searching you can release the volume down button and then you should see the window pop up that ask if you want to install the update and if so to press the power button to continue. Press the power button and the Task 29 will run, you should see a progress bar on the screen of the HD2.
Once the progress bar is done the HD2 should restart, but it will not have a ROM to boot so just pull the battery to turn it back off. Next, if you want to use Android, you need to install MAGLDR 1.13 or clk. You can install either one of these via SD card, just like the Task 29 you will have to copy the .nbh file for the custom bootloader you want to use to the root of your SD card and rename it LEOIMG.nbh. Make sure to remove the LEOIMG.nbh file that you used for the Task 29. Personally I prefer clk cause it makes the HD2 run like a native Android device, but you are having a communication error so this may lead to problems if you use clk as you have to flash Clockwork Mod Recovery via USB when you use clk. You know I would suggest you try a different USB cable as you might just have as faulty USB cable and that is what is causing the communication error. I would highly suggest you do this before trying to do anything at all more with the SD card. If you try another cable and it does not work then your HD2 more than likely has a faulty mini USB port.
If you try another cable and it works you can just use the toolkit to run the Task 29 and then use it to install either MAGLDR 1.13 or clk and then Clockwork Mod Recovery.
T-Macgnolia said:
First off sorry for the lag in response but I went to sleep not long after I posted my last response last night. If you never saw a box appear on the HD2 screen that asks you if you wanted to install the update and to press the power button to do so, then you did not run the Task 29. I am pretty sure you didn't anyway because you said you could still boot into MAGLDR 1.11 and if you had run the Task 29 then MAGLDR would no longer be on your HD2.
When you boot into the bootloader by holding the volume down button down and powering on the HD2 continue to hold the volume button down until you see searching. When you see searching you can release the volume down button and then you should see the window pop up that ask if you want to install the update and if so to press the power button to continue. Press the power button and the Task 29 will run, you should see a progress bar on the screen of the HD2.
Once the progress bar is done the HD2 should restart, but it will not have a ROM to boot so just pull the battery to turn it back off. Next, if you want to use Android, you need to install MAGLDR 1.13 or clk. You can install either one of these via SD card, just like the Task 29 you will have to copy the .nbh file for the custom bootloader you want to use to the root of your SD card and rename it LEOIMG.nbh. Make sure to remove the LEOIMG.nbh file that you used for the Task 29. Personally I prefer clk cause it makes the HD2 run like a native Android device, but you are having a communication error so this may lead to problems if you use clk as you have to flash Clockwork Mod Recovery via USB when you use clk. You know I would suggest you try a different USB cable as you might just have as faulty USB cable and that is what is causing the communication error. I would highly suggest you do this before trying to do anything at all more with the SD card. If you try another cable and it does not work then your HD2 more than likely has a faulty mini USB port.
If you try another cable and it works you can just use the toolkit to run the Task 29 and then use it to install either MAGLDR 1.13 or clk and then Clockwork Mod Recovery.
Click to expand...
Click to collapse
Whoa, after I read your post, I went and found another cable, attached it to the PC and turned on my HD2, it goes to the MAGLDR v1.11, but it has the options where I can use the volume buttons to choose things which I have never seen on this phone before lol.
What do you suggest I do since the options came up.
Wipe it and do MAGLDR v1.13
Or do one of the options on the screen
Okay well I've tried to task29 w/ the new cable, and it still does a communication error so there might be a problem with the mini USB port.
I tried to do task29 again via sd card, and this time I held down the volume down button for like 5 minutes until my fingers slipped, but there was no "searching" screen, just a "Loading..." screen and then it turns off after 10 mins.
I'm trying to get into that MAGLDR screen again with the options but I don't know how to, it was just too random.
I kind of wonder if a wrong radio was flashed to the phone and it got semi-bricked. I bought a phone once that was like that and tried to repair it and was unable to. I think there are people out there that can jtag it.
Maybe dude, right now im just waiting until someone knows exactly whats wrong with my phone and if they can fix it :d
i did do something to the radio, but i made sure it was the correct version according to their list of radios and the radio listed on my phone.
Anyway, im pretty much stuck. cant wipe via USB cable, of 3 different kinds.
and i cant wipe via sd card either.
will go back a few years and try and find old posts on old Kaiser thread,this starts to sound familiar with white screen and comms fail,if I remember properly it was/is problem with spl/hspl.
can you post what info does show on any boot screen.
am busy at moment will try searching later tonight.
Sent from my NexusHD2 using xda premium
One time I was able to flash something onto the phone and it was the "Radio_Leo_2.15.50.14" thing...
I don't remember why I did this but I did made sure it was compatible and it worked.
So it may have been the radio, I am not sure.
I do have pics of the boot loader screen before and after the flash.
If there are no solutions, I might as well sell them both. Which I'm about to do real soon

I think my phone is bricked? please help

Everytime I turn on my phone, it goes straight into bootloader mode. I don't know what to do. I've been trying to google for the past hour or so, and no luck. Can anybody help?
Could be that your vol down button is stuck, try pressing and releasing quickly a few times ...just a thought!
PS. Your phone is not bricked if you can get to boot loader!!!
i tried that, and it didnt work. any other ideas?
can anyone please help?
Maby you don't have an OS. So try to flash a stock rom.
Sorry for bad english.
i tried that, but it either loses connection or it will say something about, how the the version of the o.s doesnt work for my phone. also on the phone itself, when it tries to download the rom, where a htc image is normally there, it isnt.
i have no idea what to do
It would be helpful to understand what you were running on your phone before the problem occurred?
The Bootloader you are seeing - I assume it is the hacked Cotulla one?
If you connect your phone to a PC does the bootloader screen show "USB" rather than serial?
If you have Cotulla bootloader and USB connection to PC, I'd start again with a clean install....not sure what you were using...but Typhoon is nice and Stable
http://forum.xda-developers.com/showthread.php?t=933951
It has a "clean installation" guide that you can follow....
http://flashmirrors.com/files/ytjzury5kvx9p91/Clean Installation.pdf
HTH.
K
I was trying to reinstall a stock gingerbread o.s on the phone, but something happened, and it wouldn't allow me to. So i just wanted to reinstall stock tmobile rom, and install android after that.
Yes i have cotulla bootloader, and whenever the phone starts up, it says serial, but it ill change to usb when i plug it in.
i couldnt open the pdf file.
mh48 said:
i couldnt open the pdf file.
Click to expand...
Click to collapse
If you are getting errors while flashing the stock ROM, as in windows mobile, then 99% of the time you have bad NAND memory and the phone needs to be jtaged or the motherboard needs to be replaced. Ive experienced a lot of these similiar threads over on PPCGeeks with the HTC Touch Pro 2
whenever the image file tries to update through bootloader i get an error/update image fail due to the radio i think. it says its spl 2.08 hspl, i tried uninstalling hspl but that didnt work. what could be the problem? or am i pretty much out of luck?
mh48 said:
i couldnt open the pdf file.
Click to expand...
Click to collapse
Those mirrors do seem broken.
Well this thread gives step by step instructions.
http://forum.xda-developers.com/showthread.php?p=11097380
you have HSPL, so you need to task29, MAGLDR, CWM and then a ROM.....it'll be interesting to see if you get anywhere....
Suggest following it step by step and seeing what happens before we write off your phone!
im not able to install magldr or a new rom, it either loses connection, or says it isnt compatible
mh48 said:
im not able to install magldr or a new rom, it either loses connection, or says it isnt compatible
Click to expand...
Click to collapse
Well if you have Cotulla HSPL, and USB shown on that screen, and are connected to your PC and Task29 is not running then I'm afraid I'm out of knowledge....
Sorry.
so i found that i have a ruunbh error, what do i have to do in order to fix this?
with ruunbh I suggest you go back and flash a stock WM rom.
That has worked for some.
If that gets you back running (at winmo 6.5) then you need to start the Android process again....
......By starting with HSPL and moving on through task29, radio, magldr, clockworkmod and a android rom.
going back to winmo is described here:
http://forum.xda-developers.com/showthread.php?t=935145&highlight=stock+rom
Let's see if you can go back to winmo first!
it keeps giving me an update error, when i try to install a custom wm rom and official rom any other suggestions?
So of the steps below....where and what is the update error?
--------------------------
If you are using a 512MB ROM HD2, just download the official firmware from HTC's website. The recommendation is to use a 1.xx or 2.xx ROM, do not use a 3.xx ROM.
Download 7-zip, make sure it is 9.20 version and up.
Using 7-zip, open the official ROM update exe file. Do not execute it.
Inside you will see RUU_signed.nbh, extract just that file. Nothing else.
rename RUU_signed.nbh, to LEOIMG.nbh
Copy LEOIMG.nbh into your SD card root directory which is FAT16 or FAT32 formatted.
Unplug the battery from the HD2, count to 10, replace the battery.
Hold the VOLUME DOWN button, DO NOT LET GO.
Press the POWER BUTTON, then let go.
Follow the instructions on the screen when the device goes to RECOVERY mode.
im using tmobile u.s version
You really like being brief don't you.

Categories

Resources