I was pleasantly surprised to see an update being offered this morning. I am on 22.21.25 (the latest OTA so far for XT1064).
Did anybody else see this?
No idea what it fixes though.
XT1063 with unlocked boot loader got the same update. 39.1mb will post screenshots soon
Android The Greek said:
XT1063 with unlocked boot loader got the same update. 39.1mb will post screenshots soon
Click to expand...
Click to collapse
Screen below
5.0.2!
Yup, 5.0.2
Received the 5.02 OTA today on my XT1063 (US). installed fine. I was rooted, but unrooted using SuperSU (strangely, "full unroot" hung, but "unroot for installing a different SU app" worked just fine). I was using stock recovery, and the OTA installed perfectly fine.
Bonus: forgot to revert to original hosts from adaway before installing the OTA. Still worked! So now, I don't have root, but am ad-free!!
So looks like (for now) "Lolipop OTAs require an untouched /system" is a bit of an exaggeration. Hooray!
(haven't re-rooted yet).
I am really impressed with Motorola. I know there have been some hiccups with different variants of the same phone but wow already on 5.0.2
Downloading now
Seriously said:
Received the 5.02 OTA today on my XT1063 (US). installed fine. I was rooted, but unrooted using SuperSU (strangely, "full unroot" hung, but "unroot for installing a different SU app" worked just fine). I was using stock recovery, and the OTA installed perfectly fine.
Bonus: forgot to revert to original hosts from adaway before installing the OTA. Still worked! So now, I don't have root, but am ad-free!!
So looks like (for now) "Lolipop OTAs require an untouched /system" is a bit of an exaggeration. Hooray!
(haven't re-rooted yet).
Click to expand...
Click to collapse
They haven't moved to the block level deltas for the /system partition as yet. They are still patching file to file. So, as long as the files being patched are not touched by you, you are ok.
From here:
Today's Lollipop 5.0.2 rollout for Moto G (1st Gen & 2nd Gen): this is a soak test for India, Brazil & the U.S. If the performance data looks good after several days, then we'll roll out more widely. This is why some may see 'up to date' when checking - it is not yet exposed to the whole user population.
Note: Moto G (1st Gen) users need to ensure that they have the latest Motorola Updates Services from the Play Store. If you see an update available, please install it - otherwise you will not see the future Lollipop upgrade notification. This is not necessary for Moto G (2nd Gen).
Click to expand...
Click to collapse
This could potentially mean Moto G users as a whole may be getting Lollipop by the end of the month, if all goes well.
Traediras said:
From here:
This could potentially mean Moto G users as a whole may be getting Lollipop by the end of the month, if all goes well.
Click to expand...
Click to collapse
In EU we didn't received even 5.0 for our dual-sim models, not even a soak test.
devsk said:
They haven't moved to the block level deltas for the /system partition as yet. They are still patching file to file. So, as long as the files being patched are not touched by you, you are ok.
Click to expand...
Click to collapse
Have Google given any indication when they'll be moving to the new patching system?
Seriously said:
Have Google given any indication when they'll be moving to the new patching system?
Click to expand...
Click to collapse
They probably already have. Some people claimed they got OTA in the partition block diff format for Nexus series phones. May be motorola is keeping the current method alive on its own. After all, its just packaging and OEMs choose the packaging.
devsk said:
They probably already have. Some people claimed they got OTA in the partition block diff format for Nexus series phones. May be motorola is keeping the current method alive on its own. After all, its just packaging and OEMs choose the packaging.
Click to expand...
Click to collapse
Hopefully Moto keeps using the old patching system as they haven't been particularly forthcoming with providing factory images for the Moto G 2014.
Seriously said:
Hopefully Moto keeps using the old patching system as they haven't been particularly forthcoming with providing factory images for the Moto G 2014.
Click to expand...
Click to collapse
It honestly doesn't make much of a difference. Keep a bare stock backup always handy, with pretty much empty /data partition. So, basically the update procedure is (and would continue to be):
0. Capture the OTA zip from /cache.
1. Take a full TWRP back up of the current ROM, with your changes etc.
2. Restore to previous bare stock ROM including the stock recovery.
3. Sideload the OTA zip and make sure to boot at least once (and skip account setup if this is the first OTA ever).
4. Flash TWRP recovery partition
5. Take a TWRP backup of new bare stock ROM for use for the next OTA.
6. Restore your /data.
7. Install SuperSU.zip, and optionally busybox.
8. Profit!
This means all your changes to the /system partition are lost. But you should not be making changes to /system partition anyway (apart from the SuperSU and busybox).
Note that you can not afford to miss an OTA... The above procedure breaks. So, keep up with OTAs.
devsk said:
Note that you can not afford to miss an OTA... The above procedure breaks. So, keep up with OTAs.
Click to expand...
Click to collapse
I got a bad bootloop after rooting. I've read that eventually it will boot up. Are you having any issues? Do you have an XT1064?
LoneStarPhD said:
I got a bad bootloop after rooting. I've read that eventually it will boot up. Are you having any issues? Do you have an XT1064?
Click to expand...
Click to collapse
SuperSU 2.44 should work fine on XT1064. It should not lead to any bootloops.
devsk said:
SuperSU 2.44 should work fine on XT1064. It should not lead to any bootloops.
Click to expand...
Click to collapse
Thanks! Latest version of TWRP okay?
must unlocked boot loader used to get an OTA update lolliop ?
my device XT1063
qudsbeat said:
must unlocked boot loader used to get an OTA update lolliop ?
my device XT1063
Click to expand...
Click to collapse
No not if you had you phone on 21.11.17. If you are on 21.11.23 there is no update that I know of for XT1063.
Related
I was offered the 5.1 update on my 2013 Nexus 7. In an attempt to be on the safe side, I uninstalled busybox, titanium, and fully unrooted (I always had the stock recovery, so I didn't have to worry about that). Anyway, even after all those precautions, the attempt to install failed after a couple of minutes with an android keeled over and a red warning triangle. The highly informative message "Error!" was displayed under the keeled over android. Just wondering if other folks are seeing this same problem.
About 5 minutes later while I was poking around in this forum, the tablet rebooted itself and it appears to be running 5.0.2 with no obvious problems.
Any clues about what might be going on? Any way to extract more information than "Error!"?
Claghorn said:
I was offered the 5.1 update on my 2013 Nexus 7. In an attempt to be on the safe side, I uninstalled busybox, titanium, and fully unrooted (I always had the stock recovery, so I didn't have to worry about that). Anyway, even after all those precautions, the attempt to install failed after a couple of minutes with an android keeled over and a red warning triangle. The highly informative message "Error!" was displayed under the keeled over android. Just wondering if other folks are seeing this same problem.
About 5 minutes later while I was poking around in this forum, the tablet rebooted itself and it appears to be running 5.0.2 with no obvious problems.
Any clues about what might be going on? Any way to extract more information than "Error!"?
Click to expand...
Click to collapse
To take ota you must have a clean non rooted system. Not one you attempted to remove traces of root from. If you want ota you have to flash 5.0.2 system.img extracted from the factory image. Any trace of root or a missing file or apk will cause it to fail.
madbat99 said:
To take ota you must have a clean non rooted system. Not one you attempted to remove traces of root from. If you want ota you have to flash 5.0.2 system.img extracted from the factory image. Any trace of root or a missing file or apk will cause it to fail.
Click to expand...
Click to collapse
I'm not sure what would leave a trace. I've always been able to get OTA previously via the fully uninstall everything technique.
Claghorn said:
I'm not sure what would leave a trace. I've always been able to get OTA previously via the fully uninstall everything technique.
Click to expand...
Click to collapse
Since lollipop it is very sensitive to anything different or missing in system. Just flash the 5.1 factory image with the ~w removed from the flash-all.bat file so it doesn't wipe data. Or use wugs to flash stock 5.1 image with "no wipe" enabled. Or like I said in previous you can always flash a clean system image of 5.0.2 then take ota. Either way will update you without wiping data.
Just use fastboot and manually flash system.img and boot.img, then format cache. It works every single time, without wiping data and you can easly root it again with CF Auto Root. I don't get it why people bother with OTA all the time. Always issues with them. I just did this and went from 5.0.2 to 5.1 without losing any data, and tablet now really flies. It keeps a lot more apps in RAM, for better multitasking, and I don't experiance any lag what so ever. I strongly recommend everyone to update to 5.1, because it feels like you just got a new tablet. Good job Google !
neo5468 said:
... I don't get it why people bother with OTA all the time ...
Click to expand...
Click to collapse
I'm not really bothering with it - it just showed up and started bothering me .
1.Backup everything.
2.Flash 5.1 with nexus root toolkit.
3.Restore all the data.
4.Change your build in NRT to android 5.1
5.Root it and flash TWRP/CWM if you want.
6.?????
7.Profit! duh
neo5468 said:
Just use fastboot and manually flash system.img and boot.img, then format cache. It works every single time, without wiping data and you can easly root it again with CF Auto Root.
Click to expand...
Click to collapse
... or wait for a week until someone will release a rooted 5.1 update
sensboston said:
... or wait for a week until someone will release a rooted 5.1 update
Click to expand...
Click to collapse
Why would you wait a week, we already waited too long for offical 5.1 to come out for our tablet. It is 5minutes of work, works 100% and also fasboot is the safest way to flash. Also you download the image straight from developers.google.com so there is no bs. I much rather flash that. But to each his own.
There is already a recovery flashable "stock rooted 5.1" thanks to scrosler (cleanrom Dev).
5.1 rooted ROM
neo5468 said:
Why would you wait a week
Click to expand...
Click to collapse
Agree, week is too long. A few days - better words And "one click" solution is much better in case of possible mistakes during flashing separate partitions, rooting etc...
neo5468 said:
Just use fastboot and manually flash system.img and boot.img, then format cache. It works every single time, without wiping data and you can easly root it again with CF Auto Root. I don't get it why people bother with OTA all the time. Always issues with them. I just did this and went from 5.0.2 to 5.1 without losing any data, and tablet now really flies. It keeps a lot more apps in RAM, for better multitasking, and I don't experiance any lag what so ever. I strongly recommend everyone to update to 5.1, because it feels like you just got a new tablet. Good job Google !
Click to expand...
Click to collapse
I haven't done this in forever, is it just adb reboot bootloader, then the fastboot commands for flash system.img/boot.img. I have a custom recovery, does that matter?
beall49 said:
I haven't done this in forever, is it just adb reboot bootloader, then the fastboot commands for flash system.img/boot.img. I have a custom recovery, does that matter?
Click to expand...
Click to collapse
Custom recovery is fine. There is also a new boot loader to flash as well I think. You can also run the flash all batch file in the factory image and just remove the -w from it so it doesn't wipe data. But what you posted is also correct, but flash the boot loader too. If your rusty at it just use wugs toolkit, it will run the commands for you.
Solid, removing the -w was what I was forgetting. I knew there was something else.
Thanks!
Well this popped up for me yesterday and I, in a total blonde moment, clicked OK and it promptly crashed my tablet. Which is what is expected to happen being that it was running rooted and non stock recovery.
So yes it was bricked. But is it a Nexus. It was a soft brick and easily fixed with the Nexus Root Toolkit. Which is what I would have done to update it anyway. I don't normally take OTAs. Yes I sinned before the Gods of RomFlashing and paid for it with wasted time. LOL
nlinecomputers said:
Well this popped up for me yesterday and I, in a total blonde moment, clicked OK and it promptly crashed my tablet. Which is what is expected to happen being that it was running rooted and non stock recovery.
So yes it was bricked. But is it a Nexus. It was a soft brick and easily fixed with the Nexus Root Toolkit. Which is what I would have done to update it anyway. I don't normally take OTAs. Yes I sinned before the Gods of RomFlashing and paid for it with wasted time. LOL
Click to expand...
Click to collapse
That's a little odd, usually (since lollipop) it will just fail. Bummer it actually flashed and soft bricked.
madbat99 said:
That's a little odd, usually (since lollipop) it will just fail. Bummer it actually flashed and soft bricked.
Click to expand...
Click to collapse
No big deal really. I don't keep important data on it. It's mostly used for Kindle and games. Easy to fix.
http://www.androidcentral.com/moto-x-2014-updated-fix-stagefright-exploit
"If you happen to be using a Moto X 2014 Pure Edition, you may have an update waiting for you. It appears that Motorola has begun pushing out a patch for the Stagefright exploit, along with some minor bug fixes. Here's the official word on what this update contains:
Closes a potential security vulnerability (Stagefright)
Bug fixes and other stability improvements
It's unclear if this one is landing for everyone at the same time, or if it's a gradual rollout. For what it's worth, however, we had to manually check for the 4.3MB update to pull it down, so that would be your best bet. To do so, head to your Settings menu then go to "About Phone" and tap "System Updates.""
I manually checked, and the update was available for me. Didn't accept it, as I'm not sure if my root and Xposed would be affected.
I received the notification and installed the update without thinking and now my phone is stuck on the bootloader warning screen. I was rooted. Anyone know how I can fix this?
slicck said:
I received the notification and installed the update without thinking and now my phone is stuck on the bootloader warning screen. I was rooted. Anyone know how I can fix this?
Click to expand...
Click to collapse
My suspicion is that just as a full OTA, you need to be stock unrooted.
slicck said:
I received the notification and installed the update without thinking and now my phone is stuck on the bootloader warning screen. I was rooted. Anyone know how I can fix this?
Click to expand...
Click to collapse
I did the same thing and now I have the same problem. This is going to suck majorly if I have to wipe my entire phone now. I haven't backed up in a few weeks. :-/
Any help would be appreciated.
EDIT - To be clear, I'd love to figure out a way to recover this without having to factory wipe the phone. I can get to the recovery window but I don't have TWRP or anything installed, I just had it rooted.
dbrowdy said:
I did the same thing and now I have the same problem. This is going to suck majorly if I have to wipe my entire phone now. I haven't backed up in a few weeks. :-/
Any help would be appreciated.
EDIT - To be clear, I'd love to figure out a way to recover this without having to factory wipe the phone. I can get to the recovery window but I don't have TWRP or anything installed, I just had it rooted.
Click to expand...
Click to collapse
Flash twrp in the bootloader. Backup your data in twrp. Download factory image for your version 5.0, 5.1, etc. from Motorola servers. Flash the system.img and boot.img in the bootloader. Clear the cache and dalvik. Reboot.
Sent from my XT1095 using Tapatalk
kcustom11 said:
Flash twrp in the bootloader. Backup your data in twrp. Download factory image for your version 5.0, 5.1, etc. from Motorola servers. Flash the system.img and boot.img in the bootloader. Clear the cache and dalvik. Reboot.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Awesome, thanks! I had already gotten TWRP reflashed and I was at a loss of where to go from there.
Now I have to wait for someone to approve my download or something. Wonderful. My phone is bricked and I have to wait for someone at Motorola to manually approve me.
Anyone know of a mirror for these files?
dbrowdy said:
Awesome, thanks! I had already gotten TWRP reflashed and I was at a loss of where to go from there.
Now I have to wait for someone to approve my download or something. Wonderful. My phone is bricked and I have to wait for someone at Motorola to manually approve me.
Anyone know of a mirror for these files?
Click to expand...
Click to collapse
Found this post that has the image files. http://forum.xda-developers.com/moto-x-2014/general/5-1-firmwares-t3148211/page9
bostonirishguy13 said:
http://www.androidcentral.com/moto-x-2014-updated-fix-stagefright-exploit
"If you happen to be using a Moto X 2014 Pure Edition, you may have an update waiting for you. It appears that Motorola has begun pushing out a patch for the Stagefright exploit, along with some minor bug fixes. Here's the official word on what this update contains:
Closes a potential security vulnerability (Stagefright)
Bug fixes and other stability improvements
It's unclear if this one is landing for everyone at the same time, or if it's a gradual rollout. For what it's worth, however, we had to manually check for the 4.3MB update to pull it down, so that would be your best bet. To do so, head to your Settings menu then go to "About Phone" and tap "System Updates.""
Click to expand...
Click to collapse
Is there any way to install this as a zip file from TWR?
EDIT: Found it! http://forum.xda-developers.com/showpost.php?p=62902065&postcount=3
Dumb question, but I'll ask anyway if I root will I not be able to receive OTA updates? Because I know whenever I did that with my Note 4 that if I tried it would give a message saying operating system is modified or something in that nature.
joe1blue said:
Dumb question, but I'll ask anyway if I root will I not be able to receive OTA updates? Because I know whenever I did that with my Note 4 that if I tried it would give a message saying operating system is modified or something in that nature.
Click to expand...
Click to collapse
You will not be able to take the ota. You have two options when marshmallow comes out.
1) Use the return to stock tool and take the ota them reroot
2) Wait for a flash able zip to become available.
TrenchKato said:
2) Wait for a flash able zip to become available.
Click to expand...
Click to collapse
Which will most likely be faster available than waiting for the OTA.
I'm not sure that will be the case for the MXPE. Fastboot shows the OS as "original," leading me to believe that OTA updates may work. Remember that on the Note 4, et al, unlocking the bootloader wasn't supported by the OEM or carrier. Since Moto is supplying the unlock codes, I suspect that OTA updates will not be disabled on the MXPE as long as no other OS changes are made. I could be wrong, but we'll find out when the time comes.
Tanker Bob said:
I'm not sure that will be the case for the MXPE. Fastboot shows the OS as "original," leading me to believe that OTA updates may work. Remember that on the Note 4, et al, unlocking the bootloader wasn't supported by the OEM or carrier. Since Moto is supplying the unlock codes, I suspect that OTA updates will not be disabled on the MXPE as long as no other OS changes are made. I could be wrong, but we'll find out when the time comes.
Click to expand...
Click to collapse
Chances are, if you unlocked your bootloader, you flashed a custom recovery. You can't take an OTA through a custom recovery -- not because it's "blocked," but because the OTA tool is not written to work with that recovery.
Could be. Easy enough to fix if so. Just tell TWRP to allow the OS to overwrite it, the reflash TWRP after the update.
Can't you just flash the stock recovery to take the OTA? Sure, you'll lose root, but you could still take the OTA, then flash your custom recovery again. Is there anything, other than a stock recovery, that prevents OTA updates?
I wish we had a release date. Getting excited for the new features. Should have kept my Nexus 5!
jonathanbailie said:
Can't you just flash the stock recovery to take the OTA? Sure, you'll lose root, but you could still take the OTA, then flash your custom recovery again. Is there anything, other than a stock recovery, that prevents OTA updates?
I wish we had a release date. Getting excited for the new features. Should have kept my Nexus 5!
Click to expand...
Click to collapse
A modified system will prevent the install. You would need to flash the system image as well.
Sent from my XT1575 using Tapatalk
I know some owners rooted their device for different reasons other than roms, but imo better to wait for 6.0 for OTA first. This phone comes with pure Android rom. Not like you need to remove bloat apps. Just need custom roms and kernels which is slow developing. Maybe the devs don't want to waste time with lp and their also waiting for marshmallow. I'm surprised how slow this device is moving under development. Oneplus one didn't have mass sale but their development was quick. Being so similar with nexus 6, hopefully we can get some love with MXP.
Sent from my XT1575 using XDA Free mobile app
I have been holding out on unlocking for this reason. I'm lazy and don't want to set everything up again so I will use Marsh to back everything up first then I will go to town
Tanker Bob said:
I'm not sure that will be the case for the MXPE. Fastboot shows the OS as "original," leading me to believe that OTA updates may work.
Click to expand...
Click to collapse
OTA will not work for rooted MXPE's.
1) Rooting the MXPE requires you to load an alternative recovery (TWRP), which doesn't work with the OTA installation scripts.
2) Rooting the MXPE modified /system files. And OTA updates check /system integrity before it runs the update. Rooted phones will fail that integrity check, and will fail to OTA for that reason.
You could restore your MXPE to stock conditions (un-root, and load stock recovery) to have it accept an OTA. I'm sure that most people will do that, and then re-install TWRP and re-root after that is done. However, I'd recommend you wait a bit for other people to try this first, just in case there are any issues and to verify that root is still available in Android Marshmallow 6.0
Makes sense. Somebody has to be first. I will do a nandroid backup before attempting to update by any means.
Prior comments in this thread:
"You will not be able to take the ota. You have two options when marshmallow comes out.
1) Use the return to stock tool..."
and
"You could restore your MXPE to stock conditions (un-root, and load stock recovery) to have it accept an OTA..."
I just wanted to clarify that the Return to Stock tool does not currently remove TWRP...
Factory image will appear here once available: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
(Must log in with Motorola registered ID or gmail address)
Keep in mind you will see a Moto X (2nd Gen) Pure Edition already there...that is not ours.
hijax2001 said:
Prior comments in this thread:
"You will not be able to take the ota. You have two options when marshmallow comes out.
1) Use the return to stock tool..."
and
"You could restore your MXPE to stock conditions (un-root, and load stock recovery) to have it accept an OTA..."
I just wanted to clarify that the Return to Stock tool does not currently remove TWRP...
Factory image will appear here once available: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
(Must log in with Motorola registered ID or gmail address)
Keep in mind you will see a Moto X (2nd Gen) Pure Edition already there...that is not ours.
Click to expand...
Click to collapse
More clarification: Restore-To-Stock-Tool does replace TWRP. Have a gander inside the zip. I spy recovery.img within. What do you see?
PiousInquisitor said:
More clarification: Restore-To-Stock-Tool does replace TWRP. Have a gander inside the zip. I spy recovery.img within. What do you see?
Click to expand...
Click to collapse
Yup, you're correct ... I just used the tool earlier today and I do indeed have stock recovery.
Sent from my XT1575 using Tapatalk
Sharing my experience... good it's supposed to. Didn't for me, for some reason, until 2nd power cycle. It is stock recovery now though. Sorry for the confusion.
I've unlocked the bootloader and installed TWRP on my girlfriend's Moto G5 Plus, but now whenever she tries to take OEM updates, the device reboots into the updating stage and then fails at an image of a dead Android. I'm at work currently without access to the device, but before I get home I was wondering if anyone else has had similar issues or has a resolution to this issue?
Thank you!
Huntereb said:
I've unlocked the bootloader and installed TWRP on my girlfriend's Moto G5 Plus, but now whenever she tries to take OEM updates, the device reboots into the updating stage and then fails at an image of a dead Android. I'm at work currently without access to the device, but before I get home I was wondering if anyone else has had similar issues or has a resolution to this issue?
Thank you!
Click to expand...
Click to collapse
You can't get those automatic updates if you have modified the phone system (e.g. unlock bootloader)... if this is what you mean.
I'm still not very used to moto devices but, from what I've read so far, you have to install updates via fastboot.
luizlee86 said:
You can't get those automatic updates if you have modified the phone system (e.g. unlock bootloader)... if this is what you mean.
I'm still not very used to moto devices but, from what I've read so far, you have to install updates via fastboot.
Click to expand...
Click to collapse
Yes, that's true stuff! Also, you'll keep getting the update notifications. To end that nightmare, you need to purchase the paid version of Titanium Backup and 'freeze' the Motorola Update Service
luizlee86 said:
You can't get those automatic updates if you have modified the phone system (e.g. unlock bootloader)... if this is what you mean.
I'm still not very used to moto devices but, from what I've read so far, you have to install updates via fastboot.
Click to expand...
Click to collapse
djroese33 said:
Yes, that's true stuff! Also, you'll keep getting the update notifications. To end that nightmare, you need to purchase the paid version of Titanium Backup and 'freeze' the Motorola Update Service
Click to expand...
Click to collapse
Dang! That's unfortunate! I might just install a custom rom for her or something, then. Thanks for the information!
Huntereb said:
Dang! That's unfortunate! I might just install a custom rom for her or something, then. Thanks for the information!
Click to expand...
Click to collapse
I may be wrong.. but AFAIK custom roms don't have the one button navigation feature.
I haven't tested on modern phone but i know that if you want to install successfully an OTA update you need: 1) stock recovery (with TWRP it will fail) 2) an untouched system partition (you must install supersu in systemless mode).
Another way is via flashfire from the play store.
Hope this could help you
luizlee86 said:
I may be wrong.. but AFAIK custom roms don't have the one button navigation feature.
Click to expand...
Click to collapse
Yeah, you're wrong
Enviado desde mi XT1681 mediante Tapatalk
Huntereb said:
I've unlocked the bootloader and installed TWRP on my girlfriend's Moto G5 Plus, but now whenever she tries to take OEM updates, the device reboots into the updating stage and then fails at an image of a dead Android. I'm at work currently without access to the device, but before I get home I was wondering if anyone else has had similar issues or has a resolution to this issue?
Thank you!
Click to expand...
Click to collapse
You can still take OEM updates even if you have unlocked your bootloader. Your phone needs to have stock rom and stock recovery. Since you installed TWRP, its failing to update. Flash stock recovery image and you'll be able to update just fine.
luizlee86 said:
I may be wrong.. but AFAIK custom roms don't have the one button navigation feature.
Click to expand...
Click to collapse
Yes it has but that feature no name like onekey navigation....you can set in fingerprint gesture menu whatever you want
I have a general question about updates. On my G5 plus I'm still on the January 1st Android security level. I unlocked my bootloader but kept the recovery and rom stock.
Will I get OTA updates normally and just be able to install them through the OS? Or do I have to find the update online and install via fastboot?
welp11 said:
I have a general question about updates. On my G5 plus I'm still on the January 1st Android security level. I unlocked my bootloader but kept the recovery and rom stock.
Will I get OTA updates normally and just be able to install them through the OS? Or do I have to find the update online and install via fastboot?
Click to expand...
Click to collapse
You will get all updates via OTA:highfive:, the unlock of bootloader won't prevent you to get updates:laugh:
In extrema ratio flash via fastboot but you won't need that:good:
luizlee86 said:
You can't get those automatic updates if you have modified the phone system (e.g. unlock bootloader)... if this is what you mean.
I'm still not very used to moto devices but, from what I've read so far, you have to install updates via fastboot.
Click to expand...
Click to collapse
djroese33 said:
Yes, that's true stuff! Also, you'll keep getting the update notifications. To end that nightmare, you need to purchase the paid version of Titanium Backup and 'freeze' the Motorola Update Service
Click to expand...
Click to collapse
Wait, so if an ota rolls out, it'll fail. But you can manually flash with fastboot. But even after fastboot flashing, it'll still notify you that an update is waiting?? Even if you manually applied that update?
I'd rather not freeze the service as I do want to know when the next ota comes along that I'll want to flash.
Please mirror.
ui_print("Target: motorola/aljeter/aljeter:9/PPP29.41/b1fe5:user/release-keys");
Download
As far as I know, you must be on the Sept. patch. So, you must downgrade firmware first. It also appears to be for the Aljeter only, so I don't know if it'll work on the Jeter.
I am not responsible for any bricked devices.
1. Downgrade to OPP27.91-143 first.
2. Extract gpt_main0.bin from the ota zip and flash it in fastboot.
fastboot flash partition gpt_main0.bin
3. Reboot to recovery, and apply the OTA update from your sdcard.
4. Let the system restart. It'll take about 10min.
Could anyone verify?
Figures it's for Aljeter. Makes me wonder if Jeter will get it at all.
yes it is for aljeter and is working fine
Spaceminer said:
Please mirror.
ui_print("Target: motorola/aljeter/aljeter:9/PPP29.41/b1fe5:user/release-keys");
Download
As far as I know, you must be on the Sept. patch. So, you must downgrade firmware first. It also appears to be for the Aljeter only, so I don't know if it'll work on the Jeter.
These installation steps need confirmation. I am not responsible for any bricked devices.
1. Downgrade to OPP27.91-143 first.
2. Extract gpt_main0.bin from the ota zip and flash it in fastboot.
fastboot flash partition gpt_main0.bin
3. Reboot to recovery, and apply the OTA update from your sdcard.
4. Let the system restart. It'll take about 10min.
Click to expand...
Click to collapse
Tested and working on G6 Play do Brasil!
Up and running in UK. G6 Play XT1922-2, Carrier: ID Mobile (Carphone Warehouse), retgb.
Can't get root though, Magisk won't install for me in TWRP. Unable to mount storage or OEM. Not that fussed about that though.
Butter smooth, no glitches so far, no random reboots, battery life is great but still under observation.
Eddster3000 said:
Up and running in UK. G6 Play XT1922-2, Carrier: ID Mobile (Carphone Warehouse), retgb.
Can't get root though, Magisk won't install for me in TWRP. Unable to mount storage or OEM. Not that fussed about that though.
Butter smooth, no glitches so far, no random reboots, battery life is great but still under observation.
Click to expand...
Click to collapse
That's a Pie/Magisk problem. Easy fix...
1. Format /data in TWRP using the "yes" option. Then reboot directly back into recovery.
2. Mount /vendor then flash the universal dm-verity disabler by zackptg5.
3. Reboot directly into recovery once more and flash Magisk.
4. Reboot normally, and install the Magisk manager app manually. Done.
(Magisk should disable encryption and verity, but I've never had it work %100 of the time for both. Hence the disabler.)
Spaceminer said:
That's a Pie/Magisk problem. Easy fix...
1. Format /data in TWRP using the "yes" option. Then reboot directly back into recovery.
2. Mount /vendor then flash the universal dm-verity disabler by zackptg5.
3. Reboot directly into recovery once more and flash Magisk.
4. Reboot normally, and install the Magisk manager app manually. Done.
(Magisk should disable encryption and verity, but I've never had it work %100 of the time for both. Hence the disabler.)
Click to expand...
Click to collapse
Thanks @Spaceminer !!!! I'll give it a go. I thought at first that I might need to make some sort of patched boot image and faff about quite a bit but your instructions are clear and straightforward.
I must say I'm impressed with the G6 Play. I had a Nexus 6P and a Pixel both of which died on me from physical and customisation fatigue. I could afford a flagship so got this to see be through and I haven't had one complaint yet.
The handful of Pie features and esthetics have been implemented well by Motorola and battery life is still epic on this device.
Edit: rooted and fully set up how I usually have my daily driver handset. Pie is so tasty!
Eddster3000 said:
Up and running in UK. G6 Play XT1922-2, Carrier: ID Mobile (Carphone Warehouse), retgb.
Can't get root though, Magisk won't install for me in TWRP. Unable to mount storage or OEM. Not that fussed about that though.
Butter smooth, no glitches so far, no random reboots, battery life is great but still under observation.
Click to expand...
Click to collapse
Ta for taking the plunge and testing mate! Was beginning to think we'd never get this thing, glad to know it works on the same model number as I've got
Now to figure out the exact detailed step-by-step to getting this going, considering I'm actually on the November update...
picopi said:
Ta for taking the plunge and testing mate! Was beginning to think we'd never get this thing, glad to know it works on the same model number as I've got
Now to figure out the exact detailed step-by-step to getting this going, considering I'm actually on the November update...
Click to expand...
Click to collapse
Op is a step by step. Literally. Downgrade to Sept = Flash the build specified. Except the bootloader etc.
Flash the gpt.bin from the new build, apply update.
madbat99 said:
Op is a step by step. Literally. Downgrade to Sept = Flash the build specified. Except the bootloader etc.
Flash the gpt.bin from the new build, apply update.
Click to expand...
Click to collapse
Well yeah, I know that much. I meant the extra stuff like unlocking bootloader and downgrading the firmware etc lol. Ta for the extra info, mind.
Extra questions though because despite being having novice experience of doing phone flashing stuff, I've never touched a soak test for official firmware before...but I'm guessing I'll have to move back to Oreo temporarily to get the official Pie update...? Or will it just shift up from this soak test version?
Anyone get this working with the xt1922-7?
Donavonn said:
Anyone get this working with the xt1922-7?
Click to expand...
Click to collapse
No dice! The bootloader won't accept the gpt.bin. I think the recovery partition is the only thing that gets expanded though, so... I think if someone makes a back up of Pie in TWRP, then I can make it work on our phone. My idea is this.
1. Restore a Pie system backup using twrp, including the boot.img.
2. Use fastboot to flash the modem, oem.img, and vendor.img. Basically flash every part that isn't a patch file.
3. Hope that crap works.
I think that, or something similar would make it happen. I'll be the lab rat if someone wants to upload a system backup.
Spaceminer said:
No dice! The bootloader won't accept the gpt.bin. I think the recovery partition is the only thing that gets expanded though, so... I think if someone makes a back up of Pie in TWRP, then I can make it work on our phone. My idea is this.
1. Restore a Pie system backup using twrp, including the boot.img.
2. Use fastboot to flash the modem, oem.img, and vendor.img. Basically flash every part that isn't a patch file.
3. Hope that crap works.
I think that, or something similar would make it happen. I'll be the lab rat if someone wants to upload a system backup.
Click to expand...
Click to collapse
Haha yes! Someone get this guy a backup! Also, if it does work, the UI and everything can be changed to English, right?
Okay quick question, considering it was said "Flash the build specified except bootloader etc."; what is meant by "etc" here? Which parts of the older firmware should I avoid flashing. I know I gotta get in on that sparsechunk action but what about the other stuff like fsg, modem, boot etc? Sorry for asking what's probably a very obvious question but I don't wanna accidentally bugger my phone up trying to get this working
Donavonn said:
Haha yes! Someone get this guy a backup! Also, if it does work, the UI and everything can be changed to English, right?
Click to expand...
Click to collapse
Yes, it should be possible on the first setup. I think if it works, LTE probably won't without an APN edit. That's what happens when I flash xt1922-5 RETUS firmware anyways.
picopi said:
Okay quick question, considering it was said "Flash the build specified except bootloader etc."; what is meant by "etc" here? Which parts of the older firmware should I avoid flashing. I know I gotta get in on that sparsechunk action but what about the other stuff like fsg, modem, boot etc? Sorry for asking what's probably a very obvious question but I don't wanna accidentally bugger my phone up trying to get this working
Click to expand...
Click to collapse
Flash every part of the old firmware that you are able to. The bootloader and gpt.bin usually fail to flash if they are older than your current version. You should still try anyways. If they fail, just continue flashing the next items in line.
Spaceminer said:
Flash every part of the old firmware that you are able to. The bootloader and gpt.bin usually fail to flash if they are older than your current version. You should still try anyways. If they fail, just continue flashing the next items in line.
Click to expand...
Click to collapse
Righto. Just to clarify, I'm gonna need to unlock my bootloader to make this downgrade happen, right?
picopi said:
Righto. Just to clarify, I'm gonna need to unlock my bootloader to make this downgrade happen, right?
Click to expand...
Click to collapse
Official firmware should flash without any issue on a locked bootloader. That's my understanding. I don't know if this is %100 accurate. Every Motorola I've ever had, I unlocked the bootloader immediately. So, I've never had to test this.
Spaceminer said:
Official firmware should flash without any issue on a locked bootloader. That's my understanding. I don't know if this is %100 accurate. Every Motorola I've ever had, I unlocked the bootloader immediately. So, I've never had to test this.
Click to expand...
Click to collapse
Righto. In that case I'll report back with my findings, but yeah I'd imagine it should work fine as well. We'll see, fingers crossed.