This is something I stumbled on by accident. The easiest way to recover lost performance is utilizing HTC's RUU to return your system to completely stock, and then reroot your system and flash whatever version of android you like. If your bootloader is unlocked, you will need to relock it in order to use the RUU. There is no need to flash an HTC recovery or OS, just lock the bootloader. If you want to do the S-Off procedure, you may as well get the oldest RUU you can, and flash that.
Once you're back to stock, and you do want to go for S-Off, you will need to unlock your bootloader and gain root access. What worked for me was flashing a 4.4.3 Android Revolution HD build, and using Rum Runner. What I started off trying to do was to update the firmware for my One. One thing led to another, and 8 hours, a sleepless night, and a pot of coffee later, she was done.
The end result is that battery performance is now increased by 25%, boot times have decreased by 35%, and the general responsiveness of my phone with CM12 nightlies is much improved. She feels like a new phone again, not withstanding the new exterior casing I dropped in while I was it, creating a possibly one of a kind black T-Mobile One with absolutely no FCC or model number b.s. on the back.
Were you on older firmware before? Can't say I've felt performance in my phone dropping, aside from a possible slight decrease in battery time because of age.
With that said, I do find some ROMs bogging my phone down, but a good wipe and reflash seems to do the trick.
if you want to s-off with older Firmware/hboot and you are for example on latest Firmware/hboot ýou can't downgrade without s-off, so you Need s-off if you want to downgrade to older Firmware/hboot, also if you have for example the latest hboot 1.57 or so you won't be able to use an older RUU you should add that to your OP
That is unfortunately a limitation of the process, you are stuck with whatever version of HBOOT you have. But, that is why I recommend going with the oldest RUU available, to avoid upgrading the HBOOT to a newer version that might give you issues. I had no trouble using a 4.2.2 RUU despite having a 1.55 HBOOT, as this was the oldest RUU I could find. Far as I have found, any RUU will work with any HBOOT version. To do S-Off for any version other than 1.57, you can use Rum Runner, though you will need to use Sunshine for 1.57. And yes, I was saddled with an older version of the firmware, though I do recommend updating your firmware if at all possible. The difference could be described as akin to a dirty flash as opposed to wiping everything and then flashing. The difference between the older firmware and the most current is quite simply astounding. And the battery performance is the clincher. Initially, I would have trouble making it 6-7 hours. Now, it's anywhere from 8 hours to my record of 12 hours and change. She now has a new lease on life, and it looks like another year on the M7 is in the cards.
doing a factory reset from recovery is jsut as good...
from my expereince wiith dealing wth Windows phones ( windows phone only use RUU to flash custom /stock roms). it is the same as factory reset from settings.
Related
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
Hi all,
I just updated my Magic (Hutchison/3, Australia) (32A) to the latest official HTC firmware with sense ui (I had cyanogen on there before but it was too buggy for my liking). However, it seems that this firmware has the "perfect" spl (HBOOT-1.76.0008, Radio 6.35.08.29). I was planning to root the phone without flashing a different rom but i of course need write access to /system. My plan was to boot amon-ra's recovery to do this, however when i try and boot it with "fastboot boot recovery-RA-sapphire-v1.6.2H.img", i get told "FAILED (remote: not allow)" (same deal for the hero version).
My idea is to download an old sappimg.nbh and start up the SPL on the phone, which displays some messages about looking for that file when it starts up. I assume this will flash an older SPL; then, i install the system part of the new ROM but not the radio/SPL somehow (is this possible?) then follow my initial plan for rooting the phone
However, from what i've read it seems messing with the SPL is pretty much the only way to brick the phone. Is what i suggest safe/will it work?
Thanks guys
greeklegend said:
Hi all,
I just updated my Magic (Hutchison/3, Australia) (32A) to the latest official HTC firmware with sense ui (I had cyanogen on there before but it was too buggy for my liking). However, it seems that this firmware has the "perfect" spl (HBOOT-1.76.0008, Radio 6.35.08.29). I was planning to root the phone without flashing a different rom but i of course need write access to /system. My plan was to boot amon-ra's recovery to do this, however when i try and boot it with "fastboot boot recovery-RA-sapphire-v1.6.2H.img", i get told "FAILED (remote: not allow)" (same deal for the hero version).
My idea is to download an old sappimg.nbh and start up the SPL on the phone, which displays some messages about looking for that file when it starts up. I assume this will flash an older SPL; then, i install the system part of the new ROM but not the radio/SPL somehow (is this possible?) then follow my initial plan for rooting the phone
However, from what i've read it seems messing with the SPL is pretty much the only way to brick the phone. Is what i suggest safe/will it work?
Thanks guys
Click to expand...
Click to collapse
unfortunately wont work... it wont allow you to flash an older spl...probably will have to wait till an official 2.1 update comes out and hope that it might be rootable..
And THAT will teach me to look before I leap! I guess I can live with this update because its actually a HUGE improvement over what I was using before (radio reception is much better, text correction in the browser,sense is win in general and its much snappier) and I can still do usb tethering. But still, WHY DID YOU DO THIS TO US HTC!!!
EDIT:
I tried taking the rom image from the RUU and using fastboot to boot the boot.img from that but not even that works! I was thinking to do something like init=/system/bin/sh... I don't suppose theres another way to supply cmdline parameters to the kernel?
my girlfriend hates the OTA 2.1 cause there is so much not working now
so i was wondering if there is way/tutorial to downgrade from the crappy 2.1 OTA back to original 1.5 without rooting
if not what is there a tutorial for rooting then downgrading
Edit:
since i have a moto droid and my girlfriend didnt care much about rooting till now what type of things are diffrent when rooting the eris compared to droid (OCing, roms, themes, nandroid backups, ect.)??
Check out this link to root the eris: http://forum.xda-developers.com/showthread.php?t=647707
I'll post again once I find the 1.5 rom, although I think it may have been removed.
After searching it appears that jcase took the download down at the request of a few users.
So, what I would do is root then flash some of the new roms that have come out. Personally, I'd give either CyanogenEris or Senseless a try because they are AOSP based (like your droid is).
If you are into the Sense scene, I would check out the plethora of roms listed here: http://forum.xda-developers.com/showthread.php?t=649705
so your not able to just downgrade?? cause thats all my girlfriend really wants
and are the 2.1 roms(with sense ui cause for some reason my girlfriend likes it) based off the leaks or the official 2.1 and do they run better then the official 2.1
Edit: that tutorial is for stock 1.5 not 2.1
Downgrade instructions are here http://androidforums.com/all-things...ot-thread-apps-roms-updated-05-06-2010-a.html
Full Downgrade from 2.1root (any) to 1.5 stock - FULLY WORKING
THIS IS NOT FOR LEAK USERS SO DON'T ASK
If it bricks your phone, not my fault (it shouldn't and I hope it doesn't).
Please read and follow the directions included.
unzipme.zip md5sum: 0ed3c91d7574367d65428b3bc230f217
http://www.multiupload.com/6UE7AUN810
This is fully working, I just did a full reflash to 1.5, including the kernel, the system software, the radio firmware, recovery image and the bootloader.
This must be done from a PC with Fastboot, which comes with windows. Linux/Mac users will have to find it and compile it. You will need to have Amon's recovery image installed to use this downgrade, at the end we will overwrite his image with the stock one.
Inside unzipme.zip are three files
downgrade.zip md5sum: c440c87f1e67f4b62e05da0d255e80e9
-Do not unzip/open/alter this file
--Contains your kernel, radio firmware, and system.
recovery.img md5sum: 71a4b633bdb32de9dcdd8953fef43cdc
--stock recovery image
hboot.nb0 md5sum: 38899da4e5e002e3be22900f5f4eb6f7
--Original bootloader
Step one:
Put hboot.nb0 and recovery.img in the tools dir of your sdk.
Put downgrade.zip on the sdcard of your phone
Step two:
Turn your phone off, then turn it back on holding the power button (red) and send button (green). Once in the boot loader press volume down, then volume up to get to Amon's recovery image. Go to wipe, wipe dalvik cache, and do a factory reset (aka wipe data). Then choose flash zip from sdcard, and flash downgrade.zip. The phone will flash the kernel, and system softare, then ask you to reboot. Let it reboot so it can flash the radio, it will restart back in the recovery image. You can power down your phone now.
At this point if your just wanted 1.5 back, you are done.
If you want the original bootloader and recovery image, (ie 100% stock) continue on.
Step three:
Plug your phone into your PC. Power your phone on using the power button (red) and send button (green). Your phone should now be sitting back at the bootloader screen and say FASTBOOT USB. Now on your PC, go to the sdk tools dir in command line. Issue this commanhttp://www.multiupload.com/6UE7AUN810d
Code:
fastboot flash recovery recovery.img
Let it flash, when done wait a minute (just to make sure).
Then issue this command
Code:
fastboot flash hboot hboot.nb0
Once this is done, wait a minute then pull your battery and restart your phone.
You are now back at factory stock.
Click to expand...
Click to collapse
Personally I'd stop after step 2 in case you ever want to flash a rom in the future.
Woops, I missed that she's not rooted. You could root it and go back down to 1.5.
tiggerxplur said:
so your not able to just downgrade?? cause thats all my girlfriend really wants
Click to expand...
Click to collapse
In theory you could downgrade using the same methods as going from RUU 1.17-1.16 (since they have the same bootloader version and are both signed), but I don't know that anyone on 2.1 OTA has tried that.
Even if you got it to downgrade she'd be bugged constantly about the OTA (every 2 minutes I believe), which would suck for her. Also it takes up ~100MB of space on her phone too, so I would just go with rooting.
tiggerxplur said:
Edit: that tutorial is for stock 1.5 not 2.1
Click to expand...
Click to collapse
The root process is exactly the same for 2.1 OTA users, but will not work if it's a 2.1 leak.
At this point all the roms are based on 2.1 OTA or another person's 2.1 rom and most of them run better than the 2.1 OTA.
It's really just a trial-and-error process. Some users will swear by one rom and hate another, while others will swear by a different rom.
I'd have her look at all of the roms and pick one based on looks, because it sounds like she won't use most of the advanced features anyways.
nindoja said:
In theory you could downgrade using the same methods as going from RUU 1.17-1.16 (since they have the same bootloader version and are both signed), but I don't know that anyone on 2.1 OTA has tried that.
Even if you got it to downgrade she'd be bugged constantly about the OTA (every 2 minutes I believe), which would suck for her. Also it takes up ~100MB of space on her phone too, so I would just go with rooting.
The root process is exactly the same for 2.1 OTA users, but will not work if it's a 2.1 leak.
At this point all the roms are based on 2.1 OTA or another person's 2.1 rom and most of them run better than the 2.1 OTA.
It's really just a trial-and-error process. Some users will swear by one rom and hate another, while others will swear by a different rom.
I'd have her look at all of the roms and pick one based on looks, because it sounds like she won't use most of the advanced features anyways.
Click to expand...
Click to collapse
yea she doesnt care for the advanced things i have tried to get her to use another home replacement app like helix cause i know sense ui is a resource hog but she likes it too much and doesnt wanna try and get used to something new but i will talk her into rooting and choosing a rom she might like thanks for the help
i had a rom before 2.1 for the droid that didnt block the ota and it was very annoying it varied between 2 minutes to ten minutes
is there an app like rom manager to switch between roms like the droid
I went from 2.1 OTA back down to 1.5 using the RUU MR2 on the computer. Worked like a charm!
downgrade leak 2.1 to 1.5 stock
Is there anyway to downgrade this horrible 2.1 leak back to the stock 1.5 version.
damon428 said:
Is there anyway to downgrade this horrible 2.1 leak back to the stock 1.5 version.
Click to expand...
Click to collapse
No...... x10
Please Delete. Duplicate.
If its been said once, it's been said a thousand times here,
"can I root the 2.1 LEAK?"
As always the answer is HELL NO!!!!
"can I root 2.1 OTA?"
Yes.
"can I downgrade 2.1 OTA to 1.5"
Yes.
So just decided to get an evo. My wife has had hers since release day. This one Has the 2.20 and the 3.30.651.2 Build. The quality of the screen is horrible compared to hers (the color and brightness). Before even being able to root it I couldnt use QIK because it reboots the phone. Downloaded the latest one and I can open the software and its after my camera kicks on that it reboots now....
So i rooted it and got the s-off. Now I can take nand backups but its says they are corrupt. Cant flash a rom because it will hang on the Evo boot screen or it will drop to a boot loader loop with the HTC with 4 exclamations....
Is anyone else seeing this or is this guy flat out a lemon?
I have looked around the forums a little and found people having a hard time rooting and s-off which was easy after skimming the forums for a while. Thanks ahead of time for any input in this.
The screen problems im not sure how to fix
there is a new ota to fix your camera issues, yours is most likely the new hardware/camera 004 model.
for rooting the only method that works is toast's, unrevoked wont. Unless im behind on info. Have you tried toast's method?
Unrevoked works fine. Took me about five minutes to root useing that method when I got my replacement phone.
As far as your phone issues, take it back to the store and show them the problems. Get a replacement.
Oracle, go to your bootloader. What is the first line? Is it Supersonic EVT2-3 S-off? If so, I had the same problem. You have bad blocks. My recommendation is the that you flash sprintlovers ROM. It cones as a pc36img.zip, and you flash it through bootloader. I tried every method of rooting and none of them would let me flash through recovery.... I always either got errors while flashing or, even if it seemed to flash fine, it would never boot. Also, Sprintlovers will get your pri corrected. If this works for you, give me a shout, and I have an idea we can try.
(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?