yashsingh1/xdaforums huggingface dataset:
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] igna.98:
Hi, I have a huge problem. I was on stock A1 8.0 ROM, and flashed 12th June build to test it.

Then I flashed retail 8.1 ROM. When I did so, a message that said "verity mode is set to logging" appeared before boot animation, but it booted so I ignored it.

Some days later, when 30th June build arrived, I tried to install it, but it didn't boot, so I thought that it had something to do with verity, I checked through TWRP file manager and saw that the ROM isn't installing properly: I noticed that all files and folders from root (/) had been copied into /system and there was a subfolder called /system with all the contents of the lineage ROM (so that folder was /system/system) and that's why it didn't boot. I tried moving /system/system files to /system and deleting the other files to see if that way it would boot, but it didn't, it kept rebooting to recovery.

I tried flashing A1 8.1 ROM and then lineage but results were the same. I also tried "adb disable-verity" on stock ROM but it wasn't allowed because it's not an userdebug build. So now I am now stuck on stock ROM.

Will I ever be able to install lineage again? :confused:
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] cupanoodle:
"verity mode is set to logging" showed up on my phone immediately after unlocking the bootloader and factory resetting. I haven't tried flashing back to stock yet, but I have gone from an older los build to the 6/30 build without the issue you are describing. Not sure how to fix your issue, but I'm not sure the "verity mode is set to logging" has anything to do with it.

I have an A1 XT1900-1
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] igna.98:
I thought it had something to do with that because that message hadn't appeared before. Or I may have a TWRP issue.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] DarkLara:
that message only comes out in version 28.1, I had to go back to version 27.57-40-14 and the message disappeared and he said again that the build is official.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] ArticFighter:
google play services has stopped

i installed all by your tutorial but google play services keeps crushing
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] munchy_cool:
1. LOS has been working for almost everyone, stuff going to system/system is absolutely normal. not sure why you are trying to experiment with your device and brick it by doing things you are not supposed to do.

2. backup your data, and follow stock rom. follow the instructions in OP.

https://xdaforums.com/moto-x4/how-to/guide-how-to-flash-official-factory-t3808348

3. follow the instructions in OP to flash LOS again. Read once, twice and as many times as you want so that you know what you are doing. Watch the video, it explains everything. If you follow the instructions to the T, you cannot fail. Those instructions are very detailed.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] munchy_cool:
which gapps did you use? looks like a gapps issue.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] igna.98:
The only thing that bricked it was installing 30th June build after stock 8.1. As I wrote, I had successfully installed 12th June build before, this time I did the same procedure but it didn't boot. Maybe I'll try again in another occasion, thanks anyway
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] ptn107:
I have xt1900-1 A1 on 8.1 stock and I get the same error. Has to do with 8.1. Nothing you can do to fix it right now. It doesn't affect functionality it's just ignore it. Has nothing to do with /system/system.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] brandontowey:
I'm in RR but had the same issue. I found that carrier services isn't installed by default, installed it from the store, and now WiFi calls work so far.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] djmastermix88:
reboot to recovery, go to wipe, custom wipes , and select format data, cache, and test again.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] as.hs:
not sure if you were able to get it fixed but my x4 had the same problem too. i solved it by going into fastboot and hitting bp tools (i think thats what it is called) and it will load the rom perfectly fine. i always worry about it happening if my phone shuts off for some reason but after hitting that option, it boots normally every time
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] MotoX4:
OP, thanks for this awesome ROM. Loving it. :)
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] fourbiscuits:
How noticeable is the echo? And it says that call volume can't be adjusted, is it at a high volume or low volume by default then?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] abrfilho:
I have a brazilian variant (XT1900-6) and I don't have echo, the volume is low, but you can hear without a problem if the ambient isn't noisy.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] kanishk1010:
Latest kernel for 8.1

Moto released the oreo 8.1 kernel earlier this month for moto x4 on github (MMI-OPW28.46-13). Could it solve the echo and low vol isuues?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] patruska:
I'm having an hard time getting it to work properly. I followed the instructions, I managed to boot the rom without gapps, but I cannot install any apk, the package installer doesn't crash or even open at all. I tried rooting and installing the f-droid apk manually by moving it to /system/priv-app via built-in terminal using sudo, but i got a message like "system read only". what did I do wrong?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] assmist:
Try install it through recovery or adb sideload
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] munchy_cool:
you need to mount the system in rw.

boot into twrp, mount system and use twrp file manager to move fdroid apk where you want to and set correct permissions and see if it works.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] JMandava:
All of a sudden thread became so silent ?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Cisencjusz:
i think it's baceuse the main developer [MENTION=6298645]erfanoabdi[/MENTION] is waiting to get the device in hand

https://xdaforums.com/moto-x4/how-to/lineageos-dev-erfanoabdia-moto-x4-t3808858
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] gee one:
Did anyone notice that the snap camera is pretty buffed up? The bokeh feature isn't working but the tracking focus is pretty amazing tech.

I think snap has been a few years in the making and it's really feature rich.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] LazyCountry:
[MENTION=921457]munchy_cool[/MENTION]

ROM : UnOfficial LineageOS payton 20180630

Why this is a userdebug version? not a user version？
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] munchy_cool:
it's unofficial, hence userdebug. also, why do you want a user build?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] DeadMeme:
VoLTE not working.

I've enabled the Enhanced LTE mode on my Moto x4, but it doesn't seem to turn VoLTE on. I've even reset the Access point of Jionet. Was told to attach logcat. I grabbed one enabling and disabling the Enhanced LTE option. Not able to post link because I'm a new account. I'll put the link in the youtube video. Thanks for the help! :)
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] munchy_cool:
[MENTION=9236850]DeadMeme[/MENTION]

here's your logcat - https://file.io/7obs86
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] LazyCountry:
[MENTION=921457]munchy_cool[/MENTION] When I close the developer options then reboot device, the adb connect PC again, the developer open again, I don't know this is userdebug version feature or bugs, I don't like this.

And I think the user version have better performance than user debug version.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] erfanoabdi:
new updated versions is out

* minor bug fixes

* volte bug fixes in dual sim device

* updated blobs to official 8.1

https://www.androidfilehost.com/?fid=5862345805528062600

-----------------------------------------------------------------------------------------

Full Treble Version :

* fully treblized

* wifi/video calling fixes

* minor volte bug fixes

* battery and performance optimization

Treble Lineage : https://www.androidfilehost.com/?fid=5862345805528063250

Treble TWRP : https://www.androidfilehost.com/?fid=5862345805528063210

Treble TWRP Installer : https://www.androidfilehost.com/?fid=5862345805528063564

**this is treble build and should be flashed ONLY with treble twrp**

FAQ:

Magisk?

- try magisk 16.7 if you want

GSIs?

- yes all GSIs is installable

P?

- yep follow AB flashing guide

ENJOY
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] DarkLara:
thanks, thanks...It works perfect.....very thankful...
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] abrfilho:
I already have LOS installed on my device, can I install the treble Lineage over mine as a update? What's the differences between the versions?

You update your phone or cleaned everything before the flash?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] valeriopastore20:
Is the in call echo still present?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] erfanoabdi:
You don't need to wipe if you are in lineage already, just flash treble version

(Backup just in case)

Need to be tested some users told me it's fixed in treble
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] igna.98:
[MENTION=6298645]erfanoabdi[/MENTION] camera isn't working in Android P
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] erfanoabdi:
I've updated post gsis with Payton camera fix included, should work in new versions

But need clean install from lineage

If you are looking for quick fix, mount vendor and flash this zip
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] DarkLara:
there is no echo in the treble version. Thanks....
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] abrfilho:
Flashed, but a lot of apps crashes, SoundCloud, Camera and some GApps doesn't open, I'll wipe to see if everything works fine.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] DarkLara:
the volume works on calls in the treble version.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] munchy_cool:
P installation video and thread coming soon.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] abrfilho:
I did a factory reset, now I'm not having any crashes, but I'm getting ctsProfile: false on Magisk SafetyNet check, I'm looking for a way to fix that.

I'm using Magisk v16.7.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] assmist:
The echo is gone in the treble rom :)

I have an other issue though that have existed from the first release i think.

When switching user, the on-screen nav bar dissapears, and i have to go to settings and disable then re-enable it. I have my phone setup with a work user and a private user to keep it seperated.

Thanks!
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Neffy27:
I'll add it to FAQs thread.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] munchy_cool:
thanks buddy :)
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] munchy_cool:
yeah man, sorry today but I dont know how to sign builds with user keys. you may have to do your own builds if you want user builds.

PS:- performance wise both are same.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] radjad:
I'm not passing CTS on Safetynet on the Treble version. Is that normal?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] DarkLara:
test this worked for me, fix the certificate and safetynet check

https://xdaforums.com/apps/magisk/q...gisk-v13-3-t3800435/post77044632#post77044632
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] gee one:
You can sign your own builds.

https://wiki.lineageos.org/signing_builds.html

It's not for the faint of heart, and probably doesn't make sense unless you lock the bootloader too, which is highly NOT recommended. I re-locked my bootloader and I suggest that you do NOT do it.

You can also make your own builds and change the keys. This is easier than signing with release keys and achieves similar effects.

Other than performance, what are you trying to achieve with the user build?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] radjad:
Does anything but Pixel support arbitrary keys for locked bootloaders now? It used to not be the case, but I do like the sound of secure boot in return for a build script.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] gee one:
You can change the ROM keys and the verity keys in the build. If you re-lock the bootloader, you'lll get the yellow warning and it will show you the sha256 fingerprint of the verity key. This will let you detect if you are booting a different kernel, is, etc.

As far as I know, you can't change the hardware OEM keys on Payton, although there do appear to be some certs in the bootloader. There are also signatures that will probably break the bootloader if the certs are changed/modified.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] EudeRabelo:
My impression xt1900-6

I do not know if it's my impression, but it looks like the battery was discharging faster with 15 and I reinstalled the stock rom

But I liked version 15
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] erfanoabdi:
new treble build : https://www.androidfilehost.com/?fid=5862345805528066114

* safety net fixed

* screen DPI fixed in some apps

* more speaker fixes...

ENJOY
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] andriygamal10@gmail.com:
Do we need to repeat the entire installation process?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] abrfilho:
Just do the update process.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] munchy_cool:
OP updated. Please use treble TWRP zip and image even for updating.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] krossifix:
xt-1900-2 - able to install 04 Aug treble version with treble twrp (followed guide as updated on OP).

rebooted to android, skipped setups - rebooted back to recovery flashed Magisk v16 (Stable version as linked on OP) but cannot get the device working after this.

Device keeps restarting. im not sure what im doing wrong.

searched the thread for a solution on this but couldnt find any. could someone pls shed some light on this..
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] abrfilho:
Stable Magisk? Try with that versio: https://xdaforums.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589

Magisk compatibility with Treble came with BETA 16.6.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] krossifix:
that worked!! thanks [MENTION=8834019]abrfilho[/MENTION]

a 3 hour struggle finally came to an end. now that you shared which version works, post number #247 by erfan also makes sense. Wish i had seen that earlier.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] munchy_cool:
sorry, my bad ..i didnt update OP with correct Magisk ..done now.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] dvvaldivia:
Volume working

Well, the volume issue is fixed now, and no more eco on my XT1900-6 dual sim

the only issue im having is that im unable to see my signal bar for my second sim, it shows my second sim as disabled but it is working im able to receive calls and messages, so its not a big deal.

Thank you for your hard work :)
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] MeowDotEXE:
Just installed, and it works great. I spent 10 minutes trying to figure out why Fi wouldn't activate, just to find out I'm an idiot and that I didn't give it any permissions. However, the sound does seem a bit quieter compared to stock.

Also, why are there 3 clocks on the top bar by default?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] abrfilho:
The three clocks appeared here too, after a restart only one, as intended, remained.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] JMandava:
So since we got treble build, Can we flash gsi over this ?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] munchy_cool:
https://xdaforums.com/moto-x4/development/treble-android-p-dp5-moto-x4-t3823878
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] MeowDotEXE:
After around a day of use, I've noticed a few things.

1. Haptic feedback (keyboard typing, nav buttons) isn't as strong as it is in stock. Notifications aren't affected. This could be intentional(?)

2. PiP things start out inside the navbar, instead of above it. Probably just a minor bug.

3. There is no option that makes the display exactly the same DPI as stock Android. It's either way too big, or slightly too small.

4. Sound is definitely quieter than normal, but can be easily fixed using the ViPER4Android FX Magisk module and setting the output gain to +6DB.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] MeowDotEXE:
Also, I can't seem to use Sprint on Fi.

It takes an unusually long amount of time, then it connects to LTE, but there's a small X near the signal indicator and after around 10 seconds it disconnects again. T-Mobile works perfectly and I can't test US Cell because they don't have signal here.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] murrty:
Second, might be the modem but I'd need to test it.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] talia005:
Speaking of things not working on Fi, since installing this ROM I've been unable to activate Project Fi with an error code G003 with text "Unfortunately, your Project Fi service can't be activated because your account currently isn't authorized for service". I searched the internet and I didn't really find anything, and I contacted Fi support and the person who I was talking to was clueless (I asked if it was related to my phone's software or an error on Google's end and the response was "There is something seems to be an error.") and my case was escalated.

Upon looking at the logcat immediately following hitting the retry button, it's probably something on the phone's end...

Previously I tried running an RR ROM (the 070118 version) and Fi activated okay.

One thing I should probably mention is that I disabled data encryption (per the twrp xda page), but I tried running this ROM before that and it didn't work with it encrypted either.

I've gone through the paces of flashing stock again, factory wiping over and over, etc and I'm just stuck
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] MeowDotEXE:
Make sure you enable all permissions for the Fi app. I had the exact same error and that fixed it.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] talia005:
I swear I had checked that first because I had a similar error like a year ago! Apparently not, so it's working now. Thanks!
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] murrty:
I looked into it, stock ROM has LTE because I'm pretty sure Sprint applications are required for it to work properly, so. I don't know if Sprint offers the files to flash onto the system.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] MeowDotEXE:
I only said Sprint because I'm not able to test US Cell. Can someone who has coverage from them please see if you can connect?

<SPECULATION>Is SprintDM included in the ROM? Could it be required? I'm not able to test until tomorrow.</SPECULATION>
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] murrty:
I am not sure for Lineage because it kept giving an error while trying to flash, but I did get CarbonROM installed. It did not have SprintDM and has LTE issues.

I have a Moto G4 Plus with a custom ROM does have SprintDM and had LTE access.

Now, if only I can get xposed working on this thing....
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] MeowDotEXE:
I can confirm that SprintDM is not included. Is there any good way to install it?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] murrty:
My best thought would be, back it up from stock with like Titanium Backup and then manually install the APK through a file manager. If that doesn't work then, I dunno.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] MeowDotEXE:
It doesn't work. Using an APK extracted from a stock Moto X4, I get this error:

Failure [INSTALL_FAILED_SHARED_USER_INCOMPATIBLE: Package couldn't be installed in /data/app/com.android.sdm.plugins.sprintdm-CYfiQG7t9neC6-ffGlHKcw==: Package com.android.sdm.plugins.sprintdm has no signatures that match those in shared user android.uid.phone; ignoring!]

I also tried one extracted from a Nexus 5X running Lineage os, but got the same error.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] fubar73:
I am having the same recurring problem and I was hoping someone could help. When I try to install this rom I keep getting: Updater process ended with ERROR: 1 Error installing zip file. If anyone has any idea what this could be please let me know. Using latest version of twrp and bootloader is unlocked. I have no idea. Thanks.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] talia005:
I've run into this error several times trying to dirty flash the image. Are you getting the error flashing from clean stock? (Also make sure you're on slot A)
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] fubar73:
Yes I am on slot A. I am at a total loss. What did you do to fix this?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] talia005:
I just flashed the stock image with the flash-all.sh script (or flash-all.bat if you're on Windows) per the original instructions. In fact I literally just ran into this problem 15 minutes ago, flashed stock, and I'm up and running again.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] fubar73:
Yes I have tried that as well. I am on a xt1900-1 variant if that makes a difference. Maybe you could link me to that stock you flashed.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] talia005:
I flashed Fi version OPW28.46-13 from here, but I can't speak for any of the other firmwares there (Retail/Amazon).

Edit: I also just ran into a problem where it was complaining that none of my partitions existed (system__a, modem__a, etc) and I solved this by manually changing the flash-all.sh script to reference "system_a" etc. instead of just "system" etc. I only changed the ones that were actually flashing something, though, because the erase commands weren't dying, and nor was system_b. I'm sure there's a more elegant way to do this, but it worked and that's all I needed

---------- Post added at 09:23 AM ---------- Previous post was at 09:13 AM ----------

Here's a question for someone who knows more than me (Idk a ton :p) Are these builds built off the latest firmware w/ security patches or do they rely on the underlying stock image we flash over to have the latest updates. I.e. if I flash 28.46-13 but the latest is 28.46-21, do I need to reflash -21 stock to get the latest Android update or are they rolled into the ROM image incrementally like a standard OTA?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] fubar73:
Yea I'm still having the same problem. In fact any rom I try to flash with twrp gives me a error. Very strange. Thanks for help though.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] dan.goga:
I was getting this error. I found that if I fastboot into the twrp image file (the one specifically for treble) , I was able to flash the roms with no problem.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] abrfilho:
I have the same problem here, everytime I get the same error when I try to flash a ROM, I can only flash through the TWRP bootable img.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] fubar73:
I actually got it to flash by doing exactly that. Also may have been the version of twrp i was using. Used the version here and all went ok. Everything is workin great. Rom is excellent. It always amazes me how moto (although much less than others) take features away from android and you don't realize it til you install a custom rom. So basic yet nothing is missing.

Great job Lineage team.