Database Users

Android Nougat is coming to the M9 sometime in the "far" Future

Lets see if it comes faster to our Device then Marshmellow...after Google released it to the Manufactures.
And it comes as it seems just to three Devices. (A9,M9, HTC 10)

I just got a OTA message to move from 3.39.531.7 to 3.39.531.12 I'm with T-MO and have it rooted with Teamwin recovery 2.8.7.1_CPTB-B1 on 6.0 Marshmallow
I just wish I knew how to do the upgrade all I do is go round and round, when I tell it to update it boots into the TRWP mentioned above and I have no idea what to do next.
guess I will wait until the smart people figure it out

rtoledo2002 said:
I just got a OTA message to move from 3.39.531.7 to 3.39.531.12 I'm with T-MO and have it rooted with Teamwin recovery 2.8.7.1_CPTB-B1 on 6.0 Marshmallow
I just wish I knew how to do the upgrade all I do is go round and round, when I tell it to update it boots into the TRWP mentioned above and I have no idea what to do next.
guess I will wait until the smart people figure it out
Click to expand...
Click to collapse
You can't install OTAs with a custom recovery. You'll need to flash the stock recovery first and try again.

Got that system security OTA notification as well today. I'm using the stock ROM with root (SuperSU flashed via TWRP). Can I stay rooted to apply the OTA with the stock recovery or do I have to flash the RUU first?
Solved:
Make a backup with Titanium or however you like. Save all your data from internal SD. Afterwards apply latest RUU.exe from HTC (depending on your carrier). If you wanna reroot, I would suggest SuperSU 2.65, because newer versions end up in bootloops.

Don't expect Nougat this year...

It's the August security update
Sent from my HTC One M9 using Tapatalk

hope this year released

matmaneyre said:
You can't install OTAs with a custom recovery. You'll need to flash the stock recovery first and try again.
Click to expand...
Click to collapse
Do you have 3.39.531.12 stock recovery??

missicolin said:
Do you have 3.39.531.12 stock recovery??
Click to expand...
Click to collapse
If you are flashing from 3.39.531.7 to .12 then you need the stock recovery from 3.39.531.7 to be installed.
If you've already flashed a custom recovery like TWRP, then just pull down the RUU from HTC's Web site. Be warned, however, that it will wipe the phone back to factory-fresh, so back up all your files/data/photos/music etc. and remove the SD card just to be safe.
RUU 531.12 T-Mobile
And to answer your specific question, I don't have the stock recovery for 531.12, but I presume that I will later today after I RUU my own device. I don't know how to archive the stock recovery but I plan to flash over it immediately with TWRP.

Amishrabbit said:
If you are flashing from 3.39.531.7 to .12 then you need the stock recovery from 3.39.531.7 to be installed.
If you've already flashed a custom recovery like TWRP, then just pull down the RUU from HTC's Web site. Be warned, however, that it will wipe the phone back to factory-fresh, so back up all your files/data/photos/music etc. and remove the SD card just to be safe.
RUU 531.12 T-Mobile
And to answer your specific question, I don't have the stock recovery for 531.12, but I presume that I will later today after I RUU my own device. I don't know how to archive the stock recovery but I plan to flash over it immediately with TWRP.
Click to expand...
Click to collapse
Is it okay if i flash the RUU with unlocked bootloader or do i need to relock it?

any news on Android N at least not official

drakeNas said:
Is it okay if i flash the RUU with unlocked bootloader or do i need to relock it?
Click to expand...
Click to collapse
you should
" fastboot oem lock "
to relock your bootloader - remeber - to save alll yor apps / settings (via TitaniumBackup for exaple) before
(re) unlocking bootlader will wipe all data
...

rtoledo2002 said:
I just got a OTA message to move from 3.39.531.7 to 3.39.531.12 I'm with T-MO and have it rooted with Teamwin recovery 2.8.7.1_CPTB-B1 on 6.0 Marshmallow
I just wish I knew how to do the upgrade all I do is go round and round, when I tell it to update it boots into the TRWP mentioned above and I have no idea what to do next.
guess I will wait until the smart people figure it out
Click to expand...
Click to collapse
I just got a OTA message and doing the upgrade to 3.39.531.21 will let you all know how it goes.
since I had TWRP installed , I had to download the RUU from HTC to do the first update to .12 , it went well 2 weeks ago when I first posted here, except it wiped out TWRP. then 3 days ago my phone started complaining , when ever I tried to change permissions on apps , with a message telling me to turn off draw over on the apps, all the searches on google, sent me to people telling me it was Twighlight causing the problem , EXCEPT I don't have that app installed, then it said something about turning off sidekeyborad? I never found it, I hard reset the phone, and as usual it ruined some of my contacts ?? I always loose 5 people I call all the time.
will post in here what new bugs crop up with this PART 2 upgrade of 7.0 nougat 63 things updating now
adios :cyclops:

rtoledo2002 said:
I just got a OTA message and doing the upgrade to 3.39.531.21 will let you all know how it goes.
since I had TWRP installed , I had to download the RUU from HTC to do the first update to .12 , it went well 2 weeks ago when I first posted here, except it wiped out TWRP. then 3 days ago my phone started complaining , when ever I tried to change permissions on apps , with a message telling me to turn off draw over on the apps, all the searches on google, sent me to people telling me it was Twighlight causing the problem , EXCEPT I don't have that app installed, then it said something about turning off sidekeyborad? I never found it, I hard reset the phone, and as usual it ruined some of my contacts ?? I always loose 5 people I call all the time.
will post in here what new bugs crop up with this PART 2 upgrade of 7.0 nougat 63 things updating now
adios :cyclops:
Click to expand...
Click to collapse
here is a screen shot

rtoledo2002 said:
then 3 days ago my phone started complaining , when ever I tried to change permissions on apps , with a message telling me to turn off draw over on the apps, all the searches on google, sent me to people telling me it was Twighlight causing the problem , EXCEPT I don't have that app installed, then it said something about turning off sidekeyborad? I never found it, I hard reset the phone, and as usual it ruined some of my contacts ??
Click to expand...
Click to collapse
That's not a bug but a security feature introduced by google. It's meant to prevent malicious apps from making you accept things/permissions you don't want (keyword: tapjacking). Go to settings > app > open the three dot menu > configure apps > draw over other apps. There you can revoke that permission from any suspicious app.
There is an article about tapjacking on the xda portal if anyone wants more information. It's called "How tapjacking made a return with android marshmallow - and nobody noticed". Btw, the article explains why the security feature isn't perfect, too. (Using xda labs at the moment I can't add a direct link to the article. However google should be able to find it.)

I just hope for the classic Non-GP Sense UI. The one with the Grid View Recent Apps.
HTC One M9 is the last chance for the full Sense experience on Nougat, because is the last Non-GP HTC that is being updated.

Rollout started
rhisendark said:
any news on Android N at least not official
Click to expand...
Click to collapse
Read that Rollout started in America for Brand free devices

HTC root mobiles cannot install OTA, RUU are only way when rooted

drakeNas said:
Is it okay if i flash the RUU with unlocked bootloader or do i need to relock it?
Click to expand...
Click to collapse
Yeah you only need to flasb the RUU it would solve your problem

Can't take OEM updates after unlocking bootloader and installing TWRP

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.

Back to Stock with Oreo possible?

Hello my friends.
I bought my U Ultra in December 2017.
Now I decided to flash LeeDroid Oreo on my phone.
It works great.
I backed up in TWRP the parititions "System Image" and "System" in case for going back.
Now my question.
Is it possible to go for going to stock when I recover it all?
Can I lock the bootloader after that?
How to use the "System Image" partition? Can I fully flash my phone to stock with it? With Recovery and so on, because there is no RUU available for me?
My System Version was 2.21.401.1 and my region is Europe/Germany.
Regards

inFiniTyz_Z said:
I backed up in TWRP the parititions "System Image" and "System" in case for going back.
Is it possible to go for going to stock when I recover it all?
How to use the "System Image" partition? Can I fully flash my phone to stock with it? With Recovery and so on, because there is no RUU available for me?
Click to expand...
Click to collapse
If you have TWRP backup you simply recover the backup, wipe data and you are back to stock-ish. Naturally due to lack of original recovery you won't be able to receive/flash OTA. For HTC you simply do not exist.
inFiniTyz_Z said:
Can I lock the bootloader after that?
Click to expand...
Click to collapse
Kind of. You can make OEM lock but it won't be the factory lock. It will be relock. And if you have a custom ROM at that point the phone may not let you boot up.

QDT said:
If you have TWRP backup you simply recover the backup, wipe data and you are back to stock-ish. Naturally due to lack of original recovery you won't be able to receive/flash OTA. For HTC you simply do not exist.
Click to expand...
Click to collapse
In case when I flash the stock recovery too?

inFiniTyz_Z said:
In case when I flash the stock recovery too?
Click to expand...
Click to collapse
If you restore whole system then you will get the OTAs. (This is how I upgraded to Oreo in the first place).
Problem is with TWRP/custom recovery not being capable of performing the factory update (people are soft-bricking their phones).

QDT said:
If you restore whole system then you will get the OTAs. (This is how I upgraded to Oreo in the first place).
Problem is with TWRP/custom recovery not being capable of performing the factory update (people are soft-bricking their phones).
Click to expand...
Click to collapse
When I flash the RUU for my CID from nougat to my phone, and perform an upgrade to oreo, would it result in a hard brick?

inFiniTyz_Z said:
When I flash the RUU for my CID from nougat to my phone, and perform an upgrade to oreo, would it result in a hard brick?
Click to expand...
Click to collapse
There is a topic explaining how to recover first to Nougat and then let you phone receive OTA for Oreo.
I don't know from where you can get RUU for your CID. Keep in mind it has to be the version you have or newer if you are not going to unlock the bootloader and use 3rd party tools to trick force update.

QDT said:
There is a topic explaining how to recover first to Nougat and then let you phone receive OTA for Oreo.
I don't know from where you can get RUU for your CID. Keep in mind it has to be the version you have or newer if you are not going to unlock the bootloader and use 3rd party tools to trick force update.
Click to expand...
Click to collapse
I have the ROM for my CID.
But I would know if it works without hard brick.
I am little bit afraid from it, because I tried this two years ago on my Motorola Moto G2. For one, two, times it worked, then came marshmallow with a new bootloader, so you bricked this phone like ****.

inFiniTyz_Z said:
I have the ROM for my CID.
But I would know if it works without hard brick.
I am little bit afraid from it, because I tried this two years ago on my Motorola Moto G2. For one, two, times it worked, then came marshmallow with a new bootloader, so you bricked this phone like ****.
Click to expand...
Click to collapse
I cannot give you the guarantee. It is for you to decide. The topic explains it really good. I did it several times and no sweat at all. Other ways I don't know.

QDT said:
I cannot give you the guarantee. It is for you to decide. The topic explains it really good. I did it several times and no sweat at all. Other ways I don't know.
Click to expand...
Click to collapse
And I can downgrade to nougat and upgrade with OTA to oreo without hard brick? Did you tried that?

inFiniTyz_Z said:
And I can downgrade to nougat and upgrade with OTA to oreo without hard brick? Did you tried that?
Click to expand...
Click to collapse
Yes, I did that. I went through the described procedure and restored the phone to pristine Nougat and then let it to update via OTA to Oreo.
If your phone is s-on then there hardly any chance you will hard brick it. Soft bricks can happen, naturally. But then, dependently on the case, you can recover from it by reflash, wipe or making the downgrade again via RUU.
One important key combination you have to keep in mind. By pressing (and holding) power with volume down you will see the buttons flashing. Keeping them pressed for ca. 15 sec (shorter, longer depends) forces the phone to reboot.
Good luck.

QDT said:
Yes, I did that. I went through the described procedure and restored the phone to pristine Nougat and then let it to update via OTA to Oreo.
If your phone is s-on then there hardly any chance you will hard brick it. Soft bricks can happen, naturally. But then, dependently on the case, you can recover from it by reflash, wipe or making the downgrade again via RUU.
One important key combination you have to keep in mind. By pressing (and holding) power with volume down you will see the buttons flashing. Keeping them pressed for ca. 15 sec (shorter, longer depends) forces the phone to reboot.
Good luck.
Click to expand...
Click to collapse
It worked. After my question I did the procedure and upgraded to oreo!
Thank you.
No Brick, but I had to erase the data and cache partition again after the first start, because it stucked at the HTC Logo after booting.
But the funfact is: I wanted to do a hard reset after my first try to boot it up, and the phone did a screenshot with the logo!

inFiniTyz_Z said:
It worked. After my question I did the procedure and upgraded to oreo!
Thank you.
No Brick, but I had to erase the data and cache partition again after the first start, because it stucked at the HTC Logo after booting.
But the funfact is: I wanted to do a hard reset after my first try to boot it up, and the phone did a screenshot with the logo!
Click to expand...
Click to collapse
Good. Have fun with the phone. It is quite nice piece of hardware. I like it.

QDT said:
Good. Have fun with the phone. It is quite nice piece of hardware. I like it.
Click to expand...
Click to collapse
Thanks. You too!
And the software status is currently still on modified. Would it change when I lock the bootloader?

inFiniTyz_Z said:
Thanks. You too!
And the software status is currently still on modified. Would it change when I lock the bootloader?
Click to expand...
Click to collapse
What software status? If you restore the original recovery there is no additional message during boot. If you lock the bootloader it will report as "relocked".

QDT said:
What software status? If you restore the original recovery there is no additional message during boot. If you lock the bootloader it will report as "relocked".
Click to expand...
Click to collapse
In the bootloader mode you see your software status. And it is still with stock rom and stock recovery on "modified"

inFiniTyz_Z said:
In the bootloader mode you see your software status. And it is still with stock rom and stock recovery on "modified"
Click to expand...
Click to collapse
And to my knowledge it will be like that. You have flashed unlocked (from HTC but always) bootloader and this has to be noted. It is not that drastical as KNOX for Samsung, doesn't influence the phone functioning.

inFiniTyz_Z said:
It worked. After my question I did the procedure and upgraded to oreo!
Thank you.
No Brick, but I had to erase the data and cache partition again after the first start, because it stucked at the HTC Logo after booting.
But the funfact is: I wanted to do a hard reset after my first try to boot it up, and the phone did a screenshot with the logo!
Click to expand...
Click to collapse
When you say you followed the procedure, which exactly do you mean? Can you please help me by giving me a quick summary of the steps?

I would like to know the procedure as well.

Hi! I've installed a custom ROM, now I would like to go back to the stock ROM, I don't have a nandroid backup, what can I do?

What to do about OTA update on rooted phone?

My phone keeps bugging me to install OTA update for krack vulnerability. I tried and it sent my phone to boot loop and now I have it restored. My phone has xposed installed. What is the best course of action? I would like to update but if that's not possible can I at least stop having the message show up each time I unlock my phone?

You could try to disable/freeze the Motorola-Updateservices (/system/priv-app/3c_ota/3c_ota.apk) or flash a new full (not OTA) firmware for your device without boot.img, recovery.img and without wiping data.
Beware: After flashing a full firmware, all modifications to the system partition are lost and have to be redone.
I always disable all 3c moto services and never faced problems because of it.

thorin0815 said:
You could try to disable/freeze the Motorola-Updateservices (/system/priv-app/3c_ota/3c_ota.apk) or flash a new full (not OTA) firmware for your device without boot.img, recovery.img and without wiping data.
Beware: After flashing a full firmware, all modifications to the system partition are lost and have to be redone.
I always disable all 3c moto services and never faced problems because of it.
Click to expand...
Click to collapse
Is that even safe not to apply the patch? I find it hard to believe just because you root your device you can't update it.

twoplustwo said:
Is that even safe not to apply the patch? I find it hard to believe just because you root your device you can't update it.
Click to expand...
Click to collapse
Is it a good idea to avoid security updates? No, it isn't. Is it clever to avoid updated drivers? No, it isn't (at least in most cases).
You should have informed yourself about the backdraws of rooting your phone before you did it. You need to be completely on stock firmware without any changes
to the system files to be able to use an OTA for updating your phone. This is needed to be safe the OTA update works the way it should.
The best way for updating a rooted phone is to install the full updated rom, which is easy to get for our device.

thorin0815 said:
The best way for updating a rooted phone is to install the full updated rom, which is easy to get for our device.
Click to expand...
Click to collapse
How can this be done? I don't know what to search for in these threads?

twoplustwo said:
How can this be done? I don't know what to search for in these threads?
Click to expand...
Click to collapse
Check this for example: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138

thorin0815 said:
Check this for example: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Click to expand...
Click to collapse
Some of my apps (like TI backup) need root. Is there a root for this version yet? I've tried searching but I find these forums very difficult to navigate.

twoplustwo said:
Some of my apps (like TI backup) need root. Is there a root for this version yet? I've tried searching but I find these forums very difficult to navigate.
Click to expand...
Click to collapse
Same procedure as on other stock rom versions): you need ElementalX kernel to be flashed and afterwards your desired root method(magisk is recommended).
Guides like this are valid https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918

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.