yashsingh1/xdaforums huggingface dataset:
[Magisk] hunky-d:
Just uninstalled Magisk and, after a moment of dread with a bootloop on which I restarted in recovery and rebooted there, I got the phone started and the app automatically mounted the database in my sdcard/Download folder and works like it should. So that iBird Pro app does not like Magisk.
[Magisk] Didgeridoohan:
It is a Magisk issue, caused by how Magisk uses loop devices. It's known and it should be fixed in the next release.
[Magisk] sandaljrpit:
I'm sorry for my question. so, does anyone have a false ( cts&basic ) when the hosts without the system are enabled? happened recently. I use magisk v16.0

Samsung A7 16 ( stock Rom Nougat )

Thanks

:)

EDIT ;

after delete the playstore data and safetynet check all back to normal. at first false (cts&basic) due to clear hosts.
[Magisk] bkkzak:
I tried once a couple days ago and it didn't work for me, I believe I used TiBU. How did/have you been clearing the data of those apps (i.e., system settings, third party app manager) ?

Everytime I clear Play Services data I have to reconfigure Android Auto and WearOS, it's a hassle
[Magisk] JeepFreak:
Can someone please tell me for certain whether the patched_boot.img that is producedb by Magisk Manager can be flashed through TWRP? I can't believe I'm the first to ask, but I can't find the answer.

Thanks!

Oh, it's a Pixel 2 XL, on stock 8.1.
[Magisk] Badger50:
Nope. You have to fastboot it. Having said that, you could always try and let us know what happens. But I think we both know what the result will be :cool:
[Magisk] JeepFreak:
Haha, I almost tried it earlier but I really appreciate you saving me from my own impatience! ?
[Magisk] yochananmarqos:
You don't need to patch manually if you have TWRP. Just flash Magisk.
[Magisk] martyfender:
If you have TWRP, you can just flash the Magisk.zip through it to make it simpler, as the above poster stated, but you can also flash boot.img 's, in TWRP, unlike what was stated above. If you flash the Magisk.zip, it will patch the boot.img in the process.

I have flashed boot.img 's through TWRP, quite a few times. Boot to TWRP, hit the install button, in the lower right is an install image button, hit it, then navigate to the /sdcard/MagiskManager folder by choosing up a level, then choose patched_boot.img, then select the partition to flash image: and check the boot option, then swipe to confirm flash. Finally, navigate to the main menu, choose the reboot button then choose, system, to reboot to.

EDIT: I just successfully flashed the patched image on my Ares 8A with TWRP, just as I described.

I believe it should also work for other devices, as well.

If you don't have TWRP, you must flash it through fastboot or odin, from your PC, though.
[Magisk] Kalilinux007:
I tried to flash Magisk 16.4.zip on micromax a102 using TWRP custom recovery and got an error saying (unable to unpack boot image). I have Resurrection remix 5.8.5 Nougat(7.1.2) custom rom installed and 3.1.1 twrp. Can anybody help me how I can fix this problem?

SEE THIS ERROR LOG FOR MORE INFO----

- Mounting /system, /vendor

- Found boot/ramdisk image: /dev/bootimg

- Device platform: arm

- Constructing environment

- Adding addon.d survival script

- unpacking boot image

! Unable to unpack boot image

- Unmounting partitions

Updater process ended with ERROR: 1

Error installing zip file 'external_sd/Download/Magisk-v16.4.zip'

Updating partitions details. . .

. . .done
[Magisk] skiely666:
Yes just in system settings/apps/app info etc. Yeah it's a bit of a pain alright, I did it for something different about a year ago & it broke lots of Google stuff so I was apprehensive about doing it again but it worked out this time!
[Magisk] -Duir-:
Sorry to dig back to such old posts but wondering if any resolution has been found to this issue?

I just installed Magisk on my Axon 7 and have the same problem. I tried both 16.0 and 16.4. Magisk works fine when installed but my sdcard displays as corrupted. If I uninstall Magisk my sdcard works fine. Very confusing.

dm-verity is not enabled (we actually have to install a no-verity patch for kernel for our device to boot with TWRP installed)

device is not encrypted

sdcard is formatted as exfat.

Edit:

Tried Kantjer's 180704 build and same issue.

Also just to mention I have tried things like letting the phone format the card. As soon as it says it's finished it pops up saying it's corrupt again. I've reformatted in TWRP and Windows also with no change. I'd like to find an actual solution to this. It seems like an issue with how the installer patches the boot image that breaks exFAT support.

FWIW, back in March I was having issues with MagiskHide on this device as there was no logd. The only difference is back then my device was encrypted. I'm not sure what else has changed to make MagiskHide work now.
[Magisk] RandomPooka:
You aren't able to use the TWRP flash image function to flash them? Strange, I've been able to do that on other devices.
[Magisk] Badger50:
The stock boot.img definitely yes with twrp. However on the P2XL the boot/recovery are one in the same. So I suspect that's why it has to be fastbooted. That's just a guess of course :cool:
[Magisk] RandomPooka:
Ahhh. I didn't realize that it had a boot/recovery combo image like the Essential PH-1. That's so stupid, especially considering that BOTH phones are supposed to be flash-friendly by design. It isn't like either of them is short on internal memory to have had a separate recovery partition.
[Magisk] vampyyri1123:
Anybody having trouble tripping safety net

I've noticed that if I flash the patched boot img it trips the set warranty bit kernel message on samsung due to modifying the boot partition.

A work around I found to work if you want to avoid the safety net is have bit a stock boot img AND the patched one on my ext sd card and flash the appropriate one for what I need.

This however is tedious and time consuming. Is there an app that could automate that process?
[Magisk] JeepFreak:
Of course! I don't know why I didn't think of that. I flashed it and reflashed the custom kernel and I everything works great!

Thanks guys!
[Magisk] Artim_96:
That's a question you should ask in your devices forum. Error 1 is a bit vague, bit "unable to unpack boot image" sounds like your devices boot image is either in a format or compressed with a format Magisk can't support.

As experiment you can try to extract the boot.img from your ROMs zip file and let Magisk Manager try to patch it, but I see little chance for success. The chance night be higher that someone has a workaround like a custom kernel replacing the boot image with one Magisk can handle
[Magisk] wackowizzard:
Hi, I'm not sure what went wrong, but I can not open the Magisk application anymore.

All I did:

1) Backed up my ROM with TWRP + backup with Titanium.

2) A full wipe performed in TWRP.

3) A new ROM flashed. But I was not happy about it, because the ROM was a little buggy.

4) Flashed the backup.zip of my old ROM with TWRP.

And since then I have problems with the Magisk application. I have already removed the application, flashed the magisk_uninstall.zip, and reinstalled again. But unfortunately still the same problem. How can I solve this?
[Magisk] jcmm11:
Crashes when you open it? Try deleting the apps data via settings.
[Magisk] paolocorpo:
I read that a new version 16.6 has been released

Where may I download it?

Thanks

Inviato dal mio Mi A1 utilizzando Tapatalk
[Magisk] Sjant:
https://github.com/topjohnwu/Magisk/releases/
[Magisk] wes'side:
Just added both new updates for magisk for a nexus 6p, so far so good along with xposed holding steady, on the positive the phone starts up faster, the Lil thing that maybe my issue is my own issue but my vender says is not matching up or don't know if is a result of adding download venders from play store mod, just before the update to mm16. 5 & 5.8.0 It could be coincidence but I'm open to suggestions an will continue to give feedback on the new updates an things hold up or avalanche. ¡°§°¡

---------- Post added at 02:50 AM ---------- Previous post was at 02:43 AM ----------

16.6 to correct my last magisk update and also, my safety net hasn't been green for a moment and still progress on that's other than that everything else is goody gum drops.
[Magisk] yochananmarqos:
Magisk neither touches /system nor /vendor.
[Magisk] abbots:
I have Magisk Manager on Nexus 7 2013 ElementalX, all working well. Today got a MM update message, updated, but, when I tried to start MM, Nexus got all maxed out and unresponsive. Rebooted Nexus, tried again starting MM, again, all maxed out.

Downloaded MagiskManager-v5.8.0.apk from XDA, installed, same problem?

What should I try?
[Magisk] Didgeridoohan:
Logcat

From the sound of it, from a computer...
[Magisk] erezzun:
I have installed 2 games on my phone (clash of clans, clash royale) but none of them can not be started and they keep crashing after I updated magisk to v16 from v12.

I flashed v14 and 15 but the same problem still there.

How to fix this? :(
[Magisk] Xplorer4x4:
I have a Moto G6+. From stock, I booted TWRP using an img. I flashed TWRP installer zip. I wipped /data. I then flashed the RR official GSI img file. I booter RR no issue. I rebooted and flashed Magisk 16. When trying to reboot, I got booted to fastboot. Since then ADB and fastboot seem broken. Therefor I can't get logs to provide. I have tried the universal driver from Google and offical drivers from Moto. PC says USB Device not recognized.
[Magisk] arsaam khan:
I have installed Magisk v16.6 and i installed it from TWRP for treble as i installed magisk my device got stuck in Bootloop, I had tried clean flash ROM and tried again got same problem what may I do ??? :confused:
[Magisk] elias.parasini:
LG V30+ Oreo 8.0.0 UBL, rooted, xposed.

Recently got OTA update for magisk, instal it without TWRP, and now i have magisk 16.0, but all my xposed module cant be opened.

It says "waiting for framework to respond.." or something.

I think I lose my root. Should I reinstal magisk via TWRP?

Need guide, thanks ?
[Magisk] MirceaViP:
Bug in Magisk Manager 18 (latest as of Sunday 07 20018

There is an important bug in Magisk Manager 18 (device Alcatel Idol 3 4.7, OS Android 6 Marshmallow) in that it does not open the app. Reverted to previous version (17).
[Magisk] martyfender:
18? Where did you get v18? There is no v18 or v17, for that matter. The latest official version of Magisk just released is v16.6 beta. The previous version was v16.4 beta. The latest official Magisk Manager version is v5.8.0. The previous version of the Manager was v5.7.0 Did you by chance download it from an unofficial source? If that is the case, I would not trust it.

https://xdaforums.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589

https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
[Magisk] Abolfazl:
Installed 16.6 and latest Magisk Manager. Now my Pixel 2 is coming up with a message on every boot that says "there's an internal problem with your device".

Is this because of the DTBE?
[Magisk] abbots:
Thanks, I'll try to do that, I'll try to get the one suggested on your help pages.

Meanwhile, I've installed previous version, MagiskManager-v5.7.0.apk, that is working no issues, so all is good for now.
[Magisk] jenslody:
There is no MagiskManager 18 or 17, do you mean 5.8 and 5.7 or did you download from some other place (not [MENTION=4470081]topjohnwu[/MENTION]'s xda-thread or github).
[Magisk] davidzam:
Actually I did experience a big issue updating from 5.7 manager to 5.8. A notification appeared and I did the update. After installing, I lost root, and the device... Well went crazy, I cleaned dalvik and cache, nothing, had to unistall magisk using the zip provided for that on magisk post. I did try to install again the latest manager 5.8, then I did patch boot.img and downloaded the zip of magisk 16.6. Installed and again, no root, and device unmanageable. Not I couldn't even do a log. Unistalled again, back on manager 5.7 and magisk 16.4. All normal again installed trough twrp. Don't know what's the estate of boot.img, it doesn't matter if it is the one patched for magisk 16.6? Or I need to flash the one that was modified for magisk 16.4 by the manager 5.7. Thank you.

Enviado desde mi SM-G550T1 mediante Tapatalk
[Magisk] Didgeridoohan:
Grab a logcat from a computer with ADB.
[Magisk] Xplorer4x4:
Follow up: I flashed Magisk uninstaller. No change. I flashed 16.6 beta. No change. I tried uninstaller, but gave an error even though 16.6 was installed. I can get Offical-RR GSI img to flash and boot, but no matter what I do adb and fastboot are broekn preventing me from flashing stock firm,ware and testing things further. I have tried removing the offical Moto Drivers and the Google Universal driver, reinstall, but no luck. How can I fix ADB?
[Magisk] abbots:
OK, installed catlog from play.

as I've installed MM 5.7, got suggestion to upgrade MM, did that, got same probs as before

as catlog was running? I guess it collected what was needed ? not sure if I configured what logcat needed...?

anyhow, this was collected

https://sbt.net.au/android/logcat_and_device_info.zip
[Magisk] ChiDi9901:
I can confirm that on my on my Xperia Z3 Tablet Compact Magisk manager 5.8 won't open. It only shows the splash screen and freezes there. Reverted to 5.7 and everything is normal. Didn't loose root or anything.
[Magisk] Grgur:
I upgraded Magisk via Magisk Manager to 16.4. HTC 10 with LeeDroid R121 (Nougat). This resulted in bootloop. Clearing cache/dalvik did not help.

I managed to recover by using Magisk Uninstaller, then flashing Magisk 16.4 from recovery and installing Magisk Manager 5.8. Now Magisk works, but Magisk Manager is borked. It says my installed version is 16.4, the latest version is 16.0, and it wants to "upgrade".
[Magisk] topjohnwu:
You need to get the logcat while the crash it happening.

The logs you provided does not contain any crash related to Magisk
[Magisk] abbots:
thanks

it doesn't really crash as such: the logo/splash page comes up, but, it just stays on the logo/splash, the menu doesn't come through, the device becomes really unresponsive, if I jump over to ElemntalX summary screen, shows all 4 CPUs maxed out

I then go settings/apps and kill MM

this issue only started when upgraded MM from 5.7 to 5.8 earlier this morning

I've unistalled/reinstalled several times, prob persists
[Magisk] davidzam:
Installed again manager 5.8 on android 6.0.1 same behavior. My firts log. Thank you I'm going back to previous version
[Magisk] Psycho-Mods:
So I updated to v16.6 just now, no app can now ask for root access, I tried with titanium backup, stuck at Asking for root permission, tried with the terminal app in Lineage OS, same can't get the prompt, tried in a self made app, there too can't access root permission. Here are the logs.

That's the only thing I am getting in logs.
[Magisk] abbots:
OK, tried again:

installed MM, after install, selected 'open'

splash screen/ logo came up, waited about 5 min, still on same screen

tried back key, nothing. tried back key again. after a while, got message offering wait/close choice, did 'close'

collected logs

https://sbt.net.au/android/logcat_and_device_info2.zip
[Magisk] geodemarse:
Hi,

I have a OnepluS 5T under LineageOS 15.1. From the nightly of 2018-05-28, LineageOS did not launch anymore. So I went back to version 2018-05-21.

My question is whether with the latest version of Magisk v16.6 from 218.07.08 it works? Has anyone been able to test with the latest July nightly 15.1 release?

Thank you.

geodemarse
[Magisk] andmail:
Huawei Honor 6

MM 5.8.0 frezzes on splash screen.

MM 5.7.0 OK.
[Magisk] jenslody:
Please don't be so disrespectful.

The actual version was tested on many devices during the internal test-phase.

But as always not all possible combinations of devices and roms can be tested.

And some vendors implement stuff on a really weird way.

So even major bugs can slip through.

There is no way to test each and every device unfortunately.
[Magisk] pythonimus:
5.8 is also not starting for me anymore on LOS 15.1 in Mi Mix 2.

I reinstalled (removed and installed) the latest Magisk (beta) and Magisk Manager but it now has a weid problem for me:

Safetynet will not pass on reboot no matter what.

I have to go to settings and disable "Magisk Hide" and reenable it after every reboot (then SafetyNet passes).

Now i went back to 5.7 but the error persists.

SafetyNet Playground says "Passed all SafetyNet checks" but PlayStore will still not show me the Netflix app for download...
[Magisk] UFG93:
Hi guys. Sorry I'm kind of a newbie.

I flashed Android 8.1 Liquid Remix rom on my device but I've been trying to install Magisk and I keep failing. My device is currently unrooted.

Please what do I do and which Fastboot img should I use?
[Magisk] mrror:
Freeze on splashscreen also on Moto G 2015. I'd roll back to 5.7 but I'm afraid to make things worse....
[Magisk] guest4711:
Stop playstore and kill its data/cache. Then reboot and try again...
[Magisk] trentonite:
Almost the same issue for me. OP3T on lineage 15.1, magisk manager 5.8. Magisk hide works fine for me, but if I try using the Hide Magisk Manager option I can no longer use Magisk Manager. It launches to the splash screen and just hangs. Uninstalling manager and reinstalling works. Not sure why this is happening. /Shrug
[Magisk] mobileman88:
I found that apps which were already granted root before upgrading works but any new apps which requests for root or apps which needs safetynet fails. Downgraded back to 16.4 for now.
[Magisk] pythonimus:
Thats exactly the problem, when I reboot the safetynet test will not pass until I disable "Magisk Hide" and reenable it.
[Magisk] GryphonBR:
Hey guys, so updated from 16.4 to 16.6 on my LG V30+ using BoomBox v19 (essentially a bloatware-free version of LG's Oreo firmware), and after updating WebView's zygote process is crashing and being terminated by Magisk. Reverted to 16.4 using TWRP and everything is fine again. Not sure if this issue was known previously, so I can reinstall 16.6 to collect logs if needed.

Update: I decided to try installing 16.6 from TWRP to check for any possible differences, but to no avail. I ended up collecting a log file, though, which I'm attaching here.
[Magisk] MBechirM:
can anyone help me read this logcat to find out the reason for random reboots ?
[Magisk] Tech0308:
Having a problem with v5.8.0 of magisk manager, it freezes on splash page and then decided to freeze up my phone and heat it up really badly.

Samsung s5 phoenixrom 6.0.1
[Magisk] danishajaz:
The latest beta update is not working. I'm on 8.1 lineage OS on OnePlus 2
[Magisk] ElIT3ShOOT3R:
Can confirm on my S5 Stock too. My phone became almost unusable.
[Magisk] suyonk:
Same like me bro,

My device is samsung j7 prime stock Rom 6.0 with xposed installer,i decide to downgrade to MM 5.7.0
[Magisk] Pkt_Lnt:
Many posts about this, no logs to help get it fixed, none, zero, zilch, nada. Just like your "no logs to help" post. Come on man! :D
[Magisk] suyonk:
Sure,but i still in outside. Not in front of my laptop. How to take a logcat ?
[Magisk] Barquillo:
on lg g3 stuck on splashscreen too some fix?
[Magisk] Pkt_Lnt:
This link tells how. [MENTION=4667597]Didgeridoohan[/MENTION] has posted it literally hundreds of times, there is a TON of info in there, please bookmark it. :good:

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

---------- Post added at 09:59 AM ---------- Previous post was at 09:57 AM ----------

Until people post logs to identify *precisely* why that happens, no.
[Magisk] BombeerHC:
Hi all, I have a galaxy s8 (dreamlte), with stock ROM. Magisk 16.6 randomly bootloop the device when I turned it off and then on.. randomly becouse sometime work. I want to take a logcat but I don't know which.

Anyone have this bug?

16.4 lose root randomly.

16.0 work very well.
[Magisk] jurekn73:
Same problem in LG SPIRIT 4G LTE STOCK Marshmalow ROM

works good on j3 2016 5.1 stock
[Magisk] Pkt_Lnt:
I posted this link in the reply directly above your question.

https://www.didgeridoohan.com/magisk/MagiskHideHelp
[Magisk] Xplorer4x4:
Some help to fix adb would be greatly appreciated. No logs can be provided because of this.
[Magisk] irony_delerium:
Magisk Manager 5.8 issue - flashing wrong partition

So, I just went in on one of my devices to fix a broken install of Magisk. Huawei Mate 8, OpenKirin Lineage 15.1.

Using Magisk Manager 5.8, selected Install -> Direct Install. Let it reinstall Magisk 16.0, or so I thought. Upon reboot, I got Huawei's error screen indicating that it failed to load the kernel image.

Reloaded the kernel image from the stock firmware and rebooted, checked the backup that Magisk Manager makes (/data/stock_boot_<MD5>.img.gz), it's the image from /dev/block/bootdevice/by-name/kernel, not the ramdisk image in /dev/block/bootdevice/by-name/ramdisk.

This worked fine previously on Magisk Manager 5.7, with the caveat that if I left network access generally enabled for Magisk Manager, it would splat all over itself requiring me to go to Settings and clear data for Magisk Manager before I could use it.
[Magisk] davidzam:
Exact same issue using stock 6.0.1 on Samsung, Did a clean flash as topjohnwu advised, unistall using zip, cleaned dalvik and cache, installed manager 5.8, patched boot.img for flash through ODIN, flashed installed, bugs and root lost. Back on 16.4 and manager 5.7, stable channels of updates from now on, Thanks
[Magisk] martyfender:
I lost adb and fastboot access recently after reflashing my stock boot.img. I discovered that USB debugging was disabled. I had to go back in to developer options and re-enable it and reapprove the security prompt. Let me know if this helps.

Edit: also make sure the adbd binary is still on your system. On my Nextbook Ares 8A it is in a folder called root, in root ( /root/adbd ) with permissions 700 and also, I believe symlinked in /sbin/adbd->/root/adbd, permissions 777.
[Magisk] xxxmadraxxx:
Same here. I had to stick my HTC One M8 in the freezer. It got so hot, I thought it was about to go on fire. Battery drained from 80% down to nothing in the space of about 20 minutes. I can't even uninstall Magisk Manager as although the GUI goes through the uninstall process, the app is still there afterwards. Likewise with trying to do it via ADB. `adb shell` works, but trying to `su` to get root just times out. A proper Catch 22 mess!

Very difficult to get logcats or any other type of info given the phone is so unresponsive, it's literally 5 or 10 minutes between a tap on the screen or a command in ADB before anything happens.

I did manage [with extreme patience waiting for any response] to get a process viewer app open on my phone which showed between 98% and 100% of processor time was being consumed by several "sed" processes.

Ditto with a `pgrep` via ADB:

shell@htc_m8:/ $ pgrep sed
4493
4494
23911
23912
27215
27216
27971
27972
29889
29890
30471
30472
32288
32289

Whatever the feck's going on here, it looks like Magisk Manager is spawning numerous `sed` processes which are eating up all the phone's processor cycles.
[Magisk] Xplorer4x4:
Thanks for your reply! I have booted Offical RR GSI and verified USB debuggin is turned on but Windows gives me errors when plugging in the device, or gives me no error at all but the device is not listed in device manager or my pc. Also with out Recovery or root I'm not sure how I would verify that adb is still in place on the device.
[Magisk] andmail:
Huawei Honor 6 MM5.8.0 Freeze logcat
[Magisk] Artstar:
Same symptoms with my Samsung Note4 (N910G). Installing 5.8.0 manager resulted in a significantly slowed down handset. Luckily I planned ahead and downloaded the uninstaller to run from TWRP recovery and reinstall 16.0 with 5.7.0 manager.
[Magisk] 3dawg:
I've been having a serious battery problem with Magisk.

If I use magiskhide to hide my banking app, my battery becomes absolutely crippled by a process called logd which afaik is necessary for Magisk to keep track of apps enabled in magiskhide.

I've read that disabling logd (android logging?) results in magisk hitting the cpu heavily instead and thus not fixing the problem.

Is this a bug or intended behaviour? It makes using magiskhide cost too much in battery life to be worth it.

Thanks.