I can not block bootloader on my g5 plus moto - Moto G5 Plus Questions & Answers

I have the cell phone with the telcel company, I do not know what it was when I unlocked my bootloader, now I am in potter NPNS25.137-92-4 LATAM with the security patch of January and every time I try to block the bootloader I get errors indicating that I can not degrade and I need a signed rom ... I do not know what to do, I hope they can help me

castaños300172 said:
I have the cell phone with the telcel company, I do not know what it was when I unlocked my bootloader, now I am in potter NPNS25.137-92-4 LATAM with the security patch of January and every time I try to block the bootloader I get errors indicating that I can not degrade and I need a signed rom ... I do not know what to do, I hope they can help me
Click to expand...
Click to collapse
There's no need for crossposting, I gave you an answer in the relock bootloader thread.
And opening a new thread didn't help either.
Your on January security patch and you need that firmware to flash or relock your bootloader.
This firmware isn't uploaded anywhere, only the indian build. So stop asking the same question over and over again, YOU CAN'T DOWNGRADE YOUR BOOTLOADER, IT WILL BRICK YOUR DEVICE.
So you have to live with an unlocked bl and as I posted to you, there's no need to relock it as you never get the status of 'this device has never been unlocked'. Btw, you never posted the reason why you want to do that.
Anyway, you have to wait until someone uploads your firmware or a newer one.
Sent from my Moto G5 Plus using XDA Labs

Related

[Q] how to unlock bl

The possibility of xt907 whether official unlock bl later I want to install the cm11
glamor7 said:
The possibility of xt907 whether official unlock bl later I want to install the cm11
Click to expand...
Click to collapse
Do you have a special developer version? If not, you have to be on firmware 98.15.66 or OLDER. Basically, your phone cannot have been updated since around March 2013. If by some miracle you still have old FW, then you can use Motopocalypse to unlock BL.
If you are on newer FW, regular XT907 and not developer, there is no way to unlock BL.
You might keep an eye on this thread:
http://forum.xda-developers.com/showthread.php?t=2679190
Right now, only phones made in 2014 can be unlocked with that method and it costs $43, but maybe someday they will have the ability to unlock 2012/2013 phones.
OR you could try writing persuasive letters to Verizon's Corporate Office.

HELP, Can I downgrade to Stock Marshmallow and Upgrade to Nougat?

Hello,
Can I downgrade completly with the bootloader on Marshmallow and then upgrade to Nougat?
I want to lock my bootloader.
My G2 bricked after doing this. But I don't know if this would happen to my G4 Plus again
inFiniTyz_Z said:
Hello,
Can I downgrade completly with the bootloader on Marshmallow and then upgrade to Nougat?
I want to lock my bootloader.
My G2 bricked after doing this. But I don't know if this would happen to my G4 Plus again
Click to expand...
Click to collapse
If you wish to simply re-lock your bootloader, the easiest thing is to flash this fastboot stock ROM (which is Nougat) and use the locking script as directed in the first post. https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369 Of course, this may wipe your data - so back up, and the relocking may or may not work, in which case you may have to wait for a more up to date fastboot stock ROM to become available.
If you were to downgrade to Marshmallow, you cannot downgrade your bootloader and GPT partitions, at best, your existing bootloader would try to prevent you from downgrading those partitions. At worst, you'll brick your device again if you were to flash those - though we've got possible ways of fixing that, it's not a route I'd want to go down. Flashing the rest of Marshmallow is no problem, however, ensure you have the correct MM firmware for your device and territory.
Will this version work for my country(Germany) without OTA trouble?
inFiniTyz_Z said:
Will this version work for my country(Germany) without OTA trouble?
Click to expand...
Click to collapse
Should be okay to flash - the 93-14 build appears to be the global build that was deployed by Motorola, and should be eligible for the 93-14.4 (March 2017 security update) whenever that arrives in the EU/UK I've flashed the stock ROM onto my XT1642 several times without issue.
echo92 said:
Should be okay to flash - the 93-14 build appears to be the global build that was deployed by Motorola, and should be eligible for the 93-14.4 (March 2017 security update) whenever that arrives in the EU/UK I've flashed the stock ROM onto my XT1642 several times without issue.
Click to expand...
Click to collapse
THANK YOU IT WORKED AND THE WARNING DISAPPEARED. I am on Nougat, locked and its working like a charm
I WOULD KISS YOUR BUTT IF ITS HAVE TO BE

Anyone using the Amazon G4 version?

I don't see many people on any of the Moto G4 fórums who have the Amazon G4 ads version. I know there are a few like myself, who were able to unlock the bootloader, before Amazon stopped it.
All info on updates communicated on these forum pertain to the retail version. I would have thought more people would have bought the Amazon discounted version.
It sucks that even with the bootloader unlocked, I cannot flash a retail version of the Stock ROM. Is anyone out there with the Amazon G4 versión?
Please let me know if you are and on what Android build your on? Anyone received the September security update? We're you one of the people who were able to unlock the bootloader?
I have one
I ran MM for a long time, but I just upgraded to the Sept Nougat release fine following the steps from the first post, followed by the second:
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
I might have been able to just do the second. FWIW, I didn't relock and I did pull out the gpt and bootloader.img lines from the upgrade script.
vettejock99 said:
I ran MM for a long time, but I just upgraded to the Sept Nougat release fine following the steps from the first post, followed by the second:
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
I might have been able to just do the second. FWIW, I didn't relock and I did pull out the gpt and bootloader.img lines from the upgrade script.
Click to expand...
Click to collapse
It's your Moto G4 the Amazon ads version? I am on the June security update NPJ25-93-14.5. I was checking if anyone on the Amazon update channel got the September security update.
Also, I wanted to know if anyone was able to convert the Moto G4 from Amazon to Retail.
I have a xt1625 Amazon Prime ads g4. My phone is bootloader unlocked, rooted, and on Npj25-93-14.4 with the bootloader from retail 93-14-8 from my last attempt to change it from a amz to retus. I haven't yet found a way to use the stock retus rom on the phone, after many attempt and several bricks.
CHownclown said:
I have a xt1625 Amazon Prime ads g4. My phone is bootloader unlocked, rooted, and on Npj25-93-14.4 with the bootloader from retail 93-14-8 from my last attempt to change it from a amz to retus. I haven't yet found a way to use the stock retus rom on the phone, after many attempt and several bricks.
Click to expand...
Click to collapse
To the prior question, yes mine is an ad-supported XT1625. I unlocked it like day 2 before they stopped supporting it. I ran rooted and ad-free for about a year, then the micro-usb failed and I had to send it in for warranty repair. Moto was nice enough to take it a week after expiration and they sent a replacement - another ad-supported XT1625. That was a few months ago. Sorry I can't confirm how I got the new phone bootloader unlocked, but it is. Software channel shows retus, and I'm running the roms I linked. I do recall seriously bricking it at one point, but I do think if you're bootloader unlocked there is a way to get to retus. Again, sorry I can't recall the journey.
vettejock99 said:
To the prior question, yes mine is an ad-supported XT1625. I unlocked it like day 2 before they stopped supporting it. I ran rooted and ad-free for about a year, then the micro-usb failed and I had to send it in for warranty repair. Moto was nice enough to take it a week after expiration and they sent a replacement - another ad-supported XT1625. That was a few months ago. Sorry I can't confirm how I got the new phone bootloader unlocked, but it is. Software channel shows retus, and I'm running the roms I linked. I do recall seriously bricking it at one point, but I do think if you're bootloader unlocked there is a way to get to retus. Again, sorry I can't recall the journey.
Click to expand...
Click to collapse
Maybe the replacement they sent had Amazon ad, but the software channel is changed to retus.
CHownclown said:
I have a xt1625 Amazon Prime ads g4. My phone is bootloader unlocked, rooted, and on Npj25-93-14.4 with the bootloader from retail 93-14-8 from my last attempt to change it from a amz to retus. I haven't yet found a way to use the stock retus rom on the phone, after many attempt and several bricks.
Click to expand...
Click to collapse
By just flashing a retus bootloader you changed the channel to retus? Even with it being retus, you can't flash retus firmware on it?
Anyone with any knowledge on converting the Amazon Prime unlocked bootloader phone from AMZ update channel to retail RETUS?
If the bootloader has been unlock on an Amazon Ads phone, Why can't a retail version be flashed? It's the same firmware that the Retail XT1625 has. Even if the software channel stays AMZ, the retail firmware should work.
vettejock99 said:
To the prior question, yes mine is an ad-supported XT1625. I unlocked it like day 2 before they stopped supporting it. I ran rooted and ad-free for about a year, then the micro-usb failed and I had to send it in for warranty repair. Moto was nice enough to take it a week after expiration and they sent a replacement - another ad-supported XT1625. That was a few months ago. Sorry I can't confirm how I got the new phone bootloader unlocked, but it is. Software channel shows retus, and I'm running the roms I linked. I do recall seriously bricking it at one point, but I do think if you're bootloader unlocked there is a way to get to retus. Again, sorry I can't recall the journey.
Click to expand...
Click to collapse
Whats your current security update? Are you rooted? I am in need of the stock boot.img of the December or February security update.
CHownclown said:
I have a xt1625 Amazon Prime ads g4. My phone is bootloader unlocked, rooted, and on Npj25-93-14.4 with the bootloader from retail 93-14-8 from my last attempt to change it from a amz to retus. I haven't yet found a way to use the stock retus rom on the phone, after many attempt and several bricks.
Click to expand...
Click to collapse
Whats your current security update? Are you rooted? I am in need of the stock boot.img of the December or February security update.

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!!

Heip with G5 plus non-rooted phone with unlocked bootloader running August 2018 8.1

Hello,
I've just bought a second-hand moto G5 Plus that had a custom rom installed on it, I'm guessing it was also rooted at some point. It currently has the Aug 1 2018 version of 8.1:
build #: OPS28.85-13
It's been a while since I've messed about with flashing phones, so I wanted to ask for some assistance before potentially bricking the poor thing.
Ideally, I'd like to get it back on the stock update channel, so it can get OTA updates, but with root -- if that's not possible, I'd be almost as happy to just flash a Sept 1 2018 build (which my other 100% stock G5 plus already has) and root it. I've looked at a few posts here, notably this one:
https://forum.xda-developers.com/g5...o-twrp-flashable-stock-builds-coming-t3830482
Though not knowing the exact history of the device, I'm reluctant to just follow the instructions. Can anyone provide some insight as to the safe(st) procedure?
Thanks!
-pir
You can't have root and receive updates from official channel at the same time.. the bootloader need to be locked to recieve updates.. you can however flash twrp on the device.. flash the stock rom( you will find latest in the forums).. and when the updates come out someone will capture it and make a flashabe zip, so you just need to flash that.. you can have root that way and stay updated.. cause from what I've read so far you don't get OTA when you're bootloader is unlocked..
That makes sense. So I guess the moto software won't even attempt an update if the bootloader is unlocked? Thanks!
Unlocked bootloader won't make any difference. The OTA update checks the system files and bootloader. If you have made any modifications to the system, kernel, or are running an older bootloader version the update will fail. Lock status of the bootloader makes no difference.
Sent from my Moto G (5) Plus using Tapatalk

Categories

Resources