Database Users

How I Got My Xoom Upgraded, Rooted and Running 3.2.2

I sent my Xoom off for 4G upgrade and received it. Moto in its infinite wisdom sent me a new Xoom. So naturally, I started my Xoom and 3G/4G failed because I had a new MEID. Motor provided this new Xoom without syncing up with Verizon. So Verizon didn't have my MEID synced to my new 4G card. This explains the connectivity issues I had OOB.
I wish I new that before I went about a variety of flashing that failed in one way or the other. I did eventually get things to run with 3g/4g, and here s what I did.
1. Flash HRI66
2. Do a hard reset from Settings/Privacy
3. Reboot and fastboot flash recovery-Tiamat-R4c-100611-1150-cwm.img (http://forum.xda-developers.com/showthread.php?t=1074979)
4. Reboot into CWM and flash Android-HC-3.2.2-Stock+Rooted-1.1-SOLARNZ.zip (http://forum.xda-developers.com/showthread.php?t=1242524)
5. Flash HLK75C (http://dl.dropbox.com/u/22648028/HLK75Csystemboot.7z password is "AceXMachine" without the quotes)
Upon reboot both my WIFI and 3G/4G were restored.
When you reboot you should get prompted for HLK75D which is the market.
Peace, Happiness & Joy

I just saw this thread right before I was about to possibly enter a boot loop by trying something stupid. Thanks for posting! I will have to try this out tomorrow on my 3G XOOM.
Just FYI, Short/y posted the update for HLK75D HERE in case anyone wants to manually update.

So excited to read your post. Figured the system and boot images were the missing pieces to getting my problem solved. Unfortunately so far I have not seen any cellular data activity since getting up to HLK75D. It has been about an hour since rebooted and tried to activate.
I must still be missing a piece to the puzzle. When I look at a screen shot from droidlife under "About tablet" I see under Baseband version "CDMA_N_03.1A.54P ltedc_u_05.19.00". On my Xoom I only have the CDMA radio listed but everything else is the same. I also do not have any LTE settings under Mobile networks like I know I should based on the insert I got in the box back from Moto. This makes me think somehow I managed to corrupt the radios but I certainly never did that on purpose. Any idea how I can get the right radios to flash too?
---------- Post added at 06:02 PM ---------- Previous post was at 05:47 PM ----------
So excited to read your post. Figured the system and boot images were the missing pieces to getting my problem solved. Unfortunately so far I have not seen any cellular data activity since getting up to HLK75D. It has been about an hour since rebooted and tried to activate.
I must still be missing a piece to the puzzle. When I look at a screen shot from droidlife under "About tablet" I see under Baseband version "CDMA_N_03.1A.54P ltedc_u_05.19.00". On my Xoom I only have the CDMA radio listed but everything else is the same. I also do not have any LTE settings under Mobile networks like I know I should based on the insert I got in the box back from Moto. This makes me think somehow I managed to corrupt the radios but I certainly never did that on purpose. Any idea how I can get the right radios to flash too?

I have the same exact issue. Even bricked my xoom trying to resolve this, but fortunately I was able to unbrick it.

I did exactly the very same thing. Thanks Ace! Worked very well for me.

SemperAndroid said:
5. Flash HLK75C [/QUOTE
When you say "Flash", what should I be typing at the end of my command line
C:\Program Files (x86)\Android\android-sdk\platform-tools>?
Click to expand...
Click to collapse

Tinninches said:
SemperAndroid said:
5. Flash HLK75C
Click to expand...
Click to collapse
When you say "Flash", what should I be typing at the end of my command line
C:\Program Files (x86)\Android\android-sdk\platform-tools>?
Click to expand...
Click to collapse
The file downloads as a .7z I've tried to compress it and flash it from CWM off my external SD Card. I've tried flashing the two files individually. I've tried fastbooting them.
Could you possibly go into a bit more depth as to what you did in step 5?

SemperAndroid said:
I sent my Xoom off for 4G upgrade and received it. Moto in its infinite wisdom sent me a new Xoom. So naturally, I started my Xoom and 3G/4G failed because I had a new MEID. Motor provided this new Xoom without syncing up with Verizon. So Verizon didn't have my MEID synced to my new 4G card. This explains the connectivity issues I had OOB.
Click to expand...
Click to collapse
This was really annoying. The MEID Verizon had was a digit missing and didn't have my SIM card identified. I actually started to think the the new hardware wasn't hooked up correctly inside and was about to send it back in before I check the Verizon website.

SemperAndroid said:
I sent my Xoom off for 4G upgrade and received it. Moto in its infinite wisdom sent me a new Xoom. So naturally, I started my Xoom and 3G/4G failed because I had a new MEID. Motor provided this new Xoom without syncing up with Verizon. So Verizon didn't have my MEID synced to my new 4G card. This explains the connectivity issues I had OOB.
I wish I new that before I went about a variety of flashing that failed in one way or the other. I did eventually get things to run with 3g/4g, and here s what I did.
1. Flash HRI66
2. Do a hard reset from Settings/Privacy
3. Reboot and fastboot flash recovery-Tiamat-R4c-100611-1150-cwm.img (http://forum.xda-developers.com/showthread.php?t=1074979)
4. Reboot into CWM and flash Android-HC-3.2.2-Stock+Rooted-1.1-SOLARNZ.zip (http://forum.xda-developers.com/showthread.php?t=1242524)
5. Flash HLK75C (http://dl.dropbox.com/u/22648028/HLK75Csystemboot.7z password is "AceXMachine" without the quotes)
Upon reboot both my WIFI and 3G/4G were restored.
When you reboot you should get prompted for HLK75D which is the market.
Peace, Happiness & Joy
Click to expand...
Click to collapse
I followed these steps and everything seems to be working. I can't verify 4G works since it's not available here yet, but 3G works fine. However, my Build Number still shows HLK75C. I thought something might have went bad with the HLK75D reboot/install (battery was low) so I reflashed the 75C boot & system thinking it would reprompt for the update. It didn't. Check for updates says I'm up to date. Anyone else have this issue? Does the Build Number not change after the update?

This actually did not work for me. These were the steps I did exactly:
1) Flashed to HRI66.
2) Booted up and skipped verification and setting up a Google account. Did a hard reset through the settings.
3) Upon reboot, I flashed the Tiamat recovery image.
4) Upon reboot, I entered the CWM and flashed Solarnz's 3.2.2 image. Unfortunately, when I use the 1.1 version from his thread, I get an error telling me that it was "bad", so I had to use the original version that he posted. (This might be why it didn't work, I'm not sure.)
5) Upon reboot, I flashed the HLK75C images in Fastboot.
I loaded up and I was on 3.2.2 just fine, with the HLK75C build, but my kernel didn't have the "LTC" part in it like it did when I received it from Verizon. I still have full bars but no 3G/4G connectivity. Wi-Fi works fine.
When I take out my SIM card, I obviously lose all the bars.
[EDIT] I noticed in another thread that someone brought up the question whether people with connectivity problems were wiping the cache and davlik every time they flashed. Is that something I should be doing in CWM after flashing anything? Yeah, I'm kind of new and dumb to this. [/EDIT]

Cannot Activate on Verizon after 4G Upgrade
When I first got my Xoom back and booted it up, it imediately stuck at the logo screen and said Failed to boot LNX 0x0004 in red text and then a line below it said Starting RSD Mode 2. I tried rebooting several times but it always went to the same place. I did the HRI39 sbf and got it back up and running, then performed these steps.
1. Flash HRI66
2. Do a hard reset from Settings/Privacy
3. Reboot and fastboot flash recovery-Tiamat-R4c-100611-1150-cwm.img (http://forum.xda-developers.com/show....php?t=1074979)
4. Reboot into CWM and flash Android-HC-3.2.2-Stock+Rooted-1.1-SOLARNZ.zip (http://forum.xda-developers.com/show....php?t=1242524)
5. Flash HLK75C (http://dl.dropbox.com/u/22648028/HLK75Csystemboot.7z password is "AceXMachine" without the quotes)
I now have my Xoom on HLK95D as it should be and can connect to WiFi just fine but it does not acknowledge that the Xoom has 4G and will not activate with Verizon through 3G either. If I go into settings, About Tablet and Status, my Xoom shows Network: Unknown, Mobile network type: Unknown, MDN: Unknown, MIN: Unknown and MEID: Unknown.
I am wondering if I happened to be an unlucky one who got a bad 4G card. My understanding is that the new 4G card not only adds 4G but also replaces the built in 3G Radio chip. I did check my MEID # before I loaded the ROM that supports the 4G card and it did show my original MEID # for my Xoom but once I load a ROM that has the drivers for the 4G card, they disappear. Any thoughts

dlundy said:
I followed these steps and everything seems to be working. I can't verify 4G works since it's not available here yet, but 3G works fine. However, my Build Number still shows HLK75C. I thought something might have went bad with the HLK75D reboot/install (battery was low) so I reflashed the 75C boot & system thinking it would reprompt for the update. It didn't. Check for updates says I'm up to date. Anyone else have this issue? Does the Build Number not change after the update?
Click to expand...
Click to collapse
Figured out my issue with the 75D update. It was not installing automatically due to CWM reccovery. I had to pull the update from the \cache folder and install it manually through CWM. Of course, it overwrote recovery and killed root so I had to reflash CWM and reroot with the universal root zip, but it is now on HLK75D and working properly. I still can't test 4G, but 3G is working.

[Q] Loosing HSPA on root - no sim card

Hey guys,
after replying to several other threads i decided to make this a thread on it's own.
i tried to root my nexus 7 3G - "nakasig" with the two toolkits. also i tried it manually pushing the root stuff via adb.
when on stock + unlocked bootloader i have normal 3g connection but after the root it just says "no sim card". still i can search for networks but it doesnt let me connect to them. its as if the sim slot would lose its drivers or something. any ideas on that?
I'd be really happy if any of you would help me, im out of options i suppose...
cheers,
mo

Same problem here. Any news on that?

Here is a quick solution to your problem: STOP USING TOOLKITS!
The process is ridiculously simply. By using these automated tools, you're just asking for problems. And when one occurs, you have no idea how to troubleshoot it.
I wouldn't be surprised if the toolkit you used doesn't support the 3G model and probably broke the 3G capabilities.
1) Unlock bootloader if it hasn't already been done.
2) Flash custom recovery of your choice (make sure it's capable of supporting 4.2 multi-user)
3) Put an "su" flashable zip on sdcard.
4) Go into custom recovery and flash it.
5) Reboot
Voila. Done.

In fact, I didn't use any Toolkit (I want to control everything on my own, and am not afraid of using the console/adb).
Here are the steps, I did:
1. Unlock bootloader (fastboot oem unlock)
2. Boot custom recovery (fastboot boot [recovery.img])
3. Mount /system in recovery
4. adb shell -> put su in /system/bin -> put Superuser.apk in /system/app (and chmodded su to 06755, Superuser to 0644)
5. restarted, no 3G available
The problematic step could be the second, I used the "recovery-clockwork-touch-6.0.1.0-grouper.img", which is not specially for the N7-3G (called nakasig). Is there a better recovery Image?
I didn't want to flash the recovery, so I just booted into it. Could this be the problem?
Best regards

kroegerama said:
In fact, I didn't use any Toolkit (I want to control everything on my own, and am not afraid of using the console/adb).
Here are the steps, I did:
1. Unlock bootloader (fastboot oem unlock)
2. Boot custom recovery (fastboot boot [recovery.img])
3. Mount /system in recovery
4. adb shell -> put su in /system/bin -> put Superuser.apk in /system/app (and chmodded su to 06755, Superuser to 0644)
5. restarted, no 3G available
The problematic step could be the second, I used the "recovery-clockwork-touch-6.0.1.0-grouper.img", which is not specially for the N7-3G (called nakasig). Is there a better recovery Image?
I didn't want to flash the recovery, so I just booted into it. Could this be the problem?
Best regards
Click to expand...
Click to collapse
I had issues on my 16GB unit with that version of CWM on 4.1.2. I ended up using the 'beta' version 6.0.1.5 - it''s on XDA somewhere. When I got my N7 3G, I used the latest version of TWRP, and it works great.
But, based on what you are saying, none of that should even matter. In your case, you're not actually flashing a SU zip, you're manually installing it yourself (I did the same thing). So as long as you are able to mount /system and modify it's contents, which you obviously did, that's fine. The only thing I did differently was install su into /system/xbin, but /system/bin should be fine too.
Does 'su' and the SuperUser app work? If so, then that means your modification was successful.
Assuming that's all you did, I can't think of any reason why that would have broken 3G support. Is everything else 100% stock? If you flashed a custom kernel, it probably won't support 3G. The only one that I know of that DOES work is faux123's beta version.
Can you describe your issue a little more? Does the tablet display signal strength but just not get data? I'm assuming you disabled wifi to test, right?

Does 'su' and the SuperUser app work? If so, then that means your modification was successful.
Click to expand...
Click to collapse
Yes, they did. For example, I could install AdAway, which was able to change the hosts-file.
Assuming that's all you did, I can't think of any reason why that would have broken 3G support. Is everything else 100% stock? If you flashed a custom kernel, it probably won't support 3G. The only one that I know of that DOES work is faux123's beta version.
Click to expand...
Click to collapse
I didn't change anything. Just did the steps I described earlier...
Can you describe your issue a little more? Does the tablet display signal strength but just not get data? I'm assuming you disabled wifi to test, right?
Click to expand...
Click to collapse
Sure, I disabled WIFI. The signal strength display has all 4 bars (full reception), but no "H" or "3G" is displayed and also the bars are grey and not blue.
The weird thing is, that if I check "Use only 2G-Networks", I get blue bars with "G" and can access the internet...

kroegerama said:
Yes, they did. For example, I could install AdAway, which was able to change the hosts-file.
I didn't change anything. Just did the steps I described earlier...
Sure, I disabled WIFI. The signal strength display has all 4 bars (full reception), but no "H" or "3G" is displayed and also the bars are grey and not blue.
The weird thing is, that if I check "Use only 2G-Networks", I get blue bars with "G" and can access the internet...
Click to expand...
Click to collapse
Hrmmm....
I had the exact same issue (gray bars, no Internet), but it was because I flashed a non-3G compatible kernel. Once I replaced that, it started working properly again. I assume it worked fine prior to rooting, correct?
I still can't think of any reason why adding the su binary and SuperUser application would cause any issues with 3G connectivity. The two things have nothing to do with each other. Especially since you did it manually (which eliminates the possibility of some overzealous flashable zip. Hell, you didn't even flash a custom recovery but booted off it of it from your PC.
Have you tried rebooting since, to see if that cleared things up?
Just for the sake of eliminating them as a variable, why don't you try removing su and superuser.apk and see if that fixes it. I doubt it will, but it's worth a short.
The only other thing I can think of is for you to try reflashing the full 4.2 image (sans userdata) and see if that fixes the problem. Something else might have gotten broken and that should fix it.

Well, actually I don't know, if HSPA worked before rooting, because it was the first thing I did with my new N7
I rebooted a thousand times, toggled Airplane-Mode another thousand times and nothing helped. Now, I have reverted everything completely to stock:
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-tilapia-4.13.img
fastboot reboot-bootloader
fastboot flash radio radio-tilapia-1231_0.10.0_1021.img
fastboot reboot-bootloader
fastboot -w update image-nakasig-jop40c.zip
After that i locked the bootloader (oem lock). And guess what? I still can't get HSPA connection
I checked the SIM card in my Smartphone (N4 btw) and it worked fine, so it can't be the problem.
Do you think, I have to send my N7 back, because it has a hardware-error?

kroegerama said:
Well, actually I don't know, if HSPA worked before rooting, because it was the first thing I did with my new N7
I rebooted a thousand times, toggled Airplane-Mode another thousand times and nothing helped. Now, I have reverted everything completely to stock:
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-tilapia-4.13.img
fastboot reboot-bootloader
fastboot flash radio radio-tilapia-1231_0.10.0_1021.img
fastboot reboot-bootloader
fastboot -w update image-nakasig-jop40c.zip
After that i locked the bootloader (oem lock). And guess what? I still can't get HSPA connection
I checked the SIM card in my Smartphone (N4 btw) and it worked fine, so it can't be the problem.
Do you think, I have to send my N7 back, because it has a hardware-error?
Click to expand...
Click to collapse
Since you did that full flash (include the -w which wipes userdata), your N7 is completely back to stock.
There is definitely a possibility of a hardware issue, but before we assume that, there's one other possibility that comes to mind since you said you didn't know if it worked before.
What type of SIM card are you using? Is it the AT&T one that it came with? If so, did you activate it? If you did activate it, did you activate it through the tablet? When you turned off wifi, did it popup with a notification about logging into the AT&T network? If you activated it on the tablet, did you complete the whole process and receive the SMS and email?
And finally, the one thing that comes to mind as the possible problem if you are using that AT&T SIM card and it was activated:
What APN are you using? Mine came with two. The default is the one you use to register the SIM and activate it. The second APN is the normal usage one. After my activation, I was still on the registration APN and had to manually switch to the other one. If that is the case for you, and you are still on the registration APN, that could explain the issue. Try changing it to the other one and see if that fixes it.

No, I'm not at AT&T. Actually, I don't live in the US at all, I'm in Germany.
But I double-checked my APN-Settings and they seem to be set correctly. Also the SIM card is activated, as I'm able to use it in my Smartphone...
I've got one question, though: In the drop-down quick-settings pane, do you have a panel with your carrier name on it?
My Nexus 4 has one, but the Nexus 7 doesn't...

kroegerama said:
No, I'm not at AT&T. Actually, I don't live in the US at all, I'm in Germany.
But I double-checked my APN-Settings and they seem to be set correctly. Also the SIM card is activated, as I'm able to use it in my Smartphone...
I've got one question, though: In the drop-down quick-settings pane, do you have a panel with your carrier name on it?
My Nexus 4 has one, but the Nexus 7 doesn't...
Click to expand...
Click to collapse
Ah, well that eliminates my possible explanation.
No, I do not see that carrier name in either drop down. However, the carrier name should be on the bottom of the lock screen.
Are you 100% sure that the carrier in question will support the N7? I ask, because apparently people are having issues with T-Mobile SIM cards in the US. They work perfectly fine in a phone and/or other device, but when they put them in the N7 - nothing. Sounds like a similar issue. It seems like T-Mobile is blocking the N7 IMEIs from using standard voice or data packages.
I think the only real way to tell whether it's a hardware issue or not is if you have a friend with an N7 3G that you could try the SIM card in. That, or try buying some cheap prepaid one that you can use for a day or so.
But with what your saying, I'm thinking it very well might be a hardware issue for you.

Just to clarify:
- Which carrier is your SIM card from?
- Do you get 3G with that SIM in a smartphone? If so, which smartphone?

- My SIM is from "O2 - DE" (O2 Germany)
- Yes, I get 3G in a smartphone. It's a Nexus 4.
Are you 100% sure that the carrier in question will support the N7? I ask, because apparently people are having issues with T-Mobile SIM cards in the US. They work perfectly fine in a phone and/or other device, but when they put them in the N7 - nothing. Sounds like a similar issue. It seems like T-Mobile is blocking the N7 IMEIs from using standard voice or data packages.
Click to expand...
Click to collapse
Well, I'm not really sure, if my carrier blocks Tablets. I asked google, but no one else reported Tablet-blocking in the o2-network. But to be sure, I will test a friend's SIM card from vodafone tomorrow in my N7.
Sadly, I can't test my SIM in another N7-3G, because I don't know anyone who owns one.

So just to be sure, you are using the same APN settings on the N7 that you have in your Nexus 4?
Another thought - I have heard that with some European MVNOs, and even primary carriers that share networks with other providers, sometimes Android considers you to be roaming. Have you tried enabling data roaming just to see?
And when 2G-only is disabled, have you tried going into the mobile networks list to scan and ensure you are connected to the right network?

cmstlist said:
So just to be sure, you are using the same APN settings on the N7 that you have in your Nexus 4?
Click to expand...
Click to collapse
Yes, I used the correct settings in both devices...
cmstlist said:
Another thought - I have heard that with some European MVNOs, and even primary carriers that share networks with other providers, sometimes Android considers you to be roaming. Have you tried enabling data roaming just to see?
Click to expand...
Click to collapse
I enabled data roaming, but that also didn't help.
cmstlist said:
And when 2G-only is disabled, have you tried going into the mobile networks list to scan and ensure you are connected to the right network?
Click to expand...
Click to collapse
When I tap on the scan-button, it loads a few seconds and then says "Fehler bei der Netzwerksuche" (translated: "error while searching for networks")

kroegerama said:
When I tap on the scan-button, it loads a few seconds and then says "Fehler bei der Netzwerksuche" (translated: "error while searching for networks")
Click to expand...
Click to collapse
Yeah Android tends to do that a lot. Usually if that happens I toggle airplane mode off and on, and then try the list again. Sometimes it takes ten minutes of trying to finally get a successful scan for networks that lists all the carriers it can see.
Sent from my Galaxy Nexus using Tapatalk 2

Ok, I was now able to get to the carrier list and manually selected the correct one. But that didn't help either.
When the other SIM card, which I will test tomorrow, also doesn't get 3G access, I will send the device back to google and hope, they replace it for me...

Ok, seems like my N7 has a defect. I will call google to ask for a replacement N7...

kroegerama said:
Ok, seems like my N7 has a defect. I will call google to ask for a replacement N7...
Click to expand...
Click to collapse
Glad to hear you finally got confirmation. Based on your troubleshooting, that was looking more and more likely. I'm sure Google will replace it for you properly.

I just called google and they will send me a new N7. And when the new one arrives, I have to put my defect one in the box and send it back. That's very customer-friendly. So I can use the N7 (without 3G) until I get the new one

[Q] Galaxy S4 SGH i337m Sim/Network Unlock Help

Ok, I'm going to try to make a long story short, i hope that i've posted in the correct forum, I've been scouring this forum and others but nothing I've found has quite fixed my issue.
Got my S4 locked to Bell in Canada. Heard it was really easy to unlock [service menu *#0011# method] but once I got to Indonesia [for travel] expecting to be able to use my phone I found that the service menu was no longer available. Ok, no problem, there must be other ways;
I ended up paying for an unlock code from a site, it didn't work. In fact, immediately after I press 'unlock' it would say 'network unlock unsuccessful'.
I thought they gave me a faulty code but when the code I bought FROM Bell was the exact same one, and had the exact same problem I figured it was likely 'region locked'
I ended up flashing a stock rom with odin, one from a weird unlocking site, and eventually I got it working. The only problem was that whenever I'd go into screen lock I'd lose reception and have to airplane mode on and off to get it again.
After Indonesia I went to Turkey, was unable to connect at all with one of their service providers, but had no problems with Vodafone. I think this may have been a side effect of regionlock away app, I needed to use that as well.
Once I got back to Canada I went custom recovery with cwm and flashed Cyanogenmod. This was fine, no reception problems, 10.2 - 11 was all good.
NOW I am in Poland, and getting the same problem I had in the first place. Whatever Cyanogenmod did, re-locked my device, in some way, I'm guessing.
I'm now rooted, with TWP recovery, running Android 4.4.4 Dave GPE rom, and would REALLY like to be able to use my Polish sim card with this fantastic setup. Chainfire's regionlock away app does not work, gives me a CSC error message. My phone now says it's an i9505 instead of i337m
Anything I have overlooked? Any way I can get this fully unlocked and working the way I want it to?
*NOTE* I can't access *#0011# service menu, even though I flashed [i think] stock dialer.

You are not in the correct section
You need to be in this section.
http://forum.xda-developers.com/galaxy-s4-att/general
I can help you a little though. If the unlocking methodes fail, then it's usually because you don't have an older modem. You need to look for the modem you should flash in order for it to work. Afterwards you can flash the modem again you are on now. If you can't find it, just flash an old modem and try.
I find it hard to believe that Cyanogenmod could have caused this though.

Cool, that will be my next phase of attack. I appreciate the redirect and thoughts (Y)

No Service with Sim Card Inserted

A few days I woke up with no service on the Nexus 6p. This was a few days after updating to the latest oreo build. Sim card seems detected because when I take it out another message shows up "No SIM card - No service", and when I put it back it only shows "No service". Tried putting the card in a Nexus 5X and it works fine.
Tried the following with nothing working so far:
- Switching 2G/3G/LTE and rebooting in between.
- *#*#4636#*#* and turning off the radio, switching between the different options of GSM/LTE/etc...
- Restoring a working nandroid backup
- Reflashing different ROMs
- Factory reset
- Factory reset then flashing ROMs
- Wiping cache and dalvik
- efs fix in twrp
Hardware version ANGLER-VN2
IMEI shows up under IMEI information tab but not under SIM Status tab, there it shows not available.
I live in Ontario Canada, carrier is Freedom mobile.
So now I'm stuck, tried calling google and hwawei and they won't do an RMA because my warranty is expired.
Anyone has any ideas to try?
Thanks in advance.

Not that this is going to help, but this has GOT to be an Oreo issue, myself as well as at least 4 others that I have seen has been getting the No service, or No Sim, mine did the No Sim, then started bootlooping.
---------- Post added at 07:36 AM ---------- Previous post was at 07:06 AM ----------
https://www.theandroidsoul.com/fix-...d-wifibluetooth-issues-restoring-twrp-backup/

No this has nothing to do with O.
Which version phone do you have? H1511 or H1512?
What country are you in now?
What is your carrier? If MVNO state that.
Are your IMEI and phone numbers showing up in settings?
Everyone, please put the most basic information in your profile like where you live, which carrier you are currently on, and maybe even which variant of your phone.

I updated the first post with more info. How do I tell if I have H1511 or H1512? I bought it from the google store in Canada.

More information is good. Please update your XDA profile so the next person trying to help can check there first. You can find the device variant by booting to bootloader (not recovery) and using the vol toggle to navigate to "Barcodes". IMEI should show up there too. Date of manufacture, Serial #, etc. I think you should have started a normal thead, not Q/A, BUT your IMEI and a lot of other information should be showing up under SIM info. That's a problem. Second, you say you did the EFS fix in TWRP. Can you explain how you did this? Did you use one of YOUR OWN TWRP backups which contained the modemst1,modemst2 and restored ONLY those two partitions to your device? Did you receive any confirmation or error? Have you tried using a SIM from a Rogers or Telus in your phone to see if the SIM info shows up?

Thanks for the help, I'll update my profile with this info as well.
in the bootloader the IMEI shows up along with the rest of the info. It's a H1511 device.
The EFS fix is by following this: https://www.theandroidsoul.com/fix-empty-imei-corrupted-efs-no-sim-unknown-baseband-wifibluetooth-issues-restoring-twrp-backup/
is modemst1 and 2 contained in the twrp backup? and if so how do I restore it? in restore options there's system, data, vendor and boot only. I guess it's an option in the backup that I haven't selected?
I tried another SIM also from freedom and it didn't work. I don't have a Rogers or other SIM to try currently.

Right, so if you didn't ever select the EFS partitions when using TWRP Backup, you never backed them up so under Restore they don't show up (so you can't use that method). You can however use TWRP terminal or fastboot to wipe those and reboot. I would be sure to try at least one SIM from either Rogers or Telus. If that doesn't work, then wipe the EFS partitions and let them rebuild (hopefully).

Definitely Oreo issue. Google messed with something and it broke data for many people. I have been troubleshooting this for the last week (Verizon, US, fully stock 6P) and finally found a thread where a Google rep acknowledged the problem and said it was high priority for a fix.

I wish you luck with that one @LucJoe. This has been happening for the past 2 years from MM, N, and now O...and XDA is full of threads (just look). So you just go ahead and wait for Google to fix it for you, LOL. - Not a new issue related to O.

Never happened to me before updating. The data issues manifest differently across different carriers but for some reason Oreo likes to play it safe and disconnect data. I have not been able to get LTE for more than a couple seconds, but will get slow unstable 3G occasionally. Google confirmed the issue here: https://productforums.google.com/forum/#!msg/phone-by-google/kw3ZcXd1BVs/7HYuANdoAgAJ

A recent success using terminal from TWRP (or the OS if you are rooted). You can also use fastboot to do the same thing using the commands in the article posted in this Q/A (method 2). Good luck! See thread here.

This seems like it's a different issue described in that thread. I'm not running out of data, there's no service and no connection of at all to any network.

I did find that and try it before posting here. It did nothing to fix the problem. It did say that something was copied over '4 MB copied, at 14.3 MB/s' something like that but nothing changed.

I also have the same issue. Have tried everything including going back to stock 7.1.2 & locking the bootloader. Nothing seems to work. Interestingly, when i pull up the hidden phone diagnostic menu, it shows all cell measurement info which means that the antenna is receiving signals but the phone somehow is not registered on the network?

I can wipe those partitions with fastboot but is it safe? I have never used TWRP and my problems started after updating to Oreo. Is there a chance the official OTA could corrupt those partitions?

@LucJoe- That fix is not for you. That is for users who have no IMEI or phone number under About Phone>>SIM info. Your issue (as I understand it) is a weak and intermittent signal that keeps disconnecting LTE and sounds like a carrier or SIM issue. Why not go get a new SIM provisioned for your phone. That or pop somebody else's SIM in your phone and see if you get a different outcome.

Yes that was my first thought as well. I got a new SIM, then another one. So 3 SIMs now with the same result. I've been on the phone with so many techs from Verizon/Total Wireless and none of them have any answers. If I put the same SIMs into a Moto E4 I picked up for testing, it works fine. But the 6P immediately disconnects from LTE then bounces between 3G/1X.
My next test is to try a SIM from a different network I guess... maybe Verizon is blocking my 6P. Or maybe my LTE radio is damaged somehow.

So I did this using TWRP but wasn't sure if it actually went through or not. I did it now through adb from pc and also fastboot and it says permission denied. Any idea how to bypass that?

S8 Active SM G892U, was Sprint, unlocked and on T-Mobile. Sprint Update broke Volte

Hi,
I have a Samsung S8 Active G892U which I bought used as an unlocked phone. It's clear it was originally a Sprint phone, but I have been using it with no problems on T-Mobile USA. It was running firmware G892USQS3BRI1 until today
Today I was prompted to install the latest software update ( G892USQS3BSA1 - this was clearly a Sprint update; it appears my phone is still getting Sprint updates, which makes sense, as it has Sprint firmware).
There was a warning on the Software update screen that the update would stop Volte working, and I would therefore no longer be able to access data while in a phone call. I (foolishly!!) assumed this would not affect me as I was on T-Mobile. I regularly use data while on the phone, so I know there was no issue with this previously.
The upgrade has completed, and I can no use data while making a call (I am in a LTE area at the moment). There is no sign of any option to enable or disable Volte anywhere in the settings menus
I did try going into Settings->Connections->Mobile Networks and changing Network Mode from "Automatic" to "LTE/CMDA." (as various forums indicated that doing that would provide a menu where I could re-enable volte)
This made the situation worse - I could no longer make calls. I have changed back to 'Automatic' , and can make calls again, but still loose data connectivity when making a call.
Is there any way I can restore my previous ability to use data while calling?
I am wondering:
a) If there is a way to renable Volte without reflashing the phone (that would be preferred)
b) If I do flash the phone, what would be the best firmware to go to - Sprint (presumably the previous version), T-Mobile or something custom (I'm clearly concerned about bricking the phone here)
c) It's several years since I've found myself re-flashing a phone - I see lots of references to "Odin" as the tool to use - is that correct, and could someone point me to the best guide on using it?
Thanks in advance..

You can flash the Sprint latest firmware over the current firmware and I think that should do the trick because I did it and so far so good but proceed with caution I have no experience in dirty flashing but as long as you just stick to the AP file and don't load the bootloader etc I think you should be safe from bricking because as far as I know when the boot loader is gone you can't repair anything