Database Users

Flashing from 2.10.0 to 2.10.1 Help

Hello all
Looking for help for flashing from the stock spl 2.10.0 to 2.10.1 for some reason i cant get it to flash properly not even from SD card. it just stays stuck at loading... screen or it goes to the HTC bootloader screen but gets stuck at 0%. Any tips.
But if im understanding it correctly the 2.10.1 cant go on the stock spl?
Thanks for all help in advanced.
anybody have any idea when a new rom is going to be released from T-Mobile?

when you download a rom, if it comes as a .exe, your phone will see it as official, and it should load on your spl. (Assuming its a match, of course) if it comes as two files, ruu_signed.nbh and customruu.exe, then your phone sees it as a cooked rom, and you need hspl installed to load them. (you can of course then unload hspl again afterwards, by running the hspl prog again, and all should be well.)
(At least that is how it appears to me, there are several 'official' tmous roms ive seen, and some are one type, some are the other. I dont have a tmous, lol, so i cant test it propperly, but its how it seems, the exe roms will load into my kitchen, the customruu ones wont. )
just a late night theory.

well this rom is coming as a customRUU and a ruu signed.nbh.
So assuming the phone recognizes it as that way. does anybody have a 2.10.1 link for an official EXE rom not a cooked rom

try search this one.can't promise anything but it came as an exe.
RUU_Leo_1_5_TMOUS_2.10.531.0_Radio_Signed_15.34.50 .07U_2.08.50.08_2_Ship.exe

I have that version installed im looking for 2.10.1 not the 2.10.0

cbig said:
I have that version installed im looking for 2.10.1 not the 2.10.0
Click to expand...
Click to collapse
WHY?
My God, I don't understand why so many people, like yourself are in "dire" need of such an insignificant "update" if you could even call it that... which you can't... because it DOES NOT add anything completely outrageous or amazing that would make going through all that trouble even worth it.
This is like the 15th thread that has been started stating literally, the exact same things.
Unbelievable.

Well sorry, just im the type of person that likes to be current in software even if it does nothing.

in that case you'll be keen to flash hspl1024 as soon as you can, so that you have the latest spl protection system currently available, with the added benefit that the x.x.1 rom update will install happily. then, if you don't want hspl there permanently, remove it again. just run the hspl prog again and choose 2.08.0000.
job done, 20 minutes

cbig said:
Hello all
Looking for help for flashing from the stock spl 2.10.0 to 2.10.1 for some reason i cant get it to flash properly not even from SD card. it just stays stuck at loading... screen or it goes to the HTC bootloader screen but gets stuck at 0%. Any tips.
But if im understanding it correctly the 2.10.1 cant go on the stock spl?
Thanks for all help in advanced.
anybody have any idea when a new rom is going to be released from T-Mobile?
Click to expand...
Click to collapse
Did you trying downloading the ROM in the development section?
On a side note, I currently have ROM version 2.10.531.1 (82076) WWE installed. That is the same as the 2.10.1 stock ROM right? If I do flash a cooked ROM, I would like to be able to get back to this stock ROM as well.

samsamuel said:
in that case you'll be keen to flash hspl1024 as soon as you can, so that you have the latest spl protection system currently available, with the added benefit that the x.x.1 rom update will install happily. then, if you don't want hspl there permanently, remove it again. just run the hspl prog again and choose 2.08.0000.
job done, 20 minutes
Click to expand...
Click to collapse
Is it possible to change spl without messing up the currently installed ROM? In theory, that sounds like a solution though.

sure.installing and removing hspl has no effect on the current rom. no hard reset or anything.

Android with HSPL

Can I boot/intall Android with HSPL?

im guessing yes cause i had to HSPL my phone to run energy rom, and now im running froyo

What you mean is Android on the NAND? No, not yet.
What you can do, is to flash a custom ROM (without Android).
The Android has to be on the SDCARD!

Sorry my question was can I boot/intall Android without HSPL?

I have seen mixed opinions on installing without HSPL. The problem usually comes in when you go to make calls. People can get Android running on a completely stock HD2, but you usually need a different radio for clear audio in calls, ie no robo-voice. If you don't want to change from the stock Rom, I would still suggest running hspl and flashing a new radio. it will help to keep you from getting too angry.
Good luck.
Send from my HTC HD2 via XDA app

I like the stock ROM for the most part. In the most of custom ROMs, the start menu is the bottom which I dont like. And I have to unlock which will void warranty. I have bricked my HD2 once! So not comfortable installing HSPL and Custom ROM.

mukesh_thiru said:
I like the stock ROM for the most part. In the most of custom ROMs, the start menu is the bottom which I dont like. And I have to unlock which will void warranty. I have bricked my HD2 once! So not comfortable installing HSPL and Custom ROM.
Click to expand...
Click to collapse
Many custom ROMs come in WinMo 6.5 versions (which is what you're looking for; for example the Core Cell Evo, which is a very nice ROM and supposedly compatible to Android [I guess in terms of robot voice, haven't tried it, yet] since V3; or Elegancia ROM Series, which I use myself and can therefore confirm that it solves the robot voice problem) and of course in 6.5.5 versions (which have the start button at the bottom). Therefore, a custom ROM does not necessarily mean a totally new WInMo experience.
Other than that, I see no real problem in installing HSPL on the phone. It rather prevents bricking your phone, so why not do it. And in case you have to make use of the warranty, you can always uninstall HSPL in order to "make it stock" again.

It is recommended by most devs that HSPL 2 (or 3) should be installed beforehand

traithudo said:
It is recommended by most devs that HSPL 2 (or 3) should be installed beforehand
Click to expand...
Click to collapse
iam using stock 1.66 rom with 2.10 radio and no hspl , and i have no issus with nither the radio nor the speed , android ha nothing to do with hspl nor custom roms

hoss_n2 said:
iam using stock 1.66 rom with 2.10 radio and no hspl , and i have no issus with nither the radio nor the speed , android ha nothing to do with hspl nor custom roms
Click to expand...
Click to collapse
Let's put it like this:
If you already have a radio of 2.08 or above and a stock ROM that does not give you the robot voice or you don't care about the robot voice, then you don't need HSPL at all (as long as you're running Android off the SD card, which you might not want anymore as soon as it's flashable to Nand, which it is not yet).
If, on the other hand, you need to flash anything in order to make it work (new Radio, custom ROM), then HSPL is either recommended (in order not to brick your phone) or absolutely necessary (because most custom ROMs won't be flashable without it).
Hope that clears it up a bit more, pls correct me if I was wrong on anything.

I running stock ROM with radio version 2.10.50.26. I tried "HyperDroid"
http://forum.xda-developers.com/showthread.php?t=769026
I have robot voice.

tsrzealot said:
Let's put it like this:
If you already have a radio of 2.08 or above and a stock ROM that does not give you the robot voice or you don't care about the robot voice, then you don't need HSPL at all (as long as you're running Android off the SD card, which you might not want anymore as soon as it's flashable to Nand, which it is not yet).
If, on the other hand, you need to flash anything in order to make it work (new Radio, custom ROM), then HSPL is either recommended (in order not to brick your phone) or absolutely necessary (because most custom ROMs won't be flashable without it).
Hope that clears it up a bit more, pls correct me if I was wrong on anything.
Click to expand...
Click to collapse
I am getting the robot voice, ROM version 2.13.531.1 and radio 2.10.50.26

mukesh_thiru said:
I am getting the robot voice, ROM version 2.13.531.1 and radio 2.10.50.26
Click to expand...
Click to collapse
Yeah, well, then it's (like I wrote) most likely the stock ROM that's causing it. So either you learn t live with it or I strongly advise to install HSPL prior to flashing a custom ROM. And to prevent a question: No, at this point in time, there is no other workaround known to me. Like I said, live with it it or change it.
EDIT: Since you say you're uncomfortable about instaling HSPL and that you have bricked your phone once, I assume that you did not install HSPL when that happened? In the sense of you bricked your phone while trying to install a custom ROM without prior installation of HSPL? If that's the case, get some information on HSPL again, it's your friend, not your enemy It basically keeps you from bricking the phone. Of course, there always remains some risk, so whatever you do, you do it on your own risk. Don't come back here saying "You told me nothing could happen when I hae HSPL." That's not how it works

hoss_n2 said:
iam using stock 1.66 rom with 2.10 radio and no hspl , and i have no issus with nither the radio nor the speed , android ha nothing to do with hspl nor custom roms
Click to expand...
Click to collapse
Don't you read my post? It is recommended, not must be. Haizzz

I installed HSPL. I was using some custom ROM. Then I decided to work on my own ROM.
When installed my ROM I bricked my phone. it had HSPL. I dont know something went wrong
http://forum.xda-developers.com/showthread.php?t=761322

mukesh_thiru said:
I installed HSPL. I was using some custom ROM. Then I decided to work on my own ROM.
When installed my ROM I bricked my phone. it had HSPL. I dont know something went wrong
http://forum.xda-developers.com/showthread.php?t=761322
Click to expand...
Click to collapse
Just like they said in the other post, try entering the bootloader by turning off the phone, holding the "volume down" button, keep holding it, press the power on button while still holding the volume down. While in bootloader, you can flash a working ROM either from USB or from your SD card (see HSPL info for that process)... like I said, HSPL does not prevent anything from going wrong if there's an error in a ROM or whatever, it just leaves "a back door open"...
But that's kinda offtopic anyway In fact, if your aim is to get android running, I suggest one of the ROMs that are reportedly working, like Energy, Chucky, Miri (original or Elegancia), supposedly Core Cell Evo v3 etc... why cook your own when you don't wanna run WM anyway

PLEASE HELP: How to I uninstall HSPL?
tsrzealot said:
Other than that, I see no real problem in installing HSPL on the phone. It rather prevents bricking your phone, so why not do it. And in case you have to make use of the warranty, you can always uninstall HSPL in order to "make it stock" again.
Click to expand...
Click to collapse
As soon as I installed HSPL on my phone, my HD2's screen would not work. How do I uninstall HSPL without having to touch the phone? Is this possible? Also, I have searched and searched for a newbie version of how to uninstall HSPL, and I cannot find anything. PLEASE HELP!

[Q] Android without a new Radio ROM?

Hi,
I wonder if there is a way to use Android on the HD2 without the special ROM version it needs. During a reboot my device shows:
R 2.07.51.22~2
G 15.32.50.07U
D 1.72.86526
A reset with the volume down key being pressed shows "SPL 1.66.0000".
Thank you

Hi,
that´s a fine question. My device shows the same.
Can annybody tell us something about this topic?
Thanks

You can try andriod without any rom changes, just download it, extract to SD card & run (per instructions). It should work, in general, but you'll most likely get the common issues, like "robot voice".
Try some builds & see how they work for you.

Today I tried out "HyperDroidV1.2" but i get one of the known problems!
I don´t want to change the radiorom because of my warranty.
Every thread I looked up say, that you lost the warrenty if you try HSPL and a other RadioRom.
I'm afraid to make my phone unusable.
Thanks for your answer!

Without the right Radio ROM, Android will stop booting at the "init screen" (or "init panel"?) line and the display will fade to black.

daemonfly said:
You can try andriod without any rom changes, just download it, extract to SD card & run (per instructions). It should work, in general, but you'll most likely get the common issues, like "robot voice".
Try some builds & see how they work for you.
Click to expand...
Click to collapse
Be careful!!
I tried the FroyoSense V2 on my stock HD2, and my WM locked up totally. No 3'rd part progs would run, could not install anything. The phone was more or less useless. So backup your phone before even trying to run Android.

well you need at least 2.08 radio. i have exact same stock rom, but you need to hspl and upgrade your radio.

Why are you hesitant to flash a new radio? It is super simple to do and it is reversible. If I were you I'd go to radio 2.12. You can also flash a custom WM Rom with built in android boot manager.

My understanding is that Andriod only works with the R 2.**.50.** radio. I think these are the US radios. Any .51 radio are for EUR/AUS and will not work with Android.
I have a Telstra HD2 with 2.09.51.03 and have to flash 2.10.50.08 inorder to work with Android.
I believe unless you have a TMobile HD2, it is quite safe to use any radio rom and the flashing process is very straight forward indeed.

Going back to windows mobile 6.5 from Android- SIMPLE

Hello,
Heres the story:
I sold today my htc hd2 and someone came by to my house to get it and pay. Now i got a message that he cant get used to android. Now I need info for a simple instalation of windows mobile on the htc hd2. Like Getting a windows mobile RUU.exe and simple install it with 1 setup. The phone has hyperdroid, magdlr 1.13, cwm 1.3
I need your answer fast.
David

You can just download the official rom and flash it over usb, it will overwrite everything, HSPL, radio, splash screen, everything back to stock. Or you could do the same with most other wm6.5 roms, but if you're giving it to someone not comfortable with it and you don't want to be their phone support guy for the next however long, I would give them the phone stock, or link them to the proper official rom.
If you have a US T-Mobile HD2 (1024): http://support.t-mobile.com/doc/tm54430.xml?
If you have an HTC HD2 (512): http://www.htc.com/www/SupportDownloadList.aspx?p_id=297&act=sd&cat=2

The above instructions are correct, but did not mention that if you have flashed HSPL and MAGLDR that you will need to flash the stock ROM from an SD card that is under 2Gig in size. Just copy the original ROM file to the card, enter bootloader mode and go from there.
One thing, though - if the person who bought your phone can't get used to Android, he's in bigger trouble than he thinks. I mean, what the hell did he think he was buying? Is it that he can't get used to a PDA phone, a touch screen or does he prefer communicating by carrier pigeon? Rhetorical questions, I know, but geez... what the F did the guy think he was getting, and why is it now your problem?

I'm no expert, but I thought I remembered hearing something about how you weren't supposed to flash the original rom from sd, because it somehow makes it so you can't reflash hspl later if you change your mind.
Not 100% on that by any means.

I know this may involve an extra step, but to avoid usage of SD flashing, you can flash a custom HD2 WM6.xx ROM. Then flash the stock ROM..

willr001 said:
I'm no expert, but I thought I remembered hearing something about how you weren't supposed to flash the original rom from sd, because it somehow makes it so you can't reflash hspl later if you change your mind.
Not 100% on that by any means.
Click to expand...
Click to collapse
That may have been the case in the early stages of HSPL development. If you flashed the wrong rom and got stuck on an spl that was not supported by the HSPL versions out then that was so. This is no longer the case now with all spl versions being able to be HSPL'd.

I gave him an link to an official RUU wm 6.5 NL rom. It's an exe file. I told him he haves to run this exe file in android and if that doesnt work he haves to go to boot menu (holding volume down) and if that's doesn't work he haves to try out the usb flasher option in magdlr. I also gave him the link to this forum post.

here is a simplier way to explain it. i use it sometimes if i forget how to do it...
http://www.youtube.com/watch?v=Wc89Gh0QpIY&feature=related

Hi, New to HD2 but not to flashing ROMs ( Mogul, polaris, TyTN 2) got a second hand TMobile USA yesterday. Came with a nand Android 2.2 install, Magldr v 1.11 and spl 2.08 hspl. I intend to flash back to the stock rom ( latest version T-Mobile HD2 MR Software (Version 3.14.531.1 ) so I can dual boot with an sd android install. I also intend to check out some of the custom 6.5 builds along the way.
Have installed HTC sync for Android and and all appears to be good. I can also get a usb connection while in bootloader.
I'm assuming its as simple as the 2nd post but I don't want to brick my new phone on my first day . Would somebody please confirm that I'm not making any obvious mistakes? I gather I will then need will need to flash a new HSPL, which version is recommended for my purposes?
I apologize in advance for asking such a simple question but the HD2 forums are new to me and much larger than those for any of my old phones. I have been reading for most of the past week and think I know what I'm doing but I might be completely wrong.
EDIT
Is anybody out there?
I know that posting in "[GUIDE] Flashing Your First HD2 NAND Android Rom [For Newbs]" would be more appropriate but I can't seem to post in it as I just get a bulletin message saying I don't have permission. This is the closest thread I can find for my question.
Many Thanks in anticipation of a reply

Oh well. No replies. looks like I will just have to give it a go. Will play with some other Nand android builds first and upgrade MAGLDR to 1.13. Will also experiment with different radios to see if I can improve battery life as it is shocking (loses nearly 30% in 7 hours while 'asleep").

BTW I think my current radio is 2.08.50.08 (settings/software information/baseband version - second half of string). Happy to stand corrected if this is not where you find the radio version in android - as I said before I'm new to this OS.

In case anyone is wondering. The reason for multiple posts in a dead thread is to reach the number required to post on the more appropriate development thread.
Hope that does not upset anyone. I do promise to come back to this thread and post how I got on. ie successes, failures, tips etc.

[Q] can I flash a non-US ROM to a US HD2?

I have been trying to help a friend install Android on his HD2. We actually had it working but didn't know anything about APN so we couldn't figure out how to get the 3g data working. Ultimately I wound up flashing it back to Windows, and then figured I would try flashing Android again after that. Unfortunately we are now stuck with Windows because it seems that we cannot flash MAGLDR. When we try, the progress bar sits there, stuck at 0%.
I had downloaded the image from T-mobile's website here:
http://www.t-mobile.com/wmupgrade/
But I found this post archived:
http://forum.xda-developers.com/archive/index.php/t-612580-p-78.html
It has some information stating that "If you cannot reflash and you stay at the 0 percent screen, then another solution is to flash first an original stock HTC ROM (1.66). Enter bootloader, connect to PC/Laptop and flash this ROM. When that has been succesfull, you can then reflash Artemis ROM."
Unfortunately the ROMs they are referring to (1.66, 1.72, etc.) appear to be non-US ROMs. I found the 1.72 website for the UK:
http://www.htc.com/uk/SupportViewNews.aspx?dl_id=936&news_id=638
But the site specifically says not to use that ROM to flash a T-Mobile(US) HTC HD2 as doing so can have unintended consequences. Is this true even when using HSPL? As part of the Android process we obviously had to install HSPL 2.08. I thought the point of HSPL was that you could always flash a ROM and even if the ROM didn't work, you will drop into the bootloader where another ROM can be flashed. So basically you can't brick the device any longer since you can always access the bootloader and flash a new ROM.
It seems people had success flashing one of those 1.66/1.72 ROMs and then installing some other ROM. I tried using the US ROM and it flashes just fine (doesn't get stuck at 0 percent) but when I try reflashing MAGLDR it just gets stuck. I don't intend on booting up and using the UK ROM...I'm just curious if I can flash that on this US based phone and then try to flash MAGLDR again to see if it works. Is this a good idea?

Oops...didn't mean to post this in the dev forum! Moderators please feel free to move this to Q&A.

flash any non tmous compatible cooked rom to a tmous and it wont boot past the RGD screen.
flash any STOCK non tmous rom to a tmous and it is bricked, full stop, dead. The radio contained in non tmous roms is permanently fatal to tmous phones.
This is true regardless of HSPL or any thing.
Simply put, you should never flash any rom where the chef doesnt explicitly state tmous compatible.
I havent used artemis, though glancing through the first post i see it is is based on the Leo S 3.14 rom, which is for the regular hd2 (LEO S means regular). What it doesnt make is any mention of tmous compatibility, so unless someone knows for certain i'd stay away from it.
Is this a good idea?
Click to expand...
Click to collapse
not at all.
If your aim is magldr, put phone into bootloader, connect usb, run hspl4, choose 2.08.hspl, your radio is already OK, because if it wasn't your phone would already be bricked (all tmous radios are ok for magldr by default), return to bootlaoder, flash magldr.
EDIT - Oh and once you are on android, you dont need to worry, all roms are tmous compatible.

Great thanks for the info...I definitely don't want to brick his phone with an incompatible radio. As for loading HSPL 2.08 that is precisely what I did. I flashed Windows back on there, then flashed HSPL 2.08, then tried to flash the same radio. It got stuck at 0% so I pulled the battery and tried again but it was a no go. So then I just tried MAGLDR and it also got stuck.
At this point I read the thread about flashing Windows back so I tried that again and am still unable to flash MAGLDR. You think I should flash HSPL again and then it will work? I think I used HSPL 3...so maybe I need to try HSPL 4.
Sent from my Evo via the xda app.

Also I don't plan on using Artemis...I just found that post while trying to fix the 0% issue while flashing. I had installed prj clean desire and he really liked that. He isn't too techie so I don't worry about him wanting to flash new ROMs to try them. As long as it is not Windows mobile he is happy. Unfortunately he is stuck on that for the moment.
Sent from my Evo via the xda app.

hanging at 0%, , two possibles, either you accidentaly chose 2.08.0000 instead of 2.08.hspl when you ran hspl, or your computer is timing out, in which case dont touch the phone, reconnect to a different usb port and run the flash again.
Also, if you flashed that http://www.t-mobile.com/wmupgrade/ 3.14 rom from there, then you already have the latest radio and dont need to change it.

Oh snap you might be right...I might have chosen 2.08.0000 and not the HSPL version. I seriously doubt the computer is timing out because it works fine with that same USB port to flash the Windows ROM. I bet you're right and I just flashed the wrong SPL! I'll get his phone and just bring it home with me soon. He can use his old phone for a day or two while I iron things out.
I'll try to remember to login from my computer and hit the thanks button. I don't see any way to do that in this app...
Sent from my Evo via the xda app.

gamblor01 said:
it works fine with that same USB port to flash the Windows ROM.
Click to expand...
Click to collapse
also worth considering - once magldr is running and you are into the android side of things, go into wmdc without phone connected, choose connections settings (or whatever it says) and UNtick allow usb connections, , you don't want wmdc grabbing the usb connection. (probably also need the "google usb driver" if its your first time with android on that pc,, google them.)
Flashing from bootloader needs that box ticked, hence the slightly confusing instructions in flashing guides to 'get an activesync connection', it doesn't really mean a sync connection, but that those drivers have grabbed the usb.

samsamuel said:
also worth considering - once magldr is running and you are into the android side of things, go into wmdc without phone connected, choose connections settinsg (or whatever it says) and UNtick allow usb connections, , you don't want wmdc grabbing the usb connection. (probly also need the "google usb driver" if its your first time with android on that pc,, google them.)
Click to expand...
Click to collapse
Yeah that causes a different error. Something about USB init failed and it complains about a source file called rspl.cpp or something like that. I had to fix that issue before I could ever install the prj ROM the first time. It's ActiveSync 4.5 though (I'm running XP on this partition -- I don't buy any Microsoft products any longer -- or Apple for that matter), but the steps are essentially the same. You just have to prevent it from establishing USB connections.

@samsamuel
Thank you so much for all of your help! I got his phone back today and it looks like the Windows ROM flashed 2.10.0000 on there. I launched HSPL3 again and this time made sure that I selected 2.08HSPL. It flashed right on, as did MAGLDR 1.13, and ultimately the prj clean Desire ROM. It's back to working again and we'll plug in the APN settings when I give it back to him tonight. Victory!

gamblor01 said:
Victory!
Click to expand...
Click to collapse
heh, a happy ending, nice.