yashsingh1/xdaforums huggingface dataset:
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] kendallgreen:
I want to root my bootloader unlocked T mobile Moto Z2 force with Magisk while retaining encryption. I have downloaded the following nash_tmo_ncx26.122-59-8_boot.img, MagiskManager v5.5.2.apk, and Magisk v15.1.zip. I PLAN to install the MagiskManager apk and push the boot.img to /Internal Storage/ using adb. I plan to open the MagiskManager apk and Install > Install > patch boot image and choose the nash_tmo_ncx25.122-59-8_boot.img while preserving forced encryption. I will pull the patched_boot.img back to my PC and fashboot flash boot patched_boot.img. I will then fastboot reboot. Any suggestions? I am currently on build number NCX 26.7, do I need to flash the nash_tmo_ncx26.122-59-8_boot.img first? Do I need to do anything after rebooting
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] skywalker-live:
That boot image is from the 26.5 update that TMobile pulled for bugs and republished all fixed up as 26.7. You should be able to patch the boot.img from your phone with magisk manager, then fastboot flash it. The directions are in the magisk forums.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] ilovemeow:
do you mean wifi might be loose after flashing kernel? coz just found out i've loose the wifi signal :lol:

mac address appeared 02:00:00:00:00:00

edited:

wifi issue fixed with

https://xdaforums.com/nexus-6/help/wifi-mac-address-200000000000-t3257465/post65960082#post65960082
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Uzephi:
Yes, patched boot image in OP shouldn't have caused that unless you are encrypted which is advised against in OP as well.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] blackwing182:
Since theres now a oreo rom/ota i sugest that state in topic name that this is only for Nougat (android 7.X.X)

[MENTION=4604067]Uzephi[/MENTION]
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] DsturbD:
It states that in the OP
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Uzephi:
After kernel source releases, I am going to pull it and start the 8.0.y Pantheon kernel and put it in OP as well since probably all phones will be updated by the time source hits and 7.1.y branch will be forced into being stale at that point. (Since we have no way currently to downgrade back to 7.1 after upgrading to 8.0 firmware)

Edit: but as [MENTION=4518483]Midnight_Rider[/MENTION] stated, my OP gives all the information on the kernel. OP already States it is for Android 7.1.y. Once I get an Oreo Kernel done, the last version of Pantheon for 7.1.y will be in post 3 for history purposes as well for anyone forcing themselves to not go on Oreo (wouldn't know why, but you never know, lol). OP will always have the latest kernel version available built from source and upstreamed.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Crossdead:
Hey, quick question but on my tmobile variant I seem to have an issue of random reboots, they seem to be a lot at first then slow down once I set up the phone. When I use a kernel auditor it doesn't seem to show in the OP. I have tried this on both the modified rom on here as well as the tmobile August update and November
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Uzephi:
Which version of the kernel are you using? Did you flash the decrypt zip? Have you tried without the kernel and see if it still does it?
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Uzephi:
4.4.109 built fine. Will get separate boot images soon. (Busy today, but wanted to make sure it built fine) Only thing changed for it was some race condition fixes for ipv4. All kernel versions that released today we're mainly for the Intel chipset issues.

Edit: updated file on Google drive to 4.4.109. tested all boot images and they work just fine. Updated OP with mandatory stuff and pushed upstream to GitHub.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Crossdead:
I was using the 1.4 version tried the 1.3 as well with same issue tried ajusting the frequencys of the cpus witch seemed to help the reboots but they would still happen. I'm thinking it could be the undervolting as that would cause random reboots, I'll try ur updated one and see if the issues stops and let u know. Also can u send me or post the original voltage values so I can try that and see if it stops the reboot, thank you for your hard work on this.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Uzephi:
Under volt would have affected other users if it was that. Below is the commit for voltages in any case. All I did was put it in line with other msm8998 devices. If it was the default for other devices that caused it, it would be affecting other devices as well. T-Mobile and Sprint variants are speed bin 2 per everyone who has given me a kmesg during troubleshooting.

https://github.com/Uzephi/kernel_nash/commit/74f28c3c093685fe19b9a5fc0e7cd03942757d39

Edit: it could be the CRC-check removal that causes the reboots. If something is wrong in memory, you no longer have that in place to fix the error.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Crossdead:
Ok that would make sense, question with ur new update do we still flash the remove encryption after we flash and format data??
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Uzephi:
no, remove encryption is in /system.

edit: try v1.2, it shouldn't cause any issues, only has safetynet fixes in it. https://drive.google.com/open?id=1qimnVdw2PeuFPe06JZdnXUDjpEa5Hhga
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Crossdead:
Ok that's awesome that is intergrated now, thank you for ur hard work again I am clean flashing the phone updating and then flashing this, I'll report later on how it goes?
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Crossdead:
I'll give it a try, tried your newest release, it wouldn't boot though until I used the removeencryption.zip, after that it booted went thru setup without reboots until my main apps updated thru google play it rebooted a few times then was fine so I put my sim back in and it worked for a phone call then when I make a call after that it would reboot then random rebooted also the phone got a bit hot. Also, this is ok to use on stock firmware or should i use it with NPC rom??
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Uzephi:
I am on stock and it works fine. Can you by chance pull a log when it reboots? Can you try v1.2 I linked earlier and see if that reboots? Decrypt without my kernel? There are variables we can try to see what is causing it on your phone, those two would help: stock kernel, decrypted and then try v1.2
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] ilovemeow:
is there any kernel in google drive, without magisk upgrade?

coz it's not showing in app menu for magisk version 14.5/15+
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Uzephi:
The non rooted ones don't have Magisk in them. The rooted ones are patched with Magisk 15.2
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] ilovemeow:
cheers :)
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] LGtMgG2t:
109 flashed fine on my TMO variant just now. I flashed the twrp non root image over top of 108 then installed latest SuperSU zip and rebooted. Thanks for the continued effort.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Crossdead:
Hey so updated and used the 1.2 no reboots at all on stock TMobile NCX26.7 update, I could try to update and grab a log but when the reboots start I can't get into the phone for more then a few swipes before it freezes and reboots especially if I have my a password on screen.

I'm kinda nervous though cause the new Oreo update came out and is asking me to update and there is no image of the TMobile NCX26.7 so I would have to stay on the August update till that happens or go to Oreo witch I don't want to do until there is root and Xposed for it as u can't flash back from what I've read.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Uzephi:
I'd suggest staying on 1.2 until 8.0 source drops then. 1.2 has stock voltages for msm8998 but doesn't have OC or UC which could be causing the issue.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Uzephi:
https://github.com/MotorolaMobilityLLC/kernel-msm/issues/137

8.0 source will be released soon™! I will merge 4.4.110 this weekend and then once the 8.0 kernel is released, I'll start working on it to have the same features as 7.1.1 and upstream it.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] rechter:
Oreo release date

Anyone knows a possible date to release kernel to Oreo ???
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Uzephi:
Read my previous post. Motorola confirmed the kernel source will drop sometime this week for Oreo.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] kraatus90:
released already.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Uzephi:
Yes, git cloned and already putting it together to build correctly.

Also: putting the img files together for 4.4.110 (has the final kernel fixes for the KPTI bug). I might skip rooting the imgs as you can do that in the magisk app after downloading.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] kraatus90:
nice, i hope payton kernel source will release soon so i can build my EAS kernel. first time seeing moto has upstream the kernel. :good:
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Uzephi:
4.4.111 released. Upstreaming that and it will be the last upstream for 7.1.1 since Oreo updates are rolling out for our devices. I already have fixed and Regen the defconfig to get source to boot. Will start upstreaming Oreo source tonight. I'll have 4.4.111 released hopefully in an hour or two. Skipping 4.4.110 since 111 came out already.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Uzephi:
4.4.111 updated, Google Drive link updated with all normal boot images to flash!

until further notice (need to complete upstream for Oreo, which I can't really do that well without Sprint pushing the update) 4.4.111 might be the last release for Nougat. When I build Pantheon for Oreo, it's version will go to 2.0+
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] ilovemeow:
thanks :)
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] ianmck:
Vibration control

Does this kernel allow for adjusting vibration intensity? TMO has the phone for $375 and I am thinking of buying it. Vibration level is something I definitely want to control, but stock does not seem to allow it.

Thx
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Uzephi:
If stock doesn't have it, then mine wouldn't. Once I get Oreo, I'll see about adding it in 2.0+. 1.4 is on stable-linux status. I'll only update when k.org updates.

Speaking of that. 4.4.112 has been released and Google Drive link has been updated. Pushed to github as well. Encryption issue still there. Might debug that again and see if we can boot encrypted now that we have a TWRP that can decrypt.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Uzephi:
Note: original update didn't take the kernel injection on the TWRP images. Fixed and re-uploaded. If you flashed the TWRP image, please redownload and flash again.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] firemedic1553:
Moto mods not working after kernel update

I installed the current kernel update and none of my mods work now. They are charged and work on my non modded Moto z2. Does anyone have any idea to fix that? Other an that the phone works flawlessly.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Uzephi:
I haven't checked motomod functionality for a few builds. I will go back and get it working again. Last known version working for motomod is 4.4.109, so it shouldn't take me too long to find the commit that broke motomods.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] ilovemeow:
4.4.111 is fine for moto mod
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] donjuro:
Hey guys! New to the z2 force here! Sprint variant. I've been trying to install this kernel all day with no luck. It just throws me into a bootloop, do I HAVE to be rooted? Or can I stay stock?

Edited: After hours of endlessly searching, I finally found the decryption file everyone keeps talking about and managed to finally get my phone to boot. Please include a copy of this link in the OP.

https://xdaforums.com/showpost.php?p=74536696&postcount=13
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] donjuro:
1.4 caused me random freezes and reboots (I'm guessing under volting) so I had to roll back to 1.2 as mentioned in a previous post. I didn't check on 1.4 but I noticed that on 1.2 I can't switch color profiles, the options are there but they don't do a thing. I'm pretty much stuck on vibrant. Can anyone else confirm this?
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Uzephi:
Color mode option works for me. v1.2 had the voltage tables fixed to stock msm8998 values, so UV isn't causing your freezing and reboots. It could be the UC on the video chip. Or the OC on the top value depending on when it happens. The lower clock was an added value, so the GPU governor could be having issues adjusting to an extra value. I'll try to look into it. It's hard when there is no log given and I can't replicate the issue.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Uzephi:
Update: still trying to pinpoint the 1 of 80 commits that broke motomods on 4.4.112. once I get it working, I'll upstream to 4.4.113. each commit I revert and test is another 30 minute build which is why it's taking a bit longer than expected to fix. 4.4.110-113 has a lot of KPTI fixes to essentially rig a kernel side fix to the exploit that was all over the news the beginning of this month. So, depending on if it affects that fix, I might not be able to correct the issue if Motorola gave some bad permissions to motomods. It is essentially a USB device with a different connector in the kernel space and a few changes to how USB devices are handled are in 4.4.112 to fix the page table leak. Expect 4.4.113 release in a day or two with the motomods working and a possible warning of the security hole left by bad coding on Moto's end depending on which commit I had to revert and/or fix.

Edit: okay, so I have found the issue... And I don't like the fix. There is a commit in 4.4.112 that fixes the KPTI leak for bpf kernel space. This change makes motomods not work. Essentially, motomods are a literal hack to work and this commit fixes that hack.

So, a huge security fix, or motomod functionality... Until Motorola fixes the motomods permissions, I will have to revert that commit so we can use our mods. I'll revert it and start 4.4.113 merging.

Edit 2: https://github.com/Uzephi/kernel_nash/commit/1f2c6bc03db44435e10c0d13e0aa1c0a276bf997 for reference on the commit that broke motomods.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Uzephi:
4.4.113 Kernel version has been released! Proper warning: bpf fix for CVE-2017-5753 cannot be merged onto our device due to how the motomods driver currently works. I will look into getting it working, but as of right now, that fix isn't in our kernel. Google Drive in OP has been updated and Motomods work again.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] donjuro:
Had the OC/UC been removed?
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Uzephi:
I can't replicate the issues people have been having with OC/UC. Give me logs and I can see what is causing the issue and try to replicate to fix it. Until then, this release works flawlessly on my device.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] donjuro:
I'll update and let you know how it goes. Which logs do I have to pull?
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Uzephi:
The kernel log. Proc/kmsg. If the reboot happened because of a kernel panic, it will create a last_kmsg file. be sure to go to recovery before the system boots and grab that file

Edit: best to pull it from TWRP after the issue so it doesn't get overwritten at next boot. Just copy it to sdcard. It might have sensitive info, so either scrub it or send the log via pm

Edit 2: please only scrub things like serial, imei and such. Things like speed bin and other device info is useful for kernel logs.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Uzephi:
Edit 3: what you can also do if you don't want to share the log (it is the kernel boot time log, so it will have everything about the device on it) just pull it from proc to sdcard using recovery or adb pull and search the file for your speed bin. I think I know what's up. most of our devices are Binned at 2 and yours might be 3 or 1 so I can't see how UV/OC/UC reacts to it. I in fact you are bin 1 or 3, I can get that fixed relatively quick and the rest can still enjoy UV/UC/OC
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] donjuro:
I haven't flashed yet but another thing I forgot to mention is the twrp versions of your kernel would never work for me. In order to get your kernel installed I first have to flash Joe's recovery, then flash yours, but if I try to boot into recovery I only get a dead Android with a red !. If things are any different in the latest update I'll report back. Also, bootloader wouldn't happen to tell what version bin you have would it?
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Uzephi:
No, only the runtime at boot will. It tells the kernel which table to use in the dtsi.

The dead Android was because 4.4.112 had just stock images. TWRP boot images are 20mb while stock is 28
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] donjuro:
But the zip had 4 folders 2 stock 2 twrp and 1 rooted 1 unrooted. So did they actually not contain twrp?
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Uzephi:
On 112, no. I mistakenly did that. 113 is correct.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] donjuro:
Ok, so I'm on the latest (113) kernel. Boots into twrp perfectly fine now, SO FAR no random reboots. I'll report back if I do find something wrong, otherwise it's been smooth as a baby's bottom these past few hours.

Edit: spoke to soon, shortly after this post I got a reboot. Sending log now.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Uzephi:
So what I gather from this log... Near the end of it, you tried to turn the device on. (Went from deep sleep last, and wouldn't respond?) Per the log, oddly enough it has nothing to do with UC/UV. The Synaptics driver wouldn't wake up. Essentially your screen wasn't responding. I'll dig deeper and try to fix it if my assumption is correct. Please verify. Will also put this in my kernel thread for others to know what's up.

That's from our PM. It might be the GPU UC. But highly unlikely. "Sending information to Synaptics, error no response." Is in the last few times after you pressed power a good 4-5 times. Or unless the log wasn't complete.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] donjuro:
So after thinking more about it and reading back on your post about logging, I think something is missing here. It looks like last_kmsg is the file I should be looking for? But there isn't one stored there. Kmsg seems to constantly be logging kernel messages which must be why when I tried to copy it, it just stayed at that screen, because it was copying every action. I'm no expert but I tried reading it as best as I could and everything seems to be from inside recovery but no logs from system.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Uzephi:
Double checking the log and trying for myself, that seems to be true. It's odd I can't find dmsg or last_kmsg to pull the last boot log. After looking at your log though, I think it may be the GPU clocking. I'll revert that and release CPU only OC/UC/uv just for you to test. I'll PM it. Let me know if it works or not. Should be done later on today.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] donjuro:
So I found out last_kmsg is stored under /data/dontpanic, however as I look at it, it looks like the log is from the 17th (on 112) even though today is the 29th (on 113) and it continues to happen. Either way I have uploaded it and will send it to you now since it will probably still help anyways. I also found a bunch of files under /data/system/dropbox. Assuming these are logs kept over time too I've deleted them to start over and can send you copy of those too if need be.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] donjuro:
So even though this keeps happening the last_kmsg file never gets updated, not sure why, not sure if this is kernel related. I did however find a "kernel panic" log under /data/system/Dropbox after the latest random reboot. Uploaded and sending now.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] gerland:
I am unlocked and rooted on my z2 force edition Sprint (Nash) but cannot get this kernel to flash in twrp?? Any ideas
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] donjuro:
[MENTION=4604067]Uzephi[/MENTION] do you have a telegram channel or anything like that we could keep in contact with? Btw I just wanted to make sure you got my last pm.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Uzephi:
It's a boot image, not a flashable zip. It's in zip format so I don't have to do many links.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Uzephi:
I got it. I now have the free time to revert the said commits and will send you the file here shortly.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] gerland:
Ok thank you..
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] ilovemeow:
did the decrypt yet?
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] gerland:
Afraid not, noob here
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Uzephi:
Flash this to use my kernel for nougat.

https://drive.google.com/file/d/1Cr-7SiSiHpUDM9HYpyeXVsPHEB9Z9wym/view?usp=drivesdk
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] gerland:
Thank you sir, I will do that!!?
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] donjuro:
[MENTION=5337224]Crossdead[/MENTION] do your random reboots happen mostly when your WiFi is enabled?
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] piscesjoey:
Noob here to the Z2 Force. Picked up a bnib Sprint one from eBay for only $298 after dumping my Pixel XL & have been using it since I received it Wednesday. Unlocked the bootloader with ease & immediately flashed your rooted kernel with TWRP. I love how the recovery is together with the boot image unlike past phones where you're having to do separate processes for root & recovery. Kernel has been running like a charm on my phone since. Thanks a lot for your hard work!
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] Quantumstate:
Anyone advise how to stop Android from hassling me about taking an OTA?
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] skywalker-live:
Disable Motorola update services apk. I used Titanium Backup to freeze it.
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] jbrookex_x:
Reboot to Recovery Loop

Hello, I am currently using a Moto Z2 Force on Sprint's network running Nougat 7.1.1. I have already reached unencrypted root with twrp and supersu by following the instructions on the other thread in this category. Everything was working fine at that point as I confirmed with root checker etc. I had not however installed magisk at the time. I decided to try flashing this kernel through adb fastboot with the instructions given. I downloaded zip, extracted twrp (root) into adb and "fastboot flash boot patched_boot.img". After rebooting from there, I can now only reboot to recovery. Did I do something wrong? How can I fix this? Please help!
[Moto Z2 Force  ROMs, Kernels, Recoveries, & Other ] piscesjoey:
You have to flash the unencryption.zip that's floating around on this thread after flashing the kernel.

EDIT: Here's the zip for you.

https://drive.google.com/file/d/10av5u41siBaIIFmwzNWcJ1J_IbYXtyZj/view?usp=drivesdk