Possible fix for IMEI 0 after OTA update? - Moto G5 Plus Questions & Answers

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.

Related

Manual OTA Update process step-by-step (Stock/Rooted/Xposed)

For stock rooted/TWRP users, this is a step-by-step process of manually updating your Moto involving flashing stock firmware, updating, and restoring TWRP, root, and apps afterwards.
Benefits:
**It's really simple- once you get familiar with this process, you can do it fairly quickly.
**Take the time to read through and get everything set up and you'll be set for future updates.
**No begging the internet for flashable zips.
Preface:
So my situation is i'm running stock, bootloader unlocked, rooted, and xposed on my US XT1540 2GB Moto G. I went through the process this morning of updating to the new 23.46.4 update. Thought I'd share what I did for anyone out there wanting to update with questions ; hopefully some can be answered here. I'm familiar with flashing firmware files from my previous Moto X's '13 & '14 so trust me it's not a big deal to flash back stock firmware to update. This process should be applicable to any variant of the Moto G and and to any future updates as well, not just the one mentioned here as of 09/19/15. Just be mindful of your phone's version and use the appropriate firmware.
1) BACKUP
First, make sure everything worth keeping is on your microSD. Flashing stock firmware will wipe your phones internal memory so pictures, music, downloads, SMS, etc need to migrate. Also make sure you have SuperSU and Xposed on your microSD for re-installation. This might be obvious for some and you might have everything going to your microSD (sdcard1, EXTsdcard) already, but one thing you might miss is Titanium Backup...
Save apps in Titanium to microSD: Menu>Preferences>Backup folder location>Click to change>Ext. SD card>Create a new folder>Use current folder
Nandroid in TWRP to microSD: toward the bottom click on "Storage: Internal storage" and choose "Micro SDcard"
If you're super smart, after making that backup you'll copy that to your pc.
2) DOWNLOADS
Get the most recent firmware for your device from lost101's firmware thread (thank him threads like this are so helpful)- http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
Download and install the drivers for you phone, I believe the generic android driver will work but you can also get them from Motorola Device Manager: https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Download mini-sdk.zip, attached to the the bottom of this post. Useful light weight sdk containing adb & fastboot which should cover all your flashing needs. If you're not developing apps, full blown android sdk is bloatware
3) SETTING UP ADB/FASTBOOT
Enable USB debugging in Developer options
Extract mini-sdk.zip to a folder. Extract and add the contents of your firmware to that folder.
Open a cmd prompt on the mini-sdk folder (shift + right click, "Open Command Window Here")
Let's verify that adb sees the device:
Code:
adb devices
Should see "XXserial#XX device". If you get "offline", be sure to check your phone for the adb authorization dialog.
We're ready to flash firmware so reboot into fastboot:
Code:
adb reboot bootloader
4) STOCK FIRMWARE INSTALLATION
Once phone is in fastboot, enter the following commands in the cmd prompt (open on the mini-sdk folder containing the firmware files) one at a time. Let the current flash command finish before entering the next, especially at the img_sparsechunck steps because they take a 10-15 sec each. Also make sure all of the filenames match what you have; substitute accordingly.
Code:
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
5) UPDATE
When you reboot, if you don't get prompted for update check for it- About phone>System updates
Download & install update
When update is finished and phone boots back up, enable Android debugging in developer options.
6) FLASH BACK TWRP/ROOT/XPOSED
Place TWRP img file in mini-sdk folder. Boot back into fastboot and flash TWRP.
Code:
adb reboot bootloader
Code:
fastboot flash recovery twrp-osprey-2.8.7-test1.img
Vol up/down in bootloader to boot recovery.
Once in recovery flash Supersu & xposed (optional of course) from your microSD and reboot.
Install Titanium from play store, go back into preferences and point to backup folder on the microSD and restore apps.
When xposed and modules are reinstalled through Titanium, you will need to reboot to enable. After that you'll need to tweak your preferences in system options like notifications or display, but any settings in modules (like gravity box) will be restored as long as you backed up app+data in TB. Easier than a custom rom clean flash in that aspect.
So that's it, with that you should be back up and running. Let me know if I missed some steps or if you have questions about the process.
*****
BTW, Installing xposed from scratch for those confused on what files to do what with: http://forum.xda-developers.com/show....php?t=3034811
Flash this one in recovery: xposed-v74-sdk22-arm.zip (or most current)
Install this apk after you reboot: XposedInstaller_3.0_alpha4.apk (or most current)
Please Delete
agleroy said:
Thanks for the guide. Still gonna wait for a flashable zip though.
Click to expand...
Click to collapse
You're better than that. Trying to empower you here...
Please Delete
Hey, could you use normal/dark colors? Reading light yellow and blue is difficult, even when highlighting it with a cursor. Thanks!
a.cid said:
Hey, could you use normal/dark colors? Reading light yellow and blue is difficult, even when highlighting it with a cursor. Thanks!
Click to expand...
Click to collapse
I took all the color out and tweaked it a bit. I was using the dark theme and everything looked pretty good, but when I switched to the light theme... yeah annoying.
I'm still trying to decide if I want/need to root, and/or install a custom ROM on this phone. I have always done so on past phones, but this phone runs so well I don't want to mess it up, and I'm not sure the few features I'm missing warrant messing with things.
Thank you the tutorial though. I will certainly keep it for reference.
Sent from my MotoG3 using XDA Free mobile app
Why does every single guide say to erase the userdata partition??? This is totally unnecessary. Instead, boot into twrp and wipe your userdata. The difference is in your internal storage. If you follow the guide you wipe your internal storage in the very last command. My way, you just do a factory reset on the data partition which doesn't wipe the storage
Also, flashing stock recovery is an unnecessary step when it's being immediately replaced by twrp again.
Selmak said:
I'm still trying to decide if I want/need to root, and/or install a custom ROM on this phone. I have always done so on past phones, but this phone runs so well I don't want to mess it up, and I'm not sure the few features I'm missing warrant messing with things.
Thank you the tutorial though. I will certainly keep it for reference.
Sent from my MotoG3 using XDA Free mobile app
Click to expand...
Click to collapse
This isn't a custom rom...it's the official motorola firmware update
Thanks for this guide , it's good to know, but I would have to wait for a flasheable UPDATE.zip because my phone's configuration (XT1543, dual sim, 16gb storage, 1gb ram) doesn't have a stock firmware download link in the main thread... and also I don't want to reinstall my apps , haha.
If it works like the other 2 generations of moto g, and at least with the first moto x (all from my personal experience) just skip the erase userdata part and you'll keep your personnal data.
Ota update will go smoothly, no need to restore anything afterwards except root and recovery, indeed.
A backup is always a good thing, sure just in case, but i never used mine on all the ota's I installed on those 3 phones (moto g 2013 16gb, moto g 2014 and moto x 2013)
I don't own a moto g 2015 but my gf does, a 16gb/2gb ram one, she just got it so she installed the update before rooting. If nobody tries it before I'll try it with the next update .
cannot access filehost to get xt1541 5.1.1 any alternative link?
after I updated to 6.0 my computer is not recognising the device? any solutions?
Please add "fastboot flash system system.img_sparsechunk.6" to the top post. This could prevent idiots from sitting in a boot loop for an hour, while they try furiously to find a way out, an error in the download, revert to a previous firmware... Yeah, that was stressful.
Is this the same for the XT1548 virgin mobile 1G of ram and 8G of memory. I understand that it's probably not the same file I just don't really want to wait for the flashable .Zip. But I also don't want to mess up my only device as of now.
Hey i need help....my xt1550 is unlocked and running on stock 6.0 right now......i have installed custom ROMs and rooted the device before.....but now its unrooted and running stock but iam still not able to recieve ota updates.......why?
csumanth16 said:
Hey i need help....my xt1550 is unlocked and running on stock 6.0 right now......i have installed custom ROMs and rooted the device before.....but now its unrooted and running stock but iam still not able to recieve ota updates.......why?
Click to expand...
Click to collapse
If you have stock recovery and an update touched /boot and /system partition, you can take an OTA update. If you have TWRP, root, or other modification in the mentioned areas you cannot take an OTA update.
Having an unlocked bootloader only is not relevant.
What if you unrooted, a rooted stock recovery device, is it safe to take an OTA?
acejavelin said:
If you have stock recovery and an update touched /boot and /system partition, you can take an OTA update. If you have TWRP, root, or other modification in the mentioned areas you cannot take an OTA update.
Having an unlocked bootloader only is not relevant.
Click to expand...
Click to collapse
MrTooPhone said:
What if you unrooted, a rooted stock recovery device, is it safe to take an OTA?
Click to expand...
Click to collapse
No... If your rooted the /boot partition has been modified.
acejavelin said:
No... If your rooted the /boot partition has been modified.
Click to expand...
Click to collapse
And does it remain notably changed even after going through a full unroot via SuperSU?
MrTooPhone said:
And does it remain notably changed even after going through a full unroot via SuperSU?
Click to expand...
Click to collapse
No, doing a full unroot will return the original /boot partition, but be aware this will not undo any changes you made to /system with root access (such as debloating or Xposed modules), and even if you undo those changes, the Android system has already marked the /system partition as tampered so a check will fail.

Baseband unknown

My nexus 6p is not showing IMEI and also showing unknown for Baseband version. I have no efs backup. Tried reflashing stock firmware, erasing modemst1, modemst2, modem, fsg, custom rom (RR), and tried them in different combinations. Yet it still shown baseband unknown. :crying:
Is there any way I can get modemst1 and modemst2? Please suggest a solution to fix this. Warranty over a week before this happened. And it happened out of nowhere. :crying:
Baseband is the radio, isn't it? You can get the latest image from here:
http://forum.xda-developers.com/nexus-6p/general/nmf26f-official-7-1-1-radio-vendor-t3513430
---------- Post added at 10:53 AM ---------- Previous post was at 10:50 AM ----------
You might want to do a complete install of the latest system image if flashing the radio doesn't solve your problem:
https://developers.google.com/android/images
---------- Post added at 10:58 AM ---------- Previous post was at 10:53 AM ----------
I'm not sure that either of these will restore your IMEI, however. Do you have a CDMA or GSM phone?
jhs39 said:
Baseband is the radio, isn't it? You can get the latest image from here:
http://forum.xda-developers.com/nexus-6p/general/nmf26f-official-7-1-1-radio-vendor-t3513430
---------- Post added at 10:53 AM ---------- Previous post was at 10:50 AM ----------
You might want to do a complete install of the latest system image if flashing the radio doesn't solve your problem:
https://developers.google.com/android/images
---------- Post added at 10:58 AM ---------- Previous post was at 10:53 AM ----------
I'm not sure that either of these will restore your IMEI, however. Do you have a CDMA or GSM phone?
Click to expand...
Click to collapse
Thanks for the reply. I tried both of em. Is there any way i can get fsg, modemst1, modemst2 files? Im thinking of finding another Nexus 6P and copying its files and somehow editing the IMEI information using some HEX editor and then uploading to my phone.
If it is alright then can you or someone send me their modemst1, modemst2 and fsg files after editing their IMEI no. ?
This site provide how to edit your IMEI: androidbrick (Change it to something like 876543210123456)
Btw my phone is LTE/GSM
I think if you can get a hold of someone's EFS backup and restore it on your phone it would restore your missing IMEI number. The problem is finding someone who is willing to provide you with a copy of their EFS backup.
I was able to get the IMEI number for my Nexus 6P from Google Dashboard:
http://www.google.com/settings/dashboard
Once you know your IMEI you may be able to restore it with an app like IMEI Tweak.
jhs39 said:
I think if you can get a hold of someone's EFS backup and restore it on your phone it would restore your missing IMEI number. The problem is finding someone who is willing to provide you with a copy of their EFS backup.
Click to expand...
Click to collapse
Yes. I'm trying to find someone who can provide me with modem files.
jhs39 said:
I was able to get the IMEI number for my Nexus 6P from Google Dashboard:
http://www.google.com/settings/dashboard
Once you know your IMEI you may be able to restore it with an app like IMEI Tweak.
Click to expand...
Click to collapse
I have the box which has the IMEI. I tried some apps like IMEI Tweaks. Even tried some apps through XPOSED framework. Nothing worked. Hope someone gives me the modem files.
pronuba66 said:
My nexus 6p is not showing IMEI and also showing unknown for Baseband version. I have no efs backup. Tried reflashing stock firmware, erasing modemst1, modemst2, modem, fsg, custom rom (RR), and tried them in different combinations. Yet it still shown baseband unknown. :crying:
Is there any way I can get modemst1 and modemst2? Please suggest a solution to fix this. Warranty over a week before this happened. And it happened out of nowhere. :crying:
Click to expand...
Click to collapse
How did you erase modemst1 & modemst2? From an ADB shell like this? I can't find it to save my life, but I did read if the EFS partitions are formatted properly they will rebuild from firmware on first boot. You stated phone is out of warranty, but did you actually get denied when you called Huawei? There may be an unadvertised warranty/RMA for your phone's current state, or they may be able to suggest a fix.
v12xke said:
How did you erase modemst1 & modemst2? From an ADB shell like this? I can't find it to save my life, but I did read if the EFS partitions are formatted properly they will rebuild from firmware on first boot. You stated phone is out of warranty, but did you actually get denied when you called Huawei? There may be an unadvertised warranty/RMA for your phone's current state, or they may be able to suggest a fix.
Click to expand...
Click to collapse
I erased using dd command as stated in your link provided. But even after several reboots, and several uploads of different ROMS, it still is zero (Both modemst1 and modemst2).
My phone was bought from a different country, and hence warranty was not accepted in my country. Even the people at the Huawei service center was not very helpful.
I'm actually waiting for my friend to root his phone(unlocking required which will erase the user data) so that I can get the modem files. If fixed I'll message you.
pronuba66 said:
I erased using dd command as stated in your link provided. But even after several reboots, and several uploads of different ROMS, it still is zero (Both modemst1 and modemst2).
My phone was bought from a different country, and hence warranty was not accepted in my country. Even the people at the Huawei service center was not very helpful.
I'm actually waiting for my friend to root his phone(unlocking required which will erase the user data) so that I can get the modem files. If fixed I'll message you.
Click to expand...
Click to collapse
Good luck.
---------- Post added at 09:17 PM ---------- Previous post was at 09:12 PM ----------
jhs39 said:
Good luck.
Click to expand...
Click to collapse
From what I've read if your friend makes an EFS backup you can use that to restore yours. If the modem restore doesn't work you might want to try that,
pronuba66 said:
I erased using dd command as stated in your link provided. But even after several reboots, and several uploads of different ROMS, it still is zero (Both modemst1 and modemst2).
My phone was bought from a different country, and hence warranty was not accepted in my country. Even the people at the Huawei service center was not very helpful.
I'm actually waiting for my friend to root his phone(unlocking required which will erase the user data) so that I can get the modem files. If fixed I'll message you.
Click to expand...
Click to collapse
Any solution for this? I also have imei unknown, baseband unknown issue. I don't have an efs backup either. Also flashed stock rom, but it didn't help. Any suggestions would be really appreciated.
chathura2020 said:
Any solution for this? I also have imei unknown, baseband unknown issue. I don't have an efs backup either. Also flashed stock rom, but it didn't help. Any suggestions would be really appreciated.
Click to expand...
Click to collapse
Hi,
You can try this:
Find someone having the same firmware. Root his phone and download all the partitions from his phone (from "/dev/block/platform/soc.0/f9824900.sdhci/by-name" using dd command or adb pull (in root mode). To change the IMEI from his to yours, use a hex editor and edit the IMEI in one of the partitions (I think it was in modemst1 or modem or devinfo partition).
I have tried this but my mobile was bought from UAE and Indian firmware did not work. But that fixed some restart issue, heating problem and the phone was more stable which implied the problem was definitely some corrupted partitions.
If you get it fixed please do tell me. Good luck.
Please do keep backup of your partitions
pronuba66 said:
Hi,
You can try this:
Find someone having the same firmware. Root his phone and download all the partitions from his phone (from "/dev/block/platform/soc.0/f9824900.sdhci/by-name" using dd command or adb pull (in root mode). To change the IMEI from his to yours, use a hex editor and edit the IMEI in one of the partitions (I think it was in modemst1 or modem or devinfo partition).
I have tried this but my mobile was bought from UAE and Indian firmware did not work. But that fixed some restart issue, heating problem and the phone was more stable which implied the problem was definitely some corrupted partitions.
If you get it fixed please do tell me. Good luck.
Please do keep backup of your partitions
Click to expand...
Click to collapse
My phone is going through exact same problem. My device was stuck in bootloop I got it fixed from a market place and my device would not show any carrier signals or my imei. How can I get modem files or what is a fix to it? Please help.
hkingpro said:
My phone is going through exact same problem. My device was stuck in bootloop I got it fixed from a market place and my device would not show any carrier signals or my imei. How can I get modem files or what is a fix to it? Please help.
Click to expand...
Click to collapse
In theory the Nexus 6P should rebuild the EFS Partitions if you overwrite them with zeros.
I used the following to fix my 6P back when TWRP v3.0.2-1 had a bug that restored the EFS1 partition to both EFS slots, causing the phone to not boot.
Try this:
Boot your Nexus 6P into TWRP;
Plug the phone into a PC that has ADB tools installed;
Then on PC, open Command Prompt with access to ADB and execute the following commands:
ADB shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst1 bs=16384
and
ADB shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst2 bs=16384
Let me know if this works for you.
defcondev said:
In theory the Nexus 6P should rebuild the EFS Partitions if you overwrite them with zeros.
I used the following to fix my 6P back when TWRP v3.0.2-1 had a bug that restored the EFS1 partition to both EFS slots, causing the phone to not boot.
Try this:
Boot your Nexus 6P into TWRP;
Plug the phone into a PC that has ADB tools installed;
Then on PC, open Command Prompt with access to ADB and execute the following commands:
ADB shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst1 bs=16384
and
ADB shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst2 bs=16384
Let me know if this works for you.
Click to expand...
Click to collapse
THANK YOU SO MUCH FOR YOUR REPLY. I tried this but it did not work for me brother. I have been searching day and night for this but not getting any solution for this. I was browsing Xda the other day and found a thread https://forum.xda-developers.com/nexus-6p/help/lost-imei-sim-error-t3282545 in comments section Tyson568 has shared a link which I think might be EFS modem files? Do you think that can help? If that can how can I flash them?
hkingpro said:
THANK YOU SO MUCH FOR YOUR REPLY. I tried this but it did not work for me brother. I have been searching day and night for this but not getting any solution for this. I was browsing Xda the other day and found a thread https://forum.xda-developers.com/nexus-6p/help/lost-imei-sim-error-t3282545 in comments section Tyson568 has shared a link which I think might be EFS modem files? Do you think that can help? If that can how can I flash them?
Click to expand...
Click to collapse
Have you tried flashing a factory image to your 6P?
If not, I would backup all of your data to a computer and flash a stock factory image to your 6P and see if this resolves the issue.
You can find the images and instructions at the link below under the section titled "angler for Nexus 6P"
Make sure to NOT re-lock the bootloader at this point (just skip that step in the flashing instructions).
Keep in mind, this will remove TWRP from your 6P and revert back to the stock Recovery - keep the stock recovery and boot the 6P fully to see if the issue is resolved. If your IMEI returns, you can then flash TWRP and backup your EFS partitions.
https://developers.google.com/android/images
defcondev said:
Have you tried flashing a factory image to your 6P?
If not, I would backup all of your data to a computer and flash a stock factory image to your 6P and see if this resolves the issue.
You can find the images and instructions at the link below under the section titled "angler for Nexus 6P"
Make sure to NOT re-lock the bootloader at this point (just skip that step in the flashing instructions).
Keep in mind, this will remove TWRP from your 6P and revert back to the stock Recovery - keep the stock recovery and boot the 6P fully to see if the issue is resolved. If your IMEI returns, you can then flash TWRP and backup your EFS partitions.
https://developers.google.com/android/images
Click to expand...
Click to collapse
I tried multiple Images but none of them worked. My phone was bootlooping again and again and then finally I followed this thread. I flashed 8.0 factory image and flashed rest of images suggested by this thread and my phone booted up. I don't know what to do here.
hkingpro said:
I tried multiple Images but none of them worked. My phone was bootlooping again and again and then finally I followed this thread. I flashed 8.0 factory image and flashed rest of images suggested by this thread and my phone booted up. I don't know what to do here.
Click to expand...
Click to collapse
I had same issue on my OnePlus X. I kept backing up and restoring EFS partion everytime I needed a restore which now know not suppose to do. Unknown baseband and no imei. Anyways the way I fixed it was simply booting into bootloader mode, fastboot command window type
"fastboot erase modemst1 "
"fastboot erase modemst2 "
I never tested on my Nexus 6p so use at own risk.

apply OTA to rooted phone?

i have an unlocked rooted but otherwise stock G4P and it has an OTA but fails to install. Is there a full ROM I can apply which won't wipe? Or some other way which is not involving a full wipe?
nigelhealy said:
i have an unlocked rooted but otherwise stock G4P and it has an OTA but fails to install. Is there a full ROM I can apply which won't wipe? Or some other way which is not involving a full wipe?
Click to expand...
Click to collapse
I tried, failed, and eventually gave up. I haven't had the motivation to do a full wipe/flash, but I tried everything else I could think of before giving up.
hp420 said:
I tried, failed, and eventually gave up. I haven't had the motivation to do a full wipe/flash, but I tried everything else I could think of before giving up.
Click to expand...
Click to collapse
Did you tryied reinstall the full stock rom & recovery (through Fastboot) without wipe?
rafaelrgi said:
Did you tryied reinstall the full stock rom & recovery (through Fastboot) without wipe?
Click to expand...
Click to collapse
I had a twrp backup of my system partition, which I restored, then fastboot flashed the stock kernel, and wiped caches. Safetynet passed, but the ota would not flash. It said there was an unexpected change in the system, or something to that affect.
I'm not aware of any true, untouched flashable rom zip available. I suppose it wouldn't take long to make one, I just didn't have one available to me.
hp420 said:
I had a twrp backup of my system partition, which I restored, then fastboot flashed the stock kernel, and wiped caches. Safetynet passed, but the ota would not flash. It said there was an unexpected change in the system, or something to that affect.
I'm not aware of any true, untouched flashable rom zip available. I suppose it wouldn't take long to make one, I just didn't have one available to me.
Click to expand...
Click to collapse
To install the OTA update the stock recovery is required, and Twrp is a custom recovery.... after restore the backup you should reinstall the stock recovery before apply the OTA.
rafaelrgi said:
To install the OTA update the stock recovery is required, and Twrp is a custom recovery.... after restore the backup you should reinstall the stock recovery before apply the OTA.
Click to expand...
Click to collapse
sorry, didn't see you were asking about fastboot. no, I didn't flash the factory image. I didn't want to go that far and didn't really care enough to do a full wipe
Have you tried Magisk? Could potentially work
hp420 said:
I had a twrp backup of my system partition, which I restored, then fastboot flashed the stock kernel, and wiped caches. Safetynet passed, but the ota would not flash. It said there was an unexpected change in the system, or something to that affect.
I'm not aware of any true, untouched flashable rom zip available. I suppose it wouldn't take long to make one, I just didn't have one available to me.
Click to expand...
Click to collapse
A TWRP backup restore doesn't fix the issue. You have to reflash SYSTEM , BOOT(if modified), RECOVERY(if modified), and OEM through fastboot. That is a "block flash," instead of TWRP, which is "file based restore."
apply OTA to rooted phone
Could someone please give me this zip ota moto g4 play I need this file since I thank you.
VR25 said:
A TWRP backup restore doesn't fix the issue. You have to reflash SYSTEM , BOOT(if modified), RECOVERY(if modified), and OEM through fastboot. That is a "block flash," instead of TWRP, which is "file based restore."
Click to expand...
Click to collapse
What about other partitions :
gpt, bootloader, adspso, modem
Must they be restored ?
Just after OTA, is it possible to make a raw image backup with TWRP in R/O mode ?
hamelg said:
What about other partitions :
gpt, bootloader, adspso, modem
Must they be restored ?
Just after OTA, is it possible to make a raw image backup with TWRP in R/O mode ?
Click to expand...
Click to collapse
You only need to restore SYSTEM, OEM, BOOT AND RECOVERY images. That's all you'll ever need. NEVER touch other partitions, unless you are upgrading.
To make RAW image backups of SYSTEM and OEM partitions, use terminal in TWRP
Or "adb shell" from your computer (running as root)
adb shell
ls -al /dev/block/platform/soc/7824900.sdhci/by-name
This command will give you the names of the SYSTEM and OEM partitions of your device, Moto G4 Plus. For example, for Moto Z Play (my device), they are mmcblk0p53 and mmcblk0p51 respectively.
So, the commands would be (again, that's an example for MOTO Z PLAY):
Backup
dd if=/dev/block/mmcblk0p53 of=/sdcard/system.img
dd if=/dev/block/mmcblk0p51 of=/sdcard/oem.img
Restore
dd if=/sdcard/system.img of=/dev/block/mmcblk0p53
dd if=/sdcard/oem.img of=/dev/block/mmcblk0p51
Thanks much VR25.
With your help, I have successfully applied the latest OTA
hamelg said:
Thanks much VR25.
With your help, I have successfully applied the latest OTA
Click to expand...
Click to collapse
Confused. The VR25 guidance is when you had taken a full backup when stock, how to restore back to stock to then apply the OTA. You are describing how to apply the OTA on a rooted device without a pre-rooted backup?
You don't need backups to apply the latest OTA.
Get the stock corresponding to your device.
flash LOGO, SYSTEM, OEM, BOOT AND RECOVERY images.
Apply November OTA
Apply February OTA
I did that without wiping my data.
If you want to avoid reset to stock & apply all OTAs, you must have a binary backup of system partition, not a file based backup (see comment #8).
I asked about this issue here :
https://forum.xda-developers.com/showpost.php?p=72029402&postcount=55
hamelg said:
You don't need backups to apply the latest OTA.
Get the stock corresponding to your device.
flash LOGO, SYSTEM, OEM, BOOT AND RECOVERY images.
Apply November OTA
Apply February OTA
I did that without wiping my data.
If you want to avoid reset to stock & apply all OTAs, you must have a binary backup of system partition, not a file based backup (see comment #8).
I asked about this issue here :
https://forum.xda-developers.com/showpost.php?p=72029402&postcount=55
Click to expand...
Click to collapse
Where is the stock for my device
Where is the OTA for my device
My device is the USA unlocked G4P XT1607
nigelhealy said:
Where is the stock for my device
Where is the OTA for my device
My device is the USA unlocked G4P XT1607
Click to expand...
Click to collapse
Exactly this question, but then the XT1602. Flashed the stock parts, but no message of an OTA and they are nowhere to be found. Or does anyone have latest stock version full ROM?
TheEvilVirus said:
Exactly this question, but then the XT1602. Flashed the stock parts, but no message of an OTA and they are nowhere to be found. Or does anyone have latest stock version full ROM?
Click to expand...
Click to collapse
Yeah, others were just saying too high a level to not actually helpful. As I did this last week I'll tell you now is as step by step as I can to actually try to be helpful.
Firstly you need to know you will wipe data, there's no avoiding it, that I could find so backup everything, that can be a mix of TWRP backup of data to SDCARD external, USB OTG, or Titanium backup to online / SD / OTG. In my case I prefer to simply install everything and configure everything from scratch.
Follow this guide to return to stock.
In my case I'm on Ubuntu Linux desktop, fastboot got a "no permissions" type message so I had to sudo in front.
The stock for your device, well look at your device Status page now before you start, Settings -> About Phone -> it says Software Channel "retus" so when I go to the list of ROMs in the above guide go to mirrors.lolinet.com - firmware - moto - harpia - official - then I went to Retus, you'd go to a different one probably.
Note these are old stock ROMs I think from September so there have been one or two updates since then.
Follow the step by step guide, basically lots of fastboot commands.
The step where it says fastboot oem lock it bawks and say fastboot oem lock begin and that will do another wipe, so given a later fastboot oem unlock would do a 3rd wipe I didn't do the oem lock, I left mine unlocked and that worked fine.
Let it boot, setup, you will then be in an old stock ROM, then if it doesn't offer to do an update, go into Settings, System Updates, and trigger it to look. It will then download and apply a stock OTA ontop of the stock ROM. In my case it was 1 OTA, 1 update, then that that complete. You then are on stock current ROMs.
Then root and whatever you want.
But note, to get to the impending N OTA, you'll probably have to right back to the top here because your rooted Moto G4 Play will likely refuse the future OTA as the system is modified, so you'd have to repeat, return to an old stock ROM and then let it go through the 1 or 2 or 3 OTAs to get to that future release.
Hence you'd be doing the return to stock twice.
If the mirrors could be updated to newer stocks it would bypass the OTA. My other phone - the OnePlus3T they offer mirrors of full ROMs, they are far easier to use because if you are rooted you download the full ROM not just the delta incremental of the change of the OTA, and then you can flash in recovery the full ROM and it ignores the system state, and no wiping of data. The fact the mirror site is out of date is causing the need to wipe so the OTAs work on an unmodified system.
Fortunately I have multiple phones so I can use another for the few hours this all takes.
works great, I just flash it and without wiping data
hamelg said:
You don't need backups to apply the latest OTA.
Get the stock corresponding to your device.
flash LOGO, SYSTEM, OEM, BOOT AND RECOVERY images.
Apply November OTA
Apply February OTA
I did that without wiping my data.
If you want to avoid reset to stock & apply all OTAs, you must have a binary backup of system partition, not a file based backup (see comment #8).
I asked about this issue here :
https://forum.xda-developers.com/showpost.php?p=72029402&postcount=55
Click to expand...
Click to collapse
works great and finally my phone can upgrade the OTA updates:laugh::good:
VR25 said:
To make RAW image backups of SYSTEM and OEM partitions, use terminal in TWRP
Or "adb shell" from your computer (running as root)
...
Restore
dd if=/sdcard/system.img of=/dev/block/mmcblk0p53
dd if=/sdcard/oem.img of=/dev/block/mmcblk0p51
Click to expand...
Click to collapse
Here is time to apply the may OTA MPIS24.241-15.3-21.
I restored the vanilla system.img MPIS24.241-15.3-16 with dd, but it didn't work. The OTA failed with the error "system partition has unexpected content" because the sha1sum was incorrect.
Here is the solution :
Before restoring with dd, you must check "Mount System partition read only" is enable in the MOUNT menu of TWRP.
With TWRP 3.1, you need no more to use dd. Now, the feature "system image backup" is available

Baseband: Not found/Unknown, imei 0... Let's find a definitive solution

XT 1806 here. Well, not long ago I posted about thinking I found a way... well... nothing. followed every single thread on hoy to restore basemand/imei to no avail.
So far what I know is that I was running fine, while trying to make cerberus a system app. The phone rebooted and bam. No more baseband.
Before that, I had done the trick of installing an oreo rom (Validus) and going back to stock. It worked and I got back Baseband on bootloader and then in the OS.
I have backups from my EFS from TWRP and PartitionsManager (modem, modemst1, modemst2 and persist) within the OS. Restoring those was no good. It worked before but not now.
I have bootloader C2.06. Before, I had C2.07. Installing the latest update from https://firmware.center/firmware/Motorola/Moto G5s Plus/Stock/ , being it SANDERS_NPSS26.116-61-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml did nothing to update the bootloader or writing the modem.
So far I have a theory and is that, the phone is not taking flashing to the bootloader and or the modem as it should. I am using a high quality USB cable. Changed cables, too. Also, I think something weird is happening with the bootloader or chip programming. It is the first time I face something as weird as this.
I also think it does not like when you start the phone and reboot it quickly. Forgot its Baseband.
Let's be detailed and share experiences to find a cause and then a solution. I have more than 30 hours spent trying to fix this and it is getting to a scary point.
I lost imei and signal....somehow I don't have my efs backup....tried every combo of ROM to get signals ie. something 2g/3g but nothing happens...
However my baseband is intact
Am on 1686 Indian varient
Q. Will moto z Oreo modem work?? Am planning to give it a try
mohitzr said:
I lost imei and signal....somehow I don't have my efs backup....tried every combo of ROM to get signals ie. something 2g/3g but nothing happens...
However my baseband is intact
Am on 1686 Indian varient
Q. Will moto z Oreo modem work?? Am planning to give it a try
Click to expand...
Click to collapse
Any ideas on what happened when you lost the imei?
Please start in bootloader and see what it says in baseband.
barbaroja said:
XT 1806 here. Well, not long ago I posted about thinking I found a way... well... nothing. followed every single thread on hoy to restore basemand/imei to no avail.
So far what I know is that I was running fine, while trying to make cerberus a system app. The phone rebooted and bam. No more baseband.
Before that, I had done the trick of installing an oreo rom (Validus) and going back to stock. It worked and I got back Baseband on bootloader and then in the OS.
I have backups from my EFS from TWRP and PartitionsManager (modem, modemst1, modemst2 and persist) within the OS. Restoring those was no good. It worked before but not now.
I have bootloader C2.06. Before, I had C2.07. Installing the latest update from https://firmware.center/firmware/Motorola/Moto G5s Plus/Stock/ , being it SANDERS_NPSS26.116-61-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml did nothing to update the bootloader or writing the modem.
So far I have a theory and is that, the phone is not taking flashing to the bootloader and or the modem as it should. I am using a high quality USB cable. Changed cables, too. Also, I think something weird is happening with the bootloader or chip programming. It is the first time I face something as weird as this.
I also think it does not like when you start the phone and reboot it quickly. Forgot its Baseband.
Let's be detailed and share experiences to find a cause and then a solution. I have more than 30 hours spent trying to fix this and it is getting to a scary point.
Click to expand...
Click to collapse
You can start with this
Code:
https://www.androidbrick.com/ultimate-guide-qualcomm-snapdragon-xiaomi-mi5-imei-and-baseband-repair-fix/
and it's sister article part 2. I wrote a how-to on using QFIL to back-up and restore qcn files, and my research started there. However, after seeing how many cannot follow basic instructions to use adb/fastboot and even sometimes twrp, I am not going to post it. Let's just say you can edit the proper baseband components, but it is not going to be download and click to install. You will need the following to get started:
Code:
1.[QPST] https://www.androidbrick.com/download/download-latest-qualcomm-flasher-qfil-qpst-2-7-460/
2.[Qualcomm drivers]https://gsmusbdrivers.com/download/android-qualcomm-usb-driver/
3.[hexeditor]http://www.mitec.cz/hex.html
4.[IMEI convertor]https://androidfilehost.com/?fid=962021903579482959
5.Motorola USB drivers [you probably already have these, if you have used adb/fastboot]
You will also need a knowledgeable donor who is willing and able to donate a working backed up qcn file, of the same make/model, and bootloader must be in same state as yours. Although this will have the IMEI , it can be edited to 0 out all but the first digit of the IMEI and thus be safe for posting without fear of someone cloning it. This method has been done with other qualcomm chipsets, and the ultimate goal would be to get the proper working qcn file disassembled and compared to the faulty ones to see exactly where the basebands are being corrupted by the Oreo roms.
barbaroja said:
Any ideas on what happened when you lost the imei?
Please start in bootloader and see what it says in baseband.
Click to expand...
Click to collapse
i get baseband
[email protected] said:
You can start with this
Code:
https://www.androidbrick.com/ultimate-guide-qualcomm-snapdragon-xiaomi-mi5-imei-and-baseband-repair-fix/
and it's sister article part 2. I wrote a how-to on using QFIL to back-up and restore qcn files, and my research started there. However, after seeing how many cannot follow basic instructions to use adb/fastboot and even sometimes twrp, I am not going to post it. Let's just say you can edit the proper baseband components, but it is not going to be download and click to install. You will need the following to get started:
Code:
1.[QPST] https://www.androidbrick.com/download/download-latest-qualcomm-flasher-qfil-qpst-2-7-460/
2.[Qualcomm drivers]https://gsmusbdrivers.com/download/android-qualcomm-usb-driver/
3.[hexeditor]http://www.mitec.cz/hex.html
4.[IMEI convertor]https://androidfilehost.com/?fid=962021903579482959
5.Motorola USB drivers [you probably already have these, if you have used adb/fastboot]
You will also need a knowledgeable donor who is willing and able to donate a working backed up qcn file, of the same make/model, and bootloader must be in same state as yours. Although this will have the IMEI , it can be edited to 0 out all but the first digit of the IMEI and thus be safe for posting without fear of someone cloning it. This method has been done with other qualcomm chipsets, and the ultimate goal would be to get the proper working qcn file disassembled and compared to the faulty ones to see exactly where the basebands are being corrupted by the Oreo roms.
Click to expand...
Click to collapse
Thanks for sharing. Very interesting, indeed.
In my particular case, it happened for no apparent reason. Quick reboots being a suspect here. It seems some got baseband and no imei, others no baseband at all... Any ideas on this?
dev here.
I've been looking into this problem for quite a while now.
Can anyone briefly summarise the problem? Like what all you flashed?
From my understanding:
efs = modemst1 & modemst2 = baseband cache = created on the fly
important baseband related partitions: modem, fsg, persist
Additionally I'm sharing potter retin (march) firmware files: (Download)
Try flashing this (on stock 7.0):
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash persist persist.img
rachitrawat said:
dev here.
I've been looking into this problem for quite a while now.
Can anyone briefly summarise the problem? Like what all you flashed?
From my understanding:
efs = modemst1 & modemst2 = baseband cache = created on the fly
important baseband related partitions: modem, fsg, persist
Additionally I'm sharing potter retin (march) firmware files: (Download)
Try flashing this (on stock 7.0):
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash persist persist.img
Click to expand...
Click to collapse
Thank you so much.
Can you tell me what is your model no.?
And build no ?
And is this backup is from stock rooted rom.?
Is your device bricked yet,or have you loose IMEI in past.?
akshu2697 said:
Thank you so much.
Can you tell me what is your model no.?
And build no ?
And is this backup is from stock rooted rom.?
Is your device bricked yet,or have you loose IMEI in past.?
Click to expand...
Click to collapse
This a dump of an untouched XT1686 92-8 firmware.
rachitrawat said:
This a dump of an untouched XT1686 92-8 firmware.
Click to expand...
Click to collapse
Can you provide me twrp flashable rom 92-8.?
Because I can't find it anywhere.
akshu2697 said:
Can you provide me twrp flashable rom 92-8.?
Because I can't find it anywhere.
Click to expand...
Click to collapse
There isn't one as there is no 92-8 firmware out there.
Sent from my Moto G5 Plus using XDA Labs
did it worked ? .. im having the same problem .. cant get my network signal and imei
akshu2697 said:
Thank you so much.
Can you tell me what is your model no.?
And build no ?
And is this backup is from stock rooted rom.?
Is your device bricked yet,or have you loose IMEI in past.?
Click to expand...
Click to collapse
im having the same problem with my XT1686 indian version .. can we get it back with other efs backups ?
can we import backups from other mobiles and get the job done ?
Repiix said:
im having the same problem with my XT1686 indian version .. can we get it back with other efs backups ?
can we import backups from other mobiles and get the job done ?
Click to expand...
Click to collapse
I haven't tried it yet,
I will tell you if this work.
rachitrawat said:
dev here.
I've been looking into this problem for quite a while now.
Can anyone briefly summarise the problem? Like what all you flashed?
From my understanding:
efs = modemst1 & modemst2 = baseband cache = created on the fly
important baseband related partitions: modem, fsg, persist
Additionally I'm sharing potter retin (march) firmware files: (Download)
Try flashing this (on stock 7.0):
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash persist persist.img
Click to expand...
Click to collapse
Can you help me how to flash this file..??
Because the non-hlos.bin is of 100 mb while in stock ROM it is of around 75 mb,
So can you describe the method to restore this.
1. my device is xt1686 retin and i lost my imei and volte after reverting back to twrp flashable stock nov security patch from pixel experience oreo rom ....
2. i recovered my imei using #castell93 guide ....
https://forum.xda-developers.com/g5-plus/help/restore-imei-0-moto-g5-xt1687-t3739808
3. then i flashed twrp flashable stock jan security patch but no volte yet....
4. then i got my volte back thanks to akshu2697 guide... and backed up my efs
https://forum.xda-developers.com/g5-plus/how-to/solved-volte-fix-lost-flashing-stock-rom-t3773524
5. for a while i used custom oreo roms... and today i flashed twrp flashable stock jan security patch again and i lost imei =0 .... i have my efs backup so i recovered my efs and got my imei and volte working again..
6. today i downloaded #rachitrawat's twrp system backup file and formatted every thing using twrp and restored the system file and reboot... now i am on stock march security patch and i didnot loose my imei and volte .....
I'm on an oreo rom(no volte). Will i be able to flash stock when the oreo rom is officially released? And hopefully get volte?
Arunxyz said:
1. my device is xt1686 retin and i lost my imei and volte after reverting back to twrp flashable stock nov security patch from pixel experience oreo rom ....
2. i recovered my imei using #castell93 guide ....
https://forum.xda-developers.com/g5-plus/help/restore-imei-0-moto-g5-xt1687-t3739808
3. then i flashed twrp flashable stock jan security patch but no volte yet....
4. then i got my volte back thanks to akshu2697 guide... and backed up my efs
https://forum.xda-developers.com/g5-plus/how-to/solved-volte-fix-lost-flashing-stock-rom-t3773524
5. for a while i used custom oreo roms... and today i flashed twrp flashable stock jan security patch again and i lost imei =0 .... i have my efs backup so i recovered my efs and got my imei and volte working again..
6. today i downloaded #rachitrawat's twrp system backup file and formatted every thing using twrp and restored the system file and reboot... now i am on stock march security patch and i didnot loose my imei and volte .....
Click to expand...
Click to collapse
Which system backup did you restore.???
There are two system backup zip in that folder.
And what if you again flash system with fastboot after restore that backup.????
Is IMEI still there.??
akshu2697 said:
Which system backup did you restore.???
There are two system backup zip in that folder.
And what if you again flash system with fastboot after restore that backup.????
Is IMEI still there.??
Click to expand...
Click to collapse
Extract twrp backup system img zip file and it contains system_img folder...
Copy that folder to twrp backup and then restore...
After restore you don't need to fastboot system..
I didn't try to flash fastboot system
Arunxyz said:
Extract twrp backup system img zip file and it contains system_img folder...
Copy that folder to twrp backup and then restore...
After restore you don't need to fastboot system..
I didn't try to flash fastboot system
Click to expand...
Click to collapse
What if you fastboot flashing and again IMEI goes to 0,..??
Can you try.?
Either flashing system via fastboot or flashing stock ROM with twrp.
akshu2697 said:
Can you help me how to flash this file..??
Because the non-hlos.bin is of 100 mb while in stock ROM it is of around 75 mb,
So can you describe the method to restore this.
Click to expand...
Click to collapse
Code:
fastboot flash modem NON-HLOS.bin
akshu2697 said:
Which system backup did you restore.???
There are two system backup zip in that folder.
And what if you again flash system with fastboot after restore that backup.????
Is IMEI still there.??
Click to expand...
Click to collapse
system.img is a bit perfect backup of /system which will not break dm-verity.
akshu2697 said:
What if you fastboot flashing and again IMEI goes to 0,..??
Can you try.?
Either flashing system via fastboot or flashing stock ROM with twrp.
Click to expand...
Click to collapse
you can restore via twrp or fastboot flash
Edit: fastboot won't work. Need to compress into sparse chunks. Try motofastboot

How do I upgrade to latest firmware after a downgrade (bootloader and GPT confusion)

TL;DR
About two years back I upgraded from Marshmallow to Nougat then downgraded back to Marshmallow but didn't flash GPT or bootloader partitions (full details at the bottom)
I want to upgrade to the latest official stock firmware which I believe is this: https://forum.xda-developers.com/moto-g4-plus/how-to/guide-moto-g4-g4-oreo-soak-test-update-t3871136
But I don't know where to begin.
If I backup my phone with TWRP can I restore back to it (Marhsmallow) if I decide I don't like Oreo?
Appreciate any help
History:
A while back I upgraded from Marshmallow to Nougat using this guide: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
I then Flashed the June (2017) OTA update files
Xposed framework wasn't available for Nougat at the time so I downgraded back to Marshmallow; I believe I used the file XT1642_ATHENE_6.0.1_MPJ24.139-48_cid50_subsidy-DEFAULT_CFC.xml.zip
I THINK I followed this downgrade guide: https://forum.xda-developers.com/moto-g4-plus/how-to/how-to-downgrade-nougat-to-marshmallow-t3487201
But I vaguely remember not flashing the GPT and bootloader partitions (based on the advice of the wonderful echo92 here: https://forum.xda-developers.com/showpost.php?p=73031946&postcount=8) but I can't say for sure
I have a few backups from TWRP (https://imgur.com/a/QzgQNbh) from that time with this file structure: https://i.imgur.com/B2cxQvL.png
I blurred out the 10-character 0KB file - it seems unique but I can't remember what it's for
If you're wanting to downgrade back to Marshmallow at some point in the future, I would recommend you flash the TWRP flashable of OPJ28.111-22 https://forum.xda-developers.com/moto-g4-plus/development/rom-oreo-8-1-0-soak-test-t3873367 This TWRP flashable should update your device mostly to Oreo, but not update your GPT/bootloader partitions (your GPT/bootloader would stay on the same version as you are now). Also, you should be able to roll back using your TWRP backup (though I do not know if you'll have issues with the Oreo modem on your Marshmallow device, so you might want to find the modem/fsg files too for Marshmallow)
We found out subsequently that downgrading firmware does not downgrade your GPT/bootloader (fastboot will complain of security downgrade errors otherwise). This poses a big problem when downgrading and using old OTA updates - old OTA updates corrupt your newer bootloader and hard brick your device. By not updating your GPT/bootloader further, you reduce the number of updates that can damage your device, but again, if you roll back to Marshmallow from your TWRP back up, make sure you do not use OTA updates at all.
you might want to find the modem/fsg files too for Marshmallow
Click to expand...
Click to collapse
Not entirely sure what this means or how I do that.
I have XT1642_ATHENE_6.0.1_MPJ24.139-48_cid50_subsidy-DEFAULT_CFC.xml.zip which contains NON-HLOS.bin and fsg.mbn which I believe are the modem/baseband firmware. I don't really know what to do with them though.
Since I can flash the firmware (zip) directly on the device (and the lack of a recovery.img in the zip) I assume that TWRP stays intact and remains the default recovery?
So, as I understand it, my steps are simply:
Flash TWRP-athene-8.1.0-OPJ28.111-22.zip in TWRP
Flash Magisk stable in TWRP
We found out subsequently that downgrading firmware does not downgrade your GPT/bootloader (fastboot will complain of security downgrade errors otherwise). This poses a big problem when downgrading and using old OTA updates - old OTA updates corrupt your newer bootloader and hard brick your device. By not updating your GPT/bootloader further, you reduce the number of updates that can damage your device, but again, if you roll back to Marshmallow from your TWRP back up, make sure you do not use OTA updates at all.
Click to expand...
Click to collapse
The first part lost me a bit. Are you just saying, "Do not use OTA updates."?
Oh, and thank you very much for the help
tekwarfare said:
Not entirely sure what this means or how I do that.
I have XT1642_ATHENE_6.0.1_MPJ24.139-48_cid50_subsidy-DEFAULT_CFC.xml.zip which contains NON-HLOS.bin and fsg.mbn which I believe are the modem/baseband firmware. I don't really know what to do with them though.
Since I can flash the firmware (zip) directly on the device (and the lack of a recovery.img in the zip) I assume that TWRP stays intact and remains the default recovery?
So, as I understand it, my steps are simply:
Flash TWRP-athene-8.1.0-OPJ28.111-22.zip in TWRP
Flash Magisk stable in TWRP
The first part lost me a bit. Are you just saying, "Do not use OTA updates."?
Oh, and thank you very much for the help
Click to expand...
Click to collapse
1) Pretty much - keep the non-HLOS.bin, and FSG images from your fastboot zip handy. The TWRP flashable of the Oreo firmware contains the modem updates, whilst your TWRP backup likely does not have the modem partition. Thus, if you do downgrade and you get signal issues (don't know of anyone who downgraded from Oreo to Marshmallow, you'd be one of the first) you might have to flash the non-HLOS.bin and FSG via fastboot to downgrade your modem back to Marshmallow. The fastboot commands would be:
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Failing that, you could flash this 64 bit TWRP and back up your EFS from both your Marshmallow and Oreo firmwares: https://forum.xda-developers.com/mo...t/recovery-team-win-recovery-project-t3842903 Then if you do have signal issues, you could try to restore your EFS. Or check out this guide if you have IMEI issues: https://forum.xda-developers.com/moto-g4-plus/how-to/guide-moto-g4-plus-imei0-issue-t3859068
2)With the TWRP flashable - yes, your TWRP should stay intact and those steps sound good. Backup your existing installation beforehand.
3)If you downgrade your device stock Motorola firmware, do not use OTA updates. Else, you may hard brick your device.
Failing that, you could flash this 64 bit TWRP and back up your EFS from both your Marshmallow and Oreo firmwares: https://forum.xda-developers.com/mot...oject-t3842903
Click to expand...
Click to collapse
I've got TWRP 3.1.1-0, that looks like it has new features including the ability to do EFS backups now so I'm fine to overwrite my existing Recovery with the one you linked?
I see there's apps that can do EFS backups too. Why TWRP over them?
Thank you very much for your help with this
tekwarfare said:
I've got TWRP 3.1.1-0, that looks like it has new features including the ability to do EFS backups now so I'm fine to overwrite my existing Recovery with the one you linked?
I see there's apps that can do EFS backups too. Why TWRP over them?
Thank you very much for your help with this
Click to expand...
Click to collapse
Should be okay to overwrite your existing TWRP with the 64 bit version - you can either install in TWRP or flash TWRP via fastboot.
Alternatively, if you want to keep TWRP 3.1.1, then you can boot the 64 bit TWRP from fastboot (using the fastboot command 'fastboot boot <name of TWRP>', without quotes and where <name of TWRP> is the full file name of the 64 bit TWRP, without the arrows), then back up your EFS with the 64 bit TWRP. When you next reboot, you should still have your TWRP 3.1.1.
Not used those apps, so I can't comment, be up to you which approach to use. I've seen members use this TWRP for EFS backup without issue.
Do I need to wipe before flashing this?
Notes for myself in the future:
Updated my phones recovery partition to TWRP 3.2.3-0:
Installed MotorolaDeviceManager_2.5.4.exe
Copied recovery.img to the same directory as fastboot.exe and ran the line:
fastboot flash recovery recovery.img
I did a factory reset in TWRP
Downloaded and copied the zip across a few times but I'm just getting "zip signature verification failed".
tekwarfare said:
I did a factory reset in TWRP
Downloaded and copied the zip across a few times but I'm just getting "zip signature verification failed".
Click to expand...
Click to collapse
Hmm, which TWRP zip did you download? You could always go into TWRP settings and turn off signature verification.
Not sure if you needed to do a factory reset, though always useful when updating (hope you had a backup).
TWRP-athene-8.1.0-OPJ28.111-22.zip like you said. It's the one where AFH is crossed out but GDrive is up
Edit: I disabled zip signature verification (even though I didn't want to) and installed it. Setting things up so will see what works and what doesn't.
Thank you very much for the help
tekwarfare said:
TWRP-athene-8.1.0-OPJ28.111-22.zip like you said. It's the one where AFH is crossed out but GDrive is up
Click to expand...
Click to collapse
That's the right zip - I'd double check the download went okay, though under TWRP settings there should be an option to turn off zip verification. After that, the zip should flash okay.
Installing magisk via TWRP aslo failed the zip signature verification (just disabled the verification to install things from now on)
Managed to get a few things up and running like ViperFX.
Xposed is constantly causing bootloops (soft brick) and I can't seem to fix it. I managed to get EdXposed working with Sand Hook but it slows the system down noticeably; all I want is gravitybox.

Categories

Resources