Database Users

[Q] Battery issues & SPL/ROM Install Questions

Hi everyone,
I recently joined this forum because I got my hands on an HTC HD2 from T-Mobile. Don't know the "official" name to call it since the phone name implies that it's a HTC HD2 LEO and from the looks of it (green call button and red power/end button), it looks like it should be T-Mobile HD2. I'm an advanced computer user in general, but admit that I'm completely new to WinMo devices and have spent hours scouring these threads reading up as much as I can. Now I have a few questions and things that I just want to clear my mind of before I dive in
Please bear with me on this. So many questions to ask and they may sound simple for those that are use to it, but I'm clueless on them.
Model: T-Mobile/HTC HD2
OS Version: 5.2.21892 (21892.5.0.89)
Manila version: 2.5.20121412.2
ROM version: 2.13.531.1 (90963) WWE
ROM Date: 4/28/10
Radio version: 2.10.50.26
Protocol version: 15.39.50.07U
RAM Size: 576MB
Flash Size: 1024MB
R 2.10.50.26
G 15.39.50.07U
D 2.13.90693 8G
SPL-2.10.0000 8G XE
PB81120 SS-B3
I'm using Windows 7 64-bit and have Windows Mobile Device Center 6.1 installed already.
1. One major problem I noticed is that this phone is a power guzzler. I left the phone around 75% of power remaining and by morning, it was dead. I made sure to turn off all the unnecessary data fetching features and it didn't seem to help out much. Anyone else experienced similar problems? I read up on a lot of the battery usage tips here and elsewhere and so far, there is very little improvement.
2. Which brings me to this question. I want to try using other custom ROMS that I have been seeing users talking about here. Maybe it will help out with the power issue and also remove unnecessary garbage that may be slowing down the unit. It looks like in order for me to do any of these things, I must install HardSPL3 first:
http://forum.xda-developers.com/showthread.php?t=653614
I have a question on this part:
IMPORTANT: To install/uninstall this HSPL3 there must be any SPL version from this list on your device:
SPL 1.42.0000, SPL 1.62.0000, SPL 1.66.0000, SPL 2.07.0000, SPL 2.08.0000, SPL 2.10.000
3. If I wanted to go back to stock SPL, how do I do this? For HSPL3_PKG.exe, it looks like it will only go back to SPL 2.08.0000? My version is 2.10.0000 (8G XE, not sure what those characters are for).
4. One part says that flashing with the wrong ROM can "brick" the phone. But if I install HardSPL3 first, how do I unbrick it? Just by doing a hard reset or restoring stock ROM?
5. When we flash a custom ROM, is that ROM going to be the one used after we do a hard reset?
Here's hoping to doing my first HardSPL or ROM flash without screwing it up
Thanks in advance.

Wow, GREAT first post. Although most of these questions have been answered before, I must commend you on your post. Clear english, more information that I can shake a stick at, general politeness...you are a poster child for what we want new users to be.
Anywho, to answer your questions:
1-There are ways to conserve power with the HD2, and customs ROMs do generally have less power consumption than stock ROMs, but ultimately it comes down to that the HD2 has a small battery at just 1230MAh. I would purchase an extended battery, you can get them from eBay for like 15 bucks and they work wonders.
2-Yes, you need to install HardSPL in order to flash a custom ROM, but once you do it you never need to re-do it as it is permanent. And yes, your SPL should work with the HSPL3 package.
3-To go back to stock SPL, you can either use the HSPL package to go back to 2.08.0000 or flash the official 2.13 T-Mobile USA stock ROM via your SD card and it will overwrite HardSPL back to 2.08.0000. Even though your SPL is 2.10.0000, there is no real appreciable end-user difference between the two. The only reason you would need to go back to stock SPL is for warranty purposes.
4-Yes, flashing the wrong custom, stock or radio ROM will brick your device. PLEASE read up on which versions work. If the thread specifically says "for TMOUS" then you are pretty much in the clear. If it says for LEO512 or Euro, DO NOT attempt to flash it, as it WILL perma-brick your device. Radio's are really the most deadly. Flashing a radio ROM with .51 in its name WILL perma-brick your phone. The rule of thumb with WinMo is that if your phone can go into bootloader, by pressing power and holding the down volume button from startup, and get to the tri-color screen then you can flash a new ROM and most of the time recover. Flashing an incorrect ROM or radio will make it so that your phone will not power on, thus rendering it usesless.
and 5-Yes, whatever ROM is on your device is the ROM that will be re-installed when you Hard Reset. To go back to stock, just flash the original 2.13 T-MoUS stock ROM.
I hope that helps, and please don't hesitate to ask anymore questions. READ like crazy before flashing, and if in doubt....DON'T FLASH till you ask. Also, for more info, check out the guide in my signature, should be helpfull.

Thanks for the fast reply ashasaur
One thing on the SPL version. Since I have SPL 2.10.0000 will T-Mobile notice that it's 2.08.0000 and won't take it back? Just asking these precautionary questions. More on the careful side
I definitely have read dozens of these threads and think I pretty much get the gist of it now. Will definitely look out for those things you mentioned and have been reading those sentences in big red fonts LOL
I actually do have a few more questions.
1. I have been installing some of the apps mentioned here to my SD card. If my guess is correct, I have to reinstall these again if a different ROM is used right? There are probably settings stored in the registry on the internal memory.
2. Been having trouble using WiFi with both of my wireless routers at home even though they work for my other computers. For some reason, it connects to them but when I try to browse a webpage with Opera, it gives me an error saying it can't be found (or similar to that wording). Once I turn off WiFi, it works again with 3G.
3. This one will probably have no definitive answer and I've seen debates go on about it. Do you notice any power usage difference between using WiFi or 3G for the internet? Besides speed, if WiFi uses less power, I want to get that working.
Now to get that extended battery. Hopefully it won't stick out too much since I read up on that also somewhere.
Thanks again.

No problem.
1-No, T-Mobile has no idea what SPL you have, only that it falls within a certain range of (something) to (something), that top one being 2.10.0000. They DO know however if your SPL has been tweaked with the HSPL3 package because it displays HSPL after the SPL version.
2-Yes, if you install a new ROM, or hard reset you will have to reinstall all the applications that you have installed right now regardless of where you put them. You can however get a backup program such as Sprite Backup and backup your entire program database, then use that backup on your new ROM to put back all your programs and tweaks and whatnot in one easy process.
3-Some routers are just straight up not compatable with the HD2's WiFi adaptor. Search for how to enable WiFi N on the HD2. Even if your router doesn't support N speeds, it still sometimes solves compatability problems, as do custom ROMs.
4-3G more often then not actually uses more power than WiFi because..well...I don't really know to be honest, only that it does. Mostly from what I gather is that depending on your signal strentgh 3G may use very little, to an amazing amount of power, whereas no matter what the signal strength, WiFi is pretty constant.
They do make extended 1600MAh batteries that have the same form factor as the stock one, and don't require the bigger cover...which is about a half inch tall I'm afraid. I myself use a cheapo 1600MAh battery from eBay and get around 30% more battery life out of it versus the stock one, and can still use the stock cover.

ashasaur said:
No problem.
1-No, T-Mobile has no idea what SPL you have, only that it falls within a certain range of (something) to (something), that top one being 2.10.0000. They DO know however if your SPL has been tweaked with the HSPL3 package because it displays HSPL after the SPL version.
2-Yes, if you install a new ROM, or hard reset you will have to reinstall all the applications that you have installed right now regardless of where you put them. You can however get a backup program such as Sprite Backup and backup your entire program database, then use that backup on your new ROM to put back all your programs and tweaks and whatnot in one easy process.
3-Some routers are just straight up not compatable with the HD2's WiFi adaptor. Search for how to enable WiFi N on the HD2. Even if your router doesn't support N speeds, it still sometimes solves compatability problems, as do custom ROMs.
4-3G more often then not actually uses more power than WiFi because..well...I don't really know to be honest, only that it does. Mostly from what I gather is that depending on your signal strentgh 3G may use very little, to an amazing amount of power, whereas no matter what the signal strength, WiFi is pretty constant.
They do make extended 1600MAh batteries that have the same form factor as the stock one, and don't require the bigger cover...which is about a half inch tall I'm afraid. I myself use a cheapo 1600MAh battery from eBay and get around 30% more battery life out of it versus the stock one, and can still use the stock cover.
Click to expand...
Click to collapse
Okay.... You are so posting the particulars of that 1600MAh battery! Right?! Aren't we ALL looking for a larger battery that doesn't change the form factor of the HD2! PLEASE!!!!!

ElaineD said:
Okay.... You are so posting the particulars of that 1600MAh battery! Right?! Aren't we ALL looking for a larger battery that doesn't change the form factor of the HD2! PLEASE!!!!!
Click to expand...
Click to collapse
x2! (and here are the obligatory extra characters)

I finally did it. I stayed up until like 1AM yesterday re-reading everything in the threads here before I dove in and installed HardSPL3, Core Cell Custom ROM and to make the final finish, flashed the radio ROM to 2.12.50.02_2. Everything seems to be ok except for a few freeze ups here and there with the Core Cell ROM.
Already enabled the wireless N on the HD2 and also have an N router. Will give it another try since the attempt failed last night.
Thanks for mentioning those two programs. Just what I wanted. They will definitely save me time.
The only 1600mah batteries I found on eBay are all from China. It's going to be a long wait and if I decide to buy it, I hope it's not a cheap model. Need a good long lasting battery

Heh, awesome! You will enjoy custom ROMs. Every device I have ever had has had a custom ROM, and the HD2 is no different. They just make the phones sooooo much better.
Anyways, due to popular demand, here is a picture of my battery, and yes, it's a cheapo from China...cost me I think 8USD on eBay, and took around a week to get here by standard overseas shipping.
It's a NETCOM WCL-01A. SUPPOSEDLY works with all the HD2 variants. 3.7V, 1600MAh, and as you can see...is standard size and works with the stock battery cover. Pictures suck I know, taken with my webcam...

Thanks for the pics. Quality is more than enough to make out what it looks like. I think I saw an identical one going on eBay. Will snatch one up now since the shipping time will be the huge killer here. How long did you have it for? Last thing I want is a cheap battery leaking inside LOL

I still use it everyday...and i've had it since around June-ish I think. Still works just as well as the day I bought it.

ashasaur said:
No problem.
1-No, T-Mobile has no idea what SPL you have, only that it falls within a certain range of (something) to (something), that top one being 2.10.0000. They DO know however if your SPL has been tweaked with the HSPL3 package because it displays HSPL after the SPL version.
2-Yes, if you install a new ROM, or hard reset you will have to reinstall all the applications that you have installed right now regardless of where you put them. You can however get a backup program such as Sprite Backup and backup your entire program database, then use that backup on your new ROM to put back all your programs and tweaks and whatnot in one easy process.
3-Some routers are just straight up not compatable with the HD2's WiFi adaptor. Search for how to enable WiFi N on the HD2. Even if your router doesn't support N speeds, it still sometimes solves compatability problems, as do custom ROMs.
4-3G more often then not actually uses more power than WiFi because..well...I don't really know to be honest, only that it does. Mostly from what I gather is that depending on your signal strentgh 3G may use very little, to an amazing amount of power, whereas no matter what the signal strength, WiFi is pretty constant.
They do make extended 1600MAh batteries that have the same form factor as the stock one, and don't require the bigger cover...which is about a half inch tall I'm afraid. I myself use a cheapo 1600MAh battery from eBay and get around 30% more battery life out of it versus the stock one, and can still use the stock cover.
Click to expand...
Click to collapse
Snagged one from obostore.com $8.99 + free shipping andida brand...
"1600mah Andida Battery for HTC Touch HD2 Leo Tmobile HD2"
Hope it works!

MAGLDR NOT causes Touch Screen issues Confirmed

Update: According to info from Cotulla, MAGLDR does not initialize the touch screen since it doesn't have touch input. WinMo or Android (linux kernel) initializes the touch screen. The failures I'm seeing in Android NAND builds must be due to bug in those builds. I've just downloaded 14 different NAND builds (clockwork and not) to test out again. I'll report results later.
See Cotulla's post on the matter here. Thanks for all the help on the matter to everyone.
Update 2: Here is the link to my post testing a handful of builds and what I found.
Note: Please take the insults elsewhere. I'm trying to actually get some help and offer it. I never said MAGLDR caused any damage to my device. It's a simple bug which once pointed out can be researched and fixed.
The work the DarkForcesTeam has done is amazing! We're talking thousands of hours of work collectively. Some commercially available products don't receive such dedication. I just want to try to help out as best as possible to make it an even better product.
When I use MAGLDR, my touch screen becomes over-sensative. It'll randomly select parts of the screen as having been touched when they're not, like a "ghost hand" was using the device..
It is not a bad digitizer. It is not a hardware defect. It is a problem with MAGLDR. I've confirmed this existing with versions 1.11 to 1.13. The problem only exists when using MAGLDR. If WinMo is used, problem goes away.
Here's what I did:
1) Task 29
2) WinMo 6.5
3) Ran an Android ROM from SD (Copes AOSP SD HD2 GB232/CM7 A2SD at
http://forum.xda-developers.com/showthread.php?t=898831
Everything is fine. Screen is incredibly precise.
4) Task 29
5) MAGLDR 1.13
6) Change SD build to boot from MAGLDR instead of HARET
7) Boot up, everything comes up fine.
8) Screen goes crazy.
Since I didn't change the build I was booting, and only changed MAGLDR, there should have not been any touch screen issues.
9) Task 29
10) WinMo 6.5 reinstalled
11) Change SD build back to boot from HARET
12) Boot the Android SD build
13) Screen is very precise once again.
Does anyone know if the DarkForcesTeam (DFT) has commented on this issue before? Are they working on it? Are they even aware of it?
Has anyone else had any issue like this?
I'm using one of the first HD2s to come out for T-Mobile in the US.

FreakyFerret said:
When I use MAGLDR, my touch screen becomes over-sensative. It'll randomly select parts of the screen as having been touched when they're not, like a "ghost hand" was using the device..
It is not a bad digitizer. It is not a hardware defect. It is a problem with MAGLDR. I've confirmed this existing with versions 1.11 to 1.13. The problem only exists when using MAGLDR. If WinMo is used, problem goes away.
Here's what I did:
1) Task 29
2) WinMo 6.5
3) Ran an Android ROM from SD (Copes AOSP SD HD2 GB232/CM7 A2SD at
http://forum.xda-developers.com/showthread.php?t=898831
Everything is fine. Screen is incredibly precise.
4) Task 29
5) MAGLDR 1.13
6) Change SD build to boot from MAGLDR instead of HARET
7) Boot up, everything comes up fine.
8) Screen goes crazy.
Since I didn't change the build I was booting, and only changed MAGLDR, there should have not been any touch screen issues.
9) Task 29
10) WinMo 6.5 reinstalled
11) Change SD build back to boot from HARET
12) Boot the Android SD build
13) Screen is very precise once again.
Does anyone know if the DarkForcesTeam (DFT) has commented on this issue before? Are they working on it? Are they even aware of it?
Has anyone else had any issue like this?
I'm using one of the first HD2s to come out for T-Mobile in the US.
Click to expand...
Click to collapse
I do not know whether this will work or not. But try a NAND build with SENSE in it. Sense has a function of "Calibrate your Screen". Try and recalibrate your screen.
I know for sure the build "imilka's Vision Sense v3.0 (HD2Z)" has this feature. The link for this build is http://forum.xda-developers.com/showthread.php?t=898708
I hope that resolves your issue.

My touch screen stopped working during windows phone 7 and i cant figure out a reason why. Im running magldr 1.12

It might be a mgldr booting SD build issue, I've been using cyanogenmod 7 android 2.3 nand for a month without a single issue..
Sent from my HTC HD2 using XDA App

roloracer said:
It might be a mgldr booting SD build issue, I've been using cyanogenmod 7 android 2.3 nand for a month without a single issue..
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
Same here
Sent from my HTC HD2 using XDA App

When I use a pure NAND build, the problem is there too.
Anytime I use MAGLDR, it happens.
I don't like Sense, but I'll give the one you recommended a try later tonight.

havent had the issue either.. BUT!!! cause its winter here whenever i come from outside and i use my phone i get random presses on the screen cause its wet, when i wipe it off it just behaves..

Alright... my phone just died
Had the setup that you can see on my signature, and touchscreen just stopped responding randomly. First it was once or twice a day, now its like every other time that the screen is sleeping and I try to wake it up.
I did Task29, flashed official WinMo radio, and now the problem still exists. Every other time that the phone goes to sleep - i press any button, the screen lights up, but like the touchscreen function just wont work.
I know for sure that I am not the first, second or even tenth person that has this problem after running NAND-android. Maybe this should be put on the android development thread, so people wont break their phones.
I have no idea why is this happening, but I know that its time for a new phone. Hopefully T-Mobile will give me a new phone, which I can sell and get a native android phone. I hate windows, the reason that I got this phone was the screen size, which no other android phone had on t-mobile back when I got it.
So, one more time
PEOPLE, MAGLDR WILL CORRUPT YOUR TOUCHSCREEN IF YOU USE IT
With that said - I would like to thank everyone that made android on HD2 possible, and specially cotulla, his team, mdj and hastarin, I had a blast using it You guys ROCK!!
Edit: After flashing winmo - I kept getting problems for the first 1hr.
Now it seems that freezing is gone on Win Mo.
Will update later.

t0ny0 said:
Alright... my phone just died
Had the setup that you can see on my signature, and touchscreen just stopped responding randomly. First it was once or twice a day, now its like every other time that the screen is sleeping and I try to wake it up.
I did Task29, flashed official WinMo radio, and now the problem still exists. Every other time that the phone goes to sleep - i press any button, the screen lights up, but like the touchscreen function just wont work.
I know for sure that I am not the first, second or even tenth person that has this problem after running NAND-android. Maybe this should be put on the android development thread, so people wont break their phones.
I have no idea why is this happening, but I know that its time for a new phone. Hopefully T-Mobile will give me a new phone, which I can sell and get a native android phone. I hate windows, the reason that I got this phone was the screen size, which no other android phone had on t-mobile back when I got it.
So, one more time
PEOPLE, MAGLDR WILL CORRUPT YOUR TOUCHSCREEN IF YOU USE IT
With that said - I would like to thank everyone that made android on HD2 possible, and specially cotulla, his team, mdj and hastarin, I had a blast using it You guys ROCK!!
Click to expand...
Click to collapse
I had my touchscreen do that and just stop working BEFORE magldr even came out. A person I know who never hacked or did anything to his phone had this problem. It's a hardware defect and it's just coincidence that it broke while you had magldr on your phone.

not again...
if MAGLDR makes those weird things to your phone then DON'T USE IT!!!
I have been using MAGLDR since it came out. EVen flashing a lot of builds everyday to test but never had any issues with the touchscreen.

jose makalolot said:
not again...
if MAGLDR makes those weird things to your phone then DON'T USE IT!!!
I have been using MAGLDR since it came out. EVen flashing a lot of builds everyday to test but never had any issues with the touchscreen.
Click to expand...
Click to collapse
Same, I've flashed well over 25 times and my Touchscreen hasn't had any problems.
MAGLDR is safe, end of story.

Confirmed? Really? Because you think it happened to you?
This is anecdotal, and it is definitely not concrete in any way. This is pure FUD, nothing more. You should consider thinking before you post ridiculous claims that something has been "confirmed."
This has happened to ONE person on ONE phone, and pretty much everybody else is telling you that you are wrong. Does that sound confirmed to you?
It annoys me that you would smear somebody else's fantastic work because your phone had a freak accident. Go blame the government or something, just stop blaming magldr. Thanks.

Buy a WinMO 6.5 phone stick to WinMO6.5 if you want it to work as intended by manufacturer.
If you want to tinker, then be prepared to tinker it to its death.
If you can't afford a new phone, don't mess with it.
If you can't be without a phone for even 1 day, don't mess with it.
If you want to blame, then blame yourself. You are just messed up.

Danation and hd2k10, I'm not smearing anyone. My phone is fine. There is a bug in MAGLDR. One I'm sure the DarkForces Team can fix if someone can provide some good feedback. Read what I posted again. I'm asking to help DFT solve this software bug. Not saying it's bad.
And I did confirm the problem only exists when using MAGLDR. It runs fine on most of the phones, but there are others aside from myself who have had problems with it. We would love to see MAGLDR working perfectly and I personally encourage anyone who it works for to continue using it. I wish I could use it and want to do everything I can to make that a reality.
psykick5, did you try flashing a WinMo ROM or Android SD build to see if your screen returns to normal?

Danation said:
Confirmed? Really? Because you think it happened to you?
This is anecdotal, and it is definitely not concrete in any way. This is pure FUD, nothing more. You should consider thinking before you post ridiculous claims that something has been "confirmed."
This has happened to ONE person on ONE phone, and pretty much everybody else is telling you that you are wrong. Does that sound confirmed to you?
It annoys me that you would smear somebody else's fantastic work because your phone had a freak accident. Go blame the government or something, just stop blaming magldr. Thanks.
Click to expand...
Click to collapse
Maybe you should read around and see that its not ONE person on ONE phone?
Also, I have flashed many many times, on HD2 and other devices, the fact of the matter is that it happened. Its not just the OP, its not just me, there are plenty of posts in here, saying that exactly the same thing happened to them /just search and you will see/.
Also, I would hate if someone is talking bad about someone elses fantastic work, and this is why I thanked everyone that helped getting android on our HD2s. There is no disrespect, I was just trying to warn other people that this has happened, and not once or twice. The fact that it didnt happen to you - means nothing It wasn't happening to me either, and I even wrote an angry comment to one of the people that was complaining a while back, and ha, guess what happened today
I agree, that probably "confirmed" is not the write word in here, but what we are trying to do, is just warn other users, AND DEVELOPERS so they can look into it, what if the problem is with MAGLDR? Hopefully its not, but thats a big coincidence. What if by some way its overheating a chip or something? You never know, since you are not a developer, I'm don't think that you can be 100% sure about something that is not open source, and you can't see how its made or what it does to the device.
So cool down, and if you can't help - there is absolutely no need to post negative comments.
Thank you,
Tony.
Edit: This is not for you only, its for all the other negative comments that are before yours. And after yours Y'all need to chill out, we are here asking for help. I have donated to a good amount of developers in here, and I am not trying to disrespect any of them, as I said in my previous post. I appreciate their work, but as far as I'm concerned, and the few other guys before me - there is a bug in MAGLDR, and it would be nice if Cotullas team can take a look at it.

Must be a T-Mobile problem. I don't have it. Sorry for you tho, wish I could help.

I have EU HD2 and noticed same problems. Not all time and can say that i think its not MAGLDR problem. More NAND roms side. You ask why.
Tested many roms, not one. No, i dont go say these are bad. just tryed find wich works best for me.
With win 6.5 and win 7 roms i dont seen this problem but with android nand roms yes. Tested custom win 6.5 + android sd too. With that siutation dont had these problems.
Why i try here too is that i think its clued with another problem too, described on this hd2 forum on diffrent places. One is this thread.
Also i have read on some NAND roms thread that rom cooker are increased screen sensitivy or smth. Cant find right now it but if i remember it then i go back and post link.

Not all this sh1t again.
IF there was a "bug" in magldr for TS then it would affect the MAJORITY not the MINORITY.
Also the title of this thread is retarded, you havent "confirmed" a bloody thing other then your ability to presume something and then jump to a wrong conclusion.
EVEN if there is a bug would be a very small one and not one that DFT should waste their time on atm.

your understanding of a bug is that it shows up on the majority of a system? that's utter bull****! sorry.

HectiQ said:
Must be a T-Mobile problem. I don't have it. Sorry for you tho, wish I could help.
Click to expand...
Click to collapse
I have a tmous HD2 and don't experience that crap at all!
Sent from my HD2 Droid HD using XDA App

[Q]WP7 Flash - ROM Question

Well guys once again im posting a questino regarding my HD2. Ive been browsing the forums and youtube in regards to flashing my HD with wm6.5 to WP7.
Yes i know its going to be buggy but tbh 6.5 is horrible :S Now my question is , Which ROM is reccomended? Im leaning towards http://forum.xda-developers.com/showthread.php?t=944995&page=51 as this rom shows GREAT promise. And looks about right. Few questions that ARENT highlighted in the post.
GPRS / HSDPA working?
WIFI Working?
What shall i be prepared to find WONT be working. Also my HD only has a 176MB Internal memory. Obviously 512MB Flash
Will i have to downgrade anything as these are my software stats atm.
OS Version
5.2.21913 ( 21913.5.0.94)
Manilla Version
2.5.20181527.0
ROM Version
3.14.405.2 (04666) WWE
Radio Version
2.15.50.14
PB8100 SS-BC
SPL-2.08.HSPL 8G XE
CotullaHSPL
My phone is an insurance replacement that isnt bound to Tmobile UK anymore. So im not worried about voiding my warranty. Im worried about bricking as my Insurance wont cover that
In summary : Which ROM , Any Thing need Upgrading / Downgrading , 2gb SD Card That Ok size wise? Any thing i should be prepared to NOT have working. **** When i need to activate my LIVE Services what if he asks for my IMEI Number? Shall i hangup and redial or give him my HD2's IMEI?
Thanks for the replies and if i have broken any rules please point them out to me. But I want to be PERFECTLY certain that my choice for WP7 is the right one. As im not eligble for an upgrade for another 12 months * 24 Month Contracts FAIL *

Now that´s funny that you get a phone with HSPL - this actually voids your warranty if you send your device to a service center. In other words: Even if you would do nothing right now, you would risk to not get any warranty since HSPL is already on your device.
Or, did you flash HSPL yourself already? Anyway, doesn´t matter here.
As long as the data you listed are 100% accurate, you´re absolutely fine and ready to flash either WP7 or an Android NAND build - because you do have HSPL 2.08 plus the correct Radio ROM already.
Now, you´d have to install MAGLDR 1.13 (tutorial here), and then the WP7 ROM of your choice (I would take one which comes with all Chevron stuff built-in, means those ROMs are jailbroken already). The one you mention runs perfectly here, no problems at all.
Remember, if you want to use Live services, you´ll still need an activation code from Microsoft.

Most everything works in wp7... multitouch is kinda buggy and you only get 2 point multitouch while native wp7 phones have 4 point touch. Other than that, it will work about the same as a native wp7 phone. All the hardware works.. wifi, bluetooth, gps, phone and data. 2gb memory card is fine if that's all the memory you want. But just a warning, wp7 can be very picky about what kind of memory card it'll accept... since it actually uses the sd card as non-removable main memory, it needs cards that has a good random access speed. Give your card a try... if it works and doesn't make wp7 lag or randomly restart, then you're fine. But if it doesn't work, you're going to want to get a new card... sandisk class 2 or 4 seem to most consistently work ok.

tictac0566 said:
Now that´s funny that you get a phone with HSPL - this actually voids your warranty if you send your device to a service center. In other words: Even if you would do nothing right now, you would risk to not get any warranty since HSPL is already on your device.
Or, did you flash HSPL yourself already? Anyway, doesn´t matter here.
As long as the data you listed are 100% accurate, you´re absolutely fine and ready to flash either WP7 or an Android NAND build - because you do have HSPL 2.08 plus the correct Radio ROM already.
Now, you´d have to install MAGLDR 1.13 (tutorial here), and then the WP7 ROM of your choice (I would take one which comes with all Chevron stuff built-in, means those ROMs are jailbroken already). The one you mention runs perfectly here, no problems at all.
Remember, if you want to use Live services, you´ll still need an activation code from Microsoft.
Click to expand...
Click to collapse
Thanks tictac - after alot of INTENSE reading done today while the missus took care of the little one i have deemed a few answers to ALOT of my above questions.
Now you say i alreadyhave HSPL installed. Now NO i didnt install this. As i mentioned in my previous post this is an Insurance replacement. Now after digging around on site ive found another user who also had HSPL already installed on a replacement lol. Supposedly the reason is Suppliers sell 'refurbs' and 'send backs' to insurance companies and they dish these out. I must of got one that somebody had started to hack , and deemed it not worthy. Ive gone with the Xbmod version atm. Only due to the MASS amounts of response. and MYGOD thanks for posting the tutorial on Magldr installing. Ive been having ALOT of trouble getting it going.

Well , Everything is installed with NO hickups. Also have rather more internal Memory spare compared to when i was using Winmo6.5! Now i have a few questions once again.
I obviously want to Use LIVE services. But ive rang support around 4 times and each time they have asked me for an IMEI number. Now this i cant give obviously. I dont suppose there is a workaround for UK customers? And as its an 0844 number it isnt cheap :S
Also - Seen as chevron is already installed do i just follow the usual steps to get live going once i do manage to get an Activation code.
Ok - 1 Other Problem NO WIFI!? Is this the same in all releases?

Hazeno said:
Well , Everything is installed with NO hickups. Also have rather more internal Memory spare compared to when i was using Winmo6.5! Now i have a few questions once again.
I obviously want to Use LIVE services. But ive rang support around 4 times and each time they have asked me for an IMEI number. Now this i cant give obviously. I dont suppose there is a workaround for UK customers? And as its an 0844 number it isnt cheap :S
Also - Seen as chevron is already installed do i just follow the usual steps to get live going once i do manage to get an Activation code.
Click to expand...
Click to collapse
I sent you a private message. Yes, once you get activation code, just put it in phone and you should be good to go.

Hazeno said:
Well , Everything is installed with NO hickups. Also have rather more internal Memory spare compared to when i was using Winmo6.5! Now i have a few questions once again.
I obviously want to Use LIVE services. But ive rang support around 4 times and each time they have asked me for an IMEI number. Now this i cant give obviously. I dont suppose there is a workaround for UK customers? And as its an 0844 number it isnt cheap :S
Also - Seen as chevron is already installed do i just follow the usual steps to get live going once i do manage to get an Activation code.
Ok - 1 Other Problem NO WIFI!? Is this the same in all releases?
Click to expand...
Click to collapse
Once you get an activation Key just try to sign to live in the market place.. It will say that you cant sign in then take you to another page to enter the key once its verified your good to go... WiFi Does work its just that the MAC Address is not right and changes on every restart

hakuchi18v said:
Once you get an activation Key just try to sign to live in the market place.. It will say that you cant sign in then take you to another page to enter the key once its verified your good to go... WiFi Does work its just that the MAC Address is not right and changes on every restart
Click to expand...
Click to collapse
Aye , That seems logical. Just so annoying trying to get attached to WiFi atm. Wont even find my router :S And EVERYTHING finds it.
Also i have one more problem. When i turn my phone on i have 150MB of free Phone storage , But after 10 Minutes of Use i am down to 5mb and keep getting 'your running low on storage'. Now i had this same problem with my 6.5 randomly telling me im low on storage when im doing nothing.
Is the phone Bugged? Or is the OS bugged?

Hazeno said:
Aye , That seems logical. Just so annoying trying to get attached to WiFi atm. Wont even find my router :S And EVERYTHING finds it.
Also i have one more problem. When i turn my phone on i have 150MB of free Phone storage , But after 10 Minutes of Use i am down to 5mb and keep getting 'your running low on storage'. Now i had this same problem with my 6.5 randomly telling me im low on storage when im doing nothing.
Is the phone Bugged? Or is the OS bugged?
Click to expand...
Click to collapse
I would suggest first trying a different WP7 ROM... if the same thing happens then its your phone...
if not do a Task29 an put MAGLDR (if removed) and flash WP7 again

[Q] HD2 complete blackout after radio change, HELP!!

I have owned a few Leo's myself, flashed cooked roms, ran SD android on all of them. I flawlessly have run two different phones for months with NO radio issues, no "SOD", zero problems.
However, I am now working with my newest HD2 and had a traumatic failure...
I have a 1024 leo on TmoUS and was running Motoman234 EVO Black&Blue Remix, and for the first time, I installed it to SD without modifying anything else at all. Stock WinMo rom, Stock radio, etc. Up until last night I had zero issues with it.
I decided to change my radio for reception purposes. Installed HSPL3 without any issues, then when I ran CustomRUU to update radio, both screens went to 100 percent, then my Leo went black.
I mean black. Keys wont light up, Charge indicator LED wont light, screen is black, phone is TOTALLY unresponsive. I have tried everything that has been recommended in other "Bricked HD2" forums, but to no avail.
Can anyone help, or am I buying a new phone today???
-Clark

Hello Clark,
I'm sorry to inform you this but,
Tmous Leo + Incompatible Radio = Instant Brick .
So if you could provide on which radio you were and what version you were trying to upgrade to you might have بصيص* of hope.
*بصيص = Shaft, ray.

I did a lootttt of research, and found a radio on the master radio thread labeled "TmoUS 1024 Leo" from a list.... The one I downloaded is 2.05.50.11, however I did not write down my previous radio version.... Careless, I know...

Ok, May be it's something minor.
How good was your battery charged before installation ?
Check the battery pins, one might be bent ?
Try to Remove battery for 30 mins then re-insert and charge from wall ?
Otherwise, God shall be with you

Yessir, did all that last night, and decided to go to sleep with battery out (discharged by pressing keys w/o battery) and this morning no change. I was at about 95% battery when I did this, I really think it was the phone, not the software... Ill buy a new one =)
Sincere thanks, Kawazaki, for the help.
-Clark

Or ,since it's completely dead, you can just send it in for repair and play dumb, It might work .
I'm really sorry for you, and glad that I was -sort of- help .

Yep, dead, sorry to say. The rule is ..50.. radios only for tmous, and like every rule there is an exception. In this case the exception(s) are 2.04.50.x and 2.05.50.x which whilst they are from tmous test /pre production roms, and carry 50 v numbers, they are 51 radios really, from when the tmous roms were being developed on regular hd2's
Unlucky.

Not Your Ordinary FREEZING Issue!

So my HD2 freezes constantly. I don't have the unlock freezing issue nor the black screen freezing issue. My phone will just freeze quite constantly. Doesn't matter if I'm just doing a message, online, or it's just sitting there doing nothing. It will freeze and will have to remove the battery and restart it. I've reinstalled MAGLDR, CWM, and tried several ROMS and it still doesn't make a difference. I remove the battery and have to let it cool for around an hour just to turn it on and be able to use it for a period of time.
Any suggestions out there? Could the battery be bad? The hardware? I constantly use Task Killer and Data Eraser to make sure there aren't unnecessary programs running. I've narrowed my app collection to just the necessary ones that I need. Still doesn't make a difference. Any programs out there that would help with this issue in any way. Would repartitioning my SD card help at all. I have pretty much everything on my SD card as well so the hardware shouldn't be overloaded at all.
Any help would be greatly appreciated.
Thanks!

check here

LOADS of people are having this problem including myself.
As long as Mobile Data and Gps are OFF, I have no freezing issues.
BUT, if I turn on Mobile date or Gps, or both, then GAME OVER.....it freezes within seconds.
It's not your battery, or SD card and don't listen to the muppets who repeat themselves by saying "do a task29" coz it doesn't work.
I've tried 5 different SD card, got 2 hd2's, task29, over 100 roms, different radios etc etc.
Never used to happen on SD builds, only Nand.
if i had the cash, i'd smash my hd2 against the wall and get a Android native phone.
this aint ever gonna be solved.
matt

freeridindirtbiker said:
So my HD2 freezes constantly. I don't have the unlock freezing issue nor the black screen freezing issue. My phone will just freeze quite constantly. Doesn't matter if I'm just doing a message, online, or it's just sitting there doing nothing. It will freeze and will have to remove the battery and restart it. I've reinstalled MAGLDR, CWM, and tried several ROMS and it still doesn't make a difference. I remove the battery and have to let it cool for around an hour just to turn it on and be able to use it for a period of time.
Any suggestions out there? Could the battery be bad? The hardware? I constantly use Task Killer and Data Eraser to make sure there aren't unnecessary programs running. I've narrowed my app collection to just the necessary ones that I need. Still doesn't make a difference. Any programs out there that would help with this issue in any way. Would repartitioning my SD card help at all. I have pretty much everything on my SD card as well so the hardware shouldn't be overloaded at all.
Any help would be greatly appreciated.
Thanks!
Click to expand...
Click to collapse
Hi,
It might be worth trying to flash an original ROM and seeing if the same thing occurs in WinMo.

Have you properly formatted card? (overwrite with size adjustment)
Which rom are you using?
Does it do it on multiple roms?
Have you done a task29?
have you tried a different radio version?

TheATHEiST said:
Have you properly formatted card? (overwrite with size adjustment)
Which rom are you using?
Does it do it on multiple roms?
Have you done a task29?
have you tried a different radio version?
Click to expand...
Click to collapse
I've tried all those things. I'm using the Nexus 2 Gingerbread ROM by tytung. I've tried winmo roms, android, etc. I've done task 29 several times. Different radios as well. It doesn't make a difference at all. I found a thread that might be the culmination of it all. If anyone else is having problems like I am, take a look at this thread. It's definitely the motherboard overheating and freezing/and or shutting itself off.
http://forum.xda-developers.com/showthread.php?t=982454
Luckily, I pay insurance through t-mobile so I will be picking up a new HD2 pretty soon.

I had a similar problem, but mine came about under different circumstances. I smashed my HD2 against a wall for whatever personal reasons that you shouldn't care about, anyway, so I ordered a replacement display. When I installed the display the phone would freeze just as described by OP. I found that disabling GPS and WiFi allowed me to use it for a longer time, but if I ever so much as applied any pressure to the display (rather than just lightly touching it) the screen would freeze and sometimes it would just straight shut off until it didn't turn back on at all (this was barely the first day after installation). I opened the phone and tested, found out that the LCD flex cable had a defect to it where if it was bent (the position it's supposed to be in once the phone is assembled) the display would "short out" and with the cable fully extended no problems would be present, even after applying pressure to the display or any of the other internal components.
I'm sending my LCD back for a replacement and hopefully the new one will work fine. I've read that some LCD's cause the HD2 to freeze and I think I was unlucky enough to receive one such. I need the phone to hold on long enough until I get my contract renewal May 2012. I'm surviving on my Dream right now and I'm going through Angry Birds withdrawal...

Compatible-Bad Hardware-Insurance Questions
freeridindirtbiker said:
I've tried all those things. I'm using the Nexus 2 Gingerbread ROM by tytung. I've tried winmo roms, android, etc. I've done task 29 several times. Different radios as well. It doesn't make a difference at all. I found a thread that might be the culmination of it all. If anyone else is having problems like I am, take a look at this thread. It's definitely the motherboard overheating and freezing/and or shutting itself off.
http://forum.xda-developers.com/showthread.php?t=982454
Luckily, I pay insurance through t-mobile so I will be picking up a new HD2 pretty soon.
Click to expand...
Click to collapse
I have similar issue. Could use advice. Please.
My HD2 is about a year old. Decided to try android on the sd.
Device: HTC HD2 TMOUSA
Radio: 2.10.50.26 (Original) NOW flashed to 2.15.50.14
SPL: 2.10.xxxx (Original) NOW HSLP 2.08.0000
Android Rom: SD AmeriCanAndroid AOSP HD2 GB234 CM71
WM Rom: 2.13.531.1 (Original)
ACA seemed ok but would freeze randomly. So I flashed the radio to the 50.14. Seemed a little better but still a few freezes in android. Thought I would try the partition to improve the sd card performance. can't tell if it helped or not to many freeze ups to use android during the day. NOW my winmo side it giving me random reboots. It gets hot reboots, especially bad if using gps. I know overheating is part of the issue because during the middle of the day in my car without A/C it is terrible.
I also have an OTTERBOX Defend which has kept the phone looking great but is a really pain with on all the battery removal with the freeze ups.
I have read that this can be a mainboard issue, but how can I tell if it is or not?
Could the radio and winmo rom be incompatible?
Should I flash the winmo rom to a more compatible android rom?
Should I send it in since I have TMO insurance? (Anyone know if there is a deductible if you didn't lose the phone?)
I have also noticed the on the winmo side it reboots less if I turn htc sense off.
Not sure if I should go back to a different radio or send it in?
Are the insurance replacements refurbished or new? do they have the same issue?
Thanks for any expertise you care to share.

Had similar problems with Tmous HD2. Problems were really bad in Winmo; aca worked somewhat better. Read forums, tried standard "solutions". With time the problems got to the point where the HD2 would not boot unless it had been placed in the refrigerator for 5 minutes.
Did T-Mobile warranty exchange in April. Replacement was refurb (arrives without battery or sd card, used old one), but looked fine. Had a week to test "new" phone, before sending the old one back. Replacment phone works much better. In Winmo, gps, videos, sense no longer cause reboots; aca also works great.
Hope this helps...

TheATHEiST said:
Have you properly formatted card? (overwrite with size adjustment)
Which rom are you using?
Does it do it on multiple roms?
Have you done a task29?
have you tried a different radio version?
Click to expand...
Click to collapse
Exactly as my post from a few days ago predicted..."task 29"
FFS.