[RECOVERY][OFFICIAL]TWRP v3.2.3 For Moto G6 [ALI][2018-10-20]

[HueyT]

Will there be a version for Pie?
I rooted mine after updated to Pie using Magisk patching method (I have full ROM)

Same TWRP for Oreo or PIE but official one won't install Gapps while unofficial one by DeJello will (11/2018)

 

[Jonny_Bandana]

Do we still need to use unofficial to install GApps?

 

[oposiasty]

Do we still need to use unofficial to install GApps?

Yup

 

[neovaughn]

does it work for the Moto g6 version XT1925-3?

 

[HueyT]

does it work for the Moto g6 version XT1925-3?

Yes. Use Dejello unofficial TWRP 11/2018

 

[HACK3DANDR0ID]

Same TWRP for Oreo or PIE but official one won't install Gapps while unofficial one by DeJello will (11/2018)

I just got a Moto G6 (XT1925-6) to replace my smashed Pixel OG. Like an idiot I updated all the way to PPS.29.118-11-1 (May 1st Security Update). Bootloader Unlocked. Is there a guide somewhere for Rooting Official Pie and flashing TWRP?

 

[kc6wke]

I just got a Moto G6 (XT1925-6) to replace my smashed Pixel OG. Like an idiot I updated all the way to PPS.29.118-11-1 (May 1st Security Update). Bootloader Unlocked. Is there a guide somewhere for Rooting Official Pie and flashing TWRP?

Go Here

 

[HACK3DANDR0ID]

Go Here

The link is down for the DM Verity Disabler, would you happen to have available?

 

[kc6wke]

The link is down for the DM Verity Disabler, would you happen to have available?

read this post

 

[HACK3DANDR0ID]

Go Here

Thanks again, worked like a charm!

 

[GhostMan55]

Will this still work?

Update March 23, 2019: I'd like to apologize to everyone. It looks like I am not going to be able to actively keep this thread updated like I used to. I have had too much going on at home an work and it doesn't look like it's going to settle down any time soon. The thread is still usable so I will leave it open for discussion.

Team Win Recovery Project​

 * Your warranty is now void.
 *
 * I am not responsible for bricked devices, dead SD cards, fires, rigged elections,
 * specks of dusk sitting on cursors, cursors that mock you--waiting for cursor
 * revenge, thermonuclear war, or you getting fired because the alarms failed
 * and you could not call in.
 *
 * Please ensure you have an advanced understanding of this device before
 * flashing it! YOU are choosing to make these modifications or your own free will.

This is the first official build of TWRP for the Motorola Moto G6 (ALI)!

Notes:

• Decryption is finicky: Currently only vold decryption is working. This image must be flashed to properly decrypt. Updates may cause issues with decryption.
• If you format data (Not just factory reset) after decrypting you must reboot into recovery and format again.
• If you are unable to unlock your phone after restoring a data backup that had a lock code on it (and TWRP is able to decrypt using default password) you'll need remove the '/data/system/locksettings.db' while in TWRP. After that you should be able to reboot into Android and set a lock code. If you cannot then please use this thread as a guide and try again. Bascially you just delete more, however I was able to boot after just deleting the one file with a pattern set (Maybe random luck, maybe not)

If you have any other issues please let me know and I'll work toward fixing them! AS ALWAYS, IT'S YOUR RESPONSIBILITY IF YOU USE THIS SOFTWARE

Known Issues:

• I have just noticed some odd behaviour if you input an incorrect decryption password/pattern/etc in twrp. It can cause an issue while entering the lockscreen password/pattern/etc while booting up. Under normal circumstances these two are the same, hence why restoring can also cause a similar issue, though that one is easily fixable. The onIy way to clear the decryption pass is to format. I am unsure at the moment what is causing this, but clearly it has something to do with the decryption. At this time I'd say it'd be best to remove your current lockscreen password/pattern/etc before booting into twrp to avoid this issue. A possible work-around would be to reboot to twrp, enter the correct password, back up your data, format (reboot to twrp and format again), then restore your backup (and possibly need to delete the '/data/system/locksettings.db' file. Your data would still exist that way. I am going to work to fix this asap and maybe see if I can get another build without decryption made for official use for now.
• Flashing zips that require BusyBox will not work with the official version right now. I've built an unofficial version to use until a new official build is triggered.

ALI's Changelog: Post #2
Download: twrp.me Download
Unofficial Download (updated more often): twrp-v3.2.3-unofficial-ali-20181110.img

Simple Installation Method:
1) boot to fastboot
2) fastboot flash recovery <twrp-image-name>.img

Other instructions are available on the Official download page. It's up to you to backup your factory recovery first if you wish to have a backup: Post #3


Thanks to the TWRP team and everyone who has put in effort to make these things possible!
@Jleeblanch - Wonderful advice and guidance
@Dadud - testing
@ Everyone at github
@ XDA and the people who provided TWRP compiling threads
If I've forgotten someone who you think needs mention please let me know!

* This page will continue to be edited as more information comes

XDA:DevDB Information
[RECOVERY][OFFICIAL] TWRP v3.2.3 [2018-10-20], Tool/Utility for the Moto G6

Contributors
dejello
Source Code: [url]https://github.com/TeamWin/android_device_motorola_ali[/URL]


Version Information
Status: Stable
Current Stable Version: 3.2.3-0
Stable Release Date: 2018-10-20
Current Beta Version: 3.2.3 Unofficial
Beta Release Date: 2018-11-10

Created 2018-10-21
Last Updated 2018-11-10

Hi, will this still work on Android 8.0.0 and Build Number 104-92-6?

 

[DessertArbiter]

ive been having an issue with adopted storage in twrp, when i mount data it mounts the wrong thing, the thing it mounts is whatever is normally located at /mnt/expand/(some really long number) when android is booted

any fix for this? it seems like very odd behavior

im using twrp 3.3.1.0

 

[bhati2710]

Softbricked phone and oem locked

Update March 23, 2019: I'd like to apologize to everyone. It looks like I am not going to be able to actively keep this thread updated like I used to. I have had too much going on at home an work and it doesn't look like it's going to settle down any time soon. The thread is still usable so I will leave it open for discussion.

Team Win Recovery Project​

 * Your warranty is now void.
 *
 * I am not responsible for bricked devices, dead SD cards, fires, rigged elections,
 * specks of dusk sitting on cursors, cursors that mock you--waiting for cursor
 * revenge, thermonuclear war, or you getting fired because the alarms failed
 * and you could not call in.
 *
 * Please ensure you have an advanced understanding of this device before
 * flashing it! YOU are choosing to make these modifications or your own free will.

This is the first official build of TWRP for the Motorola Moto G6 (ALI)!

Notes:

• Decryption is finicky: Currently only vold decryption is working. This image must be flashed to properly decrypt. Updates may cause issues with decryption.
• If you format data (Not just factory reset) after decrypting you must reboot into recovery and format again.
• If you are unable to unlock your phone after restoring a data backup that had a lock code on it (and TWRP is able to decrypt using default password) you'll need remove the '/data/system/locksettings.db' while in TWRP. After that you should be able to reboot into Android and set a lock code. If you cannot then please use this thread as a guide and try again. Bascially you just delete more, however I was able to boot after just deleting the one file with a pattern set (Maybe random luck, maybe not)

If you have any other issues please let me know and I'll work toward fixing them! AS ALWAYS, IT'S YOUR RESPONSIBILITY IF YOU USE THIS SOFTWARE

Known Issues:

• I have just noticed some odd behaviour if you input an incorrect decryption password/pattern/etc in twrp. It can cause an issue while entering the lockscreen password/pattern/etc while booting up. Under normal circumstances these two are the same, hence why restoring can also cause a similar issue, though that one is easily fixable. The onIy way to clear the decryption pass is to format. I am unsure at the moment what is causing this, but clearly it has something to do with the decryption. At this time I'd say it'd be best to remove your current lockscreen password/pattern/etc before booting into twrp to avoid this issue. A possible work-around would be to reboot to twrp, enter the correct password, back up your data, format (reboot to twrp and format again), then restore your backup (and possibly need to delete the '/data/system/locksettings.db' file. Your data would still exist that way. I am going to work to fix this asap and maybe see if I can get another build without decryption made for official use for now.
• Flashing zips that require BusyBox will not work with the official version right now. I've built an unofficial version to use until a new official build is triggered.

ALI's Changelog: Post #2
Download: twrp.me Download
Unofficial Download (updated more often): twrp-v3.2.3-unofficial-ali-20181110.img

Simple Installation Method:
1) boot to fastboot
2) fastboot flash recovery <twrp-image-name>.img

Other instructions are available on the Official download page. It's up to you to backup your factory recovery first if you wish to have a backup: Post #3


Thanks to the TWRP team and everyone who has put in effort to make these things possible!
@Jleeblanch - Wonderful advice and guidance
@Dadud - testing
@ Everyone at github
@ XDA and the people who provided TWRP compiling threads
If I've forgotten someone who you think needs mention please let me know!

* This page will continue to be edited as more information comes

XDA:DevDB Information
[RECOVERY][OFFICIAL] TWRP v3.2.3 [2018-10-20], Tool/Utility for the Moto G6

Contributors
dejello
Source Code: [url]https://github.com/TeamWin/android_device_motorola_ali[/URL]


Version Information
Status: Stable
Current Stable Version: 3.2.3-0
Stable Release Date: 2018-10-20
Current Beta Version: 3.2.3 Unofficial
Beta Release Date: 2018-11-10

Created 2018-10-21
Last Updated 2018-11-10

Hi @dejello
I need your assistance if you could help. I have gone through most of your posts and i think you are the right person who can assist me right now.

Scenario:
I originally had xt1925-13 indian model which i successfully rooted and installed custom rom but afterwards it was hard bricked by mistake.

I realized it little late but then i took it to the Jtag service and the guy doesn't have the same model so i had to provide the mmcblk0 available in xda by someone and it was for xt1925-2 brazil model i guess.

Now my phone model has changed to xt1925-2 which seems illogical and soft bricked. Jtag person couldn't restore it and but it is stuck in soft brick loop (bootloader). Additionally, it also shows oem locked and when i try to flash any stock rom, it gives an error pre validation failed. Please help.

Is there any way i can restore it and get my imei numbers back.

Thank you in advance.

 

[bhati2710]

Stuck under oem_locked

Hi @dejello
I need your assistance if you could help. I have gone through most of your posts and i think you are the right person who can assist me right now.

Scenario:
I originally had xt1925-13 indian model which i successfully rooted and installed custom rom but afterwards it was hard bricked by mistake.

I realized it little late but then i took it to the Jtag service and the guy doesn't have the same model so i had to provide the mmcblk0 available in xda by someone and it was for xt1925-2 brazil model i guess.

Now my phone model has changed to xt1925-2 which seems illogical and soft bricked. Jtag person couldn't restore it and but it is stuck in soft brick loop (bootloader). Additionally, it also shows oem locked and when i try to flash any stock rom, it gives an error pre validation failed. Please help.

Is there any way i can restore it and get my imei numbers back.

Thank you in advance.

Can someone help here ?

I am in the same situation he mentioned here : https://forum.xda-developers.com/z2-...brick-t3710744

Is there any solution for this?

 

[Jorge94]

Jorge Eliecer Marriaga Rodríguez, [15.04.21 20:56]
(gestor de arranque) es lógico: recuperación: no encontrado
Enviando 'recuperación' (16194 KB) OKAY [0.632s]
Escribiendo 'recuperación' (gestor de arranque) La recuperación de la imagen falló en la validación
(cargador de arranque) Falló la validación de preflash
FALLIDO (remoto: '')
fastboot: error: el comando falló

como puedo solucionar este fallo

 

[Jorge94]

Como puedo solucionar este fallo

(gestor de arranque) es lógico: recuperación: no encontrado
Enviando 'recuperación' (16194 KB) OKAY [0.543s]
Escribiendo 'recuperación' (gestor de arranque) La recuperación de la imagen falló en la validación
(cargador de arranque) Falló la validación de preflash
FALLIDO (remoto: '')
fastboot: error: el comando falló

 

[Zzynth]

i think i bricked my phone. Black screen on boot then goes to the bootloader. XT1925-6