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

[dejello]

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

 

[dejello]

Changelogs

TWRP Changelog:
v3.2.3 changelog

ALI's Official Changelog:
v3.2.3-0 (Oct 20, 2018)
- N/A, first build!

ALI's Temp. Unofficial Changelog:
v3.2.3 (Oct 31, 2018) (This log will get moved to official when it gets updated with these changes)
- Stop using toybox (Use busybox!)
- Added vendor image mount point

 

[dejello]

Factory Backup Information

It's up to you to determine if you want/need a factory recovery image backup before flashing:

To boot twrp first (it will fail decryption, don't worry about it) just do the following while replacing <twrp> with the actual file name.

fastboot boot <twrp>.img

Then to back up your stock/factory recovery while booted in TWRP do the following.

adb pull /dev/block/bootdevice/by-name/recovery stockrecovery.img

 

[Jleeblanch]

First [emoji14]

For real tho, nice work and congrats [emoji41]

 

[GuestK00235]

Woot Woot! Congrats bro?

 

[najjannajS650]

Lockscreen after restore

Hello, this method (delete lockscreen) after restore backup works for me to ?

 

[giant22000]

Decryption doesn't work for me. XT1925-6 Ali

 

[dejello]

Decryption doesn't work for me. XT1925-6 Ali

I'll need more details if I'm to look into it. I also have an xt1925-6. Any logs? What version software are you running? What kind of lock screen are you using (pin, password, pattern, none, etc)? What happened from booting twrp up to the point of decryption failure? The more information I have the better chance I have at rectifying the issue.


[EDIT] I just did some messing around and came across something I hadn't seen before:

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.

I have added this to the first post.

 

[Snearde]

Damn thanks !

 

[aaleej0]

Hi. First thank for the contribution.
I would like to know if someone has the stock twrp, modeled 1925-1. When I modified my stock twrp, I made a back up, but I lost it.
I would like to update my security patch, but I can not because it has modified the twrp.

 

[ninjakira]

Hi. First thank for the contribution.
I would like to know if someone has the stock twrp, modeled 1925-1. When I modified my stock twrp, I made a back up, but I lost it.
I would like to update my security patch, but I can not because it has modified the twrp.

So I guess I will be the one to say it. I'm giving you one warning about this. It's against forum rules to post on multiple threads with the same subject. I've answered your question on the Ali stock firmware thread also. Please read guides and threads instead of skimming through them because it's been answered multiple times. Next time you do this and post the same thing on multiple threads I will be the one reporting you. Have a good day.

 

[dejello]

I have added an unofficial build tonight (Oct/31/2018) to fix an issue flashing zips that need busybox (Resurrected Kernel, etc) versus toybox. It also adds a 'vendor image' mount point for use in backups and flashing. Once official gets updated this unofficial build will be removed.

 

[jglm4u]

Hello, could you consider supporting the Moto g 6 play xt922-4 I'm welling to help out with logs or anyfile if needed.

 

[ninjakira]

Hello, could you consider supporting the Moto g 6 play xt922-4 I'm welling to help out with logs or anyfile if needed.

There are certain reasons there is no official twrp for our moto g6 play devices yet. Is there issue your having?. Dejello supports the regular g6 and for all intensive purposes I've being doing support for the g6 play.

 

[dejello]

Hello, could you consider supporting the Moto g 6 play xt922-4 I'm welling to help out with logs or anyfile if needed.

There are certain reasons there is no official twrp for our moto g6 play devices yet. Is there issue your having?. Dejello supports the regular g6 and for all intensive purposes I've being doing support for the g6 play.

I don't have access (well, sort of but not really) to a g6 play. My son has one, but it's not unlocked or anything and I won't experiment on his phone without having everything backed up.... Besides, getting the damn thing away from him for extended periods when he isn't in trouble would be something.... I thing it's glued to his face or something.

I am also not up to date on any issues or reasons why twrp isn't official for the g6 play. Be aware that even this version for the g6 has some issues (workarounds are available for everything so you won't lose anything) still.

I've been debating looking into it, but haven't yet for reasons above.

 

[ninjakira]

I don't have access (well, sort of but not really) to a g6 play. My son has one, but it's not unlocked or anything and I won't experiment on his phone without having everything backed up.... Besides, getting the damn thing away from him for extended periods when he isn't in trouble would be something.... I thing it's glued to his face or something.

I am also not up to date on any issues or reasons why twrp isn't official for the g6 play. Be aware that even this version for the g6 has some issues (workarounds are available for everything so you won't lose anything) still.

I've been debating looking into it, but haven't yet for reasons above.

I just had a good laugh about your son's g6 play being glued to his face ??I could definitely say I don't look at or use my phone as much as the kids now a days and I'm 27 lol I worked ina mall so I seen that alot lmao and what all would you need from someone to attempt an official twrp for it? Ill do my best to provide you with what's needed. The patched twrp for the g6 play should be a good start. I would have already started on it myself but i am not able to get it going because i don't trust my laptop (it came with Vista) and it likes to randomly reboot and all this marvelous stuff lol

 

[dejello]

I just had a good laugh about your son's g6 play being glued to his face ??I could definitely say I don't look at or use my phone as much as the kids now a days and I'm 27 lol I worked ina mall so I seen that alot lmao and what all would you need from someone to attempt an official twrp for it? Ill do my best to provide you with what's needed. The patched twrp for the g6 play should be a good start. I would have already started on it myself but i am not able to get it going because i don't trust my laptop (it came with Vista) and it likes to randomly reboot and all this marvelous stuff lol

When I get a chance I can take a look at some things. But looking at github I do see at least one device tree being worked on for jeter

 

[Jleeblanch]

I just had a good laugh about your son's g6 play being glued to his face [emoji23][emoji23]I could definitely say I don't look at or use my phone as much as the kids now a days and I'm 27 lol I worked ina mall so I seen that alot lmao and what all would you need from someone to attempt an official twrp for it? Ill do my best to provide you with what's needed. The patched twrp for the g6 play should be a good start. I would have already started on it myself but i am not able to get it going because i don't trust my laptop (it came with Vista) and it likes to randomly reboot and all this marvelous stuff lol

I wouldn't trust Windows either. Personally, I'd wipe Windows right off it and run Linux. Linux would breathe new life into a laptop that came with Vista lol.

 

[ninjakira]

I wouldn't trust Windows either. Personally, I'd wipe Windows right off it and run Linux. Linux would breathe new life into a laptop that came with Vista lol.

I do have it on dual boot with Ubuntu 18.10 it's Just the the random rebooting is persistent still but yeah I personally use use linux distos over Windows lol. My next paycheck I'm having our local computer store called microcenter help me out with a new laptop at least lol

 

[ninjakira]

When I get a chance I can take a look at some things. But looking at github I do see at least one device tree being worked on for jeter

I'm not able to send the screenshot of termux so here they are. Recovery is 16 mb