yashsingh1/xdaforums huggingface dataset:
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Demoniackers:
Should I do that? There is no other solution?

### SOLVED ###

Blankflash: https://drive.google.com/file/d/1wfNOTMquSJFcCjCtaxf1lrSPVABm9XTS/view

Drivers: https://motorola-global-en-aus.custhelp.com/app/answers/prod_detail/a_id/86934/p/154,4222

Make your PC into Test Mode.

Then run “CMD” or “Windows Terminal” as administrator and type:

bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS

bcdedit -set TESTSIGNING ON

(Restart computer)

***When you no longer need it.***

###To deactivate it we will use the following command.###

Bcdedit.exe -set loadoptions ENABLE_INTEGRITY_CHECKS

Bcdedit.exe -set TESTSIGNING OFF

Once the two commands have been executed, we must restart our computer so that the changes take effect and this mode is deactivated correctly.

If you do not detect it as Qualcomm HS-USB QDLoader 9008 using Moto device manager, you can download the following drivers.

QualcommDrv.zip: https://gsmusbdrivers.com/download/android-qualcomm-usb-driver/

Extract to an empty folder, then open the folder according to your Windows type (x64 or x86) and double click dpinst64.exe (if you have 64-bit Windows) to install the Qualcomm driver

Now please connect your Qualcomm Mobile to PC or laptop Your phone should now being detected as “Qualcomm HS-USB QDLoader 9008” (please check it through Windows’ “Device Manager”). Tts not detected, then you can keep mobile connecting to computer and press power button and volume down button.

Now you have your mobile connected to computer, now follow the below steps.

Please download zip " blankflash1.zip" from location here extract it your computer and goto extracted folder and click blank-flash.bat

It will start in command prompt and detect device on your computer port.

If process completed successful then your mobile will restart into bootloader screen and your hard brick problem has been resolved. after that you can reboot into recovery by pressing power and volume down button again if required. Once you are in recovery mode then you can flash correct stock ROM into your mobile.

(If when loading software, it shuts down, charge your phone)

Try more than 3 times, have patience. :)
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] JensKuehnel:
Hi,

I have the same problem. Looks like the update to 20181009 is broken.

I updated it from 20181002 and I have a xt1900-7.

How did you use this blankflash tool . I tried holding down Power and vol+ or vol- during pluging in or during startup of the program. What ever I tried it did not help.

Have you use the Windows oder Linux version of the tool?

how did you do it?

At least it is on my xt1900-7.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] zrex:
How did you fix this?

EDIT: Followed the #513, is there a way to update to OTA
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] reedc83:
I am running Windows 10. I held volume (+) and the power button at the same time while I clicked on the blankflash.bat file. It ran quickly and put me into bootloader mode where I was able to re-flash the latest 20181009 version. One thing I had to do after install to get it to boot was boot to recovery using fastboot. >fastboot boot twrp.img Then tap on REBOOT, SLOT A, then Reboot System. The system actually booted instead of bootlooping. The only real issue I am having now is the camera app is crashing and I still do not have LTE on Sprint or US Cellular (Project Fi customer). Looks like I may try version 16 as it seems to have LTE fixed for CDMA networks.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] jf.navica:
https://xdaforums.com/showpost.php?p=77760388&postcount=531

Hopefully, the next OTA will be fixed.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] FTL_Ian:
After trying the "upgrade" and having the phone go into a boot loop, I was able to make it work again with the above, though this line failed with a "preflash validation error:

[*]fastboot flash bootloader bootloader.img

Didn't matter. Apparently that line was not necessary to fix the problem!

I just did:

[*]fastboot flash partition gpt.bin

[*]fastboot reboot-bootloader

and rebooted - success!
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] JensKuehnel:
I tried it first with Linux multiple times no luck. Than I rebooted into Windows 7 and tried it there. No luck there as well. I tried it around 10 times, and at the 11th it is finally working. I didn't do anything different as far as I can see. Try to press Power+VolUP at the same time as starting the program. Maybe that was what helped.

So if anybody does not succeed in the first try. Retry if very often!! :)

CU

Jens
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] thoklu:
On the offical side

I think, it is very import for "normal" user to have an information of the problem with the upgrade on the official side of lineageOS for Moto x4.

If this information we will lose all normal user.

Is there a way to do it?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] carsten87:
After trying to update this morning, my X4 (XT1900-7) does not boot LOS anymore, but goes to bootloader instead. There it says:

AP Fastboot Flash Mode (Secure)
SSM: abl csv roll back 1,128
Failed to boot Linux, falling back to fastboot
Fastboot Reason: Fall-Through from normal boot mode

For what ever reason, ADB is disabled and bootloader locked :confused:

Fastboot can see the device (ADB can't), but since the bootloader is locked again (how is that possible at all?), I am not able to temporarily boot a custom recovery and re-flash. Running

fastboot --set-active=b

Fastboot tells me

Slot b does not exist. supported slots are:
_a

Also I am not able to get to recovery (LOS recovery I assume; didn't install any custom recovery) anymore, it always falls back to fastboot.

To install LOS (lineage-15.1-20181002-nightly-payton-signed.zip) I followed the official instructions on LOS Devices page for the Moto X4. Also I installed GApps (MindTheGapps-8.1.0-arm-20180808_153837.zip) and addonsu-15.1-arm64-signed.zip. No Problems before the update.

Any ideas from here? My PC is running Ubuntu 18.04 but I could use Windows, too, if necessary.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] jhedfors:
Edit: You should not need to flash everything as I did to get back.

See this:
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] carsten87:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader

Is this possible when bootloader is locked? :confused:

Edit 0:

Tried it, first command (fastboot flash partition gpt.bin) works, second command (fastboot flash bootloader bootloader.img) fails:

$ fastboot flash bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader' (9520 KB)...
OKAY [ 0.608s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.658s
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] jhedfors:
Perhaps you should try a different cable or USB port?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Z3RO2K:
OTA updates are not working correctly. The past two nightly updates have made my phone unusable.

First update (2018-10-02) it broke the bootloader which was fixed by changing partitions but had constant Google service crashes and half of the apps would not work like Google maps and Google home even after re-flashing Gapps.

Now today's update (2018-10-09) - phone won't turn on correctly. The Motorola logo pops up for half a second and then turns off so going to have to wipe again and start fresh.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Jordanegs2:
Does the fast charge work?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] smmankad:
It appears so. I went from 43% to 88% in 20-ish min.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] igna.98:
However, it may be a lineage bug, because I also have a Samsung Galaxy tab S2 SM-T810 with lineage os 15.1 and headphones don't work there too, while they used to work in Samsung's stock rom (I didn't tested them in Moto's stock rom). They are Sony MDRZX100B, bought in 2012.

Another user told that his headphones work in lineage 15.1 on his tablet. Maybe mine don't work because they are old.

I think that more users should test with various headphones and report to confirm if it's a bug.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] munchy_cool:
the second fastboot -w?

list the steps you did here.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] krossifix:
Absolutely amazing.. a custom rom for x4 is finally here. What more can this community ask for.

Will be testing this on xt1900-2
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] abhi212b:
Hey thanks for checking in.. Sorry i got late.. Its 1 am here.. Finally pulled it off...

I was stuck at 1st fastboot -w..

I reflashed stock and then started again... Flashed flash_all.bat... Rebooted.. Then fastboot -w.. Then reboot.. And everything else you showed on the video!

I think we need total stock without root or xposed to do this.. Nd i had both magisk and xposed in my phone!

I had one q though.. This is only flashed on one of the system partitions right? What about the other one.. Is this like dual boot.? :p one lineage and another stock or any other rom?

Bugs - audio is a problem! No earphones detected!

Weather widget doesn't show weather source...

It seems twrp is not able to decrypt, so I am not able to use fingerprint..

I am not sure.. This is just 1st look..

Thank you so much for all your hardwork... Keep em coming!! :D :D

Have installed magisk with modules... On 1900-2..working perfectly.!! Will report back in case of any problems!! :)

I am really a big fan of led.. I am not sure if it works perfectly... But it seems to be working... :D
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] munchy_cool:
glad you figured it out. which firmware did you use from second post.

headphone jack is a known issue.

as for dual boot - since data partition is shared and different roms have different changes to framework on all chances are rare. it might work , bit in most cases it wont.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] edufur:
congrats! nice work! has anyone tested android auto to see if it holds up over time? My biggest complaint right now on the stock rom is that android auto occasionally disconnects from the vehicle and I have to unplug and replug to get it working again. it isnt a cable problem as I have tried multiple (all which work on a different phone with no issues).
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] pbjr92:
I had a Moto Z Play in February with Lineage 15.1 and the headphone worked fine (but the camera was trash tho).

---------- Post added at 11:07 PM ---------- Previous post was at 11:05 PM ----------

By the way, even with the headphone plugged the sound is playing in the speaker.

Is like not recognizing that the headphone is actually plugged. Tried SoundAbout and other similar apps, but they seem not to work in 8.1.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] erfanoabdi:
new version is out :

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

* headphone jack fixed
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] munchy_cool:
Thank you sir. :good:

Jack's back ;)

OP updated.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] pbjr92:
Is there any recommendation in the way to update? Can I flash it as a update via TWRP?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] domdom2020:
I have a problem and although I do everything in the video so 100% exactly as in the video then he does not start me LineageOS but after several reboots he goes back to the original Rom. I've tried this several times now and it does not work. I have used the same gapps (the phone does not do it without Gapps) and also the same recovery and all 100% equal in the terminal entered.

---Lineage Version from 20180609

---Device: xt1900-7

---Used Rom version: xt1900-1 and xt1900-6

---Installed Rom before the flashing: PAYTON_OPW27.57-40-14_subsy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip

and PAYTON_FI_OPW27.57-25-6-10_subsy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip

---Used TWRP: twrp-3.2.1-1-paytion.img (this is from Androidfilehost this is exactly the same variant as in the video. But I also used the official version.)

---Gapps: open_gapps-arm64-8.1-mini-20180609.zip (his is exactly the same variant as in the video.) and open_gapps-arm64-8.1-aroma-20180611.zip
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] abhi212b:
I used 1900-1..firmware!

I guess all the retail roms and firmwares works on all retail phones... No matter which version!

There one more thing which i noticed.. It is that the notification led is way too less bright! Is that normal??

---------- Post added at 04:06 AM ---------- Previous post was at 04:04 AM ----------

Can you please tel how to carry out this update? I mean there is a slot A/B problem.. My lineage is installed in B.. So should I go to recovery and then switch to A and then flash this? And then switch again.. To B and then flash gapps? :confused:
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] brandontowey:
First full day with it. Looks like I'll end up with 8hrs SOT and about 16.5hrs total with heavy usage. Versus stock, I can only say it's as good or better. I'm on break from school so I'm on my phone way more than usual. On stock, I was getting 1.5+ days with light usage.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] domdom2020:
With the version 20180612 I have it done.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] igna.98:
I've just flashed latest version and my headphones work again. It turns out they weren't old haha. Thank you so much [MENTION=6298645]erfanoabdi[/MENTION] and [MENTION=921457]munchy_cool[/MENTION]
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] domdom2020:
The Rom is just perfect. When I think of the first Android 8.0 Rom from the Moto G5 Plus, it's just amazing how well this one works. I am happy. Thank you.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] munchy_cool:
[MENTION=5774054]pbjr92[/MENTION] [MENTION=7284510]abhi212b[/MENTION] check OP for update instructions.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] edufur:
How does this do on Project Fi? And can anyone attest to whether Android Auto works without crashing all the time?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] carsten87:
I am pretty sure it is locked: It says

oem_locked

in Fastboot and I am not able to boot custom recovery, but am told to unlock bootloader first. Also I am sure I never relocked the bootloader, I thought it was impossible to relock it.

But it turns out you had the correct solution. I tried your suggestion (see my last post, edit 0). First command ran through just fine, second command failed. Despite that, at a first glance, everything seems to work fine now. So apparently, only the first command is actually needed to get everything back up. I can access recovery, system boots, accepts my PIN and shows all my files. Even ADB is enabled, again (in fact I didn't change this before or after the update). In Developer Settings I can't find a setting to enable/disable OEM unlocking

I consider this problem solved. For me it was necessary to download the Project Fi firmware from https://xdaforums.com/moto-x4/how-to/guide-how-to-flash-official-factory-t3808348, unzip, go to the folder with the unzipped files and then run

fastboot flash partition gpt.bin

I got a "FAILED (remote failure)" status report from running

fastboot flash bootloader bootloader.img

so I assume this was not required to get the system back running. After a reboot, everything worked for me!

Thanks a lot!!! :laugh:
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] reedc83:
I am running 20181009 on my phone. After clean install it too was in a bootloop. To fix it, I just had to change slots and it started booting fine. It's like after install, the default boot slot is set to the wrong one. Hope this helps.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] carsten87:
Conclusion to fix the current update, if you still get into Fastboot:

Option 1:

Try this: https://xdaforums.com/showpost.php?p=77760388&postcount=531

which is basically just running the following command in fastboot mode:

fastboot --set-active=b

If this fails and you get a message like

Slot b does not exist. supported slots are:
_a

continue with Option 2 below.

Option 2:

Running "fastboot flash bootloader bootloader.img" may result in a "FAILED (remote failure)" status. This does not matter, after a reboot everything should be back, without any data lost :D
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Toboe3:
Having OTA trouble again.

Doing an OTA from [2018-10-02] to [2018-10-09] leads to the following error:

After the phone shuts down for the restart it doesn't start anymore.

Pressing power button: No reaction.

Pressing power and Vol down: No reaction.

Using a cable that worked ~5 minutes before:

Connecting to a charger or the laptop does not change anything about the aforementioned problems. "fastboot devices" does not recognize phone
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] gee one:
Are you in download mode? Does it show us as a USB device in your OS?

In linux, I can run lsusb and I see:

Bus 004 Device 104: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Toboe3:
How do i recognize download mode? The phone itself looks like a phone that is off.

[Edit: if by Download mode you mean fastboot, pressing the buttons (power+vol down) does not lead to any visual change on the device, nor does it lead to being detected by fastboot on the computer]

lsusb has:

Bus 001 Device 025: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] CJ1169:
Can confirm I am also having this issue. Fresh install as of 10/07/18. Ran the standard OTA update today and its exhibiting the classic 'brick' symptoms. No reaction to pressing or holding any buttons or any combination. Computer (windows) registers that something was plugged in with the classic 'plug in' noise. No device under device manager. No adb devices, no fastboot devices.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Z3RO2K:
Fresh installed the 2018-10-09 - still having the Google and general issues with stopping/crashing errors. Every Google service keeps crashing and I can't finish setting up my phone correctly.

I have tried Open G Apps and MindTheGApps, five times now each with fresh install of LineageOS.

Thinking about just going back to Stock at this point, appreciate the devs work but it's too much hassle right now.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] gee one:
Yes, that looks like download mode to me, or at least the same problem that I have.

I haven't been able to fix this yet. I might try a battery pull, but I'm looking to see if it would even work.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] assmist:
im trying to sideload update 20181009 from recovery, but im getting "ErrorCode::kInstallDeviceOpenError"

Have anyone successfully installed this?

Im also getting an other error when trying to boot twrp.

# fastboot boot twrp-3.2.3-1-payton.img

downloading 'boot.img'...

FAILED (remote: unknown command)

finished. total time: 0.001s

Any ideas?

Edit: where able to boot twrp from an other computer and sideload the update from there. strange that sideloading the update from lineage recovery isnt working.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] gee one:
I fixed it- and without having to rip out the battery.

I used the blankflash tool. I had to run as root to get it to work- duh!m The singleimage file seems a bit older, so you might have to upgrade back to the current bootloader/radio/etc.

tool is from here:

https://xdaforums.com/showpost.php?p=76942904&postcount=30

Instructions are here. In linux, execute as root.

https://xdaforums.com/moto-x4/development/rom-lineage-os-15-1-t3802265/post77752339
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] CJ1169:
No dice from me on Windows. Got the COM port to show under devices. Strangely only installed motorola usb drivers.

What's happening for me is that it'll continuously wait for a device and do nothing.

What I'll do this evening is I'll load up a live USB or something later and try it in linux instead. Crossing fingers.

Note: I did try both the fastboot blank method and trying to directly run the .bat script, just in case.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] shonmac11:
I have a slight issue. When I try to reboot twrp warns me that I have no OS
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] gee one:
That message pops up. I generally ignore it. As long as you flashed an image, you should be OK.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] shonmac11:
Is there a way to permanently use twrp as a recovery along side lineage OS
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] murrty:
Has anyone tried using rekado or nxloader on here? It'd be nice to have the switch payloads being pushed from this device.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] CJ1169:
[ 0.000] Opening device: /dev/ttyUSB0
[ 0.000] Detecting device
[ 34.604] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 34.604] Check qboot_log.txt for more details
[ 34.604] Total time: 34.604s
[ 34.604]
[ 34.604] qboot version 3.86
[ 34.604]
[ 34.604] DEVICE {
[ 34.604] name = "/dev/ttyUSB0",
[ 34.604] flags = "0x60",
[ 34.604] addr = "0x48EBC350",
[ 34.604] serial_nix.device_pathname = "/sys/bus/usb/devices/1-3/1-3:1.0/ttyUSB0",
[ 34.604] api.bnr = "0x13EDFB0",
[ 34.604] }
[ 34.604]
[ 34.604]
[ 34.604] Backup & Restore {
[ 34.604] num_entries = 0,
[ 34.604] restoring = "false",
[ 34.604] backup_error = "not started",
[ 34.604] restore_error = "not started",
[ 34.604] }
[ 34.604]

Steps:

Open terminal -> path to platform tools & blankflash->run fastboot oem flashblank

It continuously waits for a device. -> ctrl+c-> attempt sudo and fastboot oem flashblank

same result->execute blankflash.sh as root -> spits out the log above as an error

Same result as using Windows, but it was worth the attempt. However, at this point I am stuck bricked :/

Appreciate the help so far.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] gee one:
Not sure if it would make a difference, but are you using sudo or actually in a root shell?

Also, what distro are you using? I am on Debian stretch with backports.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] CJ1169:
It didn't seem to make a difference, but it seemed worth a shot.

I was using sudo & Antergos.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] xdayman:
Moto x4 won't boot after OTA

Hey guys,

I have a moto x4 that's running 15.1 and all was going fine until I went to update via ota, believe it said the build was from 10-07 but I could be mistaken. The build downloaded and installed and once I pressed restart the phone turned off and won't turn back on. I can't get adp to see it when I run 'adp devices' but windows does see that I attached it so I'm not quite sure what to do at this point. Any assistance would be greatly appreciated.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] jhedfors:
If you had read back 2 pages, and you would have found this...
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] xdayman:
I was able to get the blankflash running but it had an error and kicked out these files;

backupImg(tinyupload)

qboot_log(tinyupload)
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] jhedfors:
I am not familiar with using blankflash, but the post I linked to above may help.