Database Info

[Q] Nexus S No SIM Error (AT&T)

Couldn't find this anywhere so I thought I would ask....
I've had the White Nexus S w/ AT&T 3G Bands for a week or so now and it's been great. Running CM7 with custom kernel and all is good. For what ever reason it started giving me the "No SIM" error. I have no idea why this just happened all of the sudden like this. Anyways, AT&T was kind enough to give me a new SIM and this issue just will not go away.
I'm out of ideas on this...
Any suggestions?

freebirds87 said:
Couldn't find this anywhere so I thought I would ask....
I've had the White Nexus S w/ AT&T 3G Bands for a week or so now and it's been great. Running CM7 with custom kernel and all is good. For what ever reason it started giving me the "No SIM" error. I have no idea why this just happened all of the sudden like this. Anyways, AT&T was kind enough to give me a new SIM and this issue just will not go away.
I'm out of ideas on this...
Any suggestions?
Click to expand...
Click to collapse
I'm not sure if this will work, but try to go back to stock, and see if it's works.
I'm a Vibrant user, so I have no idea how you would do this (least I won't until Wednesday, when I get the Nexus S 4G from Sprint), but try that, may fix your problem.

Longcat14 said:
I'm not sure if this will work, but try to go back to stock, and see if it's works.
I'm a Vibrant user, so I have no idea how you would do this (least I won't until Wednesday, when I get the Nexus S 4G from Sprint), but try that, may fix your problem.
Click to expand...
Click to collapse
I'm having a very difficult time locating the stock firmware for the i9020a

Flashed back to stock and the NO SIM error still exist...
I really hope this issue isn't hardware related...

freebirds87 said:
Flashed back to stock and the NO SIM error still exist...
I really hope this issue isn't hardware related...
Click to expand...
Click to collapse
did you flash a new radio? i had problems with the kb3 radio (lost 3g after a week of use) went back to kb2 and all was good.
also possible, check your apn settings

ogdobber said:
did you flash a new radio? i had problems with the kb3 radio (lost 3g after a week of use) went back to kb2 and all was good.
also possible, check your apn settings
Click to expand...
Click to collapse
Bootloader shows the Radio version to be: I9020UCKB2
It even shows the carrier info to be ATT
What should the APN settings be for AT&T?

Borrowed the APN settings off of a Bravo here inside the store and and when I save the settings it doesn't list the APN like it should. I am saving the settings but it doesn't show after its saved.
Uuugggghhhh...

Now I'm having issues with flashing the stock radio...
Here's what the device is telling me:
"Verify Image (RADIO) ... Fail
And of course cmd prompt just shows where the write failed. I am using the radio file found here: http://forum.xda-developers.com/showthread.php?t=1033269
I'm just simply extracting the radio img from that zip and using fastboot to apply.

freebirds87 said:
Now I'm having issues with flashing the stock radio...
Here's what the device is telling me:
"Verify Image (RADIO) ... Fail
And of course cmd prompt just shows where the write failed. I am using the radio file found here: http://forum.xda-developers.com/showthread.php?t=1033269
I'm just simply extracting the radio img from that zip and using fastboot to apply.
Click to expand...
Click to collapse
flash this radio from clockwork recovery

ogdobber said:
flash this radio from clockwork recovery
Click to expand...
Click to collapse
Flashed fine thanks for the zip!
The baseband version is still the same though and the SIM Card error still exist.

freebirds87 said:
Flashed fine thanks for the zip!
The baseband version is still the same though and the SIM Card error still exist.
Click to expand...
Click to collapse
hmmm weird. have you tried swapping sim cards?

ogdobber said:
hmmm weird. have you tried swapping sim cards?
Click to expand...
Click to collapse
Yeah I have. I received a brand new one from AT&T when this first started.
I've given up on fixing this device. I contacted Negri Electronics and asked for an RMA. This unit has to be a lemon. This will make the first time I've ever had to send a phone back. Hopefully the replacement will be a better unit.

[Help] HTC One S stuck on EDGE after S-offing

I seem to have somehow messed up my HTC One S's radio while S-off'ing my phone: its now stuck on EDGE. I followed all the steps exactly, but after completing everything, I noticed that my phone wouldn't connect to 3G/UMTS anymore. I know that it isn't a hardware problem as it can occasionally latch onto a 3G signal, but everytime it did, it would have full bars, then the strength would change to 0 dBm and 99 asu, where it would then proceed to switch over to EDGE and signal strength would return to normal.
So I ended up reflashing my ROM, relocking my bootloader, RUU-ing my phone, S-on'ing my phone, trying multiple different RUUs... and nothing works.
Also, there's nothing wrong with my network, as my brother with a separate phone on the same network has no problems. I've even tried his SIM card, but that also gets placed only on EDGE.
Does anyone have any insight on what is wrong with my phone?
Edit: attached the logcat to the OP, and this is when I put my phone on 3G only mode: connects to UMTS:3, however cannot get a data connection, then disconnects and loses the signal.

Yea i had this problem to with cm 10.1 aamd did everything trying to fix and yesterday i flashed pacman room and 3g and 4g works. You can try flashing that Rom.
Sent from my One S

Thanks for the reply, I've just tried it your suggesting, but unfortunately it's still not working
I guess I'll just leave my phone to run by itself for a while, and hope that it 'clicks' and 3G comes back like what the person in the other thread said happened for him/her.

You check to see if your provider is doing maintenence or if there is an outage?
Sent from my HTC VLE_U using xda premium

My brother is on the same network, but he has full 3G signal on his phone, so there definitely is no outage.

JN3141 said:
My brother is on the same network, but he has full 3G signal on his phone, so there definitely is no outage.
Click to expand...
Click to collapse
Are you sure you haven't toggled the network data off under the quick settings panel?
Regards,
Opentang

I'm not quite sure how if data is enabled or not would affect it, as my phone can't even connect to the 3G network. It can, however, get data on the 2G network.
Tapatalked from my HTC One S running CM10

I have just been able to get around to a computer, and have grabbed a logcat of what happens when I switch my phone to 3G only mode and it just disconnects itself from the network (i.e. goes into UNKNOWN:0 mode)
If anyone could look through it and see what could possibly be wrong with my phone, it would be highly appreciated.
The main error I can see myself is the:
Code:
[main] qcril_qmi_voice_nas_control_convert_radio_tech_to_radio_tech_family: invalid radio tech = 0
But then I'm not exactly literate at logcat.
Thank you in advance to anyone who could at least look through it and help me out at least a little bit here. (Yes, it's a .rar file as the file size exceeded the upload size limit)

JN3141 said:
I have just been able to get around to a computer, and have grabbed a logcat of what happens when I switch my phone to 3G only mode and it just disconnects itself from the network (i.e. goes into UNKNOWN:0 mode)
If anyone could look through it and see what could possibly be wrong with my phone, it would be highly appreciated.
The main error I can see myself is the:
Code:
[main] qcril_qmi_voice_nas_control_convert_radio_tech_to_radio_tech_family: invalid radio tech = 0
But then I'm not exactly literate at logcat.
Thank you in advance to anyone who could at least look through it and help me out at least a little bit here. (Yes, it's a .rar file as the file size exceeded the upload size limit)
Click to expand...
Click to collapse
Have you tried to flash a new radio?

dc211 said:
Have you tried to flash a new radio?
Click to expand...
Click to collapse
Tried using the radio installer in the Development section: it changes the radio but doesn't fix the problem. Unless someone has a radio.img and some instructions on how to flash it?
Edit: okay, managed to grab a radio.img from the Sense Radio Installer. But I can't install it through fastboot flash radio radio.img even when I'm s-off'd. But a quick question on this: would flashing the radio like this affect CM?

JN3141 said:
Tried using the radio installer in the Development section: it changes the radio but doesn't fix the problem. Unless someone has a radio.img and some instructions on how to flash it?
Edit: okay, managed to grab a radio.img from the Sense Radio Installer. But I can't install it through fastboot flash radio radio.img even when I'm s-off'd. But a quick question on this: would flashing the radio like this affect CM?
Click to expand...
Click to collapse
Wow you got a interesting problem. You shouldn't have a problem using fastboot to flash a radio. What error does it give you?
It may or may not effect your phone if you're using CM10. Hardware wise the phone uses the radio installed to it. Software wise in CM10 it doesn't so there can be an effect. But since you've done several RUU's and I assume it still not working on the stock sense rom you can rule that out.
The cover on the bottom of the phone is where the cell antenna's are any chance you dropped your phone or the bottom took an impact?
Dial *#*#4636#*#* and select phone info. Then scroll down a little bit so we can't see your phone number & imei and take a screen shot. Post that here and let's see what it says. Try to take one with WCDMA preferred and WCDMA only.
Also, can you tell us what country and phone provider you have? Have you checked with your provider to see if there are any issues with your account? Did you buy the phone second hand (ebay or from someone else) or from a cell phone store?

Lol, wtf are you telling him to post his phone number and imei for?
HTC_One_S | Xparent_ICS_Blue_Tapatalk 1.06_Hboot_Downgrade | Root_Box_ROM | Komodo_Kernel | S-OFF

dc211 said:
Wow you got a interesting problem. You shouldn't have a problem using fastboot to flash a radio. What error does it give you?
It may or may not effect your phone if you're using CM10. Hardware wise the phone uses the radio installed to it. Software wise in CM10 it doesn't so there can be an effect. But since you've done several RUU's and I assume it still not working on the stock sense rom you can rule that out.
The cover on the bottom of the phone is where the cell antenna's are any chance you dropped your phone or the bottom took an impact?
Dial *#*#4636#*#* and select phone info. Then scroll down a little bit so we can't see your phone number & imei and take a screen shot. Post that here and let's see what it says. Try to take one with WCDMA preferred and WCDMA only.
Also, can you tell us what country and phone provider you have? Have you checked with your provider to see if there are any issues with your account? Did you buy the phone second hand (ebay or from someone else) or from a cell phone store?
Click to expand...
Click to collapse
The error I get when I try to flash the radio is:
Code:
FAILED (remote: not allowed)
However, when I flash an RUU, the radio version does change, so I'm not sure what's going on there.
As for the screenshots, the first pic is the WCDMA preferred, the second is the WCDMA only, where it has the inital connection to the 3G network, and the third and last one is after it errors out on WCDMA only (gives unknown).
I bought this phone brand new and imported from overseas from an only cell phone store because the S4 version doesn't exist where I live, so as such claiming warranty isn't exactly going to work, hence I'm seeking help like a madman. My phone can still operate the 3G, as it can connect to the network at all, but then it drops the signal and errors. I'm on amaysim in Australia, which operates off the Optus network over here, but there isn't anything wrong with my account, as my SIM card in my brother's phone can get 3G.
On another note: can you understand what's going on in my logcat? or if not, know anyone who can? It might have some information as to how my phone is stuffing up.

I didn't have a detail read of your posts, least look at the logcats. So I'm guessing. I'd put money this is a radio firmware issue. I think if you install this 'RUU' ( radio firmware + config ) it will work http://forum.xda-developers.com/showthread.php?t=2157841 - some nitty gritty examples on page4.
I had a similar problem after going S-OFF, it triggered a mistake I made some days or weeks earlier messing around with firmware -> no radio at all. I also noticed only 3G on Optus (using an Amaysim ) until I updated my baseband.

Did you figure anything else out? Because I am suffering from the same problem unfortunately :/ I've already tried flashing different firmware and radios
Sent from my HTC One S using xda app-developers app

bluebenno said:
I didn't have a detail read of your posts, least look at the logcats. So I'm guessing. I'd put money this is a radio firmware issue. I think if you install this 'RUU' ( radio firmware + config ) it will work http://forum.xda-developers.com/showthread.php?t=2157841 - some nitty gritty examples on page4.
I had a similar problem after going S-OFF, it triggered a mistake I made some days or weeks earlier messing around with firmware -> no radio at all. I also noticed only 3G on Optus (using an Amaysim ) until I updated my baseband.
Click to expand...
Click to collapse
Well, I tried your suggestion, using the codf4ther's method, outlined here:
1.) Download the OTA from here: http://fotadl.htc.com/OTA_Ville_U_I...2.35.531.7_release_306848u5s8i4b18xs094yw.zip
2.) Unzip this file (the OTA) and the internal zip file called firmware.zip
3.) Edit the android-info.txt file from the firmware.zip in Notepad++ (or similar text editor) and add "DelCache:1" at the end of the file. This might not be necessary, but I did it on mine.
4.) Create a new zip file that contains only the following files, give it a name less than 8 characters (eg newhboot.zip). rcdata.img and wcnss.img might not be necessary, but from what I've read they go along with the radio, so I included them.
android-info.txt
hboot_ville_1.14.0005_signedbyaa.nb0
radio.img
rcdata.img
wcnss.img
5.) Connect your phone to your computer. Execute the following commands in fastboot. If you get an error that says "FAILED (remote: 90 hboot pre-update! please flush image again immediately)" after the "flash zip" command just do it again..
fastboot oem rebootRUU
fastboot flash zip newhboot.zip
fastboot oem boot
6.) If you're on a Sense Jelly Bean rom your wifi will most likely be broken at this point. Find the wifi fix for JB roms in the dev forum and flash it in recovery.
Click to expand...
Click to collapse
But unfortunately it didn't work: it's still stuck on EDGE, although if I put it on 3G only, it can hang onto the UMTS:3 status (sometimes) for a little while, although it's 'Out of Service,' but then it would go become UNKNOWN:0. I'm guessing this method is similar to flashing a radio through an RUU (?), but considering that an RUU didn't work... yeah...
leald said:
Did you figure anything else out? Because I am suffering from the same problem unfortunately :/ I've already tried flashing different firmware and radios
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
So we're in the same boat then. And unfortunately no, haven't gotten anywhere; we seem to have gotten a very bad stroke of luck.

JN3141 said:
Well, I tried your suggestion, using the codf4ther's method, outlined here:
But unfortunately it didn't work: it's still stuck on EDGE, although if I put it on 3G only, it can hang onto the UMTS:3 status for a little while, although it's 'Out of Service,' but then it would go become UNKNOWN:0. I'm guessing this method is similar to flashing a radio through an RUU (?), but considering that an RUU didn't work... yeah...
So we're in the same boat then. And unfortunately no, haven't gotten anywhere; we seem to have gotten a very bad stroke of luck.
Click to expand...
Click to collapse
Well this is kind of annoying...
:/
Sent from my HTC One S using xda app-developers app

I am not sure if this is relevant but I had pretty much same behavior after 4.0.4 Update .. the phone showed 3g for a while but defaults back to Edge connection .... I do not have a solution yet....

Hey guys,
I believe I have exactly the same problem. My phone randomly disconnects from mobile data on wcdma only & gsm / wcdma auto. Apparently only GSM only is working properly. I'm not using a custom RUU.
I'd like to add that the E, H, G, 3G symbols are displayed in the status bar even ater the disconnection occurs. Furthermore it does not display my phone number in settings. I noticed that the likelihood of a disconnect depends on the area (and thus perhaps on the strength of the signal).

Seems like a slightly different problem to me, mine can't stay connected at all on 3G only, and no 3G or H icons come up cuz it can't get on 3G. However I can get on EDGE data, which is really, really slow. :/
leald said:
Well this is kind of annoying...
:/
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
You can say that again
Tapatalked from my HTC One S running CM10

Constant Switching from 4g/3g/edge

So I have used TMOUS rom for ALONG time and recently decided to switch to use Cyanogen being a fan of it form other platforms.
While on the TMOUS rom I had 4g connectivity in my area about 90% of the time with the occasional drop into 3g here and there. It always displayed a 4g image in the top.
When I switched to Cyanogen that pretty much stoped. It always says 3g and is slow as hell. every once in awhile it will say H+ but not for long. MOST of the time it is constantly switching between 3g/4g/edge then shutting off.
Now im not sure if its a rom problem or not, but its making me want to switch back to a TMOUS rom.
Any suggestions would be great!
Edit: Just for clairification, I am S-On

I have this problem as well. I even ran the ruu back to stock and it is still happening. Please and thank you!

cp101 said:
I have this problem as well. I even ran the ruu back to stock and it is still happening. Please and thank you!
Click to expand...
Click to collapse
Damn, this scares me.... any solution anyone?

I'm thinking it might be a hardware error at this point. I might just "lose my phone" or just flash to stock and return it, this is preposterous.

cp101 said:
I'm thinking it might be a hardware error at this point. I might just "lose my phone" or just flash to stock and return it, this is preposterous.
Click to expand...
Click to collapse
Unfortunately, it doesn't seem to be a hardware problem
I have been trolling the net for weeks but have not found a solution yet.
I've posted in threads here but no solution.....
My issues started when I went to CM ROM - I used to have great 4g all the time before I went to custom rom (I was on stock TMO US) .. Now no matter what I do, I am not able to get 4G again.... it's really irritating...
I've tried a bunch of custom ROMS.. I am on 1.13 HBOOT and S-ON .. .. CID = HTC__001 (originally my CID was stock TMO US CID whatever that is but now its not that.. I don't wan to run RUU because I don't have TMO US CID and dont want to brick my phone)

You can set your CID back easily with the All in One ToolKit found here.http://www.hasoon2000.info/getdownload.php?file=One%20S/One_S_All-In-One_Kit_v4.0.rar
That is not the problem, unfortunately. It just doesn't make much sense, whatever the problem is; and especially considering after a full RUU restock. That has always fixed whatever mess I have created in the past.

This rom should fix your problem. Dont forget to clear storage from bootloader. It will erase everything thoug. And follow the steps under show contents link.
http://forum.xda-developers.com/showthread.php?t=2250573

cp101 said:
You can set your CID back easily with the All in One ToolKit found here.http://www.hasoon2000.info/getdownload.php?file=One%20S/One_S_All-In-One_Kit_v4.0.rar
That is not the problem, unfortunately. It just doesn't make much sense, whatever the problem is; and especially considering after a full RUU restock. That has always fixed whatever mess I have created in the past.
Click to expand...
Click to collapse
I not sure if its a CID problem. The only thing I ever did was upgrade to the newest Hboot and load in the CM rom. even going back to the TMOUS rom does not fix the problem.
Its so bad, and never on 4g that im considering getting a new phone.

bnd10706 said:
I not sure if its a CID problem. The only thing I ever did was upgrade to the newest Hboot and load in the CM rom. even going back to the TMOUS rom does not fix the problem.
Its so bad, and never on 4g that im considering getting a new phone.
Click to expand...
Click to collapse
I'm in the same boat, friend. I've tried literally everything suggested, I'm just wondering what exactly happened in the flashing of the Maximus rom. The worst part being is that I GET 3g/H and then it drops back to E. It's so strange. The only thing I've not done is contact Tmobile about it, and i highly doubt that they would throttle my bandwidth without contacting me in some form or fashion.

cp101 said:
I'm in the same boat, friend. I've tried literally everything suggested, I'm just wondering what exactly happened in the flashing of the Maximus rom. The worst part being is that I GET 3g/H and then it drops back to E. It's so strange. The only thing I've not done is contact Tmobile about it, and i highly doubt that they would throttle my bandwidth without contacting me in some form or fashion.
Click to expand...
Click to collapse
my phone is still under warrenty. Im wondering if i am able to revert back to stock without them knowing if I can get a phone replacement.

From what I've read, it's doable; even with an unlocked phone. But I'd really like to know what in the dev's source code made this happen... it's a bit ridiculous.

jenenser83 said:
This rom should fix your problem. Dont forget to clear storage from bootloader. It will erase everything thoug. And follow the steps under show contents link.
http://forum.xda-developers.com/showthread.php?t=2250573
Click to expand...
Click to collapse
I just wanted to say, that I did this and it worked!
I did this the first time, but i just flashed the rom with a full wipe.
This time what I did was go into TWRP and erased everything....and I mean everything except TWRP.
After that i flashed the rom and boot.img and everything works great. 4g all the time again!
Sucks that im back on an older version of jellybean, but oh well

bnd10706 said:
I just wanted to say, that I did this and it worked!
I did this the first time, but i just flashed the rom with a full wipe.
This time what I did was go into TWRP and erased everything....and I mean everything except TWRP.
After that i flashed the rom and boot.img and everything works great. 4g all the time again!
Sucks that im back on an older version of jellybean, but oh well
Click to expand...
Click to collapse
Can you take me through the steps you took to achieve all of this? Thanks.

cp101 said:
Can you take me through the steps you took to achieve all of this? Thanks.
Click to expand...
Click to collapse
So what I did first was go into TWRP and selected wipe. Inside wipe i selected EVERYTHING, every little box. Then Wiped it.
This left nothing on the phone but the recovery. I then loaded on SuperSU from TWRP. I download the stock TMOUS rom that was posted earlier in this post.
In TWRP I mounted it and hooked it to computer and transfered the rom over.
Once the rom was on I did the install of the rom.
I rebooted the rom into bootloader.
Once in bootloader i put it into fastboot.
I had previous extracted the boot.img from the rom.
I sent the boot.img over via fastboot which restarted the phone.
Once it got all started up. No issues. I am on 4g 99% of the time now.
Im thinking the issue was definatly based in the CM rom.
Since this worked I wanted to test things out since my phone was pretty much stripped of everything.
I tried out Viper rom and a couple of other non CM based roms, and I have had no issues.
IM back on teh TMOUS rom though. Wifi calling will win over when i go overseas.

Thanks, but it did not work for me. It is a hardware issue on mine. Thanks again

cp101 said:
Thanks, but it did not work for me. It is a hardware issue on mine. Thanks again
Click to expand...
Click to collapse
Must be.
I did find something out though doing all my research. Did you ever at any point update the radio? TMobile uses some frequencies that some companies dont use.
It is my understanding that some of these roms are packed with radios that are generic and thus ment for multi carriers.
Not sure if thats your issue, but might want to look into.
Its nice being back on 4g though.

[Q] flashed radio, having problems

Hey all, so i decided i wanted to try out some radios (was running viper xl)
and tried flashing a few different radios
from this thread and
http://forum.xda-developers.com/showthread.php?t=1694012
this section
"These are radios for flashing in Sense OR CM 10.x builds after 7/15 nightly!!!. They don't include the RIL files."
anyways, now i have been problems, phone randomly thinks sim card is being removed/inserted.
and having random reboots
tried flashing the 3.18 ruu
and flashed viper again,
and am still having these problems
so what else can i do?
any suggestions would be great

Well for the latest version of Viper you need to upgrade your firmware. Which build of Viper are your running?
Sent from my Evita

timmaaa said:
Well for the latest version of Viper you need to upgrade your firmware. Which build of Viper are your running?
Sent from my Evita
Click to expand...
Click to collapse
4.2.0
which firmware do i need to upgrade to ?
(i do belive my hboot was 2.15 before) but i cant seem to remember which ruu that would be
edit:
think i just found it
http://forum.xda-developers.com/showthread.php?t=2517148
is that the correct version?

Yeah that's the one you need.
Sent from my MID-1040

Thanks it had been forever since I'd run an ruu , completely forgot about the firmware upgrade
Sent from my HTC One XL using Tapatalk

No problems.
Sent from my MID-1040

timmaaa said:
No problems.
Sent from my MID-1040
Click to expand...
Click to collapse
To add to this thread so a new one doesnt need to be created, I to am having problems with my Sim card. I have tried flashing different radios, I have done the 2.15 firmware upgrade. I am about ready to give the 5.18 RUU a run and then go through the process of re-flahsing viper.

deepsouth06 said:
To add to this thread so a new one doesnt need to be created, I to am having problems with my Sim card. I have tried flashing different radios, I have done the 2.15 firmware upgrade. I am about ready to give the 5.18 RUU a run and then go through the process of re-flahsing viper.
Click to expand...
Click to collapse
Please post your bootloader details, your recovery version, your current ROM and kernel, and the exact problem you're facing.
Sent from my Evita

timmaaa said:
Please post your bootloader details, your recovery version, your current ROM and kerncontinuehe exact problem you're facing.
Sent from my Evita
Click to expand...
Click to collapse
Hboot details are in the screen shot. TWRP 2.7.0. Viper 4.2.0. Kernel is beastmode 3.4.10.
So my problem that I am having is that my phone continues to loose all data and voice service due to the phone telling me that there is no sim. I have tried different Radios with no differnce. sometimes the phone will start reading the sim if I toggle the phone into airplane mode.

I believe the radio is your problem, you need to make sure you have one of the radios that came bundled with Sense 5 releases installed. They'll be the ones that are 1.31 and upwards.
Sent from my Evita

timmaaa said:
I believe the radio is your problem, you need to make sure you have one of the radios that came bundled with Sense 5 releases installed. They'll be the ones that are 1.31 and upwards.
Sent from my Evita
Click to expand...
Click to collapse
Ok, I read something similar to what you are saying and I did flash a radio 1.31 from this link with is 2.15 firmware. http://forum.xda-developers.com/show....php?t=2517148. However the same problem was still happening. After flashing the current radio (from the above attachment), what I have noticed is that the No Sim icon only seems to happen when I have WiFi turned on for an extended time, this was just a brief observation from last night and this morning.
I am about to flash a stock RUU (possibly the 5.18) to 1) get the phone up to date with the latest firmware and 2) to see if this will help with my Sim Card problems. Or should I use a different RUU to start from Stock again?
Also When looking at the Radios thread I dont see any radios that are 1.31 and up for ATT. All of them seem to begin with 0.xx. The thread i am looking at is http://forum.xda-developers.com/showthread.php?t=1694012

The latest RUU is probably your best bet.
Sent from my Evita

timmaaa said:
The latest RUU is probably your best bet.
Sent from my Evita
Click to expand...
Click to collapse
With S-Off and my CID all 1s I wouldnt have to worry about doing the root again? After the RUU i should be able to install TWRP again and then a custom rom?

Your bootloader will remain unlocked, your CID will remain as 11111111, and your s-off status will survive the process. It's as simple as flashing TWRP afterwards and then the ROM of your choice.
Sent from my Evita

deepsouth06 said:
Hboot details are in the screen shot. TWRP 2.7.0. Viper 4.2.0. Kernel is beastmode 3.4.10.
So my problem that I am having is that my phone continues to loose all data and voice service due to the phone telling me that there is no sim. I have tried different Radios with no differnce. sometimes the phone will start reading the sim if I toggle the phone into airplane mode.
Click to expand...
Click to collapse
Did the issue start after flashing the ROM, or any other mods. Of did it just randomly start happening? Have you tried the stock kernel?'
Have you tried the trick of simply putting Scotch tape on the SIM (don't cover the contacts) to "fatten" it and force it to make better contact in the SIM tray? Loose SIM tray is known to cause the same issue.

timmaaa said:
Your bootloader will remain unlocked, your CID will remain as 11111111, and your s-off status will survive the process. It's as simple as flashing TWRP afterwards and then the ROM of your choice.
Sent from my Evita
Click to expand...
Click to collapse
Much thanks. I will be trying this out.
---------- Post added at 10:06 AM ---------- Previous post was at 10:04 AM ----------
redpoint73 said:
Did the issue start after flashing the ROM, or any other mods. Of did it just randomly start happening? Have you tried the stock kernel?'
Have you tried the trick of simply putting Scotch tape on the SIM (don't cover the contacts) to "fatten" it and force it to make better contact in the SIM tray? Loose SIM tray is known to cause the same issue.
Click to expand...
Click to collapse
To my best knowledge the issue started happening randomly. Phone was working fine for some time while I was one Viper. I believe but not 100% I started noticing this after a drop so a loose tray could very well be the problem. Also this issue was present with the stock kernel as well.

deepsouth06 said:
To my best knowledge the issue started happening randomly. Phone was working fine for some time while I was one Viper. I believe but not 100% I started noticing this after a drop so a loose tray could very well be the problem. Also this issue was present with the stock kernel as well.
Click to expand...
Click to collapse
Those answers (randomness, possible dropped phone) to me point to loose SIM tray. Also, have you tried taking the SIM out, and putting it back in, to make sure its seated properly (if dropped, it could have loosened it)?
If none of the suggestions work, you might also try to get a new SIM from your carrier.

redpoint73 said:
Those answers (randomness, possible dropped phone) to me point to loose SIM tray. Also, have you tried taking the SIM out, and putting it back in, to make sure its seated properly (if dropped, it could have loosened it)?
If none of the suggestions work, you might also try to get a new SIM from your carrier.
Click to expand...
Click to collapse
No i havent tried taking it out. I will try that out tonight. If all else fails I may end up going for a referb phone, but now with 5.18 I might hold off for as long as i can.
Thanks for your help as well.

To all, would disabling Google play services have any affect on the SIM card. I ask because after I flashed the 5.18 RUU I flashed a recovery and the flashed Viper. Phone was up and running about 1pm yesterday. Phone ran good with no problems the rest of day. This morning I unplug the phone from charger and within an hour or so I'm already at 87 percent battery. Looking up what is keeping the phone awake the culprit Google play services ( getting very annoyed of this app) so I force stop and disable play services and within one minute I get that icon of no SIM card. So with my story does google play services have any affect on the SIM cards? And how can I limit the wake locks of Google checkin.
Sorry for the long post.

deepsouth06 said:
To all, would disabling Google play services have any affect on the SIM card. I ask because after I flashed the 5.18 RUU I flashed a recovery and the flashed Viper. Phone was up and running about 1pm yesterday. Phone ran good with no problems the rest of day. This morning I unplug the phone from charger and within an hour or so I'm already at 87 percent battery. Looking up what is keeping the phone awake the culprit Google play services ( getting very annoyed of this app) so I force stop and disable play services and within one minute I get that icon of no SIM card. So with my story does google play services have any affect on the SIM cards? And how can I limit the wake locks of Google checkin.
Click to expand...
Click to collapse
I doubt that Google Play would have that effect on the SIM. I think its just a coincidence (red herring).
deepsouth06 said:
Sorry for the long post.
Click to expand...
Click to collapse
No need to be sorry. More detail is almost always better. Its the short posts that I have a problem with; where people ask for help and don't give any specifics or details. Makes it much harder to help.

Verizon M8 3G only FIX

There are very few posts found on any site about this issue so I wanted to post a success.
Symptom: M8 that either from a ROM install or OTA is 'stuck' on 3G. This persists across radio revisions and OS.
In my case, I had a M8 with S-off arrive from Swappa but it was 3g only on 4.4.4 so I took the OTA... No change. Following, I tried 3 different SIM and opened a support case with Verizon. As with the other 2 cases I found reference to in a search, the determination was a fault with the phone and it would be factory replaced under warranty. BUT this phone is S-OFF!... so I kept digging. After trying various RUU from 4.4.3, 4.4.4. and 5.01 NONE of them worked, still trapped in 3G land even with factory reset wiped cache and clean install of 4.4.4 with the Verizon OTA update to 5.01 full path.
Solution: Roll farther back! I found a very early RUU from 4.4.2 and flashed the baseband. Immediately 4g worked. Rolling forward, every firmware version I flashed after (any baseband) also worked. SO if you have a M8 that does only 3G just roll all the way back to release baseband and then back forward to 5.01.. should fix! Verizon also indicated they know of this phone sometimes not 'taking' a SIM so try a 2nd one too.
Regards and good luck,

TekGnosis said:
There are very few posts found on any site about this issue so I wanted to post a success.
Symptom: M8 that either from a ROM install or OTA is 'stuck' on 3G. This persists across radio revisions and OS.
In my case, I had a M8 with S-off arrive from Swappa but it was 3g only on 4.4.4 so I took the OTA... No change. Following, I tried 3 different SIM and opened a support case with Verizon. As with the other 2 cases I found reference to in a search, the determination was a fault with the phone and it would be factory replaced under warranty. BUT this phone is S-OFF!... so I kept digging. After trying various RUU from 4.4.3, 4.4.4. and 5.01 NONE of them worked, still trapped in 3G land even with factory reset wiped cache and clean install of 4.4.4 with the Verizon OTA update to 5.01 full path.
Solution: Roll farther back! I found a very early RUU from 4.4.2 and flashed the baseband. Immediately 4g worked. Rolling forward, every firmware version I flashed after (any baseband) also worked. SO if you have a M8 that does only 3G just roll all the way back to release baseband and then back forward to 5.01.. should fix! Verizon also indicated they know of this phone sometimes not 'taking' a SIM so try a 2nd one too.
Regards and good luck,
Click to expand...
Click to collapse
Thanks for this share. I am having an issue that may or may not be related. I have a feeling that my sim card reader is broken but my phone was actually having a similar symptoms before its radio stopped working altogether. I came back from international roaming today (and a non vzw sim) and when I arrived stateside, my phone would only pick up CDMA evdo 3g. After much fiddling in the *#*#4636#*#* menu, I did not have any luck. Then all of the sudden my phone read "no service" and wouldn't even connect to vzw at all. I tried a new sim from a vzw store, no dice. My plan was to ruu tomorrow as a last resort. I am s-off. Would you mind sharing the 4.2.2 ruu link? I'd like to try.

bacon612 said:
Thanks for this share. I am having an issue that may or may not be related. I have a feeling that my sim card reader is broken but my phone was actually having a similar symptoms before its radio stopped working altogether. I came back from international roaming today (and a non vzw sim) and when I arrived stateside, my phone would only pick up CDMA evdo 3g. After much fiddling in the *#*#4636#*#* menu, I did not have any luck. Then all of the sudden my phone read "no service" and wouldn't even connect to vzw at all. I tried a new sim from a vzw store, no dice. My plan was to ruu tomorrow as a last resort. I am s-off. Would you mind sharing the 4.2.2 ruu link? I'd like to try.
Click to expand...
Click to collapse
I have all of the ruu in one thread which is stickied in the general section.

dottat said:
I have all of the ruu in one thread which is stickied in the general section.
Click to expand...
Click to collapse
Thanks man. U think I can just reflash radio for a fix instead? Hoping for a quicker fix rather than backup> ruu >flash twrp>restore nandroid...

bacon612 said:
Thanks man. U think I can just reflash radio for a fix instead? Hoping for a quicker fix rather than backup> ruu >flash twrp>restore nandroid...
Click to expand...
Click to collapse
The s-on ruu will not wipe. They will not affect s status or unlock status. Flash ruu. Flash twrp. Flash supersu. Ten mins or less.

dottat said:
The s-on ruu will not wipe. They will not affect s status or unlock status. Flash ruu. Flash twrp. Flash supersu. Ten mins or less.
Click to expand...
Click to collapse
But I am s-off running an aosp rom. That matter? I am under the impression that flashing that ruu will take my phone back to the way it came out of a box

bacon612 said:
But I am s-off running an aosp rom. That matter? I am under the impression that flashing that ruu will take my phone back to the way it came out of a box
Click to expand...
Click to collapse
Yes that could be a problem. If you were on a sense rom it would not be. Because it does not wipe. Those ruu are unique in that they don't. The s-off ones and every other carriers ruu do wipe.
Sent from my HTC6535LVW using Tapatalk

dottat said:
Yes that could be a problem. If you were on a sense rom it would not be. Because it does not wipe. Those ruu are unique in that they don't. The s-off ones and every other carriers ruu do wipe.
Sent from my HTC6535LVW using Tapatalk
Click to expand...
Click to collapse
Im going to attempt to reflash the latest verizon radios in Hboot and see if it clears the whatever band settings i changed that killed my radio? Perhaps this is the same as what a full RUU would be but radio only.
Edit: that didnt work. Still "no service"

bacon612 said:
Im going to attempt to reflash the latest verizon radios in Hboot and see if it clears the whatever band settings i changed that killed my radio? Perhaps this is the same as what a full RUU would be but radio only.
Edit: that didnt work. Still "no service"
Click to expand...
Click to collapse
Factory reset on stock recovery now?
Sent from my HTC6535LVW using Tapatalk

dottat said:
Factory reset on stock recovery now?
Sent from my HTC6535LVW using Tapatalk
Click to expand...
Click to collapse
Did a full RUU. That didnt work. Factory reset worked!!!!! Thanks so much!

bacon612 said:
Did a full RUU. That didnt work. Factory reset worked!!!!! Thanks so much!
Click to expand...
Click to collapse
Yeah. That's always been the old standby as it sets the nv golden config back.
Sent from my HTC6535LVW using Tapatalk

So while that did reset my radio. My SIM card reader is also broken. My LTE comes in and out. Its my fault.
I have been sent a warranty replacement from VZW but its running the 5.0.1 firmware. I have come to learn that there is no way to RUU downgrade to a 4.4.4 firmware so I can run sunshine to S-Off.
Does this mean I am SOL installing TWRP and roms since im stuck S-ON? ive actually never been S-On on an HTC device before.

bacon612 said:
So while that did reset my radio. My SIM card reader is also broken. My LTE comes in and out. Its my fault.
I have been sent a warranty replacement from VZW but its running the 5.0.1 firmware. I have come to learn that there is no way to RUU downgrade to a 4.4.4 firmware so I can run sunshine to S-Off.
Does this mean I am SOL installing TWRP and roms since im stuck S-ON? ive actually never been S-On on an HTC device before.
Click to expand...
Click to collapse
You can use a Java Card to S-OFF your M8 - check out the Verizon M9 Java Card thread.
(@dottat has one, he is my recommendation - but all are very trustworthy and if someone is closer it may be easier on you to go with them)

Been having this issue myself. Tried RUU, flashing all radios from 4.4.2 on up, factory reset, etc. I'm only getting 3G-- not LTE whatsoever. Any ideas?
Edit: Got a new SIM-- no cigar. Unless there are some network settings that I don't know about, the 4G antenna might just be broken or something

dottat said:
Factory reset on stock recovery now?
Click to expand...
Click to collapse
Thank you! This saved me from having to get a new M8 from Verizon (after the new SIM didn't work) and losing S-OFF.

meskibob said:
Thank you! This saved me from having to get a new M8 from Verizon (after the new SIM didn't work) and losing S-OFF.
Click to expand...
Click to collapse
It's not possible to lose s-off? Did you turn it on yourself?
Sent from my Nexus 6 using Tapatalk

dottat said:
It's not possible to lose s-off? Did you turn it on yourself?
Click to expand...
Click to collapse
I meant that I can keep my current M8 (still S-OFF) and have working LTE, instead of having to swap it with the new M8 that Verizon is sending to me (which I can now return).

meskibob said:
I meant that I can keep my current M8 (still S-OFF) and have working LTE, instead of having to swap it with the new M8 that Verizon is sending to me (which I can now return).
Click to expand...
Click to collapse
Thank you for the clarification. Gotta keep the folks from spinning rumors you can lose s-off
Sent from my Nexus 6 using Tapatalk

dottat said:
Thank you for the clarification. Gotta keep the folks from spinning rumors you can lose s-off
Click to expand...
Click to collapse
Sorry for the confusion, and thanks again!

No dice. On any of these fixes. I've gone through all the RUUs that dottat has posted, full back to stock (with root /s-off). I'm at a complete loss. Does anyone have any other suggestions to try and get this fixed?
After I flashed on of the RUUs I have 4G for about 10 mins, then it bumps back down to 3G. I've checked this in three different cities (Home, Work, Friends) so its not the network in my area. I was thinking of stopping at Verizon, maybe get a new SIM, but I'm not sure if that would work.