Related
NOTE:
This post is/was only relevant for users of the original modded stock recovery for YP2. For the newer & better TWRP recovery for YotaPhone 2 installing unsigned packages such as Xposed framework is not an issue.
Please note that the Xposed version below is outdated, Xposed alpha 4 is available. See Xposed for Lollipop thread.
Old post content:
Not exactly a proper development thread, but posting it here anyway because of the relation with the modded recovery, ad the slightly technical angle.
Xposed framework for Lollipop allows you to install modules that tweak/change many aspects of Android. It's pretty powerful as it can hook into existing software and change it's functionality. The version referred to in this post is an alpha version.
Therefore:
Warning: I recommend you don't install this unless you're a nerd. It's not yet stable, and may cause trouble (such as boot-loops).
Also: by the time you read this there may be newer versions, so read the Xposed thread for updates.
Background
The modded recovery image allows to install software signed by either Yota Devices (such as ota update zips) or signed with testkeys, but it does not allow to flash UNsigned zips. Many flashable zips are signed with testkeys (like SuperSU) but rovo89's Xposed flashable zip for LP in the current 20150430 version are unsigned, so we can't flash them as-is.
Flashing it anyway:
There's two ways: the harder and slightly educational way (useful for e.g. when new Xposed versions are released) and the lazy but convenient way.
1) Signing the Xposed framework zip yourself:
You need:
- signapk.jar plus test key and certificate
Get SignApk.jar from somewhere (build it from AOSP source, or download a zip from this thread (I used zipaligner 1.2, linux). This zip contains other stuff, but we need testkey.pk8, testkey.x509.pem and signapk.jar
- Xposed framework zip for LP 5.0 (xposed-sdk21-arm-20150430.zip) from the official thread from here
- java environment (JDK or JRE)
To sign the file put all files in one dir (including xposed-sdk21-arm-20150430.zip) and run:
Code:
java -jar signapk.jar -w testkey.x509.pem testkey.pk8 xposed-sdk21-arm-20150430.zip xposed-sdk21-arm-20150430_signed.zip
You just created xposed-sdk21-arm-20150430_signed.zip that you can flash.
2) Using a pre-Signed zipfile:
I attached a testkey-signed version of rovo89's file xposed-sdk21-arm-20150430.zip to this post for convenience, so you can skip the steps above.
Steps to install the Xposed framework for LP
1) put device in fastboot/download mode and boot the modded recovery image (see recovery thread)
2) choose "apply update from ADB" from recovery menu
Code:
adb sideload <yourpath>/xposed-sdk21-arm-20150430_signed.zip
3) reboot
4) choose allow 'unknown sources' in settings->security
5) copy the file XposedInstaller_3.0-alpha2.apk to your phone (or scan the QR code on the Xposed page to download this file to your phone directly.
6) use a file manager (like ES File Explorer, or the built-in Cabinet) to browse to and open XposedInstaller_3.0-alpha2.apk and install it.
Now you can download Xposed modules through the Xposed Installer app. I tried GravityBox [LP] (make sure you select the right version!) to change the launcher grid to 5x5 instead of 4x4. After a reboot that worked. I'm not saying that using GravityBox is safe, they warn that it may cause trouble with non-standard ROM's (such as ours).
Please not that I can't/won't provide any support for Xposed itself, please see the relevant Xposed threads for that.
Credits:
rovo89, author of the Xposed Framework
nice one, many thanks
Does anyone have then latest version please that's signed for this device
Sent from my YD201 using Tapatalk
read the start topic good, every thing you need is in there with links
Gojira-r32 said:
read the start topic good, every thing you need is in there with links
Click to expand...
Click to collapse
Which version of xposed is for yotaphone I see a few different versions on the xposed thread. Link From the op
Sent from my YD201 using Tapatalk
I used xposed-v68-sdk21-arm.zip just two days ago, and signed it myself according to the instructions.
It seems to play well, at least for two days
I just booted TWRP and sideloaded it, I never flashed the TWRP.
Had a little mess getting the driver to install in windows, when TWRP sideloads, it had a new identity in the device manager and I was unable to make accept the drivers I had. So I made a little manual edit in the .inf file from the yotaphone flashtool package, and then was able to load the driver needed. Google was my friend, but I can paste the change here later if someone want it.
Those who are using xposed do you notice any long freeze on the epd and reboots.
Sent from my YD201 using Tapatalk
adamo86 said:
Those who are using xposed do you notice any long freeze on the epd and reboots.
Sent from my YD201 using Tapatalk
Click to expand...
Click to collapse
Nope. I am running latest Xposed framework with gravitybox and youtube adaway. No crashes or freezes, but the battery life does fluctuate quite a bit sometimes. But I think that that is because of Lollipop.
No issues with xposed here either. Running alpha4 I believe.
Installed but not active.. That's what i get! Why is thaT?
Thanks!
I signed the last version of xposed using the method in the first post, and flashed (file attached) using TWRP. no issues so far.
no need to say, make sure you backup first!
Bootloop
I have accidentally flashed the xposed-sdk21-arm-20150430_signed.zip...so my phone stuck in bootloop. How can I uninstall it?
Wanderess said:
I have accidentally flashed the xposed-sdk21-arm-20150430_signed.zip...so my phone stuck in bootloop. How can I uninstall it?
Click to expand...
Click to collapse
SOLVED. Stock rom (4.4.3 HK) flashed with Yota Flasher. After this everything went smoothly.
Oficial Xposed running with no problems, well just one named Lollipop
Jeopardy said:
Nope. I am running latest Xposed framework with gravitybox and youtube adaway. No crashes or freezes, but the battery life does fluctuate quite a bit sometimes. But I think that that is because of Lollipop.
Click to expand...
Click to collapse
The same with me, Lollipop because using the EPD is so much better, otherwise I would happily be on KitKat, battery life on Lollipop is awfull, I also have the Xposed installed the official one with no problems, running some Modules to prevent battery from draining as much as possible in this Google Sucking Lollipop...
Not my credit but took me a while to figure out and I didn't find it here beforehand. So, I'm sharing it here. Apologies if it's already in a thread somewhere here.
1. Install Adaway (actually it doesn't seem to matter if you install the apk before or after the next steps)
2. Make sure Adaway has root access
3.Flash [on Recovery] AdAway_systemless_hosts_v2.zip (https://www.androidfilehost.com/?fid=24438995911977059])
4.Install Busybox (this did the trick)
5. Run Adaway Update, test & profit
I hope it helps others...
Installing Magisk with root and enabling systemless hosts from within Magisk is a better option. (You also don't need to install busybox because Magisk has that built in as well)
Sent from my Nexus 5X using Tapatalk
Trevonn said:
Installing Magisk with root and enabling systemless hosts from within Magisk is a better option. (You also don't need to install busybox because Magisk has that built in as well)
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
thanks body was easy.
Since OTA updates NXT-L09CxxxB580+ for our devices is out and because of the fixes in the kernel, we are now able to root our device using Magisk.
This is a step-by-step guide leading you throughout the process and also stating the pros of using Magisk over using SuperSU.
News:
09/11/2017
- Magisk was updated to v14 which adds more root hiding mechanisms and also more devices compatibility.
07/18/2017
- Magisk was updated to version 13.3 and will once again pass SafetyNet without any issues
- To update, just open MagiskManager and press Download and Install (if you are new to Magisk, just follow guide below)
07/14/2017
- Google updated SafetyNet and Magisk devices will not pass it
Pros of using Magisk over SuperSU:
Automatic updates
Does not break OTA updates
Does not break SafetyNet (you will be able to use AndroidPay, play Pokemon Go, install Netflix from Google Play and use apps requiring SafetyNet pass)
Ability to install modules from the repository (much like xposed modules)
Before installation:
Unlock your bootloader
Make sure you have stock boot.img
Make sure you are on B580+ as Magisk cannot be installed on older versions
Installation:
Flash this recovery in fastboot: https://forum.xda-developers.com/mate-8/orig-development/twrp-t3576364
Flash latest Magisk in TWRP recovery: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Boot into system
Check your apps for Magisk Manager
[OPTIONAL] In the magisk manager, you can check if you pass SafetyNet
Troubleshooting:
Magisk Manager was not installed
- Open the Magisk.zip, inside open common folder and install magisk.apk
SafetyNet does not pass
- First try disabling and enabling Magisk Hide in the Magisk Manager
- If above does not help open stock Huawei dialer, dial *#*#2846579#*#*, tap Background settings, tap LOG settings, check all checkboxes, open Magisk Manager and disable and enable Magisk Hide
Supported devices:
All NXT-L29 B580+ devices
All NXT-L09 B580+ devices
All other Mate 8 versions with B580+
Basically any other device as Magisk is not device dependent (works with like 95% of all devices, as long as the device's kernel supports loop mount and few other things)
My Magisk Modules for Mate 8:
[Magisk] Official Huawei Automatic Call Recorder
Hope this will help you guys!
car nikolaj
. I recommend this app to anyone who want for the root acces. :good::good::good::good::good::good::good:
Does this method and the TWRP attached work on B585?
Thanks.
Just installed B581 via OTA and decided to give Magisk a try. I was able to get it installed by following your instructions but I'm not able to pass SafetyNet due to CTS profile mismatch. Any idea?
xxlap1xx said:
Just installed B581 via OTA and decided to give Magisk a try. I was able to get it installed by following your instructions but I'm not able to pass SafetyNet due to CTS profile mismatch. Any idea?
Click to expand...
Click to collapse
Same here. CTS profile mismatch
Fresh B581
Thanks for this, have not tried it yet but if I do, and I for some reason wish to unroot, how does one do that?
necc0 said:
Does this method and the TWRP attached work on B585?
Thanks.
Click to expand...
Click to collapse
Yes
xxlap1xx said:
Just installed B581 via OTA and decided to give Magisk a try. I was able to get it installed by following your instructions but I'm not able to pass SafetyNet due to CTS profile mismatch. Any idea?
Click to expand...
Click to collapse
sZx1 said:
Same here. CTS profile mismatch
Fresh B581
Click to expand...
Click to collapse
Did you installed Xposed? Check Magisk manager settings if you have Magisk hide enabled.
shestolemyusrname said:
Thanks for this, have not tried it yet but if I do, and I for some reason wish to unroot, how does one do that?
Click to expand...
Click to collapse
You just press uninstall button in Magisk manager
Boosik said:
Yes
Did you installed Xposed? Check Magisk manager settings if you have Magisk hide enabled.
You just press uninstall button in Magisk manager
Click to expand...
Click to collapse
When I boot into TWRP for the first time, should I keep Ready Only or Swipe to Allow Modifications?
Can you help me??
Magisk installed -all its ok, but im trying copy one folder and set attributes to system\app folder, but unfortunatelly - cannot write to system\app.... (i must install HwCallRecorder)
I tested Total commander and Root explorer
thx
Boosik said:
Yes
Did you installed Xposed? Check Magisk manager settings if you have Magisk hide enabled.
You just press uninstall button in Magisk manager
Click to expand...
Click to collapse
Nope, freshly installed B581. I read something about SafetyNet was being updated so that's probably why.
Sent from my HUAWEI NXT-L29 using Tapatalk
woji said:
Can you help me??
Magisk installed -all its ok, but im trying copy one folder and set attributes to system\app folder, but unfortunatelly - cannot write to system\app.... (i must install HwCallRecorder)
I tested Total commander and Root explorer
thx
Click to expand...
Click to collapse
I have the same issues as woji, and also can't write hosts file for AdAway.
Seemingly the simple reasons for rooting aren't available in systemless root, or we have errors preventing this?
Hilton.Swart said:
I have the same issues as woji, and also can't write hosts file for AdAway.
Seemingly the simple reasons for rooting aren't available in systemless root, or we have errors preventing this?
Click to expand...
Click to collapse
Same, I had issues with adaway not being to write hosts files using magisk as well. I went back and flashed SuperSU and the problem is gone.
Sent from my HUAWEI NXT-L29 using Tapatalk
Hilton.Swart said:
I have the same issues as woji, and also can't write hosts file for AdAway.
Seemingly the simple reasons for rooting aren't available in systemless root, or we have errors preventing this?
Click to expand...
Click to collapse
xxlap1xx said:
Same, I had issues with adaway not being to write hosts files using magisk as well. I went back and flashed SuperSU and the problem is gone.
Sent from my HUAWEI NXT-L29 using Tapatalk
Click to expand...
Click to collapse
Open Magisk Settings and enable Systemless hosts data.
Systemless root means you can't directly edit /system partition, because editing it voids SafetyNet. Magisk uses Magic Mount to systemlessly replace /system files and folders on-the-fly without actually modifying the original ones. All you need is appropriate modules from magisk manager "Downloads" tab.
woji said:
Can you help me??
Magisk installed -all its ok, but im trying copy one folder and set attributes to system\app folder, but unfortunatelly - cannot write to system\app.... (i must install HwCallRecorder)
I tested Total commander and Root explorer
thx
Click to expand...
Click to collapse
Try installing it as user app and use App Systemizer module in magisk manager to convert it to system app.
xxlap1xx said:
Nope, freshly installed B581. I read something about SafetyNet was being updated so that's probably why.
Sent from my HUAWEI NXT-L29 using Tapatalk
Click to expand...
Click to collapse
Yea you are right, I have it working, but the process is a bit tedious. We better wait for new Magisk version, where it should be fixed.
shestolemyusrname said:
When I boot into TWRP for the first time, should I keep Ready Only or Swipe to Allow Modifications?
Click to expand...
Click to collapse
Keep it Read Only.
Boosik said:
Open Magisk Settings and enable Systemless hosts data.
Click to expand...
Click to collapse
This was my first logical step when hosts would not apply, I've changed the settings numerous times and the host simply will not write.
Tried Magisk for the ability to keep SafetyNet intact, but it still fails any tests. So I think I'll follow xxlap1xx, and try Magisk at another time.
Boosik said:
Yes
Did you installed Xposed? Check Magisk manager settings if you have Magisk hide enabled.
You just press uninstall button in Magisk manager
Click to expand...
Click to collapse
No Xposed installed. Hide was enabled in settings and in hide tab as well.
Reading about SafetyNet looks like unlocked bootloader can be a problem.
V13 beta same results.
Probably have to wait for workaround
Thanks.
Hilton.Swart said:
This was my first logical step when hosts would not apply, I've changed the settings numerous times and the host simply will not write.
Tried Magisk for the ability to keep SafetyNet intact, but it still fails any tests. So I think I'll follow xxlap1xx, and try Magisk at another time.
Click to expand...
Click to collapse
sZx1 said:
No Xposed installed. Hide was enabled in settings and in hide tab as well.
Reading about SafetyNet looks like unlocked bootloader can be a problem.
V13 beta same results.
Probably have to wait for workaround
Thanks.
Click to expand...
Click to collapse
I already know how to workaround it, but the process is a bit unfriendly to normal users (requires terminal emulator). We better wait for new Magisk beta.
Boosik said:
Yes
Did you installed Xposed? Check Magisk manager settings if you have Magisk hide enabled.
You just press uninstall button in Magisk manager
Click to expand...
Click to collapse
Boosik said:
I already know how to workaround it, but the process is a bit unfriendly to normal users (requires terminal emulator). We better wait for new Magisk beta.
Click to expand...
Click to collapse
Can you, please, share. I'm pretty handy with terminal and willing to experiment. Worst - have to return to stock.
Thanks
As current and all previous Magisk releases can break any fire tv on update from manager, I made custom build of Magisk 25.1 for Fire TV
Releases GitHub URL
Changes:
- Manager doesn't have direct install / update options
- Dark theme by default
- Amazon orange color for default and AMOLED themes
- Grant root permission by default
- Fix issue of enabled Zygisk with Xposed Framework
- Change version to 25.1.FTV (25777)
Fixes:
- fix D-PAD navigation on Grant / Deny root dialog
- fix D-PAD navigation on Log section
- fix D-PAD navigation on Zygisk DenyList
- fix D-PAD navigation on Reboot button after flash
Install:
- Install APK (uninstall previous Manager version if exist 1st),
- Rename apk to zip and flash from TWRP recovery
Have fun!
p.s. maybe someday devs will apply those changes to source, now they call it "offtopic"
Hey, it hangs at CHECKING for digest. Magik 23.0 worked before. Any idea?
Isn't to grant / deny root access with the remote working by default for fireTV devices?
Never saw a problem like that, for tank/sheldon/mantis/sloane, works fine here!?
Sus_i said:
Isn't to grant / deny root access with the remote working by default for fireTV devices?
Never saw a problem like that, for tank/sheldon/mantis/sloane, works fine here!?
Click to expand...
Click to collapse
It works on Android 9, but on Mantis (4K with 7.1.2) dialog worked with Magisk 20.4 (old manager) and broken (don't have any focus so user can't press any button in it) with any Magisk 21+ and new Manager GUI
mamcho said:
Hey, it hangs at CHECKING for digest. Magik 23.0 worked before. Any idea?
Click to expand...
Click to collapse
hm, it's apk from studio, tesed it on TWRP from Fire TV 4K and it installs fine. Try to disable digest check in TWRP options.
Im on sloane and disabling digets check doesnt change anything. I ve read that 24.3 is problematic for sloane. 23.0 works tho
Hi,
I'm on 4K stick and I have Magisk 24.3 installed (apk from their github).
If I want to switch to this I have to uninstall current Magisk Manager even if I flash from TWRP?
BTW: guys on magisk github page asnwer really bad to your suggestion, no reason to do that
The manager UI is not tv-friendly so it's really easy to press update by mistake. It was the 1st thing I though when I saw it after installation...
Noisemaker00 said:
Hi,
I'm on 4K stick and I have Magisk 24.3 installed (apk from their github).
If I want to switch to this I have to uninstall current Magisk Manager even if I flash from TWRP?
Click to expand...
Click to collapse
You need to uninstall Manager in any case because app signature differs. After install you need o flash apk renamed to zip from recovery to match daemon / apk signatures. Magisk in 1s post updated to v25.0.FTV.
tsynik said:
You need to uninstall Manager in any case because app signature differs. After install you need o flash apk renamed to zip from recovery to match daemon / apk signatures. Magisk in 1s post updated to v25.0.FTV.
Click to expand...
Click to collapse
So the steps are:
uninstall current magisk-manager version
download and rename your .apk to .zip
reboot to twrp and flash the zip
reboot the system
is it correct?
hiding the app is not working propertly. if i generate a new app it fails to load and want to download full manager again.
mamcho said:
hiding the app is not working propertly. if i generate a new app it fails to load and want to download full manager again.
Click to expand...
Click to collapse
Yes, probably it's some kind of bug in Magisk. When hiding, Magisk replaced with stub app, which download full apk from https://github.com/tsynik/Magisk/releases, but failing to load it's classes and initialize app context.
Fixed with v25.1.FTV release
tsynik said:
As current and all previous Magisk releases can break any fire tv on update from manager, I made custom build of Magisk 25.1 for Fire TV
Releases GitHub URL
Changes:
- Manager doesn't have direct install / update options
- Dark theme by default
- Amazon orange color for default and AMOLED themes
- Grant root permission by default
- Fix issue of enabled Zygisk with Xposed Framework
- Change version to 25.1.FTV (25777)
Fixes:
- fix D-PAD navigation on Grant / Deny root dialog
- fix D-PAD navigation on Log section
- fix D-PAD navigation on Zygisk DenyList
- fix D-PAD navigation on Reboot button after flash
Install:
- Install APK (uninstall previous Manager version if exist 1st),
- Rename apk to zip and flash from TWRP recovery
Have fun!
p.s. maybe someday devs will apply those changes to source, now they call it "offtopic"
Click to expand...
Click to collapse
Hello tsynik
I flashed this version, but never granted su permissions .
The Magisk Mannager is missing in fireOS.
When reinstall, it crashes and disappear .
Can you give me instructions on how to uninstall this version?
thanks
What I did was to rename .apk to .zip, flash with twrp. manager was not to be found on apps. then I manually installed the .apk and it appeared on apps.
yakovperelman69 said:
Hello tsynik
I flashed this version, but never granted su permissions .
The Magisk Mannager is missing in fireOS.
When reinstall, it crashes and disappear .
Can you give me instructions on how to uninstall this version?
thanks
Click to expand...
Click to collapse
I am having the same issue
BTW to uninstall rename the apk to uninstall.zip then flash it in twrp
I have a tank (2nd gen stick) with latest firmware (5.2.9.5 at time of writing)
Now that Magisk v26 has dropped support for android 5, it would be wise to release a final version for old fire sticks.
Anyway the UI does not start at all, both on your fork and on the original v25.2 . (and, both of them do not remember superuser permissions - they get asked every time)
I just tried to flash Magisk v26.1 via TWRP. FireOS6 (mantis - FTV4K)
First fresh Kernel followed by Magisk v26.1.zip.
All seams to work but I noticed that the repacking step went unusual fast!
After rebooting and updating Magisk app to v26.1 it seams to work.
But now I get after a fresh start/reboot a warning message in Magisk app that an reflash is necessary!
I now went back to 25.2 (again Kernel + Magisk.zip) and all is good again.
I do not know what happens here or if something went wrong or if 26.1 is not fully compatibe to FireOS6 (Android 7)...
Anyway - Just wanted to let you all know.
Hi
fyi:
I created a Magisk Module to replace the FakeStore in OmniROM with the patched PlayStore from NanoDroid
The Module will replace the apk for the FakeStore with an empty file and add the directory
/system/priv-apps/Phonesky
with the patched PlayStore from NanoDroid.
The patched Playstore works with MicroG so that apps using the license functionality from the Playstore can also be used in ROMs using MicroG .
The ZIP file with the Magisk Module can be downloaded from here:
http://bnsmb.de/files/public/Android/PlayStore_for_MicroG.zip
(I am not sure if I can attach the file in this forum ..)
regards
Bernd
How can i update this patched Playstore Module?
Does your module do the same as the fakestore2playstore module ? If not, what are the differences ?
SERGE4NT said:
How can i update this patched Playstore Module?
Click to expand...
Click to collapse
I don't think it needs updating...
edit : so, I wanted to install your module next to this version of microG. It is a microG installer that works as a Magisk module, and the only way I got microG to work on unofficial CrDroid Android 13 for the Samsung A20e.
Anyway, didn't managed to install your module through Magisk. If I tried to install it after having installed the microG module, it says error: system/priv-app/Phonesky already exists.
If I try to install it before the microG module, it says error: no version of microG detected.
I had to boot to TWRP, try to install it from there, where it would hang on detecting TWRP, force restart my phone, then it appears as installed for some reason.
But it works ! Don't know how or why, or what's up with the installation, but it works, whereas other versions of this module didn't, so... thanks x)
Hi
fiy:
see How to install a more recent version of the Playstore in OmniROM for how to install a more recent version of the playstore
regards
Bernd