Database Users

[GUIDE] EFS Partitions: What They Are And How To Get It Back If Lost

Hello. My name is Poise, and I'm a victim of EFS Corruption.
I know, laugh it up.
Anyways, you're either here because you don't know what the EFS is and you wanna know, you ruined your EFS and you're looking for redemption, or you just wanna see me ramble. Whichever the case, I figured I'd write this so nobody else has to deal with the looming fear of your 300 dollar phone with infamously-bad customer support becoming a worthless, barely functioning phone, if not a big 300 dollar brick.
Before I go on, I wanna mention that this guide applies for most if not all phones, not necessarily just the OPO. So if anyone is losing their mind over a corrupted or lost EFS partition, this should get them on the right track to at least understanding the problem.
BACKGROUND: AKA "WHAT IS THE EFS AND WHY DO I EVEN CARE"
EFS stands for Encrypted File System. Imagine the EFS as a big folder containing all of the important stuff that makes the "phone" part of your phone (i.e. what lets you communicate from one person with a phone to another) tick. It contains your IMEI, lots of files revolving around your SIM card and Wifi/Bluetooth (this includes your MAC address for all the radios of your phone), and lots of other things that should never ever under any circumstance be deleted or touched. It's sensitive, it's devastatingly important, and it's a huge pain. If you lose your EFS folder, you lose pretty much any chance of your phone being able to use data, Wifi, Bluetooth, and (in my case) your phone will just not wanna respond and reboot quite a lot.
CHAPTER 1: AKA "THAT SOUNDS LIKE GARBAGE HOW CAN I FIX THIS"
So, like all nice and important things that we have on Android, we can back this folder up, assuming you're rooted and with a custom recovery (though quite frankly if you're not rooted/installing ROMs I have zero idea how you'd corrupt your EFS). I'd recommend doing it through a nandroid backup (TWRP usually has the option to backup EFS, if not there's an unofficial version for bacon that can), but there are other apps that do the job quite nicely. Backing up your EFS is just as essential as backing up your previous ROM; in fact, backing up your EFS is MILES MORE ESSENTIAL because you can just flash a ROM over a corrupted system to get it working. There is no "flashable EFS"; if it were that easy, it wouldn't be so sensitive, and I wouldn't be writing this guide.
CHAPTER 2: AKA "I'M SUPER CAREFUL BRO I'LL NEVER MESS UP MY EFS PARTITION, WHY BOTHER"
Do it anyways.
I installed a ROM, realized my gapps package was screwed up, restored a CM13 backup, and realized my SIM card wasn't being detected. My phone would lag like hell, and after a while it'd just crash and reboot. I had no IMEI, I had no SIM card detection. I knew exactly what it meant. It wasn't fun to restore it.
If ROM installations were perfect, we wouldn't really have to backup anything. But, sometimes a hiccup will occur, something will touch something else that it shouldn't, and chaos ensues. So, if you don't wanna take 4 hours out of your day to hope to Christ that you didn't royally ruin your phone and the restoring method worked, just back it up. It's like, 3MB and it'll save so much frustration. Honestly.
CHAPTER 3: AKA "YEAH ABOUT THAT MY EFS IS ALREADY CORRUPTED, PLS HELP"
Congrats, you did it! Don't feel too bad, it happens to the best of us. :crying:
Fixing an EFS on the Oneplus One is pretty easy, but really time consuming and riveting because it might not 100% of the time work. You'll need the following:
Some sort of ADB/fastboot program. I use Minimal ADB and Fastboot, which rarely has any problems, but you can use whatever as long as it'll talk to your device.
Your near-dead Oneplus One.
A few hours of your time.
Some sort of backup of your data, you'll be factory resetting.
OxygenOS. Preferrably, a package that can be flashed in TWRP. I won't find that for you.
An unlocked bootloader. I cannot stress how important this is. If you don't know what this is, do some research before trying to fix your ruined EFS. Again, how you'd have even ruined it with a locked bootloader is beyond me...
TWRP 2.8.6.0. Yes, it has to be this version; this is the only one that can install firmware correctly. The unofficial modified 2.8.7.0 might be able to, but I'm not about to try it.
Competence and good reading skills. Do everything exactly as I wrote it.
Some knowledge on how flashing a ROM works.
A modified persist.img file that we'll be flashing. You can find it in this thread. Download the Never Settle package and take out the persist.img file; we don't care about the rest. Whether this is mandatory or not, I don't know, but I used it and it worked fine so I'll include it. If anyone tries this without the persist file and it works, let me know. Thanks a ton to markbensze for making this, he saved my skin.
Now for how it's done:
To start, we gotta put your phone into fastboot mode. Do this by holding the power button and the up volume button as you're turning your phone on. You'll know it worked when the phone very dimly says "Fastboot Mode".
Plug your phone into your computer. Let it do any driver stuff it has to, then open your ADB/Fastboot program. Type "fastboot devices", if you see a bunch of letters/numbers with the word "fastboot" a few spaces away, you're set.
Seriously, if your bootloader isn't unlocked, you gotta do that. This will wipe EVERTHING from your phone, including any backups. I won't cover that mess, there's trillions of guides for that.
Type the following commands:
Code:
fastboot erase modemst1
fastboot erase modemst2
fastboot erase persist
This erases a bunch of partitions that have to do with the EFS. They all regenerate themselves, but as an added precaution we're gonna flash that persist.img you got from the thread in the "what you need" list. In order to do this, enter the following command:
Code:
fastboot flash persist [location to your persist.img on your computer]
If all goes well, you'll get a handy success message and you can get out of fastboot mode by holding down the power button until it turns off.
Now, reboot to recovery; do this by holding the power button and holding the down volume button as you turn your phone on, until you see the TWRP splash screen.
How you do this next step is up to you; you can use the built-in MTP to transfer the Oxygen OS file over from your computer to your phone, or you can use ADB sideload. If you don't know how sideload works, just transfer it over.
Factory reset as you would installing a normal ROM, and flash Oxygen OS through the install menu/sideload/however you wanna. Let it fully install.
Reboot. Let it boot, pray to the EFS gods that they'll give you their blessing, and check if your SIM card gets detected.
If it did, congradulations! Your EFS is working. Now, go make a backup while you can.

Very glad that you made a guide about it. I didn't f*** up my phone though, but I truly got the importance of backing up the EFS. Also, got to know about it a bit more.
Thanks!

I have a feeling this is going to come in handy with my project OPO... good stuff man thanks

It worked. After I did this I kept getting boot Loops what was progress on this phone. I did the factory reset in recovery. Let it bootloop some more. Went back to recovery and fixed selinux permissions. Boot Loops again, went back to recovery wipe the dalvik. now it freaking works.

First off, great guide.
But after following this, despite having my IMEI shown previously, my baseband and my imei are now gone. I was told to use this guide to try and fix my data connection problems as it seemed something was wrong with my EFS partition, but it seems following this has left me worse off.
Any suggestions to what else I could do?

Is there a stock oxygen OS file kicking around somewhere? I tried searching for them, but most are modified by other people. One of them hardbricked my phone (the ported Oneplus X oxygen os), so I'd rather not further experiment with other modified ones. I used another OxygenOs file, but despite booting, it didn't fix the baseband or IMEI problem.
I tried doing this but using stock CM13.1.2 instead of OxygenOS, but it didn't fix the problem either. So any other suggestions?
Edit: Nvm, found the official from the OnePlus website, I'm an idiot, going to try doing this with Oxygen to see what happens.

FAILED (remote: Partition flashing is not allowed)
OnePlus 3t with TWRP BlueSpark 3.2.1 recovery.
I am open to flash Roms with TWRP with no problem but I am not able to flash persist.zip (TWRP version) it says it flash but folder doesn't appear and your instructions via fast boot I get the following error.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash persist c:\android\persist.zip
target reported max download size of 435159040 bytes
sending 'persist' (344 KB)...
OKAY [ 0.036s]
writing 'persist'...
FAILED (remote: Partition flashing is not allowed) <------ Problem here or or is my partition on my phone messed up?
finished. total time: 0.057s
I any suggestions for fixing my WiFi/Bluetooth problem?

Fastboot commands not working, ADB way of doing it?
PlayingPoise said:
Hello. My name is Poise, and I'm a victim of EFS Corruption.
I know, laugh it up.
Anyways, you're either here because you don't know what the EFS is and you wanna know, you ruined your EFS and you're looking for redemption, or you just wanna see me ramble. Whichever the case, I figured I'd write this so nobody else has to deal with the looming fear of your 300 dollar phone with infamously-bad customer support becoming a worthless, barely functioning phone, if not a big 300 dollar brick.
Before I go on, I wanna mention that this guide applies for most if not all phones, not necessarily just the OPO. So if anyone is losing their mind over a corrupted or lost EFS partition, this should get them on the right track to at least understanding the problem.
BACKGROUND: AKA "WHAT IS THE EFS AND WHY DO I EVEN CARE"
EFS stands for Encrypted File System. Imagine the EFS as a big folder containing all of the important stuff that makes the "phone" part of your phone (i.e. what lets you communicate from one person with a phone to another) tick. It contains your IMEI, lots of files revolving around your SIM card and Wifi/Bluetooth (this includes your MAC address for all the radios of your phone), and lots of other things that should never ever under any circumstance be deleted or touched. It's sensitive, it's devastatingly important, and it's a huge pain. If you lose your EFS folder, you lose pretty much any chance of your phone being able to use data, Wifi, Bluetooth, and (in my case) your phone will just not wanna respond and reboot quite a lot.
CHAPTER 1: AKA "THAT SOUNDS LIKE GARBAGE HOW CAN I FIX THIS"
So, like all nice and important things that we have on Android, we can back this folder up, assuming you're rooted and with a custom recovery (though quite frankly if you're not rooted/installing ROMs I have zero idea how you'd corrupt your EFS). I'd recommend doing it through a nandroid backup (TWRP usually has the option to backup EFS, if not there's an unofficial version for bacon that can), but there are other apps that do the job quite nicely. Backing up your EFS is just as essential as backing up your previous ROM; in fact, backing up your EFS is MILES MORE ESSENTIAL because you can just flash a ROM over a corrupted system to get it working. There is no "flashable EFS"; if it were that easy, it wouldn't be so sensitive, and I wouldn't be writing this guide.
CHAPTER 2: AKA "I'M SUPER CAREFUL BRO I'LL NEVER MESS UP MY EFS PARTITION, WHY BOTHER"
Do it anyways.
I installed a ROM, realized my gapps package was screwed up, restored a CM13 backup, and realized my SIM card wasn't being detected. My phone would lag like hell, and after a while it'd just crash and reboot. I had no IMEI, I had no SIM card detection. I knew exactly what it meant. It wasn't fun to restore it.
If ROM installations were perfect, we wouldn't really have to backup anything. But, sometimes a hiccup will occur, something will touch something else that it shouldn't, and chaos ensues. So, if you don't wanna take 4 hours out of your day to hope to Christ that you didn't royally ruin your phone and the restoring method worked, just back it up. It's like, 3MB and it'll save so much frustration. Honestly.
CHAPTER 3: AKA "YEAH ABOUT THAT MY EFS IS ALREADY CORRUPTED, PLS HELP"
Congrats, you did it! Don't feel too bad, it happens to the best of us. :crying:
Fixing an EFS on the Oneplus One is pretty easy, but really time consuming and riveting because it might not 100% of the time work. You'll need the following:
Some sort of ADB/fastboot program. I use Minimal ADB and Fastboot, which rarely has any problems, but you can use whatever as long as it'll talk to your device.
Your near-dead Oneplus One.
A few hours of your time.
Some sort of backup of your data, you'll be factory resetting.
OxygenOS. Preferrably, a package that can be flashed in TWRP. I won't find that for you.
An unlocked bootloader. I cannot stress how important this is. If you don't know what this is, do some research before trying to fix your ruined EFS. Again, how you'd have even ruined it with a locked bootloader is beyond me...
TWRP 2.8.6.0. Yes, it has to be this version; this is the only one that can install firmware correctly. The unofficial modified 2.8.7.0 might be able to, but I'm not about to try it.
Competence and good reading skills. Do everything exactly as I wrote it.
Some knowledge on how flashing a ROM works.
A modified persist.img file that we'll be flashing. You can find it in this thread. Download the Never Settle package and take out the persist.img file; we don't care about the rest. Whether this is mandatory or not, I don't know, but I used it and it worked fine so I'll include it. If anyone tries this without the persist file and it works, let me know. Thanks a ton to markbensze for making this, he saved my skin.
Now for how it's done:
To start, we gotta put your phone into fastboot mode. Do this by holding the power button and the up volume button as you're turning your phone on. You'll know it worked when the phone very dimly says "Fastboot Mode".
Plug your phone into your computer. Let it do any driver stuff it has to, then open your ADB/Fastboot program. Type "fastboot devices", if you see a bunch of letters/numbers with the word "fastboot" a few spaces away, you're set.
Seriously, if your bootloader isn't unlocked, you gotta do that. This will wipe EVERTHING from your phone, including any backups. I won't cover that mess, there's trillions of guides for that.
Type the following commands:
Code:
fastboot erase modemst1
fastboot erase modemst2
fastboot erase persist
This erases a bunch of partitions that have to do with the EFS. They all regenerate themselves, but as an added precaution we're gonna flash that persist.img you got from the thread in the "what you need" list. In order to do this, enter the following command:
Code:
fastboot flash persist [location to your persist.img on your computer]
If all goes well, you'll get a handy success message and you can get out of fastboot mode by holding down the power button until it turns off.
Now, reboot to recovery; do this by holding the power button and holding the down volume button as you turn your phone on, until you see the TWRP splash screen.
How you do this next step is up to you; you can use the built-in MTP to transfer the Oxygen OS file over from your computer to your phone, or you can use ADB sideload. If you don't know how sideload works, just transfer it over.
Factory reset as you would installing a normal ROM, and flash Oxygen OS through the install menu/sideload/however you wanna. Let it fully install.
Reboot. Let it boot, pray to the EFS gods that they'll give you their blessing, and check if your SIM card gets detected.
If it did, congradulations! Your EFS is working. Now, go make a backup while you can.
Click to expand...
Click to collapse
Is there a way to replicate your 3 fastboot commands, using ADB? My bootloader is unlocked and running the latest TWRP recovery 3.2.2
My results via fastboot
"
fastboot erase modemst1
erasing 'modemst1'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.024s
"

I have a Samsung Galaxy Note 2 phone with a broken logic board. I need to replace, but I may need to change the IMEI of the replacement board with my old phone's IMEI if I buy the replacement board from China.
Does the IMEI number pass to the other phone if I restore my Twrp backup which contains all partitions (more specifically the EFS partition), over this motherboard? Does it solve my problem.

Any chance to get an upload of the file needed??

Same EFS partition over time ? after updating Android ?
Thx a lot, this has saved me a lot of troubles ^^
Was just wondering, is the EFS partition always the same over time ? modemst1 & modemst2 files are the same for all Android/OxygenOS version ?
I've backed up mine under OxygenOS 3.2.8 and I was wondering if i could still use it to restore the EFS partition if anything goes wrong ?
PS : Sorry for my bad english, it's not my native language ^^
---------- Post added at 09:28 PM ---------- Previous post was at 09:26 PM ----------
crenshaw1979 said:
Is there a way to replicate your 3 fastboot commands, using ADB? My bootloader is unlocked and running the latest TWRP recovery 3.2.2
My results via fastboot
"
fastboot erase modemst1
erasing 'modemst1'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.024s
"
Click to expand...
Click to collapse
You can find how to do it on this thread : https://www.theandroidsoul.com/fix-...d-wifibluetooth-issues-restoring-twrp-backup/

EFS / Modem backup option gone?
hey there :]
I want to backup my phone. In TWRP I had the option to backup EFS and modem partitions. I decided to upgrade TWRP, since my version (3.2.x) was older than the most recent (3.4). After flashing the .img from inside TWRP, everything function as expected... however, the option to backup EFS and Modem is gone.
I downgraded to older version of TWRP, but TWRP still does not show the option for EFS and modem backups.
recovery.log, that was created when I made the TWRP backup lists "Unable to locate '/modem_st1' partition for backup calculations."
What did I do wrong? Does bacon require some extra step to unlock EFS and modem access for TWRP?

Does this method work with lgv60 snapdragon 865 unlocked bootloader ?

Whenever I get a new device , on day number one I always backup my efs partitions.. I use termux app from my device and type:
su (push enter)
Then I type these in one by one in termux and grab the two files off my device's sdcard and upload them to a cloud and transfer them both to my PC and/or a thumb drive.
dd if=/dev/block/sdf2 of=/sdcard/modemst1.bin bs=2048
(push enter)
dd if=/dev/block/sdf3 of=/sdcard/modemst2.bin bs=2048
(enter)
If ever I lose my IMEI these can be fastboot flashed back and restored that way. This info I first came across over on Funk Wizard's XDA guide thread for OnePlus 6t. Works great. Only thing is now I'm a retired crack flasher so my days/years of installing everything available for my device are most definitely over and that's how I always lost mine back in the Nexus days... During an installation of only God knows what back then. Still much better to be safe than sorry and have an expensive paper weight for a phone if ever something does happen.

Need a A2017 Modem

Hey Guys,
i good a little problem with my axon 7. ive got the g model with cm13 and yesterday i tryed to flash the b29 o n my phone.
now the problem is that my sim card is accepted and the imeis are correct but i have no data connection at all.
so i tryed to go back to b03 oder other otas for the g model but i cant install any of this updates.zips in recovery because of error 8.
older backups dont fix the problem even and when i want to go back to the first backup i made after rooting the phone then it tells me that something is wrong withe the encoding...
so has anyone an idea how i can fix that problem?

for everyone with the same issue:
is used this guide (https://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484) and it worked.
-> if you get the "encryption error1 after flashing the rom then just press reset phone.
-> if the divice doesnt boot after flashing just boot into recovery frist and reboot system in there.
but be sure that you havent any impiortant flies on internal sd card!

Try this: boot into TWRP recovery and in "advanced" go to Terminal Emulator
There, enter these codes
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1
and execute and then enter
Code:
dd if=/dev/zero of=/dev/block/bootdevice/modemst2
and execute
This should erase those partitions and they should regenerate automatically on boot.
If this doesn't help, you could indeed try to use someone else's modems
EDIT: damn, too late

Now we have two solutions!
thank you

[FIX] Phone Reboots Into Recovery Mode & Can Only Be Started From Fastboot

Thanks to xda member @Shooting Star Max for the original post for this solution
If your phone is always rebooting into recovery, and the only way to boot normally is by using the bootloader, follow these instructions:
Some users recommend removing your SD before doing the following as incorrectly formatted SD Cards could cause the phone to boot into recovery instead of booting normally.
1) Boot into TWRP recovery.
2) Plug your Cedric into your computer (which needs to have drivers and fastboot installed).
3) Open a command prompt window and type:
Code:
adb pull /dev/block/platform/soc/7824900.sdhci/by-name/misc misc.img
This will make a backup of the misc partition just in case.
4) Type the following:
Code:
adb shell dd if=/dev/zero of=/dev/block/platform/soc/7824900.sdhci/by-name/misc
This will clear the misc partition. You might get a message regarding lack of space, but it's okay.
5) Your Cedric will boot normally again

TheFixItMan said:
Thanks to xda member @Shooting Star Max for the original post for this solution
If your phone is always rebooting into recovery, and the only way to boot normally is by using the bootloader, follow these instructions:
1) Boot into TWRP recovery.
2) Plug your Cedric into your computer (which needs to have drivers and fastboot installed).
3) Open a command prompt window and type:
Code:
adb pull /dev/block/platform/soc/7824900.sdhci/by-name/misc misc.img
This will make a backup of the misc partition just in case.
4) Type the following:
Code:
adb shell dd if=/dev/zero of=/dev/block/platform/soc/7824900.sdhci/by-name/misc
This will clear the misc partition. You might get a message regarding lack of space, but it's okay.
5) Your Cedric will boot normally again.
Click to expand...
Click to collapse
I did the procedure and everything went back normal.
I did a backup with the twrp and when I went to restore and go back everything as before, it will continue to restart in the bootloader and I must confirm with the power key to boot the system.
I tried to repeat the procedure but nothing to do does not work anymore.
Some help thank you

masterdex said:
I did the procedure and everything went back normal.
I did a backup with the twrp and when I went to restore and go back everything as before, it will continue to restart in the bootloader and I must confirm with the power key to boot the system.
I tried to repeat the procedure but nothing to do does not work anymore.
Some help thank you
Click to expand...
Click to collapse
As long as you have fully booted your phone before trying again I don't see why you couldn't repeat it
Or reflash the recovery and try again

[/ATTACH]
TheFixItMan said:
As long as you have fully booted your phone before trying again I don't see why you couldn't repeat it
Or reflash the recovery and try again
Click to expand...
Click to collapse
Still tried on minimal adb and phower shell does not work. I attach pictures.

masterdex said:
[/ATTACH]
Still tried on minimal adb and phower shell does not work. I attach pictures.
Click to expand...
Click to collapse
Make sure adb is connected properly
Code:
adb kill-server
adb devices
Your device should be displayed as connected & should be the only device listed
If it still doesn't work then the only solution I can think of is restoring your stock firmware by fastboot - do not flash the bootloader part of the firmware

TheFixItMan said:
Make sure adb is connected properly
Code:
adb kill-server
adb devices
Your device should be displayed as connected & should be the only device listed
If it still doesn't work then the only solution I can think of is restoring your stock firmware by fastboot - do not flash the bootloader part of the firmware
Click to expand...
Click to collapse
Yes is connected. If only I could find the firmware for my XT1675 16gb / 2gb single sim model.

masterdex said:
Yes is connected. If only I could find the firmware for my XT1675 16gb / 2gb single sim model.
Click to expand...
Click to collapse
Same phone as mine & Iv never had this problem - I use lineageos - try flashing that
Other than that I can't suggest anything else

Thank you anyway. They persistently waited for Lenovo to provide the tools and release the firmware for my model that is currently unavailable.
I've tried all the constructions here, but they all have background noise during calls and fixed gps in over a minute and it's not accurate.
Do you have my own model with the same features?

masterdex said:
Thank you anyway. They persistently waited for Lenovo to provide the tools and release the firmware for my model that is currently unavailable.
I've tried all the constructions here, but they all have background noise during calls and fixed gps in over a minute and it's not accurate.
Do you have my own model with the same features?
Click to expand...
Click to collapse
I have the XT165 running lineageos
No problems with calls - iv changed the build.prop to edit call volume (see my last post in the lineageos thread)
No problem with gps
You could try running these commands in fastboot as this was a fix for gps in past moto devices
Code:
fastboot erase modemst1
fastboot erase modemst2

Okay, now I'm just trying to build stock, if I think I bought the phone, just the time to get home and unlock bootloader and put custom rom, I almost do not know the functions of building stock. Now I see how it behaves and I guess if I install Lineage again and make all the corrections you've suggested very kindly thanks.

TheFixItMan said:
4) Type the following:
Code:
adb shell dd if=/dev/zero of=/dev/block/platform/soc/7824900.sdhci/by-name/misc
This will clear the misc partition. You might get a message regarding lack of space, but it's okay.
Click to expand...
Click to collapse
Clearing the whole misc partition may be overkill and cause other issues. In the LG threads they currently suggest clearing only the first 256 bytes.

ST Dog said:
Clearing the whole misc partition may be overkill and cause other issues. In the LG threads they currently suggest clearing only the first 256 bytes.
Click to expand...
Click to collapse
This works fine for our users - its been tested & no one has reported any issues

TheFixItMan said:
This works fine for our users - its been tested & no one has reported any issues
Click to expand...
Click to collapse
That's cool. Just a thought.
Different OEs put different stuff there, but really no reason to clear it all if only part is the problem.
And one never knows when they might change the usage.
Oh, and masterdex above appears to have had some issue.

ST Dog said:
That's cool. Just a thought.
Different OEs put different stuff there, but really no reason to clear it all if only part is the problem.
And one never knows when they might change the usage.
Oh, and masterdex above appears to have had some issue.
Click to expand...
Click to collapse
It worked for him but then he restored old phone backups - I recommended flashing lineageos from scratch

Nothing to do, I tried again to download Lineage, make a clean installation by deleting all the entries in the TWRP, configuring the phone restarted in recovery, and rewriting the procedure, the result does not change always restarts the bootloader.
At this point you only have to install the firmware from scratch, someone knows where to find firmware stock model XT1675 16gb storage and 2 gb sin ram single sim?

masterdex said:
Nothing to do, I tried again to download Lineage, make a clean installation by deleting all the entries in the TWRP, configuring the phone restarted in recovery, and rewriting the procedure, the result does not change always restarts the bootloader.
At this point you only have to install the firmware from scratch, someone knows where to find firmware stock model XT1675 16gb storage and 2 gb sin ram single sim?
Click to expand...
Click to collapse
This is rom stock Cedric work on XT1675 16 gb 2 gb ram installed on Motog5 brand Tim :https://www.youtube.com/watch?v=EMyaDv1lcYg

TheFixItMan said:
I have the XT165 running lineageos
No problems with calls - iv changed the build.prop to edit call volume (see my last post in the lineageos thread)
No problem with gps
You could try running these commands in fastboot as this was a fix for gps in past moto devices
Code:
fastboot erase modemst1
fastboot erase modemst2
Click to expand...
Click to collapse
I tried to give these commands fastboot but the result and that when I restart the phone no longer sees the sim and I have to reinstall the original firmware with fastboot. Tried twice the same result, are you sure you have the right commands?

My Cedric is listed on the adb devices code when it's turned on. But if I restart to twrp then it's not listed. Now how can I perform this
Sent from my Motorola Moto G 2014 using XDA Labs
---------- Post added at 11:57 AM ---------- Previous post was at 11:52 AM ----------
It is listed when I turned off the Mtp. But when I give the first command to backup the misc folder I get
[?] /dev/block/platform/soc/7824900.sdhci/by-name/misc: 1048576/?.
Sent from my Motorola Moto G 2014 using XDA Labs
---------- Post added at 12:17 PM ---------- Previous post was at 11:57 AM ----------
Again solved it. I just backed up the misc in twrp itself by copying the misc file to the /sdcard using the inbuilt file manager of twrp. Then tried the second command. It worked like charm. Thank you
Sent from my Motorola Moto G 2014 using XDA Labs

Perfect!
Thank you, TheFixItMan! I have an XT1672, Android 7.0 Stock Rom, and I was having this problem after trying the November update via OTA. The correction steps worked perfectly! Happy New Year!

Thanks hope to try this tonight, have you had feedback that this works? Thanks

Severe Issues after uninstalling Magisk - Motorola XT1926-7 G6 Plus

I will try to be as brief as possible, but explain in detail what happened to my moto g 6 plus XT1926-7.
I was running the stock firmware from the:
RETLA
Channel from march 27, 2019:
XT1926-7_EVERT_RETLA_9.0_PPWS29.116-11-2
I unlocked the bootloader using the info provided by motorola.
I used a TWRP installer which I found in this website and successfully installed twrp 3.2. I quickly realized that this version did not decrypt the data partition.
No problem, using the boot command in fastboot, I can load TWRP 3.3 which does decrypt the data partition.
I installed magisk V19.2
I then installed 2 magisk modules:
Viper equalizer
Pixel 3 ( something ) which makes the UI a little nicer.
The phone worked with no problems for months until the July OTA "update unsuccessful" nag screen started showing up every 10 seconds.
I read from several sources that an unlocked bootloader phone from motorola won´t take OTA updates. Fine. I lived with it for a couple of weeks until the nagging screen became unbearable.
I decided to unroot, relock the bootloader get the OTA and move on with my life.
I uninstalled magisk from the magisk manager and the phone immediately went into boot loop.
I´ve been using TWRP for years now with several phones, and each time i´ve had a problem, i just restored from the last backup ( which i do at least once a month ) and move on.
This time i used the full twrp backup from a couple of weeks ago, but it didn´t work.
The phone still bootlooped. It either rebooted at the "verity disabled" screen or it went straight into TWRP 3.2
I decided to use the original backup i did several months back when i first installed magisk and it didn´t work either. First time in years that a TWRP backup didn´t work.
I read in several threads on several websites that the only thing left to do was to flash stock rom from motorola in fastboot basically file by file.
So I did it and flashed the original stock rom for my device from the RETLA channel:
XT1926-7_EVERT_RETLA_8.0.0_OPWS27.113-89-5
The phone booted into android but both IMEI and wifi mac address were gone. So no carrier signal and no wifi.
I read from several threads that a backup from the EFS and persist partitions would solve this, so I tried both backups of these partitions i had, but nothing worked.
fastboot would read the IMEI number with the get vars command, but android would not recognize them.
Then i found a post here from a couple of days ago of a person who had the same problem and by flashing the latest stock rom fixed this.
So i downloaded:
XT1926-7_EVERT_RETLA_DS_9.0_PPWS29.116-11-6
from the RETLA channel and again proceeded to flash via fastboot file by file.
this time android booted and it did load the both IMEIs and the wifi mac address BUT, wifi disconnects every 10 seconds and the carrier signal is worse.
I then tried the lenovo assistant as suggested in another thread in this website and used the flash / recover feature. Same thing happened. android boots but wifi signal is lost every 10 seconds and carrier signal gets cut off at regular intervals and is very weak.
This has rendered my phone basically useless. I had been using a Moto G2 for many years with no problem and i bought this one just a couple of months ago.
I don´t mind flashing the phone again, and i´m good at following step by step procedures.
It would be super cool if someone would point me in the right direction on how to fix this.
Thanks in advance

This is how I managed to fix my Moto G6 plus
I was able to fix my phone so I will reply to my own post:
It took me almost 4 days to fix the phone. It took a lot of reading and MANY hours of trial and error, so I´m going to describe what I did in order to help anybody with the same problem to save themselves a LOT of time.
As it happens, I found out that a lot of people have run into the same problem of bootloops after uninstalling magisk and then even after flashing the stock rom, had no wifi and no carrier signal. Hence, a useless phone.
Prerequisites for this solution:
Be able to boot your phone into bootloader mode.
If you don´t know what bootloader mode is, do your research. It´s very simple to get to it. Just power off your phone and then press the power and volume down buttons simultaneously for a couple for a couple of seconds. How to use it is another matter entirely. Again... do your research.
1. Before disaster strikes... Do not use an installer script to force install TWRP on a phone which has A / B boot slots. If you plan to install Magisk later, do not force instal TWRP. Moto G6 Plus is such a phone. This is written very clearly in the Magisk troubleshoot wiki. I wish I had read this before.
If you want to use TWRP ( and you should ), load TWRP 3.3 or newer temporarily from fastboot with the boot command. It will be able to decrypt your phone´s data. TWRP 3.2 does not.
To decrypt you will need to have a pin or pattern unlock set previously on your phone.
I used a script to force install twrp 3.2 to my phone. It´s useless since it can´t decrypt the phone and it was surely the cause of all this mess.
I´m not blaming TWRP or Magisk. This mess was all my fault. I´ll tell you about it later.
2. I have a TWRP 3.3 full decrypted backup of ALL the partitions of the phone from last week. I always do regular backups. I´ve been using TWRP for years and it has always served me well. This time it didn´t. My bad, not TWRP´s. I flashed the backup to the phone and it kept bootlooping. I flashed the backup about 20 times!
3. If you´re in this mess already because you forced install TWRP and you uninstalled magisk and your phone is bootlooping, you will probably have to wipe your phone and flash the stock ROM appropriate to your model. Trust me, if you´re not an android / linux guru, your only way to get your phone back will be to wipe your phone completely. I realized this the hard way.
Don´t flash the original ROM for the G6 plus ( android 8 ). Use the latest build. It seems motorola took note of so many people having the "no carrier / no wifi signal" problem, so they have included a fix for this in the latest android 9 releases. This has worked for other people, It worked for me. I don´t know for sure if it will work for you.
4. Here´s one important piece of info. For motorola phones it is very important to have a backup of these two partitions:
EFS
PERSIST
I´m not 100% percent sure of all the info they have or the entire purpose that they serve, but I now know 1 thing. These two partitions have critical and unique information about your phone.
They provide the unique IMEI info. Wifi Mac address info. Baseband info, which is all the technical carrier signal communications stuff, etc..
How do you back up these partitions? Use a custom recovery like TWRP or similar. If you want to mod your phone, please do your research on the software you are going to install. I usually do it, this time around I just winged it, and look where it got me.
5. Here´s another important piece of information to take note of BEFORE disaster strikes. Write down on a piece of paper and store in a safe place ( a txt file on your pc will do ) the following:
Your phone´s exact model Nº. Mine is:
XT1926-7
Go to settings: tap System, tap about phone and write down which software channel you are on.
Mine is: RETLA
This is important because it determines which stock ROM you will need to download, as not all ROMS for this device are the same. The XT1926-7 is a dual SIM phone so NO. Not all versions of the stock rom will work.
6. In order to download the correct stock ROM for your phone, on your computer, go to:
mirrors .lolinet .com /firmware/moto/evert/official/
This website is one of several which offer stock roms for motorola phones. You can use this one or search around for another one.
The website will show you a directory structure of all the different software channels available for the motorola Moto G6 Plus. Choose the folder appropriate for your phone.
Remember mine was the RETLA channel?
These are the only channels which offer stock roms for the XT1926-7
RETLA
or
TEFCO
or
TEMX
or
TIGCO
If your phone is factory unlocked you will probably have to use the RETLA versions.
Within the correct folder, look for the latest ROM for your model. Pay close attention to the name of the rom. The first section will indicate what model it´s intended for. For example, in the RETLA folder there´s ROMS for 2 different models:
XT1926-6
XT1926-7
The correct file for my phone was:
XT1926-7_EVERT_RETLA_DS_9.0_PPWS29.116-11-6_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Please do your research and download the right file for your phone. If you´re not careful, it will lead to bigger problems.
Please also download the original factory version of android 8 ( oreo ) made for your phone. you´re gonna need 2 files from that ROM. In my case the file was:
XT1926-7_EVERT_RETLA_8.0.0_OPWS27.113-89-5_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
The stock roms are about 2 gigs in size.
6. Next you´ll need to download the right tools to flash the stock rom to your phone.
I´m assuming you have downloaded and installed the latest motorola USB drivers for your computer and installed them. If you haven´t. The time is now.
The internet will tell you to download the Android SDK platform tools. This package will give you fastboot and ADB.
Don´t download it. The "vanilla / run of the mill" version of fastboot won´t help you.
Motorola created a modified version of fastboot for their phones, which flashes a motorola phone in specific ways. It´s called: mfastboot
I saw the procedure differences while running mfastboot in the DOS window. In the end I was able to fix my phone because of the differences which mfastboot offers. You´re gonna have to trust me on this one.
Since the motorola version of fastboot is small in size, i´m going to attach it to this comment. Look for the attached file named:
mfastboot_adb_tools.zip
7. Create a folder on your hard drive. It doesn´t matter how you call it. Just remember where it is. Unzip / decompress the entire contents of the file:
mfastboot_adb_tools.zip
you just downloaded to that folder. it should look like this:
Then unzip / decompress the entire contents of the:
XT1926-7_EVERT_*YOUR-CHANNEL*_DS_9.0_PPWS29.116-11-6
to the same folder. it should look like this:
Now we will need just 2 files from the:
XT1926-7_EVERT_*YOUR_CHANNEL*_8.0.0_OPWS27.113-89-5
Unzip these two files to the same folder where you have unzipped everything else:
8. It is now time to boot your G6 Plus into bootloader mode. With the phone turned off, press the power and volume down buttons simultaneously for about 5 seconds.
You´ll get a black screen with the android robot laying on its back. At the bottom of the screen you will see a piece of text which reads:
Connect USB Data cable.
Do it. Connect the usb cable to your computer and then connect it to the phone. the connect data cable message will change to a green sentence which reads:
Transfer mode: USB connected
9. On your computer, return to the folder where you placed all the files. Look for a blank space with no files within that folder and press the shift key + mouse right click. out of the context menu you get, select:
open command window here
You will get a black screen with a white prompt.
Now let´s make sure your phone is connected to your computer. In that black window type:
mfastboot devices
The result should be your phones serial number followed by the word fastboot.
If you got nothing or any sort of error it means you phone is not connected properly or some drivers are missing. troubleshoot that and come back when your phone is actually connected.
10. OK... let´s start flashing the files. The following series of commands I copied from another post in this website. I did not come up with this set of commands and I will repeat that i´m no expert. This worked for my particular situation and by no means i can guarantee that it will work with your phone. All I´m saying is that if you´re desperate and at the current moment you have a soft bricked phone, go ahead and try this.
In that black window, start copying these commands 1 by 1. Wait for them to execute and get an OK message from the phone. If you get an error try that command again. to paste the command in the black window ctrl + v does not work. you have to right click your mouse on top of that window and paste the command that way. When you´ve pasted the command, press enter to execute.
These are the commands:
Code:
mfastboot getvar max-sparse-size
mfastboot oem fb_mode_set
mfastboot flash partition gpt.bin
mfastboot flash bootloader bootloader.img
mfastboot flash modem_a NON-HLOS.bin
mfastboot flash fsg_a fsg.mbn
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash bluetooth_a BTFM.bin
mfastboot flash dsp_a dspso.bin
mfastboot flash logo_a logo.bin
mfastboot flash boot_a boot.img
mfastboot flash system_a system.img_sparsechunk.0
mfastboot flash system_a system.img_sparsechunk.1
mfastboot flash system_a system.img_sparsechunk.2
mfastboot flash system_a system.img_sparsechunk.3
mfastboot flash system_a system.img_sparsechunk.4
mfastboot flash system_b system_b.img_sparsechunk.0
mfastboot flash system_b system_b.img_sparsechunk.1
mfastboot flash oem_a oem.img
mfastboot flash oem_b oem_other.img
mfastboot flash vendor_a vendor.img_sparsechunk.0
mfastboot flash vendor_a vendor.img_sparsechunk.1
mfastboot erase carrier
mfastboot erase userdata
mfastboot erase ddr
mfastboot oem fb_mode_clear
press power button on the phone and restart it.
It might take a while to boot, but if and when you see and hear the "hello moto" greeting, it means your phone has been fixed.
You might end up with a restored phone, but no wifi and no carrier signal. Then what you will need to do is to flash the backup of your EFS and Persist partitions using TWRP, and then retry the whole procedure again.
This is the way I fixed my Moto G6 plus.
It wasn´t a perfect fix for me. Since I had forced installed TWRP 3.2 with an installer script, that did something to the boot partition and now even after reflashing the entire phone I don´t have any type of recovery.
No stock recovery of any kind. It´s not a problem since we can boot TWRP temporarily from mfastboot and in bootloader mode just like the procedure we did with the stock rom. All the rest is back to perfect working condition.
I was also able to make a new full phone backup.
I will tell you this, now I know that all this mess is not TWRP´s or Magisk´s fault. They are fine programs. It was my fault due to a lack of research. I shouldn´t have mixed them both in the way I did.
I forced installed TWRP to my phone because it was what I was used to and I didn´t read any instructions for Magisk which I had never used. I come from the SU era.
I hope this wall of text will be of help to anyone going through the same situation with a Moto G6 plus.
Unfortunately nobody replied to my original post so I had to solve this on my own. The good thing is that I did manage to fix it.
I will repeat it one more time. I´m not an android expert. Not by far. I´m not saying this procedure will work for your particular problem. I´m only sharing what worked for me and I hope it will work for you. If it doesn´t. Keep looking and researching.
GOOD LUCK.

hello, i have the exact same problem but my stock rom dowes not have any system_b file ( my rom is RETAR) what should i do?
Edit: sorry, i had another update file, pien not oreo. On oreo zip it appears
---------- Post added at 01:07 AM ---------- Previous post was at 12:21 AM ----------
Ok, so now i followed your guide exactly as you did it but it doesn't boot. It bootloops
Do you know what's happening?

juampapo546 said:
hello, i have the exact same problem but my stock rom dowes not have any system_b file ( my rom is RETAR) what should i do?
Edit: sorry, i had another update file, pien not oreo. On oreo zip it appears
---------- Post added at 01:07 AM ---------- Previous post was at 12:21 AM ----------
Ok, so now i followed your guide exactly as you did it but it doesn't boot. It bootloops
Do you know what's happening?
Click to expand...
Click to collapse
Sorry for spamming the thread, i got out of the boorloop by installing again the oreo stock rom (with no imei nor mac). After doing it i did the whole procedure again and it booted but still having the wifi/mobile data resetting. I will redo everything againand if after several times i get to nothing i will post another question here.
Sorry and thank you

Still doesn't work

juampapo546 said:
Still doesn't work
Click to expand...
Click to collapse
Do you have a backup of your EFS and Persist partitions from when the phone was in working condition?
You could use those to restore you Emei and wifi mac address and then flash Pie again.

lcmp said:
Do you have a backup of your EFS and Persist partitions from when the phone was in working condition?
You could use those to restore you Emei and wifi mac address and then flash Pie again.
Click to expand...
Click to collapse
No, I don't have one. I thought that in this guide I didn't need the backup but apparently there is no solution for now if there is no backup.
Thank you

juampapo546 said:
No, I don't have one. I thought that in this guide I didn't need the backup but apparently there is no solution for now if there is no backup.
Thank you
Click to expand...
Click to collapse
Like I said in my post, i´m not an expert. I just posted the procedure which worked for me.
I did have a backup of those partitions and I used them several times and it did not work. Are you using mfastboot instead of regular fastboot?
I would try the procedure several times.
Buena Suerte.

lcmp said:
Like I said in my post, i´m not an expert. I just posted the procedure which worked for me.
I did have a backup of those partitions and I used them several times and it did not work. Are you using mfastboot instead of regular fastboot?
I would try the procedure several times.
Buena Suerte.
Click to expand...
Click to collapse
I tried it several times but as I said previously there is no point doing it with no backup ( not my words, I talked to a guy that develops most of the g6 Plus roms and told me for now there is no solution without the backup, it was over the Spanish telegram group. I highly recommend it, if you want to join talk to me at the PM because I can't share social network on posts)
Thank you for your advise, if I am able to solve it I will let you know

lcmp said:
Like I said in my post, i´m not an expert. I just posted the procedure which worked for me.
I did have a backup of those partitions and I used them several times and it did not work. Are you using mfastboot instead of regular fastboot?
I would try the procedure several times.
Buena Suerte.
Click to expand...
Click to collapse
I screwed up my efs/persist and didn't have a backup (a few months ago).
So can I please have a copy of the backed up efs and persist partitions? I should be able to go through and replace any ids (mac address and imei) with my own. If I figure it out, I'll write a guide on it too .
I have the same device model as you (XT1926-7 RETLA).
I've also been looking at this (https://forum.xda-developers.com/razr-i/development/pds-partition-fix-risky-faint-heart-t2813292) which is for a different problem with a different phone where someone posted their pds/persist partition, but it looks like the data in those partitions are just stored plainly in binary.

stevendoesstuffs said:
I screwed up my efs/persist and didn't have a backup (a few months ago).
So can I please have a copy of the backed up efs and persist partitions? I should be able to go through and replace any ids (mac address and imei) with my own. If I figure it out, I'll write a guide on it too .
I have the same device model as you (XT1926-7 RETLA).
I've also been looking at this (https://forum.xda-developers.com/razr-i/development/pds-partition-fix-risky-faint-heart-t2813292) which is for a different problem with a different phone where someone posted their pds/persist partition, but it looks like the data in those partitions are just stored plainly in binary.
Click to expand...
Click to collapse
Well yes, but actually no. You can't use another's device efs/persist because these files can only be read by the device that created them
However I found a magisk module that fixes several persist issues. It is called PIXELARITY

However I found a magisk module that fixes several persist issues. It is called PIXELARITY
Click to expand...
Click to collapse
Does this actually fix the persist issues permanently? Or does it just work around them while it is installed? I am in the same boat as others without a proper backup of efs/persist. If it fixes anything I will be happy.
Also, how are you getting the Magisk module installed? I have no wifi or cell service so the Magisk app can't download the module. Tried just downloading the module repo .zip file and manually installing from that, but magisk is not recognizing it as a valid module. I almost never install Magisk at all let alone modules, so I am a bit in the dark on the general procedures.
Edit: Wound up getting it installed with a USB ethernet dongle to get some form of connection. But the PIXELARITY mod did absolutely nothing in my case. Flashed stock and I have IMEI and Wifi MAC Address back, but they are now both cutting out in the same way as yours. The Magisk module did nothing there either.

I forgot to post it, for mi actually it just partially worked ( permanent). I said partially because I lost my IMEI.
I am now trying to use the efs that doesn't have an IMEI to patch it up with mine and maybe make it "universal" and share it to other people and they just patch their IMEI.
However it is quite complicated and I am not having a really advanced progress on this.
---------- Post added at 12:33 PM ---------- Previous post was at 12:29 PM ----------
I have just seen the edit.
What worked for me I believe it was a chance and I can't recall exactly what I did before it "workerd", I did a lot of things, as I believe you also did.
I would try following the guide up here and installing the module, maybe that's what I did.

Fixed the signal drop with no backups here the link
https://forum.xda-developers.com/g6-plus/how-to/guide-how-to-solve-wifi-mobile-data-t3994827

Help with an nv_error caused by a bad flash

I was having issues with my m3 (it was stuck in edl mode). after waking up I flashed the latest mi fastboot rom with mi flash tool and now I get a corrupt nv_data error and phone reboots in recovery mode.
I've been reading about it and it seams this is a result from a corrupt efs partition as I don't have a backup of efs,
as far as I've read the fix is in deleting modem files
adb shell dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1​adb shell dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2​adb shell dd if=/dev/zero of=/dev/block/bootdevice/by-name/fsg​and then editing qcn with qpst tool.
qpst tool requires edl mode and I just got my phone out of edl, and I'm not even sure how to get into edl without opening the back cover.
does anyone have more information about this nv_error issue, does someone have a link to or can share an efs backup of m3.
I've read some posts here about people with similar issues however I can't seam to find a guide on how to fix this nv_error issue.
I took my device to the local mi service centre (they're a xiomi partner and representatives for my country not xiaomi themself) and the guy there wanted to replace my mother board but they didn't have m3 on stock but they guy knew hardware bad had no idea what magisk was so I'm not too keen on their sugestions.

trying to erase efs from adb returns an error
sh-5.0# dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1​dd: /dev/block/bootdevice/by-name/modemst1: write error: No space left on device​as the phone is stuck in recovery I am using adb side load functions in twrp/fox
what am I donig wrong how do I null these partitions?

An update, it seams that dd from adb cannot be done on more recent devices as they expect an image to write to those partition not zeros but those partitions can be nulled from fast boot
fastboot erase modemst1​fastboot erase modemst2​I did this, as standard rom couldn't boot I flashed engineering rom and with qpst I managed to reset my IMEI, the device works as expected in engineering rom ie both sim slots work, wifi,bt and 2g/3g/4g work but after reflashing release rom from both fastboot (miflash tool) and twrp (orange fox) the phone refuses to boot and in stock recovery I get the error message nv_error.
Any ideas what to do next, as installing engineering rom is not a real solution as that is not a production release as it has only debug tools not even an apk installer.
Reading posts here it would seam that snapdragon devices have an nv_data.bin file inside the /efs partition

another update
after thinking if engineering rom worked why not flash only engineering modem image not whole OS
doing
fastboot flash modem NON-HLOS.bin​the device boots, both IMEI are lost and the phone wants to update to miui 12.5.9.0 as far as I can tell there is no update to the modem, afer the update I'll try and restore imei.
this doesn't seam legit if engineering rom boots why do I get a corrupt nv with production rom

after updating miui the phone refused to boot with courupt nv_data
after reflashing engineering modem and twrp,installing magisk and resetting my imei with qpst my network kind of works.
Wifi, bt work fine, 4g works (assuming 3g also works) but 2g does not.
Any ideas? Maybe the error was somewhere else not the modem, not really sure what to try next?
Should I try flashing the entire rom from edl mode with qfl