Database Info

Stop Waiting for TMO to Update to ICS!

If you are waiting for TMO to Update the Sensation to ICS you should stop waiting and update to ARHD. I am a ARHD user and have been applying each update as it comes down and have had no issues at all. Battery life has improved ten fold and Android 4.0.3 is great.
If you are concerned about the warranty issues with rooting, don't be. You are on the XDA forum, so I will assume that you have at least a basic understanding of how to operate your computer. It is a simple process and you would have to be a complete idiot to screw it up.
Take it from me, switch to ARHD and you will be beyond happy!

gdwhite said:
If you are waiting for TMO to Update the Sensation to ICS you should stop waiting and update to ARHD. I am a ARHD user and have been applying each update as it comes down and have had no issues at all. Battery life has improved ten fold and Android 4.0.3 is great.
If you are concerned about the warranty issues with rooting, don't be. You are on the XDA forum, so I will assume that you have at least a basic understanding of how to operate your computer. It is a simple process and you would have to be a complete idiot to screw it up.
Take it from me, switch to ARHD and you will be beyond happy!
Click to expand...
Click to collapse
x2 arhd is good stuff along with many other roms in the dev forum

ARHD is Sense, 'tis not?

enserio said:
ARHD is Sense, 'tis not?
Click to expand...
Click to collapse
Yes, and the update from HTC will be Sense also...so no point in waiting? Getting off base install from TMO did wonders for the speed of my Sensation.
I know some people are concerned about losing Wifi calling, but it seems to work in ARHD and Virtuous ROMs just fine (btw Virtuous does NOT have Sense). I had one minor hiccup with it in an older ARHD version, but its stable now.
I was worried about losing my warranty, but if you follow the S-off/on procedure closely, you can revert your phone back to normal in case you need warranty service!

demonsavatar said:
Yes, and the update from HTC will be Sense also...so no point in waiting? Getting off base install from TMO did wonders for the speed of my Sensation.
Click to expand...
Click to collapse
Yummy what do you mean, the official ICS OTA for T-Mobile US has not been released yet?

Would love to update but the procedure seems extremely convoluted with unknown result. I am now trying to find a Youtube guide or something of this sort.

Im on ARHD right now but i would love to flash a stock ICS...problem is everytime i followed one of the guides out there i ran into a problem. I guess its because the guides are not for Sensation 4G.
Would be really nice if someone can put up a guide on how to flash a stock ICS on Sensation 4G tmo.

Question for you all. My phone is stock. If I do one of these ICS ROMs, will that wipe out all the apps I have installed and their progress? Will it make my phone like brand new?
I'm ASSUMING if I wait for the T-Mobile ICS it will keep all of my apps and their info?
Thank you
Jerry

I got tired of waiting.
I tried AHRD first and it's good. I ran it for about a week playing with sebatian's and faux's kernels. I've been running Elegancia for the last week with Bricked kernel I like it more.
I want to try CM9 when it's fully operational for a pure AOSP experience. I also want to try a Sense 4 ROM, but I understand BT isn't fully functional yet and I need that in the car - and I'm reading bad reports on battery life at this point.
---------- Post added at 10:36 AM ---------- Previous post was at 10:29 AM ----------
hortaja said:
Question for you all. My phone is stock. If I do one of these ICS ROMs, will that wipe out all the apps I have installed and their progress? Will it make my phone like brand new?
I'm ASSUMING if I wait for the T-Mobile ICS it will keep all of my apps and their info?
Thank you
Jerry
Click to expand...
Click to collapse
Your data will be wiped and you'll be doing setup like a new phone.
Download Titanium Backup first and backup all your apps/data. You're apps should auto install after you flash the ROM - or you can install them manually. Then you can restore your app data from Titanium and your game progress will be back.
I don't know if waiting for T-mo's update will require the same backup or not. But give that firmware will be updated and a complete OS update, I don't see how your app data would be safe then either.

rebar71 said:
I don't know if waiting for T-mo's update will require the same backup or not. But give that firmware will be updated and a complete OS update, I don't see how your app data would be safe then either.
Click to expand...
Click to collapse
With a stock OTA update, the update is installed via the stock recovery. The stock recovery makes a backup first before flashing the update. After the update is flashed the stock recovery takes and installs all your apps and other data from the backup it made. This way when you flash the OTA the end user does not loose all their settings, apps, and personal ink saved on their device.

T-Macgnolia said:
With a stock OTA update, the update is installed via the stock recovery. The stock recovery makes a backup first before flashing the update. After the update is flashed the stock recovery takes and installs all your apps and other data from the backup it made. This way when you flash the OTA the end user does not loose all their settings, apps, and personal ink saved on their device.
Click to expand...
Click to collapse
Thank you so much for this info.

[Q] Clean Rom

Hello everyone,
What exactly does Clean Rom do? How is it different from what comes with the phone stock? Will Clean Rom mess with the updates that are pushed to our phones? Any big differences between layout?
Sorry for all the questions. I'm just not familiar with modifying my phone.

Must read more. Spend as much time as you can reading in the dev section. Clean ROM removes all of the ATT bloat and adds functionality like the FM radio and remapping the 3 dot menu button that takes up screen real-estate to the recent apps softkey. The recent apps can be accessed by holding down the home button, like we're familiar with. It also has performance and battery tweaks (says so in the changelog, haven't been using it long enough to notice). I flashed it the day before yesterday and I'm liking it.
Sent from my HTC One X

Clean Rom doesn't use profane language, think of it as the Will Smith of Roms...
Sent from my HOX running WCX

Did you bother to go to the Development forum, and read the CleanROM threads? They very well describe the features of each version of CleanROM.
You don't ever want to install an OTA update once on a custom ROM. It won't be compatible. Either it won't install, or it will remove root, or it will totally bork the system. The devs typically keep their ROM updated to the newest firmware base, and often long before the OTAs go out. So there is virtually never a benefit to updating via OTA (even if it did work).

Most custom ROMs prevent you from even getting an update pushed in the first place. Kind of a non-issue there.
To the OP, if you want to flash custom, just do it. Spend a few days on Clean, try out Smokin's ROM, too. Just find something you like. Worst that can happen is you RUU back to stock.
Sent from my HTC One X using Tapatalk 2

SoberGuy said:
Most custom ROMs prevent you from even getting an update pushed in the first place. Kind of a non-issue there.
Click to expand...
Click to collapse
Depends on the device, and I believe the carrier (and maybe the custom ROM as you mentioned). I've gotten OTA notification, and even able to download OTA (didn't install it, just to see if it would actually download . . . some have said custom ROMs will prevent that too) on 2 previous HTC devices on custom ROMs. But one was a Canada Bell phone used on AT&T, and the other was the WiFi-only Flyer tablet. So it may be that AT&T somehow directly blocks OTA to rooted phones.

redpoint73 said:
Depends on the device, and I believe the carrier (and maybe the custom ROM as you mentioned). I've gotten OTA notification, and even able to download OTA (didn't install it, just to see if it would actually download . . . some have said custom ROMs will prevent that too) on 2 previous HTC devices on custom ROMs. But one was a Canada Bell phone used on AT&T, and the other was the WiFi-only Flyer tablet. So it may be that AT&T somehow directly blocks OTA to rooted phones.
Click to expand...
Click to collapse
I don't think att can see your on a custom ROM, it has to do with if the developer is able to include that ability or not.

Thank you for the replies!
I'm trying my best to understand how Clean Rom works. Is it the same thing as rooting a phone? Any disadvantages of using Clean Rom?
I'm just curious about how it works because I tried jailbreaking my iPhone and that made it very crash prone. It's a bad example but it's the reason why I never tried using custom software again but I'm interested in giving this a try. I only get about 2 hours screen time and about 12 hours of screen off time for my phone to die.
I did the HTC battery test and my phone went down to 92% so I'm pretty sure it's not the battery that's wrong with the phone.

RPTheLefty said:
I'm trying my best to understand how Clean Rom works. Is it the same thing as rooting a phone?
Click to expand...
Click to collapse
It appears you need to do more reading to get a better understanding or root, ROMs, etc.
Root is just a change of permissions on your phone. It allows the user and apps access to system files that are normally restricted. Nothing more, nothing less.
Clean ROM (or installation of any custom ROM) is a total replacement of the firmware or operating system of the phone (also called a "ROM"). Clean ROM in particular is mostly based on the latest stock firmware version, but cleaned up to remove bloat, optimizations to make it faster and smoother, and some cool added features. There are 3 different versions of CleanROM. Just read the threads for each version to learn the differences.
I don't really keep up with iPhone stuff. But my understanding is that jailbreaking adds functionality, but makes the system less stable.
Whether a custom ROM on Android makes the phone more or less stable depends on the ROM. Some are ported from other phones, to give new UI look or functions, but can be a bit buggy at first. But any good ROM will be stable once it reaches "maturity" and the bugs are worked out. They can be very stable, and even more stable and smoother than the stock ROM. Which is one of the points of running a custom ROM.
CleanROM in particular is based on stock firmware, just cleaned up. So its very stable. Just as stable as stock, a bit smoother in some places, and with some awesome added features. Any disadvantages? Not really. But you need to unlock the bootloader to install any custom ROM, which voids the warranty. nd flashing anything to the phone has the risk of damage if you don't follow the instructions properly. Thats the only downsides I can think of (for any custom ROM, not just for CleanROM).

Redpoint had an excellent summary.
If you're looking for battery life improvement, there are significant advantages to a custom ROM. Some will allow you to adjust the clock rate for the processors. So you can turn the up a bit (overclock) to get incredible performance, or you can turn them down a bit (underclock) to get better battery life.
If that's your main goal, I personally suggest Sick Sense from Smokingl337. He has incorporated this into his ROM, and the reports I've seen have been positive. I had used his ROM before, and I did like it. The day I flashed CleanROM due to a minor bug, Smokinl337 updated his ROM to fix that bug. Figures! But I'll be going back to Sick Sense pretty soon, I'm sure.
Hopefully you can find something that works for you.
Sent from my HTC One X using Tapatalk 2

Different kernel or different radio may also help battery life.
But you need to root, SuperCID, and unlock bootloader to do any of these things (including flashing custom ROMs). So head over to Development and start reading:
http://forum.xda-developers.com/showthread.php?t=1671237

There is also a clean rom developers edition that takes out most of the HTC sense... there is the cm9 alpha 4 rom that seems very stable...
Sent from my HTC One X using Tapatalk 2

OP, I was in your shoes last week. New to android/roms etc. I rooted, unlocked the bootloader and flashed Clean Rom. Just follow the instructions in the associated threads and you'll be fine.

AT&T One X not keeping accurate time

I've noticed that the clock on my HOX runs slow. I have it set to automatically update the time and time zone. After about a day it will be 8-10 minutes slow. If I reboot the phone, it appears to update the time with AT&T and correct itself. I've also set the time to not automatically update and set the time manually. By the next day, it will be off again. That means the issue is not that AT&T has their time set wrong.
I'm running the stock 1.73 ROM. I have rooted the phone, but done virtually nothing else.
Is there a parameter to set how frequently it syncs the internal clock with the carrier time signal?
Does anyone else have this same issue? If so, was it fixed in a newer ROM? I'm not having any other issues, so I have not been any hurry to upgrade.

DonS said:
I've noticed that the clock on my HOX runs slow. I have it set to automatically update the time and time zone. After about a day it will be 8-10 minutes slow. If I reboot the phone, it appears to update the time with AT&T and correct itself. I've also set the time to not automatically update and set the time manually. By the next day, it will be off again. That means the issue is not that AT&T has their time set wrong.
I'm running the stock 1.73 ROM. I have rooted the phone, but done virtually nothing else.
Is there a parameter to set how frequently it syncs the internal clock with the carrier time signal?
Does anyone else have this same issue? If so, was it fixed in a newer ROM? I'm not having any other issues, so I have not been any hurry to upgrade.
Click to expand...
Click to collapse
As far as I know, if you disable automatic time and turn off the phone the phone doesn't have internal clock, meaning if you reboot it will be out of sync. With automatic checked, I'm guessing it only syncs after every boot or when you get signal again.
Sent from my HTC One X using xda app-developers app

Someone else had a very similar issue. Not sure if they resolved it. I will try to find the thread and link it here.
Though, the first thing I would do in your case is update to the latest OTA if you want to stay stock.
Edit: Here's the link http://forum.xda-developers.com/showthread.php?t=1665559&highlight=clock Looks like updating did solve the issues. So go ahead and do that.

Thanks for the link. At least two people in that thread noted the issue was worse with the 1.73 ROM. I'll probably go through all the steps to change the CID to the SuperCID, upgrade to the 1.85 ROM, unlock the bootloaded, install a custom recovery, reroot, and remove bloatware. Then I'm set to use custom ROMs.
Since I'll void the warranty from AT&T I was waiting to make sure there weren't any quality issues with the phone. I also needed a real reason to upgrade. Since everything else was working fine, I was in no hurry to upgrade.

DonS said:
Thanks for the link. At least two people in that thread noted the issue was worse with the 1.73 ROM. I'll probably go through all the steps to change the CID to the SuperCID, upgrade to the 1.85 ROM, unlock the bootloaded, install a custom recovery, reroot, and remove bloatware. Then I'm set to use custom ROMs.
Since I'll void the warranty from AT&T I was waiting to make sure there weren't any quality issues with the phone. I also needed a real reason to upgrade. Since everything else was working fine, I was in no hurry to upgrade.
Click to expand...
Click to collapse
By the way, the order is root -> supercid -> unlock -> recovery (use TWRP) -> flash custom romzzz
You don't actually need to go to 1.85 the official way or through the RUU. You can just flash a custom rom directly from any version provided that you wipe.

stnguyen09 said:
By the way, the order is root -> supercid -> unlock -> recovery (use TWRP) -> flash custom romzzz
You don't actually need to go to 1.85 the official way or through the RUU. You can just flash a custom rom directly from any version provided that you wipe.
Click to expand...
Click to collapse
I was thinking of going to the stock 1.85 ROM only remove the bloatware instead of a custom ROM. The order I mentioned is documented in a how-to method posted on another thread. With the process I listed I can always go to a custom ROM later on.

CM10 Stable - Touchscreen not responding

Done a bit of research now and all the keywords I have searched through haven't returned any results of this particular issue.
I have flashed CM10 (Stable) to the XL, has installed and boots fine, however there is 0 feedback from the touchscreen so i can't use it at all.
I couldn't really find anyone else with a similar issue. Has anyone run into this, or know what may be causing it?
Have downloaded numerous times, different versions of twrp, everything's been cleared out/wiped (both before and after flash).
I'll add that I have not had this issue at all elsewhere, EXCEPT where yesterday I updated stock to the latest version to give it a go (was hoping for more of a JB experience...). In this case there is / was a bug with TWRP where if you installed Android 4.1 (Latest stock), the touch would no longer work in TWRP. Luckily the TWRP dev updated to 2.3.3.1 today, fixing the touch again (which some themes such as viper require). But I have no idea if any of this is related, shouldn't be though,given the rom should work standalone...
Any ideas would be great. I battled to overcome that damn TWRP mess (seen above) that I got myself into, then I got past a boot issue and now that I'm booted the damn touch doesn't work lol.
Hope to hear some good news,
regards.

Well known and posted about all over this forum.
HTC changed some firmware relating to the touchscreen in the 3.17 update. Roms require a kernel update to work. Twrp can cheat and just use htc's new kernel, cm10 build their kernel from source so could be hard to figure what changed until HTC release source.
-known issue, but only yesterday I told h8rift and Rohan who previously were unaware of the issue.
-The change is in firmware delivered with 3.17
-Requires kernel update to resolve issue.
-Twrp easy to fix.
-Cm and others not so easy and may require waitng for source from HTC.

twistedddx said:
Well known and posted about all over this forum.
HTC changed some firmware relating to the touchscreen in the 3.17 update. Roms require a kernel update to work. Twrp can cheat and just use htc's new kernel, cm10 build their kernel from source so could be hard to figure what changed until HTC release source.
-known issue, but only yesterday I told h8rift and Rohan who previously were unaware of the issue.
-The change is in firmware delivered with 3.17
-Requires kernel update to resolve issue.
-Twrp easy to fix.
-Cm and others not so easy and may require waitng for source from HTC.
Click to expand...
Click to collapse
Thanks for your reply. I just tried installing JellyBam now and alas the same issue, checking here confirms things
Can you recommend a Kernel that will work for the mean time? I was actually looking at some of the kernels, but didn't really go anywhere with it.

You can only use roms and kernels made from 3.17 for the time being.

twistedddx said:
You can only use roms and kernels made from 3.17 for the time being.
Click to expand...
Click to collapse
This sucks. I can't find a single rom/kernel that is compatible with whatever this 3.17 'thing' is (what's this the version of?). Can i roll back this version?
I can't even use the RUU to go back to stock because now the phone has blank version numbers and details and errors out.
My restores also don't work. Only JB roms actually boot now and all of them don't have any touch screen support. I AM able to get touch support if i install the ElementX JB kernel, however that then throws infinite "nfc and android.phone process-stop" messages (just after applications are being upgraded w/ the first boot of a JB rom).
Just looking to make the phone work
Playing around with Joker and have got the phone back into a working state. *phew*

xlmama said:
I can't find a single rom/kernel that is compatible with whatever this 3.17 'thing' is (what's this the version of?). Can i roll back this version?
I can't even use the RUU to go back to stock because now the phone has blank version numbers and details and errors out.
Click to expand...
Click to collapse
3.17 is the HTC build number of the OTA(Over The Air) update you accepted and installed on your phone. Your phone did tell you it was about to install 3.17 and the phone would have referred to it's software version as 3.17 if you had checked.
Currently there is no known way to downgrade the parts that need to be downgraded to restore things to how they were.
This ROM will work on your phone:
http://forum.xda-developers.com/showthread.php?t=2076361
Make sure to flash the boot.img from fastboot.
Extract the boot.img from the zip and do:
fastboot flash boot boot.img
As time goes on more Sense ROM's will be released based on 3.17 and newer anyways so will be less of an issue.
And for non-sense based things like CM eventually HTC will release the source to their kernel and an update to CM will fix the problem also.

twistedddx said:
3.17 is the HTC build number of the OTA(Over The Air) update you accepted and installed on your phone. Your phone did tell you it was about to install 3.17 and the phone would have referred to it's software version as 3.17 if you had checked.
Currently there is no known way to downgrade the parts that need to be downgraded to restore things to how they were.
This ROM will work on your phone:
http://forum.xda-developers.com/showthread.php?t=2076361
Make sure to flash the boot.img from fastboot.
Extract the boot.img from the zip and do:
fastboot flash boot boot.img
As time goes on more Sense ROM's will be released based on 3.17 and newer anyways so will be less of an issue.
And for non-sense based things like CM eventually HTC will release the source to their kernel and an update to CM will fix the problem also.
Click to expand...
Click to collapse
Thanks for your help. I'm now not clueless about my phones fate. :victory:

I have the same issue - updated to Andriod 3.17 about a week ago, and decided to flash CM10 afterwards. As a result, I am stuck with no touchscreen functionality.
Have there been any updates the past few days in terms of ROM's being released that will work on 3.17? How far into the future are we talking about before a release of CM10 will become available?
Is there no way to revert back to ICS and thus have a fully functioning version of CM10?

Is there any news on this issue ?

It's not possible until HTC releases kernel source. There's nothing the devs can do. You can only run sense roms
Sent from my VENOMized HoxL

twistedddx said:
3.17 is the HTC build number of the OTA(Over The Air) update you accepted and installed on your phone. Your phone did tell you it was about to install 3.17 and the phone would have referred to it's software version as 3.17 if you had checked.
Currently there is no known way to downgrade the parts that need to be downgraded to restore things to how they were.
This ROM will work on your phone:
http://forum.xda-developers.com/showthread.php?t=2076361
Make sure to flash the boot.img from fastboot.
Extract the boot.img from the zip and do:
fastboot flash boot boot.img
As time goes on more Sense ROM's will be released based on 3.17 and newer anyways so will be less of an issue.
And for non-sense based things like CM eventually HTC will release the source to their kernel and an update to CM will fix the problem also.
Click to expand...
Click to collapse
Not mine, tried it twice. The only ROM I've been able to get running is PA 2.54, and the only way I could get the touchscreen to work is by flashing the Kernal from Hatkas ROM. Even that fc'd NFC to the point repeatedly So I'm thinking if I can find [or get help finding] a 3.17.661 kernal that will work with PA, I'll be golden.

I think I may be having the same problem, though I don't remember ever upgrading to 3.17. Is what you all are seeing like the screen doesn't even turn on? It just stays black, but the power button and volume button seem to be responsive? I can't even seem to get into recovery or bootloader, and this all started when I flashed the latest CM10 nightly.

Never mind.

Magickalhack said:
Not mine, tried it twice. The only ROM I've been able to get running is PA 2.54, and the only way I could get the touchscreen to work is by flashing the Kernal from Hatkas ROM. Even that fc'd NFC to the point repeatedly So I'm thinking if I can find [or get help finding] a 3.17.661 kernal that will work with PA, I'll be golden.
Click to expand...
Click to collapse
You do realized you flashed a sense kernel for an aosp Rom?... And you're wondering why it gave you FC's?

I'm on hboot 1.09, did not do OTA update, and the touchscreen works on CM 10.1 90% of the time, but sometimes I open it up and it doesn't respond. Hitting the sleep button twice fixes it but it's annoying. Would the above fix do anything for me? What else could be the problem?

slash178 said:
I'm on hboot 1.09, did not do OTA update, and the touchscreen works on CM 10.1 90% of the time, but sometimes I open it up and it doesn't respond. Hitting the sleep button twice fixes it but it's annoying. Would the above fix do anything for me? What else could be the problem?
Click to expand...
Click to collapse
Do you use s2w? That causes that issue
Sent from my VENOMized HoxL

[Q] VZW M8 - Sunshine S-Off - CM12 / GPE / Custom ROMs

I need some assistance please! I am truly baffled by what I am experiencing and would like to know why and hopefully how to fix it. Here's the details:
CARRIER: Verizon
MODEL: HTC One M8
S-OFF: Yes (Sunshine)
ROOT: Yes
HBOOT: 3.19
RADIO: 1.09.20.0926
OpenDSP: 46.2.2
OS: 3.28.605.4
First off, sorry for the book, but I figured more details would be better at this point to figure out what is up, so I appreciate any assistance in advance! PS: I bolded the key items to the story for those that like to skim.
Prior to S-Off and Root, I was on OTA version 4.4.4 waiting in anticipation for 5.0 to come to my device. Was unsure about spending $25 for Sunshine's method, but finally decided to take the plunge. At first things seemed great and very smooth. Following all instructions from Sunshine I was finally with S-Off status. I then used WeakSauce2 to gain temp root of the Stock ROM so that I could install Flashify and TWRP. Rebooted and loaded up TWRP Recovery and completed the first Nandroid. SUCCESS! Next up was Titanium Backup and such and copied everything off to my computer for safe keeping. So far so good and then loaded up a few ROM files and whatnot to the External SD Card so I could start flashing a new ROM. Feeling good up to this point, but here's where the troubles begin...
I have had great success with CyanogenMod in the past on previous devices and always very pleased. I read CM12 for others was great and stable and performed well, so I decided to grab the latest CM12 Nightly and the GApps package. Did the normal Wipe / System Wipe for initial flash of a new ROM and then installed both ZIPs no problem. The ROM boots up and everything seems okay, only I do not have LTE at all, only 3G. I also tried the GPE rom by Digitalhigh and experienced the same thing! Restoring from Nandroid also did not fix LTE, so at this point I got worried I broke my phone somehow.
To make a long story short after lots of testing I found a fix for getting LTE back on my original ROM. I found the 4.4.4 RUU and placed the 1.7 GB zip file (0P6BIMG.zip) on the root of my external SD Card, booted into HBOOT and ran the update. It did it's thing and booted up into the Stock ROM. Still no LTE! So then I found a comment somewhere about once that is done, do a Factory Reset from HBOOT using the Stock Recovery and it is supposed to reset the NV Radio Partition, so I did this and when it booted back up, SUCCESS! I have LTE back.
Once that was done I can now flash GPE, (but unusable because SMS is not working for some reason... I am using Google Voice BTW), so I am back to my original 4.4.4 TWRP Recovered ROM. I tried just for kicks to see if after the "fix" if I could make CM12 work, but again will bring it down to an unworking LTE status. Rinse and repeat the "fix" and got LTE back and did Nandroid Recovery. I paid the money to get S-Off and Root access so I could enjoy the Custom ROM's, but now I feel I am stuck...
All that being said... Can someone please explain to me what is going on?? And is there any way I can fix this so I can use CM12 and have LTE, and even then some other ROMs? I will post in Digitalhigh's forum for resolution to the SMS issue, but I have never had this much trouble with a device before and do not know enough about the different partitions and how they work and such. Any assistance and advice is MUCH appreciated!
Thank you!

Nobody has any advise or explanation?

I don't know the version numbers you posted from you bootloader off the top of my head but did you update your firmware to one of the unofficial ones around before flashing one of the lollipop roms? Is so, are you sure it took completely as sometimes you have to flash it twice.
Alternatively you could wait for our official firmware to drop any minute now and have pretty good odds of working for you.

cntryby429 said:
I don't know the version numbers you posted from you bootloader off the top of my head but did you update your firmware to one of the unofficial ones around before flashing one of the lollipop roms? Is so, are you sure it took completely as sometimes you have to flash it twice.
Alternatively you could wait for our official firmware to drop any minute now and have pretty good odds of working for you.
Click to expand...
Click to collapse
Yes I did use official firmware, and flashed twice per recommendations. I have it working with GPE, but every time I flash CM12 it breaks LTE. I have seen articles and posts of others running CM12 on their M8's with VZW and stating "zero issues"... Lack of LTE sounds like an issue to me. So my big question at hand is, why does CM12 break LTE, and is there a fix? Everything else seemed to work great otherwise.

kjparenteau said:
So my big question at hand is, why does CM12 break LTE, and is there a fix? Everything else seemed to work great otherwise.
Click to expand...
Click to collapse
I was reading the CM12 m8 thread earlier this week and many reported that LTE did not work on builds from late Feb. early March. CM12 is in no way stable and results will vary from phone to phone. Even the speaker issues have not been fully resolved. Bummer, because I'd really like it to be more stable.
http://forum.xda-developers.com/htc...genmod-12-0-nightlies-htc-one-t2998070/page75

Thank you for your reply. Definitely wanting CM since I used to run that regularly on my older devices with no troubles at all. The speed and simplicity are what I am going for. Sense is okay, but the difference of less than 300 megs with CM compared to over a gig for stock is unreal. WAY less overhead.