yashsingh1/xdaforums huggingface dataset:
[Magisk] ktmom:
Can you just fastboot flash the stock image from your computer?

The stock backups are usually at /data/magisk_backup_{sha1}/boot.img.gz
[Magisk] salomaoa:
Yes I can flash the stock boot. However if I do that I Will loose root.

There is no magisk folder under /data folder. Is there any way I can put my stock boot img file there?

Enviado do meu HD1910 através do Tapatalk
[Magisk] gcrutchr:
I have root on my SM-T295 A8 tablet!!

Attached boot.tar file is for XXU2ASL3 only.

T295-Magisk-AP.tar

Okay, after multiple failed attempts, I read about a method to root my T295. It did not work!! But, I decided to just use Magisk Manager on the boot.img file only. The resultant file would not flash - it will fail. The original boot.img & recovery.img files are 65,536K bytes each. I had to take the Magisk modified boot.img and overlay it onto the original boot.ing file. I did the same for the recovery.img. Then the files would flash successfully. The first thing after booting was to check Magisk Manager. It showed I have Magisk 20.3 installed. So, I tested this with Root Explorer. I did have root!!

If you are going to try this, you need to unlock your boot loader, I think. I have not tried this with a locked bootloader.
[Magisk] wangdaning:
If you want to do the OTA method and their is not backup of stock boot, flash stock and reboot then reroot with magisk. It should create a backup of stock when you reroot. Then you can go back to the step where you got stuck. You will not be able to manually insert a backup boot onto the device, magisk must create it.

You should be able to put your boot.img in you phone storage, click install magisk, select patch boot image, select saved image, and when it patches it a backup should be created.
[Magisk] tau.gi.mo:
Hi,

is there any way to get Magisk Logs from before a restart or alternatively to gather Magisk Logs without root access?

Magisk 20.3 seems to crash randomly over night on my device (Magisk Manager shows Magisk not installed until I reboot) causing the device to be super laggy (like 1 Minute to even open Magisk Manager or another app). I am currently on Android 10, Havoc Rom on a Redmi Note 5 Pro.

Thanks!

tau.gi.mo
[Magisk] JimZiii:
I was asking for help creating symlink to my sdcard and celebrated a bit early. I managed to create it in root explorer but it only works in root explorer and only root explorer recognizes the symlink.

All other apps fail when trying to create a symlink and only think that works is cloning the path which takes about space on both drives.

I've read that i need global namespace for this to work but I'm not sure I'm able to change namespace successfully.

When the namespace is set to inherit and i run su in terminal emulator it shows the same starting line, HWFRD:/, which is my phone model, of course it changes $ to #, indicating i got root.

But, if i change namespace to global or even isolated it changes from the regular HWFRD:/ $ to HWFRD: (unreachable) #

So it's still giving me root on global and isolated but it also says (unreachable), so it's something wrong or how do i fix this?

I assumed it shouldn't say unreachable so i tried re-flashing magisk with global set and i also tried reinstalling the terminal explorer but I'm still getting the same result
[Magisk] martyfender:
This magisk module created by [MENTION=4487388]jcmm11[/MENTION] solved the unreachable message in the root terminal for me.

https://xdaforums.com/showpost.php?p=80946661&postcount=2454
[Magisk] seemebreakthis:
Thanks. Next time iI will try rootbeerfresh if it starts having issues again.
[Magisk] AjaySp:
Anyone use play station remote play 3.0.0 it still detects root even when its hidden in magisk manager i have system less xposed installed i tried disabling it but still the same . Any suggestions?
[Magisk] ktmom:
That's usually due to memory management issues created by the ROM. If your device allows you to pin the manager in the recents list, try that.

Take a look at dontkillmyapp.com

Scroll to the bottom of this page: https://www.didgeridoohan.com/magisk/MagiskRootIssues#

There are many ways an app can detect root. This page had a long list of possible issues.
[Magisk] J.Michael:
SM-T290 rooted

Following the advice of [MENTION=1826556]gcrutchr[/MENTION], I was able to install Canary Debug 276 on my SM-T290 Galaxy Tab A 8" 2019 (Android 9)

https://xdaforums.com/galaxy-tab-a/how-to/sm-root-t4050329

---------- Post added at 01:21 ---------- Previous post was at 01:00 ----------

Why does the Canary Debug build identify itself as "276", with no apparent reference to the version numbers I'm used to?

I thought Magisk Manager was up to 7.5.2, so I expected Canary to be 7.5.2 or 7.5.3.

And what is that 8-digit number? (Like "ce7cb1ee".)
[Magisk] wangdaning:
The 8 digit number is the last commit from to github before the build. The other number not so sure about, so I will not look stupid saying what I think. Also, probably better to put this in the canary thread not the general one.
[Magisk] blumenkasten:
After flashing the patched bootloader-image of my Blackview BV9800Pro the phone doesn't accept the bootloader. There's an error with verified boot.

Is there an option to disable verified boot or correcting the image-signature?
[Magisk] zgfg:
You patched and flashed the bootloader, not boot (or recovery)?

Maybe it is a specific procedure for your phone...
[Magisk] wangdaning:
Could also try to patch with verity disabled, not recommended in most cases though.
[Magisk] blumenkasten:
Magisk patched the boot.img. But I have to install it via PC because there's no custom recovery available yet.
[Magisk] AjaySp:
So i was able to hide magisk manager. And the ps4 remote play is working how ever i repack the app and the canary apk with the changes ui is always switched to old ui. Is there something wrong I am doing?
[Magisk] blumenkasten:
There's no difference. If I disable AVB 2.0/dm-verity the verified boot error occurs too. :(
[Magisk] ktmom:
Maybe this thread or the vbmeta.img in the troubleshooting tips at the end of this post might help.
[Magisk] wangdaning:
Not to distract from the previous poster, but is magisk no longer taking submissions for the repo or am I just blind?
[Magisk] J.Michael:
That vbmeta.img is the same as the one produced by Magisk, except that it's been padded with zeroes to 4K.
[Magisk] Didgeridoohan:
No, that's correct. [MENTION=4470081]topjohnwu[/MENTION] is considering making some changes to how the repo works, so he's closed submissions for now.
[Magisk] wangdaning:
I have a module for mainland Chinese users to enable LTE on pixel 3 devices (maybe Pixel 4, too), but it can wait.
[Magisk] J.Michael:
worked in spite of SECURE CHECK FAIL: vbmeta

When I succeeded in installing Magisk on my SM-T290, it was in spite of the "SECURE CHECK FAIL: vbmeta" message on the tablet.

The instructions emphasize the importance of going directly from "download firmware to tablet using Odin" to "wipe data/factory reset in recovery". They don't explain what horrible things will happen if the tablet reboots to Android without that "wipe". I don't have the stomach to try to find out. I usually assume that if the tablet says FAIL, nothing got flashed. For no particularly good reason, this time I ran the download twice, then followed the instructions in spite of the two FAIL messages. The tablet took a long time to boot. Once it had booted, there was no Magisk Manager. When I installed the Manager, it was a pleasant surprise that it finally said it had other things to do.

TL;DR Once you've committed to following the instructions, even if the tablet displays an error message, it might be a good idea to follow the rest of the instructions anyway: It might have successfully flashed.
[Magisk] PoochyX:
Good for u Michael
[Magisk] blumenkasten:
The first solution doesn't work without an available custom recovery and the second didn't do anything. There is no vbmeta partition but metadata. Flashing this with the vbmeta.img makes no difference, it doens't disable dm-verity. :crying:

Is anyone out there who succesfully installed Magisk on an BV9800 Pro? :confused:
[Magisk] blackroseMD1:
Edit: Question answered.
[Magisk] xunholyx:
The model number won't tell you.

Ask for the IMEI, then enter it in Verizon's IMEI checker that you can find here

If it comes up as "NON-VZW", then you can unlock the bootloader and root it.
[Magisk] twinsq:
install magisk 20.3 got Unsupported/Unknown image format on oneplus 6 (android 10) .

How to solve this problem ?
[Magisk] dcarvil:
This might help. https://github.com/topjohnwu/Magisk/issues/1634
[Magisk] noooooo:
So, I'm asking for help as i cannot make google pay to work with magisk. I've hidden google pay, google play services and the bank app of the card i want to use. I've deleted these app data from the settings, i've hidden magisk trough the menu option. But when i try to even open google pay it closes. There is a button to add the card to google pay from the bank app, but after the setup a google pay screen tells me that it was unsuccesful as the device is rooted, any help?

BTW, i'm on a pixel 2 xl updated at february patch android 10
[Magisk] rodken:
You might want to try this method.
[Magisk] noooooo:
Sorry but how can a build prop editor help me?

I mean, my device passes safety net with no problems, it is just gpay that detects root
[Magisk] Wolfcity:
That isn't just a build prop editor, it's a module to change your device's fingerprint (beside other functions). Maybe changing the fingerprint can help you as you tried almost all other things (hiding manager,hiding gpay,services, clearing app data).

Maybe just give it a try, you can revert the changes if it doesn't work as it's systemless.

You're passing safety net but there must be something that triggers gpay.

You can also take a look here:

https://www.didgeridoohan.com/magisk/MagiskHideMore
[Magisk] beardymarrow:
It fixed this exact same issue for me.
[Magisk] dcarvil:
This method worked for me. It is for older versions of Magisk and Android, but I just did it successfully on Android 10 and a recent version of Magisk.

https://xdaforums.com/apps/magisk/magisk-google-pay-gms-17-1-22-pie-t3929950
[Magisk] noooooo:
On a last try before looking at the fingerprint module i was able to solve using this two magisk modules, and enabling the card from google settings page, and not the google pay app itself. Anyway, thanks to everyone that helped, if this method stops working i already know ehre to look at!
[Magisk] lieuliau:
I'm using Pixel XL with stock android 8 rom. I flashed Magisk 20.3, enable Google Play Services in Magisk Hide. There is no other modules installed. I also use random magisk manager name. But I checked safetynet, basicIntegrity and ctsProfile all failed. Any way to fix it?
[Magisk] varadinum:
Hello I need your help

I rooted my phone with magisk. Now I have a new update but it cannot be installed.

"the system has been changed unauthorized" (OTA Update Samsung) Samsung Galaxy A9 2018

How can i install it? I want to keep the data and applications. Is it possible? Everything is deleted with Odin?

Can someone help me? Or is there a description for it?

Thanks in advance
[Magisk] siamak5561:
Hi

I have a Bank app that recognize phone rooted , I already putt this app in Magisk hide but still app finde phone is rooted and not work. any solution?

Latest magisk with latest magisk manager in Nexus 5x in Latest Lineage rom.
[Magisk] guest4711:
Did you hide Magisk Manager itself by repackaging it using a random name?
[Magisk] siamak5561:
No! how to do that?

other bank apps works well with magisk hide but this damn app not!
[Magisk] guest4711:
Magisk Manager - Settings - Manager - Hide Magisk Manager
[Magisk] siamak5561:
Thanks Bro, Works very well :laugh::D
[Magisk] PoochyX:
Good for you
[Magisk] JudgeDread11:
I'm not familiar with Samsung, but on some devices it's enough to uninstall magisk from manager (don't reboot) run your update (don't reboot) install magisk again from manager then reboot. You should still have your after the update and your data intact.

If that doesn't work try to uninstall magisk from manager, reboot and then update. You will need to flash magisk after again manually put you won't have root.

If that doesn't work, something else is changed our some protection got tripped. In that case you'll more likely find answers in your device thread.
[Magisk] Firdhaus81:
Hi may i check if my A9 Pro A910F/DS is able to do a magisk root? Any help will be appreciated.. And im on android 8.
[Magisk] strat1959:
is it possible to fake the value of "development_settings_enabled" from particular applications? or for a specific period of time?

its for knowing that whether user has enabled development settings.

there's a financial app that checks that status and won't let me access it. Is there a workaround? [MENTION=4470081]topjohnwu[/MENTION]
[Magisk] nexthak:
Bugreport Magisk, xiaomi Redmi 6A

Hello, I want to contact the magisk developer. I have a redmi 6A smartphone. We have a defective root that magisk issues. All system changes made using root magisk

disappear after reboot. This is a common problem with this model. On stock and custom firmware.

Android 8 and 9. Can this be fixed?

I am ready to give all the information on this issue.

I am writing through google translate.

Please help me!

[MENTION=4470081]topjohnwu[/MENTION]
[Magisk] wangdaning:
You could try installing with AVB/dm-verity disabled. I had to do that on my Pixel 3 with android pie to modify system.
[Magisk] nexthak:
I can change the system, but after a reboot everything is reset. I do not think that AVB / dm-verity disabled will help, I'm not the only one with this problem, all owners of this line of smartphones

[MENTION=4470081]topjohnwu[/MENTION]
[Magisk] philip_rhoades:
Pixel2XL - lost root after OTA update to Android 9 - is there quick re-root?

People,

I didn't get a response to this previously:

"I saw in some posts that Magisk is supposed to allow for an OTA update? Anyway, I probably should have been more cautious but now I have lost root and want to get it back - as well as update to Magisk 17.1 (which has been downloaded to the phone already) - is there a way to do this without starting the rooting process from scratch?"

I have since had a couple more OTA updates but I still want to get my rooted phone back - when I boot into Recovery Mode now I just get a dead android picture with a red triangle and exclamation mark . . where do I go from here? I have downloaded the latest Magisk but I am not sure what the simplest method is to get root back from here.

Thanks,

Phil.
[Magisk] garylawwd:
What kind of device is it at least?

Is it legacy recovery or does it have fastboot also?

If it has fastboot then twrp is probably your best bet.

Just boot twrp from fastboot (you will need a PC)

fastboot boot twrp.img

Then just flash the magisk zip in twrp and reboot
[Magisk] rodken:
+1

---------- Post added at 11:17 AM ---------- Previous post was at 11:08 AM ----------

Reflash TWRP with this method. If you are a Mac user, no need not to worry about drivers, but you need to download and unzip the Mac fastboot package. Also, place the file TWRP.img in the same folder. You can also follow this guide for Chromebooks.

---------- Post added at 11:18 AM ---------- Previous post was at 11:17 AM ----------
[Magisk] Firdhaus81:
Any advise?
[Magisk] rodken:
Please refer to this.
[Magisk] Firdhaus81:
Not sure if this helps.. Ive tried. But which one is legit
[Magisk] Didgeridoohan:
I would start with the official installation instructions.

https://topjohnwu.github.io/Magisk/install.html

If you can't get those to work I would search for more info in your device's section here on XDA.

https://xdaforums.com/samsung-a-series

I believe you'd need Xposed/EdXposed for that. Can't give more insight than that unfortunately, since I don't use either.

Sounds like you're trying to edit the magic mask that Magisk mounts then doing systemless modifications to the system partitions. Does it make any difference if you enable Core Only Mode in the Magisk Manager settings (don't forget to reboot after enabling/disabling it)?

Just for info, the dead Android is your stock recovery. Apart from the advice you've already been given you can also use the official installation instructions to get up and running again:

https://topjohnwu.github.io/Magisk/install.html

It could also be a good idea to take a look at this, for future reference:

https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
[Magisk] Wolfcity:
Often the solution is to toggle magisk hide on/off.

Sometimes this has to be done after every reboot so you can use a script

#!/system/bin/sh
sleep 120
/sbin/magiskhide --disable
sleep 1
/sbin/magiskhide --enable

place in data/adb/service.d and give it 755 permission.
[Magisk] Davidoski01:
Ho guys! I'm starting to approach the rooting, so I have to ask some questions about it :)

1) Do I have to install a specific Magisk version which is exactly suitable for my device? (I mean like ROMs and TWRPs)

2) Is It true that ROM updates delete the root?

Thank you in advance :)
[Magisk] Firdhaus81:
Thank you for the links. Ill try it although it seems that tgis method i have tried but failed as it loops my phone after installing twrp. And secondly somehow the zip files that i place in my internal folder for flashing disappears. I cant find it there..
[Magisk] IndoD:
Help Please

Hi,

I wanted to root a Padfone S with Marsmellow 6.0.1

I followed this instruction https://xdaforums.com/android/help/padfone-s-x-android-6-0-to-root-t3502680

But I could not get Super Su installed. TWRP 2.8.7.8 seems be working.

As I could not install SuperSu with that instruction I tried to install the latest Magisk with TWRP. But after reboot my phone get stuck at the bootscreen. After that I tried to use the uninstall.zip. But that did not help either. Then I tried to install the stock software from Asus, but that did not help either.

Can you help me please?
[Magisk] ktmom:
That sounds like a secure settings value. You probably could write a script to change the value. Search for writing secure settings. If you are a Tasker user, you probably can do it from Tasker.
[Magisk] ktmom:
You can not install one to solution on top of another. That is probably why Madison didn't work - though there would have been an error that the boot.img was already modified. You must return to an unofficial condition before attempting to change root methods. The uninstall script requires the device bringing in a known state, which yours wasn't since you flashed Magisk on top of SuperSu.

Restoring to stock is beyond the scope of this thread. You would most likely get the best support in the Padfone X and S Q&A, Help & Troubleshooting forum. You may find a thread there that already addresses the problem you are having.
[Magisk] IndoD:
Thank you for your reply.

I did not got SuperSu installed. I checked after I tried to installed if Supersu was installed and my phone was rooted. But it wasn't. Also in TWRP it said I was not rooted and with every reboot it asked if I wanted to install SuperSu. So SuperSu was not installed. I did not managed to do so. That is why tried magisk
[Magisk] ktmom:
Just because your weren't rooted, don't mean that SuperSu didn't modify things. More than that would require installation logs :good:
[Magisk] IndoD:
When I wanted to reboot TWRP is saying SuperSu is not installed. So I guess it has not been installed.

I have the logs, but cannot attach them here :crying:
[Magisk] Mcdan333:
On my Moto Z3 Play, I used the boot image patch method to install Magisk. Now I have Magisk Manager showing "Magisk is not installed". I get the following when I run magisk from an ADB shell, so it is installed and magiskd is running, but permission denied is not good. Any suggestions?

beckham:/ $ ps -A|grep magisk

root 1060 1 19356 1480 0 0 S magiskd

beckham:/ $ magisk -c

20.3:MAGISK (20300)

beckham:/ $ magisk --list

su

resetprop

magiskhide

beckham:/ $ magisk su ls

Permission denied

beckham:/ $

Problem solved. I had the Magisk app set to use SD card storage. Switched it to internal, everything is working fine now.
[Magisk] philip_rhoades:
Pixel2XL - lost root after OTA update to Android 9 - is there quick re-root?

The phone was mentioned in the Subject: "Pixel2XL - lost root after OTA update to Android 9 - is there quick re-root?"

Prints:

< waiting for any device >

. . but nothing happens . .

I notice that when the phone is normall booted and connected, "adb devices" prints:

List of devices attached
712KPNY1322463	unauthorized

but once booted into "fastboot" mode, no devices are listed - I have tried multiple cables, USB ports etc

---------- Post added at 05:36 PM ---------- Previous post was at 04:39 PM ----------

Using:

./platform-tools/fastboot flash recovery twrp-3.3.0-0-taimen.img

Gives:

< waiting for any device >

but nothing happens . .

Fedora Linux user .
[Magisk] wangdaning:
Are you sure you have the most updated adb/fastboot?
[Magisk] philip_rhoades:
Pixel2XL - lost root after OTA update to Android 9 - is there quick re-root?

Just got the most recent version for this exercise:

platform-tools/fastboot --version
fastboot version 29.0.6-6198805
Installed as /home/phr/android/pixel2xl/platform-tools/fastboot

If the phone responds to adb when it has been booted normally but not when it is in fastboot mode - doesn't that mean there is a problem with the phone?
[Magisk] NHNXDA:
Oneplus 7 pro 10.0.4, stock kernel, installed twrp mauronofrio, this works fine on its own with rom, but when I install magisk I lose wifi, it wont stay turned on & the cellular icons are showing no sim but data works.

I tried doing a network reset & this lost everything in network, couldn't access any sim settings, all were greyed out & still wifi wont stay on, toggles to on but after few seconds goes back to off.

Reinstalled OOS 10.0.4 with twrp, everything back working again.

Anyone else had issues, considering trying an older magisk.

TIA.
[Magisk] Firdhaus81:
Thank you.. Followed the steps and running magisk smoothly on my A9 pro SM-910F
[Magisk] billyt1:
Mine did to I jus flashed kirisakura kernel with twrp or franco Kern manager.

https://xdaforums.com/oneplus-7-pro/development/kernel-kirisakura-1-0-0-op7-pro-aka-t3933916
[Magisk] Firdhaus81:
Another issue is that i always get threat found as attached on the picture. It asjs to restart which when i do it will automatically boot to twrp and when i boot to system it comes back normal but starts the pop up again. Any way i can get it to stop?
[Magisk] Didgeridoohan:
Is that a built-in feature in your ROM or a separate McAfee app? Try adding the app/service to the MagiskHide list and also rename the Manager with a random package name and a custom app label (in the Manager settings).

More details about hiding Magisk and the Manager can be found here:

https://didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
[Magisk] nexthak:
Yes, you think correctly. But unfortunately what you suggested does not work. Everything is much more complicated. Without the help of the developer, nothing will work. All owners are suffering with this problem, and no one has found a simple solution.

Writing google translate
[Magisk] lieuliau:
I just try toggle magisk hide on/off, and also put that script in data/adb/service.d. But safetynet still fail both :(
[Magisk] marulamsamosir:
The last magisk not work for mandiri mobile app (https://play.google.com/store/apps/details?id=com.bankmandiri.mandirionline)

I'm using magisk v20.3 and magisk app v7.5.1
[Magisk] Wolfcity:
Ok, I'm sorry for that, very often this small action solves the problem.

Maybe take a look into this really helpful guide by [MENTION=4667597]Didgeridoohan[/MENTION]:

https://www.didgeridoohan.com/magisk/MagiskHide#hn_Passing_SafetyNet

A lot of good hints and pointers.

Next step would be logging the whole process (also the flashing). A good idea would be trying Canary debug which a) may solve the problem or b) at least provides very extensive logs.
[Magisk] Firdhaus81:
Hi Sir, thank you for the reply. Yes its an inbuilt feature. I did the renaming and added the service but it still pops up..