Database Info

No Internet Data in CM14 (no G,3G,4g)

Hi guys, I have been trying to get the MI 4c working with the data but still with troubles. I have restored to stock 2 times ( a long nightmare getting locked by the way) and still without getting the Data working. I can call and use internet with WIFI but not by itself.
Anyone can give a hand?
Trying with different bands in the menu of *#*#4636#*#* without a happy end.
THANKS A LOT

trying this guide about Restoring IMEI DIDN´T work!!!
en.miui.com/thread-315233-1-1.html

Are you using 2 Sims? Have you tried manually adding the apn details?

ermacwins said:
Are you using 2 Sims? Have you tried manually adding the apn details?
Click to expand...
Click to collapse
I am using only 1 SIM, and YES I have tried to put APN manual.

Does the *#06# gives you an IMEI number (or 2...).
If not, what happen to loose it? You should start by explaining that.

Kéno40 said:
Does the *#06# gives you an IMEI number (or 2...).
If not, what happen to loose it? You should start by explaining that.
Click to expand...
Click to collapse
It is giving me 2 IMEI NUMBERS but in Settings, About Phone and Status doesnt show my mobile number.
AFTER RESTORE TO LATEST MIUI I can use DATA 4g but I want to use Cyanogenmod instead, lets see.

tiredofthisbs said:
Settings, About Phone and Status doesnt show my mobile number.
Click to expand...
Click to collapse
That's not important.
So in the CM, there is just a problem with APN.
Post what are they maybe someone from your country could help....

After restore Stock rom MIUI 6.1.7, unblocked with fastboot oem unlock and flashing twrp and CM 14.1 I got 4g working I went to something about SIM CARD activate, and removing all APN and putting my APN manually. I did it before but didn't work .But after all it interrupts also WIFI after a few minutes I dont understand why.

Get LTE Back

Hello guys,
As I have stated on my Q&A thread I was going to be posting a tutorial in order to bring LTE back for those who had lost it. I will give you some background in order for you to know how I lost it and then I will explain how did I get it back:
How did I lost it:
I had bought a Xiaomi Mi A1, and had given my previous Redmi Note 5 SD636 to my wife, for reasons that don't care at this time haha. So, I get it and I am on carrier Tigo Colombia, which uses band 4 AWS-1 . Everything was working as expected, I had my 4G LTE as a regular user. I had installed the gcam, unlocking bootloader and then relocking it, flawless. Everything was working perfect.
The issue came, when I decided that was time to try one of the AOSP Pie roms. I decided to try Simplix Blue, which called my attention due to not being available on RN5 the device that I used to own. I am pretty sure, that has nothing to do with the rom, for reasons that I will explain later on, but more fault of the SD625, boot.img and modem of the device. So I flashed the rom, as I usually do, following instructions, installing TWRP, changing slot, bla bla bla.. you already know this. So I booted up the rom, and it was on 3g, seemed strange, but on the initial set up I thought myself it was more of configuration on the network side. So, as soon as I finished the set up, I went into settings and selected LTE/WCDMA, did not work. Selected only LTE, did not work. Dialed #*#*4636*#*#, choose LTE network, did not work. So I said, this is more of a ROM problem then. Installed Arrow OS, same issue. Started getting strange, so I said, maybe it is a stock rom problem on my device, so I downloaded Stock ROM and flashed. Surprisingly, did not work either.
So I started to look around for solutions, wrote on telegram group and got ignored, as usually happens on that group, and I posted a Q&A thread here, which you can find here:
https://forum.xda-developers.com/mi-a1/help/lost-lte-pie-t3852725
Got no response at first, and then I saw some similar threads with same issue but no resolution. So I started looking for myself. Lasted 2 days looking for a solution as I was completely sure it was not a Hardware issue as I had it before. So, I will explain how I get it back after combining a tutorial with some personal knowledge.
I need to give credits to: @kirtikhurana, he does not even know I used his tutorial for Lenovo P2 haha, but it is worth it thanking him as his thread helped me a lot.
What we need:
QPST
QXDM (You can find this two programs on this thread, 3rd post https://forum.xda-developers.com/lenovo-p2/how-to/enabled-4g-ca-p2-t3707584) Once again, thanks to the creator of the thread for this.
Minimal ADB and Fastboot
LTE Band Calulator app(Which you can find on play store)
Network signal guru app (Which you can find on play store too)
Stock rom (Then you can change it and flash whatever rom you want)
First thing, is have the stock rom rooted, with magisk or whatever method you choose to root it. We will connect the phone to our PC and turn on the USB debugging. For the ADB and fastboot, let's make sure we open the CMD with administrator rights.
I will assume you had already installed QPST and QXDM. We will open a CMD where we have ADB and Fastboot and type:
Code:
adb shell
and then:
Code:
su
We will grant adb shell superuser rights on our phone. As soon as superuser rights are granted, we need to enter on DIAG mode, for that, we will type on the CMD:
Code:
setprop sys.usb.config rndis,diag,adb
On the original thread, it is stated that you can also dial *#*#717717#*#* to enter directly in diagnostic mode (Use this option if QPST does not detect your phone on following steps and reboot).
Now, we will go to QPST>bin folder and open QPST Config, with administrator rights. Check whether your phone is connected or not on diagnostic mode. I will clarify something here:
On the second tab of the QPST Config, you will see an option to add ports, by default, you can select COM1, which is usually not the port where we connect the USB. If that happens and does not detect your device, go to device administrator in the control panel, and make sure your android phone is detected as Diagnostic device, you can check that on USB and ports, where you will also find COM1 as another device. As soon as you make sure drivers and everything is ok, but still does not detect the phone, do the step previously mentioned of: *#*#717717#*#* and reboot.
Now, assuming that your phone is showing there, you will now go to QXDM>bin and open on the tools bar, options and click on communications: You will see your device and the type of model of the processor, in this case, should be MSM8986 or similar. Check below and you will see an option called target port, check on drop down list and choose the com port where you have your device. Now you can close that window.
Now, we will go to view and pick NV Browser, then look for the filter LTE. Then we will select the first option (if this and the other option if grayed out means it has not taken the connection of your phone).
On that first option, you will see two fields below. We will choose the first one and click on read. As soon as we do that, it will autopopulate a number, that number are the bands that you have enabled.
Let's go now to our phone and open LTE band calculator, and let's pick up the bands we need to have (if you write a random number on the app, it will show you which bands will be selected with that number).
Having that number, we will, in QXDM, double click on the input field and write the number that the app has given us and then click on write. As soon as we do that, we need to reboot the phone.
Now, when the phone is already rebooted, we will open network signal guru, provide corresponding permissions and now, click on the three dots at the top right corner and click on lock bands, select LTE. Now, you will see that the band that you were missing, for you to get LTE is there! So what you need to do is select it and click accept. Your phone will freeze for a bit and then reboot itself.
As soon as the phone is rebooted, you will see that you have your LTE back!!
This was the way I was able to get it.
I said it was not a rom, because if you flash stock rom again, with miFlash, you may loose LTE again and need to repeat the process as it happened to me. However, if you are on stock and decide to flash another rom, oreo or pie, you will not lose it.
Hopefully is clear enough for you guys who are facing this issue.
Regards

I lost also band 20 after flashing LOS and after that latest stock
So if i install LOS 15.1 after this method, band 20 will stay unlocked?
Thanks

trance89 said:
I lost also band 20 after flashing LOS and after that latest stock
So if i install LOS 15.1 after this method, band 20 will stay unlocked?
Thanks
Click to expand...
Click to collapse
Yes sir it will! You can do it with no issues whatsoever.

And if i root my system with patched boot.img + magisk method and after this mod i just revert back the untouched boot.img then can i relock bootloader?
ota updates or factory reset won't destroy it?
Thank you

trance89 said:
And if i root my system with patched boot.img + magisk method and after this mod i just revert back the untouched boot.img then can i relock bootloader?
ota updates or factory reset won't destroy it?
Thank you
Click to expand...
Click to collapse
You can do all your stuff. Only thing is if you flash again via MiFlash stock rom, then it may break and you may need to redo the process. But besides that, you can root, unroot, install custom, everything you want to do and you will not loose your band.

Please help! I can't seem to get the device into diagnostic mode or the damn windows drivers don't work. I've installed minimal ADB and drivers from xiaomi. as soon as I enter setprop sys.usb.config rndis,diag,adb no vibrate or anything on my device and in my windows device manager the Android device changes to an ADB interface and a Android device with a yellow exclamation mark. Dialing *#*#717717#*#* doesn't do a thing. I'm on LOS 15.1. Of course no com1 ports to connect to Any ideas?

saski4711 said:
Please help! I can't seem to get the device into diagnostic mode or the damn windows drivers don't work. I've installed minimal ADB and drivers from xiaomi. as soon as I enter setprop sys.usb.config rndis,diag,adb no vibrate or anything on my device and in my windows device manager the Android device changes to an ADB interface and a Android device with a yellow exclamation mark. Dialing *#*#717717#*#* doesn't do a thing. I'm on LOS 15.1. Of course no com1 ports to connect to Any ideas?
Click to expand...
Click to collapse
use google usb driver, it works with all devices: https://developer.android.com/studio/run/win-usb
Jemec26 thanks for the step by step instructions, i got back my lost band

saski4711 said:
Please help! I can't seem to get the device into diagnostic mode or the damn windows drivers don't work. I've installed minimal ADB and drivers from xiaomi. as soon as I enter setprop sys.usb.config rndis,diag,adb no vibrate or anything on my device and in my windows device manager the Android device changes to an ADB interface and a Android device with a yellow exclamation mark. Dialing *#*#717717#*#* doesn't do a thing. I'm on LOS 15.1. Of course no com1 ports to connect to Any ideas?
Click to expand...
Click to collapse
Go with stock rom first. It is not mandatory, but on other roms it may not work.

trance89 said:
use google usb driver, it works with all devices: https://developer.android.com/studio/run/win-usb
Jemec26 thanks for the step by step instructions, i got back my lost band
Click to expand...
Click to collapse
Glad it helped you!

saski4711 said:
Please help! I can't seem to get the device into diagnostic mode or the damn windows drivers don't work. I've installed minimal ADB and drivers from xiaomi. as soon as I enter setprop sys.usb.config rndis,diag,adb no vibrate or anything on my device and in my windows device manager the Android device changes to an ADB interface and a Android device with a yellow exclamation mark. Dialing *#*#717717#*#* doesn't do a thing. I'm on LOS 15.1. Of course no com1 ports to connect to Any ideas?
Click to expand...
Click to collapse
to make use of qualcomm diagnostic mode you must use qualcomm driver, take a look here https://forum.xda-developers.com/mi-a1/how-to/tool-low-level-backup-restore-unbrick-t3790307 in faqs section.
and here an explanation https://forum.hovatek.com/thread-22399.html

Main branch of los and aosp has network issue it needs to be fixed from scratch.

Ok finally I've managed to work through this and it now shows that band 20 is finally back enabled! However there is still no LTE band 20 reception (only band 3 in the city) and yes LTE band 20 signal strength is good when checking with other devices.
Anyway thanks so much for this tutorial but I guess my MiA1 is defective or bricked beyond repair. ;(

saski4711 said:
Ok finally I've managed to work through this and it now shows that band 20 is finally back enabled! However there is still no LTE band 20 reception (only band 3 in the city) and yes LTE band 20 signal strength is good when checking with other devices.
Anyway thanks so much for this tutorial but I guess my MiA1 is defective or bricked beyond repair. ;(
Click to expand...
Click to collapse
Weird. Please upload a pic when you can of the lock bands on the network signal guru app. Also, check with the *#*#4636#*#* the network mode that you are currently running. If your band 20 is already enabled, you should get it. Have you tried different sim?

Jemec26 said:
Weird. Please upload a pic when you can of the lock bands on the network signal guru app. Also, check with the *#*#4636#*#* the network mode that you are currently running. If your band 20 is already enabled, you should get it. Have you tried different sim?
Click to expand...
Click to collapse
Can't upload a screenshot since I'm at work now. LTE discovery shows only Band 3 LTE in the city and no LTE at all only 2G/3G in rural areas (where LTE Band 20 is availble!). Already switched SIMs they work fine (Telefonica Germany).
Signal Guru shows the following locked LTE bands:
B1:2100
B3:1800+
B5:850
B7:2600
B8:900 GSM
B20: 800DD (this one is new since I've unlocked it!)
B34: TDD 2000
B38: TDD 2600
B39: TDD 1900+
B40 TDD 2300
#*#*4636#*#* Shows Radio Band Automatic. Will Check all my steps again. could it be that I need to disable some bands in order to get band 20 working? Got my hand on a working MiA1 and it shows less LTE bands than the faulty one.

saski4711 said:
Can't upload a screenshot since I'm at work now. LTE discovery shows only Band 3 LTE in the city and no LTE at all only 2G/3G in rural areas (where LTE Band 20 is availble!). Already switched SIMs they work fine (Telefonica Germany).
Signal Guru shows the following locked LTE bands:
B1:2100
B3:1800+
B5:850
B7:2600
B8:900 GSM
B20: 800DD (this one is new since I've unlocked it!)
B34: TDD 2000
B38: TDD 2600
B39: TDD 1900+
B40 TDD 2300
#*#*4636#*#* Shows Radio Band Automatic. Will Check all my steps again. could it be that I need to disable some bands in order to get band 20 working? Got my hand on a working MiA1 and it shows less LTE bands than the faulty one.
Click to expand...
Click to collapse
Hmm I did not have to disable other bands but you can try and let us know, it won't damage anything and you can always make a backup. Try disabling bands that you know are not in use.

Tried everything disabled bands - nothing helped. Last Idea was to use the low level backup tool https://forum.xda-developers.com/mi-a1/how-to/tool-low-level-backup-restore-unbrick-t3790307 to backup all partitions from a functioning device with LOS installed and restore it to the one with LTE issues. Now the IMEI is gone. Reflashed August 2017 ROM with miflash to get the damn thing into diagnostic mode again (doesn't that work with LOS?) restored my IMEI, triggered OTA and got a boot loop. I'm afraid I've bricked my device beyond repair
update: I cannot mount my system_a partition in TWRP anymore. flashing stock fails with:
target reported max download size of 536870912 bytes
sending sparse 'system_a' (516697 KB)...
FAILED (data transfer failure (Too many links))
finished. total time: 4.295s
"Flash system_a error"
Any ideas? system_a cannot be 516697 KB in size no way!

saski4711 said:
Tried everything disabled bands - nothing helped. Last Idea was to use the low level backup tool https://forum.xda-developers.com/mi-a1/how-to/tool-low-level-backup-restore-unbrick-t3790307 to backup all partitions from a functioning device with LOS installed and restore it to the one with LTE issues. Now the IMEI is gone. Reflashed August 2017 ROM with miflash to get the damn thing into diagnostic mode again (doesn't that work with LOS?) restored my IMEI, triggered OTA and got a boot loop. I'm afraid I've bricked my device beyond repair
update: I cannot mount my system_a partition in TWRP anymore. flashing stock fails with:
target reported max download size of 536870912 bytes
sending sparse 'system_a' (516697 KB)...
FAILED (data transfer failure (Too many links))
finished. total time: 4.295s
"Flash system_a error"
Any ideas? system_a cannot be 516697 KB in size no way!
Click to expand...
Click to collapse
Whoa bro. I stated on the thread that you need to have stock rom. LOS may not work, after that you could install it. Now, for the prob that you have, try downloading a different image, try to even downgrade it to 7 and see if it works to restore partitions. I would suggest july firmware, some of the fw are not full, some do not even touch partitions, I know that july does, reason why I am suggesting it

Will this work for this problem? https://forum.xda-developers.com/mi-a1/help/4g-update-to-pie-t3877027 It's quite similar.... but with stock beta pie....

arc4d14n said:
Will this work for this problem? https://forum.xda-developers.com/mi-a1/help/4g-update-to-pie-t3877027 It's quite similar.... but with stock beta pie....
Click to expand...
Click to collapse
Yes, it will work. But i suggest you to wait the official fix.

jack_21 said:
Yes, it will work. But i suggest you to wait the official fix.
Click to expand...
Click to collapse
Thank you, I'll wait for a couple of patches before trying this, I just wanted to now all the alternatives

[GUIDE] Activate VoWiFi / WLAN Call

First of all a BIG thanks to ed-gonzo
He made this possible
This is the instruction to activate VoWiFi / WLAN Call on the Poco F1
Its tested and verfied to work with EU ROM (Oreo , Pie and Q based) and german provider o2 (Telefonica)
Before you read on i want to make clear that I am not responsible for bricked devices !
Basic requirements are root rights to do this mod
Maybe latest 2020 Qualcomm Diag QD-Loader Windows 10 Drivers signed are needed for this to work.
!!! Before doing this Mod you should backup EFS-partition !!!
- download QPST tool and install
- enable USB debugging in Developer settings
- now either go to terminal app and type:
Code:
su
setprop sys.usb.config diag,serial_cdev,rmnet,adb
or
adb from PC
Code:
adb shell
su
setprop sys.usb.config diag,serial_cdev,rmnet,adb
- connect Poco F1 with original USB cable to PC
- start PDC (from QPST tool) on PC
- Poco F1 should be recognized by PDC (if not install Qualcomm driver and check Device Manager)
- activate corresponding profile (in case of german o2 its DT_Greece)
- install VoLTE & VoWiFi Enabler Magisk module (optional) or activate setting with dialer code *#*#869434#*#*
- restart Poco F1
- Voila

FAQ:
Q: What are the requirements for VoWiFi
A: A provider resp. plan which includes VoWiFi
Q: How to know if VoWiFi is working ?
A: Put phone in airplane mode and reactivate WiFi only. If you are able to make a call then VoWiFi is working.
Q: Does this only work with MIUI ROM ?
A: No ... its reported to work also on Custom ROMs like LOS, crDroid ...

Thx for this guide! Have been waiting for this.
Does this work with custom ROM (LOS)?
in case of german o2 its DT_Greece? are you sure? german carrier and greece?

saski4711 said:
Does this work with custom ROM (LOS)?
Click to expand...
Click to collapse
in german forum there is a user who has it running.... but it seems that LOS has no icon for VoWiFi
But nlow ...
saski4711 said:
in case of german o2 its DT_Greece? are you sure? german carrier and greece?
Click to expand...
Click to collapse
yes indeed DT-Greece for german o2
I have it up and running ...

der_Kief said:
in german forum there is a user who has it running.... but it seems that LOS has no icon for VoWiFi
But nlow ...
yes indeed DT-Greece for german o2
I have it up and running ...
Click to expand...
Click to collapse
Ok thx will give it a shot as soon as I get access to a windoze PC :highfive:

Ok this definately didn't work on my Poco-f1 with latest LOS16 and 8.11.15 vendor/fw. Funny thing that VoLTE now seems to be gone (Device switches back to H+/E). Got it back by restoring efs. Has anyone else been successful with this running custom ROMs? Even without this "hack" I have been able to activate VoWIFI after 8.11.5 update but it didn't work so I guess this depends on FW version.
Two things - a little offtopic though: Any Idea if this can be tried on the MiA1? I suspect that xiaomi doesn't include support in it's firmware for this device at all and I 'm afraid to cripple both my devices (Poco and MiA1) at the end .
Has anyone had success getting HDVoice with BT headsets on the Poco-f1 with custom ROMs? Sorry for asking this here but in the LOS thread I seem to get ignored with this question / bug report.

@saski4711
to bad that its not working for you.
It defintively works with EU ROMs based on Oreo or Pie.

Double post
*deleted*

der_Kief said:
@saski4711
to bad that its not working for you.
It defintively works with EU ROMs based on Oreo or Pie.
Click to expand...
Click to collapse
Yeah bummer. Will give it another shot the next days maybe I messed up somewhere. Isn't this device supposed to get VoWIFI by default with the Pie update anyway? Maybe this will work OOTB with final pie?

not works with EU pie rom to me too. from Sri Lanka we have VOWIFI network. tried switching many profiles but not works .

saski4711 said:
Isn't this device supposed to get VoWIFI by default with the Pie update anyway?
Click to expand...
Click to collapse
Dont know ... i'm on Stable EU ROM 10.0.6.0 (based on Oreo)

I know for sure it worked out of the box after pie update on stock beta with a service provider in Greece.
Can make settings appear with *#"#vowifi#*#* but being in India don't think providers support vowifi so doesn't work.

sanjay0501 said:
I know for sure it worked out of the box after pie update on stock beta with a service provider in Greece.
Can make settings appear with *#"#vowifi#*#* but being in India don't think providers support vowifi so doesn't work.
Click to expand...
Click to collapse
How can you be sure then?
Enabling the VoWiFi option doesnt mean its working !

der_Kief said:
How can you be sure then?
Enabling the VoWiFi option doesnt mean its working !
Click to expand...
Click to collapse
2 diff statement.
Can enable with code but doesn't work in india.
It worked for a friend in Greece without doing anything immediately after pie update.
What I was suggesting that maybe and just maybe if provider supports it ,vowifi can be enabled simply by code.

It is working perfect. I did some test calls on wifi. Thumb up..... BTW I'm on German Telekom D1

SatBandit said:
It is working perfect. I did some test calls on wifi. Thumb up..... BTW I'm on German Telekom D1
Click to expand...
Click to collapse
could you please tell us which ROM you are using and which profile you activated within PDC ?

I'm using 8.11.27 global beta and I modified the DT_greece section. Set sub0 and sub1 to active.
Opened dialer and dialed *#*#vowifi#*#*

ok this works, just needed a bit more work for WoWiFi in my case
after a reboot it kept returning to my default carrier config (VoLTE working just fine anyway)
so what I did was to remove my carrier config from within PDC Tool, just that by doing that it defaulted to a non-VoLTE config
well, removed that also and this time it kept DT_Greece config on both subs
VoLTE works and VoWiFi also (carrier Orange Romania)
ps. don't restart phone if you want to test new configs
just click on activate and enter airplane mode then exit (keeps testing faster)

I've gotten as far as I can with my Mi Mix 2S, works on both AOSP and MIUI to allow the radios to be enabled, and the settings to appear in MIUI (AOSP usually shows them anyway).
With this said, I tried only enabling the WiFi option on the carrier that already had the sim activated...
I see many people here on different carriers in the EU who enabled the DT_Greece options and voila. Is this an accurate conclusion? I'm wondering if I just need an answer from a carrier other than my own to acknowledge the WiFi option exists to turn it on? Being in the US it seems as if the DT_Greece config could cause some problems, but it's not an option in my list. I don't know at this point.
Edit:
Tried all the US bands and even a few others, specifically ones that said WiFi. None worked so far, I'm going to cry! :crying::crying::crying:

I tried this on a Redmi Note 5 Pro but after selecting the device in PDC it throws an error message and doesn't show the list of carriers.
I've tried QPST 2.7.420 and 2.7.474 and a couple different pie roms, windows 7 and 10 but it always fails.
I can use EFS Explorer and dump the NV data just fine though...

TMO 10.5.17.IN55CB installation problem? rooted

is there any way to install this update? every time i try i get an error message that only says "Installation Problem".

eisawi99 said:
is there any way to install this update? every time i try i get an error message that only says "Installation Problem".
Click to expand...
Click to collapse
You can't install updates while rooted. You would need to use MSM tool to go back to stock and then upgrade, afterwards you can root again. T mobile disables the local update option in system update and also only sends out the ota package and not the full system firmware. Just make sure you backup your persist partition before using MSM (recommend using the readback feature F8 of the MSM tool to back it up and then restore persist using fastbootd if it breaks fingerprint).

jeffsga88 said:
You can't install updates while rooted. You would need to use MSM tool to go back to stock and then upgrade, afterwards you can root again. T mobile disables the local update option in system update and also only sends out the ota package and not the full system firmware. Just make sure you backup your persist partition before using MSM (recommend using the readback feature F8 of the MSM tool to back it up and then restore persist using fastbootd if it breaks fingerprint).
Click to expand...
Click to collapse
Is there a guide for doing this using the MSM tool? I'm sure I could figure it out eventually but I'd probably also break something in the process lol.

eisawi99 said:
Is there a guide for doing this using the MSM tool? I'm sure I could figure it out eventually but I'd probably also break something in the process lol.
Click to expand...
Click to collapse
Here's the link to MSM tool:
https://forum.xda-developers.com/oneplus-8/how-to/op8-unbrick-tool-to-restore-device-to-t4093043
It has a guide in the OP of how to use it. Again, I highly recommend backing up your persist partition using the tool first. Just open tool, press F8, select persist, password is oneplus, connect phone in edl mode, click readback. It will copy your persist to root of your hard drive. Disconnect phone, close and reopen MSM, reconnect phone in edl mode and run MSM tool. Completely restores phone. Update to newest 10.5.17, then if you lost fingerprint, unlock bootloader, then from fastboot type:
Code:
fastboot reboot fastboot
Brings you to a screen with Chinese and English on it, type the following:
Code:
fastboot flash persist persist.img
Replace persist.img with location of your backed up persist. Then you can boot or install TWRP and flash magisk for root.
I had rooted my op8 and wanted the update so did exactly the above, used MSM, lost fingerprint so flashed my backed up persist and everything works great.

jeffsga88 said:
Here's the link to MSM tool:
https://forum.xda-developers.com/oneplus-8/how-to/op8-unbrick-tool-to-restore-device-to-t4093043
It has a guide in the OP of how to use it. Again, I highly recommend backing up your persist partition using the tool first. Just open tool, press F8, select persist, password is oneplus, connect phone in edl mode, click readback. It will copy your persist to root of your hard drive. Disconnect phone, close and reopen MSM, reconnect phone in edl mode and run MSM tool. Completely restores phone. Update to newest 10.5.17, then if you lost fingerprint, unlock bootloader, then from fastboot type:
Code:
fastboot reboot fastboot
Brings you to a screen with Chinese and English on it, type the following:
Code:
fastboot flash persist persist.img
Replace persist.img with location of your backed up persist. Then you can boot or install TWRP and flash magisk for root.
I had rooted my op8 and wanted the update so did exactly the above, used MSM, lost fingerprint so flashed my backed up persist and everything works great.
Click to expand...
Click to collapse
By completely restores phone, you mean I'll lose all my data? If so it's fine but is there an easy way to back up and restore the data?

eisawi99 said:
By completely restores phone, you mean I'll lose all my data? If so it's fine but is there an easy way to back up and restore the data?
Click to expand...
Click to collapse
Sorry, meant to put that on that reply before. It completely erases your phone. They have the OnePlus switch app, not sure how it is as I've never used it. I use Swift backup from the play store, but it's not completely free (i.e. batch backup and restore isn't free), also know others use titanium backup as well.

Got my update so far pretty unimpressed. Maybe I don't know what I'm doing should it show NR or 5G? Cell mapper will show NR at times, but my phone says 5G. Coverage might have improved some, but not much Decent download speeds, but upload is horrible almost always, sometimes it just errors out,

Christobal34 said:
Got my update so far pretty unimpressed. Maybe I don't know what I'm doing should it show NR or 5G? Cell mapper will show NR at times, but my phone says 5G. Coverage might have improved some, but not much Decent download speeds, but upload is horrible almost always, sometimes it just errors out,
Click to expand...
Click to collapse
Overall, it will not put you on SA (NR only) mode by default. The network will still keep you on NSA (LTE + NR) at most times. Generally, your speeds on NSA will be faster than on SA. The benefit of SA is that you don't need to have good LTE signal to connect to 5G. The issue, current 5G phones can't do calls over NR (VoNR) which means if you force SA mode, you won't be able to make our receive calls. Next year's phones will have VoNR, so SA will matter more then. By the way, cell mapper won't show you much information, the only useful thing to look for on cell mapper regarding 5g right now is the:
Code:
5G State: Connected
If it says that, you're Connected to 5g. If you're Connected to 5g and it gives you no LTE cell information, you should be on SA. There's only 1 app that correctly shows everything for 5g and it's Network Signal Guru, but it requires root and to see 5g info requires the beta version and a license. By the way, phone will show 5g. Another way to tell if on SA, pull down the quick settings and it will say TMO instead of T-Mobile and you can go to the phone dialer and type the following:
Code:
*#*#4636#*#*
Click on phone information and see what it says for data network and voice network, it will say NR if on SA or say LTE if on NSA. You can also force it to NR only with that menu, but again you won't be able to make or receive calls if you do that.

jeffsga88 said:
Overall, it will not put you on SA (NR only) mode by default. The network will still keep you on NSA (LTE + NR) at most times. Generally, your speeds on NSA will be faster than on SA. The benefit of SA is that you don't need to have good LTE signal to connect to 5G. The issue, current 5G phones can't do calls over NR (VoNR) which means if you force SA mode, you won't be able to make our receive calls. Next year's phones will have VoNR, so SA will matter more then. By the way, cell mapper won't show you much information, the only useful thing to look for on cell mapper regarding 5g right now is the:
Code:
5G State: Connected
If it says that, you're Connected to 5g. If you're Connected to 5g and it gives you no LTE cell information, you should be on SA. There's only 1 app that correctly shows everything for 5g and it's Network Signal Guru, but it requires root and to see 5g info requires the beta version and a license. By the way, phone will show 5g. Another way to tell if on SA, pull down the quick settings and it will say TMO instead of T-Mobile and you can go to the phone dialer and type the following:
Code:
*#*#4636#*#*
Click on phone information and see what it says for data network and voice network, it will say NR if on SA or say LTE if on NSA. You can also force it to NR only with that menu, but again you won't be able to make or receive calls if you do that.
Click to expand...
Click to collapse
Thanks for the info. I did force it to NR to test. I personally don't care about speed, but was hoping for better coverage. So do you need the x60 modem to use VoNR?

Christobal34 said:
Thanks for the info. I did force it to NR to test. I personally don't care about speed, but was hoping for better coverage. So do you need the x60 modem to use VoNR?
Click to expand...
Click to collapse
Yeah unfortunately still need to wait for x60 for VoNR (at least that's my understanding is that x50 and x55 don't support VoNR). I wouldn't be surprised if OnePlus patched the modem in the future so even if you force NR that it still detects when you place a call or get a call to drop to LTE for phone call. Samsung appears to have done this with the s20s.

Lenovo Legion 2 Pro no Mobile Data and not detected in fastboot.

Live in canada phone supports frequencies but only carrier where correct apn settings get loaded os freedom. I have telus and rogers and bell also do not work.. Im with telus and for telus it loads hotspot settings so basically i can hotspot my data to a different phone but not use it on the phone itself. I have tried to flash a new rom on it on both linux and windows but the phone is not detected by the abd shell when the phone is in fastboot mode. My old phone however is. I dont know what else to try in terms of getting the right apn settings as they dont seem to save even when i try apps or abd shell to do so.