Database Users

Monthly OTA updates from Google

This is new: http://www.androidpolice.com/2015/08/05/google-announces-new-update-policy-for-nexus-devices-including-monthly-security-patches-for-3-years-and-major-otas-for-2-years-from-release/
That would be a real pain for us rooted users....but I guess the security patches are a good thing

A real pain...
Sent from another Nexus..
6...

No pain, it literally takes minutes to flash stock, update, root using the toolkit. [emoji1]

I wonder if there are again going to be separate builds for each carrier.

meldroc said:
I wonder if there are again going to be separate builds for each carrier.
Click to expand...
Click to collapse
That's a good point...maybe?

I wish there was an app for rooted users to get notifications about these updates (and maybe offer a way to download a flashable zip as well?)
I got a Nexus 6 because I wanted to be able to always have access to a stable, current version of Android. I didn't realize that OTA updates wouldn't work out of the box with rooted devices though.
Would be nice to have some method to get back that functionality!

ArmoredCavalry said:
I wish there was an app for rooted users to get notifications about these updates (and maybe offer a way to download a flashable zip as well?)
I got a Nexus 6 because I wanted to be able to always have access to a stable, current version of Android. I didn't realize that OTA updates wouldn't work out of the box with rooted devices though.
Would be nice to have some method to get back that functionality!
Click to expand...
Click to collapse
There is, stay stock or learn how to manually update to new versions. It's quick to do.

Xplicit84 said:
There is, stay stock or learn how to manually update to new versions. It's quick to do.
Click to expand...
Click to collapse
Both those things ignore the whole point of what I brought up.
I'm saying it would be nice if there was an equivalent automatic notification/update process for rooted users.

ArmoredCavalry said:
Both those things ignore the whole point of what I brought up.
I'm saying it would be nice if there was an equivalent automatic notification/update process for rooted users.
Click to expand...
Click to collapse
That is the equivalent. Stay stock or manually update. Rooted users don't worry about such a thing, since changing ROMs and adding various features are a common occurrence.

Xplicit84 said:
That is the equivalent. Stay stock or manually update. Rooted users don't worry about such a thing, since changing ROMs and adding various features are a common occurrence.
Click to expand...
Click to collapse
Rooted users don't care about convenience? I dunno about you, but I'm rooted, and I still would prefer to do repetitive/manual processes as little as possible...
You can be a rooted user just to use rooted apps, and not care about trying a different ROM every week. In which case, it would be nice to have the same benefits of automatic updates as stock users. Not sure why you seem to be against the idea?
I get that you think it is unnecessary, but I'm saying I would prefer it as an option. So, maybe we can just leave it at that?

ArmoredCavalry said:
Rooted users don't care about convenience? I dunno about you, but I'm rooted, and I still would prefer to do repetitive/manual processes as little as possible...
You can be a rooted user just to use rooted apps, and not care about trying a different ROM every week. In which case, it would be nice to have the same benefits of automatic updates as stock users. Not sure why you seem to be against the idea?
I get that you think it is unnecessary, but I'm saying I would prefer it as an option. So, maybe we can just leave it at that?
Click to expand...
Click to collapse
I would also like that if it was possible...

It is possible. Get notification from XDA users down load ota file someone has probably posted someplace plug in to computer and side load. It usually 1 week faster than waiting your turn to receive ota from carrier's

hdtechk said:
It is possible. Get notification from XDA users down load ota file someone has probably posted someplace plug in to computer and side load. It usually 1 week faster than waiting your turn to receive ota from carrier's
Click to expand...
Click to collapse
and that's exactly what I am going to do...

hdtechk said:
It is possible. Get notification from XDA users down load ota file someone has probably posted someplace plug in to computer and side load. It usually 1 week faster than waiting your turn to receive ota from carrier's
Click to expand...
Click to collapse
I don't think this will work. If your N6 is rooted, you can't sideload the OTA file. Your phone will need to be stock (unrooted) to apply the OTA.
You could wait for somebody to publish a flashable zip, or just download the new factory images and use fastboot to flash the new system.img over your existing phone, and reroot.

jj14 said:
You could wait for somebody to publish a flashable zip, or just download the new factory images and use fastboot to flash the new system.img over your existing phone, and reroot.
Click to expand...
Click to collapse
Isn't there a chance of losing the ability to reroot with this method though? I've been waiting for users to publish flashable zips for this reason, but maybe that is not necessary?

ArmoredCavalry said:
Isn't there a chance of losing the ability to reroot with this method though? I've been waiting for users to publish flashable zips for this reason, but maybe that is not necessary?
Click to expand...
Click to collapse
Is there a chance that google will publish a new Nexus factory image that can't be rooted? Sure - in theory, that is possible. But unlikely.
Till date, all nexus devices have been rooted (thanks @Chainfire)

jj14 said:
. . . Your phone will need to be stock (unrooted) to apply the OTA.
. . . use fastboot to flash the new system.img over your existing phone, and reroot.
Click to expand...
Click to collapse
Recently I used both methods just to see if there were differences.
Both had the same results. That means among others that my settings were gone.
- LCD_density defaults (384)
- WiFi interval defaults (was 200)
- Needed to flash Black Google Now Launcher and uninstall Google.app updates to get my black background back.
When this happens every month . . . [email protected]#$%&

jj14 said:
I don't think this will work. If your N6 is rooted, you can't sideload the OTA file. Your phone will need to be stock (unrooted) to apply the OTA.
You could wait for somebody to publish a flashable zip, or just download the new factory images and use fastboot to flash the new system.img over your existing phone, and reroot.
Click to expand...
Click to collapse
When you flash a new factory image I'm assuming you flash each partition and avoid flashing the data partition (dirty flash) ?
Does google always post a whole new image for each ota? What about the carrier variants like tmobile? Is there a new image for each ota?
Thanks. I'm not a N6 owner yet but I plan to be stock rooted and am trying to determine the ota update process in advance.

@NCguy
"When you flash a new factory image I'm assuming you flash each partition and avoid flashing the data partition (dirty flash) ?" Correct
Does google always post a whole new image for each ota?" Yes
"What about the carrier variants like tmobile? Is there a new image for each ota?" There has been a T-Mobile specific factory image for each OTA.
Here are the factory images > https://developers.google.com/android/nexus/images

cam30era said:
@NCguy
"When you flash a new factory image I'm assuming you flash each partition and avoid flashing the data partition (dirty flash) ?" Correct
Does google always post a whole new image for each ota?" Yes
"What about the carrier variants like tmobile? Is there a new image for each ota?" There has been a T-Mobile specific factory image for each OTA.
Here are the factory images > https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Thanks cam30era. I was a bit concerned that being a stock rooted device might be too much trouble, especially with the security updates. But this looks manageable to me.

MDB08M is up

https://developers.google.com/android/nexus/images?hl=en

I haven't even gotten MDB08L via OTA yet. Has anyone else gotten either of the two?

I'm still on MDB08I too. Went through the "about phone" to check for an update and it says there isn't one. Don't really want to flash this seeing as i'm not rooted or unlocked.

Very strange that they'd release two images simultaneously. Can't recall seeing something like this before.

I think MDB08x is just carrier specific I I got notified for mdb08i when I first booted the phone up with no sim. After I put my verizon sim in, it said I was up to date. But when I put a tmobile sim in and right away prompted me to update.

FYI
MDB08M uses MDB08I boot image, so feel free to flash and root.

k.s.deviate said:
FYI
MDB08M uses MDB08I boot image, so feel free to flash and root.
Click to expand...
Click to collapse
Hi - I may be misinterpreting, but when I look at the boot.img files in the two system images with 7zip, the CRCs are different. Doesn't that mean they're not the same? Just don't want to bork my phone! Thanks.

sgravel said:
Hi - I may be misinterpreting, but when I look at the boot.img files in the two system images with 7zip, the CRCs are different. Doesn't that mean they're not the same? Just don't want to bork my phone! Thanks.
Click to expand...
Click to collapse
I see the same thing, but I reflashed the "systemless" rooted boot image and it booted up just fine. Differences are minimal, I guess?

I can't seem to find the changelogs for the factory images. I'm I just missing it or is it hidden somewhere?
Thanks!

jm.kloz said:
I can't seem to find the changelogs for the factory images. I'm I just missing it or is it hidden somewhere?
Thanks!
Click to expand...
Click to collapse
https://groups.google.com/forum/#!msg/android-security-updates/n1aw2MGce4E/jhpVEWDUCAAJ

k.s.deviate said:
FYI
MDB08M uses MDB08I boot image, so feel free to flash and root.
Click to expand...
Click to collapse
delete

To restate, I'm running the MDB08M build. And I'm rooted.
I used the systemless bullhead boot.img from http://forum.xda-developers.com/showpost.php?p=63197935&postcount=2
I did however use the factory image script to wipe the phone clean when I flashed it. That was the only vaguely strange thing I did.
Not noticed any strange behaviour, but this phone isn't my daily driver yet.
Added some screengrabs

Is the update file available anywhere so you can update without a data wipe? New to the nexus world.
Sent from my Nexus 5X using Tapatalk

adrialk said:
Is the update file available anywhere so you can update without a data wipe?
Click to expand...
Click to collapse
I haven't found an OTA zip link yet, but I'm sure they'll come. What I don't get it why Google doesn't post the OTA links themselves.

adrialk said:
Is the update file available anywhere so you can update without a data wipe? New to the nexus world.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
If your bootloader is already unlocked, yes by flashing the factory image's system.img manually. If not unlocking the bootloader would trigger a wipe.
You'll be able to adb sideload once someone captures an OTA for it, but in theory the OTA should start rolling out to everyone gradually.

If my bootloader is unlocked is it impossible to accept an ota update? The only other nexus I messed with is my mom's N7 2013 and it's a royal pain to install updates on it. Have to manually do everything to save the data.

Unlocked bootloader has no effect on ota update.
Sent from my Nexus 5X using Tapatalk

Looks like the change logs have been posted
MDB08L is the Security Update and MDB08M is the WLAN patch below.
https://android.googlesource.com/platform/hardware/broadcom/wlan/+/25e0325

Anyone still on mda89e? Got the phone on Friday, manufacture date Oct. On Verizon and still says I'm up to date.
Only thing I've done is unlocked bootloader. Haven't flashed a modified boot.img or put a custom recovery.

antiseen said:
Anyone still on mda89e? Got the phone on Friday, manufacture date Oct. On Verizon and still says I'm up to date.
Only thing I've done is unlocked bootloader. Haven't flashed a modified boot.img or put a custom recovery.
Click to expand...
Click to collapse
Im on Verizon and still on MDA89E. Im still completely stock. Im reading up on bootloader unlock, recovery and root so I dont EFF anything up

How do I update to the march patch with twrp installed?

When I got my phone last month, I unlocked the bootloader and installed TWRP. I just got the march OTA and it will not update. It just boots into TWRP and doesnt update. How do I update to the newest patch?

UntamedTyrant said:
When I got my phone last month, I unlocked the bootloader and installed TWRP. I just got the march OTA and it will not update. It just boots into TWRP and doesnt update. How do I update to the newest patch?
Click to expand...
Click to collapse
I'd assume that you have to manually flash it with the zip. I'm not sure how it is with a 6p, but with my Oneplus devices that's how it worked.

UntamedTyrant said:
When I got my phone last month, I unlocked the bootloader and installed TWRP. I just got the march OTA and it will not update. It just boots into TWRP and doesnt update. How do I update to the newest patch?
Click to expand...
Click to collapse
You can't flash an OTA with TWRP, and you can't take an OTA if you have root/modifications. If you've never rooted or modified in any way you should be able to just flash the stock recovery back and then initiate the OTA process. If you do have root you need to flash the factory images to update. See my guide for details:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928

Sr Vincenzo said:
I'd assume that you have to manually flash it with the zip. I'm not sure how it is with a 6p, but with my Oneplus devices that's how it worked.
Click to expand...
Click to collapse
This is why it's best to stick to giving advice for devices that you own and are familiar with.

Heisenberg said:
This is why it's best to stick to giving advice for devices that you own and are familiar with.
Click to expand...
Click to collapse
I understand that. However it was just an assumption, i never said it would actually work. I'm still trying to learn this device myself as it is my first and only Nexus.

Sr Vincenzo said:
I understand that. However it was just an assumption, i never said it would actually work. I'm still trying to learn this device myself as it is my first and only Nexus.
Click to expand...
Click to collapse
Ok, but you need to realise that people could still try whatever you're assuming and posting here. If what you're posting is incorrect, it could cause major problems for them. What I'm saying is this: do your learning for this device first, and then advise people one you know the information you're giving is solid.

Heisenberg said:
Ok, but you need to realise that people could still try whatever you're assuming and posting here. If what you're posting is incorrect, it could cause major problems for them. What I'm saying is this: do your learning for this device first, and then advise people one you know the information you're giving is solid.
Click to expand...
Click to collapse
Alright man...

Some people should never unlock their bootloader or root their phone.

UntamedTyrant said:
When I got my phone last month, I unlocked the bootloader and installed TWRP. I just got the march OTA and it will not update. It just boots into TWRP and doesnt update. How do I update to the newest patch?
Click to expand...
Click to collapse
I used Heisenberg's method yesterday and it worked well. If you copy the commands into notepad, edit them so the file paths and build numbers are correct you can just copy/paste into the command prompt. All settings will be saved with the exception of a couple of widgets I had to redo.
I will say with the latest update the device seems faster so I feel like it is worth it.

Panic - plz help! applied the wrong ota file from adb by mistake, now bootloop

I applied the wrong ota file by mistake and now the phone is stuck in bootloop.
phone is unlocked and "fastboot flashing unlock" won't work as unlocking was disabled in developer options.
Factory reset didn't work. Further, getting the Google's device corrupted message during the bootloop.
Any solutions?

sumit29 said:
I applied the wrong ota file by mistake and now the phone is stuck in bootloop.
phone is unlocked and "fastboot flashing unlock" won't work as unlocking was disabled in developer options.
Factory reset didn't work. Further, getting the Google's device corrupted message during the bootloop.
Any solutions?
Click to expand...
Click to collapse
You can use adb sideload to install one of the new full OTA files with the stock recovery, I have instructions in my guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
These full OTA zips don't require a certain preceding build number to be installed prior to installation.

Heisenberg said:
You can use adb sideload to install one of the new full OTA files with the stock recovery, I have instructions in my guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
These full OTA zips don't require a certain preceding build number to be installed prior to installation.
Click to expand...
Click to collapse
Is it possible to downgrade to an older OTA? I received DP3, got a bootloop. Tried sideloading, wiping, nothing solved.
I´m trying to sideload DP2 but it gives me this error:
Cant install this package over newer build
E: error in /sideload/package.zip (Status 7)

gasparzim said:
Is it possible to downgrade to an older OTA? I received DP3, got a bootloop. Tried sideloading, wiping, nothing solved.
I´m trying to sideload DP2 but it gives me this error:
Cant install this package over newer build
E: error in /sideload/package.zip (Status 7)
Click to expand...
Click to collapse
No, as per the instructions in my guide you can only install a newer build. I wasn't aware that full OTA zips were even available for the Developer Previews.

Heisenberg said:
You can use adb sideload to install one of the new full OTA files with the stock recovery, I have instructions in my guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
These full OTA zips don't require a certain preceding build number to be installed prior to installation.
Click to expand...
Click to collapse
Have already tried doing this...this also gets interrupted mid-way, with the command terminal showing - "connection reset by peer". these are the same OTA files available on the google developers website.

and for some reason, it worked this time around!!!

Heisenberg said:
You can use adb sideload to install one of the new full OTA files with the stock recovery, I have instructions in my guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
These full OTA zips don't require a certain preceding build number to be installed prior to installation.
Click to expand...
Click to collapse
hey can you help me please? i was on marshamllow and yesterday when the android n beta came i installed it through ota update. after it installed and started booting up for the first time it does not boot up. the android boot animation keeps on going for hours. i tried wiping cache and doing factory reset to but its still the same. i cant flash stock image since i didnt enable oem unlocking.

Ame123 said:
hey can you help me please? i was on marshamllow and yesterday when the android n beta came i installed it through ota update. after it installed and started booting up for the first time it does not boot up. the android boot animation keeps on going for hours. i tried wiping cache and doing factory reset to but its still the same. i cant flash stock image since i didnt enable oem unlocking.
Click to expand...
Click to collapse
Same problem have you been able to sort it out yet?

Ame123 said:
hey can you help me please? i was on marshamllow and yesterday when the android n beta came i installed it through ota update. after it installed and started booting up for the first time it does not boot up. the android boot animation keeps on going for hours. i tried wiping cache and doing factory reset to but its still the same. i cant flash stock image since i didnt enable oem unlocking.
Click to expand...
Click to collapse
AlfexOmega said:
Same problem have you been able to sort it out yet?
Click to expand...
Click to collapse
I don't know what you can do, sorry. I'm not sure why you wouldn't just unlock your bootloader and leave it unlocked, that alone would mean you could fix this issue in a matter of minutes. I know me saying this is of no use to you right now, but hopefully it'll impress on you (and anyone reading) the importance of having a fail-safe when things go sideways like this.

Heisenberg said:
I don't know what you can do, sorry. I'm not sure why you wouldn't just unlock your bootloader and leave it unlocked, that alone would mean you could fix this issue in a matter of minutes. I know me saying this is of no use to you right now, but hopefully it'll impress on you (and anyone reading) the importance of having a fail-safe when things go sideways like this.
Click to expand...
Click to collapse
i did not think that the update will break the device and since i didnt wish to unlock the bootloader as all my data could have gone. do you know where i can report to google so that they an fix this issue in next ota update?
---------- Post added at 02:50 PM ---------- Previous post was at 02:50 PM ----------
AlfexOmega said:
Same problem have you been able to sort it out yet?
Click to expand...
Click to collapse
no.:crying::crying:

Ame123 said:
i did not think that the update will break the device and since i didnt wish to unlock the bootloader as all my data could have gone. do you know where i can report to google so that they an fix this issue in next ota update?
---------- Post added at 02:50 PM ---------- Previous post was at 02:50 PM ----------
no.:crying::crying:
Click to expand...
Click to collapse
An update failing is the single most likely cause of a problem like this. The issue here isn't with the update itself, otherwise pretty much every other user taking the update would be experiencing the same thing. There could be any number of reasons for this update going badly for you.
If you had researched you would have known that you need to unlock the bootloader when you first get the device, before you commit too much data to it. Either that or just back up your personal data, unlock the bootloader and then copy your data back. Surely even that is a better option that being stuck in a situation like this where you essentially have a brick.
All you can do now is contact Google support, explain what has happened, and ship it off to them to have it fixed. You shouldn't have to pay if it genuinely wasn't your fault. And remember to unlock your bootloader when you get it back.

Heisenberg said:
An update failing is the single most likely cause of a problem like this. The issue here isn't with the update itself, otherwise pretty much every other user taking the update would be experiencing the same thing. There could be any number of reasons for this update going badly for you.
If you had researched you would have known that you need to unlock the bootloader when you first get the device, before you commit too much data to it. Either that or just back up your personal data, unlock the bootloader and then copy your data back. Surely even that is a better option that being stuck in a situation like this where you essentially have a brick.
All you can do now is contact Google support, explain what has happened, and ship it off to them to have it fixed. You shouldn't have to pay if it genuinely wasn't your fault. And remember to unlock your bootloader when you get it back.
Click to expand...
Click to collapse
the place where i stay does not have any support so that i can ship to them. i bought the device from uk but now i stay in UAE. I dont know what to do now:crying::crying: . Also there are many such cases on xda having the same issue.

Ame123 said:
i did not think that the update will break the device and since i didnt wish to unlock the bootloader as all my data could have gone. do you know where i can report to google so that they an fix this issue in next ota update?
---------- Post added at 02:50 PM ---------- Previous post was at 02:50 PM ----------
no.:crying::crying:
Click to expand...
Click to collapse
Mine is also still messed up I'm calling the store where I bought it to see if they can do anything highly doubt they will though

Ame123 said:
the place where i stay does not have any support so that i can ship to them. i bought the device from uk but now i stay in UAE. I dont know what to do now:crying::crying: . Also there are many such cases on xda having the same issue.
Click to expand...
Click to collapse
Oh, that is not a good situation at all. You might need to find a good repairer in your area and pay for them to fix it for you.

Heisenberg said:
Oh, that is not a good situation at all. You might need to find a good repairer in your area and pay for them to fix it for you.
Click to expand...
Click to collapse
I've heard that it's basically unrepairable.. As there is literally no way to flash android again without an unlocked bootloader and with OEM unlocking disabled

AlfexOmega said:
I've heard that it's basically unrepairable.. As there is literally no way to flash android again without an unlocked bootloader and with OEM unlocking disabled
Click to expand...
Click to collapse
An accredited repair centre should have access to software tools that can do it.

AlfexOmega said:
I've heard that it's basically unrepairable.. As there is literally no way to flash android again without an unlocked bootloader and with OEM unlocking disabled
Click to expand...
Click to collapse
ADB Sideload the developer 3 preview 3 like the other user successfully did.
Sent from my Nexus 5X using Tapatalk

SlimSnoopOS said:
ADB Sideload the developer 3 preview 3 like the other user successfully did.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
did not understood what you said. can you explain a little bit more?

Heisenberg said:
You can use adb sideload to install one of the new full OTA files with the stock recovery, I have instructions in my guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
These full OTA zips don't require a certain preceding build number to be installed prior to installation.
Click to expand...
Click to collapse
Ame123 said:
did not understood what you said. can you explain a little bit more?
Click to expand...
Click to collapse
Sure, see the above post.
Sent from my Nexus 5X using Tapatalk

SlimSnoopOS said:
Sure, see the above post.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I've tried sideloading multiple times and they succeeded however my phone is still not booting :/

G6 Play: Pie Soak Test

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.