Hello everybody. I just wanted to know if someone has an official firmware for the amazon channel NPNS25.137-93-8. Because I can not find it myself. Required to lock bootloader
marsian4uk said:
Hello everybody. I just wanted to know if someone has an official firmware for the amazon channel NPNS25.137-93-8. Because I can not find it myself. Required to lock bootloader
Click to expand...
Click to collapse
As the Amazon firmware was unlockable until a few days ago there is no special firmware uploaded.
But I'm not sure that you can't flash the standard firmware or maybe the builds are identical. Unfortunately there is no NPNS25.137-93-8 firmware uploaded atm but there is a NPNS25.137-93-10 build (april security patch):https://drive.google.com/open?id=16Bfp3nVfvKMURAeKagOaOImX-lvJrYBF
As I said, I'm not sure if the firmwares are similar so if you flash it you do it at your own risk.
Sent from my Moto G5 Plus using XDA Labs
hi
Wolfcity said:
As the Amazon firmware was unlockable until a few days ago there is no special firmware uploaded.
But I'm not sure that you can't flash the standard firmware or maybe the builds are identical. Unfortunately there is no NPNS25.137-93-8 firmware uploaded atm but there is a NPNS25.137-93-10 build (april security patch):
As I said, I'm not sure if the firmwares are similar so if you flash it you do it at your own risk.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
browsing the files. The difference is only OEM partition. What is it for?
marsian4uk said:
browsing the files. The difference is only OEM partition. What is it for?
Click to expand...
Click to collapse
It's a kind of manufacturer storage:
https://forum.xda-developers.com/cr...on-general/observation-oem-partition-t3189677
All changes the manufacturer does are stored in OEM.
So if you flash a standard firmware the device may change to a standard retail device too.
But this is a bit over my knowledge about firmwares, maybe some of the pro's could have a look into it.
Sent from my Moto G5 Plus using XDA Labs
Wolfcity said:
It's a kind of manufacturer storage:
https://forum.xda-developers.com/cr...on-general/observation-oem-partition-t3189677
All changes the manufacturer does are stored in OEM.
So if you flash a standard firmware the device may change to a standard retail device too.
But this is a bit over my knowledge about firmwares, maybe some of the pro's could have a look into it.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
so, if I will be able to flash OEM partition, i can get OTA on reteu?
marsian4uk said:
so, if I will be able to flash OEM partition, i can get OTA on reteu?
Click to expand...
Click to collapse
If you flash the complete NPNS25.137-93-10 firmware via fastboot (as there is no 93-8 available and downgrading could hardbrick your device) it should work like this. It's the same hardware after all.
But there is always a risk in crossflashing (if this is crossflashing at all), maybe Amazon has built in some kind of security feature.
But as far as I understand the whole thing the Amazon version is just a normal Moto G5+ with some changes made in the oem partition.
If you flash the 93-10 firmware all traces should be overwritten and you should be in the standard reteu channel and be able to receive OTA for it.
But remember, you do everything at your own risk.
Maybe you can contact someone who owns a Amazon build too, here is a thread about it:
https://forum.xda-developers.com/g5-plus/help/resolved-root-moto-g5-plus-amazon-t3652932
Edit: After unlocking your device it is wiped.
Did you recognise the difference of the oem partition before or after the wipe?
Sent from my Moto G5 Plus using XDA Labs
Wolfcity said:
If you flash the complete NPNS25.137-93-10 firmware via fastboot (as there is no 93-8 available and downgrading could hardbrick your device) it should work like this. It's the same hardware after all.
But there is always a risk in crossflashing (if this is crossflashing at all), maybe Amazon has built in some kind of security feature.
But as far as I understand the whole thing the Amazon version is just a normal Moto G5+ with some changes made in the oem partition.
If you flash the 93-10 firmware all traces should be overwritten and you should be in the standard reteu channel and be able to receive OTA for it.
But remember, you do everything at your own risk.
Maybe you can contact someone who owns a Amazon build too, here is a thread about it:
https://forum.xda-developers.com/g5-plus/help/resolved-root-moto-g5-plus-amazon-t3652932
Edit: After unlocking your device it is wiped.
Did you recognise the difference of the oem partition before or after the wipe?
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
OEM is changing the size of various software versions of the same update channel. Can this be helpful?
marsian4uk said:
OEM is changing the size of various software versions of the same update channel. Can this be helpful?
Click to expand...
Click to collapse
I think that depends OTA updates. For example: Some users flashed a 92-x firmware on their european/us (reteu,retus)device. This firmware is made for India and South America (retin,retbra).
Their devices are still working completely but they don't get any OTA anymore. The devices still say reteu but the OTA server is looking for a 93-x firmware which is not present. I think these users can return to their software channel by flashing a 93-x firmware.
As you are going to flash a 93-x on a device running a 93-x firmware you should be good to go.
The only uncertainty is if Amazon has done anything that signs your device as "Amazon prime" even after flashing a whole new firmware.
The result would be no OTA. But I don't think so, even if that may be technically possible.
We all won't be sure until someone with a Amazon device tries it.
Sent from my Moto G5 Plus using XDA Labs
Wolfcity said:
I think that depends OTA updates. For example: Some users flashed a 92-x firmware on their european/us (reteu,retus)device. This firmware is made for India and South America (retin,retbra).
Their devices are still working completely but they don't get any OTA anymore. The devices still say reteu but the OTA server is looking for a 93-x firmware which is not present. I think these users can return to their software channel by flashing a 93-x firmware.
As you are going to flash a 93-x on a device running a 93-x firmware you should be good to go.
The only uncertainty is if Amazon has done anything that signs your device as "Amazon prime" even after flashing a whole new firmware.
The result would be no OTA. But I don't think so, even if that may be technically possible.
We all won't be sure until someone with a Amazon device tries it.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
do you think theres some chance we could bootloader unlock if this were successful?
krzee said:
do you think theres some chance we could bootloader unlock if this were successful?
Click to expand...
Click to collapse
The only way to find it out is to try it.
Sent from my Moto G5 Plus using XDA Labs
Related
Hello, two short questions
What's the latest official firmware for XT1642 and where to download?
I only found old ones.
If I relock Bootloader to get the latest OTA, am I be able to reopen it again?
Do I need my e-mail address I used for the first code or can I make a new one?
Thanks
I think you dont' need to relock the bootloader for OTA. I find old firmware too and i didn't test it.
The lock/unlock state of your bootloader isn't relevant to OTA updates, you just need stock recovery and an unmodified system partition.
acejavelin said:
The lock/unlock state of your bootloader isn't relevant to OTA updates, you just need stock recovery and an unmodified system partition.
Click to expand...
Click to collapse
When I got the phone I got an OTA with MJP24.139-63, but when I flashed MJP24.139-48 it always says "Your system is up to date".
I thought this was because of the unlocked bootloader.
I checked immediately after flashing stock firmware, I didn't modify it but still got no OTA.
HE4VYCR0WN said:
When I got the phone I got an OTA with MJP24.139-63, but when I flashed MJP24.139-48 it always says "Your system is up to date".
I thought this was because of the unlocked bootloader.
I checked immediately after flashing stock firmware, I didn't modify it but still got no OTA.
Click to expand...
Click to collapse
It is not because of the unlocked bootloader... I can't tell you exactly why it said that but I can say that isn't the cause.
Remember if you downgraded you are in a mixed state... Not every "piece" can be downgraded, I would bet when you flashed a couple of the parts it said 'Pre-flash validation failed' or something like that, meaning that partition was older and could not be downgraded, typically the bootloader and gpt.bin which is the partition table. That could be the issue, or it could be something else, it's hard to say. There has been some rumor that if the update server has handed out a specific OTA package to certain device for some reason it may not offer it to it to that device again under some conditions.
I don't understand why lenovo don't give us the last full firmware for our device... Sadly i didn't make a backup before flashing kernel and recovery.
titou4488 said:
I don't understand why lenovo don't give us the last full firmware for our device... Sadly i didn't make a backup before flashing kernel and recovery.
Click to expand...
Click to collapse
Have you requested it? You can contact Moto support and ask for it, that's how we got such a large collection for the Moto G 2015, a few people request each firmware image and we share. It can take a couple of days to a few months but Moto usually comes through.
acejavelin said:
Have you requested it? You can contact Moto support and ask for it, that's how we got such a large collection for the Moto G 2015, a few people request each firmware image and we share. It can take a couple of days to a few months but Moto usually comes through.
Click to expand...
Click to collapse
I asked for it just seconds ago, I will keep you up to date when I hear something new.
Thanks for your help.
HE4VYCR0WN said:
When I got the phone I got an OTA with MJP24.139-63, but when I flashed MJP24.139-48 it always says "Your system is up to date".
I thought this was because of the unlocked bootloader.
I checked immediately after flashing stock firmware, I didn't modify it but still got no OTA.
Click to expand...
Click to collapse
its because MJP24.139-63 is the latest .MJP24.139-63 is the the previous update. you need to be on MJP24.139-63 to get the android N upgrade.
zain st said:
its because MJP24.139-63 is the latest .MJP24.139-63 is the the previous update. you need to be on MJP24.139-63 to get the android N upgrade.
Click to expand...
Click to collapse
But he can't have MJP24.139-63 because he doesn't have the OTA update.
Motorola doesn't want to give us the last full firmware. I asked them.
Moto/Lenovo replied to my E-Mail and won't provide assistance in anyway.
Which firmware did you flash? maybe an older firmware will work. I found this: XT1621-XT1622-XT1642_ATHENE_MPJ24.139-23.4_cid50_subsidy-DEFAULT_CFC.xml.zip
HE4VYCR0WN said:
Moto/Lenovo replied to my E-Mail and won't provide assistance in anyway.
Click to expand...
Click to collapse
You can find everything in Guides section: http://forum.xda-developers.com/moto-g4-plus/how-to/index-moto-g4-plus-factory-firmware-t3409033
Nougat Update not appearing and still on build MPJ24.139-48 anyone has the same issue? BTW it's Amazon 16gb with ads variant.
samuel6827 said:
Nogat Update not appearing and still on build MPJ24.139-48 anyone has the same issue? BTW it's Amazon 16gb with ads variant.
Click to expand...
Click to collapse
You should have been notified for the -64 update, before you can install the nougat update.
Are you rooted?
samuel6827 said:
Nogat Update not appearing and still on build MPJ24.139-48 anyone has the same issue? BTW it's Amazon 16gb with ads variant.
Click to expand...
Click to collapse
I have the same issue, same build number, same phone... anyone?
samuel6827 said:
Nogat Update not appearing and still on build MPJ24.139-48 anyone has the same issue? BTW it's Amazon 16gb with ads variant.
Click to expand...
Click to collapse
lI have same phone and have the same build as you. No update.
I went from -49 straight to Nougat. I reloaded the os though.
The reason I wiped and reloaded was that I wasn't getting the prompt for the update anymore.
Sent from my Moto G (4) using Tapatalk
I have the same phone, build -49. Still no update...
Same here, stuck on .49. Not rooted or boot loader unlocked.
tekweezle said:
I went from -49 straight to Nougat. I reloaded the os though.
The reason I wiped and reloaded was that I wasn't getting the prompt for the update anymore.
Sent from my Moto G (4) using Tapatalk
Click to expand...
Click to collapse
What do you mean by "reloaded" the OS?
the procedure outlined here will overwrite/reload your OS as a clean system
https://forum.xda-developers.com/moto-g4/how-to/guide-simple-ota-update-rooted-unlocked-t3510126
this assumes that you have a unlocked bootloader and non amazon prime version of phone
samuel6827 said:
Nogat Update not appearing and still on build MPJ24.139-48 anyone has the same issue? BTW it's Amazon 16gb with ads variant.
Click to expand...
Click to collapse
I have the same model XT1625 amz, also did not come updates.
On the forum lenovo answered me "06.04 Not everyone has received it yet." (c) AlphaDog
The guy in the next topic wrote that he, too, was jammed with the old firmware, that he was helped by manipulations like for the return of brick life, get OTA 7.0
https://forum.xda-developers.com/showpost.php?p=71809639&postcount=7
Today my G4 was still stuck on -49 so I decided to try this https://forum.xda-developers.com/moto-g4/development/unbrick-hard-bricked-moto-g4-amazon-t3486578 and it worked beautifully. Phone is installing system update right now. I didn't have to unlock bootloader, just did as described except that I didn't use RSDLite but pasted all commands directly into fastboot. Thanks!!!!!
If in the near future I will not receive an OTA Update Android 7.0 to my Moto G4 XT1625 Amazon Prime, I will also try this method
Does anyone have the stock fw for retus devices? (I unwisely neglected to back it up before modifying /system. Thought I had. Oops.) Thanks.
Kufat said:
Does anyone have the stock fw for retus devices? (I unwisely neglected to back it up before modifying /system. Thought I had. Oops.) Thanks.
Click to expand...
Click to collapse
go here bro
https://www.youtube.com/watch?v=e06UeBE1T3A
hit thumbs up if i helped you
Thanks. I did see that, and the other thread, but I thought it was a different region's FW.
Is /system the same across regions and just /oem different? What makes a retus phone different from a retin/reteu one; where does that setting live?
I recovered my RETUS XT1687 with the rom that was labeled -35 (as I remember mine came with -35, it's an Amazon non subsidized model)
there are definitely differences between RETIN/RETEU and RETUS mainly the replacement of NFC with a compass but I have seen no issues with the rom I used(ie: TMUS wifi calling works, VoLTE works, camera works, etc)...I wonder if there's scripts that install the proper blobs?
bakedpatato said:
I recovered my RETUS XT1687 with the rom that was labeled -35 (as I remember mine came with -35, it's an Amazon non subsidized model)
Click to expand...
Click to collapse
Interesting. Is your "software channel" still showing up as retus?
Kufat said:
Interesting. Is your "software channel" still showing up as retus?
Click to expand...
Click to collapse
Yep
Did you use POTTER_NPN25.137-35 or POTTER_AMZ_NPN25.137-35 ?? (AMZ is presumably the Amazon in-store app version?)
bakedpatato said:
I recovered my RETUS XT1687 with the rom that was labeled -35 (as I remember mine came with -35, it's an Amazon non subsidized model)
there are definitely differences between RETIN/RETEU and RETUS mainly the replacement of NFC with a compass but I have seen no issues with the rom I used(ie: TMUS wifi calling works, VoLTE works, camera works, etc)...I wonder if there's scripts that install the proper blobs?
Click to expand...
Click to collapse
GoodOlDan said:
Did you use POTTER_NPN25.137-35 or POTTER_AMZ_NPN25.137-35 ?? (AMZ is presumably the Amazon in-store app version?)
Click to expand...
Click to collapse
I don't think I've seen a AMZ image but i used the former...I dunno what would happen if I installed the AMZ one on my phone as mine isn't an AMZ model
Moto Firmware
I did the same thing with my moto g6 xt1925-6 variant. I couldn't get factory firmware from Motorola but I did come across this site hosting a bunch of factory images. Hope it helps.
mirrors. lolinet. com/firmware/moto/
Sorry it's first post and it won't let me post the URL in one piece.
AlexUlrich99 said:
I did the same thing with my moto g6 xt1925-6 variant. I couldn't get factory firmware from Motorola but I did come across this site hosting a bunch of factory images. Hope it helps.
mirrors. lolinet. com/firmware/moto/
Sorry it's first post and it won't let me post the URL in one piece.
Click to expand...
Click to collapse
https://mirrors.lolinet.com/firmware/moto/potter/official/
Sent from my Moto G5 Plus using XDA Labs
Does anyone have the potter NPNS25.137-93-8 complete firmware ? If yes, can please share with us ? Thanks in advance
aSaro12 said:
Does anyone have the potter NPNS25.137-93-8 complete firmware ? If yes, can please share with us ? Thanks in advance
Click to expand...
Click to collapse
Bumping this up. I'm looking for this one too.
wait a minute.. 93-8? i'm on march patch in 92-8..
M1810 said:
wait a minute.. 93-8? i'm on march patch in 92-8..
Click to expand...
Click to collapse
93-4 is already out
braindeductions said:
93-4 is already out
Click to expand...
Click to collapse
M1810 said:
wait a minute.. 93-8? i'm on march patch in 92-8..
Click to expand...
Click to collapse
Firmwares with the ending 92-x are for India and Brazil, ending on 93-x for Europe, US and Asia Pacific.
For Europe/US the latest firmware is 93-10 (April security patch).
The latest one I found uploaded is 93-4. The same for India, 92-4 is uploaded.
Sent from my Moto G5 Plus using XDA Labs
POTTER_NPNS25.137-93-4: https://androidfilehost.com/?fid=746010030569968312
Most recent, uploaded on 04/11. Don't expect the next one for a few or more months.
Wolfcity said:
Firmwares with the ending 92-x are for India and Brazil, ending on 93-x for Europe, US and Asia Pacific.
For Europe/US the latest firmware is 93-10 (April security patch).
The latest one I found uploaded is 93-4. The same for India, 92-4 is uploaded.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
Maybe that's why my device got screwed? Because I flashed EU firmware 93-4 on an Indian Variant? I think NOT
braindeductions said:
Maybe that's why my device got screwed? Because I flashed EU firmware 93-4 on an Indian Variant? I think NOT
Click to expand...
Click to collapse
A lot of people did. Maybe that's causing problems, I only know that you can't receive OTA's anymore.
The devices should work as expected but what happens if you flash a custom ROM and go back to stock (maybe another build?)I don't know but it's possible that all this voLTE and IMEI losing stuff is related to it.
Sent from my Moto G5 Plus using XDA Labs
Wolfcity said:
A lot of people did.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
Meanwhile, I am figuring out a way to hardbrick this device and use blankflash to bypass the bootloader.
Wolfcity said:
A lot of people did. Maybe that's causing problems, I only know that you can't receive OTA's anymore.
The devices should work as expected but what happens if you flash a custom ROM and go back to stock (maybe another build?)I don't know but it's possible that all this voLTE and IMEI losing stuff is related to it.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
That's what happens when there's multiple variants of the same phone and no one properly labels the firmware or provides specifications. I've done it, got back to stock with a locked bootloader and recovered IMEI. OTA updates installed with no issues but left with stuck with IMEI 0 again. Anyone in this situation who failed to make an initial backup with EFS or lost that backup is screwed. At this point you're best option is to stick with a stable Oreo ROM. We're getting better support from devs while Lenovo leaves us in the dark.
braindeductions said:
Meanwhile, I am figuring out a way to hardbrick this device and use blankflash to bypass the bootloader.
Click to expand...
Click to collapse
https://forum.xda-developers.com/g5-plus/help/moto-g5-plus-hard-bricked-hard-t3661219
^^A user said using albus blankflash Deodexed ROM worked.
Randumb_User said:
https://forum.xda-developers.com/g5-plus/help/moto-g5-plus-hard-bricked-hard-t3661219
^^A user said using albus blankflash Deodexed ROM worked.
Click to expand...
Click to collapse
My problem is finding a way to hardbrick the device while the bootloader is locked.
Does anybody have this file yet? Thanks.
can anyone make a flashable TWRP?
https://drive.google.com/file/d/1Kn6oIejMP8zSOB5QOIfVx5nVqP3SvOYE/view?usp=drivesdk
I'm using the Amazon version of the g5 plus. Is it even possible to downgrade to nougat on this?
I'm gonna say no... bootloader can't be unlocked. But why would you want to? There are no real issues with Oreo...
jmindset said:
I'm using the Amazon version of the g5 plus. Is it even possible to downgrade to nougat on this?
Click to expand...
Click to collapse
Yes, you can downgrade to nougat but you should remove the bootloader and gpt codes , so your device won't hard brick.
acejavelin said:
I'm gonna say no... bootloader can't be unlocked. But why would you want to? There are no real issues with Oreo...
Click to expand...
Click to collapse
Well I just hate the fact that night mode was removed. Now when I use an app for blue light filter, it only works while using the phone. Not on the lockscreen not the pulldown notifications bar. An annoyance more than an actual issue but still...
riyan65 said:
Yes, you can downgrade to nougat but you should remove the bootloader and gpt codes , so your device won't hard brick.
Click to expand...
Click to collapse
Except if you do this, and happen to accept an OTA later it will hard brick if experience with previous Moto devices holds.
acejavelin said:
Except if you do this, and happen to accept an OTA later it will hard brick if experience with previous Moto devices holds.
Click to expand...
Click to collapse
I don't think so, as you are using the latest bootloader with old firmware, after if you update also it just going to update as normal happeneds. If you won't downgrade your bootloader it won't brick at all.yes by updating there could a soft brick chances,but that can be recoverable by fast boot.
riyan65 said:
I don't think so, as you are using the latest bootloader with old firmware, after if you update also it just going to update as normal happeneds. If you won't downgrade your bootloader it won't brick at all.yes by updating there could a soft brick chances,but that can be recoverable by fast boot.
Click to expand...
Click to collapse
I can tell you with 100% certainty that this can happen, and did on Moto G 2015 and Moto X Pure. If you upgraded, then downgraded by fastboot flashing and skipping bootloader and GPT, then you take an OTA update back to the higher version it would hardbrick... No boot, no bootloader, no fastboot... falls immediately into Qloader 9008 mode. It related to the partition table, which is in gpt.bin, and how it resizes it. I know it doesn't make sense, but it definitely happens.
You could always reflash the full factory to upgrade though, that worked... But that OTA was bad news on a device that was downgraded.
acejavelin said:
I can tell you with 100% certainty that this can happen, and did on Moto G 2015 and Moto X Pure. If you upgraded, then downgraded by fastboot flashing and skipping bootloader and GPT, then you take an OTA update back to the higher version it would hardbrick... No boot, no bootloader, no fastboot... falls immediately into Qloader 9008 mode. It related to the partition table, which is in gpt.bin, and how it resizes it. I know it doesn't make sense, but it definitely happens.
You could always reflash the full factory to upgrade though, that worked... But that OTA was bad news on a device that was downgraded.
Click to expand...
Click to collapse
It thought it was impossible to flash a stock room with a locked bootloader? I have the Amazon version of the Moto g5 plus. Am I missing something?
jmindset said:
It thought it was impossible to flash a stock room with a locked bootloader? I have the Amazon version of the Moto g5 plus. Am I missing something?
Click to expand...
Click to collapse
You can flash a stock ROM that is the same version or higher, in the same software channel, on a locked bootloader... you cannot downgrade or use a different software channel with a locked bootloader.
Sorry, we kind of got off on a bit of a tangent there.
acejavelin said:
You can flash a stock ROM that is the same version or higher, in the same software channel, on a locked bootloader... you cannot downgrade or use a different software channel with a locked bootloader.
Sorry, we kind of got off on a bit of a tangent there.
Click to expand...
Click to collapse
It's ok lol so basically I won't be able to downgrade? Knowing Motorola they won't bother responding to the complaints https://forums.lenovo.com/t5/Moto-G...-provided-in-moto-g5-plus/td-p/4222569/page/4
jmindset said:
It's ok lol so basically I won't be able to downgrade? Knowing Motorola they won't bother responding to the complaints https://forums.lenovo.com/t5/Moto-G...-provided-in-moto-g5-plus/td-p/4222569/page/4
Click to expand...
Click to collapse
Correct... You cannot downgrade without an unlocked bootloader, and you cannot unlock the bootloader on an Amazon device.
Moto is now owned by Lenovo, since this occurred they have shown little interest in enhancing or changing anything they release for a device over 6 months old. Unless there is tremendous outcry, meaning like 10's of thousands of people... We tried to petition them to continue update on the Moto G 2015 a while back (something that was stated initially in the devices release) and got about 25,000 signatures. Lenovo didn't even acknowledge it existed. So if you want a significant change in a device, you are going need to get a fairly LARGE outcry from customers, like 50k+ I am guessing, before they would even consider thinking about it, and that isn't likely to happen.
acejavelin said:
Correct... You cannot downgrade without an unlocked bootloader, and you cannot unlock the bootloader on an Amazon device.
Moto is now owned by Lenovo, since this occurred they have shown little interest in enhancing or changing anything they release for a device over 6 months old. Unless there is tremendous outcry, meaning like 10's of thousands of people... We tried to petition them to continue update on the Moto G 2015 a while back (something that was stated initially in the devices release) and got about 25,000 signatures. Lenovo didn't even acknowledge it existed. So if you want a significant change in a device, you are going need to get a fairly LARGE outcry from customers, like 50k+ I am guessing, before they would even consider thinking about it, and that isn't likely to happen.
Click to expand...
Click to collapse
Lol and for that exact reason, I will not purchase another Motorola device. So glad that the mid-range phone market is getting wider each year. I will purchase a Nokia 7.1 next. At least that phone will get guaranteed updates for the next few years.
Just adding to this thread, even if it were possible to downgrade the system to nougat, you would have problems with losing your IMEI. The fix would require root access, and again that's not possible on a locked bootloader.