Database Develop

Won't boot

Went to recovery, tried wiping cache, after about an hour I thought it was just frozen and not doing anything, so I restarted the phone, then went back into recovery and factory reset. Now the M logo appears for a few seconds, then disappears, but the screen buttons are unresponsive. At this point, the only thing I can do is hold the power button and the M screen will come back up, OR I can get into fastboot and everything acts normal until I try rebooting. I've wiped cache and factory reset several more times and the same problem keeps persisting.
Any tips?
Thanx

VooDooCC said:
Went to recovery, tried wiping cache, after about an hour I thought it was just frozen and not doing anything, so I restarted the phone, then went back into recovery and factory reset. Now the M logo appears for a few seconds, then disappears, but the screen buttons are unresponsive. At this point, the only thing I can do is hold the power button and the M screen will come back up, OR I can get into fastboot and everything acts normal until I try rebooting. I've wiped cache and factory reset several more times and the same problem keeps persisting.
Any tips?
Thanx
Click to expand...
Click to collapse
It's entirely possible you are having some kind of hardware failure, but as we can't help you fix that let's focus on software for now.
Is your bootloader unlocked and do you have TWRP recovery? If you have TWRP, have you tried to restore any backups of your system?
Have you tried reflashing firmware, either lastest stock via ADB or custom ROM? (choice depending on whether your bootloader is unlocked or not)

bootloader is locked, everything is stock.

VooDooCC said:
bootloader is locked, everything is stock.
Click to expand...
Click to collapse
do you have TWRP installed? If so, do you have a backup you can restore?
If not, then reflash latest firmware (either via TWRP or via ADB).

ChazzMatt said:
do you have TWRP installed? If so, do you have a backup you can restore?
If not, then reflash latest firmware (either via TWRP or via ADB).
Click to expand...
Click to collapse
TWRP is not installed. Is there a guide somewhere how to reflash? Everything I have found is for a normally working phone.

VooDooCC said:
TWRP is not installed. Is there a guide somewhere how to reflash? Everything I have found is for a normally working phone.
Click to expand...
Click to collapse
See section 0 (zero) of this thread.
[GUIDE] How to unlock your bootloader, install TWRP and gain root access
https://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684
[FXZ] Official Stock Firmware 6.0.1 MCG24.251-5-5
https://forum.xda-developers.com/dr...-official-stock-firmware-6-0-1-mcg24-t3569334
realbbb said:
Flash with RSD or FASTBOOT.
BUILD REQUEST INFO:
SW Version: quark_verizon-user 6.0.1 MCG24.251-5-5 5 release-keysMDM9625_41.51.07.22.04R
MBM Version: 70.96
Modem Version: MDM9625_41.51.07.22.04R
FSG Version: UNKNOWN
Build Fingerprint: motorola/quark_verizon/quark:6.0.1/MCG24.251-5-5/5:user/release-keys
VERSION INFO FOUND UNDER 'ABOUT PHONE' SCREEN:
System Version: 24.91.5.quark_verizon.verizon.en.US
Model number: DROID TURBO
Android Version: 6.0.1
Baseband Version: MDM9625_41.51.07.22.04R
Build Number: MCG24.251-5-5
Build Date: Mon Jan 30 08:40:14 CST 2017
OTHER MISC VERSION INFO:
Subsidy Lock Config: slcf_rev_b_default_v1.0.nvm
Regulatory Info (eLabel): None
Blur Version: Blur_Version.24.91.5.quark_verizon.verizon.en.US
Version when read from CPV: quark_verizon-user 6.0.1 MCG24.251-5-5 5 release-keys
QUARK_VERIZON_6.0.1_MCG24.251-5-5_cid2_subsidy-DEFAULT_CFC.xml.zip
Download Link : https://mega.nz/#!dd4wXYiI!sRgo3aathlCDcg4YqBLxrRrd2ZK4u8BbnvHSCDoP7hE
SHA1 hash : 723f1d2b40f21343ecd87ebf4bb36c0f921e01e3
Recovery Only
Download Link : https://mega.nz/#!EFZFRKoC!G62yatqnQMJI4lEFZPlYHtMEIvUCgLYBjFE-p5uZ4Tw
SHA1 hash : 670b3830bc990f78a223273a99b42b9b9d5c74c8
Radio Only
Download Link : https://mega.nz/#!pJIFGCpS!CbyB1S3kDUKvh81-TjcDB-f_TKaP1XFSiN7JISwDU0o
SHA1 hash : 4eaea2d55f5fab1048b78598500d47c4fd3ca063
BBB
Threw Nead
Click to expand...
Click to collapse

Edit 1: Read faster than I was understanding. Trying it now.
Edit 2: Didn't understand how to flash the one you linked, so I used the one supplied in the guide and flashed everything. Still getting the same issue though.

VooDooCC said:
bootloader is locked, everything is stock.
Click to expand...
Click to collapse
whoa, I somehow mis-read this. Your bootloader is locked? Do you want to unlock your bootloader? If so, if you do not have the latest firmware, then don't flash the latest firmware. Ignore my last post.
However, if you are already on the latest firmware, then you can't unlock your bootloader anyway, so you might as well re-flash that firmware to fix whatever is corrupted.
---------- Post added at 02:56 PM ---------- Previous post was at 02:54 PM ----------
VooDooCC said:
Read faster than I was understanding. Trying it now.
Click to expand...
Click to collapse
I read too fast also. I thought your bootloader was UNlocked and you were still stock.
What firmware were you on before you had this trouble?
If you were on the very latest already, then you can't flash that firmware in that thread -- because you can't downgrade with a locked bootloader. You can only flash same version or higher.

I assume I was on the latest, at least I know I didn't have any pending OTA's
Sorry for being a bit ignorant on this, I told myself with this one I was just going to leave everything alone and not unlock or do anything like I did on all my others.

VooDooCC said:
I assume I was on the latest, at least I know I didn't have any pending OTA's
Sorry for being a bit ignorant on this, I told myself with this one I was just going to leave everything alone and not unlock or do anything like I did on all my others.
Click to expand...
Click to collapse
OK, let's assume you were on the latest already.
With these instructions below, on step 4 instead of the link he provides you would use the link I provided (which is the very latest firmware). @TheSt33v's goal for this thread is to unlock the bootloader -- and these instructions were originally intended to get users with older firmware to upgrade and install the very last version firmware that could be unlocked with Sunshine. We are re-purposing the instructions to get you to re-flash the latest firmware on your phone, hoping that will fix any corruption issue.
TheSt33v said:
Section 0: Installing Firmware Version MCG24.251-5 (instead you would be installing Official Stock Firmware 6.0.1 MCG24.251-5-5. Note the extra "5" on the end. It's the very latest stock firmware, but cannot be unlocked as of this date by Sunshine.)
1. Go to Settings -> About phone -> Build number. If it says SU4TL-44, SU4TL-49 or MCG24.251-5, skip to section 1 of this guide. If it says MCG24.251-5-5, you are probably out of luck. This guide will not work for you. If it says anything else, continue reading.
Flashing MCG24.251-5 using this method will erase all of your data. Back up any important files/information before proceeding.
2. Download and install Minimal ADB and Fastboot from here: http://forum.xda-developers.com/showthread.php?t=2317790.
3. Download and install the Motorola Device Manager from here: https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
4. Download the MCG24.251-5 firmware package from here: https://www.androidfilehost.com/?fid=889764386195901169
(instead download THIS VERSION: Official Stock Firmware 6.0.1 MCG24.251-5-5)
5. Extract the contents of the MCG24.251-5 firmware package to the installation directory of Minimal ADB and Fastboot (C:\Program Files (x86)\Minimal ADB and Fastboot on any 64-bit installation of Windows). (INSTEAD you would extract the firmware version I linked to.)
6. Power off your phone.
7. Hold down the volume down button and power on your phone. Release the volume down button when you see that the phone has booted into bootloader mode. You'll see a dead green android.
8. Plug the phone into your computer.
9. Open the Minimal ADB and Fastboot shortcut on your desktop. This will open a command prompt.
10. Type "fastboot devices" and press enter. If it displays your device's serial number, you're ready to go. If it displays nothing, your computer is not recognizing your device properly.
11. Navigate to the installation directory of Minimal ADB and Fastboot and double click on FlashAll.bat. This will flash MCG24.251-5 to your device and erase all of your data. (This will instead install MCG24.251-5-5 if you downloaded that version, but yes it will erase all your data.)
12. Use the power button to select Start in the bootloader menu to boot normally.
13. Set up your phone at least to the point where you can install apps if you want to.
Click to expand...
Click to collapse

ChazzMatt said:
OK, let's assume you were on the latest already.
With these instructions below, on step 4 instead of the link he provides you would use the link I provided (which is the very latest firmware). @TheSt33v's goal for this thread is to unlock the bootloader -- and these instructions were originally intended to get users with older firmware to upgrade and install the very last version firmware that could be unlocked with Sunshine. We are re-purposing the instructions to get you to re-flash the latest firmware on your phone, hoping that will fix any corruption issue.
Click to expand...
Click to collapse
The blue link you provided in that post doesn't work. Assuming it's the same that you provided a few posts earlier, there is no flashall.bat file.

VooDooCC said:
The blue link you provided in that post doesn't work. Assuming it's the same that you provided a few posts earlier, there is no flashall.bat file.
Click to expand...
Click to collapse
I fixed the download link, so should work now.
As for the bat.file, I don't know.
I searched and found some more download versions, like this:
https://easy-firmware.com/index.php?a=browse&b=file-info&id=80611

Sweet Sassafrass, it works! I simply copied the .bat file from the -5 zip to the -5-5 (newest FW) took almost 5 minutes on the Droid splash screen, but it's alive. Thank you so much @ChazzMatt for all your help.

Unroot and Lock Bootloader

I have TWRP and magisk installed.
I want to update to latest firmware and lock the bootloader so that no message appear on startup and I can receive future updates.
How to do this ?
If I update directly from updater, it doesn't work and gets cancelled automatically.
Please let me know.

nik_123 said:
I have TWRP and magisk installed.
I want to update to latest firmware and lock the bootloader so that no message appear on startup and I can receive future updates.
How to do this ?
If I update directly from updater, it doesn't work and gets cancelled automatically.
Please let me know.
Click to expand...
Click to collapse
You can do this but you still won't get back your waranty.
You need to download the latest firmware from firmware finder and flash them(all 3 zip files)
FIRST ENABLE OEM UNLOCKING FROM DEVELOPER SETTINGS
So in short use HuRupdater.
Here's a link to an archive that has all 3 files of the latest update extract it and you'll get 3 files.
https://forum.xda-developers.com/showpost.php?p=77704176&postcount=38
You need to rename the files accordingly, check the HuRupdater thread for details
https://www.google.co.in/amp/s/foru...lash-official-firmware-recovery-t3769279/amp/
Flash the HuRupdater file from TWRP. Don't put recovery image with the files(you'll understand after reading the HuRupdater thread) since you want to go complete stock.
After flashing relock your bootloader:
First at boot, hold the volume up button to get in the e-recovery. Then do a factory reset. Then go into fastboot mode (shutdown the device, holddown the volume down button and plug in USB) and use this code to relock bootloader.
FASTBOOT OEM RELOCK YOUR CODE
ITS IMPORTANT TO KEEP OEM UNLOCK ENABLED IN DEVELOPER SETTINGS BEFORE DOING ANYTHING.
(this'll surely work but incase you screw up remember YOU SCREWED UP)
Hit that thanks button if it works.?

Can't OTA update after downgrade to Oreo

hey,
so i had bought this phone and updated to android pie immediately. I wanted to install gcam so I unlocked bootloader, booted twrp (without flashing just booting) and ran the adb commands. But gcam app still kept crashing. I read somewhere that this method didnt work in pie so I ran Fastboot flashing unlock_critical and downgraded to oreo september update using miflash tool.
After everything was done, I immediately tried updating to November security patch update and after the update downloads, the installation fails (saying "installation problem" ). I dont believe I have updated any system or boot partitions doing these steps.
Anybody know what's wrong and/or how I can get it working?
Thanks

Fastboot oem unlock
Fastboot flashing uock
Just to be sure, then try flashing 9.6.16 again

thanks for your reply @Nebrassy. i had downgraded to 9.6.15 because i couldnt find the link to 9.6.16 image. But even after unlocking and reflashing stock image, i cant update via OTA. My OTA updates are still failing

http://en.miui.com/getrom-353.html

Nebrassy said:
http://en.miui.com/getrom-353.html
Click to expand...
Click to collapse
ok thanks will try this

Help to update rooted Nokia 8

So, I rooted my device following this https://forum.xda-developers.com/nokia-8/how-to/guide-how-to-root-nokia-8-ability-to-t3848390, but I cannot update my nokia...
The only thing I did different was that I had to rollback my device (with this guide) to June update, and then proceed accordingly.
When I try to update now, I keep getting an error on the update: "Couldn't update. Installation problem".
Can someone please help me? I am ok with both manual or automatic updates, but I need to update.

You only need to flash the stock (untouched) version of the boot partition to the active slot with relevant patch, which is June version at your occasion. Go to this page: https://forum.xda-developers.com/nokia-8/development/nb01-stock-boot-imgs-fixing-wifi-t3854310
***
Edit: See my second post.
Also there is magisk uninstall feature, which you can restore the partition to stock and update and then magisk-root the inactive partition (newly installed system).
I have not upraded my phone, yet. That is, I didn't try anything I mentioned here.
Click to expand...
Click to collapse

Dr. Slump said:
You only need to flash the stock (untouched) version of the boot partition to the active slot with relevant patch, which is June version at your occasion. Go to this page: https://forum.xda-developers.com/nokia-8/development/nb01-stock-boot-imgs-fixing-wifi-t3854310
Click to expand...
Click to collapse
Thanks, I'm in the same situation, unlocked bootloader and rooted on the October patch, do I flash the stock Oct patch and then update via OTA?
Thanks!

vonManstein said:
Thanks, I'm in the same situation, unlocked bootloader and rooted on the October patch, do I flash the stock Oct patch and then update via OTA?
Thanks!
Click to expand...
Click to collapse
That is right. You are welcome.
Also there is magisk uninstall feature, which you can restore the partition to stock and update and then magisk-root the inactive partition (newly installed system).
I have not upraded my phone, yet. That is, I didn't try anything I mentioned here. You may verify the ideas by wandering at some topics like that:
https://forum.xda-developers.com/nokia-8/how-to/guide-how-to-root-nokia-8-ability-to-t3848390

Dr. Slump said:
You only need to flash the stock (untouched) version of the boot partition to the active slot with relevant patch, which is June version at your occasion. Go to this page: https://forum.xda-developers.com/nokia-8/development/nb01-stock-boot-imgs-fixing-wifi-t3854310
***
Edit: See my second post.
Click to expand...
Click to collapse
The magisk uninstall have not worked, the same error persists... I'm gonna try the first method you mentioned, and will be back with results, thanks!
Edit: also, could you please provide steps for doing that?
Not sure if supposed to do that through Nokia software, twrp or fastboot.
Thanks again

guideo said:
The magisk uninstall have not worked, the same error persists... I'm gonna try the first method you mentioned, and will be back with results, thanks!
Edit: also, could you please provide steps for doing that?
Not sure if supposed to do that through Nokia software, twrp or fastboot.
Thanks again
Click to expand...
Click to collapse
It is "fastboot flash". It seems OK. This is what I will do if magisk uninstall doesn't work for me. But, again, you should know that I have not tried this yet.
Also, if your plan is to upgrade to pie, AFAIK there is some preliminary problems with it. They are mentioned in relevant topics here. I think it is better to wait for a better version.

Dr. Slump said:
It is "fastboot flash". It seems OK. This is what I will do if magisk uninstall doesn't work for me. But, again, you should know that I have not tried this yet.
Also, if your plan is to upgrade to pie, AFAIK there is some preliminary problems with it. They are mentioned in relevant topics here. I think it is better to wait for a better version.
Click to expand...
Click to collapse
Hi, thanks for the help.
The command fastboot flash boot "june.img" worked, but now I can't turn on my WiFi... It turns on then off again on its own...
Im gonna tinker around a little with it, but probably be back on the 25th or 26th, due to xmas.
Thanks a lot and merry christmas to you

Worked with may patch...
I think that my device was trying to apply the June patch, and so it was in may patch.
Ive installed it and now the update is ongoing.
Gonna try to re-root it after the holidays
I'm not going to apply the pie update, gonna wait for a while.
Thanks a lot man! You saved my device :laugh:

guideo said:
Worked with may patch...
I think that my device was trying to apply the June patch, and so it was in may patch.
Ive installed it and now the update is ongoing.
Gonna try to re-root it after the holidays
I'm not going to apply the pie update, gonna wait for a while.
Thanks a lot man! You saved my device :laugh:
Click to expand...
Click to collapse
I just got to the september update (should have stopped in august), but now I cannot root my device... TWRP wont boot, neither the prerooted september image.
If you have any idea about this, I would really appreciate! Thanks!

guideo said:
I just got to the september update (should have stopped in august), but now I cannot root my device... TWRP wont boot, neither the prerooted september image.
If you have any idea about this, I would really appreciate! Thanks!
Click to expand...
Click to collapse
Thanks, marry christmas to you, too. TWRP won't work because there isn't a dedicated recovery partition anymore, it was patched into boot partition and wiped out with the flashing
If you are trying the prerooted boot image with "fastboot boot", it is broken after the august update. If not, maybe it is better to download the stock image to /sdcard and patch it with your latest magisk, later upload it to computer and "fastboot flash" it.

So guys any way to root official pie with december security patch?

nabil427 said:
So guys any way to root official pie with december security patch?
Click to expand...
Click to collapse
You can find a twrp-prepatched boot image for Pie + December Patch here: https://cloud.tmsp.io/s/nb1?path=/Boot Images/2018-12
Enter download mode and use fastboot to flash it into your active boot partition (either boot_a or boot_b, depending on the output of "fastboot getvar current-slot").
Then boot into recovery mode (using adb reboot recovery, or by shutting the phone down and pressing volume up while connecting it to the PC) and flash the Magisk installer .zip

THMSP said:
You can find a twrp-prepatched boot image for Pie + December Patch here: https://cloud.tmsp.io/s/nb1?path=/Boot Images/2018-12
Enter download mode and use fastboot to flash it into your active boot partition (either boot_a or boot_b, depending on the output of "fastboot getvar current-slot").
Then boot into recovery mode (using adb reboot recovery, or by shutting the phone down and pressing volume up while connecting it to the PC) and flash the Magisk installer .zip
Click to expand...
Click to collapse
Hi,
thank you for your help but i'm stuck in boot here are the commands I did:
C:\Program Files (x86)\Minimal ADB and Fastboot> .\fastboot.exe getvar current-
slot
current-slot: b
PS C:\Program Files (x86)\Minimal ADB and Fastboot> .\fastboot.exe boot twrp-3.2.3
-1-NB1.img --slot=b
downloading 'boot.img'...
OKAY [ 0.127s]
booting...
OKAY [ 5.208s]
finished. total time: 5.337s
I've also tried to boot on TWRP 3.2.3-1 but same issue I could not boot onto it and then flash it.
Any Idea ?
Regards
>> Hi, never mind working OK thx

Dr. Slump said:
Thanks, marry christmas to you, too. TWRP won't work because there isn't a dedicated recovery partition anymore, it was patched into boot partition and wiped out with the flashing
If you are trying the prerooted boot image with "fastboot boot", it is broken after the august update. If not, maybe it is better to download the stock image to /sdcard and patch it with your latest magisk, later upload it to computer and "fastboot flash" it.
Click to expand...
Click to collapse
This worked for me with September boot. Just did what you said and then "fastboot flash boot patched_boot.img".
Thanks again

Restoring OTA for stock

Is there a way to restore my stock rooted phone to allow updated the latest stock OTA updates without having to reflash the whole previous stock ROM? With my previous MOT phones (Moto 2, Moto 3, Moto 4) all I had to do was restore stock recovery and logo and then reboot to allow OTA updates. But since there is no recovery.img in this phone's ROM xml then that option is out. It would be nice not have to restore everything from scratch in order to get the updates.

pastorbob62 said:
Is there a way to restore my stock rooted phone to allow updated the latest stock OTA updates without having to reflash the whole previous stock ROM? With my previous MOT phones (Moto 2, Moto 3, Moto 4) all I had to do was restore stock recovery and logo and then reboot to allow OTA updates. But since there is no recovery.img in this phone's ROM xml then that option is out. It would be nice not have to restore everything from scratch in order to get the updates.
Click to expand...
Click to collapse
Yup, If you are just rooted stock and have NOT installed the copy partions.ZIP... Boot to TWRP From FASTBOOT BACKUP your DATA to flash back after Install...Just the Data and install Magisk Uninstaller... After MAGISK unistall... Format DATA PARTITION ONLY...MAKE SURE YOU ARE ON BOOT SLOT A... Reboot to the SETUP WIZARD... STOP and reboot to bootloader.......HAVE STOCK BOOT IMG READY TO BOOT FROM CURRENT FIRMWARE... The STOCK installed boot img has the bootloader and modified devices flagged so that kills the OTA INSTALLATION.... If you have installed any modded logo.bin you have to replace it with STOCK on both logo_a and logo_b
fastboot --set-active=a
fastboot flash logo_a logo.bin
fastboot flash logo_b logo.bin
fastboot boot boot.img
DONT FLASH BOOT
it will trick the flags from trippin that stop the OTA
Setup the phone from setup wizard and it should automatically update the OTA so really its two updates....
Once its done reinstall TWRP and TWRP restore data then install Magisk reboot to your data rooted stock updated OTA

KtownJeff said:
Yup, If you are just rooted stock and have NOT installed the copy partions.ZIP... Boot to TWRP From FASTBOOT BACKUP your DATA to flash back after Install...Just the Data and install Magisk Uninstaller... After MAGISK unistall... Format DATA PARTITION ONLY...MAKE SURE YOU ARE ON BOOT SLOT A... Reboot to the SETUP WIZARD... STOP and reboot to bootloader.......HAVE STOCK BOOT IMG READY TO BOOT FROM CURRENT FIRMWARE... The STOCK installed boot img has the bootloader and modified devices flagged so that kills the OTA INSTALLATION.... If you have installed any modded logo.bin you have to replace it with STOCK on both logo_a and logo_b
fastboot --set-active=a
fastboot flash logo_a logo.bin
fastboot flash logo_b logo.bin
fastboot boot boot.img
DONT FLASH BOOT
it will trick the flags from trippin that stop the OTA
Setup the phone from setup wizard and it should automatically update the OTA so really its two updates....
Once its done reinstall TWRP and TWRP restore data then install Magisk reboot to your data rooted stock updated OTA
Click to expand...
Click to collapse
Thanks KtownJeff, that does sound much easier. Why aren't others posting this much simpler solution? Has anyone else tried this?
I haven't tried it yet as it looks like they may be about to figure out the low call volume issue in custom ROMs and then these OTA updates won't be necessary anyway? I'll wait and see what happens over the next week or so.
I'm wondering why it's necessary to wipe the data though. Why isn't uninstalling Magisk and booting with the original kernel enough?

JerseyChewi said:
Yeah the calling issue is just a lineage thing...and lineage is so generically lame. mokee or corvusos are my favs. Most of the custom Roms work well.... and there is a lot more ROMS for our device that is not on XDA.... The Data may be fine Just back it up first....and I put this on telegram and if you haven't checked it out there is five channels for our phone with tons of stuff.....more ROM builds We also have Pitch Black Recovery now available which is twrp with a cleaner UI and lots more options
Click to expand...
Click to collapse

KtownJeff said:
Yup, If you are just rooted stock and have NOT installed the copy partions.ZIP... Boot to TWRP From FASTBOOT BACKUP your DATA to flash back after Install...Just the Data and install Magisk Uninstaller... After MAGISK unistall... Format DATA PARTITION ONLY...MAKE SURE YOU ARE ON BOOT SLOT A... Reboot to the SETUP WIZARD... STOP and reboot to bootloader.......HAVE STOCK BOOT IMG READY TO BOOT FROM CURRENT FIRMWARE... The STOCK installed boot img has the bootloader and modified devices flagged so that kills the OTA INSTALLATION.... If you have installed any modded logo.bin you have to replace it with STOCK on both logo_a and logo_b
fastboot --set-active=a
fastboot flash logo_a logo.bin
fastboot flash logo_b logo.bin
fastboot boot boot.img
DONT FLASH BOOT
it will trick the flags from trippin that stop the OTA
Setup the phone from setup wizard and it should automatically update the OTA so really its two updates....
Once its done reinstall TWRP and TWRP restore data then install Magisk reboot to your data rooted stock updated OTA
Click to expand...
Click to collapse
WHHAAAT?? I got a few questions...
Why is it important not to have the copy-partitions.zip installed?
Why you should be on slot _a?
There is no need to boot the boot.img instead of flashing it. The Magisk uninstaller restores exactly the same boot.img as you can find in the firmware zip. Your device isn't able to store any data on that image.
Sorry, but this is the most complicate way for an OTA I have ever red. You could sum up these steps to "flash the stock firmware". In the end the result is the same. But it's much easier.

WoKoschekk said:
There is no need to boot the boot.img instead of flashing it. The Magisk uninstaller restores exactly the same boot.img as you can find in the firmware zip. Your device isn't able to store any data on that image.
Click to expand...
Click to collapse
Sooo... assuming you haven't changed the logo then all you need to do is uninstall Magisk? Why do you need to flash the stock firmware then?
WoKoschekk said:
Sorry, but this is the most complicate way for an OTA I have ever red. You could sum up these steps to "flash the stock firmware". In the end the result is the same. But it's much easier.
Click to expand...
Click to collapse
It seems a lot less risky to me. Flashing all those different partitions makes me nervous.

JerseyChewi said:
Sooo... assuming you haven't changed the logo then all you need to do is uninstall Magisk? Why do you need to flash the stock firmware then?
Click to expand...
Click to collapse
Assuming this is not your first time flashing the firmware and you already have a flash script/.bat file:
1. run the script
Done! One command and 5 min later you are on the latest firmware.
JerseyChewi said:
It seems a lot less risky to me. Flashing all those different partitions makes me nervous.
Click to expand...
Click to collapse
Motorola provides you OEM signed images and a .xml sheet with proper commands to flash them as a .zip file. I've never heard that someone bricked his device by using the manufacturer's recommended way. I think it's risky to use your own workaround just because you're nervous about it.
Even if you unplug the device in the middle of the flashing process you won't face any trouble. Every single flashing command loads the image into your device's RAM before it gets written to the device.
fastboot oem fb_mode_set = no matter what reboot command you run your device boots into bootloader
Why are you nervous about it?

Why is it important not to have the copy-partitions.zip installed?
Ok so the copy partitons zip is only supposed to be installed when you install the first custom rom coming from original stock..... because it breaks the chain for OTA from motorola.... If you root stock and flash recovery only Its not necessary.... so that way when OTA comes it will move to the B partition the way that it was intended to.....but the boot-loader is unlocked now both slots start with a boot-loader, bootloader_a and bootloader_b.. .and the on board preboot chip will trip the first flag that communicates with stock flashed boot image which also holds the recovery and the kernel... even if its backed up stock.img with magisk, it will break the next flag on the device along with the custom logo.bin.... now the custom logo if it is cloned with a moto signature official it wont matter and the only one Im aware is logo.bin for the TMOBILE REVVLY variant.... when you boot not flash the stock boot.img it bypasses the security chain until reboot.... I've flashed b slot on accident and then booted several GSI and other lake Roms and at some point ill notice on the bootloader screen that maybe i have April 2020 when Im running July 2020 version....which is headache to fix and i booted to b slot flash stock as normal let boot to the setup wizard then reverse to a and do it again because it brings it back together... now the mapping for the AB partition with duel slots t is standard for all ARM64 AB devices Bootloader a and b Boot a and b Radio a and b which is (firmeware) slot Vendor a and b System a and b....
https://www.xda-developers.com/how-...ess-updates-affect-custom-development-on-xda/
the reason why I wrote it the way that I did was because I tried everything to OTA back and this was the only way it worked for me.... and trust me I stayed up for weeks trying to break it or fix it....I finally I came across a moto g6 thread where some one relocked there bootloader and didnt have the oem unlock set and they couldnt do anything to unlock it again using fastboot because the switch was grey out on developer options which means they couldnt root to fix..., I believe it was Sd_shadow that recommended trying to boot the boot.img like how we boot the twrp.img because it bypasses the security flag... well my first attempt it didn't work which led me to the mismatched boot-loaders and I kept at it and by process of elimination and fully learning the way these partitions communicate..... which is totally backwards from the way it used to be... If u leave data then flash back stock, the boot-loader thinks its fresh but finds its not......so boot-loop... tried it cussed and tried again and screamed but now its automatic. for me because of trial and error... I've been at this a few years now and I'm learning something new all the time and most of time when people don't post is because they either don't know or don't wanna give wrong info or maybe nobody showed them. There kinda is an unwritten bylaw at XDA (tough love)... you gotta learn by experience that way when get an opportunity to help or find a new way it makes it worth the stress
That is why I wrote it the way I did step by step in the easiest way possible because of my experiences and headaches...If it don't work you didn't follow directions.... Now I'm gonna tell you I re-locked my bootloader too and was not able to flash back ota don't even try its a waste of time because the only way to get that flag back is to re ball a chipset, or replace the motherboard, or buy a new phone....
Quoteriginally Posted by WoKoschekk
Sorry, but this is the most complicate way for an OTA I have ever red. You could sum up these steps to "flash the stock firmware". In the end the result is the same. But it's much easier.
I
Our device is unbreakable... trust me I've tried to and still haven't managed to Qualcomm brick it.... test point is the only way to get it to EDL mode and i plan on taking my screen off tonight just to see if I can..... and write another essay because some ass hole from Germany thinks he know everthing

KtownJeff said:
Why is it important not to have the copy-partitions.zip installed?
Ok so the copy partitons zip is only supposed to be installed when you install the first custom rom coming from original stock..... because it breaks the chain for OTA from motorola.... If you root stock and flash recovery only Its not necessary....
Click to expand...
Click to collapse
First of all the copy-partions.zip is a simple dd command script packed with flashize to flash it through TWRP. It determines the active slot and copies your essential partitions to the inactive one in case they were left blank by your manufacturer. You should have a look inside it.
Also there is no complicated chain of safety for OTAs. When a device powers on, the bootloader first checks if a device is locked or unlocked. If a device is unlocked, the bootloader shows the user a warning and then proceeds to boot even if the loaded OS isn't signed by the root of trust.
If the device is locked, the bootloader goes through the steps in Verifying Boot to verify the device's software.
Magisk hides the unlock state to pretend a trustworthy environment. That's the reason why OEM unlocking option is active and OTA updates start to install. But OTA update files verify your system's integrity by calculating checksums for each partition. This check fails with a active Magisk installation and update process ends with an error.
A preboot chip or sth like this is not in use on Moto devices. Partitions 1-14 (+/-) are defined as your bootloader. A prebootloader does only exist for MediaTek devices but not for SnapDragon.
There's a lot of official documentation about all the stuff...
In my opinion the easiest way to update your device is to flash the stock ROM. One script and it's done. No need to flash this and boot that only to be able to download the OTA which hasn't been installed until then. Your system takes more time to flash the OTA update then fastboot takes to flash the firmware.
BTW: You can call me what you want but that doesn't make your statements right either.

WoKoschekk said:
First of all the copy-partions.zip is a simple dd command script packed with flashize to flash it through TWRP. It determines the active slot and copies your essential partitions to the inactive one in case they were left blank by your manufacturer. You should have a look inside it.
Also there is no complicated chain of safety for OTAs. When a device powers on, the bootloader first checks if a device is locked or unlocked. If a device is unlocked, the bootloader shows the user a warning and then proceeds to boot even if the loaded OS isn't signed by the root of trust.
If the device is locked, the bootloader goes through the steps in Verifying Boot to verify the device's software.
Magisk hides the unlock state to pretend a trustworthy environment. That's the reason why OEM unlocking option is active and OTA updates start to install. But OTA update files verify your system's integrity by calculating checksums for each partition. This check fails with a active Magisk installation and update process ends with an error.
A preboot chip or sth like this is not in use on Moto devices. Partitions 1-14 (+/-) are defined as your bootloader. A prebootloader does only exist for MediaTek devices but not for SnapDragon.
There's a lot of official documentation about all the stuff...
In my opinion the easiest way to update your device is to flash the stock ROM. One script and it's done. No need to flash this and boot that only to be able to download the OTA which hasn't been installed until then. Your system takes more time to flash the OTA update then fastboot takes to flash the firmware.
Click to expand...
Click to collapse

KtownJeff said:
Yes correct it easier to flash rom after it is available for download with a month behind....
Click to expand...
Click to collapse
You should check your sources.

KtownJeff said:
Quoteriginally Posted by WoKoschekk
Sorry, but this is the most complicate way for an OTA I have ever red. You could sum up these steps to "flash the stock firmware". In the end the result is the same. But it's much easier.
I
Our device is unbreakable... trust me I've tried to and still haven't managed to Qualcomm brick it.... test point is the only way to get it to EDL mode and i plan on taking my screen off tonight just to see if I can..... and write another essay because some ass hole from Germany thinks he know everthing
Click to expand...
Click to collapse
I also want to leave my device in oem_locked state and not in flashing_locked

Holy Moly! Come on guys! I only wanted a way to fix OTA on my rooted stock installation without having to do a complete stock reinstall. At the time I asked the question, the newest full stock ROM update was not yet available. It is now. My point was I didn't like going through a complete reinstall of my apps and settings, Backing up my Data partition then trying to restore it has never seemed to work for me. Anyway you all need to just chill and put your egos away.

pastorbob62 said:
Holy Moly! Come on guys! I only wanted a way to fix OTA on my rooted stock installation without having to do a complete stock reinstall. At the time I asked the question, the newest full stock ROM update was not yet available. It is now. My point was I didn't like going through a complete reinstall of my apps and settings, Backing up my Data partition then trying to restore it has never seemed to work for me. Anyway you all need to just chill and put your egos away.
Click to expand...
Click to collapse
The fact is you need to restore everything back to stock for an OTA. This includes a deinstallation of Magisk (also modules are gone) and restore your stock boot.img with the stock recovery. Then you download and install the OTA, go back to fastboot mode and start installing TWRP and everything else.
This was option 1.
Option 2: Download the latest firmware on Telegram (only possible with your device!) or install LMSA tool, which also downloads the latest build. Boot into fastboot, flash the firmware (without erase userdata) and boot TWRP. Flash TWRP installer and Magisk. Done!

WoKoschekk said:
The fact is you need to restore everything back to stock for an OTA. This includes a deinstallation of Magisk (also modules are gone) and restore your stock boot.img with the stock recovery. Then you download and install the OTA, go back to fastboot mode and start installing TWRP and everything else.
This was option 1.
Click to expand...
Click to collapse
I'm thinking not, since this was the first thing I tried when I got the notification for the update. And the update still failed.
WoKoschekk said:
Option 2: Download the latest firmware on Telegram (only possible with your device!) or install LMSA tool, which also downloads the latest build. Boot into fastboot, flash the firmware (without erase userdata) and boot TWRP. Flash TWRP installer and Magisk. Done!
Click to expand...
Click to collapse
Telegram didn't have it when I installed the update. LMSA kept giving me a "Decompression failed" error message. So I just reinstalled the stock version I was already on and allowed the update to complete. Then reinstalled TWRP and Magisk without any issues once I had all of my apps and data restored.
Not taking any offense here, but I am not a noob and while I didn't give all of the details to what I had tried I also didn't want to reinvent the wheel. I didn't think about eliminating the line "erase userdata". Since it was very simple with previous devices to do it I knew there had to be an easier way. By the way, the XT1965-2_LAKE_RETLA_10_QPWS30.61-21-14_subsidy-DEFAULT_regulatory-XT1965-2-SUTEL-DS_CFC.xml.zip verson of the ROM is now available here: https://mirrors.lolinet.com/firmware/moto/lake/official/

pastorbob62 said:
Telegram didn't have it when I installed the update.
...
By the way, the XT1965-2_LAKE_RETLA_10_QPWS30.61-21-14_subsidy-DEFAULT_regulatory-XT1965-2-SUTEL-DS_CFC.xml.zip verson of the ROM is now available here: https://mirrors.lolinet.com/firmware/moto/lake/official/
Click to expand...
Click to collapse
The mentioned firmware is available on Telegram since Sep 03. Screenshot
Telegram group: https://t.me/s/motoupdatestracker

WoKoschekk said:
The mentioned firmware is available on Telegram since Sep 03. Screenshot
Telegram group: https://t.me/s/motoupdatestracker
Click to expand...
Click to collapse
That's nice. But the one for my phone was not available on tracker until the day after I updated via OTA.

KtownJeff said:
Yup, If you are just rooted stock and have NOT installed the copy partions.ZIP... Boot to TWRP From FASTBOOT BACKUP your DATA to flash back after Install...Just the Data and install Magisk Uninstaller... After MAGISK unistall... Format DATA PARTITION ONLY...MAKE SURE YOU ARE ON BOOT SLOT A... Reboot to the SETUP WIZARD... STOP and reboot to bootloader.......HAVE STOCK BOOT IMG READY TO BOOT FROM CURRENT FIRMWARE... The STOCK installed boot img has the bootloader and modified devices flagged so that kills the OTA INSTALLATION.... If you have installed any modded logo.bin you have to replace it with STOCK on both logo_a and logo_b
fastboot --set-active=a
fastboot flash logo_a logo.bin
fastboot flash logo_b logo.bin
fastboot boot boot.img
DONT FLASH BOOT
Click to expand...
Click to collapse
I tried this to go back to stock rom from LOS17.
With : fastboot --set-active=a
I have this error :
(bootloader) slot-suffixes: not found
error: could not get suffixes
Any idea of what it means ?
Many thanks

[email protected] said:
I tried this to go back to stock rom from LOS17.
I've never seen that error before have you tried google search for the error?
Click to expand...
Click to collapse

[email protected] said:
I tried this to go back to stock rom from LOS17.
With : fastboot --set-active=a
I have this error :
(bootloader) slot-suffixes: not found
error: could not get suffixes
Any idea of what it means ?
Many thanks
Click to expand...
Click to collapse
Don't know what your error means, but flash the stock ROM and it should be fine.