Related
Systemless Dolby Atmos r6.5
Requirements:
Magisk 11+
Remove any other audio modules you have installed
Using Magisk's inbuilt superuser for root access (no phh/supersu)
Instructions:
Just flash Module zip through Magisk Manager or TWRP.
To use ViPER4Android, install APK from here.
Download from Magisk manager
Port of Dolby Atmos r6.5 by worstenbrood on Magisk.
Github
Credits: worstenbrood (for original Dolby Atmos port) & topjohnwu (for V4A module and Magisk)
Can it work simultaneously with Viper?
A_Random_Guy said:
Can it work simultaneously with Viper?
Click to expand...
Click to collapse
I don't think so. You can try. Most probably I'll have to create a separate zip with Dolby+Viper.
A_Random_Guy said:
Can it work simultaneously with Viper?
Click to expand...
Click to collapse
Same problems on LeeDroid.
Wysłane z mojego HTC 10 przy użyciu Tapatalka
Tried this module on my Nexus 6P, stock ROM (7.1.1) with Magisk 11.1. went into bootloop.
Thanks so much!!!! I had to give up on Atmos a while back when SafetyNet ramped up its security and I was hoping a magisk module would show up eventually.
How about the Collective Dolby ATMOS, https://forum.xda-developers.com/android/software/soundmod-axon-7-dolby-atmos-t3412342/, which are newer versions. Did you ever tried on that? I adapted these Collective Dolby ATMOS into Magisk modules since v7, but they failed on v10 and v11. Any ideas?
https://github.com/laggardkernel/magisk-module-template/tree/leeco_lemax_2
Update: sorry, my fault. The problem is that I used multirom to test these modules but Magisk v10 and v11 aren't compatible with multirom anymore.
@Yash98 r6.5 Magisk module causes a black screen immediately after stock moto splash screen.
My steps:
1. Download and install r6.5 through Magisk Manager.
2. "Installation successful" dialogue
3. Tap reboot
4. Device starts to reboot but screen goes black after stock moto splash screen
I had to boot into recovery and delete the mod for my phone to boot up.
My current device info is in my signature
JERW28 said:
@Yash98 r6.5 Magisk module causes a black screen immediately after stock moto splash screen.
My steps:
1. Download and install r6.5 through Magisk Manager.
2. "Installation successful" dialogue
3. Tap reboot
4. Device starts to reboot but screen goes black after stock moto splash screen
I had to boot into recovery and delete the mod for my phone to boot up.
My current device info is in my signature
Click to expand...
Click to collapse
Where do you find the mod to delete? I have the same problem but I don't find what I have to delete (Nexus 5X).
Thanks.
@kartikb @Plonkyplonk @boutsism
The module is called Mount-Magisk.zip. I found it here in the first post: https://forum.xda-developers.com/apps/magisk/collection-magisk-modules-t3445257
1. Flash in twrp
2. Using twrp file manager, go to /magisk
3. Choose mod and tap delete
The phone should reboot normally
laggardkernel said:
How about the Collective Dolby ATMOS, https://forum.xda-developers.com/android/software/soundmod-axon-7-dolby-atmos-t3412342/, which are newer versions. Did you ever tried on that? I adapted these Collective Dolby ATMOS into Magisk modules since v7, but they failed on v10 and v11. Any ideas?
https://github.com/laggardkernel/magisk-module-template/tree/leeco_lemax_2
Click to expand...
Click to collapse
Never tried magiskifying that as they never worked on my devices.
JERW28 said:
@Yash98 r6.5 Magisk module causes a black screen immediately after stock moto splash screen.
My steps:
1. Download and install r6.5 through Magisk Manager.
2. "Installation successful" dialogue
3. Tap reboot
4. Device starts to reboot but screen goes black after stock moto splash screen
I had to boot into recovery and delete the mod for my phone to boot up.
My current device info is in my signature
Click to expand...
Click to collapse
I'll need a logcat of this @boutsism
I see that the original post was updated this morning, does that mean it works correctly with Magisk 11.1 now, without causing bootloops?
Jinded said:
I see that the original post was updated this morning, does that mean it works correctly with Magisk 11.1 now, without causing bootloops?
Click to expand...
Click to collapse
Nope I'm getting a bootloop on magisk v11.1, Nexus 6, Stock Android 6.0.1.
Working fine on Nexus 6, Pure Nexus 7.1.1_r13 (01/21), Magisk v11.1 and MagiskSU.
Why is the APK supposed to use just the old version of the module's zip file? Are we supposed to extract it?
Just a heads up, I'm using on a HTC 10 and it's all good.
PartyPlease said:
Nope I'm getting a bootloop on magisk v11.1, Nexus 6, Stock Android 6.0.1.
Click to expand...
Click to collapse
Do you have any other audio modules installed?
Yash98 said:
Do you have any other audio modules installed?
Click to expand...
Click to collapse
Nope, fully stock everything.
Lost root after flash this module. I used magisk 11.1 and supersu 2.79.
Hi There,
I met some issues when I tried to flash the Magisk zip to my MIX2S.
Phone MIX 2S
OS:MIUI 10.3 by xiaomi.eu 9.2.15
Recovery:TWRP
Situation:
Part 1, at the beginning, I flashed the xiaomi.eu rom to my MIX 2S, and then flashed magisk zip file, everything works well except sometime the saftynet check will fail. After I check the post of saftypatcher , I changed to ianmacd mod. Everything seems fine until then. I need to re-flash the magisk official zip every time after I update my phone, and than update magisk to ianmacd mod in magisk manager.
Part 2,
Today I updated my rom to MIUI 10.3 by xiaomi.eu 9.2.22, I then re-flash the official magisk zip as usual, and then updated to ianmacd mod in magisk manager. I re-boot the phone, then it reboot to recovery when I tried to input my pin. Reboot again, still went to the recovery. So I use ianmacd uninstaller to uninstall the magisk, and tried to flash the official zip. The phone booted into the system, but when I open the magisk manger, it shows that mangisk is not installed. I reflashed again, still the same issue.
I uninstalled the manger, tried to install the offical manger apk file, told the app was not installed.
I downgrade my system to MIUI 10.3 by xiaomi.eu 9.2.15, reflash the offical 18.1 zip file, reboot, no magisk manger on my phone, tried to install the apk file, still failed.
I boot into the recovery to uninstall and install again, still no manger in the system. Now I'm totally lost.
Part 3, some of my app tells me that my phone is rooted, so I guess the magisk is in somewhere of my system?
Attached is the recovery log.
Thank you in advance. Sorry for my English.
You've been mixing Managers with different signatures (the official with unofficial)...
Try this:
https://www.didgeridoohan.com/magisk/Magisk#hn_Cant_install_the_Magisk_Manager
Didgeridoohan said:
You've been mixing Managers with different signatures (the official with unofficial)...
Try this:
https://www.didgeridoohan.com/magisk/Magisk#hn_Cant_install_the_Magisk_Manager
Click to expand...
Click to collapse
Thank you very much for the help. It fixed my issue.
Now I need to investigate the "boot to recovery" issue.
Hello guys,
I made an update in TWRP and installed Havoc 2.4 to try it. After 1 hour I restored my backup and changed back to MIUI. I couldn't log in, so I cleaned the keyfiles to set a new pin.
I reflashed new Beta (25.4 MIUI - Xiaomi.eu) ROM and Magisk but root does not apply on my device... What is wrong? Seems that it's not possible to root anymore... Its does not give me any fails when installing the magisk 18.1 zip in TWRP...
thanks in advance
Have you tried a simple reboot? Usually it takes a reboot more to apply.
no it's not that. now its always booting into twrp when I try to flash magisk
makmak001 said:
no it's not that. now its always booting into twrp when I try to flash magisk
Click to expand...
Click to collapse
Extract the boot.image from the rom and place it in your downloads folder.
Now with Magisk Manager , download and install Magisk to that boot image
Magisk will write root to the boot.image file and then will automatically flash the the updated boot image, and restart to system >>> Issue resolved.
I fixed it by wiping data... now its working
tsongming said:
Extract the boot.image from the rom and place it in your downloads folder.
Now with Magisk Manager , download and install Magisk to that boot image
Magisk will write root to the boot.image file and then will automatically flash the the updated boot image, and restart to system >>> Issue resolved.
Click to expand...
Click to collapse
I have the same problem with magisk, after weekly update and after magisk installed, boot only TWRP. I tried with18.1 version but will not recognise. Boot image and Magisk 19.1 are in downloads but no success. Anyway, with this weekly update all people have loosen magisk, I have read in Xiaomi forum.
slave2007 said:
I have the same problem with magisk, after weekly update and after magisk installed, boot only TWRP. I tried with18.1 version but will not recognise. Boot image and Magisk 19.1 are in downloads but no success. Anyway, with this weekly update all people have loosen magisk, I have read in Xiaomi forum.
Click to expand...
Click to collapse
Nope, no issues on my Mi 8. Here is the trick. When updating do not flash Magisk until you out have booted into the system and ran updates and deleted cache and trash, then reboot to recovery and flash Magisk.
If the method that I described before in the previous post doesn't work, then unpack the boot image from the update and flash it to boot in recovery then flash Magisk Canary debug.
I have been doing this for every weekly update using the beta ROM.
I had an issue just once that was resolved by flashing SuperSu, booting to system confirming root, then reboot to recovery and removing Su, flashing the boot and Magisk Canary
Sent from my Xiaomi MI 8 using XDA Labs
slave2007 said:
I have the same problem with magisk, after weekly update and after magisk installed, boot only TWRP. I tried with18.1 version but will not recognise. Boot image and Magisk 19.1 are in downloads but no success. Anyway, with this weekly update all people have loosen magisk, I have read in Xiaomi forum.
Click to expand...
Click to collapse
Here you can see that I have root and latest update
Sent from my Xiaomi MI 8 using XDA Labs
tsongming said:
Nope, no issues on my Mi 8. Here is the trick. When updating do not flash Magisk until you out have booted into the system and ran updates and deleted cache and trash, then reboot to recovery and flash Magisk.
If the method that I described before in the previous post doesn't work, then unpack the boot image from the update and flash it to boot in recovery then flash Magisk Canary debug.
I have been doing this for every weekly update using the beta ROM.
I had an issue just once that was resolved by flashing SuperSu, booting to system confirming root, then reboot to recovery and removing Su, flashing the boot and Magisk Canary
Click to expand...
Click to collapse
Man has found the guilty in Xiaomi.eu/community.
It is not Magisk, but Viper 4.2. I have flashed Magisk, after reboot again in recovery and wanted to flash version 4.1. It was uninstalled, have no Viper, but Magisk is installed ?
slave2007 said:
Man has found the guilty in Xiaomi.eu/community.
It is not Magisk, but Viper 4.2. I have flashed Magisk, after reboot again in recovery and wanted to flash version 4.1. It was uninstalled, have no Viper, but Magisk is installed ?
Click to expand...
Click to collapse
I no longer use Viper because my phone has 1 speaker and for me Ainur Sauren works pretty well for all sounds.
For listening to music I have the Pro version of Power amp which has every wanted option such as dynamic compression, dynamic EQ, convolution reverb, limiting , tag editing, visualizations etc, I bought it 5 years ago for $3. Best 3 bucks that I ever spent!
Seriously, I can't recommend Poweramp highly enough, its worth its weight in gold.
Sent from my Xiaomi MI 8 using XDA Labs
So i was minding my own business then i notice "Magisk Manager" have red dot notification on it's icon upon opening there's update for "Magisk Manager" app and "Magisk" itself... so i decided to first Install the "Magisk Manager" update and it went real smooth
but when i try to update Magisk itsaid "Magisk Manager is Dead. Love live the Magisk app" then it ask me for Method
"Select and Patch file" or "Direct Install" now at this point idk what to do. I have at least done 3x Magisk update installation already it never ask me this option also when i try download root checker on playstore itsaid im rooted i just want to update Magisk should i patch my stock boot.img again or what??
For me this has been the case all this time for Magisk updates - I get that choice, and I choose 'direct install'. This time also I chose the same - 'direct install'. It got installed and prompted me to reboot.
scarmage said:
For me this has been the case all this time for Magisk updates - I get that choice, and I choose 'direct install'. This time also I chose the same - 'direct install'. It got installed and prompted me to reboot.
Click to expand...
Click to collapse
clicking Direct Install doesn't do anything
This is what my Magisk Manager look like before i update it to v22.0
https://ibb.co/gvPzDs7
Now after i update it to Magisk Manager V22.0 i can't update Magisk
https://ibb.co/HXLCvLS
You can try going to the Magisk GitHub and download the app and install it through file manager and try updating again. I did that accidentally and had no issues installing.
dl200010 said:
You can try going to the Magisk GitHub and download the app and install it through file manager and try updating again. I did that accidentally and had no issues installing.
Click to expand...
Click to collapse
I have the app already but after they decided to merge Magisk Manager and Magisk in just one apps i can't update Magisk anymore also i have stock boot.img of my device that i have previously patched via Magisk so it's just unusual for Magisk Manager to ask me again ...
ineedroot69 said:
I have the app already but after they decided to merge Magisk Manager and Magisk in just one apps i can't update Magisk anymore also i have stock boot.img of my device that i have previously patched via Magisk so it's just unusual for Magisk Manager to ask me again ...
Click to expand...
Click to collapse
I downloaded the apk from GitHub and installed it over the updated one. I was able to do a direct update. I was just suggesting it. Couldn't hurt to try it.
dl200010 said:
I downloaded the apk from GitHub and installed it over the updated one. I was able to do a direct update. I was just suggesting it. Couldn't hurt to try it.
Click to expand...
Click to collapse
Same here. Worked on Xiaomi Note 10 Pro (Tucana) with Android 10.
Did not work on Xiaomi Mi 10 Lite 5G (Monet) with Android 11. (The phone booted into fastboot-mode, so I had to extract the original boot.img from an original ROM and flashed it via fastboot-command to get the phone back booting to system).
PrussianWolf said:
Same here. Worked on Xiaomi Note 10 Pro (Tucana) with Android 10.
Did not work on Xiaomi Mi 10 Lite 5G (Monet) with Android 11. (The phone booted into fastboot-mode, so I had to extract the original boot.img from an original ROM and flashed it via fastboot-command to get the phone back booting to system).
Click to expand...
Click to collapse
Can you tell more? How did you extract the boot.img? Did you get it from the newest Android full OTA? DId it just straight up work after flashing the new boot.img? I'm asumming it was an unpatched one, right?
PrussianWolf said:
Same here. Worked on Xiaomi Note 10 Pro (Tucana) with Android 10.
Did not work on Xiaomi Mi 10 Lite 5G (Monet) with Android 11. (The phone booted into fastboot-mode, so I had to extract the original boot.img from an original ROM and flashed it via fastboot-command to get the phone back booting to system).
Click to expand...
Click to collapse
How do I flash a ROM from bootloader? I am on Xiaomi Redmi Note 4 (mido) and have the same issue. Device won't boot into anything except fastboot. I tried flashing recovery using fastboot flash recovery <reccovery>.img but it got stuck in bootloop again.
ineedroot69 said:
This is what my Magisk Manager look like before i update it to v22.0
https://ibb.co/gvPzDs7
Now after i update it to Magisk Manager V22.0 i can't update Magisk
https://ibb.co/HXLCvLS
Click to expand...
Click to collapse
Exactly the same experience as OP here.
I am at exactly this stage as well..oneplus 6T; rooted; stock image.
Not sure what to do next?
Thanks in anticipation.
~S.O
where is the "Download zip only" option ?
VangelisGi said:
where is the "Download zip only" option ?
Click to expand...
Click to collapse
There isn't one, because there is no separate zip anymore:
https://topjohnwu.github.io/Magisk/releases/22000.html
Why?
I'm so confused.
I'm on Lineageos 17 on Oneplus 6
I used to install magisk with the zip and it went smoothly now I don't have the option anymore..
How can you do when you use OTA update?
Cygnust said:
Why?
I'm so confused.
I'm on Lineageos 17 on Oneplus 6
I used to install magisk with the zip and it went smoothly now I don't have the option anymore..
How can you do when you use OTA update?
Click to expand...
Click to collapse
It's all explained in the link posted right above your post...
Spoiler: rename the .apk to .zip.
Didgeridoohan said:
It's all explained in the link posted right above your post...
Spoiler: rename the .apk to .zip.
Click to expand...
Click to collapse
Sorry, I skipped that part and when directly to the one saying you had to patch BOOT.IMG..
Many thanks
Didgeridoohan;
I understand that the 'Manager' now has become the 'App'. I also understand to just rename the '.apk' file to '.zip' to flash from an OTA update event. I also understand that the '.apk' now with this latest release has everything you need to install Magisk.
I have had Magisk already installed like this: https://ibb.co/gvPzDs7
So, after I updated, can I ask what do I do about the problem of 'update' indicating via the Magisk Home page on the App?
I mean now I have this: https://ibb.co/HXLCvLS
Just don't worry about it?
Thank-you for your help.
sprocketoctopus said:
Didgeridoohan;
I understand that the 'Manager' now has become the 'App'. I also understand to just rename the '.apk' file to '.zip' to flash from an OTA update event. I also understand that the '.apk' now with this latest release has everything you need to install Magisk.
I have had Magisk already installed like this: https://ibb.co/gvPzDs7
So, after I updated, can I ask what do I do about the problem of 'update' indicating via the Magisk Home page on the App?
I mean now I have this: https://ibb.co/HXLCvLS
Just don't worry about it?
Thank-you for your help.
Click to expand...
Click to collapse
Magisk still consists of two parts, Magisk app and Magisk internals, they're now just distributed together.
What your screenshot shows is that you've now updated the app, but not yet the internals...
Do not update simply as the update is Device bricking.
Magisk 22.0 update killed phone will only boot into fastboot
Have never had an issue went to update to latest Magisk app, followed directions and restored it first, everything seemed fine, then went to flash Magisk itself from the app (Direct install) like always, didn't seem to do anything, checked the...
forum.xda-developers.com
I updated my magisk to version 22, and it looks ok, except for the bottom menu that disappeared, does anyone know where it went or is it a bug?
We can root in an easy way without unlocking the bootloader
I think this method works with all versions realme
Don't forget to activate OEM unlocking From Developer options
1-You must install drivers:
Realme USB Driver - Realme Firmware
From here you can download USB driver for realme mobile phones. The given USB driver is supported only for the Windows operating system
realmefirmware.com
Realme USB Driver - Google Drive
drive.google.com
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
Download SPD Flash Tool R26.21.2801 - Official SPD/Unisoc Flash Tool
Download SPD Flash Tool R26.21.2801 to Flash Stock Firmware on Spreadtrum Smartphone and Tablets.
spdflashtool.com
2-You have to unpack the ROM using SPD_Upgrade_Tool
https://www.gsmmafia.com/ Here are the ROMs
After completing the extraction, make a patch for the boot With Magisk-v24.3
You will get a rooted boot file Replace it with the old boot
In the end, flash the device and you will notice that you have the root
I am attaching an explanatory video
not the group you looking for but thanks for sharing this
gianonceu said:
not the group you looking for but thanks for sharing this
Click to expand...
Click to collapse
thanks.
gianonceu said:
not the group you looking for but thanks for sharing this
Click to expand...
Click to collapse
How can we create realme c25y group in xda
Excuse me I want to ask, will this delete all internal data?
Doly12 said:
Excuse me I want to ask, will this delete all internal data?
Click to expand...
Click to collapse
yes.
Yo, how did you flash it?
Biglet0w said:
Yo, how did you flash it?
Click to expand...
Click to collapse
spd flash tool
turn off the phone. After that, press and hold the Volume Down button and at the same time connect the phone to the PC using the USB cable. You will see that the Upgrade Download program was able to identify the phone and the flashing process will start automatically.
Hi
When I try to call the emergency numbers, I can't, it says that the credit is not enough to make the call
I rebooted and flashed according to the video you posted, but it didn't work
I changed the chip but the same problem remains
Can you give me a solution to this problem
my phone recognize sim but when call people it said cellular is not available, when i use my sim in other phone it work normal, i try flash the rom again but spd tool said error !!!GSM Cali in phone is not calibrated.Reserved[7]:0x00000000,[ID=0x2] pls help
i have rmx3269_11_A.18 and its not on gsmmafia this build number what i do please help
Can i install twrp from c25 or c25s
Hello! I would like to ask for a few questions.
1) At the time of the post, the Magisk version is v24.3. Can I use the latest Magisk v25.2?
2) I've updated my phone to A.41, will downloading A.29 still work since the latest ones aren't downloadable?
Reyproject said:
Hello! I would like to ask for a few questions.
1) At the time of the post, the Magisk version is v24.3. Can I use the latest Magisk v25.2?
2) I've updated my phone to A.41, will downloading A.29 still work since the latest ones aren't downloadable?
Click to expand...
Click to collapse
1) I don't think so.
2)Yes.
JA sunny said:
1) I don't think so.
2)Yes.
Click to expand...
Click to collapse
Successfully rooted the phone. Not updating to Magisk v25.2.
This is my second time flashing since I went into a bootloop.
The first flash, I installed Audio Compatibility Patch Magisk Module, rebooted, speakers were now always on mono, installed Audio Mod Library module, still the same. Tried uninstalling ACP by going through the install prompts when flashing and updated Magisk to v25.2 at the same time. Once I rebooted, it went to bootloop.
Flashed the whole thing again, back with root again. I'll be installing stuff one by one so I can know the cause.
Too bad there's no custom recovery. TWRP or OFRP would be nice.
We can flash recovery using Flashify right? So why hasn't anyone build a custom recovery port yet?
Reyproject said:
Successfully rooted the phone. Not updating to Magisk v25.2.
This is my second time flashing since I went into a bootloop.
The first flash, I installed Audio Compatibility Patch Magisk Module, rebooted, speakers were now always on mono, installed Audio Mod Library module, still the same. Tried uninstalling ACP by going through the install prompts when flashing and updated Magisk to v25.2 at the same time. Once I rebooted, it went to bootloop.
Flashed the whole thing again, back with root again. I'll be installing stuff one by one so I can know the cause.
Too bad there's no custom recovery. TWRP or OFRP would be nice.
We can flash recovery using Flashify right? So why hasn't anyone build a custom recovery port yet?
Click to expand...
Click to collapse
I think you need to have the bootloader unlocked to boot into custom img
elokuba said:
Can i install twrp from c25 or c25s
Click to expand...
Click to collapse
Don't
Reyproject said:
Successfully rooted the phone. Not updating to Magisk v25.2.
This is my second time flashing since I went into a bootloop.
The first flash, I installed Audio Compatibility Patch Magisk Module, rebooted, speakers were now always on mono, installed Audio Mod Library module, still the same. Tried uninstalling ACP by going through the install prompts when flashing and updated Magisk to v25.2 at the same time. Once I rebooted, it went to bootloop.
Flashed the whole thing again, back with root again. I'll be installing stuff one by one so I can know the cause.
Too bad there's no custom recovery. TWRP or OFRP would be nice.
We can flash recovery using Flashify right? So why hasn't anyone build a custom recovery port yet?
Click to expand...
Click to collapse
Can you please check if this works
File
XDA forum
JA sunny said:
Can you please check if this works
File
XDA forum
Click to expand...
Click to collapse
What does it do?
Reyproject said:
What does it do?
Click to expand...
Click to collapse
removes the black bar on the notch/punchhole side that you see on some apps and games when the phone is in landscape. I'll root my phone if this works.