Database Users

P9 Lite Update released today (Question)

My question is simple, if i update im gonna lost my root and my custom recovery?

xCoNDex said:
My question is simple, if i update im gonna lost my root and my custom recovery?
Click to expand...
Click to collapse
Which Model have u got? Also i think u might lose ur root and custom recovery by updating.

Usama707 said:
Which Model have u got? Also i think u might lose ur root and custom recovery by updating.
Click to expand...
Click to collapse
VNS-L31, if im gonna lost all my data again repeating the root process i prefer to stay at this version

xCoNDex said:
My question is simple, if i update im gonna lost my root and my custom recovery?
Click to expand...
Click to collapse
I've successfully installed b131 update on my vns-l31 with twrp, and yes, I've lost both twrp and root. But this ca be easily redone because you still have bootloader unlocked. And your data is safe

lzimbrea said:
I've successfully installed b131 update on my vns-l31 with twrp, and yes, I've lost both twrp and root. But this ca be easily redone because you still have bootloader unlocked. And your data is safe
Click to expand...
Click to collapse
Thats nice!, and how about the update?, it is noticeable improvement?

xCoNDex said:
Thats nice!, and how about the update?, it is noticeable improvement?
Click to expand...
Click to collapse
Update changelog doesn't provide many information...
Just some carrier specific things and some system security improvement.
I didn't notice any differences in UI or overall performance.
But anyway my device run smoothly from day one.
What update you received? B131? Or other?

lzimbrea said:
Update changelog doesn't provide many information...
Just some carrier specific things and some system security improvement.
I didn't notice any differences in UI or overall performance.
But anyway my device run smoothly from day one.
What update you received? B131? Or other?
Click to expand...
Click to collapse
B131? , my update says B120
Log: System improvements and visual improvements on the ui text

xCoNDex said:
B131? , my update says B120
Log: System improvements and visual improvements on the ui text
Click to expand...
Click to collapse
Yes b131
Also i think that is is completely software since the update.app from the zip has 2.9 Gb

Please, could someone do this before update?
http://forum.xda-developers.com/mate-7/general/how-to-hicould-stock-firmware-link-ota-t3395467
Thanks

Sorry for jumping in here but I have a question.. if we have an unlocked bootloader and rooted do we still even get notifications that there's an update? tia

lilbrat said:
Sorry for jumping in here but I have a question.. if we have an unlocked bootloader and rooted do we still even get notifications that there's an update? tia
Click to expand...
Click to collapse
Yes you will receive the notification, but in most cases update fail to install due to various reasons, first is that system has been modified.
I was never afraid of bricking my devices and tried to see what happens. After restarting, when I saw the twrp logo, I was a bit sceptical, but after 2 minutes or so, phone restarted in stock recovery and finishing update

lilbrat said:
Sorry for jumping in here but I have a question.. if we have an unlocked bootloader and rooted do we still even get notifications that there's an update? tia
Click to expand...
Click to collapse
Yeah, i have root and twrp and i receive a notification update to B120 version yesterday

Guys can someone tell me how HiVoice works?, i dont have any config menu, just the fast calls
BTW the option "Im Here" to find your phone?, could be possible to use it on p9 lite?

lzimbrea said:
Yes you will receive the notification, but in most cases update fail to install due to various reasons, first is that system has been modified.
I was never afraid of bricking my devices and tried to see what happens. After restarting, when I saw the twrp logo, I was a bit sceptical, but after 2 minutes or so, phone restarted in stock recovery and finishing update
Click to expand...
Click to collapse
Thanks for the info.. I'm not worried about bricking it had lots of experience undoing my tinkering..lol and no update out for the middle east region.. though I do find my phone to be quite funny it has all the languages but for locations it covers the US and all of Africa and a few islands thats it..lol

Anyone knowes if is possible to change the system font?
lzimbrea said:
Yes you will receive the notification, but in most cases update fail to install due to various reasons, first is that system has been modified.
I was never afraid of bricking my devices and tried to see what happens. After restarting, when I saw the twrp logo, I was a bit sceptical, but after 2 minutes or so, phone restarted in stock recovery and finishing update
Click to expand...
Click to collapse
how you perform the update?, the automatic process dont work for me

xCoNDex said:
Anyone knowes if is possible to change the system font?
how you perform the update?, the automatic process dont work for me
Click to expand...
Click to collapse
I performed update process automatically, just press install after download has finished.
After some checking device rebooted in twrp and after some installation in twrp ( modem.img and things like this. I don't pay attention to device ), device rebooted second time, this time in stock recovery and finished the installing process.
But as far as I know even the dload method is safe. Your data partition is safe. As long as you update.app is from an update.zip , not from a stock full rom.
Update: I checked received package and didn't see any format or erase command on /data partition
It should be safe to flash even with dload method

lilbrat said:
Sorry for jumping in here but I have a question.. if we have an unlocked bootloader and rooted do we still even get notifications that there's an update? tia
Click to expand...
Click to collapse
Yeah, you still getting update notifications

lzimbrea said:
I performed update process automatically, just press install after download has finished.
After some checking device rebooted in twrp and after some installation in twrp ( modem.img and things like this. I don't pay attention to device ), device rebooted second time, this time in stock recovery and finished the installing process.
But as far as I know even the dload method is safe. Your data partition is safe. As long as you update.app is from an update.zip , not from a stock full rom.
Update: I checked received package and didn't see any format or erase command on /data partition
It should be safe to flash even with dload method
Click to expand...
Click to collapse
Dude i recently update succesfull to B120 and my bootloader gets locked again!, is this normal?
I had to upgrade from Stock recovery, twrp Was not doing anyhting (The phone reboot, twrp stars automatic but dont do anything), now i have to unlock boot loader again wich means format all my data again

xCoNDex said:
Dude i recently update succesfull to B120 and my bootloader gets locked again!, is this normal?
I had to upgrade from Stock recovery, twrp Was not doing anyhting (The phone reboot, twrp stars automatic but dont do anything), now i have to unlock boot loader again wich means format all my data again
Click to expand...
Click to collapse
Probably you're update had a bootloader update also...
My bootloader is still unlocked after update.
I really don't know what contain all updates.
And be aware that any rooted device can get bricked by official updates. So if you need your data partition, you have 2 options
1- stay with stock software and receive updates officially
2- experiment what you want with your device, but do a backup first or prepare yourself for data loss
I had a lot of luck with this update. Is first time when this happens to me

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?

Now done with ZTE rubbish

Ok it doesn't matter what I do I end up with a decrypted phone it doesn't matter what ROM I use or if I go stock rom.......
The moment I reboot or swap Sim card it instantly boot loop and I go in to recovery and it asks me for a password to decrypt it and when I flash it back to stock with stock bootloader and lock the bootloader up it doesn't play the video property and no sound........ZTE is not a good product.

stinka318 said:
Ok it doesn't matter what I do I end up with a decrypted phone it doesn't matter what ROM I use or if I go stock rom.......
The moment I reboot or swap Sim card it instantly boot loop and I go in to recovery and it asks me for a password to decrypt it and when I flash it back to stock with stock bootloader and lock the bootloader up it doesn't play the video property and no sound........ZTE is not a good product.
Click to expand...
Click to collapse
Pretty sure that's not ZTE's fault entirely

troy5890 said:
Pretty sure that's not ZTE's fault entirely
Click to expand...
Click to collapse
I have followed every thing that I was told to do to unlock the bootloader if I didn't it would have never been unlocked so saying that the encryption by automatically generated is the problem even when I flash stock rom back and don't use any password the thing is still encrypted that is the problem.

The AXON 7 is a very good smartphone until people try to put custom Rom on it. I have never tried and I will not to do it.... Don't complain about a product you've decided to modify by yourself. The problem is not the smartphone.
Envoyé de mon ZTE A2017G en utilisant Tapatalk

JLLE said:
The AXON 7 is a very good smartphone until people try to put stock Rom on it. I have never tried and I will not to do it.... Don't complain about a product you've decided to modify by yourself. The problem is not the smartphone.
Envoyé de mon ZTE A2017G en utilisant Tapatalk
Click to expand...
Click to collapse
But it is when they removed the options for me to encrypt the device and allow it by default........this is the problem I am having.....

Do a full wipe, format data and or internal storage maybe.
After flashing ROM also flash root. Doing the latter kept encryption from happening for me (a long time ago though).
Moto G5S Plus XT1806, GZOSP_PixelExperience, MultiROM, Tapatalk 4.9.3

Just flash with EDL
---------- Post added at 10:22 AM ---------- Previous post was at 10:22 AM ----------
Just fully flash phone to stock with edl

stinka318 said:
But it is when they removed the options for me to encrypt the device and allow it by default........this is the problem I am having.....
Click to expand...
Click to collapse
I think Axon 7 is encrypted by default on stock ROM (it says encrypted in settings/security) and can not be changed as it is fot me.

I also noticed that a newly flashed recovery asks you for a password, even thought I haven't encrypted the phone at that point, but do you know how I got past this? I clicked cancel... Atleast on TWRP this worked every time... Moreover if you correctly install LineageOS for example, you can encrypt your phone. I did it once after a complete wipe (because I soft bricked the phone), and it stayed encrypted ever since.
However if you try to modify your phone for the first time, I'm pretty sure you have to flash via EDL/Fastboot/ADB. EDL is the easiest way since there are tools for getting SU access and unlocking the bootloader I think. ADB works too but it's a little more complicated. This is because (like almost (is there even one?) every other manufacturer) ZTE doesn't allow flashing or getting SU access by default, so customers don't brick their phone

User unlocks bootloader (which ZTE does not officially support), starts flashing things (again not supported by ZTE) and then blames ZTE as if its their fault!?!?!?!?!
Can we say...dunce....

stinka318 said:
Ok it doesn't matter what I do I end up with a decrypted phone it doesn't matter what ROM I use or if I go stock rom.......
The moment I reboot or swap Sim card it instantly boot loop and I go in to recovery and it asks me for a password to decrypt it and when I flash it back to stock with stock bootloader and lock the bootloader up it doesn't play the video property and no sound........ZTE is not a good product.
Click to expand...
Click to collapse
-ZTE is not a product
-You want your phone to be encrypted? Flash the stock ROM, then start the phone. If you want root install it AFTER the ROM boots for the first time, because Magisk or SuperSU turns encryption off.
If the recovery asks you for a password then your phone is ENcrypted, not decrypted. If you want DEcryption, FORMAT the internal storage and then flash Magisk Then you can reboot.

stinka318 said:
Ok it doesn't matter what I do I end up with a decrypted phone it doesn't matter what ROM I use or if I go stock rom.......
The moment I reboot or swap Sim card it instantly boot loop and I go in to recovery and it asks me for a password to decrypt it and when I flash it back to stock with stock bootloader and lock the bootloader up it doesn't play the video property and no sound........ZTE is not a good product.
Click to expand...
Click to collapse
It's not the phone fault when you are not smart enough to unlock bootloader. ) Victims blame?

tamahouse said:
It's not the phone fault when you are not smart enough to unlock bootloader. ) Victims blame?
Click to expand...
Click to collapse
But I have unlocked the bootloader you have to do that to get custom recovery in it.......then it asks me for a password that I didn't even make......by the way I was able to get it all sorted.....

stinka318 said:
But I have unlocked the bootloader you have to do that to get custom recovery in it.......then it asks me for a password that I didn't even make......by the way I was able to get it all sorted.....
Click to expand...
Click to collapse
Yeah, that's your fault for not knowing that it is completely normal. After unlocking the phone, you have to format your data...

stinka318 said:
But I have unlocked the bootloader you have to do that to get custom recovery in it.......then it asks me for a password that I didn't even make......by the way I was able to get it all sorted.....
Click to expand...
Click to collapse
Use the security code you setup for Android.
Sent from my Moto Z (2) using Tapatalk

xRogerxC said:
Use the security code you setup for Android.
Sent from my Moto Z (2) using Tapatalk
Click to expand...
Click to collapse
Didn't set up encryption or password.......but it still asking for it in recovery......

Choose an username... said:
Yeah, that's your fault for not knowing that it is completely normal. After unlocking the phone, you have to format your data...
Click to expand...
Click to collapse
I had the same thing happen to me as well. I just had to format data and it fixed the problem.

xRogerxC said:
Use the security code you setup for Android.
Click to expand...
Click to collapse
again, nope, format data

stinka318 said:
But I have unlocked the bootloader you have to do that to get custom recovery in it.......then it asks me for a password that I didn't even make......by the way I was able to get it all sorted.....
Click to expand...
Click to collapse
The password is not by ZTE, it belong to android 7 or above by default. There no valid password, so you have to bypass it somehow. I not quite remember because I have to use so many methods, I wiped the phone up or miflashing or using axon tools.
The most easy way may be you have to miflash to an old version stock firmware, unlock the phone, install twpr, and flash the latest rom.

Best method to revert to Nougat from Oreo

Since the Oreo update, notifications from ALL play store apps are barely audible. Built in/system sounds are not effected. Have tried uninstalling/reinstalling apps, and a factory reset. Issue still persists. Like so low that I can't even hear them with the volume on max unless the phone is right next to my head.
Phone is not rooted and never has been. It is also NOT the Amazon variant, it is non carrier specific purchased from Walmart. Do I just need to follow a rooting guide for Oreo, then simply fastboot flash stock 7.0 & be sure to disable the update service afterwards? Do I need to worry about bootloader stuff or anything else? Or just flash the stock 7.0 image as is?

plastic_green_head said:
Since the Oreo update, notifications from ALL play store apps are barely audible. Built in/system sounds are not effected. Have tried uninstalling/reinstalling apps, and a factory reset. Issue still persists. Like so low that I can't even hear them with the volume on max unless the phone is right next to my head.
Phone is not rooted and never has been. It is also NOT the Amazon variant, it is non carrier specific purchased from Walmart. Do I just need to follow a rooting guide for Oreo, then simply fastboot flash stock 7.0 & be sure to disable the update service afterwards? Do I need to worry about bootloader stuff or anything else? Or just flash the stock 7.0 image as is?
Click to expand...
Click to collapse
I would suggest that the only way to do it safely is to unlock and root, then do a clean flash of the TWRP flashable nougat builds.
If you go from Oreo to nougat you will lose your IMEI, unless you change ownership of specific files and folders in your persist partition. There's no way to do that without root.
https://forum.xda-developers.com/g5-plus/development/twrp-flashable-stock-builds-t3813351

NZedPred said:
I would suggest that the only way to do it safely is to unlock and root, then do a clean flash of the TWRP flashable nougat builds.
If you go from Oreo to nougat you will lose your IMEI, unless you change ownership of specific files and folders in your persist partition. There's no way to do that without root.
https://forum.xda-developers.com/g5-plus/development/twrp-flashable-stock-builds-t3813351
Click to expand...
Click to collapse
Thanks. It looks like backing up my persist & ESF should eliminate any worries regarding loss of IMEI.

plastic_green_head said:
Thanks. It looks like backing up my persist & ESF should eliminate any worries regarding loss of IMEI.
Click to expand...
Click to collapse
Well if by backing up you mean backing up persist and efs on Oreo then u might have issues. I dont think Oreo backup would work on Nougat. There was a thread tho on this exact topic. So you need to leave out gpt and some other partition if u fastboot flash it. You cannot downgrade the bootloader. I'm sure u know that. Safer way would be to flash via TWRP.
GL:good:

debdeep98 said:
Well if by backing up you mean backing up persist and efs on Oreo then u might have issues. I dont think Oreo backup would work on Nougat. There was a thread tho on this exact topic. So you need to leave out gpt and some other partition if u fastboot flash it. You cannot downgrade the bootloader. I'm sure u know that. Safer way would be to flash via TWRP.
GL:good:
Click to expand...
Click to collapse
Hmmmm. TWRP it is then. I have plenty of experience with TWRP, but I haven't flashed a phone in MANY years. One thing about the page you linked to. It states "An important note for those who have flashed custom Oreo roms. It is a frequent issue regarding Oreo roms that the device's IMEI is set to 0 in certain conditions."
So since my phone is on stock ota Oreo & not a custom Oreo rom... do I need to even worry about losing IMEI? Maybe I should ask in that thread?

plastic_green_head said:
Maybe I should ask in that thread?
Click to expand...
Click to collapse
Yes that sounds good.

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.