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??
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
Hello everyone, i installed the leaked soak test with the "apply update from SD card" on stock recovery after locking my bootloader.
One week later, i unlocked it again and flashed TWRP for rooting with magisk.
Even with root tweaks i still face problems with soak 8.1, due to the lack of custom kernels.
So i decided to flash Stock N (1st April) with the TWRP Flashable zip from @Jleeblanch , how i avoid IMEI loss doing that? If i backup Oreo's EFS with TWRP, it will be compatible if i try to restore it after flashing, or it's not even necessary?
The TWRP flashable zip files by @Jleeblanch does not have the commands "fastboot erase modemst1" and "fastboot erase modemst2" so your IMEI will be fine. However Stock Oreo does mess up with IMEI.
Flash TWRP flashable Stock Nougat by Jleeblanch. You will not lose IMEI, but there will still be a problem of persist (i.e you will lost IMEI if you flash Stock ROM via fastboot). So to fix persist, follow this thread: [Guide] [XT16XX] [Solve] Moto G4/Plus IMEI=0 issue
Losing IMEI is a persist related problem (Soak Test 8.1, and all 64bit Pie ROMs are causing this). So if you fix persist, then you will never lose IMEI.
I recommend you to take backup of EFS before this process (i.e while having a bad persist and working EFS) and also after fixing persist (i.e while having a good persist and working EFS).
EFS backup by Lyuu's TWRP takes a backup of EFS, fsg and persist.
Since you upgraded to Soak test from a locked bootloader, I strongly oppose moving back to Stock Nougat. Even if you go back to Nougat, MAKE SURE THAT YOU NEVER DO ANY OTA UPDATE. Whenever Official Oreo comes out, either flash it by fastboot or by TWRP flashable zip file (Jleeblanch said that he will make one for Official Oreo too once it's released)
Heeth21 said:
The TWRP flashable zip files by @Jleeblanch does not have the commands "fastboot erase modemst1" and "fastboot erase modemst2" so your IMEI will be fine. However Stock Oreo does mess up with IMEI.
Flash TWRP flashable Stock Nougat by Jleeblanch. You will not lose IMEI, but there will still be a problem of persist (i.e you will lost IMEI if you flash Stock ROM via fastboot). So to fix persist, follow this thread: [Guide] [XT16XX] [Solve] Moto G4/Plus IMEI=0 issue
Losing IMEI is a persist related problem (Soak Test 8.1, and all 64bit Pie ROMs are causing this). So if you fix persist, then you will never lose IMEI.
I recommend you to take backup of EFS before this process (i.e while having a bad persist and working EFS) and also after fixing persist (i.e while having a good persist and working EFS).
EFS backup by Lyuu's TWRP takes a backup of EFS, fsg and persist.
Since you upgraded to Soak test from a locked bootloader, I strongly oppose moving back to Stock Nougat.
Click to expand...
Click to collapse
Rajat's 64bit TWRP doesn't have EFS Backup option here. I will try Lyuu's
Thanks for the help.
xSamukaBRx said:
Rajat's 64bit TWRP doesn't have EFS Backup option here. I will try Lyuu's
Thanks for the help.
Click to expand...
Click to collapse
Read the second post again, I have edited it.
Heeth21 said:
Since you upgraded to Soak test from a locked bootloader, I strongly oppose moving back to Stock Nougat. Even if you go back to Nougat, MAKE SURE THAT YOU NEVER DO ANY OTA UPDATE. Whenever Official Oreo comes out, either flash it by fastboot or by TWRP flashable zip file (Jleeblanch said that he will make one for Official Oreo too once it's released)
Click to expand...
Click to collapse
I kinda fear it auto-updating, so i'll make sure to delete the "3c_ota" app from /priv-app
EDIT: Already know the risks of taking OTA with unlocked bootloader or after downgrade...
Heeth21 said:
Since you upgraded to Soak test from a locked bootloader, I strongly oppose moving back to Stock Nougat. Even if you go back to Nougat, MAKE SURE THAT YOU NEVER DO ANY OTA UPDATE. Whenever Official Oreo comes out, either flash it by fastboot or by TWRP flashable zip file (Jleeblanch said that he will make one for Official Oreo too once it's released)
Click to expand...
Click to collapse
What about Lineage-based 7.1.2 32 bits ROMs? Can i flash them without issue? Already flashed Stock N
with TWRP, and It worked fine. Just want to know.
Please don't tell me i need the fastboot Stock N, i can't flash that anymore i think. :crying:
xSamukaBRx said:
What about Lineage-based 7.1.2 32 bits ROMs? Can i flash them without issue? Already flashed Stock N
with TWRP, and It worked fine. Just want to know.
Please don't tell me i need the fastboot Stock N, i can't flash that anymore i think. :crying:
Click to expand...
Click to collapse
Yes you can flash Custom ROMs from TWRP, however, I don't think you should right now.
I got my device hard bricked randomly from Custom ROM. idk what caused it, maybe some changes which I did or something else. If a similar thing were to happen with you, there's no guarantee whether the current blankflash would work or not.
Heeth21 said:
Yes you can flash Custom ROMs from TWRP, however, I don't think you should right now.
I got my device hard bricked randomly from Custom ROM. idk what caused it, maybe some changes which I did or something else. If a similar thing were to happen with you, there's no guarantee whether the current blankflash would work or not.
Click to expand...
Click to collapse
Even through i just want a pure lineage OS instead of a custom based on it (too many stuff comes with a risk, right?), i better not try...
hi all, as people are posting tutorial to downgrade from pie to oreo with the help of restoring boot and efs folder uploaded by them,, is it safe to restore from someone's else twrp backup i mean efs folder??
as per my knowledge efs is backup of imei right?
so restoring from someone's else efs won't affect mine imei?
No help here?
??????????????????????????????/
i don't think so people are helpful here or either not expert as nobody is replying lol
No idea. Sorry
taran181 said:
hi all, as people are posting tutorial to downgrade from pie to oreo with the help of restoring boot and efs folder uploaded by them,, is it safe to restore from someone's else twrp backup i mean efs folder??
as per my knowledge efs is backup of imei right?
so restoring from someone's else efs won't affect mine imei?
Click to expand...
Click to collapse
4-6 months back there was thread why we should not restore efs of someone & proper tutorial for people who messed up their mac address with some kernel.
Now this tutorial on downgrading pie to oreo. I have no idea. Someone's efs would mess your IMEI, wifi mac, Bluetooth mac, thats what i think. But there are tutorial how to edit imei using some Qualcomm tool.
Ask @CosmicDan. He's the expert.
Just flash Oreo on fastboot, with full wipe. Why doesn't that work?
I was having an issue since using custom rom with december fw btw.
and I was mistaken flashing november fw back to solve some calling issue, so I ended up with no signal which should be came from I didn't restore dev's efs backup.
So I start from flashing full clean stock november and ended with bootloop on it, which is something I still curious what cause it.
At that times, I'm on locked bootloader and can't even enter edl to reflash the rom and can't unlock bootloader since the rom still not booting to enable oem unlocking option.
I don't remember what I have done to it, but at times my phone can boot with no signal, 0 imei on sim1 and null on sim2.
So I start to rewrite the imei then everything is back to normal.
Downgraded using the method of restoring boot and efs... Nothing changed for me, imei is the same as in the box of my mi a1. ? Maybe people did something before doing the downgrade that messed up something.
CosmicDan said:
Just flash Oreo on fastboot, with full wipe. Why doesn't that work?
Click to expand...
Click to collapse
@CosmicDan no flashing just oreo doesn't help, phone gets stuck in bootloop, so people has posted tutorial about flashing their efs and boot etc through twrp to get out of bootloop.
Eg: https://forum.xda-developers.com/mi-a1/how-to/tutorial-downgrade-9-0-to-8-1-edl-imei-t3879624
fhsd22 said:
Downgraded using the method of restoring boot and efs... Nothing changed for me, imei is the same as in the box of my mi a1. ? Maybe people did something before doing the downgrade that messed up something.
Click to expand...
Click to collapse
but my question why use someone's else efs while downgrading, as efs contains imei and modem backup ..
taran181 said:
@CosmicDan no flashing just oreo doesn't help, phone gets stuck in bootloop, so people has posted tutorial about flashing their efs and boot etc through twrp to get out of bootloop.
Eg: https://forum.xda-developers.com/mi-a1/how-to/tutorial-downgrade-9-0-to-8-1-edl-imei-t3879624
Click to expand...
Click to collapse
Well you can try it I guess, just backup the EFS partition and other stuff with my backup tool and you can always go back if worse comes to worst.
CosmicDan said:
Just flash Oreo on fastboot, with full wipe. Why doesn't that work?
Click to expand...
Click to collapse
Xiaomi put out a message on their forum that after the Pie update, the phone should not be rolled back. Its for all Android one models. When users flash an older roms, bootloops occur.
https://www.fonearena.com/blog/271177/xiaomi-pie-oreo-downgrading-disabled-android-one-devices.html
taran181 said:
but my question why use someone's else efs while downgrading, as efs contains imei and modem backup ..
Click to expand...
Click to collapse
But what he is saying is that he did downgrade EFS, but IMEI didn't change. This suggests that EFS isn't the original source of IMEI after all. Or maybe the bootloader can re-write IMEI and stuff on boot, who knows... Surely others have actually confirmed that EFS cross-flash = IMEI change, right? Not just assumed?
...point is, you can backup your EFS via EDL mode so there should be no risk. If you made a full EDL backup of your own device when you were still on Oreo then you would be golden, as EDL has full access to all partitions.