Database Users

Xposed for Lollipop on Moto X

Given the fact that we finally got stock 5.0.2, and that Xposed for Lollipop is out, albeit on alpha (http://forum.xda-developers.com/showthread.php?t=3034811), I'm making this thread so that the Moto X (2013) community can share their experience installing and using Xposed on our device on Lollipop.
I myself was unable to get it working thus far, and my device refuses to install ANYTHING after I flash the zip on the thread posted above...
I see people were able to get it working, who mention that the device becomes slow and buggy afterwards...
So, whats your experience with this? Would you consider the current Xposed version to be compatible with our device running 5.0.2?
[EDIT]
After doing a factroy reset and installing for the second time it worked for me. Not that I also have SeLinux Mode Changer to set the mode to "Permissive".
I do notice a slight performance drop, it is not so snappy anymore, but all seems to be working pretty good nevertheless.
Cheers.

Charlie.igg said:
Given the fact that we finally got stock 5.0.2, and that Xposed for Lollipop is out, albeit on alpha (http://forum.xda-developers.com/showthread.php?t=3034811), I'm making this thread so that the Moto X (2013) community can share their experience installing and using Xposed on our device on Lollipop.
I myself was unable to get it working thus far, and my device refuses to install ANYTHING after I flash the zip on the thread posted above...
I see people were able to get it working, who mention that the device becomes slow and buggy afterwards...
So, whats your experience with this? Would you consider the current Xposed version to be compatible with our device running 5.0.2?
Cheers.
Click to expand...
Click to collapse
In my case it works well enough. GravityBox is working fine as well. The device is responsive and works really well.
You could try to do the following:
Factory Reset
Flash latest TWRP
Flash the Xposed zip
Wipe Cache and Dalvik
Install Xposed Installer

alresave said:
In my case it works well enough. GravityBox is working fine as well. The device is responsive and works really well.
You could try to do the following:
Click to expand...
Click to collapse
Factory Reset
Flash latest TWRP
Flash Super Su
Flash the Xposed zip
Wipe Cache and Dalvik
Install Xposed Installer
I did this steps plus flashing Super Su. So far so good. I installed gravity box, amplify, greenify, true silent mode and suggestion toggle.
Everything is working fine and I had no problem at all with xposed.
Sent from my XT1058 using XDA Free mobile app

Working well on my phone haven't install that many xposed apps, gravity and LP themer
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

alresave said:
In my case it works well enough. GravityBox is working fine as well. The device is responsive and works really well.
You could try to do the following:
Factory Reset
Flash latest TWRP
Flash the Xposed zip
Wipe Cache and Dalvik
Install Xposed Installer
Click to expand...
Click to collapse
I tried this yesterday to no avail, but I'll try again today and let you guys know.
I do have a question however, because everyone keeps saying to wipe dalvik... Is dalvik cache still relevant since we are all now running ART runtime?

Charlie.igg said:
I tried this yesterday to no avail, but I'll try again today and let you guys know.
I do have a question however, because everyone keeps saying to wipe dalvik... Is dalvik cache still relevant since we are all now running ART runtime?
Click to expand...
Click to collapse
ART keeps its cache on the same space as dalvik. The only thing that changed is when the cache is created: Dalvik did it when the app runs the first time and ART when the app is installed.

Charlie.igg said:
Given the fact that we finally got stock 5.0.2, and that Xposed for Lollipop is out, albeit on alpha (http://forum.xda-developers.com/showthread.php?t=3034811), I'm making this thread so that the Moto X (2013) community can share their experience installing and using Xposed on our device on Lollipop.
I myself was unable to get it working thus far, and my device refuses to install ANYTHING after I flash the zip on the thread posted above...
I see people were able to get it working, who mention that the device becomes slow and buggy afterwards...
So, whats your experience with this? Would you consider the current Xposed version to be compatible with our device running 5.0.2?
[EDIT]
After doing a factroy reset and installing for the second time it worked for me. Not that I also have SeLinux Mode Changer to set the mode to "Permissive".
I do notice a slight performance drop, it is not so snappy anymore, but all seems to be working pretty good nevertheless.
Cheers.
Click to expand...
Click to collapse
I have the same problem. After taking the ota and installing the xposed app, I have no ram left. I get this random error saying I need 250mb of storage in order to install anything. But I have plenty of room on my phone. Not sure what the issue is. So I flashed back to KitKat via stock image from moto (don't recommend, many issues could arise) took the ota again, I'm back at zero. I haven't restored anything yet, I flash the xpose zip necessary, I get the same error.

This is what i get.

r_diaz13 said:
View attachment 3224960View attachment 3224961
This is what i get.
Click to expand...
Click to collapse
Yeah, that's the same thing I had.
I got it working on the 2nd try, and this is exactly what I did:
Installed LP OTA
Did a factory reset
Flashed latest version of TWRP via fatsboot
Rooted by flashing SuperSU using TWRP
Installed SELinux Mode Changer from Play Store and then set mode to "Permissive" using this app
Flashed the Xposed Zip bia TWRP
Installed Xposed .apk
After this it seems to work just fine
I've found a couple of modules that will wreak havoc into your phone if you're using LP tho, specially PinNotif :S

Charlie.igg said:
Yeah, that's the same thing I had.
I got it working on the 2nd try, and this is exactly what I did:
Installed LP OTA
Did a factory reset
Flashed latest version of TWRP via fatsboot
Rooted by flashing SuperSU using TWRP
Installed SELinux Mode Changer from Play Store and then set mode to "Permissive" using this app
Flashed the Xposed Zip bia TWRP
Installed Xposed .apk
After this it seems to work just fine
I've found a couple of modules that will wreak havoc into your phone if you're using LP tho, specially PinNotif :S
Click to expand...
Click to collapse
I'm about to try this after not being able to get it to work the usual way. Does setting it to permissive increase security risk on my phone?

Charlie.igg said:
Yeah, that's the same thing I had.
I got it working on the 2nd try, and this is exactly what I did:
Installed LP OTA
Did a factory reset
Flashed latest version of TWRP via fatsboot
Rooted by flashing SuperSU using TWRP
Installed SELinux Mode Changer from Play Store and then set mode to "Permissive" using this app
Flashed the Xposed Zip bia TWRP
Installed Xposed .apk
After this it seems to work just fine
I've found a couple of modules that will wreak havoc into your phone if you're using LP tho, specially PinNotif :S
Click to expand...
Click to collapse
So basically I will do a factory reset, I'll still have twrp and su (currently rooted so FR will just wipe everything but SD), just install the selinux changer, make the change, then install zip/apk. Will report back in a few days.

No success. Tried the FR, I'm already on latest TWRP and rooted, installed SELinux changer, the whole thing, came up with the same error about space.

It worked for me! Followed the same steps as above. I also cleared cache and dalvik and had to re-install the zip and the apk. Not sure if it was the selinux changer that did it. On latest TWRP and rooted.

moto x 2013 ota lollipop soak test
I flash my phone with 4.4.4 brasil retail. then install the OTA 5.0.2. I flash TWRP by the bootloader. install zip from SuperSU and could be root. I install Xposed lollipop. and there are very good modules like lpthemer, lolistat, instagram themer, greenify work fine. I have also whatsapp plus reborn by osmdroid and walk like the original whatsapp calls. Voice commands motorola still lacks a reset. but pretty good overall :laugh:

Working perfectly so far
I have gravity box and amplify working, seemingly without issue, on Lollipop 5.02 (second soak, build 221.41.38).
Steps:
1. fastboot flashed brazil 4.4.4 system and boot
2. in recovery flashed fixed 5.02 soak, then flashed fixed 2nd 5.02 soak, then flashed chainfire's latest supersu (then booted and used for a few days)
3. in recovery flashed xposed for LP .zip, then cleared cache and dalvic
4. booted normally and installed xposed apk
5. added gravity box and amplify modules and rebooted
Notes:
I didn't need to do anything with selinux.
edit: First problem - As reported by others, "sdcard" space is suddenly lower as reported by both settings->storage and es file manager. <- this problem seems to be with TWRP's mishandling of selinux permissions on the /sdcard/TWRP directory. I [mostly] fixed it with 'restorecon' command.
Everything I configured in gravity box seems to be working perfectly. Thanks rovo89 and C3C076!

I have a question is I may.....
I miss xposed on my phone. The old version is still on my X after the 5.1 OTA but not working.
Can I flash the LL xposed on top or do I need to remove it first? Which version is everyone here using? I'd like to have the best chance at getting it working the first go around.

svennn said:
I have a question is I may.....
I miss xposed on my phone. The old version is still on my X after the 5.1 OTA but not working.
Can I flash the LL xposed on top or do I need to remove it first? Which version is everyone here using? I'd like to have the best chance at getting it working the first go around.
Click to expand...
Click to collapse
remove the old xposed and follow the thread

I can't seem to remove the old framework. I think that is my problem.

svennn said:
I can't seem to remove the old framework. I think that is my problem.
Click to expand...
Click to collapse
Open App Drawer
Open Xposed Framework
Select Framework
Select Uninstall
Select OK
Select Reboot
or http://forum.xda-developers.com/showpost.php?p=60468815&postcount=18

From stock 4.4.3 to latest 5.0 (RU1.1.34) with Magisk v9 (xposed not yet working)

A short summary of upgrading my YotaPhone 2 to run Magisk v9 on the latest RU lollipop build (1.1.34) because I've seen no threads about Magisk here yet and writing my experience down might help others (or myself in the future).
Background: Got the phone last week from bestgear, and I'm surprised at how great it is. The EPD is much more responsive than I expected. And the phone looks just great! So much has changed/improved in the modding community in the last years (and I got out of touch with it), that I decided to go cutting edge with systemless Xposed through Magisk with root hiding, having no experience with either.
Lollipop
The phone had exactly the same about screen as in the lollipop upgrade thread so I sort-of followed that and subsequently went for the latest Russian version (RU1.1.134).
However, my setup prevented flashing directly to any of the 5.0 versions. The YotaPhoneFlasher showed that flashing /system failed (which can be seen by scrolling up on the prompt about flashing the user data). Probably due to the file size being too large. However, this procedure seemed to do the trick (see above thread for details):
Flash 5.0.0-RU1.1.124. Booting hangs at the 'Powered by Android' screen.
Flash 4.4.3-S01-003-RU1.0.3.61a. Booting succeeds.
Somehow, it now knows that it can perform an OTA update and proceeds through several versions to get to RU1.1.134
Not sure whether the RU version is worth it though, because it adds some bloatware like a Russian NFC payment app, a Russian air plane app and a dictionary app that primarily supports to/from Russian.
TWRP
Subsequently the recovery was flashed to TWRP 2.8.5.0. This seems a rather old version of TWRP though, perhaps too old to flash Magisk v9, see below. (This is my first TWRP experience as well, absolutely fabulous compared to older recoveries!)
Magisk
Magisk v9 refused to install directly. Flashing Magisk-v9.zip always ended up with either "E: footer is wrong" or "E:Error executing updater binary in zip". I tried to 'Install' from TWRP and to 'adb sideload' from both TWRP and modified stock recovery. Googling these errors lead me to believe that it might be related to the TWRP version. (The download was fine, because the zip file was exactly the same as the one that the Magisk Manager installed.)
In the end it was rather simple:
Flash Magisk-v8.zip
Install the magisk version of phh's superuser (and the corresponding Superuser app).
Install Magisk Manager
Upgrade Magisk to v9 from within the manager.
The "Emoji One" module proved that Magisk works (by replacing all the smilies). However, couldn't get Pokemon Go to login, so the root hiding might not work, but I didn't try PoGo before installing Magisk, so could be another issue.
Xposed
My actual goal was experimenting with Xposed, but the Xposed Installer keeps saying that the "Xposed Framework is installed, but not active." I'll keep you posted if I manage to get it working.
Some more notes:
A windows 10 laptop was used for all of the flashing (because the YotaPhoneFlasher software is windows only it seems).
Several reboots and cache/data wipings were omitted from the above. These did make the process take ages though, updating all the apps etc. all the time.
Thank you for all the information on this forum that let me get this far. I'm very happy with having a Lollipop YotaPhone with root.

Thank you for your detailed experience. I read the magisk thread here on XDA buy I didn't understand why is it for? And another question, why are you installing xposed? Are there benefits or special added features added to our Yotaphone?

I'm both new to Magisk and Xposed myself, and indeed it is not directly clear 'what these are for' from their xda posts. So I decided to just try them out and see for myself.
Xposed allows hundreds of modules to be installed to alter the OS in one way or the other. I'm most interested in Xprivacy, which should allow the user to limit what data / functionality apps can access and provides apps with mock data and such. Like a fine grained permission system I think.
Magisk also allows modules to alter the OS, but there seem to be only a handful, including Xposed. The selling point of Magisk is, if I understand correctly, that it does not alter the system partition. This makes it easy to apply future OTA updates etc. Supposedly it can also hide itself and root from certain apps.
It's not that important to me, so not sure whether I'll continue my exploration soon. (The Magisk threads are many, many pages, so it could take quite some research to get it to work properly.)

Did you get any further with Magisk & Xposed? My YD201 just arrived and I'm trying to decide how to proceed with hacking the crap out of it.

hippy dave said:
Did you get any further with Magisk & Xposed?
Click to expand...
Click to collapse
Not yet hippy dave. The Marshmallow beta came out soon after my initial experiments and I decided to wait for the official Marshmallow release before experimenting further. My concern was that I didn't want to redo the entire process every other week, and I messed something up so I can't boot to recovery...
The final Android 6.0 rom seems to take a while, so maybe it is worthwhile to continue with the latest beta. My plan is to first fix my recovery partition somehow, then upgrade to the latest Marshmallow beta, and then try Magisk again. I don't want to use the 'normal' system-partition-modifying Xposed because I like the cleanliness that Magisk promises. I haven't followed the Magisk development since, so maybe things have changed.
Your experiences would be welcome.

BlackShift said:
Your experiences would be welcome.
Click to expand...
Click to collapse
Makes sense, I decided to skip the MM beta for now and wait for release, but I couldn't wait that long to get root etc, so I tried Magisk out on the latest Russian LP. First I tried the latest release of Magisk 11.x, and then the latest unofficial source build 12.x, and tho it installed (with TWRP 3 latest version) and worked fine in terms of root, I couldn't get Magisk Hide to work and pass SafetyNet. Tried all the tips I could find like turning off USB debugging, turning things off & on in Magisk in a particular order with reboots in between etc. So I gave up for now and didn't get as far as trying Xposed for Magisk or any other modules.
For the time being I decided to go with the tried and tested stuff, standard root and regular Xposed, and will reevaluate when Marshmallow gets an official release or if I hear of improvements to Magisk Hide.

hippy dave said:
Makes sense, I decided to skip the MM beta for now and wait for release, but I couldn't wait that long to get root etc
Click to expand...
Click to collapse
The official MM came out a couple of days ago, but so far, no more success than you got.
Updated to MM. Forgot how, it refused to update over the air, so think I adb sideloaded the full 1.34 OTA with TWRP. Safetynet check from Magisk manager successful (of course).
Installed TWRP 3.0 and the official Magisk 12. However, the Magisk root seemed to have failed, also after a reboot. Safetynet check failed.
Installed SuperSU systemless by typing echo SYSTEMLESS=true>>/data/.supersu in the TWRP command prompt because SuperSU failed to install systemless automatically. Magisk Hide claims it doesn't operate that well with SuperSU, and safetynet check failed.
So Magisk and root access works, but not root hiding. Which kinda defeats the point of using Magisk. I didn't try many of the clever tricks you refer to though and I gave up for now. It is supposedly cleaner than other methods of rooting, so I'll keep it anyway. Next up is
(Not really relevant to this thread.) Getting 800Mhz band to work
Getting XPosed installed systemless.
Perhaps send a boot image to the Magisk team so they can improve the support for our yotaphones? Not sure how this process works.

Hi, has there been any more progress with Magisk and Yotaphone? My bank finally started using Android Pay, so I'm keen to have another crack at hiding root. I don't think there have been any changes to Yotaphone firmware since you last posted, but I don't know what progression there's been with Magisk. Maybe when I have the chance I'll try to send the Magisk people whatever they need to try and get it working.

I haven't made any attempts since last time and probably won't soon. Let us know if you are successful.

Ok I did a fresh install of the latest Russian MM (kept my data tho), installed the current Magisk release version (14.0), and it just worked straight off, Android Pay is running happily and root is working in the few root apps I've tried so far. Only downside so far is no Xposed, there's an unofficial Xposed for Magisk but it doesn't pass Safety Net so would presumably break Android Pay. I'm gonna see what Magisk modules are available and if they can fill the void, and decide from there I guess.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Woop, finally got SafetyNet passing while Xposed is running (as slightly evidenced by the circle battery).
This wasn't straightforward, and didn't end up using Magisk. This is using SuperSU, suhide v0.55, and a patched system library (I had to patch the yotaphone one myself, let me know if anyone wants it).
The only quirk now is that the Xposed Installer doesn't see the xposed framework as installed/active, even tho the framework and modules are working fine. Gonna investigate that too, but can work around it for now. edit: Compiled my own version of Xposed Installer with tweaked paths and now it works fully.

hippy dave said:
Woop, finally got SafetyNet passing while Xposed is running (as slightly evidenced by the circle battery).
This wasn't straightforward, and didn't end up using Magisk. This is using SuperSU, suhide v0.55, and a patched system library (I had to patch the yotaphone one myself, let me know if anyone wants it).
The only quirk now is that the Xposed Installer doesn't see the xposed framework as installed/active, even tho the framework and modules are working fine. Gonna investigate that too, but can work around it for now. edit: Compiled my own version of Xposed Installer with tweaked paths and now it works fully.
Click to expand...
Click to collapse
Would you please send me the patched library ?
Sent from my YD201 using Tapatalk

stanley321 said:
Would you please send me the patched library ?
Sent from my YD201 using Tapatalk
Click to expand...
Click to collapse
Sure thing, I'll attach it to this post. You might know that you have to fix the file contexts when you replace the original library with the patched one - I'd boot into TWRP and use adb push to put the file into place, then adb shell and use the following command in the right directory:
chcon --reference=libandroid.so libandroid_runtime.so

[RECOVERY][UNOFFICIAL][XT1650][griffin] TWRP 3.0.3-n2 for Moto Z

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Here is TWRP 3 for the Moto Z
I decided to open this thread and make unofficial builds because the official TWRP (3.0.2) is still based on MM and will not work properly with N Firmwares and ROMs.
It should work when you flash it, but using it is still a try at your own risk procedure.
Our device comes with forced encryption and, more important,
verity which checks at every boot if /system partition has been changed or not.
If /system has been changed, verity won't allow booting your device which means
you can't flash anything unless you disable verity.
So, you must be sure to keep /system in ReadOnly mode in TWRP and don't try to alter it unless you're using a custom Kernel/boot to disable verity.
Of course, custom ROMs come with custom boot, so no worries about verity security with Lineage or AOKP for example.
Click to expand...
Click to collapse
To temporarily boot this recovery:
Code:
fastboot boot twrp.img
To permanently flash it:
Code:
fastboot flash recovery twrp.img
The download is up on moto.shreps.fr.
Changelog:
twrp-3.0.3-n2-athene_shreps.img
- Kernel and boot update - should be compatible with more variant
- Some TWRP fixes
twrp-3.0.3-n1-athene_shreps.img
- Qseecom and crypto stuff updated to N
> I'm able to decrypt my /data partition (F2FS) - Tested on XT1650-03_NPL25.86-17-3
- Fully rebased on AOSP Recovery 7.1
- TWRP bump to 3.0.3, with a lot of fixes
- Dark Material Theme
- Removed cursor pointer
XDA:DevDB Information
[RECOVERY][UNOFFICIAL][XT1650][griffin] TWRP 3.0.3-n2 for Moto Z, Tool/Utility for the Moto Z
Contributors
Shreps
Source Code: https://github.com/omnirom/android_bootable_recovery
Version Information
Status: Stable
Created 2017-01-30
Last Updated 2017-03-07

[ROOT] How to root with latest N firmware NPL25.86-17-3
Simple procedure:
Unlock your BL
Flash this TWRP Recovery
Download the superuser zip (thanks to phh)
Flash it through TWRP
Reboot
Install phh's SuperUser app from play store
Enjoy

Shreps said:
Here is TWRP 3 for the Moto Z
I decided to open this thread and make unofficial builds because the official TWRP (3.0.2) is still based on MM and will not work properly with N Firmwares and ROMs.
Click to expand...
Click to collapse
Thanks for this, could you please patch this :
https://forum.xda-developers.com/showpost.php?p=70492947&postcount=8793
To make supersu systemless root possible
Thanks again

erfanoabdi said:
Thanks for this, could you please patch this :
https://forum.xda-developers.com/showpost.php?p=70492947&postcount=8793
To make supersu systemless root possible
Thanks again
Click to expand...
Click to collapse
Use superuser systemless root, has mentionned in post #2. It's safer.

Shreps said:
Use superuser systemless root, has mentionned in post #2. It's safer.
Click to expand...
Click to collapse
I added pull request for this
And I also built it : https://mega.nz/#!ScxHASjB!teSpEOZnO2cYej7W41sgTELAv3Z8-6qa6GH1z1mRwdI
I don't know why, but I hate phhsuperuser

erfanoabdi said:
I added pull request for this
And I also built it : https://mega.nz/#!ScxHASjB!teSpEOZnO2cYej7W41sgTELAv3Z8-6qa6GH1z1mRwdI
I don't know why, but I hate phhsuperuser
Click to expand...
Click to collapse
I hate phhsuperuser too, but what is this recovery.img that you linked ?
in your images you show up SuperUser 2.78 R2, it works ? What happend with the release 2.59. I tried before and my phone don;t boot any more when I install SuperUser

[email protected] said:
I hate phhsuperuser too, but what is this recovery.img that you linked ?
in your images you show up SuperUser 2.78 R2, it works ? What happend with the release 2.59. I tried before and my phone don;t boot any more when I install SuperUser
Click to expand...
Click to collapse
My Link is TWRP recovery image
Here I installed SuperSU as systemless mode, which is always fails installation on official TWRP
In pictures I really only installed es explorer as root needed app and I didn't mess with SuperSU anymore not sure about other's
BTW I recommend to stay on phh's superuser

erfanoabdi said:
My Link is TWRP recovery image
Here I installed SuperSU as systemless mode, which is always fails installation on official TWRP
In pictures I really only installed es explorer as root needed app and I didn't mess with SuperSU anymore not sure about other's
BTW I recommend to stay on phh's superuser
Click to expand...
Click to collapse
So using this recovery and forcing to flash in systemless mode boots into ROM? Because last time I tried system mode ended up in bootloop and systemless mode dint gain any root access

silvercat said:
So using this recovery and forcing to flash in systemless mode boots into ROM? Because last time I tried system mode ended up in bootloop and systemless mode dint gain any root access
Click to expand...
Click to collapse
Again, it's safer to flash supersuser by phh, everything works out of the box
See post #2

Shreps said:
Again, it's safer to flash supersuser by phh, everything works out of the box
See post #2
Click to expand...
Click to collapse
Currently I'm using phh without any issue but FlashFire doesn't work with this, it requires SuperSU

silvercat said:
So using this recovery and forcing to flash in systemless mode boots into ROM? Because last time I tried system mode ended up in bootloop and systemless mode dint gain any root access
Click to expand...
Click to collapse
First at all I really don't recommend this root method, cause I didn't test it too much
But your answers:
There's no force just flash released superSU from chainfire this will flash in systemless
Before this recovery, old official one could not install SuperSU as systemless and it was stops on decompressing ramdisk, I just fixed installation part which is only related to TWRP bug
And force system (xbin) root still makes bootloop , as I know it's not about TWRP

erfanoabdi said:
First at all I really don't recommend this root method, cause I didn't test it too much
But your answers:
There's no force just flash released superSU from chainfire this will flash in systemless
Before this recovery, old official one could not install SuperSU as systemless and it was stops on decompressing ramdisk, I just fixed installation part which is only related to TWRP bug
And force system (xbin) root still makes bootloop , as I know it's not about TWRP
Click to expand...
Click to collapse
Then according to you which method of Rooting is the Best or safe instead...or which TWRP & supersu file should be flash , if i am on Nougat updated through OTA

kethsawant said:
Then according to you which method of Rooting is the Best or safe instead...or which TWRP & supersu file should be flash , if i am on Nougat updated through OTA
Click to expand...
Click to collapse
I recommend to follow OP guide, it's safe
But if you like SuperSU use my TWRP and flash latest SuperSU

erfanoabdi said:
I recommend to follow OP guide, it's safe
But if you like SuperSU use my TWRP and flash latest SuperSU
Click to expand...
Click to collapse
I tried that in Stock rom but ended up in bootloop..

erfanoabdi said:
I recommend to follow OP guide, it's safe
But if you like SuperSU use my TWRP and flash latest SuperSU
Click to expand...
Click to collapse
Pls provide the link of TWRP & Super SU you recommend (i am stock Nougat)

kethsawant said:
Pls provide the link of TWRP & Super SU you recommend (i am stock Nougat)
Click to expand...
Click to collapse
OK use my TWRP and flash this super su
This is not modded version just old version of stock superSU
Please test it and tell how is it.

Is this only for N bootloader?
I am still on MM bootloader and got freezing screen on TWRP home. Could not touch/select the menu, had to flash back to official TWRP 3.0.2.

paulnorinn said:
Is this only for N bootloader?
I am still on MM bootloader and got freezing screen on TWRP home. Could not touch/select the menu, had to flash back to official TWRP 3.0.2.
Click to expand...
Click to collapse
Hum yes, but should work too with MM bootloader. You can try to press power to shutdown the screen and then power or volume again to wake up and the touch should be initialized.

Shreps said:
Hum yes, but should work too with MM bootloader. You can try to press power to shutdown the screen and then power or volume again to wake up and the touch should be initialized.
Click to expand...
Click to collapse
Ok, thats fix it. I can now touch the screen. Guess I have to do it on every boot?
Thanks for the tip.

OK I formatted my partitions in twrp and it was formatted as ext4. I read somewhere that the moto Z uses f2fs by default. Is this true and I just reduced performance of my phone because of a bug in twrp? I couldn't find an option to format as f2fs.

Guide to install magisk v13.1 on kenzo

For those who got problems with installation on v13.1 use the following guide it will help you all links below its from official sites not mirrors etc.
Steps for make sure you're not confused
1)reboot to twrp recovery or cwm
2)install magisk uninstaller zip
3)install unroot kenzo zip
4)install magisk v13.1
5) reboot device
6) install magisk manager if not installed automatically
7) attention before you use it keep your boot.img as a backup to restore it if you are not going to use a custom kernel read below the edit why thanks
Ps.worked perfectly on Nougat NOS release latest beta with radon kernel 5.1 hope to work on your ROM too
EDIT:When you use the nitrogen unroot zip in restore the nos kernel by Nougat version so on Miui and other ROMS of course if you dont use custom kernel take a backup of your current kernel just the boot part or just install the custom kernel like radon,agni after the whole steps etc sorry about that it just took me a while to find out cuz I just checked my kernel adiutor and I just saw the wild kernel of nitrogen on performance gov and it burned my hand almost xd
UPDATE:Try this unroot zip file first it doesn't going to mess with your kernel amd change it but if that doesn't work you have to do it with tge other way thanks for understanding :')
-->Download link press here<--
Kenzo unroot by NOS site (worked in Nougat with radon 5.1)check the update please before use this zip file
magisk uninstaller from official link by @topjohnwu
magisk v13.1 by official link of @topjohnwu
magisk manager 5.0.4 from official link of @topjohnwu

1. CM/AOSP without root (or unroot)
2. Flash Magisk 13.1 (Magisk Manager included, no need to remove the old one if you are using)
3. Done

Archmage1809 said:
1. CM/AOSP without root (or unroot)
2. Flash Magisk 13.1 (Magisk Manager included, no need to remove the old one if you are using)
3. Done
Click to expand...
Click to collapse
I talk about people who got problem with installation about error 1 since all roms got root they have to use an unroot zip as I just saw only new halogen os doesn't include root dont pretend the smart boy you can just ignore the post

i have problem with miui 8 developer rom, stuck in boot loading although i have dirty flashed rom

solo player said:
i have problem with miui 8 developer rom, stuck in boot loading although i have dirty flashed rom
Click to expand...
Click to collapse
Flash the kernel again and the problem will be solved I just figured out something just now cuz my device burned my hand almost xd

After install install magisk v13.1, Do I need to install phh-superuser-magisk-r266-2.zip?
After install install MagiskManager-v5.0.4.apk, Do I need to install Superuser_1.0.3.3.apk?

magisk v13.1 by official link of @topjohnwu not works on MIUI 8.3.0.5(MHOMEID).. Already tried and stuck at MI logo..

xmixmaster said:
Flash the kernel again and the problem will be solved I just figured out something just now cuz my device burned my hand almost xd
Click to expand...
Click to collapse
sadly it didn't work for me i have to wait for fix or another wokaround

jerung3000 said:
After install install magisk v13.1, Do I need to install phh-superuser-magisk-r266-2.zip?
After install install MagiskManager-v5.0.4.apk, Do I need to install Superuser_1.0.3.3.apk?
Click to expand...
Click to collapse
No it will autoroot your phone just check the steps I writed and pay attention on update I did

solo player said:
sadly it didn't work for me i have to wait for fix or another wokaround
Click to expand...
Click to collapse
What rom you got?

xmixmaster said:
What rom you got?
Click to expand...
Click to collapse
miui 8 7.7.6 developer rom

Do we really need this guide? Lol

I have installed superuser how can I replace it to magisk as safteynet check doesn't pass on superuser after Xposed installation.

I flashed Nitrogen 2 based on Orio in Redmi Note 3. How i can install / flash magisk .?
I root the same with Supersu

the module that is listed is download section of magisk will work in all phone or on the specific phone that is mentioned there?

links are down:cyclops:

D802 any root methods are not working!

hi ppl
it was rooted before. used twrp and some custom roms. but later it unrooted somehow.
I tried flashing super su, magisk and ioroot. supersu and magisk turn with an error msg
io root made it stuck on bootloader animation so I flashed a backup.
how to root it?
thx in advance

1) flash latest twrp http://www.gregtwallace.com/lgg2-projects/twrp/ - then reboot into twrp
2) made absolutely all wipes incl internal and data (delete all stuff) - then reboot into twrp
3) connect to usb - and simply copy rom, gapps, and root solution what you want to flash
latest stable magisk for twrp - https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
latest supersu for twrp - Recovery Flashable.zip http://www.supersu.com/download
3) flash the rom what you wanted and flash gapps
3) flash magisk or supersu
(if android 7.1.2 or higher of course - I recommend magisk, because of working nfc pay features, a lot of great systemless addons etc...)
if you prefer old lollipop rom (for example CloudyG2_3.3 ) - it supersu only.
This is the correct sequence - which will eliminate problems with the firmware. If you deleted and installed the root earlier (as you say)
I tried flashing super su, magisk and ioroot. supersu and magisk turn with an error msg
Click to expand...
Click to collapse
jeezes)) you already killed the rom.... and then restore the all this restores backup, this is a "dirty flash" with a bunch of "remnants". I recommend to do clean flash it in the specified sequence and everything will be ok.
You will spend a couple of 1-2 hours only on installing (and setting) completely all applications. It is not so difficult. But it will save you from a bunch of nonsense questions...
If you actually don't have TWRP recovery installed or old Kit kat Rom - this is absolutely another question and the instructions will not work for you. Also, Kit Kat and Lollipop based ROMs does not support Magisk - because of this error.

zemix said:
1) flash latest twrp http://www.gregtwallace.com/lgg2-projects/twrp/ - then reboot into twrp
2) made absolutely all wipes incl internal and data (delete all stuff) - then reboot into twrp
3) connect to usb - and simply copy rom, gapps, and root solution what you want to flash
latest stable magisk for twrp - https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
latest supersu for twrp - Recovery Flashable.zip http://www.supersu.com/download
3) flash the rom what you wanted and flash gapps
3) flash magisk or supersu
(if android 7.1.2 or higher of course - I recommend magisk, because of working nfc pay features, a lot of great systemless addons etc...)
if you prefer old lollipop rom (for example CloudyG2_3.3 ) - it supersu only.
This is the correct sequence - which will eliminate problems with the firmware. If you deleted and installed the root earlier (as you say)
jeezes)) you already killed the rom.... and then restore the all this restores backup, this is a "dirty flash" with a bunch of "remnants". I recommend to do clean flash it in the specified sequence and everything will be ok.
You will spend a couple of 1-2 hours only on installing (and setting) completely all applications. It is not so difficult. But it will save you from a bunch of nonsense questions...
If you actually don't have TWRP recovery installed or old Kit kat Rom - this is absolutely another question and the instructions will not work for you. Also, Kit Kat and Lollipop based ROMs does not support Magisk - because of this error.
Click to expand...
Click to collapse
thx bro. I did all the steps but it seems same problem going on. sure I want the latest of everything. better updated all. so, using the latest twrp, I wipe all data then format all data then again wipe everything
this aosp rom and gapps worked perfectly. then flashed teh magisk but again its unrooted.
it installs magisk perfectly but root checker says its not rooted. anyway thx for help
btw, aosp rom android 9 has a bluetooth bug. giving a bluetooth stopped message every 10 seconds.

so any advice anout that problem?

you must grant root permission when popup (magisk) appears.
its not automatically
popup similar as in supersu
root works excellent on d802 with Magisk
for example Es File Explorer or any Root Checker
---------- Post added at 17:12 ---------- Previous post was at 17:10 ----------
I use 7.1.2 android based AospExtended v 4.6
because latest pie rom has bugs and not stable

Screenshot https://i.imgur.com/6IcIvJx.jpg

slabongrade said:
thx bro. I did all the steps but it seems same problem going on. sure I want the latest of everything. better updated all. so, using the latest twrp, I wipe all data then format all data then again wipe everything
this aosp rom and gapps worked perfectly. then flashed teh magisk but again its unrooted.
it installs magisk perfectly but root checker says its not rooted. anyway thx for help
btw, aosp rom android 9 has a bluetooth bug. giving a bluetooth stopped message every 10 seconds.
Click to expand...
Click to collapse
flash magisk.zip and install magisk.apk to root android 9

zemix said:
you must grant root permission when popup (magisk) appears.
its not automatically
popup similar as in supersu
root works excellent on d802 with Magisk
for example Es File Explorer or any Root Checker
---------- Post added at 17:12 ---------- Previous post was at 17:10 ----------
I use 7.1.2 android based AospExtended v 4.6
because latest pie rom has bugs and not stable
Click to expand...
Click to collapse
zemix said:
Screenshot https://i.imgur.com/6IcIvJx.jpg
Click to expand...
Click to collapse
elffoh said:
flash magisk.zip and install magisk.apk to root android 9
Click to expand...
Click to collapse
zemix said:
you must grant root permission when popup (magisk) appears.
its not automatically
popup similar as in supersu
root works excellent on d802 with Magisk
for example Es File Explorer or any Root Checker
---------- Post added at 17:12 ---------- Previous post was at 17:10 ----------
I use 7.1.2 android based AospExtended v 4.6
because latest pie rom has bugs and not stable
Click to expand...
Click to collapse
zemix said:
Screenshot https://i.imgur.com/6IcIvJx.jpg
Click to expand...
Click to collapse
elffoh said:
flash magisk.zip and install magisk.apk to root android 9
Click to expand...
Click to collapse
I used supersu and it turned out to be "certification verify" problem. OS not running because of this problem but says rooted. so I can still reach twrp but it really become annoying. this is my old phone and will use as 2nd in my Thailand trip soon.
what to do now? can I use unrooted with a sim card? with no problem?

Please, don't use this nonsense "overquoting" when you answer to someone. Have some respect to the forum rules, and users.
if you want stable rom for LGG2-D802 flash
1) aosp extended based on 7.1.2 or 8.1 versions of Android.
2) flash gapps nano
3) flash magisk zip
4) after rom starts - do the first quick settings - then open Magisk (and if needed update the Magisk manager)
Do not flash both (supersu and magisk) risk to brick the phone.
"device not certified" messege will be always if you use Supersu. It's obviously. Using supersu you unable to use apps like Google pay or any banking apps, because of system root.
Magisk is systemless solution, that's why Google do not recognize Magisk's root. And Play Store on about screen always show "Your device is certified". Also you can Hide root from some apps using Hide option in Magisk manager (it's very useful for local banking apps).
I have a suspicion that you used an older version of Android KitKat (official). And now you try to flash a new Rom (above the Android 7.1.2+). You can't do this. Because you must have Lollipop bootloader. You must be an Android Lillipop first. And then (get Root, then TWRP). And after all that - you will be able to flash some of Rom we are talking about.

zemix said:
Please, don't use this nonsense "overquoting" when you answer to someone. Have some respect to the forum rules, and users.
if you want stable rom for LGG2-D802 flash
1) aosp extended based on 7.1.2 or 8.1 versions of Android.
2) flash gapps nano
3) flash magisk zip
4) after rom starts - do the first quick settings - then open Magisk (and if needed update the Magisk manager)
Do not flash both (supersu and magisk) risk to brick the phone.
"device not certified" messege will be always if you use Supersu. It's obviously. Using supersu you unable to use apps like Google pay or any banking apps, because of system root.
Magisk is systemless solution, that's why Google do not recognize Magisk's root. And Play Store on about screen always show "Your device is certified". Also you can Hide root from some apps using Hide option in Magisk manager (it's very useful for local banking apps).
I have a suspicion that you used an older version of Android KitKat (official). And now you try to flash a new Rom (above the Android 7.1.2+). You can't do this. Because you must have Lollipop bootloader. You must be an Android Lillipop first. And then (get Root, then TWRP). And after all that - you will be able to flash some of Rom we are talking about.
Click to expand...
Click to collapse
Oh Finally!
dowloaded aosp 8.1 and all done. I was trying to use android 9 to be updated. But, pie becoming to be a "creampie" to me so I listened your word. and did it
just opened recovery mode and deleted all the zips. and copied new ones and flashed in order
1) aosp extended 8.1
2) open gapps nano for 8
3) magisk beta (yes this time I tried beta ver and it worked!)
after settings etc. checked with root checker and it was ok. so magisk.apk is not necessary now
thx again bro