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?
Related
Ok, so I finally received my new Titan from USCC (Us Cellular). I figured it would be a while before getting it, but surprisingly, It was here 2 days after they advised me it would be sent.
Question is this: How can I make a functional ROM dump (copy) of it's ROMS?
I know that once flashed to a GPS ROM, it is very risky to flash back to a non-GPS ROM; however, I've read several threads on PPCGEEKS on how to successfully accomplish this. My new phone isn't even activated yet, so, If anyone can guide me through a method of successfully making a functional copy of this stock ROM, and RADIO, It might be very helpful to UL this to a wizard like DCD so that he can work his magic and provide yet another useful upload for all of those wishing to re-flash to stock!
I'm DEFINITELY going to flash DCD's latest ROM to my new phone, but I was hoping that someone could help me copy/create a functional ROM dump prior to me altering it!
Any advise?
BTW, thanks, DCD, for working on this USCC related stuff.
Ok... I was in a nasty car accident on friday. One of the things that got damaged in the crash was my phone. Luckily, I had the insurance and just got the new phone.
I was running DCD 3.x before with a GPS compatible ROM and it was working GREAT!
I'm a little confused by the whole RevA and Verizon GPS thing. I've been reading all sorts of things.
My question is... do I need to do anything special to the phone BEFORE I flash the latest and great Radio and DCD ROM? I read somewhere I need to flash back to a previous Verizon ROM before flashing to DCD or the GPS will get screwed up. True?
The two important things I want are GPS and tethering. Must have those. =)
Thanks in advance... we now, return to our regularly scheduled pain killers.
PS - My phone has the following from factory:
ROM - 2.09.605.8
Radio - 1.30.60
http://forum.ppcgeeks.com/showthread.php?t=33857
read that, then reread it... then follow the steps
Thanks!... that much I knew. What I am unsure about is the new M1 update on Verizon and the GPS issues I'm reading about.
How do I tell if this new phone has the M1 update already?
ookami007 said:
The two important things I want are GPS and tethering. Must have those. =)
Thanks in advance... we now, return to our regularly scheduled pain killers.
PS - My phone has the following from factory:
ROM - 2.09.605.8
Radio - 1.30.60
Click to expand...
Click to collapse
Your phone has the original stock radio and ROM on it.... It doesn't have MR1 on it.....
Thanks! I think I may wait a few days tho... painkillers and phone upgrades don't mix.
Gentlemen,
I have read a few threads on this and I cannot get a handle on how well it works. The ROM I dl'd did not look like the shipped rom, it was a windows mobile screen, not a TF3D screen. Also the start screen was different. I have to turn in this phone cause my earpiece does not always work. So please, someone that has done a warranteee turn in after flashing a new ROM respond with how the process worked for yyou. Also, which of the shiiped ROMs shoould I use fromm the raphael wiki page.
Thanks,
Scott
I’ve never had to do any warranty work on my phone but I have used the latest ROM update from HTC’s website which has everything you’re asking for in a ROM. Go to htc.com click the support tab and then select your device from the drop down menu.
Everything you need to know is located in the Wiki, search for it and follow those directions and you'll be good.
SEARCH before starting a new thread!
http://forum.xda-developers.com/showthread.php?t=502720
Hey buddy, as I stated I did search the threads. The thread you quoted I used and as I stated it did not look like an att shipped ROM. That is why I posted. Please read the post before you flame..
Scottk517 said:
Hey buddy, as I stated I did search the threads. The thread you quoted I used and as I stated it did not look like an att shipped ROM. That is why I posted. Please read the post before you flame..
Click to expand...
Click to collapse
ok, maybe u are right i ain't got a fuze so i didn't need the at&t rom. still the solution to your problem is very simple.. having a fuze means you should be able to download the latest official rom either from the htc site or the at&t site. follow the steps in the thread u already found and when in comes to flashing just flash what you downloaded.
to further show u my good intentions i went ahead and found the latest official release from at&t, flash this and you won't have any problems with warranty
http://forum.xda-developers.com/showthread.php?t=519698&highlight=latest+at&t
The Process....
1. Flash the stock AT&T rom. It should include the stock AT&T Radio. 2. Flash the OEM Hard SPL as instructed in the sticky at the beginning of this forum. If you can't get the hard SPL to take then flash it from the bootloader screen. 3. Re-flash your stock AT&T Rom again to get the Hard SPL version of 1.95 that came with your Fuze. Don't skip the re-flash of the stock ROM or you will be sending the phone back with 1.90 not 1.95. May the force be with you. I'm not responsible if you mis-read the directions and mess up your phone!! I have had to do this twice now and it works perfectly.
Cheers!
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.
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.