After updating I tried to flash TWRP to install magisk, but it failed. Then I found magisk patched boot image on xda and flashed it. Root works fine but the problem is my magisk modules are not working. I removed them and then again installed them but they doesn't seem to work.
Is it just me having this problem?
What to do?
No official TWRP for Android 10 yet. Android 10 just came out and a lot of developers have yet to update their modules. I would avoid TWRP and magisk for now
Magisk 20 works fine
Just be smart and don't use modules like audio mods and stuff for now
Things like FDE are updated, Vanced works, font changers will probably work, move certificates, call recorder, etc.
Related
Hey all,
Just purchased a LG U2 and now trying to make it work in the way i want it.
All informations here seem very old, so I wanted to open an update thread, with all what is possible on th lgu2, while
I found only very outdated informations...:crying:
So far:
First I setup the watch with AW2.0, after that flashed twrp 3.1.1.0 and supersu wear 2.82
I managed to get busybox installed and wanted further add Xposed.
There my problem starts, flashing xposed didn't work out.
So right after that, I switchd to Magisk root, to try work with the modules supplied.
(Steps -> use script UnSU, after that flash boot.img again, than flash MAgisk through twrp)
But after that the same with the modules. I try to install busybox, magisk tell me its no magisk module (i've downloaded the module and pushed it on the sd through adb, while the download button isn't reachable in magisk dialogue menu)
in twrp the module tells me there is no magisk installed.
so how can we go on from here? is there a way to make it all work?
did somebody try to change dpi and download the module directly through magisk? does it work?
also if somebody could help with an updated list of sideload able full android apps?
would need an email that can handle at least two accounts directly on the watch (please not advice outlook, its working from the phone i know)
thanks to all in advance
sebj84 said:
Hey all,
Just purchased a LG U2 and now trying to make it work in the way i want it.
All informations here seem very old, so I wanted to open an update thread, with all what is possible on th lgu2, while
I found only very outdated informations...:crying:
So far:
First I setup the watch with AW2.0, after that flashed twrp 3.1.1.0 and supersu wear 2.82
I managed to get busybox installed and wanted further add Xposed.
There my problem starts, flashing xposed didn't work out.
So right after that, I switchd to Magisk root, to try work with the modules supplied.
(Steps -> use script UnSU, after that flash boot.img again, than flash MAgisk through twrp)
But after that the same with the modules. I try to install busybox, magisk tell me its no magisk module (i've downloaded the module and pushed it on the sd through adb, while the download button isn't reachable in magisk dialogue menu)
in twrp the module tells me there is no magisk installed.
so how can we go on from here? is there a way to make it all work?
did somebody try to change dpi and download the module directly through magisk? does it work?
also if somebody could help with an updated list of sideload able full android apps?
would need an email that can handle at least two accounts directly on the watch (please not advice outlook, its working from the phone i know)
thanks to all in advance
Click to expand...
Click to collapse
Ok i did a fresh flash.
i see my fault was to install busybox the first time after installing supersu.
did it this time without and mgisk works so far fine. granting access for total commander no problem.
but now another thing. i installed now busybox from the repos in magisk, he say installation successful, but the module isn't there after reboot?
anyone got the same?
sebj84 said:
Ok i did a fresh flash.
i see my fault was to install busybox the first time after installing supersu.
did it this time without and mgisk works so far fine. granting access for total commander no problem.
but now another thing. i installed now busybox from the repos in magisk, he say installation successful, but the module isn't there after reboot?
anyone got the same?
Click to expand...
Click to collapse
another try. i switched back to supersu wear 2.82, installed stericsons busybox. works.
installed xposed sdk25 via twrp, says success, but after reboot xposed installer says no active framework.
i used a systemless framework... will search for the link again.
anybody got it done this way?
So I ran into a bootloop today all of the sudden. All I did was trying to install the Youtube Vanced magisk module.
When I rebooted my phone, the Youtube Vanced app was not installed, but it showed up in the Magisk modules list.
So, I rebooted again and ran into a bootloop which forced me into wiping my phone and start from scratch.
Anyone else have problems with modules?
OxygenOS 5.1.5, stock recovery, just Magisk 16.4 installed
uniQ191 said:
So I ran into a bootloop today all of the sudden. All I did was trying to install the Youtube Vanced magisk module.
When I rebooted my phone, the Youtube Vanced app was not installed, but it showed up in the Magisk modules list.
So, I rebooted again and ran into a bootloop which forced me into wiping my phone and start from scratch.
Anyone else have problems with modules?
OxygenOS 5.1.5, stock recovery, just Magisk 16.4 installed
Click to expand...
Click to collapse
Did you bloc the update of the original YouTube app ?
I only activated VoEnabler, figured i'd wait with mods lile viper for when i have twrp and can do a backup first...
We should use this thread to make a list with mods people got working
In this case :
- YouTube vanced ( working !)
- cloudfare DNS ( working !)
- Sony music ( working !)
Stock recovery oos 5.1.5
?
Youtube vanced worked fine for me. Be sure to uninstall the YouTube app first.
I gave it another shot, this is what I did:
1. Uninstalled Youtube with System Apps uninstaller
2. Installed Youtube Vanced module
3. Reboot
No YouTube App installed -.-
Now I am afraid to delete the module or reboot the phone.
Youtube Vanced works fine for me. Installed it over the original app without any issues. Of course, update has to be blocked.
Further more:
- Ainur Auron
- Audio Modification Library
- Dolby Atmos Black ´n Cheese Edition
- Viper4Android Fx for Magisk v15
- Xposed Framework (SDK 27)
I had issues with Magisk going missing after a while, but now everything is fine.
Installed magisk modules
anthonythangaraj said:
Installed magisk modules
Click to expand...
Click to collapse
Youtube Vanced is listed in magisk for me aswell, but it's not installed within android.
I just installed the APK + MicroG and this actually worked. Pretty odd.
After two years being stuck on an unrooted phone (Huawei), I'm thrilled to have everything working on OP7 x TWRP x Magisk.
On several threads I have read suggestions of Xposed modules that could be interesting, and saw that @topjohnwu published a thread with an Xposed installer apk and Xposed module for Magisk, which sounds amazing.
My question is: on OnePlus, does this work well, or would it be asking for trouble? The last thing I want now that everything is working is to make a wrong move that gets me into boot loops.
Also, if this is confirmed to work well, I see that there are several Xposed modules in the Magisk download section.
Is it "Xposed Framework, v90-beta3 created by rovo89"? Or the Tai Chi one, or the Riru ones?
Thanks for any advice!
Use edxposed, no problems so far for me
My biggest question is with Snapchat. I've read people getting banned because of using Xposed (even if no Snapchat specific module's are used).
Can anyone confirm or deny this? I just want to use it for a couple of modules like Amplify.
Its a bad idea! Snapchat thinks you use 3rd party app... Been locked out 3 times now...
In case this can help someone else, I should let you know that trying to install the "Xposed Framework v90-beta3 by rovo89" from inside Magisk has brought me a lot of heartaches (boot loop, factory reset, still struggling to get a stable system back).
Maybe the problem is not related to that module specifically, but here is what happened. It seemed to install, but when I looked at it in the "Modules" section, every section said "unknown". So I flagged it for deletion, and on reboot the phone entered a boot loop.
I tried to uninstall the module via mm, but it didn't show. So I uninstalled Magisk via Magisk-Uninstall in TWRP. The phone booted, but when I reinstalled Magisk, the boot loop restarted.
Since then, I have done two factory resets: one via the basic TWRP "Wipe", one via OOS / Settings / System. Each time, some files from before are left on the SD card. I thought that the problem was solved, but after two hours working to set up the phone (not downloading Magisk modules, just Apps from the Play Store), I got a new boot loop. Luckily this time I had done a backup. But will be looking for a way to do a more "aggressive" factory reset.
Anyhow, maybe I installed the wrong Xposed, but thought I'd share my experience.
who ah way said:
In case this can help someone else, I should let you know that trying to install the "Xposed Framework v90-beta3 by rovo89" from inside Magisk has brought me a lot of heartaches (boot loop, factory reset, still struggling to get a stable system back).
Maybe the problem is not related to that module specifically, but here is what happened. It seemed to install, but when I looked at it in the "Modules" section, every section said "unknown". So I flagged it for deletion, and on reboot the phone entered a boot loop.
I tried to uninstall the module via mm, but it didn't show. So I uninstalled Magisk via Magisk-Uninstall in TWRP. The phone booted, but when I reinstalled Magisk, the boot loop restarted.
Since then, I have done two factory resets: one via the basic TWRP "Wipe", one via OOS / Settings / System. Each time, some files from before are left on the SD card. I thought that the problem was solved, but after two hours working to set up the phone (not downloading Magisk modules, just Apps from the Play Store), I got a new boot loop. Luckily this time I had done a backup. But will be looking for a way to do a more "aggressive" factory reset.
Anyhow, maybe I installed the wrong Xposed, but thought I'd share my experience.
Click to expand...
Click to collapse
That isn't edexposed and isn't supported on pie
Arden144 said:
That isn't edexposed and isn't supported on pie
Click to expand...
Click to collapse
Thank you!
Will try edexposed on the next install, after backing up.
Ha, looking in Magisk / Downloads / Search / Xposed, I see two versions of EdXposed:
- Riru - EdXposed v0.4.5.1_beta(4463) (SandHook)
- Riru - EdXposed v0.4.5.1_beta(4463) (YAHFA)
Which one for OP7: SandHook, or YAHFA?
Thanks in advance.
who ah way said:
Ha, looking in Magisk / Downloads / Search / Xposed, I see two versions of EdXposed:
- Riru - EdXposed v0.4.5.1_beta(4463) (SandHook)
- Riru - EdXposed v0.4.5.1_beta(4463) (YAHFA)
Which one for OP7: SandHook, or YAHFA?
Thanks in advance.
Click to expand...
Click to collapse
Either. I used YAHFA with no issues for what i needed. Then i tried SandHook out of curiosity and found no difference.
Asking for trouble
Thank you both.
After TWRP backup, installed edexposed which involved three steps:
- riru exexposed core module (in Magisk)
- riru edexposed module by yahfa (Magisk)
- edexposed installer app (from GitHub)
EdXposedInstaller_v2.2.4-release.apk
https://github.com/solohsu/XposedInstaller/releases
System rebooted, SafetyNet status OK in Magisk.
As far as y'all know is this list of modules known to work on OP7?
Wouldn't even know where to start… But curious.
Edit: when I went to do a new Backup, the TWRP menu was unusual (it asked new questions about modifying the system). Decided to backpedal and restore to before exposed installation.
In the end, I just don't know enough to understand what risks I'm taking. In the hands of an expert user, it's probably safe, in mine, it's asking for trouble.
Hi!
This morning I ran into some trouble while running the Android Q Open Beta rom that I've been using since release. I have downloaded and flashed the zip of the open beta with TWRP recovery and flashed Magisk afterwards. After the install was complete I booted in to Android Q and checked Magisk Manager to see if it installed correctly, which it did. I have some apps like Pokémon Go that require Magisk hide and they also worked fine for days. Until today, out of the blue Magisk Hide didn't seem to work anymore and those apps knew the devices was rooted.
I have then tried to:
1. reflash Magisk (although it was still installed)
2. reinstalled Magisk Manager
3. Reapplied Magisk Hide for those apps and rebooted
Between every step I also removed cache and data from the applications (even reinstalled), however I couldn't get the hide the root for the apps.
Anyone else encountered this? It's strange that it only failed after a few days of working on Android Q. Anyway I'm back on Android P at the moment.
Did you try updating magisk in magisk manager? I wasn't passing safety net until I did so
ConsoleHax said:
Hi!
This morning I ran into some trouble while running the Android Q Open Beta rom that I've been using since release. I have downloaded and flashed the zip of the open beta with TWRP recovery and flashed Magisk afterwards. After the install was complete I booted in to Android Q and checked Magisk Manager to see if it installed correctly, which it did. I have some apps like Pokémon Go that require Magisk hide and they also worked fine for days. Until today, out of the blue Magisk Hide didn't seem to work anymore and those apps knew the devices was rooted.
I have then tried to:
1. reflash Magisk (although it was still installed)
2. reinstalled Magisk Manager
3. Reapplied Magisk Hide for those apps and rebooted
Between every step I also removed cache and data from the applications (even reinstalled), however I couldn't get the hide the root for the apps.
Anyone else encountered this? It's strange that it only failed after a few days of working on Android Q. Anyway I'm back on Android P at the moment.
Click to expand...
Click to collapse
What version of magisk did you install? Try the magisk canary (debug) build. Works like a charm.
I've recently ran into a few issues by upgrading Magisk from 25.1 to 26.1 stable. After updating Magisk and rebooting V4a's drivers are completely broken . No matter how many times I reboot and try to reinstall ,I keep getting same error. Simple fix. I went and downloaded Magisk 25.1 APK and renamed APK to zip. Go into Magisk app/modules/flash from storage and select what you just changed to zip. Flash and reboot. Now your left with 25.1 installed but Magisk manager 26.1 rename same file back to APK. Completely uninstall Magisk through apps. Click on 25.1 APK in storage and reboot. Back to vipers drivers working. This should work on last few versions of Magisk. Hope it helps someone else because Viper is a huge part of my android ecosystem streaming bt stereo to my vehicle and headphones. Downgrading magisk version in this matter did not wipe data in Magisk manager either.