Current config in signature.
I don't want to go back to stock or s-on or bootlocked I'm just interested in flashing the latest official sense ROM. I'm troubleshooting an issue making/receiving calls. I've already replaced the SIM and have talked with support. I've also tried an older version of the ROM I'm using so I thought I would give the sense ROM a try. What is the easiest way to go about this?
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?
I have an AT&T HTC One M8 which I messed up trying to upgrade it to 4.4.3. I need to get it back on sense but nothing seems to work. When I try to flash the stock rom I downloaded from another post it says failed. I managed to install CM11. How can I get it back to sense? The Cid is 1111111. I really need help!!! I'm kind of new so I need the step by step process.
Thanks.
What recovery and version are you using? Did you try to download the stock ROM again, or check MD5 to make sure the file wasn't corrupted during download.
Did you try a Sense based custom ROM, there are several based on either the AT&T or "international" stock ROM, that are very close to stock, just debloated and with some optimizations (which are both good things). Personally, I'd recommend the international base over the stock AT&T ROM, anyway.
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.
I just rooted my HTC One M8 and I was wondering if I could still flash roms without having s off because my phone has everything required besides the s off portion but I wanted to see if there's a way I can still flash roms because I want to upgrade it to sense 7
Sent from my HTC One_M8 using XDA Free mobile app
No, you don't have to be s-off, unless you are flashing a custom, non stock rom like cyanogen mod. I assume you are referring to the Skydragon rom which purports to have the new Sense 7 UI when you say you want to flash a rom with sense 7. Personally I would go s-off before doing anything as it makes reverting back to older firmware much easier. Just scan the q&a thread for all the problems people who are s-on have when jumping from kit kat to lollipop or to dev editions, gpe, etc. Trust me, the $25 spent on Sunshine will be worth the time and headaches you'll get when you start getting flash happy, but that's just my opinion.
As mentioned above, you don't "need" to have s-off to flash a ROM, literally anyway. The ROM will flash, and boot (eventually), and mostly work. But if you are currently on KitKat, and try to go to any Lollipop Sense ROM, its very common you will have some serious issues such as extreme long boot times (10 min or more) with no boot animation (making many folks think it isn't booting at all), broken WiFi, and possibly audio issues. All due to outdated firmware (partitions such as hboot, radio, and more that don't flash with the ROM). And s-off is needed to update to Lollipop firmware, until AT&T releases the LP update officially. In that case, you can update to the proper firmware by official OTA or RUU.
I am fairly new to the whole ROM thing on this device. I have experience with older phones and am just getting back into this recently. That being said...
Current state is: Bootloader unlocked, currently running stock 4.4.4, Sense 6.0, Kernel 3.4.0-g931e842, Build 3.42.502.1 CL441323; ROM applied via RUU. (RUU_M8_[email protected]41216A_40.34.C35006.02_F_release_407726_signed_2)
Bottom line is that since I have attempted to root and flash ROMs I have had issues with making and/or receiving calls, or no SIM recognized at all, requiring S-off/firmware upgrades, etc.
I am looking for a stable build ROM which is compatible with the 4.4.4 firmware on my device which can be applied without obtaining s-off. Main goal is to be able to personalize the UI and to run a faster, debloated ROM.
Tried first using Renovate 5.0... could not receive calls on that one.
Removed. back to stock.
Next I found a Lollipop 5.0.1 ROM (HTC_One_M8_Lollipop_5.0.1LRX22C) which did not appear to require firmware updates... seemed to work great... except that I could not receive calls...
Removed... back to stock.
Next, I used ViperOneM8 and really liked it, but had to abandon once I was told by people that they were still getting sent straight to voice mail.
I did get some calls, so I tested having some people call me and it seemed fine... well turned out that during those tests I was on the 3G network... Once again, troubleshot down to the fact that anytime I was on 4G network I could not receive calls. Having had no way to change my network selection in this ROM (error was displayed when I attempted this). Contacted their support to confirm my issue. They are aware, no resolution available.
Removed... back to stock.
So my question is, are there any options OTHER THAN paying $25 to use Sunshine to get S-off, upgrade firmware? I am not a developer and I love my M8. I know there are people here who know exactly what I need and understand what I am looking for. Thanks in advance for any assistance.
GA_Android said:
Next I found a Lollipop 5.0.1 ROM (HTC_One_M8_Lollipop_5.0.1LRX22C) which did not appear to require firmware updates... seemed to work great... except that I could not receive calls...
Removed... back to stock.
Click to expand...
Click to collapse
I can't tell what ROM your are talking about based on that description. Possibly GPE stock rooted?
What I can tell you, is that most any Lollipop Sense ROM will have issues when used alongside 4.4.4 firmware.
Sense 4.4.4 ROMs will play well with your firmware, as will a number of 4.4.4 and 5.0 GPE and AOSP ROMs (that specifically state they support 4.4.4 firmware). However, when it comes to AT&T, there is more at play then whether the ROM corresponds to the firmware. That other complication is that AT&T does some annoyingly unique things with their network. In the past, this has included changes to build.prop and even the signal icons, which sometimes caused "international" custom ROMs to have some issues. And now you see that their HD Voice (Voice over LTE) is messing with some custom ROMs. As the other thread you posted in mentioned "blame AT&T".
Running an AT&T base 4.4.4 ROM is your best bet for trouble-free use on AT&T's network. WNC's ROM might fit the bill for what you want (debloated) and is often where I send folks that want a bug-free experience on AT&T (while retaining some AT&T specific features). The 3.28 version ROM is what you should try: http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
There are other ROMs that might work for you. But the above is my suggestion, at least as a start.
redpoint73 said:
I can't tell what ROM your are talking about based on that description. Possibly GPE stock rooted?
What I can tell you, is that most any Lollipop Sense ROM will have issues when used alongside 4.4.4 firmware.
Sense 4.4.4 ROMs will play well with your firmware, as will a number of 4.4.4 and 5.0 GPE and AOSP ROMs (that specifically state they support 4.4.4 firmware). However, when it comes to AT&T, there is more at play then whether the ROM corresponds to the firmware. That other complication is that AT&T does some annoyingly unique things with their network. In the past, this has included changes to build.prop and even the signal icons, which sometimes caused "international" custom ROMs to have some issues. And now you see that their HD Voice (Voice over LTE) is messing with some custom ROMs. As the other thread you posted in mentioned "blame AT&T".
Running an AT&T base 4.4.4 ROM is your best bet for trouble-free use on AT&T's network. WNC's ROM might fit the bill for what you want (debloated) and is often where I send folks that want a bug-free experience on AT&T (while retaining some AT&T specific features). The 3.28 version ROM is what you should try: http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
There are other ROMs that might work for you. But the above is my suggestion, at least as a start.
Click to expand...
Click to collapse
You are correct. It is a GPE stock rooted Lollipop ROM. It works just fine as long as I have 3G selected as my network, but it is just not as much flash as I wanted.
I am going to give the one you sited here a look and maybe give it a try. I appreciate your taking the time to reply. It was helpful and informative.
Erring on the Side of Caution
I'm in a similar quandry as the OP. I have lots of experience flashing ROMS on my older phones but trying to keep up with all the changes since getting my M8 has me confused.
Here's my current setup. I'm running Skydragon after trying the last 4.4 milestone of Liquidsmooth. I like both, but am interested in keeping up with the Lollipop guild.
I have Sunshine installed but when I ran it I found out I need to remove or disable Xposed Installer to continue. I'll deal with that by disabling it.
UPDATE: Well, that didn't work. Xposed was installed with the ROM and there's no option to uninstall it.
My biggest concern is updating the firmware. From my bootloader info, I'm assuming that I'm way behind on the latest firmware, but after reading so many threads about updating, my head is swimming.
If I need to update, I just want to make sure that I don't brick my phone.
CanuckinPA said:
I have Sunshine installed but when I ran it I found out I need to remove or disable Xposed Installer to continue. I'll deal with that by disabling it.
UPDATE: Well, that didn't work. Xposed was installed with the ROM and there's no option to uninstall it.
Click to expand...
Click to collapse
Return to stock ROM and stock recovery, for optimal configuration for sunshine to work. RUU is probably the easiest way to get back to stock. Backup your personal data, than relock bootloader to run RUU.
CanuckinPA said:
My biggest concern is updating the firmware. From my bootloader info, I'm assuming that I'm way behind on the latest firmware, but after reading so many threads about updating, my head is swimming.
Click to expand...
Click to collapse
Yes, based on your hboot number, your firmware is about as old as it gets (Android 4.4.2).
You can RUU to 4.4.4 firmware without s-off; and Lollipop Skydragon GPE should work fine with 4.4.4 firmware.
You can of course still s-off and update to Lollipop firmware. But you need to use some other firmware besides AT&T (such as Dev Edition, Euro, etc.), since they haven't released a Lollipop update (and therefore no firmware).