HTC ONE M8 no sim / emergency calls only

[alphalvr]

Hello I have a problem with a M8 that I got from a mate that had a broken screen. He told me the phone was working but now I do not know what to believe.

I bought a replacement screen and a brand new back cover and the whole repair went well.

I turned the phone on just before fitting the back and checked the screen was functional. Then i stupidly put it all back together and realised that the phone will not see a sim and no bars appear in the signal area, it has a little 'x' there.

It constantly just says 'no sim / emergency calls only'. So I took it all apart again scuffing my new screen/case in the process and dismantled it all and re built it paying close attention to every connection.

It still has the same problem, I also tried every sim in the house, they all work in other phones.

I even tried adding tape to help with the connection (on back of sim) even though really the sim carrier is new.

I tried putting the sim in the old phone and connecting the old sim carrier to the new phone and still get same result to try and rule out the sim carrier.

I never tried the phone before changing the screen, i just assumed it was a phone with busted screen, nothing else. (next time I will check)

i have run a diagnostic thing and the phone sees 3 cell towers just the same as my phone I am using with reported good signal, even though the phone shows no bars.

I have re installed the sim a 1000 times, turned flight mode on and off 2000 times and factory reset the phone to no avail. I also went through all the phone settings and scoured the web but found nothing.

Everything else works perfectly, I am at my wits end. Any suggestions??

Oh one last thing to my knowledge I believe the phone is stock.

Thank you.

 

[4yush]

Hello I have a problem with a M8 that I got from a mate that had a broken screen. He told me the phone was working but now I do not know what to believe.

I bought a replacement screen and a brand new back cover and the whole repair went well.

I turned the phone on just before fitting the back and checked the screen was functional. Then i stupidly put it all back together and realised that the phone will not see a sim and no bars appear in the signal area, it has a little 'x' there.

It constantly just says 'no sim / emergency calls only'. So I took it all apart again scuffing my new screen/case in the process and dismantled it all and re built it paying close attention to every connection.

It still has the same problem, I also tried every sim in the house, they all work in other phones.

I even tried adding tape to help with the connection (on back of sim) even though really the sim carrier is new.

I tried putting the sim in the old phone and connecting the old sim carrier to the new phone and still get same result to try and rule out the sim carrier.

I never tried the phone before changing the screen, i just assumed it was a phone with busted screen, nothing else. (next time I will check)

i have run a diagnostic thing and the phone sees 3 cell towers just the same as my phone I am using with reported good signal, even though the phone shows no bars.

I have re installed the sim a 1000 times, turned flight mode on and off 2000 times and factory reset the phone to no avail. I also went through all the phone settings and scoured the web but found nothing.

Everything else works perfectly, I am at my wits end. Any suggestions??

Oh one last thing to my knowledge I believe the phone is stock.

Thank you.

Apparently I have the same issue. Tried Different ROMs flashed different firmwares but all in vain. I guess it is an hardware issue and can't be fixed. Maybe use it for entertainment purpose or paper weight.

 

[alphalvr]

Damn I hoped there would be some suggestions, guess I tried a fair amount.

 

[redpoint73]

Apparently I have the same issue. Tried Different ROMs flashed different firmwares but all in vain. I guess it is an hardware issue and can't be fixed. Maybe use it for entertainment purpose or paper weight.

Did you replace the screen like the OP?

 

[4yush]

Did you replace the screen like the OP?

No, but the problem is the same.

 

[redpoint73]

No, but the problem is the same.

No, it's not the same problem. Some of the symptoms may be the same, but the cause is possibly (or even probably) not the same.

The OP did a hardware repair, where a lot of things can go wrong, such as damaged antenna connection, or some other hardware fault resulting from the repair. That isn't the case for you, it might be a software problem. I'm not too good with hardware issues. I personally avoid hardware repairs, and therefore my experience with those types of issues is limited. So I therefore hesitate to advise the OP. But I have a lot more experience with software/firmware related issues; and may possibly be of help to you (depending on the circumstance).

You need to outline the exact circumstances which led to the "no SIM" issue, and give details about your device. Did you try to flash anything to the device, to cause the problem? Did you drop the device, or any other physical damage? If you know how, do fastboot getvar all, and post the results (delete IMEI and serial number before posting).

For instance, it's been fairly common to see folks flash the wrong firmware to a Verizon/Sprint version M8, which results in "no SIM". Lots of times, those folks don't' even realize they have a Verizon or Sprint variant. But we can tell easily from the getvar info.

Yes, it might just be a hardware issue (such as broken SIM tray), but if you give no details on your device or how the problem occurred, than it's hard for us to help you.

In general, I would advise saying "I have the same problem" (without giving any specific details about your device and situation). I can honestly say, that after seeing this posted dozens (maybe hundreds) of times; that this has never been actually true (that it was the exact same problem) not even one time. Once we start digging for more info, we find that the details are always different. Every time.

 

[4yush]

No, it's not the same problem. Some of the symptoms may be the same, but the cause is possibly (or even probably) not the same.

The OP did a hardware repair, where a lot of things can go wrong, such as damaged antenna connection, or some other hardware fault resulting from the repair. That isn't the case for you, it might be a software problem. I'm not too good with hardware issues. I personally avoid hardware repairs, and therefore my experience with those types of issues is limited. So I therefore hesitate to advise the OP. But I have a lot more experience with software/firmware related issues; and may possibly be of help to you (depending on the circumstance).

You need to outline the exact circumstances which led to the "no SIM" issue, and give details about your device. Did you try to flash anything to the device, to cause the problem? Did you drop the device, or any other physical damage? If you know how, do fastboot getvar all, and post the results (delete IMEI and serial number before posting).

For instance, it's been fairly common to see folks flash the wrong firmware to a Verizon/Sprint version M8, which results in "no SIM". Lots of times, those folks don't' even realize they have a Verizon or Sprint variant. But we can tell easily from the getvar info.

Yes, it might just be a hardware issue (such as broken SIM tray), but if you give no details on your device or how the problem occurred, than it's hard for us to help you.

In general, I would advise saying "I have the same problem" (without giving any specific details about your device and situation). I can honestly say, that after seeing this posted dozens (maybe hundreds) of times; that this has never been actually true (that it was the exact same problem) not even one time. Once we start digging for more info, we find that the details are always different. Every time.

Thanks for enlightening me with your wise words. I stand corrected. The phone was stock when suddenly the signal dropped I flashed GP edition(S-ON) and one day the signal showed up out of no where. Worked for 2-3 days and the same issue started again. Still on GP edition tried flashing Venom OS but no good.

(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.15.720.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B65000
(bootloader) cidnum: HTC__038
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

 

[redpoint73]

Thanks for enlightening me with your wise words. I stand corrected. The phone was stock when suddenly the signal dropped I flashed GP edition(S-ON) and one day the signal showed up out of no where. Worked for 2-3 days and the same issue started again. Still on GP edition tried flashing Venom OS but no good.

"No good" meaning what? Signal did not come back, or the ROM didn't flash?

Flashing a ROM shouldn't affect the signal/SIM tray. Any reason to believe your local carrier is having an outage in your area?

Otherwise, it doesn't sound like anything you did to cause the SIM issue. So the spontaneous occurance may in fact be a hardware problem. Some folks have had issues with the SIM tray. Sometimes putting tape on the SIM will help the SIM make better contact. But be careful not too jam up the tray with too much tape, or covering the metal contacts on the SIM.

 

[4yush]

"No good" meaning what? Signal did not come back, or the ROM didn't flash?

Flashing a ROM shouldn't affect the signal/SIM tray. Any reason to believe your local carrier is having an outage in your area?

Otherwise, it doesn't sound like anything you did to cause the SIM issue. So the spontaneous occurance may in fact be a hardware problem. Some folks have had issues with the SIM tray. Sometimes putting tape on the SIM will help the SIM make better contact. But be careful not too jam up the tray with too much tape, or covering the metal contacts on the SIM.

Signal didn't come back. No, no outage because it works on my other phone. I've tried the tape thing also doesn't work. It's probably an hardware issue.

 

[redpoint73]

Signal didn't come back. No, no outage because it works on my other phone. I've tried the tape thing also doesn't work. It's probably an hardware issue.

Another thing you can try, is flash the signed firmware again. I've seen this help some folks with signal issues; in cases where it seems the radio baseband firmware is corrupt or damaged. May or may not help, but I'd say it's worth a try. Obviously, if the issue is in the hardware, flashing firmware isn't going to help.

In order to flash the firmware, since you are s-on, you will have to jump though some hoops:
1) Lock bootloader with command: fastboot oem lock
The signed firmware will only flash with a locked or relocked bootloader (will not flash with bootloader unlocked).
Take note that locking the bootloader renders the phone unable to boot. And you will lose any user data. So plan accordingly before doing this step.
2) Flash the signed firmware 6.15.720.2 from here (instruction near the bottom of the post): https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
2) Firmware is a small file with hboot, radio, etc., and does not contain the full ROM. RUU is not available for your version (that I am aware of, anyway), which does contain the ROM.
Therefore, you will then need to unlock the bootloader again (use the same bin code to unlock the bootloader you previously used, or get a new code from HTCDev.com)
3) Install TWRP to the phone again (it would have been wiped by flashing the signed firmware).
4) Flash a custom ROM again. Of restore the stock TWRP backup (stock ROM) 6.15.720.2 from here: https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860

 

[alphalvr]

Just to update this thread, it was a ribbon cable that was not clipped in correctly. My bad.

So now I want to unlock the bootloader BUT I cant register at HTC DEV, I fill in the form and nothing happens when I click register. Tried it a 1000 times, the screen just refreshes and does nothing. I am at a loss. any ideas???

Regarding my original issue.......he was right......the problem was not the same. My issue was I had no idea if the problem already existed, if I had known the phone worked before I started I would have tried harder to fix it When I posted here and there were no similar posters it made me go back and check again.

I swear the phone is cursed.......do a simple thing like register at a website and get thwarted again.

So I guess the OP is solved.

Also I tried registering with a different computer, just to try everything.......and it registered first time, is that weird or what?
So hopefully I am another step closer to trying some custom roms \0/

 

[redpoint73]

Also I tried registering with a different computer, just to try everything.......and it registered first time, is that weird or what?

HTCDev site is pretty buggy. I've seen other reports of it not working, then randomly working if you try later.

 

[4yush]

Another thing you can try, is flash the signed firmware again. I've seen this help some folks with signal issues; in cases where it seems the radio baseband firmware is corrupt or damaged. May or may not help, but I'd say it's worth a try. Obviously, if the issue is in the hardware, flashing firmware isn't going to help.

In order to flash the firmware, since you are s-on, you will have to jump though some hoops:
1) Lock bootloader with command: fastboot oem lock
The signed firmware will only flash with a locked or relocked bootloader (will not flash with bootloader unlocked).
Take note that locking the bootloader renders the phone unable to boot. And you will lose any user data. So plan accordingly before doing this step.
2) Flash the signed firmware 6.15.720.2 from here (instruction near the bottom of the post): https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
2) Firmware is a small file with hboot, radio, etc., and does not contain the full ROM. RUU is not available for your version (that I am aware of, anyway), which does contain the ROM.
Therefore, you will then need to unlock the bootloader again (use the same bin code to unlock the bootloader you previously used, or get a new code from HTCDev.com)
3) Install TWRP to the phone again (it would have been wiped by flashing the signed firmware).
4) Flash a custom ROM again. Of restore the stock TWRP backup (stock ROM) 6.15.720.2 from here: https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860

Thank you so much for taking these efforts for helping. I'll do the steps you mentioned and get back to you. Again really thankful.

 

[HTC_ONE_M8(lite)]

No, it's not the same problem. Some of the symptoms may be the same, but the cause is possibly (or even probably) not the same.

The OP did a hardware repair, where a lot of things can go wrong, such as damaged antenna connection, or some other hardware fault resulting from the repair. That isn't the case for you, it might be a software problem. I'm not too good with hardware issues. I personally avoid hardware repairs, and therefore my experience with those types of issues is limited. So I therefore hesitate to advise the OP. But I have a lot more experience with software/firmware related issues; and may possibly be of help to you (depending on the circumstance).

You need to outline the exact circumstances which led to the "no SIM" issue, and give details about your device. Did you try to flash anything to the device, to cause the problem? Did you drop the device, or any other physical damage? If you know how, do fastboot getvar all, and post the results (delete IMEI and serial number before posting).

For instance, it's been fairly common to see folks flash the wrong firmware to a Verizon/Sprint version M8, which results in "no SIM". Lots of times, those folks don't' even realize they have a Verizon or Sprint variant. But we can tell easily from the getvar info.

Yes, it might just be a hardware issue (such as broken SIM tray), but if you give no details on your device or how the problem occurred, than it's hard for us to help you.

In general, I would advise saying "I have the same problem" (without giving any specific details about your device and situation). I can honestly say, that after seeing this posted dozens (maybe hundreds) of times; that this has never been actually true (that it was the exact same problem) not even one time. Once we start digging for more info, we find that the details are always different. Every time.

So I think my problem is the firmware one where I've got a full backup of my old stock rom that even after restoring still has signal but once I flash a custom rom (skydragon Lollipop / Sense7) it just has that little x above the signal bar and says emergency calls only. Nothing I tried helped so I think it must be a firmware issue but I have no idea about how to resolve it. I'm also quite new to such problems usually I just installed a rom and everything always worked fine so this bothers me and I'd love to get it up and working as I have serious reasons to not use the stock rom as it drains battery 1/3 faster and needs more cpu power to be just turned on. Its pretty **** compared to the skydragon rom +kernel but I need to resolve the connectivity issue first and I've really ran out of all ideas and google doesn't seem to be very interested in showing me a useful result.

 

[redpoint73]

So I think my problem is the firmware one where I've got a full backup of my old stock rom that even after restoring still has signal but once I flash a custom rom (skydragon Lollipop / Sense7) it just has that little x above the signal bar and says emergency calls only.

Your post is really confusing, as it specifically is in reply to one of my posts, directed to another member (with specific device details).

You don't provide any device specifics to work with. If you know how, do fastboot getvar all, and post the results (delete IMEI and serial number before posting). Or at a minimum, list what OS number is listed on the phone's bootloader screen (do not go by the version number in phone settings) or if it is blank, tell us what it says for hboot and radio baseband number.

Most of the custom ROMs require Marshmallow firmware, so if you are on old firmware, it may in fact be a firmware issue. But can't be sure, without more details.

Nothing I tried helped so I think it must be a firmware issue but I have no idea about how to resolve it.

This statement does not really tell us anything, if you don't know what specific "fixes" you tried.