HD2 Too Sensitive to flashing? - HD2 General

I have been flashing ROM's many times on various htc devices even going far back as hermes (TyTn) days, and all those times only once in a blue moon did have to resort to flashing back a stock ROM or do mtty after a bad flash!
Judging by the number of related post in the ROM Development thread and my own experiences with HD2 what surprises me is how sensitive it is to being flashed many times! where one has to either resort to flashing back stock ROM or perform task 29 through mtty in order to avoid a bad flash or any other issues!!
It's actually got to the point I now know when I've had a bad flash and that I need to either perform task 29 or re-flash stock! I came across this discovery by accident the other day, usually after flash I always perform a hard reset that's when I noticed that the progress bar for hard reset sometimes goes up to quarter or halfway and then it prompts you to re-boot normally the progress bar should go all the way!

I don't know. I don't have any experience with WM phones apart from the HD2, but I just make it a habit to run MTTY between every flash for good measure, since it literally only takes a few extra seconds to do. It's silly not to do it, IMO, if stability is something you are after, which I am.

I've never had a bad flash in my life (HD2 and Diamond) other than of my own wrongdoings...and I've literally flash more times than I care to remember.

donalgodon said:
I don't know. I don't have any experience with WM phones apart from the HD2, but I just make it a habit to run MTTY between every flash for good measure, since it literally only takes a few extra seconds to do. It's silly not to do it, IMO, if stability is something you are after, which I am.
Click to expand...
Click to collapse
Yes it's easy to perform MTTY no big deal! but my point is in the past I would flash probably almost every other day trying every cooked ROM under the sun and seldom have I had any stability issues!!
The point I'm trying to make is could it be the newer EPROM's HD2 are not as resilient as the older ones in previous htc devices?

Related

Clockwork like problems with Services.exe

Recently my HD has developed an annoying little fault. I'v done a search and a few people had this fault but there were no real replys.
After i power on my HD or do a soft reset, within 15 minutes without fail, services.exe will crash. No matter what i do with the phone, even if i switch it on and let it idle.
I'v removed just about every program on the phone and been through HD tweak and no joy...
The crash doesn't seem to affect how the phone runs, i just wanted to see if there was a known solution i'd missed or at least know if i should be worrying about this process crash if it performs a useful function to the phone.
Many thanks guys!
Have you tried hardresetting your phone? To me it seems that you have installed something that runs as a service and that software crashes. Also you may try to remember when the crashes began and uninstall anything that could be responsible for them.
tkolev said:
Have you tried hardresetting your phone? To me it seems that you have installed something that runs as a service and that software crashes. Also you may try to remember when the crashes began and uninstall anything that could be responsible for them.
Click to expand...
Click to collapse
I wanted to try to avoid hard resetting. I have un-installed just about every program on there, certainly anything that could cause this that i can think of.
Ok i just did a hard reset, within 5 minutes of the phone being on services.exe crashed again. This is without the storage card in as well...
I have the same problem on my Orange HTC Touch HD from day one (11/05/09) and so fair been unable to find any info on it in connection to Windows Mobile platform. I am already on my second phone, sim card and I only had the contract two weeks. The phone will not run Orange maps as it refuses to complete install on the 1st start. Wish i never got it now to be honest, but what phone to have instead as I hate the iPhone
[email protected] said:
I have the same problem on my Orange HTC Touch HD from day one (11/05/09) and so fair been unable to find any info on it in conuction to Windows Mobile platform. I am already on my second phone, sim card and I only had the contract two weeks. The phone will not run Orange maps as it refuses to complete install on the 1st start. Wish i never got it now to be honest, but what phone to have instead as I hate the iPhone
Click to expand...
Click to collapse
From browsing on here there are a few people with this issue with services.exe so we are not alone.
I've just done about 4 hard resets trying differeny suggestions from previous threads and nothing worked. Really annoying as surely since im using stock ROM and even after a hard reset it's doing it, it has to mean there is a glitch with the core software.
As for orange maps... my HD from Orange didn't come with any mapping software i i just downloaded a googlemaps cab.
Are U on an orange ROM??
If so try setting date and time to a month earlier after hard reset at setup - just for testing for a day.. Mostly they (orange) have used some trialware software/extension which is expiring of it's free trial and sending the device to Reset. I know some one who flashed a custom ROM later due to this..
Freypal said:
Ok i just did a hard reset, within 5 minutes of the phone being on services.exe crashed again. This is without the storage card in as well...
Click to expand...
Click to collapse
crajee said:
Are U on an orange ROM??
If so try setting date and time to a month earlier after hard reset at setup - just for testing for a day.. Mostly they (orange) have used some software/extension which is expiring and sending the device to Reset. I know some one who flashed a custom ROM later due to this..
Click to expand...
Click to collapse
Mmm interesting, I am on a stock 1.19.61.1 WWE (11/25/08) Orange ROM yes. If this is true then i guess it gives me a good excuse to flash a cooked ROM. Been toying with the idea...
I take it after your mate flashed a new ROM the problem disappeared?
Yes, but he was not tied to Orange network..
Some ppl have reported connectivity probs with orange with custom ROM and some have not. Your mileage might vary.
If doesn't work you can always go back to Stock Orange ROM.
BTW I heard this is one of the s'kiest ROM
If you want Orange Maps you can have it free for normal version, just make sure you have a data package and just text:
Orange Maps to 247
I am also with Orange device but it is unlocked. However I flashed the ROM on the first day because it is my second HD after an unfortunate incident involving a set of keys thrown at me in the dark an my first HD in my hand... my point is - you should definitely try a new ROM, however I suggest using USPL and flashing an older cooked ROM (not 1.56 based), so you don't have to update the SPL and make reverting back to stock much easier, should you decide to make use of the warranty, because many people here are complaining about HTC returning their devices because of 'illegal firmware'.
tkolev said:
I am also with Orange device but it is unlocked. However I flashed the ROM on the first day because it is my second HD after an unfortunate incident involving a set of keys thrown at me in the dark an my first HD in my hand... my point is - you should definitely try a new ROM, however I suggest using USPL and flashing an older cooked ROM (not 1.56 based), so you don't have to update the SPL and make reverting back to stock much easier, should you decide to make use of the warranty, because many people here are complaining about HTC returning their devices because of 'illegal firmware'.
Click to expand...
Click to collapse
As long as the returning isn't involved with lack of screen or input to the screen (touch pad not working) then you are alright? My personal dread would be flashing the phone have it working great for months then something goes wrong only to find out you cannot revert it then you have no come back at all.
Well - with your screen not working you can still flash a new ROM if you know the procedure. There is no touch input involved in the procedure, so you should be fine with it and you can alway claim that you had to hard reset (the phone after flashing will appear like after hard reset - time/date not set etc.) before returning for repair because of the corporate information stored in it.
Still everyone should be aware that flashing the ROM and/or SPL can void the warranty and decide for themselves.
So what is the deal with returns?
I have Orange care insurance on my contract and in the past with other handsets if i've had a problem i've just sent it off and had a new handset the following day by courrier.
If i was to flash a cooked rom and then have the screen smashed. It would be a replacement under insurance, not warranty so i would still be sent a replacement handset and i guess that would be the end of it ?

Sorry for Cryin out loud but need your help guys

Hello Guys,
I am from india and I got the HD2 few months back, well to sum up the experience, I have had with the device would be “love and hate” kind of. There are times when I am simple awe stuck by the awesomeness of the device and yet there are times when she acts like a complete ***** freezes for no particular reason. It got so frustrating at times that I even contemplated on selling it off but some thing always stopped me .I would like to thank all the wonderful developers out here who have come up with such amazing apps that at least has made my device usable to a great extend. I THANK YOU ALL from the bottom of my heart.
I am on my official ROM with which the device came shipped with and the version being 1.43 and it’s quite ironical that we haven’t had a single ROM update ever since it has been launched in our country. Any way to cut the whole story short I would humbly request you guys to please look in to my queries:-
1)I am a newbie in to windows OS, so the utter thought of flashing the device kind of scares me off cause I have heard that if not done properly it can brick the device ,But lately I am willing to take that risk only if the cooked rom can solve these 2 grave issues of mine.
a) the screen acts like a lunatic on the run .ghost presses ,hyper sensitivity etc the screen sensitivity tweak did help me a lot but still I am not 100% confident while typing ,So my question is does any of the cooked ROM takes care of this ? and if yes kindly let me the name of it.(this is one issue which I really cant get over)
b) The phone freezes for no particular reason at all , It just stops responding of its own .does the cooked ROM would take care of this as well?
2)Do the official ROM’s address the issues that I have mentioned above from what I know that HK got a new ROM update with the version being 1.72 (Sorry if I am wrong),So in 200 million years I would get to get the official ROM in my country as well and If I am not a prehistoric fossil by then I would rather wait for the it to come as its rather a safe bet for a newbie like me .So any ideas guys as to if the HTC official ROMS take care of these issues .
3)The erratic nature of the screen is it a generic problem ? I can not replace my device in the pretext of this behavior if this is a problem specific to my device, because we have no replacement policies out here. So can a ROM update (cooked or Official ) get rid of this completely .
So guys please do let me know the name of the roms both cooked and official which can help me get rid of these issues.
Cheers .
Flashing the phone is extremely straightforward and easy to do.
If you can follow instructions, you can do it.
I've HSPL'd 3 devices and haven't bricked any of them.
Once you've HSPL'd it's highly unlikely that anything else (within reason) you do will brick the device.
You may render your device temporarily unuseable, but the fact that HSPL allows you to flash without a USB connection off the microSD (!) means that it's nearly impossible to brick a successfully HSPL'd phone.
my suggestion is to dare for a custom rom. study very carefully the tutorials in the rom development forum and you'll be fine, it's not rocket science.
however, to avoid any issues, please remember to always clean your device between two custom flashes by any of the 3 methods:
- flash stock rom + hard reset
- mtty
- task 29
i've always used the 1st method without any issues. it's more time consuming then the others but i've got used to it.
about which rom, this is a matter of preference, there is no best rom for everybody.
you can see which is my favorite under my signature. it's very fast and stable and very close to stock.
i will end by saying that i had many issues in the first couple of month after buying this phone but now it works like a charm, i love it!
oh, and i'm never gonna go back to stock... ever.
cheers and good luck,
antaed
antaed said:
my suggestion is to dare for a custom rom. study very carefully the tutorials in the rom development forum and you'll be fine, it's not rocket science.
however, to avoid any issues, please remember to always clean your device between two custom flashes by any of the 3 methods:
- flash stock rom + hard reset
- mtty
- task 29
i've always used the 1st method without any issues. it's more time consuming then the others but i've got used to it.
about which rom, this is a matter of preference, there is no best rom for everybody.
you can see which is my favorite under my signature. it's very fast and stable and very close to stock.
i will end by saying that i had many issues in the first couple of month after buying this phone but now it works like a charm, i love it!
oh, and i'm never gonna go back to stock... ever.
cheers and good luck,
antaed
Click to expand...
Click to collapse
Mate did you have problems with the screen as well? If yes then did the ROM that you are suggesting took care of them all?
Cheers.
i'm not sure if this is what you mean but i remember it acting strange at some point, after continuous use for 2-3 weeks with the original stock onboard and especially in opera. for example, streams of small vibrations but no movement while trying to scroll or zoom pages.
i've never experienced anything like that since but i have to admit that i flash a new rom every second week or so. i always want to try the latest release, it's very addictive .
hey chakraa...
I have had similar probs...and did HSPL on my HD2 and have been satisfied, and have tried 30 different roms so far.... if you are looking for suggestions i would say "ROMeOS" makes some good roms... his latest 4.07 is good....suggest you try it.... after you do the HSPL your HD2.
challu said:
hey chakraa...
I have had similar probs...and did HSPL on my HD2 and have been satisfied, and have tried 30 different roms so far.... if you are looking for suggestions i would say "ROMeOS" makes some good roms... his latest 4.07 is good....suggest you try it.... after you do the HSPL your HD2.
Click to expand...
Click to collapse
Hey Bro ,Thanks a lot , I am finally mustering courage to go for THE big step(lol I am sounding as if I am about to get married or something), I would surely look in to the ROM which you have suggested,Would let you know about the outcome.
Finally did it.
Hey Guys,
Thanks a lot for your help I finally did flash the ROM all seems to be working fine now.
@CHALLU thanks buddy in the end I installed the rom suggested by you,seems quite stable as of now.Never been a big fan of SENSE so got SPB back ,the key board works like charm and some how I am getting this uncanny feeling that the battery life has improved as well.Do suggest me some other ROMS as well which would improve battery life ,take care of the screen sensitivity and enhance the over all stability.

What the BRICK!?!

So I went out and got a TMOUS HD2. Fantastic. Love it more than the Iphone for the typical reasons. So I'm at the point where its time to really make it mine, custom rom, a few tweaks, a few preferred apps, etc...
Here's what goes down.
1. I try to install HSPL. I fail, not yet knowing there is a difference between the TMOUS and typical flavor machine. Luckily I don't brick, learn my lesson, find the right HSPL.
2. Install a TMOUS friendly HSPL. Cotulla shows in the boot loader and all that jazz. Radio is of the 2.08 flavor which should be compatible with sutom roms, so with that 100% successful I should be good to go.
3. Huh. Rom page says I should TASK29 before I install. Ok. TASK29 seems like a cleanout and reformat of the room, so that makes sense, though I only seem to half understand it. What's the least hassle way to handle that? Well, since I don't want to change my radio it looks like the "ShaDrac repack" is the way to go. I follow the download link, watch the youtube video, and set to do the deed.
4. This is where I should be saying "and then I went into the bootloader and installed the TMOUS friendly custom rom." I didn't get this far. TASK29 went to 100% and rebooted the phone, only it hung on the T-Mobile splash screen (that part that says "stick together!" in obnoxious pink). I figure it just needs a good old fashioned reset like in the instructions. I pull the battery and put it back in, getting the same result. I'm a bit worried, but I have my rom ready on an SD card, toss that in and proceed to try to go to the boot loader (which should always come up since HSPL is installed, right?) Well, that time when I tried to boot up I got nothing, not even the ill fated splash screen. This thing looks bricked, doesn't respond AT ALL, even after I let it sit for 24 hours to let the internal battery die and hope it'll go to at least the bootloader. Tried hard reset, tried linking it up to the computer (WMDC says there is no device there), tried volume down+power. Nothing it just sits there like a rock.
I went over my steps carefully, read numerous posts, and as far as I can see I did nothing wrong. (I completely avoided anything involving the radio and the dreaded number "51") Please correct me if I'm effed up somewhere. I've flashed devices before and never bricked, even though this was my first HD2 attempt, so I'm not completely unknowing in the subject.
If anyone has a solution I'd love to hear it. If anyone has any idea WTF happened, I'd love to hear that as well, even if it means I just made a $300 mistake. At this point I am officially stumped like a chump.
darkekun said:
So I went out and got a TMOUS HD2. Fantastic. Love it more than the Iphone for the typical reasons. So I'm at the point where its time to really make it mine, custom rom, a few tweaks, a few preferred apps, etc...
Here's what goes down.
1. I try to install HSPL. I fail, not yet knowing there is a difference between the TMOUS and typical flavor machine. Luckily I don't brick, learn my lesson, find the right HSPL.
2. Install a TMOUS friendly HSPL. Cotulla shows in the boot loader and all that jazz. Radio is of the 2.08 flavor which should be compatible with sutom roms, so with that 100% successful I should be good to go.
3. Huh. Rom page says I should TASK29 before I install. Ok. TASK29 seems like a cleanout and reformat of the room, so that makes sense, though I only seem to half understand it. What's the least hassle way to handle that? Well, since I don't want to change my radio it looks like the "ShaDrac repack" is the way to go. I follow the download link, watch the youtube video, and set to do the deed.
4. This is where I should be saying "and then I went into the bootloader and installed the TMOUS friendly custom rom." I didn't get this far. TASK29 went to 100% and rebooted the phone, only it hung on the T-Mobile splash screen (that part that says "stick together!" in obnoxious pink). I figure it just needs a good old fashioned reset like in the instructions. I pull the battery and put it back in, getting the same result. I'm a bit worried, but I have my rom ready on an SD card, toss that in and proceed to try to go to the boot loader (which should always come up since HSPL is installed, right?) Well, that time when I tried to boot up I got nothing, not even the ill fated splash screen. This thing looks bricked, doesn't respond AT ALL, even after I let it sit for 24 hours to let the internal battery die and hope it'll go to at least the bootloader. Tried hard reset, tried linking it up to the computer (WMDC says there is no device there), tried volume down+power. Nothing it just sits there like a rock.
I went over my steps carefully, read numerous posts, and as far as I can see I did nothing wrong. (I completely avoided anything involving the radio and the dreaded number "51") Please correct me if I'm effed up somewhere. I've flashed devices before and never bricked, even though this was my first HD2 attempt, so I'm not completely unknowing in the subject.
If anyone has a solution I'd love to hear it. If anyone has any idea WTF happened, I'd love to hear that as well, even if it means I just made a $300 mistake. At this point I am officially stumped like a chump.
Click to expand...
Click to collapse
If I'm following you then what you need to do is put the phone in bootloader manually. Pull the battery and hold down the "down volumn" button. This should bring up the tri-colored screen(bootloader). Connect your USB cable wait for it to show "USB" then Flash away...I hope this helps
Im sorry...Just read your whole post and it seems you've already done what I suggested..
well if the battery is dead, it isnt going to turn on. now that the battery has depleted completely, let the phone charge again. once it does try to go into bootloader and flash ROM from sdcard or via USB.
One more thing...
Oh, one thing I forgot to mention before.
I've set the thing charging for about 3 hours and still no response. Furthermore, when I have the charge cable in I don't get the LED that lights up during a charge does not turn on. It just sits there unresponsive.
check your battery pins. plus you haven't said what rom was on your sd card.
oh and in step four, after task 29, it's supposed to hang at the boot screen, there's no rom on the phone, task 29 just erased it.
you should have held vol down as soon as it hit 100% and gone into boot loader. if you mis time it, pop the battery, hold vol down and tap power to manually enter boot loader then connect to usb and flash your rom.
The rom I was trying to flash to was the latest OZrom for the 1024. Seems like the most stable cooked rom that I've been able to find for the TMOUS HD2.
Mostly I just want a WM 6.5.5 rom with CHT and the full functionality of the HD2. WM 6.5 stock just isn't quite finger friendly enough for me (though HTC Sense helps a LOT) and I want to have some more of the customization that CHT offers.
Holy crab in a burning biodegradable bag on my doorstep.
It was the battery pins not lining up properly. Why is it always the dumbest most simple things that defeat me when I'm handling something high tech?
did you get it flashed okay? I'm gonna attempt my first flash tomorrow for my hd2 and I was gonna do the task 29 also, pretty much with the same steps you listed. When I saw your post it worried me for a sec
SUCCESS!!!
I have successfully flashed OZrom onto my HD2 and have saved myself from having to spend another $300 in shame.
Had to flash from SD card since for some reason WMDC 6.1 was not detecting the HD2 on bootload screen, but it still worked.
Hopefully that'll take some of the fear out of this process.
Do your research right and things go (almost) according to plan.
dont worry
Do not worry man same **** happen to me.... I had gunk on the batt pins felt like an idiot lol
If you have any other issues with the phone not charging check out my post on the pins for the battery.
http://forum.xda-developers.com/showthread.php?t=701939
There has been an issue with the contacts being bent and then they don't contact the battery and wouldn't charge it.
Well, I'd like to thank you all for your help with my issue. My HD2 seems to be rocking nicely. Battery life seems to be shortened a bit, but I've also probably been tooling around with it too much, else it might just be I chose a power hungry rom. I'll also keep my eye on that batter contact issue.
Once again. Thank you.
darkekun said:
Well, I'd like to thank you all for your help with my issue. My HD2 seems to be rocking nicely. Battery life seems to be shortened a bit, but I've also probably been tooling around with it too much, else it might just be I chose a power hungry rom. I'll also keep my eye on that batter contact issue.
Once again. Thank you.
Click to expand...
Click to collapse
Do this test with different radios.
Flash a radio and let it charge all the way and write the time you unplug it and let it die by it self and then write the time.
Flash another radio and do the same thing.
While doing these test try to use the phone with the same settings as the previous tests and close to the same usage.
This way you can find the best radio for the area you live in which helps battery life overall.
darkekun said:
Had to flash from SD card since for some reason WMDC 6.1 was not detecting the HD2 on bootload screen, but it still worked.
Click to expand...
Click to collapse
no it won't recognize it.it doesn't need to.
when the phone is in boot loader connect usb and watch the phone screen for the word serial to change to usb. when it says usb you can flash. wmdc will never see a phone in boot loader.
when instructions say "connect to active sync " they don't mean connect to the active sync/wmdc software they just mean connect to usb. its an added confusion that there is no need for.

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.

[Q] Few noobish questions

So... uh... I know you're disappointed, maybe even angry that with all those FAQs there are still some guys who don't understand everything.
I bought my HD2 today (or maybe I got it today, but ordered it few days ago). It was used before, but as far as I could tell, nothing was done there - stock ROM, SPL 1.42.000, radio 2.07.51.22_2. The first thing I wanted to do was to install Android, so I read some guides here, HardSPL'd to 2.08.hspl, then I saw that I'd have to upgrade my radio. BUT! I've read that you can brick your phone by installing wrong radio and there was no answer to...
FIRST QUESTION: What radio(s) can I upgrade to without fear of bricking my precious?
SECOND QUESTION: What are the differences between radios and why the one with top number isn't the best?
THIRD QUESTION: When I'll eventually install new radio, how do I know if it's worse or better than previous one? Is there a fast and efficient way to check it? I don't use my phone as a calling device too often (average 1 call and 0.5 sms a day), so it would take ages to detect all flaws by using it as always.
And without going into any details, can you say - why would I install Android on SD? From what I've heard and read, NAND version is faster (and I haven't heard anything else).
Oh. Please, don't kill me because I'm a newbie I have some experience with jailbreaking iPods and installing ROMs on HTC Artemis, but with HD2 things I'm for now like "I'd better not touch it, I paid so much for this phone, so I don't want to brick it ".
If something is unclear, just ask.
1) If you have a tmobile HD2 you can flash any radio with the third set of numbers being .50 as long as it's above 2.08.50, you cannot flash any radio where those numbers are .51.
example:
2.10.51.xx = brick
2.07.50 = brick
2.11.50 = safe
etc...
If you do not have a tmobile US version, you're safe with the radios I stated above not to flash.
For Android, only use 2.10.50 and above, I've had nothing but problems with older radios.
2) They communicate slightly differently with your hardware. The "newer" might have better battery life for some, or better reception with Android but not WP7. The truth is no one knows exactly what aspect of which radio is better, you have to just flash them and find out. Newer does not always mean better (although I do like 2.15.50 the most).
3) There's no fast way to check this, other than maybe on the 2.11.50 radio you had only Edge with terrible speeds, then flash 2.12.50 and suddenly you see H everywhere (I've had that happen). Also you might see more bars immediately. For battery life you can have Current Widget (Android) which will show your battery drain. One radio might show 2ma and the other might have 10ma for some reason, obviously the 2ma will give you longer battery life (this is in standby)
But there are so many factors. Which ROM, kernel, mod, apps all effect stuff on your device. Different radios work better in different regions too.
What I would recommend is use 2.15.50 for Android and 2.12.50 for WP7
But play around and see what you think!
Spaqin said:
So... uh... I know you're disappointed, maybe even angry that with all those FAQs there are still some guys who don't understand everything.
I bought my HD2 today (or maybe I got it today, but ordered it few days ago). It was used before, but as far as I could tell, nothing was done there - stock ROM, SPL 1.42.000, radio 2.07.51.22_2. The first thing I wanted to do was to install Android, so I read some guides here, HardSPL'd to 2.08.hspl, then I saw that I'd have to upgrade my radio. BUT! I've read that you can brick your phone by installing wrong radio and there was no answer to...
First, Congratulations
FIRST QUESTION: What radio(s) can I upgrade to without fear of bricking my precious?
Depends, is your device the european version or the T-Mobile's Version? (Are the Talk and Hang-up button Coloured with green and red? and do you see "T-Mobile"'s logo ontop of your device?)
The radio's that supposedly won't kill your device must meet those two conditions:
1- The radio must be above 2.08 .. (2.09 or 2.10 .... 2.15)
2- The radio SHOULD NOT have "51" in it's tag (i.e. this radio "2.04.51_55_8 will brick your device )
SECOND QUESTION: What are the differences between radios and why the one with top number isn't the best?
Because Radio's efficiency depends on where you live, some people use the latest and it gives them very good reception .. others on different places might get poor receptions.
THIRD QUESTION: When I'll eventually install new radio, how do I know if it's worse or better than previous one? Is there a fast and efficient way to check it? I don't use my phone as a calling device too often (average 1 call and 0.5 sms a day), so it would take ages to detect all flaws by using it as always.
Well, I don't think there is another way beside monitoring your reception and your data losses .. Just keep an eye on your signal bar and/or your call (drops) (despite cLK/PPP)
And without going into any details, can you say - why would I install Android on SD? From what I've heard and read, NAND version is faster (and I haven't heard anything else).
Some people prefer to have Windows Phone 7 on their NAND, yet they want to play with Android sometimes so it becomes a win win . Furthermore, SD cards are easier to deal ith in term of modifications.
I don't think NAND builds are faster, both have same speed (you just have to pick the right rom for you )
Oh. Please, don't kill me because I'm a newbie I have some experience with jailbreaking iPods and installing ROMs on HTC Artemis, but with HD2 things I'm for now like "I'd better not touch it, I paid so much for this phone, so I don't want to brick it ".
(we won't kill you )
If something is unclear, just ask.
Click to expand...
Click to collapse
Omg, I need to recharge my battery
EDIT:
Well, Orangekid was faster, i think
Thanks for the replies, guys!
My device is the european version (no coloured buttons and no logo, bought at Polish store with no simlock). So it looks like I should be safe with all radios, right? There's no way that something may screw up by itself? As I said, my HD2 isn't new and I don't know much about device's history. Is there something I should check?
Sorry if I ask too many questions... I'm just amazed with the phone (everything else seems to be so little now and I wouldn't want to break anything.
About NAND and SD versions of Android - well, I've heard that you need to wait very long to wake up the phone from standby (I mean it's not instant definitely) on SD version, but with playing with NAND you could break something more easily.
Spaqin said:
Thanks for the replies, guys!
My device is the european version (no coloured buttons and no logo, bought at Polish store with no simlock). So it looks like I should be safe with all radios, right? There's no way that something may screw up by itself? As I said, my HD2 isn't new and I don't know much about device's history. Is there something I should check?
Sorry if I ask too many questions... I'm just amazed with the phone (everything seems to be so little and I wouldn't want to break anything.
About NAND and SD versions of Android - well, I've heard that you need to wait very long to wake up the phone from standby (I mean it's not instant definitely) on SD version, but with playing with NAND you could break something more easily.
Click to expand...
Click to collapse
NP, better to ask a bunch of questions than brick your device.
you do not have a tmobile US version, so those .51 and below 2.08.50 radios will not brick your phone, however Android doesn't like anything below 2.10.50 and does some stupid ****.
as far as wake-up from SD lag, doesn't happen on my SD rom, so I wouldn't worry about that. This ROM:
http://forum.xda-developers.com/showthread.php?t=957652
is awesome, and performs just as well or better than any NAND rom I've used. Since I use WP7 in NAND, I stick to that ACA SD ROM and I love it.
Marvlesz said:
The radio's that supposedly won't kill your device must meet those two conditions:
1- The radio must be above 2.08 .. (2.09 or 2.10 .... 2.15)
2- The radio SHOULD NOT have "51" in it's tag (i.e. this radio "2.04.51_55_8 will brick your device )
Click to expand...
Click to collapse
#2 isn't the best example because even if that radio was .50 it would brick a tmous device.
orangekid said:
#2 isn't the best example because even if that radio was .50 it would brick a tmous device.
Click to expand...
Click to collapse
I know
.04 and .05 can have .50 yet brick devices .. that's why I said above .08
thnks !
Marvlesz said:
I know
.04 and .05 can have .50 yet brick devices .. that's why I said above .08
thnks !
Click to expand...
Click to collapse
No worries, good write-up.
The more often we tell people this stuff hopefully the less "oh **** I bricked my tmous hd2" threads.
So ALL the radios should work? Does updating radio require WinMo, or can it be done without it?
Anyway, it looks like I won't bother much with NAND Android. I'll just leave WinMo 6.5 for now, maybe later I'll be able to understand this magldr thing (for now all the descriptions are like 'it's something that allows you to boot other OS from NAND', but I have no clue how does it work).
Spaqin said:
So ALL the radios should work? Does updating radio require WinMo, or can it be done without it?
Anyway, it looks like I won't bother much with NAND Android. I'll just leave WinMo 6.5 for now, maybe later I'll be able to understand this magldr thing (for now all the descriptions are like 'it's something that allows you to boot other OS from NAND', but I have no clue how does it work).
Click to expand...
Click to collapse
Yes, you're safe from radio brick, but i wouldn't bother with any radio below 2.10.xx
You can flash the radio from HSPL (hold the volume down button and power on) or from WinMo with an activesync connection.
MAGLDR is a second bootloader that sits on top of HSPL and allows you to:
1) boot WP7
2) boot Android recovery
3) boot Adroid NAND
4) boot android SD without having to boot winmo first
5) play tetris from your bootloader
Flashing MAGLDR is very safe and very easy, same process as flashing a radio. You can't do anything with or from magldr that will brick your phone because it loads after HSPL so worst case is you boot into HSPL and flash stock or reflash magdlr.
about nand or sd:
some people like to dual-boot either winmo or Android. This will give you the option to run one or the other. If you decide to go the sd route then you might want to check a program called RunDroid found here. It makes it make the process of booting different builds a lot more simple and easier I feel.
About radio:
I know a lot of people seem to say stay above 2.10 but I've seen a small increase using 2.08.50. This will/can be different for you so i would suggest to try them to see what gives you the best signal. Start with the newest or maybe even 2.15.50.
About testing signal strength:
For a good way to get a fairly accurate reading on signal I would go into settings, about phone, then network. Look at the signal you have, I would suggest to leave your phone in one place and don't try to move it. Get the readings maybe 3-5 times over a few mins, I'd think the longer the better. Then flash a new radio. The closer to a positive number the better. Low signal for me normally means around -108 while good for me is around 89. (It's normal to show negative when you have poor signal.) This is a little more accurate I feel then trying to see how bars you have. Infact one radio over another may only show a small increase and not enough to generate a full bar so just play around and see what works best for where you live.

Categories

Resources