yashsingh1/xdaforums huggingface dataset:
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] ThE_MarD:
@jtnc, just to check, are you using FBE and not FDE for encryption methods? I just formatted the data on my payton and wiped dalvik and flashed LOS 18.1 and tested both via fastboot boot twrp-3.6.1_11-0-payton.img and adb sideload twrp-installer-3.6.1_11-0-payton.zip and both booted fine and I could PIN decrypt my LOS 18.1 ROM

View attachment 5595947

View attachment 5595949

It does take a minute or three to boot into TWRP, so I do recommend giving it a bit of time for decryption to work.

As I mentioned above though, TWRP cannot currently decrypt A12.x ROMs, so users MUST remove lockscreen security in the ROM before rebooting to TWRP.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] woodpe:
Will there some time be a chance to decrypt A12 ROMs with lockscreen security by TWRP?

Thanks for an answer.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] ThE_MarD:
Heyyo @woodpe, from my understanding? Android 12.1 changes the way security key storage works, so the path that TWRP usually uses for decryption does not exist... so unless a new solution is found? Potentially TWRP might never decrypt lock screen security ever again...
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] ThE_MarD:
Please test the pre-official TWRP build from their built server.

TWRP image:

https://build.twrp.me/twrp-3.6.1_11-0-payton.img

TWRP installer zip:

https://build.twrp.me/twrp-installer-3.6.1_11-0-payton.zip

If they are confirmed as working? I will ask for a new official TWRP build for payton.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] woodpe:
I'm using lineageos19.1 in combination with the pre-offical TWRP.

All works fine, but no decryption.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] ThE_MarD:
@woodpe for A12 ROMs? You must remove lockscreen security, reboot to TWRP, make changes, reboot to system and then setup your lockscreen security again
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] jtnc:
I think this is the problem I've been seeing then. I think I was hoping your test build fixed that problem! All my decryption issues with TWRP have occurred after moving to LineageOS 19.1. I did not have a chance to roll back to 18.1 and revalidate the 3.6.1 build you posted over the weekend, but given the above comment and your experiment on 18.1 I'd expect it to work fine for me.

Removing the lock screen pin and rebooting to recovery worked fine with 19.1 and TWRP 3.6.1_11, I have not tried it on TWRP 3.5.0_9. It's a bit annoying that you have to redo fingerprints every time you remove the lock screen security (at least for PIN, I assume that's true for any).

But given that TWRP 3.6.1 is not expected to work well PIN and 19.1, I'd say go ahead and make 3.6.1_11 official. The only thing I haven't tried is a complete ROM install but I was able to flash recover and other zips from it fine.

Question, would it be worth adding a note to maybe the second post of the lineageOS 19.1 thread indicating TWRP + 19.1 + lockscreen PIN does not currently work?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] wkn000:
For upgrade my Lineage OS from 18.1 to 19.1, i booted temporary twrp-3.6.1_11-0-payton.img (at this point the test version, is saw it is official now). Data partition was able to decrypt with pin code there.

After upgrade LOS i had to reinstall Magisk, so, rebooted again to TWRP and was then NOT able to decrypt data partition anymore. But for reinstallation of Magisk, cancel was OK and proceed further.

So, decryption still doesn't work yet with newest TWRP in combination with LOS 19.1 as it does with LOS 18.1 before.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] ThE_MarD:
@jtnc @wkn000 yeah I'll add a note for TWRP
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] BERA1985:
Hey guys. When I saw that LOS19 was released, I decided to upgrade, without noticing this TWRP issue... I am not an advanced user, so I got used to this 3.5.9 version (that was able to decrypt with collected fingerprint by LOS18)...

LOS19 is great! But I tried to go to recovery mode and got stuck on splash screen.

Is there any solution to that? Tks!!!!
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] jtnc:
You will need to install the latest TWRP (3.6.1_11). Since you're stuck booting into TWRP, it will need to be done via fastboot and then sideload. See the first post or the TWRP docs for detailed steps.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] BERA1985:
Thanks! I'll try that this weekend. I'll need to remove fingerprints anyway, that's it?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] wkn000:
My way is to have Lineage Recovery installed permanent and boot only temporary to TWRP, when i really "needed" or feel more "comfortable" doing something with it.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] BERA1985:
Hnnn!!! How do I get (or access) Lineage Recovery? I only use twrp to update LOS, if there's a "official" and permanent recovery, I can live without twrp easily...

Tks in advance!
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] wkn000:
Lineage Recovery is installed automatically with Lineage OS. Just reboot to recovery from the phone. Also used during OTA updates from System / Updater. At the moment it has less functionality compared with TWRP, but all in what normally needed.

Temporary TWRP is accessed by "adb reboot bootloader" and "fastboot boot twrp-xxx.img".
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] BERA1985:
Thank you for the explanation! I used to to 1) install LOS + TWRP, 2)reboot to recovery to install GApps and then finally reboot to system... Probably since LOS17. (And "got stuck" on TWRP 3.5.9 because it's was the one that was able to get into recovery without erasing my fingerprints on Android security)

Will I be able to install GApps using LinRecovery? Does it decrypt system with fingerprints? If yes, I see no point on installing TWRP anymore!
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] ThE_MarD:
@BERA1985 LOS Recovery can install ROMs and mods like GApps, but it doesn't do decryption of data as it's meant for only installing this or pulling pstore logs.

It also does not do any data backups or restore as LOS recommends using SeedVault for that.

TWRP cannot decrypt data on A12 ROMs as the first post note mentions, but you can access the data if you first remove the lockscreen security.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] BERA1985:
@ThE_MarD, @wkn000, @jtnc - Thanks guys!

Updating TWRP using ADB was easy, but it's mandatory to lose fingerprints, since you have to set your "login security" to "none".

Ok, I was able to upgrade to latest L.OS - but then I got problems with some Google Apps (Gmail, Play store were not opening anymore). So I decided to format my device (using TWRP to do that), reboot to recovery - got into L.OS Recovery and used that to reinstall.

It works great! Was able to install L.OS and reboot to recovery to install GAPPS without problems.

But now I have another questions (probably my last two haha):

1 Am I obliged to reboot to recovery in order to reinstall GAPPs every time LOS updates???

2 Will I be able to use LOS Recovery without setting my login security options to "none"??

Thanks in advance!
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] woodpe:
Short answers:

1: It's not necessary to reinstall GAPPS if you use the built-in updater.

2: Yes
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] wkn000:
Just tested new TWRP version twrp-3.6.2_11-0-payton.img

Still not able to decrypt data partition with password or pin.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] ThE_MarD:
@wkn000 , they haven't posted the release notes on the TWRP website, but this is only a bug fix release. You can read the notes on Gerrit though:

https://gerrit.twrp.me/c/twrpme/+/5534
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] wkn000:
Thanks for the link, as you said, changelogs could sadly not be found for TWRP.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] rseiler:
Is that also true if you're sideloading via LOS recovery? I'd really prefer doing it that way now purely for reliability. Reason:

I've gotten stuck on the splash screen upon reboot via the updater, but I don't really know why. I had no apparent recourse but a reset from LOS recovery, which worked, but later I wondered if temp booting into TWRP would have worked by clearing Dalvik/Cache. That might be an Old Wive's tale, though.

Still, I had nothing to lose by trying, but because I didn't have the lockscreen disabled, since I didn't know of that requirement until today, I guess I couldn't have done it anyway.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] woodpe:
I think in that case you have to reinstall GAPPS.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] rseiler:
OK. That definitely was a possibility but was another aspect of it that I couldn't confirm (whereas it's very clear that there's a need to install Gapps before booting into LOS the first time after coming from stock).

I'd really prefer to use the updater, but since that didn't work out the one and only time I've tried it, for reasons that may be unknowable, I'm trying to nail down a reliable alternative method, and TWRP will probably play a role (either for all of it or just the clearing of cache part).
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] woodpe:
I always use the updater and there was never a problem.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] ThE_MarD:
Heyyo @rseiler, you MUST reinstall GApps if manually updating (sideloading or install via USB OTG, etc) as A/B partitioned devices cannot use releasetools to reinstall any add-ons.

The Lineage Updater did have some bugs I think last month but they are resolved now. If you're on a recent build? The Lineage Updater will work correctly again.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] rseiler:
@ThE_MarD Great to know that about Gapps definitively, and not needing to do that that would definitely be a primary reason that I'd prefer to use the updater. When I try the updater next time though, I'm going to have fingerprint security disabled just in case I need to temp boot into TWRP to try the longshot solution of getting past an infinite boot logo: reset Dalvik/cache. With nothing to lose in that situation, it's worth a try.

An updater bug would make sense, since I could find no one really complaining about the updater in modern times. I was on 19.1-20220531 at the time, going to 19.1-20220614, so if this was a bug it was a bit unlucky. I've now looked in the Gitlab, and so far I haven't really found any recent discussion of it, but there's a lot there and descriptions aren't always optimal.

As it happens, I'll have an identical X4 so will be able to repeat the updater experiment.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Edenzero69:
Hi, which version of TWRP do i flash in this phone

phone is XT1900-4

android 9: PPWS29.69-40-3-1

security patch: 1 september 2019

and if somebody want to give me an advice in this thread https://xdaforums.com/t/installing-twrp-and-magisk-questions.4473903/ , thanks in advance
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] rseiler:
It's this one:

Motorola Moto X4

Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...

twrp.me

But I only used it on this phone a couple times in a temporary fashion.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Edenzero69:
is there any difference between

twrp3.6.2_11-0-payton

and

twrp3.6.0_9-0-payton

the first one looks the recent one, however it has number 11, and the other one has number 9, it has to do with which android version you have? meaning if i have android 9, i must use the 3.6.0_9, or wont matter and i can use the 3.6.2_11
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] rseiler:
@Edenzero69 That's a reasonable assumption, but I'm not sure (I have Android 12 so just picked the top one). The 9 one is only a few months old in any case. You could ask here:

https://xdaforums.com/t/official-tests-twrp-for-the-motorola-moto-x4-payton.4197459
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] ThE_MarD:
Heyyo @Edenzero69 , the 3.6.2_11-0-payton build is meant to work for Moto x4 on Android 11 and higher.

The 3.6.0_9-0-payton build will work on Android 10 and below.

Essentially if you plan on using the latest Android ROM? Please use the latest TWRP
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] salukii:
Yo, when i flash twrp installer zip it ends with "error 1 failed to unpack image" but twrp is fixed in my recovery and i can flash magisk to root without error. flash custom roms with this twrp can cause something?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] ThE_MarD:
Heyyo @salukii, can you please share logcat? and recovery log too?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] salukii:
Where i find this?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] ThE_MarD:
@salukii first perform the action that's giving you the error, then dump logcat you can use

adb logcat -d > logcat.log

You can retrieve the recovery.log by going into the menu for advanced > copy log. Then send me the recovery.log that it will dump. It should show you the location of it.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] woodpe:
There's a new version of TWRP 3.7.0_12-0!
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] wkn000:
I just tried to fastboot boot twrp-3.7.0_12-0-payton.img, but no luck, booted to LOS system afterwards.

Moto X4 XT1900-7 RETEU

Question: Why no twrp-3.7.0_11.0-payton.img as there is a zip existent?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] ThE_MarD:
Heyyo, as @woodpe mentioned TWRP 3.7.0_12 is out which is based upon the same device changes as that last test build. :)

@wkn000 I'll be requesting that 3.7.0_11 build to be removed completely for payton as it's broken. Instead of fixing 11 I figured it would be better anyways if I just focused on A12 since it supported decryption on A12 and A13 ROMs
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] woodpe:
I also tried to fastboot boot twrp-3.7.0_12-0-payton.img, but no luck, phone booted to LOS system afterwards.

It's a pity.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] wkn000:
Tried again with img:

but same issue, tries to boot, but after a few seconds, reboot to system.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] ThE_MarD:
@wkn000 can you please tell us what version of Android you currently have installed?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] wkn000:
@ThE_MarD

Last official Android (before intallation of LOS, expected by installation wiki) was XT1900-7_PAYTON_RETEU_DS_9.0_PPWS29.69-37-5_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml

Since this morning (OTA update) it is on lineage-19.1-20221018-nightly-payton-signed.zip

Magisk is installed, no GApps. No problems with twrp-3.6.2_11-0-payton.img
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] wkn000:
Anything happened here to TWRP? Still not functional version from 17.10.2022 in list.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] ThE_MarD:
@wkn000 sorry I've been busy and forgot about this. If you could please provide logcat and recovery logs using latest official TWRP build for payton when you get any errors
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] wkn000:
@ThE_MarD

Found time to test today, hopefully the logcat shows the issue ;-)
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] jtnc:
For what its worth, twrp 3.7.0-12 is working great for me. It decrypted storage again which is great, no more removing lock before using twrp! I've only tried it with lineageos 19.1.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] ThE_MarD:
This logcat seems to be from LineageOS. Please reboot to TWRP and logcat there as I need those logs to diagnose any TWRP issues
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] wkn000:
@ThE_MarD

So, first try to boot to not working TWRP 3.7.0_12-0 and then after the automatically boot to system, reboot to working TWRP 3.6.2_11-0 and take logcat in there?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] ThE_MarD:
@wkn000 if you can't get logcat from within that TWRP then try to reboot to that older TWRP and try this:

adb pull /sys/fs/pstore

It will copy from the device that pstore folder and then please share whatever files are in there
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] wkn000:
@ThE_MarD

Find time today to test again with TWRP. But i got no files in pstore only the folder itself.

So i have no further information for debugging for you, sadly.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] ThE_MarD:
A new TWRP test build is up! twrp-3.7.0_12-0_UNOFFICIAL-20230101-03-payton contains a bunch of reorganizing and changes to a lot of the device tree in order to blindly try and fix whatever issues some users report without logs 😂🙈👍

Release twrp-for-payton twrp-3.7.0_12-0_UNOFFICIAL-20230101-03-payton - twrp-for-payton - OSDN

Release twrp-for-payton twrp-3.7.0_12-0_UNOFFICIAL-20230101-03-payton - twrp-for-payton #osdn

osdn.net

I know it works and can decrypt LineageOS 19.1 and use the storage and install LineageOS 20 official for Payton and MindTheGApps 13 because attached is pictures of me doing it
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] wkn000:
I will give it a try fpr me asap. :)
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] woodpe:
Unfortunately no temporarily boot in twrp-recovery, phone boots into system!
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] ThE_MarD:
@woodpe sorry I don't quite understand, are you trying like this?

fastboot boot twrp-3.7.0_12-0_UNOFFICIAL-20230101-03-payton.img
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] wkn000:
So, tested with new test build, but same issues as before.

Handy tries to boot TWRP but after a second reboots to system again. (as described by woodpe before)

Commands from Windows CMD:

adb devices

adb reboot bootloader

fastboot devices

fastboot boot twrp-3.7.0_12-0_UNOFFICIAL-20230101-03-payton.img

All without any error message there. Works same way with 3.6.2_11-0 flawlessly.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] woodpe:
Yes, that's exact the command I used.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] ThE_MarD:
Well I'm clueless then lol... Well if the older builds or TWRP work? Then the only other thing I can think of is the boorctrl but I don't think I can use A11 boorctrl in A12 L... Oh well, I guess for those with some weird device things going on they can stick with older TWRP builds as they work fine anyways for A11 to A13 anyways

I just noticed that @wkn000 is using Magisk... @woodpe are you also using Magisk? Not sure if this is potentially a culprit or not as I do not use Magisk (and I haven't in probably three years)
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] woodpe:
I'm using Magisk, too.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] woodpe:
@ThE_MarD :

Strange thing

fastboot boot twrp_old.img works

fastbot boot twrp_newest.img fails

but even

fastboot boot lineage20recovery.img fails!

Perhaps it's really because of Magisk!?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] wkn000:
Because of some issue in Updater, i had to reboot to installed Lineage recovery 20 to Apply update of LOS20.zip. That worked even with Magisk installed. Only thing was, that addons.d was not executed so Magisk got not reinitiated.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] ThE_MarD:
@woodpe yeah LOS 20 recovery should boot just fine... so it's either Magisk or something on your device is corrupt... so the fact that LOS 20 recovery doesn't work means something really odd is going on there...

@wkn000 , any device with A/B partitions and manually flashing a ROM zip? Releasetools will not run thus addon scripts are not used to backup/restore any mods. It's the same as installing any ROM zip manually. Flash it, reboot to recovery, reinstall GApps and any optional addons you have, reboot to system. It's because it always flashes to the inactive slot and the reboot to recovery is to allow it to swap slots properly.

When installing a ROM update via OTA updater in the system? At that point it can run releasetools and backup/restore mods as it can include them with the installation.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] mihaum:
Does encryption on LOS20 work for you?

I made a data backup on LOS19.1, but now (on LOS20) I cannot restore it, due the data not being decrypted.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] alecxs:
TWRP backup is not encrypted. Do you have formatted userdata before restoring backup? Try this workaround (untested)

https://xdaforums.com/t/question-an...r-restoring-twrp-backup.4565049/post-88287815
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] mihaum:
I cannot mount /data due the decryption issue, so I've just assumed I will not be able to restore.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] alecxs:
Then the red letters in OP apply. format userdata first ;)
[Touch Diamond, MDA Compact IV General] d3us:
Hi,

did anyone succeed in calling using the WM6 VoIP via 3G? I tried sipconfigtools and setup_voip0.3, the modified drivers for Diamond (http://xdaforums.com/showthread.php?t=415262) and the unmodified, nothing works... (I tried 2 sip accounts, they both work using Fring). Am I the only one in this case?
[Touch Diamond, MDA Compact IV General] htc-p3600:
I also I tried to install WM6 VoIP and setup Voip, but does not work very well. The problem is not only that does not work and you also freezes the internal antenna GPS and the only way to restore the proper functioning is a HARD RESET.

I lived on my skin and only after I read in other POST.

The only application, in my opinion, that works really well for the VOIP and the Chat as MSN, Skype, Twitter, etc. Gtalk. Fring is! It works very well on Diamond, also used on the P3600 and have always been happy.

I hope to be state aid.:D:rolleyes:
[Touch Diamond, MDA Compact IV General] hc_blacki:
Ask your mobile phone provider. I think he will tell you that they block some ports and you cant use voip over 3g.
[Touch Diamond, MDA Compact IV General] d3us:
No, VoIP works using Fring so it can't be this. But the quality of VoIP using Fring is not very good and all the others applications I have tried so far don't work properly (GoSIP, Skype, SJphone, Wengophone).