Database Users

Issue upgrading ZE551KL to Marshmallow

Trying to upgrade my ZE551KL to Marshmallow but I've hit an issue. I'll recap all the steps I went through today and then the error I'm getting:
Started the day with firmware 763
Took a backup with TWRP
Updated FW to 1106, 1234 and 1531 in sequence in order to prepare for update to Marshmallow
Took one more backup with TWRP
Attempted update to MM using download from ASUS, manually initiating from recovery, got the error below
Attempted update to MM again using the notification prompt after booting phone with update file on SD card (per ASUS' instructions), got the same result, below.
The error text is this:
Code:
Can't install this M package (Tue May 17 23:05:50 CST 2016)
L less than 20160426 build (Tue Dec 1 17:16:17 CST 2015)
E:Error in /sideload/package.zip
(Status 7)
E: fota_return_code 409
It seems this error typically means that the current Lollipop version is old and needs to be updated to the latest before trying to update to MM. I've validated in the About screen that my firmware version is indeed 1531 so I'm not sure what else I need to do.
I apologize if this question has been answered elsewhere. I hunted around for a while on this forum and using Google and didn't find anyone that seemed to be in this same situation.
Thank you for the help!

did you try with the stock recovery.img of 1531?
I had the exact same problem the only thing worked with TWRP was to use the back2stock method.
http://forum.xda-developers.com/zen...50kl-ze551kl-zd551kl-ze600kl-ze601kl-t3333482

murat124 said:
did you try with the stock recovery.img of 1531?
I had the exact same problem the only thing worked with TWRP was to use the back2stock method.
http://forum.xda-developers.com/zen...50kl-ze551kl-zd551kl-ze600kl-ze601kl-t3333482
Click to expand...
Click to collapse
Well I never actually flashed TWRP, I just booted it using fastboot each time I needed it. Does flashing the OTA updates update the recovery or do I have to do that manually?

I got the exact error you are getting with original recovery or TWRP. The only difference is that I was using MM and deleted the OS by mistake so I could not reflash official MM . back2stock method was the only way. Now I have TWRP, official MM via back2stock and root at the same time.
I am sure more expert members can give you better advice.

murat124 said:
I got the exact error you are getting with original recovery or TWRP. The only difference is that I was using MM and deleted the OS by mistake so I could not reflash official MM . back2stock method was the only way. Now I have TWRP, official MM via back2stock and root at the same time.
I am sure more expert members can give you better advice.
Click to expand...
Click to collapse
Does back2stock require a full wipe? I was hoping not to have to do that...

bennettj1087 said:
Trying to upgrade my ZE551KL to Marshmallow but I've hit an issue. I'll recap all the steps I went through today and then the error I'm getting:
[*]Updated FW to 1106, 1234 and 1531 in sequence in order to prepare for update to Marshmallow
Click to expand...
Click to collapse
Worked in my case when I updated to latest lollipop firmware available.
(Actually I never installed the complete firmware, just flashed
Code:
boot.img
and
Code:
recovery.img
for the latest lollipop firmware available and marshmallow FW installed like a charm, though I'd suggest you install the complete lollipop framework)

Help - T Mobile OTA 7.1.2 Update fails with "Error" on Stock Android 7.1.1

Hi,
My 6P is on 7.1.1 Stock Android and I recently unlocked my bootloader, downgraded radio to 3.72 from 3.78 since 3.78 radio was giving LTE issues on T-Mobile. And yesterday, I saw the OTA 7.1.2 update message, so I tried to install, but after re-start, around 30% through the installation process, it suddenly aborts to "Error!". The update availability message again appeared this morning, only to error out again the same way.
I didn't see anyone having similar issue, so wanted to post here to see what could I do.
Thanks

solluidforever said:
Hi,
My 6P is on 7.1.1 Stock Android and I recently unlocked my bootloader, downgraded radio to 3.72 from 3.78 since 3.78 radio was giving LTE issues on T-Mobile. And yesterday, I saw the OTA 7.1.2 update message, so I tried to install, but after re-start, around 30% through the installation process, it suddenly aborts to "Error!". The update availability message again appeared this morning, only to error out again the same way.
I didn't see anyone having similar issue, so wanted to post here to see what could I do.
Thanks
Click to expand...
Click to collapse
OTAs will not install if you have changed any partition. Think of OTAs like a puzzle piece. You can change one side of the puzzle piece by cutting it off to suit your needs, however you have effectively ruined the possibility of the next piece fitting into where you cut off.
Download the Full OTA Image and ADB sideload the OTA. This is the only present form of "OTA" that will install over any user modifications done to the phone. This process will not wipe your phone.
https://developers.google.com/android/ota
Sent from my Nexus 5X using Tapatalk

Thank you. Someone on reddit suggested another option of flashing the radio image for 3.78(which was the one for 7.1.1) and then to try the OTA - Luckily, he uploaded the 3.78 radio image file on gdrive, so I pulled it and succesfully was able to update to 7.1.2.
The issue is that as observed in other threads, only 3.72 radio is the only temporary radio image file which lets me have stable LTE connection on T-Mobile. So, if I want to flash back 3.72 radio image now, for future update I realize that I need to have a 3.81(tied to 7.1.2 build) raido image file as backup. Can you let me know if it's easy for a newbie to understand how to obtain the radio image file? I downloaded 7.1.2 (N2G47J) file from the URL you provided, and it contains radio.modem.img file. Is that it?

I was in the nexus 6p beta program. I am currently suffering the GOOGLE boot loop. Current build on the phone is N2G47i. Out of no where , the phone froze , reboot and just got stuck and never boot pass the GOOGLE boot screen.
I tried to ADB Sideload , but it would not take any file , be it OTA or FUll image that is older than March 8 , as the N2G47i build. is new than the official build. There is no new build newer than March 8 as far as i can tell. My phone is stock non root and bootloader locked. If anyone can assist , I would appreciated.

solluidforever said:
Thank you. Someone on reddit suggested another option of flashing the radio image for 3.78(which was the one for 7.1.1) and then to try the OTA - Luckily, he uploaded the 3.78 radio image file on gdrive, so I pulled it and succesfully was able to update to 7.1.2.
The issue is that as observed in other threads, only 3.72 radio is the only temporary radio image file which lets me have stable LTE connection on T-Mobile. So, if I want to flash back 3.72 radio image now, for future update I realize that I need to have a 3.81(tied to 7.1.2 build) raido image file as backup. Can you let me know if it's easy for a newbie to understand how to obtain the radio image file? I downloaded 7.1.2 (N2G47J) file from the URL you provided, and it contains radio.modem.img file. Is that it?
Click to expand...
Click to collapse
Hello, you can download the desired radio here: https://www.androidfilehost.com/?w=files&flid=49332
The link above belongs to an XDA dev!
You can flash it with fastboot from bootloader (bootloader needs to be unlocked by the way) with:
fastboot flash radio radio.img
Where radio.img is the radio you want to flash. Assuming you have basic knowledge on how to use adb/fastboot...
Good luck...
510jungleboy said:
I was in the nexus 6p beta program. I am currently suffering the GOOGLE boot loop. Current build on the phone is N2G47i. Out of no where , the phone froze , reboot and just got stuck and never boot pass the GOOGLE boot screen.
I tried to ADB Sideload , but it would not take any file , be it OTA or FUll image that is older than March 8 , as the N2G47i build. is new than the official build. There is no new build newer than March 8 as far as i can tell. My phone is stock non root and bootloader locked. If anyone can assist , I would appreciated.
Click to expand...
Click to collapse
Hello... Isn't N2G47H newer than N2G47I ?
Try sideloading 7.1.2 public release: https://dl.google.com/dl/android/aosp/angler-ota-n2g47h-f3bffaba.zip
Supposed to be the latest...
If the above doesn't work, try factory reset from recovery. If your bootloader is unlocked, you can try to flash a full stock image from Google site: https://dl.google.com/dl/android/aosp/angler-n2g47h-factory-f1111327.zip
If nothing work, you should likely think about RMA your device.
Good luck...

5.1 said:
Hello, you can download the desired radio here: https://www.androidfilehost.com/?w=files&flid=49332
The link above belongs to an XDA dev!
You can flash it with fastboot from bootloader (bootloader needs to be unlocked by the way) with:
fastboot flash radio radio.img
Where radio.img is the radio you want to flash. Assuming you have basic knowledge on how to use adb/fastboot...
Good luck...
Hello... Isn't N2G47H newer than N2G47I ?
Try sideloading 7.1.2 public release: https://dl.google.com/dl/android/aosp/angler-ota-n2g47h-f3bffaba.zip
Supposed to be the latest...
If the above doesn't work, try factory reset from recovery. If your bootloader is unlocked, you can try to flash a full stock image from Google site: https://dl.google.com/dl/android/aosp/angler-n2g47h-factory-f1111327.zip
If nothing work, you should likely think about RMA your device.
Good luck...
Click to expand...
Click to collapse
Actually I mistype the build number. The build number I have is NPG47i. This build is dated on March 8. The official build is March 3rd , even though it final release was in April. SO I would need a build that would be dated higher than March 8.

510jungleboy said:
Actually I mistype the build number. The build number I have is NPG47i. This build is dated on March 8. The official build is March 3rd , even though it final release was in April. SO I would need a build that would be dated higher than March 8.
Click to expand...
Click to collapse
Ok. Got it. Well... I guess you have to wait next month if you don't want to RMA. Sorry...
Good luck...

510jungleboy said:
Actually I mistype the build number. The build number I have is NPG47i. This build is dated on March 8. The official build is March 3rd , even though it final release was in April. SO I would need a build that would be dated higher than March 8.
Click to expand...
Click to collapse
If you still have a warranty you should RMA your device. Doing a stock OTA update when you are fully on stock with no modifications shouldn't boot loop your phone unless there is something wrong with it. These phones have serious build issues that cause them to permanently bootloop, seemingly out of nowhere. From what I've read people don't generally recover from the type of boot loop you are describing but good luck. If the phone isn't under warranty it's likely time for a new one. The 6P doesn't seem to last very long past the expiration of the warranty.

Thanks for the link
5.1 said:
Hello, you can download the desired radio here: https://www.androidfilehost.com/?w=files&flid=49332
The link above belongs to an XDA dev!
You can flash it with fastboot from bootloader (bootloader needs to be unlocked by the way) with:
fastboot flash radio radio.img
Where radio.img is the radio you want to flash. Assuming you have basic knowledge on how to use adb/fastboot...
Click to expand...
Click to collapse
Hi, thanks for the url, that is really helpful. Also, I realized that, the file is also available in the unzipped version of Nexus 6P Image file. So, it was helpful for me to learn alternatives along with process. :good:

[HELP]: XT1644 Keeps Rebooting to TWRP After Moto Security Update

Received security update notification from Moto, and installed.
Moto G4+ XT1644 (4GB/64GB)
TWRP 3110, ElementalX kernel, Magisk rooted, custom logo
bootloader unlocked
Latest TWRP backup on 08/31/17
After install:
Phone now always reboots to TWRP
tried wiping data, cache, Dalvik but no difference
tried restore backup but still reboots to TWRP
Can only shut phone off via power button
Any advice to get my phone back to normal will be greatly appreciated. Thanks.

mel2000 said:
Received security update notification from Moto, and installed.
Moto G4+ XT1644 (4GB/64GB)
TWRP 3110, ElementalX kernel, Magisk rooted, custom logo
bootloader unlocked
Latest TWRP backup on 08/31/17
After install:
Phone now always reboots to TWRP
tried wiping data, cache, Dalvik but no difference
tried restore backup but still reboots to TWRP
Can only shut phone off via power button
Any advice to get my phone back to normal will be greatly appreciated. Thanks.
Click to expand...
Click to collapse
You messed up your rom by installing official update on custom kernel. Can you boot from twrp to system? What happens if you do that? Which stock rom you have exactly? Otherwise you can flash stock rom with fastboot, but never downgrade!

strongst said:
Can you boot from twrp to system? What happens if you do that? Which stock rom you have exactly? Otherwise you can flash stock rom with fastboot, but never downgrade!
Click to expand...
Click to collapse
Thank you for your reply, strongst. When I press the Reboot->System buttons in TWRP, the phone boots back to TWRP recovery.
Here are the stats I recorded before things went sideways:
Original stock firmware Build Number - NPJS25.93-14-4
Original OS version - 7.0
Original Kernel - 3.10.84-gb9596e1 [email protected] #1 Fri Mar 3 02:04:02 CST 2017
Original Baseband version - M8952_70030.25.03.62RATHENE_RETUSA_CUST
Updated Kernel - 3.10.84-ElementalX-G4-1.04 [email protected] #1 Sat Mar 11 14:16:55 EST 2017
Note: I found NPJS25.93-14-4 firmware at
https://www.getdroidtips.com/npjs25-93-14-4-march-security-moto-g4-plus
but it's titled as "March 2017 security patch" OTA update. I'm not sure if that is full replacement firmware or not.
If necessary, should I simply flash NPJS25.93-14 (full firmware) via fastboot and allow Moto to finish the updates via OTA?

mel2000 said:
Thank you for your reply, strongst. When I press the Reboot->System buttons in TWRP, the phone boots back to TWRP recovery.
Here are the stats I recorded before things went sideways:
Original stock firmware Build Number - NPJS25.93-14-4
Original OS version - 7.0
Original Kernel - 3.10.84-gb9596e1 [email protected] #1 Fri Mar 3 02:04:02 CST 2017
Original Baseband version - M8952_70030.25.03.62RATHENE_RETUSA_CUST
Updated Kernel - 3.10.84-ElementalX-G4-1.04 [email protected] #1 Sat Mar 11 14:16:55 EST 2017
Note: I found NPJS25.93-14-4 firmware at
https://www.getdroidtips.com/npjs25-93-14-4-march-security-moto-g4-plus
but it's titled as "March 2017 security patch" OTA update. I'm not sure if that is full replacement firmware or not.
If necessary, should I simply flash NPJS25.93-14 (full firmware) via fastboot and allow Moto to finish the updates via OTA?
Click to expand...
Click to collapse
You can also flash the latest available for your device with June security patch. After that you can root again with ex kernel if you want https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Make sure to mount storage within twrp first and save your internal memory before flashing stock rom!

In future, if that happens, you could try booting to the bootloader, then on the bootloader screen, press 'Start' and try to get your device to boot normally. Credit to: https://forum.xda-developers.com/showpost.php?p=72114657&postcount=170
Personally, I'd go with strongst's suggestion to flash the June 2017 stock fastboot ROM - you'd have to revert to stock (completely) anyway to accept the OTA - as you've found out, OTAs will only successfully flash onto a device with stock recovery, kernel, and unmodified system including no root. You may as well update at the same time to the same patch level that the OTA would have brought you up to.

echo92 said:
In future, if that happens, you could try booting to the bootloader, then on the bootloader screen, press 'Start' and try to get your device to boot normally. Credit to: https://forum.xda-developers.com/showpost.php?p=72114657&postcount=170
Personally, I'd go with strongst's suggestion to flash the June 2017 stock fastboot ROM - you'd have to revert to stock (completely) anyway to accept the OTA - as you've found out, OTAs will only successfully flash onto a device with stock recovery, kernel, and unmodified system including no root. You may as well update at the same time to the same patch level that the OTA would have brought you up to.
Click to expand...
Click to collapse
This 100%. Boot into bootloader and choose start from there. I ran into the same issue last night whilst trying to update my XT1644 and figure this out through trial and error. Once I got it back up though, flashing many stock recoveries that I found online couldn't get the update to work either. It would error out a few seconds after booting into the stock recovery and starting the update. I finally resigned to re-flashing a stock image of marshmallow and updating it all again from there. I wanted to pull the stock recovery before I replaced it with TWRP again but I couldn't find a way to do that. Any method I found required having root access already, and of course I can't get root access without flashing a custom recovery first.

echo92 said:
In future, if that happens, you could try booting to the bootloader, then on the bootloader screen, press 'Start' and try to get your device to boot normally.[/url]
Click to expand...
Click to collapse
Thanks for all replies. Rebooting from the bootloader screen brought my phone back to normal. Same March 2017 patch, as well as the same TWRP and ElementalX kernel and build number. Unlocked bootloader logo.bin remains intact. Magisk is still at v13.3 and it passes SafetyNet. Internal memory intact. I'm relieved.
Settings->System Updates->New version NPJ25.93-14.5
However, I'm now contemplating whether it'll be worthwhile to patch my phone to the NPJ25.93-14.5, June 2017 update.
Can I assume that the June 2017 1.1 GB "patch" contains the full NPJ25.93-14.5 firmware for XT1644?
( https://www.androidfilehost.com/?fid=889764386195918175 )
Is there a way to flash the June 2017 ROM via TWRP, and without having to reinstall ElementalX kernel, etc.?

mel2000 said:
Thanks for all replies. Rebooting from the bootloader screen brought my phone back to normal. Same March 2017 patch, as well as the same TWRP and ElementalX kernel and build number. Unlocked bootloader logo.bin remains intact. Magisk is still at v13.3 and it passes SafetyNet. Internal memory intact. I'm relieved.
Settings->System Updates->New version NPJ25.93-14.5
However, I'm now contemplating whether it'll be worthwhile to patch my phone to the NPJ25.93-14.5, June 2017 update.
Can I assume that the June 2017 1.1 GB "patch" contains the full NPJ25.93-14.5 firmware for XT1644?
( https://www.androidfilehost.com/?fid=889764386195918175 )
Is there a way to flash the June 2017 ROM via TWRP, and without having to reinstall ElementalX kernel, etc.?
Click to expand...
Click to collapse
Yes it's the full rom. And no, you need to flash kernel and magisk after every rom flash, stock twrp, fastboot or custom rom doesn't matter(otherwise it's already included).

strongst said:
Yes it's the full rom. And no, you need to flash kernel and magisk after every rom flash, stock twrp, fastboot or custom rom doesn't matter(otherwise it's already included).
Click to expand...
Click to collapse
Thanks again strongst. I'm still contemplating because of the complexity. However, the constant phone notification to update is weakening my resistance. Not sure I want to have to look at that for days on end.
Just to clarify, are you stating that I won't have to reinstall TWRP? That would be a relief.
Would it suffice to copy my internal SD to my PC and restore it later? Do I need to copy everything? Will my Nandroid backup save my Magisk settings?

I did make a TWRP backup of the XT1644 updated to NPJ25.93-14.5. I could share it with you if you'd like. However, you'd still need to flash ElementalX and root after.

mel2000 said:
Thanks again strongst. I'm still contemplating because of the complexity. However, the constant phone notification to update is weakening my resistance. Not sure I want to have to look at that for days on end.
Just to clarify, are you stating that I won't have to reinstall TWRP? That would be a relief.
Would it suffice to copy my internal SD to my PC and restore it later? Do I need to copy everything? Will my Nandroid backup save my Magisk settings?
Click to expand...
Click to collapse
You need to flash twrp after you flashed the stock rom cause the stock rom flash the stock recovery. Copy the whole internal memory, better to save everything when you don't know exactly what you need
Restore the whole internal memory isn't good, just restore what's missing if you recognize it. Your magisk settings will be saved with nandroid, that's true, but don't restore your partitions from nandroid backup from your prior rom version to the new, that cause trouble. Make backup of your apps with titanium backup instead.

Just to clarify - are you on the Amazon software channel (amz) or do you have the Amazon Prime edition of the XT1644 (with the ads on the lockscreen)? I'm just curious as whether this NPJ25.93-14.5 update is exclusive to Amazon or if it's more widespread.
EDIT - seen a couple of users reporting they've received it on the retus channel, so maybe more widespread to US users, maybe to include the Verizon emergency calling patch that the G5 Plus got too?

tmp000 said:
I did make a TWRP backup of the XT1644 updated to NPJ25.93-14.5. I could share it with you if you'd like. However, you'd still need to flash ElementalX and root after.
Click to expand...
Click to collapse
That sounds great tmp000. I'd definitely like you to share it. How would I go about flashing it? Any particular precautions? Thanks.

mel2000 said:
That sounds great tmp000. I'd definitely like you to share it. How would I go about flashing it? Any particular precautions? Thanks.
Click to expand...
Click to collapse
Sorry, I'm not an expert, so I can't say much about precautions. What I will do is tell you what I did to get my phone to its current state now is:
Backup my data
After failing to apply the NPJ25.93-14.5 update many times through a bunch of different stock recoveries that I found online (including versions extracted from full stock ROMs), I found a way to downgrade back to the stock ROM of Marshmallow for the XT1644. I applied all the OTA updates, all the way to NPJ25.93-14.5.
At this point, I flashed TWRP recovery again. At the same time, right after running the command to flash TWRP with fastboot, I also flashed logo.bin to get rid of that unlocked bootloader message. I then booted into TWRP and then backed up the system and boot partition as it was (so stock kernel and no root).
In TWRP, I flashed ElementalX, and then SuperSU after that (I know you are using a different root method so flash yours).
Then I restored the data (data partition only) of the backup I made.
After that, I rebooted into system and everything booted up just fine. I had root access and all of my data was intact. Your steps 2 and 3 would be:
Put my backup with your other backups in the TWRP folder
Do an wipe in TWRP to wipe dalvik cache, cache, system, and boot. DO NOT WIPE INTERNAL STORAGE
Then continue on with step 4 from above. And of course, I can't emphasize enough to back up your data. Not just through TWRP, but any photos, etc that you can copy onto your computer first. I'll PM you a link to my backup.

strongst said:
Your magisk settings will be saved with nandroid, that's true, but don't restore your partitions from nandroid backup from your prior rom version to the new, that cause trouble.
Click to expand...
Click to collapse
Thanks for the advice. However, I'm having trouble determining exactly what I need to backup before the firmware flash.
Which folders from the Root dir of internal memory need to be saved?
Do I need to save the SDCARD directory?
Can I use TWRP to restore individual apps within the Nandroid backup instead of the whole archive?
Just trying to be extra careful to preempt things from going sideways. Thanks.

echo92 said:
I'm just curious as whether this NPJ25.93-14.5 update is exclusive to Amazon or if it's more widespread.
Click to expand...
Click to collapse
I have the retail version of xt1644 and hope that NPJ25.93-14.5 is intended for or compatible with that.

tmp000 said:
I'm ready to do the NPJ25.93-14..5 update. For clarity, I reordered your steps for the update:
Backup my data
Put my backup with your other backups in the TWRP folder
Do an wipe in TWRP to wipe dalvik cache, cache, system, and boot.DO NOT WIPE INTERNAL STORAGE
In TWRP, I flashed ElementalX, and then SuperSU after that (I know you are using a different root method so flash yours).
Then I restored the data (data partition only) of the backup I made.
Click to expand...
Click to collapse
Am I to assume that after step 2 or 3, the actual updating consists of doing a TWRP Restore using the NPJ25.93-14.5 folder that I downloaded? Do I do the wipes before the Restore update? Thanks again for all your help.

mel2000 said:
Am I to assume that after step 2 or 3, the actual updating consists of doing a TWRP Restore using the NPJ25.93-14.5 folder that I downloaded? Do I do the wipes before the Restore update? Thanks again for all your help.
Click to expand...
Click to collapse
Yes, wipe then restore the backup. Sorry for the terrible instructions with missing steps.

mel2000 said:
Received security update notification from Moto, and installed.
Moto G4+ XT1644 (4GB/64GB)
TWRP 3110, ElementalX kernel, Magisk rooted, custom logo
bootloader unlocked
Latest TWRP backup on 08/31/17
After install:
Phone now always reboots to TWRP
tried wiping data, cache, Dalvik but no difference
tried restore backup but still reboots to TWRP
Can only shut phone off via power button
Any advice to get my phone back to normal will be greatly appreciated. Thanks.
Click to expand...
Click to collapse
When you are booted in twrp, reboot to bootloader of system (obviously). Then press power button when it displays start. Like this the phone will boot into system and not in recovery
Or
Just reboot to bootloader and read the thread attached with it.
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
Be sure to turn on usb debugging and oem unlock mode

DgnrtnX said:
When you are booted in twrp, reboot to bootloader of system (obviously). Then press power button when it displays start. Like this the phone will boot into system and not in recovery
Or
Just reboot to bootloader and read the thread attached with it.
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
Be sure to turn on usb debugging and oem unlock mode
Click to expand...
Click to collapse
Thank you for your reply DgnrtnX. It matches the successful solution I received from exho92 on 09/01/17. The only issue is that I need to boot via that method each time. I no longer boot directly into my system. However I plan to update to NPJ25.93-14.5 shortly so I'm hoping the reboot issue will go away if that upgrade goes well.
USB debugging and OEM unlock were already enabled and remain so.

Can't turn on moto g4 plus

I cannot turn on moto g4 plus. While connecting the charger the led is blinking but cannot see the charging sign on screen. Please help

What ROM were you running and what device do you have?
Did you flash anything or install anything prior to your device being in this state?

echo92 said:
What ROM were you running and what device do you have?
Did you flash anything or install anything prior to your device being in this state?
Click to expand...
Click to collapse
I was using AICP oreo, but after that i unroot my device and backed to stock.i installed the security patch and after that it's dead. Nothing else i did.
My device is XT1643

Krish_Vihaag said:
I was using AICP oreo, but after that i unroot my device and backed to stock.i installed the security patch and after that it's dead. Nothing else i did.
My device is XT1643
Click to expand...
Click to collapse
Sounds like you bricked it cause you take ota on stock rom and you don't have stock recovery I think... You should try to flash the stock rom via fastboot https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Your information about what you did isn't exactly enough to provide a detailed troubleshooting. If you have more detailed information which steps you exactly take and which rom versions you restored etc it would be helpful.

Krish_Vihaag said:
I was using AICP oreo, but after that i unroot my device and backed to stock.i installed the security patch and after that it's dead. Nothing else i did.
My device is XT1643
Click to expand...
Click to collapse
Do you remember what version of stock ROM you had when you flashed AICP ?
I don't think you had December's security patch as itis just month old, so you can try blank-flash with September's patch update.
to blank-flash (download September's gpt and bootloader, where it's mentioned on thread)
Follow it.: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
EDIT: Before proceeding to blank-flash, can you tell us if you have access to bootloader or recovery ?
If not, then proceed for blank-flash.

After flashing my phone with Moto G4 Plus XT1640-43 ATHENE NPJ25.93-14 Stock Img, I tried to update the April 2018 security patch. After that my phone doesn't start. Then I use blank flash and my phone starts with recovery mode. Now the problem is when I try to flash my phone again, it say security version downgrade and FAILED. Can you guys please help me into this?

Mayur Thakur said:
After flashing my phone with Moto G4 Plus XT1640-43 ATHENE NPJ25.93-14 Stock Img, I tried to update the April 2018 security patch. After that my phone doesn't start. Then I use blank flash and my phone starts with recovery mode. Now the problem is when I try to flash my phone again, it say security version downgrade and FAILED. Can you guys please help me into this?
Click to expand...
Click to collapse
Sounds like you flashed the Dec 2016 security patch firmware, and then took an OTA - the OTA update on a downgraded firmware likely is what hard bricked your device.
Flash this April 2018 stock firmware: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
In future, please do not flash older stock firmware, or if you do downgrade, please do not use OTA updates. The safest way to update is to flash the latest stock firmware for your device/region - after that, OTA updates may be safe.

MOTO G4 plus stock rom
MOTO G4 plus will get OREO update officially so I flashed latest firmware via fastboot on my phone so can update it through ota update when it will be able without bricking my phone or else when it comes I should download the zip and flash it with fastboot with step same step of flahsing nougat forward on my phone

Gaminwarrior said:
MOTO G4 plus will get OREO update officially so I flashed latest firmware via fastboot on my phone so can update it through ota update when it will be able without bricking my phone or else when it comes I should download the zip and flash it with fastboot with step same step of flahsing nougat forward on my phone
Click to expand...
Click to collapse
Nobody can tell you about future things, but in my opinion it should be like this.

Cannot update stock rom

My phone has its bootloader unlocked and ive had customs ROMs in the past - I ended up loosing my IEMI and the EFS files, so I went back to stock and got the IEMI and EFS back.
Iam currently on NPNS25.137-93-4, has any one else had this issue were the OTA update will not work? it will start the update process and ends up with a droid laying down with an error " ! " coming out of it. In addition when I boot my phone the "unlocked bootloader warning" says "ID: bad key" were before it said "ID: N/A" with the lineage ROM - Not sure if it matters. Should I relock my bootloader?
or does anyone have a link for the newest update XT1687 north america?

I am also on NPNS25.137-93-4. I tried installing with adb sideload but installation was aborted. I also tried installing with stock recovery but the my phone can not mount internal or external storage

jgmmjg said:
I am also on NPNS25.137-93-4. I tried installing with adb sideload but installation was aborted. I also tried installing with stock recovery but the my phone can not mount internal or external storage
Click to expand...
Click to collapse
You think its the version thats the issue?

vonwap said:
My phone has its bootloader unlocked and ive had customs ROMs in the past - I ended up loosing my IEMI and the EFS files, so I went back to stock and got the IEMI and EFS back.
Iam currently on NPNS25.137-93-4, has any one else had this issue were the OTA update will not work? it will start the update process and ends up with a droid laying down with an error " ! " coming out of it. In addition when I boot my phone the "unlocked bootloader warning" says "ID: bad key" were before it said "ID: N/A" with the lineage ROM - Not sure if it matters. Should I relock my bootloader?
or does anyone have a link for the newest update XT1687 north america?
Click to expand...
Click to collapse
When I tried unlocking my phone and installing 64-bit TWRP incorrectly, I ran into an issue similar to you. Now, my phone was on an older software version so I was able to fully install a firmware the fixed my device. (It had an 83 in it, can't remember what it was fully.) I'd look for a NPS25.137-93-14 build and flash all the files. That's the latest XT1687 build.

reCoded said:
When I tried unlocking my phone and installing 64-bit TWRP incorrectly, I ran into an issue similar to you. Now, my phone was on an older software version so I was able to fully install a firmware the fixed my device. (It had an 83 in it, can't remember what it was fully.) I'd look for a NPS25.137-93-14 build and flash all the files. That's the latest XT1687 build.
Click to expand...
Click to collapse
As far as I know there's no 93-14 version available, the last build uploaded is 93-10. There's a 92-14 firmware but that one is for India/Brazil only.
Sent from my Moto G5 Plus using XDA Labs

Wolfcity said:
As far as I know there's no 93-14 version available, the last build uploaded is 93-10. There's a 92-14 firmware but that one is for India/Brazil only.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
damn thats my problem i guess