I'm creating this thread because i have a moto G4 xt1621 bricked by OTA android 7.0 update.
my phone is from latin america dual sim model 16gb rom.
bootloader unlocked, twrp installed plus lineage oficial 7.1.2 for ATHENE running for more than a year no problems.
one day i was using it for videos and realized the quality was not very good so i decided to install the original android 6.0.1 from motorola to check if the quality of the main camera improved, all went ok thru fastboot and the phone rebooted to android 6.0.1 no problems, so the downgraded android was not the problem, yes the cam improved the video quality a little, moto cam vs ported lineage cam is one step down in my opinion the later, flashed a custom logo.bin to hide the unlocked bootloader screen of pain and all was ok, then the phone asked for an update OTA to android 7.0 and i declined but days later i decided to test the 7.0 flavor against the marshmallow in camera quality tings, why why i'm such a nerdddd whyyyyyyy.....
the update 990 Mbit downloaded in under 10 min, i got 100 meg fiber lol.
the phone started to install the update and after 85% 20 min or so, pum! dead screen in front of me, i was like wth is connected to the pc plus the battery have over 75%, hit the power on, nothing, disconnected from pc, connected again, only the famous bricked flashing white led of dead pulsing was alive no combination of buttons or usb connections did nothing.
googling find lost of threads talking about OTA 7.0 from motorola bricking phones that dont do it in steps like marshmallow to the first nougat then the next security update and so on, when you go from 6.0.1 to the latest nougat OTA lost of ATHENE´s die bricked with no hope.
the problem is in the GPT.bin and BOOTLOADER.bin binaries of the marshmallow and the latest nougat NOT BEING COMPATIBLE AT ALL.......
FIX
after a full day and i meant 20 hours in front of the pc i find the right combination of tools for my problem:
in W10 64bit turn test mode on and driver integrity check off from admin powershell (remember to do it backwards after, changing on by off and disable by enable)
bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING ON
RESTART PC
download QualcommDrv.zip in this post and install the correct x64 or x86 version of the driver, google motorola usb drivers and install them. (MotorolaDeviceManager_2.5.4.exe)
RESTART PC
connect the phone thru usb 2.0 (regular usb in the MB not add cards or hubs or keyboards) and open device manager, when the pc tell you it do not recognize the usb device or any usb error pop, hit at the same time power and volume down in the phone until the pop in device manager go away or the error disappear.
in device manager you have to look for COM/LPT new entry in the tree and when open it say qualcomm stuff of some kind. (is over 9000 kind 9008 or so dont remember) lol
Download blankflash.zip in this post and unzip it in a folder, run blank-flash.bat
when you do this steps the phone should boot a generic fastboot, there you will have the phone ready to do some magic like installing twrp if the bootloader is unlocked before you bricked the moto or reflash a stock moto original rom, plenty of threads for both that routes here in xda. WORKS FOR ME.
my phone is from latin america dual sim model 16gb rom.
bootloader unlocked, twrp installed plus lineage oficial 7.1.2 for ATHENE running for more than a year no problems.
one day i was using it for videos and realized the quality was not very good so i decided to install the original android 6.0.1 from motorola to check if the quality of the main camera improved, all went ok thru fastboot and the phone rebooted to android 6.0.1 no problems, so the downgraded android was not the problem, yes the cam improved the video quality a little, moto cam vs ported lineage cam is one step down in my opinion the later, flashed a custom logo.bin to hide the unlocked bootloader screen of pain and all was ok, then the phone asked for an update OTA to android 7.0 and i declined but days later i decided to test the 7.0 flavor against the marshmallow in camera quality tings, why why i'm such a nerdddd whyyyyyyy.....
the update 990 Mbit downloaded in under 10 min, i got 100 meg fiber lol.
the phone started to install the update and after 85% 20 min or so, pum! dead screen in front of me, i was like wth is connected to the pc plus the battery have over 75%, hit the power on, nothing, disconnected from pc, connected again, only the famous bricked flashing white led of dead pulsing was alive no combination of buttons or usb connections did nothing.
googling find lost of threads talking about OTA 7.0 from motorola bricking phones that dont do it in steps like marshmallow to the first nougat then the next security update and so on, when you go from 6.0.1 to the latest nougat OTA lost of ATHENE´s die bricked with no hope.
the problem is in the GPT.bin and BOOTLOADER.bin binaries of the marshmallow and the latest nougat NOT BEING COMPATIBLE AT ALL.......
FIX
after a full day and i meant 20 hours in front of the pc i find the right combination of tools for my problem:
in W10 64bit turn test mode on and driver integrity check off from admin powershell (remember to do it backwards after, changing on by off and disable by enable)
bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING ON
RESTART PC
download QualcommDrv.zip in this post and install the correct x64 or x86 version of the driver, google motorola usb drivers and install them. (MotorolaDeviceManager_2.5.4.exe)
RESTART PC
connect the phone thru usb 2.0 (regular usb in the MB not add cards or hubs or keyboards) and open device manager, when the pc tell you it do not recognize the usb device or any usb error pop, hit at the same time power and volume down in the phone until the pop in device manager go away or the error disappear.
in device manager you have to look for COM/LPT new entry in the tree and when open it say qualcomm stuff of some kind. (is over 9000 kind 9008 or so dont remember) lol
Download blankflash.zip in this post and unzip it in a folder, run blank-flash.bat
when you do this steps the phone should boot a generic fastboot, there you will have the phone ready to do some magic like installing twrp if the bootloader is unlocked before you bricked the moto or reflash a stock moto original rom, plenty of threads for both that routes here in xda. WORKS FOR ME.
