yashsingh1/xdaforums huggingface dataset:
[Magisk] Fry-kun:
Installed 5.5.3 / 15.2 just now (direct/recommended)

After 1st reboot got a notification that some image got patched and a reboot is needed (haven't seen this behavior before)

After another reboot and subsequently getting "There's an internal problem with your device" error on boot.

Pixel 2 XL, stock 8.1.0

Edit: developer options said OEM unlocking was off, something triggered it? Switched back on, error still present. Do I need to do a full deinstall+reinstall?

Edit2: I see main thread says patching dtbo image causes this.. I don't want to mod vendor partition, and "preserve" options were both checked. Restore images doesn't work, says stock backup doesn't exist. How to fix?

Edit 3: after restore, magisk immediately patches the fresh dtbo, ignoring its own setting :(
[Magisk] Killua96:
Magisk Manager is unable to hide with 15.2 on my H870 (LG G6)

It installs the new Magisk but it'd cancelled after a few seconds...

Here it is a logcat, if you need something else I'll provide it.
[Magisk] Mohamed Elhadad:
how to fix that

unable unpack boot image
[Magisk] AndreSantoro84:
Well done! Version 15.2 fixed the MagiskHide. Thank you!
[Magisk] chudy_85:
Install this mod using TWRP or magisk manager.

Reboot device and then go to play store wait 2-5 min and you have certificate. After this uninstall mod or no. Your decision

https://xdaforums.com/showthread.php?p=72138574

Wysłane z mojego EVA-L09 przy użyciu Tapatalka
[Magisk] xiiihyou13:
magiskSU does not add new root required app to the list even after "Grant" forever

Phone: Mi5

ROM: AEXMod 8.1

Magisk: 15.2
[Magisk] Souldrinker:
What's the best way to downgrade Magisk to 15.1? Can I just flash the old zip from twrp or should I first uninstall or do something else?
[Magisk] thatOneWeeaboo:
You might want to uninstall it first, then flash the old one
[Magisk] jhill110:
Deleted
[Magisk] Didgeridoohan:
"Running post-fs-data.d scripts" and "Running service.d scripts" always show in the log. If the actual scripts runs it'll be listed underneath.

Have you given your scripts execution permissions?
[Magisk] DiamondJohn:
Yes.

I have even had them at 777. The owner is root
[Magisk] DisloyalRock:
Try reinstalling magisk from 0, so, reset your cellphone to factory version (with the properly tuto) and then try to flash it again. This happen to me yesterday and do this and now it works.

Same with the camera, it doesnt work, re install everything. Cheers!
[Magisk] Wolfcity:
[MENTION=4667597]Didgeridoohan[/MENTION] I own a Moto G 5 Plus (potter, also reteu) since a few days and I want to root it with Magisk. I was on a Moto G 2014 (titan) before and it was working well with magisk 14 on Aosp Extended 7.1.2.

I heard about the flawed implementation of f2fs so that some Moto devices can't mount the Magisk image properly.

Hence I have three questions:

1) Is it necessary to flash the no-verity-opt-encrypt-5.1.zip as described in the rooting guide for my device or am I right that Magisk handles that by itself?

And if yes since what version is magisk able to do that? I would like to try it with v14 and maybe update later.

2) Have I to flash a custom kernel right from the start because of the f2fs implementation or could I try it with the stock kernel that maybe doesn´t have that issue?

I know that I could reformat it but I haven´t done that before and I´m not sure if something could go wrong that way.

3) Regarding to the questions above should my way look like this:

- unlock bootloader

- flash or boot into twrp

- flash magisk

optional:

- flash custom kernel like elementalX

It would be nice to handle the procedure so that I can receive future OTA´s. I will flash a custom rom on the long run as usual but first I want to check out the stock rom.

Thx in advance.
[Magisk] spiritforme:
Why I can't run this application? After check rooting, the application exit
[Magisk] AndrOmega:
root is not hidden properly on your device.

magisk cannot guarantee that work with all apps.

it looks this app is smarter than magisk

:highfive:
[Magisk] jasio2k:
Device: Oneplus 3T

Os: RR-5.8.5

Magisk version: 15.2

Issue:

Getting random system hang and unable to install any module (getting error /data/magisk isn' t setup properly!) solution was installing module F2FS_Loopback_Bug_Workaround. This problem only happens if /data partition using file system f2fs

info from module:

Some kernels from devices with F2FS-formatted data partition (i.e., Motorola) have a bug that prevents loopback devices (.img files) from being mounted read-write. It limits systemless modifications that can be achieved with Magisk.

- This module works by moving magisk.img to the cache partition (EXT4) and linking it to its actual location (/data/adb or /data). The other half of the process consists on automatically recreating magisk_merge.img shortly after boot and handling it the same way as magisk.img.

- With this workaround, a patched kernel is dispensable.

- Cache partition's size is the only limiting factor -- and that's pretty much self-explanatory.
[Magisk] veritas25:
Device: HTC U11

Rom: ViperU 2.1.0

Magisk:v15.2

Magisk Manager: 5.5.3

I cannot get adaway to work... it never asks for root access and just hang... never had issue with adaway and magisk before. After I did a clean install of the rom and update magisk to 15.2. it happens... I think it is okay in 14.5 which comes from the rom...Anyone else experience the same issue? thanks
[Magisk] jhill110:
Search this thread. There's plenty of info about the issue.
[Magisk] RASTAVIPER:
This have been asked many times during the last weeks, but I couldn't find any specific reply either.

If anyone has something any idea about how to get rid of this permanent check, i believe it will be useful for many people.

Also, is it normal that the 2nd Preserve Dm-verity is Off and I still get during boot the dm warning message?
[Magisk] veritas25:
Thanks! Just saw it
[Magisk] DodoGTA:
1) You're right

2) I highly recommend to flash it

3) Yes
[Magisk] Telperion:
This is probably very simple and I've searched, but it uses such common terms that I'm having a difficult time finding relevant results.

I'm creating a module that places a file in /sbin/, how do I accomplish that in the config.sh? It's easy enough to add things under /system/ but I'm having a difficult time figuring out how to do that in the module.
[Magisk] Äptiva:
Device? Rom? Kernel version?
[Magisk] Thumaroil:
Same here. Moto G 1st on CM13.
[Magisk] DaDiDo:
I am having the same issue , i am using "[MM 6.0.1] AOKP-ROM" link , i also had yesterday this rom "[ROM][6.0.1]Temasek's CyanogenMod 13" link , and i followed the instructions step by step without any mistake but both rom give me the same error , the turn off toggle doesn't work even thought root access is granted and also the Safetynet doesn't pass.

can you please help me ?

*Safetynet screenshot attached.
[Magisk] fak3rx:
I don't know what to do, i already try alot of things. Someone can help?

Asus Zenfone 2 - Stock Version (5.0)

SuperSu 2.76

and all Magisk Itens
[Magisk] DaDiDo:
i think Magisk doesn't work with Supersu , so you need to open supersu do a complete root delete then flash magisk and phh super user in custom recovery then re-install Magisk and Phh super user (from market) i think that should do it for you
[Magisk] fak3rx:
Thx for help, i used Phh's in first time, but still show the same error.

"Root Improperly Installed"

:(
[Magisk] Syoenth:
I'm using a Samsung S3 I9300 and Beanstalk 6.20 (CM 13.0 based ROM)
[Magisk] Iceyogurt:
Does v4a work well through ordinary installation?

Viper4android magisk module works perfectly on my device, OnePlus 3 Oxygen OS, when SELinux enforced. But I'm not using the zip in the OP since deep_buffer removal is needed on my device. Maybe you should try to remove or disable deep_buffer as well.
[Magisk] rockerdudelive:
ok I'm learning how to do this stuff as I go. I think I got the logcat, but I'm really just looking for tutorials and how to videos because I am in no way a developer or anything like that.

I also put it in a zip file because the txt file was bigger than 512k and xda won't let me upload it.

edit: I think I got the boot from the original rom I flashed and then also extracted the boot.img with adb after I flashed magisk
[Magisk] westeight:
I also got that today. Twice. Wondering what changed... :crying:

Weirdest thing of all is that SafetyNet is still fine and I can add and remove cards from Android Pay.

Merchant end perhaps?
[Magisk] Iceyogurt:
Thanks for your report. I encountered the similar trouble when trying to adapt arise numbers as a magisk module. It seems our method is a little different. I just made a copy of build.prop, adapted the setprop commands and added them in the new build.prop.

Unfortunately, my device stuck at the boot animation and the mount process just stopped during boot according to the magisk.log.
[Magisk] igoticecream:
Ok I finally know WHY magisk corrupts some LG Kernels leading to "fastboot started mode" bootloader error.

This line fails and continue the execution

$BINDIR/bootimg-extract $ORIGBOOT

It wont extract the boot image and the script will repack an empty image causing this error. i ran this command and got "Unknown ramdisk type".

[MENTION=4470081]topjohnwu[/MENTION] How can i fix this? may i send you the boot.img to take a look?
[Magisk] peeweew:
Noob question.

1. Before installation, does 100% stock mean fresh ROM install? Or will it be okay to just uninstall SuperSU/Xposed then proceed without reformatting the system.

2. Magisk Manager toggles Root Access on/off. Since Xposed is systemless also, does that mean the modules would work even though Root toggle is off in Magisk Manager?

TIA!

P.s Sorry for the noob question.
[Magisk] Captain_Throwback:
For the people having issues with the root toggle turning itself back on:

Assuming you have unrooted your device properly prior to installing Magisk, etc. (I hear [MENTION=4544860]osm0sis[/MENTION]' unSU zip works well for this if you have system root), then your issue *may* be related to Busybox. If your ROM comes with Busybox pre-installed, it may be causing a conflict with the Busybox that comes prepackaged with Magisk.

If you've manually installed Busybox on your ROM, try uninstalling it and seeing if the toggle works properly. Or, if you can remove the ROM Busybox install, see if that helps. Just another idea of something to try, since I keep seeing the same posts over and over again...
[Magisk] Artim_96:
1. You have to at least restore your boot.img. if you had already changed anything in /system (like root, XPosed) you need to at least restore your stock system too... For most devices the easiest way would be to restore the whole ROM then
[Magisk] pharmdeon:
I have a question ... I have tried to search the thread and did not see an exact answer. Will the uninstaller listed in the OP remove PHH SuperUser mentioned in the second post? (this one phh's SuperUser 17 (Magisk Version) (2016.8.20))?

Thanks
[Magisk] igoticecream:
Some kernels are compressed with lz4... maybe the root of this problem?
[Magisk] npatelli:
Well actually, pokemon go isn't working too ^^'

It's the normal version of xposed, v86.5 (systemless by topjohnwu)

I also tried safetynet playground, the request fails.
[Magisk] Syoenth:
Well, I ended flashing a ROM with Cyanogenmod 12 and phh's supersu and Magisk work, but I really wanted this works on Cyanogenmod 13 :/
[Magisk] DaDiDo:
Thank you so much , i thought my phone was unrooted since it didn't have SuperSU installed, but it was , right after flashing unSU script from "osm0sis" , the root toggle off worked fine in Magisk.

UnSU thread link:

http://xdaforums.com/showpost.php?p=63615067
[Magisk] DodoGTA:
What exactly are you trying to do?
[Magisk] Didgeridoohan:
Hm... Not sure then. Does modules using post-fs-data.sh or service.sh work? Could you upload your scripts?

If you wan't to retain OTA capabilities you're going to have to keep the stock recovery (so only boot TWRP). You'd also need the completely stock boot image which means you'd have to somehow reflash the untouched boot image before taking an OTA. Take a look at the OTA tips in the official documentation.

Try to also hide the Manager (there's an option in the Manager settings). You might also have to clear data for the app since some apps "remember" that you're rooted.
[Magisk] m7md_ramadan:
I can't install any modules

Magisk v15.2
[Magisk] jenslody:
First question that comes in my mind:

did you add it to the hidelist in MagiskManager settings ?

If yes, try what [MENTION=4667597]Didgeridoohan[/MENTION] writes:
[Magisk] alchokem:
Magisk Xposed Framework Module Conflict with TWRP Manager

If one installs the Xposed Framework (SDK 23) 88.0 module, created by rovo89 and wanam within Magisk Manager, this module breaks the application, TWRP Manager. Upon startup, TWRP Manager remains in an endless loop indicating it is "checking settings and root". Uninstall this module and the problem disappears. Any chance, this problem can be corrected? I am running Magisk Manager v5.5.3 and Magisk v15.2 on HTC One M8 running Marshmallow 6.0.
[Magisk] Macmoc16:
my oneplus one on linageOS 15.1 go in bootloop after flash magisk 15.2 whitout error, but I can not understand why. ( i wipe system, cache and dalvik)
[Magisk] RavenII:
Huawei H1611

Android 6

Magisk Manager: Latest

Magisk Installed v14.0

If I try to update to v15, v15.1, v15.2 it all = bootloop....am I missing something?
[Magisk] Abraham_T.:
i found a way and dont know if its the correct way but i never face any issue after doing it

waht i did is check the preserve force encryption and dm-verity and hit install and select the recommended (the last one)

reboot done
[Magisk] RASTAVIPER:
And by doing that did you manage to get rid of the annoying dm message during booting?

Unleashed by my rooted OP3T in 8.0
[Magisk] Abraham_T.:
no messages all good

but i repeat i did it just like that i dont know if this is wright or wrong

but everything is working fine i have no issues

maybe it will not work with u as me

i am just a random guy
[Magisk] DiamondJohn:
Big "hmmmmmmmmjmMMMMmmmm..." as for some unknown reason, it just started randomly working:confused: Thanks for your time.

Because I rely on my boot scripts, I tried using KA to run my boot scripts and a few reboots and manually running the scripts from adb later, after one of the reboots, I noticed all my logging (from my boot scripts) just magically were there :eek:. So I undid my KA changes, and rebooted again, and it all seems to be working now:confused: I do not know of any changes I made specific with Magisk between when it wasn't working and when it did work.

Also, I did not mention, the very first few reboots, any scripts I placed in service.d and/or post-fs-data where replaced/overwritten with files of the exact same size but blank characters :silly: (it stopped doing it before I got a copy, so not sure which character exactly, and this actually happened in a previous version as well, but I couldn't find that post)

So in short, its now working, for reasons unbeknownst to me.:victory:

As its now working, I don't think testing the .sh version will provide any further clues. However, I build my own ROMs so expect to re-flash and reinstall Magisk again, so is there anything specifically I could do to attempt to help get to the source of this behavior if it starts happening again? From memory, the last time I had the blank file replacement issue, I just changed from post-fs-data to service.d and it stopped happening. But after this last experience, maybe it was actually just somehow related to rebooting the phone or something. And yes, I know the quote "Insanity: doing the same thing over and over again and expecting different results." :rolleyes:
[Magisk] jamy015:
Magisk v15.2 and f.lux still aren't playing nice. When I enable f.lux, after a while my phone starts acting so weird (home button, app switcher, lock screen stop working correctly) that I need to restart my phone. Everything worked perfectly under Magisk v14.
[Magisk] hungragezone:
I am using MIUI 7.12.28 (latest) on Redmid 3S and I can flash magisk 15.2 using TWRP normally (no error message) but when the phone restart, i go to magisk manager and it shows that magisk is not installed

I tried flash many time but the same problem happen

When i tried to flash magisk 14.0, it works. what is the problem here o_o
[Magisk] QkiZMR:
I don't know if Magisk causes reboot of Android framework but after flashing 15.2 when I try to unlock phone from fingerprint reader Android framework is restarting. This happened from time to time with random manner. I don't have logs from Magisk because I need to reboot phone completely after restart of Android framework. I can't run anything because every app keep crashing. Only full reboot helps. Is somebody have same issue with fingerprint reader reboots?

Sent from Moto G (5S) Plus via Tapatalk
[Magisk] Fry-kun:
15.2/5.5.3 keeps patching DTBO after some reboots, please fix!

Settings for encryption & Preserve AVB... are both checked

Pixel 2 XL, latest stock 8.1.0
[Magisk] plastikwar:
Magisk 14 and LineageOS

I have HTC 620g. I can use only custom recovery (not twrp). Also I have custom rom Lineage OS 13 (Android 6). When l'm trying to install Magisk 14 by recovery, I have a error - unable to detect boot image. But I found a desicion - unzip my custom rom, take boot.img and patched by Magisk Manager. Then replace boot.img and zip rom again

But it patched only last ver. 15.2 and saferynet doesn't work. How can I patched my boot.img with Magisk 14? I have zip with Magisk 14, but don't know how it patched without Magisk Manager.
[Magisk] F4JL0:
I updated Magisk v. 15.2 and I got same error as when I updated to v 15. 1.

Phone is working but root isn't. When I try to open Magisk Manager it stuck at mask logo and nothing happens

My phone: SONY Xperia M4 Aqua

Android version: 6.0
[Magisk] ante0:
Ok. Found one problem with Mate 9. Since I have a RAMDISK partition and a KERNEL one, when it does the hexpatch it does it on the ramdisk (There is an empty Image.gz in there, that bootloops if I remove it, that gets the hex patch).

So I extracted Image.gz and then zImage from that and applied the hex patch manually. Flashed both ramdisk (pre-patched with magisk) and kernel. Now phone doesn't recognize ramdisk or kernel, so it goes directly to a white error/rescue screen with an error in boot, can't load. or something like that. When I flash back stock ramdisk it complains about recovery, can't load. So I flash back kernel and phone boots up.

I can't figure out what's wrong though. Even if hexpatch was applied to my kernel partition it would still fail to load.

I believe Pixel had a similar bug?

Edit: it boots fine with just the patched kernel. If I flash magisk pre-patched ramdisk it just reboots before bootanim.

This is Mate 9 Oreo.
[Magisk] sandaljrpit:
Hey :) ...

I use application ” Tcash wallet ” is unsuccessful & root detected. I’ve done according to the turorial but still detected.

any suggestion ?

My phone Xiaomi MI4 Lte.
[Magisk] jenslody:
What exactly did you do ?

Add the app to the hidelist in MagiskManager ?

Hide the manager itself (from its settings)?
[Magisk] Artim_96:
If you hid everything but it still fails then it's possible that it uses some root detection method that can't be circumvented (yet). That's especially the case with banking apps
[Magisk] QkiZMR:
Again system kills android framework. Now I have logcat, attached. I switched to 15.1 if problem persists on lower version.
[Magisk] Xtriel:
Problems with mounting the system

Help Me!:eek:

My Magisk does not mount the system in RW, when the system changes, the smartphone hangs. Smartphone BQ Aquaris X Android 7.1.1 AOSP
[Magisk] teddy0209:
You already have magisk, why would you want to mount system rw?
[Magisk] dardack:
Did anyone run into Android Pay not actually working at a register after 15.x? I updated to 15.0 when it first hit, saftenet passes. Went to store, android pay opened, but when I went to pay it said Android Pay can't work on y our system, please unroot or something like that.

I went back to 14.6. I have a Pixel XL. Was it just a fluke? Should I update to 15.2 and try again?
[Magisk] Xtriel:
Сan remove system applications, many applications also need a RW system. I want to know this error? Or can this be fixed?
[Magisk] teddy0209:
There is a debloater module which you can use for that...
[Magisk] Xtriel:
Yes, that's all I know and use, but still I do not understand this error or not? On other smartphones the same way, right?
[Magisk] teddy0209:
I don't know exactly as I never mounted system rw, ever since I used magisk/systemless... I need it untouched for taking ota....
[Magisk] Xtriel:
I hope I will get response, thanks
[Magisk] Didgeridoohan:
There are normally no issues mounting /system rw with Magisk. How are you doing it and where's the logcat?
[Magisk] Xtriel:
Use root explorer to mount the system, after the smartphone just hangs. Hangs after any changes to the system or any app changing the system . The log I will do in the near future.
[Magisk] Yudh:
Guys please read the readme file(I made it previously) from this link https://github.com/YUDHPK/BackDoorRootScripts to help me

the above method worked properly for magisk-v14.0 and magiskmanager-v5.4.0 apk

but now the files name have changed in magisk-v15.2 so the above method doesn't work what should i do???

if i update magisk to 15.2 from the app itself using direct install method(both checkboxes ticked) i get a black screen first warning me about different operating system installed and then when it moves forward a black screen asking me about my password (no password works including email's, my lockscreen's or 12345678)

(log attached )(i recover from this state by flashing OP20 zip placed in my internal storage via stock recovery )

Device details (:(previous method worked with the same)

OnePlus3T

Android Oreo, OxygenOS OpenBeta 20 with a locked bootloader and stock recovery

with the attached modified zip i am able to use magiskmanager-v5.5.3.apk with magisk-v14.0
[Magisk] Xtriel:
I can not write log, smart phone hangs :eek:
[Magisk] Didgeridoohan:
The paths for Magisk have changed with v15+, yes. Instead of /data/magisk it's now /data/adb/magisk. I guess it should simply be a case of changing the paths in the scripts...

---------- Post added at 16:43 ---------- Previous post was at 16:42 ----------

Use a computer and adb.
[Magisk] paras19b:
Is there any screen recorder or magisk module which records screen as well as internal audio(not mic)
[Magisk] Xtriel:
https://drive.google.com/open?id=1xApAenBQ-RBnvC2wk-OfQI9MzPBExzXA
[Magisk] Yudh:
No it doesn't work that way . I already did what you said

But while trying to run

./magiskinit --createimg magisk.img 64

OR

./magiskinit

I get segmentation fault error

[emoji1308]
[Magisk] plastikwar:
Hello, dear friends!

Is there any way to patch boot.img on the computer or on the phone to the suitable version of Magisk? Magisk Manager updated boot.img only to version 15.2. This is not what I need. I need version 14.0.
[Magisk] Didgeridoohan:
Why have you changed the command to magiskinit? It's magisk that creates the image.
[Magisk] Yudh:
Because there is no file named as magisk

[emoji1308]
[Magisk] Didgeridoohan:
You probably should read through the source code to find what you need. Example:

# Extract magisk if doesn't exist
[ -e magisk ] || ./magiskinit -x magisk magisk
[Magisk] jhill110:
You can find 14.0 in the official magisk thread at the bottom of the first post here:

https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

EDIT: Also download the Uninstaller and flash it before you flash 14.0 if that's what you're going to do.
[Magisk] Wildchild0369:
Why???? stay in moto zplay aex rom 7.1.2, magisk 15.2 :crying:
[Magisk] m_s_ifland:
I noticed the 15.2 update has broken Titanium Backup. Getting the "not enough space error" again. I went back to 15.0 and everything worked fine on TiBu again. Thanks for your hard work.