Related
My phone works perfectly except I can't answer calls, when I press answer/ignore it freezes until it goes to voicemail and then comes back. I've flashed multiple roms and had the problem with all of them. I'm not using any special themes or anything, and the only software I ever install are HD Tweak and Finger Keyboard 2.1 and my radio 1.14.25.24. Here's a list of what I've done since I had the phone:
1. Bought phone. Flashed HSPL. Flashed Laurentius L26, no problems. Was being lazy so I didn't hard reset after flashing.
2. Flashed Dutty R14. Didn't hard reset after flashing. No problems for awhile and then the problem of not being able to answer calls appeared.
3. Flashed EnergyRom wm6.5 rom. Hard reset twice after. Still having problem where I can't answer calls.
4. Flashed Dutty 3.9XT wm6.1 rom. Hard reset twice after. Still having problem where I can't answer calls.
If anyone can help me figure out why my phone is doing this I'd really appreciate it, I'll even pay you some money on PayPal if you like because I really want to fix it. Here are some ideas I had as to why it's not working:
- Problem with rom flash. No, because I tried it with 3 different roms so far and had the same problem.
- Touch HD isn't fast enough to run wm6.5 and be stable. No, because I tried it with a wm6.1 rom too and had the same problem.
- Someone suggested it might be a problem with the battery. No, because I ordered new replacement batteries and tried them and had the same problem.
- Some of the settings in HD Tweak are incompatible with something in the roms I'm using. Maybe, is this possible? I don't really change much, just the softkeys and the highlight color and things like that.
- Screwed up something in the SPL or something because I didn't hard reset after flashing the first 2 roms. Maybe, is this possible?
- Dropped my phone and somehow managed to break nothing but the mechanism involved in answering calls. Maybe, is this possible?
Today I'm going to reflash HSPL, flash the stock HTC rom, hard reset twice, and see if I still have the problem. I don't know what else to do or what other possibilities there are. If anyone can shed some light on this issue, that would be great, because I really don't want to have to buy a new phone. Thanks
Did you try another SIM?
rpimps said:
My phone works perfectly except I can't answer calls, when I press answer/ignore it freezes until it goes to voicemail and then comes back. I've flashed multiple roms and had the problem with all of them. I'm not using any special themes or anything, and the only software I ever install are HD Tweak and Finger Keyboard 2.1 and my radio 1.14.25.24. Here's a list of what I've done since I had the phone:
1. Bought phone. Flashed HSPL. Flashed Laurentius L26, no problems. Was being lazy so I didn't hard reset after flashing.
2. Flashed Dutty R14. Didn't hard reset after flashing. No problems for awhile and then the problem of not being able to answer calls appeared.
3. Flashed EnergyRom wm6.5 rom. Hard reset twice after. Still having problem where I can't answer calls.
4. Flashed Dutty 3.9XT wm6.1 rom. Hard reset twice after. Still having problem where I can't answer calls.
If anyone can help me figure out why my phone is doing this I'd really appreciate it, I'll even pay you some money on PayPal if you like because I really want to fix it. Here are some ideas I had as to why it's not working:
- Problem with rom flash. No, because I tried it with 3 different roms so far and had the same problem.
- Touch HD isn't fast enough to run wm6.5 and be stable. No, because I tried it with a wm6.1 rom too and had the same problem.
- Someone suggested it might be a problem with the battery. No, because I ordered new replacement batteries and tried them and had the same problem.
- Some of the settings in HD Tweak are incompatible with something in the roms I'm using. Maybe, is this possible? I don't really change much, just the softkeys and the highlight color and things like that.
- Screwed up something in the SPL or something because I didn't hard reset after flashing the first 2 roms. Maybe, is this possible?
- Dropped my phone and somehow managed to break nothing but the mechanism involved in answering calls. Maybe, is this possible?
Today I'm going to reflash HSPL, flash the stock HTC rom, hard reset twice, and see if I still have the problem. I don't know what else to do or what other possibilities there are. If anyone can shed some light on this issue, that would be great, because I really don't want to have to buy a new phone. Thanks
Click to expand...
Click to collapse
Hi rpimps,
I think that would be a good idea, flash back to stock, check for any differences, if everything works ok, then try flashing to a custom ROM again.
It might be an idea to try out a different radio version, for example, try 1.17 as this could improve certain built in feaures of your phone, especially since radio versions are known to work only in specific regions, it may work out better for you overall
Also, if not already cooked into the custom ROM of your choice, you should also install the RIL version that matches your radio version - 1.17 Radio supports RIL version 1.14 (1.14.25.24), which you can download the RIL via this link, at the bottom of post #1 - read this section as it also explains how to install the RIL.
I recently remember another member mention that their phone would sometimes hang when/after receiving a call, this was solved by installing the associated RIL - a layer in an operating system which provides an interface to the hardware's radio and modem.
Best regards.
Just to see if call mechansm works;
- try to record something (to check mic)
- try front speaker (i dont know how to do this)
- check if vibration works. (vibrate on connect may be on)
I guess your gsm radio works well since you can receive calls. Try to use windows original phone canvas instead of touchflo 3d. Dont know what to check more Its strange.
simplistian said:
Did you try another SIM?
Click to expand...
Click to collapse
I did that just now and it had the same problem (on the HD) no matter what sim I put in it.
Mastoid said:
Hi rpimps,
I think that would be a good idea, flash back to stock, check for any differences, if everything works ok, then try flashing to a custom ROM again.
It might be an idea to try out a different radio version, for example, try 1.17 as this could improve certain built in feaures of your phone, especially since radio versions are known to work only in specific regions, it may work out better for you overall
Also, if not already cooked into the custom ROM of your choice, you should also install the RIL version that matches your radio version - 1.17 Radio supports RIL version 1.14 (1.14.25.24), which you can download the RIL via this link, at the bottom of post #1 - read this section as it also explains how to install the RIL.
I recently remember another member mention that their phone would sometimes hang when/after receiving a call, this was solved by installing the associated RIL - a layer in an operating system which provides an interface to the hardware's radio and modem.
Best regards.
Click to expand...
Click to collapse
Here's what I did today:
1. Reflashed HSPL. Hard reset.
2. Couldn't find a working stock rom so I just reflashed Dutty 3.9XT. Hard reset.
3. Installed 1.17 radio and rilphone 1.14 like you recommended.
4. Didn't install anything else. Tested phone right after install and it's still having the problem.
barisahmet said:
Just to see if call mechansm works;
- try to record something (to check mic)
- try front speaker (i dont know how to do this)
- check if vibration works. (vibrate on connect may be on)
I guess your gsm radio works well since you can receive calls. Try to use windows original phone canvas instead of touchflo 3d. Dont know what to check more Its strange.
Click to expand...
Click to collapse
I can call other people and it works fine. And actually about 10% of the time I CAN answer calls, and when it works it works perfectly. But 90% of the time it won't let me answer.
I might just have to put this phone on ebay and go back to my Diamond
rpimps said:
I can call other people and it works fine. And actually about 10% of the time I CAN answer calls, and when it works it works perfectly. But 90% of the time it won't let me answer.
I might just have to put this phone on ebay and go back to my Diamond
Click to expand...
Click to collapse
that's a shame dude, not sure what else to suggest... it sounds like a hardware related issue as you have repeatedly tried flashing different firmware one on the phone... i suppose it's not under warranty?
Mastoid said:
that's a shame dude, not sure what else to suggest... it sounds like a hardware related issue as you have repeatedly tried flashing different firmware one on the phone... i suppose it's not under warranty?
Click to expand...
Click to collapse
It's only a few months old so it might be, but doesn't flashing spl/roms void the warranty?
rpimps said:
It's only a few months old so it might be, but doesn't flashing spl/roms void the warranty?
Click to expand...
Click to collapse
Unfortunately, it breaks the warranty aggreement. So e-bay is a good idea, I guess.
P.S: I heard from someone that you can go back to stock rom then you can still use your guarantee. But I'm not sure if they can see that you reflashed it or not.
rpimps said:
It's only a few months old so it might be, but doesn't flashing spl/roms void the warranty?
Click to expand...
Click to collapse
From what I have read, if you flash back to the exact stock ROM which was installed on your phone when you had received it, then this will not affect your warranty - if you decide to return your phone (assuming it is still under warranty) just make sure you downgrade to Stock ROM and Radio version, with no trace of HSPL or USPL also, or else you will have to pay them money if they (HTC) find out
EDIT: Please follow these steps to restore back to your stock ROM version:
1. First, be sure to restore your stock OS, and then the stock radio. The Stock SPL is always to be done last!
2. Download your choice of a stock spl package from the link shown below. (currently 1.13, 1.14, 1.15, 1.54)
3. Also download the original hardspl from the link shown below.
4. Run the hardspl exe but do not click anything in RUU yet. Just let the hardspl EXE extract the files for flashing.
5. The SPL you want to revert to is a .NBH file, put the stock SPL NBH in the extracted hardspl package, overwriting the original NBH file in it!
6. Continue with the RUU (or if needed, run SSPL-Manual.exe manually, then run RUU when it goes to tricolour 1.07.OliNex screen), it goes to 100%, reboots, done.
7. To verify, enter bootloader mode, see version number on tricolour screen, should now just say 1.14.0000 or any other version ending in .0000, but not ending in OliNex!
that's it.
Please refer to the following link for more information and the necessary files you will require to re-flash back to Stock (see and read the last section of post #1):
http://forum.xda-developers.com/showthread.php?t=431217
Regards.
p.s. also remember to flash back to the original Radio version of the phone, if required.
There are several stock ROMs linked in the Blackstone Wiki, flash back to one of those and see if your problem is still there. If it is, send it back for a Warranty repair - as long as there is a stock SPL and ROM image on your phone, you Warranty will be intact.
what i dont see is mention of ho u are answeing the calls.
there or at least three ways
1. the on screen prompt. i assuming this is the one that freezes
2. the answe key at the bottom left of the phone
3. the htc headphones im assuming you have
have u tried using all three of these methods to answer calls??
Hi,
I wonder if there is a way to use Android on the HD2 without the special ROM version it needs. During a reboot my device shows:
R 2.07.51.22~2
G 15.32.50.07U
D 1.72.86526
A reset with the volume down key being pressed shows "SPL 1.66.0000".
Thank you
Hi,
that´s a fine question. My device shows the same.
Can annybody tell us something about this topic?
Thanks
You can try andriod without any rom changes, just download it, extract to SD card & run (per instructions). It should work, in general, but you'll most likely get the common issues, like "robot voice".
Try some builds & see how they work for you.
Today I tried out "HyperDroidV1.2" but i get one of the known problems!
I don´t want to change the radiorom because of my warranty.
Every thread I looked up say, that you lost the warrenty if you try HSPL and a other RadioRom.
I'm afraid to make my phone unusable.
Thanks for your answer!
Without the right Radio ROM, Android will stop booting at the "init screen" (or "init panel"?) line and the display will fade to black.
daemonfly said:
You can try andriod without any rom changes, just download it, extract to SD card & run (per instructions). It should work, in general, but you'll most likely get the common issues, like "robot voice".
Try some builds & see how they work for you.
Click to expand...
Click to collapse
Be careful!!
I tried the FroyoSense V2 on my stock HD2, and my WM locked up totally. No 3'rd part progs would run, could not install anything. The phone was more or less useless. So backup your phone before even trying to run Android.
well you need at least 2.08 radio. i have exact same stock rom, but you need to hspl and upgrade your radio.
Why are you hesitant to flash a new radio? It is super simple to do and it is reversible. If I were you I'd go to radio 2.12. You can also flash a custom WM Rom with built in android boot manager.
My understanding is that Andriod only works with the R 2.**.50.** radio. I think these are the US radios. Any .51 radio are for EUR/AUS and will not work with Android.
I have a Telstra HD2 with 2.09.51.03 and have to flash 2.10.50.08 inorder to work with Android.
I believe unless you have a TMobile HD2, it is quite safe to use any radio rom and the flashing process is very straight forward indeed.
Update: Maybe stock rom is not flashing because i'm not getting the correct ROM for this phone?
Could someone PLEASE help me identify the correct stock ROM with the below serial number of the phone?
Hi Xda gods,
I shows me as a noob because i forgot my old account password!
Anyway, I have with me a friend's EU HD2. Details as follows:
HTC HD2 T8585
S/N: SH06KNW01615
The following are the problems with the phone:
1. I think he had someone try to upgrade the radio on the phone WITHOUT HSPL first because it used to show a 'software update failed, please try again' msg when turned on.
2. Installed HSPL 2.08 successfully and tried to install radio version 2.15.50.** and that didn't work either. got an error 264 i think which said 'this update utility cannot be used on your PDA'.
3. Read in many threads that a possible solution could be to flash back to a stock ROM that came with the phone via SD card method but after abt 3% i get an error saying 'radio v2 FAILED, LEOIMG.NBH FAILED, Update Failed'.
4.Used Mtty and followed the steps..set value to 14 0, task 29, task 8...and then flashed a custom rom through SD card...
5.The cutom rom flased fine but now phone is stuck on 'HTC quietly brilliant' and does nothing else.
Could one of you brilliant minds PLEASE help me solve this problem? i tried for more than 7 hours yesterday but didn't get anywhere...
thanks in advance!
Custom ROM did not have a Radio included so expect trying a Radio such as linked in my sig may be worth another go.
If problems persists could be memory issue or other hardware issue.
Thanks Mister B for the quick response..
I tried flashing a radio before flashing a custom Rom but got the same 'This update utility cannot be used on your PDA' error..tried radios: 2.15.50...2.12.something..even 2.08.50 but all with the same error...
You try radio after flashing ROM ?
What custom ROM are you using ?
Try to flash official ROM. It will update your radio.
Sent from my HTC HD2 using XDA App
"stuck radio" - pretty common error, with varying symptoms. Yours is the standard set of symptoms, , , everything flashes except radios, nothing boots (because radio is corrupt and cannot initialise, i presume).
Other variants are
- spl/hspl appears to flash ('we hacked it' when running hspl.exe) but doesn't change
- radio wont flash but custom roms WILL flash and boot (radio is stuck but not corrupted)
- spl and radio are both stuck and won't change.
Sadly, there are very few success stories regarding this error, however there are one or two, so don't give up hope just yet.
Primarily though, you need to find the correct stock roms, , tried contacting htc support? that's where i would start.
Then, once you know the correct roms to use, get all versions (i.e the 1.42, the 1.66 ((or 1.72 if its branded)) and 3.14) roms for that region/carrier, and try flashing them from sd card. There have been one or two occasions where trying again and again just suddenly works, and there are one or two more where using the freezer trick makes it work.
If your spl is currently 2.x then you need to change that,,, 2.x is NOT a stock spl for regular hd2's, only for tmous hd2's, and it can cause issues as it doesnt like being downgraded, even by sd card flashing. In which case, use hspl2 to set 1.66.0000 and go from there with the sd card flashes, , start with 1.42.
Mainly tho, prepare for bad news, that way when you've exhausted all possibilities you wont be as disappointed, and if it DOES suddenly take, it will be a bonus.
samsamuel said:
"stuck radio" - pretty common error, with varying symptoms. Yours is the standard set of symptoms, , , everything flashes except radios, nothing boots (because radio is corrupt and cannot initialise, i presume).
Other variants are
- spl/hspl appears to flash ('we hacked it' when running hspl.exe) but doesn't change
- radio wont flash but custom roms WILL flash and boot (radio is stuck but not corrupted)
- spl and radio are both stuck and won't change.
Sadly, there are very few success stories regarding this error, however there are one or two, so don't give up hope just yet.
Primarily though, you need to find the correct stock roms, , tried contacting htc support? that's where i would start.
Then, once you know the correct roms to use, get all versions (i.e the 1.42, the 1.66 ((or 1.72 if its branded)) and 3.14) roms for that region/carrier, and try flashing them from sd card. There have been one or two occasions where trying again and again just suddenly works, and there are one or two more where using the freezer trick makes it work.
If your spl is currently 2.x then you need to change that,,, 2.x is NOT a stock spl for regular hd2's, only for tmous hd2's, and it can cause issues as it doesnt like being downgraded, even by sd card flashing. In which case, use hspl2 to set 1.66.0000 and go from there with the sd card flashes, , start with 1.42.
Mainly tho, prepare for bad news, that way when you've exhausted all possibilities you wont be as disappointed, and if it DOES suddenly take, it will be a bonus.
Click to expand...
Click to collapse
Thanks for the feedback.
Actually, HSPL flashes fine..after the 'we hacked it' screen i go into bootloader again and the HSPL has installed.
With custom Roms, they flash fine but stay stuck at the boot screen and nothing else.
Tried every possible method even with Mtty but to no avail! No radio will flash!!
I'm currently on 2.08 but i will downgrade to 1.66 or 1.42 like you said and try again..
It was a branded htc but i installed HSPL..should i still try only stock roms or custom roms are fine?
Also, i saw in someone's post that their bricked HTC was brought back to life using the Goldcard method with dutty's Rom...maybe i can try this method.
Will let you guys know how it turns out.
Excuse me "hijacking" the thread with a question - I've been through this and another long thread about "stuck" radios and not seen a definitive answer (perhaps there isn't one).
In which part of the phone's firmware does the "carrier lock" reside, and what form does it take, is it in the bootloader, radio rom, or main firmware?
I've just purchased a second hand carrier locked HD2. I don't specifically want to unlock it as my sim matches it, but I have installed hspl, using hspl4, with a view to playing with ROMs, and wondered how far you can go without unlocking.
I'm quite used to flashing roms from previous unlocked HTCs I've owned, but I've never had a carrier locked phone before, hence the question.
You can flash away as normal, Carrier SIM lock makes no difference but for the cheap price of HD2 unlocking it may be wise to get a code & unlock it know rather than perhaps the future.
Thanks. I might well take your advice on unlocking bearing in mind the minimal cost.
Still puzzled, as a few of the queries I've seen seem to suggest the problems flashing different radios some folk were having were down to the phone being carrier locked. Or, maybe it was just a case of certain radios only working with certain firmwares (and maybe with certain spls) and nothing to do with carrier lock at all?
Sorry for my apparent ignorance on the subject!
Pete_S said:
Still puzzled, as a few of the queries I've seen seem to suggest the problems flashing different radios some folk were having were down to the phone being carrier locked. Or, maybe it was just a case of certain radios only working with certain firmwares (and maybe with certain spls) and nothing to do with carrier lock at all?
Click to expand...
Click to collapse
you have a regular hd2, therefore all radios will work on your phone, , but with some caveats.
If you intend to
a - use wp7 or nand android..
b - use a custom wm6.5 rom that unlocks the 576mb ram
then you MUST have a tmous radio - which translates to - you MUST use a radio with ..50.. in teh version.
i.e 2.07.51. will not work, 2.07.50 WILL work.
ALL radios will have either 50 or 51 in that third set of digits, if a radio doesn't, dont download it, go find another one. (some radio downloads may show the protocol version first, so it may say something like ''15.32.50.07U 2.07.51.22 2'' in which case its a 51 radio
Many people (myself included) find that some radios give slightly better reception and/or battery and/or less wake from sleep issues than others, however its not consistent, , what works well for one hd2 may not be the optimal for the next hd2 in the same location.
In general tho, most people seem to have settled on 2.11.50, 2.12.50 2.14.50 or 2.15.50.
(For simplicity, go flash 2.15.50 and you can forget about it till you've got everything else working)
Dont bother going lower than 2.10, theres nothing down there thats any better than those four.
As for the radio brick from flashing the wrong radio, thats tmous hd2 only, you can ignore that.
Carrier being locked will have no effect on anything you do, though you cannot unlock it under android, you need to be running winmo 6.5 to enter an unlock code and make it stick.
(Reports on this vary slightly, some people say they have successfully entered a carrier unlock code under android, , , i'm sceptical)
Big note - - - Anything that refers to a tmous, or a tmobile hd2, or a tmobile radio, , does not apply to you, just because it may be t mo provided, or locked to tmo, or running a tmobile branded stock rom,. its still a regular hd2 you have (well, assuming you didnt get an import from the states? it would say t mobile under the earpiece, and have red and green end/send keys if its a tmous). Only t mobile usa bought a different version hd2 from HTC.
samsamuel said:
(Reports on this vary slightly, some people say they have successfully entered a carrier unlock code under android, , , i'm sceptical)
Click to expand...
Click to collapse
Don't be! Sceptical, I mean... They're right!
I've managed to unlock by code a few TMoUS-version HD2s under Android(various versions, I don't remember...)!
Unlocking by wires is another story: it can be done under WM, only!
bib*oops said:
Don't be! Sceptical, I mean... They're right!
I've managed to unlock by code a few TMoUS-version HD2s under Android(various versions, I don't remember...)!
Unlocking by wires is another story: it can be done under WM, only!
Click to expand...
Click to collapse
Hmm interesting, noted.
samsamuel said:
(For simplicity, go flash 2.15.50 and you can forget about it till you've got everything else working)
Dont bother going lower than 2.10, theres nothing down there thats any better than those four.
As for the radio brick from flashing the wrong radio, thats tmous hd2 only, you can ignore that.
Carrier being locked will have no effect on anything you do, though you cannot unlock it under android, you need to be running winmo 6.5 to enter an unlock code and make it stick.
(Reports on this vary slightly, some people say they have successfully entered a carrier unlock code under android, , , i'm sceptical)
Click to expand...
Click to collapse
Thanks so much for all the nuggets of info. I actually have radio 2.15.50 already, so it can't be bettered and is ready for android if I decide to go that route.
The info relating to Android and carrier lock (that it doesn't make any difference unless you want to unlock) is also very useful.
From what you've said it seems carrier locking has very little effect on anything other than, er, choice of sim
So, sorry to be persistent, where does the carrier lock info reside in the phone? In other words, when you unlock a phone, officially or otherwise, where are the bits of information which change? It's purely out of curiosity - I need to know these things
Sorry, no clue, I'd suspect some dedicated chip somewhere, since its not affected by anything we have access to. Just a wild guess tho.
Pete_S said:
Thanks so much for all the nuggets of info. I actually have radio 2.15.50 already, so it can't be bettered and is ready for android if I decide to go that route.
The info relating to Android and carrier lock (that it doesn't make any difference unless you want to unlock) is also very useful.
From what you've said it seems carrier locking has very little effect on anything other than, er, choice of sim
So, sorry to be persistent, where does the carrier lock info reside in the phone? In other words, when you unlock a phone, officially or otherwise, where are the bits of information which change? It's purely out of curiosity - I need to know these things
Click to expand...
Click to collapse
The SIM lock is part of the bootlaoder, more specifically the IPL. This is what only Win Mo ROMs can be used to SIM unlock a HD2 because only Win Mo ROMs can actually communicate with the IPL of the bootloader. Now let me go a little deeper, like Samsamuel said it is more than likely a seperate chip somewhere on the mainboard of the HD2 that actually stores the SIM lock but only the IPL can access and change the data on that chip.
Thanks to you both for the info. That would explain why being network locked has almost no effect on anything else like ROMs etc. The actual info might even be stored in flash in the chip which "drives" the sim.
I think the problem could be somewhat overcome if i knew which would be the correct stock rom for this phone! Its quite maddening!
My phone's serial starts with SH which i know is Shanghai, China but i haven't been able to find a 1.66 stock rom for this..
Thoughts?
samsamuel said:
"stuck radio" - pretty common error, with varying symptoms. Yours is the standard set of symptoms, , , everything flashes except radios, nothing boots (because radio is corrupt and cannot initialise, i presume).
Other variants are
- spl/hspl appears to flash ('we hacked it' when running hspl.exe) but doesn't change
- radio wont flash but custom roms WILL flash and boot (radio is stuck but not corrupted)
- spl and radio are both stuck and won't change.
Sadly, there are very few success stories regarding this error, however there are one or two, so don't give up hope just yet.
Primarily though, you need to find the correct stock roms, , tried contacting htc support? that's where i would start.
Then, once you know the correct roms to use, get all versions (i.e the 1.42, the 1.66 ((or 1.72 if its branded)) and 3.14) roms for that region/carrier, and try flashing them from sd card. There have been one or two occasions where trying again and again just suddenly works, and there are one or two more where using the freezer trick makes it work.
If your spl is currently 2.x then you need to change that,,, 2.x is NOT a stock spl for regular hd2's, only for tmous hd2's, and it can cause issues as it doesnt like being downgraded, even by sd card flashing. In which case, use hspl2 to set 1.66.0000 and go from there with the sd card flashes, , start with 1.42.
Mainly tho, prepare for bad news, that way when you've exhausted all possibilities you wont be as disappointed, and if it DOES suddenly take, it will be a bonus.
Click to expand...
Click to collapse
Fone HTC support, they'll tell you in seconds.
Also, there are no branded 1.66 roms, ,, because branded 1.66 roms carry the verson number 1.72.
(1.3ruu+HSPL+ROM+Raido driver)
OK, long story short, phone not able to recive txt messages, and lots of droped calls on my verizon trophy. I had interop unlock, and chevron. Verizon claimed it a hardware problem and sent me a new phone. In the mean time, I decided to test the roms on the old one. But some how brok something, I want to figure it out befrore I break the new one (already in my possession)
installed a 1.3 RUU rom on my verizon trophy (then activated)
Did HSPL unlock
Installed DFT v1 for spark_W
phone worked, (but txt still did not, HW problem I guess)
installed radio v2 drivers as it seeme to have the original htc driver.
Never got it working again
So, did I do something wrong? For the new phone do I just not use the new radio drivers with the roms?
s10010001 said:
(1.3ruu+HSPL+ROM+Raido driver)
OK, long story short, phone not able to recive txt messages, and lots of droped calls on my verizon trophy. I had interop unlock, and chevron. Verizon claimed it a hardware problem and sent me a new phone. In the mean time, I decided to test the roms on the old one. But some how brok something, I want to figure it out befrore I break the new one (already in my possession)
installed a 1.3 RUU rom on my verizon trophy (then activated)
Click to expand...
Click to collapse
Good, you can use a 1.3 stock like rom in this thread here too, if you already have HSPL installed instead of flashing the stock RUU (you might not be able to flash anything without Goldcard if you keep installing OSPL).
s10010001 said:
Did HSPL unlock
Installed DFT v1 for spark_W
Click to expand...
Click to collapse
DFT v1? Only DFT v3 HSPL for First Generation Phones supports Spark_W ;
s10010001 said:
phone worked, (but txt still did not, HW problem I guess)
Click to expand...
Click to collapse
With either a stock rom, or stock like rom like the ones I posted above, do a factory reset (Settings=>About=>Factory Reset...), THEN do a full *228 option 1 programming. Test phone calls and texting only then. If you aren't doing a factory reset with the stock rom, not all settings will be reset in the Spark_W's programing (which could possible cause a texting issue).
Also, is the phone stuck with a 1X indicator?
s10010001 said:
installed radio v2 drivers as it seeme to have the original htc driver.
Don't worry
Never got it working again
Click to expand...
Click to collapse
All the radios are original radios. The NoDo radio is the one that shipped with the 1.3 RUU. If you are running the 1.3 stock like rom, flash the NoDo radio from my radio thread.
Don't flash any radios for now. Try the factory reset with stock rom (or stock like rom).
s10010001 said:
So, did I do something wrong? For the new phone do I just not use the new radio drivers with the roms?
Click to expand...
Click to collapse
New phone may come with a mango 2.x series rom (highly likely it will at least be Mango v1) or newer (maybe 2.4 if its coming from Verizon). You can still downgrade, but downgrade with official 1.3 RUU will also downgrade radio (don't worry about radio off the bat). The key thing is, to test EVERYTHING before doing HSPL on the new phone. Then:
Flash 1.3 official RUU for SPL downgrade.
Install HSPL
Program Phone (it's fine to program the phone even if you install HSPL, so long as you are running a stock or stock like rom! Full unlock is what gives us the pain in the butt time.. I'm still working on isolating that issue!)
Flash custom rom of choice (I'd go with ansar's Tango build for now).
Also, before you send your old phone back, even if the steps I outlined don't work, make sure you flash OSPL via DFT's v3 for First Generation Phones, then flash "RUU_Spark_W_VERIZON_WWE_1.03.605.22_RS0512_2K_4K_h ybrid_new_partition_RELEASE," and run a FULL Zune update to current software! This should fix any bootloader stuff that Verizon and/or HTC might detect.
It could very well be that you do have some bad hardware, but make sure you cover your butt by going back to OSPL and updating via Zune. If you flash a newer stock rom, you might half brick the bootloader and not be able to flash anything (that requires a GoldCard to fix).
Hope the newer phone works better when you do get it, but yeah, you can still try to fix it using the reset setups I outlined above.
Now, if you get an error trying to place a call that says "Sorry, we could not authenticate your phone, please call blah blah blah..." even after flashing stock rom and a factory reset and programing with *228 option 1, log into your My Verizon account, and switch the phone on the plan to another compatible phone, then switch it back to the Spark_W. I somehow think that you aren't having this issue so you can ignore this unless you are getting this error.
Not a problem with custom ROMs
I am not running anything custom on my phone. However I have not been able to send or receive calls or text messages since last Saturday (Jun 30).
This doesn't seem to be isolated either - these two threads are full of people with the same problem!
(see xda.png - I can't post outside links)
My data connection is usually stable, however it alternates between 5 bars and 1 bar.
-sucks-
My data connection always alternates between 1 and 5 bars..regardless of phone.. but not when I am near a tower (only in my fringe range area).
My bill is current, and I have had no issue sending and receiving text.
Anyone in these threads try dialing *228 and using option 1 or 2 to reprogram the phone/update the PRL?
I'll try to read the threads tomorrow when I have more time.
Are these peoples phones fully updated with the newest 2.4 software (Mango 8107)?
TheXev said:
My data connection always alternates between 1 and 5 bars..regardless of phone.. but not when I am near a tower (only in my fringe range area).
My bill is current, and I have had no issue sending and receiving text.
Anyone in these threads try dialing *228 and using option 1 or 2 to reprogram the phone/update the PRL?
I'll try to read the threads tomorrow when I have more time.
Are these peoples phones fully updated with the newest 2.4 software (Mango 8107)?
Click to expand...
Click to collapse
I'm running 8107.79, and *228 won't even go through.... Phone gets stuck at "Dialing..."
Only time I've had that issue is when I'm completely out of range.. but the phone may still show 3 bars of reception. Have you tried doing it closer to a Verizon tower?
I'm lucky, when I need to get next to a tower, I just go eat my my local DQ. XD
I'm in Manhattan - pretty much near a tower by default
Okay, I'm out of ideas. Only phone (HTC) that I've had do what you described is my HTC Eris.. and its because I let it bake in a window while plugged into the charger (using it as a WiFi hotspot). It's reception has been crap ever since. :/
Sucess?
Has anybody succeeded in resolving the problem?
TheXev said:
Good, you can use a 1.3 stock like rom in this thread here too, if you already have HSPL installed instead of flashing the stock RUU (you might not be able to flash anything without Goldcard if you keep installing OSPL).
DFT v1? Only DFT v3 HSPL for First Generation Phones supports Spark_W ;
With either a stock rom, or stock like rom like the ones I posted above, do a factory reset (Settings=>About=>Factory Reset...), THEN do a full *228 option 1 programming. Test phone calls and texting only then. If you aren't doing a factory reset with the stock rom, not all settings will be reset in the Spark_W's programing (which could possible cause a texting issue).
Also, is the phone stuck with a 1X indicator?
All the radios are original radios. The NoDo radio is the one that shipped with the 1.3 RUU. If you are running the 1.3 stock like rom, flash the NoDo radio from my radio thread.
Don't flash any radios for now. Try the factory reset with stock rom (or stock like rom).
New phone may come with a mango 2.x series rom (highly likely it will at least be Mango v1) or newer (maybe 2.4 if its coming from Verizon). You can still downgrade, but downgrade with official 1.3 RUU will also downgrade radio (don't worry about radio off the bat). The key thing is, to test EVERYTHING before doing HSPL on the new phone. Then:
Flash 1.3 official RUU for SPL downgrade.
Install HSPL
Program Phone (it's fine to program the phone even if you install HSPL, so long as you are running a stock or stock like rom! Full unlock is what gives us the pain in the butt time.. I'm still working on isolating that issue!)
Flash custom rom of choice (I'd go with ansar's Tango build for now).
Also, before you send your old phone back, even if the steps I outlined don't work, make sure you flash OSPL via DFT's v3 for First Generation Phones, then flash "RUU_Spark_W_VERIZON_WWE_1.03.605.22_RS0512_2K_4K_h ybrid_new_partition_RELEASE," and run a FULL Zune update to current software! This should fix any bootloader stuff that Verizon and/or HTC might detect.
It could very well be that you do have some bad hardware, but make sure you cover your butt by going back to OSPL and updating via Zune. If you flash a newer stock rom, you might half brick the bootloader and not be able to flash anything (that requires a GoldCard to fix).
Hope the newer phone works better when you do get it, but yeah, you can still try to fix it using the reset setups I outlined above.
Now, if you get an error trying to place a call that says "Sorry, we could not authenticate your phone, please call blah blah blah..." even after flashing stock rom and a factory reset and programing with *228 option 1, log into your My Verizon account, and switch the phone on the plan to another compatible phone, then switch it back to the Spark_W. I somehow think that you aren't having this issue so you can ignore this unless you are getting this error.
Click to expand...
Click to collapse
dude you rock thanks for all that.
with my new trophy here is what im running:
8773.98 - DFT v5 - with broken Wifi Internet sharing, arg... not that I really need it..
radio is 1.53.00.02.15_23.17w.05.13u
hspl 1.3
Sound optimal? it seems to run pretty good. Battery life seem better than ever, phone seems to lag sometimes, but that might just be tango. Do you think its worth using ansar's Tango rom at this point? I'm going to reset soon to change my Live ID to a @outlook
if so, what would be the process for getting that rom on from here? just flash right?
'sup guys
I'm attempting to give this HD2 another chance (my dad dumped it for something else, claiming the battery's bad, I fixed that in the mean time) and wish to run android on it.
These forums being great resources for information, I pretty much started right away. But yeah I've gotten myself into a little problem here...
I've lost USB connectivity (won't even show up in the bootloader, 'Serial' is there to stay) after flashing a new radio with CustomRUU.
Device: HTC HD2 (LEO512) - WP 6.5
HSPL: 2.08.HSPL
Radio: Leo_RADIO_2.15.50.14 (well, not sure if that even worked out well, I was trying to get that installed. The radio version on boot didn't change to 2.15...)
was planning to:
Bootloader: MAGLDR v1.13
Recovery: ClockworkMod Recovery 5.0.2.6
NexusHD2 JB 4.1.2 -> NAND installation
checks done:
usb cable: works fine, phone still charges and the LED still turns on (green)
tried connecting to another computer, but no drivers were found to use the device. There was also a mention of 'Generic RNDIS'
I've tried rebooting, didn't help (didn't expect it to)
lost connection with the WP device center during changes made by customRUU.
have I looked around on the forums? Yeah, quite a lot, but the words 'no connectivity USB bootloader no recognition' in any kind of sentence resulted in the 'project' threads for the radios and flashing services being on top of the results every single time...
factory resetting didn't solve anything
feeling where it went wrong: RUU told me I had an outdated rom (3.whateverblabla), what kind of rom? No idea, but I thought I'd let it update, but I now regret doing that since something might be in bad shape.
Connectivity was lost after the rom update. I could still use WP6.5 if there isn't a fix (no problem running it/booting/...), but I'd love to get android running on this device!
~EDIT: I believe I forgot to go into bootloader when running RUU... :/
Would be really great to hear from you! I haven't looked into the possibilities with SD's, but I've got a 1Gb microSD if you want to fix stuff by using an SD. Thanks in advance
ps: if there's a way to undo the current 'extra' non-WP installations, like a simple reset, that's just fine. I'd rather start over again anyway (;