Related
Maybe its just dumb luck, but I doubt it. I've had a whole crapload of HTCs come into the shop lately that need their MEIDs repaired due to clueless people attempting nefarious things. And well, there is a wealth of info here and elsewhere on how people go about doing these repairs; More often than not, it involves scanning memory locations - etc. From my experience, just using the "open sesame door" trick works just fine, and bypasses all this memory scanning\zero'ing\etc. The question I pose is this: does this only work with a unlocked bootloader\s-off? For those that have no clue what I am talking about, and you have a zero'ed meid Evo phone you'd like to repair, do this:
Install the proper diag drivers of course
In QPST, add the diag port, then run EFS Explorer
Check and see if your NV items folder is locked
If it is, create a directory named "open sesame door" right off of the EFS root
Reboot phone, then go back to the EFS Explorer. Your NV NUM dir containing all the NV item files should now be unlocked. Now you can
just edit the 0 (pesn file..), 1 (pesn checksum file..) and 1943 (meid file..) files directly instead of scanning for mem locations. I've done countless repairs like this, but always seem to forget to check if its possible prior to unlocking. Just a thought\rant, input is very welcomed.
The phone doesn't even have to be rooted.
It can be completely stock.
Hey I was trying to get my esn fixed but in qpst it does not save. I copied the 0 and 1946 then hex edit copy back. After rebooting they are the same. Any help you could offer me would be great.
payohtea said:
Maybe its just dumb luck, but I doubt it. I've had a whole crapload of HTCs come into the shop lately that need their MEIDs repaired due to clueless people attempting nefarious things. And well, there is a wealth of info here and elsewhere on how people go about doing these repairs; More often than not, it involves scanning memory locations - etc. From my experience, just using the "open sesame door" trick works just fine, and bypasses all this memory scanning\zero'ing\etc. The question I pose is this: does this only work with a unlocked bootloader\s-off? For those that have no clue what I am talking about, and you have a zero'ed meid Evo phone you'd like to repair, do this:
Install the proper diag drivers of course
In QPST, add the diag port, then run EFS Explorer
Check and see if your NV items folder is locked
If it is, create a directory named "open sesame door" right off of the EFS root
Reboot phone, then go back to the EFS Explorer. Your NV NUM dir containing all the NV item files should now be unlocked. Now you can
just edit the 0 (pesn file..), 1 (pesn checksum file..) and 1943 (meid file..) files directly instead of scanning for mem locations. I've done countless repairs like this, but always seem to forget to check if its possible prior to unlocking. Just a thought\rant, input is very welcomed.
Click to expand...
Click to collapse
blah blah
I had done this successfully in the past on my Evo 3d.
Now when I try to overwrite the 0 and 1943 nvitems, I keep getting "Runtime Error" and EFSExplorer.exe quits.
I had lost my Flash after trying to gain S-off.
in EFSexplorer, the nvnum folder is not readonly, after doing open sesame door.
But does anybody know or have seen the Runtime Error, and how you fixed it.
I downgraded my hboot to 1.4, and still s-off, downgraded to Gingerbread stock, still no go
==
edit:
nevermind, problem solved
baalho said:
I had done this successfully in the past on my Evo 3d.
Now when I try to overwrite the 0 and 1943 nvitems, I keep getting "Runtime Error" and EFSExplorer.exe quits.
I had lost my Flash after trying to gain S-off.
in EFSexplorer, the nvnum folder is not readonly, after doing open sesame door.
But does anybody know or have seen the Runtime Error, and how you fixed it.
I downgraded my hboot to 1.4, and still s-off, downgraded to Gingerbread stock, still no go
==
edit:
nevermind, problem solved
Click to expand...
Click to collapse
i did not have a runtime error. my issue was that the changes never stuck. i would change 0 and 1943 write them back to the phone then after a reboot i checked them and they were back to original.
jlmancuso said:
i did not have a runtime error. my issue was that the changes never stuck. i would change 0 and 1943 write them back to the phone then after a reboot i checked them and they were back to original.
Click to expand...
Click to collapse
I had similar issues using Open Sesame. I could not successfully overwrite the existing 0 & 1943 files from NV folder after unlocking.
After several retries & reboots, I had success (luck?) using the following:
I rebooted my pc
First opened DFS demo version & sent SPC (MSL) and also HTC password 01F2030F5F678FF9 in password field
I then closed out of DFS & opened QPST / EFS Explorer
NVM was available. It finally worked when I just deleted 0 & 1943 files
THEN copied the 0 & 1943 files from my pc using File Menu
I did not experiment with drag & drop.
Both files stuck after reboot & 3G calls & text are working fine after OTA
Hope this helps someone else
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
Hello all and a good day.
Device: Samsung Galaxy Note 8.0 GT-N5100 (3G) - XME (Malaysia)
What I did: Nothing unusual! Device mainly used for text reading and some writing. After updated to Android 4.2.2 (PDA: N5100XXCMI1, CSC: N5100OLBCMH2, MODEM: N5100XXCMI1) via ODIN, the symptom # 1 appeared. The firmware for Malaysia was downloaded from the sammobile.com.
Same time I came to know the importance of /efs backup, so rooted (1st time) the device, backed-up /efs via EFS Pro, used Triangle Away, unroot, and flashed the stock. Since the symptom # 1 continued, I did a factory reset, and then all other symptoms appeared.
Symptoms:
1) Tablet doesn’t vibrate.
2) Kies is unable to detect the tablet.
3) SIM Cards are not detected. A prohibition sign is shown at the cell signal (left to the battery indicator) (see image 1).
4) In “Settings > About device”, and in “Settings > About device > Status”, many fields are stated as “Unknown”, e.g.:
Baseband and IMEI (see image 1 and image 2). Incorrect Serial number (/efs has the correct one as in the back cover).
5) Camera view is upside down.
6) Proximity sensor doesn’t work. In the *#0*# Test mode, Proximity value is 1.0. If exit and check again value becomes 0.0.
7) Regardless of Flight mode or not Cell standby drains the battery a lot. Once activated, Flight mode turns grey (see image 3).
8) [SOLVED, see 5th post] Several times (not always), a white screen appeared at the boot screen (model name), and also when plugged to power source while the tablet switched off. I guess something to do with param partition.
9) [SOLVED, see 5th post] "No command" error message in the stock recovery (3e).
9) “Modem boot timeout” and “Couldn't find 'rild' socket” errors in logcat -b radio.
10) When tried to use the tablet as a modem from Windows 7, it gives an Error 692, and the diagnostics states, “Timed out waiting for response from modem”.
Solutions tried (no success): As many, I too tried various /efs based solutions mentioned in XDA, and flashed all the five firmwares available for the device, but the problem stays same. I tried to solve this without troubling others much, but now I am lost.
Help needed: Is this problem can be fixed by me with some guidance, which would be great since to claim warranty the tablet need to be send to another country. Or is it a hardware problem, therefore I should send it straight to Samsung service without wasting more time?
Attached files, if they help:
1) Outputs of the following commands
logcat -b radio
logcat *:E
dmesg
ls -la /efs
ls -la
mount
cbd -t xmm626x -o t
2)
- recovery log from - CivZ_rev1.1-PhilZ 5.1.1 (touch)
- build.prop file
Thank you for reading. Greatly appreciate any help and guidance. Sorry, if I violate any XDA rules in this post. Kind regards!
New Problem: "There is no PIT partition."
Last night managed to fix a part of the problem (customer.xml error in logcat) in the above post thanks to the guidance from civato. In an attempt to fix other problems, last night I had mistakenly executed the following cmd in ADB while in recovery.
Code:
dd if=/data/media/0/efs.img of=/dev/block/[B]mmcblk0[/B]
The correct one should have used is mmcblk0p3 (/efs partition in Note 8.0). At least I managed to do some damage, otherwise all the credit goes to Samsung.
Now I can go to download mode only. A white screen flashes if try recovery mode or normal boot or even connect to a power source to recharge. Since charging or not also unsure (before this happened battery was 100%), I have a limited time to use the device to get it to work properly. Other problem is, if fail, can’t claim warranty as there’s no way to use the Triangle Away in this situation.
Now when try to flash via ODIN:
1) normal way - it failed stating, "There is no PIT partition." (see image 1).
2) with kona3g.pit I have - it failed stating, "Re-partition operation failed." (see image 2).
Even when the device was working properly, 2nd option never worked for me.
My kona3g.pit read well by PIT Magic 1.3.10.
Can anyone provide me a working .pit for Note 8 GT-N5100. Thinking of trying Heimdall Suite 1.4.0 tonight, but need some reading as I never used it and limited battery time for flashing.
Any advice to recover my device is highly welcome.
King regards.
Here you go, unzip it and in Odin select repartition and then Odin a new stock rom. (PDA)
Or look here for the 5110 pit file it should alos work on the 5100 as the modem partition is also created.
reinstall your csc also after rom onstallation
PS try the included Odin
Working kona3g.pit for GT-N5100
civato said:
Here you go, unzip it and in Odin select repartition and then Odin a new stock rom. (PDA)
Or look here for the 5110 pit file it should alos work on the 5100 as the modem partition is also created.
reinstall your csc also after rom onstallation
PS try the included Odin
Click to expand...
Click to collapse
Brilliant and thank you! The Odin3_v3.07.exe you provided missing an Odin3.ini (see image). I used an Odin3.ini (see attached files) that I have (for the same version) together with your Odin3_v3.07.exe and kona3g.pit, and the flashing went perfectly without any errors. So your kona3g.pit is a genuine working one. Thank you
I’ll continue further tonight and post here. My friend share his laptop with me, therefore I have limited time.
EDIT: When looked from the PIT Magic 1.3.10, the GT-N5110.pit is same as the GT-N5100 one (kona3g.pit). But when looked from the HxD - Hexeditor 1.7.7.0, the signatures at the end of the files are different, so it might not work on the sister device. Also, your GT-N5110.pit has trailing zeros after the signature, somewhere I read that these zeros must be deleted from a hexeditor for it to work.
Kind regards!
Image:
Solutions for symptoms 8 & 9
Solution for symptom 8:
Googled for a param.bin for Note 8.0, but only found one for Galaxy S3. Anyway, being fed up with the white screen, I copied S3 param.bin to the mmcblk0p4 partition of Note 8.0, surprise it worked. But the boot screen became S3 . Later among my backups, I found a param backup of mmcblk0p4 that I took via EFS Pro. Unfortunately couldn't restore it via EFS Pro as I had renamed the tar.gz to keep things tidy. So I extracted it to get a file called param. Since this param didn't work after copying, I compared it in the hex editor with the working S3 param, and noticed EFS Pro add some data to the beginning of the file. I removed this begining data and also the trailing zeros, and renamed it to param.bin (to go along with the name in kona3g.pit, perhaps not necessary). Finally, copied it by "dd if=/sdcard/param.bin of=/dev/block/mmcblk0p4" command, after couple of reboots white screen disappeared.
Solution for symptom 9:
Difficult to say this is a solution but it disappeared after this. In order to send for warranty claim, I restored the device to clean stock. First used Triangle Away to reset the counter. Booted and fully unroot via SuperSU. Then flashed the stock rom with the pit file, and without restart option. Shut down the device and boot into the recovery to do a full wipe, and the "No command" error wasn't there.
I must say, since my modem not working, capslock66's Android Reverse Tethering 3.15 saved my day to download the required Triangle Away add-on via laptop's broadband connection.
Since all other symptoms couldn't be solved my me after much effort, I sent the tablet for Samsung service.
hello everyone,
my device sm-n910a is currently working well with wifi connection, i'm using it in asia, so i need the IMEI to unlock the phone.
But unfortunately my IMEI went null, i don't know what caused it, but since the IMEI is still good, here's what happened :
1. I tried to unlock via *#9090#, i forgot what i've pressed, my phone immediately restarted itself, and it went in bootloop (switched on for about 1-3minutes and the phone restart itself again).
I've realized that the imei and baseband went null (*#06# shows "null")
2. Then i found an article in other forum to fix bootloop problem.
i followed the instructions there without realizing that it's supposed to be supported with a service box (octoplus)
The instructions are :
1. Downgrade to 4.4.4 via Odin. Extract OC4, extract Odin, open Odin, select four files into correct position (BL, AP, CP, CSC) 4.4.4 OC4 Odin 3.09 (Samsung Mobile drivers required)
2. Once on 4.4.4 or below, enable developer options by tapping "build version" several times, enable USB debugging & mock location, and install KingRoot 4.0.0.233 to phone. Caution, newer versions did not work for me.
3. Open "Command Prompt" and type "adb version" should reply with "Android Debug Bridge version x.x.x", if does not, change to the correct directory where adb is installed via "cd" command. Need ADB? Here
4. These next two steps can be a little tricky as the phone often reboots before completed, must work quickly, I suggest copying the long command, then paste when ready.
5. Connect to working WiFi. Turn off your phone, reboot, or wait for it to reboot itself. Soon as phone turns on, open KingRoot, soon as WiFi connected notification appears, touch button in center of KingRoot app, soon as KingRoot reaches 30%, began adb commands.
6. ADB commands: first command "adb shell", second command "su", third command "dd if=/dev/zero of=/dev/block/mmcblk0p10 | dd if=/dev/zero of=/dev/block/mmcblk0p13 | dd if=/dev/zero of=/dev/block/mmcblk0p14 | dd if=/dev/zero of=/dev/block/mmcblk0p15 | dd if=/dev/zero of=/dev/block/mmcblk0p16" phone will reboot or you can reboot and after reboot boot-loop and unknown baseband will be fixed! Can now write new IMEI via "Write Cert" and possibly "Write QCN" if any network troubles, then all good to go!
Click to expand...
Click to collapse
3. After finished all the instructions given, my phone's baseband got fixed, but the imei still unknown (*#06# shows "/01")
4. In the instructions said that it can be fixed by "write cert" from the box.
Unfortunately i can't find any box seller in my country.
And i've brought my phone to Samsung Service Centre, they said that they're going to TRY installing another ROM, and they said that the risk of the process failure is my phone will be dead, and if that happened, i have to bring back to US AT&T to fix the phone (which is very far from my current country).
I didn't want to take the risk, so i currently using my phone only with wifi.
I've checked via Root Explorer and ES Explorer while being rooted, the efs folder is empty.
Unfortunately, i don't have any backups from this phone.
Any solution for this condition?
Thanks before
IMEI
jooo91 said:
hello everyone,
my device sm-n910a is currently working well with wifi connection, i'm using it in asia, so i need the IMEI to unlock the phone.
But unfortunately my IMEI went null, i don't know what caused it, but since the IMEI is still good, here's what happened :
1. I tried to unlock via *#9090#, i forgot what i've pressed, my phone immediately restarted itself, and it went in bootloop (switched on for about 1-3minutes and the phone restart itself again).
I've realized that the imei and baseband went null (*#06# shows "null")
2. Then i found an article in other forum to fix bootloop problem.
i followed the instructions there without realizing that it's supposed to be supported with a service box (octoplus)
The instructions are :
3. After finished all the instructions given, my phone's baseband got fixed, but the imei still unknown (*#06# shows "/01")
4. In the instructions said that it can be fixed by "write cert" from the box.
Unfortunately i can't find any box seller in my country.
And i've brought my phone to Samsung Service Centre, they said that they're going to TRY installing another ROM, and they said that the risk of the process failure is my phone will be dead, and if that happened, i have to bring back to US AT&T to fix the phone (which is very far from my current country).
I didn't want to take the risk, so i currently using my phone only with wifi.
I've checked via Root Explorer and ES Explorer while being rooted, the efs folder is empty.
Unfortunately, i don't have any backups from this phone.
Any solution for this condition?
Thanks before
Click to expand...
Click to collapse
My baseband is ok but my IMEI is "unknown " does this mean there is hope
I had this happen to my note 2 i gave up and it sat for 6 months i bought another device and fogot about it then one day i was bored and decided to try fixing it again. I did fix it by flashing the modem i believe in odin can't remember exactly but when i turned it on everything came back. I deleted a folder i wasn't suppose to google that problem and you should find something ill try and find what i did.
bonebeatz1234 said:
I had this happen to my note 2 i gave up and it sat for 6 months i bought another device and fogot about it then one day i was bored and decided to try fixing it again. I did fix it by flashing the modem i believe in odin can't remember exactly but when i turned it on everything came back. I deleted a folder i wasn't suppose to google that problem and you should find something ill try and find what i did.
Click to expand...
Click to collapse
is it the modem.bin which is extracted from the ROM (tar.md5 file which we put on odin's AP) ?
i've tried it, but no luck :crying:
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