Database Users

[Guide]Flash Root/Xposed - Differences between System and Systemless Mode

Because several Users have problems with understanding what they actually should do i think the easiest way is writing some How-to.
Guide for Unlocking Bootloader Backup TA and so on
I AM NOT RESPONSIBLE FOR ANY DAMAGES THAT MAY CAUSE YOUR DEVICE
Your Bootloader must be unlocked and TWRP recovery installed.
1. Systemless Root/Xposed
Systemless Mode means that there is no File changed in your System Partition, this works because the main changes are made in the Kernel and not to the Android System itself. Because of this you have a special file on your Internal Memory in /data/ for Systemless Root you get a su.img file and for Systemless Xposed you get a xposed.img file. If you have both sure there are both files present. These files are loaded while your device is booting before the Android System is booting. This is good for us because we can easily Update our Systems (on same Rom).
1.1 Download latest beta-superSU/systemless xposed framework and place them on your sdcard.
1.2 Reboot into recovery and flash beta-superSU/systemless xposed framework (if both, in that order)
1.3 clear cache/dalvik
1.4 reboot
2. System Root/Xposed
With System Mode your changes are direct on the System Partition and mostly Updates dont work.
2.1 System Root is not available for our Device with MM. Download latest beta-superSU/xposed Framework and place them on your sdcard.
2.2 Reboot into recovery and flash beta-superSU/xposed framework (if both, in that order)
2.3 clear cache/dalvik
2.4 reboot
3. Change your Kernel while having a Systemless modified Android
Because the changes that were made while flashing Systemless Root/Xposed, your System wont work with just flashing the new Kernel.
3.1 Download the new Kernel to your Computer (make sure it is with TWRP or you flash it seperate after flashing the Kernel).
3.2 Download latest beta-superSU/systemless xposed framework and place them on your sdcard.
3.3 Reboot your device into fastboot mode and flash the new Kernel "fastboot flash boot xxxx.img"
3.4 Reboot your device into TWRP and flash beta-superSU/systemless xposed framework (if both, in that order)
3.5 clear cache/dalvik
3.6 reboot
4. Switch between System and Systemless Mode
For Switching from System Mode to Systemless with Xposed:
4.1 Update or install Material Design xposed installer App
4.2 Download the usual xposed uninstaller zip and the systemless xposed framework for your device
4.3 Open Material Xposed Installer and deactivate the framework
4.4 Reboot into recovery
4.5 Flash the uninstaller zip
4.6 clear cache/dalvik
4.7 Flash systemless xposed framework
4.8 reboot into System (take a few minutes)
4.9 Open Material Xposed Installer and activate Systemless Xposed framework
4.10 reboot
5. Delete / uninstall Systemless Root/Xposed
5.1 Open Material Xposed Installer and deactivate the framework
5.2 restart your System
5.3 Use an Explorer with root access and delete the files "/data/su.img" and "/data/xposed.img"
5.4 restart your System
If i forgot something please tell me i will add it.
Regards

make this for locked bootloaders :/

Can you please provide the link for systemless xposed file??

Could use some help

Hi everyone,
I have a s4 Active sgh i537. I want to have Lollipop and Xposed installed. To this end I flashed it back to Kitkat, towelroot'd it, flashed the I537_OC7_Stock_Rooted_Deodexed_ROM to preserve the root. I've tried to use the recovery option that comes with the rom to flash the Xposed framework and install the apk but Xposed said that the framework wasn't installed. Figured that the rom doesn't come with a custom recovery. Then I tried afterwards to flash the framework using flashfire the same way I flashed lollipop. The att splash screen load and got stuck for over 6 hours.
I'm going to try reflashing kitkat and starting over but I was wondering if I'm doing something wrong.
rom: http://forum.xda-developers.com/galaxy-s4-active/general/how-to-update-to-i537oc6-5-0-1-t3089355
Xposed framework SDK21 arm v86: http://dl-xda.xposed.info/framework/sdk21/arm/
Edit 1: went through again and I learned I needed the touchwiz Xposed Framework. Installed and my phone now can run Lollipop and install Xposed
New question regarding adb. I'm trying to install MicroG and I can't seem to connect adb and my phone together to remove the /system/priv-app/ and /system/app/ prerequisites any help with this would be extremely helpful

Rooting a Moto G4 Android 6.0.1

Hi,
I originally posted this over at android central where I was told it is not possible to root a Moto G4, so I am trying here hoping for a different answer = )
I am attempting to install Cyanogenmod on my handset using the below guide:
Install_CM_for_peregrine (looks like I can't post link but that is the name of the page on he Cyanogenmod site)
I have unlocked the handset, copied the Cyanogenmod zip file to my sdcard, booted in recovery mode and attempted to install the zip package. At this point I get an error "E:failed to verify whole-file signature". I have tried both the stable and nightly build with the same result. Also when I have attempted to install SuperSU using the same process have received the same error so I suspect it is not a corrupted file.
I believe this is being caused by the signature check and to get around this have been following the below guide to disable signature check:
tutorial-how-to-disable-signature-check.html (name of the tutorial as can't post links)
When it comes to the step "Then find a option Called "Patch To Android", I don't see this option, and from what I understand this may be due to not having my phone rooted.
I have installed Kingo ROOT to resolve this but it failed to root the handset (error 0x1C5C33 if that means anything to anybody), checking the list of phones which Kingo ROOT can root, Moto is not one of them. What are the other options?
Any advice greatly appreciated. Thanks in advance.

Get rid of kingo. Look up android doctor on YouTube for unlock, root, twrp instructions. CM has a lot of bugs and isn't ready for daily use on this device. Slim roms has released their rom, it's CM based. I've been using it for a few days, and it's running smooth. There's a thread about it with the link on here. The only problem I've had was a boot loop when I try and flash xposed and supersu. There's a built in super user access in the settings, so supersu isn't necessary.

hooks024 said:
Get rid of kingo. Look up android doctor on YouTube for unlock, root, twrp instructions. CM has a lot of bugs and isn't ready for daily use on this device. Slim roms has released their rom, it's CM based. I've been using it for a few days, and it's running smooth. There's a thread about it with the link on here. The only problem I've had was a boot loop when I try and flash xposed and supersu. There's a built in super user access in the settings, so supersu isn't necessary.
Click to expand...
Click to collapse
Phone rooted, thanks!
Now to install SlimRoms

Strange, after rooting gained the below options in Lucky Patcher:
Signature Verification Status always True
Disable .apk Signature Verification
Disable signature verification in the package manager
Patch applied for all three, but then when I restart in recovery mode and attempt to install the SlimRoms zip still getting error "E:failed to verify whole-file signature".

I didn't patch anything. Just root, installed twrp, and flashed slim rom and gapps

hooks024 said:
I didn't patch anything. Just root, installed twrp, and flashed slim rom and gapps
Click to expand...
Click to collapse
Ah I see, did not realise you install the rom via twrp. It's installed now, awesome, thanks.

Rooting OREO (41.3.A.2.24)

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

Your Phone Is Locked Because The Payment Service Was Uninstalled

I've checked the .xml file and the lines which is described in the guides to fix this error does not exist, there is not kgagent.
I've installed a custom rom and opengapps, magisk, microg, supersu, all these flashed through twrp.
https://forum.xda-developers.com/android/general/phone-locked-payment-service-uninstalled-t4018177
SM-J530F D/S
Tartarus v.2 rom android 9.0
3.3 Twrp
Whilst waiting for help I'm going to try installing a samsung pay.apk through adb sideload. Going to try on different pc as here I get the closed error as I try to push or do adb usb, adb root or whatever.
As a side note I've noticed that I'm having issues with installing magisk, which seemingly requires to be reinstalled if installing multiple things like microg, patcher, which throws error about android pie not being supported, etc. It says that the boot image incompatible or something. Also had issue with supersu saying that the binaries are or occupied by something else whilst inside the os. Trying to copy files in file manager (twrp) throws error 1.
Edit: no success.

ClownWorld said:
I've checked the .xml file and the lines which is described in the guides to fix this error does not exist, there is not kgagent.
I've installed a custom rom and opengapps, magisk, microg, supersu, all these flashed through twrp.
https://forum.xda-developers.com/android/general/phone-locked-payment-service-uninstalled-t4018177
SM-J530F D/S
Tartarus v.2 rom android 9.0
3.3 Twrp
Whilst waiting for help I'm going to try installing a samsung pay.apk through adb sideload. Going to try on different pc as here I get the closed error as I try to push or do adb usb, adb root or whatever.
As a side note I've noticed that I'm having issues with installing magisk, which seemingly requires to be reinstalled if installing multiple things like microg, patcher, which throws error about android pie not being supported, etc. It says that the boot image incompatible or something. Also had issue with supersu saying that the binaries are or occupied by something else whilst inside the os. Trying to copy files in file manager (twrp) throws error 1.
Edit: no success.
Click to expand...
Click to collapse
1. Samsung apps wont work on AOSP.
2. Try flashing the base ROM with a base firmware that doesnt have any carrier like vodafone etc.

NecromancerViper said:
1. Samsung apps wont work on AOSP.
2. Try flashing the base ROM with a base firmware that doesnt have any carrier like vodafone etc.
Click to expand...
Click to collapse
Are you saying that tartarus v.2 is a carrier dependant rom? Any suggestions of stable / bugless rom?
I've tried several, some sound issues, others soft brick/crash, and others thread topic.