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 ...
Related
I can't delete any system apps with it anymore, does anybody else have the same problem or even a fix for it?
Working fine on 6.01 for me, Did you try uninstalling and reinstalling it?
I just updated to 6.0.1 myself, rooted using superSU 2.61. I too cannot delete system apps using titanium. I tried to uninstalled and reinstall the app (via playstore) but it didn't help.
I also tried to do the same via the root explorer option in ES file explorer and it didn't work. I tried to toggle the root explorer option in ES, but after I turned it off I couldn't turn it on again. Root checker does say that I have root, and other root apps e.g. adaway, xprivacy still work.
Any help and suggestion is most welcome!
case-sensitive said:
I just updated to 6.0.1 myself, rooted using superSU 2.61. I too cannot delete system apps using titanium. I tried to uninstalled and reinstall the app (via playstore) but it didn't help.
I also tried to do the same via the root explorer option in ES file explorer and it didn't work. I tried to toggle the root explorer option in ES, but after I turned it off I couldn't turn it on again. Root checker does say that I have root, and other root apps e.g. adaway, xprivacy still work.
Any help and suggestion is most welcome!
Click to expand...
Click to collapse
hey guys, "system less root"
That would modify system... Just freeze the apps.
geoff5093 said:
That would modify system... Just freeze the apps.
Click to expand...
Click to collapse
Some people still want to recover the space.
With systemless root you will need to modify the system in TWRP to get titanium and ES working correctly.
It's as simple as going into TWRP and mounting the system R/W.
You then need to open the terminal in the following places:
/system/bin and execute "touch su"
/system/xbin and execute "touch su"
This will create zero byte files for SuperSu to come along and swap/link to on boot so that ES and TiBu can ask for root and get it.
They will then operate as you expect.; with the caveat that you are on your own when you start tinkering and may break something.
tech_head said:
Some people still want to recover the space.
With systemless root you will need to modify the system in TWRP to get titanium and ES working correctly.
It's as simple as going into TWRP and mounting the system R/W.
You then need to open the terminal in the following places:
/system/bin and execute "touch su"
/system/xbin and execute "touch su"
This will create zero byte files for SuperSu to come along and swap/link to on boot so that ES and TiBu can ask for root and get it.
They will then operate as you expect.; with the caveat that you are on your own when you start tinkering and may break something.
Click to expand...
Click to collapse
Pretty sure you lose Android Pay with this method though, just FYI if you care about that.
But if you are running Xposed you broke it anyway. There is a way to get it working.
You will need to remove the empty su files you just created to be able to add cards.
You will need to use a Xposed module to hide modifications to the system so that the device check comes back clean.
It's a pain, but if you want Xposed, TiBu, ES and Android Pay, that is the price.
Sent from my Nexus 6P using Tapatalk
I usually use this app:
https://play.google.com/store/apps/details?id=com.jumobile.manager.systemapp
I'm not on 6.0.1 at the moment so I can't test if it works. Anyone wanna test it out and report back?
WizeGuyDezignz said:
I usually use this app:
https://play.google.com/store/apps/details?id=com.jumobile.manager.systemapp
I'm not on 6.0.1 at the moment so I can't test if it works. Anyone wanna test it out and report back?
Click to expand...
Click to collapse
Doesn't work. Apps restore themselves.
So ive noticed on most roms that when you remove default built in root, it gives you an android is starting or optimising message on every boot. I deleted built in root so i could root with supersu and install suhide so i could play pokemon go. Well su hide wont install with built in root still intact so i had to do a full unroot first. Thats where the optimising problem on every reboot began. But i managed to solve it by copying the su file from supersu to the /su/xbin folder. After that no more problems on reboot. Thought id share in case someone else was having this same annoyance.
how to do that .... full unroot built in root
copy su file to su/xbin folder how to do this ?????
I have rooted almost every phone I've had and have always used the same rom, superuser app, etc. I recently switched from dirty unicorns 6.0 to aicp 7.0 because of an Android os problem. I have both SuperSU & magisk manager apps and binaries installed ( both came with rom for some reason and can't get rid of either, didn't mind too much) and when I open adaway it asks for superuser permissions and I grant it, then another window will pop up saying it can't find the su binary or I didn't grant it root access. I went through some other forums and tried using a terminal emulator to be able to rewrite system, But came back with saying "there is no such file or directory”. I then tried installing "mount /system ro/re (root)" from the play store, it said it was successful. So I tried adaway again and still says the same thing. Any other ideas?
Magisk has own "hosts", you don't need adaway. @as.hs
dzidexx said:
Magisk has own "hosts", you don't need adaway. @as.hs
Click to expand...
Click to collapse
I checked magisk and I see what you are saying (I think) and checked the option but it says it doesn't get rid of ads, it just supports adblocker apps, does that mean I still don't need an adblocker?
I'm using AdClear app, it does the work for me. Also we can select individual app in which we want ads blocked
https://forum.xda-developers.com/android/apps-games/app-adclear-root-version-ad-blocker-t3309011
Hi guys
I am pretty new to android, but i know a lot about pc's.
I have a OP5 and rooted it, but then i had an issue with SuperSU and uninstalled it. What i did not think, is that if i reinstall it, it has no root access, because i can not grant it.
So i tried reinstalling it with TWRP, but it did not get root access.
Does anyone know how to give it root again/reinstall it with root?
(i could reflash the os and reinstall superSU, but i dont want to set uo the phone again)
Also does anyone know the progress on nethunter for OP5?
Thanks and yours
cacciu
Cacciu said:
Hi guys
I am pretty new to android, but i know a lot about pc's.
I have a OP5 and rooted it, but then i had an issue with SuperSU and uninstalled it. What i did not think, is that if i reinstall it, it has no root access, because i can not grant it.
So i tried reinstalling it with TWRP, but it did not get root access.
Does anyone know how to give it root again/reinstall it with root?
(i could reflash the os and reinstall superSU, but i dont want to set uo the phone again)
Also does anyone know the progress on nethunter for OP5?
Thanks and yours
cacciu
Click to expand...
Click to collapse
It's been awhile since I used SuperSU so I might be fuzzy: SuperSU has two components, 1) the .zip portion installed from TWRP and 2) the APK. The zip is like "the framework/service/su" part and the APK is the app that just tracks and loads the DB with which apps or services have been granted SU access.
My question is "Which of these did you uninstall?" : OR: Did you uninstall both? Maybe only uninstalling one or the other causes an 'out of sync' condition.
Anyway: This version of SuperSU https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133 discussed in that thread has the APK in the .zip file. By definition all TWRP recoveries are rooted and can do what they want to like installing SuperSU.
What happens after you boot seems more likely to be about left-over crud from the APK / DB component, (and I'm guessing here), so if the SuperSU APK is still there, I'd clear it's data entirely, perhaps get rid of it entirely if you can and reinstall the .zip that contains all parts of SuperSU (maybe they all do now) from that link ^^. Make sure that link I gave is the one you want (systemless, etc).
TWRP should've done the heavy lifting during SuperSU install since it's already rooted. If it didn't, then keep the log from TWRP and look over it's install steps during the SuperSU install. Post it here maybe.
Thanks for the answer.
I uninstalled the apk.
I already tried to install the apk directly and also installing it from the zip, and there was either a message like "no root detected" or " root is corrupted".
I also deleted the su folder, uninstalled the apk and reinstalled the zip. But it was always the same: the apk did either say it's not rooted or did not install/show in the apps.
Probably i have to unroot and root it, or do you have any other idea?
TWRP Terminal
I found out, that there is a terminal with root access on twrp. So i searched for eu.chainfire.supersu with the find comman and use chown root:root to give each directory root access. But it still did not recognize the root. So i thought about the db you said and maybe it doesnt recognize the db.
So i tried the same with dsploit as it doesnt run without root, but it's the same.
I will try to delete all the supersu directories as well as any su directory and reinstall the zip. Or if there is an apt-get, i will try it to install it by terminal
Cacciu said:
I found out, that there is a terminal with root access on twrp. So i searched for eu.chainfire.supersu with the find comman and use chown root:root to give each directory root access. But it still did not recognize the root. So i thought about the db you said and maybe it doesnt recognize the db.
So i tried the same with dsploit as it doesnt run without root, but it's the same.
I will try to delete all the supersu directories as well as any su directory and reinstall the zip. Or if there is an apt-get, i will try it to install it by terminal
Click to expand...
Click to collapse
You might be out of luck if you deleted the su directory or any other related to binary su code. I'm not sure why you couldn't do a reinstall of the original SuperSU .zip file. You've got that whole 'catch-22' thing going right now.
The only thing I'm wondering about is whether a certain amount of cleanup has to take place before you can just roll SuperSU*.zip over an old mangled version and get it to work. Do you get errors in TWRP when trying to reinstall the entire package?
---------- Post added at 02:48 PM ---------- Previous post was at 02:05 PM ----------
I downloaded this version of SuperSU (which may or may not be what you used, but you of course want the one you used): http://download.chainfire.eu/1114/SuperSU/SR1-SuperSU-v2.82-SR1-20170608224931.zip
Then I unzipped it and the installer script for not only the binary parts but the apk is here .\SR1-SuperSU-v2.82-SR1-20170608224931\META-INF\com\google\android\updater-binary. (updater-script is a dummy). It's kind of old school and is very easy to understand (the shell script that installs it).
All the files that it pushes onto the SD are easy to find and use, although you have to keep SELinux settings in mind.
It's worth taking a look at if you want to try to rebuild the wrecked version or if you want to just reapply the zip and have a better understanding of any errors it spits out.
Good luck.
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.