Database Develop

Unable to flash anything in TWRP Or in MAGISK

Hi
In latest open beta with Magisk 15.3 , used debloater and made space in system , but on flashing anything no error is there but nothing shows in app drawer , same is happening with Magisk also . Managed to flash viper but the drivers are not getting installed showing io error while same works fine for others without manual driver installation, no idea what's wrong !!!!

Yikes. Sounds like something is glitched in there. Try wiping : system and cache ( only )and reloading the rom and then rebooting into recovery and then booting up in system.
.
If it's still glitched ( ugg ) then its wipe all ( less external data ) and factory reset and start over.
.
Um, did you make yourself a nandroid backup ?

AKHIL.cochin said:
but on flashing anything no error is there but nothing shows in app drawer.
Click to expand...
Click to collapse
What do you mean by this? Do you mean that you don't see any apps after flashing a Magisk module? Many modules don't install any apps and you either don't have to do anything to configure or run a terminal command. What modules are you talking about?
Managed to flash viper but the drivers are not getting installed showing io error while same works fine for others without manual driver installation, no idea what's wrong !!!!
Click to expand...
Click to collapse
That's a known issue with V4A on OxygenOS Oreo. Some don't experience it though, which is incredibly frustrating...

Also what version of twrp r u using

old_fart said:
Yikes. Sounds like something is glitched in there. Try wiping : system and cache ( only )and reloading the rom and then rebooting into recovery and then booting up in system.
.
If it's still glitched ( ugg ) then its wipe all ( less external data ) and factory reset and start over.
.
Um, did you make yourself a nandroid backup ?
Click to expand...
Click to collapse
did a clean flash and checked , its still there , no idea whats wrong ..

Bradl79 said:
Also what version of twrp r u using
Click to expand...
Click to collapse
twrp-3.2.1-0

Didgeridoohan said:
What do you mean by this? Do you mean that you don't see any apps after flashing a Magisk module? Many modules don't install any apps and you either don't have to do anything to configure or run a terminal command. What modules are you talking about?
That's a known issue with V4A on OxygenOS Oreo. Some don't experience it though, which is incredibly frustrating...
Click to expand...
Click to collapse
" not only magisk , have u read my post , on flashing arise magnum on twrp also gave no errors and i selected viper , dolby , dolby atmos , xperia music etc and all flashed fine but none was showing in there thats what i have mentioned i also tried many viper and dolby modules in magisk , nothing s working "

AKHIL.cochin said:
" not only magisk , have u read my post , on flashing arise magnum on twrp also gave no errors and i selected viper , dolby , dolby atmos , xperia music etc and all flashed fine but none was showing in there thats what i have mentioned i also tried many viper and dolby modules in magisk , nothing s working "
Click to expand...
Click to collapse
Yes, I did read your post, but it was lacking in detail so I needed to ask some clarifying questions. Unfortunately, your answer is also somewhat lacking in detail...
But, I'm guessing you're trying to install some audio mods. V4A isn't working properly on OOS Oreo for the OP3T. A few users have it running fine, but it seems like those are a minority.
There are not that many Dolby mods that work on Oreo yet, so you might have to look around a bit to find one that does. There'll most likely be some more readily available soon though.

Didgeridoohan said:
Yes, I did read your post, but it was lacking in detail so I needed to ask some clarifying questions. Unfortunately, your answer is also somewhat lacking in detail...
But, I'm guessing you're trying to install some audio mods. V4A isn't working properly on OOS Oreo for the OP3T. A few users have it running fine, but it seems like those are a minority.
There are not that many Dolby mods that work on Oreo yet, so you might have to look around a bit to find one that does. There'll most likely be some more readily available soon though.
Click to expand...
Click to collapse
THE FRUSTRATING THING S ITS WORKING FOR ALL THE OTHERS WITHOUT ANY ISSUES IN SAME ROM KERNEL COMBO

AKHIL.cochin said:
THE FRUSTRATING THING S ITS WORKING FOR ALL THE OTHERS WITHOUT ANY ISSUES IN SAME ROM KERNEL COMBO
Click to expand...
Click to collapse
Yes, it's frustrating, but there's no need to shout. And it does NOT work for everyone else. I haven't had an audio mod working properly on my OP3T since updating to OOS 5+...
It works for some, but not for others. You could try the OOS beta. It seems like some have better luck with that.
Either you try to help, if possible, or you change to a working ROM combo, or you wait until someone finds a fix.

I had a problem that some modules wouldn't activate (they install successfully, but after reboot I would still see "module will be updated at next reboot"). As I didn't have time and will to debug this, I reverted to OOS 4.5.1.

Viper4Android Pie Compatible???

As the title states ...v4a is it compatible with pie? Im rooted running a custom rom rooted with magisk. Installed v4a thru magisk manager it installs but i get the install driver /re-install driver message everytime. Is it an workaround to get it working?

recepo1 said:
As the title states ...v4a is it compatible with pie? Im rooted running a custom rom rooted with magisk. Installed v4a thru magisk manager it installs but i get the install driver /re-install driver message everytime. Is it an workaround to get it working?
Click to expand...
Click to collapse
working fine here. maybe a root/magisk issue.

bober10113 said:
working fine here. maybe a root/magisk issue.
Click to expand...
Click to collapse
What rom are you on and which version of magisk are you running?

recepo1 said:
What rom are you on and which version of magisk are you running?
Click to expand...
Click to collapse
infinity rom.
magisk v18 and also newer test canary builds.
but prety sure its an issue where you don't wait 3 minutes after rebooting before doing actions that require root.
and not sure to which extent you tried to make magisk work with various files and mods but maybe you should just factory wipe and try and get magisk working before anything else. also mayke sure busybox is installed. and dont forget that 3 minute rule after a reboot.

bober10113 said:
infinity rom.
magisk v18 and also newer test canary builds.
but prety sure its an issue where you don't wait 3 minutes after rebooting before doing actions that require root.
and not sure to which extent you tried to make magisk work with various files and mods but maybe you should just factory wipe and try and get magisk working before anything else. also mayke sure busybox is installed. and dont forget that 3 minute rule after a reboot.
Click to expand...
Click to collapse
Thanks im sure it maybe an magisk issue im running 17.3 because i kept losing root on v18. I acquire root with v4a but it freezes and then keeps telling me to reinstall driver after reboot. I will try the 3 minute rule though..thank you. You installed v4a directly thru magisk or flashed a different version?

recepo1 said:
Thanks im sure it maybe an magisk issue im running 17.3 because i kept losing root on v18. I acquire root with v4a but it freezes and then keeps telling me to reinstall driver after reboot. I will try the 3 minute rule though..thank you. You installed v4a directly thru magisk or flashed a different version?
Click to expand...
Click to collapse
v3.3 on magisk dated of jan. 16th.
use aroma option. it will reboot on its own from magisk console and the just follow the automated steps in recovery

bober10113 said:
v3.3 on magisk dated of jan. 16th.
use aroma option. it will reboot on its own from magisk console and the just follow the automated steps in recovery
Click to expand...
Click to collapse
Thank you appreciate your help i will give it a try

I have tried everything for hours to get viper4android to work with no avail until now. Go to the xda download page and select the beta version. Boom. It works. I know you might have long forgot this or already figured it out but I had to share

old legacy magisk module has been working for months and months.

Modules not working, can't return to old version, wipe needed on Galaxy S8 / Nougat

Hi,
I was running stock ROM with stock recovery plus Magisk v16 and MagiskManager v5.9.1 on my Galaxy S8 and Nougat. As far as I remember I did install MagiskManager using adb, pushed, patched and pulled the boot.img, flashed it using Heimdall. Both apk and patched_boot.img are available on my hard disk...
I then updated MagiskManager using the in app update. Afterwards I used the "direct install" to update Magisk. That took me to 20.4 / 8.0.2. I don't remember if it asked to install the runtime.
I installed modules busybox, sqlite3 and movecertificates, but with no effect (e.g. there is no /system/bin/sqlite3, no nc in my path, user certs remain user certs). I also can't find any indication in MagiskManager that modules are installed.
I didn't have time to figure out what's wrong and tried to revert back to my old versions.
That's what I did: Full uninstall from MagiskManager 8.0.2. Reboot without Magisk, adb push MagiskManager-v5.9.1.apk. Flash my old patched_boot with Magisk v16 using Heimdall. But unfortunately that gives me Magisk Manager stuck on the splash sceen. No applet can get root access, e.g. su on adb shell blocks (needs ctrl+c). Ok, uninstalled MM.
I installed the stock boot img in the intention to load MM 8.0.2 before I flash M 20.4. That didn't accept my pattern for the "your device is encrypted" screen. Well... I flashed M 20.4 patched boot.img again. After first try it shows an integrity issue and offers to wipe the phone.
* Anyway to go from here besides wipe?
* What residuals might be blocking when returning to the old versions?
* Why are modules not working on current version?
Thank you

urbancubb said:
* Why are modules not working on current version?
Click to expand...
Click to collapse
Are they current module zips, or ones that you had laying around from before updating? The modules might be using outdated installation scripts (that's my prime suspect at least).
* What residuals might be blocking when returning to the old versions?
Click to expand...
Click to collapse
Magisk v16 is soooo old. It's gonna be almost impossible to give any kind of help with that. Better to update to a current Magisk release.
* Anyway to go from here besides wipe?
Click to expand...
Click to collapse
I have no idea, you'd wan't someone who knows Samsung for that. Your device's forum might be a good place to start.

Didgeridoohan said:
Are they current module zips, or ones that you had laying around from before updating? The modules might be using outdated installation scripts (that's my prime suspect at least).
Click to expand...
Click to collapse
I installed them from within Magisk Manager from the online repo.
I noticed that this might be the case, but as there was updates this year I think on at least two of them and none worked, I think its a general problem and not caused by the module itself. Any module I could use to test wich works for sure?
Didgeridoohan said:
Magisk v16 is soooo old. It's gonna be almost impossible to give any kind of help with that. Better to update to a current Magisk release.
Click to expand...
Click to collapse
Which didn't work... We'll see.
Didgeridoohan said:
I have no idea, you'd wan't someone who knows Samsung for that. Your device's forum might be a good place to start.
Click to expand...
Click to collapse
Good hint, I started a new thread.
Thank you!

For the modules issue, the only way to know for sure what happened is to look at the install logs and the Magisk log for the following reboot.
So if you get things up and running again, and the issue still persists, make sure to provide those.

One thing I didn't think of before: I recently tried the SafatyNet check (which failed), maybe the failed reboot was the first one after checking, I don't remember exactly.

Viper4Android on Pixel 4A 5G

Has anyone been able to get Viper4Android working an Android 11? i flashed using the April 2021 Factory Image and have tried following multiple threads and guides, but have never gotten V4A to work consistently/completely.

Viper4android Android 11??
There is viper4android for android11 or I need to wait?
forum.xda-developers.com
This is the Viper4Android I've used for 6+ months. Its the only working, plug and play version I've found for Android 11. You simply download the zip, flash in magisk -- and done. There's nothing else you need to do.
Its 100% safe. Its 100% working. So easy.
I can vouch for it... And love it!

Click on the youtube link, and the zip is in the info there. No need to watch the video. Just flash with magisk or a kernel manager... and done.

I'm on LineageOS for microG 18.1, Proton kernel 1.4, Magisk rooted and this is not working for me. Further more, it mess up with SElinux making it disabled. Fortunatelly, there is an app SElinux switch, that on every boot make it Enforcing again.

I have the 5a but there are no posts yet.....
are any of you getting V4a to work using the USB port ? I run my phone usually into a dac via the usb, but Viper's only working on my phone through the headphone jack.

That YouTube video has been removed. Any chance someone could post the .zip? TIA

Root with magisk and install the Viper plugin, works like a charm on my 4a 5G. Not much else to it.

mmarcz said:
Root with magisk and install the Viper plugin, works like a charm on my 4a 5G. Not much else to it.
Click to expand...
Click to collapse
Not as simple as that for me I'm afraid. Magisk module causes bootloop.
Had the ViperFX_Android11.zip before from that same YT vid (purple/white GUI) and it worked well.
No luck or erratic performance with other versions (black/green GUI), the one from the guy with the name that looks Thai -- Pittanddwwitt idk lol.

Are you rooted normally with magisk per the instructions in this forum? Thats all I've done. Do you have a phone from google or from a carrier?
I got mine from google. Im rooted per the normal instructions. I have magisk v2.7.2.1 and the magiskhide props config modules installed. Ive never had a bootloop with either.
Not really sure what else to try. For what its worth, I cant get viper working on a rooted pixel 3, no bootloops, but the status always says abnormal.
Danny St. Angelo said:
Not as simple as that for me I'm afraid. Magisk module causes bootloop.
Had the ViperFX_Android11.zip before from that same YT vid (purple/white GUI) and it worked well.
No luck or erratic performance with other versions (black/green GUI), the one from the guy with the name that looks Thai -- Pittanddwwitt idk lol.
Click to expand...
Click to collapse

mmarcz said:
Are you rooted normally with magisk per the instructions in this forum?
Click to expand...
Click to collapse
Yes. And updating using this thread (thank you @drdionysius).
(Thanks for the reply btw.)
mmarcz said:
Do you have a phone from google or from a carrier?
Click to expand...
Click to collapse
Bought from a 3rd party actually, sealed box, no carrier branding or firmware.
Magisk version (from Canary channel) is f822ca5b (23001) -- that doesn't look right lol... oh, and Systemless hosts module installed only.
I only lost Viper when I updated to the September factory image
<shrug> idk why </shrug->
don't think it happened with other updates.
I'm pretty sure tho that I'd be in top shape, also indebted, if someone could post ViperFX_Android11.zip since the above referenced YouTube vid is gone and, with it, the link and I can't find the same version anywhere else. Thank you very much.

I just received my used 4a 5g. Got V4A v2.7.2.1 downloaded from Magisk v23 working last night...but it was a long trial & error ordeal. First download it showed Unsupported and Abnormal. Thought maybe it needed the Audio Mod Library but that didn't work. Then I tried the Audio Compatibility Patch to no avail. I tried V4A Legacy. Mulitple installs and uninstalls of all the various modules and combinations. At this point I'm not even sure what I did, or in what order/combination, but V4A is installed and working as intended. I do NOT have any of the Audio modules installed, just V4A. Don't know why it didn't work originally, or what made it finally work after fiddling with it for about an hour, but for me, that's my story/advice. Wish I could give an exact process to follow.

Here you go

mmarcz said:
Here you go
Click to expand...
Click to collapse
Top man!
Thank you

mmarcz said:
Here you go
Click to expand...
Click to collapse
Thanks for posting this! The version I had (v2.7.2.1) didn't work as reliably as it should. Often times it wasn't "processing". I uninstalled it and installed yours. So far it seems to be working well.
BIG BONUS - your version allows to view settings for the speaker, ear-buds, & blue-tooth without actually being connected to said devices. I never liked that "feature" of the newer V4A versions.

what about android 13?

Question [issue] GrapheneOS, Magisk and June update [SOLVED]

The latest OTA update made my phone bootloop if i re-flash magisk patched init_boot image...
After I asked Stock users, it looks like it's a GrapheneOS june update + Magisk specific issue.
Do someone else also have this issue?
Phone boots normally, then reboot to recovery instead of reaching lock screen.
For now, I re-flashed panther-factory-2023061402 init_boot.

Have you tried Magisk canary version? or maybe GrapheneOS doesn't like june update and newest Magisk and you need to either go back down to stable Magisk or an older version of Magisk?
Actually, after re-reading your OP, a module might be the cause of the bootloop -- I've recently seen similar behavior from other members where device bootloops or crashes during/right-after loading & starting up -- if you were on the stock ROM I would suggest you loading up in Safe Mode to see if it is a module issue; I don't know anything about GrapheneOS so I don't know if it offers anything similar. I wonder if the adb command to remove modules at boot would work....

mhh, right, i don't have a lot of modules aside hosts, fdroid and busybox, but it may be module-related.
Until now, I did everything with TWRP, but now, well, let's say it's a little more difficult =)
... safe mode works with GrapheneOS, good =)
re-enabling modules one by one until i find the culprit.
... and the failing module was... Magisk built-in Busybox 1.0.5 \o/

Albirew said:
mhh, right, i don't have a lot of modules aside hosts, fdroid and busybox, but it may be module-related.
Until now, I did everything with TWRP, but now, well, let's say it's a little more difficult =)
... safe mode works with GrapheneOS, good =)
re-enabling modules one by one until i find the culprit.
... and the failing module was... Magisk built-in Busybox 1.0.5 \o/
Click to expand...
Click to collapse
knew it....
glad I helped get you there!