Related
after my phone rebooted once the update was complete, it wont get passed the "at&T World Phone" white screen... SOMEONE PLEASE HELP ME!!!! i was using a stock at&t pure with the stock rom. i can not upgrade hardspl or ANYTHING any suggestions on how to get my phone to boot? hard-reset went through with no signs of failure but it still will not boot up after that finishes... sorry if its something im overlQQKing, but i just cant figure it out. n yes i have researched although obviously not enough at this point. Thanks to anyone who can help in advance. forgive my stupidity!!!
......
noone?????
The HTC Pure updates hosed my phone too, I had already applied hard-spl to my Pure and i've flashed it with dozens of roms. Since I was currently using one of the "Stock" AT&T roms posted on XDA I figured I could apply the updates. Unfortunately after applying the update my phone froze at the boot loader. I was forced to flash my rom using the memory card method and then restore a backup.
you could try putting the phone in SSPL mode manually, (reset button+volume down), the run hard-spl hard-spl in manual mode.
you can then flash your rom using the memory card method. (FAT32 formated memory card, rom file renamed to topaz.nbh copied to root of flash card, reset button+volume down to enter SSPL, power button to confirm flash).
All this assumes you've already tried to hard reset your Pure (reset button+vol up+vol down)
Thanks for the reply! Unfortunatly, i tried the manual method and after it hanging at 0% for about 5 minutes, i keep getting error [262] update error.. (communications error) is this becuase i can not sync with mobile device center (win7)? I really dont want to just have to toss the phone! I have had an at&t tilt, at&t fuze, and now the at&t pure, and this is the only phone i have had this problem with for some reason...
Try Unplugging Your Pure From the computer Take Out the Battery Put the Battery Back in Mean While Restart your computer and Press Power And Volume Down At the Same time on your Pure If its on the colored screen your good,..Make sure your system is online and your not downloading anything and plug in your Pure to the computer it give it about 2 minutes to download the HTC USB driver then once its done your phone will say USB on the bottom of the Red Green Blue And White four color screen Then open up one of your ROM's and Flash it,....Do You Have Windows Mobile Device Center Installed?
If Not here is the Link
http://www.microsoft.com/windowsmobile/en-us/downloads/microsoft/device-center-download.mspx
If you do already you need to uninstall the Driver update for windows mobile media center then install it again .
i can get the bootloader screen just fine! i just can not get hardspl to flash onto it. it sits at 0% every time. the phone will not boot so i can NOT get into mobile device center. The tri-colored screen comes up with no problem and it says USB on the bottom, so the drivers are already installed. I even tried hard-reset and still no luck
There was an additional cab file I needed to install to HSPL the Pure
"enablerapinew.cab"
basically the machine just would fail to load the HSPL without it
but it still functioned afterwards, does yours?
Do a search on XDA find and DL the cab (or I could attach a zipped copy)
If you can still access the device,
just copy enablerapinew.cab to any temp dir on the device
the execute it through fileexplorer
then go back to installing the HSPL (mine then worked fine)
If you haven't already, You should go to
http://forum.xda-developers.com/showthread.php?t=520312
you'll find troubleshooting info and a link to the extra cab there
If you really are bricked at this point , it sounds like nothing has actually
been changed on your device yet? its just frozen should be still under warrentee? Unless anyone else has a better suggestion you should be
able to return it for exchange to ATT
Good Luck
KJL
It sounds like Windows is not properly recognizing your device when it is plugged into the USB port while in SSPL mode.
Have you tried different ports?
Is there another computer you can use?
another thought about returning under warranty
on the boot page of the stock Pure it indicates HSPL 1.83.000
After you update the HSPL it will say HSPL "1.83.Olinex"
this normally an indication of a successful update,
but it will probably void your warranty if they just look at the boot screen
This is true for all Pure (and Tmobile Compact V) Rom upgrades
The Stock Pure came with 6.5 and therefore the 1.83.00 HSPL
The Diamond2s did not, so their solution which reverts to 1.63 <?>
will not correctly revert to 1.83.00 on the Pure.
No way to correct this yet as far as I know,?
All the "reverts" are geared toward the Diamond2s, not the Pure.
But If your boot screen indicates 1.83.00 before it freezes
I'm fairly sure its still entitled to a warranty repair/replace
How could they tell the cause of the failure
was a reburn as opposed to natural causes?
Good Luck
KJL
When you put the phone into a manual bootloader mode... Mobile Device Center becomes obsolete.
HardSPL is only needed for unofficial roms. Forget HardSPL for the time being. The goal here is to get your phone operational. Just download the official HTC WM6.5 WWE rom and flash that. Put phone in manual bootloader mode and run the Rom installer.
As long as your phone is in bootloader mode and says "USB"... then your set to go.
Another solution is to try another PC. You'd be surprised how often that will resolve your issues. Perhaps find an XP machine and install Activesync (so it loads the bootloader USB drivers). I had to do that on several occasions when my main PC refused to flash my mobile device.
I did both of the updates htc has for the pure. Both worked fine. I am on the origianal rom. It does reboot your phone and stays on the white screen for a min then it loads the update and the phone starts.
The offical ROM comes back with a wrong vender ID error I guess cause its a "pure" and not the HTC branded "topaz"... NOW what should i do??? Seems like i NEED hardspl so i can flash any ROM, as from what i researched, there IS NO AT&T Pure rom that has been released. I still cant figure out why a hard-reset will not work though.... This is REALLY starting to get me angry!!!
Just for reference, the Pure's ID is TOPA210 32M
SPL-1.83.0000
The official hotfixes worked fine for me as well. Did you apply the hotfixes on the original ROM that came with your Pure?
Also, does the official HTC Touch Diamond 2 ROM work for you? If so, the hotfixes for the Pure are irrelevant, as are any future updates released for the Pure. You should look for updates for the Touch Diamond 2 on the Worldwide HTC site.
If you needed to do a warranty claim, the closest you can get to returning your phone to stock/shipped form is to use the ROM dump using HardSPL and hope they don't notice that the SPL is different. Currently, there's no way to return the Pure back to completely official software.
A hard reset simply wipes everything off and restores everything back to what is contained in just the ROM you currently have on it. If you've flashed your phone at all, you've already wiped out the original ROM that came with it.
It is still the STOCK ROM. I have never flashed it yet.. The topaz rom will not flash due to a vender ID error. The spl is still stock also... i think thats is why i am having this problem. I bought the phone off craigslist so returning it to AT&T is NOT an option either way. My only solution is to find a fix. (or trash it) I really appreciate all of your suggestions and input so far. You guys are by far the best board around! I am a LONG time follower, but a few-time poster. Obviously i have little to contribute to the board.
Can I trouble you to dig up a few version numbers? It'd help evaluate your situation so we can see which options are best for your case.
ROM version? You can find this in Device Information. Start --> Settings --> System --> Device Information
Bootloader version? Do a soft reset while holding down the volume down button on the side until a screen with red, green, blue, and white, ordered top to bottom, shows up. It should be the second line starting with "SPL-..."
The ROM is the STOCK AT&T ROM (again...) I CAN NOT go to start;.... because if you noticed in the first post, the phone will not boot past the white "AT&T WorldPhone" screen... the spl is stock also incase you missed that part. (1.33.0000) I have never flashed the divice. EVERYTHING IS HOW AT&T SELLS THE PURE OUT OF THE BOX! NO MODS. NO FLASHED ROMS. NO HardSPL... NOTHING! STOCK!!! (for those overlooking the details in my previous posts) I have no doubt you guys (n hopefully a few girls ) will help me fix my issue. I'm just REALLY anxious for it to happen sooner than later!
Have you tried downloading the official rom here on xda and renaming it to TOPAIMG.nbh and update using the sd card method?
Here is the thread:
http://forum.xda-developers.com/showthread.php?t=600339
The download is in post #1
I have downloaded the official ROM. Although I thought it is still concidered "custom" and that you need spl updated to install it... Am I wrong about this? Also, by using the SDcard to flash, do I NEED to have hardspl on the device? If yes, I can not use this method, as I have stated before that the spl is still stock and NOT updated in any kind of way. NOTHING on the phone has been updated or flashed. Will this method still work then???? I am at work for 3 more hours and then will go home and try it either way and come back to update you all on the results. Again, THANK YOU for your continued support in helping me out!! At this point, I will send a donation via paypal to whoever can get me out of this hole!
jromeo350 said:
I have downloaded the official ROM. Although I thought it is still concidered "custom" and that you need spl updated to install it... Am I wrong about this? Also, by using the SDcard to flash, do I NEED to have hardspl on the device? If yes, I can not use this method, as I have stated before that the spl is still stock and NOT updated in any kind of way. NOTHING on the phone has been updated or flashed. Will this method still work then???? I am at work for 3 more hours and then will go home and try it either way and come back to update you all on the results. Again, THANK YOU for your continued support in helping me out!! At this point, I will send a donation via paypal to whoever can get me out of this hole!
Click to expand...
Click to collapse
You can flash hard SPL the same way by renaming the .nbh file to
TOPAIMG.nbh
jromeo350 said:
I have downloaded the official ROM. Although I thought it is still concidered "custom" and that you need spl updated to install it... Am I wrong about this? Also, by using the SDcard to flash, do I NEED to have hardspl on the device? If yes, I can not use this method, as I have stated before that the spl is still stock and NOT updated in any kind of way. NOTHING on the phone has been updated or flashed. Will this method still work then???? I am at work for 3 more hours and then will go home and try it either way and come back to update you all on the results. Again, THANK YOU for your continued support in helping me out!! At this point, I will send a donation via paypal to whoever can get me out of this hole!
Click to expand...
Click to collapse
Actually that is supposed to be an officially signed rom. If that is true it will work with the stock spl. It will either work or it won't. Also, as stated in the response after yours, you can apply the hardspl via SD as well.
Okay this is what happen I had files in my SD card and there was this exe file that i downloaded onto the phone it rebooted and then it stays stuck on the tmobile slpash stick together screen. Tried downloaded a different ROM to the phone but still wont work. I dont know what else to do? Should i return it back to Tmo US and what should i say? Can anyone please help.
Never mind iI fixed it thank you all for your help.... Great Community
You take it back and tell them pretty much that after reboot it simply got stuck... They have lot more capabilities of fixing it quickly then you with replacing ROMs, etc.
i dowloaded the spl 1024 can i go back to tmo regular rom US
eenbox said:
You take it back and tell them pretty much that after reboot it simply got stuck... They have lot more capabilities of fixing it quickly then you with replacing ROMs, etc.
Click to expand...
Click to collapse
jgu71424 said:
Okay this is what happen I had files in my SD card and there was this exe file that i downloaded onto the phone it rebooted and then it stays stuck on the tmobile slpash stick together screen. Tried downloaded a different ROM to the phone but still wont work. I dont know what else to do? Should i return it back to Tmo US and what should i say? Can anyone please help.
Click to expand...
Click to collapse
1. Did you flash HSPL ?
2. Are you a new in flashing ROMs
Turn mobile off, turn it on with volume key down. Connect phone to PC using USB cable (word : `serial` changes to `USB`), flash HSPL (if you didn`t flash it already), flash stock ROM or custom ROM (some custom ROMs require to flash radio first).
Kris
EDIT :
Sorry didn`t see some first answers. If you didn`t mess around SPL, you didn`t loose your warranty .. I would take it back to the store. If you changed SPL you can still reverse it and than take it to the store. If you don`t want to, you can follow procedure above (at your own risk).
Yes i did flash HSPL 1024 for Tmmo US and had a custom ROM on it. And sort of yes. Do you know where i could get the stock rom so it could back to tmo and i could return it and tell them after leaving it overnight charging with the phone completly off and turning it on in the morning it stayed at the tmo screen. Lets see what they say. But can you or someone give me the stock rom
kregowski said:
1. Did you flash HSPL ?
2. Are you a new in flashing ROMs
Turn mobile off, turn it on with volume key down. Connect phone to PC using USB cable (word : `serial` changes to `USB`), flash HSPL (if you didn`t flash it already), flash stock ROM or custom ROM (some custom ROMs require to flash radio first).
Kris
Click to expand...
Click to collapse
try this
http://forum.xda-developers.com/showthread.php?t=609477
Link for TMO US HSPL is down? hope it comes out soon.
kregowski said:
try this
http://forum.xda-developers.com/showthread.php?t=609477
Click to expand...
Click to collapse
Hey so i just picked up an hd2 on craigslist. when the seller handed my the phone he showed me the phone working and then did a hard reset so i thought nothing of it and took the phone while it was resetting. then while waiting for it to boot i noticed it was taking quite a while so i took out the battery and let it reboot, it turned on then froze on the homescreen. i've tried several hard resets and have gotten the phone to the point where it works but only after putting in a removing the battery several times and the phone sticking on the "stick together" logo. I was going to try to do the newest tmobile update on the phone using the one available on their website but now i have an issue plugging the phone into the computer or wall adapter as it will make the phone freeze and ill have to go back through my removing the battery 5 times process. is this some sort of common issue with a common fix or should i take the phone to tmobile or htc and see what they can do for me. i dont have a receipt as a purchased the phone on craigslist so im not sure tmobile will do anything for me.
Edit: i can now connect my phone to the pc i'm trying to update to 2.13.531.1 but i got to 8% but the update froze there and the phone currently has no image version. I'm using windows 7 ultimate and ive tried to run as administrator and with xp service pack 3 compatibility.
thatg said:
Hey so i just picked up an hd2 on craigslist. when the seller handed my the phone he showed me the phone working and then did a hard reset so i thought nothing of it and took the phone while it was resetting. then while waiting for it to boot i noticed it was taking quite a while so i took out the battery and let it reboot, it turned on then froze on the homescreen. i've tried several hard resets and have gotten the phone to the point where it works but only after putting in a removing the battery several times and the phone sticking on the "stick together" logo. I was going to try to do the newest tmobile update on the phone using the one available on their website but now i have an issue plugging the phone into the computer or wall adapter as it will make the phone freeze and ill have to go back through my removing the battery 5 times process. is this some sort of common issue with a common fix or should i take the phone to tmobile or htc and see what they can do for me. i dont have a receipt as a purchased the phone on craigslist so im not sure tmobile will do anything for me.
Click to expand...
Click to collapse
I would put the phone in boot load manually by holding the volume down button while turning it on, and remove the memory card and then reflash the tmobile rom
can someone also help me figure out how to get the ruu.nbh file off this rom and how big it should be so i can try to flash it from the sd card. thanks
http://forum.xda-developers.com/showthread.php?t=681030
zelendel said:
I would put the phone in boot load manually by holding the volume down button while turning it on, and remove the memory card and then reflash the tmobile rom
Click to expand...
Click to collapse
i found a .nbh file on my computer that was 4mb and renamed it leoimg.nbh then tried putting it on a freshly formatted fat 32 micro sd car and went into bootloader mode but the phone gives me an upgrade error, asks me to try again and just goes to a white "loading..." screen now the phone is stuck here. its like the newest issue is the one im stuck with. now i cant get the phone to sync with the computer or run the .exe to recognize the phone
thatg said:
i found a .nbh file on my computer that was 4mb and renamed it leoimg.nbh then tried putting it on a freshly formatted fat 32 micro sd car and went into bootloader mode but the phone gives me an upgrade error, asks me to try again and just goes to a white "loading..." screen now the phone is stuck here. its like the newest issue is the one im stuck with. now i cant get the phone to sync with the computer or run the .exe to recognize the phone
Click to expand...
Click to collapse
What error did it give you? Found an nbh file? was it from a stock rom? Do you have Hard SPL on it? If it doesnt have HSPL on it then you will only be able to load a stock rom
zelendel said:
I would put the phone in boot load manually by holding the volume down button while turning it on, and remove the memory card and then reflash the tmobile rom
Click to expand...
Click to collapse
+1 or flash the phone then task 29 it.
Sent from my HTC Desire using XDA App
zelendel said:
What error did it give you? Found an nbh file? was it from a stock rom? Do you have Hard SPL on it? If it doesnt have HSPL on it then you will only be able to load a stock rom
Click to expand...
Click to collapse
no i have not run hard spl so i can only install a stock rom a suppose. the exe gets stuck at 8%, i have no idea where the right nbh file is. i read somewhere when you run the exe it installs the nbh in a temp folder but im not sure i found the right one. ive also downloaded task29 and tried to run as admin but it doesnt do anything just goes to the htc install screen and stays at 0% Getting frustrating it was working fine actually before i tried to install the new tmobile software update. ive read that task29 gets rid of extra leftovers of other roms and might help the exe finish up on the phone and get past that 8% wall but it doesnt seem to be working for me
right click the stock exe file choose extract here, will give 9 or so files, one of them is about 200meg and is called ruu_signed.nbh that's the file you want.
randomly flashing nbh files that you don't know what they are, that's about the stupidest thing you can do...... you deserve a brick for being an idiot.
samsamuel said:
right click the stock exe file choose extract here, will give 9 or so files, one of them is about 200meg and is called ruu_signed.nbh that's the file you want.
randomly flashing nbh files that you don't know what they are, that's about the stupidest thing you can do...... you deserve a brick for being an idiot.
Click to expand...
Click to collapse
lol thank you for the words of encouragement, so i've extracted the .nbh file its 268mb, renamed it to leoimg.nbh tried the update from the sd card and it fails at the radio says, update terminated, update FAIL. any idea where to go from here?
Edit: i've run hspl3 on the phone is boot loader mode and have also run task29 from doloop but still get the same error with the tmobile file. 8% using the exe and FAIL trying to flash from the sd card
heh you're welcome. (i was harsh to make the point,,, if you found a random bottle of liquid that said petrol on it, you wouldn't put it in your car till you were sure it was petrol, right?)
as to why it failed, i'm not sure, i think i'd probably hspl3, choose 2.08.hspl, then try flash a radio on its own (see the tmous radio thread) because it could be a bad radio.
just please confirm the exact filename of the .exe you extracted ruu_signed from?
samsamuel said:
heh you're welcome. (i was harsh to make the point,,, if you found a random bottle of liquid that said petrol on it, you wouldn't put it in your car till you were sure it was petrol, right?)
as to why it failed, i'm not sure, i think i'd probably hspl3, choose 2.08.hspl, then try flash a radio on its own (see the tmous radio thread) because it could be a bad radio.
just please confirm the exact filename of the .exe you extracted ruu_signed from?
Click to expand...
Click to collapse
The first exe file, which got to 8 percent then went red and failed was
T-Mobile_HD2_MR_Software_2.13.531.1
After hspl3 and using task29 i tried flashing this exe which gets to 99% and fails
RUU_Leo_1_5_TMOUS_2.02.531.MASD_S__Radio_Signed_15.29.50.07U_2.06.50.04_TeleNav-5.5.42
that second one, did you flash from sd card? cos its a manufacturing test rom, and if so then you may now be stuck with a test spl of 2.02, and if so things just got a heap worse,,,
go into bootloader and tell me what it says next to spl
samsamuel said:
that second one, did you flash from sd card? cos its a manufacturing test rom, and if so then you may now be stuck with a test spl of 2.02, and if so things just got a heap worse,,,
go into bootloader and tell me what it says next to spl
Click to expand...
Click to collapse
i tried flashing using the .exe method in bootloader mode. next to spl it reads -2.08.hspl 8g XE
it now says
Upgrade ROM code error
ah ok, good.
so, it seems to be the radio causing the error, so since you have hspl installed, why not try a custom rom? they don't include a radio, so it may bypass the problem.
samsamuel said:
ah ok, good.
so, it seems to be the radio causing the error, so since you have hspl installed, why not try a custom rom? they don't include a radio, so it may bypass the problem.
Click to expand...
Click to collapse
Which do you suggest, i bought the phone so that i could ultimately install android on it. but it seems i'd be lucky to even have wm running on the thing
Edit. just tried kumars classic rom, renamed to leoimg tried running off the sd card, The update finishes successfully but after i hit the reset button on the back of the phone i just see the tmobile stick together logo and the phone doesnt boot. Do a lot of people struggle with the hd2s or do i just have a bad example here?
well unfortunately i think you may have a dud. its the radio that is preventing it from booting.
it could be the radio from that test rom, it could be something else (but still the radio)
options...
its still under warranty, speak to t mobile and/or htc, but don't mention flashing and be sure to remove hspl if you do send it back. (run hspl3, choose 2.08.0000, that's stock)
or
look on here for a user called xmoo, he knows a lot about this sort of problem, (im just good with regular flashing issues)
im having the same issue so if you believe its the radio will installing different radio maybe fix the problem?
i;ve tried installing a new radio from the sd card. it goes red and fails
It sounds like a hardware issue at this point. I'm willing to bet you fried something when you pulled the battery in the middle of the master reset.
Hope thats something htc will cover. Phones on its way over
Ok, guys I REALLY NEED HELP WITH MY TMOUS HD2.
I currently have HSPL 2.08 but everytime i go into the bootloader and install a WinMo 6.5 Rom it gets stucked at 8% percent for awhile then goes to 100. After i installed it, it gets stuck on T-Mobile, Stick Together screen with the R G B thing on the bottom.
I had NAND on my HD2 but it keeps freezing in every rom anytime I use data connection, recieve calls, or use browser or anything that uses the Data Or T-Mobile Connection. So i decide to reflash everything starting with Radio, and I recently installed Radio 2.15 something like that in A radio thread somewhere on the forums. I chose that one because im assuming it's the newest one. I flashed it, and removed MAGLDR, and etc. I currently tried using Task29 and flashed stock 2.08 radio but had the same problems. I CANNOT FLASH ANY ROMS. I TRIED REFLASHING MAGLDR AND CWM AND I CANT GET INTO RECOVERY I GET A FATAL ERROR1. Should return the HD2 to T-Mobile? They don't sell the HD2 anymore so i assume HTC will have to give me one. I'm currently deciding the only choice i have is to return my HD2 to T-Mobile. I flashed SPL 2.08 so it's back to stock. I cannot install or load any roms without it being stuck in the T-Mobile screen. Any help? Or i just have to replace it with a new one?
blahblah13233 said:
Ok, guys I REALLY NEED HELP WITH MY TMOUS HD2.
I currently have HSPL 2.08 but everytime i go into the bootloader and install a WinMo 6.5 Rom it gets stucked at 8% percent for awhile then goes to 100. After i installed it, it gets stuck on T-Mobile, Stick Together screen with the R G B thing on the bottom.
I had NAND on my HD2 but it keeps freezing in every rom anytime I use data connection, recieve calls, or use browser or anything that uses the Data Or T-Mobile Connection. So i decide to reflash everything starting with Radio, and I recently installed Radio 2.15 something like that in A radio thread somewhere on the forums. I chose that one because im assuming it's the newest one. I flashed it, and removed MAGLDR, and etc. I currently tried using Task29 and flashed stock 2.08 radio but had the same problems. I CANNOT FLASH ANY ROMS. I TRIED REFLASHING MAGLDR AND CWM AND I CANT GET INTO RECOVERY I GET A FATAL ERROR1. Should return the HD2 to T-Mobile? They don't sell the HD2 anymore so i assume HTC will have to give me one. I'm currently deciding the only choice i have is to return my HD2 to T-Mobile. I flashed SPL 2.08 so it's back to stock. I cannot install or load any roms without it being stuck in the T-Mobile screen. Any help? Or i just have to replace it with a new one?
Click to expand...
Click to collapse
your phone is currently out of warranty, do not send it to HTC.
Download the tmobile stock ROM by going to the tmobile website > support and they will aks you for your IMEI and SN, enter it and it will give you a download for the stock ROM.
Download the ROM, then extract the file.
Take the .nbh file and rename it to LEOIMG.NBH
put that on the root of your 8gb or less SD card, pop it in, get into bootloader, and hit the power button when it tells you to.
IF this fails it sounds like a hardware issue.
Put your phone in a plastic bag and stick it in th fridge for 10 minutes, take it out and reflash as above, after flash call HTC on a warranty claim because your phone will be stock and hence back in warranty.
I've tried that, i only have a 16gb sd card and it works, but it gets stuck in the stick together crap. D:
seems to be cropping up every few days lately, this problem, though it's always been around. 'stuck radio', 'spl wont change ' 'flash fails at 8/9/10%' and variants thereof, , android gives fatal hit, nothing sticks when flashed, and teh phone never gets past teh rgd screen (cos the radio is shafted)
so i cant send it to htc? then wtf..?
blahblah13233 said:
so i cant send it to htc? then wtf..?
Click to expand...
Click to collapse
Well from reading this thread I agree with samsamuel, it sounds like you are having a hardware problem as most of the HD2's that people have that show the symptoms Sam mentioned can not be fixed with software solutions. Bu there is the occasional anomaly that someone manages to bring back to life but even m,ost of them eventually completely get "stuck" and then they are useless.
As for what to do. You can take it or send it somewhere to replace the mainboard for you. Or just buy another HD2. That is it short and sweet.
so whats the update blahblah 13233?
Thanks guys with all the help possible, I went to a T-Mobile store and asked for a replacement, it should be coming in 2 days. I had to pay 5$ Shipping. So when I get my new phone I gotta give my old phone in some container or whatever and mail it to htc or give it to any T-Mobile store Thanks guys with giving me ideas. The people at T-Mobile said it's a hardware problem like the guy stated above. Oh well, I hope it doesn't happen again.
(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?