Develop Bugs

Installed full 3.2.8, help with xposed?

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.

HTC One M9 Nougat Update 4.14.401.7 + Magisk v11.1

Hi,
I currently have my HTC One M9 with the following installed:
TWRP v3.0.2-0
Magisk v10.2
Magisk Manager v4.1
phh's SuperUser 2.0 [Beta 11]
And it's running: Android 6.0 (Marshmallow)
Now, I've received the OTA update notification for Android 7.0 (Nougat) - 4.14.401.7. I'm assuming that if I do the update, it will overwrite both my boot and recovery partitions, and therefore my phone will return to a stock status.
My question now is: Has anyone tried installing TWRP + Magisk v11.1 on this phone, running Android 7.0 (Nougat) - 4.14.401.7 (Stock)?? And, has it worked fine??

phen0m2016 said:
Hi,
I currently have my HTC One M9 with the following installed:
TWRP v3.0.2-0
Magisk v10.2
Magisk Manager v4.1
phh's SuperUser 2.0 [Beta 11]
And it's running: Android 6.0 (Marshmallow)
Now, I've received the OTA update notification for Android 7.0 (Nougat) - 4.14.401.7. I'm assuming that if I do the update, it will overwrite both my boot and recovery partitions, and therefore my phone will return to a stock status.
My question now is: Has anyone tried installing TWRP + Magisk v11.1 on this phone, running Android 7.0 (Nougat) - 4.14.401.7 (Stock)?? And, has it worked fine??
Click to expand...
Click to collapse
I have the developer edition (4.23.617.1) but Nougat works fine with TWRP (3.0.3-0_unofficial) and Magisk 11.1. The new MagiskSU has worked fine as a root solution and within Magisk Hide - but some users have reported that it is necessary to disable/enable Magisk Hide, or even reboot to pass a SafetyNet check. For me, disabling & re-enabling after install worked fine - and was necessary only immediately after install.

computerslayer said:
I have the developer edition (4.23.617.1) but Nougat works fine with TWRP (3.0.3-0_unofficial) and Magisk 11.1. The new MagiskSU has worked fine as a root solution and within Magisk Hide - but some users have reported that it is necessary to disable/enable Magisk Hide, or even reboot to pass a SafetyNet check. For me, disabling & re-enabling after install worked fine - and was necessary only immediately after install.
Click to expand...
Click to collapse
Hey computerslayer. Thanks for the reply!
So in order to do a clean install of the Nougat Update (4.14.401.7) + Magisk v11.1, I should do the following:
1.- Uninstall phh's SuperUser using Magisk Manager > Modules
2.- Unistall Magisk Manager using TWRP > Magisk Uninstaller
*.- (Unistalling TWRP wouldn't be necessary as the Update rewrites the Recovery Partition)
3.- Apply the Nougat Update
4.- Reinstall TWRP
5.- Reinstall Magisk
6.- Finished
Is this procedure OK??

phen0m2016 said:
Hey computerslayer. Thanks for the reply!
So in order to do a clean install of the Nougat Update (4.14.401.7) + Magisk v11.1, I should do the following:
1.- Uninstall phh's SuperUser using Magisk Manager > Modules
2.- Unistall Magisk Manager using TWRP > Magisk Uninstaller
*.- (Unistalling TWRP wouldn't be necessary as the Update rewrites the Recovery Partition)
3.- Apply the Nougat Update
4.- Reinstall TWRP
5.- Reinstall Magisk
6.- Finished
Is this procedure OK??
Click to expand...
Click to collapse
Honestly, I'm not sure. I don't know if it is possible to upgrade between Android versions via OTA with TWRP installed - I vaguely remember some limitations on OTAs and TWRP. Best to check the official TWRP thread and the readme thread to be sure.
Similarly, I'm not sure about a clean install of Magisk. I've only been using it for about a month so I'm not confident in offering advice about uninstalling - especially since giving bad advice could end up with you not passing SafetyNet because I missed some basic step. I recommend checking out the Magisk forums.
I'm sorry I can't be of more help.

can you update magisk through magisk manager

I was wondering can you update magisk through magisk manger or do you have to flash the zip over again Im not new to flashing updating but the Razer phone is so touchy and some things are different than other phones.thanks

I rooted my phone shortly after the Oreo update and have been updating magisk via magisk manager since.
I'm on magisk 19.1, manager is 7.1.2

SeriousFlash said:
I rooted my phone shortly after the Oreo update and have been updating magisk via magisk manager since.
I'm on magisk 19.1, manager is 7.1.2[/QUOTe.
Thanks for the reply works great and thank you again.
Click to expand...
Click to collapse

I may be being thick, but I can't see a way to update Magisk (not the manager) thru Magisk Manager?
Peace

That's how it looks for me. Always Magisk update on top and manager update below

I have an older version then maybe that won't allow update to Magisk ...

Magisk on T320?

It finally worked on mine (19.1).
Even it stated 4.2 may not support, I managed to:
Update to the last 2017 stock.
Install and run TWRP
Install Magisk and Magisk Manager and it shows latest version installed
That's it. I switched from SuperSU (no more development) to Magisk

Suggested Magisk Version ?

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 ?