yashsingh1/xdaforums huggingface dataset:
[Magisk] ipdev:
[MENTION=3299044]PWn3R[/MENTION] Can you share the boot.img or link to the ota you are using?

Did you try to boot that 14mb image?

From that log, it looks like it patched properly.

I accidentally downloaded xiaomi.eu_multi_MIMix3_V10.0.12.0.PEECNFH_v10-9 a while back.

I do not have a Mix 3, just clicked on the wrong download link and never got around to deleting it yet. ;)

I double checked the boot.img from it and patched with Magisk 18-Debug.

-rwxr-xr-x@ 1 root admin 14786560 Jan 19 19:42 boot.img
-rw-r--r-- 1 root admin 14790656 Jan 19 19:43 new-boot.img

Makes me curious why the one you have is 64mb. :confused:

Pulled from boot partition maybe?
[Magisk] PWn3R:
Here's a link to the image I'm patching from the OTA.

https://drive.google.com/file/d/1O5kwxvFH1zHJY35kjR5ot9dCX6cG5Ot2/view?usp=drivesdk

I suspect the image is actually missing the ramdisk. I haven't been near a computer to try to extract the patched version but it's too small to be right.

The image is from the global OTA that was posted in XDA news the week of Christmas.

http://bigota.d.miui.com/V10.0.11.0.PEEMIFH/miui_MIMIX3Global_V10.0.11.0.PEEMIFH_9761b07e78_9.0.zip - this is where that image is from.
[Magisk] ipdev:
It wouldn't be the first time I've seen reference to a device using an empty ramdisk.

Not sure if a Mix3 is one though.

Oddly enough, the global boot.img matches the eu boot.img when repacked and patched with magisk.

-rwxr-xr-x@ 1 root admin 14786560 Jan 19 19:42 eu-mix3-boot.img
-rwxr-xr-x@ 1 root admin 67108864 Jan 19 21:48 boot.img

-rw-r--r-- 1 root admin 14790656 Jan 19 19:43 eu-mix3-new-boot.img
-rw-r--r-- 1 root admin 14790656 Jan 19 21:48 new-boot.img

Now I wish I had a Mix3 to try it on. :D
[Magisk] PWn3R:
I meant I suspect the patched one is missing the ramdisk inside the image. If you want I can try to patch the EU image and try to use it on the Global Rom. I saw someone who posted on the Chinese MIUI forums saying some of the newer Chinese MIUI versions don't patch right with Magisk. I didn't even bother trying the version I made from the canary app on my Pixel 3 XL as the image size is like 14mb and I think it should be 64mb. [MENTION=7280276]ipdev[/MENTION]
[Magisk] -LinfernO-:
Greetings I have a head unit in my car (android 8.1) at 10.1 inches on an Allwinner T8 processor. There was a problem when turning on the radio. Magisk 18.0 is installed, when you turn on the radio and if I turn on the rear gear, the radio is hanging with a black screen. There was a problem that you need to edit the system initializer file. Magisk patches it, if you interrupt the kernel load, the system hangs.
[Magisk] Didgeridoohan:
Please do try and report back.
[Magisk] montainz09:
Hello,

I'm just wondering if there is a clean / easy way to maintain Magisk on a A/B device during an OTA sideload. Ideally, I would love to be able to just use OTA updates as per the Magisk tutorials page, but my Pixel doesn't find any updates when checking despite being on a August 2018 security patch.

Telus Pixel (sailfish) w/ Magisk 18.0, TWRP 3.2.3-1 on build PPR1.180610.010
[Magisk] Homeboy76:
Download the OTA image for 'Sailfish'

"sailfish" for Pixel

9.0.0 (PQ1A.190105.004, Jan 2019)

SHA256	d5feb9d8085517d27f848d22cc36b71d13991c2963c954342bfb3b75084b1f55

From here: Full OTA Images for Nexus and Pixel Devices

Check the SHA256 and then Sideload it.
[Magisk] montainz09:
Does regular sideloading preserve root though? I'm aware of how to sideload and where to get the images, and am fine with flashing the Magisk zip to reinstall if I have to, but I was just wondering if there was a nicer way to do this. With the advent of the super clean and easy "Install to inactive slot" method as outlined in the Magisk docs (sorry I can't link), I thought there might be something equivalent for ota sideloading given its similarity.
[Magisk] Badger50:
Whether you side load the OTA, fastboot the factory image, or flash the OTA zip in twrp, (depending on your device) you'll have to root again.
[Magisk] Ps24u:
I have an annoying bug that occurs with the patched ES File Explorer 4.0.2.2 Systemless + latest Magisk :

Sometimes renaming files in /system just fails. ES Explorer says "renaming successfully", but upon refresh the renaming did not occur. And I can try 10 times, it'll never actually rename the file.

When ES Explorer is in this state, I can delete files, or change permissions without issues, or even rename files in /data alright (so it has root privilege), but it just won't rename files in /system.

Rebooting my device fixes that issue, in that after rebooting, renaming files in /system with ES Explorer actually works, but I'd really like to find out what's causing this, sometimes.

This did never occur when I was using SuperSU 2.82 instead of Magisk, with the same ES File Explorer 4.0.2.2 Systemless, so I guess it's really an issue with Magisk?
[Magisk] ipdev:
Give the last one you patched a try.

As for the ramdisk, it appears Mix 3 uses an empty ramdisk.

(I checked both the stock and patched.)

-rwxr-xr-x@ 1 root admin 67108864 Jan 19 21:48 boot.img
DECIMAL HEXADECIMAL DESCRIPTION
--------------------------------------------------------------------------------
0 0x0 Android bootimg, kernel size: 14780612 bytes, kernel addr: 0x8000, ramdisk size: 0 bytes, ramdisk addr: 0x1000000, product name: ""
4096 0x1000 gzip compressed data, maximum compression, from Unix, NULL date (1970-01-01 00:00:00)

-rw-r--r-- 1 root admin 14790656 Jan 19 21:48 new-boot.img
DECIMAL HEXADECIMAL DESCRIPTION
--------------------------------------------------------------------------------
0 0x0 Android bootimg, kernel size: 14783726 bytes, kernel addr: 0x8000, ramdisk size: 0 bytes, ramdisk addr: 0x1000000, product name: ""
4096 0x1000 gzip compressed data, maximum compression, from Unix, NULL date (1970-01-01 00:00:00)

As why the stock boot.img is so big, I'm still not sure why.

If you flash the patched boot image and then did a "dd" copy of the boot partition, I bet you would get an image file that is 67108864.
[Magisk] jcmm11:
That's correct. Current partition size is 64MB and dd will copy the entire partition. The actual data size that's used within the partition is a different animal and can vary depending on the kernel used (generalizing for all devices running Android)
[Magisk] Legendary Cryptid:
Moon reader pro doesn't work for me. AospExtended, Mi A1 running 8.1.0 Oreo.
[Magisk] PWn3R:
[MENTION=4667597]Didgeridoohan[/MENTION] [MENTION=7280276]ipdev[/MENTION] - I tried just now, the image will boot, but does not actually appear to be patched. The device boots and then it tells me that magisk needs to be installed, but it fails installing. The image doesn't have root, because if I type "su" from adb shell, I get "su not found".
[Magisk] Bakica:
Hide it with the magisk manager.
[Magisk] Legendary Cryptid:
I did that, but it still won't work. I'm using Magisk 18.
[Magisk] Didgeridoohan:
Details on this, please. Do you mean that the Manager simply shows that Magisk isn't installed, or is there something else?
[Magisk] PWn3R:
Screenshots of what happens when I try to open the app. I also can't CD to the path where the logs are supposed to be based on what I found on the Magisk site.
[Magisk] James_Oakley:
The consensus at https://github.com/topjohnwu/Magisk/issues/907 and https://github.com/topjohnwu/Magisk/issues/585 seems to be that SafetyNet randomly starts to fail with Magisk 18.0, and works fine if you downgrade to 17.3.

That's certainly what I found: With 18.0, it could fail anything from immediately to a day or two after rebooting the phone, and then would need a fresh reboot (or just luck) to start passing again. So I downgraded to 17.3, and for nearly a week now I've not had one SafetyNet fail.
[Magisk] Strephon Alkhalikoi:
Not a Magisk issue, as it works correctly here on my Pixel 2 XL, Moto X Pure, and Lenovo Tab 4. Something else is screwing around with the app.
[Magisk] dvhttn:
Found the same - Galaxy S7 with the Galaxy Project ROM.
[Magisk] muttonhead411:
Hope this vid helps illustrate the erratic behavior of magisk hide, which may be linked to safety net failing at certain times

https://photos.app.goo.gl/PVA2qwktm8kNbHMq9

ON Pixel 3 January patch, magisk v18

If anyone has any advice...
[Magisk] Teknouser:
Hi,

I am new to forum. I have read some threads and many posts regarding Magisk. I'm confused about one thing. It is said to be that Magisk is a system less root method. In order to install it(step3) , it requires custom recovery to be installed beforehand(step2). In order to install a custom recovery, say TWRP, phone must be rooted in advance(step1)..

So, if the phone have to be rooted at the very beginning(step1). what is the meaning of installing Magisk any more? Is it the only purpose to hide the first rooting step of the phone to googleplay and to some other applications?

I have a Lg G4 H815P phone which has a locked bootloader. Firmware is MM 6.0.

There is a thread regarding the rooting of MM with SALT/FWUL. But that method is also tricking the phone by some means that it phone thinks that it is root state.

So, if I root the phone in this tricky way, will another tricky way of installing Magisk ( one above the other)will work or not?

I hope I could explain my confusion, I will appreciate it too much If you explain it in detail my confusion and how to proceed with my phone?
[Magisk] Didgeridoohan:
There are devices that need to be rooted to install a custom recovery, but that is not the norm. Normally all you need is to have an unlocked booloader so that you can flash a new recovery image.

If your device is one of those unfortunate that require root to install a custom recovery you might have more luck with the patched boot image method (see the release thread for instructions).

If you cannot unlock the booloader you might be out of luck when it comes to Magisk.
[Magisk] jcmm11:
Phone does not have to be rooted to install TWRP. Bootloader does need to be unlocked. You can boot into TWRP without actually installing it (but you still need an unlocked bootloader). See https://twrp.me/lg/lgg4.html
[Magisk] Legendary Cryptid:
Is there any way to take a logcat to determine what's breaking the app?
[Magisk] Ps24u:
Anyone else experienced this or a similar behavior?
[Magisk] PWn3R:
Could the problem with the Mi Mix 3 be that it doesn't mount /system and mounts / as the system?
[Magisk] s.murdock:
Hej there.

I am trying to root my Honor 7. I had it rooted with SuperSU already but wanted to go on Magisk.

So I unrooted it, flashed the stock roms (extracted from the update.app) and then I got the Magisk Manager via .apk download, made a patched_boot.img out of the stock boot.img and tried to flash it.

But in twrp it says: Size is too large.

And in fastboot it says: FAILED (remote: flash write failure)

Can someone help me please?
[Magisk] xunholyx:
You need to flash the patched boot.img in fastboot.

Another alternative would be to uninstall Magisk Manager, and just flash the Magisk.zip (it contains Magisk Manager) in TWRP. It patches the boot.img for you when you flash it.

You can get the Magisk.zip (and instructions too) from this thread.
[Magisk] kakabobo:
Basic Integrity Fail and CTS profile match fail randomly.

Any one facing above problem as well ?
[Magisk] zer0zen_:
Hi there...

I have minor problem when installing magisk v18. Suddenly my gyro sensor stop working (not detected by sensor box), but the other sensors like proximity and accelerometer are working fine.

When i uninstalled the magisk, then my gyro sensor is working fine again. Is there any workaround to overcome this? because i need both of them (the gyro and the magisk) to work.

My system is latest cancro aex 8.1.0 btw.
[Magisk] s.murdock:
Hej unholy,

thanks for the hints.

Unfortunatly the Flash with fastboot doesn't work as mentioned above. Error: "FAILED (remote: flash write failure)" and then it Aborts

When I try to Flash the magisk.zip via twrp it puts out an Error 1 - think it was something About insufficient Partition space
[Magisk] M1chiel:
What partition do you try to flash it to? In oreo on honors and huaweis the boot partition is called ramdisk.
[Magisk] dvhttn:
Read back the last couple of pages ……
[Magisk] iR3kT:
As of recently I have randomly been losing root on Magisk 18.0 on OnePlus 5T Oreo. The first time it occured I reflashed the ota then Magisk installer then Xposed installer and got back root. In the span of a month Magisk has again stop granting permissions for root besides the 5 or so apps (outof like 15) that was able to be granted root. I also noticed these 5 or so apps were the recently opened apps and any apps later were denied root.

EDIT: Solved it by removing power-saving modules
[Magisk] habylab:
Safety net fails for the first time yesterday and then the same again this morning. Haven't rebooted my phone, so are Google doing some updates on their side?

Back to 17.3 I will go then. Thanks for this!
[Magisk] silverik1:
Solved by reinstalling firmware , format data yes (wipe all data), install latest twrp 3.2.3-2 with odin 3.13.1 and flash magisk v18
[Magisk] PWn3R:
[MENTION=7280276]ipdev[/MENTION] [MENTION=4667597]Didgeridoohan[/MENTION] - Any ideas what I should try next? I could backup my data and factory reset and see if I can get root with the image I made, but I suspect the image isn't actually rooted.
[Magisk] Didgeridoohan:
[MENTION=4544860]osm0sis[/MENTION] did some digging into your device's FOTA and found that the issue likely has to do with how the ramdisk is set up (boot and recovery ramdisk combined, or something along those lines). For now, there's likely not much you can do...
[Magisk] PWn3R:
Ok, I'm going to see if I can figure out how to patch "by hand" from linux. My goal is to make manually patched working version that we can use for the time being. Sorry I missed whatever osmosis posted.
[Magisk] Didgeridoohan:
Don't worry, he didn't post anything publicly. I just made sure that it didn't seem like I was the one that had done the digging...

Good luck on the patching.
[Magisk] fmotta:
You guys are certainly aware of this peculiar aspect of Mi Mix 3...

MIX 3 is system-as-root device.

https://xdaforums.com/mi...h-succeed-t3865392/post78200323#post78200323t

Google forced system-as-root for the devices shipped with Pie.
[Magisk] osm0sis:
Correct. It's system-as-root, but with both recovery and boot files combined into the system-as-root, which is new. The boot.img itself actually has no ramdisk at all instead of a recovery ramdisk (which is similar to what we had seen on Huawei's "half-Treble", but in that case they had the ramdisks in their own partitions instead of system-as-root). Hopefully that makes more sense now.

I don't think magiskinit is able to handle this currently, since it'll have to pull in files from the system partition for both recovery and boot, and there's no ramdisk and therefore no OEM init in the ramdisk itself.

What I think will have to happen is [MENTION=4470081]topjohnwu[/MENTION] will have to make it create a ramdisk from scratch containing just .backup and init (which is of course actually magiskinit), and then hopefully pulling things in from system is all it will need (though I have a hunch it'll need more work, as I said above). So if you do want to try just to see what will happen, that's what you should do.
[Magisk] PWn3R:
That makes A LOT more sense. I suspect I cannot fix this myself. At least not without trying to learn what topjohnwus code does. It's not going to be a primary language for me so I would be super slow. Gonna have to defer to his expertise lol.
[Magisk] fmotta:
Thanks [MENTION=4544860]osm0sis[/MENTION] for the explanation. Much more that I can understand LOL

What still makes me think is why Chinese and Eu (Chinese based) ROMs for Mi Mix 3 are rootable with 17.3 magisk version but Global one isn't.

The system is the same "system as root"

Anyway... I will go to sleep. I am old and tired.

?
[Magisk] s.murdock:
Via adb/fastboot? I did try to flash the boot partition. As in every guide I found was mentioned. so: fastboot flash boot boot.img or something

Just flashed the 330 stock rom again (boot, cust, recovery, system, userdata). Then rebooted into fastboot modus again. Flashed the twrp onto the recovery.

Started the honor 7 up, rebooted into twrp/recovery and then I tried to install Magisk v18 zip.

-Flashing new boot image
! Insufficient partition size
- Unmounting partitions
Updater process ended with ERROR: 1
Error installing zip file '/external_sd/Download/Magisk-v18.0.zip'

Is there a way to complete format the partitions? I thought it is done with the fastboot flash of an image already.

I then tried to flash the patched boot image again. The size of the stock boot is: 24.526 KB. The size of the patched one is 24.758 KB.

Used adb with "fastboot flash boot boot_patched.img"

target reported max download size of 471859200 bytes
sending 'boot' (24758 KB)...
OKAY [ 0.547s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 0.562s

Maybe I'll need to downgrade first or something?
[Magisk] jcmm11:
What's the OS on that phone? Is that emui 9 by any chance?
[Magisk] LonePaladin:
Sorry for the delay in updating. Had to dig to find this post.

The release thread didn't really help me -- I may be misreading it, but it looks like it's wanting me to compile a whole new copy of TWRP, and I'm not that proficient any longer.

What I resorted to was installing SuperSU -- reasoning that my tablet's OS wasn't going to wind up with the SafetyNet 'feature' anyway, as it's a bit old. SuperSU installed on the first try without a hitch, allowing me to install Resurrection. Some parts of it are still insisting that I don't have root access, but I accomplished my main goal -- overwriting the bloated OS that shipped with the tablet.

I tried running the Magisk Manager app later on; it would download the latest version, but never actually try to install it. So maybe it's just not in the cards for me. :rolleyes:
[Magisk] zer0zen_:
Nevermind... i found a workaround by editing the sensor_def_qcomdev.conf
[Magisk] s.murdock:
Nah, it's EMUI 4.0

btw: wonderfull - since yesterday when I tried to reflash everything I got no space left on the internal partitions. Total space 3,87GB, free: 141 MB.

What the hell?! :confused:

TWRP wipes don't help. Neither does a new Flash.
[Magisk] madkiran:
Hi ..

I am running havoc 2.1 (android 9.0 pie) latest build

I have been using magisk 18 with no problem till yesterday.. (of course, I have selected "hide magisk Manager" from settings to make my banking apps work correctly)

today I have clean flashed the update and installed magisk 18 , magisk manager 6.1 but all of my banking apps are stopped working. (GPay, Phone Pay.. )

I tried to "hide Magisk manager" from settings with no luck.. (from [MENTION=9639512]Fu-San[/MENTION] 's advice)

can anybody help me sort this out. any help is greatly appreciated..

thanks in advance
[Magisk] FuSan:
Does your magisk pass the safety net test?

Did you enable magisk hide on the banking apps from the left sidebar (Not the settings one.)?
[Magisk] madkiran:
Yes..

Magisk passes safetyNet and Magisk hide is enabled for Banking apps..
[Magisk] Dims_Camper:
Grab Driver always detects root

Anyone using this app? it detects root without even asking for grant access or something, ofc my device passed safetynet, tried hiding the app from magisk hide, and also hiding magisk manager. Is this because safetynet is kinda broke on magisk v18? (saw several post about magisk hide/safetynet broke on banking apps even tho the app listed in magisk hide). I tried to downgrade to 17.3 as someone said safetynet there is working fine, but didn't help. I also tried the magisk canary build, still didn't help. Will be glad if someone tell any workaround, i can also provide logs if it helps. Cheers.
[Magisk] hyborian:
I use Grab app. When it asked for root, I denied it and it never asked again, at least on my phone.
[Magisk] RandomPooka:
I'd be more concerned with why that app is asking for root than whether it means SafetyNet is broken or not.
[Magisk] waledakmal:
after flashing magisk from twrp starzplay app not working and detected root

cant work in rooted device.

any idia for that or fix
[Magisk] Dims_Camper:
Grab != Grab Driver app, even tho both of them asking for root access. When you revoke Grab root access, you can still open it right? Grab Driver isn't, it gave you huge pop upabout unrooting your device blahblah and closes itself.

Just like another mobile banking app ofc?
[Magisk] RandomPooka:
When I asked that, I was unaware that you two were talking about different apps. So, I was thinking your banking app was requesting root access, not simply detecting it.

After seeing your response, I totally get your situation. Though, I'm still wondering wtf the Grab Driver app is requesting root for in the other situation. That's shady sounding to me
[Magisk] hoeni:
Are you using twrp?

What android version are you on?
[Magisk] xCRUTCIOx:
As i said im using android 5.1.1 CM12.1 this one ( Lollipop 5.1.1 (CyanogenMod 12.1) 20160718 stable ) and yeah using TWRP 2.7 something.
[Magisk] teddy0209:
Update your twrp if there is any...
[Magisk] hoeni:
Try mounting system in "mount" before flashing.

After updating twrp :)
[Magisk] xCRUTCIOx:
http://xdaforums.com/showthread.php?t=2748327 this one is good or?

---------- Post added at 11:39 AM ---------- Previous post was at 11:37 AM ----------

GT-I8190_TWRP_3.0.2-1.tar.md5 this one thru Odin right? Sorry for being bad but im not rly into this stuff :(
[Magisk] teddy0209:
If that one is for your device model, then give it a go.

Edit: We don't have the same device, so I can't give any specifics...
[Magisk] Astramos:
Not working on samsung galaxy note 4 and 7. Waiting for update :)
[Magisk] Artim_96:
It's working on Note 4, I'm using it myself
[Magisk] xCRUTCIOx:
So i flashed with Odin that TWRP and its not working when i press vol+ home + power its restarts my phone.
[Magisk] lehongwang:
working on my note 7
[Magisk] Didgeridoohan:
Isn't this conversation better suited for your device forum. The thread is cluttered enough already...
[Magisk] exodius48:
I know it, but i want all in one app, gps spoofer + analog movement.

There a lot of gps spoofer apps on playstore, but almost of them does not have feature analog movement.
[Magisk] Benconquerer:
Thanks. I'll have made the change. Do I need any other files? How do I make it run?
[Magisk] xCRUTCIOx:
Okey guys flashed the new TWRP.. but i keep getting Unable to detect boot image when im trying to install Magisk v6
[Magisk] Xx MOE:
HELP

Pokemon go brought me here and i have a ton of questions. So I'm running CM13 on my HTC One Max with root and xposed installer. I was reading the pokemon go article about the new update and how it bans rooted devices. The article stated that Magisk would help continue to play pokemon go with the new update AND IT WOULD ALLOW THE USE OF BANKING APPS. This is where i became confused. I'm still able to use my credit union baking app and Chase banking app. If root stops the use of banking apps how are mine still working? Thanks for the help!
[Magisk] putridfoetus:
The file auto_mount tells magisk to run the script at boot.
[Magisk] Benconquerer:
This works now. Thank you!!

For anyone that wants Tethering on nexus 6P (Haven't tested other devices) unzip this in the Magisk folder. http://cloud.tapatalk.com/s/57e1192737802/Tethering.zip
[Magisk] xCRUTCIOx:
Did everything flashed the new TWRP mounted system still this boot image error when flashing magisk
[Magisk] geek85:
information to Zenfone 2 users:

I was able to put magisk on Zenfone 2 Z00A on Android 6 MM with this tuto.

It works if you don't miss any step.

there is a new official android 6 firmware for Zenfone 2.

[MENTION=4470081]topjohnwu[/MENTION] I don't know what was modified in the differents files (magisk, supersu and xposed) to make them work but it seems they have been modified specificaly for Asus Zenfone.
[Magisk] BlindArtisan:
Not all banking apps utilize SafetyNet and therefore block rooted phones. None of the bank apps which I use have SafetyNet and apps that utilize it are not terribly common (yet).