Database Users

SOLVED: Flashed TruPureXMM rom in Indian dualsim XT1572 and now No sim detection

I was on indian_mm_deodexed_rooted then flashed TruPureXMM as one of my friends suggested trying it out as it is smooth etc.
I didn't knew that it is Pure single sim version and after flashing no network and then i checked only single sim showed :crying: then i again formated and flashed back indian_mm_deodexed_rooted and modem_indian_mm_fixed but this time it shows two sims with no network atall and Emergency calls on both... In settings SIM cards its SIM 1 emty and SIM 2 empty :crying::crying: tried flashing with indian modem again and also tried lp modem but nothing is working, please help :crying::crying:
Both IMEI Unknown status.
I didn't even took back of my stock as i didn't knew about it before
Bootloader is unlocked and TWRP is installed.
Note: My x style came with lollipop and then i did official update with marshmallow and then i wanted to root so flashed.
Please help me get back dual sim with network if possible
EDIT: Solved the issue now and here is the solution:
Download Stockrom from this link according to your exact model and follow the commands exactly:
[Firmware] Moto X Style/Pure Stock Software by lAndroXl
I just ignored command fastboot oem lock begin as told by @dj_ooms so boot loader is still unlocked and also i have installed TWRP and rooted by flashing SuperSu.
Also very important thing is take nandroid backup after installing TWRP i.e backup your stock rom by selecting backup in TWRP... please also take backup your EFS partition also, thanks
@dj_ooms @Unicornzz and @bw03
:angel: Thank you guys for your valuable replies and thanks to lAndroXl uploader and thread... really helped :angel:

Use the ROM from here.
http://forum.xda-developers.com/moto-x-style/development/rom-indian-marshmallow-variants-t3253684
Edit: you may get the modem working with just flashing the modem zip but I'm not sure as I don't have a dual sim phone to try. You can try it. If that doesn't work, then flash the ROM.

bw03 said:
Use the ROM from here.
http://forum.xda-developers.com/moto-x-style/development/rom-indian-marshmallow-variants-t3253684
Edit: you may get the modem working with just flashing the modem zip but I'm not sure as I don't have a dual sim phone to try. You can try it. If that doesn't work, then flash the ROM.
Click to expand...
Click to collapse
Thanks for the reply.
I already did flashed the modem zip but it didn't worked and also flashed to indian_mm_deodexed_rooted.zip with indian mm but still my imei is unknown.
Any other way or any other rom which i can try??

desiaddict said:
Thanks for the reply.
I already did flashed the modem zip but it didn't worked and also flashed to indian_mm_deodexed_rooted.zip with indian mm but still my imei is unknown.
Any other way or any other rom which i can try??
Click to expand...
Click to collapse
Did you do a dirty or clean flash? I would use twrp to wipe everything but external sd card, then flash ROM and modern.

bw03 said:
Did you do a dirty or clean flash? I would use twrp to wipe everything but external sd card, then flash ROM and modern.
Click to expand...
Click to collapse
I used twrp and wiped cache data and also system and then flashed ROM and modem but still it is not working
didn't flashed internal rom as it had ROM but wiped everything else but still no luck.

bw03 said:
Did you do a dirty or clean flash? I would use twrp to wipe everything but external sd card, then flash ROM and modern.
Click to expand...
Click to collapse
I used twrp and wiped cache data and also system and then flashed ROM and modem but still it is not working
didn't flashed internal rom as it had ROM but wiped everything else but still no luck.

Perhaps do a clean flash on a ROM from here? I don't know. Just throwing it out there.
http://forum.xda-developers.com/mot...-stock-x1572-1575-5-1-1-lph23-116-18-t3229355

bw03 said:
Perhaps do a clean flash on a ROM from here? I don't know. Just throwing it out there.
http://forum.xda-developers.com/mot...-stock-x1572-1575-5-1-1-lph23-116-18-t3229355
Click to expand...
Click to collapse
I will try it out... downloading now and will let you know later when dl and flashing finishes and hope i get it working this time, fingers crossed.

If you check my modem thread i posted last night try the code at the bottom after you have flashed the India Dual sim modem you already have, it purges the cache's for modem/general cache
If your still struggling after that ill see what files i have stored away for modems, Im sure i have another dual sim modem other than the indian one..
Edit:
Packaging you afew flashable zip's now with Dualsim Modems for the XT1572

You may need to do the Indian LP modem from the first linked thread too.

http://forum.xda-developers.com/mot...-eu-single-t3297051/post64888714#post64888714
I have posted up more DUAL Sim modems for you to try. Hope it helps and you get it sorted

Unicornzz said:
If you check my modem thread i posted last night try the code at the bottom after you have flashed the India Dual sim modem you already have, it purges the cache's for modem/general cache
If your still struggling after that ill see what files i have stored away for modems, Im sure i have another dual sim modem other than the indian one..
Edit:
Packaging you afew flashable zip's now with Dualsim Modems for the XT1572
Click to expand...
Click to collapse
Hey thanks for the reply... the code did not worked and now trying your modems from ur thread ASIA Dual Sim.
bw03 said:
You may need to do the Indian LP modem from the first linked thread too.
Click to expand...
Click to collapse
Yes i will LP modem flash.
Just one question to all : when i got moto x style in dec it was having Lollipop then i did marshmallow update and then flashed for rooting so now if i again flash to lP stock rom will it get bricked or work?? As i am not getting signals so i will try it later when nothing else works

desiaddict said:
Hey thanks for the reply... the code did not worked and now trying your modems from ur thread ASIA Dual Sim.
Click to expand...
Click to collapse
Try both LP and MM one
I don't agree how you got shafted into this mess, ROM Makers should NEVER package Radio/Modem or Bootloader files in with a ROM ever.
When i release mine in the coming weeks it will be X175x with all the optional modem files or none at all.
Best of luck to you

Unicornzz said:
Try both LP and MM one
I don't agree how you got shafted into this mess, ROM Makers should NEVER package Radio/Modem or Bootloader files in with a ROM ever.
When i release mine in the coming weeks it will be X175x with all the optional modem files or none at all.
Best of luck to you
Click to expand...
Click to collapse
Guys still no luck... nothing worked. I tried both DS modem but did not got sim detection.
I hope somehow who might have faced same issue and got solved will see and reply the thread and save me.
You guys tried to solve my problem... Thank you to both.

Stock ROMs
Have you tried the guide in this thread?:
[Firmware] Moto X Style/Pure Stock Software
You will need a computer and to follow the guide exactly and will lose all data off your internal storage so back up your sdcard to external storage or computer beforehand. Flashing this solved my problems when I had them. Just make sure you back up things before you start. The ROMs are completely stock so you will need to root and install a custom recovery again once done.
Hope this helps.
Ooms

dj_ooms said:
Have you tried the guide in this thread?:
[Firmware] Moto X Style/Pure Stock Software
You will need a computer and to follow the guide exactly and will lose all data off your internal storage so back up your sdcard to external storage or computer beforehand. Flashing this solved my problems when I had them. Just make sure you back up things before you start. The ROMs are completely stock so you will need to root and install a custom recovery again once done.
Hope this helps.
Ooms
Click to expand...
Click to collapse
Okay i am dling the Asian dual sim variant now and hope it works.
But i am little unclear about process as i already have unlocked bootloader and TWRP so can i directly clean flash ROM via TWRP??
Also pls check my reply in that thread for better understanding and not confusing:
http://forum.xda-developers.com/moto-x-style/development/firmware-moto-x-style-pure-stock-t3272486/page8

Did you backup your efs partition? Your imei is inside that partition...

desiaddict said:
Okay i am dling the Asian dual sim variant now and hope it works.
But i am little unclear about process as i already have unlocked bootloader and TWRP so can i directly clean flash ROM via TWRP??
Also pls check my reply in that thread for better understanding and not confusing:
http://forum.xda-developers.com/moto-x-style/development/firmware-moto-x-style-pure-stock-t3272486/page8
Click to expand...
Click to collapse
To be honest, I left the lock bit out. These are the commands I used when I did it:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Click to expand...
Click to collapse
The bootloader will stay unlocked this way meaning you can flash TWRP after. I would flash as above first and once the phone is booted and confirmed to be working, I would then flash TWRP and other mods. On a note, I have an EU XT1572 so I only had 9 parts on the system flash part (upto system.img_sparsechunk.8). The dual sim version may have 10 or more parts. Check how many parts you have beforehand and make sure you flash all bits.
Hope this helps.
Ooms

dj_ooms said:
To be honest, I left the lock bit out. These are the commands I used when I did it:
The bootloader will stay unlocked this way meaning you can flash TWRP after. I would flash as above first and once the phone is booted and confirmed to be working, I would then flash TWRP and other mods. On a note, I have an EU XT1572 so I only had 9 parts on the system flash part (upto system.img_sparsechunk.8). The dual sim version may have 10 or more parts. Check how many parts you have beforehand and make sure you flash all bits.
Hope this helps.
Ooms
Click to expand...
Click to collapse
Oh GOD that totaly worked out great :good::good:
Everything is working fine now
Also rooted again without any problem :cyclops:
Thank you buddy.

@dj_ooms @Unicornzz and @bw03
:angel: Thank you guys for your valuable replies... really helped :angel:

[FIXED] IMEI #2 = 0, due to fastboot erase modemst2

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??

Downgrading to stock from 8.1

Admin Note: This is a special Q&A-formatted thread. Please follow this link to view it in your browser: [url]http://xda.tv/post75619905[/URL]
Please delete the EFS file, restoring another phone's EFS is illegal, sorry.

i lost my voLTE after flashing twrp based stock rom ( nov patch) on pixel experience feb build... now i cant use my jio sim for calls ... No VoLTE support...
if you have a backup of your EFS , can you please send me the file...

sir,what is your baseband version when the volte is working.?(if your current rom has volte working then what is your current baseband version.?)

IMEI shows 0 again after Restore your EFS file

Restore his efs file after flashing pixel experince 8.1,
Just go into twrp,
Flash pixel experince 8.1
And afther that restore his efs partition from twrp .
You will able to get your imei back,
But problem is after doing this way I still not able to get volte.

M8953_02.03.07.08r

Can you tell us what version of baseband do you see when you enter in boot loder.?
Because in my boot loder I see M8953_02.03.07.08U.

thedr34m13 said:
Admin Note: This is a special Q&A-formatted thread. Please follow this link to view it in your browser:
Click to expand...
Click to collapse
Persist backup may help to get volte back..please share if you can

yes,can you share the whole backup of pixel experience rom 8.1 (with volte working),by restoring that backup i think we may able to get volte.

i found this really helpful on another post,
what i did was deleting these files
fastboot erase modemst1
fastboot erase modemst2
from the fastboot comands before flashing back to stock
that works perfectly for me and i got back my signal &4glte.

Possible fix for IMEI 0 after OTA update?

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.

Want to flash TWRP Flashable 7.0 to downgrade from Soak Test. How to avoid IMEI loss?

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...