OTA update fails - Moto G4 Play Questions & Answers

Hi,
my situation is this:
1.) I had installed TWRP + Root + Xposed + Stock Android 6.0.1 and everything worked fine.
2.) Then came the last OTA update notification.
3.) I picked an old backup when i had only TWRP installed and the rest was untouched.
4.) When the backup was done i picked the recovery.img file from this .rar XT1602_HARPIA_MPI24.241-15.3_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml (4) and flashed it with mfastboot. (USB Debugging Enabled, Fastboot Mode Enabled)
5.) I started the Recovery Mode and ended with the "Dead Android Guy". Even though i was able to reach the stock recovery menu using a key combination (POWER+VOL UP+VOL DN at the same time)
6.) Restart the phone
7.) Download the OTA Update
8.) Tried to install it but ended always with an error
9.) Phone restart -> "An error occured during the OTA update"...
Everytime when i try to reach the stock recovery i always see the dead android guy first. Ive also tried to wipe the cache+wipe data + factory mode. But nothing helps. How the hell can i fix that and install the last OTA update (and why did that happen to me -.-?)
EDIT
I managed to solve the problem by flashing every single file of the firmware. Heres a list:
mfastboot oem fb_mode_set
mfastboot flash partition gpt.bin
mfastboot flash bootloader bootloader.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash dsp adspso.bin
mfastboot flash oem oem.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot erase customize
mfastboot erase clogo
mfastboot oem fb_mode_clear
Click to expand...
Click to collapse
EDIT
But still. When i try to enter the stock recovery i see the dead android guy first. Can you help me out?

Well, the "dead droid" before stock recovery it's the expected behavior, isn't it?

Idk. Im not used to the dead droid.

removed

sevenRA1 said:
Idk. Im not used to the dead droid.
Click to expand...
Click to collapse
In the stock the dead droid always cames before the stock Recovery, don't worry about it.

Same problem here. I've got an XT1602 with 6.0.1. stock and Oct 2016 security patches and an OTA update is available, but fails to install. TWRP says error 7, stock displays the dead droid.
I have my phone rooted, but installed a system backup before installing the OTA.
Flashing stock from here leads to 6.0.1. with July patches, but no OTA update available.
Any Ideas? Can anyone provide a a newer stock rom?
@sevenRA1 are you sure you're on the latest version? can you please check your security patch level?

Yes im very sure. Security Level is now Feb. 2017 and when i search for new updates it doesnt find some. Do what i did. Flash every single file by hand. Heres a How To.

ValdarX said:
Same problem here. I've got an XT1602 with 6.0.1. stock and Oct 2016 security patches and an OTA update is available, but fails to install. TWRP says error 7, stock displays the dead droid.
I have my phone rooted, but installed a system backup before installing the OTA.
Flashing stock from here leads to 6.0.1. with July patches, but no OTA update available.
Any Ideas? Can anyone provide a a newer stock rom?
@sevenRA1 are you sure you're on the latest version? can you please check your security patch level?
Click to expand...
Click to collapse
ValdarX did you manage to solve this problem? I've got the same thing: restored to stock (saving the user data) and no more OTA available, so stuck on an old version. I guess maybe only full recovery to stock will work.

Excuse me, I would like to do the same thing, in order to prepare for nougat. My phone is bought from vodafone romania, vodafone branded. It is harpia xt1604. Its specs are shown in picture. Could I flash the Harpia XT1602 firmware RETAIL from here to have it unbranded and to get the latest updates?
Thank you.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

TheEvilVirus said:
ValdarX did you manage to solve this problem? I've got the same thing: restored to stock (saving the user data) and no more OTA available, so stuck on an old version. I guess maybe only full recovery to stock will work.
Click to expand...
Click to collapse
unfortunately not

I have the same issue. I've tried several times to install the update on my stock xt1607 and it fails every time. I've restored my stock backup from immediately after I unlocked my bootloader...totally unmodified. I get an error in stock recovery saying there was an unexpected change to /system. I even flashed the stock boot logo again, just in case. My only remaining option is a full factory flash, to be completely sure the /system is unmodified.

me too
Before rooting, I did backups of untouched /system /boot, recovery and logo partition.
I've carefully followed this howto and it doesn't work definitively.
https://forum.xda-developers.com/moto-g4-plus/how-to/guide-sucsessfull-ota-update-rooting-t3472658
On second attempt, I've tried this without success :
https://forum.xda-developers.com/showpost.php?p=71461568&postcount=64
After rebooting, "Parameters>>About Phone>>System Update" says my phone is up to date and I'm unable to get the OTA. I tried to apply the OTA (Blur_Version.24.201.8.harpia.retail.en.US.zip) downloaded with my current version (MPIS24.241-15.3-7) , I got another error :
Package expects build thumbprint of 6.0.1/MPIS24.241-15.3-16/17 .... or 6.0.1/MPIS24.241-15.3-7/8 ... ; this device has 6.0.1/MPIS24.241-15.3-3/3
So at now, I'm blocked at security level Oct 2016.
Anybody to help us ?

hamelg said:
me too
Before rooting, I did backups of untouched /system /boot, recovery and logo partition.
I've carefully followed this howto and it doesn't work definitively.
https://forum.xda-developers.com/moto-g4-plus/how-to/guide-sucsessfull-ota-update-rooting-t3472658
On second attempt, I've tried this without success :
https://forum.xda-developers.com/showpost.php?p=71461568&postcount=64
After rebooting, "Parameters>>About Phone>>System Update" says my phone is up to date and I'm unable to get the OTA. I tried to apply the OTA (Blur_Version.24.201.8.harpia.retail.en.US.zip) downloaded with my current version (MPIS24.241-15.3-7) , I got another error :
Package expects build thumbprint of 6.0.1/MPIS24.241-15.3-16/17 .... or 6.0.1/MPIS24.241-15.3-7/8 ... ; this device has 6.0.1/MPIS24.241-15.3-3/3
So at now, I'm blocked at security level Oct 2016.
Anybody to help us ?
Click to expand...
Click to collapse
Did you try to flash the stock rom through fastboot? Including recovery?

Yes, but I flashed only boot.img, logo.bin, recovery.img, system.img_sparsechunk.0 till 7.
I'm a little bit nervous to do a full flash and to be stick with July Patch like ValdarX at comment #6. After a full flash, if something goes wrong, I won't be able to restore my backup.
Edit :
What about to keep my data, can I safely skip erase userdata ?
What is the purpose of the customize partition ?

issue solved, here :
https://forum.xda-developers.com/showpost.php?p=71999579&postcount=11

No need to worry, the only thing you are missing is. It may be possible that you installed fiware not contain Moto upgrade sevice. You should download this from play store. Or download the correct fiware from firmwarecentre

sevenRA1 said:
Yes im very sure. Security Level is now Feb. 2017 and when i search for new updates it doesnt find some. Do what i did. Flash every single file by hand..
Click to expand...
Click to collapse
I stand corrected, that works. I'm on Feb 2017 security patches now. Didn't even have to erase userdata.

I have the same issues again with the next security update -.-
@hamelg Your advice fixed nothing for me. This night ill flash the whole stock image again.

Does anybody have any experience how/whether this works if the only image available for your phone model now involves a downgrade?
My phone (XT1602 reteu) was delivered with a July 2016 patch level, which corresponds to the only stock image (the XT1602 RETAIL one) I see available for it.
Flashing that to unroot, apply the OTA updates (up to February 2017) and then re-root worked fine, but what about a repeat performance? I originally assumed I could simply start with that stock image again and then apply all OTAs (including any new ones) once more, but I've since learned that the bootloader (and partition table) isn't necessarily downgradable and might cause problems with reapplying the OTAs after downgrading the rest of the phone.

Although at least for the time being never mind - it seems like there are now RETAIL images for both February and May patch levels floating around, which avoids any need to downgrade.

Related

[GUIDE] Restore Moto Firmware for American Moto G

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hello guys, this guide is to help you to go back to Stock Firmware from any custom ROM or from Google Play edition firmware.
First, all credits go to the original owners of this guide, firs of all thanks to @Semseddin and his previous guide !!!
Click to expand...
Click to collapse
I started this thread because I have an Argentinian Retail Moto G, and downloaded the retail 4.4.2 firmware for Argentina, it comes in *.tar.gz format, but the guide stated above was for *.xml.zip firmware, so here it comes some differences.
DISCLAIMER: If your Moto G dies, explodes, turn into a zombie, goes berserk and tries to kill you, I'm not the one to blame. I've tested this tutorial and worked for me, if this does not work for you, keep googling about your problem. I can help you but its not my fault! Try this at your own risk.
THIS SHOULD WORK ON LOCKED AND UNLOCKED BOOTLOADERS​
LETS BEGIN...
-1 - Make a backup of all the apps and media in your SD card because all of this erases and formats everything inside! So backup everything!
0 - DOWNLOAD and install Motorola drivers.
1 - Go to THIS PAGE and download a 4.4.2 firmware suitable for your device. In my case I searched and downloaded Retail Argentina 4.4.2 firmware. There aren't a lot of 4.4.4 specific firmware, so download a 4.4.2 firmware. After installing it, you can OTA to 4.4.4.
2 - On Windows, create a temporary folder in drive c:\ called "restore" so it would be like this: c:\restore ; and there using 7zip or similar, extract everithing inside the firmware file into this "retail" folder. (The firmware I needed was in *.tar.gz format but this can work if the firmware you get is in *.XML.zip format)
3 - Now, download the attachment I provide you (those three files are from 4.4.4 OTA ZIP). Extract and place them inside the "restore" folder and replace the files inside.
4 - Download "mfastboot-adb.rar" in the attachments. After that, extract everything inside the RAR in the "restore" folder.
Important: Everything has to be inside the "restore" folder, don't leave files inside extraxted folders. It has to look like this:
5 - Turn off the phone and turn it on in FASTBOOT MODE (When turned off tap and hold ON BUTTON and VOLYME DOWN BUTTON for 5 seconds and release them, you should see the FASTBOOT MENU) and plug the phone to PC via USB.
6 - Start CMD (Windows console) with Administrator rights (in Windows 7 click on Start and in the search bar write CMD and above right click on CMD and start it as Administrator) and type:
cd c:\restore
Click to expand...
Click to collapse
This will place the console inside the "restore" folder.
7 - Here starts the COPY-PASTE action. Don't miss ANY LINE here!!! Copy and paste this lines one by one, waiting to the flashing to finish and giving an OKAY as a result!!! If some of this commands gives a (bootloader) FAILED answer, try to repeat that command.
If you upgraded to Lollipop, you can go back to KitKat, but DONT FLASH THE COMMANDS I GIVE HERE THAT ARE IN RED COLOR. Use the RED commands only if you NEVER upgraded to Lollipop before:
mfastboot flash aboot emmc_appsboot.mbn
mfastboot flash partition gpt.bin
mfastboot reboot-bootloader
mfastboot getvar max-sparse-size
mfastboot oem fb_mode_set
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img -- (this one gives trouble on some devices, if that is your case, click below)
If mfastboot flash system system.img gives an error, you can try this commands:
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
If yoy have a Moto G LTE version, you can use this commands: (Correct me if these are not the right ones for LTE)
mfastboot flash system system.img_sparsechunk1
mfastboot flash system system.img_sparsechunk2
mfastboot flash system system.img_sparsechunk3
mfastboot flash system system.img_sparsechunk4
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata -- THIS ERASES ALL YOUR DATA AND FORMATS SD! You should have done a backup by this point! (If this command gives a (bootloader) FAILED error, immediately run this command again, that should work.)
mfastboot oem fb_mode_clear
mfastboot reboot
Click to expand...
Click to collapse
Please, I say this again! Do this one line at a time, waiting for every line to flash and perform actions and to return an OKAY as an answer...
If every step on the copy-paste steps give OKAY as an answer, you will see your Moto G return to life with the original Moto firmware!!!! The first boot will take like 7 or 8 minutes, so be patient!
So this is it. If you need help let me know below... :fingers-crossed:
Everything looks good and worked for me except for 2 things:
-Flashing motoboot.img will error if you're trying to downgrade from 4.4.4 gpe or 4.4.3 moto but you can just skip it
-You need to add a .img at the end of this "mfastboot flash system system (this one gives trouble on non european models but is the one that works on american (and argentinian) Moto G!)" (not a big deal but it errors if you don't and people can get scared)
anerik said:
Everything looks good and worked for me except for 2 things:
-Flashing motoboot.img will error if you're trying to downgrade from 4.4.4 gpe or 4.4.3 moto but you can just skip it
-You need to add a .img at the end of this "mfastboot flash system system (this one gives trouble on non european models but is the one that works on american (and argentinian) Moto G!)" (not a big deal but it errors if you don't and people can get scared)
Click to expand...
Click to collapse
You're damn right man, correcting right now! :good:
Hey man thanks for the guide. No the question is, why flash back? GPE is much better for me! or it is because we will have problems when trying to update to Android L?
I plan to do this when 5.0 comes out. Currently I'm on CM11. However, on the official downloads page I only see 4.4.2 for my retail firmware. Would this be fine if I'm on 4.4.4?
Thanks for the guide.
there is one thing, if you upgrade to 4.4.3/4.4.4, you will not be able to downgrade yourself to 4.3.
I have tried. it just wont boot.
SloppyBeef said:
I plan to do this when 5.0 comes out. Currently I'm on CM11. However, on the official downloads page I only see 4.4.2 for my retail firmware. Would this be fine if I'm on 4.4.4?
Thanks for the guide.
Click to expand...
Click to collapse
Yes, I was on GPe 4.4.4 firmware, then I flashed 4.4.2 Moto firmware, then OTAed to 4.4.4 Moto firmware.. So this will work..
AgentChaos said:
there is one thing, if you upgrade to 4.4.3/4.4.4, you will not be able to downgrade yourself to 4.3.
I have tried. it just wont boot.
Click to expand...
Click to collapse
Yes, that is true, so 4.3 is no more an option.. I wonder if this will happen in the future, I mean, maybe when 5.0 comes out, will it be impossible to downgrade to 4.4.2 firmware also?... I hope I'm wrong..
titotito1983 said:
Hey man thanks for the guide. No the question is, why flash back? GPE is much better for me! or it is because we will have problems when trying to update to Android L?
Click to expand...
Click to collapse
This is just in case you miss Stock firmware... If you like GPe firmware just stay there, but if you have trouble you can use this guide. Also this should work to revert from CM11 or another custom ROM. :good: But, when Lollipop arrives, there will be no problems with OTAs on GPe firmware, but Motorola gives some extra features..
I returned to stock because of some options and features Stock firmware has... (FM radio, Sounds Effects, Assist, Moto Camera, OTG options on Settings > Storage, etc...)
Hi, i bougth the Moto G in Argentina with 4.4.2 and unlocked the bootloader, updated OTA to 4.4.4 and rooted the device , if i do this procedure will i lost the CMW recovery and/or root? the bootloader will remain unlocked?
i just tried the Factory Reset option but it ends un a bootloop... is there another option to have the stock rom clean or i have to do all this?
THANKS !
sublowBASS said:
Hi, i bougth the Moto G in Argentina with 4.4.2 and unlocked the bootloader, updated OTA to 4.4.4 and rooted the device , if i do this procedure will i lost the CMW recovery and/or root? the bootloader will remain unlocked?
i just tried the Factory Reset option but it ends un a bootloop... is there another option to have the stock rom clean or i have to do all this?
THANKS !
Click to expand...
Click to collapse
If you do all of this, you will loose root and CWM... but you can root it again when you do this procedure-- and the bootloader will remain unlocked. :good:
If you download the firmware in .xml.zip format enter :
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
Instead of mfastboot flash system system.img
Cyber. said:
If you download the firmware in .xml.zip format enter :
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
Instead of mfastboot flash system system.img
Click to expand...
Click to collapse
When I tried to flash my specific firmware, those commands didnt work, and somewhere else I read those commands you say are for some european devices. I use the system.img command and it worked every time I do it on my retail Arg moto g. That is a little difference between some devices.
Edit: sorry I forgot that the firmware I used was in tar.gz format, so that's why those commands didn't work for me.. If the firmware you download is xml.zip you have to use the other guide that is on sticky posts.
Thanks for your guide! It was very usefull.
I've been trying CM rom and the Decepticon kernel, and because of that I've reinstalled the stock rom quite a few times now.
Because of that, every time I restored the 4.4.2 rom (Retail Argentina) and then OTA to 4.4.4. It's very annoying to download that update every time and I couldn't find it online so I've made a backup of the update zip. That way I only need to enter into the recovery and flash the update.
Anyone else wants it?
I was worried about the sparsechunk.xx files as well, but flashing them worked no problem for me (I'm using the Bell 4.4.2 Canada firmware).
Got my Moto G back to Moto stock 4.4.2 from GPe 4.4.4 just fine! Thanks Marckozz <3 Can confirm this works for XT1032 in Canada (although this is probably the same model as an American one to be honest).
MarckozZ said:
Hello guys, this guide is to help you to go back to Stock Firmware from any custom ROM or from Google Play edition firmware.
I started this thread because I have an Argentinian Retail Moto G, and downloaded the retail 4.4.2 firmware for Argentina, it comes in *.tar.gz format, but the guide stated above was for *.xml.zip firmware, so here it comes some differences.
DISCLAIMER: If your Moto G dies, explodes, turn into a zombie, goes berserk and tries to kill you, I'm not the one to blame. I've tested this tutorial and worked for me, if this does not work for you, keep googling about your problem. I can help you but its not my fault! Try this at your own risk.
THIS SHOULD WORK ON LOCKED AND UNLOCKED BOOTLOADERS​
LETS BEGIN...
-1 - Make a backup of all the apps and media in your SD card because all of this erases and formats everything inside! So backup everything!
0 - DOWNLOAD and install Motorola drivers.
1 - Go to THIS PAGE and download a 4.4.2 firmware suitable for your device. In my case I searched and downloaded Retail Argentina 4.4.2 firmware. There aren't a lot of 4.4.4 specific firmware, so download a 4.4.2 firmware. After installing it, you can OTA to 4.4.4.
2 - On Windows, create a temporary folder in drive c:\ called "restore" so it would be like this: c:\restore ; and there using 7zip or similar, extract everithing inside the firmware file into this "retail" folder. (The firmware I needed was in *.tar.gz format but this can work if the firmware you get is in *.XML.zip format)
3 - Now, download the attachment I provide you (those three files are from 4.4.4 OTA ZIP). Extract and place them inside the "restore" folder and replace the files inside.
4 - Download "mfastboot-adb.rar" in the attachments. After that, extract everything inside the RAR in the "restore" folder.
Important: Everything has to be inside the "restore" folder, don't leave files inside extraxted folders. It has to look like this:
5 - Turn off the phone and turn it on in FASTBOOT MODE (When turned off tap and hold ON BUTTON and VOLYME DOWN BUTTON for 5 seconds and release them, you should see the FASTBOOT MENU) and plug the phone to PC via USB.
6 - Start CMD (Windows console) with Administrator rights (in Windows 7 click on Start and in the search bar write CMD and above right click on CMD and start it as Administrator) and type:
This will place the console inside the "restore" folder.
7 - Here starts the COPY-PASTE action. Don't miss ANY LINE here!!! Copy and paste this lines one by one, waiting to the flashing to finish and giving an OKAY as a result!!! If some of this commands gives a (bootloader) FAILED answer, try to repeat that command.
Please, I say this again! Do this one line at a time, waiting for every line to flash and perform actions and to return an OKAY as an answer...
If every step on the copy-paste steps give OKAY as an answer, you will see your Moto G return to life with the original Moto firmware!!!! The first boot will take like 7 or 8 minutes, so be patient!
So this is it. If you need help let me know below... :fingers-crossed:
Click to expand...
Click to collapse
i was on stock 4.4.4(no root no unlocked boot loader indian moto g)
then i installed Asian stock soak 5.0.2 from here
http://forum.xda-developers.com/moto-g/general/moto-g-xt1033-asia-retail-android-t3001206
but i want to install it from ota update( it has some other features also)
i have tried every damn method including yours but it shows invalid piv system signature file...
can you help?
gpe lollipop 5.0.1 to stock retail
hey man, thnks for ur guide, I have a question what if i have gpe. Lollipop 5.0.1 but i want the 5.0.2 lollipop retail firmware from motorola? How do i proceed? I want the argentinian retail stockand my bootloader is unlocked. Thks!
Maxxgavin said:
hey man, thnks for ur guide, I have a question what if i have gpe. Lollipop 5.0.1 but i want the 5.0.2 lollipop retail firmware from motorola? How do i proceed? I want the argentinian retail stockand my bootloader is unlocked. Thks!
Click to expand...
Click to collapse
Try this:
*Flash ENTIRE firmware image from Brazil Retail Lollipop 5.0.2... So your bootloader will be updated to Moto bootloader... (search in this forum that firmware image and steps to flash it, and yes, flash motoboot.img and gpt.bin also, I've done that and it can be flashed on top of the old Google bootloader from GPE)
*Then, flash Retail KK 4.4.4 using this guide, but dont flash motoboot or gpt.bin from 4.4.4....
*And last, update via OTA to Retail AR Lollipop...
:fingers-crossed:
Thks, but why do i have to flash the brazilian firmware first? Flashing directly the argentinian retail 5.0.2 wont work?
Maxxgavin said:
Thks, but why do i have to flash the brazilian firmware first? Flashing directly the argentinian retail 5.0.2 wont work?
Click to expand...
Click to collapse
there is no AR 5.0.2 firmware yet, you can either wait or do what @MarckozZ suggested

[OTA] Moto G 2014 XT1063 v22.11.6 Android Lollipop

This OTA has been copied straight from the /cache folder by @KennyWuLee.
Download Here!
Steps For Applying the Update:
Copy the ZIP to your Moto G.
Go into Recovery.
Select "apply update from sdcard"
Choose the File which you copied.
Wait till it finishes and select reboot.
This update is specifically for the XT1063 model and isn't meant for other variants.
Update Details:
Code:
v22.11.6
Android Version: 5.0
Build Number: LXB22.39-6
Are you sure? cause the file name is "Blur_Version.21.11.17.titan_retuglb.retuglb.en.US.zip"
Any chance of this working on XT1068?
emmanuelreyes said:
Are you sure? cause the file name is "Blur_Version.21.11.17.titan_retuglb.retuglb.en.US.zip"
Click to expand...
Click to collapse
Yes, he is sure because the filename naming scheme used by Motorola automatically renames any update to the name of the firmware currently installed.
KennyWuLee, had 21.11.17 installed while he downloaded the update and that is why the filename is "Blur_Version.21.11.17.titan_retuglb.retuglb.en.US.zip"
pleomaxell said:
Yes, he is sure because the filename naming scheme used by Motorola automatically renames any update to the name of the firmware currently installed.
KennyWuLee, had 21.11.17 installed while he downloaded the update and that is why the filename is "Blur_Version.21.11.17.titan_retuglb.retuglb.en.US.zip"
Click to expand...
Click to collapse
What if i have a different version? Will it work? or i have to rename it?
emmanuelreyes said:
Are you sure? cause the file name is "Blur_Version.21.11.17.titan_retuglb.retuglb.en.US.zip"
Click to expand...
Click to collapse
pleomaxell said:
Yes, he is sure because the filename naming scheme used by Motorola automatically renames any update to the name of the firmware currently installed.
KennyWuLee, had 21.11.17 installed while he downloaded the update and that is why the filename is "Blur_Version.21.11.17.titan_retuglb.retuglb.en.US.zip"
Click to expand...
Click to collapse
@emmanuelreyes, Exactly what @pleomaxell said. Plus here's the screenshot running on my XT1063.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Is there a chance to make this file a flashable zip through TWRP? For some reason it doesn't want to install, it says "/system/lib/hw/sensort.MSM8226.so" has unexpected contents :S
Fine to XT1068
Thanks and this works fine with my XT1068, check this post http://forum.xda-developers.com/showpost.php?p=56765946&postcount=138
@Taimur Akmal why does the screenshot show an Exclamation(!) sign with the network icon?
pleomaxell said:
@Taimur Akmal why does the screenshot show an Exclamation(!) sign with the network icon?
Click to expand...
Click to collapse
It shows that I am without an Internet connection. I have Mobile Internet turned off.
Cannot lock bootloader
tbunlmtd said:
Working just fine, thanks!
Click to expand...
Click to collapse
I am stuck here too. Cannot relock bootloader ...
build version KXB21.85-17; System version: Blur_Version.21.11.17.titan_retuglb.retuglb.en.US
I have downloaded the same firmware from http://sbf.droid-developers.org/phone.php?device=36
Applied flash according to :
mfastboot.exe oem lock begin
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash system system.img_sparsechunk.3
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
mfastboot.exe oem lock
Click to expand...
Click to collapse
getting downgrade error, PIV signed image error, sst lock fail error !
[NB: I have changed to US version (retuaws) before and flashed back to global ]
Sounds like your on a XT1063. This is what I did when I was in the same position as you. I restored my Nandroid of KK. If you have a all stock copy then you should be better then I was & about to skip a few of these steps. I found a system dump on here of the stock system & started pushing the files I knew I removed. Actually I used ES File Explorer & done a select all, copy, paste. You get prompted to ask what to do about files that are already there. Check apply to all & choose skip. This left me with a audio file that was replaced & had to be change back. You should make a new Nandroid to save your work to this point. Flash the stock recovery & run the update.zip. mine installed fine with the unlocked bootloader & root.
L is really buggy tho so be warned.
Sorry for the noob question.
I have the XT1063 and my system version is 21.11.14 titan_retla.retla.en.01 . Will this ota work on my phone?
rasbin said:
Sorry for the noob question.
I have the XT1063 and my system version is 21.11.14 titan_retla.retla.en.01 . Will this ota work on my phone?
Click to expand...
Click to collapse
I doubt it will without flashing the other firmware.
rasbin said:
Sorry for the noob question.
I have the XT1063 and my system version is 21.11.14 titan_retla.retla.en.01 . Will this ota work on my phone?
Click to expand...
Click to collapse
You will have to flash via fastboot the XT1063 retugbl firmware in order to use this OTA file.
Check this thread, but consider making a full backup.
My md5 checksum:
2e632d07edc3c1ceb38a0ee486f12a5b
you need the bootloader unlocked?
I successfully flashed this while being fully stock/locked bootloader. Everything works except the flashlight won't turn back off after I activate it... anyone else have this issue?
patrickjaden said:
I successfully flashed this while being fully stock/locked bootloader. Everything works except the flashlight won't turn back off after I activate it... anyone else have this issue?
Click to expand...
Click to collapse
Working totally fine on my end. You are talking about the Flashlight from the Notif menu right?
Taimur Akmal said:
Working totally fine on my end. You are talking about the Flashlight from the Notif menu right?
Click to expand...
Click to collapse
Yes the bootloader needs unlocked to flash the stock firmware.

New firmware

Hi All!
I just receive a new firmware MPN24.104-44.
Anybody else?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Yes, me too. UK, unlocked. It was a big download, still going. Not Nougat, which is what I first thought. No idea yet what it fixes.
I have been on this version on the US unlocked version (screenshot) I wish we would get nougat already.
mrbracht said:
I have been on this version on the US unlocked version (screenshot) I wish we would get nougat already.
Click to expand...
Click to collapse
So, it's the August security update? That's it?
Yeah, I'm guessing so. Kind of disappointed with the dev work and software updates for this phone. Still one of the best phones I have ever had. Just wish it would take off on here.
mrbracht said:
I have been on this version on the US unlocked version (screenshot) I wish we would get nougat already.
Click to expand...
Click to collapse
Unrelated to updates, how did you get the black/dark theme?
which firmware are you in , I wnt the dsds modem firmware lol
Any ideas on how to flash it on an unlocked device; I couldn't even with the stock recovery.
TWRP gets far into the update but ends with ERROR: 7 (the system partition has unexpected contents.)
Yeah, I'm having the same issue. It's getting on my nerves...
Even when trimming the updater-script file, I still end up with asset errors. I went so far I now get Error: 6 and now I can't be bothered to find the missing semicolon...
Stuck during update
Sebastiann70 said:
Hi All!
I just receive a new firmware MPN24.104-44.
Anybody else?
Click to expand...
Click to collapse
I did, but my phone keeps hanging during the update. I need to reset it at the boot menu. Else its stuck in a loop trying to install the update, then reboots and starts over again. I dont know what i should do.
LloydGSR said:
Unrelated to updates, how did you get the black/dark theme?
Click to expand...
Click to collapse
Just use substratum and download the "A swift dark theme" from the store.
mrbracht said:
Just use substratum and download the "A swift dark theme" from the store.
Click to expand...
Click to collapse
How did you get Substratum to work? None of the themes I've tried are working, keeps saying exception in trying to install.
EpsiMaxx said:
I did, but my phone keeps hanging during the update. I need to reset it at the boot menu. Else its stuck in a loop trying to install the update, then reboots and starts over again. I dont know what i should do.
Click to expand...
Click to collapse
Scrap my past post, I think I know what it is (and not the same as yours). We'll see.
Hey guys, just curious do we need to un-root our device before updating via OTA or can we keep our device rooted and apply update without any issues? Also does root survive after updating to a new version via OTA? I havent got my phone yet, still shipping..
mhp1995 said:
Hey guys, just curious do we need to un-root our device before updating via OTA or can we keep our device rooted and apply update without any issues? Also does root survive after updating to a new version via OTA? I havent got my phone yet, still shipping..
Click to expand...
Click to collapse
You can try to install SuperSU survival script but I haven't tried it, I'm rooted , running xposed and ultered some system files so the ota will not flash on my system.
You'll definitely have to flash stock recovery and uninstall any customizations you have made to your system.
I tried flashfire myself and it wouldn't flash the ota for me.
Sent from my XT1635-02 using XDA-Developers Legacy app
You can't keep root to accept the OTA. If anything in the /system, /oem, /boot, /recovery partitions are different from what it expects, it'll fail with error 7.
To revert to a state where you can accept the OTA, go get the correct stock image file for your variant. In my case, it was XT1635-02_ADDISON_RETUS_MPN24.104-49_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip (you can download stock images from https://mirrors.lolinet.com/firmware/moto/addison/official/).
In the zip file will be boot.img, oem.img, recovery.img, and system.img_sparsechunk.0 (all the way through system.img_sparsechunk.10). You need to flash all 13 of those files from the bootloader:
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
From there, boot into the OS and check for update, it'll go through the process, reboot into the stock recovery and go through the OTA update.
Wife's unlocked/GSM MZP got the November Security patch a couple days ago. I would think Moto would be trying to update this phone to Nougat soon after the Z and Z Force got it last month, but that doesn't seem to be the case. Even the Moto G got updated before this phone.
Oh well, Nougat doesn't really bring much to the phone anyways, I've had it on my 6P since its release. It will be interesting to see if this phone gets even better battery life after the update though. 10+ hours of SoT in a charge is already insane.

back to stock android marshmallow or nougat [too new security patch i think?]

Hello, i currently run the Tesla rom on my moto g4 plus xt1642 from this one https://forum.xda-developers.com/moto-g4-plus/development/7-1-1-ground-zero-roms-validus-tesla-t3553036
and i tried to flash this one:
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
but i get error saying downgrading security and one time it worked and i had no wifi.
So i returned back to the tesla one from a backup and now my fingerprint is not working and i have 1 sim card slot instead of 2. So basicly it is now a moto g4. I want to return it to stock marshmellow or nougat but i think my security patch is too new or something.
Flashing any other rom is not working also i get boot loops always
can someone help me?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
codGmer said:
Hello, i currently run the Tesla rom on my moto g4 plus xt1642 from this one https://forum.xda-developers.com/mo...7-1-1-ground-zero-roms-validus-tesla-t3553036
and i tried to flash this one:
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
but i get error saying downgrading security and one time it worked and i had no wifi.
So i returned back to the tesla one from a backup and now my fingerprint is not working and i have 1 sim card slot instead of 2. So basicly it is now a moto g4. I want to return it to stock marshmellow or nougat but i think my security patch is too new or something.
Flashing any other rom is not working also i get boot loops always
can someone help me?
Click to expand...
Click to collapse
• What build of Stock Firmware ?
• Are you Dirty Flashing Other ROMs ?
If you want to downgrade to stock MM, skip flashing the bootloader and partition table. After this, if WiFi and the SIMs work fine, then good; else flash the Nougat modem (only the modem).
tywinlannister7 said:
If you want to downgrade to stock MM, skip flashing the bootloader and partition table. After this, if WiFi and the SIMs work fine, then good; else flash the Nougat modem (only the modem).
Click to expand...
Click to collapse
I have trouble flashing because it always hangs at "sending system" on sparcechunk files.
And if i do one by one it succeeds eventually(with rebooting fastboot etc) but then i get the MOTO powered by android screen and it just does nothing.
i have this one: https://www.filefactory.com/file/6j...24.139-13.1_cid50_subsidy-DEFAULT_CFC.xml.zip
codGmer said:
I have trouble flashing because it always hangs at "sending system" on sparcechunk files.
And if i do one by one it succeeds eventually(with rebooting fastboot etc) but then i get the MOTO powered by android screen and it just does nothing.
i have this one: https://www.filefactory.com/file/6j...24.139-13.1_cid50_subsidy-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
Think that's the wrong firmware for XT1642 devices, so I'm hoping you've not flashed it (if I recall, our earliest Marshmallow build was 139-23.4 https://forum.xda-developers.com/showpost.php?p=68618242&postcount=8), and looking at your baseband, looks like the installer has decided your phone is a G4 (not a G4 Plus) as you've noticed (70009.08.03... is a G4 baseband, whereas G4 Plus devices are 70030.25.03...)
You may be able to rescue it by flashing the correct firmware from here https://mirrors.lolinet.com/firmware/moto/athene/official/RETAIL/ (e.g. either the 23.4 build, though it seems listed for XT 1622, so you may wish to double check this will flash okay. Also, the 139-48 build is listed for XT 1642 devices). I would strongly recommend to do some research, to confirm what builds are correct before you flash anything, as flashing the wrong file may further damage your device.
When flashing, are you wiping your data and executing the erase commands (e.g. fastboot erase cache, fastboot erase userdata), and are you able to use another USB data cable/ USB port just in case there's a bad cable or port?
Thanks for the messages
the 23.4 one didn't work also stuck at the moto logo screen.
i always do this after i extract the rom files:
Code:
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash dsp adspso.bin
mfastboot flash oem oem.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot erase customize
mfastboot erase clogo
codGmer said:
Thanks for the messages
the 23.4 one didn't work also stuck at the moto logo screen.
i always do this after i extract the rom files:
Code:
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash dsp adspso.bin
mfastboot flash oem oem.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot erase customize
mfastboot erase clogo
Click to expand...
Click to collapse
Hmm, that flashing list seems okay, did the commands execute correctly without error (and you observed [OKAY] with each command)? Maybe look into trying with the minimal ADB rather than the mfastboot adb client, perhaps? (v1.4.2 is here https://forum.xda-developers.com/showthread.php?t=2317790) Just remember to use fastboot rather than mfastboot for those commands.
How long did you leave your device at the moto screen for? Your device may take time (perhaps 3-5 minutes, maybe slightly longer than that) to boot since you've wiped your user data and cache.
I have to redo the sparcechunks one by one because it just hangs and then reboot bootloader and then try again till it says OK. So yeah everything is ok but i don't know if this redoing influcuences something?
codGmer said:
I have to redo the sparcechunks one by one because it just hangs and then reboot bootloader and then try again till it says OK. So yeah everything is ok but i don't know if this redoing influcuences something?
Click to expand...
Click to collapse
Difficult to tell, given the flashing was designed to happen at the same time. You may be okay or perhaps the hang/reboot is messing up the flash and hence why you're unable to boot. What's telling is that you seem to be able to flash custom ROMs okay, which suggests your flash memory is working. How long do you wait before you decide your script has hung, and does the flashing also hang if you perform the flashing manually (i.e. copy pasting each command into the adb client and waiting for it to complete)?
Are you using your original cable as supplied with your device to connect to your computer with, and have you tried using another USB port? I'm wondering if something is wrong with the USB cable, or USB port in delivering data to your device, or even the microUSB port on your device.
about 1 minute when it says sending system and then i get FAILED (data transfer failure (Unknown error)) so its a usb problem you think? i use different cables and different usb ports they make no differance. I know some usb ports are bad, i am trying to install ubuntu to do it there maybe it makes a difference. i am trying to flash the other one you've supplied me [EDIT] STuck on motorola boot logo again.
And i don't mean the loading logo that it is stuck on but on the moto powered by android before the animation.
i use twrp and when i go to mount then it won't allow me to mount data and system, then i have to format those and i can access them again i dont know if that has something to do with it?
i flashed in the past my bootloader and gpt this could also be the problem. My bootloader info is:
Code:
BL0.0C ( sha-0d66019, 2016-04-01 12:16:00)
baseband: M8952_70030.25.03.62R etc
product/variant: athene_16mp XT1642 16gb P2a
serial number ZY2239QDL4
cpu MSM8952
eMMC 16gb samsung qe13mb rv=08 pv=07 fv=00000000000000007
dram : 2gb samsung lp3 DIE:8gb m5=01 m6=05 m7=00 m8=1f
console [null]: null
battery ok (charging)
flashing_unlocked
software status:modified
transer mode: usb connected
suddenly my phone is booting after i did the batch file once again and it went flawless without any errors????
second sim not working have to wait to check the fingerprint.
i now have the 139-48 build and after flashing a nougat modem it is now M8952_70030.25.03.62R broadband but still no fingerprint.
i have tried many different firmware but doesn't help
I have given up for now. I have reset my bootloader with qualcomm refresher tool, and tried 15 firmwares i think. Read many texts about it and still the installeren thinks nu phone is a moto G4 instead of G4 plus. I think it is easy to fix but i have to have some help to do it exactly right.
Replied to the other thread you made. Definitely seems likely that it is related to the partition table/bootloader so flashing system/boot is not going to help. Was the common cause that we both had N, then reflashed using the batch file and did the March security path - perhaps multiple times?
I'm no android expert but If someone with a working G4+ with build number NPJS25.93-14-4 could post their bootloader/partion table images and we compare ours, maybe we could look for differences?
Seems like this can be done by dumping the boot partition
https://forum.xda-developers.com/showthread.php?t=2450045
parted /dev/sda print > gpt.bin
the output of this might be helpful too:
adb shell
ls -al /dev/block/platform/dw_mmc/by-name
I realize this is quite a bit to ask someone with a working phone to do, but it would be awesome to get to the bottom of this.
Definitely learning something here - I assumed a nandroid backup was a full backup of my device and that as long as I didn't brick my device, I would be able to get back to my previous version.
Hello, i am on official Indian nougat 7.0, and fed up with heating and battery drain in standby, i want to go back to MM. Can some one link me to the guide for going back to stock marshmallow.
Thanks

Brick moto g4 xt1622

Hi, yesterday i have unlock bootloader of my moto g4, xt 1622 , i have flashed twrp and this is perfect, but after i have flashed zip of magisk.zip for root permission, when i reboot i obtain only black screen and led white ( intermittence led) .
The device is recognize by windows 10 (in test mode and no signature driver verify ) but not in tray bar..
Mode recognized by pc are:
in fast boot like " fastboot athene_13mp S " in "other device"
In adb mode " sideload" ( from stock recovery) like "Moto g4 plus " in device manager/usb devices"
I have stock recovery and can't start blank flash because the device isn t recognized by pc like qualcomm device..
What can i do??? Thanks a lot my friends!!
The problem is that magisk is not compatible with the Stock kernel, so if you want magisk you need to flash a custom kernel, i recomend this: https://elementalx.org/devices/moto-g4/ you need to flash the kernel and after this flash magisk.
Regards
Wow! So the phone is save? ?
And what can i flash pther kernel, can i have a guide plz? Can i flash with sideload? Thanks!
Yes, you need to enter un recovery, conect your phone to pc and with adb put in the cmd adb sideload nameofyourzip.zip and then flash magisk with sideload if hoy wanr
Unfortunately i recive this error.. what can i do? Thanks!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ok, first you need to install twrp: https://forum.xda-developers.com/mo...p-twrp-3-0-2-2-recovery-moto-g4-plus-t3386586
Then you need to go in twrp to avanced and adb sideload and flash it.
Hmm, can you confirm if you have stock Marshmallow (6.0.1) or Nougat (7.0) on your device? I see from the stock recovery version that it's 6.0.1/MPJ24.139-23-4 (a really old build of Marshmallow).
Thanks ismael! I m going to try it
@ECHO first of this mods, the smartphone have nougat full stock. When i have installed twrp the sistem started normally, but when i flashed magisk the sistem started with black screen, before this i ve factory reset and flash a zip of stock rom.. and start a very problem!!
Thaks a lot to all for help me and sorry for my bad english.
David
scossa1994 said:
Thanks ismael! I m going to try it
@ECHO first of this mods, the smartphone have nougat full stock. When i have installed twrp the sistem started normally, but when i flashed magisk the sistem started with black screen, before this i ve factory reset and flash a zip of stock rom.. and start a very problem!!
Thaks a lot to all for help me and sorry for my bad english.
David
Click to expand...
Click to collapse
Thanks, as Ismael034202 pointed out above, if you were on stock Nougat, then you will need to flash a custom kernel, as rooting on the stock Motorola Nougat kernel will cause a boot failure. If you were still on Nougat, then you could have followed this guide https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918 with flashing magisk instead of SuperSU.
As you've re-flashed the old Marshmallow stock ROM, then you do not need a custom kernel (Marshmallow stock ROM kernels are less strict about rooting), flashing TWRP and then flashing magisk should work on Marshmallow.
However, you need to be very careful if you revert back to full stock - as you've appeared to have downgraded from Nougat, taking OTA updates may hard brick your device. If you can remember what Nougat stock ROM you had before unlocking your device, I would recommend downloading a copy of that stock ROM and using the stock ROM to update. Try not to use stock OTA updates.
Very well explained echo92. +1 ?
what can i flash somethings?? because usb debug is off after wipe dataa, and i can t enter in android to activate it!! plz help
i think that android is stock nougat, with old stock recovery and magisk(the real problem) and stock kernel.
what can i solve?
thanks
scossa1994 said:
what can i flash somethings?? because usb debug is off after wipe dataa, and i can t enter in android to activate it!! plz help
i think that android is stock nougat, with old stock recovery and magisk(the real problem) and stock kernel.
what can i solve?
thanks
Click to expand...
Click to collapse
Hmm, in that case, the easiest way may be to flash the latest stock ROM to your device and start over again. As an alternative, do you have a TWRP backup of your device?
For XT1622, you'll likely want NPJS25.93-14-13 (Nougat, 7.0 stock, December 2017 security patch) firmware from here: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Download and extract as directed in the post, and to flash to repair your device, use the following flashing commands:
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 dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Click to expand...
Click to collapse
This should not re-lock your bootloader. Next, download TWRP, ElementalX and magisk and flash as I suggested in the guide above. The basic guide for rooting on Nougat is:
a)Flash/boot TWRP. Backup your device.
b)Flash ElementalX.
c)Flash magisk or SuperSU.
d)Wipe cache/Dalvik in TWRP.
e)Reboot and wait for boot.
f)Any issues, revert to your backup made in a)
Can i use fastboot within debug usb off? Because i recive an error, i m tryng and post a pic.
Thanks
This is my situation after try to use fastboot
Hace you installed Motorola drivers for pc, you can use fastboot without USB debugging
https://mobilesupport.lenovo.com/rola/es/solution/MS89882 This os the link for the fastboot drivers
Thanks guys!! I had write the stock 7.0!! Now the phone is perfect!! Thanks!!
I had wrong driver and pc not recognized the phone!! Now yes ??
Now install twrp, elementalX Kernel, magisk and enjoy
Hi i need urgent help. My Moto g4 plus is not starting anymore. I was using it and but suddenly switched off and nithing works now. Only the led light comes two times when charging cable is connected. Please help help
It was rooted.
Moto Singh said:
Hi i need urgent help. My Moto g4 plus is not starting anymore. I was using it and but suddenly switched off and nithing works now. Only the led light comes two times when charging cable is connected. Please help help
It was rooted.
Click to expand...
Click to collapse
Can you enter in bootloader pressing vol - and power?? If is possible is not problem because you can flash stock rom in fastboot.
scossa1994 said:
Can you enter in bootloader pressing vol - and power?? If is possible is not problem because you can flash stock rom in fastboot.
Click to expand...
Click to collapse
No nothing is working.
Moto Singh said:
No nothing is working.
Click to expand...
Click to collapse
I don t know.. the problem is the corrupted bootloader ( i think..)

Categories

Resources