Why should I be waiting for a Sprint ROM release as opposed to using DCD's latest release with the 3.39 radio? Is there any practical benefit to waiting? Will I have trouble with having a phone replaced if it's not an official Sprint ROM?
using the beta sprint rom has led to issues with legacy applications working for me (like dashwire and som other applications). DCD has a better rom. period. I think his roms are faster and respond much better than that of the sprint rom, without sacrificing page pool and therefore how many tasks the ppc can run. That said, as far as taking it back to sprint, before you do it, just reflash it to the stock sprint rom. Its that simple
Official ROM"s are pretty good,not counting beta roms!
No Official ROM"s = no DCD roms
Had my custom ROM phone replaced couple times , sprint never gave me problem. U can always relock and flash sprint rom.
Related
I had a older rom version on my Verizon XV6800, I was able to get gps working by following this link: http://www.phonenews.com/how-to-add-gps-to-htc-mogul-xv6800-p4000-titan-2663/ but it stop vibrating, it would only ring. I Took it the tech support, they determined I needed a replacement phone. I got a replacement phone with the following specs:
Windows Mobile 6.1
ROM version: 3.57.605.1
Rom Date 7/21/08
Radio Version: 3.37.75
Should I following this: http://www.phonenews.com/how-to-add-gps-to-htc-mogul-xv6800-p4000-titan-2663/ to get my GPS working again or is there another method since this ROM is a new version
You have 2 choices, search for the thread in using gps with MR1, or flash it back to an older Verizon stock rom with Windows Mobile 6.0 and then follow the normal flashing thread to get it up to a custom 6.1 rom. The problem is MR1 disables GPS except for their own GPS app or the Valhala server that someone wrote.
Honestly I think it's best that you flash back to 6.0 and then upgrade normally thru the custom route so that more GPS tools work without running a 3rd party app.
BTC
Do u kno where I can find the thread to go back to original rom?
try this http://forum.xda-developers.com/archive/index.php/t-376873.html http://forum.xda-developers.com/showthread.php?t=376873
good think is before flashing stock rom ,activate different phone then flash
after you done reactivate PDA so you dont have to call verizon to get a A-KEY
Why do you recommend to activate a different phone? I did not need a new a key when I went from MR1 to old stock version then to DCD.
when i flashed mine to old rom then dcd's first what i did. flashed bootloader ,radio rom ,and dcd's rom .using RUU via USB cable and i lost A-key .
i did not use SD card method
BillThyCat said:
You have 2 choices, search for the thread in using gps with MR1, or flash it back to an older Verizon stock rom with Windows Mobile 6.0 and then follow the normal flashing thread to get it up to a custom 6.1 rom. The problem is MR1 disables GPS except for their own GPS app or the Valhala server that someone wrote.
Honestly I think it's best that you flash back to 6.0 and then upgrade normally thru the custom route so that more GPS tools work without running a 3rd party app.
BTC
Click to expand...
Click to collapse
Hey Billy do u have walk thru for flashin back to 6.0 and then upgrading normally
Actually I don't have a Verizon phone, I only know what I stated based on other threads I have read.
I would check HTC's website, they may have an older stock rom listed still. If not, then I'm sure there is a Wiki on here somewhere with links to older roms.
As far as ability to flash, you may need to relock the phone first, I would wait for some other wiser VZW user to respond.
BTC
http://forum.ppcgeeks.com/showthread.php?t=21161
Searching found this link very easily.
Thank u sir
I unlock the device, flash a custom ROM and upgrade to a Sprint radio that will allow GPS..Took a while but Gps is now working. Now I need to get my picture messaging to work now. Any tips?
BillThyCat said:
You have 2 choices, search for the thread in using gps with MR1, or flash it back to an older Verizon stock rom with Windows Mobile 6.0 and then follow the normal flashing thread to get it up to a custom 6.1 rom. The problem is MR1 disables GPS except for their own GPS app or the Valhala server that someone wrote.
Honestly I think it's best that you flash back to 6.0 and then upgrade normally thru the custom route so that more GPS tools work without running a 3rd party app.
BTC
Click to expand...
Click to collapse
<REQUEST TO MODERATORS>
Hey all, can anyone update the Verizon aGPS fix article in the wiki to include this info? A lot of people see the links that send them to the wiki for the fix (having MR1 already on their phone, updated or bought that way) and the fix doesn't work (FRUSTRATING). It would save so much trouble if there was 1 line that said "If you have MR1 installed and want to upgrade to a custom rom w/GPS, downgrade to (link to original rom) and then upgrade to your choice." Apparently that is a big problem people run into (me included) and so much frustration would be avoided (as well as so much posting space). So, can anyone add/change that for us?
Hello everybody, I am new in matter of Smarth Phones and more even, on HTC one's...
I have a HTC HD2 T-Mobile
Qualcomm 8250B 1ghz procesador
576 RAM
1024 Flash Memory Size
687.12 MB Storage Size
16 GB Micro SD memory
OS vrsion 5.2.219.13 (21913.5.0.94)
Manila version: 2.5.20181424.0
ROM version: 3.14.531.1 (04666) WWE
Radio Version: 2.15.50.14
Protocol Version: 15.42.50.11U
I want to know 4 things:
What is the ¨Radio¨ thing, as I said, I am new in this so I want to know what it is and what is it about, cause I hear people talking about fixing their bugs and freezes by changing it.... explanation?
What changes when changing the Radio? when you change it, it comes side by side with the ROM? or they are changed separatly...? (sorry about my english)
Can install ROMS for HTC HD2 normal version to a HTC HD2 T-Mobile version? without having problems?
And the last one.... I understand that the ROM is not the OS, since it is Win 6.5.... but.... what it is exactly then?... and can someone tell me about the MOST ESTABLE ROM available for my HTC HD2 T-Mobile? Doesn't matter if it's unofficial ROM, at least that it works fine and better than the original one that freezes a lot...?
PS. : I'm pretty good at computers (I like to think so...XD) and I learn fast, so please feel free to explain me how ever you can and I'll do my best to understand it. thnx!
Read sticky FAQ. All your questions are answered there
Hi Emilio,
Let me try to answer your questions - someone correct me if I'm wrong... this is what I've understood from browsing the forums for a half a year now...
The radio in your phone is what controls all wireless access, such as wifi and cell reception. Different radios have different battery life/better reception depending on the cellphone - I haven't seen anyone come out and say one is the best although I have been using 2.15 for quite some time now and it's pretty good. Just remember your radio has to be 2.xx.50 because of your type of phone (T-Mobile/TMOUS) or else you will brick your phone (it wont work).
Some ROMs change your radio when you flash - although I haven't come across any custom ROMs that do. In any case, any time you flash make sure the ROM says TMOUS or T-mobile supported! Also, before you flash you need HSPL (search the forums to find out what it is and how to use it).
The ROMs the the awesome chefs here make are usually based on WM 6.5 or 6.5.x - but you dont have to worry about it. For all purposes its Windows Mobile 6.5.x or 6.5 and all windows programs work, etc.
Which ROM is best? That's a long argument. I've been using Energy Roms for quite some time now - every time I flash I always make my way back to Energy in the end. Just go through the ROM section - most ROMs are good (actually so far I haven't come across a bad one) and they are almost all much more stable and smoother. Just remember to make sure it's TMOUS compatible.
Flashing HSPL, Radios, and ROMs are in the forum and perfectly well explained... just search and you'll see.
thank you man!
salonluden said:
Hi Emilio,
Let me try to answer your questions - someone correct me if I'm wrong... this is what I've understood from browsing the forums for a half a year now...
The radio in your phone is what controls all wireless access, such as wifi and cell reception. Different radios have different battery life/better reception depending on the cellphone - I haven't seen anyone come out and say one is the best although I have been using 2.15 for quite some time now and it's pretty good. Just remember your radio has to be 2.xx.50 because of your type of phone (T-Mobile/TMOUS) or else you will brick your phone (it wont work).
Some ROMs change your radio when you flash - although I haven't come across any custom ROMs that do. In any case, any time you flash make sure the ROM says TMOUS or T-mobile supported! Also, before you flash you need HSPL (search the forums to find out what it is and how to use it).
thnk you very much!... oh... so, Energy ROMS are estable enough to change ?
The ROMs the the awesome chefs here make are usually based on WM 6.5 or 6.5.x - but you dont have to worry about it. For all purposes its Windows Mobile 6.5.x or 6.5 and all windows programs work, etc.
Which ROM is best? That's a long argument. I've been using Energy Roms for quite some time now - every time I flash I always make my way back to Energy in the end. Just go through the ROM section - most ROMs are good (actually so far I haven't come across a bad one) and they are almost all much more stable and smoother. Just remember to make sure it's TMOUS compatible.
Flashing HSPL, Radios, and ROMs are in the forum and perfectly well explained... just search and you'll see.
Click to expand...
Click to collapse
thnx! a lot!
one thing missed in the otherwise comprehensive answer above...
you have 3.14 rom, so as it stands hspl cannot be installed so cooked roms and radios cannot be installed.
should you want to try the cooked roms you would first flash the stock tmous 2.10 rom, which willdowngrade your spl and hspl3 will work.
oh! so I have to get to my old rom first after changing to the Energy ROMS?
yep. there are 3.14 based cooked roms coming out but not many, most are 2.x based so require the downgrade.
you don't have to wait for the flash to completely set up and running before you flash the cooked rom, as soon as the flash finishes, and windows begins to set up, pop the battery and enter bootloader, apply hspl, enter bootloader again and flash the rom.
I just got around to rooting my TB and have attempted to install a couple of liquids roms. I had to revert back to the original backup both times due to loss of service? is it a requirement to flash a radio right after rom installatio?? Both of my Moto Droids were romed, but the Tb seems to be a different animal.
Any help appreciated, Thanks
ROMs are radio specific, older froyo ROMs use the MR1 radio. GB and most newer Froyo ROMs use MR2 and up. The wrong radio will cause you to lose service, the OP of your ROM thread usually lets you know which radio to run.
setexascustoms said:
ROMs are radio specific, older froyo ROMs use the MR1 radio. GB and most newer Froyo ROMs use MR2 and up. The wrong radio will cause you to lose service, the OP of your ROM thread usually lets you know which radio to run.
Click to expand...
Click to collapse
Thanks for the help, still learning!
No problem, that's what we're here for.
I was areading a couple of treads saying GB radio will brick you and etc (http://forum.xda-developers.com/showthread.php?t=1096104)
My Tbolt is running fine, but is it recommended I revert back to Froyo?
if so Do I just flash a Froyo ROM and use an MR1 radio?
You should be fine, I've been running Gingerbread for some time now. I believe it was concluded to be a hardware problem, not software.
I agree. I have been running several different GB ROMs with no problem. Some of the ROMs do have specific recommendations for the particular radio based on the testing by the ROM developers.
That being said, I recommend that you run a radio from an official release. For example, I did not update to the leaked radio, I waited until the last OTA was released and the radio had been yanked out of it for separate installation.
You should be fine. It seems like the vast majority of the people are on GB now. Understand tho that there is always a small risk of bricking your phone even on something that people deem "safe".
There's always a possibility of your phone bricking. It wouldn't matter if you were running Froyo or a GB ROM.
First of all this is my first post. Hello to everyone. I have been searching/reading thru these forums. Great source of info.
Phone info:
Currently S-OFF, unlocked, lateset AT&T 4.4.2 firmware, viperone 6.2.1, twrp
I have a pretty good comprehension of how to install or revert pretty much anything that can be done to this phone and have done so with great success. What I don't understand is the relationship between the firmware base of an RUU and the build of any given ROM. How is it that a custom Rom based off let's say x.xx.401.x work with x.xx.502.x main version? The devs say to update to the most current available firmware. Does that mean I have to flash a firmware base that matches what the Rom base for optimal performance? Because I originally thought that was the case and when I did my phone developed syncing issues particularly with the stock mail and weather apps. They would only sync over WiFi. Everything else about the phone worked as normal. Believing there was a problem with the Rom I flashed a few different popular roms on here. Always returning to full AT&T stock first. I later fully converted to GPE and to my surprise everything worked as normal. So I then converted to stock developer edition by way of zip flash and RUU exe. (By the way, when I say stock I mean s-off & unlocked but otherwise factory.) Received all the ota's. Main version would show as x.xx.1540.x. supposedly this would make my phone a dev edition with AT&T as the provider. And yet the syncing problems returned. So once again I returned back to factory AT&T 4.4.2 and all returned to normal. I then decided to try and use a Rom based off 4.4.2 and not one from 4.4.3; expecting the syncing issues to return only this time they didn't. So now I am really confused.
My questions are:
If coming from 4.4.2 factory firmware, is it best to run a Rom from the same base or am I doing something wrong and I should be able to use a Rom from a newer base on an older firmware?
If the developer edition and GPE can be carried by AT&T then why was I having syncing issues with the developer edition and not GPE?
I thought by being s-off I should be able to flash any RUU from any carrier without problems, just that I would be limited to the network capabilities of the actual service provider.
Everything I know about this stuff I learned from this forum. But I think I missed something.
My AT&T M7 always works best on the stock software.
The only thing I could figure is that AT&T have refined the software and radio so well that all the other versions pale in comparison.
I noticed the Developers Edition always had a horrible Bluetooth and WiFi radio. Signal strength was always weak compared to the stock AT&T software.
To answer your questions
Flash any version Roms you want on the latest AT&T firmware. And you'll have the best your phone can be.
clsA said:
My AT&T M7 always works best on the stock software.
The only thing I could figure is that AT&T have refined the software and radio so well that all the other versions pale in comparison.
I noticed the Developers Edition always had a horrible Bluetooth and WiFi radio. Signal strength was always weak compared to the stock AT&T software.
To answer your questions
Flash any version Roms you want on the latest AT&T firmware. And you'll have the best your phone can be.
Click to expand...
Click to collapse
I get so mixed up with all the terms being used interchangeably. So to clarify, as long as I am using the latest firmware from AT&T (currently 5.12.502.2 kk4.4.2), I can flash any custom ROM base. Whether it is based on 4.4.2 or higher. Correct?
I still want to know why I experienced the sync problems while running the factory x.xx.1540.x dev edition but not with the GPE. I never tried the factory x.xx.401.x WWE firmware either. However, I just got an sim unlock code from AT&T earlier today. I'm gonna try that maybe tomorrow and see if it makes a difference altho I don't believe it should. And I'm not gonna switch to a different provider.
Honestly, I was happy with my phone before I got wrapped up in all of this. I just decided to tinker with the phone and the mod bug has bitten.
ANGRY_robert said:
I get so mixed up with all the terms being used interchangeably. So to clarify, as long as I am using the latest firmware from AT&T (currently 5.12.502.2 kk4.4.2), I can flash any custom ROM base. Whether it is based on 4.4.2 or higher. Correct?
I still want to know why I experienced the sync problems while running the factory x.xx.1540.x dev edition but not with the GPE. I never tried the factory x.xx.401.x WWE firmware either. However, I just got an sim unlock code from AT&T earlier today. I'm gonna try that maybe tomorrow and see if it makes a difference altho I don't believe it should. And I'm not gonna switch to a different provider.
Honestly, I was happy with my phone before I got wrapped up in all of this. I just decided to tinker with the phone and the mod bug has bitten.
Click to expand...
Click to collapse
I think I figured this out. I continued to flash different ROMs and firmwares with the same results as I posted in the OP. Then earlier tonight I decided to try to convert to developer edition again (x.xx.1540.x) and flashed an ruu.zip, went thru the setup process, and as before the same issues returned. Then I had an idea; lets try something I haven't done yet. I pulled the SD card and factory reset the phone. After I completed the basic setup process I inserted the SD card and let the phone do its thing. The phone now works as it should (same as it does with the AT&T xx.502.x firmware installed).
Just figured I would pass this along.
Cheers
I give up
I thought I had this figured out. Last night after to converting to dev edition with all updates, everything seemed normal. I flashed the latest viperone rom as it is the rom I want. Turn the phone on this morning and the sync problems are present once again. I have searched thru a tom of pages on this sight alone. I cant find an answer. So its back to stock at&t.
I solved the problem. Incorrect settings in 4636 menu.