yashsingh1/xdaforums huggingface dataset:
[Magisk] ToastedToast:
I have a sony xperia 10, and TWRP is not out for that device. Magisk 19 puts my phone into a bootloop, and apparently something in the magisk 19 update broke magisk with sony phones. There is currently no way to patch an older version of magisk using magisk manager, and I cannot get TWRP without a recovery.img, which, due to sony's proprietary boot.sin file being all weird, cannot be extracted (boot.sin includes boot and kernel images or something) Is there any way to patch an older version of Magisk, or does anyone have a way to get Recovery.img from a boot.sin?
[Magisk] guest4711:
How about replacing the file in question with a 0-byte file?
[Magisk] vladone97:
Thanks. One question though: someone else told me to backup and restore the boot img before flashing the 19.1 zip. What's up with that? I'm just asking because I've messed my phone up in the past and I want to be extra sure.
[Magisk] Zaben:
Same thing happened to me on Xperia 10 Plus.

Boot and recovery being combined is not Sony specific, it's the newer Android A/B format.

The boot image can be extracted from from boot*.sin with 7zip. The older 7.1.1 Magisk manager was able to patch boot*.sin directly. 7.1.2 for whatever reason no longer can. Patching the boot image with 7.1.2 to 19.1 and then flashing with fastboot still resulted in a bootloop for me (without resetting userdata). I was only able to regain 18.1 root by flashing userdata back to stock. Something got changed in there that prevented Magisk 18.1 from working when I flashed back to the previous patched boot. Hopefully you have a recent backup.
[Magisk] ToastedToast:
Hello, I have noticed that you have had some success (at least more than me) in rooting an xperia 10/10 plus. I am still trying to figure out how to patch my boot.img with magisk 18. ( I have the boot.sin and older magisk manager, but it keeps asking me to update) Any help you'll be appreciated
[Magisk] Trey n:
anyone else have high cpu usage by magisk 19.1? its due to magisk hide being enabled, i disable it and re enable it and for about a day or two its back eating my cpu usage.....and battery

sent from my klte
[Magisk] Zaben:
I don't know of a way to patch a boot image with an older version of Magisk using the manager. You may want to ask on the Xperia 10 forums and see if anyone can share an 18.1 patched boot image for your specific variant. Even then you'll still need to reset userdata since you tried 19.1 like me.
[Magisk] r0tt0r:
hello, i encounter an issue since magisk 19 related adaway app.

someone has the exact same issue with amaze behaving like this and downgrading magisk to 17.3 or comple wipe and reinstall of magisk solves the issue.

please find my post related https://xdaforums.com/showthread.php?t=2190753&p=79499792 including logcat partial.

as wiping magisk/downgrade solves the issue i think its somehow a magisk issue. i tested different channels of magisk but only purging solves that. and it only affects adaway. other apps like.amaze , kernel adiutor request root permission as usual.

br

r0tt0r

Update: thx to post of guest4711 i was finally able to solve the issue.

i edited the magisk.db file manually with sqlite and added under policies table a line:

uid 10196

name org.adaway

policy 2

unitl 0

logging 1

notification 1

deleted /system/xbin/su

then symbolic linked magisk su to system/xbin

ln -s /sbin/su /system/xbin/su

rebooted and adaway is working again.
[Magisk] jcmm11:
https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/post79502860
[Magisk] JudgeDread11:
Can't you turn off internet access? Turn off WiFi and data or use a firewall. That would prevent Magisk from seeing there are any updates available.
[Magisk] BillGoss:
Or change the channel in Magisk Manager to Custom and leave it blank.
[Magisk] polygon21:
Flashed stock boot.img after uninstaller and flashed 19.1 on my s7, still no joy, manager reported as not installed
[Magisk] zgfg:
What is the purpose of a smartphone if you disable Internet?!

Magisk Manager, Settings, has an option Check Updates, you can turn it off but if still bothering with updates (?):

- If using AdAway (or similar tools), add github.com to the black list

- Or directly add to the etc/hosts file a line with

127.0.0.1 github.com

And reboot.

It will prevent access to GitHub.com to all apps, but if not a developer yourself, likely that Magisk Manager is the only app wanting to check for the updates.
[Magisk] JudgeDread11:
Obviously turning off internet just for the moment he would try to patch his boot.img

Realize now though this wouldn't work as the files to patch the boot image need to be downloaded.

Which is the same as using a firewall

And it won't work either as this would prevent Magisk to download the necessary files as well.
[Magisk] zgfg:
Obviously, I was not advising to disable github.com while installing/patching/configuring, but afterwards, because if you don't keep the latest Magisk Manager (as he originally wrote), then even if you disable Updates in its Settings, MM still sometimes notify about the available updates.
[Magisk] JudgeDread11:
Problem was/is he can't patch the boot image because the manager asks to update first.
[Magisk] varadinum:
nearby

Hi, I have rooted my Android phone with Magisk.Without TWRP, because it does not exist yet. Galaxy A9 2018 SM-A920F

I get the following message:"Nearby service is stopped repeatedly"

And Safety warning: "unauthorized processes have been detected"

I tried everything as well as force stop, delete cache, delete data ...Unfortunately, all without success.

Do you have an idea? Can somebody help me?

Thanks
[Magisk] zgfg:
With the Custom but blank, when you restart Magisk Manager, it will spin forever for checking updates.
[Magisk] levone1:
I'm just going to bring back my question once again, (I had asked previously about what's new in v.19, and I was given 'read the changelog', which of course I had done already, and was quite aware of, but not exactly my point in the question, plus, much of what's in the changelog is not understandable to the common user)... Why not just stick to 18 for now, since there are obviously issues that need to be worked out? In other words, if someone has v.18 working fine, what are they really missing out on? Don't get me wrong - I was one of the first I knew of to try it, and go through the whole bootloop thing, and reflash and soft brick, and back to stock, etc..., so I understand the drive to try it, and I appreciate people wanting to test and give feedback, etc., but when it became clear that it just wasn't going to work without extensive effort, the question quickly came to me - what am I really missing out on? Maybe I should just wait...

So, what is it?

---------- Post added at 02:11 PM ---------- Previous post was at 02:11 PM ----------

I'm just going to bring back my question once again, (I had asked previously about what's new in v.19, and I was given 'read the changelog', which of course I had done already, and was quite aware of, but not exactly my point in the question, plus, much of what's in the changelog is not understandable to the common user)... Why not just stick to 18 for now, since there are obviously issues that need to be worked out? In other words, if someone has v.18 working fine, what are they really missing out on? Don't get me wrong - I was one of the first I knew of to try it, and go through the whole bootloop thing, and reflash and soft brick, and back to stock, etc..., so I understand the drive to try it, and I appreciate people wanting to test and give feedback, etc., but when it became clear that it just wasn't going to work without extensive effort, the question quickly came to me - what am I really missing out on? Maybe I should just wait...

So, what is it?

(BTW - double-post is not my doing; XDA glitch...)
[Magisk] fspirolazzi:
flashing magisk zip encrypts my phone

Hi, I'm having problems with rooting with magisk.

(I'm using the latest stable version V19.1)

My phone is NOT encrypted and after flashing the zip file successfully, when I reboot to the system asks me a password, then asking me to do a factory reset saying that the password was correct but the storage is corrupted.

After this message showing "decryption unsuccessfull" I must restore the old boot.img and my phone starts normally without any encryption or decryption message.

Please help me, I don't know what to do.

I've already tried the wiping "format data and typing yes" but it didn't work, and it stills giving me a decryption error.
[Magisk] JudgeDread11:
Some apps that can detect root on 18.1 are unable to do so on 19.1

Also 19+ doesn't use a image file anymore. Which means it works without workarounds on devices which suffer from the f2fs bug, like mine.

I couldn't use modules with anything prior to v19.

If you just want root and have no problems hiding it where needed and don't have the f2fs bug then you are not missing out as far as I am aware of.
[Magisk] zgfg:
Please always provide info about your phone, make, model, stock or custom ROM, modifications, etc.

And read previous posts to see if somebody else already reported the same problem for the same phone (there is a Search field on the top/right).

If your phone is Huawei P9 (or Plus, Lite) with Huawei stock firmware - see post #33325.

As you already wrote, restore Boot image with v18.1 (no Decryption issue there) and then stay on v18.1 (don't retry to update), no other help here, this is a bug with Magisk v19.x (you cannot boot with)

You can keep with the latest Magisk Manager but in Settings, disable Check Updates
[Magisk] guest4711:
But be aware that some modules need 19.x nowadays, [MENTION=6283426]levone1[/MENTION]
[Magisk] ahhl:
hi i am using magisk 19, on redmi 6a android 8 rooted with twrp.

1. i am not sure why but some apps not able to find busy box and i tried to install busy box, it was unsuccessful. tried many apps

2. i tried to change/modified some file in root, but not successful. whether total commande, root browser etc, it always not success full

sorry, not sure where to direct the question because i do not know whether somthing wrong with magisk or twrp
[Magisk] zgfg:
Unfortunately, some phones do not work with v19.x at all (like Huawei P9 [and Plus, Lite and Honor 8] with Nougat - with Oreo no problem) cannot boot with v19, while v18.1 and earlier worked like a charm.

Seems also there are serious issues for v19 with Sony Xperia.

IMO, these are the issues [MENTION=6283426]levone1[/MENTION] wanted to emphasize
[Magisk] levone1:
Thank you - very helpful.
[Magisk] warrencoakley:
Anyone getting a parsing error when trying to update Magisk Canary?
[Magisk] jcmm11:
There're some known issues with Manager

https://xdaforums.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337/post79518822
[Magisk] Wolfcity:
Did you read the link? Was your manager hidden? And the manager for Canary builds may be signed with a different key so download it again. Maybe the download was just corrupt.
[Magisk] guest4711:
If nothing helps, download the Manager (but do not install it), uninstall the old manager and install the new one.

Mostly it is a problem of different keys used for signing (when you try to update ianmacd's build with canary or vice versa).

Edit: See https://xdaforums.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337/post79518822
[Magisk] warrencoakley:
Do I have to unhide it? Others are stating they cannot rehide it again. Can you confirm?
[Magisk] Phantom Thief:
Not sure if this was reported yet but seems like on android 5 devices magisk apps on "magisk hide" will unhide themselves when leaving the app.
[Magisk] warrencoakley:
I'll wait for a fixed to be pushed to solve the parsing issue instead. It seems you cannot hide once you install too. Serious bugs that need to be fixed.
[Magisk] warrencoakley:
Managed to update both but I cannot hide Magisk. Keep getting this error? Any ideas?
[Magisk] AndrzejDwo:
Mate please, read once again.

https://xdaforums.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337/post79518822
[Magisk] hyborian:
Just wait for the fix.
[Magisk] bluenote73:
Can someone with github access re-open two bugs related to Axon 7 A2017U support on stock? topjohnwu mentioned it was fixed and would show up soon, but that was months ago, and 19.1 still doesn't work but the issues are closed.

It's https://github.com/topjohnwu/Magisk/issues/729

and https://github.com/topjohnwu/Magisk/issues/980

Thanks
[Magisk] martyfender:
Why can't you post it yourself? Just sign up on github.

Keep in mind that [MENTION=4470081]topjohnwu[/MENTION] may close it again if you don't provide proper info such as the magisk.log, install logs and in many instances also, logcats and device info. He also prefers that you post logs with the Canary debug builds for better info.
[Magisk] SupDr:
[MENTION=4470081]topjohnwu[/MENTION]

I hope you will disable the auto reboot after in magisk manager update

Or make it optional allowing me to reboot manually
[Magisk] Didgeridoohan:
What do you mean? There's no auto reboot after updating Magisk or the Manager...
[Magisk] guest4711:
Which autoreboot, please? When updating Manager, I did not see anything like this. When updating Magisk through Manager, I can skip the reboot by touching the back arrow.
[Magisk] alteristkang:
Hello all,

I am using a OnePlus 5 on Oreo. I updated from Magisk 18.1 to 19.1. The update looks fine. But when I boot my phone, I see Magisk version is 19.1 but my whole phone now cannot play any audio and videos. All audio doesn't work no matter where I listen to them from, Spotify, Youtube, or mp3.

I will stick to Magisk 18.1, but anyone here has any idea what's wrong?

Thanks!
[Magisk] guest4711:
Perhaps an incompatible module? Boot in core.only mode to see whether audio is working again. If yes, disable the first mofule and reboot. If not working, disable the second one too... So you should find the culprit.

If no, you should provide the neccessary infos to allow analyzing the issue...
[Magisk] SupDr:
on latest version magisk manager 7.1.2 , i installed patched recovery through odin

after starting magisk manager it ask to install some required files i hit ok

after completed it gives notification ( rebooting in 5 seconds ) without asking to confirm
[MENTION=8010004]guest4711[/MENTION]
[MENTION=4667597]Didgeridoohan[/MENTION]
[Magisk] Didgeridoohan:
Ah... That's something different than just a standard update. And the reboot is likely required to prevent an unstable system.
[Magisk] uudruid74:
OK. I need to root a system without TWRP or an open recovery. I've done this before to install the old SuperSU on a Rockchip system (my car). Basically, take the stock update.zip, open with my Linux box, unpack, modify the files manually following the steps in the update script. Rebuild/pack the images, zip it all up, and update the system. The stock recovery didn't expect a signature! It doesn't run the twrp compatible flash scripts, so I can't flash magisk.zip, but it will accept rockchip flashable format files which are basically a custom archive with disk images.

My newest project is new hardware, a Libre Renegade, running Station OS. It is also running a Rockchip system and the recovery looks to be the same. I'm pretty sure I can modify the images and make the recovery accept it. I want to kill the Chinese crapware, add micro G, Viper Audio, Nginx and SSH, and maybe set Kodi as the default launcher, and add Magisk.

Getting Magisk will be step 1 so I can test the rest before making permanent changes to the image.

Anyone have any tips on how to install to an image file? I assume I'll be basically changing boot.IMG but Magisk looks a bit harder to install than old SuperSU.
[Magisk] warrencoakley:
Confirmed latest manager updated fixed the parsing and hide issues from before (Canary Debug) ?
[Magisk] wilsonhlacerda:
As you are coming from Supersu and seems new to Magisk, those links may help you to better understand it:

https://www.didgeridoohan.com/magisk/HomePage

https://xdaforums.com/apps/magisk/root-explorer-autorun-receiver-t3928129
[Magisk] JohnWrick:
The Magisk app need to "force stop" for the app details in order to stop showing "Downloading module" notification when the module has already been downloaded, flashed and installed on the system.
[Magisk] uudruid74:
No. I'm not new to Magisk at all. I never said that! I've been running it on my phone for years. I've just never installed it without using the zip and it's built in tools and was wondering it anyone has.
[Magisk] Didgeridoohan:
If it's just a matter of modifying a boot image, the Magisk Manager can do that (https://topjohnwu.github.io/Magisk/install.html#boot-image-patching).

If you need other kinds of info you've got some details in [MENTION=4470081]topjohnwu[/MENTION]'s documentation: https://topjohnwu.github.io/Magisk/
[Magisk] Ang Hong Eng:
Hello bro, both my magisk and Xposed can't be open, I had the magisk 1st, after that I install the Xposed installer apk u given, then I install the Xposed framework in magisk module, but after reboot, both of them can't be open, after I uninstalled the Xposed apk and reboot, magisk can be open again, could you please guide me how to solve it, thank-you very much bro, my phone is Nubia z17 lite NX591J Android 7.1.1
[Magisk] :
hey guys,

i've installed magisk 19 and it works in lineage but is it correct that i have no possibility to actiave root access in developer options? it is grey. but magisk is working and superuser rights are given for necessary apps.
[Magisk] guest4711:
Yes, that's correct. You should use Magisk Manager to control root access.
[Magisk] uudruid74:
I just read that. Getting the boot image modified seems to be the easy part.

Damn rescue says to use the vol up, vol down, and power buttons to control the menu. This box has none of those! LOL. And it doesn't seem to work via a USB keyboard. I'll have to make the on-board updater think this is a real update.

Thanks.

---------- Post added at 12:21 PM ---------- Previous post was at 12:18 PM ----------

The links were helpful. Looks like Magisk makes things easy. I had never even looked at the options for modifying the boot image built in to the APK!

That part worked
[Magisk] fribriz:
Magisk 19.1 breaks TWRP recovery - not able to get to recovery by conventional means. Restoring original boot.img and recovery.img allows getting to TWRP.

Going back to 19.0 solved this. Hopefully a future update fixes this. No other issues otherwise.

Phone: Xperia Z1 with Latest Carbon ROM Pie
[Magisk] grapestain.m8:
MAGISK v19.1 vs. TWRP issue

Not related to anything, I just want it to be written somewhere to help others facing the same issue:

TWRP cannot start after MAGISK v19.1 installed on Sony Xperia Z1 (honami). Tried with variety of TWRP versions (v2.8.7.0 official, v3.0.2 official, v3.2.1 official, v3.2.3 unofficial, v3.3.0 unofficial). TWRP does not start regardless of method (power-menu reboot to recovery, fastboot reboot recovery, power up + volume key combo, fastboot boot twrp.img). The symptoms are similar in all cases: TWRP seems to try starting for a bit, but the splash screen never appears, then power led flashes red and phone reboots into system or simply freezes with a black screen, maybe with the SONY brand logo on the screen).

There's no such issue with Magisk v18.

Issue was fixed by restoring previous boot partition nand backup from fastboot. If I flash v19.1 again from TWRP just to see, the issue comes back, so connection is clear. Not sure if device specific or only specific to my config or may be a more general thing affecting other devices as well also if it's an issue with Magisk v19.1 or it is only an issue when installing Magisk using TWRP from ZIP.

My OS is Resurrection Remix v5.8.5 (Nougat 7.1), kernel version is 3.4.113.

The system boots fine and Magisk v19.1 works fine otherwise. Only recovery is affected.

---------- Post added at 11:44 AM ---------- Previous post was at 11:43 AM ----------

Wow, you've beat me by 1 minute. Coincidences, huh?
[Magisk] Didgeridoohan:
[MENTION=4460467]fribriz[/MENTION] and [MENTION=7374076]grapestain.m8[/MENTION]

It's known and under investigation:

https://github.com/topjohnwu/Magisk/issues/1418
[Magisk] Al-Bcherrany:
Hello guys, i followed the A/B partition steps to root my Nokia 7 plus and worked perfectly, however i'm having a little confusion about OTA, everytime i need to apply OTA do i have to use "Install to inactive slot" step ? Or i only need to apply it once ?
[Magisk] heineken78:
[MENTION=4470081]topjohnwu[/MENTION]

I have question about vboot1.0 ab system init bypass on ^

Magisk forces kernel cmdline to boot in recovery and uses own init on system and system boots. Its clear.

If I don't want to use magisk, can you help me with what I need to patch on my costom kernel or in cmdline to let stock system init boot?

I have tried to replace init= with system partition number. android.verifiedbootmode with logging but its still not working- bootloop or hanging on init.

Can you point me what can be done to boot without using of magisk?

Thank you in advance!
[Magisk] bluenote73:
I'm trying to get it reopened. It was already posted properly by me, acknowledged by topjohnwu, it's supposed to be fixed, it's not. If you have access to re-open it, that would be really helpful.

https://github.com/topjohnwu/Magisk/issues/729

https://github.com/topjohnwu/Magisk/issues/980
[Magisk] Didgeridoohan:
What he's saying is that it's much easier if you open a new issue with the relevant information and a reference to the old issue. It's likely that it didn't actually have anything to do with the problem described in issue #980, so new information is needed.
[Magisk] hall3:
...pls help:
[Magisk] bluenote73:
Is there something wrong with #729 ?
[Magisk] Didgeridoohan:
Mainly only that a lot of it is old information. Has anyone tried the patched boot image mentioned in that issue thread on Magisk v19.1+? Maybe some of the issues mentioned had to do with the Magisk image, and Magisk is image-less now....
[Magisk] tuga_z:
https://github.com/topjohnwu/Magisk/issues/755
[Magisk] hochoch:
I'm having this issue as well. My phone is like dying to put everything in PiP (picture-in-picture) mode when using 19.1. I flashed back to stock and everything was fine. It also appears to be affecting plex which keeps starting and pausing infinitely. ugh.
[Magisk] Didgeridoohan:
From the current Canary build changelog (19102):

In other words: it's a bug, it's been fixed.
[Magisk] hochoch:
awesome, thanks so much - it's been bugging me so bad lately! so, now we just wait for it to get main-lined into the beta/stable branches? I've tried so many things trying to figure out the cause of this. was trying to avoid a clean flash!
[Magisk] XtraWater:
I had a similar issue. It worked after I cleared cache of magisk.
[Magisk] malte180684:
Just tested "Drivedroid", it's working...

LG D802, Magisk v6, systemless xposed deactivated.
[Magisk] rgawenda:
Stable from Play Store.

If you read drive droid FAQ, it states that it needs:

Capable firmware, capable kernel, and root. If you are using a custom ROM, check your kernel. It always worked for me in CM/Nexus4 and CyanogenOS 12/13 OPO (Bacon), with SuperSU, and now with Magisk v6 and phh's open source SU
[Magisk] zaphiel:
Hello.

Im so newbie with this, so... i need help.

I have custom rom with pre-root installed, so i need remove all root but, how i can i do it?, i dont know how remove it...

Thanks.
[Magisk] ilfat12:
The fact that DriveDroid (FlashFire too) working with the original SuperSU excellent. My phone too OnePlus One [bacon]. Sultanxda rom.

Since it works with the original SuperSU (and other non-modified SU) and does not work with Magisk, then the problem is in Magisk.

Logical?

Many thanks to [MENTION=4470081]topjohnwu[/MENTION] for his work. Let's hope that he will do so in all everything worked :)
[Magisk] jed.padilla:
So I recently just upgraded my Galaxy S4 (MDK unlocked bootloader) to stang5litre Edition 5.0 v3 (lollipop). I removed SuperSU, went to TWRP (2.8.4.0) and flashed Magisk. I was stuck at the Samsung boot screen. Do I need to remove BusyBox also? When I ran the Magisk Manager after removing SU, it told me the device was not rooted, so I thought I would be okay. Any advice?