Yesterday I got to know the latest Android 10 firmware for my SM-A9080, A9080ZCU2BTCA, and flashed it.
And surprisingly, I managed to get it rooted with Magisk by patching the boot.img, since there is no TWRP for the SM-A9080.
However, one new issue occurs: I get the phone paired via bluetooth to other devices, but after the phone is rebooted, those paired devices disappear from the list.
I searched for two methods, replacing libsecure_storage.so directly or flashing a Magisk module. But unluckily, neither worked.
Thus, is there any more solution? Thanks in advance!
jasonc417 said:
Yesterday I got to know the latest Android 10 firmware for my SM-A9080, A9080ZCU2BTCA, and flashed it.
And surprisingly, I managed to get it rooted with Magisk by patching the boot.img, since there is no TWRP for the SM-A9080.
However, one new issue occurs: I get the phone paired via bluetooth to other devices, but after the phone is rebooted, those paired devices disappear from the list.
I searched for two methods, replacing libsecure_storage.so directly or flashing a Magisk module. But unluckily, neither worked.
Thus, is there any more solution? Thanks in advance!
Click to expand...
Click to collapse
One very simple solution....only one that works.
Flash back stock rom.. and try process again. If it doesnt work....then obviously rooting or magisk is corrupting some partition. So only way to fix this is stay stock...
jasonc417 said:
Yesterday I got to know the latest Android 10 firmware for my SM-A9080, A9080ZCU2BTCA, and flashed it.
And surprisingly, I managed to get it rooted with Magisk by patching the boot.img, since there is no TWRP for the SM-A9080.
However, one new issue occurs: I get the phone paired via bluetooth to other devices, but after the phone is rebooted, those paired devices disappear from the list.
I searched for two methods, replacing libsecure_storage.so directly or flashing a Magisk module. But unluckily, neither worked.
Thus, is there any more solution? Thanks in advance!
Click to expand...
Click to collapse
Look up Bluetooth Library Patcher on the Magisk Downloads (or use this link). I use it on Android 10 and never had any issues with my bluetooth devices being forgotten.
Thanks for your advice.
I found the module in Magisk and it does work!
yomama163 said:
Look up Bluetooth Library Patcher on the Magisk Downloads (or use this link). I use it on Android 10 and never had any issues with my bluetooth devices being forgotten.
Click to expand...
Click to collapse
I'm using a Samsung Galaxy Note 10 Plus (SM-N975) running One UI 3.1 on Android 11.
I rooted my phone with Magisk and experienced this same problem.
After installing the Magisk Module 'Bluetooth Library Patcher' by 3arthur6 and that solved the problem.
Related
Hi all when flashing any version above v12 on to my phone it gets stuck at the boot logo I am using Lineageos latest version of typing this but if I use v12 its fine but dont pass the CTS and stuff
I have tried to fully uninstall the magisk and reinstall it on the newer version and nothing can anyone help please
I have also fully reinstalled the ROM with formatting everything and it still don't boot
Your bootloader must be unlocked to flash LOS on the S5, right? I have the same setup as you and running no issues at all. Are you flashing the zip after flashing the ROM?
ldeveraux said:
Your bootloader must be unlocked to flash LOS on the S5, right? I have the same setup as you and running no issues at all. Are you flashing the zip after flashing the ROM?
Click to expand...
Click to collapse
The Samsung galaxy S5 plus (g901F) is different from Samsung galaxy S5 (g900) si magisk work on second one but on the first one magisk v13 never worked and it's confirmed at the lineage OS side. I'm on this case too so I confirm the issue.
Jet45 said:
The Samsung galaxy S5 plus (g901F) is different from Samsung galaxy S5 (g900) si magisk work on second one but on thé first one magisk v13 never worked and it's confirmed at the lineage OS side. I'm on this case too so I confirm the issue.
Click to expand...
Click to collapse
So glad someone eles has the same problem and I'm not on my own it just seems weird how the v12 works it don't pass but all loads fine. Let hope they find why and fix it.
Flash your stock bootloader then try flashing magisk
I'm using the stock bootload not changed my bootloader
If it was the bootloader why foes v12 work fine?
No request to have any information about this ?
What do the devs need (other than time of course) to try a troubleshooting ?
How to get this logs/boot image and logs ?
Managed to get it working, but did a clean install and lost it, first time I got it working I was at 19-07-2017 build with magisk manager 5.1.1 and magisk 12, with magisk folder mount and magisk ext SD access modules installed, then upgraded to 26-07-2017 build through official update from settings, and after installation I rebooted the phone into recovery and installed magisk 13.3 (as you know when updating we lose magisk root) and it worked.
Then did a clean install of 26-07 build (thinking it will work) but nope.
Recycool said:
Managed to get it working, but did a clean install and lost it, first time I got it working I was at 19-07-2017 build with magisk manager 5.1.1 and magisk 12, with magisk folder mount and magisk ext SD access modules installed, then upgraded to 26-07-2017 build through official update from settings, and after installation I rebooted the phone into recovery and installed magisk 13.3 (as you know when updating we lose magisk root) and it worked.
Then did a clean install of 26-07 build (thinking it will work) but nope.
Click to expand...
Click to collapse
Hi ! Can you make a little synthetic how to ? I'd like to try it on my S5 plus (g901F) It may be a walkthrough wating any response from magisk team ?
Jet45 said:
Hi ! Can you make a little synthetic how to ? I'd like to try it on my S5 plus (g901F) It may be a walkthrough wating any response from magisk team ?
Click to expand...
Click to collapse
I tried to do that again but I couldn't. As said:
In was on 19-07-2017 build with magisk 12 sdk and magisk manager 5.1.1 app, had magisk folder mount 0.8.5 and SD card access module, then on 26.07.2017 I received the weekly update, after update I rebooted the phone into recovery and instead of magisk 12 sdk I installed magisk 13.3 (for testing) and it worked. I tried doing that again but didn't worked so I don't know what to say lol.
Recycool said:
I tried to do that again but I couldn't. As said:
In was on 19-07-2017 build with magisk 12 sdk and magisk manager 5.1.1 app, had magisk folder mount 0.8.5 and SD card access module, then on 26.07.2017 I received the weekly update, after update I rebooted the phone into recovery and instead of magisk 12 sdk I installed magisk 13.3 (for testing) and it worked. I tried doing that again but didn't worked so I don't know what to say lol.
Click to expand...
Click to collapse
So I'll try to reproduce it at my side with that you've said, it may be a walktrough . Two brains to work on it may succeed
Jet45 said:
Hi ! Can you make a little synthetic how to ? I'd like to try it on my S5 plus (g901F) It may be a walkthrough wating any response from magisk team ?
Click to expand...
Click to collapse
I posted a logging of the problem on the main support thread, let's see what happens
https://forum.xda-developers.com/ap...sal-systemless-t3432382/page1765#post73249492
cross the fingers (I hope that you say like that in English)
Fingers crossed they sort it. Would love yo be able to use magisk again
Does anyone here have this issue on a stock ROM or is it just Lineage OS? From the log that was posted in the main support thread it looks like the Magisk installation was successful, but the system hangs on this one line before it can fully boot. I'm not qualified to read more than that out of the log though...
There's been some code added to GitHub in the last few days. Have anyone tried the latest unofficial snapshot? There was a new one built yesterday: https://forum.xda-developers.com/apps/magisk/unofficial-magisk-v10-beta-built-t3521901
Hi we got anymore news on this I have tried the latest beta one and it still gets stuck at booting.
It seems there is nothing to expect from nor magisk team neither lineage team. Nobody seem want to work on this really specific problem.
I'm running into a rather annoying problem when trying to install the Stereo Sound Mod for my One Plus 5t. Stock ROM and kernel. When attempting to flash the zip via magisk, it tells me that 'Magisk is not activated' and then proceeds to abort/fail the process. Ran into the same results when trying to flash via twrp. In fact, I've ran into this error a number of times - like when trying to install xposed via magisk manager. I'm not sure what the problem is since magisk is clearly installed and I'm properly rooted. I checked the data partition and the magisk.img file is there. Any ideas? I've attached the log from MM and the logcat filtered with 'magisk' as search parameters
nightraving said:
I'm running into a rather annoying problem when trying to install the Stereo Sound Mod for my One Plus 5t. Stock ROM and kernel. When attempting to flash the zip via magisk, it tells me that 'Magisk is not activated' and then proceeds to abort/fail the process. Ran into the same results when trying to flash via twrp. In fact, I've ran into this error a number of times - like when trying to install xposed via magisk manager. I'm not sure what the problem is since magisk is clearly installed and I'm properly rooted. I checked the data partition and the magisk.img file is there. Any ideas? I've attached the log from MM and the logcat filtered with 'magisk' as search parameters
Click to expand...
Click to collapse
Did you try rebooting?
Sent from my LG-LS997 using Tapatalk
Yep, rebooted several times and it's still not working. I don't seem to have a problem when installing modules that are already listed in the repo though. It just doesn't like me installing modules that I've downloaded separately
nightraving said:
Yep, rebooted several times and it's still not working. I don't seem to have a problem when installing modules that are already listed in the repo though. It just doesn't like me installing modules that I've downloaded separately
Click to expand...
Click to collapse
They may not be updated to support the new Magisk. You may have to wait till they are updated.
Sent from my LG-LS997 using Tapatalk
rootlinux said:
They may not be updated to support the new Magisk. You may have to wait till they are updated.
Sent from my LG-LS997 using Tapatalk
Click to expand...
Click to collapse
I suspect you're probably right with that one. I also had it happen with the xposed module. So presume that's not updated to support the new Magisk either?
I don't think it is yet.
Sent from my LG-LS997 using Tapatalk
I'm M having the same problem with all modules, including the ones in the repo,
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.
I'm having issues with Magisk on my Pixel 3 after installing the latest Android monthly patch.
The first issue:
Even with latest Canary build I was not able to patch the boot image...it looked like it worked but the image was the same size as the original and booting it did not give me root. I'm pretty sure this issue was occurring before the Android update, since I patched the boot.img before performing the update (but did not notice any issue with it until after the upgrade was complete). So I used an old patched boot image I had (unfortunately not the latest Magisk version), which booted and gave me root (and allowed me to do a direct install of latest)...but that leads to the second issue.
Second issue:
No sound! None at all. No UI sounds, video plays with no sound, etc. Have not tried a phone call yet. If I flash the stock boot image everything works fine, so it has something to do with the Magisk patched boot image. This occurs both with the old version I had and the latest canary version (direct installed over the old version). Not sure if it's related, but right after entering my login PIN it always says "System UI isn't responding," which also does not occur with stock boot image.
Update: I'm getting a bajillion of these firing multiple times per-second in logcat: 2020-12-08 10:14:04.521 1437-4414/? E/AudioSystem-JNI: AudioSystem::listAudioPorts error -19
Thanks in advance for any help you can provide. Happy to provide any logs or anything you think might be helpful to troubleshoot.
My first guess would be that it's one of your modules that's causing problems (that's usually the case when experiencing device issues after updating the OS). Disable the modules and try again.
Didgeridoohan said:
My first guess would be that it's one of your modules that's causing problems (that's usually the case when experiencing device issues after updating the OS). Disable the modules and try again.
Click to expand...
Click to collapse
I had not tried that...but unfortunately after doing so the issue still persists (I only had one module enabled -- the props config to make ctsProfile pass).
Hello everyone, I have a weird issue that I never encountered before. I updated my custom ROM from fastboot, and as always I had to re-root my device after updating. Im under Android 12, so I didnt use TWRP but I used the patched boot image method to reinstall magisk and have my phone rooted. Surprisingly, it seems my phone is rooted correctly, but the Magisk app shows Installed:N/A. A quick google search showed that it could be due to not unhiding Magisk before updating (even If I never did in the past and never had this issue). I tried the solution I found (unistalling magisk from adb) but it didnt fix the problem. Any idea on how to solve this?
[Discussion] Magisk - The Age of Zygisk.Magisk 24.1 released and perfect for android 12.