Tired of the hot pink T-Mobile USA Stick Together logo greeting you whenever your HD2 crashes and restarts? As you might know, there are 4 parts to the splash screen, and plenty of threads for the 3rd(GIF) and 4th(Welcomehead), but none for the first two-part Static ones, which require flashing and HSPL. Since we've been warned enough times to not use the euro HD2 stuff to flash, and there are no USA HD2 first boot screens that does not include a rom...
Let me start a USA HD2 thread with ready-made first boot splash screen to flash via microSD.
WHAT:
15 second LEOIMG.nbh 480x800 static first splash screen with retro dark Windows logo to replace the USA HD2 initial static Pink StickTogether logo. This leoimg.nbh will cover both parts before the animate GIF.
HOW: instructions
1. You will need HardSPL, (here)
2. You will need a microSD formatted to FAT32
3. Place LEOIMG.nbh from the zip into the root of your microSD.
4. With phone off, sim out, & microSD IN, go into bootloader by pressing VolumeDown and RedPowerButton.
5. Follow the instructions in bootloader (POWER to go on, or VolDown to abort).
6. Shouldn't take more than 10 seconds before it completes.
7. Take out the microSD and erase the leoimg.nbh just in case.
8. Soft Reset. That's it! DONE!
If you already have HardSPL, this whole process shouldn't take more than a minute.
Recap:
--You will need HardSPL, since this is considered flashing,
--There is No Radio, nor SPL, nor ROM, nor animatedGIF in this LEOIMG.nbh file.
--MicroSD must be FAT32.
--You won't need ActiveSync, microUSB cable, customruu.exe, nor computer, except to erase the leoimg.nbh from your microSD card when done.
WHY: purpose
--for when you flash a custom rom with some weird narcissistic boot logo.
--for if pink aint your color,
--for if you'd like to change splash screens as often as wallpapers.
WHO: credit
--Samsamuel (link) for the command prompt scripting and instructions on how to create the leoimg.nbh from the nbimg tool,
--POF (link)for the nbimg BMP to NBH tool
--Reignzone (link) for starting the thread on animated GIF boot splash
--mskip for flashing via microSD instructions
Let's keep this thread a clean repository, just post your ready-made custom first Splash Screen leoimg.nbh
--To learn how to make your own Parts 1&2, follow the short Samsamuel thread above.
--To learn how to make your own Part 3, follow Reignzone thread above.
--For a collection of Part 3 animated GIF see this Jaguarali thread.
Following usual disclaimers, I give no guarantees. But it looks like this same nbh file could be used for both UStmo hd2 and euro hd2 (same padding size, command prompt script, and file size). Since I've only tested this in the USTMO, Here's the ustmobile stock splash if you need it.
disclaimer 2: double check the file size of the leoimg.nbh in your microSD, as you should not use the microSD method for any file that might have an SPL in it. Erase leoimg.nbh from the card after flashing.
nice straightforward writeup.
just for completeness of info, you can also flash these using customruu over usb, just like radios and roms, no problem, and yes they should be cross compatible.
samsamuel said:
nice straightforward writeup.
just for completeness of info, you can also flash these using customruu over usb, just like radios and roms, no problem, and yes they should be cross compatible.
Click to expand...
Click to collapse
Samsamuel, you answered me in another thread that we don't have to have HSPL in order to change the boot screen, however, this thread makes it clear that you do...
WHICH IS IT???
mfrey0118 said:
Samsamuel, you answered me in another thread that we don't have to have HSPL in order to change the boot screen, however, this thread makes it clear that you do...
WHICH IS IT???
Click to expand...
Click to collapse
The first screen requires HSPL3 to flash over. However, the second and third portions do not. Those are the animated ones and the one after the animation.
Cheers.
mfrey0118 said:
Samsamuel, you answered me in another thread that we don't have to have HSPL in order to change the boot screen, however, this thread makes it clear that you do...
WHICH IS IT???
Click to expand...
Click to collapse
I did? then i apologise, i certainly didn't mean to. So sorry.
(got a link for me to edit it please?)
Is There anyplace where i could find Different pics for the startup screen?
bigal1336 said:
Is There anyplace where i could find Different pics for the startup screen?
Click to expand...
Click to collapse
+1
I was able to do it on my device and I want it to be change to something different.
An idea (always dangerous)
So, this is a clear way of explaining things, and even though I did get to this same point via the LONG route, here is what I would LOVE TO SEE:
There are a lot of great 640x800 graphics floating around, some truly beautiful. It kind of bugs me that the only access we have to replacement of the initial splash screen and really, just about everyone (everyone that's SANE, I should qualify) wants to kill that Pink "Stick This" T-Mobile screen! I mean, when I 1st got the phone, I used to hide it while this screen was in, LOL!
What I am wondering is this:
1. How difficult is it to embed/tweak/modify a graphic and then package it with RUU to create these? If its complex, a tutorial or write up would be really great.
2. Are there limits on the graphic, as in file size, DPI etc? Like a lot of techies, I am pretty handy modifying and converting graphic files. All I need at this point is the process, since there seem to be extremely limited choices in this area
None of this is intended to dis the graphic presented in this thread. In fact, it is really nice. But it's someone else's you know? I want something unique, if I can make it my own, I would be happy.
Anyone care to explain whats needed to make that happen? Thanks to any and all that contribute to this.
its easy, twenty mins start to finish.
http://forum.xda-developers.com/showthread.php?t=684301
Thanks to all for the instructions, I have made my splash screen and did everything to the T, atleast I believe I did. Anyway I've made a splash screen and converted in to a 24 bit, bmp file. I've used the nbimg-1.1 win32.exe to make the .bmp.nbh file which I used to flash on to my hd2. I went to the process of flashing but when the hd2 restarted the same pink stick together was still there. I don't know what I did wrong. The only thing I can see is that I did not used HSPL3, I have HSPL2 on my phone already and thought that would be ok. Does anyone know if using HSPL3 is mandatory for this, like I said I have HSPL2 on my phone already. Also if I flash with the HSPL3 wouldn't that completly erase my phone again, kinda like a hard reset?
Thanks
J
Sim-Unlocked TMOUS HD2
Manila version: Touch X-Treme 2 2.0.00.02
ROM: 2.13.531.1 (90963) WWE
Radio: 2.10.50.26
when you enter bootloader, it should say 'x.xx.hspl' next to spl, so long as it does, then its flashable. doesnt matter which.
Contribution
Here's what I now have as my start up splash, I got tired of the full on white pink but rather enjoy the Stick Together slogan.
Maybe someone else will like it haha =P
Includes the bmp and nbh but you really only need the nbh.
Ha ha Metastable... Excellento... i loke it i loke it
LeoDroid Windows boot splash screen
Here're two more first boot splash screens, to show off your HD2 LeoNdroid LeoDroid Desire Froyo
Thanks Demaxmeister for the LeoDroid Ubuntu wallpaper and icon.
Another Big Thanks to the devs for making LeoNdroid possible.
Instructions: see first post
i cant get mine to flash this nbh file, i used 2 cards so far, reformated to fat32, hold down vol down + pwr button, and i dont get the option to flash and im on hspl...
nm, i got it guess the file name has to be lower case nbh, not NBH, weird...
I don't know why people hate the t-mobile splash screen, If you think hard stick together can turn to stick to-get-her
I cant get it to work, I tried like 10 time, I reformatted my cards, and made sure the name was right, tried Serial, and usb, but It gives me no flash option.
i flashed HSLP3
any body? [FALSE ALARM]
Edit: Had to try 4 different sd's...4ths the charm
HardSPL3 is telling me, that it will delete everything on my phone. Is that true? Just for changing the boot screen, I have to install everything again? (ie. contacts, programs, files, settings..)
Worked out great thanks! I was pretty sick of the pink logo.
fyi, when pressing down volumedown and powerbutton, leave your finger on the powerbutton only after awhile, I was holding down on both and the bootloader quit because it thought I was cancelling the flash
Related
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".
I was having some freezing issues and I was told to do a task 29 -.-
Big mistake.
I followed this step
http://forum.xda-developers.com/showthread.php?t=644781
I used the
Repack by ShaDrac (Recommended):
And when the steps said
"use the leocustomruu.exe provided with your favorite rom package to flash a new rom"
I went to this page
http://forum.xda-developers.com/showthread.php?t=791303
and downloaded the first one "ROM version - 6.5.3.1.1 Vibrant GTX beta"
then it wont pass the splash screen. I was told to update my RADIO, so I went here
http://forum.xda-developers.com/showthread.php?t=611787
and downloaded Leo_RADIO_2.10.50.26** and used CustomRUU to install it, but when I get to 99% it crashes.
What can I do?
I can still see the flash screen, so I'm guessing it's not fully bricked.
I have a US TMobile HTC HD2, which Radio should I install!
Plz HELP!
Have you tried flashing via SD card instead if USB??
a) Put the nbh file onto root of your SD card and rename it leoimg.nbh
b) Go into bootloader by powering on the phone while holding the Volume Down.
c) Flash the rom.
TheATHEiST said:
Have you tried flashing via SD card instead if USB??
a) Put the nbh file onto root of your SD card and rename it leoimg.nbh
b) Go into bootloader by powering on the phone while holding the Volume Down.
c) Flash the rom.
Click to expand...
Click to collapse
Flash the RADIO? I did put the RADIO on the root and renamed it to leoimg.nbh and nothing. The RVB menu is there and it says serial.
Any help? Plz?
What Radio do I need to download??!?!
sounds kind like mine
this sounds kinda like what happend to my hd2 look at my crazy guide i just posted in http://forum.xda-developers.com/showthread.php?t=961001 post 9
Please read the whole post first sorry about the mess it is my first post thanks to everyone here on xda who came up with everything i used to do this There is guides for this xda has a lovely list of tmous roms if you are on t mobile in the us http://www.xdafil.es/index.php?path=HD2/TMOUS/
i would start with the RUU_Leo_1_5_TMOUS_2.02.531.MASD_S__Radio_Signed_15 .29.50.07U_2.06.50.04_TeleNav-5.5.42.zip
extract the .exe file if it has one than extract the RUU_signed.nbh from the .exe file using win war or 7 zip than rename it to LEOIMG.nbh and place it on a newly formatted microsd not a microsdhc and i had problems with anything over class 4
place it in your phone and hold the volume down button and power button as loading comes up let off volume down power button will start the flash(i was only able to do complete flashes in the freezer if not it would hang or get radio errors)
i also had a tmous which did not want to flash the radio i would get an an error and rsa fail it sounds crazy but i wrapped it in plastic and stuck it in the freezer for a while before and during the flash this was the only way i could install the radio and actually see rgd information on boot screen after this first one you will have an old test rom with an old spl you cannot change to hspl from here i also was not able to go straight to 2.10, i had to step up from RUU_Leo_1_5_TMOUS_2.03.531.6_Radio_Signed_15.30.50 .07U_2.06.50.23_3_Test.zip, to RUU_Leo_1_5_TMOUS_2.03.531.6_Radio_Signed_15.30.50 .07U_2.06.50.23_3_Test.zip the same way i did the first one,hard resetting after each one and let it open windows completely to know it is working. than i believe there is an hspl3 file somewhere out there with all thanks to DarkForces Team HardSPL3 by bepe and Cotulla i will try to attach it that will work with spl 2.02 wich you should now be on now you can download your radio in the master radio thread http://forum.xda-developers.com/showthread.php?t=611787
i also just renamed the ruu_signed.nbh to LEOIMG.nbh and ran through sd i seem to have problems through usb and i was trying to be careful with the radio
once you got the radio you want you could flash the rom preferably running task 29 before or get yourself magldr to install through nand i also stuck my laptop an the freezer with the phone to get wp7 completely installed i did all this mess with a phone that had a broken screen i think there is like thermal compound over the processor to the case that is not on right and overheats when not in the operating system like a crappy old laptop with its fans full of stuff trying to install xp. and while a stock rom was being installed the usb was pulled during the radio installation i hope this helps i belive i saw one post to stick it in the freezer out of everything that i think helped the most.i also notice i have to put it in the freezer at boot too sometimes or i will get a fatal hit error i think its just over heating..... i also have an hd2 which has never been opened before that i have never had to stick in the freezer it gets flashed quite abit right now running gingerbread on normal hd2 and wp7 dual boot android 2.2 on the one i had to freeze i hope this helps i was here for weeks reading reading i was stumped cus my first hd2 and g1 were so eazy i will update this post once i stop being lazy and open the phone again to replace the goop to see if that is the problem
Thank you for reading my jumble and thanks again to all you phone heads here on xda which without you none of this would be possible and i would not have wp7 and gingerbread on my hd2 : D
i hope i dont get in trouble for posting this again you can remove one if you like moderator just trying to help after all the help i have gotten here
Well I don't know which Radio I need to download and install. I also dont have a microsd I only have a microSDHC (16GB and a 4GB)
UPDATE: OMG you saved me! Thank you so much! From that link I downloaded a TMOUS (TMOUS means T MObile US... Lol I didn't know that) and now is working fine!
YEs!, so happy!
Thank you again.
Hi Guys,
I am getting desperate with my HD2. I've read and tried most of your advices here on XDA, but I can't get rid of HSPL from my phone and return to stock ROM to send it for repair.
When I tried to flash my phone directly from SD card with renamed .nbh file, it would always get stuck at some point of installation and would leave me with phone that wouldn't boot, neither Android nor Windows. When I flash the phone thru USB while in boot loader mode (i tried few roms and radios, most recently radio 2.06.51.07 with HTC_WWE_1.66.405.2 rom)
It would install correctly and even boot the Win Mobile, but once restarted it wouldn't boot again and would get stuck on a blank white screen. Also the HSPL is still shown on the boot loader screen.
when I repeated the process and installed both radio and rom again, the same thing would repeat and I'm stuck on blank screen again.
My boot loader screen shows this:
PB81100 HX-BC
SPL-2.08.HSPL 8G XE
0x05
cotulla HSPL 0x40
The phone was from UK Virgin mobile, but came unbranded and I'm not sure what the stock rom was. I tried flashing it with SPL 2.08, but that wouldn't get me rid off the HSPL.
Any help will be greatly appreciated!
Thanks!
Get hspl2, and choose 1.66.0000
Retry the wwe 1.66 rom again.
Post results.
Spl 2.x is tmous spl, and doesn't like to let itself downgrade, which is what the 1.66 rom is trying to do.
thanks for the reply!
Just tried and it went without any error logs (only took couple of seconds) and claimed it was successfully installed, but when restarted, the boot loader screen still says SPL-2.08 HSPL.
any other ideas?
stuck radio then, most likely, which often prevemts spl from changing too.
no definitive answer as to what exactly causes it, , corrupted nand most likely.
when you say it sticks part way thru the flashing, , does it stick around 8-10%? if so then its definitely a stuck radio problem. do you get 'radio_rsa fail' or something similar?
sadly there isn't any way i know of to fix it. all i can suggest is you try various troms from sd. i read one thread (out of hundreds with teh same issue) where the OP finally found one stock rom that took.
dont forget that it needs to be teh correct stock rom, not just any stock rom. so an O2 uk hd2 must use o2 uk stock roms. 1.42, 1.72 or 3.14.
locate your correct stock roms and try them all.
Yea exactly thats what I get when flashing from SD card, stuck soon at around 10% and brings up the radio fail log.
When I do that and try to flash them all from SD card, shall I install radio first or it doesn't matter when flashing ROM from SD card?
Any idea how to find out what's the stock rom for my hd2? I tried HTC site but you can't download anything from there for HD2 since they updated their site.
Also, shall the SD card be formated with ext3 system partition on it (the android setup) or just use an empty FAT32 formatted card?
Vipo said:
Yea exactly thats what I get when flashing from SD card, stuck soon at around 10% and brings up the radio fail log.
When I do that and try to flash them all from SD card, shall I install radio first or it doesn't matter when flashing ROM from SD card?
Click to expand...
Click to collapse
doesnt matter when flashing stock roms, they all imclude a radio. It cant hurt to try flashing teh radio separately, but i suspect teh same outcome.
Any idea how to find out what's the stock rom for my hd2? I tried HTC site but you can't download anything from there for HD2 since they updated their site.
Click to expand...
Click to collapse
pretty sure virgin phones came rom unlocked, so look at teh filenames of teh roms, , you want 'HTC-WWE' where HTC means unbranded, and wwe means world wide english.
example
o2 branded rom filename .. RUU_Leo_S_O2_UK_3.14.206.1_Radio_15.42.50.11U_2.15.50.14_LEO_S_Ship
unbranded rom filename ... RUU_Leo_S_HTC_WWE_3.14.405.2_Radio_15.42.50.11U_2.15.50.14_LEO_S_Ship
ALso, see the green numbers? thats the same for all same roms, so all o2 roms are 206 and all unbranded wwe are 405
Also, shall the SD card be formated with ext3 system partition on it (the android setup) or just use an empty FAT32 formatted card?
Click to expand...
Click to collapse
shouldnt matter, but again it cant hurt to fully format the phone to fat32, full format, not quick format.
Thanks for your help man! Will try and post results later.
Vipo said:
When I tried to flash my phone directly from SD card with renamed .nbh file, it would always get stuck at some point of installation and would leave me with phone that wouldn't boot, neither Android nor Windows.
Click to expand...
Click to collapse
Thats because you are not booting into the right bootloader. See pt 4 below.
No need for all the hassle, there is a really easy way to do this. This will revert your phone ENTIRELY. Remember to have at least 50% battery before doing this:
1.Download official ROM and extract with winRAR or WinZip.
2.Rename the *.nbh file to LEOIMG.nbh
3.Format a SD card with FAT32 and put the LEOIMG.nbh file in the root directory
4.Insert the card to the phone and enter bootloader (While phone is Off:Hold Volume down & press power button)
5. The bootloader will recognize the .nbh file and ask if you want to flash it. Follow instructions
6.Wait a few minutes and you are back to WM6.5
Tried, doesnt work. Explained in the first post.
why are you sending it for repair in the first place?
I dropped it once and since then has the screen got some weird yellowish/greenish colours. seems like some contacts got fu**ed up, but there isnt any mechanical damage visible, so they should repair under the warranty.
But only if in bootloader the spl says 1.42.0000 1.66.0000 or 3.03.0000
Anything else will be rejected.
What you mean by 'not the right boot loader'. I did get it to start installation and recognise the file, but after a while it would come up with a error log saying something like radio failed or something like that...
Yea I know, thats why Im trying to put it back to stock.
what size sd card are you flashing the .nbh file from? you will need to use a 4gb or smaller sd card.
what he meant by the right bootloader i think was to be flashing the .nbh from the tri-color bootloader, not from MAGLDR or CWM Recovery.
If you are using a 4gb or smaller card and it's still failing at the radio, then you might as well try flashing a few different radio's by themselves and maybe you'll get one of them to take, then possibly be able to get out of HSPL
well yea, thats what will be trying to do next.
it wont let me to MAGLDR or CWM, seems like these files got corrupted too so yea, im using the tri-color bootloader.
and its 2GB sd card im using
so i guess the only way now is to try flash different roms...
dude 2-3 days back even i was facing the same problem, and here i am writing , how i get through this. i guess you already tried this, but still i am writing so that you get some help...
1)i use hspl2 and select 1.42.0000 to remove my hspl 2.08.
2)extract stock rom using "7-zip" and in the extracted folder find "RUU_signed.nbh" rename it to "LEOIMG.nbh". copy that file to your formated fat32 micro sd card.
3) reset the your hd2 while holding vol down and end call button.
4) first a tri-color screen will appear, keep pressing both the buttons, then a gray screen will come with written "loading".
5) after that 1 more gray screen will appear, loose the vol down button now, rest everything will go smooth, u dont have to do anything.
meet.rajiv15 said:
dude 2-3 days back even i was facing the same problem, and here i am writing , how i get through this. i guess you already tried this, but still i am writing so that you get some help...
1)i use hspl2 and select 1.42.0000 to remove my hspl 2.08.
2)extract stock rom using "7-zip" and in the extracted folder find "RUU_signed.nbh" rename it to "LEOIMG.nbh". copy that file to your formated fat32 micro sd card.
3) reset the your hd2 while holding vol down and end call button.
4) first a tri-color screen will appear, keep pressing both the buttons, then a gray screen will come with written "loading".
5) after that 1 more gray screen will appear, loose the vol down button now, rest everything will go smooth, u dont have to do anything.
Click to expand...
Click to collapse
but if you return to hspl 1.42.000 the you cant flash your rom ..you need hspl 2.08 only to flash
Thanks zaaaan but I got bit luckier and virgin replaced the phone for no extra charge. I was 2 weeks before the end of the contract and I gave it a shot, sent it to virgin. They got back to me saying that they cant repair it and will therefore send me a replacement phone. I got new desire, bit smaller, but android on it runs really nicely and most of all its built for it, so no more flashing and killed hours of running in circles.
then I got 20£ discount just to stay with them on no contract. they got me
should probably add that the phone still had hspl on it
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
Hi,
It's been fun installing all the various Android ROMS these past 2 years. Unfortunately the time is up for this phone and I will be moving to another one. I want to restore it back to a Windows 6.5 phone.
I tried to follow all the steps outlined by jayceooi but can't get past step 9. I have the tri-color boot screen but I don't see any where that says loading. Regardless, I tried to time it to the exact split second where it finishes loading the text on top and let go of the volume button. It just shows the word "Serial" in the bottom white box and nothing happens.
I notice that in the video, he's not using the T-Mobile HD2 (no colors on the phone buttons and no T-Mobile name on top). Do those instructions still apply?
I downloaded the official T-Mobile software and have renamed that RUU nbh file to leoimg.nbh in the root folder of my SD card. Does it matter if my SD card still has other files in it (from Android) as long as that nbh file is in the root folder?
I couldn't find much doing a search here or on Google, but do I have to uninstall HSPL? I have 2.08 which seems to be the same version shown in that video.
Thanks.
gk17 said:
Hi,
It's been fun installing all the various Android ROMS these past 2 years. Unfortunately the time is up for this phone and I will be moving to another one. I want to restore it back to a Windows 6.5 phone.
I tried to follow all the steps outlined by jayceooi but can't get past step 9. I have the tri-color boot screen but I don't see any where that says loading. Regardless, I tried to time it to the exact split second where it finishes loading the text on top and let go of the volume button. It just shows the word "Serial" in the bottom white box and nothing happens.
I notice that in the video, he's not using the T-Mobile HD2 (no colors on the phone buttons and no T-Mobile name on top). Do those instructions still apply?
I downloaded the official T-Mobile software and have renamed that RUU nbh file to leoimg.nbh in the root folder of my SD card. Does it matter if my SD card still has other files in it (from Android) as long as that nbh file is in the root folder?
I couldn't find much doing a search here or on Google, but do I have to uninstall HSPL? I have 2.08 which seems to be the same version shown in that video.
Thanks.
Click to expand...
Click to collapse
I don't think there should be anything wrong with that method for a TMOUS having given it a quick read through. If that method succeeds for you, then the HSPL will already have been reset back to the default one for the WinMo ROM you flashed. If not, then just flash a stock WinMo ROM from the bootloader as you normally would, then flash a stock SPL afterwards. It has the same effect as the one in jayceooi's guide, but it's just a little easier IMO.
dont forget sd card flashing wont work on cards bigger than 4gb
Thanks for the replies. I followed everything but still couldn't figure it out so I did the following instead:
1. Used HSPL3 tool to flash back 2.08.0000 For some reason it won't restart my phone and go into the boot loader, so I manually booted it into the boot loader and the tool kicked in.
2. Next I installed the official software ROM release by T-Mobile. Same problem. Had to boot it to the boot loader manually for this to proceed. My guess is that this is because it's not a Windows OS so active sync is not being used.
3. Crossed my fingers and it looks like everything went well. Back to WinMo 6.5 :good:
Hopefully if anyone runs into a similar situation, the above steps will work out for them also. Was banging my head on this one and with my luck, I couldn't find any 2GB micro SD cards in the house