Database Users

[how to] downgrade moto x after ota camera patch update, lost root ability

{
"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,
I dont have enough posts to post in dev section so I posted here and put is on my blog as well.
DISCLAIMER: I AM NOT RESPONSIBLE FOR ANYTHING THAT MIGHT OCCURE WITH YOUR DEVICE. PLEASE READ ALL ARTICLES IN FULL BEFORE ATTEMPTING.
(Only tested for Rogers, cannot guarantee this works with other firmwares but I do not see why it wouldn't)
Not sure is this was covered before but I couldnt find anything with respect to my situation. I recently discovered a way to DOWNGRADE my MOTO X after I installed the OTA camera patch that allowed rooting via JCASE's PwnMyMoto to not work. I tried using RSDLite to flash back to the original stock firmware to no avail. I was lazy and did NOT google around and didnt read JCASE's updated disclaimer on his [Root/Write Protection Bypass] MotoX (no unlock needed) post at XDA that read
"The latest OTAs patch this exploit
The "Camera patch" patches the vulnerability we use to gain system user, and pwnmymoto will no longer work on devices with this update"
All credit where credit is due, I simply discovered a flaw to undo the update OTA camera patch giving me back the ability to use JCASE root method, which involved swapping the gpt.bin file from the new stock firmware found here: http://sbf.droid-developers.org/ghost_rcica/list.php
ROGERS-CA_XT1058_4.2.2-13.9.0Q2.X-116-LCX-36_cid14_CFC_1FF.xml.zip (camera patch)
to the original
Rogers_XT1058_4.2.2-13.9.0Q2.X-116-LCX-26-34_CFC_1FF.xml.zip (no camera patch)
I then fired up RSDLite removed the necessary line from the XML to allow the flashing of the original firmware and voila!!!!!! bobs your uncle! the OTA appeared on screen asking to be installed. Ignore for now root your phone using JCASE PwnMyMoto found in the link below:
[Root/Write Protection Bypass] MotoX (no unlock needed)
If you want to apply the OTA patch I highly recommend you read both JCASE article in full and the one below as well before attempting to do this. The article below describes how to preserve root and apply the OTA camera patch.
Tutorial: How To Protect and Restore Root for an OTA Update
All credit for rooting and saving/preserveing root to JCASE and Dark9781 on XDA developers.
Thank you.

g01di3l0ck5 said:
Hello,
I dont have enough posts to post in dev section so I posted here and put is on my blog as well.
DISCLAIMER: I AM NOT RESPONSIBLE FOR ANYTHING THAT MIGHT OCCURE WITH YOUR DEVICE. PLEASE READ ALL ARTICLES IN FULL BEFORE ATTEMPTING.
(Only tested for Rogers, cannot guarantee this works with other firmwares but I do not see why it wouldn't)
Not sure is this was covered before but I couldnt find anything with respect to my situation. I recently discovered a way to DOWNGRADE my MOTO X after I installed the OTA camera patch that allowed rooting via JCASE's PwnMyMoto to not work. I tried using RSDLite to flash back to the original stock firmware to no avail. I was lazy and did NOT google around and didnt read JCASE's updated disclaimer on his [Root/Write Protection Bypass] MotoX (no unlock needed) post at XDA that read
"The latest OTAs patch this exploit
The "Camera patch" patches the vulnerability we use to gain system user, and pwnmymoto will no longer work on devices with this update"
All credit where credit is due, I simply discovered a flaw to undo the update OTA camera patch giving me back the ability to use JCASE root method, which involved swapping the gpt.bin file from the new stock firmware found here: http://sbf.droid-developers.org/ghost_rcica/list.php
ROGERS-CA_XT1058_4.2.2-13.9.0Q2.X-116-LCX-36_cid14_CFC_1FF.xml.zip (camera patch)
to the original
Rogers_XT1058_4.2.2-13.9.0Q2.X-116-LCX-26-34_CFC_1FF.xml.zip (no camera patch)
I then fired up RSDLite removed the necessary line from the XML to allow the flashing of the original firmware and voila!!!!!! bobs your uncle! the OTA appeared on screen asking to be installed. Ignore for now root your phone using JCASE PwnMyMoto found in the link below:
[Root/Write Protection Bypass] MotoX (no unlock needed)
If you want to apply the OTA patch I highly recommend you read both JCASE article in full and the one below as well before attempting to do this. The article below describes how to preserve root and apply the OTA camera patch.
Tutorial: How To Protect and Restore Root for an OTA Update
All credit for rooting and saving/preserveing root to JCASE and Dark9781 on XDA developers.
Thank you.
Click to expand...
Click to collapse
removing the necessary line from the xml I don't feel like would solve the problem. I think once you take the OTA it puts code in the bootloader that doesn't allow you to downgrade. Since bootloaders are locked for people that are actually stuck on the update (because they would just unlock the BL if they were and wanted to downgrade) I didn't think there was a way to downgrade since we can't touch the BL. Maybe rogers is different or you didn't take the full OTA but Id like to know if anyone else has success with this.

Can already verify this doesn't work with ATT. I've tried changing the same file to old/new/other carrier, didn't matter. Once you get past the GPT flash that works, the rest will still fail.

rmead01 said:
Can already verify this doesn't work with ATT. I've tried changing the same file to old/new/other carrier, didn't matter. Once you get past the GPT flash that works, the rest will still fail.
Click to expand...
Click to collapse
Try unlocking the bootloader first. Google "moto x unlock bootloader", i can't post links yet. Open motorola's link.
After that, follow what the OP said.

dliberalesso said:
Try unlocking the bootloader first. Google "moto x unlock bootloader", i can't post links yet. Open motorola's link.
After that, follow what the OP said.
Click to expand...
Click to collapse
Unlocked bootloader is necessary.

dliberalesso said:
Try unlocking the bootloader first. Google "moto x unlock bootloader", i can't post links yet. Open motorola's link.
After that, follow what the OP said.
Click to expand...
Click to collapse
ATT and VZW bootloaders are locked. This is why it won't work.

dliberalesso said:
Try unlocking the bootloader first. Google "moto x unlock bootloader", i can't post links yet. Open motorola's link.
After that, follow what the OP said.
Click to expand...
Click to collapse
The reason most people want to downgrade after an OTA is because they lost root. If they could unlock the bootloader, they could just get root again and not have to downgrade.

Most pointless thread ever. Root normally with unlocked bootloader and still have fixes. You don't need an exploit to root if your bootloader is unlocked.
Sent from my XT1055 using Tapatalk

Does anyone from rogers know if the first file name mentioned is a working Rogers with ota?
Sent from my XT1058 using Tapatalk

Instructions for root
g01di3l0ck5 said:
Hello,
I dont have enough posts to post in dev section so I posted here and put is on my blog as well.
DISCLAIMER: I AM NOT RESPONSIBLE FOR ANYTHING THAT MIGHT OCCURE WITH YOUR DEVICE. PLEASE READ ALL ARTICLES IN FULL BEFORE ATTEMPTING.
(Only tested for Rogers, cannot guarantee this works with other firmwares but I do not see why it wouldn't)
Not sure is this was covered before but I couldnt find anything with respect to my situation. I recently discovered a way to DOWNGRADE my MOTO X after I installed the OTA camera patch that allowed rooting via JCASE's PwnMyMoto to not work. I tried using RSDLite to flash back to the original stock firmware to no avail. I was lazy and did NOT google around and didnt read JCASE's updated disclaimer on his [Root/Write Protection Bypass] MotoX (no unlock needed) post at XDA that read
"The latest OTAs patch this exploit
The "Camera patch" patches the vulnerability we use to gain system user, and pwnmymoto will no longer work on devices with this update"
All credit where credit is due, I simply discovered a flaw to undo the update OTA camera patch giving me back the ability to use JCASE root method, which involved swapping the gpt.bin file from the new stock firmware found here: http://sbf.droid-developers.org/ghost_rcica/list.php
ROGERS-CA_XT1058_4.2.2-13.9.0Q2.X-116-LCX-36_cid14_CFC_1FF.xml.zip (camera patch)
to the original
Rogers_XT1058_4.2.2-13.9.0Q2.X-116-LCX-26-34_CFC_1FF.xml.zip (no camera patch)
I then fired up RSDLite removed the necessary line from the XML to allow the flashing of the original firmware and voila!!!!!! bobs your uncle! the OTA appeared on screen asking to be installed. Ignore for now root your phone using JCASE PwnMyMoto found in the link below:
[Root/Write Protection Bypass] MotoX (no unlock needed)
If you want to apply the OTA patch I highly recommend you read both JCASE article in full and the one below as well before attempting to do this. The article below describes how to preserve root and apply the OTA camera patch.
Tutorial: How To Protect and Restore Root for an OTA Update
All credit for rooting and saving/preserveing root to JCASE and Dark9781 on XDA developers.
Thank you.
Click to expand...
Click to collapse
I am new here to the forums, and I have a tmobile moto x (unlocked bootloader) running 4.4 with camera update. I just want to know your exact method on how to downgrade.
I know I download the older firmware, then is there a Mac version or equivalent to the rsdlite as I only have access to a Mac? I also do not know what to revert back to.
Any help would be appreciated.

[GUIDE]ROOT Your LG Marshmallow ROM With Systemless ROOT. No More ExFAT Issues!

This is not a fix for already persisting issues. If you're currently dealing with ExFAT (or BT) issues, Systemless ROOT will not help you. Bring your device in a state where you don't have these issues by flashing a stock ROM matching exactly your variant and location. Then use Systemless ROOT using a custom recovery.
Unlocked Bootloaders Only
Confirmed working by me on a H815-EUR bought in Germany.
UPDATE: Confirmed to be working on following MM ROMs:
H815 EUR 20A/C/D Germany
H815 EUR 20B Poland
H815 EUR 20A Croatia
Please report if this works for you according to this scheme: H815-EUR-20A-GERMANY
Legend
Blue: Device Model
Black: Device region
Red: Firmware Version
Green: Location
Simple:
After flashing or updating to a stock LG MM ROM, boot into TWRP and flash Chainfire's Systemless ROOT 2.67. It'll automatically backup, patch and flash the Kernel. It'd be great if you could confirm by giving details about your device, e.g. "H815-EUR Germany" or "H815-EUR Poland" etc.
As stated by @Chainfire in his thread:
If you are coming from a SuperSU install in /system, you must re-flash the stock system partition contents prior to installing this.
If you are coming from a SuperSU system-less install, you must re-flash the stock kernel prior to installing this.
If TWRP tells you SuperSU is not installed, and asks you to install it, do not do it, you will break things!
Future updates will be significantly less painful
Click to expand...
Click to collapse
With the introduction of TWRP 3.X.X., this is no longer an issue. TWRP will no longer ask to install SuperSU if it detects a Marshmallow ROM.
For G4 (H815) users:
You have to reflash the latest stock KDZ or .zip (modem, system, boot - restart recovery - bootloader) if you're currently dealing with exFAT issues. Then you can fire up TWRP and flash Systemless ROOT 2.67.
The reason why you might want to use this method to root instead of simply flashing a pre-patched Kernel is differences in ROM versions. As it happened to me, on my H815-EUR from Germany, I received the MM update. It was called "20A" for some reason, but it has the same fixes and updates as 20B. So it's not to be confused with the early 20A build from Poland! Quick as I am, I flashed the repacked boot.img for 20A by @cile381 and lost exFAT support, and somehow corrupted ADB, since cile381's repacked kernel was built from and for the Poland 20A build.
I hope this'll help you =)

Great, but if it's not necessary to flash a modified boot image anymore, do we could have root permission with Android MM, by flashing a modified system image (with supersu injected) by using the DD method with Android 5.1 running? This can be helpful for people who can't unlock the bootloader

Andrea__93 said:
Great, but if it's not necessary to flash a modified boot image anymore, do we could have root permission with Android MM, by flashing a modified system image (with supersu injected) by using the DD method with Android 5.1 running? This can be helpful for people who can't unlock the bootloader
Click to expand...
Click to collapse
No, that's not true. You still need a modified boot.img. With this method, you basically create your very own patched kernel, from the boot.img extracted from your very device.
MM still requires a patched/repacked kernel.
EDIT: Ok, now I see where the confusion came from. Misleading title.

thank you ! very useful ...
i have a question :
why ,with a phone (bootloader unlocked) with MM 6 ,it's possible to easily have a root .......but the locked device no ? ===> but instead of use TWRP , by injecting only the SuperSU with adb fastboot (or kdz pack?) for locked device???

Basically, Marshmallow has very strict security restrictions. The stock kernel won't allow any modifications. That's why we need a modified (vulnearable) one. You can simply flash a modified kernel onto a bootloader unlocked device. But since you can't flash custom boot.img's on locked devices, people with non-unlockable devices currently have no way to root their MM devices.
More details can be found in this XDA article.

very very interesting what you have said ,thank you for sharing and help
i didn't know MM...
that's mean ther NEVER have a chance for a root of MM with locked bootloader !!! if i have correctly understood ...
the only way is to unlock this damned bootloader ......or downgrade to LP by LG-UP (kdz) and then root with fastboot method ??? i'm true ???
i just discover this LG G4
in the past i have had a LG optimus series ...with old methods and full possibilities !
i begin to believe that it's the begining of the dead of android development if all manufacturers and google "lock" and add too many securities on these news devices with "hard" methods ...

Haha, sure! You're welcome =)
I wouldn say "never". There's always a chance that a genius will find a way. You also need to factor in the relatively young age of the G4.
To the last part: Yeah, it's getting harder and harder. But nothing unexpected. Remember, power users like us do only make up a very small, almost insignificant amount of all the Android users out there. I'm sure most people don't even know what Android is. Google just went full on Spock and said "Thee needs of the many outweigh the needs of the few or the one" :laugh:

ho my god ...sh** ........
imagine the future LG G5 (and others manufacturers ) with bootloader locked !!!! and if they never want to unlock with these new security politic........and this damned MM for original firmware more and more securised ==> we all profoundly have it on ours ass !!!
otherwise there are big chance to hard brick devices with bests devs attempts ...
Sorry for my bad words ,but this xda article that you previously have given to me ,make me really afraid !!!!!!! ...
Another big question :
when we have done MM update on G4 ,i have read that it's possible to easily downgrade to LP with LG-UP ....but full upgrade ??? it change this new MM bootloader with LP one ? for to have the possibility to root with locked bootloader ...

"While horror for us XDA people, it's better for the general public." This is how I think Google and OEMs justify their decision (which I find questionable tbh). But enough of that. Let's keep it on topic. I'd love to see reports from you whether it worked or not. Please include your ROM version, device and the country it was bough in. E.G. H815-EUR v20A Germany.
Btw. This just happened
{
"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"
}

Just used this on LG G4 H81520A, ( bootloader officially LG Unlocked ) went sweet as a nut.

I think if you flashed the repacked 20B boot.img it's possible you wouldn't have had ExFat issues. German 20A is Polish 20B. When you mismatch boot.img's you have ExFAT issues.
Systemless root is certainly nice though. I wasn't aware there was an automated tool now. Will make getting root after a new release even easier now

I'm not worried about the G5 to be honest. The LG v10 makes it as easy as on Nexus to unlock the bootloader: Look here. Sorry for offtopic, but it really fitted for me .

MickyFoley said:
I'm not worried about the G5 to be honest. The LG v10 makes it as easy as on Nexus to unlock the bootloader: Look here. Sorry for offtopic, but it really fitted for me .
Click to expand...
Click to collapse
If it is only for the T-Mobile variant they are probably at the same (if not worse) point that the G4 is. At least we can officially unlock some devices...

nitrous² said:
"While horror for us XDA people, it's better for the general public." This is how I think Google and OEMs justify their decision (which I find questionable tbh). But enough of that. Let's keep it on topic. I'd love to see reports from you whether it worked or not. Please include your ROM version, device and the country it was bough in. E.G. H815-EUR v20A Germany.
Click to expand...
Click to collapse
ok ,sorry for out of topic ...
i keep you thread preciously whe i will decide to unlock my bootloader thank again and again !
MickyFoley said:
I'm not worried about the G5 to be honest. The LG v10 makes it as easy as on Nexus to unlock the bootloader: Look here. Sorry for offtopic, but it really fitted for me .
Click to expand...
Click to collapse
i like your optimism ! i want to believe ...

I never had exfat problem with cile381 repacked kernel as autoprime stated it only happens if boot. Img mismatches. Other than that maybe this method could solve exfat problem on cm13?

@i-m: exFAT-issues of CM13 should be solved at 7th of December :
Code:
g4: vold: enable native exfat support (android_device_lge_g4-common)
g4: build exfat driver (android_kernel_lge_msm8992)

autoprime said:
I think if you flashed the repacked 20B boot.img it's possible you wouldn't have had ExFat issues. German 20A is Polish 20B. When you mismatch boot.img's you have ExFAT issues.
Systemless root is certainly nice though. I wasn't aware there was an automated tool now. Will make getting root after a new release even easier now
Click to expand...
Click to collapse
I did that too. I mean, flashing repacked 20B on German 20A. I then no longer had issues with exFAT formatted cards, but ADB was still "corrupted", meaning it wouldn't let me authorize my PC and the option to de-authorize was no longer available in the developer settings menu. Of course, might as well be an isolated case.
i-m said:
I never had exfat problem with cile381 repacked kernel as autoprime stated it only happens if boot. Img mismatches. Other than that maybe this method could solve exfat problem on cm13?
Click to expand...
Click to collapse
Sure you hadn't. But if you read OP closely, you'll see why some people, me included, had issues. No, it will not solve exFAT issues for CM13.
MickyFoley said:
@i-m: exFAT-issues of CM13 should be solved at 7th of December :
Code:
g4: vold: enable native exfat support (android_device_lge_g4-common)
g4: build exfat driver (android_kernel_lge_msm8992)
Click to expand...
Click to collapse
It was still broken when I tried the nighlty from December 7th.

Followed OP, root is working.
Still can't use my SD Card as on rooted 5.1:
- in FX Explorer I need to set a bookmark to a mounted location somewhere deep in the root filesystem,
- Lightroom says SD Card not available.
But this is a Marshmallow specific problem, isn't it?

Jens1969 said:
Followed OP, root is working.
Still can't use my SD Card as on rooted 5.1:
- in FX Explorer I need to set a bookmark to a mounted location somewhere deep in the root filesystem,
- Lightroom says SD Card not available.
But this is a Marshmallow specific problem, isn't it?
Click to expand...
Click to collapse
Apps have to be updated for proper support for SD cards. I switched to Solid Explorer because FX hasn't been updated for months.

Jens1969 said:
Followed OP, root is working.
Still can't use my SD Card as on rooted 5.1:
- in FX Explorer I need to set a bookmark to a mounted location somewhere deep in the root filesystem,
- Lightroom says SD Card not available.
But this is a Marshmallow specific problem, isn't it?
Click to expand...
Click to collapse
This is not a fix for devices that ran into SdCard issues. This is supposed to help you prevent exFAT issues from happening. The pre-requisite is an alread working device without exFAT issues.
This is specifically for Marshmallow devices. I'm surprised your device booted up after this Systemless ROOT patches your Marshmallow FW's kernel.

How to upgrade to .67 version ?

Hi ! I was using custom roms on my phone then I switched back to stock nd also I relocked my bootloader but after that I cant update it to .67 version I am on .35 version. I am from India and everyone has received OTA for .67 version but mine doesnt shows any update. Any help ?
Sent from my Moto G (5) Plus using Tapatalk

deepu28792 said:
Hi ! I was using custom roms on my phone then I switched back to stock nd also I relocked my bootloader but after that I cant update it to .67 version I am on .35 version. I am from India and everyone has received OTA for .67 version but mine doesnt shows any update. Any help ?
Click to expand...
Click to collapse
Same problem here.

You'd have to be on the NPN25.137-15 firmware to have received the .67 update - if you're on the retin software channel, I think the .35 version is the incorrect one for your channel (.35 is for US devices, if I recall). Therefore, you'll likely not get any updates, and if you were to flash the NPNS25.137-35-5 update, may mean you cannot downgrade in future.
If you're on the retin channel and want the .67 update, then unfortunately you'll likely have to unlock your bootloader (wiping your device) then attempt to flash NPN25.137-15 (do your research first and ensure this does not brick your device), then you should be able to update to NPN25.137-67. As far as I know, there is no fastboot ROM currently for NPN25.137-67 so re-locking the bootloader is not possible at the moment.

echo92 said:
You'd have to be on the NPN25.137-15 firmware to have received the .67 update - if you're on the retin software channel, I think the .35 version is the incorrect one for your channel (.35 is for US devices, if I recall). Therefore, you'll likely not get any updates, and if you were to flash the NPNS25.137-35-5 update, may mean you cannot downgrade in future.
If you're on the retin channel and want the .67 update, then unfortunately you'll likely have to unlock your bootloader (wiping your device) then attempt to flash NPN25.137-15 (do your research first and ensure this does not brick your device), then you should be able to update to NPN25.137-67. As far as I know, there is no fastboot ROM currently for NPN25.137-67 so re-locking the bootloader is not possible at the moment.
Click to expand...
Click to collapse
I downgraded my phone from .35 to .15 version and now I have received OTA and have successfully updated to .67 version.
Sent from my Moto G (5) Plus using Tapatalk

deepu28792 said:
I downgraded my phone from .35 to .15 version and now I have received OTA and have successfully updated to .67 version.
Sent from my Moto G (5) Plus using Tapatalk
Click to expand...
Click to collapse
Please provide instructions for this, I am unable to downgrade.

earlycray said:
Please provide instructions for this, I am unable to downgrade.
Click to expand...
Click to collapse
Its really simple. Just download the firmware .15 from the link below and flash it. If you have already re-locked ur bootloader thn flash the full firmware and if not yet unlocked use the commands provide in the thread. The .15 version shows for Brazil but it works with our Indian version too. Try it I did the same.
https://forum.xda-developers.com/showthread.php?t=3638835
Press thanks if I helped you.

deepu28792 said:
Its really simple. Just download the firmware .15 from the link below and flash it. If you have already re-locked ur bootloader thn flash the full firmware and if not yet unlocked use the commands provide in the thread. The .15 version shows for Brazil but it works with our Indian version too. Try it I did the same.
https://forum.xda-developers.com/showthread.php?t=3638835
Press thanks if I helped you.
Click to expand...
Click to collapse
{
"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"
}
I am receiving this error. I was previously on NPNS25.137-35-5.

earlycray said:
I am receiving this error. I was previously on NPNS25.137-35-5.
Click to expand...
Click to collapse
then you cant downgrade. I thought you were on .35, I have read it somewhere that if u r on .35-5 then you cannot downgrade
Sent from my Moto G (5) Plus using Tapatalk

deepu28792 said:
then you cant downgrade. I thought you were on .35, I have read it somewhere that if u r on .35-5 then you cannot downgrade
Sent from my Moto G (5) Plus using Tapatalk
Click to expand...
Click to collapse
I will have to wait for full image of -67 to upgrade, correct ?

earlycray said:
I will have to wait for full image of -67 to upgrade, correct ?
Click to expand...
Click to collapse
I'm not even sure if you can flash the NPN25.137-67 image even, MarckozZ downgraded from NPNS25.137-35-5 to NPN25.137-15 and attempted to take the OTA to NPN25.137-67, which hard bricked their device. https://forum.xda-developers.com/showpost.php?p=73029820&postcount=70
Though they were able to recover their device, it looks like updating is very risky/not possible after the recovery: https://forum.xda-developers.com/g5-plus/help/moto-g5-plus-hard-bricked-recognized-t3636457
Now, the fastboot of NPN25.137-67 might not let you flash the GPT and bootloader over the NPNS25.137-35-5 and let you flash the rest of the OS, but that's asking for trouble when an OTA arrives - hopefully the OTA scripts would check for a bootloader/GPT mismatch, but they may not and you could run into a hard brick.

echo92 said:
the fastboot of NPN25.137-67 might not let you flash the GPT and bootloader over the NPNS25.137-35-5
Click to expand...
Click to collapse
Wow. I dun goofed. What are my options at this point? Also, could you kindly please explain the above ?

earlycray said:
Wow. I've done goofed. What are my options at this point? Also, could you kindly please explain the above ?
Click to expand...
Click to collapse
As I understand it, fastboot has checks built in that communicate with the bootloader and verify whether the GPT/bootloader of the firmware you're attempting to flash can be flashed. If you have a newer bootloader on your device, then your bootloader may refuse to permit the flash of the older bootloader (especially with the NPNS25.137-35-5 update, which appears to have a critical security bug fixed in the May 2017 patch, so downgrading would allow you to re-open that bug, which Motorola wouldn't want).
Now, you can get around this, in theory, by omitting GPT and bootloader from your fastboot flash, so fastboot may flash the rest of your system. However, now you'll have a NPN25.137-67 system, but a GPT/bootloader from NPNS25.137-35-5. Though this should run, it becomes very risky if you choose to install an OTA and forget you have this mismatch; the OTA will think you have the NPN25.137-67 firmware and patch accordingly, which may seriously corrupt your bootloader. In that case, you'll have to use a blankflash to recover your device (if it works) and be unable to recover your data, unless it was held on a SD card mounted in portable storage. I've seen similar scenarios occur with the Moto G4 (luckily we've just got a new blankflash to recover from the June 2017 security patch) and with the Moto Z Play.
In summary, you could flash the NPN25.137-67 firmware when it comes out, but the mismatch makes updates very risky - I personally wouldn't use the fastboot updates in this situation. You might wish to look into the TWRP flashables of the NPN25.137-67, as they'll update the system side of things (and most if not all the functions of your device should work as though you were still on stock NPN25.137-67), but without the risk of bricking your device. Granted, you'll have to unlock and flash TWRP in this situation though, and you will no longer be able to flash OTA updates, though hopefully the TWRP flashable maintainer will update the TWRP flash file to the newest OTA.
I'm not aware of other options besides keeping an eye out for NPNS25.137-35-5 updates, unfortunately, as your device is off the official update path Later on, Motorola may unify firmware updates into one global file, but for the time being, just be careful (and also be aware that the patch situation is a bit confusing!). On the other hand, at least you've got a May security patch

If I simply stuck to the current firmware, what would happen? The NFC chip appears to be working even tho this is the us? Model.

earlycray said:
If I simply stuck to the current firmware, what would happen? The NFC chip appears to be working even tho this is the us? Model.
Click to expand...
Click to collapse
Hang on, which model of the Moto G5 Plus are you using?
Cause depending on the model, you might actually be on the right firmware and not need the -67 update (which is usually only for retin, Indian retail) devices...
To clarify, as far as I know:
retin (I think retla too?) devices should be on NPN25.137-67 (March 2017 security patch)
retus devices should be on NPNS25.137-33-5 (May), NPNS25.137-35-5 (May) or NPN25.137-43-5 (Verizon specific, March)
reteu devices should be on NPNS25.137-33-5 (May)
From your previous posts you've got a XT1685?

That is correct. However it was purchased in Australia. And judging by some Australian tech forums the latest fw is -67.

[Help Me] Moto G5 Plus Hard Bricked & Solved

Hello All,
Recently my device Moto G5 Plus Hard Bricked and was not opening. When I plug data cable to laptop or Charger LED light was blinking. I have searched many threads on this Forum but finally, somehow I managed to recover my Device. (This thread Helped me to recover my device https://forum.xda-developers.com/showpost.php?p=73268905) And the thing is BlankFlash (@vache) for POTTER was not working on my device and I have searched thread and got to know that I have downgraded update and due to this my device has eaten up my bootloader. So now one of the members of this forum (@Rakesh1b) helped me to recover my device as he said "Now I need to blank flash (ALBUS) with Moto Z2 Bootloader (it has worked with many members and me too) on Moto G5 Plus and it worked fine and I cannot Install Stock ROM on POTTER rather I have to install Stock ROM which STOCK TOM DEODEXED DEBLOATED" then I can Install any Custom ROM on it! You can see the picture I have attached to this thread.
Now my actual problem is "I want to go back to my STOCK ROM (I need OTA Updates though) with Relock Bootloader" Can anyone help me to figure out these problems which I am facing now.
{
"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"
}

Bro sorry to say this that until we get an updated blankflash which has an updated bootloader and gpt version of potter which has either the same or higher version that we had in our mobile when they're bricked i.e mostly after May or June or same as April version of bootloader we cannot get back to stock room because you know that the bootloader and gpt are of motoz so obviously the ROM won't bootup due to mismatch so let's hope and wait for the developers or any member until they release a leaked Motorola blankflash with updated blankflash there is nothing we can do until then but just wait in xda for motog4 also same happened when many had updated through OTA to take nougat and they had downgraded before that and they had waited for 4 to 6 months till and updated blankflash is leaked but in our case we are very lucky that Albus blankflash worked and we are able to use our phones ,potter blankflash will work for them who had not updated bootloader when flashing different ROMs the npns35-5,npns33-3,.67 OTA had updated bootloader and gpt if we have not tried any of these then vaches blankflash will work.
I am confident that an updated blankflash with the bootloader and gpt of the updated version will be released but we have to wait till then we can only hope that vache sees our problem then there is chance because the current blankflash is even provided by him thanks a ton vache without your help many potters would have been in coma.
Guys first don't hardbrick your mobile read everything carefully then flash if they're safe. That they won't mess with your bootloader.
Caution:
* Don't take OTA after downgrading ROM.
* Flash any stock ROMs through fastboot only.
And there is not much problem with custom ROMs which are twrp flashable.

Bhai, suppose if vache releases updated Blank Flash for Moto G5 plus with updated bootloader then can we Install NPN137.15 then get OTA directly to NPN137. 67??? Is this possible if he releases the updated one???
Also please inform me if vache releases updated version of Blank Flash. Because badly I'm in need of this. Hope you understand my pain !!!

If vache releases an updated blankflash with updated bootloader and gpt then you can flash npn15 through fastboot ROM but if you again try to take OTA then what happens is if the bootloader version in OTA is old compared to bldr version in blankflash then you will again successfully hardbrick your mobile now same blankflash can be used again to revive it back but the solution is when an updated blankflash comes then whatever stock ROMs we flash we have to just flash them using fastboot method in this method if we are on a latest available ROM and we try to downgrade to old version of ROM then fastboot will safely don't allow us to flash the old rom saying downgrade error or even it flashes it will leave the bootloader and gpt with the updated version and only flashes system images and you could boot up your downgraded ROM the thing is fastboot verifies and keeps us in safe zone but in the case of OTA it doesn't check all that but only checks if it is on the correct default ROM for which the OTA is released and patches the ROM with all the contents in it so we are risking taking the OTA so safe method is to flash only fastboot stock ROMs that will be released and stay with them if we are clear about the versions of bootloader gpt then we can take OTA there is no problem but many don't know that and they try and bricked their devices.
Hope you understood.

Dear posters... 3 things:
1. Please do NOT keep quoting the previous post - there's no point and it just slows page loads down.
2. Do NOT keep "mentioning" other members in your posts. This REALLY annoys those you have mentioned as their inbox gets full of repeated childish demands for attention. And guess what? They ignore them... and you.
3. Questions must be asked in the Q and A Forum. So moved.

If anyone finds the Blank Flash updated version for Moto g5+ with updated bootloader please let me know through this thread. I'll be thankful.

Can anyone help me to get a better camera quality on custom ROM

anthonyqwe said:
Can anyone help me to get a better camera quality on custom ROM
Click to expand...
Click to collapse
No Chance Bro, only on stock you can achieve...

@Rakesh1b Bro, as you know I'm using Albus bootloader in my potter. So can I use albus stock ROM in my potter??

?? bro I could understand your desperation there is no other way other than using twrp based stock ROMs or any custom ROMs for us u had been using debloated stock ROM since I bricked it is much more faster and stable than Moto stock images don't try any other ROMs which are not meant for motog5plus plus because there kernel source varies and configuration varies so don't try any other ROM and mess your potter u will make it totally unusable if even the current blankflash fails to work after installing any other ROM.
Hope you understood.
Be cool just enjoy your potter till new blankflash is released.
Bye..

@vache please help!!!

the best option we have since i also hardbricked and returned thanks to albus, is to wait for the release of Oreo, rather than using new blank flash, with oreo stock rom image (around 1.5 gb) and flashing it through fastboot we'll be able to return to stock since will have new updated recovery gpt and whatever is needed. by the monent as Rakesh1b said debloated is better than stock faster cleaner etc and the otas.......not necesary really i have installes lineage 14.1 (nougat based) and works awesome, maybe ill move to 15 once more stable and may be even before the offic( oreo based) ial release of oreo.

LLegion said:
the best option we have since i also hardbricked and returned thanks to albus, is to wait for the release of Oreo, rather than using new blank flash, with oreo stock rom image (around 1.5 gb) and flashing it through fastboot we'll be able to return to stock since will have new updated recovery gpt and whatever is needed. by the monent as Rakesh1b said debloated is better than stock faster cleaner etc and the otas.......not necesary really i have installes lineage 14.1 (nougat based) and works awesome, maybe ill move to 15 once more stable and may be even before the offic( oreo based) ial release of oreo.
Click to expand...
Click to collapse
Gpt and bootloader from Oreo won't be enough. Since they're using albus bootloader and partitions, overwriting gpt and bootloader from Oreo, will simply throw errors. Definitely will be needed a blankflash specifically for potter; then any Oreo firmware will work for flashing.

Moto G5s Hard bricked blankflash files and loader.img required.

Rakesh1b said:
bro I could understand your desperation there is no other way other than using twrp based stock ROMs or any custom ROMs for us u had been using debloated stock ROM since I bricked it is much more faster and stable than Moto stock images don't try any other ROMs which are not meant for motog5plus plus because there kernel source varies and configuration varies so don't try any other ROM and mess your potter u will make it totally unusable if even the current blankflash fails to work after installing any other ROM.
Hope you understood.
Be cool just enjoy your potter till new blankflash is released.
Bye..
Click to expand...
Click to collapse
Did Vache realesed Potter BlankFlash? I have find something in potter folder http://cloud.vache-android.com/Moto/potter/blankflash/ is this the original blank flash of potter?

mohammadsharfuddin said:
Did Vache realesed Potter BlankFlash? I have find something in potter folder http://cloud.vache-android.com/Moto/potter/blankflash/ is this the original blank flash of potter?
Click to expand...
Click to collapse
Nope, it's the one that he developed. There's no official one yet.

thedr34m13 said:
Nope, it's the one that he developed. There's no official one yet.
Click to expand...
Click to collapse
I thought that blankflash, with the April 2017 timestamp on it, was the original potter one, as it looked to be leaked with the original factory image? Regardless, we can't make blankflashes sadly (needing to be signed by Motorola, as I understand it) and that potter blankflash is far too old to be used in most cases.
If we're really lucky, perhaps a factory Oreo stock ROM might be leaked which may have an original Oreo potter blankflash. If not (i.e. it's just a standard fastboot ROM) then we'd have to wait for a leak or spend money on a new motherboard.

echo92 said:
I thought that blankflash, with the April 2017 timestamp on it, was the original potter one, as it looked to be leaked with the original factory image? Regardless, we can't make blankflashes sadly (needing to be signed by Motorola, as I understand it) and that potter blankflash is far too old to be used in most cases.
If we're really lucky, perhaps a factory Oreo stock ROM might be leaked which may have an original Oreo potter blankflash. If not (i.e. it's just a standard fastboot ROM) then we'd have to wait for a leak or spend money on a new motherboard.
Click to expand...
Click to collapse
It it's an original one then I heard wrong, but like you said it's outdated. I'm really hoping that stock Oreo fixes all the imei issues and such.
How does the pixel series do in terms of going back to stock? Google does have full firmware images online, but do they completely restore the phone?

thedr34m13 said:
It it's an original one then I heard wrong, but like you said it's outdated. I'm really hoping that stock Oreo fixes all the imei issues and such.
How does the pixel series do in terms of going back to stock? Google does have full firmware images online, but do they completely restore the phone?
Click to expand...
Click to collapse
Yeah, depends on what we'll get when the Oreo fastboot ROMs come out. I still am not entirely sure what causes the loss of IMEI (would be nice to know to prevent a future repeat), though like you I hope that the updated modems fix those unfortunate IMEI issues.
I think the fastboot images for Pixel devices do let you restore back to stock without wiping data (unless you're coming from a custom ROM, then general advice seems to be a full wipe). Like with our Moto devices, you can do the equivalent of omitting 'fastboot erase userdata' with removing -w in the flashing script: https://forum.xda-developers.com/pixel-xl/how-to/info-how-restored-to-stock-soft-t3494478
I guess the provision of updated firmware makes it less likely that a user flashes old firmware and then gets hard bricked by an old OTA flashing over a newer bootloader, and also Google appears to prevent you from flashing older firmware anyway: https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
That being said, there appear to be some Pixels that have been hard bricked (though looks like hardware failure than flashing something the Pixel didn't like: https://forum.xda-developers.com/pixel/help/pixel-bricked-replaced-phone-returned-t3776752

Stuck in bootloop
I blankflashed the albus bootloader on my potter. But when i flash the stock potter rom, it doesn't boot up and goes into boot loop . Only shows the unlocked bootloader warning again and again. Also i am unable to flash the twrp of either potter or albus. It says unsigned bootloader.
Can u provide the link of the stock rom that u flashed?

ATTENTION!Help needed to revive phone

I downgraded to marshmallow and I tried to update to nougat through the official way. It was updating for some time and then screen went off. I tried turning it on with no avail. I had latest bootloader which was unlocked.
Please help guys
I beg you

CMKdaGreatest said:
I downgraded to marshmallow and I tried to update to nougat through the official way. It was updating for some time and then screen went off. I tried turning it on with no avail. I had latest bootloader which was unlocked.
Please help guys
I beg you
Click to expand...
Click to collapse
Seems you bricked your phone by downgrade the bootloader...
Did you tried to follow the unbrick guide here https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016
Otherwise please provide on which rom version you are before downgrade to marshmallow and also the device type you have.
I'm sure @echo92 will help further :good:

strongst said:
Seems you bricked your phone by downgrade the bootloader...
Did you tried to follow the unbrick guide here https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016
Otherwise please provide on which rom version you are before downgrade to marshmallow and also the device type you have.
I'm sure @echo92 will help further :good:
Click to expand...
Click to collapse
Downgraded from stock nougat to stock marshmallow and tried OTAing back to nougat

CMKdaGreatest said:
Downgraded from stock nougat to stock marshmallow and tried OTAing back to nougat
Click to expand...
Click to collapse
Which stock nougat rom and which marshmallow rom. The versions. And did you tried the unbrick guide?

I tried the unbrick guide. I flashed the blank flash and got a dummy bootloader but I can't flash gpt or bootloader. It always shows failed. How should I do it?

strongst said:
Which stock nougat rom and which marshmallow rom. The versions. And did you tried the unbrick guide?
Click to expand...
Click to collapse
I used this guide. In the third page there's a post containing a blank flash attached. I flashed that but can't flash gpt or bootloader

CMKdaGreatest said:
I used this guide. In the third page there's a post containing a blank flash attached. I flashed that but can't flash gpt or bootloader
Click to expand...
Click to collapse
Can you link the post which you got the blankflash from?
In this post you'll find the latest athene blankflash and the December 2017 GPT/bootloader. https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
The December 2017 GPT/bootloader files are here https://drive.google.com/open?id=1IfAX7v94ooB5wS7KTJGNYfQ2kXkHxP80 and I pulled them from the NPJS25.93-14-13 stock ROM.
As an aside, you cannot safely downgrade and use OTA updates. If you downgrade, only use stock firmware to update. You cannot downgrade bootloaders and thus using older OTA updates on your device corrupts your bootloader.

echo92 said:
Can you link the post which you got the blankflash from?
In this post you'll find the latest athene blankflash and the December 2017 GPT/bootloader. https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
The December 2017 GPT/bootloader files are here https://drive.google.com/open?id=1IfAX7v94ooB5wS7KTJGNYfQ2kXkHxP80 and I pulled them from the NPJS25.93-14-13 stock ROM.
As an aside, you cannot safely downgrade and use OTA updates. If you downgrade, only use stock firmware to update. You cannot downgrade bootloaders and thus using older OTA updates on your device corrupts your bootloader.
Click to expand...
Click to collapse
Thank you so much man. Much appreciated

echo92 said:
Can you link the post which you got the blankflash from?
In this post you'll find the latest athene blankflash and the December 2017 GPT/bootloader. https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
The December 2017 GPT/bootloader files are here https://drive.google.com/open?id=1IfAX7v94ooB5wS7KTJGNYfQ2kXkHxP80 and I pulled them from the NPJS25.93-14-13 stock ROM.
As an aside, you cannot safely downgrade and use OTA updates. If you downgrade, only use stock firmware to update. You cannot downgrade bootloaders and thus using older OTA updates on your device corrupts your bootloader.
Click to expand...
Click to collapse
I already flashed a blank flash. How do I flash another one??

CMKdaGreatest said:
I already flashed a blank flash. How do I flash another one??
Click to expand...
Click to collapse
You won't be able to flash another blankflash unless your device is in the Qualcomm HS-USB 9008 mode again (in other words, you hard bricked by corrupting your bootloader again).
I'm hoping as whatever blankflash you used worked properly and thus you shouldn't have issues flashing the latest firmware. However, they can overwrite a damaged bootloader with the dummy bootloader, and as such you need to verify you're flashing the correct blankflash. The inbuilt checks should stop you from flashing the wrong blankflash however.
If you still want to revert back to Marshmallow, then do not use OTA updates at all.
As an aside, do not always depend on these blankflashes, Motorola is updating the bootloader with every firmware release and there's always a chance the blankflashes may not work anymore. We're not supposed to have these blankflashes (leaks from generous engineers are our source) and so we don't know if we can get another one should the current blankflash stop working.

echo92 said:
You won't be able to flash another blankflash unless your device is in the Qualcomm HS-USB 9008 mode again (in other words, you hard bricked by corrupting your bootloader again).
I'm hoping as whatever blankflash you used worked properly and thus you shouldn't have issues flashing the latest firmware. However, they can overwrite a damaged bootloader with the dummy bootloader, and as such you need to verify you're flashing the correct blankflash. The inbuilt checks should stop you from flashing the wrong blankflash however.
If you still want to revert back to Marshmallow, then do not use OTA updates at all.
As an aside, do not always depend on these blankflashes, Motorola is updating the bootloader with every firmware release and there's always a chance the blankflashes may not work anymore. We're not supposed to have these blankflashes (leaks from generous engineers are our source) and so we don't know if we can get another one should the current blankflash stop working.
Click to expand...
Click to collapse
It worked. After the bootup, I received an update. I updates my phone and it successfully booted up. I received another update. Now, after this, its back to the same condition. Why is this happening?

Can you give me links for the firmware too if you don't mind? I need the Indian version for XT1643. Dont mind me man, I'm still in 9th grade

CMKdaGreatest said:
It worked. After the bootup, I received an update. I updates my phone and it successfully booted up. I received another update. Now, after this, its back to the same condition. Why is this happening?
Click to expand...
Click to collapse
CMKdaGreatest said:
Can you give me links for the firmware too if you don't mind? I need the Indian version for XT1643. Dont mind me man, I'm still in 9th grade
Click to expand...
Click to collapse
Did you re-flash the latest firmware? https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 For NPJS25.93-14-13 (Nougat, Dec 2017 build)
If not, then your device is still with a mismatched bootloader and system - you have the December 2017 bootloader but the much older Marshmallow system. That means any OTA update you take may well keep hard bricking your device unless you re-flash your device to have firmware of the same patch level (bootloader and system). Then, you should be okay to take OTA updates.
This is the major problem with downgrading - OTA updates have the ability to overwrite your bootloader without checking first if your bootloader is the same patch level as your system. As you've downgraded, this is likely why older OTA updates brick.
Un-brick your device then use the flashing instructions here https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761 with the latest NPJS25.93-14-13 firmware. Do not use/install OTA updates until you've re-flashed the latest stock firmware.

echo92 said:
Did you re-flash the latest firmware? https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 For NPJS25.93-14-13 (Nougat, Dec 2017 build)
If not, then your device is still with a mismatched bootloader and system - you have the December 2017 bootloader but the much older Marshmallow system. That means any OTA update you take may well keep hard bricking your device unless you re-flash your device to have firmware of the same patch level (bootloader and system). Then, you should be okay to take OTA updates.
This is the major problem with downgrading - OTA updates have the ability to overwrite your bootloader without checking first if your bootloader is the same patch level as your system. As you've downgraded, this is likely why older OTA updates brick.
Un-brick your device then use the flashing instructions here https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761 with the latest NPJS25.93-14-13 firmware. Do not use/install OTA updates until you've re-flashed the latest stock firmware.
Click to expand...
Click to collapse
The first link in your last post, does it have latest firmware? I reflashed the may or march 2016 firmware after the blank flash, I don't remember which

CMKdaGreatest said:
Can you give me link to latest firmware?
Click to expand...
Click to collapse
The link to the latest firmware was the first link I gave you in my previous reply... NPJS25.93-14-13 is the latest stock ROM for India, Brazil and EU devices.
Yeah, flashing the May 2016 or March 2016 firmware really won't help you - again, as your bootloader is December 2017 flashing older firmware and attempting to take OTA updates will just keep hard bricking you until you reflash the December 2017 firmware, or if you do not use OTA updates. You cannot downgrade bootloaders usually.

echo92 said:
The link to the latest firmware was the first link I gave you in my previous reply... NPJS25.93-14-13 is the latest stock ROM for India, Brazil and EU devices.
Yeah, flashing the May 2016 or March 2016 firmware really won't help you - again, as your bootloader is December 2017 flashing older firmware and attempting to take OTA updates will just keep hard bricking you until you reflash the December 2017 firmware, or if you do not use OTA updates. You cannot downgrade bootloaders usually.
Click to expand...
Click to collapse
Yea I'll try tomorrow man. Thanks a ton!! The method of blank flash is the same right?? If it doesnt work then what should I do??

CMKdaGreatest said:
Yea I'll try tomorrow man. Thanks a ton!! The method of blank flash is the same right?? If it doesnt work then what should I do??
Click to expand...
Click to collapse
Should be, please use the latest athene blankflash in the Unbrick guide: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761 and the latest stock ROM as mentioned. I would also advise deleting any old stock ROMs - Marshmallow or Nougat - on your computer, unless you are confident you will not use OTA updates whilst downgraded. Motorola and other OEMs appear to have not designed protections into their updates for downgraded devices (and assume that you've taken responsibility ever since you unlocked your bootloader).
If this doesn't work, then you'll either have to wait for another newer blankflash to be leaked (perhaps when we get the Oreo update, but again, it's by chance whether we get another blankflash), or be willing to pay for a motherboard replacement. A motherboard replacement appears to be in the range of 7000-10000 rupees or your regional equivalent.

echo92 said:
Should be, please use the latest athene blankflash in the Unbrick guide: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761 and the latest stock ROM as mentioned. I would also advise deleting any old stock ROMs - Marshmallow or Nougat - on your computer, unless you are confident you will not use OTA updates whilst downgraded. Motorola and other OEMs appear to have not designed protections into their updates for downgraded devices (and assume that you've taken responsibility ever since you unlocked your bootloader).
If this doesn't work, then you'll either have to wait for another newer blankflash to be leaked (perhaps when we get the Oreo update, but again, it's by chance whether we get another blankflash), or be willing to pay for a motherboard replacement. A motherboard replacement appears to be in the range of 7000-10000 rupees or your regional equivalent.
Click to expand...
Click to collapse
I'm just curious to know what happens if we flash an old blank flash.

CMKdaGreatest said:
I'm just curious to know what happens if we flash an old blank flash.
Click to expand...
Click to collapse
Depends - if it's an old blankflash for our device (for Snapdragon 617, MSM8952), it'll likely fail as the blankflash, in communicating with the device's bootloader, determines the blankflash is too old to repair the bootloader. Blankflashes appear to send a programmer over to your device which verifies that your device bootloader is not newer than the blankflash, else you'd be downgrading your bootloader and possibly causing a security issue. Thus, your device may not be rescued and require a new motherboard. We saw plenty of these incidents when users downgraded to Marshmallow from Nougat 6 months ago and then tried to use OTA updates, and it was only with the leak of a newer bootloader version B1:06 compatible blankflash that people were able to rescue their devices without spending a lot of money. Without that blankflash, I think we have very limited means of rescue. We cannot make these blankflashes as they have to be cryptographically signed and built by OEMs like Motorola, I think to maintain the bootloader security, as such we do not know if we'll get a new one. In theory, we could make a loader image - a complete image of a working device - to try to bypass the bootloader corruption without needing a blankflash. That has had some success on other devices, but hopefully you should need neither a blankflash nor a loader image.
We've seen instances of other Moto devices' blankflashes rescuing devices (e.g. Moto Z2 Play rescuing Moto Z Play and G5 Plus), however, their CPUs are very similar. Our Snapdragon 617 is not used by any other Motorola device, so we have a very limited source of blankflashes.
I would hope blankflashes are in general well programmed enough to not flash onto devices they are not meant to flash onto, else if they could flash onto a different device, you could really screw up your device.
In summary, an older blankflash likely just won't work, and you'd either have to wait for a newer blankflash or pay for an expensive repair. Unless you are willing to do either, I would be very careful in future with downgrading.

echo92 said:
Depends - if it's an old blankflash for our device (for Snapdragon 617, MSM8952), it'll likely fail as the blankflash, in communicating with the device's bootloader, determines the blankflash is too old to repair the bootloader. Blankflashes appear to send a programmer over to your device which verifies that your device bootloader is not newer than the blankflash, else you'd be downgrading your bootloader and possibly causing a security issue. Thus, your device may not be rescued and require a new motherboard. We saw plenty of these incidents when users downgraded to Marshmallow from Nougat 6 months ago and then tried to use OTA updates, and it was only with the leak of a newer bootloader version B1:06 compatible blankflash that people were able to rescue their devices without spending a lot of money. Without that blankflash, I think we have very limited means of rescue. We cannot make these blankflashes as they have to be cryptographically signed and built by OEMs like Motorola, I think to maintain the bootloader security, as such we do not know if we'll get a new one. In theory, we could make a loader image - a complete image of a working device - to try to bypass the bootloader corruption without needing a blankflash. That has had some success on other devices, but hopefully you should need neither a blankflash nor a loader image.
We've seen instances of other Moto devices' blankflashes rescuing devices (e.g. Moto Z2 Play rescuing Moto Z Play and G5 Plus), however, their CPUs are very similar. Our Snapdragon 617 is not used by any other Motorola device, so we have a very limited source of blankflashes.
I would hope blankflashes are in general well programmed enough to not flash onto devices they are not meant to flash onto, else if they could flash onto a different device, you could really screw up your device.
In summary, an older blankflash likely just won't work, and you'd either have to wait for a newer blankflash or pay for an expensive repair. Unless you are willing to do either, I would be very careful in future with downgrading.
Click to expand...
Click to collapse
It worked!! Thank you so much. Now it's perfect!!