yashsingh1/xdaforums huggingface dataset:
[Magisk] mikeyb123:
Im using a galaxy A10 problem im facing is this, with magisk v19.3 i patched the firmware with magisk to get root, i then patched TWRP with magisk, everything has been working great without any problems, but with Magisk v20 alone without TWRP the phone boots fine i dont encounter any problems, but as soon as i flash TWRP i run into problems - i flash multidisabler format data ect phone boots up to optimizing apps, restarts then im stuck at the splash screen and wont boot... i have started all over again fresh, flashed stock rom then tried steps again still the same issue! Does anyone have any suggestions or has anyone had this problem? Any help would be much appreciated thank you.
[Magisk] ktmom:
Restore back to the "stock" boot.img or recovery.img as appropriate for your device, clear cache, reboot to make sure things work, then install Magisk 19.3. How to restore your device would probably be best supported in your device forum.

If someone with the s5e posted logs so the problem could be reviewed, maybe the problem could be addressed.

From just few posts ago..
[Magisk] ballerd:
Trying to get magisk canary working or magisk working with Samsung a10 exynos processor which system as root and is a A only partition device trying to see why twrp bootloops with this how would I grab logs device is rooted with magisk but twrp causes bootloop could I flash twrp then try boot and run dmesg or logcat to see the issue I don't how to pinpoint my issue don't expect spoon feeding or is there some changes I need to make in my twrp device ?? Thanks to anyone who cares and for your appricated time
[Magisk] ktmom:
With a system as root, non A/B device, you are installing Magisk into the recovery partition, right?

In that case, I don't think TWRP is compatible with Magisk

https://topjohnwu.github.io/Magisk/install.html#magisk-in-recovery
[Magisk] deejay7:
Magisk installation fails in Honor 3C

I couldn't install Magisk in my Honor 3C phone.

Custom ROMS tried :

[UPDATE][NOV]Lineage-OS14.1-H30-U10-Syed-Hassan

RR-N-v5.8.5-Jan2018-H30-U10-Syed-Hassan--Final

Different errors while flashing Magisk zip. Almost tried all versions of Magisk from high to low, all fails with errors. Versions 7,8,9 installs but Magisk manager won't detect them.

Errors while flashing Magisk zip:

"Unable to repack boot image!" next line of Repacking boot image [IMG="Error screenshot"]https://photos.app.goo.gl/2ccLzNaqQv8rBQje8[/IMG]

"unsupported/unknown image format"

What am I doing wrong? appreciate your input to move forward.
[Magisk] svetlio359:
Hi I have the same issue on my galaxy a50

What device you have and witch version of android you have
[Magisk] ISoreo:
Galaxy Note 4 run with Android 6.0 stock try to downgrade Magisk
[Magisk] svetlio359:
How to downgrade

Is there any specific way

To not brick the phone
[Magisk] ISoreo:
Downgrade of what? OS or Magisk if Magisk just uninstall latest version by using Magisk Manager then download older version (V19.2 or older) from Johnwu's Github then flash this zip by using recovery mode like TWRP or CWM
[Magisk] Vitmor01:
Salve o un Oukitel k7 pro 2019 ultimo che è uscito della k7 volevo sapere se c'è un metodo per mettere o vero o twrp recovery robot visto che quello che ho e originale ma quando avvio installazione di twrp o rom o magisksu non va a buon fine per niente .....Aiuto vi prego
[Magisk] imatts:
Any news on a Note 7 root workaround for Pokemon Go?

I'm using the Spring Userdebug/custom root script, so i dont think the standard SSU root for bootloader unlocked Note 7's would apply for us users with bootloader locked Canadian/US variants.

Any input is appreciated!
[Magisk] cubandanger05:
Sorry to hear that mate
[Magisk] matif525:
:p Thanks for your remind, Captain_Throwback!

I don't konw if Magisk v7 will solve that, but new Manager seems to be release in these days.
[Magisk] IzaacJ:
Hello. [MENTION=4470081]topjohnwu[/MENTION] just wondering, what is needed for you to add compatibility with the Lenovo Tab 3 710F?
[Magisk] Captain_Throwback:
A device to test on would be helpful, I'm sure ;).
[Magisk] mathy007:
It's like the updater script is not detecting my boot partition table maybe that's why am getting unable to detect boot image when trying to flash magisk in recovery FYI am using HTC one m7 dual sim running lollipop 5.0.2 is there anything I can do to fix it?
[Magisk] Captain_Throwback:
Wait for v7.
[Magisk] mathy007:
Ok will do
[Magisk] topjohnwu:
For those who are hammering the F5 button, please take a rest now :)

From my side, things are all working nice and smooth, however I decided to wait for my testers to find some potential bugs.

I gave them the files, if all is working well then I'll construct the threads tomorrow (because I need sleep now :p)

Goodies are arriving!!
[Magisk] mathy007:
Hope you fix the issue with unable to detect boot image with some devices especially HTC one m7 dual?
[Magisk] RandomPooka:
I've found that I've had to back up ALL the partitions in TWRP to get a functional backup ever since the starts of systemless root. Backing up the "System Image" partition is absolutely required on my Nexus 6 anymore. I always backed up the EFS, Boot, Data, and System anyway. Now, I also add Recovery and System Image (2gb, but worth it for having a functional backup again)
[Magisk] crackers8199:
okay, that makes sense...but i still don't get why just doing a backup would seemingly kill magisk/root altogether. that seems extremely weird...just making a backup shouldn't be making any changes to anything, right?
[Magisk] Gelialtron:
Just noticed that after doing the magisk installation, I lost deep sleep on my S6 Edge T-Mobile variant.

Any way to get this fixed without removing magisk?

Thanks!

[MENTION=4470081]topjohnwu[/MENTION]
[Magisk] flindaman:
So since xposed isn't working on nougat, what all is available aside from the few things in the magisk module list for 7.0? I'm having trouble finding useful mods.
[Magisk] joshuaw84:
Check out the templates post, I believe post #4, anyhow all the tools are there to show you how to make your own modules.
[Magisk] H4X0R46:
Hello! I just installed Magisk and phh root, and I have to say! Well done! This is a really neat mod with a LOT of potential! :D Now quick question. Does vipe4android magisk version support Android 7.0 Nougat? I'm running the last developer preview on my Nexus 6 (no official update quite yet.....) and I was just wondering if I can get viper4android on the device, preferably with Magisk. Thanks!
[Magisk] matif525:
It works in my M7, or maybe you can try to check what you did is wrong, find where is different between others' steps while you are waiting Magisk V7.
[Magisk] rudedog830:
Deleted
[Magisk] ftarules:
I've Magisk v6 installed with the Superuser 17 zip that is listed in the OP. NOW i want to update the Superuser to the latest v259 that is the in phh Superuser thread. How do I do that and still have the Magisk toggle ability? Do I just flash the latest Superuser v259 zip or do I have to do anything different?
[Magisk] Wyzp:
+1 , Not sure why, but magisk just break the Deep Sleep, maybe the new Samsung base ?
[Magisk] ballerd:
If I am still rooted can I replace magisk with supersu would that still conflict with TWRP
[Magisk] palmbeach05:
Like move away from magisk and go old school with chainfire's supersu?
[Magisk] Ch3vr0n:
Good luck with that, SuperSU hasn't been updated since ccmt took it over and abandoned it. Good luck having it support the current implementation of A/B or system as root devices. Ain't happening.
[Magisk] Faylen:
Hello,

I have a Oneplus 6

And I successfully updated to Android 10 and I would like to be Root, with the Magisk boot patcher works except that I forgot to uninstall the pie modules, so since some are not compatible with Android 10, it causes a bootloop, how can you remove the modules install without twrp?

Please thank you
[Magisk] ktmom:
This has been discussed several times. Go back to this section of the thread:

---------- Post added at 09:35 ---------- Previous post was at 08:49 ----------

Translates from Italian to:

This is an English language forum. The rules you agreed to when you joined was to post in English, even if that means you use an online translator. You may post the original language after the English version.

This thread is not a "how do I root my device" thread. Your device does not appear to have much support. I am not aware of TWRP recovery for it. If the bootloader is unlockable, it's possible that you might be able to root it. I suggest you ask for help where someone experienced with Mediatek devices might be able to help. You might start with the following thread:

Questo è un forum in lingua inglese. Le regole che hai accettato quando ti sei iscritto erano di pubblicare in inglese, anche se ciò significa che usi un traduttore online. Puoi pubblicare la lingua originale dopo la versione inglese.

Questo thread non è un thread "come posso eseguire il root del mio dispositivo". Il tuo dispositivo non sembra avere molto supporto. Non sono a conoscenza del recupero TWRP per questo. Se il bootloader è sbloccabile, è possibile che tu sia in grado di eseguirne il root. Ti suggerisco di chiedere aiuto dove qualcuno con esperienza con i dispositivi Mediatek potrebbe essere in grado di aiutarti. Potresti iniziare con il seguente thread:

[HELP THREAD] Ask ANY Question. Noob Friendly.
[Magisk] Faylen:
Thank you very much for your help, sorry I hadn't seen that but it worked,

Thank I was thinking of doing a factory reset because of that. :D
[Magisk] vanydotk:
Noob question, if I pull off my boot.img, patch it using Magisk manager and flash, if it doesn't work I should be able to flash the original boot.img to revert the changes right? I would use TWRP but it's not available for my device yet, Pixel 4 XL.
[Magisk] ktmom:
Yes, reverting to the stock boot.img should return you to stock. I personally would clear cache in the process.
[Magisk] Badger50:
Correct. Be interested to see if you can indeed achieve root with the P4XL. Which would be awesome since mine arrives latter this week. Hope your enjoying the new device :good::cool:
[Magisk] vanydotk:
Clear it before flashing the patched boot.img or after?

Thanks! I'll try it and report back!
[Magisk] ktmom:
Well, I'm of the opinion that clearing cache never hurts [emoji56] but I meant of it's necessary to restore stock.
[Magisk] Ingor59:
Tank you for your reply,

I did read the page of the logfiles carefully, but I cannot find any logfile (for now I have no root access to files)

If you can tell me which specific logfile is of interest I can try to create it.

A little bit of xtra information: I did use the most recent original firmware and the one before that

XEH-T725XXU1ASG3-20190802190600.zip and the newest XEH-T725XXU1ASH1-20190904141020.zip

Both gave the VBmeta problem

I have an Galaxy tab S5e SM-T725

As I wrote there was no problem with Magisk Manager 7.3.2 and Magisk 19.3

Updated to 20.0 gave these problems.

The tab stayd in download modus with the error message mentioned.

Is it of interest to give the patched VBmeta .img file??

I think this problem can easily be reproduced by following install procedure mentioned above
[Magisk] estofjlw:
[MENTION=4470081]topjohnwu[/MENTION], I am trying to get info and specs on the Magisk Tethering Enabler Module.. I am trying to find out if it hides tethering from the carrier and does one need a tethering - or can use - a tethering program like "Wifi Tether for Root users" which I use now. In other words is the Tethering Enabler a firewall to the IP addresses behind it the Tethering / Router program creates?
[Magisk] kyljys:
Oneplus 6 with the first beta version of android 10 has some issues with Magisk 20.0. Installing magisk causes the stock recovery to be inaccessible (no working TWRP as of yet) which in return makes e.g. clearing cache impossible. Is the recovery problem something to do with Oneplus's implementation or could something be done with magisk's side?
[Magisk] martyfender:
I believe [MENTION=4470081]topjohnwu[/MENTION] fixed that issue with this commit:

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

So be patient and wait for him to update the Canary build with that fix or for a new stable build if you don't like using Canary.
[Magisk] bhelmouth:
i have k20 pro (raphael) flashed orange fox r10_7 , magisk v20.0 , and magisk manager v7.3.5 then when i open the magisk manager, the pop up windows said its required to install the magisk environment setup. after installing its, reboot, then stuck in recovery/ cant boot to system.
[Magisk] xunholyx:
Flashing the magisk-uninstall.zip would have been a much less drastic option than a factory reset.
[Magisk] ballerd:
I had twrp working for my galaxy a10 now its not allowing twrp to be installed with magisk is that something wrong in the twrp build or is it magisk and how can I fix or what logs etc do I need to check or is it a patch ?? I can provide any details you need
[Magisk] martyfender:
Did you follow the directions here and in the section below it on how to install on Samsung devices?

https://topjohnwu.github.io/Magisk/install.html#magisk-in-recovery

Also, from twrp.me (I don"t know if this applys to Samsung devices or not)
[Magisk] kotuamoalt:
Installing magisk has no effect on TWRP. You have something else going on that you need to address.
[Magisk] martyfender:
Is this the recovery for your device that you used? If so, it looks like that each time you update Magisk, that you must patch the twrp recovery image with it with Magisk Manager and reflash it.

https://xdaforums.com/galaxy-a10/how-to/magisk-root-galaxy-a10-series-t3963822/page9

UPDATE: Just ticking the recovery mode option in Magisk Manager before patching may will do this.

From the github installation guide:

Or in your case, from what I read on that device forum, apparently the twrp.img can be patched by Magisk Manager on this type of system as root device.
[Magisk] fichatel:
Hello,

Message for topjohnwu.

Following the "Best Practices for MagiskHide" in Magisk tutorial, and especially the very last point :

<<Uninstall Magisk Manager: this is the last thing you should try. Sometimes the hiding technique used in Magisk Manager is just not good enough (it is improving, like recently added code obfuscation), try uninstalling and see if it works. If it does, report to me and I will hack up a solution ASAP.>>

this message is just to report my experience.

I had an unofficial LineageOS 16 installed (clean install with all swipes) on a Samsung Galaxy S4 GT I9506 with an banking app (Ma Banque) not working (root detected with Magisk 20 when trying to use SecuriPass feature).

After trying almost everything explained in Magisk tutorial, I finally uninstalled Magisk and my banking app works now.

Thank you
[Magisk] martyfender:
Your quote above indicates uninstalling Magisk Manager only, but in your final statement you ended up uninstalling Magisk entirely. Did you try uninstalling MM only first? At least then you still often have at the least, root access, not in all cases though.
[Magisk] wawanRedblack:
Revert back to 19.4, v20 messed up recovery on oos 10
[Magisk] kyljys:
How can I revert back to 19.4 without TWRP? Installing to 2nd slot after OTA or patched boot image are currently the only way to root this android 10 beta, and both ways force v20. :mad:
[Magisk] stifmaster81:
used the viper xhifi Or the fx, but with Android 10 does not work either .. any alternative to turn up the volume? Why modify the mixer.patch can not be true? I have a pixel XL

Enviado desde mi Pixel XL mediante Tapatalk
[Magisk] Artim_96:
Did you make a full uninstall of Magisk and then flash the patched boot image?

Installing to 2nd slot only makes sense if there actually was a OTA
[Magisk] kyljys:
I did. And there was an OTA, the first method I used was installing to second slot. Result: magisk v20 and no recovery, not even the stock one.
[Magisk] Artim_96:
Ok, that's bad
[Magisk] :
Hı [MENTION=4470081]topjohnwu[/MENTION]

I am using MIUI 11.0.2 Rom.

My device is the Redmi Note 7 4GB / 64GB version.

I have installed Magisk 20.0 my device.

I have a problem.

sometimes when I open the magisk manager, I get 'not installed magisk' warning.

however, Magisk 20.0 is successfully installed.

no application has root permission when I receive this error.

but the problem disappears when you restart the device.

this error appeared many times.

what should I do to get rid of this error.

Please help me. Thanks.
[Magisk] newbieprime:
Hey, ever since I have updated to Magisk 20.0 my G610F(J7 Prime) now has issues on the lock screen, when I try to trace my pattern, the screen freezes for a few seconds and then timeouts, (i think the phone thinks i am not performing any action), I am forced to spam the home button to keep it from timing out, any fix? I'm scared that it would be impossible to unlock this if it worsens.
[Magisk] mewbow1:
Uninstall Magisk Manager

Flash Magisk-Uninstaller zip

Then again flash Magisk-v20

Clear Dalvik Cache and Reboot

Try this...
[Magisk] :
ok i'll try.
[Magisk] fischli:
Sorry but I'm confused. I like to try Magisk 20 (or 19.4) but I do not get real root access. Su and Magisk says I have root, but I do not have write access to the filesystem. I cannot modify anything. I know the new mouning point since 19.4, but I don't know what to do.

My device: Pixel XL (marlin), with latest Lineage 16.0 and TWRP.

Magisk 19.3 is working so fine!
[Magisk] JudgeDread11:
Lineage 16 =Android 10?

If so then it's not possible to edit the system position directly. Only systemless modifications (through Magisk modules) are possible on Android 10.
[Magisk] m0han:
android 10 is lineage os 17. https://www.cyanogenmods.org/download-lineageos-17/
[Magisk] martyfender:
Try doing it with a Magisk Module. Even on Android 9 you may have to do this.

I do have a new Android 9 device, stock, but rooted with Magisk Canary, but I dare not try to write to system mounted as /. I have done it systemlessly with a Magisk module, though.
[Magisk] apprila:
My bank app detected the phone rooted on magisk manager v7.3.5 but it passed on v7.3.4 .
[Magisk] damnation333:
Hi,

Need some help for hiding root for my banking App (CaixaBank app and Caixa Sign). OnePlus 3, Android 9.

* Magisk Canary: 20.1-59fd38bb (20001)

* Magisk Manager Canary: 7.3.5-5ffb9eaa (246)

* Hide MM: on

* SafetyNet: pass

* Magisk Hide for all rooted apps including the banking ones is on (and before opening the apps)

* Developer Options: off

* AdAway log:

Anybody have suggestions which of those I should block?
[Magisk] garylawwd:
Are you passing safetynet? If not then that could be the cause
[Magisk] damnation333:
Forgot the obvious one. Sorry.

Yes, I pass ctsProfile and basicIntegrity. All fine there.
[Magisk] martyfender:
Normally, you should not be hiding root apps, but only the apps that detect root, such as your banking apps.
[Magisk] damnation333:
I saw that as a suggestion in one of the guides. It's just Titanium Backup, AdAway and a root explorer.
[Magisk] zgfg:
What will be the purpose of hiding root from AdAway or Titanium - then, they cannot use root.

The idea (from that guide?!) might be to uninstall root apps, because some banking apps or so may search for well known root apps - if they find them, they can conclude that system is probably rooted (otherwise there won't be use of installing AdAway, AppQuarantine, etc)

So you could try by uninstalling one by one of them - to see if it helps and for which of them your banking app is looking
[Magisk] damnation333:
Thanks for explaining and the suggestion. Just uninstalled those and cleared the data from the bank app. To no avail.

In that AdAway DNS log, did any one of those look suspicious to you and worth blocking in the hosts file?
[Magisk] jenslody:
Make sure the vanking apps are not on external/adoptable storage or MagiskHide will not work for these apps.
[Magisk] damnation333:
From what I understand I don't have external/adoptable storage. My OnePlus3 just has an internal SD. Thanks though.
[Magisk] fischli:
Thank you. Which module should I use? And yes, Lineage 16 is Android 9 of course. As said with Magisk 19.3 I have no problems at all.
[Magisk] alexp1289:
Hey guys I keep getting an error on Netflix it says device failure when launching the app. My device passes safety net and everything I'm even able to download Netflix from the play store. I'm on resurrection remix android pie 9.0 for the LG v20 h910 and I can't for the life of me figure out why it's doing this. I'm on the latest magisk and everything like that made sure everything is up to date.
[Magisk] NisseGurra:
I find android 10 to be an mess, any way to mount system as RW?, the magisk debloater don't run properly on android 10. Magisk installed but no access to system.
[Magisk] tech_head:
Try disable then enable Magisk Hide.

I've found this needs to be done sometimes after and update.
[Magisk] Ch3vr0n:
No, under android 10 /system is mounted as ro. No way around that, it's at the partition level ext4_ro i think. The app will need to be updated, or you could try titanium backup and remove stuff
[Magisk] Didgeridoohan:
I don't think anyone has mentioned this yet: since it worked with v7.3.4, the app is likely detecting the Manager (even if you have it hidden). Known to happen on v7.3.5, but [MENTION=4470081]topjohnwu[/MENTION] is working on it:

https://twitter.com/topjohnwu/status/1185116451205570560

https://twitter.com/topjohnwu/status/1186581296627105793

If it still doesn't work if you uninstall the Manager (temporary solution), take a look here if you haven't already:

https://didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
[Magisk] demonoidmaster:
No i meant that if you had previously used a boot image that worked on v19 just flash it in twrp, but honestly if v19 works but v20 doesn't then just use magisk 19

To be sure, if you're using a custom rom just reflash it, flash gapps, then magisk 19

However something you could try before doing this is maybe you need to have dm-verity disabled, OrangeFox recovery can do this automatically upon zip installs if it detects it being present

---------- Post added at 07:36 PM ---------- Previous post was at 07:33 PM ----------

But wouldn't you be able to just set it to rw using an adb command or something?
[Magisk] Mzprx:
No, it's not Oneplus only. I have Pixel (first generation) and after upgrading to Android 10, I lost the ability to boot in stock recovery (both via adb and button combination).

I found out it is because of Magisk. When restored the image, everything is normal. So, restore the image, do whatever you need to do, flash Magisk again. This workaround will be until Magisk is somehow fixed. Apparently Magisk is changing something which Android 10 detects. It was not a problem with Android 9 and older, but obviously Android 10 is different.

John
[Magisk] zgfg:
With Magisk you have root.

Hence with like MiXPlorer granted root access you should have full access to Cache, to be able to delete (then you reboot)
[Magisk] Mzprx:
I have Pixel (first generation) and after upgrading to Android 10, I lost the ability to boot in stock recovery (both via adb and button combination).

I found out it is because of Magisk. When restored the image (one of the Magisk two "uninstall" options) I got back the ability to boot in recovery. So, after I do whatever I need to do, I flash Magisk again to get back root. Apparently Magisk is changing something which Android 10 detects. It was not a problem with Android 9 and older, but obviously Android 10 is different.

Is there a plan for this to be fixed in future releases?

Thank you

John
[Magisk] Didgeridoohan:
Not necessarily. There are now devices with system partitions that are completely read only.

Some info:

https://github.com/topjohnwu/magisk...a0/notes.md#new-system-as-root-implementation

https://twitter.com/topjohnwu/status/1170404631865778177
[Magisk] NisseGurra:
Yes, its a mess, cant even block ads due to the non RW system in android 10.

This makes all mods reliant on system root access impossible, no need for magisk...