Related
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.
Hi, I'm receiving OTA updates, official software, oem locked. I had previously installed a lot of roms on this phone, rooted, etc, and once I flashed stock rom with moto g5 plus toolkit it killed my phone, or did it. It's pretty complex.
So right along the time this happened, I gave my imei to a verizon rep, he verified my phone was compatbile with verizon network, sent a verizon prepaid sim out (i'm switching to 40 plan from redpocket to verizon prepaid) the sim is still in the mail. Along this time I also was on lineage os from vache, 8.1 But I didn't like it so I reflashed stock rom with moto g5 plus toolkit, (google it)
So. it was PRECISELY after I re-flashed stock rom that no sim card worked. I immediately assumed it was verizon's fault, they must have locked my phone to their network, right? But then I dialed *#06# on my dialer and my IMEI showed up as ZERO. I talked in android discord, and was told I must have deleted EFS whatever that is.
So, I'm stuck. I have an imei that's zero, no sim card will work on this phone, i'm oem locked and receiving ota updates and official software status via fastboot. android security patch november 1, 2017 and build number = npn25.137-92
I did call Verizon to make sure they weren't causing the issue, but the rep was confused. My phone was showing up as an x1 or something on his screen, but he said I "can't use any other carriers/sims" until i "activate the verizon sim they shipped me" but then this information was falsified by the verizon folks at reddit, who said the rep didn't know what he was talking about.
So I'm thinking this issue is being caused by the stock rom I flashed, NOT verizon. Let me know, I was previously on Redpocket.
Either way, no sim will work right now, I called motorola support, they said they can only send me a new phone for $150, as flashing rom voids warranty, so my phone is essentially a wifi only device without cellular capabilities.
I am stumped as what to do. this is US NA moto g5 plus, again, official software status, oem locked. If someone could help me get my celullar back and identify WHAT CAUSED THIS, I would be eternally grateful. Again, I didn't do anything but erase everything in TWRP (data, cache, etc) and REFLASH stock rom, downloaded from moto g5 plus toolkit link. So HOW could I have deleted my EFS folder? It just doesn't make sense. So I'm debating after all, maybe it is Verizon messing up my phone?
beatlesfan5858 said:
Hi, I'm receiving OTA updates, official software, oem locked. I had previously installed a lot of roms on this phone, rooted, etc, and once I flashed stock rom with moto g5 plus toolkit it killed my phone, or did it. It's pretty complex.
So right along the time this happened, I gave my imei to a verizon rep, he verified my phone was compatbile with verizon network, sent a verizon prepaid sim out (i'm switching to 40 plan from redpocket to verizon prepaid) the sim is still in the mail. Along this time I also was on lineage os from vache, 8.1 But I didn't like it so I reflashed stock rom with moto g5 plus toolkit, (google it)
So. it was PRECISELY after I re-flashed stock rom that no sim card worked. I immediately assumed it was verizon's fault, they must have locked my phone to their network, right? But then I dialed *#06# on my dialer and my IMEI showed up as ZERO. I talked in android discord, and was told I must have deleted EFS whatever that is.
So, I'm stuck. I have an imei that's zero, no sim card will work on this phone, i'm oem locked and receiving ota updates and official software status via fastboot. android security patch november 1, 2017 and build number = npn25.137-92
I did call Verizon to make sure they weren't causing the issue, but the rep was confused. My phone was showing up as an x1 or something on his screen, but he said I "can't use any other carriers/sims" until i "activate the verizon sim they shipped me" but then this information was falsified by the verizon folks at reddit, who said the rep didn't know what he was talking about.
So I'm thinking this issue is being caused by the stock rom I flashed, NOT verizon. Let me know, I was previously on Redpocket.
Either way, no sim will work right now, I called motorola support, they said they can only send me a new phone for $150, as flashing rom voids warranty, so my phone is essentially a wifi only device without cellular capabilities.
I am stumped as what to do. this is US NA moto g5 plus, again, official software status, oem locked. If someone could help me get my celullar back and identify WHAT CAUSED THIS, I would be eternally grateful. Again, I didn't do anything but erase everything in TWRP (data, cache, etc) and REFLASH stock rom, downloaded from moto g5 plus toolkit link. So HOW could I have deleted my EFS folder? It just doesn't make sense. So I'm debating after all, maybe it is Verizon messing up my phone?
Click to expand...
Click to collapse
bro never use toolkit again to flash stock use fastboot instead there is no problem with your device now what you will do is unlock your bootloader with the code u received from moto and after that wipe everything in twrp check if in bootloader your baseband is showing some version then if it shows no problem now flash any 64bit oreo custom rom nos,validus,pe ur wish then reboot to bootloader now type the commands fastboot erase modemst1 ,fastboot erase modemst2 then boot into custom rom you installed now you will have signal,then again boot into twrp recovery and backup efs and store it on pc or cloud ur choice, now you can use any custom rom with signal without any hassle and if you want to move to stock while flashing stock rom skip fastboot erase modemst1 ,fastboot erase modemst2 commands you boot into rom it should have signal if you dont get signal flash twrp then restore your oreo efs backup you will surely get back your signal but no volte sadly for now.
after stock oreo release flash it may be everything will be normal again.
i wish you good luck.
Rakesh1b said:
bro never use toolkit again to flash stock use fastboot instead there is no problem with your device now what you will do is unlock your bootloader with the code u received from moto and after that wipe everything in twrp check if in bootloader your baseband is showing some version then if it shows no problem now flash any 64bit oreo custom rom nos,validus,pe ur wish then reboot to bootloader now type the commands fastboot erase modemst1 ,fastboot erase modemst2 then boot into custom rom you installed now you will have signal,then again boot into twrp recovery and backup efs and store it on pc or cloud ur choice, now you can use any custom rom with signal without any hassle and if you want to move to stock while flashing stock rom skip fastboot erase modemst1 ,fastboot erase modemst2 commands you boot into rom it should have signal if you dont get signal flash twrp then restore your oreo efs backup you will surely get back your signal but no volte sadly for now.
after stock oreo release flash it may be everything will be normal again.
i wish you good luck.
Click to expand...
Click to collapse
Thanks so much for replying I will try exactly everything you said
beatlesfan5858 said:
Thanks so much for replying I will try exactly everything you said
Click to expand...
Click to collapse
bro 1 advice dont ever use toolkit to flash stock use fastboot its the best secure way.
Rakesh1b said:
bro 1 advice dont ever use toolkit to flash stock use fastboot its the best secure way.
Click to expand...
Click to collapse
Hi which rom would you recommend? i try downloading validus and pixel experience, but the zip files extract to cpgz files, I can't get the actual files. I need flashable rom
beatlesfan5858 said:
Hi which rom would you recommend? i try downloading validus and pixel experience, but the zip files extract to cpgz files, I can't get the actual files. I need flashable rom
Click to expand...
Click to collapse
i will give u the link
---------- Post added at 04:22 AM ---------- Previous post was at 04:16 AM ----------
Rakesh1b said:
i will give u the link
Click to expand...
Click to collapse
https://androidfilehost.com/?fid=746010030569952670
---------- Post added at 04:23 AM ---------- Previous post was at 04:22 AM ----------
Rakesh1b said:
i will give u the link
Click to expand...
Click to collapse
https://androidfilehost.com/?fid=746010030569952670
thank you Rakesh, I'm downloading it now, I will update you to let you know if it works. I just want my phone back
what are instructions to flash this rom?
beatlesfan5858 said:
what are instructions to flash this rom?
Click to expand...
Click to collapse
bro just flash that rom then boot into bootloader then type these 2 fastboot commands and enter after every command
fastboot erase modemst1
fastboot erase modemst2
then boot into custom oreo you will have your imei back now you will have imei with any custom rom but if you want to go to stock then backup your efs from twrp menu and store the files inside your backup folder on potter that shows up in your computer when connected to pc it will have a folder with z******** some serial no and in it you will have 4 files but save only 3 files leave recovery log file and save them to pc and now you can fastboot flash stock rom now what the problem here is it cant detect imei on nougat stock so after flashing fastboot rom you flash twrp recovery and then backup efs then it will create a folder efs backup on you potter then move the previous 3 efs backup files to the backup directory where there will be 4 files same as before and now restoree that backup and you can boot into stock rom it will have imei.
I figured it out thanks.
beatlesfan5858 said:
I don't know how to flash the rom bro I just got a bunch of files, I have fastboot
Click to expand...
Click to collapse
follow this guide bro if you want to fastboot flash stock rom https://forum.xda-developers.com/g5-plus/development/stock-firmware-npn25-137-67-5-fastboot-t3694738
Rakesh1b said:
follow this guide bro if you want to fastboot flash stock rom https://forum.xda-developers.com/g5-plus/development/stock-firmware-npn25-137-67-5-fastboot-t3694738
Click to expand...
Click to collapse
I'm trying to flash the validus zip you gave. I put it on an sd card and tried flashing it with twrp but it gave me error code 255
beatlesfan5858 said:
I'm trying to flash the validus zip you gave. I put it on an sd card and tried flashing it with twrp but it gave me error code 255
Click to expand...
Click to collapse
bro first wipe everything off your potter if you dont have any important data on it i mean clean flash take out your sd card and now select advanced wipe>select all options>wipe one by one
format potter using format option now copy validus zip to your potter internal storage it will show up when connected to pc then select installl in twrp then swipe to flash it should flash well then wipe dalvik cache then boot to bpootloader try those 2 commands then you boot to rom it will have signal bro. try it
Bro I did exactly what you said, copied Validus zip to internal, removed sd card and erased everything in twrp. It's still giving me error code 255 when I try to flash the Validus zip.
beatlesfan5858 said:
Bro I did exactly what you said, copied Validus zip to internal, removed sd card and erased everything in twrp. It's still giving me error code 255 when I try to flash the Validus zip.
Click to expand...
Click to collapse
bro wipe everything of ur device and try format then factory reset and then reboot to recovery again then try to flash the rom again
---------- Post added at 05:01 AM ---------- Previous post was at 04:58 AM ----------
Rakesh1b said:
bro wipe everything of ur device and try format then factory reset and then reboot to recovery again then try to flash the rom again
Click to expand...
Click to collapse
try this twrp it need s64bit supported twrp to flash that rom try this twrp flash this recovery then format then try to flash https://dl.twrp.me/potter/twrp-3.2.1-0-potter.img.html
---------- Post added at 05:02 AM ---------- Previous post was at 05:01 AM ----------
Rakesh1b said:
bro wipe everything of ur device and try format then factory reset and then reboot to recovery again then try to flash the rom again
Click to expand...
Click to collapse
try this twrp it need s64bit supported twrp to flash that rom try this twrp flash this recovery then format then try to flash https://dl.twrp.me/potter/twrp-3.2.1-0-potter.img.html
Thanks bro, much love, that was it. I can finally flash the rom. I'll flash it, and then try your next steps to get signal. Thanks again I really appreciate it.
What's the best way to backup EFS?
beatlesfan5858 said:
Thanks bro, much love, that was it. I can finally flash the rom. I'll flash it, and then try your next steps to get signal. Thanks again I really appreciate it.
Click to expand...
Click to collapse
good luck. stay safe with efs always.
Rakesh1b said:
good luck. stay safe with efs always.
Click to expand...
Click to collapse
I got signal much love bro, you really saved my day!
Rakesh1b said:
good luck. stay safe with efs always.
Click to expand...
Click to collapse
boot into oreo rom once you have signal then go to twrp then>backup >swpie to backup>it will save 4 backup files in internal memory twrp backup folder copy that whole folder and keep it safe when ever you loose signal just backupefs again in new rom then it will create backup folder then replace that backup folder with this oreo efs backup you can get back signa then.
is it working now having signal?
---------- Post added at 05:16 AM ---------- Previous post was at 05:15 AM ----------
Rakesh1b said:
boot into oreo rom once you have signal then go to twrp then>backup >swpie to backup>it will save 4 backup files in internal memory twrp backup folder copy that whole folder and keep it safe when ever you loose signal just backupefs again in new rom then it will create backup folder then replace that backup folder with this oreo efs backup you can get back signa then.
is it working now having signal?
Click to expand...
Click to collapse
once oreorom stock comes you willbe good to go and everything will be normal.
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
Like many people who have lost IMEI after flashing Oreo ROM and reverting to stock, I too have run into the same issue. I've managed to get my IMEI back and now have a working EFS backup. I've also got my VoLTE fixed using the VoLTE fix thread.
The problem I'm running into now is that the OTA updates from motorola keep breaking my IMEI. So every time I install an OTA, my IMEI becomes 0 afterwards. I then have to install TWRP and restore my EFS+persist backup to get my IMEI back. But this essentially prevents me from installing the next OTA update.
Has anyone found a way to install the OTA update without losing IMEI? Any help would be much appreciated!
I've thought of possible solution but I'm not sure if it will work. If someone could tell me if this will work, that would be great!
1. Using Partition Backup app from playstore, backup Modem, Modemst1, Modemst2 and persist on working stock ROM
2. Do a fresh install of stock ROM via fastboot and install OTA
3. Use Magisk to patch boot image and flash the image from fastboot
4. Re install Partition Backup from playstore, grant root access and restore the partition backup to get IMEI back?
This way you can restore the stock boot image and install next OTA all without installing and decrypting your storage with twrp.
PLEASE
please share the EFS folder:good::good:
Another users EFS paritition won't help you and sharing is not allowed on XDA, this has been addressed multiple times since there are over a dozen threads about the the same damn thing.
THE REAL FIX:
Accept that you made a mistake cause you didn't keep a secure backup of your original firmware, and let it be a learning experience in the future. Some users are in worst situations following some of these half-cocked fixes.
Randumb_User said:
Another users EFS paritition won't help you and sharing is not allowed on XDA, this has been addressed multiple times since there are over a dozen threads about the the same damn thing.
THE REAL FIX:
Accept that you made a mistake cause you didn't keep a secure backup of your original firmware, and let it be a learning experience in the future. Some users are in worst situations following some of these half-cocked fixes.
Click to expand...
Click to collapse
No....we did not make mistakes actually. Many things have been borked by Oreo development, I did nothing to lose my Imei other than flash 64bit Roms, keeping a secure backup of stock firmware would not restore your imei, if so, so would flashing via fastboot your original stock firmware.
Ok so I've been analyzing the app "Partition Backup" on the play store and it seems that you can also flash your backed up partition through fastboot. So if you back up those partitions, you can restore them through fastboot even without the app (As long as you backup the partition in the .img format). I haven't tried any of this yet so I'm not sure if it will work.
smartish123 said:
Ok so I've been analyzing the app "Partition Backup" on the play store and it seems that you can also flash your backed up partition through fastboot. So if you back up those partitions, you can restore them through fastboot even without the app (As long as you backup the partition in the .img format). I haven't tried any of this yet so I'm not sure if it will work.
Click to expand...
Click to collapse
Best way to back up partitions is to use ADB
Code:
ls -al /dev/block/platform/soc/7824900.sdhci/by-name
which will give you a list of all partitions by name and their starting addresses. Then ADB shell and dd command, for instance for persist
Code:
dd if=/dev/block/mmcblk0p30 of=/external_sd/persist.img
This backs up that partition to your external sd card. To restore/write it
Code:
dd if=/external_sd/persist.img of=/dev/block/mmcblk0p30
Of course you would do this for each partition you want to back up.
[email protected] said:
Best way to back up partitions is to use ADB
Code:
ls -al /dev/block/platform/soc/7824900.sdhci/by-name
which will give you a list of all partitions by name and their starting addresses. Then ADB shell and dd command, for instance for persist
Code:
dd if=/dev/block/mmcblk0p30 of=/external_sd/persist.img
This backs up that partition to your external sd card. To restore/write it
Code:
dd if=/external_sd/persist.img of=/dev/block/mmcblk0p30
Of course you would do this for each partition you want to back up.
Click to expand...
Click to collapse
Do you need to have root installed to run those commands through adb? What I'm planning on doing is to unroot my device and go to pure stock. I want to be able to restore my modem partitions when I install an OTA (which will probably break my IMEI).
UPDATE
I tried flashing the backed up image of modemst1 i got from the app through fastboot. It failed saying "flash permission denied"
Code:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:modemst1: not found
target reported max download size of 536870912 bytes
sending 'modemst1' (2048 KB)...
OKAY [ 0.076s]
writing 'modemst1'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.101s
How to get back imie...??? Please help
madhu kumaraaa said:
How to get back imie...??? Please help
Click to expand...
Click to collapse
Try this thread
https://forum.xda-developers.com/g5-plus/help/restore-imei-0-moto-g5-xt1687-t3739808
Try this.
1-Pixel Experience workaround (Flash PE, don't turn on wifi, get to home screen, reboot to bootloader, run fastboot erase modemst1 and fastboot modemst2, let phone reboot, confirm network.)
2-Lock Bootloader (If the last OTA you got was 9x-8 you're in a tight spot til firmware is available. If it was -4, you're good.)
3-Flash Full Firmware (but not fastboot erase modemst1 and modemst1. Keep as-is)
4-Install and Flash OTA
I can make absolutely no promises it will work for you. But I was dealing with IMEI 0, and now my bootloader is locked, on Stock, OTA installed with IMEI. I've had the phone return IMEI 0 after OTA updates before this. I can't confirm LTE/voLTE connectivity, not much data in the first place cause I don't need it.
If it doesn't work. Try again but do this first. I dunno if it's redundant or not. I can't test further and I'm leaving this phone alone now.
--When I was messing with my phone while doing this. I ****ed up the first time and only did 1- and 3-. I ran the above steps after phone as on the home screen and not enabling wifi
For reference. I don't have an EFS backup and I never messed with persist.
Randumb_User said:
Try this.
1-Pixel Experience workaround (Flash PE, don't turn on wifi, get to home screen, reboot to bootloader, run fastboot erase modemst1 and fastboot modemst2, let phone reboot, confirm network.)
2-Lock Bootloader (If the last OTA you got was 9x-8 you're in a tight spot til firmware is available. If it was -4, you're good.)
3-Flash Full Firmware (but not fastboot erase modemst1 and modemst1. Keep as-is)
4-Install and Flash OTA
I can make absolutely no promises it will work for you. But I was dealing with IMEI 0, and now my bootloader is locked, on Stock, OTA installed with IMEI. I've had the phone return IMEI 0 after OTA updates before this. I can't confirm LTE/voLTE connectivity, not much data in the first place cause I don't need it.
If it doesn't work. Try again but do this first. I dunno if it's redundant or not. I can't test further and I'm leaving this phone alone now.
--When I was messing with my phone while doing this. I ****ed up the first time and only did 1- and 3-. I ran the above steps after phone as on the home screen and not enabling wifi
For reference. I don't have an EFS backup and I never messed with persist.
Click to expand...
Click to collapse
So just to clarify (I understand that this may not work for me):
After following the above steps, you were able to have a working IMEI and you were able to install an OTA update without having your IMEI go to 0 correct?
Also on step 4, when you say "Install and Flash OTA" do you mean you proceed to install the OTA normally (as in you click the install button in Stock and your phone reboots and installs it)?
smartish123 said:
So just to clarify (I understand that this may not work for me):
After following the above steps, you were able to have a working IMEI and you were able to install an OTA update without having your IMEI go to 0 correct?
Also on step 4, when you say "Install and Flash OTA" do you mean you proceed to install the OTA normally (as in you click the install button in Stock and your phone reboots and installs it)?
Click to expand...
Click to collapse
Correct and correct, I'm a ****show when it comes to explaining things.
I'm still not sure what's gonna happen after a factory reset. The reluctance is overwhelming.
Did anyone else have any luck?
If anyone manages to get thier IMEI at any point I'd suggest Unlocking/TWRP to make an EFS backup. First thing I did after rooting again. Then I got stuck on the logo, had to flash 93-4 and....IMEI 0. EFS backup worked proper and restored it just fine. I could wipe data in TWRP without losing IMEI.
Gonna avoid custom ROMs. Stick with Stock+ElementalX+Magisk.
What a fun device....
Here's some probable good news: https://www.xda-developers.com/google-require-oem-regular-security-patches/
Randumb_User said:
Did anyone else have any luck?
If anyone manages to get thier IMEI at any point I'd suggest Unlocking/TWRP to make an EFS backup. First thing I did after rooting again. Then I got stuck on the logo, had to flash 93-4 and....IMEI 0. EFS backup worked proper and restored it just fine. I could wipe data in TWRP without losing IMEI.
Gonna avoid custom ROMs. Stick with Stock+ElementalX+Magisk.
What a fun device....
Here's some probable good news: https://www.xda-developers.com/google-require-oem-regular-security-patches/
Click to expand...
Click to collapse
Yea as of now, no one has been able to figure out how to apply OTA without losing imei. However someone has managed to figure out how to apply an OTA using the firmware files without losing imei.
https://forum.xda-developers.com/g5-plus/help/restore-imei-0-moto-g5-xt1687-t3739808/post76468866
The only drawback with this method is that you need have the firmware zip of the OTA.
smartish123 said:
Yea as of now, no one has been able to figure out how to apply OTA without losing imei. However someone has managed to figure out how to apply an OTA using the firmware files without losing imei.
https://forum.xda-developers.com/g5-plus/help/restore-imei-0-moto-g5-xt1687-t3739808/post76468866
The only drawback with this method is that you need have the firmware zip of the OTA.
Click to expand...
Click to collapse
I have used OTA to update to 93-8 and the other day 93-10 (For XT1687 retus) without losing IMEI, it's an anomaly to me. Prior to that I was dealing with the same OTA updates reverting back to IMEI 0. I'm not trying to gloat or anything, I've been hoping at least one person managed the same outcome. It's a really $h!t situation for a lot of people.
Randumb_User said:
I have used OTA to update to 93-8 and the other day 93-10 (For XT1687 retus) without losing IMEI, it's an anomaly to me. Prior to that I was dealing with the same OTA updates reverting back to IMEI 0. I'm not trying to gloat or anything, I've been hoping at least one person managed the same outcome. It's a really $h!t situation for a lot of people.
Click to expand...
Click to collapse
What sucks so much is how random things are with this device. For example, a month ago I fastbooted one of the firmwares and my imei was there(was 0 before flashing). After that flashing an Oreo rom, my imei was 0. Going back and repeating the process, flashing same firmware, imei 0 still?????. So damn random. If only we had a safe way to manually insert our imei. Let's just hope the problems do not multiply when we get 32bit official Oreo .
Cupcake 1.5 said:
What sucks so much is how random things are with this device. For example, a month ago I fastbooted one of the firmwares and my imei was there(was 0 before flashing). After that flashing an Oreo rom, my imei was 0. Going back and repeating the process, flashing same firmware, imei 0 still?????. So damn random. If only we had a safe way to manually insert our imei. Let's just hope the problems do not multiply when we get 32bit official Oreo .
Click to expand...
Click to collapse
I've been doing a lot of thinking and I came up with this idea on how to install OTA safely without losing imei.
Essentially, the main goal is to be able to install the OTA and then restore a backup of your modemst1 and modemst2 partitions. You need to be able to do this without installing TWRP, since it will decrypt your data partition. The only way I can think of doing this is through backing up and restoring your modemst1 and modemst2 partitions through ADB, which unfortunately requires root. Using some logic, we can see that in order to do this you need to preserve root without installing it through TWRP. I'm proposing that if you can use magisk manager (the apk one) and use it create a patched boot.img (which can be obtained via any firmware zip) with root access , you can flash this patched boot.img in fastboot and obtain root access WITHOUT having to use TWRP. So whenever you install an OTA, you can restore the original boot.img through fastboot, install the OTA, restore patched boot.img, and use root access to restore modemst1 and modemst2 backups via ADB.
UPDATE
I came up with a better idea. It seems it is possible to boot into twrp without having to flash it on your phone via
fastboot boot twrp.img
If this works, you can restore an EFS backup everytime you install an OTA since your stock recovery remains intact.
I haven't tried any of this yet. It would be amazing if you guys could give me your opinions about this. I'd be happy to clarify any of this for you guys.
My G5 Plus was stolen and it's now someone's problem other than mine. Good luck to them. I've inherited a OnePlus X.
Farewell folks.
smartish123 said:
UPDATE
I came up with a better idea. It seems it is possible to boot into twrp without having to flash it on your phone via
fastboot boot twrp.img
If this works, you can restore an EFS backup everytime you install an OTA since your stock recovery remains intact.
I haven't tried any of this yet. It would be amazing if you guys could give me your opinions about this. I'd be happy to clarify any of this for you guys.
Click to expand...
Click to collapse
This doesn't work, I just tried it. You can of course restore EFS this way but the next OTA will not work, you get the "Error!" message.
fivefour said:
This doesn't work, I just tried it. You can of course restore EFS this way but the next OTA will not work, you get the "Error!" message.
Click to expand...
Click to collapse
Drat. This means that whatever efs we are using to recover our imei is tampered. I don't know how to fix that.