Hello guys,
ive been using magisk module of ios emoji (from here) just fine on 1.1.7. Then I updated on 1.1.8 (via OTA method - lost root, fastboot booted patched boot.img - rooted again) and the module suddenly stopped working - simply doesnt appear anywhere. I tried to delete it, install it again, reboot device, but no luck. Tried even different modules of iOS emojis, still not working.
My ionly other module Fullscreen/immersive gestures is working fine after the update. Magisk app updated on thle latest version.
Any idea what could be the issue?
Thank you!
Try this: https://forum.xda-developers.com/t/...dex-facebook-samsung-twemoji-windows.3418801/
Create Magisk Module and Flash it over Magiskt, the internal flash method from app is not working properly.
If its not working download FX File Manager > Grant Root and delete all Folders in \Root\data\fonts\files
Restart your phone and you should get the iOS Emoji's. It could be that you need to delete these folders in \files again after the next Gboard Update
paper88 said:
Try this: https://forum.xda-developers.com/t/...dex-facebook-samsung-twemoji-windows.3418801/
Create Magisk Module and Flash it over Magiskt, the internal flash method from app is not working properly.
If its not working download FX File Manager > Grant Root and delete all Folders in \Root\data\fonts\files
Restart your phone and you should get the iOS Emoji's. It could be that you need to delete these folders in \files again after the next Gboard Update
Click to expand...
Click to collapse
You're a life saver, thank you so much, I really appreciate it, worked perfectly!
paper88 said:
Try this: https://forum.xda-developers.com/t/...dex-facebook-samsung-twemoji-windows.3418801/
Create Magisk Module and Flash it over Magiskt, the internal flash method from app is not working properly.
If its not working download FX File Manager > Grant Root and delete all Folders in \Root\data\fonts\files
Restart your phone and you should get the iOS Emoji's. It could be that you need to delete these folders in \files again after the next Gboard Update
Click to expand...
Click to collapse
I couldn't get it to work no matter what procedure I tried to follow. Currently running on 1.1.7 with the 16.4 beta magisk module but I have zero luck.
I just noticed that I'm a beta tester of GBoard. Can it have an impact? Not sure if anyone tried it with Beta version.
Related
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
I've finally figured out how to get the ViPER4Android Magisk module properly working on a Galaxy S6 running Nougat.
Open the Download section of the Magisk Manager app; flash ViPer4Android FX and App Systemizer.
Reboot.
Install a ViPER4Android APK. I prefer the Material verzion on XDA Labs, but the original will work just fine.
Put LazerL0rd's script in /magisk/.core/post-fs-data and change the permission to 0755.
Replace the audio_effects.conf file in /magisk/.core/v4a/system/etc with Vaira's version. Copy that same file to /magisk/.core/v4a/vendor/etc. Make sure that the permission on both is set to 0644.
Open AppSystemizer in your app drawer and select ViPER4Android FX. Remember to hit the green save button.
Reboot.
Tried this on an HTC One M8 with LOS and Team M8 Kernel - it caused a bootloop for me.
Help with step 4 please...
EncryptedCurse said:
I've finally figured out how to get the ViPER4Android Magisk module properly working on a Galaxy S6 running Nougat.
Open the Download section of the Magisk Manager app; flash ViPer4Android FX and App Systemizer.
Reboot.
Install a ViPER4Android APK. I prefer the Material verzion on XDA Labs, but the original will work just fine.
Put LazerL0rd's script in /magisk/.core/post-fs-data and change the permission to 0755.
Replace the audio_effects.conf file in /magisk/.core/v4a/system/etc with Vaira's version. Copy that same file to /magisk/.core/v4a/vendor/etc. Make sure that the permission on both is set to 0644.
Open AppSystemizer in your app drawer and select ViPER4Android FX. Remember to hit the green save button.
Reboot.
Click to expand...
Click to collapse
Sorry new to modding,
Step 4: not sure exactly where to paste? I tried but when saving I get error no permission..? I've been trying to get this working for weeks...
SM-G925F
Stock Rom
Magisk 13.3
Busybox. Stericson
The latest Magisk version (14.6) which has received quite a revamp thanks to @topjohnwu finally works easily and like a charm on our devices.
I'm running the stock rom with advanced stock kernel and haven't been able to get Magisk running.
Until now.
I gave it another shot after I had heard about the many changes in 14.6 and so installed the Magisk Manager again, flashed the zip and can now finally enjoy Pokemon GO on a rooted Z2.
Thought I'd share this
Edit: I have to dim my enthusiasm a little.
I could flawlessly install it and it marks it as installed. When apps ask for root permission, I can grant it and the apps recognize the root permission too ...
but something seems a little odd. my ES file explorer won't write in my root folder, Titanium won't uninstall system apps, and Greenify also doesn't work properly ...
Guys, i am on stock os, 7.0 , recently flashed magisk for systemless root and when i tried to use app mover to move some apps to system, i get error as could not remount/system. Tried supersu root as well but same result, im a newbie here. please help Used both Vegito and Ex kernel too. but i get the error everytime. But root checker shows i have root.
You could try the Magisk module named "App Systemizer". It can convert user apps to system apps, but systemlessly.
thorin0815 said:
You could try the Magisk module named "App Systemizer". It can convert user apps to system apps, but systemlessly.
Click to expand...
Click to collapse
Thanks, Is there a way to edit system files , like modifying host file ? It seems i have been using system root all these days. Is it still available ?
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.