Having problems getting gltools to install, tried APK, flashable zip and magisk module. The magisk module says all went well, I reboot but gltools is nowhere to be seen. I am running latest beta firmware 11.2 from mi-globe, has anyone been able to use gltools with stock ROM?
Related
So I wont say I tried everything but have been reading and trying solutions and they havent worked for me. Maybe someone can point me in a different right direction. So far I clean installed 3.2.8(twice btw), I'm fastbooting into twrp 3.0.2-1, flashed supersu 2.78 SR4 and flashed xposed framework v87.
Sometimes xposed framework v87 flashes in twrp and when I open xposed installer it says xposed framework is not installed. I attempt to then unintstall and try again and sometimes it fails in twrp with this message "cp: cant create '/system/xposed.prop':Read-only file system". I attached a screenshot. I'm also running xposed installer 3.1.1, also tried 3.0.1 by dvdandroid. Any suggestions?
Have you tried Magisk and Systemless Xposed?
mznk said:
Have you tried Magisk and Systemless Xposed?
Click to expand...
Click to collapse
Are you asking if I tried it in the past on my onplus3? I didnt see anyone trying it now with 3.2.8 so I didnt think of it.
SysAdmNj said:
Are you asking if I tried it in the past on my onplus3? I didnt see anyone trying it now with 3.2.8 so I didnt think of it.
Click to expand...
Click to collapse
I'm using it on 3.2.8 currently and all works well so far.
Here's how I did it: Clean flashed 3.2.8 using sideload with official recovery, then booted twrp-3.0.2-1 (from twrp.me), flashed Magisk v9 and flashed the phh-superuser. After booting into android, installed phh's SuperUser from Playstore, and installed Magisk Manager, then installed Xposed systemless arm64 sdk23 using the inbuilt downloader (or use the zip on the thread).
mznk said:
I'm using it on 3.2.8 currently and all works well so far.
Here's how I did it: Clean flashed 3.2.8 using sideload with official recovery, then booted twrp-3.0.2-1 (from twrp.me), flashed Magisk v9 and flashed the phh-superuser. After booting into android, installed phh's SuperUser from Playstore, and installed Magisk Manager, then installed Xposed systemless arm64 sdk23 using the inbuilt downloader (or use the zip on the thread).
Click to expand...
Click to collapse
Thanks it all worked and went green except when I tried to download the systeless arm64 sdk23 from within magisk manager. I ended using a test1 version and it went through. Now I wasnt even planning on using magisk but how are you using magisk? When I used it before it was for android pay but I thought that all broke.
Installing xposed breaks SafetyNet anyways and I have no use of Android pay or Pokemon Go etc.
But, with magisk I can install and mod system files without making changes in the system partition like dpi, Viper, SystemUI mods etc. I really like it for the ease of that.
I have installed Xposed on 3.2.8 with a success from the beginning. Steps I've taken:
1. Dirty flashing full zip OOS 3.2.8.
2. Flashing systemless SuperSU from Chainfire (you have to:
Code:
echo SYSTEMLESS=true >> /data/.supersu
for systemless).
3. Flashing Xposed v87-test version, which now disappeared from dl-xda.xposed.info/framework/sdk23/arm64/
4. Flashing ElementalX 0.28.
I was upgrading from 3.2.6.
mznk said:
I'm using it on 3.2.8 currently and all works well so far.
Here's how I did it: Clean flashed 3.2.8 using sideload with official recovery, then booted twrp-3.0.2-1 (from twrp.me), flashed Magisk v9 and flashed the phh-superuser. After booting into android, installed phh's SuperUser from Playstore, and installed Magisk Manager, then installed Xposed systemless arm64 sdk23 using the inbuilt downloader (or use the zip on the thread).
Click to expand...
Click to collapse
OxygenOS 3.2.7 with v87.1 Magisk version installed. Got stuck at boot animation when dirty flashing to oos 3.2.8. Any ideas? Is there compatibility problem with xposed modules?
I would use a newer recovery, twrp-3.0.2-23-oneplus3 is the latest and I've had zero issues with it. I uploaded it to drive vs searching for it. Next, as stated, install Xposed via the app, version 3.0.1 by dvdandroid is what I'm using and after selecting arm64 api23 , granting root, it installs, reboot and done.
I have been trying to install Magisk and cannot get it to install properly. I am currently running stock/rooted PJ1 rom. I tried unrooting, fresh install, Magisk Manager app from play store install. It always errors out. Does anyone have any advice? Thanks!
What is the error?
bpditty said:
I have been trying to install Magisk and cannot get it to install properly. I am currently running stock/rooted PJ1 rom. I tried unrooting, fresh install, Magisk Manager app from play store install. It always errors out. Does anyone have any advice? Thanks!
Click to expand...
Click to collapse
Did you do in this exact order?
1. Flash Rom.
2. Open SuperSU. And click Full uninstall!
3. Reboot into recovery and install magisk v12 zip.
4. Reboot and install magisk manager!
5. All done!
Here is magisk files: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Download from direct links. The zip and app.
Hello xda community.
I got some knowledge about flashing stuff on my oneplus 3. But Since I use Android oreo beta 29, 30, or stable 5.0 OOS version even when I use the aroma installer from Freedom OS. Magisk doesn't install propobly. .
Im using latest Twrp from Bluespark 3.2.1 -X
I can flash most off the magisk versions 15.0 - 15.1 - 14.6 without bootloops. I tried alot off them but when I boot the phone magisk is not installed.(there is no Magisk app)
When I install the magisk apk. the magisk is also telling me magisk is not installed.
On beta 29 SuperSU was working didn't try it yet on beta 30 but I really want to use Magisk.
I'm reading the forums here also on the OP community but seems like I'm the only one with this problem.
uninstall magisk app from the rom, flash rom again and then flash magisk 15.3... works fine
theduke7 said:
uninstall magisk app from the rom, flash rom again and then flash magisk 15.3... works fine
Click to expand...
Click to collapse
Thanks for your reply.
I did a clean flash Beta 29 also on 30.
15.3 is not working to for me....
Ghost123NL said:
Thanks for your reply.
I did a clean flash Beta 29 also on 30.
15.3 is not working to for me....
Click to expand...
Click to collapse
flash the rom then reboot to recovery then flash magisk... don't flash immediately after the rom ....
theduke7 said:
flash the rom then reboot to recovery then flash magisk... don't flash immediately after the rom ....
Click to expand...
Click to collapse
Also not working.
same steps with supersu is working only
Ghost123NL said:
Also not working.
same steps with supersu is working only
Click to expand...
Click to collapse
maybe the only way to make sure is to wipe everything , did you try with custom kernel?
try to flash rom reboot to recovery, then derp kernel (tested and works on latest beta) , then flash magisk... that worked for me at 1st try.
Flash magisk 14.0 and boot see magical working and then update magisk15.3 via magisk manager application.
Use OOS debloater from the themes and apps section to remove some apps from the system. Then reinstall magisk. Problem solved. We have a lot less space left in the system partition and that's the reason magisk is silently failing to install.
Facing same issue
Hi,
I have a 'weird' problem:
I installed Magisk some time ago on my Redmi Note 5 Pro (Global).
Now I'm on version 19.3 (updated today).
I also installed two Magisk modules in order to unlock Camera2API and some stuff for the camera (nhappyman Camera patch).
I recently received and installed the latest global stable build, Android 8.1.
I reinstalled TWRP recovery in order to install also the Magisk zip.
BUT now I don't understand why I don't have Camera2API.
I see the modules activated;
I also see that Magisk is activated and it's on the latest version;
I disabled and enabled again the module but nothing changes.
The only thing I can do in order to make Camera2API work is:
Reboot into TWRP;
Install Magisk, AGAIN;
Wipe Dalvik and cache;
Reboot.
It will work until next reboot.
If I reboot the phone, Magisk modules will not work at all.
The problem is that Magisk modules seems working on Magisk but if I try to open GCam keeps crashing.
So, what can I do? Can you help me please?
P.S.: It was already unlocked when I bought it.
Thanks
-Alex
Download build prop editor and search for
persist.vendor.camera.HAL3.enabled
And change to 1
rounakr94 said:
Download build prop editor and search for
persist.vendor.camera.HAL3.enabled
And change to 1
Click to expand...
Click to collapse
I updated build.prop adding this line.
It works.
Thanks
-Alex
I own a firetv stick 2nd gen (tank). I have unlocked the device and installed the Prerooted rom which requires you to install magisk after you install the rom
I just cant figure out which magisk version to use. I have tested 25.2, 25.1, 24.3 but in all these versions the manager just crashing once i press any button on my remote (It doesnt open, it only shows the logo)
I tested 20.03 which luckily works and i had not got time to test any other versions, but i thought i'd ask here if anyone know why this is happening or what magisk version is suggested
Lenicyl said:
i thought i'd ask here if anyone know why this is happening or what magisk version is suggested
Click to expand...
Click to collapse
It sounds like a signature mismatch. You can't mix and match official and unofficial Magisk versions.
If you try to install the official Magisk Manager, with a custom Magisk build, you will see what you are experiencing. Magisk Manager will close and the icon will revert to just Magisk text.
With Magisk 22+ the zip and manager are the same file. Whatever zip you used to patch your device, rename it to magisk.apk and install it as an app in FireOS.
I think a custom Magisk build is used with a couple of the FireSticks to protect the rooting method.
Finnzz said:
It sounds like a signature mismatch. You can't mix and match official and unofficial Magisk versions.
If you try to install the official Magisk Manager, with a custom Magisk build, you will see what you are experiencing. Magisk Manager will close and the icon will revert to just Magisk text.
With Magisk 22+ the zip and manager are the same file. Whatever zip you used to patch your device, rename it to magisk.apk and install it as an app in FireOS.
I think a custom Magisk build is used with a couple of the FireSticks to protect the rooting method.
Click to expand...
Click to collapse
hey! For all the versions i installed (which is from the original magisk repo itself), i used the same apk to install both the manager and Magisk itself, so i dont think its signature
mismatch.
I was not aware of any custom magisk builds for firetv until i read your reply. I found this but this has the same issue as normal magisk, the issue being the Manager not working.
Also i just tested Magisk v22 and it works !!
Im thinking ill just stay on this version and i think ill be fine for now ?