Database Develop

[MM] [Flashable] Patcher to provide root access without /system modification

This patcher is now outdated. Use the new SuperSU instead. http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
This zip is a systemless version. That means that you'll get root and be able to use it normally, but your system partition will not be modified, like in normal root methods. Only for Marshmallow.
Keep reading for disadvantages and advantages
Chainfire had released a newer version of his SuperSU that doesn't need to modify the system partition to provide root access. This method doesn't have much of a practical application right now, but it allows you to flash OTA updates without having to unroot or flash the stock system partition.
HOW TO USE:
If you have rooted before, flash the system partition (or reinstall the ROM) before flashing this zip.
Download the attached zip, and flash it from a recovery (I tested it with TWRP).
Download SuperSU 2.56 from here: http://forum.xda-developers.com/showpost.php?p=63197935&postcount=2 (Just download the apk)
Reboot to TWRP. If it asks you whether you want system to be mounted as r/w, and if you want to take OTAs later, choose to keep system read-only (this will replace TWRP with stock recovery on reboot).
Flash SuperSU-v2.56-20151030013730.zip
Reboot
TWRP will say that you are not rooted, just ignore that. Do not tell it to root it.
This will work with all Marshmallow kernels, even the stock kernel.
Drawback : A factory data reset will remove superuser privileges. If that happens, simply flash SuperSU-v2.56-20151030013730.zip again.
TO RECEIVE OTA UPDATES :
Just make sure not to do anything that modifies /system. For example, no build.prop changes, and no system app removal. Or even if you do these, make sure to undo these changes before flashing an OTA. You can flash OTAs without unrooting now.
Flash the stock boot.img for your current Android version before flashing OTAs.
BUGS :
I didn't find any, yet, but Chainfire wrote the following on his thread:
Apps with hardcoded paths to su (seriously?) will bork
Factory reset unroots
Factory reset wipes pin
...
Bugs... Bugs everywhere!
ADDITIONAL INFO :
This zip will replace sepolicy as mentioned on Chainfire's thread (thanks to @metaspook for the patched sepolicy, which I extracted from his zip), so you'll be able to get root access even on SELinux enforcing kernels (only the stock MM kernels right now). Also, you can flash any other kernel (as long as it comes in a zip format, not as an img) before or after flashing this, and you'll still have root access.

out386 said:
Chainfire had released a newer version of his SuperSU that doesn't need to modify the system partition to provide root access. This method doesn't have much of a practical application right now, but it allows you to flash OTA updates without having to unroot or flash the stock system partition.
HOW TO USE:
Download the attached zip, and flash it from a recovery (I tested it with TWRP).
Download SuperSU 2.56 (or newer, if it supports systemless mode) from here: http://forum.xda-developers.com/showpost.php?p=63197935&postcount=2 (Just download the apk)
Flash SuperSU-v2.56-20151030013730.zip
Reboot
This will work with all Marshmallow kernels, even the stock kernel.
Drawback : A factory data reset will remove superuser privileges. If that happens, simply flash SuperSU-v2.56-20151030013730.zip again.
TO RECEIVE OTA UPDATES :
Just make sure not to do anything that modifies /system. For example, no build.prop changes, and no system app removal. Or even if you do these, make sure to undo these changes before flashing an OTA. You can flash OTAs without unrooting now.
Flash the stock boot.img for your current Android version before flashing OTAs.
BUGS :
I didn't find any, yet, but Chainfire wrote the following on his thread:
Apps with hardcoded paths to su (seriously?) will bork
Factory reset unroots
Factory reset wipes pin
...
Bugs... Bugs everywhere!
ADDITIONAL INFO :
This zip will replace sepolicy as mentioned on Chainfire's thread (thanks to @metaspook for the patched sepolicy, which I extracted from his zip), so you'll be able to get root access even on SELinux enforcing kernels (only the stock MM kernels right now). Also, you can flash any other kernel (as long as it comes in a zip format, not as an img) before or after flashing this, and you'll still have root access.
Click to expand...
Click to collapse
Well done bro!
I'm just waiting for this

Help regarding installation
I am using MicroMax Android One with Marshmallow
Currently, I've not tired the phone.
When I open recovery, I see some options like Apply update from SD card, mount, cache wipe, factory reset, etc.
So which option should I use to flash the zip file.

out386 said:
Chainfire had released a newer version of his SuperSU that doesn't need to modify the system partition to provide root access. This method doesn't have much of a practical application right now, but it allows you to flash OTA updates without having to unroot or flash the stock system partition.
HOW TO USE:
Download the attached zip, and flash it from a recovery (I tested it with TWRP).
Download SuperSU 2.56 (or newer, if it supports systemless mode) from here: http://forum.xda-developers.com/showpost.php?p=63197935&postcount=2 (Just download the apk)
Flash SuperSU-v2.56-20151030013730.zip
Reboot
This will work with all Marshmallow kernels, even the stock kernel.
Drawback : A factory data reset will remove superuser privileges. If that happens, simply flash SuperSU-v2.56-20151030013730.zip again.
TO RECEIVE OTA UPDATES :
Just make sure not to do anything that modifies /system. For example, no build.prop changes, and no system app removal. Or even if you do these, make sure to undo these changes before flashing an OTA. You can flash OTAs without unrooting now.
Flash the stock boot.img for your current Android version before flashing OTAs.
BUGS :
I didn't find any, yet, but Chainfire wrote the following on his thread:
Apps with hardcoded paths to su (seriously?) will bork
Factory reset unroots
Factory reset wipes pin
...
Bugs... Bugs everywhere!
ADDITIONAL INFO :
This zip will replace sepolicy as mentioned on Chainfire's thread (thanks to @metaspook for the patched sepolicy, which I extracted from his zip), so you'll be able to get root access even on SELinux enforcing kernels (only the stock MM kernels right now). Also, you can flash any other kernel (as long as it comes in a zip format, not as an img) before or after flashing this, and you'll still have root access.
Click to expand...
Click to collapse
Good work n thanks for mention bt can't understand why u created a patcher again where I'v already created one!
Its ok, good job.

Good.... Thanks for posting

metaspook said:
Good work n thanks for mention bt can't understand why u created a patcher again where I'v already created one!
Its ok, good job.
Click to expand...
Click to collapse
Yes, well, I would never have reposted the same thing, so, I'm sorry if it seemed like that.
This one uses Chainfire's new systemless root method. Unlike other root methods that need modifications to /system, this method uses modifications to the boot image to set up and run the su daemon from a loop device on the /data partition and achieve root. Right now, that doesn't have much of an advantage except to make flashing OTAs easier. Chainfire made it because future devices might need it. I made the patch because someone on FB asked about it.

<accidental double post, sorry. Can't delete>

kalpitandroid said:
I am using MicroMax Android One with Marshmallow
Currently, I've not tired the phone.
When I open recovery, I see some options like Apply update from SD card, mount, cache wipe, factory reset, etc.
So which option should I use to flash the zip file.
Click to expand...
Click to collapse
You need to install a custom recovery first. Go to the Android One (First generation) General forums on this site. You'll find a how-to at the very top of the list of threads. Once you have a custom recovery, flash this using the "install zip" option.

out386 said:
Yes, well, I would never have reposted the same thing, so, I'm sorry if it seemed like that.
This one uses Chainfire's new systemless root method. Unlike other root methods that need modifications to /system, this method uses modifications to the boot image to set up and run the su daemon from a loop device on the /data partition and achieve root. Right now, that doesn't have much of an advantage except to make flashing OTAs easier. Chainfire made it because future devices might need it. I made the patch because someone on FB asked about it.
Click to expand...
Click to collapse
Hmm... gotcha now.. Good work!
If u ever need any help just pm.
Thank you...

out386 said:
<accidental double post, sorry. Can't delete>
Click to expand...
Click to collapse

TWRP, System writing, Supersu, Impossible?

I have had my fair share of problems modifying android before but I have never had a phone flat out lie to me and say an operation was successful and actually nothing happened at all.
Have had my nexus 6 for a year or so now. Have had minor issues rooting / modifying marshmallow in the past but I figured out it was all caused by the system partition having basically 0 free space. Made a huge mistake and installed to the latest 7.0 OTA. Wanted to simply enable tethering and edit the thermal config to not shut cores down. Should be as simple as pulling the files, editing them, pushing them back to the phone in twrp with the system partition mounted and thats the end of it right? Wrong.
First of all twrp 3.0.2 refuses to let me touch the system partition without some giant prompt about how its going to make itself stick and offer to root the phone. Simple enough I have seen it in previous versions I say yes as usual except twrp proceedes to immediately spew a bunch of superuser files that do nothing throughout the system partition without asking me if I want root. Dumb but whatever. I mount /system as read write and I go edit and replace my two files like usual (build.prop and thermal config). No matter if I ADB push or use twrps built in file manager it claims the file replacement is successful. Reboot into android and not only have both files not been touched (Verified by adb pull) but the recovery gets overwritten with the factory recovery anyways. (NEVER had issues with twrp sticking on marshmallow. Now after every reboot it gets wiped out)
Second of all if I select yes to twrp mounting system as writable and it does its spewing as I mentioned before then installing SuperSU instantly causes the phone to not boot. Rewrite the boot.img to factory and it boots fine OR Rewrite the clean factory system image and the SuperSU boot works fine. But modifying /system with twrp and then running supersu at the same time is a no go. TWRP is obviously doing something stupid to system that pisses off supersu so undoing twrps mess or uninstalling supersu makes it bootable again.
I dont even want root! Everyone is claiming you need to run "settings put global tether_dun_required 0" as root along with adding the usual "net.tethering.noprovisioning=true" in the build.prop to get native tethering working again! On 6.X only the build.prop edit was needed to get it working.
So long story short. I just want native tethering to work and to tweak my /system/etc/thermal-engine-shamu.conf . Is there anyone here who has done this successfully on nougat? I feel like its all twrps fault but im far too tired and frustrated to try another version tonight.

You must be running an old version of TWRP. Update to the latest, as the latest no longer offers to root your device for you. The version of superuser included was ancient and caused the device to bootloop.
As to TWRP being overwritten Android 7.0 I believe does that on a stock system. If I recall, there is a script that needs to be modified to prevent it.

Strephon Alkhalikoi said:
You must be running an old version of TWRP. Update to the latest, as the latest no longer offers to root your device for you. The version of superuser included was ancient and caused the device to bootloop.
As to TWRP being overwritten Android 7.0 I believe does that on a stock system. If I recall, there is a script that needs to be modified to prevent it.
Click to expand...
Click to collapse
It's stated in the op he's using twrp 3.0.2.

Didgeridoohan said:
It's stated in the op he's using twrp 3.0.2.
Click to expand...
Click to collapse
I misread his post then. I wonder if perhaps he is running TWRP via fastboot instead of installing it.

Flashing recovery using "fastboot flash recovery XXX.img"

[DEPRECATED] [Module/Tool] [2018.10.9] F2FS Loopback Bug Workaround -- No Kernel Patch Needed

THIS PROJECT IS NO LONGER SUPPORTED.
# F2FS Loopback Bug Workaround
## README.md
### Copyright (C) 2017-2018, VR25 @ xda-developers
#### License: GPL v3+
---
#### DISCLAIMER
This software is provided as is, in the hope that it will be useful, but without any warranty. Always read/reread this reference prior to installing/upgrading. While no cats have been harmed, I assume no responsibility under anything which might go wrong due to the use/misuse of it.
A copy of the GNU General Public License, version 3 or newer ships with every build. Please, read it prior to using, modifying and/or sharing any part of this work.
To prevent fraud, DO NOT mirror any link associated with this project; DO NOT share ready-to-flash-builds (zips) on-line!
---
#### DESCRIPTION
Some kernels from devices with F2FS-formatted data partition (i.e., Motorola) have a bug which prevents loopback devices (.img files) from being mounted read-write. This limits systemless modifications that can otherwise be achieved with Magisk.
This module works by moving magisk.img to the cache partition (EXT[2-4]-formatted) and linking it to its actual location (i.e., /data/adb/magisk.img). The other half of the process consists on automatically recreating magisk_merge.img shortly after boot and handling it the same way as magisk.img.
With this workaround, a patched kernel is dispensable.
Cache partition's size is essentially the only limiting factor -- and that's pretty much self-explanatory.
/cache/magisk_.img is automatically backed up to/data/adb on boot (only if modified) & restored on install. Thus, whenever cache is wiped, magisk_.img and its respective symlink can easily be restored by simply reinstalling the module.
---
#### PRE-REQUISITES
- Magisk v15+
- F2FS-formatted data partition
- EXT[2-4]-formatted cache partition
---
#### SETUP STEPS
Fist time
- Install from custom recovery as a regular flashable zip.
Upgrades
- Install from Magisk Manager or custom recovery.
- Reinstall after cache wipes to restore magisk.img backup.
---
#### NOTES/TIPS
Always install large modules from custom recovery only. In fact, I recommend installing every module from recovery if your device's cache partition has a very small size (i.e., only a few Megabytes).
To revert changes, uninstall the module, boot into custom recovery and delete </data/adb/magisk.img> & <magisk.img.bkp>. Lastly (while still in custom recovery), move </cache/magisk_.img> to </data/adb/magisk.img>.
Updates and reinstalls can be carried out from Magisk Manager as well.
---
#### ONLINE SUPPORT
- [Facebook Support Page](https://facebook.com/VR25-at-xda-developers-258150974794782/)
- [Git Repository](https://github.com/Magisk-Modules-Repo/f2fs-loopback-bug-workaround/)
- [XDA Thread](https://forum.xda-developers.com/apps/magisk/guide-magisk-official-version-including-t3577875/)
---
#### RECENT CHANGES
**2018.10.9 (201810090)**
- Bug fixes
- Latest module template, with added sugar.
- Magisk 15-17.2 support
- Updated documentation
**2018.9.2 (201809020)**
- Improved compatibility
- Major optimizations
- Updated documentation
**2018.8.1 (201808010)**
- General optimizations
- Striped down (removed unnecessary code & files)
- Updated documentation
**2018.7.24 (201807240)**
- Fixed modPath detection issue (Magisk V16.6).
- Updated documentation

Works with stock roms as well ?

My cat lost two and half lives because of this thread. Sadly, the disclaimer is in order, so I can't sue.

Is this for Nougat or Marshmallow?

does this work on nougat update or only on MM?

Can someone please confirm if it will work on retin channel with dual sim... I am running stock nougat... Will it work or does it only work on MM rom...

Anybody know how to fix notifications without breaking safety net?

VR25 said:
DISCLAIMER
Not taking responsibility for any thermonuclear war or cat harm. Do it at your any risk.
NEEDED
[Unlocked Bootloader] https://youshouldknowthisbynow.com
[Latest TWRP] https://forum.xda-developers.com/mo...recovery-unofficial-twrp-moto-z-play-t3495629 credits @Alberto97
[Latest FSFS patched Kernel] https://forum.xda-developers.com/moto-z-play/development/kernel-stock-kernel-f2fs-patched-t3546732 credits @tomparr
[Latest Magisk zip] https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 credits @topjohnwu
[Latest Magisk Manager app] https://play.google.com/store/apps/details?id=com.topjohnwu.magisk&hl=en credits @topjohnwu
PROCEDURE
0. reboot bootloader
1. fastboot boot twrp.img
2. adb sideload fsfs patched kernel
3. adb sideload magisk
4. reboot system
5. install magisk manager from play store
6. reboot bootloader [yes, again]
7. fastboot boot twrp.img [yes, again]
8. adb sideload magisk [yes, again]
9. reboot system [yes, ag... you get the point]
10. open magisk manager settings, enable "magisk hide"
11. reboot, done
Click to expand...
Click to collapse
Works like a charm.
I however did not temporarly boot into TWRP, I flashed it as such.
mhp1995 said:
does this work on nougat update or only on MM?
Click to expand...
Click to collapse
I'm on Android 7.0 Nougat.
Thanks!
Erwin

fortunz said:
My cat lost two and half lives because of this thread. Sadly, the disclaimer is in order, so I can't sue.
Click to expand...
Click to collapse
Hopefully your cat is ok now
jjdavis699 said:
Is this for Nougat or Marshmallow?
Click to expand...
Click to collapse
mhp1995 said:
does this work on nougat update or only on MM?
Click to expand...
Click to collapse
mhp1995 said:
Can someone please confirm if it will work on retin channel with dual sim... I am running stock nougat... Will it work or does it only work on MM rom...
Click to expand...
Click to collapse
It should work on both Marshmallow and Nougat, as long as you pick the appropriate kernel for your system version (6 or 7). @mhp1995, I don't think the software channel matters. It should work across all (retus, retin , reteu, etc.).
xxBrun0xx said:
Anybody know how to fix notifications without breaking safety net?
Click to expand...
Click to collapse
No idea at this point, man. I've never had to fix mine. Perhaps only some people have it...?
@erwin, I chose not to touch the stock recovery to keep OTA installations straightforward. Easy for everyone.

one question... if i wanted to install viper4android and xposed framework, should i download it from the magisk download tab or shud i flash them manually via TWRP? thanks

mhp1995 said:
one question... if i wanted to install viper4android and xposed framework, should i download it from the magisk download tab or shud i flash them manually via TWRP? thanks
Click to expand...
Click to collapse
There are specific versions of these modified for systemless root. DO NOT install the standard versions. You should follow the instructions given in Magisk Manager app to download and install.

VR25 said:
There are specific versions of these modified for systemless root. DO NOT install the standard versions. You should follow the instructions given in Magisk Manager app to download and install.
Click to expand...
Click to collapse
Ok :good: I think xposed is not available at the moment for nougat ..Its WIP....If possible when the time comes try to include installing xposed via Magisk tutorial in this thread too.... Coming to the posts, u mind if i add this rooting tutorial in my all-in-one thread? Of course credits will be given

mhp1995 said:
Ok :good: I think xposed is not available at the moment for nougat ..Its WIP....If possible when the time comes try to include installing xposed via Magisk tutorial in this thread too.... Coming to the posts, u mind if i add this rooting tutorial in my all-in-one thread? Of course credits will be given
Click to expand...
Click to collapse
Oh, yes the availability... I forgot to mention that. Hopefully a proper Xposed version will be available for nougat very soon. When that happens, I'll update the thread.
About adding the tutorial to your thread... sure, go ahead.

I honestly declare I didn't read whole thread - is this method work for stock Nougat rom - I need root for Titanium Backup only for now , since facebook messenger goes crazy on my new phone MZP :-/ . Or maybe there is a way to restore old conversations ,not restored automatically in Facebook Messenger - anybody knows how to do it ? . On every phone I had I used root for two things mainly - Titanium Backup and to block adds - dns66 do block adds very well without root but , Titanium Backup has no alternative for me .

Just for the records: Magisk 12 release works fine.
@sebx_g1 incredible 2 pages! That are more than 10 postings! Sure nobody can read so much. And nearly all ask or answer your question, but it is just too much ...

tag68 said:
Just for the records: Magisk 12 release works fine.
@sebx_g1 incredible 2 pages! That are more than 10 postings! Sure nobody can read so much. And nearly all ask or answer your question, but it is just too much ...
Click to expand...
Click to collapse
[emoji4] but voting is only 3 works 2 not, so?
Wysłane z mojego XT1635-02 przy użyciu Tapatalka

What is expected to be done for next OTA to work? Just restore Nandroid backup of boot partition and everything should be ready for patchlevel newer than January 2017, right? And afterwards f2fs fixed kernel and Magisk again for having root again of course.
(twrp not flashed, no logo modified, system should be untouched)
---------- Post added at 09:14 PM ---------- Previous post was at 09:11 PM ----------
sebx_g1 said:
[emoji4] but voting is only 3 works 2 not, so?
Click to expand...
Click to collapse
Xposed does not work on Nougat by now. Magisk does. The 2 negative votes you counted referred to Xposed

Anyone have an adblock that works with systemless and passes safetynet? Do we need to check the "enable systemless for adblocks" in Magisk settings?

DNS66 do the same what do adblock, you can use it without root. But yes, there is special version of adblock systemless.
Wysłane z mojego XT1635-02 przy użyciu Tapatalka

Worked fantastically, thanks a lot!

future of SuperSU vs. Magisk

The guy who made SuperSU, @ChainfireXDA , retired from SuperSU. 2.82 SR5 was his last beta release. Some Chinese owned company named CCMT bought SuperSU a while back, but @ChainfireXDA retired from the aforementioned on 03OCT2017 (10th anniversary). https://plus.google.com/+Chainfire/posts/6Sp6t9LxtQZ
https://desktop.firmware.mobi
https://www.chainfire.eu
SuperSU at XDA
https://forum.xda-developers.com/apps/supersu
So, since nothing has yet been posted by CCMT for SuperSU (as of 14NOV2017), it seems that @topjohnwu Magisk will become more prominent.
Magisk at XDA
https://forum.xda-developers.com/apps/magisk

The purpose of this thread was what exactly?

choosing rooting app for OEM unlocked Moto Z2 Force
TheKnux said:
The purpose of this thread was what exactly?
Click to expand...
Click to collapse
Since Moto Z2 Force Sprint and T-Mobile variants are OEM unlockable, the long term choice of a systemless root for an OEM unlocked Moto Z2 Force seems to be a relevant topic for discussion and/or news for Moto Z2 Force. I wanted SuperSU to be developed further by @ChainfireXDA , but his retirement from SuperSU likely means that to get the most up-to-date systemless rooting app for my OEM unlocked Moto Z2 Force, I will have to soon switch to @topjohnwu Magisk.

The point of this thread was that we had to work extra hard for magisk support and we now have it via mine and @Uzephi kernel we have figured out why there are bootloops and will be adressing here shortly

On OEM unlocked T-Mobile Moto Z2 Force with latest TWRP (as of 15NOV2017), I just switched to Magisk 14.3 beta from SuperSU 2.82 SR5 beta w/SU Hide 1.09. In this long process, I lost all my data because Magisk 14.3 beta did not properly disable force encryption! I really didn't think it was going to be as hard as it was. It absolutely refused to boot properly with default upstream kernel (i.e., that comes along with latest TWRP; kernel probably soon to be tweaked per previous post) and latest Magisk 14.3 beta no matter how many times I formatted data, etc. I ended up having to use SuperR's Kitchen free for Linux.
SuperR's Kitchen free for Linux
https://forum.xda-developers.com/apps/superr-kitchen/kitchen-superr-s-kitchen-v1-1-50-v2-1-6-t3597434
SuperR's Kitchen donate version for Windows/Linux
https://forum.xda-developers.com/apps/superr-kitchen/windows-linux-superr-s-kitchen-v3-0-0-0-t3601702

jhofseth said:
On OEM unlocked T-Mobile Moto Z2 Force with latest TWRP (as of 15NOV2017), I just switched to Magisk 14.3 beta from SuperSU 2.82 SR5 beta w/SU Hide 1.09. In this long process, I lost all my data because Magisk 14.3 beta did not properly disable force encryption! I really didn't think it was going to be as hard as it was. It absolutely refused to boot properly with default upstream kernel (i.e., that comes along with latest TWRP; kernel probably soon to be tweaked per previous post) and latest Magisk 14.3 beta no matter how many times I formatted data, etc. I ended up having to use T-Mobile 05AUG2017 kernel, no-verity-opt-encrypt-5.2 (attached), and Android Terminal TWRP Installer. But the important thing is Magisk 14.3 beta is finally working with latest Moto Z2 Force TWRP!
Click to expand...
Click to collapse
Interesting experiment... two questions:
1. have you tried using flashable zip to unforce encryption for "any kernel" by @erfanoabdi on our device?
2. since latest TWRPs by @joemossjr come with a (little) modified/recompiled kernel, why don't disable forced encryption by default on them?

enetec said:
Interesting experiment... two questions:
1. have you tried using flashable zip to unforce encryption for "any kernel" by @erfanoabdi on our device?
2. since latest TWRPs by @joemossjr come with a (little) modified/recompiled kernel, why don't disable forced encryption by default on them?
Click to expand...
Click to collapse
i didn't read thread and other posts but please don't install my zip here
that will harm the device in worst way
1) Z2 have a/b boot partition
2) different fstab and partition table
@enetec remove my flashable zip from your old post

erfanoabdi said:
...
@enetec remove my flashable zip from your old post
Click to expand...
Click to collapse
:good:
P. S. : Welcome back pal!
P. P. S. : we *want* you on Z2!!!

re-encrypting not due to upstream kernel with TWRP
enetec said:
Interesting experiment... two questions:. ....
2. since latest TWRPs by @joemossjr come with a (little) modified/recompiled kernel, why don't disable forced encryption by default on them?
Click to expand...
Click to collapse
The re-encrypting was not the fault of the upstream kernel with TWRP, it was that the 14.3 beta Magisk didn't properly disable force encryption in a stock boot image. It errored & told me to use a stock boot image during Magisk direct install (i.e., inside Magisk manager), so I dd flashed a stock boot image and FlashFire flashed Magisk right afterward. Yeah.....force encryption fun! Eventually, I ended up having to use SuperR's Kitchen free for Linux. All's well that ends well.
SuperR's Kitchen free for Linux
https://forum.xda-developers.com/apps/superr-kitchen/kitchen-superr-s-kitchen-v1-1-50-v2-1-6-t3597434
SuperR's Kitchen donate version for Windows/Linux
https://forum.xda-developers.com/apps/superr-kitchen/windows-linux-superr-s-kitchen-v3-0-0-0-t3601702

jhofseth said:
The re-encrypting was not the fault of the upstream kernel with TWRP
Click to expand...
Click to collapse
Never intended that... I was only asking why don't include directly in modified kernel the possibility to remain unencrypted...

enetec said:
Never intended that... I was only asking why don't include directly in modified kernel the possibility to remain unencrypted...
Click to expand...
Click to collapse
I think @joemossjr and @Uzephi try, but this encryption can be frustrating. Many techniques that are supposed to stop it don't work properly. Somehow SuperSU 2.82 beta SR5 does a good job of stopping it when installed systemlessly. No version of Magisk that I've tested stops encryption on our phone--even though it is supposed to stop force encryption by default.

jhofseth said:
I think @joemossjr and @Uzephi try, but this encryption can be frustrating. Many techniques that are supposed to stop it don't work properly. Somehow SuperSU 2.82 beta SR5 does a good job of stopping it when installed systemlessly. No version of Magisk that I've tested stops encryption on our phone--even though it is supposed to stop force encryption by default.
Click to expand...
Click to collapse
user data is formatted f2fs and system/boot/etc ext4. SU decrypts both while magisk sees f2fs and decrypts only f2fs partitions.

Flashable unencrypter must format data will not work on stock kernel. But will with twrp.
https://drive.google.com/file/d/1Cr-7SiSiHpUDM9HYpyeXVsPHEB9Z9wym/view?usp=drivesdk

enetec said:
Never intended that... I was only asking why don't include directly in modified kernel the possibility to remain unencrypted...
Click to expand...
Click to collapse
the "encrypt" part is in /system, not kernel. I can add a module when I build with anykernel to do the same thing as joemoss's zip. But it isn't the kernel. The kernel will work both encrypted and decrypted.

Uzephi said:
the "encrypt" part is in /system, not kernel. I can add a module when I build with anykernel to do the same thing as joemoss's zip. But it isn't the kernel. The kernel will work both encrypted and decrypted.
Click to expand...
Click to collapse
I could be wrong, but I have maturated the idea that disabling force encryption is one of (many...) things which can be done both working on /boot or /system....
I had posted @erfanoabdi script for Moto Z (Griffin) even to have it studied for an eventual porting... (I'm quite sure it works on /boot... )
More... I think even SuperSU method could work on /boot: if it worked modifying /system, a kernel reflashing shoudn't disable it's tweak... am I wrong?

enetec said:
I could be wrong, but I have maturated the idea that disabling force encryption is one of (many...) things which can be done both working on /boot or /system....
I had posted @erfanoabdi script for Moto Z (Griffin) even to have it studied for an eventual porting... (I'm quite sure it works on /boot... )
More... I think even SuperSU method could work on /boot: if it worked modifying /system, a kernel reflashing shoudn't disable it's tweak... am I wrong?
Click to expand...
Click to collapse
AnyKernel pulls apart the boot image and injects the kernel. it doesn't put the image back correctly. to try this, dd pull your boot image and play with AIK (linux solution to manually add a kernel). Don't edit anything and it will lose root as well when you reflash the repacked boot image. it is something in the ramdisk that doesn't get saved.

Uzephi said:
AnyKernel pulls apart the boot image and injects the kernel. it doesn't put the image back correctly. to try this, dd pull your boot image and play with AIK (linux solution to manually add a kernel). Don't edit anything and it will lose root as well when you reflash the repacked boot image. it is something in the ramdisk that doesn't get saved.
Click to expand...
Click to collapse
Understood. But @ChainfireXDA should have found a solution to this... or not?

enetec said:
Understood. But @ChainfireXDA should have found a solution to this... or not?
Click to expand...
Click to collapse
How can he? he doesn't have the device to test this out. He just patches the boot image the normal way like other devices. (albeit it took some community testing to get the boot image and ramdisk to work for our device, but hey, you get what you can when the dev doesn't have your device)

enetec said:
Understood. But @ChainfireXDA should have found a solution to this... or not?
Click to expand...
Click to collapse
@Uzephi wrote, "data is formatted f2fs and system/boot/etc ext4. SU decrypts both while magisk sees f2fs and decrypts only f2fs partitions."
So, I think that's why when we formatted data ext4 in TWRP, SuperSU 2.82 beta SR5 was OK but not so for Magisk.

Ok what uzephi is trying to say is encryption in handled in our fstab.qcom. which if you have a stock kernel it's gonna be in there and one's gonna be in system and another in system_root. So in the fstab there is this line for userdata which isn't used as you can see the # means it's not used. When magisk sees this because it's right above our userdata it modifies the "forceencrypt" part to "encryptable" which allows decryption on the f2fs partition but we don't use that. Follow me? Now below that one is ours. And where you see the term "fileencryption" that's just another term for force encrypt. So when magisk is flashed it only sees the one above it and changes it and goes on. Now the difference between magisk and supersu is supersu looks for terms like "verify" for dm verity and "forceencrypt" for encryption and also "fileencryption" and removed the verify term to remove verity and changes all the above terms if noticed to "encryptable" instead of going line by line supersu does it better. Now if you have twrp it has a fstab in it that patched already but what I forgot to check is where twrp puts it and where it puts it is n in the root of our device where it doesn't belong. So that's why I made a flashable zip that sends that modified fstab to system where when the system boots it will see the new modified fstab and realize that it can boots.
#/dev/block/bootdevice/by-name/userdata /data f2fs rw,discard,nosuid,nodev,noatime,nodiratime,nobarrier,inline_xattr,inline_data wait,check,formattable,forceencrypt=/dev/block/bootdevice/by-name/metadata
/dev/block/bootdevice/by-name/userdata /data ext4 nobarrier,noatime,nosuid,nodev,discard,data=ordered,noauto_da_alloc wait,check,formattable,fileencryption=ice

So I have a few questions

some information: I have a rooted with magisk moto g(6). if you need more information, just ask.
question 1: probably the most important one, my USB debugging keeps turning off. after a reboot, it was on before I rebooted but now it's off. I want to know how to fix this and what in the world is making this happen.
question 2: my sim card isn't being detected, I don't know id this is related to my IMEI number being unknown which leads to my next question...
question 3: why is my IMEI number unknown? this one is self-explanatory and I don't know how to explain it more
Question 4: final question, can I update. I am running android 9 with security patch January 1, 2019.
this is my first post here and I hope I didn't make any errors. if you have an answer for any of these questions, please share your knowledge.
I have fixed questions 2 and 3 by reflashing stock images a few times
I also believe that fixed question 1 so now I just really need to know how to update

I have the same problem that USB debugging is switching off after a reboot. I'm on stock, rooted with magisk. Do really fix that problem for your device?
You can update to the latest security patch. There are no issues but a little bug related to Magisk. The latest v20.3 causes a bootloop when it's being installed on a clean and fresh stock rom. The solution is flashing v19.3, boot your device and update it through the Magisk Manager to v20.3.
Don't ask me why but it works.

WoKoschekk said:
I have the same problem that USB debugging is switching off after a reboot. I'm on stock, rooted with magisk. Do really fix that problem for your device?
You can update to the latest security patch. There are no issues but a little bug related to Magisk. The latest v20.3 causes a bootloop when it's being installed on a clean and fresh stock rom. The solution is flashing v19.3, boot your device and update it through the Magisk Manager to v20.3.
Don't ask me why but it works.
Click to expand...
Click to collapse
O that sounds like it would work, I used to flash 16 something because I didn't know 19.3 worked, definitely gonna make a few backups too

16??

WoKoschekk said:
16??
Click to expand...
Click to collapse
Yes I saw it in a guide once. Why can TWRP sometimes not see my internal storage, it says there is 0 bytes there. Also if my backup is in internal storage, does that mess anything up?
O and when I try to update, it loads into TWRP recovery. Help.

I think the best way is to give you a complete guide...
But this only works for PPSS29.55-37-7-2.
If your current FW is PPSS29.118-15-11-2 this method ends up in a bootloop!! Then follow this thread, please.
Find below two download links. One of them is the fstab.zip which contains the patched fstab.qcom file. Unzip it and put the file somewhere accessible for you while following this guide.
BACKUP YOUR DATA IF POSSIBLE!
I AM NOT RESPONSIBLE FOR ANY DAMAGES ON YOUR DEVICE!
1.) Flash the latest firmware based on your software channel from here
2.) Let the phone boot to "Hello Moto" just to be sure everything is fine.
3.) Reboot to bootloder and flash the latest TWRP via fastboot.
4.) Boot directly into recovery by choosing it in the bootloader's menu.
5.) The first boot takes a few seconds and then TWRP requests a password to decrypt /data => press "cancel"
6.) Format /data (do not wipe) to remove encryption. After that format /data a second time and reboot into recovery.
7.) Format /data again.
8.) Now mount /vendor, open the file explorer and go to "/vendor/etc" and erase the file "fstab.qcom". Copy the patched file in this directory. This will disable forceencryption on your device. The trick is to replace the word "forceencryption" by "encryptable" in line 9.
9.) Open the terminal and type these commands:
Code:
cd vendor/etc
chmod 644 fstab.qcom
touch -r gps.conf fstab.qcom
With the last command (it's optional) you restore the original timestamp of the file by copying it from another. I use gps.conf because it's pretty short and fast to type.
Check the commands with
Code:
ls -l fstab.qcom
The output should look like this:
Code:
-rw-r--r-- 1 root root 1680 2009-01-01 07:00 fstab.qcom
It's very important to have the right permissions -rw-r--r-- root root
10.) Almost done... Flash Magisk v19.3 and not the latest v20.3 or you will get a bootloop.
I don't know why it bootloops... But AFAIK the only difference between those versions are the signing keys that are used to sign the boot.img after patching it with Magisk.
While installing Magisk the .zip disables dm-verity so you don't need an additional tool for that.
11.) If you like you can delete some system apps or what ever you want.
12.) It's done! Reboot to system and enjoy your rooted and unencrypted Moto g6 with disabled dm-verity!!
Don't panic if your device reboots one time after a few seconds. That's normal.

I wish I knew about the fstab file, I assume it removes the need to do the formatting but I already set up everything after I figured the update thing out. Would it be worth it to try and do the fastab?
Also why does it say I can turn OEM unlocking on again in my developer settings? I find that weird. And why when I boot up do I get a screen like this
YOUR DEVICE HAS BEEN UNLOCKED AND CANT BE TRUSTED
(My code here)
Contact something
ID:
YOUR PHONE WILL BOOT IN 5 SECONDS
I would think that my code would be where it says ID. Also it's as accurate as I can make it but in reality the code is overlapping the contact stuff. Just wondering if this is normal or if it's a sign that my phone's gonna explode or something. And are there any custom ROMs I should look into?

What exactly is the problem??
---------- Post added at 07:18 AM ---------- Previous post was at 07:08 AM ----------
To solve all the issues with your device you should flash a clean stock rom to get things into shape. There're several things messed up on your phone I think. A clean installation is the basic for all.

Bulbasaur Army said:
Would it be worth it to try and do the fastab?
Click to expand...
Click to collapse
Encrypted = you have to format /data every time before you are going to use TWRP
Decrypted = TWRP works perfect
Bulbasaur Army said:
Also why does it say I can turn OEM unlocking on again
Click to expand...
Click to collapse
Magisk enables the verity_state which leads to those options.
Bulbasaur Army said:
YOUR DEVICE HAS BEEN UNLOCKED AND CANT BE TRUSTED
(My code here)
Contact something
ID:
YOUR PHONE WILL BOOT IN 5 SECONDS
Click to expand...
Click to collapse
really?
---------- Post added at 10:29 AM ---------- Previous post was at 10:23 AM ----------
What about learning some basics before modifying your device?? I don't get in a car, sit down behind the wheel without even knowing how to drive.
I gave you a very detailed instruction about how to root your device. You will finally manage to get root or not.

I see, I already had my phone rooted but I didn't see the guide for fastab so I was wondering if I should apply it, I will attempt to do so later today. Thank you for all the help you have given.
PS: what does the "---------- Post added at 10:29 AM ---------- Previous post was at 10:23 AM ----------" is it part of XDA?