Hi,
I have my 5T rooted with Magisk and TWRP recovery.
I've upgrated from OOS 9 to official OOS 10.0.1 flashing with TWRP as usual. I did a full nandroid backup before.
Everything went fine until I noticed that during the booting of the phone after the flashing, it didn't ask for the SIM code as it used to. And once the mobile had fully restarted, I could see 2 new icons on top of the screen picturing the 2 sim cards that can be contained in a OnePLus 5T. They were striken through, as if not present, when I had My SIM in Slot 1. And so, no mobile signal, no data network.
I tried switching Sim cards with another mpbile. My SIM worked fine in the other mobile and the other SIM was not recognized by my mobile.
I've read that I could be facing problems of damaged EFS. So I tried restoring through TWRP the EFS partition from the Nandroid I had done before. Nothing. Same thing with the modem partition. Nothing.
I tried then to restore the EFS from a safety backup that I had using Fastboot. Nothing.
I could still try to restore the full nandroid backup done at the beginning, but I forgot to take out pin protection code before taking the Nandroid, and I've read somewhere that it could be an issue after restoring the system. I might not be able to restart the phone and be obliged to factory reset, witch I would really like to avoid. And anyway, if restoring with Fastboot did not work, I wonder if the full restore would change anything.
Anyway, anybody has a magic idea about might be happening? A little help please??
Same problem!
I'm having the same problem. I have my 5T rooted with Magisk and TWRP recovery.
I've upgrated from OOS 9 to official OOS 10.0.1 flashing with TWRP as usual. I did a full TWRP backup before, including my EFS partition.
I'm seeing this too:
>"once the mobile had fully restarted, I could see 2 new icons on top of the screen picturing the 2 sim cards that can be contained in a OnePLus 5T. >They were striken through, as if not present, when I had My SIM in Slot 1. And so, no mobile signal, no data network."
I did the same thing and had the same no result.
>I've read that I could be facing problems of damaged EFS. So I tried restoring through TWRP the EFS partition from the Nandroid I had done >before. Nothing. Same thing with the modem partition. Nothing.
I'm looking for a solution too.
I came across this: https://forum.xda-developers.com/oneplus-5t/help/baseband-imei-lost-t3834334 and this: https://www.getdroidtips.com/how-to-repair-and-fix-imei-baseband-on-oneplus-5t-a5010/
I've been reluctant to try and rebuild the QCN file, but it might work.
Working on this
So I'm working on reprogramming the IMEI using the Qualcomm tools. I was able to use them to back up my phone and see the it still has the correct MEID.
However, the .gcn file linked to below isn't accepted, with a weird error: "The file model MSM8998 does not match the phone model MSM8998. Please select a file for the MSM8998."
I'm not sure what it isn't liking. In theory, I think I could just put the IMEI numbers into the QPST programming tool, but I'm not certain where they would go and the correct format for them (with the chksm at the end or not?).
This is as far as I've gotten. I'm looking for an alternate .qcn or .qcnx (which is the kind the tool generates when saving files).
rootlessabroad said:
I'm having the same problem. I have my 5T rooted with Magisk and TWRP recovery.
I've upgrated from OOS 9 to official OOS 10.0.1 flashing with TWRP as usual. I did a full TWRP backup before, including my EFS partition.
I'm seeing this too:
>"once the mobile had fully restarted, I could see 2 new icons on top of the screen picturing the 2 sim cards that can be contained in a OnePLus 5T. >They were striken through, as if not present, when I had My SIM in Slot 1. And so, no mobile signal, no data network."
I did the same thing and had the same no result.
>I've read that I could be facing problems of damaged EFS. So I tried restoring through TWRP the EFS partition from the Nandroid I had done >before. Nothing. Same thing with the modem partition. Nothing.
I'm looking for a solution too.
I came across this: https://forum.xda-developers.com/oneplus-5t/help/baseband-imei-lost-t3834334 and this: https://www.getdroidtips.com/how-to-repair-and-fix-imei-baseband-on-oneplus-5t-a5010/
I've been reluctant to try and rebuild the QCN file, but it might work.
Click to expand...
Click to collapse
Hi
I've found a code (*#06#) in a page that gives you the MEID. It worked for me. Hopefully, I have the correct MEID too. The code for the IMEI did not show anything. I'll check the lynks you posted later today.
Thanks for sharing!!
PS. I can not include the lynk to codes page as I'm too junior a member and XDA forums won't let me.
rootlessabroad said:
So I'm working on reprogramming the IMEI using the Qualcomm tools. I was able to use them to back up my phone and see the it still has the correct MEID.
However, the .gcn file linked to below isn't accepted, with a weird error: "The file model MSM8998 does not match the phone model MSM8998. Please select a file for the MSM8998."
I'm not sure what it isn't liking. In theory, I think I could just put the IMEI numbers into the QPST programming tool, but I'm not certain where they would go and the correct format for them (with the chksm at the end or not?).
This is as far as I've gotten. I'm looking for an alternate .qcn or .qcnx (which is the kind the tool generates when saving files).
Click to expand...
Click to collapse
So I've tried te rebuild the QCN file. But my issue is that I can't make the ADB comunicate with my mobile. It is as the mobile was not plugged in?? The usb debugging is activated. I can browse the mobile memory from the computer. But the ADB doesn't lynk with the mobile; when you type adb devices, it says List of devices attached and nothing after. Any idea what might be happening?
What about you rootlessabroad? could you fix it?
rootlessabroad said:
So I'm working on reprogramming the IMEI using the Qualcomm tools. I was able to use them to back up my phone and see the it still has the correct MEID.
However, the .gcn file linked to below isn't accepted, with a weird error: "The file model MSM8998 does not match the phone model MSM8998. Please select a file for the MSM8998."
I'm not sure what it isn't liking. In theory, I think I could just put the IMEI numbers into the QPST programming tool, but I'm not certain where they would go and the correct format for them (with the chksm at the end or not?).
This is as far as I've gotten. I'm looking for an alternate .qcn or .qcnx (which is the kind the tool generates when saving files).
Click to expand...
Click to collapse
Related
Hello, this is really weird. In fact, when I insert the SIM to my Note 2 N7100 and turn it on, it allows me to make emergency call, but I cannot use it to make any others and it doesn't show the carrier name (it shows Emergency call only). And when I try to use it to make normal phone calls, it says that I am not registered to a mobile network. I try to factory reset my phone, but the problem remains. I then try to remove the SIM card, and it says that I need to insert a SIM card (that means that it is not a hardware problem since it recognizes the card). I then try to go to the mobile network setting to try to connect to the network manually, it connects me but it shows me a warning which says that the mobile network service is not available (and the Emergency call only label remains). However, I am sure that this is not the problem of the card neither since when I insert the card to my Moto MB860, I can make calls as usual. So, what is the problem ??? It seems to me that the problem happens spontaneously since it works perfectly until yesterday. And all other wireless function works fine including wifi , Bluetooth and GPS and the only thing goes wrong is 3g and 2g.
Additional information:
ROM: Omega v.16
Carrier: Fido Canada (as you can see)
Thanks.
First of all, check whether you can see the IMEI of the device. If you can see.
1. Contact your network operator and check whether your IMEI is blacklisted or not.
If you cannot see the IMEI
1.Restore the efs and persist backups (if you have one)
2. flash the device again with the modem image (download the firmware of your device from samfirmwares.com, delete everything from the .tar file except modem.bin, and then flash this file to the phone with Odin (you can get Odin and instructions from that site or from here)
2. maybe your nv_data.bin file or /efs directory got corrupted, make a backup of the folder, then simply delete nv_data.bin, it will be recreated for you.
For this, you’ll need root. If you have a root-enabled kernel, you only have to install the Superuser app and Busybox on the phone, download the Android SDK to your PC, install platform-tools in the SDK manager, go to the platform-tools directory and start adb shell.
In the shell, type su, wait for the Superuser prompt to appear on the phone (if it does not appear, open the Superuser app and try executing su again), enable root access for the command. Now go to /efs, copy everything to for example /sdcard/efs, then rm nv_data.bin.
Reflashing the device with a kernel and checking “phone EFS clear” in Odin also works (make sure you made a backup of the EFS folder just in case).
3. you can try changing the CSC: enter *#272*imei# on the phone tab.
Try this . I'm not sure it works. Just give it a try on yourself.
Trying the above mentioned methods could be vulnerable to your phone if it not done properly. So do it carefully. If you have any doubts feel free to ask me or search elsewhere. But, don't blame me for a fully dead phone. I am not at all responsible for any...
Noob 1st post......have had similar problems with koodo CDN
Not gonna give such an in depth suggestion as above.....he's something simple to try.
I live in a dead zone and often my phone ( galaxyAce) will switch to no service. Even after refreshing and selecting network under settings, it says it's connected, but isn't. A simple apk that always fixes the problem for me is Network Signal Booster @ theplaystore
jabrif said:
First of all, check whether you can see the IMEI of the device. If you can see.
1. Contact your network operator and check whether your IMEI is blacklisted or not.
If you cannot see the IMEI
1.Restore the efs and persist backups (if you have one)
2. flash the device again with the modem image (download the firmware of your device from samfirmwares.com, delete everything from the .tar file except modem.bin, and then flash this file to the phone with Odin (you can get Odin and instructions from that site or from here)
2. maybe your nv_data.bin file or /efs directory got corrupted, make a backup of the folder, then simply delete nv_data.bin, it will be recreated for you.
For this, you’ll need root. If you have a root-enabled kernel, you only have to install the Superuser app and Busybox on the phone, download the Android SDK to your PC, install platform-tools in the SDK manager, go to the platform-tools directory and start adb shell.
In the shell, type su, wait for the Superuser prompt to appear on the phone (if it does not appear, open the Superuser app and try executing su again), enable root access for the command. Now go to /efs, copy everything to for example /sdcard/efs, then rm nv_data.bin.
Reflashing the device with a kernel and checking “phone EFS clear” in Odin also works (make sure you made a backup of the EFS folder just in case).
3. you can try changing the CSC: enter *#272*imei# on the phone tab.
Try this . I'm not sure it works. Just give it a try on yourself.
Trying the above mentioned methods could be vulnerable to your phone if it not done properly. So do it carefully. If you have any doubts feel free to ask me or search elsewhere. But, don't blame me for a fully dead phone. I am not at all responsible for any...
Click to expand...
Click to collapse
I tried a simple way which is format everything and flash another ROM but the problem remains.
TRS_80 said:
Noob 1st post......have had similar problems with koodo CDN
Not gonna give such an in depth suggestion as above.....he's something simple to try.
I live in a dead zone and often my phone ( galaxyAce) will switch to no service. Even after refreshing and selecting network under settings, it says it's connected, but isn't. A simple apk that always fixes the problem for me is Network Signal Booster @ theplaystore
Click to expand...
Click to collapse
I don't know that we are in the same situation since at home I often got a good signal and this happened to me only since yesterday.
jabrif said:
First of all, check whether you can see the IMEI of the device. If you can see.
1. Contact your network operator and check whether your IMEI is blacklisted or not.
If you cannot see the IMEI
1.Restore the efs and persist backups (if you have one)
2. flash the device again with the modem image (download the firmware of your device from samfirmwares.com, delete everything from the .tar file except modem.bin, and then flash this file to the phone with Odin (you can get Odin and instructions from that site or from here)
2. maybe your nv_data.bin file or /efs directory got corrupted, make a backup of the folder, then simply delete nv_data.bin, it will be recreated for you.
For this, you’ll need root. If you have a root-enabled kernel, you only have to install the Superuser app and Busybox on the phone, download the Android SDK to your PC, install platform-tools in the SDK manager, go to the platform-tools directory and start adb shell.
In the shell, type su, wait for the Superuser prompt to appear on the phone (if it does not appear, open the Superuser app and try executing su again), enable root access for the command. Now go to /efs, copy everything to for example /sdcard/efs, then rm nv_data.bin.
Reflashing the device with a kernel and checking “phone EFS clear” in Odin also works (make sure you made a backup of the EFS folder just in case).
3. you can try changing the CSC: enter *#272*imei# on the phone tab.
Try this . I'm not sure it works. Just give it a try on yourself.
Trying the above mentioned methods could be vulnerable to your phone if it not done properly. So do it carefully. If you have any doubts feel free to ask me or search elsewhere. But, don't blame me for a fully dead phone. I am not at all responsible for any...
Click to expand...
Click to collapse
Some updates;
- IMEI is checked.
- I do not have any efs backup
- nv_data.bin has been deleted and recreated
- trying to register for the firmware
- My phone is always rooted.
Dan Law 001 said:
Some updates;
- IMEI is checked.
- I do not have any efs backup
- nv_data.bin has been deleted and recreated
- trying to register for the firmware
- My phone is always rooted.
Click to expand...
Click to collapse
Results..??
Sent from my GT-I9001 using xda premium
jabrif said:
Results..??
Sent from my GT-I9001 using xda premium
Click to expand...
Click to collapse
I need to get the firmware first... since I already passed the download quota for today... need to wait until tomorrow...
Mmm... I heard that you mentioned clearing the EFS in your given procedure, but I do not think that I modified that folder... However, about few days ago, since I want to gain better control on the volume on my headphone remotes, I did modify the file called Generic.kl in system/usr/keylayout, but I restore it after since it didn't work. However, I don't think that this modification will trigger something in the efs folder since it has different directory. By the way, I did some research online and they say that the efs contains information about the carrier on the phone, so will there's a greater chance that the problem is caused by the possible modification on the efs than any other factor and will there also something else that possibly trigger the similar effects?
Sent from my GT-N7100 using xda premium
Still nothing
How does one change the IMEI?
I've tried this without success:
1. Root your device
2. Download and install QSPT and UltraEdit (HxD would also do).
3. Download an IMEI converter.
4. Get hold of a working qcn (I used my own which I know works in my other P2). Open the file by using Ultraedit/HxD and try to locate the IMEI. In my case it often starts with "08 8A...".
5. Use the IMEI converter and input your true IMEI. Memorize the output.
6. Return to the qcn file. Write it over with the IMEI output you got in step 5.
7. Save the file.
8. In a terminal enter:
su
setprop sys.usb.config rndis,diag,adb
9. Restore the qcn file from step 7 by using QSPT. You click on QPST configuration and go to "ports". If your port isn't already visible go to the device manager, look up the Qualcomm Diag port and add it. For me I believe it's COM9. Now you click on "start clients", then "software download". Tick the "Allow phone/file ESN mismatch", locate your saved qcn file and start restoring it.
10. All done. Reboot!
Apparently some XDA members managed to get their signal back once the modem was deleted so I guess somebody should know.
Other methods I've tried include flashing stock MM and installing OTA until you're on S251 as well as restoring an older full TWRP backup from when your signal used to work. Needless to say, they didn't work.
This procedure worked for me. Lenovo K6 Power with Qualcomm proc.
Successfully I found other users qcn file and wrote my IMEI in it.
Signal is back but diag port disappeared and I can't turn it on again.
WhatsApp me or call me 8436243173
WHERE CAN I GET THIS QNCN ? I'm confused
I had same problem, here are my steps with qcn backup file from working P2. My IMEIs stays right. Sorry for my english and here is my link and read next threads from that forum.
https://forum.xda-developers.com/showpost.php?p=73444145&postcount=70
mL-7 said:
This procedure worked for me. Lenovo K6 Power with Qualcomm proc.
Successfully I found other users qcn file and wrote my IMEI in it.
Signal is back but diag port disappeared and I can't turn it on again.
Click to expand...
Click to collapse
Have K6 power with IMEI turned 0 after fastboot erase modemst1 and 2. Could you please detail the steps to restore IMEI?
Please read Bootloader Unlock and Root Instruction to understand how to work with Qfil.exe
1. Download Ftm - partition from phone. You can do it via Qfil.exe or Root
adb shell
su
dd if=/dev/block/bootdevice/by-name/ftm of=/sdcard/ftm.bin
2. You need to know your Serial Number so go imei24.com or imeipro.info and type yours IMEI.
3. Now open Ftm.bin with Hex.exe ( attached )
Then go Navigation -> Go to Offset... and type 73728
Type SN and save changes.
4. Flash it back in phone with Qfil.exe or copy ftm.bin to internal sdcard
adb shell
su
dd if=/sdcard/ftm.bin of=/dev/block/bootdevice/by-name/ftm
reboot
Done!
And if what I lost was my imei, can I recover it with this method?
IMEI recorded here twice: Offset 53248 and 14680132.
For restoring IMEI you need your backup efs
Thanks a lot for your instructions.
I've successfully restored my S/N on the V35AWM.
I updated my V35AWM to V35ULM last November, then I flashed the wrong firmware version in April 2020 when the newest firmware was released. After I resume the device, I found my S/N was lost but had no idea about how to get it restored.
But there was still a most difficult part in this instruction which is how to enter the 9008 mod, this cost me about 2 hours.
So everything is ready now only awaiting for the new Android 10 to release.
do you have video tutorials
do you have video tutorials?
SaiLas said:
Please read Bootloader Unlock and Root Instruction to understand how to work with Qfil.exe
1. Download Ftm - partition from phone. You can do it via Qfil.exe or Root
adb shell
su
dd if=/dev/block/bootdevice/by-name/ftm of=/sdcard/ftm.bin
2. You need to know your Serial Number so go imei24.com or imeipro.info and type yours IMEI.
3. Now open Ftm.bin with Hex.exe ( attached )
Then go Navigation -> Go to Offset... and type 73728
Type SN and save changes.
4. Flash it back in phone with Qfil.exe or copy ftm.bin to internal sdcard
adb shell
su
dd if=/sdcard/ftm.bin of=/dev/block/bootdevice/by-name/ftm
reboot
Done!
Click to expand...
Click to collapse
SaiLas said:
IMEI recorded here twice: Offset 53248 and 14680132.
For restoring IMEI you need your backup efs
Click to expand...
Click to collapse
Hy chazmatt. Is that possible to restore or change imei if forget to backup.
muzammil457 said:
Hy chazmatt. Is that possible to restore or change imei if forget to backup.
Click to expand...
Click to collapse
No, imei is gone. Now your phone is a tablet.
Kyrimeas said:
No, imei is gone. Now your phone is a tablet.
Click to expand...
Click to collapse
But in v30 there is a way to put imei no through service code *#546368#*933#. We can update imei no thorugh this. In v35 is there any option like this
muzammil457 said:
But in v30 there is a way to put imei no through service code *#546368#*933#. We can update imei no thorugh this. In v35 is there any option like this
Click to expand...
Click to collapse
There is. *#546368#*350#. But once you erased imei, this option gets blocked. Always imei will be 0.
Does missing serial number has anything to do with not being able to make phone calls?
I have a V35 unlocked version (pretty sure this is V350ULM), I flashed it with Korean Q and it worked fine while traveling in Korea. After coming back to U.S. I tried ATT based Tracfone SIM and data works fine but when I try to make calls it always immediately shows Call Ended. I notice the serial number is blank.
hp79 said:
Does missing serial number has anything to do with not being able to make phone calls?
I have a V35 unlocked version (pretty sure this is V350ULM), I flashed it with Korean Q and it worked fine while traveling in Korea. After coming back to U.S. I tried ATT based Tracfone SIM and data works fine but when I try to make calls it always immediately shows Call Ended. I notice the serial number is blank.
Click to expand...
Click to collapse
hp79 said:
Does missing serial number has anything to do with not being able to make phone calls?
I have a V35 unlocked version (pretty sure this is V350ULM), I flashed it with Korean Q and it worked fine while traveling in Korea. After coming back to U.S. I tried ATT based Tracfone SIM and data works fine but when I try to make calls it always immediately shows Call Ended. I notice the serial number is blank.
Click to expand...
Click to collapse
I've got a ULM with the A10 Korean rom. I have no issues making or receiving calls without a SN.
cmrntnnr said:
I've got a ULM with the A10 Korean rom. I have no issues making or receiving calls without a SN.
Click to expand...
Click to collapse
Is it possible for you to share some of your system partitions to get mine to work again? I'm not sure which partitions would be needed to get it back to working condition. I can get it to QFIL mode and flash some. I think this may have happened after some more flashing but not sure. My IMEI is still intact, serial number is blank.
It sounds like you are successfully rooted and on a Korean A10 rom. If you are unsure, follow clouds localize guide then flash the partition image in this post:
[Guide] Make the Korean Q Great Again [relocalise, volte, wowifi, debloat and more]
I've completed all the steps (except for lg weather) and I didn't notice anything different in call features until I saw the description of the international roaming setting referenced "outside of US PR etc." instead of "outside of foreign...
forum.xda-developers.com
It sounds like you are successfully rooted and on a Korean A10 rom. If you are unsure, follow clouds localize guide then flash the partition image in this post:
[Guide] Make the Korean Q Great Again [relocalise, volte, wowifi, debloat and more]
I've completed all the steps (except for lg weather) and I didn't notice anything different in call features until I saw the description of the international roaming setting referenced "outside of US PR etc." instead of "outside of foreign...
forum.xda-developers.com
Hi,
I recently tried to flash qcn on my OnePlus 7T and it seems that I lost efs data (some sensors aren't working now).
To extract qcn or xqcn file you need to enable usb diagnostic port (in phone app dial *#801# and click the second and fourth buttons).
Doing so will make your phone detectable in Qualcomm softwares.
To extract qcn, use QFIL and click Tools>QCN Backup/Restore. In the field "QCN file path" write the path to the directory you want to save the backup, and also write the name of the file that will be created. Then click Backup QCN.
To extract xqcn, use QPST Software Download, and go to the Backup tab. Click Browse to select the destination for the xqcn backup, and set a name to the backup that will be created. Then click start.
Doing this process is quick and should take approximately 5 minutes if you already have the QPST software.
In case you need it, I have the installer from Qualcomm for QPST 2.7.480 :
http://www.mediafire.com/file/nm0zlac003tn41j/qualcomm_qpst_setup_2.7.480.zip/file
Also you have to know that your IMEI will be visible in these backups, and you should remove them using an hex editor to replace it with some random numbers or zeros before sharing it with me or anyone.
If you need informations on how to find your IMEI in your qcn or xqcn backup using an hex editor, I will explain it in this thread too.
Thank you
Are you saying with these same methods you lost efs data or you did a mistake while flashing ?
Thanks @egekonuk for your reply.
In fact I was trying to flash international rom version on my TMobile Oneplus 7T by editing MSM download tool (using x64dbg which is a software sharing many functionalities with IDA Pro).
I did not managed to flash international but yes, I lost efs in the process.
Superboy58 said:
Thanks @egekonuk for your reply.
In fact I was trying to flash international rom version on my TMobile Oneplus 7T by editing MSM download tool (using x64dbg which is a software sharing many functionalities with IDA Pro).
I did not managed to flash international but yes, I lost efs in the process.
Click to expand...
Click to collapse
Just curious why you didn't do the other posted method to go from TMO to international? I did the other method and it worked out just fine. Of course I don't know if that very friendly person is still doing unlocks or not.
Is there a difference between the QCN and XQCN between ROMs?
@amcferrin90 yes I didn't mentioned that but it's because my device was not SIM unlocked by T-Mobile. I bought it on ebay and I was not aware it was not paid off, and seller refused a return.
If I was SIM unlocked, I'd be able to unlock the bootloader and flash the international rom using fastboot.
I did not understand what you meant about qcn, xqcn and roms.
To me, qcn and xqcn are different because xqcn backups are larger than qcn ones.
I think xqcn contains some efs data, but I'm not sure about this.
Would you be ok to make a xqcn backup and share it with me?
Thanks
I also need a backup of QCN.(please)
I need experts review and help to resolve my issue last night i am update my phone s20 ultra G988B/ds to its original software everything working fine except network i was using root phone it was fine on all networks but after updating my imei status goes to NG(not good) sim accepted phone but shows emergency calls both imei shoes but network not working plz give me suggestions and issue solution. I am again root my phone but still not working networks plz help
S20 ultra imei status NG
Why you experts not solving my issue no comments at all?
Bro i've posted same kind of post just now i hope someone replies soon otherwise i'll try z3x software or chimera and let you know about the results, i think if your imei is not corrupted then cert file will do the wonder.
well hey everyone same issue i have s20 plus phone was rooted and i flash the firmware and now imei is NG i trid the chimera tool but no luck if u find any fix please help me.
did you guys resolve it ?
i may have an idea
Any fix
do you guys even search before asking?
First, do a TWRP backup, all partitions including efs & modem.
Open the root explorer app, open the efs folder, delete the files named nv_data.bin
, nv_data.bin.md5 & the folder called imei. Then open twrp, wipe all partitions. Flash the latest firmware with Odin.
That solution work???
juda iskariotsky said:
do you guys even search before asking?
First, do a TWRP backup, all partitions including efs & modem.
Open the root explorer app, open the efs folder, delete the files named nv_data.bin
, nv_data.bin.md5 & the folder called imei. Then open twrp, wipe all partitions. Flash the latest firmware with Odin
Click to expand...
Click to collapse