yashsingh1/xdaforums huggingface dataset:
[Magisk] prinz3nroll3:
zte blade L5

hi,

i want to install magisk at my zte blade l5.

first i try Magisk v18.0 but i get an error,

after that i try v18.4, got the same error.

i try to install the zip file ..18.0...zip or ...18.4...zip with the twrp.

twrp version is 3.0.1 i think it it the only recover for the blade l5.

i attach the log.
[Magisk] Didgeridoohan:
I'm going to assume you mean v16.0 and v16.4. Typo?

That recovery log only shows us that you made a backup of your device, nothing about Magisk... You'll have to save the recovery log directly after you've tried to flash Magisk.

If it doesn't work to install in recovery, you might have better luck patching the boot image from the Manager (see the installation instructions in the release thread) and then flashing that patched boot image through TWRP.
[Magisk] prinz3nroll3:
hi,

thanks for the reply yes it is version 16.X sorry for that.

i ve attached the magisk twrp log. sorry for the first wrong log.

greetings
[Magisk] Didgeridoohan:
I just took another look at your log, and you're trying to install this on KitKat (Android 4.4.4), aren't you? Magisk is Android 5+ compatible only...
[Magisk] prinz3nroll3:
no,

it is android 5.1, see the screenshot
[Magisk] Didgeridoohan:
Have you tried patching the boot image from the Manager, like I suggested previously? Mediatek devices, and especially ones as old as yours, does not have the best track record when it comes to Magisk...
[Magisk] Alucard:
My RR rom has root check,wich says no root,but i do have it...
[Magisk] Augustoandro:
Check your Magisk Superuser, if the app you use to check is listed in it, grant it superuser permissions.
[Magisk] himagxol:
hey guys,

magisk 16.4 is failing saftey net for me, inside app its showing saftey net passed but in other apps it failed and am not able to run banking apps

i don't have xposed installed or any other saftey net ticking stuff

My android ver. is 8.1.0

Oxygen os ver. is 5.1.2

magisk ver. is 16.4

may security patch

i did install elemental x kernel but it's the same with stock kernel
[Magisk] Pkt_Lnt:
Here the tools provide for free here on XDA by members to troubleshoot your issues.

Start here.

https://xdaforums.com/apps/magisk/guide-magisk-troubleshooting-t3641417

Then here.

https://www.didgeridoohan.com/magisk/HomePage

and

https://www.didgeridoohan.com/magisk/MagiskHideHidingRoot
[Magisk] Didgeridoohan:
When you say "other apps", do you mean the SafetyNet checking apps from the developer Free Android Tools? Because it seems like there's something wrong with their apps... All other apps I've tested report that I pass SafetyNet (and the Play Store is certified), but not theirs.

Apart from that, you've got some good resources linked above by [MENTION=4403217]Pkt_Lnt[/MENTION] that might help you use your banking apps.
[Magisk] Rumsfield:
Having a heck of a time getting Magisk to work on my moms older phone. The goal is to use the hide function to stop her PNC banking app from crashing as it detects root now.

SuperSu was uninstalled then the boot.bin was flashed again followed by Magisk in TWRP

Manager installed fine and detected the installation (I've tried 16 and 16.4) and root was given.

Modules all fail to install and the hide function doesn't work. I have read the troubleshooting guides and even tried the f2fs workaround and it didn't do anything different.

From the LOG:

- Mounting /data/adb/magisk_merge.img to /dev/tmp/magisk_img

Cannot mount image!

! /data/adb/magisk_merge.img mount failed...

Failed!

! Installation failed

Phone Specs:

Galaxy S5 900V.05 (Verizon) MM 6.01

G900VVRU2DQL1_G900VVZW2DQL1_G900VVRU2DQL1_HOME_No_ Aboot (Basic MM 6.01 QL1 stock rom/unlocked bootloader friendly)

3.4.0 Kernal (Could this be the problem? Too old of a version?)

Thanks for anyone's input on the matter, I appreciate it.

-Rumsfield
[Magisk] Didgeridoohan:
Can't say about the module installation issue, but this is definitely why you can't use MagiskHide... Hide uses mount namespace, which wasn't introduced until Linux kernel 3.8. There is a slight, slight possibility that someone, somewhere has made a kernel for that device that has mount namespace backported. But, that is a very slight chance...
[Magisk] Artim_96:
If only that app is saying that you aren't rooted host ignore it. Then you obviously have no problem
[Magisk] Rumsfield:
Tried the "SparkPlug" kernel, the phone managed to boot with it but would crash constantly. I couldn't even make it into settings to see what the kernel version was. Restored back to previous image in TWRP. The modules arent a huge deal I guess because they can be flashed manually in recovery. I guess a newer working kernel is what I need to get Magisk to work on this old phone. Ripping my hair out over a stupid banking app. Magisk works perfect on my Moto phone and Shield tab so screwing around with these stupid Samsung devices wants me to throw them in the trash sometimes.
[Magisk] Didgeridoohan:
It is extremely unlikely that you'll find a kernel newer than 3.4 for the device. That just doesn't happen... The only chance you would have, is if someone has modified the existing kernel so that is has support for mount namespace. But, that is also very unlikely...

Samsung does do a lot of stuff that isn't very mod-friendly.
[Magisk] dizM0nkey:
Apologies in reviving your old post, but do you happen to know what build of Magisk you were using? I'm getting the same "! /data/adb/magisk_merge.img mount failed." error and you may be the only one who knows that it may be build related. I'm currently running Magisk 16.3 on an Oneplus 6. No other mods installed and not able to update modules after the initial boot after install of Magisk.

Any insights you can provide as to how you overcame the mounting issue would be appreciated!
[Magisk] Rumsfield:
fingers crossed! :(
[Magisk] ianmacd:
I was using a post-16.4 snapshot that I built myself from the source. A bad recent commit had broken module installation, but the developer fixed it within a few days. You're running 16.3, so whatever the cause of your issue is, it's going to have a different explanation to the problem I ran into.
[Magisk] jenslody:
No custom rom for your device ?
[Magisk] BlaMa:
Magisk manager crashes on every start

I have Huawei p10 with magisk v16.4 and magisk manager 5.7.0. Android is v8.0

The application itself crashes on every start. I attached the logcat file.

Please can someone help me how to fix it?
[Magisk] Didgeridoohan:
Looks like the repo bug. Fixed already, just not released. Meanwhile, clear data for the app. Clearing repo cache in settings can also work, if you can open the app that is.
[Magisk] jcmm11:
Did you try SuperSu-SR5, installed in sbin mode, + suhide-lite 1.09?

https://xdaforums.com/apps/supersu/suhide-lite-t3653855

The requirement there is Android 6.0+, but no mention of a kernel version dependency.

Might have better luck considering how old the device is. (You mentioned SuperSu, but not suhide). If you do try this make sure you read the About tab after installing suhide.
[Magisk] andrew2432:
Update to a 7.1+ custom os, mountnamespace is supported in RR 7.1.2 kernel for smg900x
[Magisk] andrew2432:
Don't make fun of that security patch!
[Magisk] lazostat:
i try install magisk on lenovo tab2 10-70 and says it not supported for kit kat android. Is there something i can do?
[Magisk] Strephon Alkhalikoi:
[MENTION=5945816]lazostat[/MENTION]: Yep. Install SuperSU.
[Magisk] gothicVI:
Install a custom ROM

Gesendet von meinem Moto G (5) Plus mit Tapatalk
[Magisk] masterbyte:
i discovet that i can uncompress and compress original img using carliv kitchen tools.

***************************************************
* *
* Carliv Image Kitchen for Android v1.3 *
* boot+recovery images (c)2016 carliv@xda *
* including support for MTK powered phones images *
* WINDOWS x64 version *
***************************************************
* The unpacking images script *
***************************************************

Your image: boot.img
Create the boot folder.
Printing information for "boot.img"
Unpack image utility by carliv@xda

[!] This image has a MTK header

Header:
Magic : ANDROID!
Magic offset : 0
Page size : 2048 (0x00000800)
Base address : 0x40078000
Kernel address : 0x40080000
Kernel size : 6122344 (0x005d6b68)
Kernel offset : 0x00008000
>> kernel written to 'boot/boot.img-kernel' (6121832 bytes)
Ramdisk address : 0x44000000
Ramdisk size : 1899280 (0x001cfb10)
Ramdisk offset : 0x03f88000
>> ramdisk written to 'boot/boot.img-ramdisk.gz' (1898768 bytes)
Second address : 0x40f00000
Tags address : 0x4e000000
Tags offset : 0x0df88000
Board name : '1510026515'
Cmdline : 'bootopt=64S3,32N2,64N2'
Compression used: gz
Unpacking the ramdisk....
../boot.img-ramdisk.gz: 53.5%
7970 blocks
Done. Your image is unpacked in boot folder.
Prima qualquer tecla para continuar . . .

now i question is: how i can manualy add/replace necessary files to patch manualy my boot.img
[Magisk] Artim_96:
Why would you want to do that? Let the Magisk manager do the job and just compress it yourself. Otherwise you'd need to check GitHub to find out what needs to be changed. It's way more than just add/replace some files
[Magisk] notsyncing:
Hello, I'm using Magisk v16.4 on my device with LineageOS 15.1 GSI. And adb does not work since I installed magisk. I have to manually copy /system/bin/adbd to /sbin/adbd then execute "start adbd" to make adb working on every restart. This also happens on v16.0. Is there something to do with this? Thanks very much!

Logs are here: https://pastebin.com/ebNyR1R7
[Magisk] madbat99:
Magisk is for Android 5.0 and up. No exceptions.

RTFM
[Magisk] masterbyte:
the magisk manager generates an invalid image. i have tried to uncompress the image patched with magisk manager and gives me a error. i have tried several tools to uncompress the inage with no result.

the crazy solution is uncompress the original image, make again the image with no compression (i don't know how...), take that image and patch with magisk, unpack the image and repack and recompress with the same compression.

or... learn russian :P
[Magisk] Artim_96:
Well, the crazy solution is still much simpler than digging around in Magisk source code to find out which changes apply to your device and how to apply them. And to make an image from a bunch of files shouldn't be any problem. Just Google for a program. And it probably doesn't have to be uncompressed, only compressed in a format Magisk can handle. It should be able to handle any UNIX typical compression format like GZip or LZip
[Magisk] fil3s:
Keep losing root with any Oreo 8.1 ROM

Regards.
[Magisk] jcmm11:
Thanks for the highly detailed report. Very helpful.
[Magisk] DB126:
Have to read between the lines ... :rolleyes:
[Magisk] Badger50:
And I'll get my crystal ball! ?
[Magisk] WeyardWanderer:
Hi I've tried searching my tablet model number to check if it's compatible with Magisk but I haven't found anything. I have a Samsung Galaxy Tab A SM-P550 running 7.1.1 with TWRP installed. Should Magisk be compatible? I downloaded the zip with v16 and tried installing it with TWRP but it gave me an error.

Incidentally, while I haven't previously rooted my tablet with another method, I tried reflashing the stock firmware to be safe since I saw that's necessary for Magisk, but the sammobile website doesn't have the firmware for my country (USA) while it does have it available for many others. If that's the problem, do you know where I can get the stock firmware? Thanks.
[Magisk] Single_Core:
I've found an application that seems to detect root access regardless if I use magisk hide.

Application: https://play.google.com/store/apps/details?id=be.belfius.directmobile.android&hl=en (Belgium banking app - Belfius)

Behavior without Magisk hide enabled:

- It gives a friendly warning about being rooted and possible security risks but allows me to use the app regardless, however unlocking the app with fingerprint is disabled due to having root.

Behavior with Magisk hide enabled:

- Enabling magisk hide gives me the options to enable my fingerprint settings and upon matching my fingerprint it again displays a warning that I can't login using fingerprint with root access.

Added two screenshots below, one of passing safety-net and my settings of the version/security patch/ ...
[Magisk] jcmm11:
Try 16.4 - it's made some changes in the way it hides itself.

Did you hide magisk manager?
[Magisk] martyfender:
I think the app could also be detecting your selinux status as permissive, but Magisk hide, is supposed to hide that, also, I believe?

Also have you tried clearing the banking apps data and cache?

Here are some other suggestions:

https://www.didgeridoohan.com/magisk/MagiskHide
[Magisk] Single_Core:
Thanks for the quick reply.

I just flashed 16.4 and hid the app, but I can't seem to find magisk manager in the magisk hide list? Is it listed under another name?
[Magisk] martyfender:
To hide the Magisk Manager, go to settings.
[Magisk] lazostat:
What exactly "magisk hide" option does?
[Magisk] martyfender:
https://www.didgeridoohan.com/magisk/HomePage
[Magisk] techy97:
Unable to mount /vendor in Redwolf treble. Sorry if it's already mentioned somewhere among 2537 pages. I don't wanna visit each of them.
[Magisk] Pkt_Lnt:
You do not need to read all pages, use this.

https://xdaforums.com/search.php
[Magisk] techy97:
It is of little help.
[Magisk] Darke5tShad0w:
Using search tells you that you need to provide logs as only you and one other person is experiencing this.

https://xdaforums.com/showpost.php?p=76116600&postcount=24052
[Magisk] Earldeath:
Magisk detected on all gamevil games, still waiting for next update 😊
[Magisk] dknight178:
Hi Guys,

I used search already but none of the previous posts involving this issue was ever resolved - just going to give this a try.

I want to install magisk on my phone (S7 Edge Exynos - stock Oreo). I also installed TWRP (which does not stick for some reason) which tripped my Knox.

I tried both the latest stable and beta versions via odin - and tried either just "preserve force encryption" (default) or "preserve force encryption" and "preserve AVB 2.0/dm-verity" but it yielded the same issue:

"Verification Failed: Unable to restart your device. The integrity verification has failed. You need to reset your device to factory default settings. This will erase all your data" and this asks me to reset. Fortunately, I can still use odin to flash stock boot.img.tar.

I tried TWRP but I can't access my storage files (both sd card and internal storage). I mounted USB OTG to follow this (https://xdaforums.com/s7-...xynos-t3726314) and flash the two files mentioned but the same error occurred.

Is there any other way aside from formatting data (to let twrp access internal storage and allow me to flash the disable encryption zip) or to do factory setting (so that encryption will be gone)?

I don't have any backups of my files and titanium backup does not work on non-rooted phones.

Thank you!
[Magisk] masterbyte:
it's easier to know what to google, because i don't have a clue what to google..

so... i am stucked...
[Magisk] badbd09:
I already have CF Auto-root in my Samsung Tab s2. Do i need to uninstall it to Get Magisk???
[Magisk] Artim_96:
Cf autoroot is just the installation mechanism. You have SuperSU installed. So yes, you have to get rid of it by at least flashing back stock boot.img

---------- Post added at 07:28 PM ---------- Previous post was at 07:26 PM ----------

Jesus, have you never learned how to Google? Just type in what your looking for. In your case, the most obvious thing to Google for would be something like "img Creator" or "create img from a folder" or stuff like that
[Magisk] martyfender:
I believe you need to format data so a new, unencrypted data partition can be created. It can't unencrypt the existing data partition, magically. That is what I have had to do on all of my devices. Maybe you could copy important files to a computer, through MTP, or USB OTG, to another storage device before you delete the data partition? You would still need to download programs you use when you start fresh and set each on up again, though. I must admit, though, I don't know much about the S7 Edge Exynos. I would definitely check in the device forum, also.

After deleting the data partition, first boot can take some time to recreate the new, unencrypted partition. At least on my Nextbook Ares 8A's, it will be on the boot animation for 5-7 minutes before it gets to the setup screen, so be patient. It will appear to be a bootloop.

Not sure why, when you checked, preserve force encryption, why it did not work, unless it needs to create a new, encrypted partition, that is clean, maybe?

Maybe someone with more knowledge than me will have some ideas?
[Magisk] Omel:
Hi

I'm on a n7 port for my note 4 and I need some help to hide my selinux state permissive it has to be enforced I have tried many things but I can't change the state of my kernel for the port rom any helt will be appreciated
[Magisk] martyfender:
[MENTION=1210295]Omel[/MENTION] I believe I did that in the past by opening my boot.img in Android Image Kitchen and adding the following line to the init.rc file:

# root use permissive
write /sys/fs/selinux/enforce 0

Then repacking it and flashing it and Magisk.zip, in TWRP. When I did this I was using SuperSU, systemless, though. SuperSu, patched the sepolicy file in the boot.img, when I did this. And the key was to flash it, after the boot.img, before reboot. That was for my Nextbook Ares 8A. I'm not sure if that will work for your device, or not. Also, have you tried this module?:

https://xdaforums.com/apps/magisk/module-magiskhide-props-config-t3789228/page23

There is also an app on these forums called: The SELinux Switch, by [MENTION=4828250]Ibuprophen[/MENTION]. It is much easier to use than patching the boot.img. You can toggle between enforcing and permissive. It just requires a reboot after changing the settings, to take effect.

https://xdaforums.com/android/apps-games/app-selinux-switch-t3656502

I am currently running all of my devices in enforcing mode, as I have nothing on them that requires the kernel to be permissive. Why do you need a permissive kernel?

Upon re-reading your post, did you mean you are permissive already and need to be enforcing?

# root use permissive
write /sys/fs/selinux/enforce 1
[Magisk] jcmm11:
Yes
[Magisk] vamprook:
I instaled Magisk today on a Galaxy A5 2017, the log show me a few errors mounting /Data, now i have a verify error everytime i boot my phone.

I tried everything, even the no-verity-patch but still the same issue, i know that i can fix it doing a factory reset, but i want to keep some files. the big issue is that i can't mount the internal storage using TWRP, so i can't save my files.

Any idea?
[Magisk] martyfender:
[MENTION=3879533]vamprook[/MENTION] I believe your data partition is still encrypted and that is why you can't mount it in TWRP. You need to format your data or factory reset so that a new, unencrypted data partition can be created. Can you backup important files through MTP? If you only format the data only and not the internal in TWRP, or just do a factory reset in TWRP, your files in the internal sd card should still remain. you will, of course have to re-download your programs through the playstore or other sources and re-install them and apply your preferred setting in Android settings and program settings.

First boot, upon deleting the data partition can take up to 5-7 minutes, at least on my Nextbook Ares 8A tablets, because it needs a lot of time to recreate the partition. It will appear to be in a bootloop, just wait.

If, by chance you want to preserve encryption, you can check the preserve force encryption box in the MM, then reboot. Theoretically, the device should be faster without the overhead of encryption. Some use cases though, warrant encryption.
[Magisk] vamprook:
I can't format my data, same mount error https://imgur.com/a/Xhwk7rl
[Magisk] Ibuprophen:
Hello Everyone! :)

I just wanted to let you know that I've encountered questions regarding a few Custom Firmwares that were keeping devices in a Permissive Mode permanently and this would only apply to a few select devices (I'd say 1-2% +/-).

After a little more digging, I had found a few Custom Firmware Developments were doing this by design and, apparently, requires it for the developments to work properly.

It seems as though this decision to develop the Firmware in a Permissive Mode was not by choice but, required by design to allow the Custom Firmware to operate and, with those devices being fairly new with the Unlocking, Custom Recovery, etc... They're actually still trying to figure out how to get the Firmware to operate correctly without them being in a Permanent Permissive Mode.

I hope that I had explained this okay via text... :eek:

Just to clarify... I'm not endorsing this at all but, I just wanted to help spread this awareness to you here.

To be honest, it must have taken me about a week or so along with a few members help (who were experiencing this) to get to the bottom of this and understanding what was going on.

Thank you all very much for your time and understanding with this announcement... ;)

~~~~~~~~~~~~~~~

I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
[Magisk] martyfender:
In the past I have used the fastboot commands;

fastboot format data
fastboot format cache

But I believe on Samsung devices you don't have fastboot and bootloader mode, you have Odin and download mode.

I have only used Odin once to fix a colleagues S3 by flashing a stock, rooted ROM to it so my memory of it is not very clear. Can you format the data in Odin? Or start fresh by flashing the whole firmware in Odin?

Upon reviewing your screen shot, I recall when I got my first Ares 8A and rooted it. I saw similar errors in TWRP because I had flashed a boot.img with forced encryption removed and dm_verity removed.

Those errors were there because my data partition had not been formatted and was still encrypted.

Formatting the data and cache in fastboot, solved it for me. Hopefully you can do that also in Odin.
[Magisk] Ibuprophen:
Have you taken a look at the following threads that's specific to your device with this same discussion regarding what your having issues with?

https://xdaforums.com/showthread.php?t=3759214

https://xdaforums.com/showthread.php?t=3800852

Just a helpful FYI... :)

~~~~~~~~~~~~~~~

I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
[Magisk] vamprook:
If i flash a new firmware, will i lose all storage data? Because fastboot is not working and Odin can't format data.
[Magisk] martyfender:
You can try this: boot into TWRP, hit the wipe button, above factory reset on right side there is an option format data.

Press on this option and a keyboard rises. type YES and select format data.

After this check data partition,should be mounted. And yes, this will delete userdata. From one of the threads [MENTION=4828250]Ibuprophen[/MENTION] linked. I had forgotten about that option was there as I have only used it once or twice. I'm not sure how it would be any different than just checking off the partitions you want to format though, and why it would mount here and not in the other options.
[Magisk] vamprook:
When I boot my phone, the system ask me to restore the system by formating all data, but I was expecting to save some data.

I will try to found another solution or I will do it.
[Magisk] demonoidmaster:
So if you just do factory wipe (wipes everything except data/media/) does it work?

What partition type is data? Usually it's Ext4
[Magisk] lazostat:
I have magisk 16.4. how can I downgrade? I try the magisk Uninstaller but gives error 1..

When I try to dirty install magisk 16 it gives error 255.

EDIT

I just installed it via magisk manager.
[Magisk] vamprook:
I can't do a factory wipe https://imgur.com/a/Xhwk7rl
[Magisk] zakijesk:
how can I give local terminal superuser permissions ?
[Magisk] gothicVI:
su

Gesendet von meinem Moto G (5) Plus mit Tapatalk