Hey guys, i just bought the phone and flashed zips immediately But have a question as i've never encrypted my phones till now(it's forced). So i'm on stock kernel and latest 4.5.14 Nolimits rom. Now I want to install xposed, bluspark kernel and remove the encryption from my device(i read something like a dm-verity disabler). Which order and method I should chose to flash those ? I saw something about decyrpted device in the first page of the rom's aroma installer and an option for the xposed but not sure and i don't want any bootloops
Thanks!
I was waiting for a root enabler for oreo (41.3.A.2.24), and I could find https://forum.xda-developers.com/xperia-x-performance/how-to/guide-stock-kernel-root-twrp-drm-fix-41-t3711837.
But this link is for version 41.3.A.0.401 and it does not work for everybody including me.
Since androplus still didn't bring out a new version of his kernel I tried the method from the above link.
But I'm using newer versions than in the description, I use TWRP 3.2.0, Magisk manager 5.2.2 and Magisk 15.2.
I can install the new version, twrp, the new boor image and Magisk 15.2.
I can boot and Magisk runs but the Safetynet control failes and Magisk does not enable root.
On the installation of the boot image, twrp and magisk I got some messages (marked in red)
unable to mount storage
failed to mount
Before I tried with magisk manager 5.5.1 and magisk 15.1 but then I got stuck at boot time at the sony logo.
Does anybody have a way to root Oreo (the latest version), enable DRM and enable root?
Ok I started all over again and I noticed I didn't follow the procedure first time.
So I excluded the FOTA kernel but whatever else I check no full wipe is done, I can always see the previous installed apps, it does not matter if I check Cust-reset, master-reset or reset-wipe-reason, the system is not wiped.
So that's my first problem, how to wipe the previous install.
Flashing the rom seems to be OK, same thing for flashing boot_oreo.img and twrp-3.1.1-0-dora.img.
I'm not sure about twrp 3.2.0.0 because this version is off-line now, so I tried with TWRP 3.1.1.0 and 3.2.1.0 but they all gave me the same result.
Problems start when I have to flash drmfix.zip, safety-net cleaner or magisk 15.2. The procedure tells me the flash is ok but have a look at thet attached images, I get errors while flashing. One picture for drmfix, one for safety-net-cleaner and one for magisk 15.2
After flashing all of this I can boot successfully but when I try to get root in ES File Explorer pro, it does not work. When I go into Magisk and try the afety-net check I get ctsProfile false and basicIntegrity False.
So the rom does work but I do not get root.
I tried all of this with the Italian rom 41.3.A.2.24.R1E ? I can start all over again with the UK version 41.3.A.2.24.R2E but I do not know if this makes any sense.
So can anybody tell me what to do to get it all going?
deboopi2 said:
I was waiting for a root enabler for oreo (41.3.A.2.24), and...
Click to expand...
Click to collapse
1 - Do use always Adrian DC latest fully working TWRP build for dora.
2 - You don't need a 3rd party kernel to achieve that, instead, you can easily create your own one, based always on stock kernel!
Thats the SELinux's problem.
Flash this first then flash magisk
https://forum.xda-developers.com/xp...ment/mod-sony-stock-patcher-xperia-x-t3528148
Hi guys, just some hours ago i got into a problem (at least for me).
I switched today from LineageOs 14.1 to AospExtended Oreo and since i can't use LineageOs root and i don't trust SuperSu anymore (because CodingCode), the only root available for me is Magisk.
Now i have flashed Magisk and set up some modules and the root itself is working, but i cannot delete system apps and modify /system in general. I haven't faced this problem in LineageOs (also with magisk).
And yes, i have tried "reboot disemmcwp" and it didn't work.
I am on A2017G, TWRP 3.2.1.7 (Nfound's build).
Thanks in advance for the answers.
EDIT: I FOUND A SOLUTION (KIND OF)
The situation, however turned out a bit different. At first i thought it was magisk messing with zte's system write protection, but it turned out that the culprit was actually SdMaid. Yep. It has a bug, so when you install a module that REPLACES a system app, like Vanced Youtube, it cannot recognize all the links and tricks that Magisk does and screws up everything, showing /system as read only and if you try to uninstall any system app with its inbuilt app manager, it makes Android crash.
There are 2 possible causes:
1. Magisk
2. You're on the B35 bootstack
I had your issue with Magisk before. Personally, I still think SuperSU can be trusted. But if you're willing to try it again, you should know that it will cause a bootloop with Oreo. It's because of the dtb patching. But I figured out how to make it work anyway. Download the SuperSU 2.72 SR5 zip. Unzip the file into a folder. Then open /meta-inf/com/google/android/update-binary in a text editor. Search for all instances of dtb, and change true to false. Save the file, and create a new zip. Then get the Aroma SuperSU Config zip. In TWRP, flash the config zip first. Select sbin mode on the first page, on 2nd and 3rd pages just use default options or whatever you want. Then flash your modded SuperSU zip. You should be able to boot. All works fine for me.
The 2nd possibility is that you are using the B35 bootstack. There is an issue with it where root appears to work but system partition can't be changed no matter what you do. You need to find a B32 bootstack zip and flash that instead.
I personally am using AOSP Extended Oreo, with B32 bootstack and SuperSU, all is fine so far. I can modify system partition too. If you need more clarification then just ask.
Good luck!
I've used the "disemmcwp" option in nfounds twrp options and it worked for me.
AnonVendetta said:
There are 2 possible causes:
1. Magisk
2. You're on the B35 bootstack
Click to expand...
Click to collapse
Wow, thanks for the fast answer!
I am currently using the B32 bootstack (also from Nfound), so the culprit must be Magisk (unfortunately).
I think i will try your method in the next days, meanwhile i will post this in the Magisk thread, maybe they have some clues about this.
Sent from my ZTE Axon 7 using XDA Labs
Modded SuperSU zip is attached.....
Modded B32 bootstack:
https://forum.xda-developers.com/attachment.php?attachmentid=4427264&d=1519249436
Aroma SuperSU config:
http://download.chainfire.eu/1121/SuperSU/AROMA-SuperSUConfig-v1.00.zip
Magisk uninstaller:
http://tiny.cc/latestuninstaller
Flash Magisk uninstaller, B32 bootstack, Aroma SuperSU config, then modded SuperSU, in that order. Go to /system/xbin and delete the su file, it will interfere with SuperSU. Wipe cache/dalvik cache and reboot. And run the "reboot disemmcwp" (as root, or with ADB), for good measure. You should be able to modify /system now.
Thanks, really.
Sent from my ZTE Axon 7 using XDA Labs
Ok, i did exactly what you said, but i ended up with a bootloop :/
But after dirty flashing my rom and Magisk and reboot disemmcwp in twrp, guess what? I got complete access to /system. That's wizardry my friend.
wannaskoo said:
Ok, i did exactly what you said, but i ended up with a bootloop :/
But after dirty flashing my rom and Magisk and reboot disemmcwp in twrp, guess what? I got complete access to /system.
Click to expand...
Click to collapse
Just for the sake of knowledge i should report that, after many tries, i discovered something interesting (at least for me). Magisk IS actually messing with system write protection, but only if you have any modules enabled. I have Ainur Sauron, Deep_buffer remover, Dolby Atmos for Oreo, AudioModLib, Youtube Vanced and Syspatch as Magisk modules, and i can't touch system in any way after booting into AEX, but if i enable Magisk Core mode and reboot i get complete access to /system.
I hope this thread will be useful for someone having problems with Magisk, because it is a great tool for modding and rooting, but i do really care to have /system access, that's the point of custom roms (for me).
Sent from my ZTE Axon 7 using XDA Labs
wannaskoo said:
Just for the sake of knowledge i should report that, after many tries, i discovered something interesting (at least for me). Magisk IS actually messing with system write protection, but only if you have any modules enabled. I have Ainur Sauron, Deep_buffer remover, Dolby Atmos for Oreo, AudioModLib, Youtube Vanced and Syspatch as Magisk modules, and i can't touch system in any way after booting into AEX, but if i enable Magisk Core mode and reboot i get complete access to /system.
I hope this thread will be useful for someone having problems with Magisk, because it is a great tool for modding and rooting, but i do really care to have /system access, that's the point of custom roms (for me).
Sent from my ZTE Axon 7 using XDA Labs
Click to expand...
Click to collapse
Thanks. I would recommend you report this on the Magisk Thread
Yep, i will do that.
Sent from my ZTE Axon 7 using XDA Labs
I won't go into the mentioning the whole Technical details of the project treble here. Giving you links to the Pages and threads that have dedicated their time into explaining it in the best possible manner.
XDA thread
https://www.xda-developers.com/how-project-treble-revolutionizes-custom-roms-android-oreo/
Android Authority
https://www.androidauthority.com/project-treble-818225/
Project Treble
https://forum.xda-developers.com/project-treble
Due to the unofficial implementation of Treble ROMs, a new partition called 'Vendor' Partition is introduced. This gives the noobs like me a huge headache as most of the programs and modules including magisk give errors while trying to flash them. This has led to all the threads being flooded with the same questions again and again without much help.
I thought of compiling all the problems and providing all the solutions to the problems.
All the Treble ROMs and GApps packages can be installed by any latest recovery coz 'mido' phones have unofficial Treble builds which is done by tweaking some partitions. The recovery software or the phone firmware is not aware of it and can't distinguish between the two.
The problems arise when one tries to flash the modules or rooting softwares. The most common error is 'Error:1' 'Can't mount the vendor partition'.
Getting Started
You need to have a treble enabled Custom Recovery.
TWRP Exclusive 3.2.1-7 by @NFound
This recovery would show the 'cust' partition as 'vendor'. Thus solving all the errors regarding the Vendor partition.
Most of the oreo 8.1.0 ROMs are Treble enabled as of now. But this recovery will support non Treble ROMs as well without any problem. Below are the list of ROMs available for Mido.
Oreo ROMs
All ROMs
Root
The official Magisk thread is flooded with the same question of Error:1 can't mount vendor.
The official version(16.0) doesn't throw an error when flashed with treble enabled recovery but the phone goes into a bootloop. A customized version of magisk for Treble ROMs is required to solve this issue.
Magisk 16.4 - Treble by @Nurananto
Tip : Install Magisk Manager before flashing Magisk in recovery. Can solve 'app not installed' errors while updating Magisk Manager.
Unistalling magisk cannot be achieved by the Magisk Uninstaller. Extract the 'boot.img' from your ROMs flashable zip and flash it using TWRP recovery.
Boot into recovery -> Install -> Install Image -> boot.img -> click on boot -> Reboot.
Reflashing Magisk will return all the Modules without any problems.
Tip : This trick can be used if any module or magisk runs into error or keeps stopping. It can also be used for updating Magisk to the latest version.
Im searching for a Rom with mock location Support
I dont find one thats run with magisk
Only bootloop and encryption error
Please help
Noel87 said:
Im searching for a Rom with mock location Support
I dont find one thats run with magisk
Only bootloop and encryption error
Please help
Click to expand...
Click to collapse
From my experince, the mock location support is just a module for flashing on magisk manager (found in modules part). I am currently using LOS 15.1 (Lineage OS) unofficial with su acces provided by Magisk. For disabled encryption you can flsh no verfiy opt-encrypt 6.0.zip (works for me) to remove encryption on internal storage (flashed using TWRP/ or any custom recovery)
Sent from S7 edge running LOS 15.1 (Android 8.1)