I just got off the phone with a guy from Motorola Brazil.
He clarified a lot of things. Some are good news, others not really.
DISCLAIMER: I am not responsible for any actions you take after reading this. If you try anything and it doesn't work, it's you to you to find a way out. You can always post it here and the community will try to help you. It's your phone. Your actions.
Release Date
He didn't give me a date, rather, he told me the roadmap to it. Motorola is scaling upwards.
G > X > G2 > X+1 > Maxx/Turbo
Reminder: Verizon says when Turbo gets it after Motorola ships it to Verizon.
They are testing the waters on smaller and cheaper devices. Apparently the "under-the-hood" changes are pretty complicated and giving them some headaches. I'd say it makes sense to what @Chainfire has been saying for quite a while now. Many security changes that are affecting how you can interact with the kernel and the init.d process, for example.
Bootloader Unlockability
Moto Maxx is unlockable. All you need is to go to their website and follow instructions. In KITKAT
Apparently, Motorola still hasn't confirmed if they'll allow their customers to unlock the bootloader once Lollipop hits.
Like I said, there's no confirmation. Motorola can always just be a good pal and keep on allowing it, it's all just speculations.
Recovery Firmware
It's the same firmware as the Moto X AND the Moto X 2014. It's up to you to try it out. I might try it next weekend if I got the time.
There are no devs working on Maxx/Turbo AFAIK. However, we can apparently use the firmwares from Moto X or the Moto X 2014.
This topic is the sole reason I added the disclaimer up there. Read it!
The guy told me this, but understand that even though its not a confidential thing, it certainly is extra official. For those who thought a Moto X 2014 TWRP or CWM would brick their devices. Well, apparently, it won't. I'll remove the apparently when I have confirmation on this. Anyone feeling lucky, post your results here or just PM me.
Root
Root is a complicated matter.
In Kitkat.
With the previous information, we might be able to root it following Moto X 2014's instructions. More news in the future.
In Lollipop.
For those who don't know, we should be able to use root, once we patch up the kernel to boot the device allowing root. @Chainfire got it to work without the patch on the Nexus line in SuperSU 2.27, but it's really simple for Google to patch it. Don't expect it to last. Considering the amount of work it takes, we might end up with the shorter stick here. Unless some cool dev decides make it work for us as well, or if the patch for the Nexus 6 somehow work with the Maxx.
Someone will have to try it.
That's it for now. I'll try to update this as new info comes out.
Please, leave a THANKS if you enjoyed it.
Surely these are quite good news. But officially, based on moto website, maxx is not unlockable by now. But these stuff being true is worth of not getting kitkat OTA, to keep the supposed unlockable state, using custom roms, if they someday become available.
ska4fun said:
Surely these are quite good news. But officially, based on moto website, maxx is not unlockable by now. But these stuff being true is worth of not getting kitkat OTA, to keep the supposed unlockable state, using custom roms, if they someday become available.
Click to expand...
Click to collapse
I unlocked mine already. It's just as the site says: get the code, send it to them, they reply with the unlock code
Nice! Thanks for the clarification!
alexcreto said:
Release Date
He didn't give me a date, rather, he told me the roadmap to it. Motorola is scaling upwards.
G > X > G2 > X+1 > Maxx/Turbo
Reminder: Verizon says when Turbo gets it after Motorola ships it to Verizon.
They are testing the waters on smaller and cheaper devices. Apparently the "under-the-hood" changes are pretty complicated and giving them some headaches. I'd say it makes sense to what @Chainfire has been saying for quite a while now. Many security changes that are affecting how you can interact with the kernel and the init.d process, for example.
Click to expand...
Click to collapse
So according to your source, we should be getting Lollipop after all the G's and X's were updated?, if this is the case, I think we should be getting Lollipop really soon, because most of the devices already have Android 5.
:highfive:
Galaxo60 said:
So according to your source, we should be getting Lollipop after all the G's and X's were updated?, if this is the case, I think we should be getting Lollipop really soon, because most of the devices already have Android 5.
:highfive:
Click to expand...
Click to collapse
I don't think that's the case. Both of those devices have a soak test in progress but lollipop has not officially been released to either. Unless I missed a few updates. .
cyberr8der said:
I don't think that's the case. Both of those devices have a soak test in progress but lollipop has not officially been released to either. Unless I missed a few updates. .
Click to expand...
Click to collapse
The soak tests were made before Lollipop was officially released (before Nov 13), but Motorola already made an official state about this here:
http://motorola-blog.blogspot.mx/2014/11/its-time-to-unwrap-android-5-lollipop.html
It seems that Lollipop was already released.
Looks like you're correct. Based on that it seems it is released for certain models. Surprised to see that yet the soak test hasn't started for the turbo. Thanks for sharing.
ska4fun said:
Nice! Thanks for the clarification!
Click to expand...
Click to collapse
I've put my oem unlock key in Motorola website and it says my device is unlockable, but I didn't proceed
I will proceed with the release of the first compatible recovery.
Galaxo60 said:
The soak tests were made before Lollipop was officially released (before Nov 13), but Motorola already made an official state about this here:
http://motorola-blog.blogspot.mx/2014/11/its-time-to-unwrap-android-5-lollipop.html
It seems that Lollipop was already released.
Click to expand...
Click to collapse
Just saw this as well. Seems the soak test for the Verizon Moto X is under way.
http://m.androidcentral.com/soak-test-invites-going-out-2014-moto-x-verizon
The guy mentioned they were testing an internal build for the G2
Firmware for moto x and Moto x 2014 obviously doesn't work,not even recovery, first of all the devices are different in hardware and have different device trees, it will simple not flash whoever in motorola that told you that, doesn't know how all this works.
Jaocagomez said:
Firmware for moto x and Moto x 2014 obviously doesn't work, but even recovery, first of all the devices are different in hardware and have different device trees, it will simple not flash whoever in motorola that told you that, doesn't know how all this works.
Click to expand...
Click to collapse
yeah I think it's just a first line of support or something like that
Jaocagomez said:
Firmware for moto x and Moto x 2014 obviously doesn't work, but even recovery, first of all the devices are different in hardware and have different device trees, it will simple not flash whoever in motorola that told you that, doesn't know how all this works.
Click to expand...
Click to collapse
I thought it was weird. I even double checked. "Moto X+1 with the Moto X recovery??" and the guy said that he'd done it himself.
Go figure...
Sent from my XT1225 using XDA Free mobile app
Nexus 6 have a same hardware, anyone think if works in maxx?
The recovery for the 6 is for LP and is markedly different than a KK recovery. Also be aware that Troy Dees (TWRP) is on record as saying the recoveries for LP are much more involved than KK and to expect a relatively slow roll out for them to a broader range of devices. He did not say it but the impression I have from reading his comments on this are that marginal devices in terms of number of owners may be waiting a long time or never see a TWRP recovery for LP.
matheus_sc said:
Nexus 6 have a same hardware, anyone think if works in maxx?
Click to expand...
Click to collapse
if nexus 6 already has twrp recovery check if it works, thats the same hardware. just unlock moto maxx bootloader first.
worst case escenario its that TWRP wont work and you'll have to flash stock recovery.img again.
Jaocagomez said:
if nexus 6 already has twrp recovery check if it works, thats the same hardware. just unlock moto maxx bootloader first.
worst case escenario its that TWRP wont work and you'll have to flash stock recovery.img again.
Click to expand...
Click to collapse
once u flash recovery u will lose all ur data
danger2u said:
once u flash recovery u will lose all ur data
Click to expand...
Click to collapse
No... Once u unlock boot loader u loose all your data!
Related
From the Motorola website:
https://motorola-global-portal.cust...ldYaksyY0VsIiwic2Vzc2lvbklEIjoiV1hqSzJjRWwifQ..
I would be surprised if we didn't. It's only a matter of how much time Motorola decides to take pushing this update.
Moto X | Stock Unrooted
abiezer said:
From the Motorola website:
https://motorola-global-portal.cust...ldYaksyY0VsIiwic2Vzc2lvbklEIjoiV1hqSzJjRWwifQ..
Click to expand...
Click to collapse
Sweet! Now we just need a date.
dapezboy said:
Sweet! Now we just need a date.
Click to expand...
Click to collapse
I actually reckon we shouldn't get a date.. Issues may pop up that may delay release.. Remember the feeling of frustration when Punit Soni announced that Dev editions would be released in days and it didn't happen for weeks?
Sent from my XT1058
dr3wster said:
I actually reckon we shouldn't get a date.. Issues may pop up that may delay release.. Remember the feeling of frustration when Punit Soni announced that Dev editions would be released in days and it didn't happen for weeks?
Sent from my XT1058
Click to expand...
Click to collapse
Funny you mention that:
"We are moving directly to 4.4. I dont like to discuss timing. It just puts a lot of stress on the team, and there is always a chance we find something which delays us a bit.
Rest assured, we are on it. You have seen the speed with which we are moving as a Google company, that shall continue."
- Punit Soni, https://plus.google.com/+PunitSoni/posts/LAKKMnEE6CQ , scroll way down (or just Ctrl-F a phrase from that quote)
I'm just looking forward to all the awesome things we have in store; just got my MotoX yesterday and got it activated today; less than 12 hours with an activated and working phone, and I love everything it does already. Getting 4.4 is just icing on the cake for me.
Don't get me wrong.. I'm equally impatient lol... But then again, the Moto X runs amazingly on 4.2.2 already
Sent from my XT1058
I'm just wondering, will the bootloader have to be relocked in order to receive the OTA?
sookster54 said:
I'm just wondering, will the bootloader have to be relocked in order to receive the OTA?
Click to expand...
Click to collapse
No, just like the previous update, someone will come up with a flashable zip.
sookster54 said:
I'm just wondering, will the bootloader have to be relocked in order to receive the OTA?
Click to expand...
Click to collapse
The bootloader does not have to be relocked! just make sure that you flash back to stock format including your recovery. And you'll be able to take any and all updates. After you update to Kit Kat you should be able to flash superuser zip in CWM or TWRP. To gain Root.
Sent from non rooted motoX :'(
matt99017d said:
The bootloader does not have to be relocked! just make sure that you flash back to stock format including your recovery. And you'll be able to take any and all updates. After you update to Kit Kat you should be able to flash superuser zip in CWM or TWRP. To gain Root.
Sent from non rooted motoX :'(
Click to expand...
Click to collapse
OK that makes sense, I can always restore back to stock then.
I'm keeping my hopes high and my expectations low. I still remember the Atrix after all. New Motorola or not, even if they plan to ship out 4.4 quickly, there is still the carrier issue. I'll believe it when the soak invites go out.
Sent from my XT1058 using Tapatalk
I kept telling all you guys that Motorola was skipping 4.3 and going directly for kit Kat now its come to fruition. You're welcome
Hi,
I have my moto x with the last OTA, i kept root with a tuto that's here.
I want to flash the stock firmware with rsd, my question is if it will take it as downgrade.
I want to wait for KitKat un-rooted.
Thanks
Well it looks like 5.0.1 has started to roll out to the Moto G 1st and 2nd generation. I hope it fixes the freezing problem I have on my xt1064 running 5.0
Post here if you receive and/or install 5.0.1, and let us know how it works out for you. Such as improvements, bugs, problems with installation, etc. Please include what model you have.
http://www.androidauthority.com/android-5-0-1-lollipop-moto-g-575758/
Indian soak test user received it yesterday
I think we can all safely assume that now, 5 weeks after starting, the "soak test" is now long over and done with. After all, Motorola stated that Lollipop would be out on the Moto G *before* the end of 2014... and guess what? Only 12 days of that left. Unless they're into cutting it fine, this IS the final release, folks.
gnubash said:
I think we can all safely assume that now, 5 weeks after starting, the "soak test" is now long over and done with. After all, Motorola stated that Lollipop would be out on the Moto G *before* the end of 2014... and guess what? Only 12 days of that left. Unless they're into cutting it fine, this IS the final release, folks.
Click to expand...
Click to collapse
To be frank, Motorola likely shifted from 5.0 to 5.0.1 midway the soak test. And 5.0.2 is pretty near as well, who knows if they won't shift development for it before this rollout ends.
Derfderk said:
To be frank, Motorola likely shifted from 5.0 to 5.0.1 midway the soak test. And 5.0.2 is pretty near as well, who knows if they won't shift development for it before this rollout ends.
Click to expand...
Click to collapse
What does that matter, when it's all Lollipop, after all? Would you prefer they release 5.0 and not a more updated, polished release version instead? They'll release on time, believe me.
Yep just got it, lets see what it shall bring!
Sent from my SM-P600 using XDA Premium HD app
One vital piece of information that people seem to be overlooking, once THEY get Lollipop on THEIR device, is this:
Mention your country please
Have successfully upgraded to 5.01 on ma XT1033 BRAZ FRAMEWORK Soak LP N now waiting for XT1068.. Its awesome n more smoother now..
sent From My XT1033{LP} using TapatalK
gnubash said:
One vital piece of information that people seem to be overlooking, once THEY get Lollipop on THEIR device, is this:
Mention your country please
Click to expand...
Click to collapse
It would also be nice if people would also make note of the baseband version associated with each release. There already been enough tears from fools flashing baseband firmware willy-nilly.
Okay, I had upgraded to 22.21.16 via TWRP using KennyWuLee's packaged tool. This morning I received a notice that I had an update available for 22.21.25 which I assume is 5.0.1. So like a dummy I went ahead and accepted. Now all it does is boot into TWRP. When I restart to system from TWRP it boots up just fine then after about 15 seconds reboots to TWRP.
I assume it is looking for the stock recovery which will then allow me to install the update? So will I be safe to go ahead and reflash the stock recovery, reboot and go from there? Or should I go all the way back to stock everything?
I have an XT1063.
pastorbob62 said:
Okay, I had upgraded to 22.21.16 via TWRP using KennyWuLee's packaged tool. This morning I received a notice that I had an update available for 22.21.25 which I assume is 5.0.1. So like a dummy I went ahead and accepted. Now all it does is boot into TWRP. When I restart to system from TWRP it boots up just fine then after about 15 seconds reboots to TWRP.
I assume it is looking for the stock recovery which will then allow me to install the update? So will I be safe to go ahead and reflash the stock recovery, reboot and go from there? Or should I go all the way back to stock everything?
I have an XT1063.
Click to expand...
Click to collapse
Correct
Android The Greek said:
Correct
Click to expand...
Click to collapse
To which question?
Are European buyers still being ignored? XT1068: no MFN, no update of any kind here. If I am interpreting Motorola forum correctly, they haven't released anything in the EU, not even a soak test.
Derfderk said:
To be frank, Motorola likely shifted from 5.0 to 5.0.1 midway the soak test. And 5.0.2 is pretty near as well, who knows if they won't shift development for it before this rollout ends.
Click to expand...
Click to collapse
Correct, 5.0.2 has been released for Nexus 7 today.
And PLEASE, PLEASE before updating go here and try to capture the ota.
kzakhar said:
Are European buyers still being ignored? XT1068: no MFN, no update of any kind here. If I am interpreting Motorola forum correctly, they haven't released anything in the EU, not even a soak test.
Click to expand...
Click to collapse
I think Motorola secretly hate us because we can unlock our devices and still make a warranty claim if the hardware fails.
rufflove said:
I think Motorola secretly hate us because we can unlock our devices and still make a warranty claim if the hardware fails.
Click to expand...
Click to collapse
You could be right.
I got this phone happy in the knowledge I'll always be running (nearly) the latest clean version of Android, instead I have a phone with a memory management issue running at least a month behind other continents.
Tongue in cheek aside, I do have some suspicions.
It stands to reason that the people most likely to join the MFN are those who like to tinker and who are eager to receive updates. These people are also the most like to unlock the bootloader. If something goes awry during an OTA roll-out test and the user cannot resolve the issue, support from Motorola can be requested, potentially resulting in a warranty claim, unless the device has been unlocked and was purchased outside of the EU... It therefore seems logical that Motorola would not do soak tests in the EU, where possible: It reduces the blowback in the unlikely event that there is a serious bug in the update.
rufflove said:
Tongue in cheek aside, I do have some suspicions.
It stands to reason that the people most likely to join the MFN are those who like to tinker and who are eager to receive updates. These people are also the most like to unlock the bootloader. If something goes awry during an OTA roll-out test and the user cannot resolve the issue, support from Motorola can be requested, potentially resulting in a warranty claim, unless the device has been unlocked and was purchased outside of the EU... It therefore seems logical that Motorola would not do soak tests in the EU, where possible: It reduces the blowback in the unlikely event that there is a serious bug in the update.
Click to expand...
Click to collapse
That sounds like the most plausible reason they may have, if they have one. To be honest, I've got better things to think about than when a frivolous software update arrives for a non-cricital device, but your thoughts certainly are rational ones
Well I was part of the xt1069 Brazilian soak test and I have to say it's a bad joke. A lot of users didn't get the update, there was almost no support or even feedback from Motorola in the forum. And to finish it off, they had an issue with their forum software that got all comments deleted. I don't think EU users are missing much
Source: David Schuster - https://plus.google.com/+DavidSchuster/posts/cV4vDyyMmw2
LATEST UPDATE [06-19-2015]
Full deployment has started for US Retail, Brazil Retail and Rogers in Canada.
Source: David Schuster - https://plus.google.com/+DavidSchuster/posts/bEVD4De32Uo
UPDATE [06-09-2015]
"I wanted to give a quick update on where we are with the Lollipop upgrades for the 2013 Moto X (1st Gen) devices.
We have started full soak testing in France and Germany retail this week with the expectation of full deployment next week if all goes well.
In addition, we have addressed an issue we found in a previous soak test and should start full soak testing in the US and Brazil for retail later this week. If all goes well, full deployment can happen the following week.
There were some questions about support for Lollipop upgrades from our carrier channels. We are in a number of the carrier labs now so we don't anticipate issues in getting the upgrades deployed. As you guys know.... the carrier channels typically take longer.
UPDATE: If all goes well with the soak testing this week we expect to start deployment for 2013 Moto X (1st gen) in India next week."
Source: David Schuster - https://plus.google.com/+DavidSchuster/posts/ETpoNrkmmrA
UPDATE [04-22-2015]
Due to the "leaks" about 5.1 "updates rolling out" in Brazil, here's some trusted words in regard to 5.1 current state:
"We're still in testing. We'll post something in the parked comments when it moves to the Soak stage and then again when full deployment happens. Don't always believe what you read online."
Source: Motorola Forums Manager (Mark).
Awsome
Kustaa said:
So, it's kind of official now, we'll have to wait a little longer, but 5.1 will be definitely here for our 2013 X
source: David Schuster - https://plus.google.com/+DavidSchuster/posts/cV4vDyyMmw2
Click to expand...
Click to collapse
good stuff. im no longer annoyed at the update taking so long again
This is great news, it can surely only be a matter of weeks now before it is officially released
I'm still on 4.4.4... Should I take the official or just wait for a rooted version?
Also assuming there is still issues with xposed?
mroneeyedboh said:
I'm still on 4.4.4... Should I take the official or just wait for a rooted version?
Also assuming there is still issues with xposed?
Click to expand...
Click to collapse
You can't take nothing yet lol
Good news, I can survive with 4.4.4 till 5.1.
5.0.2 still have issues.
Cool stuff!
I kinda feel bad for the people who won't be able to return to stock 4.4.4 now. :s
Sweet. Can't wait to rock this in 2017!
I'm just getting an error when I click the link?
Sent from my XT1060 using Tapatalk
wiidbzxt said:
Cool stuff!
I kinda feel bad for the people who won't be able to return to stock 4.4.4 now. :s
Click to expand...
Click to collapse
Do you mean those who installed 5.0.2 test drive?
I don't think Motorola would leave the official MFN testers on an incomplete test drive version, furthermore it makes sense to use the same testers to test 5.1, so as soon as those users get 5.1 it will leak and those who sideloaded 5.0.2 will have the upgrade.
Otherwise, it would be as easy as return to 4.4.4 temporary (skipping gpt and motoboot) and sideload the 5.1 upgrade, not big deal.
No matter what, the situation is not to feel bad about them, maybe they'll even get the upgrade before you do.
I have an brazilian XT 1058 and take the soak. I will be able to update to 5.1?
Logically yes.
Sent from my XT1052 using XDA Free mobile app
I'm glad for this. 5.1 didn't address the memory leak did it?
crazyxzer0 said:
I'm glad for this. 5.1 didn't address the memory leak did it?
Click to expand...
Click to collapse
I'm pretty sure it did, at least for the nexus 6
I think the memory leak was also addressed via xposed module so less of an issue for xposed users
Sent from my XT1053 using Tapatalk 2
wiidbzxt said:
Cool stuff!
I kinda feel bad for the people who won't be able to return to stock 4.4.4 now. :s
Click to expand...
Click to collapse
I can confirm, that downgrading of bootloader from 30.BC back to 30.B7 IS possible. I bricked one my phone for test: 4.4.4->5.0.2 (via OTA)->4.4.2->bricked by OTA via WiFi. Now it's running again Thanks to Tenigima
good news i hope soak 5.1 for all regions not only for brazil as with 5.0.2
Ii there a specific date ??
Moto-x said:
good news i hope soak 5.1 for all regions not only for brazil as with 5.0.2 [emoji14]
Ii there a specific date ??
Click to expand...
Click to collapse
In android world there's never a specific date unfortunately.
Enviado desde mi XT1060 mediante Tapatalk
sylarm said:
Good news, I can survive with 4.4.4 till 5.1.
5.0.2 still have issues.
Click to expand...
Click to collapse
Have you even used it?
I'm not saying Moto did or did not fix anything, but so many people keep saying "Ohhh its version XXXX which has XXXX bug!"
1.) We don't run AOSP
2.) When google updates android, all of those changes are published. 5.1 is NOT a full re-write, sections of code are fixed. These fixes are published and if moto REALLY felt like it they could apply all the same code changes to a 5.0.1 base... At that point what is "version number" is is kinda semantics....
Moto started work on 5.0.2, so that is what their build is called, there is no reason they cannot include the already published bug fixes from later versions of android so they they can release their tested a developed build rather then throwing everything away and starting with a new base every time google updates.
Mine will be arriving Monday hopefully.
I've noticed people are flashing the Moto G 2015 twrp which I find a little worrying. Just wondering is this because we don't yet have kernel source for the X Play?
I'm hoping to eventually see CM12 for this phone but it all depends on its popularity.
Sent from my Vodafone Smart ultra 6 using Tapatalk
ephumuris said:
I've noticed people are flashing the Moto G 2015 twrp which I find a little worrying. Just wondering is this because we don't yet have kernel source for the X Play?
Click to expand...
Click to collapse
Yep. It's all we can do for now.
We don't even have a stock firmware to flash back to if something goes wrong. That's why I just did a temporary boot to TWRP to install SuperSU and Xposed. I'm not willing to flash anything until there is something to fall back on.
ephumuris said:
I'm hoping to eventually see CM12 for this phone but it all depends on its popularity.
Click to expand...
Click to collapse
Honestly, I wouldn't bet on it happening.
The X Play isn't very popular and has no mod support so far. I haven't seen a single ROM/kernel developer posting on these forums to date. That might change when the kernel sources are released and the stock firmware becomes available for download, but I'm not holding my breath.
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.