yashsingh1/xdaforums huggingface dataset:
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] iron maiden:
I'll try again

The steps are these:

* To flip through fastboot the kernel-boot img of the rom nougat

Restart phone

Go to twrp and flare kernel tomparr nougat

Flasear magisk 11.1 zip

The supersu SR3 also need to flase?

Use scraping from supuersu settings and also unistaller magisk.zip
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] prins29:
I can't understand what is your issue. Did your rooting won't worked or you can't boot in to system
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] h1ddev:
Mmm I flashed the same version and didn't work. Maybe different nougat ROM? Dual SIM - single SIM phone difference?

Btw, I have a z play single sim and flashed the Nougat RETIN from the Nougat 7.0 thread.
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] prins29:
I have a dual sim and retin naugat which you flashed is based on my TWRP backup .. so I don't think it's a ROM issue
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] iron maiden:
Hello, I feel my English does not start, it does not capture it, I put it back later, but it is necessary to re-float the fixed kernel of tomparr after the boot.img kernel of the rom nougat? I'm sorry if you can not understand me, thank you very much
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] prins29:
After flashing boot.img (unrooted) just start ur device without flashing any thing.

After ur device boots normally than do the process for rooting.

And I am attaching the boot.img I used.

https://1drv.ms/u/s!AryUww1_9vvCgushk8EWNRZBQWnXOw
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] iron maiden:
Hello not working Safety ? Very tahnks

Enviado desde mi XT1635-02 mediante Tapatalk
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] h1ddev:
Apparently, we have to flash the boot.img of Nougat from the fastboot, then go to TWRP and flash -> this kernel fix from op -> SuperSU 2.79 SR3 -> magisk 11.1.

The reason for which we have to flash the boot.img from fastboot, I think, is because the script that installs the boot.img of the Nougat backups roms from the other thread is some kind of "broken" and doesn't do it right. I was reading the instalation script of the rom when I noticed that. And so, when you try to fix the boot problem by reflashing that rom, it solves the boot problem ofc, but isn't going to have a cleaner boot.img partition.

I will try it by the morning. It is too late here.

Edit: the other method that may work if the one of above doesn't:

- Flash the Nougat 7.0 ROM from TWRP

- Go to the file manager in TWRP and /data, and delete the files related to magisk, SuperSU and su, if you have any of them.

- Reboot the phone into bootloader again. Flash the boot.img from fastboot

- Enter to TWRP again

- Flash kernel fix from OP

- Flash SuperSU 2.79 SR3

- Flash Magisk 11.1

- Wipe Dalvik?

- Reboot to system and pray
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] prins29:
So you revived from that bootloader logs (unbootable into the system )?
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] iron maiden:
Hi, I do not understand what you mean, does it work for you? thanks
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] felipevsw:
If we're on Lineage should we flash this kernel to benefit from its f2fs fix or it only matters on stock roms?
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] iron maiden:
Hello I would not know to tell you since I do not have lineage and I have not tested on the stock nougat the supuersu root works but what I can not get is magisk safety

regards
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] tag68:
SafetyNet check only can get green with Magisk Hide. Magisk hide is only supported using MagiskSU. If SuperSU is flashed, is not possible.
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] iron maiden:
Hello as the companion said it worked because I've been trying it all morning in Mm if it worked thanks

Enviado desde mi Nexus 6P mediante Tapatalk
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] tomparr:
For LineageOS you don't really need this kernel. It is primarily for Stock ROMS to have the ability to install systemless modifications (e.g. SuperSU) so you can still receive official OTAs.
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] tomparr:
In addition to Magisk Hide, the kernel may need a patch too. On MM, SafetyNet also checks for modifications in the boot.img. Could anyone on Nougat who is rooted check the following:

Install Terminal Emulator (e.g. Android Terminal Emulator)

Open Terminal Emulator

Type 'su' to get root

Type 'cat /proc/cmdline'

Check if the output contains the entry 'androidboot.verifiedbootstate=' and report back please.
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] iron maiden:
Hello teacher does this? Thank you

Enviado desde mi XT1635-02 mediante Tapatalk
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] tomparr:
Perfect. Thank you. I'll build a new version this evening which should help passing SafetyNet checks.
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] iron maiden:
Hello ok very very tahnks

Regards

Enviado desde mi XT1635-02 mediante Tapatalk
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] pillopoulos:
Is it my impression or do I really have better battery life with this kernel?

Στάλθηκε από το XT1635-02 μου χρησιμοποιώντας Tapatalk
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] core720:
For root NOUGAT:

Install ONLY Patch Kernel and SuperSU 2.79 RC3 and reboot, NOOOOO MAGISK
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] tomparr:
I don't think thats possible, although it would be nice ;) Kernel is built from Motorolas sources with same config as Stock ROMS and without any further optimizations.
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] tomparr:
An updated kernel is available. Use only Magisk 11.1, MagiskSu and Magisk Hide and you might be able to pass SafetyNet.

Download
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] -=MoRpH=-:
After flashing Magisk 11.1 i got "failed to load kernel" :(
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] iron maiden:
Hello, as long as I can, I'll try to thank you

Enviado desde mi XT1635-02 mediante Tapatalk
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] tomparr:
Then Magisk is somehow messing up the boot image. I'll take a look at it.
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] -=MoRpH=-:
Thx [emoji106] And btw great work. [emoji108]

Gesendet von iPhone mit Tapatalk
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] iron maiden:
Hello then I waited for you to look at it again

Enviado desde mi XT1635-02 mediante Tapatalk
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] h1ddev:
Yap, tested flashing the boot.img, then magisk or supersu+magisk, and none of them worked.

Waiting for some fix. Thanks so much, [MENTION=4539224]tomparr[/MENTION]!!
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] tag68:
Does that mean, you don't need to undo change of kernel for OTA?

(Am considering switching to nougat and use your kernel, thinking you need to replace your kernel by original one before doing OTA is what made me hesitate using it all the time)
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] tomparr:
You will need to return to stock kernel before doing the OTA by flashing boot.img (backup or official once available), but you don't have to flash the system sparseschunks and redo all OTAs prior to the new one.
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] tag68:
There was some part in that article about f2fs that I didn't understand. Maybe it's because I'm no native English speaker. It was, if you use corrected f2fs, you have to update all drivers. Some access with earlier f2fs without that fix will cause kernel panic. You need to revert the timeout change to avoid this.

Did I get that right, that accessing the f2fs partition using the corrected driver will cause the original kernel to crash when installed? There is some puzzle piece in this that does not fit for me. Why is the structure where some pointers were accidentally missing written to disk, or does cause changes on disk that do problems when accessing it without the fix? But the problem is exposed when writing using the fix using the corrected f2fs - although there is no format change in disk involved? Is this only for the time of install? Or only when using the loopback device for /su? Will the system be able to work stable without your kernel? With or without systemless root?

Hope you can enlighten me a bit. As software developer having dealt with similar things several times I thought my understanding for these kinds of problems would be quite good, and it should be easy for me. But at some point came contradicting information for me (the written data is the same, but the not fixed driver detects somehow that data is written by the corrected version and crashes? How?), and I am just confused.
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] tomparr:
Not sure what you mean by 'you have to update all the drivers' but here is how I see it. All f2fs versions prior to the one included in Linux 4.10 have a problem with mounting images as loopback device when the image resides on the f2fs partition, e.g. /data/su.img. To fix it, we have two options. We can add the missing pointers to our old version or backport the version included in 4.10.

However both options introduce new bugs. In case we just added the pointers, the kernel will panic if we any access data on the partition. The format which is written on disk is the same, but another issue with the older f2fs version is triggered and prevents the data from being read correctly. Therefore a second patch is needed.

In case one choose to use the latest f2fs version, there is an seperate issue which could lead to deadlocks because of a high tineout value of two minutes.

So that is my basic understanding of the issue, but I am not sure if it helps you. Feel free to PM me if you want to discuss this in your (and my) native language ;)
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] diegochiva95:
Can someone explain to me why they delete the encrypted??
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] flashallthetime:
It makes your device slightly faster, normally your data has to be unencrypted prior to reading it, so decryption bypasses that so your data gets read faster.
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] tag68:
Thank you for the offer, but I'm quite sure now it is not a problem of the language. And the problems with versions without fix only exist when running concurrently, because a pointer to that structure gets stored in memory and access will fail using the other version of the structure. Think this is the part I did not get right.

The consequences. If you have fix installed, loopback devices are working. If not, they fail. If you root systemless, SuperSU or MagiskSU do a loopback device which is used not only while install but also when being accessed, created on boot.

If you restore the original kernel by restoring boot.img, f2fs fix will be gone, but systemless root also, which is fine (it wouldn't work without f2fs fix). After OTA update rooting again is necessary anyway. And systemless root would not run without that fix. Except for phh superuser which seems not to use a loopback device, or at least not trigger the problem.

Now I just need some time to do backup, OTA update and see if it runs and under which circumstances. Do I really need to unroot before the update, or does this not get checked for OTA? Read several times that systemless root should not be an obstacle for OTA. But kernel changes (which I didn't do by now) always were.
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] iron maiden:
Hello someone tried this magisk version? snapshots v.12

https://xdaforums.com/apps/magisk/unofficial-magisk-v10-beta-built-t3521901

regards
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] tomparr:
Good summary of the issue.;)

I don't think unroot is necessary for phh, but haven't tested it since phh didn't work for me in enforcing mode.
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] tag68:
Did you find something out? Would also like to use Magisk (pay online using Sparkasse credit card is only possible with green SafetyNet check), thought it would run already.

(Don't need it urgent, currently not really necessary - would just like to have that possibility)
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] tomparr:
Unfortunately I haven't found the issue yet. Magisk runs fine under MM, just Nougat has problems. But I'll keep searching for a solution.
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] tag68:
Do you have any insight if AOSP will distribute the f2fs fix you compiled, and when it may be available? Do you see any chance that Lenovo distributes it with 7.1 and security patch level February or March 2017?
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] iron maiden:
Hello mister you know something of Magisk for Nougat or you are investigating. Thanks

Enviado desde mi XT1635-02 mediante Tapatalk
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] -=MoRpH=-:
[Kernel][6.0/7.0] Stock kernel with f2fs patched for systemless modification

Ich got magisk to work.

But I can't remember the way.

I spend two days with try and error. [emoji85]
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] iron maiden:
Can you explain step by step with more details? I probe of everything included what you have done and nothing is no way thanks
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] xxBrun0xx:
This doesn't work. Step 6 is wrong, phone will not boot unless you flash Magisk uninstaller. Also, no idea where the su folder is in recovery.
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] tomparr:
Based on what Motorola publishes on GitHub, they use a seperate project only for f2fs called motorola-kernel which seems to be a different version compared to the code in AOSP or CAF. Additionally, the last commits are over six months old, but I do not know if everything Motorola does is pushed to GitHub. I believe it isn't.

I will create a pull request on GitHub. If Motorola accepts it, we might have a chance to see it patched in 7.1.(1).
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] Nil253259:
Is it possible to reduce the vibration intensity through any kernel control app? Is the parameter tweakable? TIA
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] tomparr:
As far as I know, it is not tweakable with the stock kernel config.

I'll do some research on how to add it, if anyone already has some documentation on how to add it feel free to throw it in my direction.
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] fortunz:
I almost hate to ask/abuse your goodwill but is there any chance you'd be interested in exploring kcal color control? https://xdaforums.com/android/software-hacking/dev-kcal-advanced-color-control-t3032080 Our 625 is not specifically listed as a supported processor, but I guess I'm hoping it has so much in common with those listed that it'll work anyway.

If not, no worries. Thanks for being a Z Play dev. :) All activity here is much appreciated.
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] cowboysgz:
Has anybody been successful at running systemless root?
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] dedraks:
Running
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] lpchaim:
Sistemless root works flawlessly with SuperSU 2.79 R3 and this kernel. It's just Magisk that refuses to run on Nougat for our phone AFAIK.
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] cowboysgz:
So I should run MM if I want systemless root?
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] lpchaim:
Not at all, it works normally on Nougat. The Magisk part was me venting off my frustration on it not working and not that relevant, so my bad.
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] cowboysgz:
Lol OK cool then. So order of flashing is kernel, SuperSU and magisk right?
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] lpchaim:
I mean, Magisk doesn't work at all on our stock Nougat as I said before, but otherwise yes. Give this thread a look for details, no offense but I feel we've taken this a bit too off topic as it stands.
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] cowboysgz:
I was looking at OP but this is much clearer. Thank you sir.
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] santos_10:
Snapchat and Pokemon Go works with this method?
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] -=MoRpH=-:
Only if u get magisk to work.
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] tomparr:
Should work fine on Marshmallow with Magisk. On Nougat, there were some issues reported with Magisk.
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] xxBrun0xx:
Magisk v12 works fine on all the nougat builds I've tried, but passing safetynet does not seem possible with an unlocked bootloader at this time (although some have posted screenshots of it passing, none of them know how they did it).
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] tomparr:
Good to know v12 works now, only received reports from v11 users that it messes up the ramdisk.

Safetynet is a real pain since we don't know what exactly it checks for.
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] tomparr:
I did some more testing with Magisk and SafetyNet. Turns out SafetyNet fails on the device if systemless host support for AdAway or other ad blockers is enabled. Turning it off gave me a green status.
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] tag68:
My recommendation then is dns66, it does not modify hosts, but implements a VPN server as local DNS. The result is the same as with AdAway, with advantage that you can turn it off per app and disadvantage that you can't use it while another vpn is active. And it doesn't need root, but that's not important at this place ;)
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] dedraks:
Thank you [MENTION=4539224]tomparr[/MENTION]

I have one question please.

Where can I find instructions to compile my own kernel?

Thanks in advance.
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] -=MoRpH=-:
My device pass saftynet just fine. I use AdAway on stock nougat.
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] tomparr:
You can use the instructions provided by Motorola for the X Play here: https://github.com/MotorolaMobilityLLC/readme/blob/master/MPD24.107-56.txt

The steps are pretty much the same for the Z Play.
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] dedraks:
TKS.
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] dedraks:
[MENTION=4539224]tomparr[/MENTION] I can't build the kernel using the instructions above.

Can you please post the steps you did?

Thanks in advance.
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] kafisc:
I'm also stuck on boot screen.

Any suggestions?

Thank you in advance

kafisc
[Moto Z Play ROMs, Kernels, Recoveries, & Other Dev] prins29:
Re flash the unrooted boot.Img

https://1drv.ms/u/s!AryUww1_9vvCgushk8EWNRZBQWnXOw

You can download it from here.

Use twrp or fastboot flash boot boot.Img command for it.
[General Questions and Answers] psaxno:
Hello,

I have a Cubot Manito with android 6.0. How can I root it?
[XDA Assist] XDA Visitor:
I'm trying to root my galaxy a8 (sm-a800f), but everytime i flash the CF-auto-root file i would just be greeted with this same message. I'm sure its the correct file, because its the only one out there. Everytime this happens, I just flash the official stock ROM again and everything is fine, I don't even lose my data.

CF-Auto-Root-a8elte-a8eltejv-sma800f.tar is the file im using, and A800FXXU1BPH4_A800FOLB1BPH4_A800FXXU1BPG3_HOME.tar is the stock rom.

I have OEM unlock enabled.
[XDA Assist] Razvan:
Hi there and welcome to assist,

Some users reported that CF-Auto-root don't work with that firmware. Try other methods like:

How to Root Any Device

You'll have to create an account to post in the main forums if you have any other questions.

> Samsung Galaxy A Series > Galaxy A3, A5, A7, A8 Q&A, Help & Troubleshooting

Good luck
[LG G Flex 2] Pungasul:
Hey guys.

I have the opportunity to buy a really cheap slightly used G Flex 2 H955A (for about 90€) it is actually for my dad as Ive already got H955 for myself for more than 1 year now.

Now my question is...

Can H955 20c kdz be flashed on H955A???
[OnePlus 3 Questions & Answers] kpmohamedhussain:
After updating to nougat, speaker volume semms to be dumb... Any help...

Device info - rooted, 4.0.2...
[OnePlus 3 Questions & Answers] Explorer23:
And what is "dumb volume" supposed to mean?
[LeEco Le Pro3 Questions & Answers] slgooding:
Is it possible to get dash charge working on our device?
[LeEco Le Pro3 Questions & Answers] GalaticStryder:
No.

By far, not possible, you need the OnePlus blob for it, the Kernel driver and the needed changes in AOSP system/core code to make it possible.

Even coding the Kernel part of it doesn't help much since OnePlus has obviously created strong checks on that level. LeEco has done some changes, though, to allow more current in the QPNP controller flux at the cost of battery heat throughput. In don't think those changes would make charging faster at a point that you sacrifice Qcom's recommended charging factors to get 5min less charging time, also battery safety on this device is a little doubtful since they adopted a cheaper manufacturer.

We'll see if some code from dash charge in Kernel is helpful and can be adapted but it's too early to say anything since I don't have my device in hands and I'd need to buy some electrical equipment to measure those properly.

What we can do is hack the code to allow user tweaking of the max allowed USB voltage to allow more throughput in current but that's unsafe for this kind of battery, I did this on my LG G2 but the battery in that device is well known and much smaller, safer in that case.
[LeEco Le Pro3 Questions & Answers] slgooding:
Thanks for the info. After reading about Dash, one of the great things about it is that the load (or whatever) is done in the power block and not on the device (unlike Quick Charge 3.0). That means that the OnePlus stays very cool during charging.

My main concern is premature battery wear considering the amount of heat generated during charging. It would be really nice to be able to limit the current to bring down the heat. Some of us don't really need to have this thing fully charge in a record amount of time :D. Maybe we cam add the capability to reduce the current, but not set it above default. I would be super happy if we could get a stock kernel with a modification that allows for this sort of change :).

Thanks!