Database Info

[Q] Can't Make Calls with Full Signal?

I'm new to the whole Android scene so let me know if I left out information and what not.
I'm currently running RCMix HD v5.9.3 and decided to flash my radio. I was using Radio_12.39.60.19_26.06.04.06_M - Cingular US 1.80.502.3 and every time I made a call, my phone beeps and then hangs up. I'll eventually make a call but its very annoying. I went ahead and flashed the suggested rom from this topic (Radio_12.28e.60.140f_26.04.02.17_M2_SF - HTC WWE 1.72.405.3 R2) and I thought that fixed the problem but it is starting to happen again and when I look down I will have almost full signal if not full.
Did I do something wrong while flashing it? Should I go back to stock?
All help is appreciated! Thanks

Did you do a backup (nandroid or otherwise) before loading the current ROM?
If so, you could start from there, restoring your backup and seeing if everything is fine. If you used either of the hack kits here, then the ROM you revert back to should be rooted and close to stock, meaning you have all of your basic functionality and can verify that the hardware is working.
Think back to when you installed your current ROM of choice - did you clear the cache and data when you did it? If not, then that could be a big part of your issue right there. Try reloading the ROM again after wiping cache and data.
You could also try a ROM closer to the stock ROM like ClearDroid - very nice one that I'm using at the moment, and the guys supporting it are active here and helpful with issues (though I myself haven't had any).
This would be my personal method of resolution - to pinpoint the issues and verify the source, be it hardware or software. Feel free to get a second (or more) opinion on this - I'm not "old hat" on the Android platform yet, but I have been tinkering with this and it doesn't seem like a phone that is terribly easy to brick.
Good luck with it, and post back with your resolution - maybe you can help someone else who's seeing the same issue.

The cell coverage in your area could be over loaded. Can you make calls at night or off peak without issues?

nightborne said:
Did you do a backup (nandroid or otherwise) before loading the current ROM?
If so, you could start from there, restoring your backup and seeing if everything is fine. If you used either of the hack kits here, then the ROM you revert back to should be rooted and close to stock, meaning you have all of your basic functionality and can verify that the hardware is working.
Think back to when you installed your current ROM of choice - did you clear the cache and data when you did it? If not, then that could be a big part of your issue right there. Try reloading the ROM again after wiping cache and data.
You could also try a ROM closer to the stock ROM like ClearDroid - very nice one that I'm using at the moment, and the guys supporting it are active here and helpful with issues (though I myself haven't had any).
This would be my personal method of resolution - to pinpoint the issues and verify the source, be it hardware or software. Feel free to get a second (or more) opinion on this - I'm not "old hat" on the Android platform yet, but I have been tinkering with this and it doesn't seem like a phone that is terribly easy to brick.
Good luck with it, and post back with your resolution - maybe you can help someone else who's seeing the same issue.
Click to expand...
Click to collapse
Thanks for the info. I'll do a backup and try going back to the rooted ROM I had with the hack kit later tonight. Thanks again for the ideas. I'm hoping something works *crosses fingers*

I was having the same issue as you when running cm7 or any gingerbread Tom using the stock radio. I ended up flashing a gingerbread radio and that solved the problem but now my upload speeds suck again :-(. Give it a shot
Sent from my rooted Inspire 4G using XDA App

I went ahead and wiped everything and basically went through the hack kit again to get root stock and everything seems to be working normally. I love the RCMix rom and will give start fresh from there and see if the same thing happens.
@nino313
I'll look at the gingerbread radio if things start messing up again.

[Q] PLEASE HELP!!! Cannot Boot Nexus S!!

Hi everyone,
I'm sorry I'm quite new to this, and I'm afraid I've gotten myself somewhat stuck with my Nexus S. Yesterday I managed to root it, install superuser, as well as clockwork mod. Today I wanted to try a new rom and after some attempts, it seems I no longer have any working roms on my phone. After much searching with no luck, I turn to you guys for your expertise.
So I am able to see fast boot upon pressing the volume up and power buttons, and am certainly able to choose recovery and get into clockwork mod. Within clockwork mod I can mount USB storage, so I can transfer roms to the internal SD card. I've tried 3 or 4 roms, some say they install correctly, others not, and after trying to boot after any installation I simply get stuck at the google screen with the lock image at the bottom. The only things I have "deleted" is wiped the data and cache. I have no idea, but I think I may have erased the bootloader image or something else that I should not have that is required.
I have a i9020a model (non-4g model I believe), can you pleeeeeeeeeeeeeaaaassee help me!! I just want to get back to gingerbread 2.3.6, and my phone back up and running the way it was. I've become quite nervous after some searching with some saying a resistor mod is needed on the hardware!!

Your okay cause you can get into fastboot and recovery so don't worry. Maybe the rom you downloaded is not for your phone. Did you make a nandroid backup before flashing the rom? If yes then go into backup and restore from clockwork recovery to go back to stock.
Sent from my A500 using Tapatalk

If you can get to recovery, just flash the stock image FOR YOUR PHONE. Then you can go through and reroot..don't worry, you'll get the hang of it.
Sent from my Nexus S using Tapatalk

So my phone is not "bricked" as they say?? I'm not in big trouble?
I did not make a nandroid backup What kind of image am I looking for and how do I install it on the phone? I know my phone is of the variant i9020a, but how am unsure of how much more specific I should be looking for.
Looking at the following post: http://forum.xda-developers.com/showthread.php?t=1063664.
Should I try installing the Android 2.3.6/GRK39F/UCKF1 Radio/KA3 Bootloader option?

Choose the latest 9020a version of the FULL ROM, which is what you have already have eyes on.

I've tried installing the file I mentioned above, but I get a status 7 error when trying to install, and the install is aborted.
Could I get some more assistance please? Can anyone point me to a correct, full rom? Or perhaps I'm installing it incorrectly, could someone be so kind to outline the correct steps to a proper install?
Edit: I think the above mentioned file is for a GSM model, I'm sure I have the CDMA version.
Also, somewhat good news. I managed to install the oxygen rom, but for the 4g version and installed fine with no errors, but I have no service. What does this indicate, as I still want to restore back to a factory version (non-4g) of gingerbread 2.3.6.

What CWM version do you have? Is it 3.0.0.0?
Also, if you have no service, it's likely that you downloaded a ROM with an incorrect radio.
Edit:
If you have CWM 3.0.0.0, make sure to download the latest version, found in this thread: http://forum.xda-developers.com/showthread.php?t=988686 (use 5023-cyan.img). You flash this the same way you did CWM previously, though in the terminal make sure you type out the 5023-cyan.img file name.
Next, download the stock ROM from this thread: http://forum.xda-developers.com/showthread.php?t=1063664. Simply look for your phone version, and you'll find the correct software variant.
Maybe you've fixed your phone already; if not, I hope this helps!
I wish you the best of luck. Oh, and through problems like these, you come to learn a lot more about your phone. That's what I've found, at least.

At the thread you mentioned above there is a version with a different radio, you might want to give that one a try.
You also said that you only wiped data and cache, so maybe you should do a full wipe before. Not doing that can sometimes lead to problems.
Sent from my Nexus S using XDA App

To be brief, the phone is up and running as brand new! Thank you so very much everyone. It seems the error was with CWM, as I was able to install and boot a 4g oxygen rom on my phone, I went into rom manager, and at the bottom of the list was an option to upgrade to 5.x. Installed the CWM update, wiped everything and was able to install the factory rom, no issues, and everything works just as I remember
I have most certainly learned more about my phone, and I am going to look at it as a rather stressful learning experience rather than a mistake on my part.
But a sincere thanks to everyone once again, I posted this at like 4am here and had a response within a few minutes, I was pulling my hair out haha!

Flashing to stock rom will help you out. You can get stock roms from Internet simply by searching in Google...
Sent from my Nexus S using XDA App

[Q] Flashing to stock - phone force closes process com.android.phone, help

Please bare with me since this is the first time having to post for an issue since I usually find an answer on your forums
So here's the situation.
I bought the photon q 4g lte from ebay and it came with the unlocked bootloader.
Needless to say it was with the stock ics and i tried to find a jellybean update because it wasn't taking the ota and ended up going with cyanogen since i had no problems before. However those phones i had before were with sim cards not cdma.
I found out i couldn't update prl or profile manually without having to do something on the pc.
So after searching left and right i found i could use rsl lite (I used 6.1.5) and eventually found the "stock" file from this post
http://forum.xda-developers.com/showthread.php?t=2095536&highlight=rsd+lite
I did the stock jellybean, got it to go through the process and it booted up with no errors.
However, when it boots into the os it pops up a force close on omadmclient_sprint_dataservice and eventually also on the process com.android.phone.
I tried putting it in airplane mode to see if the service error would go away but it didn't work for the process part crashing.
I tried re-flashing, deleting cache in recovery, doing a data/factory reset in recovery and the one time i was able to do a data factory reset within the settings menu.
I could not find anyone that said they had a rom that worked with sprint and updating prl within the rom, if anyone knows of one let me know and i will flash it through rsd.
Otherwise does anyone have an idea of what could be happening because googling the omadmclient part did not pull up anything specific and pulling up the process issue for other phones has not helped me either.

Was this a hacked GSM phone, or are you using it as CDMA?
I've never heard of people having FC issues after flashing a FXZ from RSD. Which one did you flash? Android 4.1.2 - Sprint US - 9.8.2Q-122_XT897_FFW-5 (No simlock) ?
If you are on stock, you should be able to update the PRL within the ROM.

I was trying to use it with cdma network through sprint. and yeah that was the file i downloaded, had to remove the getvar to get it working but flashed with no errors after doing that.
As for updating the prl i can barely navigate through the phone, there is no home page loading and the process pop comes up often enough that its hard to go through the settings

crispy6 said:
I was trying to use it with cdma network through sprint. and yeah that was the file i downloaded, had to remove the getvar to get it working but flashed with no errors after doing that.
As for updating the prl i can barely navigate through the phone, there is no home page loading and the process pop comes up often enough that its hard to go through the settings
Click to expand...
Click to collapse
Sounds like something went wrong mate. Are you already activated on Sprint? I don't know if that would matter, it might.
I would honestly redownload and redo the RSD process.

arrrghhh said:
Sounds like something went wrong mate. Are you already activated on Sprint? I don't know if that would matter, it might.
I would honestly redownload and redo the RSD process.
Click to expand...
Click to collapse
I originally tried to activate the phone through cyanogen and then when the rep said he couldnt do it because of the lack of prl to update within the rom we just setup the activation back on the old phone/ That phone is working on the network.
I re-downloaded the file just in case and re-flashed but same problem. The only thing i thought of was maybe updating the radio but since its a stock rom it should work out of the gate. whats also weird is i tried turning wifi on but it didnt work either.
Anychange you know of a rom that works with sprint. I dont care if its stock since i would probably root later again.

crispy6 said:
I originally tried to activate the phone through cyanogen and then when the rep said he couldnt do it because of the lack of prl to update within the rom we just setup the activation back on the old phone/ That phone is working on the network.
I re-downloaded the file just in case and re-flashed but same problem. The only thing i thought of was maybe updating the radio but since its a stock rom it should work out of the gate. whats also weird is i tried turning wifi on but it didnt work either.
Anychange you know of a rom that works with sprint. I dont care if its stock since i would probably root later again.
Click to expand...
Click to collapse
Which one are you flashing?
Try another perhaps...? I honestly have never heard of this. It sounds like the phone might be damaged, or the RSD process just did not flash correctly.
I guess I should ask, was the phone modified at all for the GSM SIM slot mod? I wonder if having a non-Sprint SIM in is messing with it... That is just a shot in the dark.

arrrghhh said:
Which one are you flashing?
Try another perhaps...? I honestly have never heard of this. It sounds like the phone might be damaged, or the RSD process just did not flash correctly.
I guess I should ask, was the phone modified at all for the GSM SIM slot mod? I wonder if having a non-Sprint SIM in is messing with it... That is just a shot in the dark.
Click to expand...
Click to collapse
so far the only rom i tried was 10.1 cyanogen and the stock rom for jellybean. However for the stock rom it doesnt let me downgrade to ics with rsd 6.1.5 do you think if i downloaded an old version i could downgrade to a lower stock rom?
Also I honestly had not looked for the cdma roms since most of what i saw was troubleshooting related for this phone but i just saw this rom -AOKP 4.2.2 (Android Open Kang Project) (CDMA&GSM) that you created - http://forum.xda-developers.com/showthread.php?t=2293892
I re-rooted and installed that one and it looks great, just wondered how you got sprint to activate the phone or if you had done it before changing the rom? Also how would the prl and profile be updated.
Lastly the wifi wasn't turning on this time either, it did work initially when i got the phone so that has me stumped.

crispy6 said:
so far the only rom i tried was 10.1 cyanogen and the stock rom for jellybean. However for the stock rom it doesnt let me downgrade to ics with rsd 6.1.5 do you think if i downloaded an old version i could downgrade to a lower stock rom?
Also I honestly had not looked for the cdma roms since most of what i saw was troubleshooting related for this phone but i just saw this rom -AOKP 4.2.2 (Android Open Kang Project) (CDMA&GSM) that you created - http://forum.xda-developers.com/showthread.php?t=2293892
I re-rooted and installed that one and it looks great, just wondered how you got sprint to activate the phone or if you had done it before changing the rom? Also how would the prl and profile be updated.
Lastly the wifi wasn't turning on this time either, it did work initially when i got the phone so that has me stumped.
Click to expand...
Click to collapse
To downgrade to ICS, you need to remove some additional lines. See this post for more information on that.
However, you should be able to update the PRL on either stock ROM.
I think I said this before, but I will say it again. You need to do PRL updates, activate the phone, and get EVERYTHING working on stock BEFORE you flash ANY custom ROM. This is just standard practice - you don't want to put the cart before the horse! Get the phone working, then play with custom ROM's.

Something stupid

I think i did something stupid. Yesterday I decided to upgrade de modem/radio on my Note 3 running on ProBAM 1.3.3. I flashed CP-modem-NE6.tar. I was on CP_N9005XXUENC2.tar.md5 radio/modem with bootloader BL_N9005XXUEND6.tar. I was using the normal kernel which came with the rom.
After this update everything seemed to work okay. Until I decided to make a phonecall. Then my phone got hung up and I had to reboot. After the reboot the calling issue was not fixed. I tried flash back to my former radio/modem but that didn't work as well. Only mobile internet 3G/4G/HSDPA works and my phone has signal, but i cannot receive calls (i dont hear a ringtone) and make calls myself.
So I decided to make a full wipe of system, data, sdcard and start from scratch with a full Samsung Stock rom. I used this one: N9005XXUEND3_N9005PHNEND1_N9005XXUENC2_HOME.tar.md5. PHN is the CSC code for The Netherlands. The rom installs fine in Downloading Mode. After installing i went to the stock recovery and did a system reset/wipe and cleared the cache partition. Then the rom booted fine. What is strange is that i dont hear the standard bootsound during booting. For me this was a clue that something is not good. I still can't receive and make calls and my phone don't function anymore like it should. The sound buttons react very slow, camera doesn't work anymore. The samsung music app makes my phone to hang etc.
Has anyone have a clue on what can be wrong and how to correct it?

TheWizzard2203 said:
I think i did something stupid. Yesterday I decided to upgrade de modem/radio on my Note 3 running on ProBAM 1.3.3. I flashed CP-modem-NE6.tar. I was on CP_N9005XXUENC2.tar.md5 radio/modem with bootloader BL_N9005XXUEND6.tar. I was using the normal kernel which came with the rom.
After this update everything seemed to work okay. Until I decided to make a phonecall. Then my phone got hung up and I had to reboot. After the reboot the calling issue was not fixed. I tried flash back to my former radio/modem but that didn't work as well. Only mobile internet 3G/4G/HSDPA works and my phone has signal, but i cannot receive calls (i dont hear a ringtone) and make calls myself.
So I decided to make a full wipe of system, data, sdcard and start from scratch with a full Samsung Stock rom. I used this one: N9005XXUEND3_N9005PHNEND1_N9005XXUENC2_HOME.tar.md5. PHN is the CSC code for The Netherlands. The rom installs fine in Downloading Mode. After installing i went to the stock recovery and did a system reset/wipe and cleared the cache partition. Then the rom booted fine. What is strange is that i dont hear the standard bootsound during booting. For me this was a clue that something is not good. I still can't receive and make calls and my phone don't function anymore like it should. The sound buttons react very slow, camera doesn't work anymore. The samsung music app makes my phone to hang etc.
Has anyone have a clue on what can be wrong and how to correct it?
Click to expand...
Click to collapse
Short Story - Modem Should match the rest of the firmware. Flash the Stock NE6 Full rom which you pulled out the Modem from. Things should be back to normal. Made the Same Mistake with NE3. Dont flash and try to fix it in another way, You might lose the IMEI resulting in a visit to the Service Center.
P.S - Some "wannabe" will point out that this post needs to be in the Q&A Section soon.

Problem is that i only have that modem file CP-modem-NE6.tar and flashed that onto my existing rom. I don't even know which stock rom it was pulled from. To test I just flashed N9005DXUENE3_N9005OLCENE4_N9005DXUENE2_HOME.tar.md5 but nothing has changed about this problem. What is the next step?
JazonX said:
Short Story - Modem Should match the rest of the firmware. Flash the Stock NE6 Full rom which you pulled out the Modem from. Things should be back to normal. Made the Same Mistake with NE3. Dont flash and try to fix it in another way, You might lose the IMEI resulting in a visit to the Service Center.
P.S - Some "wannabe" will point out that this post needs to be in the Q&A Section soon.
Click to expand...
Click to collapse

TheWizzard2203 said:
Problem is that i only have that modem file CP-modem-NE6.tar and flashed that onto my existing rom. I don't even know which stock rom it was pulled from. To test I just flashed N9005DXUENE3_N9005OLCENE4_N9005DXUENE2_HOME.tar.md5 but nothing has changed about this problem. What is the next step?
Click to expand...
Click to collapse
Flashing NE3 wont solve your problem. Find the NE6. You might get lucky in samfirmware.com

JazonX said:
P.S - Some "wannabe" will point out that this post needs to be in the Q&A Section soon.
Click to expand...
Click to collapse
Those "Wannabes" would be right and because of Guys like you, these "Wannabes" that could easily help out doesn't care about others people's Phones anymore...
Gesendet von meinem SM-N9005

TheWizzard2203 said:
I think i did something stupid. Yesterday I decided to upgrade de modem/radio on my Note 3 running on ProBAM 1.3.3. I flashed CP-modem-NE6.tar. I was on CP_N9005XXUENC2.tar.md5 radio/modem with bootloader BL_N9005XXUEND6.tar. I was using the normal kernel which came with the rom.
After this update everything seemed to work okay. Until I decided to make a phonecall. Then my phone got hung up and I had to reboot. After the reboot the calling issue was not fixed. I tried flash back to my former radio/modem but that didn't work as well. Only mobile internet 3G/4G/HSDPA works and my phone has signal, but i cannot receive calls (i dont hear a ringtone) and make calls myself.
So I decided to make a full wipe of system, data, sdcard and start from scratch with a full Samsung Stock rom. I used this one: N9005XXUEND3_N9005PHNEND1_N9005XXUENC2_HOME.tar.md5. PHN is the CSC code for The Netherlands. The rom installs fine in Downloading Mode. After installing i went to the stock recovery and did a system reset/wipe and cleared the cache partition. Then the rom booted fine. What is strange is that i dont hear the standard bootsound during booting. For me this was a clue that something is not good. I still can't receive and make calls and my phone don't function anymore like it should. The sound buttons react very slow, camera doesn't work anymore. The samsung music app makes my phone to hang etc.
Has anyone have a clue on what can be wrong and how to correct it?
Click to expand...
Click to collapse
Did you write only the modem or you also wrote NON-HLOS.bin? Also sometimes it is said that you also need to flash the corresponding RIL.

I wrote both files. First modem.bin and then took out the battery, replaced it and booted to download mode again and flashed non-hlos.bin and again pulled the battery, put it back and booted the rom.
xclub_101 said:
Did you write only the modem or you also wrote NON-HLOS.bin? Also sometimes it is said that you also need to flash the corresponding RIL.
Click to expand...
Click to collapse

Until you get on a NE6 firmware (Same version the Modem CP was pulled from), Nothing else will help. I went through this path. It was a headache Mate. However NE6 Firmware is not that bad. Just the uneasy feeling that It's not XX, but a DX.
HSD-Pilot said:
Those "Wannabes" would be right and because of Guys like you, these "Wannabes" that could easily help out doesn't care about others people's Phones anymore...
Gesendet von meinem SM-N9005
Click to expand...
Click to collapse
Sorry Mate, Obviously didn't meant to hurt your feelings. It was a random thought which I dedicated to a few "certain users" who reply - "this should be in Q&A" without answering the poor soul's question.
Some time ago here in XDA, In a situation like this, First we see the answers, then a moderator silently moves this to Q&A and put up a warning to the bloke who made the mistake. Unfortunately nowadays, just as soon as people see the thread is in the wrong section, they just bark as if they suddenly turned blind to the problem OP is having. Mistakes are not made purposely, and obviously these are people who's new to forum.
I went through the same problem by jumping to the NE6 modem a few days ago. So I know how this agony feels.
Man kann die Natur nicht ändern.

No one can hurt my feelings in an Forum, so no prop
The point is, the Rules are sticked on top >
http://forum.xda-developers.com/showthread.php?p=46416908
So when i'm new on an Forum the first thing should be reading and respecting these.
I was Mod in an German Smartphone Forum (Handy-Faq) and i know it's an pain in the ass always remembering people to follow the rules and move unmatched stuff into the right sections. Mods usually don't get paid and doing this in her Freetime. They're trying to provide and clean Forum and this takes a lot of time, especially in such an huge Forum like XdA.
So it shouldn't be that hard to take the time and read at least the sticked Stuff, before posting...
Just think, you're coming home from work and open the Forum. The first thing you'll have to do is to go through the Threads and move this and that, simply because it's posted wrong or there's already an Thread about it. For Example there are meanwhile a couple of Threads about this Problem in Q&A. So I instead of helping people you used 30min or more to clean the Threads.
Gesendet von meinem SM-N9005

The problem is that on Sammobile.com i only can find firmware version N9005ZHUENE6 and i cannot get this firmware to flash correctly to the phone. It keeps telling the the system partition cannot be written because it doesn't match the phone orso...

TheWizzard2203 said:
The problem is that on Sammobile.com i only can find firmware version N9005ZHUENE6 and i cannot get this firmware to flash correctly to the phone. It keeps telling the the system partition cannot be written because it doesn't match the phone orso...
Click to expand...
Click to collapse
ZH Series is for Hongkong. Hong Kong N9005 is 16GB, so yeah It will not flash to the 32GB version.
Check the thread where you found the Modem from, The Link for the Rom will be there.

Stupid thing and together lucky is that i just flashed the NE4 radio and all seems to be back to normal again. Phone is again fast and everything seems to work again. Now I have to test with making calls.
Will report back later this evening.

[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.