Database Info

Mobile Network Issue, apps Not Connecting

Hello guys, I'm having a huge issue with my mobile network.
For the past two weeks I've not been able to make use of my mobile network correctly, it sometimes works, but most of the time doesn't. The icon in my status bar shows there is activity, it's fully connected to 3G or LTE, even with full bars. But all my apps like Telegram, Pokémon go, Messenger and the likes are stuck "reconnecting" to the network, as if my phone doesn't have any reception at all. At some points even SMS messages refuse to send, even though I've got full reception.
I've already gotten my SIM card switched out, attempted multiple clean flashes and the issue still persists.
My current firmware: 0.1.c1.11-00006-M8974AAAAANAZM-1
Current ROM: idprophecy's unofficial optimized lineage-14.1-20180413-UNOFFICIAL-bacon
Current Recovery: Kutep0v TWRP 3.2.1-K2
Is there anything I can do? I'm getting really desperate.

I have flashed countless of other ROM's by now, and different firmwares. Yet I've yielded no results, is there nobody that can be of help?

Is there any other forum or something else of some kind that can be of help? I seriously don't want to be forced to buy a new smartphone just because of some software issue.

Elder Lyons said:
Is there any other forum or something else of some kind that can be of help? I seriously don't want to be forced to buy a new smartphone just because of some software issue.
Click to expand...
Click to collapse
Has no one got back to you?
I hope that I can help.
Firstly. Let's work through.
You seem to know about flashing a ROM so I won't bore you with all the details.
Clean flash!
Wipe everything except Internal Storage & OTG.
Download a different firmware :
MrShme Frankenstein build is a good one to start with.
https://forum.xda-developers.com/oneplus-one/general/firmware-modem-oneplus-one-lollipop-t3300907
Remember to CLEAN FLASH first.
Wipe all except Internal Storage & OTG
(All but the two bottom options unticked).
Next flash a firmware.
Next flash a ROM.
Next flash GApps.
Set it up.
DO NOT INSTALL Magisk or similar yet.
Goto settings ->About Phone->Status->Sim Status.
In there you should find out all the information that you need to check Network.
Also here is an invaluable help section by @Timmmmaaahh:
https://forum.xda-developers.com/on...de-ultimate-answer-to-bacon-flavored-t3567439
I hope that helps you resolve your problems.
Gimme a thanks to let me know that you have read my reply!

bmark240 said:
Has no one got back to you?
I hope that I can help.
Firstly. Let's work through.
You seem to know about flashing a ROM so I won't bore you with all the details.
Clean flash!
Wipe everything except Internal Storage & OTG.
Download a different firmware :
MrShme Frankenstein build is a good one to start with.
https://forum.xda-developers.com/oneplus-one/general/firmware-modem-oneplus-one-lollipop-t3300907
Remember to CLEAN FLASH first.
Wipe all except Internal Storage & OTG
(All but the two bottom options unticked).
Next flash a firmware.
Next flash a ROM.
Next flash GApps.
Set it up.
DO NOT INSTALL Magisk or similar yet.
Goto settings ->About Phone->Status->Sim Status.
In there you should find out all the information that you need to check Network.
Also here is an invaluable help section by @Timmmmaaahh:
https://forum.xda-developers.com/on...de-ultimate-answer-to-bacon-flavored-t3567439
I hope that helps you resolve your problems.
Gimme a thanks to let me know that you have read my reply!
Click to expand...
Click to collapse
Thank you very much.
I ALWAYS do clean flashes though, have never done a dirty one in my life, though I always flash the firmware after the ROM. So, I'll try your order instead.
I'll try this right this very moment and I'll report back with results.

bmark240 said:
Has no one got back to you?
I hope that I can help.
Firstly. Let's work through.
You seem to know about flashing a ROM so I won't bore you with all the details.
Clean flash!
Wipe everything except Internal Storage & OTG.
Download a different firmware :
MrShme Frankenstein build is a good one to start with.
https://forum.xda-developers.com/oneplus-one/general/firmware-modem-oneplus-one-lollipop-t3300907
Remember to CLEAN FLASH first.
Wipe all except Internal Storage & OTG
(All but the two bottom options unticked).
Next flash a firmware.
Next flash a ROM.
Next flash GApps.
Set it up.
DO NOT INSTALL Magisk or similar yet.
Goto settings ->About Phone->Status->Sim Status.
In there you should find out all the information that you need to check Network.
Also here is an invaluable help section by @Timmmmaaahh:
https://forum.xda-developers.com/on...de-ultimate-answer-to-bacon-flavored-t3567439
I hope that helps you resolve your problems.
Gimme a thanks to let me know that you have read my reply!
Click to expand...
Click to collapse
Alright well, it didn't work.
Is it possible my antennae is broken then? I seriously have no idea what else it could be, as the issue started out of nowhere, tried two different SIM cards and the issue still persists.
I've tried pretty much all firmwares, a ****load of ROM's and the likes but it still persists.
Though I don't understand how it periodically works fine. Let's say my mobile network works like it should for about a minute, then it's gone, then it's back again after a random amount of time, whilst my location hasn't changed at all. Though sometimes it cuts out completely when going through a certain part of my village, whereas I used to have perfect signal there before this issue started happening. Though the signal bar shows it's still fully connected to H+ or 4G, this is so weird and it's driving me insane.

Does anything show up in the settings at all?
Does it show an imei number?

bmark240 said:
Does anything show up in the settings at all?
Does it show an imei number?
Click to expand...
Click to collapse
If I dial "*#06#" I indeed get an IMEI number, in the screenshot is what shows up in my sim card status inside of settings.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

What about swipe down from quick tiles. Press on mobile signal symbol.
Top right menu (3 dot descending menu)-> Mobile Networks->Access Point Names->there might be up to five different options. Make sure you find out your APN settings & delete the doubles. Make sure under Bearer LTE is selected & any other bands that your provider uses.
Does #*#*4636*#*# in phone show up? Refresh mobile and update. Use LTE setting (plus others) in drop down box.
Other than that can you use a friends SIM to make sure that your provider is compatible?
Or did the SIM always work until recently?

bmark240 said:
What about swipe down from quick tiles. Press on mobile signal symbol.
Top right menu (3 dot descending menu)-> Mobile Networks->Access Point Names->there might be up to five different options. Make sure you find out your APN settings & delete the doubles.
Click to expand...
Click to collapse
I've already done this multiple times, to no avail. All settings are always correct as well, even after flashing a new ROM.
bmark240 said:
Make sure under Bearer LTE is selected & any other bands that your provider uses.
Click to expand...
Click to collapse
Alright, it was "unspecified" before, but it's been on this setting since I've gotten the phone (Which was three years ago.). So it'd be weird if that suddenly would be an issue, that didn't fix it either though.
bmark240 said:
Does #*#*4636*#*# in phone show up? Refresh mobile and update. Use LTE setting (plus others) in drop down box.
Other than that can you use a friends SIM to make sure that your provider is compatible?
Or did the SIM always work until recently?
Click to expand...
Click to collapse
Yes it does show up and I tried messing with those settings as well, again, no difference. :/
This is so weird, I never had an issue before this started happening, it's so incredibly frustrating and annoying.
I've also tried using a different sim card of a different provider yesterday, and it throws me the exact same issue.

Maybe look here.
https://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
It may or may not work. I have no guarantees. It could relate to EFS.
But I have exhausted a few of my options. Maybe you might consider
the help of @Timmmmaaahh.

Thanks for the tag, Mark.
Elder Lyons said:
... it should for about a minute, then it's gone, then it's back again after a random amount of time, whilst my location hasn't changed at all. Though sometimes it cuts out completely when going through a certain part of my village, whereas I used to have perfect signal there before this issue started happening. Though the signal bar shows it's still fully connected to H+ or 4G, this is so weird and it's driving me insane.
Click to expand...
Click to collapse
Hey there! Looks you're in pretty deep so that calls for a bootloading adventure. Before you proceed, do two things: use that K2 recovery to perform an EFS backup (as you can see your IMEI, it is not corrupted) and check with your provider if there are any outages on the network.
All good? Great, let's proceed. This will require some patience so please hang in there and read all steps before doing them. It's fairly simple but you can't skip a single thing. First make backups of your internal data (cat pictures, cat videos,... you know, all your cat stuff) then make a backup of any apps you want to salvage later and make sure the whole lot is copied to an external source (including the EFS backup!).
Then simply follow this guide: https://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
However, this is very important: do NOT follow step 4! Resetting flags or locking the bootloader on OPO is a very bad idea.
This should take you back about three years, enjoy the nostalgia and do follow the initial setup and do test your connection in this old skool environment. Working better? Great, flash TWRP again, wipe data and stuff and install your preferred ROM. Didn't work at all? Then I'm deeply sorry, your hardware is indeed starting to fail (or the SIM is dying but you seem to have checked that).
Good luck!

bmark240 said:
Maybe look here.
https://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
It may or may not work. I have no guarantees. It could relate to EFS.
But I have exhausted a few of my options. Maybe you might consider
the help of @Timmmmaaahh.
Click to expand...
Click to collapse
Alright, I'll first do this and then restore it to full stock.
Timmmmaaahh said:
Thanks for the tag, Mark.
Hey there! Looks you're in pretty deep so that calls for a bootloading adventure. Before you proceed, do two things: use that K2 recovery to perform an EFS backup (as you can see your IMEI, it is not corrupted) and check with your provider if there are any outages on the network.
All good? Great, let's proceed. This will require some patience so please hang in there and read all steps before doing them. It's fairly simple but you can't skip a single thing. First make backups of your internal data (cat pictures, cat videos,... you know, all your cat stuff) then make a backup of any apps you want to salvage later and make sure the whole lot is copied to an external source (including the EFS backup!).
Then simply follow this guide: https://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
However, this is very important: do NOT follow step 4! Resetting flags or locking the bootloader on OPO is a very bad idea.
This should take you back about three years, enjoy the nostalgia and do follow the initial setup and do test your connection in this old skool environment. Working better? Great, flash TWRP again, wipe data and stuff and install your preferred ROM. Didn't work at all? Then I'm deeply sorry, your hardware is indeed starting to fail (or the SIM is dying but you seem to have checked that).
Good luck!
Click to expand...
Click to collapse
Hey!
Alright, thanks for the detailed post. There's no outages though, since it's been going on for a month now and I tried a different provider already it's most definately the phone itself.
I'll try this out and see what gives. If this doesn't work I probably have to replace my daughterboard, right?
Cheers!

Elder Lyons said:
I'll try this out and see what gives. If this doesn't work I probably have to replace my daughterboard, right?
Cheers!
Click to expand...
Click to collapse
I'm afraid I can only be of assistance on the software part
Careful with @bmark240's suggestion! One of the instructions entails "RUN THE flash-all.bat FILE FROM FASTBOOT", that might contain a "fastboot oem lock" command, which is an OPO killer! I have experienced this first hand.
If you've already taken the steps, it may still be fine. If "fastboot oem unlock" works, you're in the clear. If not, there's still some hope... I'll guide you through it if needed.
Cheers!

Timmmmaaahh said:
I'm afraid I can only be of assistance on the software part
Careful with @bmark240's suggestion! One of the instructions entails "RUN THE flash-all.bat FILE FROM FASTBOOT", that might contain a "fastboot oem lock" command, which is an OPO killer! I have experienced this first hand.
If you've already taken the steps, it may still be fine. If "fastboot oem unlock" works, you're in the clear. If not, there's still some hope... I'll guide you through it if needed.
Cheers!
Click to expand...
Click to collapse
Alright well, I've literally tried everything by now. Even multiple times in a row, different methods etc, still to no avail.
To be honest I think changing my daughterboard would be the best idea at this point, finally. Even though I'm not even sure that will fix it. Where can I buy genuine Oneplus One parts though?

Two months later, still no solution to the problem.
I still don't get this. It shows full reception, and the fact I've got a signal in the IMEI menu, it just baffles me.
Isn't there a single I can do, run a test or something to see why this is happening? I'm truly desperate.

Motorola G5 Plus Bootloader

I typed in the command to get oem_unlock_data and got my devices string. I input it into fastboot and it says "phone not eligible". I previously had a Motorola G5 plus and had no issues and aft r checking the phone is definitely eligible. I put the Gmail I use onto the phone from my Motorola account and am still having errors. I read a thread stating my device id may be within settings option of phone and if i take off this setting it may work. I cannot find this option within settings. Any ideas on how to unlock bootloader on an eligible device that is telling me is ineligible? My device also says oem_locked in bootloader screen so I know this is the case. Any input would be highly appreciated.

WarrenC1236 said:
I typed in the command to get oem_unlock_data and got my devices string. I input it into fastboot and it says "phone not eligible". I previously had a Motorola G5 plus and had no issues and aft r checking the phone is definitely eligible. I put the Gmail I use onto the phone from my Motorola account and am still having errors. I read a thread stating my device id may be within settings option of phone and if i take off this setting it may work. I cannot find this option within settings. Any ideas on how to unlock bootloader on an eligible device that is telling me is ineligible? My device also says oem_locked in bootloader screen so I know this is the case. Any input would be highly appreciated.
Click to expand...
Click to collapse
Go to system settings>developer options, find the OEM unlock setting and toggle it to the enabled position. To enable developer options, go to system settings>about>software info>build number(or wherever your build number setting is located in your device's settings). Tap on the build number 7-10 times quickly, this will enable dev options. Then go back to system settings and you'll see developer options has been added to the list somewhere at the bottom.
Then try your unlock method.
Sent from my SM-S767VL using Tapatalk

Force bootloader unlock for T-mobile 3a?

So I just ordered a Pixel 3a today and it's the T-mobile locked version. Now I think I might have messed up because I just read that the T-mobile version cannot be bootloader unlocked or even flash factory images (or beta?). This honestly didn't even cross my mind because I thought Pixel devices were always fully open and is a main reason why I wanted it.
My question is if there is anyway to bypass this restriction and run the Google factory image? When I got a T-mobile OnePlus 6T there was a tool that allowed me to flash the factory image and then enable bootloader unlocking. I've been searching online but finding conflicting information that is outdated from a year ago.
Edit: What happens if you adb sideload an image with the bootloader locked as described here? https://developers.google.com/android/ota

My pixel 3a is the T-Mobile version. I was able to unlock the bootloader with zero issues. What seems to be the hangup on your end? I've talked to a few people who have had similar issues, and they stated that OEM unlocking was unavailable in the developer options menu. Is this where youre getting stuck? Or does the problem occur in fastboot when you actually attempt the unlock?
If the issue lies in the developer options menu, there's a workaround that I'll have to find for you. But i *think* what is happening is when you do a factory reset, it installs the generic image -- but as soon as it boots up, the Tmobile Sim causes carrier specific settings/software to be overlayed and effectively blocking the "OEM unlock" setting from being toggled. Without researching it, I believe the solution to your problem is to remove the sim card, then do a factory reset. Boot it up, go through the setup without the SIM physically installed. This should theoretically keep the the option to enable OEM locking available to be turned on.
I bought mine through T-Mobile, used it for 3 months and then asked to have it sim unlocked, which they did. At that point, I installed the verizon Sim card, did a factory reset, and the option to unlock the bootloader became available. So the method I laid out above, should work for you. If not, I'll actually dig around and get ya set up.
Let me know how it turns out, k?

eSim on Verizon branded Pixel 3

There are a lot of Verizon branded unlocked Pixel 3. It is reported on the web that eSim has been disabled on these. However, a quick check with *#06# shows two IMEI on this phone. So maybe eSim is there. I need eSim to use International roaming using USMobile plans. Anybody have any ideas about what happened to the eSim on this phone?

rajivtiwary said:
There are a lot of Verizon branded unlocked Pixel 3. It is reported on the web that eSim has been disabled on these. However, a quick check with *#06# shows two IMEI on this phone. So maybe eSim is there. I need eSim to use International roaming using USMobile plans. Anybody have any ideas about what happened to the eSim on this phone?
Click to expand...
Click to collapse
I am fine to root this phone. Will that enable eSim?

Code:
adb shell settings put global euicc_provisioned 1

I have had a personal conversation with a representative at Google fi and Google. Unfortunately because Google has no idea how Verizon restricted the use of this function, unfortunately any pixel 3 with a sku from Verizon is unable to have this feature activated at this moment. However they expressed interest in that if I discover a way to activate it and file a bug report, they will most certainly be interested in looking into the idea of activating the future on all pixel 3s.
In the meantime they do offer a free SIM card for anyone who wants to join Google fi and has a Verizon pixel 3. They have confirmed that although the device is Verizon made or rather Verizon issued, their SIM card for Google fi does indeed work on this device. It's just unfortunate you need the physical SIM card. If you do not get the SIM card through Google you will have to pay about $10 maybe a little bit more to get it anywhere else.

rajivtiwary said:
I am fine to root this phone. Will that enable eSim?
Click to expand...
Click to collapse
How to root a Verizon pixel 3/3xl please?

Pixel 3xl said:
Code:
adb shell settings put global euicc_provisioned 1
Click to expand...
Click to collapse
My Phone is a refurbished one. Imei.info says it was originally purchased in Japan. With no esim option.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have tried adb shell settings put global euicc_provisioned 1. nothing happens. No + Appears for me to add network.
I have tried adb shell get props euicc_provisioned . It shows that the property has been set to 1.

Pixel 3xl said:
How to root a Verizon pixel 3/3xl please?
Click to expand...
Click to collapse
See my recent post in the thread you commented on earlier. I think I'm getting closer. One thing that works in my favor is an existing unpatched CVE in citadel
captainwifi said:
My Phone is a refurbished one. Imei.info says it was originally purchased in Japan. With no esim option.
View attachment 5306635
I have tried adb shell settings put global euicc_provisioned 1. nothing happens. No + Appears for me to add network.
I have tried adb shell get props euicc_provisioned . It shows that the property has been set to 1.
Click to expand...
Click to collapse
There is no real distinguishable way to tell whether your phone is actually through Verizon or not. The only way I pretty much was able to tell was looking through the installed applications using an activity launcher. It lists the package names such as com.package.name. one of the carrier setup applications is a Verizon application to set up a phone through Verizon. That's pretty much how I got the message this was a Verizon phone. Google says on any pixel 3 phone that has a Verizon SKU, the esim option is disabled. They don't know how Verizon did it therefore they do not have a process to activate it. They did not however deny my process did anything and seemed genuinely intrigued by the fact I even managed to get that far. That tells me I can probably do more but I only just stumbled upon this and never looked into it any further because I never had any intentions of looking into it any further. Only because I didn't think anybody had any interest in it and I stand corrected. If I come across anything else I will gladly update everybody.

captainwifi said:
My Phone is a refurbished one. Imei.info says it was originally purchased in Japan. With no esim option.
View attachment 5306635
I have tried adb shell settings put global euicc_provisioned 1. nothing happens. No + Appears for me to add network.
I have tried adb shell get props euicc_provisioned . It shows that the property has been set to 1.
Click to expand...
Click to collapse
Try
*#*#794824746#*#*
In your dialer
It will give you a message esim enabled
Try and see if it works.

I got the esim enable message. Thanks. But still stuck in the checking network info loop.

This thread hasn't been active in awhile, but thought I'd add my experience.
I have a vzw pixel3, but it was bought on Woot and it was new in box, never activated. Following another thread that indicated; remove vzw sim, minimal startup but connect wifi, enable dev options, select oem unlock. It worked.
I immediately did a firmware update with latest google generic 06/05 zip. Then decided to relock bootloader. No probs, and it can still be unlocked.
Then, today, tried info in this thread. Sure enough, changed the setting to 1 and then a '+' sign showed up for additional networks. Followed though with that and 2 showed up; Google Fi and Sprint, and also an option to scan a Q code if your's wasn't listed.
So, I guess one can say that the vzw phones, so long as they haven't been activated on vzw network, can be made to work as one might like. A big **IF** though, I realize.

AsItLies said:
This thread hasn't been active in awhile, but thought I'd add my experience.
I have a vzw pixel3, but it was bought on Woot and it was new in box, never activated. Following another thread that indicated; remove vzw sim, minimal startup but connect wifi, enable dev options, select oem unlock. It worked.
I immediately did a firmware update with latest google generic 06/05 zip. Then decided to relock bootloader. No probs, and it can still be unlocked.
Then, today, tried info in this thread. Sure enough, changed the setting to 1 and then a '+' sign showed up for additional networks. Followed though with that and 2 showed up; Google Fi and Sprint, and also an option to scan a Q code if your's wasn't listed.
So, I guess one can say that the vzw phones, so long as they haven't been activated on vzw network, can be made to work as one might like. A big **IF** though, I realize.
Click to expand...
Click to collapse
I can confirm I am able to reproduce exactly what you are seeing on a Vzw unlocked Pixel 3 . Unfortunately, I believe that Vzw wiped the device EID before shipping these phones. I am unable to view the individual devices EID which is required to register the device as an Esim. The processes outlined above appear to be simply software locks to keep you out of something that is not available on the device. I would love for someone to prove me wrong on this theory.

woodysgate said:
I can confirm I am able to reproduce exactly what you are seeing on a Vzw unlocked Pixel 3 . Unfortunately, I believe that Vzw wiped the device EID before shipping these phones. I am unable to view the individual devices EID which is required to register the device as an Esim. The processes outlined above appear to be simply software locks to keep you out of something that is not available on the device. I would love for someone to prove me wrong on this theory.
Click to expand...
Click to collapse
I don't think you're wrong actually. I didn't go any farther than what I mentioned, iow, didn't actually add an esim account.
But research and trying to add acct, yeah, no EID is a big issue. I didn't try extensively as I don't need esim ability, but thought after what I'd done, unlock, flash generic rom, etc, that everything would be working... and mostly it is, but not esim it appears.
alas, cheers

Cannot find OEM Unlock for Samsung galaxy s21 + 5g

Last month, I decided that I wanted to try rooting my Samsung galaxy s21 + 5g (model name SM-g996u), and I got as far as unlocking the network before I hit a snag. In all of the tutorials I have looked at concerning how to root my device, they all keep saying that I need to OEM Unlock my phone under the developer settings. However, as the title of this post would indicate, that setting is not present in the development settings. I have just about lost my damn mind trying to find and enable this setting via online tutorials, and I keep coming across the same suggestions: configure date/time setting so that it is not automatically set, manually set the date back a couple of months, go to dev settings and disable auto-update system setting, disable 'Download updates automatically' setting in software update (this is the only step I was not able to follow because that setting appears to have been removed from more updated version), and restart the device. I even tried removing my sim card, resetting my phone, and retrying the previously outlined steps. Nothing has worked. Is there anyone out there that can help me with this? Any info would be great.

Is device leased from a carrier, e.g Verizon? AFAIK by default this phone has OEM Unlock option in Android's Developer Options.

[Android][UNSAMLOCK] Bootloader Unlock for Samsung US/Canada Devices
This thread is @svetius approved Important notice: Do not update to April 2023 security update (XXXXXXXXXXWCX) or later. Examples: G998USQS6EWCA, N986USQU4HWD1. Samsung has patched the bootloader unlock again on those updates. NOTE: The OneUI...
forum.xda-developers.com

whiggs2 said:
Last month, I decided that I wanted to try rooting my Samsung galaxy s21 + 5g (model name SM-g996u), and I got as far as unlocking the network before I hit a snag. In all of the tutorials I have looked at concerning how to root my device, they all keep saying that I need to OEM Unlock my phone under the developer settings. However, as the title of this post would indicate, that setting is not present in the development settings. I have just about lost my damn mind trying to find and enable this setting via online tutorials, and I keep coming across the same suggestions: configure date/time setting so that it is not automatically set, manually set the date back a couple of months, go to dev settings and disable auto-update system setting, disable 'Download updates automatically' setting in software update (this is the only step I was not able to follow because that setting appears to have been removed from more updated version), and restart the device. I even tried removing my sim card, resetting my phone, and retrying the previously outlined steps. Nothing has worked. Is there anyone out there that can help me with this? Any info would be great.
Click to expand...
Click to collapse
This device(all of the US models) doesn't have the OEM unlock option. As far as I know, these devices have to be unlocked via a paid service from a 3rd party.

jwoegerbauer said:
Is device leased from a carrier, e.g Verizon? AFAIK by default this phone has OEM Unlock option in Android's Developer Options.
Click to expand...
Click to collapse
Device has been paid off. It is also network unlocked as well. The device was originally leased from Tmobile. I am aware that the setting is supposed to be in developer settings. I am telling you, it is not showing up for me.

whiggs2 said:
Device has been paid off. It is also network unlocked as well. The device was originally leased from Tmobile. I am aware that the setting is supposed to be in developer settings. I am telling you, it is not showing up for me.
Click to expand...
Click to collapse
May I'm wrong but the fact that the client have covered the contract, doesn't mean that the carrier do that, if a special petition was not presented to them, then, they don't care about. If the device came with a firmware that came with that feature disabled, so it, also, ends its "normal" life with the same featured included (or not) in the firmware by default.
But you could make advantage from the network unlocked condition, switching to a different firmware it would be possible, and, the option may appear.

SubwayChamp said:
May I'm wrong but the fact that the client have covered the contract, doesn't mean that the carrier do that, if a special petition was not presented to them, then, they don't care about. If the device came with a firmware that came with that feature disabled, so it, also, ends its "normal" life with the same featured included (or not) in the firmware by default.
But you could make advantage from the network unlocked condition, switching to a different firmware it would be possible, and, the option may appear.
Click to expand...
Click to collapse
I have seen that suggestion mentioned before online, though I have not really found any good tutorials on how to go about doing that. Any suggestions?

Droidriven said:
This device(all of the US models) doesn't have the OEM unlock option. As far as I know, these devices have to be unlocked via a paid service from a 3rd party.
Click to expand...
Click to collapse
This - The 'U' devices do not have OEM unlock by default.

whiggs2 said:
I have seen that suggestion mentioned before online, though I have not really found any good tutorials on how to go about doing that. Any suggestions?
Click to expand...
Click to collapse
This may be just a kind of starting point, to have in mind, but that need more research though, I did it in my GN8 but with your device, things may be different.
There are some things you have to check, in the download screen, KG has to be completed, not prenormal or checking, also search for the CSCs that are compatible for your device, this is one of the tutorial, kind of, that I followed https://www.getdroidtips.com/guide-...ocked-firmware-galaxy-note-8-sm-n950u-n950u1/