I downloaded de.robv.android.xposed.installer_v33_36570c.apk but it said there was a compatibilty issue with my version of sdk and arm64-v8a.
Any install instructions that cover marshmallow on the 1575?
You need to XposedInstaller_3.0_alpha4.apk and xposed-v80-sdk23-arm64.zip found in the official xposed forum. Install the apk file as usual then you need to flash the framework zip file in recovery. Wipe cache/dalvik before rebooting to system.
The files are listed at the bottom, here: http://forum.xda-developers.com/showpost.php?p=58828974&postcount=1
Can we use xposed with systemless root or should we wait ?
Xposed runs with systemless root. But to note, it is preferable to install to system partition, the traditional method.
http://forum.xda-developers.com/showpost.php?p=64916199&postcount=3
Changelogs
10.05.2016 - v2.72 - BETA - RELEASE NOTES
- Add support for ChromeOS boot images (Pixel C)
- supolicy: Fix logging to logcat for some processes on some firmwares
- supolicy: Fix fsck of /data/su.img being denied on some firmwares
- ZIP: Add LESSLOGGING flag
- ZIP: Add KEEPVERITY flag
- ZIP: Add KEEPFORCEENCRYPT flag
- ZIP: Also read flags from /cache/.supersu (aside from /data/.supersu and /system/.supersu)
Yes, baby !
wow! That's a surprise!
BaristaBot said:
wow! That's a surprise!
Click to expand...
Click to collapse
Indeed .. but now we have support.
Just tested 2.72 .. works perfectly.
Installed stock boot.img via TWRP and Supersu.zip directly afterwards ..
Supersu.zip is perfectly modifying the ramdisk and re-signing the kernel to chromeos.
Tested xceed kernel and my pre-rooted kernel too.
Supersu will not modify the ramdisk at all.
"Can't find stock Image, already modified .." and will stop the ramdisk installer.
The system will start anyway, but with "old" ramdisk modifications.
So a fresh clean stock boot.img is recommended.
Install it via TWRP, just before the supersu.zip installation.
No reboot required, nothing.
Download from here ..
http://forum.xda-developers.com/pixel-c/development/twrp-flashable-monthly-update-zip-pixel-t3375591
Running on 2.72 now ... we don't need to build any stock rooted kernels anymore.
Don't be surprised .. after Supersu.zip installation the first boot will look like bootloop, but only once. Same like on other devices as well.
Cheers
After flashing a stock android N preview 2, I installed TWRP and flashed the superSU ZIP (2.72). I can confirm this works perfectly, and i have root on android N preview 2
@NYCHitman1 @cheep5k8 Did you see this? Great news eh?
Samt434 said:
After flashing a stock android N preview 2, I installed TWRP and flashed the superSU ZIP (2.72). I can confirm this works perfectly, and i have root on android N preview 2
Click to expand...
Click to collapse
Great! I'd like to give the N preview a try now, too. Could you please elaborate on how you achieved root with the new SuperSU? Did you have to reflash a custom recovery after flashing Android N?
Which version of TWRP should be used as there are alot of other versions around thats not clear which one is working?
scoobydu said:
Which version of TWRP should be used as there are alot of other versions around thats not clear which one is working?
Click to expand...
Click to collapse
This one
TWRP_dragon_3.0.2-0_v2.img
- Added vendor.img flashing via TWRP. (thx to NYCHitman1 )
Download: https://onedrive.live.com/?authkey=!ABLdSOKIeXgg_XU&id=479EB75F5DD9DA59!117&cid=479EB75F5DD9DA59
Cheers
followmsi said:
This one
TWRP_dragon_3.0.2-0_v2.img
- Added vendor.img flashing via TWRP. (thx to NYCHitman1 )
Download: https://onedrive.live.com/?authkey=!ABLdSOKIeXgg_XU&id=479EB75F5DD9DA59!117&cid=479EB75F5DD9DA59
Cheers
Click to expand...
Click to collapse
Using this version, TWRP loads but it cannot see my files on the internal sdcard, so I cannot install supersu, or anything else for that matter.
Not sure what I am missing.
Edit: Ok, didn't do the format data piece doing that now
Edit2: I managed to boot with boot-ryu-MXC89F-su-nocrypt-r205 and then copy the latest supersu to my sdcard. I rebooted into TWRP and installed Supersu successfully. Rebooted to system resulted in a boot loop to recovery?
Going into security to check encryption status causes setting to fc.
Edit 3 [Resolved] Copied the only kernel that would boot, as well as the clean boot.img from the latest factory images. Booted into TWRP and first flashed the clean boot.image from the factory images and then installed supersu successfully this time. I tried before with the boot.img from here -> http://superuser.phh.me/nexus/ryu/MXC89F/ but couldn't get supersu to install.
@Chainfire Thanks!! for supersu and flashfire support.
Great news! Any idea if supersu works with complete stock and encryption enabled?
And TWRP_dragon_3.0.2-0_v2.img doesn't solve the encryption problem yet, right?
doumer said:
Great news! Any idea if supersu works with complete stock and encryption enabled?
And TWRP_dragon_3.0.2-0_v2.img doesn't solve the encryption problem yet, right?
Click to expand...
Click to collapse
For me on a previously unrooted encrypted device I couldn't get it to work by just installing it and supersu, no.
But that may have been user error on my part, but my guess is that encryption was causing an issue with just the v2 TWRP installed as it could not see my data partition, even after a format.
scoobydu said:
Using this version, TWRP loads but it cannot see my files on the internal sdcard, so I cannot install supersu, or anything else for that matter.
Not sure what I am missing.
Edit: Ok, didn't do the format data piece doing that now
Edit2: I managed to boot with boot-ryu-MXC89F-su-nocrypt-r205 and then copy the latest supersu to my sdcard. I rebooted into TWRP and installed Supersu successfully. Rebooted to system resulted in a boot loop to recovery?
Going into security to check encryption status causes setting to fc.
Edit 3 [Resolved] Copied the only kernel that would boot, as well as the clean boot.img from the latest factory images. Booted into TWRP and first flashed the clean boot.image from the factory images and then installed supersu successfully this time. I tried before with the boot.img from here -> http://superuser.phh.me/nexus/ryu/MXC89F/ but couldn't get supersu to install.
@Chainfire Thanks!! for supersu and flashfire support.
Click to expand...
Click to collapse
Three lines above your thread ..
Tested xceed kernel and my pre-rooted kernel too.
Supersu will not modify the ramdisk at all.
"Can't find stock Image, already modified .." and will stop the ramdisk installer.
The system will start anyway, but with "old" ramdisk modifications.
So a fresh clean stock boot.img is recommended.
As well the Phhuson kernel is not pre-rooted for SuperSU.
( boot-ryu-MXC89F-su-nocrypt-r205 )
NEW Root access:
For root access: Pls install latest "stock" kernel and install SuperSU.zip version 2.72 directly afterwards - no reboot in between.
Hope this help all people in the same situation ..
Cheers
doumer said:
Great news! Any idea if supersu works with complete stock and encryption enabled?
And TWRP_dragon_3.0.2-0_v2.img doesn't solve the encryption problem yet, right?
Click to expand...
Click to collapse
Yes, it doesn´t solve the problem ..
There were no encryption related changes in this TWRP release.
But .... we have a new SuperSU now ..
Look here .. should be tested from the encryption fans .. Maybe this works on Pixel C too.
http://forum.xda-developers.com/htc...bootloader-t3365986/post66837323#post66837323
EDIT 2: Figured I might as well detail my complete procedure here, so others can confirm whether it works for them (or not):
Unlocked bootloader via HTC Dev
Flash TWRP
Boot into TWRP (Cancel decryption prompt & leave system read-only on boot)
Backup "Boot" and ""System Image" in TWRP to External SD
Wipe - Format Data (or Wipe Encryption) in TWRP
Boot device and let it re-encrypt
Reboot back into TWRP (Cancel decryption prompt & leave system read-only on boot)
In adb shell or TWRP Terminal, echo KEEPFORCEENCRYPT=true>>/cache/.supersu
Flash BETA-SuperSU 2.72 from external SD card
Reboot back to system, and the device will reboot itself once as SuperSU installs
Do the SunShine
Boot into TWRP, restore stock boot and system image backup & Wipe - Format Data (or Wipe Encryption) again
Reboot device and let it encrypt again
Reboot back into TWRP (Cancel decryption prompt & leave system read-only on boot)
In adb shell or TWRP Terminal, echo KEEPVERITY=true>>/cache/.supersu (the file should still be there, so both commands will now be present)
Flash BETA-SuperSU 2.72 (again) from external SD card
Reboot back to system, and the device will reboot itself once as SuperSU installs (again)
Now you're rooted, with pristine stock system image and with forced encryption and dm-verity still enabled. In this state, you should be able to Download OTAs, use Android Pay, etc.
Inside the SuperSU.zip are more informations ...
Overridable variables (shell, /system/.supersu, /cache/.supersu,
# /data/.supersu):
# SYSTEMLESS - Do a system-less install? (true/false, 6.0+ only)
# PATCHBOOTIMAGE - Automatically patch boot image? (true/false,
# SYSTEMLESS only)
# BOOTIMAGE - Boot image location (PATCHBOOTIMAGE only)
# STOCKBOOTIMAGE - Stock boot image location (PATCHBOOTIMAGE only)
# BINDSYSTEMXBIN - Poor man's overlay on /system/xbin (true/false,
# SYSTEMLESS only)
# PERMISSIVE - Set sepolicy to fake-permissive (true/false, PATCHBOOTIMAGE
# only)
# KEEPVERITY - Do not remove dm-verity (true/false, PATCHBOOTIMAGE only)
# KEEPFORCEENCRYPT - Do not replace forceencrypt with encryptable (true/
# false, PATCHBOOTIMAGE only)
# Shell overrides all, /data/.supersu overrides /cache/.supersu overrides
# /system/.supersu
Hope this helps .. but the external sd card could be tricky.
Cheers
followmsi said:
Three lines above your thread ..
Tested xceed kernel and my pre-rooted kernel too.
Supersu will not modify the ramdisk at all.
"Can't find stock Image, already modified .." and will stop the ramdisk installer.
The system will start anyway, but with "old" ramdisk modifications.
So a fresh clean stock boot.img is recommended.
As well the Phhuson kernel is not pre-rooted for SuperSU.
( boot-ryu-MXC89F-su-nocrypt-r205 )
NEW Root access:
For root access: Pls install latest "stock" kernel and install SuperSU.zip version 2.72 directly afterwards - no reboot in between.
Hope this help all people in the same situation ..
Cheers
Click to expand...
Click to collapse
Is this the case if you are already stock, unrooted and encrypted? as I had copied Supersu to my sdcard but TWRP could not see it.
boot-ryu-MXC89F-su-nocrypt-r205 was used only to boot the device after twrp was installed, as the stock boot.img would not boot and caused a recovery boot loop.
boot-ryu-MXC89F-su-nocrypt-r205 got me out of the bootloop and allowed me to recopy supersu to the sdcard, but I could not see if encrypttion was now disabled, as settings/security caused a force close of settings.
I had assumed that boot-ryu-MXC89F-su-nocrypt-r205 allowed me to disable encryption and copy supersu to sdcard, which twrp could then find and supersu worked successfully.
scoobydu said:
Is this the case if you are already stock, unrooted and encrypted? as I had copied Supersu to my sdcard but TWRP could not see it.
Click to expand...
Click to collapse
If you are on stock and unrooted it works the way above.
Sorry, I am not sure on encryption now.
Removed it on the first day.
Before copying SuperSu to data .. just followed the guide.
Needs to be verified if 3.0.0.0 version from xceed is able to access encrypted data ..
Sorry, can't help you better here ...
scoobydu said:
Is this the case if you are already stock, unrooted and encrypted? as I had copied Supersu to my sdcard but TWRP could not see it.
boot-ryu-MXC89F-su-nocrypt-r205 was used only to boot the device after twrp was installed, as the stock boot.img would not boot and caused a recovery boot loop.
boot-ryu-MXC89F-su-nocrypt-r205 got me out of the bootloop and allowed me to recopy supersu to the sdcard, but I could not see if encrypttion was now disabled, as settings/security caused a force close of settings.
I had assumed that boot-ryu-MXC89F-su-nocrypt-r205 allowed me to disable encryption and copy supersu to sdcard, which twrp could then find and supersu worked successfully.
Click to expand...
Click to collapse
I saw only the first part of your answer ...
You got recovery boot-loop after installing TWRP ?
Never had any reboot issues, but I had always unencrypted data partition and could access my SuperSu.zip - all the time.
Never had to reboot without unchanged fstab nor stock kernel, as was able to flash SuperSu all the time.
As said before, I did remove encryption directly.
I did use xceed kernel for this .. some time ago.
Needs to be checked if xceed 3.0.0.0 TWRP has also problems to boot into system with stock kernel, was always used with xceed kernel together.
Version 3.0.2.0.img is using xceed only settings.
Version 3.0.2-0_v2.img has some parts from NYCHitman1 included.
Needs to be verified...
But we may need to adapt the instructions .. and may still need a stock rooted kernel for initial SuperSU installation.
Uploaded new TWRP version .. as TWRP flashable zip !
Just install this version with your current TWRP version and reboot to recovery again.
Have a look .. OTG is working now.
Update.ZIP_TWRP_dragon_3.0.2-0_v4.zip
Just made a fresh backup to my usb-stick via USB-OTG ..
Cheers
Samt434 said:
After flashing a stock android N preview 2, I installed TWRP and flashed the superSU ZIP (2.72). I can confirm this works perfectly, and i have root on android N preview 2
Click to expand...
Click to collapse
Is your device still encrypted ?
Did you format the /data partiton inside TWRP ?
How did you access the SuperSu.zip file inside TWRP ?
Did you install other kernel for intermediate reboot into system to decrypt data ?
A lot of questions .. but it helps to understand problems better
Thanks
I just successfully rooted the Android N beta with this!
I upgraded from Preview 2 via flash-all without wiping data.
The Magisk Universal Systemless Interface by XDA Recognized Developer @topjohnwu has received an update that bumps it up to version 7. There are a bunch of notable changes that follow in the changelog:
Fully open source
Remove supolicy dependency, use my own sepolicy-injection
Run everything in its own selinux domain, should fix all selinux issues
Add Note 7 stock kernel hex patches
Add support to install Magisk in Manager
Add support for image merging for module flashing in Manager
Add root helpers for SuperSU auto module-ize and auto upgrading legacy phh superuser
New paths to toggle busybox, and support all root solutions
Remove root management API; both SuperSU and phh has their own superior solutions
Downloads:
1)Official MM OOS STOCK 3.1.3 - https://s3.amazonaws.com/oxygenos.o...OTA_018_all_201609291837_741146bcf28e4587.zip
2)Official MM H2OS Stock 2.0 - http://download.h2os.com/oneplus_x/mp/OnePlusH2OS_14_OTA_001_all_201609270726_5aa42273def7431b.zip
3) Use this recovery to Flash Magisk (TWRP by Bluespark) - http://forum.xda-developers.com/devdb/project/dl/?id=20236
4)Magisk Manager.apk - http://forum.xda-developers.com/attachment.php?attachmentid=3893660&d=1475527472
5)Latest Magisk Zip File - http://forum.xda-developers.com/attachment.php?attachmentid=3893659&d=1475527472
6)Systemless Superuser (use this Systemless superuser) - http://forum.xda-developers.com/apps/magisk/magisk-phh-s-superuser-android-pay-t3435921
7)Magisk Uninstaller (if anything goes wrong) - http://forum.xda-developers.com/attachment.php?attachmentid=3893658&d=1475527472
Before Flashing:
1) If you are already on MM with stock recovery and no root,then wipe your data and cache,flash full MM rom pack, flash provided TWRP and follow the instruction below
2)If you are in MM with rooted system,do wipe data and cache,flash full rom pack, flash twrp and follow the instruction
MOST IMPORTANT:
BEFORE FLASHING MAGISK,YOU NEED TO HAVE UNMODIFIED SYSTEM
USE TWRP TO FLASH MAGISK
FLASHING INSTRUCTION:
1)Flash your rom pack
2)Flash magisk zip file
3)Flash systemless root
4)Flash systemless xposed
Ooh laa... Got unmodified system with root access
what is this used for?
meraj99 said:
what is this used for?
Click to expand...
Click to collapse
Systemless Benefits
OTA:
The system partition will not be modified or mount r/w, thus your Android devices are capable of applying OTA updates even if ur mobile s rooted
Safety Net:
Android Pay is confirmed working!
Im not responsable for hard bricks/ soft bricks on youre devices do at your own risk
I already test it and works on my rooted ms428
I want to give a special thanks to the devs for the patience, dedication and for working hard to make the root possible for this device
Its highly recommended to perform a nan-backup incase of an emergency or incase if you want to go back
The steps are quite simple
1) root your device, if you dont have it rooted here is the link for the steps to root for the lg k10 both metropcs and T-Mobile editions only
(forum.xda-developers.com/lg-k10/development/root-twrp-rom-t-mobile-k428-k10-t3582493)
2) install magisk manager on playstore
3) open magisk manager and install the zip file via automatic
4) boot into twrp and flash the zip file located in magisk folder
5) once it done wipe cache and dalvik cache
6) once it finish booting open magisk manager and click on downloads tab
7) install on magisk xposed framework sdk23 (marshmallow) *note if you have lollipop its the sdk22
8) once it finished click on reboot later, boot into twrp and wipe dalvik cache and cache and reboot
9)install xposed apk (its the one i use on my ms428 forum.xda-developers.com/xposed/material-design-xposed-installer-t3137758)
10) enjoy
See it for your self ?
itztropic- after I rooted I just downloaded the xposed framework from the website normally and it worked properly, I must be not understanding something about the method you described?
I don't really understand what magisk is for I thought it was a developer tool of some sort (which i'm not)
leopard_fist said:
itztropic- after I rooted I just downloaded the xposed framework from the website normally and it worked properly, I must be not understanding something about the method you described?
I don't really understand what magisk is for I thought it was a developer tool of some sort (which i'm not)
Click to expand...
Click to collapse
Magisk is a frontend designed to manage apps and modules that use systemless capabilities. It has its own superuser based on phh's superuser, and features modules much like Xposed, though some are useful even on Nougat. Xposed can be installed systemless as well and Magisk can disable and re-enable root and Xposed on the fly, as well as its modules, so you can have a rooted phone and still use Android Pay and Pokemon Go.
ItzTropic said:
Im not responsable for hard bricks/ soft bricks on youre devices do at your own risk
I already test it and works on my rooted ms428
I want to give a special thanks to the devs for the patience, dedication and for working hard to make the root possible for this device
Its highly recommended to perform a nan-backup incase of an emergency or incase if you want to go back
The steps are quite simple
1) root your device, if you dont have it rooted here is the link for the steps to root for the lg k10 both metropcs and T-Mobile editions only
(forum.xda-developers.com/lg-k10/development/root-twrp-rom-t-mobile-k428-k10-t3582493)
2) install magisk manager on playstore
3) open magisk manager and install the zip file via automatic
4) boot into twrp and flash the zip file located in magisk folder
5) once it done wipe cache and dalvik cache
6) once it finish booting open magisk manager and click on downloads tab
7) install on magisk xposed framework sdk23 (marshmallow) *note if you have lollipop its the sdk22
8) once it finished click on reboot later, boot into twrp and wipe dalvik cache and cache and reboot
9)install xposed apk (its the one i use on my ms428 forum.xda-developers.com/xposed/material-design-xposed-installer-t3137758)
10) enjoy
Click to expand...
Click to collapse
Don't re-create threads when they are already present. LG K10 ROMS, KERNELS, RECOVERIES, & OTHER DEVELOPMENT is not the place to post these kinds of things.
There is already a thread for Xposed: https://forum.xda-developers.com/lg-k10/how-to/guide-xposed-lg-k10-t3505970.
Post it there. Delete this thread.
GuyInDogSuit said:
Magisk is a frontend designed to manage apps and modules that use systemless capabilities. It has its own superuser based on phh's superuser, and features modules much like Xposed, though some are useful even on Nougat. Xposed can be installed systemless as well and Magisk can disable and re-enable root and Xposed on the fly, as well as its modules, so you can have a rooted phone and still use Android Pay and Pokemon Go.
Click to expand...
Click to collapse
Thanks for the explanation-also Overdrive took some time via pm to explain a few things about it. I've been working with it a couple days and I like it now that I understand, another cool thing to learn about