yashsingh1/xdaforums huggingface dataset:
[Magisk] Didgeridoohan:
Confirmed... Thanks. I've notified [MENTION=9815783]diareuse[/MENTION] about the problem and he'll fix.

You have Magisk installed already. Give it a go again on a clean system without Magisk...
[Magisk] drezz2:
I have stayed in 18.1 since it works, update to a later one and it was not going, so I went back, what I do not know is if it is a problem of magisk or cerberus (the support of cerberus seems to have disappeared and they do not respond to anything )

What is the advantage of updating to 19.2? I saw that with 18.1 followed correctly passing safetynet
[Magisk] watatara.102:
not sure if this issue is reported or not, you will stuck on boot if you have Hide Magisk Manager enabled.

this is what I'm doing that lead to stuck on boot

1. enable Hide Magisk Manager

2. on twrp, flash new kernel

3. flash magisk(19.2).zip

4. boot to system

Magisk 19.2 (19200)

magisk manager 2.7.0 (213)

if not stuck on boot, magisk is not installed
[Magisk] m0han:
if i remember right, magisk dev recommends that one flashes kernel after magisk.
[Magisk] dougluna:
In zenfone max pro m1 the only version that works without getting stuck in the Asus logo is 18.1 both 19.1 and 19.2 I have the problem of getting stuck in the Asus logo.
[Magisk] RandomPooka:
Flashing the unrooted kernel again after flashing Magisk would overwrite Magisk. You do not want to do that. Or, perhaps I'm misunderstanding your post.
[Magisk] martyfender:
This is from the official Magisk Documentation:
[Magisk] jcmm11:
Some custom kernels, on some phones, don't preserve Magisk. In that case Magisk must be last. Other than that yes, Magisk should be flashed before custom kernel (but it will work the other way round as well)
[Magisk] RandomPooka:
I definitely agree with both of you, but was thinking stock kernel when I replied.

If your custom kernel install procedure doesn't say otherwise, I guess flash it in whatever order you like. But, make sure it doesn't specify an order of operations in the kernel install instructions.
[Magisk] krohn:
Not sure where to drop this request.

Looking for direction rooting a new phone, no support yet. Probably wont get any down the road. Need back up before recovery gets flashed to try anything. [IMG="newdevice pic "]https://ibb.co/DrwPKt0[/IMG]

Where do i start on this guy. This is a GetNord, LYNX, not the Oynx. Oreo8.1.0,

keral version, 3.18.79(gcc version 6.3.1 20170109)

(Linaro gcc 6.3n2017.02)

Se22@tripod-dept3-srv3 #1

Tue mar 19 15:21:07 cst 2019

Build # L808F_lynx_o_20181017_V1.1.0

I cant link pics i guess.
[Magisk] occtec:
Hi all, I am on the latest build of Havoc -OS- on my pixel 2xl and after flashing magisk in twrp my kernel reverts back to stock kernel instead of the baked in kernel 'caseium' in Havoc -OS- am I doing something wrong or anyone else experience this? I am on the latest build of magisk. Thanks

Edit: not only do I lose the baked in kernel but also twrp recovery after flashing magisk?

Any help would be greatly appreciated..
[Magisk] jcmm11:
At a minimum need full TWRP log from install.
[Magisk] occtec:
Please see attached, although I have since reinstalled in this order. TWRP.zip>reboot to recovery>Magisk.img>flash custom kernel (caseium)>take log>reboot to system

Edit: custom kernel (caseium) & magisk are present now and both working as should but twrp recovery has been replaced with stock recovery after flashing magisk:confused:
[Magisk] niltonsm357@gmail.com:
Magisk General Support/
[Magisk] martyfender:
You are replying here to a very, very, old post.
[Magisk] Didgeridoohan:
https://topjohnwu.github.io/Magisk/install.html

Since you're installing by patching the boot image (and I'm assuming you're using the stock image when patching) you will end up replacing any other kernel/boot image mods when installing the Magisk patched image. That's why you lost the kernel (but you've figured out that you need to flash that after installing Magisk) and since the recovery is in the boot image on A/B devices, you also replaced TWRP with the stock recovery.
[Magisk] occtec:
So how can I get twrp recovery back on without losing magisk, just boot into twrp via fastboot and flash the twrp.zip recovery file? Will I lose anything? Thanks for your help :good:
[Magisk] krohn:
This phone is new, i have not flashed or tried anything yet.

When i try to get bootloader, i get the dead android guy, and it says no command.

Finding the right buton combo, i get the basic restart menu with update from adb, or sd card, factory restore. I followed anoyher gue that said doing a factory restor would possibly bring back recovery. It did not. So i guess there is no recovery. Android device info app says booloader unknown. Not sure how to get a backup, or get a recovery, without bricking this thing.
[Magisk] Kousei Arima:
Pls add direct install method for installing magisk in upcoming magisk manager updates, just like v18, i can't install latest magisk via twrp causes a bootloop, i am using mihran's twrp with f2fs enabled for redmi note 5 pro (Indian), is this because of recovery?
[Magisk] smart123123:
That's not the bootloader it's the recovery mode... Share complete details about your phone, Android version, etc etc...
[Magisk] Didgeridoohan:
Previously, it's been a good idea to not actually install TWRP, but only boot it on devices with recovery in the boot image. At least when also having Magisk installed. Since they both alter the same parts of the image this can lead to unwanted effects. No idea if that has changed with newer versions of TWRP... Other than that it should just be a matter of flashing the twrp zip, yes.

As already stated that is the (stock) recovery you're seeing. This sounds more like you need general advice on how to unlock a bootloader and flash images to your device. There should be plenty of guides available by searching the big great interweb...

Once you've got all that sorted you can follow the installation instructions I linked you previously (note that you don't actually need a custom recovery to install Magisk if you use the patch boot image method).

You mean for the Magisk Manager to root an unrooted device? To be able to do that, the Manager would need to have superuser access. So... That won't work...
[Magisk] krohn:
Yes, just looked again, that menu is the recovery.

I think i need to allow oem unlock, and the look at bootloader again. I thought you could see if it was locked with out that though. I have only done htc's in the past. My current one is htc m10 with magisk. I remember that install method.

Ill do some more digging tomorrow. Thanks guys.
[Magisk] occtec:
That's exactly what I was thinking regarding both twrp and magisk altering the boot image and I believe you are correct regarding conflict, as I have experienced. I will attempt to flash twrp recovery and see what happens with magisk. If i lose magisk then I'll just use twrp recovery for flashing purposes but it would be nice to use it as a stock recovery and have magisk working also. I'll let you know how I go. Thanks again :svetius:
[Magisk] Kousei Arima:
Yes exactly, in Magisk manager 6.0.1 when any device was unrooted with twrp recovery, when we clicked on install for Magisk, it used to give 3 options, Dwld zip only, Patch img file n direct install(recommended)

This third option got removed in future magisk updates, i want this back, cuz somehow twrp causes bootloop for me beyond magisk version 18
[Magisk] Didgeridoohan:
No. The "Direct install" option has never been available on an unrooted device... Sounds like you've got some details mixed up.
[Magisk] Kousei Arima:
Oh yeah sorry my bad, it was available when i was on V18 n wanted to update magisk, but still, without formatting my phone when i was on 19.1, for upgrading to 19.2 it wasn't available, i think it got removed in recent versions, for upgrading i mean not rooting

I was lucky to have found v 18 magisk zip lying around in my pc, otherwise now, i can't install magisk via twrp, anything above v18 doesn't work at all, u got a solution mate?
[Magisk] Didgeridoohan:
The "Direct install" option for updating has not been removed. If it's not avilable for you, that means your Magisk installation is broken and it is impossible for me to say what is the cause.

If you have v18 installed and working, why don't you just update (by using "Direct install")? The current stable release is v19.2, so it'll update directly to that...

Edit: Alternatively, if you really can't get things working, you can try to update by downloading the v19.2 zip and installing it by flashing it from the modules section of the Manager, just as if you would install a Magisk module manually.
[Magisk] Kousei Arima:
Oh alright, i will do that, i guess my recovery is at fault, i use a modified twrp from. the time when official one didn't properly support f2fs, guess i need to update to latest official twrp now, will have to format everything for f2fs again, Thanks for help tho bro :)
[Magisk] partwish:
Motorola G5s+ and Magisk

Hi! I have Moto G5s+ with Pixel rom 9.0 caf. I installed magisk version 14 when I rooted my phone, but now.. I cant Install magisk manager, I can't install either of the version from Recovery. With 19.2 version I got cannot mount/vendor, process ended with error 1! If I try to install version 14, it looks like I installed it, but after I boot to system, I don't have magisk.
[Magisk] guest4711:
Deinstall MagiskManager before flashing Magisk.zip

The new Manager is not compatible with Magisk14...
[Magisk] partwish:
I did it, because manager won't even start.

Edit: I flashed Rom again, and I installed manager... But I can't install 19.2 zip file.
[Magisk] Artim_96:
Flash it in TWRP, if it gives you an error, save the log in /cache and attach it here.

BTW did you also try extracting your ROMs boot image and let the manager patch it?
[Magisk] free4flight:
Same thing happened to me. Oneplus 6T.... 19.2 was working on OB10, updated to OB11 and now it won't install, booted back to twrp. Tried several methods, no go. Had to revert back to 18.1 ... is there a fix ??? TIA

Edit: worked via direct install but didn't work earlier, perhaps the updated rom had to acclimate a bit? ;)
[Magisk] krohn:
got more info from the phone

Didgeridoohan,

So i found the Engineering mode, dial code *#*#3646633#*#*

and factory mode, which is just the test features. dial code *#*#2266#*#*

the rest of these pics show the options i get with volume up, and power button. Black menu, boot options.

and the recovery - no command-droid, then recovery menu.

i have not found any other boot option.

i will see about getting magisk and testing the bootloader in a few more minutes. I guess this is why I stay away from foreign phones.

this is a shared folder with all the info and pics.

I'm limited to links to keep spam down. :) drive.google.com/drive/folders/1thbHZBq9lpYOpMSioRAv39KvlRWNXBUB if the link does not work just do: drive dot google dot com/drive/folders/1thbHZBq9lpYOpMSioRAv39KvlRWNXBUB

DEVICE

Model: LYNX (LYNX)

Manufacturer: malata

Baseband Version: MOLY.LR9.W1444.MD.LWTG.MP.V237.3, 2019/03/18 14:38

RIL Version: android reference-ril 1.0

Build Number: L808F_LYNX_O_20181017_V1.1.0

Build Fingerprint: Getnord/LYNX/LYNX:8.1.0/O11019/1539777212:user/release-keys

Bootloader: unknown

Java VM: ART 2.1.0

OS Version: O MR1 (8.1.0)

SDK: 27

DISPLAY

Resolution: FWVGA, 480x854 pixels

Software Density: 240 dpi (hdpi)

Refresh Rate: 59.52 Hz

PROCESSOR

CPU Architecture: AArch64 Processor rev 4 (aarch64)

Board: k37mv1_64_bsp

Chipset: MT6737

Cores: 4

Clock Speed: 221 MHz - 1248 MHz

Instruction Sets: arm64-v8a

CPU Features: fp asimd evtstrm aes pmull sha1 sha2 crc32

CPU Governor: interactive

Kernel Version: 3.18.79

Kernel Architecture: aarch64
[Magisk] occtec:
Ok so I flashed twrp but version 3.2.3.1 this time and still the same issue, I've lost magisk :( so went back in to recovery only to find I've now also lost twrp recovery and my custom kernel 'caseium' has been replaced with stock kernel again. How is everyone keeping twrp recovery & magisk at the same time?
[Magisk] Roi007leaf:
seems like magisk 19.2 breaks OB 19 on OnePlus 6 .. SIM toggle goes crazy and after a few seconds the phone boots into recovery (TWRP in my case)

EDIT: 18.1 seems to work fine
[Magisk] jcmm11:
Personally, I'm not. I just boot TWRP when I need it, which is mostly just at the beginning of the month for Google patch day. Pixel 3 XL, stock, Canary Magisk, Kirisakura kernel.

There are people keeping both, and I may try it down the road just to try it but I doubt I'll keep it. Just one more thing that can go wrong. It was different when there was a separate recovery partition.

From what I know on the Pixel 2 (XL) the order needs to be (starting with a stock kernel).

fastboot boot TWRP.img

Via TWRP install TWRP.zip

install magisk.zip

install caseium

Reboot

Apparently caseium preserves root so you can flash it last. TWRP will remove Magisk - they both occupy the ramdisk. Magisk will modify the existing ramdisk. TWRP will just replace it. So TWRP has to be the first thing you install.
[Magisk] krohn:
so, after a few in adb and fastboot, here is what i get. I'm guessing here, but looks like my only possible way to get a copy of my images is to fastboot TWRP and backup images?

I just don't want to be stuck in the water with no backup. any help is greatly appreciated. Things i need to understand, is this an, a/b system.

what does the ability to unlock number mean?

PS C:\adb> fastboot devices

0123456789ABCDEF fastboot

PS C:\adb> fastboot flashing get_unlock_ability

...

(bootloader) unlock_ability = 16777216

OKAY [ 0.008s]

finished. total time: 0.010s

PS C:\adb>
[Magisk] occtec:
Ok so this is step by step what I've done to get to where I am.

(1) Flashed stock image (Android Pie) via PC.

(2) Setup just to enable USB debugging

(3) Format system including internal storage

(4) Fastboot into twrp

(4) sideload custom rom (Havoc-OS) including twrp.zip, magisk.img & caseium kernel.

(5) Flash twrp.zip then reboot too recovery

(6) Flash Havoc-OS

(7) Flash Magisk

(8) Flash Caseium Kernel then reboot to system

Once in system all is well, but when I reboot to twrp recovery it's no longer present and has been replaced with stock recovery. When I attempt to reflash twrp, magisk disappears and custom kernel is replaced with stock kernel:confused:
[Magisk] guhvanoh:
What happens if you don't install TWRP? Since you can do everything you need to do in TWRP by just booting it, why install it?
[Magisk] occtec:
Point taken and I agree, but it was nice back in the day to be able to use twrp as a backup option

---------- Post added at 05:46 PM ---------- Previous post was at 04:57 PM ----------

I guess my only point is that twrp recovery doesnt stick, for me anyways magisk always wipes it out, so ive come to the conclusion as you have stated above, it literally is only as temp recovery. Gone are the days of using twrp as a backup solution, i just thought i was doing something wrong to retain both magisk and twrp and that there was just a simple mistake on my end that someone would clarify. Thanks again
[Magisk] occtec:
I had someone in the Havoc-OS thread suggest these steps instead, what do you think?

f you wanna start over I suggest following these steps:

1. Open cmd type fastboot --set-active=a

2. Run flash-all.bat

3. Type fastboot --set-active=b

4. Run flash-all.bat

5. Type fastboot boot twrp.img

6. Sideload the needed files.

7. In twrp go to Wipe>Swipe to factory reset. No need to go into advanced wipe.

8. Flash havoc zip.

9. Flash twrp zip.

10. Reboot>Recovery.

11. Flash caesium zip.

12. Flash magisk zip.

13. Reboot>System.

I'm just not sure I understand step 1 & 3 and then running flash-all.bat twice? Is that doing it manually as I have just normally run flash-all.bat and it would usually just flash slot A & B automatically, or am I mistaken? I was also advised to reboot into bootloader after flashing each individual file, is that necessary, should I be rebooting into bootloader then recovery or recovery directly?
[Magisk] Didgeridoohan:
[MENTION=4997933]occtec[/MENTION] From a quick look I would say that your main issue was that you were flashing the ROM after TWRP. The ROM will then replace the boot image with the stock ROM image and you're back to square one...
[Magisk] occtec:
That's it, indeed I was :o so much appreciated! Thanks for your help..
[Magisk] Redline:
Just going to leave this here in case anyone else has the same issue.

After initially updating Magisk Manager, and then doing a direct install of the latest 19.3, I rebooted to find I was still only on 19.2

I thought it odd, so I downloaded the zip, rebooted to TWRP, flashed 19.3 over 19.2, wiped my caches and rebooted.

Back in the system, was showing no Magisk installed at all O.o

At this point, I downloaded the latest 19.3 zip again, the latest uninstaller zip and the latest canary Manager apk, rebooted to TWRP and flashed the uninstaller. Wiped caches and rebooted to TWRP again. Flashed the 19.3 zip, booted to system and installed the latest Manager, detected and working fine.

LineageOS 16.0 on an LG V30+. Not sure what caused it, but it was at most a mild inconvenience to resolve. 'Tis the price I pay for running Canary.
[Magisk] newkydawg:
It's not just the Canary builds. I ran into this issue with Stable builds as well so anytime I use TWRP to update Magisk or my ROM, I always run the uninstaller first.
[Magisk] martyfender:
I know this goes against conventional wisdom, but on my devices I have run into problems if I wipe caches after flashing Magisk in TWRP, before a reboot to the system. I can wipe them later after the reboot to the system with no problems, though. However, it may just be a peculiarity of my devices, I'm not sure.
[Magisk] Tianhe:
I am not sure which build, but I had faced the same problem once. Even flashing ROM and wiping cache before rebooting caused issues. Now avoid wiping cache or do it after rebooting once.
[Magisk] VampiruX:
Hi,

For me, Magisk v19.2 doesn’t work better than v19.1.

My device is SM-G950F (Samsung Galaxy S8), Android V7.0, French version NRD90M.G950FXXU1AQK7? TRW 3.2.1.0.

I have upgraded Magisk Manager from v7.1.2 (213) to v7.2.0 (208), and updated Magisk from v18.1 to v19.2. All is OK and the zip seems to be correctly installed. After rebooting the device, Magisk manager shows a warning “Magisk not installed”. So, I downloaded the zip file and manually installed via TRW without any trouble, but when restarting, the result is the same: Magisk not installed and, of course, no root.

So I restored from the backup I made before installing v19.2, and the device is now operational with Magisk Manager v7.1.2 and Magisk v18.1.

What can I do or did I miss something?

Thank you.
[Magisk] garylawwd:
Read a few posts up from yours
[Magisk] VampiruX:
Thank you, but I didn't read all because it evolves so fast that I am not able to read all and a lot of things that I don't understand appear.
[Magisk] AndrzejDwo:
Gary meant 3 posts above yours... I think ;)

Edit: [MENTION=4824645]partwish[/MENTION] dude, attach not paste... txt, log, zip...
[Magisk] VampiruX:
Redline describes something like what I experienced. But where is the v19.3. What is Canary Manager?

Enough for today, I'll restart tomorrow.
[Magisk] AndrzejDwo:
Canary indeed... I have experienced this also, but I gave it a second chance and with second attempt of direct install updated successfully.

Good luck

Cheers
[Magisk] ashish1989:
Then why mine is not working all the 3 apps synd e-passbook, pnb m-passbook, google pay

Formatted the phone just installed the new rom, then why this issue is persisting
[Magisk] Didgeridoohan:
There is absolutely no way for me to answer that. Only you know how your device is set up...

Best I can do, I've already done. Follow the link I posted for you and see if any of the information there can help.
[Magisk] tylerhole:
A bunch of us with SM-G9650 had this issue and it took flashing the stock boot.img in twrp to the boot partition then right after that flashing Magisk 19.1 in twrp then booted and did direct install through Magisk manager to 19.2 and now all is right in the world.
[Magisk] darfri:
Well I cant use magisk 19.2 at all on my oneplus 6t with havoc rom. The systemui completely freezes at the very end of bootup (after pin, pattern etc).

This happens with or without the custom kernel. Either install it in magisk or twrp, same result

19.1 is ok
[Magisk] tylerhole:
Well as long as you didn't have any of the issues with 19.1 that 19.2 fixes then 19.1 should definitely be solid for you to use until the next update.
[Magisk] Artim_96:
First of all, I said ATTACH for a reason...

Second, the installer can't find the vendor partition, so the fstab file seems to be messed up. You should speak to your ROMs developer to get that fixed. There is probably no other way around
[Magisk] samz2:
With the latest version of Magisk Manager (7.2.0), I hate how Magisk Hide behaves. Basically root isn't hidden from all activities of the apps (examples - enterprise and banking apps) due to which I have to manually check for all activities in Magisk Hide every couple of hours. Enterprise apps show non-compliance while banking apps block login.

It is very irritating and frustrating to do this repeatedly after doing it for the first time. I've attached screenshot of Outlook as an example.
[Magisk] samsexy98:
Magisk is getting uninstalled automatically overnight.

Running Havocos with Madkernel reborn

Magisk version is latest 19.2 with manager being 7.2

Reflashed many times.. Same issue... It shows magisk installed after a flash but overnight the other day suddenly it says magisk not installed.
[Magisk] EmmanuelMacron:
How do you restore the previous version ? I have the same problem with my Xperia L1
[Magisk] the dreamer:
How can I use snapcept & minminguard by using Magisk
[Magisk] alexopth1512:
Hi, have s9+. Can i bypass MaaS360 control with magisk? knox counter is 0x1. Currently official image not rooted
[Magisk] Pandemic:
Where can i find canary build, any link ? Sorry if i missed that ;)
[Magisk] m0han:
try this: https://raw.githubusercontent.com/topjohnwu/magisk_files/master/canary_builds/release.json
[Magisk] martyfender:
Search:

in your favorite search engine. There is also a search box on xda. It's that simple.
[Magisk] svcopio:
Hello , Can someone pls help me with installing magisk on infinix hot 7 pro x625B running android pie?

I have the manager installed on my device but i dont know how to flash the zip, or if its compatible with my device.

It is a mediatek device MT6762/WB

Edit: I also couldn't find TWRP for my device.
[Magisk] _V3D4N7_:
I don't know if this is a error/bug or problem with my device.... But the magisk app crashes whenever I click "V2ray for Android" module in download section. did anyone else get this error ? If it's a error due to my device , is there a way for me to fix it ?
[Magisk] guest4711:
It's a problem with the description (file). But MM should not fc even if a file is misformated...

Download the module from github using a webbrowser and install it using the add button (plus sign) in module section of MM.

https://github.com/Magisk-Modules-Repo/v2ray
[Magisk] rogat92:
+1, same for me, my phone is running official LOS 16, this is quite frustrating
[Magisk] martyfender:
This could be a temporary workaround of you:

https://xdaforums.com/apps/magisk/magisk-installed-workaround-t3908748

I have not tried this. I just saw this and thought it might be useful.
[Magisk] uxwbfjsrc:
When installing Magisk 19.x or canary my device is stuck in bootloop. Magisk 18.1 is working fine. Kernel and system is stock. Huawei p9 lite (pra-lx1)

Log

mediafire.com/download/ttcgj1yywy3w74a
[Magisk] qwer222:
Hi, I am using samsung Note 3, just installed magisk manager 7.2, I used to patch boot img and use odin to root my phone. But in this latest magisk manager, I can't find option to patch boot img in .tar format, it only let me patch it to .img format. Anyone can help on this?
[Magisk] jcmm11:
I'm on 7.2(214) (Canary). When I choose the option to "select and patch a file" the tool tip that pops up states "select a raw image (*.img) or ODIN tarfile (*.tar)". So you should be able to select either and it'll modify it accordingly