yashsingh1/xdaforums huggingface dataset:
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] MotoX4:
To clarify what to do with "4G LTE Switcher" and improve Project FI connections see this post: https://xdaforums.com/showpost.php?p=77979521&postcount=39

It's 5 am. You'll please forgive me if I don't type it all out again. :eek:

But this should help some of you here using Lineage 15.1 as it did with me too.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] soup can:
Hello, I've been using this ROM for a few weeks now and it's working great, there are no major issues that break the phone (aside from OTA updates obviously). There are still a few issues I'd like to report, however.

1) AudioFX app doesn't work, no difference in audio whether on or off

2)FM Radio app recording doesn't work; a file is made but it appears to not contain anything and "Stop Recording" stays grayed out

3) Unable to edit hosts file (using AdAway) and build.prop. It seems that I can't modify /system even with the official LineageOS root package.

If it makes any difference, my phone's model is XT1900-1.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] user9192:
Hi There, i have the same Problem.

one thing that is not working either ist Fingerprint.

i can't even find it in the settings...

any ideass?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] carsten87:
Had this issue, too. Problem is that /system is mounted read-only. To solve the problem you need to remount /system with write access. I did this via adb.

1. Allow root over adb in developer options.

2. On your PC open a shell and run 'adb root' to get an adb root shell.

3. Run 'adb remount', which will remount /system with write access. (See https://stackoverflow.com/questions/28961572/what-does-adb-remount-do-when-is-it-useful for more info on adb remount command.)

Maybe a reboot is required, not sure... But editing hosts files will now work as expected.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] soup can:
Thanks, that worked just fine. AdAway was able to edit hosts and I was able to modify build.prop.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] plgmfrs:
I installed Lineage OS according to this (https://wiki.lineageos.org/devices/payton/install) on my Moto X4.

When i installed the lineage zip file it said "Skipping Digest check: no Digest file found". When i rebooted afterwards it said no OS installed but i ignored it, then it seemed to be a hard brick, my phone didn't do anything. It only showed up as Qualcomm HS-USB QDLoader 9008 (COM #) or something similar in my PC's devices manager.

I then got it to boot to bootloader with blankflash.bat (https://xdaforums.com/moto-x4/development/rom-lineage-os-15-1-t3802265/page61#post77847019).

Next i reinstalled twrp and tried installing Lineage OS again but it showed the same old no digest file error so i didn't reboot afterwards. I installed/reinstalled various drivers and also tried putting cwm on it like described here (https://xdaforums.com/crossdevice-dev/android-one-crossdevice-development-original-android-development/recovery-clockworkmod-recovery-6-0-5-1-t2885736). But the "fastboot flash recovery recovery.img" command didn't work, I think it said no partition "recovery".

Since then i've been rebooting to bootloader/twrp and reinstalling drivers and so on and now i somehow am stuck in the bootloader and can't flash twrp with "fastboot boot twrp-3.2.3-1-payton.img" command. It says "(bootloader) Failed to load/authenticate boot image: Not Found" and "FAILED (remote failure)". Command "fastboot devices" in cmd does find the device, "adb devices" doesn't. Devices manager on PC only seems to show "Android Device > Motorola ADB Interface". Rebooting the phone brings me to Bootloader logs now, see attached image.

https://imgur.com/a/kcooIrN

What can i do now?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] JMandava:
Dude why did you mess up so much and none of the steps you followed belong to A/B devices. Moto x4 is an A/B DEVICE and if you are coming from stock please follow the steps in post 1.

Please check if you are booting twrp from your fastboot directory of your pc. As your device is being recognised, it should be problem with location of twrp file.

ADB works only if you have the system booted up(provided you enable ADB in developer options) or in a custom recovery like twrp. Why would you need ADB in bootloader mode? You won't be having any success with ADB commands in bootloader mode ?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] mensch72:
Stuck on login screen (both LineageOS and restored original system)

Dear all, with my brandnew X4 I followed the instructions to the point (at least I think so), but Lineage wouldn't boot. Instead it gave the "can't load android system" error when trying to boot. When installing the copy partitions zip and trying to wipe dalvik/cache afterwards, I think I saw a message saying that /cache was not found.

Then I tried to restore the backup of the original system+boot+data partitions I made with TWRP, but although the restore went without error, the system still doesn't boot, this time not even showing an error, just hanging on the boot screen forever. Also "factory reset" (wiping data) does not help.

Help - what can I do to get any working system back?

Could it be that something with the copy partitions went wrong and now the partition table is corrupt? Could it be an issue with the A/B slot stuff (which I don't quite understand)? Is it a good idea to restore other partitions that I backed up (vendor, vendor image, etc.)?

twrp-3.2.3-1-payton.img

lineage-15.1-20181023-nightly-payton-signed.zip

SOLUTION:

While I could reproduce the effect when using the procedure as described in the first post of this thread WITHOUT installing TWRP (only using fastboot), the problem was solved immediately when going through it all again WITH the optional step of installing TWRP!
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] edhunterbg:
Hello mr. [MENTION=6298645]erfanoabdi[/MENTION]

Has second sim issue been fixed? I am trying to understand the change entries from lineageoslog.com for our device, but dont understand most of them. Do we have some kind of more user friendly list of issues or fixes?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] lazy-o:
Just tried it with 20181030 update. Everything google keep crashing, again.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] assmist:
have anyone tried the lates update via OTA? if so, did it work?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] abrfilho:
I think you'll need to wipe your data...

When I was using the unnoficial version, the procedure to install an update was:

-Dirty flash ROM with twrp

-Reboot recovery

-Flash GApps and Magisk, if you want

-Wipe Dalvik

-Reboot system.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] p-ho:
Have tried 20181030-update via OTA:

Bricked again after reboot

Boot to system was eventually possible through blankflash-utility
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] mkfsf2fs:
First of all, thank you [MENTION=6298645]erfanoabdi[/MENTION] for putting so much effort into this ROM :)

[MENTION=610992]edhunterbg[/MENTION] , I am also using a dual sim setup. My problem is similar - my second SIM is half-way grayed out. I have tried to use each SIM separately and that works perfectly.

Only if I try to use both, the second SIM is not recognized.

(SIM1 has no PIN | SIM2 has a PIN)

What happens exactly is:

- I slide in the two cards

- SIM1 seems to be recognized

- SIM2 shows the PIN-entering screen

- While typing (or not) the window suddenly disappears.

I'll try to generate some useful logfiles soon and hope that I can find something...
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] uniquer4ven:
Bug Wifi not working

Hi,

I have a completely new phone (unpacked and lineaged).

- I am not able to connect to a WiFi Hotspot, neither with Passphrase nor with WPSPushButton. Any idea what I could try? Can I provide further information on this and how exactly?

- The System takes 12GB of memory, does the procedure provided delete the former OS, or performs some kind of formatting of the memory?

- The browser of lineageOS immediately crashes.

Cheers
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] plgmfrs:
Downloading stock firmware and running "fastboot flash partition gpt.bin" (first command of https://xdaforums.com/moto-x4/development/flash-official-frmware-moto-x4-t3730750) apparently fixed the partitions and bootloader, so i booted twrp again, installed the copy partitions zip, formatted data and sideloaded the LineageOS weekly.

As before it said "Skipping Digest check: no Digest file found" then did step 1/2 and step 2/2, showing an indeterminate progress bar during step 1/2 which soon stops moving and is completely blue for some time. When i wanted to reboot it also said "no OS" again so i did all the commands to install stock firmware instead. Now i have a working OS but i'd still like to install LineageOS. Any ideas why it doesn't work?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] lazy-o:
That is the problem. Having to wipe everything in every update. On victara I used to just do a dirty flash and that is it. It is working.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] abrfilho:
Wipe data only if Google apps keep crashing.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] lazy-o:
Since I installed LOS I have to wipe data in every update. It always make google apps crash. On next update I'll try to wipe dalvik only to see if it helps
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] TadMSTR:
I installed LineagOS and have done one update since. I did not need to wipe anything, including dalvik/cache. I did update opengapps when I did the ROM update. Maybe it's an issue with the gapps package/version you are using?

Here is my update process. Assuming you installed ROM to slot B like initial instructions show.

1. Boot to recovery. (should be on slot B)

2. Change to slot A and reboot to recovery.

3. Flash latest LineageOS and TWRP. (installs ROM to slot B and TWRP to both)

4. Change to slot B and reboot to recovery.

5. Flash latest opengapps and Magisk. (installs gapps and magisk to slot B)

6. Reboot into Android. (you can wipe dalvik/cache before rebooting if you want but it should not be needed)

I get errors when trying to change slots from recovery so I need to do that from bootloader using fastboot commands. Most should be able to change slots from recovery so that's how I listed the process. Also I use the pico opengapps package.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] lazy-o:
I followed the first tutorial and everything work great, but when I reboot to recovery I never noticed the slot. Now I just tested and went to A. Maybe that is the problem? Should I follow your steps only changing A->B and B->A?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] TadMSTR:
When you are in slot A, which is default for stock, and you flash LineageOS its actually installing to slot B. The end of that process then changes the active slot to B. So when you reboot you are now running from slot B and the stock OS is still in slot A. Only the ROM zip installs to the opposite slot from what is active and then changes the active slot. That is why after flashing the ROM you need to reboot back to recovery if you want to flash gapps and/or magisk. Reboots are needed to actually switch the active slot, just selecting it in recovery is not enough. So if you installed LineageOS into slot A instead of B (following the tutorial would have had the ROM installed in B) then just reverse the letters in the steps I listed.

You can have two different ROMs in the slots but they share data. So if you want to switch from one ROM to the other you can change the active slot in recovery and reboot. However, you will need to wipe data or else you will most likely have errors. That is probably what is happening to you. Always remember to change to the opposite slot when flashing an update. If running Linage from slot B then always change to slot A to flash update, then reboot to recovery to install gapps and magisk (or just reboot if you don't need to update either). Reverse the letters if you are running Lineage from A. You can flash TWRP zip from either slot as TWRP will install to both. Always flash TWRP zip after flashing Lineage update so you don't lose TWRP recovery.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] lazy-o:
Thanks a lot for all explanation! All this slot thing makes sense now :)
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] JMandava:
Haha, it says that no OS is installed , I faced the same. No problem it is is actually installed ;) You can proceed with further steps like installing gapps and all. You will have your los mate :)
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] zerolam:
Hello everyone

Could some one tell me how the "copy partition.zip" affect the installation when the device comes from stock.

And does the firmware provided in the post include os/boot partition?

Understanding the steps will help me to flash without error.

Thank you
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] TadMSTR:
The Moto X4 uses the A/B slot setup that Google introduced with the Pixel. However, Motorola decided to only setup the partitions in slot A. The copy partition zip copies the partitions from slot A into slot B. This allows you to now flash/install a ROM into slot B. Without flashing copy partitions zip I'm not sure you would even be able to change to slot B. You definitely would not be able to flash anything to it.

ROMs should include everything needed to boot into the OS. Lineage includes boot, system, and recovery. If you don't want to use Lineage recovery then you need to flash the TWRP zip after flashing Lineage, even after just flashing an update. So technically all you need is the Lineage zip to have a fully functioning Android OS. However, you will most likely also want gapps. You should be good following the tutorial in the beginning of this thread. For applying updates see my post above.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] uniquer4ven:
Hey guys, could you please tell me, how much memory I should have left after installing lineageOS (and maybe OpenGapps mini)? How can I make sure, that there is no old trash left from the former ROM and thus maximize the available space? Thanks ...

PS: Upon wipe I seem not to be able to mount data (failed with invalid argument) and storage (unable to mount), any ideas here? Is that necessary? CopyPartitions.zip shows me the same ...
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] TadMSTR:
I assume by memory you mean storage space? Partition sizes won't change no matter how much of it is actually used. The OS and gapps get installed into \system. A copy of gapps also goes into \data upon first boot and then any updates from the Play Store go in \data as well. So when you factory reset or wipe data the OS grabs a copy from \system and puts it into \data. When you install Lineage it actually wipes \system before installing. Though it does make a copy of the gapps in \system before wiping then restores them. Because of that you don't have to flash gapps when you just want to update the ROM.

As for what you did I don't know what you wiped so can't really answer that without more info. Remember this device has two slots for system so be aware of which slot you installed Linage to and which slot is currently active. There are fastboot commands to check active slot and you can also look in the Reboot menu in TWRP recovery.

If you need to start over there are forum posts for flashing the stock firmware. However, as long as you can boot into TWRP recovery you can probably fix. Check which slot is active from the Reboot menu. Then flash Lineage and TWRP zips. Reboot back to recovery (you must do this before flashing anything else). Flash gapps, and Magisk if you want root. Do a factory reset from TWRP (just use the slider in the Wipe menu). Then restart and wait for the OS to fully boot. Next time you go into recovery check the active slot and you should now be in the opposite slot. So if you start in slot A you will now be in slot B, and vice versa. See my post above about how slots work.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] user9192:
Finally I found a solution.

I forgot to install Firmware (as described, but hidden in post #2)

That was really hard to find out!

I guess I am not the only one who did not realize that additional steps!

Refering to this reddit this seems quite common, so perhaps you could make the installation description more clear at this point.

Where ich found really helpful information, was the install guide for unofficial LOS 16.0

to the point: must install Firmware via fastboot between installation of "copy partitions" and Lineage OS Image

[LIST]
[*]Now INSTALL "Copy Partitions Zip"
[*] Reboot to your bootloader. - Stay at the bootloader screen (do not load TWRP)
[*] Download the firmware for your phone (find links in post [URL="https://xdaforums.com/showpost.php?p=77490529&postcount=2"]#2[/URL]

[*] Unzip (firmware) on your computer.
[*] Use flash_all.bat (found in the unzipped files) if on windows as administrator OR ./flash_all.sh if on Linux as root.
[*] Reboot your phone to bootloader
[*] Reboot your device to bootloader and reuse the previous fastboot command to load TWRP listed above.
[/LIST]

Now my device is up and running, no issues found so far.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] uniquer4ven:
Yes, storage space ... so ~19GB is max I assume after your explanation?

I wiped everything (system, dalvik, data and internal storage), installed the firmware provided on post 2, restarted into TWRP and tried to install copypartitionspayton.zip with the afore mentioned errors with mounting data and storage. Same after slot change under "reboot" or reboot into TWRP.

:confused:
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] TadMSTR:
Looking at my Moto X4 using the Diskinfo app these are the partition sizes.

\system 3.8 GB (because 2 slots there are 2 \system but you can only see one at a time)

\data 18.9 GB

The rest is cache/dalvik/swap

As for your issue with copy partitions zip I'm not sure. Try restoring stock firmware (there is a post for that somewhere) then follow the tutorial without wiping everything. You should only need to wipe data and dalvik/cache or just use the factory reset option. I believe TWRP recovery relies on how Android mounted the various partitions, depending on what you are doing. Wiping everything could potentially be breaking something.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] zerolam:
Thank you for the detailed reply

And sorry for my bad English

The firmware I said is this

https://xdaforums.com/showpost.php?p=77490529&postcount=2

Because I saw the installation is to flash lineage os over the firmware.

If the firmware includes os/boot, does this mean it is a dirt flash?

If not, that is what I learned.

Also, I find there is a firmware for xt1900-2

https://xdaforums.com/moto-x4/development/official-firmware-moto-x4-xt1900-02-t3831939

Can I flash this firmware for xt1900-2 instead of xt1900-1?

Thank you so much
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] TadMSTR:
Dirty flash means not doing a factory reset when flashing the ROM. If you are coming from stock then you always need to do a factory reset. Also changing from one ROM to another will need a factory reset. If just flashing an update to Lineage you don't need to factory reset or wipe dalvik/cache (though many people do opt to wipe dalvik/cache when updating the ROM). A lot of people will call that a dirty flash. In any case the factory reset is the most you will ever need to worry about. You will almost never need to manually wipe \system as ROM installs will wipe/overwrite what it needs to.

Also, factory reset won't wipe internal storage, which is separate from data (apps and settings).

ROMs can usually be installed on any model variant. However, when restoring stock you always want to use the firmware labeled for your model. So if you have an xt1900-1 then use the firmware labeled for that. When restoring stock firmware the process will fully wipe the phone and bring it back to stock condition. They come with a script that will run all the commands for you. Usually called "flash-all.bat" or something like that.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] amirite:
Hi all - sorry if the answer is someplace obvious but are OTA updates still not working? Got another update notification but have been holding off on any updates.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] zerolam:
Thank you, thank you so much

One more question

I have a new motor x4 (xt1900-2), the bootloader is unlocked now and I am about to unlock it.

Is this possible to make the firmware by myself for the use of installing lineage?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] vidra:
Does the wide angle camera and 4K recording work?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] uniquer4ven:
NFC impaired, fix possible?

Hi,

1. the apps I want to use the NFC chip with are telling me, they can't work with it, as it does not support Extended Lenght. As I believe to have heard, that moto x4 DOES support extended length NFC on the hardware side, I was wondering, whether you [MENTION=6298645]erfanoabdi[/MENTION]) can and want to do something about it?.

That would be great ...

2. when having VLC paused in the background (ready for pluging in headphones and continue listening) it keeps getting closed. This is quite annoying. Anybody an idea, what can be done about it?

Apart from that so far the last build works fine, thank you [MENTION=6298645]erfanoabdi[/MENTION]!

Cheers
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Droidge:
Works with the Moto Camera app off the Play Store, although you won’t get portrait mode out of the box.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] guibyn:
After about 2 months using LOS, today i got a notification about a new version so i proceded to update via the original updater from LOS, after that i tapped "Reboot" and now my phone wont turn on again, not even on bootloader, how can i fix it?

Edit: usb wont work on my laptop, when connected to charger, won't to anything also. when last used, phone battery was at about 80%
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] gee one:
This sounds like the QDL download mode. You might have to use the blankflash tool to restore it to a bootable state.

If you are on linux, try lsusb to see if it shows up when plugged in.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] guibyn:
Thanks for the advice, i'll try that when i get home. I just got one question, when its on QDL is it normal not to show absolutelly nothing on screen?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] cango123:
Yes it's normal
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] azazelcrey:
LOS 15 NO DATA Project Fi

So I've flashed the firmware provided from munchycool 1900-1 for my fi moto x4 and installed LOS15 and Gapps/magisk, ive set all the permissions in the Fi app but still cannot get it to connect has anyone got any insight? Did anyone have connectivity issues with Project fi and LOS15?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] guibyn:
It's not showing up anything on screen and also it's not being recognized on the pc, all software on the computer are working fine and drivers are updated, is there anything i can do?

i have googled some blank flash files and stock firmware, the only problem left is making the phone talk to the computer
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] gee one:
It might truly be bricked. I think there are some diagnostic things you can try- on linux, use lsusb. There might be something on windows, but that's above my pay grade. Maybe see if it shows up as a qualcom gobi QDL 9008 something or other in the devices menu. Again, lsusb works for me.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Samyantak:
Does 4g volte calling and cellular network works normally