Related
After lots of dead ends I finally found a solution, flash global QCN on the Chinese version of the phone.
1. Go here and go up to step 6 and STOP. Make sure you don't delete with ADB before you backup with QPST too (see step 2)
2. Go to QPST -> Start clients -> Software Download -> Backup --- Back up as QCN, this is your original is anything goes wrong.
2.5 Make sure you have your IMEI written somewhere.
3. Download QCN and XQCN + All you need for the guide , proceed with the guide until step 12 and then first restore the QCN, reboot -> restore edited XQCN, reboot
4. Enjoy LTE
5. Backup new QCN with working LTE.
Drivers:
Drivers
Alternate method:
Use RF_MV_Manager to restore IMEI directly to the QCN file, youll need to use the QPST from that thread, the other one doesn't have RF_MV_Manager.
Restore only QCN, LTE fixed.
Bonus:
Using this guide, make sure you still have band 4, original value should be 2061584302303.
vkass said:
After lots of dead ends I finally found a solution.
1. Go here and go up to step 6 and STOP. Make sure you don't delete with ADB before you backup with QPST too (see step 2)
2. Go to QPST -> Start clients -> Software Download -> Backup --- Back up twice, once as QCN and once as XQCN.
3. Download QCN and XQCN + All you need for the guide , proceed with the guide until step 12 and then first restore the QCN, reboot -> restore edited XQCN, reboot
4. Enjoy LTE
5. Backup new QCN with working LTE.
Drivers:
Drivers
Bonus:
Using this guide, make sure you still have band 4, original value should be 2061584302303.
Click to expand...
Click to collapse
Is there a QCN or XQCN with all US LTE bands unlocked yet?
LiQuiD_FeAR said:
Is there a QCN or XQCN with all US LTE bands unlocked yet?
Click to expand...
Click to collapse
I don't think there will ever be one.
You can unlock all the bands you need with http://forum.xda-developers.com/redmi-note/general/unlock-lte-bands-step-step-xiaomi-mi-t3084774
If it doesn't work there might be a filter, which is a hardware mod.
vkass said:
I don't think there will ever be one.
You can unlock all the bands you need with http://forum.xda-developers.com/redmi-note/general/unlock-lte-bands-step-step-xiaomi-mi-t3084774
If it doesn't work there might be a filter, which is a hardware mod.
Click to expand...
Click to collapse
I tried to set my nv memory up for AT&T and my current values look like this:
sim0
00441 : 0xFFFF
00946 : 0xBFFF
01877 : 562950069289347
02954 : 131072
06828 : 2061719111903
06829 : 2061719111903
I get 4g in Europe where i am currently but i haven't been to America to try it on at&t yet
LiQuiD_FeAR said:
I tried to set my nv memory up for AT&T and my current values look like this:
sim0
00441 : 0xFFFF
00946 : 0xBFFF
02954 : 131072
06828 : 2061719111903
06829 : 2061719111903
I get 4g in Europe where i am currently but i haven't been to America to try it on at&t yet
Click to expand...
Click to collapse
Well I guess you'll find out if it worked when you get there.
If it doesn't it's probably hardware filter.
vkass said:
After lots of dead ends I finally found a solution.
1. Go here and go up to step 6 and STOP. Make sure you don't delete with ADB before you backup with QPST too (see step 2)
2. Go to QPST -> Start clients -> Software Download -> Backup --- Back up twice, once as QCN and once as XQCN.
2.5 Make sure you have your IMEI written somewhere.
3. Download QCN and XQCN + All you need for the guide , proceed with the guide until step 12 and then first restore the QCN, reboot -> restore edited XQCN, reboot
4. Enjoy LTE
5. Backup new QCN with working LTE.
Drivers:
Drivers
Bonus:
Using this guide, make sure you still have band 4, original value should be 2061584302303.
Click to expand...
Click to collapse
if not root can't?
@aried73 must be rooted
thanks I made everything as you wrote, LTE began to catch well! but now I established android 5.1.1 AOSP, I can establish CM13 and not lose the qcn control?
I still have the following issues after following the steps:
- 4Gs network are actually detected when doing network search, but it will be 3G after we select it anyway
- setting preferred mode to LTE Only will make things worse: can't search for network
- in 2nd sim 4G works fine
any help?
Edit: actually I also want to ask: should I first restore your QCN file (80DE5873_0), unmodified? (I did). What's the difference between XQCN and QCN
Hi just wanna ask if this tutorial actually are the method to repair IMEI for anyone that have invalid or blank IMEI after flash / upgrade from custom vendor ROM?
Mine updated from custom vendor ROM MIUI7 (version 7.1.9.0.0) to MIUI7 (7.3.2) the IMEI seems ok, both SIM have different IMEI, even after flash to MIUI8 dev, for unlocking bootloader purpose, the IMEI seems valid, still only SIM2 able to lock 4G.
P/S : Currently I'm on CM13 look like the IMEI still valid and okay and yet only SIM2 can do 4G,
BTW does the method above can be apply on CM13 or just under MIUI environment?
What you're doing here is flash default global qcn file.
If you got a phone with custom firmware it's probably the Chinese version and that's why LTE doesn't work.
@salzzz yes that right first qcn then xqcn, I don't know the default imei for the qcn so can't edit it, only with alternate method I posted after.
Which ROM and radio are you using?
Make sure you use adb commands from the guide to wipe everything related to radio.
@Kirk77777 flashing Roms has not affect on qcn.
@BaTaK_iCe like I said it flashes default global qcn, it will fix any issues with radio, whether it's Lte or imei. Works with any rom.
Basically like going back to global stock.
@ vkass
hello please say why on cm13 santoshi, and other customs, lte only on 2sim slot ?
Kirk77777 said:
@ vkass
hello please say why on cm13 santoshi, and other customs, lte only on 2sim slot ?
Click to expand...
Click to collapse
It didn't work for you.
You need to follow the guide completely step by step, wiping with adb is crucial.
dd if=/dev/zero of=/dev/block/mmcblk0p13
dd if=/dev/zero of=/dev/block/mmcblk0p14
dd if=/dev/zero of=/dev/block/mmcblk0p16
reboot
Just restoring the QCN should give you LTE, but the IMEI will be different, that why you need to restore XQCN with your IMEI.
OR like I said in OP follow alternative method and edit IMEI in QCN directly.
It didn't work for you.
You need to follow the guide completely step by step, wiping with adb is crucial.
dd if=/dev/zero of=/dev/block/mmcblk0p13
dd if=/dev/zero of=/dev/block/mmcblk0p14
dd if=/dev/zero of=/dev/block/mmcblk0p16
reboot
I DO THIS, its not working to me, i`m sad ((
I have tried it again:
I can't install the QPST from alternative method link, so I followed "the guide" (restoring imei), followed that dd-fill-with-zero, restore QCN.
I managed to restore imei using QXDM, yet LTE is still not working (before & after I restore imei)
I'm on CM13 1807 by Santosh, some days ago there's a radio.zip in that thread, and I flashed it, dunno which version, but baseband shows -8976_GEN_PACK-3.53308.1.57464.1
I'm not sure about imei, too, first time I bought the phone it comes with same imei, only 1 imei on box (which matches both sim imeis),
Phone comes with 7.19 rom. forgot whether the LTE was working/not though; after I flashed global rom, I just check that LTE is detected in both SIM1/2, but only works in sim 2
salzzz said:
I have tried it again:
I can't install the QPST from alternative method link, so I followed "the guide" (restoring imei), followed that dd-fill-with-zero, restore QCN.
I managed to restore imei using QXDM, yet LTE is still not working (before & after I restore imei)
I'm on CM13 1807 by Santosh, some days ago there's a radio.zip in that thread, and I flashed it, dunno which version, but baseband shows -8976_GEN_PACK-3.53308.1.57464.1
I'm not sure about imei, too, first time I bought the phone it comes with same imei, only 1 imei on box (which matches both sim imeis),
Phone comes with 7.19 rom. forgot whether the LTE was working/not though; after I flashed global rom, I just check that LTE is detected in both SIM1/2, but only works in sim 2
Click to expand...
Click to collapse
I really don't know, maybe check phone settings at
*#*#4636#*#* and make sure it's on LTE for sim1.
As you can see it works for me, I also have same imei for both sims.
AFAIK the radio zip is for official cm, maybe backup your rom and try flashing stock MIUI just to see if it works.
hi, just wondering how come i dont get the option to use xqcn in qpst?? it only allows me to restore qcn
[edit] updated version of qpst allows xqcn.
But now I'm getting this error when i try to restore xQCN after QCN
"The ESN of the phone does not match the ESN of this file containing RF calibration data"
What should i do?
I'm also getting. "No space on device" error when i run these commands
dd if=/dev/zero of=/dev/block/mmcblk0p13
dd if=/dev/zero of=/dev/block/mmcblk0p14
dd if=/dev/zero of=/dev/block/mmcblk0p16
Need to tick "allow file esn mismatch", restore anyway.
The error doesn't really make sense as it is used to delete.
Maybe the process needs to be done on stock MIUI.
Btw do you execute them one by one?
Dimmz said:
I'm also getting. "No space on device" error when i run these commands
dd if=/dev/zero of=/dev/block/mmcblk0p13
dd if=/dev/zero of=/dev/block/mmcblk0p14
dd if=/dev/zero of=/dev/block/mmcblk0p16
Click to expand...
Click to collapse
according to this, it's just a false positive error, you can ignore it
@vkass LTE is on for sim 1 and 2 (if it isn't, it shouldn't have been detected when doing network search either)
Hopefully there'll be a solution for this soon. Btw, what's your baseband version?
UPDATE (07-Jan-2017):
If your OnePlus 2's IMEI#2 = 0, (IMEI#1 is showing correct IMEI)
Because you run these commands in fastboot mode:
"fastboot erase modemst1 "
"fastboot erase modemst2 "
"fastboot erase cache"
Then,
A fix has been made into this zip file.
https://www.androidfilehost.com/?fid=529152257862693598
Kindly thank Tony.L & Crystal.Z from OnePlus OOS team.
You have to be on OOS 3.5.6 (Clean-Flashed, non-rooted, from whatever ROM you are currently on).
I had TWRP Hybrid Recovery v3.4 installed.
IMEI#2 will come back again.
Now, Remember to backup EFS using terminal method.
& DONT erase modem ever again.
mine have same problem..only IMEI2 shows "0"..my phone keep random rebooting until now
osr.arora said:
I will be really grateful, if anybody can help me recover/write IMEI#2 on my OnePlus 2.
IMEI#2 currently shows as "0", (IMEI#1 is showing correct IMEI)
I don't have a EFS backup.
Device is out of warranty.
OnePlus's L2 support team, flashed OOS v3.1.0 via Qualcomm recovery method via remote session, but still no fix.
Lastly (I think, some may consider this illegal, but I'm just trying to write the missing IMEI on my phone),
I searched for IMEI writer softwares ( WriteDualIMEI(W+G_eMMC), Read&Write_Tool_v1.3) on internet, but somehow, i couldn't make them work (Maybe incorrect Qualcomm drivers on my PC, or idk what )
*********How did this all happen*********
I read a blog, that In order to increase the download speed from the Jio SIM, preferred LTE Band should be switched (from 3 to 40).
So, I pressed *#*#4636#*#*, >> Phone Info page >> three dot menu >> select radio band >> SELECTED Band mode 40.
Immediately after that,
Vodafone Sim stopped working in any of the SIM-Slots, But Jio sim (4G) was working in both the slots.
*****
Then I ran these commands in fastboot mode:
"fastboot erase modemst1 "
"fastboot erase modemst2 "
"fastboot erase cache"
Immediately, Both the SIM slots stopped working.
*****
Then I flashed "new-modem.zip" from benschhold (https://androidfilehost.com/?fid=24407100847293158)
which makes SIM-Slot-1 work with both Vodafone & Jio,
But SIM-Slot-2 only detects the sim, but with 0 network bars i.e. "No service| Vodafone"
I would appreciate your help.
Click to expand...
Click to collapse
***************************************
lockmunk said:
mine have same problem..only IMEI2 shows "0"..my phone keep random rebooting until now
Click to expand...
Click to collapse
Lesson for you guys. The first thing to do after flashing a custom recovery is to make a complete nandroid backup..
Tunatje said:
Lesson for you guys. The first thing to do after flashing a custom recovery is to make a complete nandroid backup..
Click to expand...
Click to collapse
FYI, a full nandroid backup doesn't backup the two EFS partitions even though EFS is an option in TWRP's backup menu.
You need to manually backup the modemst1 & modemst2 partitions
Spannaa said:
FYI, a full nandroid backup doesn't backup the two EFS partitions even though EFS is an option in TWRP's backup menu.
You need to manually backup the modemst1 & modemst2 partitions
Click to expand...
Click to collapse
True. Done it myself through terminal. Forgot about the dual sim :laugh:
osr.arora said:
I will be really grateful, if anybody can help me recover/write IMEI#2 on my OnePlus 2.
IMEI#2 currently shows as "0", (IMEI#1 is showing correct IMEI)
I don't have a EFS backup.
Device is out of warranty.
OnePlus's L2 support team, flashed OOS v3.1.0 via Qualcomm recovery method via remote session, but still no fix.
Lastly (I think, some may consider this illegal, but I'm just trying to write the missing IMEI on my phone),
I searched for IMEI writer softwares ( WriteDualIMEI(W+G_eMMC), Read&Write_Tool_v1.3) on internet, but somehow, i couldn't make them work (Maybe incorrect Qualcomm drivers on my PC, or idk what )
*********How did this all happen*********
I read a blog, that In order to increase the download speed from the Jio SIM, preferred LTE Band should be switched (from 3 to 40).
So, I pressed *#*#4636#*#*, >> Phone Info page >> three dot menu >> select radio band >> SELECTED Band mode 40.
Immediately after that,
Vodafone Sim stopped working in any of the SIM-Slots, But Jio sim (4G) was working in both the slots.
*****
Then I ran these commands in fastboot mode:
"fastboot erase modemst1 "
"fastboot erase modemst2 "
"fastboot erase cache"
Immediately, Both the SIM slots stopped working.
*****
Then I flashed "new-modem.zip" from benschhold (https://androidfilehost.com/?fid=24407100847293158)
which makes SIM-Slot-1 work with both Vodafone & Jio,
But SIM-Slot-2 only detects the sim, but with 0 network bars i.e. "No service| Vodafone"
***************************************
I would appreciate your help.
Click to expand...
Click to collapse
Did you managed to get any info on that??
I also encountered the exactly same issue..
ashu01 said:
Did you managed to get any info on that??
I also encountered the exactly same issue..
Click to expand...
Click to collapse
No Fix, as of yet !
Somebody said, he flashed modem files from beanstalk Rom thread, & that fixed the missing IMEI issue.
I haven't tried it yet,
If you try it, & it fixes this problem, update me on thia thread !
Hi
Like I wrote in another thread, this is what I did to get working modem after testing out the unstable H2OS firmware
1. Ran TWRP backup of CM14 install
2. Restored OOS 3.1 OTA zip
3. Formatted modemst1 and 2 and persist partition using fastboot
4. Did factory reset and booted up OOS and powered down the phone
5. Powered up into fastboot and restored persist partition with the persist.img dump found in some thread in this forum
6. Restored back my CM14 install and now everything is working again (except for losing some configuration probably stored in the persist partition like button swapping and battery text on icon)
Best regards
pitrus- said:
Hi
Like I wrote in another thread, this is what I did to get working modem after testing out the unstable H2OS firmware
1. Ran TWRP backup of CM14 install
2. Restored OOS 3.1 OTA zip
3. Formatted modemst1 and 2 and persist partition using fastboot
4. Did factory reset and booted up OOS and powered down the phone
5. Powered up into fastboot and restored persist partition with the persist.img dump found in some thread in this forum
6. Restored back my CM14 install and now everything is working again (except for losing some configuration probably stored in the persist partition like button swapping and battery text on icon)
Best regards
Click to expand...
Click to collapse
Can u send me persist.img pls
My email is [email protected]
Would be better, if you upload persist file here.
pitrus- said:
Hi
Like I wrote in another thread, this is what I did to get working modem after testing out the unstable H2OS firmware
1. Ran TWRP backup of CM14 install
2. Restored OOS 3.1 OTA zip
3. Formatted modemst1 and 2 and persist partition using fastboot
4. Did factory reset and booted up OOS and powered down the phone
5. Powered up into fastboot and restored persist partition with the persist.img dump found in some thread in this forum
6. Restored back my CM14 install and now everything is working again (except for losing some configuration probably stored in the persist partition like button swapping and battery text on icon)
Best regards
Click to expand...
Click to collapse
We are facing missing IMEI#2 issue,
Did your steps, fix this issue ?
osr.arora said:
We are facing missing IMEI#2 issue,
Did your steps, fix this issue ?
Click to expand...
Click to collapse
Yes they did, after flashing the H20S firmware and going back to OOS firmware I was missing IMEI on both modems/incompatible modemst partitions. Formatting these and booting up OOS recreated these and after also restoring persist partition both IMEIs was reported and Cyanogenmod no longer bootlooped.
pitrus- said:
Yes they did, after flashing the H20S firmware and going back to OOS firmware I was missing IMEI on both modems/incompatible modemst partitions. Formatting these and booting up OOS recreated these and after also restoring persist partition both IMEIs was reported and Cyanogenmod no longer bootlooped.
Click to expand...
Click to collapse
Before flashing H2Os firmware,
What was your OP2 running ?
Also can you list all links to files, which helped you.
Just an hour ago, i flashed "ResurrectionRemix-6.0-OOS-2.2.1-Modem.zip" on my OnePlus 2 (running Oxygen OS 3.1.0 with TWRP) & it went into bootloop.
So now i'm downloading @Spannaa 's "Oxygen OS 2.1.1 fastboot.zip" , to make my phone working again.
osr.arora said:
We are facing missing IMEI#2 issue,
Did your steps, fix this issue ?
Click to expand...
Click to collapse
I though my phone was fine, then I noticed my swedish BankID just didn't want to work. Turns out my SIM2 has null IMEI just like yours. Tried Qualcomm restore to OOS 3.0.2 but still IMEI2:0, so it looks like trying out the H2OS 2.5 beta firmware and going back was a real killer for my phone. I get signal on both SIM cards and strangely I can call using both SIM cards even though one is showing no IMEI
Update
After analyzing the nv data of my phone, I can tell that the IMEI for SIM card 1 is there, and there does not seem to be any address register for a second IMEI so the phone must figure this out itself. For me the first IMEI ends with a 99 and second with a 81 which means a difference of -18, perhaps second IMEI is always -18 hexadecimal from the first and therefore automatically calculated and registered by the modem firmware?
@pitrus-
Do you have a European A2003 model? I remember that the difference between European and Chinese models was that the Chinese has only 1 IMEI. Maybe this H20S firmware changed your European model effectively to Chinese. FYI my IMEIs, untoutched by H2OS, differ by 8, 72 vs 64. You can check your original IMEIs from the red box that the phone shipped in, if you still have it.
To resolve this, Oneplus customer service recommends to replace the motherboard:
https://forums.oneplus.net/threads/those-who-lost-their-imei-please-read.475930/page-5#post-15427155
pryggi said:
@pitrus-
Do you have a European A2003 model? I remember that the difference between European and Chinese models was that the Chinese has only 1 IMEI. Maybe this H20S firmware changed your European model effectively to Chinese. FYI my IMEIs, untoutched by H2OS, differ by 8, 72 vs 64. You can check your original IMEIs from the red box that the phone shipped in, if you still have it.
To resolve this, Oneplus customer service recommends to replace the motherboard:
https://forums.oneplus.net/threads/those-who-lost-their-imei-please-read.475930/page-5#post-15427155
Click to expand...
Click to collapse
Yes, it's an A2003 European model. If only I had a dump of a working A2003 NV Data so I could find the difference between them. Whoever could give me this could just zap out 00550 NV Item (IMEI) so as not to share it with me. That would tell us which NV Items to change to swap between single och dual sim card modell.
@pitrus-
I have the IMEIs on my OP2 still intact, I have not flashed latest H2OS beta, nor have I used the fastboot erase/format commands. So I can analyse the /dev/block/mmcblk0p17 and /dev/block/mmcblk0p18 dd dumps. Could you tell me which tools to use, or how can I edit out my IMEIs?
Really confused, what to flash, what not to flash (to fix the IMEI issue) !!!
I restored my OP2 to OOS 2.1.1 with Qualcomm Restore Files (from OnePlus Forums) as @Spannaa 's fastboot file, didn't worked, idk why !
osr.arora said:
Really confused, what to flash, what not to flash (to fix the IMEI issue) !!!
I restored my OP2 to OOS 2.1.1 with Qualcomm Restore Files (from OnePlus Forums) as @Spannaa 's fastboot file, didn't worked, idk why !
Click to expand...
Click to collapse
It doesn't mather what you flash, our nv data is incompatible with all modems other than the unstable H2OS 2.5 one. Only solution is to wait for a OxygenOS modem that uses the same nv data structure if you like me didn't make a dump of the nv data before flashing the H2OS ROM. If you do want to go back to CM14, just flash H2OS 2.5.x and then format system, data, cache and flash latest CM14. You will still get null IMEI on second SIM slot, there's no solution for this right now. (You could also Qualcomm restore back to OxygenOS 3.1, this will give you the TZ needed by CM14).
pitrus- said:
It doesn't mather what you flash, our nv data is incompatible with all modems other than the unstable H2OS 2.5 one. Only solution is to wait for a OxygenOS modem that uses the same nv data structure if you like me didn't make a dump of the nv data before flashing the H2OS ROM. If you do want to go back to CM14, just flash H2OS 2.5.x and then format system, data, cache and flash latest CM14. You will still get null IMEI on second SIM slot, there's no solution for this right now. (You could also Qualcomm restore back to OxygenOS 3.1, this will give you the TZ needed by CM14).
Click to expand...
Click to collapse
i also used fastboot erase command..and in the same situation of showing imei2 0.
do you think the oos update will have a fix for this issue??
My nexus 6p is not showing IMEI and also showing unknown for Baseband version. I have no efs backup. Tried reflashing stock firmware, erasing modemst1, modemst2, modem, fsg, custom rom (RR), and tried them in different combinations. Yet it still shown baseband unknown. :crying:
Is there any way I can get modemst1 and modemst2? Please suggest a solution to fix this. Warranty over a week before this happened. And it happened out of nowhere. :crying:
Baseband is the radio, isn't it? You can get the latest image from here:
http://forum.xda-developers.com/nexus-6p/general/nmf26f-official-7-1-1-radio-vendor-t3513430
---------- Post added at 10:53 AM ---------- Previous post was at 10:50 AM ----------
You might want to do a complete install of the latest system image if flashing the radio doesn't solve your problem:
https://developers.google.com/android/images
---------- Post added at 10:58 AM ---------- Previous post was at 10:53 AM ----------
I'm not sure that either of these will restore your IMEI, however. Do you have a CDMA or GSM phone?
jhs39 said:
Baseband is the radio, isn't it? You can get the latest image from here:
http://forum.xda-developers.com/nexus-6p/general/nmf26f-official-7-1-1-radio-vendor-t3513430
---------- Post added at 10:53 AM ---------- Previous post was at 10:50 AM ----------
You might want to do a complete install of the latest system image if flashing the radio doesn't solve your problem:
https://developers.google.com/android/images
---------- Post added at 10:58 AM ---------- Previous post was at 10:53 AM ----------
I'm not sure that either of these will restore your IMEI, however. Do you have a CDMA or GSM phone?
Click to expand...
Click to collapse
Thanks for the reply. I tried both of em. Is there any way i can get fsg, modemst1, modemst2 files? Im thinking of finding another Nexus 6P and copying its files and somehow editing the IMEI information using some HEX editor and then uploading to my phone.
If it is alright then can you or someone send me their modemst1, modemst2 and fsg files after editing their IMEI no. ?
This site provide how to edit your IMEI: androidbrick (Change it to something like 876543210123456)
Btw my phone is LTE/GSM
I think if you can get a hold of someone's EFS backup and restore it on your phone it would restore your missing IMEI number. The problem is finding someone who is willing to provide you with a copy of their EFS backup.
I was able to get the IMEI number for my Nexus 6P from Google Dashboard:
http://www.google.com/settings/dashboard
Once you know your IMEI you may be able to restore it with an app like IMEI Tweak.
jhs39 said:
I think if you can get a hold of someone's EFS backup and restore it on your phone it would restore your missing IMEI number. The problem is finding someone who is willing to provide you with a copy of their EFS backup.
Click to expand...
Click to collapse
Yes. I'm trying to find someone who can provide me with modem files.
jhs39 said:
I was able to get the IMEI number for my Nexus 6P from Google Dashboard:
http://www.google.com/settings/dashboard
Once you know your IMEI you may be able to restore it with an app like IMEI Tweak.
Click to expand...
Click to collapse
I have the box which has the IMEI. I tried some apps like IMEI Tweaks. Even tried some apps through XPOSED framework. Nothing worked. Hope someone gives me the modem files.
pronuba66 said:
My nexus 6p is not showing IMEI and also showing unknown for Baseband version. I have no efs backup. Tried reflashing stock firmware, erasing modemst1, modemst2, modem, fsg, custom rom (RR), and tried them in different combinations. Yet it still shown baseband unknown. :crying:
Is there any way I can get modemst1 and modemst2? Please suggest a solution to fix this. Warranty over a week before this happened. And it happened out of nowhere. :crying:
Click to expand...
Click to collapse
How did you erase modemst1 & modemst2? From an ADB shell like this? I can't find it to save my life, but I did read if the EFS partitions are formatted properly they will rebuild from firmware on first boot. You stated phone is out of warranty, but did you actually get denied when you called Huawei? There may be an unadvertised warranty/RMA for your phone's current state, or they may be able to suggest a fix.
v12xke said:
How did you erase modemst1 & modemst2? From an ADB shell like this? I can't find it to save my life, but I did read if the EFS partitions are formatted properly they will rebuild from firmware on first boot. You stated phone is out of warranty, but did you actually get denied when you called Huawei? There may be an unadvertised warranty/RMA for your phone's current state, or they may be able to suggest a fix.
Click to expand...
Click to collapse
I erased using dd command as stated in your link provided. But even after several reboots, and several uploads of different ROMS, it still is zero (Both modemst1 and modemst2).
My phone was bought from a different country, and hence warranty was not accepted in my country. Even the people at the Huawei service center was not very helpful.
I'm actually waiting for my friend to root his phone(unlocking required which will erase the user data) so that I can get the modem files. If fixed I'll message you.
pronuba66 said:
I erased using dd command as stated in your link provided. But even after several reboots, and several uploads of different ROMS, it still is zero (Both modemst1 and modemst2).
My phone was bought from a different country, and hence warranty was not accepted in my country. Even the people at the Huawei service center was not very helpful.
I'm actually waiting for my friend to root his phone(unlocking required which will erase the user data) so that I can get the modem files. If fixed I'll message you.
Click to expand...
Click to collapse
Good luck.
---------- Post added at 09:17 PM ---------- Previous post was at 09:12 PM ----------
jhs39 said:
Good luck.
Click to expand...
Click to collapse
From what I've read if your friend makes an EFS backup you can use that to restore yours. If the modem restore doesn't work you might want to try that,
pronuba66 said:
I erased using dd command as stated in your link provided. But even after several reboots, and several uploads of different ROMS, it still is zero (Both modemst1 and modemst2).
My phone was bought from a different country, and hence warranty was not accepted in my country. Even the people at the Huawei service center was not very helpful.
I'm actually waiting for my friend to root his phone(unlocking required which will erase the user data) so that I can get the modem files. If fixed I'll message you.
Click to expand...
Click to collapse
Any solution for this? I also have imei unknown, baseband unknown issue. I don't have an efs backup either. Also flashed stock rom, but it didn't help. Any suggestions would be really appreciated.
chathura2020 said:
Any solution for this? I also have imei unknown, baseband unknown issue. I don't have an efs backup either. Also flashed stock rom, but it didn't help. Any suggestions would be really appreciated.
Click to expand...
Click to collapse
Hi,
You can try this:
Find someone having the same firmware. Root his phone and download all the partitions from his phone (from "/dev/block/platform/soc.0/f9824900.sdhci/by-name" using dd command or adb pull (in root mode). To change the IMEI from his to yours, use a hex editor and edit the IMEI in one of the partitions (I think it was in modemst1 or modem or devinfo partition).
I have tried this but my mobile was bought from UAE and Indian firmware did not work. But that fixed some restart issue, heating problem and the phone was more stable which implied the problem was definitely some corrupted partitions.
If you get it fixed please do tell me. Good luck.
Please do keep backup of your partitions
pronuba66 said:
Hi,
You can try this:
Find someone having the same firmware. Root his phone and download all the partitions from his phone (from "/dev/block/platform/soc.0/f9824900.sdhci/by-name" using dd command or adb pull (in root mode). To change the IMEI from his to yours, use a hex editor and edit the IMEI in one of the partitions (I think it was in modemst1 or modem or devinfo partition).
I have tried this but my mobile was bought from UAE and Indian firmware did not work. But that fixed some restart issue, heating problem and the phone was more stable which implied the problem was definitely some corrupted partitions.
If you get it fixed please do tell me. Good luck.
Please do keep backup of your partitions
Click to expand...
Click to collapse
My phone is going through exact same problem. My device was stuck in bootloop I got it fixed from a market place and my device would not show any carrier signals or my imei. How can I get modem files or what is a fix to it? Please help.
hkingpro said:
My phone is going through exact same problem. My device was stuck in bootloop I got it fixed from a market place and my device would not show any carrier signals or my imei. How can I get modem files or what is a fix to it? Please help.
Click to expand...
Click to collapse
In theory the Nexus 6P should rebuild the EFS Partitions if you overwrite them with zeros.
I used the following to fix my 6P back when TWRP v3.0.2-1 had a bug that restored the EFS1 partition to both EFS slots, causing the phone to not boot.
Try this:
Boot your Nexus 6P into TWRP;
Plug the phone into a PC that has ADB tools installed;
Then on PC, open Command Prompt with access to ADB and execute the following commands:
ADB shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst1 bs=16384
and
ADB shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst2 bs=16384
Let me know if this works for you.
defcondev said:
In theory the Nexus 6P should rebuild the EFS Partitions if you overwrite them with zeros.
I used the following to fix my 6P back when TWRP v3.0.2-1 had a bug that restored the EFS1 partition to both EFS slots, causing the phone to not boot.
Try this:
Boot your Nexus 6P into TWRP;
Plug the phone into a PC that has ADB tools installed;
Then on PC, open Command Prompt with access to ADB and execute the following commands:
ADB shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst1 bs=16384
and
ADB shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst2 bs=16384
Let me know if this works for you.
Click to expand...
Click to collapse
THANK YOU SO MUCH FOR YOUR REPLY. I tried this but it did not work for me brother. I have been searching day and night for this but not getting any solution for this. I was browsing Xda the other day and found a thread https://forum.xda-developers.com/nexus-6p/help/lost-imei-sim-error-t3282545 in comments section Tyson568 has shared a link which I think might be EFS modem files? Do you think that can help? If that can how can I flash them?
hkingpro said:
THANK YOU SO MUCH FOR YOUR REPLY. I tried this but it did not work for me brother. I have been searching day and night for this but not getting any solution for this. I was browsing Xda the other day and found a thread https://forum.xda-developers.com/nexus-6p/help/lost-imei-sim-error-t3282545 in comments section Tyson568 has shared a link which I think might be EFS modem files? Do you think that can help? If that can how can I flash them?
Click to expand...
Click to collapse
Have you tried flashing a factory image to your 6P?
If not, I would backup all of your data to a computer and flash a stock factory image to your 6P and see if this resolves the issue.
You can find the images and instructions at the link below under the section titled "angler for Nexus 6P"
Make sure to NOT re-lock the bootloader at this point (just skip that step in the flashing instructions).
Keep in mind, this will remove TWRP from your 6P and revert back to the stock Recovery - keep the stock recovery and boot the 6P fully to see if the issue is resolved. If your IMEI returns, you can then flash TWRP and backup your EFS partitions.
https://developers.google.com/android/images
defcondev said:
Have you tried flashing a factory image to your 6P?
If not, I would backup all of your data to a computer and flash a stock factory image to your 6P and see if this resolves the issue.
You can find the images and instructions at the link below under the section titled "angler for Nexus 6P"
Make sure to NOT re-lock the bootloader at this point (just skip that step in the flashing instructions).
Keep in mind, this will remove TWRP from your 6P and revert back to the stock Recovery - keep the stock recovery and boot the 6P fully to see if the issue is resolved. If your IMEI returns, you can then flash TWRP and backup your EFS partitions.
https://developers.google.com/android/images
Click to expand...
Click to collapse
I tried multiple Images but none of them worked. My phone was bootlooping again and again and then finally I followed this thread. I flashed 8.0 factory image and flashed rest of images suggested by this thread and my phone booted up. I don't know what to do here.
hkingpro said:
I tried multiple Images but none of them worked. My phone was bootlooping again and again and then finally I followed this thread. I flashed 8.0 factory image and flashed rest of images suggested by this thread and my phone booted up. I don't know what to do here.
Click to expand...
Click to collapse
I had same issue on my OnePlus X. I kept backing up and restoring EFS partion everytime I needed a restore which now know not suppose to do. Unknown baseband and no imei. Anyways the way I fixed it was simply booting into bootloader mode, fastboot command window type
"fastboot erase modemst1 "
"fastboot erase modemst2 "
I never tested on my Nexus 6p so use at own risk.
Admin Note: This is a special Q&A-formatted thread. Please follow this link to view it in your browser: [url]http://xda.tv/post75619905[/URL]
Please delete the EFS file, restoring another phone's EFS is illegal, sorry.
i lost my voLTE after flashing twrp based stock rom ( nov patch) on pixel experience feb build... now i cant use my jio sim for calls ... No VoLTE support...
if you have a backup of your EFS , can you please send me the file...
sir,what is your baseband version when the volte is working.?(if your current rom has volte working then what is your current baseband version.?)
IMEI shows 0 again after Restore your EFS file
Restore his efs file after flashing pixel experince 8.1,
Just go into twrp,
Flash pixel experince 8.1
And afther that restore his efs partition from twrp .
You will able to get your imei back,
But problem is after doing this way I still not able to get volte.
M8953_02.03.07.08r
Can you tell us what version of baseband do you see when you enter in boot loder.?
Because in my boot loder I see M8953_02.03.07.08U.
thedr34m13 said:
Admin Note: This is a special Q&A-formatted thread. Please follow this link to view it in your browser:
Click to expand...
Click to collapse
Persist backup may help to get volte back..please share if you can
yes,can you share the whole backup of pixel experience rom 8.1 (with volte working),by restoring that backup i think we may able to get volte.
i found this really helpful on another post,
what i did was deleting these files
fastboot erase modemst1
fastboot erase modemst2
from the fastboot comands before flashing back to stock
that works perfectly for me and i got back my signal &4glte.
XT 1806 here. Well, not long ago I posted about thinking I found a way... well... nothing. followed every single thread on hoy to restore basemand/imei to no avail.
So far what I know is that I was running fine, while trying to make cerberus a system app. The phone rebooted and bam. No more baseband.
Before that, I had done the trick of installing an oreo rom (Validus) and going back to stock. It worked and I got back Baseband on bootloader and then in the OS.
I have backups from my EFS from TWRP and PartitionsManager (modem, modemst1, modemst2 and persist) within the OS. Restoring those was no good. It worked before but not now.
I have bootloader C2.06. Before, I had C2.07. Installing the latest update from https://firmware.center/firmware/Motorola/Moto G5s Plus/Stock/ , being it SANDERS_NPSS26.116-61-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml did nothing to update the bootloader or writing the modem.
So far I have a theory and is that, the phone is not taking flashing to the bootloader and or the modem as it should. I am using a high quality USB cable. Changed cables, too. Also, I think something weird is happening with the bootloader or chip programming. It is the first time I face something as weird as this.
I also think it does not like when you start the phone and reboot it quickly. Forgot its Baseband.
Let's be detailed and share experiences to find a cause and then a solution. I have more than 30 hours spent trying to fix this and it is getting to a scary point.
I lost imei and signal....somehow I don't have my efs backup....tried every combo of ROM to get signals ie. something 2g/3g but nothing happens...
However my baseband is intact
Am on 1686 Indian varient
Q. Will moto z Oreo modem work?? Am planning to give it a try
mohitzr said:
I lost imei and signal....somehow I don't have my efs backup....tried every combo of ROM to get signals ie. something 2g/3g but nothing happens...
However my baseband is intact
Am on 1686 Indian varient
Q. Will moto z Oreo modem work?? Am planning to give it a try
Click to expand...
Click to collapse
Any ideas on what happened when you lost the imei?
Please start in bootloader and see what it says in baseband.
barbaroja said:
XT 1806 here. Well, not long ago I posted about thinking I found a way... well... nothing. followed every single thread on hoy to restore basemand/imei to no avail.
So far what I know is that I was running fine, while trying to make cerberus a system app. The phone rebooted and bam. No more baseband.
Before that, I had done the trick of installing an oreo rom (Validus) and going back to stock. It worked and I got back Baseband on bootloader and then in the OS.
I have backups from my EFS from TWRP and PartitionsManager (modem, modemst1, modemst2 and persist) within the OS. Restoring those was no good. It worked before but not now.
I have bootloader C2.06. Before, I had C2.07. Installing the latest update from https://firmware.center/firmware/Motorola/Moto G5s Plus/Stock/ , being it SANDERS_NPSS26.116-61-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml did nothing to update the bootloader or writing the modem.
So far I have a theory and is that, the phone is not taking flashing to the bootloader and or the modem as it should. I am using a high quality USB cable. Changed cables, too. Also, I think something weird is happening with the bootloader or chip programming. It is the first time I face something as weird as this.
I also think it does not like when you start the phone and reboot it quickly. Forgot its Baseband.
Let's be detailed and share experiences to find a cause and then a solution. I have more than 30 hours spent trying to fix this and it is getting to a scary point.
Click to expand...
Click to collapse
You can start with this
Code:
https://www.androidbrick.com/ultimate-guide-qualcomm-snapdragon-xiaomi-mi5-imei-and-baseband-repair-fix/
and it's sister article part 2. I wrote a how-to on using QFIL to back-up and restore qcn files, and my research started there. However, after seeing how many cannot follow basic instructions to use adb/fastboot and even sometimes twrp, I am not going to post it. Let's just say you can edit the proper baseband components, but it is not going to be download and click to install. You will need the following to get started:
Code:
1.[QPST] https://www.androidbrick.com/download/download-latest-qualcomm-flasher-qfil-qpst-2-7-460/
2.[Qualcomm drivers]https://gsmusbdrivers.com/download/android-qualcomm-usb-driver/
3.[hexeditor]http://www.mitec.cz/hex.html
4.[IMEI convertor]https://androidfilehost.com/?fid=962021903579482959
5.Motorola USB drivers [you probably already have these, if you have used adb/fastboot]
You will also need a knowledgeable donor who is willing and able to donate a working backed up qcn file, of the same make/model, and bootloader must be in same state as yours. Although this will have the IMEI , it can be edited to 0 out all but the first digit of the IMEI and thus be safe for posting without fear of someone cloning it. This method has been done with other qualcomm chipsets, and the ultimate goal would be to get the proper working qcn file disassembled and compared to the faulty ones to see exactly where the basebands are being corrupted by the Oreo roms.
barbaroja said:
Any ideas on what happened when you lost the imei?
Please start in bootloader and see what it says in baseband.
Click to expand...
Click to collapse
i get baseband
[email protected] said:
You can start with this
Code:
https://www.androidbrick.com/ultimate-guide-qualcomm-snapdragon-xiaomi-mi5-imei-and-baseband-repair-fix/
and it's sister article part 2. I wrote a how-to on using QFIL to back-up and restore qcn files, and my research started there. However, after seeing how many cannot follow basic instructions to use adb/fastboot and even sometimes twrp, I am not going to post it. Let's just say you can edit the proper baseband components, but it is not going to be download and click to install. You will need the following to get started:
Code:
1.[QPST] https://www.androidbrick.com/download/download-latest-qualcomm-flasher-qfil-qpst-2-7-460/
2.[Qualcomm drivers]https://gsmusbdrivers.com/download/android-qualcomm-usb-driver/
3.[hexeditor]http://www.mitec.cz/hex.html
4.[IMEI convertor]https://androidfilehost.com/?fid=962021903579482959
5.Motorola USB drivers [you probably already have these, if you have used adb/fastboot]
You will also need a knowledgeable donor who is willing and able to donate a working backed up qcn file, of the same make/model, and bootloader must be in same state as yours. Although this will have the IMEI , it can be edited to 0 out all but the first digit of the IMEI and thus be safe for posting without fear of someone cloning it. This method has been done with other qualcomm chipsets, and the ultimate goal would be to get the proper working qcn file disassembled and compared to the faulty ones to see exactly where the basebands are being corrupted by the Oreo roms.
Click to expand...
Click to collapse
Thanks for sharing. Very interesting, indeed.
In my particular case, it happened for no apparent reason. Quick reboots being a suspect here. It seems some got baseband and no imei, others no baseband at all... Any ideas on this?
dev here.
I've been looking into this problem for quite a while now.
Can anyone briefly summarise the problem? Like what all you flashed?
From my understanding:
efs = modemst1 & modemst2 = baseband cache = created on the fly
important baseband related partitions: modem, fsg, persist
Additionally I'm sharing potter retin (march) firmware files: (Download)
Try flashing this (on stock 7.0):
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash persist persist.img
rachitrawat said:
dev here.
I've been looking into this problem for quite a while now.
Can anyone briefly summarise the problem? Like what all you flashed?
From my understanding:
efs = modemst1 & modemst2 = baseband cache = created on the fly
important baseband related partitions: modem, fsg, persist
Additionally I'm sharing potter retin (march) firmware files: (Download)
Try flashing this (on stock 7.0):
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash persist persist.img
Click to expand...
Click to collapse
Thank you so much.
Can you tell me what is your model no.?
And build no ?
And is this backup is from stock rooted rom.?
Is your device bricked yet,or have you loose IMEI in past.?
akshu2697 said:
Thank you so much.
Can you tell me what is your model no.?
And build no ?
And is this backup is from stock rooted rom.?
Is your device bricked yet,or have you loose IMEI in past.?
Click to expand...
Click to collapse
This a dump of an untouched XT1686 92-8 firmware.
rachitrawat said:
This a dump of an untouched XT1686 92-8 firmware.
Click to expand...
Click to collapse
Can you provide me twrp flashable rom 92-8.?
Because I can't find it anywhere.
akshu2697 said:
Can you provide me twrp flashable rom 92-8.?
Because I can't find it anywhere.
Click to expand...
Click to collapse
There isn't one as there is no 92-8 firmware out there.
Sent from my Moto G5 Plus using XDA Labs
did it worked ? .. im having the same problem .. cant get my network signal and imei
akshu2697 said:
Thank you so much.
Can you tell me what is your model no.?
And build no ?
And is this backup is from stock rooted rom.?
Is your device bricked yet,or have you loose IMEI in past.?
Click to expand...
Click to collapse
im having the same problem with my XT1686 indian version .. can we get it back with other efs backups ?
can we import backups from other mobiles and get the job done ?
Repiix said:
im having the same problem with my XT1686 indian version .. can we get it back with other efs backups ?
can we import backups from other mobiles and get the job done ?
Click to expand...
Click to collapse
I haven't tried it yet,
I will tell you if this work.
rachitrawat said:
dev here.
I've been looking into this problem for quite a while now.
Can anyone briefly summarise the problem? Like what all you flashed?
From my understanding:
efs = modemst1 & modemst2 = baseband cache = created on the fly
important baseband related partitions: modem, fsg, persist
Additionally I'm sharing potter retin (march) firmware files: (Download)
Try flashing this (on stock 7.0):
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash persist persist.img
Click to expand...
Click to collapse
Can you help me how to flash this file..??
Because the non-hlos.bin is of 100 mb while in stock ROM it is of around 75 mb,
So can you describe the method to restore this.
1. my device is xt1686 retin and i lost my imei and volte after reverting back to twrp flashable stock nov security patch from pixel experience oreo rom ....
2. i recovered my imei using #castell93 guide ....
https://forum.xda-developers.com/g5-plus/help/restore-imei-0-moto-g5-xt1687-t3739808
3. then i flashed twrp flashable stock jan security patch but no volte yet....
4. then i got my volte back thanks to akshu2697 guide... and backed up my efs
https://forum.xda-developers.com/g5-plus/how-to/solved-volte-fix-lost-flashing-stock-rom-t3773524
5. for a while i used custom oreo roms... and today i flashed twrp flashable stock jan security patch again and i lost imei =0 .... i have my efs backup so i recovered my efs and got my imei and volte working again..
6. today i downloaded #rachitrawat's twrp system backup file and formatted every thing using twrp and restored the system file and reboot... now i am on stock march security patch and i didnot loose my imei and volte .....
I'm on an oreo rom(no volte). Will i be able to flash stock when the oreo rom is officially released? And hopefully get volte?
Arunxyz said:
1. my device is xt1686 retin and i lost my imei and volte after reverting back to twrp flashable stock nov security patch from pixel experience oreo rom ....
2. i recovered my imei using #castell93 guide ....
https://forum.xda-developers.com/g5-plus/help/restore-imei-0-moto-g5-xt1687-t3739808
3. then i flashed twrp flashable stock jan security patch but no volte yet....
4. then i got my volte back thanks to akshu2697 guide... and backed up my efs
https://forum.xda-developers.com/g5-plus/how-to/solved-volte-fix-lost-flashing-stock-rom-t3773524
5. for a while i used custom oreo roms... and today i flashed twrp flashable stock jan security patch again and i lost imei =0 .... i have my efs backup so i recovered my efs and got my imei and volte working again..
6. today i downloaded #rachitrawat's twrp system backup file and formatted every thing using twrp and restored the system file and reboot... now i am on stock march security patch and i didnot loose my imei and volte .....
Click to expand...
Click to collapse
Which system backup did you restore.???
There are two system backup zip in that folder.
And what if you again flash system with fastboot after restore that backup.????
Is IMEI still there.??
akshu2697 said:
Which system backup did you restore.???
There are two system backup zip in that folder.
And what if you again flash system with fastboot after restore that backup.????
Is IMEI still there.??
Click to expand...
Click to collapse
Extract twrp backup system img zip file and it contains system_img folder...
Copy that folder to twrp backup and then restore...
After restore you don't need to fastboot system..
I didn't try to flash fastboot system
Arunxyz said:
Extract twrp backup system img zip file and it contains system_img folder...
Copy that folder to twrp backup and then restore...
After restore you don't need to fastboot system..
I didn't try to flash fastboot system
Click to expand...
Click to collapse
What if you fastboot flashing and again IMEI goes to 0,..??
Can you try.?
Either flashing system via fastboot or flashing stock ROM with twrp.
akshu2697 said:
Can you help me how to flash this file..??
Because the non-hlos.bin is of 100 mb while in stock ROM it is of around 75 mb,
So can you describe the method to restore this.
Click to expand...
Click to collapse
Code:
fastboot flash modem NON-HLOS.bin
akshu2697 said:
Which system backup did you restore.???
There are two system backup zip in that folder.
And what if you again flash system with fastboot after restore that backup.????
Is IMEI still there.??
Click to expand...
Click to collapse
system.img is a bit perfect backup of /system which will not break dm-verity.
akshu2697 said:
What if you fastboot flashing and again IMEI goes to 0,..??
Can you try.?
Either flashing system via fastboot or flashing stock ROM with twrp.
Click to expand...
Click to collapse
you can restore via twrp or fastboot flash
Edit: fastboot won't work. Need to compress into sparse chunks. Try motofastboot