Related
!!!
I just tried to do the 3.16 update via dcd's instructions and now I see this, frozen at the sprint splashscreen. I tried a hardreset
I got until step 3 -- Flash new ROM, it went through no problems
WHAT TO DO!?
PLEASEe HELP <3 thanks in advance!
read..why flash a rom if you cant read?!
if i remember correctly, it is because dcd's rom doesnt include the new sprint radio.
either flash the sprint radio by itself, or flash the unofficial sprint rom followed by whatever ya want after that
of course it's gonna be a pita since you didnt do your research beforehand. tsk..tsk...
SOLUTION
Actually I think you did everything right...
... you just overlooked the same thing that I did ...
The instructions are a bit vague on one thing (for those of us who haven't done much rom flashing before)
You must load the new radio BEFORE your new rom will even boot!
----------that is why you are hanging on the yellow Sprint boot screen------------
1. This means you need to go back into "boot loader mode" (hold power and camera and reset with stylus)
2. Then run titan_radio_3.27.00.exe while your phone is hooked up via USB)
After that finishes you should be rockin with the rest of us!
I just got my new HTC HD and I used USPL and flashed Dutty's newest ROM according teo the instructions here: http://forum.xda-developers.com/showthread.php?p=3638336#post3638336
In step 6e it says "Turn off your phone. I personally do it right after flashing completes and I see the "Smart Mobility" screen. I just yank the battery out instead of waiting for it to boot up all the way and go through customization process just to hard reset ". Well, I did that but when I was pulling the battery out teh graphics on the screen whent all screwy. Now teh graphics are corrupted. I've hard reset and it changed nothing. Did I screw up my phone permanently?
[Update]
OK, I flashed the RUU_BlackStone_HKCSL_WWE_1.57.831.1_Radio_52.64.25.34_1.14.25.24_Ship.exe ROM adn the phone is back to normal. I guess that measn I did something wrong in flashing Dutty's ROM earlier. I will try again tonight and see what happens.
Hi Roger
I am not an expert in this area but if you should have ensured 2 steps beforehand:
Firstly updated the stock ROM to that provided by HTC to 1.56
Secondly, then used the HardSPL program to allow yourself to use cooked 1.56 ROMS going forward.
Can you still get bootloader up? This is done by switching the phone off (you should get a warning sign about data being lost) and then switching back on again pressing the down button.
If you can then there are instructions on how to get yourself out of your current predicament.
Hope this helps.
Kaid
Hi,
Thanks for the advice. I put on the stock 1.56 (which my phone had never had on it before) and then updated to the cooked rom and everything is fine. I thought I could skip the step with the stock 1.56 rom because I thought I read that somewhere on here but obviously that wasn't the case.
Roger
Hello,
I have a problem with my G1.
I got my G1 maybe a month ago. It had firmware 1.1 and radio module 1.22.12.29. Back then I did not realize it was a radio image compatible with firmware 1.0 as far as I gather from the HTC website.
At first, I did not intend to root it at all, a decision later I would regret. Well, it worked OK, only it was not updated. I was told I would receive the update over-the-air in 4 days. At first they said it would be to 1.5, but it turned out my operator started to upgrade straight to 1.6.
And so I did receive it in 4 days and the problems began.
Basically, the voice quality is so bad that half of what I say is ununderstandable. My voice sounds metalic and I cannot have a coherent conversation over the phone. It is a business phone, so you can imagine it is rather annoying when I have to struggle to be understood by clients.
Ok, so I checked the bootloader for the radio image version and I found out it was still version 1.22.12.29. As per the HTC website I should have 2.22.19.26I. So, obviously the radio firmware was not updated as it should be as per the HTC website. Thus, it seems the reason voice quality is so poor is the outdated radio firmware.
Since I did not plan to return my new phone to my operator (I had no time for it), I decided to root the phone and update the radio firmware myself. It seemed simple enough and I use Unix and Linux since 15 years, so it seemed it would pose no problem.
Quickly I learned that rooting 1.6 is not so simple. One-click method fails. Only goldcard worked and after a few days of struggle I finally got back to firmware RC7 and rooted the device.
Right after I updated the recovery image to CM 1.4, but before I flashed the CM ROM I attempted to update the radio firmware as was suggested by one tutorial I followed as well as the CM website.
Well, it all went smooth. After the update I pressed Home and Back, it rebooted, back to recovery CM1.4, one more time Home and Back and I was back to the working phone. I checked the radio firmware and lo and behold, it was still version 1.22.12.29. No errors, nothing, smooth update process and no result. I repeated it at least 5 times to no avail.
I decided to install CM 4.2.7.1 ROM and try to update the radio then. Before the CM ROM I updated the SPL to HardSPL with success to have fastboot and went to install CM. It went smooth and I booted into this new rooted G1 ROM with ease.
Again, I attempted to update the radio firmware from recovery CM1.4 and again no results.
So, I am back to square one. I have again firmware 1.6 only from CM instead of stock HTC, and I cannot use this phone for calling.
So, summarizing, I got the phone with firmware 1.1, but radio firmware from 1.0. Why it was not updated together with the system I do not know. Then I got an update to 1.6 and the radio firmware also did not upgrade. Then I went back to RC7 (firmware 1.0), rooted the phone, attempted the radio firmware update before installing CM ROM and failed. And finally, I installed HardSPL + HTC 1.6 recovery (as suggested on the CM website) + CM ROM and again failed to update the radio firmware to 2.22.19.26I. The update process is going without any errors. Verification, extracting, installation of radio image all go OK, the phone reboots but no radio updated.
Anybody any idea why it is like this? Why this phone refuses to update the radio from HTC website.
Any suggestions?
Oliwer
PS. One more thing, I was contemplating updating the radio via fastboot, but it seems after reading HTC website that fastboot is only for system and recovery image flashing. The radio has to go first adn from recovery console. Am I right on this?
I too have a problem updating to the 26i version. however i rooted at 1.5 using the one click root method and ive since switched from cyan 1.4 recovery and cyan roms to amon recovery and dwang roms. No matter which recovery i use, the 26 update flashes without an error but shows up as the same radio ive had all along (1.22.14.11) i made a thread about it but noone seems to have an answer. Sorry I couldnt help, but at least bumped up your thread and maybe someone can help us.
speedysilwady said:
I too have a problem updating to the 26i version. however i rooted at 1.5 using the one click root method and ive since switched from cyan 1.4 recovery and cyan roms to amon recovery and dwang roms. No matter which recovery i use, the 26 update flashes without an error but shows up as the same radio ive had all along (1.22.14.11) i made a thread about it but noone seems to have an answer. Sorry I couldnt help, but at least bumped up your thread and maybe someone can help us.
Click to expand...
Click to collapse
Thanks for sharing!
At least I know I am not alone here with this problem.
Since it's Christmas and I have some more time, I decided to do a Nandroid backup and wipe my phone back to the original rom with 1.0 firmware (RC7).
I used my goldcard and I flashed it in a few minutes. I logged back into 1.0 firmware with the original bootloader and recovery console.
Next I put everything on my goldcard, flashed the recovery CM1.4 from the terminal, went to the bootloader, flashed update.zip with the newest radio 2.x from HTC, everything went smooth. Reboot and again NO change of the firmware. Tried a few more times flash the radio and HardSPL together to no avail. I restored my backup and found myself back to square one.
One think I noticed, and I wonder if you get the same, is that when I flash the radio, the phone reboots back to the recovery console and shows "Formating Cache..." message. It does not tell me anything like Please reboot, just this message. Meanwhile I can move the cursor up and down the recovery menu, so the phone has not hang up. It just sits at the recovery until I reboot it. Once I waited 30 minutes to see if it reboots itself and it does not. So, I press Home+Back and then it reboots fully and after loging in I check the radio and NO change.
So, I wonder if your phone does the same?
Oliwer
PS.
T-Mobile G1 - w/ ROOT
DREA110 PVT 32B
HardSPL 10.95.3000
Recovery image: HTC Android 1.6 (from HTC website)
Class IV 8GB SD Card w/ Ext 4 Partition and Swap partition
That's a huge wall of text, and it's Christmas so I'm a little merry
When flashing the radio image w/ Cy's recovery you must flash as an update.zip using alt-s, press whatever key you need to press to confirm and reboot using home+back. If you use flash any zip or use the trackball to reboot the radio image (or SPL) will not reboot in the required way to complete installation.
AdrianK said:
When flashing the radio image w/ Cy's recovery you must flash as an update.zip using alt-s, press whatever key you need to press to confirm and reboot using home+back. If you use flash any zip or use the trackball to reboot the radio image (or SPL) will not reboot in the required way to complete installation.
Click to expand...
Click to collapse
I tried all possible ways. Just a few minutes ago I went to CM1.4 recovery, used the update from update.zip, pressed Home+Back, rebooted back to recovery console, pressed Home+Back again, booted to CM4.2.10, punched the PIN code, checked the About Phone section and I am still with 1.22.x radio firmware.
This phone simply refuses to update the firmware in any known way.
So, my plan now is to un-root it back to the state I got it 2 months ago and return it to the operator and request upgrade of radio, since Donut with an old radio is basically useless. People simply do not understand half of what I say even if I speak slowly and quietly.
Cheers,
Oliwer
You have to press
Cam+power and it will show radio
....
In settings that radio has nothing to do with one installed...Do you know that the radio does?
It allows custom roms like cyan to be installed while keeping root access. The rom allows some tmo apps like account to still be used here in the states.
yes oliwer i get the same formatting cache message but nothing else happens. i tried in cyans recovery and amons recovery using only button shortcuts and not the trackball. i always named the radio update.zip, but still no luck. Im not sure if the 26i radio requires a certain version before it can upgrade, like maybe i have to upgrade to another radio before i can get to 26i? im not quite sure...ive run out of ideas on what to do. I dont have a warranty or anything on my g1. does the fact im using a donut rom on a cupcake radio have anything to do with it? if i had a cupcake rom and upgraded the radio to 26i from there would it work? i know these might sound like dumb ideas but im still relatively new to the scene and im running out of ideas as to why this is happening or why i cant solve it..
bump? anyone have a solution for us? or advice?
i just realized that i had android 1.1 with the 1.22.14.11 radio when i first got my phone, when t-mobile gave me the 1.5 update, i was still stuck on the same radio for some reason. After that I used the one click method to root and ive been on dwang donut rom ever since with the same dated radio...Ive tried using cyans recovery to flash and still no luck, no error, it says its updated but when i check the baseband or stock spl its still the same radio. I never went for a danger spl when i rooted because i was afraid to brick so i cant fastboot a radio update. I asked in another topic if it was possible to use the "flash_image" command in terminal to flash the radio but i dnt think itll work and i dont wanna risk it. If anyone has any advice or a possible solution please keep us updated.
Thank you!
Turn your phone off, hold the camera button down, and power on your phone.
What do you see?
each time before and after the flashing of the radio using cyans or amons recovery image id get the same rainbow screen saying
DREA100 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-1.22.14.11
Serial0
so im still stuck on the Android 1.1 radio.
speedysilwady said:
yes oliwer i get the same formatting cache message but nothing else happens. i tried in cyans recovery and amons recovery using only button shortcuts and not the trackball. i always named the radio update.zip, but still no luck. Im not sure if the 26i radio requires a certain version before it can upgrade, like maybe i have to upgrade to another radio before i can get to 26i? im not quite sure...ive run out of ideas on what to do. I dont have a warranty or anything on my g1. does the fact im using a donut rom on a cupcake radio have anything to do with it? if i had a cupcake rom and upgraded the radio to 26i from there would it work? i know these might sound like dumb ideas but im still relatively new to the scene and im running out of ideas as to why this is happening or why i cant solve it..
Click to expand...
Click to collapse
I do not know, really, why the radio refuses to upgrade. Since my last message I have read tons of posts on this issue and nearly ALL people can upgrade the radio firmware easily, just like the SPL. Somehow, I can upgrade the SPL to whatever I want, but not the radio. Very strange indeed and no luck so far.
Oliwer
speedysilwady said:
bump? anyone have a solution for us? or advice?
i just realized that i had android 1.1 with the 1.22.14.11 radio when i first got my phone, when t-mobile gave me the 1.5 update, i was still stuck on the same radio for some reason.
Click to expand...
Click to collapse
Exactly the same in my case. Except they upgraded straight to 1.6. Before the upgrade I have 1.1 firmaware and quality of voice was perfect. After the upgrade things went south.
speedysilwady said:
After that I used the one click method to root and ive been on dwang donut rom ever since with the same dated radio...Ive tried using cyans recovery to flash and still no luck, no error, it says its updated but when i check the baseband or stock spl its still the same radio.
Click to expand...
Click to collapse
Same thing with me.
speedysilwady said:
I never went for a danger spl when i rooted because i was afraid to brick so i cant fastboot a radio update.
Click to expand...
Click to collapse
Well, I installed HardSPL and it worked despite the old radio. HardSPL offers FASTBOOT and I use it at times. This is safe, at least for me.
speedysilwady said:
I asked in another topic if it was possible to use the "flash_image" command in terminal to flash the radio but i dnt think itll work and i dont wanna risk it.
Click to expand...
Click to collapse
Well, I did, but it does not work since flash_image updates partitions and G1 does not have radio partition. So, when you try to update the radio.img it tells you no radio partition. It is only possible for Roger G1 since it has radio partition unlike all other G1s and there you could upgrade the radio with flash_image.
speedysilwady said:
If anyone has any advice or a possible solution please keep us updated.
Thank you!
Click to expand...
Click to collapse
Yeap! I just practised how to un-root the phone straight to 1.6 with the original SPL and recovery and I was able to restore my phone to the state before rooting and I plan to give it back to my operator under warranty and ask to get this radio fixed. I will do it next week. I will report if the authorized service will be able to upgrade the radio.
Oliwer
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.
(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?