yashsingh1/xdaforums huggingface dataset:
[Magisk] Razor1973:
Did you flash your original boot.img before starting over?

No and I can't find that anywhere, at least the latest version for the H811, which is 20p.

Does the ROM you're using come with some root method built in, and if so, did you remove it?

Yes and no. No idea how.

If you're not willing to start over to get it working, then you may just have to live with it.

If this is caused by the custom ROM, starting over and installing the custom ROM would leave me in the same place I'm in today. :(

I see one of the features in the ROM thread that you're using says "Rooted System" which is the first most obvious thing that will break SafetyNet.

Does this go back to your previous comment about removing root?

SELinux might also be running in permissive mode, which SafetyNet doesn't usually like. You'll have to check that via Terminal or adb shell using the "getenforce" command.

I did find this during my searches after your last reply to me, but, at least according to what I read (notice link), this seemed to be temporary and will go away every time I reboot the phone.

By the way, thank you very much for truly trying to help.
[Magisk] armando_rod:
Thank you! And sorry for not to sue search didnt think it was a known issue.
[Magisk] Didgeridoohan:
Reflashing your ROM will still leave you with a system that triggers Safety Net, yes. But it will be clean from any mods you've been trying during this process. From there you can continue by removing the built-in root (sorry, since I don't know how your ROM's built, I've no idea how - check your ROM's thread - or maybe someone here has an answer if you're lucky).

You don't want SELinux to be permissive, it needs to be enforcing to pass Safety Net. Easiest way to know what you have is to use a Terminal Emulator app on your phone and simply type in getenforce. That will tell you the status.
[Magisk] PachiMc:
Moto x 2 xt1097

the v9 version is working with moto x 2 2014 xt 1097 or not yet ? :(
[Magisk] Artim_96:
Most likely not, not for all I know
[Magisk] Razor1973:
I'm truly lost with the ROM and I'm not sure what I'm asking. (Is there a way to unroot this ROM sounds stupid to me. LOL) However, I installed Terminal and ran "getenforce" and the response was "Enforcing". That's good, correct?
[Magisk] AbsolutelyProprietary:
Here's what I need you to do, get your kdz file for your phone http://lg-phone-firmware.com/mobile/

Then use the kdz extractor to get your stock bootimg http://xdaforums.com/showthread.php?t=2600575 and flash it using fastboot

---------- Post added at 08:39 AM ---------- Previous post was at 08:33 AM ----------

Something else you can try is to get the newest one using the lg mobile support tool, find it's folder in appdata and close the program using task manager when it finishes downloading, it won't reflash your phone.
[Magisk] HaoZeke:
So I've set up a custom kernel with Anykernel2 .... Anyone manged to integrate Magisk and phh's superuser?
[Magisk] santos_10:
I install Viper4android module I intall de app but I can't make it work. :(
[Magisk] yochananmarqos:
It's probably best not to integrate it. If you want to try it, check out the scripts that patch the kernel, that may help you.
[Magisk] Chris189:
Hello, I'd like to ask a question. I'm using Galaxy S7 with f2fs data and cache partitions Phoenix ROM V3 and Magisk v9 + Magisk version of Xposed Framework can't be installed. It stuck when settings permissions, it not compatible with F2FS partitions? Thanks.
[Magisk] Razor1973:
First of all, THANK YOU!

Second, I tried downloading the KDZ from that first link you gave me and there's 4 links for my device (first screenshot below). I picked the first one, the one with the most downloads, and it takes me ad.fly, which, after 5 seconds, takes me to a site that doesn't exist. I tried this in 3 different browsers in case it was a browser-specific issue.

Third, I tried using the LG Mobile Support Tool to download the files. However, since I have the latest firmware, the tool doesn't let me do anything (screenshot 2), meaning it doesn't download the firmware.

Fourth, I tried finding the firmware (latest version should he H811V20p) and ended up finding it only in this XDA thread. The name of the thread is "Stock Rooted Radio", but something tells me the KDZ itself isn't rooted or, at least, that the boot.img in it is stock. No? I don't understand this enough to be able to tell. So I downloaded that and the KDZ extractor you gave me in the second link and I was able to extract the KDZ. I noticed the KDZ only has a couple of files, all libs except a DZ file and I saw an Extract DZ button, so I assume I had to extract that one too (like a ZIP within a ZIP). I did that successfully, as you can see in screenshot 3. There's a lot of files, but I can't find anything named boot.img. It's all a bunch of BIN files and the closest is probably aboot_237568.bin. Any suggestions at this point?

Thank you again!

EDIT: After some more searching, I found that I need to merge the system files into a system.img file and then, use a tool called Ext2explore (I found and downloaded version 2.2.71) to then extract the system.img into a bunch of other files. I am hoping boot.img is there. Running right now and will provide update.

EDIT 2: system.img finished extracting and there's no boot.img in it. Back to square one?
[Magisk] AbsolutelyProprietary:
Boot img should be in dz file, and aboot is the bootloader, ask someone running stock to give you the boot
[Magisk] Razor1973:
Where in the DZ file? Did you see my screenshots above? Here's the full list of files in the DZ:

abootbak_248832.bin
aboot_237568.bin
BackupGPT_61070336.bin
boot_491520.bin
factory_917504.bin
files.txt
hypbak_246784.bin
hyp_235520.bin
laf_393216.bin
merge_output
modem_32768.bin
persist_294912.bin
pmicbak_243712.bin
pmic_229376.bin
PrimaryGPT_0.bin
raw_resourcesbak_778240.bin
raw_resources_770048.bin
rct_379904.bin
recovery_573440.bin
rpmbak_247808.bin
rpm_236544.bin
sbl1bak_241664.bin
sbl1_230400.bin
sdibak_252928.bin
sdi_234496.bin
sec_376832.bin
system.img
system_1048576.bin
system_1312904.bin
system_1576912.bin
system_1837192.bin
system_1841240.bin
system_2101200.bin
system_2361480.bin
system_2365528.bin
system_2625488.bin
system_2885768.bin
system_2889816.bin
system_3149776.bin
system_3410056.bin
system_3414104.bin
system_3674064.bin
system_3936208.bin
system_4198352.bin
system_4460496.bin
system_4722640.bin
system_4984784.bin
system_5246928.bin
system_5509072.bin
system_5771216.bin
system_6033360.bin
system_6295504.bin
system_6557648.bin
system_6815744.bin
system_7077888.bin
system_7340032.bin
system_7602176.bin
system_7604360.bin
system_7608408.bin
system_8126464.bin
system_8128648.bin
system_8132696.bin
system_8650752.bin
system_8912896.bin
system_9175040.bin
system_9437184.bin
system_9699328.bin
system_9703376.bin
tzbak_244736.bin
tz_232448.bin
[Magisk] AbsolutelyProprietary:
boot_something.bin

Rename it as boot.img and fladh it via fastboot

---------- Post added at 08:20 PM ---------- Previous post was at 08:01 PM ----------

The boot_numbers.bin , rename it to boot.img and flash it via fastboot

---------- Post added at 08:21 PM ---------- Previous post was at 08:20 PM ----------

boot_numbers.bin rename it to boot.img and flash via fastboot

---------- Post added at 08:22 PM ---------- Previous post was at 08:21 PM ----------

Thanks xda app for being stable
[Magisk] Artim_96:
I'd guess the f2fs cache partition is the problem since Magisk does changes there though I don't understand it enough to say why.

In my opinion, as long as TWRP can handle f2fs, it should at least install (btw which errors does the TWRP log say during installation?) since the most changes happen in the boot.img, but obviously there is more behind it.
[Magisk] michel sedgh:
I have a OnePlus 3 with cache and data f2fs, magisk installs without any issue but I can't get PHH superuser to work. I will try SuperSU later.
[Magisk] Artim_96:
Then I understand it even less... Maybe topjohnwu or anyone else with knowledge of the matter can look into that
[Magisk] Razor1973:
I'm not sure I have positive progress to report.

I renamed that boot_491520.bin file as boot.img and flashed it, but using TWRP's image flash functionality (as opposed to fastboot... it should theoretically be the same, from what I understand). The flash was successfully, but, as soon as the phone reboots, system.img just hangs, sits there for a while and then reboots the phone and this repeats on and on. See screenshot below. The reason I say it's system.img hanging is because if I tap on the screen repeatedly while it's in this state, a message pops up saying system.img is hanging and asks if I want to wait or kill it. I tried both with no lock.

In order to get my phone working again, I tried finding a stock boot.img elsewhere. I find older versions all over, but the only place I could find the latest 20p version is in this XDA thread. I used the "LG-G4-H811-20p-stock-rooted.zip" link, extracted the boot.img from the ZIP and flashed it using TWRP again. The phone booted just fine and CheckRoot said the phone wasn't rooted. I went back to recovery mode, flashed phh's SuperUser and rebooted. Still no root. Back to TWRP, flashed Magisk-v9, then phh's SuperUser again and rebooted. CheckRoot now said the phone was rooted. I enabled the Hide feature in Magisk Manager, made sure I selected Android Pay as well as any Google or Android application, opened Android Pay, tried to add a credit card and got the typical error.

What am I doing wrong? :(

Thank you for your continued help, all of you who've offered it. It really is invaluable.

UPDATE: So I decided to START OVER from scratch and used LGUP and the latest KDZ to reflash the phone to 100% stock. Then, I installed TWRP, flashed Magisk, flashed phh's SuperUser, installed Magisk Manager, enabled Hide, selected Android Pay and Google Play Services and voilá! I was finally able to add a CC in Android Pay! Next, I figured I'd install my custom ROM again, which uses the Aroma installer and, this time, I actually read and stored the install log, which makes it clear this ROM installs SuperSU. I then uninstalled SuperSU (by flashing the UnSU uninstaller), reflashed Magisk and phh's SuperUser, rebooted and that's it... Android Pay broken again. It's definitely something with the ROM. I tried one last thing... I flashed the stock kernel boot.img... No luck. So I am using LGUP once again, going back to stop and repeating every step except the ROM.
[Magisk] MiAndrew:
Not working magisk v9 on xiaomi.eu_multi_HMNote2_6.12.1_v8-5.0

Installing causes bootloop on RedMi Note 2 on weekly 6.12.1. Try on clean install.

On 6.11.17 everything was fine. Can't even get to TWRP through Vol+
[Magisk] santos_10:
Hi! I have a N6 and I'm trying to install V4A but I can't, I get busybox error and I don't know how to fix it, pls help :(

I already installed Busybox from stericson but it doesn't work and continue showing the error.
[Magisk] Didgeridoohan:
Have you tried using the built in Magisk busybox?
[Magisk] rester555:
I currently have nitrogen OS installed on my Nexus 6 running sdk25 Android 7.1. I have PHH Superuser r266 installed with magisk and magisk manager. I tried searching the forums for this issue and I couldn't find it. A lot of people are using hide my root which I don't think works with PHH Superuser.

Anyone know a way to hide the Su binary from DirecTV now?
[Magisk] Didgeridoohan:
My base setup: Nexus 6, stock 7.0 with November security patch and Franco Kernel r57. Magisk v9 and Magisk superuser r266-2.

When it doesn't bug out because of the "losing root" bug, Magisk Hide works pretty well for me to hide root from apps.

Magisk Hide is made to work with Magisk phh's superuser.
[Magisk] yochananmarqos:
"Not working* tells us nothing. Provide a TWRP log.
[Magisk] oreo27:
Just looking to get some insight. What are the benefits of using Magisk to install mods besides Safety Net and Android Pay?

To be honest, I don't fully understand the whole systemless issue which apparently started with Marshmallow.

Right now, I have SuperSU flashed using TWRP. How can I know if this is a systemless Root? If I were to switch to Magisk's implementation, how would I go about it?

Thanks!
[Magisk] AbsolutelyProprietary:
Magisk is a kernel modification that runs before your OS and allows you to modify almost every aspect of your device without actually modifying the OS. It also means that you can run multiple ROMs side by side. Systemless means not modifying /system aka the OS. To install magisk you flash the zip from the recovery. What device do you have?
[Magisk] Didgeridoohan:
For me, the benfits from Magisk are that after an update I don't have to redo a bunch of modifications. Pre-Magisk I had to do several restarts during my update process, changing build.prop settings, replacing system files (ui sounds), re-rooting, reflashing Xposed (when I still used that), and so on. It'd take 20 to 30-ish minutes to get everything working as I want it.

Yesterday when the December factory images dropped for my Nexus 6, I downloaded it to my phone, extracted system.img and boot.img (everything else was the same as the previous patch) and flashed them directly in TWRP. With that done I flashed a custom kernel (Franco's) and Magisk v9 in TWRP and rebooted. 5 minutes spent, updated and with all my mods and root intact. Priceless!
[Magisk] oreo27:
Okay. So basically, it makes the modification without actually modifying the contents of the /system partition?

While SuperSU modifies the /system partition?

I'm on a Xiaomi Mi Max.

---------- Post added at 04:33 PM ---------- Previous post was at 04:24 PM ----------

That does sound like a huge benefit!

Congrats on the Nougat update (second one I believe?). I'm still waiting on MIUI to release Nougat for my device. :fingers-crossed:

So basically, Magisk keeps all your mods somewhere separate from /system; meaning I can go ahead and update my system partition (which normally removes root, xposed and other mods since they reside there), simply re-flash magisk (to patch boot.img I presume?) whenever I have a ROM update?

Side note. Why did you stop using Xposed?
[Magisk] AbsolutelyProprietary:
There's systemless supersu

Check if you have an su folder in /
[Magisk] oreo27:
Yes, I do have the /su path at the very root of the device. Does this mean I'm on a traditional install or in systemless mode?
[Magisk] AbsolutelyProprietary:
If the su binary is in /su/bin then you are systemless
[Magisk] oreo27:
Upon entering /su/bin, this is what I get:

/su/bin/app_process
/su/bin/daemonsu
/su/bin/su
/su/bin/sukernel
/su/bin/supolicy_wrapped
/su/bin/sush
[Magisk] AbsolutelyProprietary:
Yeah, you're systemless, what device do you have?
[Magisk] oreo27:
Nice! So I can go directly to flashing Magisk then as per the instructions? I'm using a Xiaomi Mi Max on MIUI 8 (Android 6.0).
[Magisk] Didgeridoohan:
Correctamundo!

And on the side note: No Xposed for Nougat and I only ever used it for Amplify and Greenify. On Nougat I have seen very little if any difference in battery life since switching to only using Greenify in root mode...
[Magisk] AbsolutelyProprietary:
Check the main thread for instructions
[Magisk] MiAndrew:
MiAndrew

Fing a solution: install v8, then upgrade to v9 in sistem - all working.
[Magisk] oreo27:
That sounds lovely. I do need Xposed for some tweaks I'm running so there's that.

Checked it out. It was fairly easy. Thanks!

[MENTION=535343]all[/MENTION] - So I got it working already thanks to your suggestions and encouragement. Here's what I did.

Flashed Xposed uninstaller.

Full unroot option using SuperSU < Couldn't revert back to original boot.img but that didn't bother me that much since if I have to do it again, Magisk will take care of it.

7. Flash Magisk < This takes care of dm-verity and encryption through boot image patching. Same as SuperSU does.

8. Flash latest phh's SuperUser

9. Reboot into the device.

10. Install phh's SuperUser from the playstore - https://play.google.com/store/apps/details?id=me.phh.superuser

11. Install Material Design Xposed installer:

*http://xdaforums.com/xposed/material-design-xposed-installer-t3137758 - Material Design Xposed installer. Use this. Make sure to go to the MIUI tab and select the latest SDK which is also the Magisk variant.

All is working well now! To top it all off, I have an MIUI update. So my procedure would be:

1. Flash update.zip in TWRP.

2. Flash Magisk.

3. Flash phh's SuperUser

Is that correct?

Sidenote, is the "Enable BusyBox" option recommended for BusyBox? Or is there another thread dedicated for Magisk for BusyBox?
[Magisk] Didgeridoohan:
Great you got it running.

If you used Magisk phh's superuser (currently r266-2) you can skip step 3. Otherwise it looks good.

If you enable Busybox in Magisk there's no need for anything else.
[Magisk] AbsolutelyProprietary:
Uninstall busybox if you have it in system, use magisk busybox.

I don't know about the update, I think you can keep magisk if you save the boot.img and magisk image beforehand
[Magisk] oreo27:
This defenitely made my day. I've been brushing off reading about Magisk because I never really saw a benefit for myself until now. Couldn't have come at a better time since an update is available for me.

Sounds good. Enabled Busybox.

Alright. I'm downloading the update.zip for my device now.

I don't have to relfash anything else after re-flashing magisk after the update? What about Xposed?
[Magisk] Didgeridoohan:
Since you're not using Magisk Xposed (right?) it'll probably be wiped with the update... Edit: I re-read your post.

Any mod you've installed as a Magisk Module will still be there after a system update (as long as you leave data intact, of course).

Anyway, let us know if it works out or if you crash and burn. :D
[Magisk] oreo27:
That's pretty neat. This will make updating so much better. Well, I guess I better do a backup before flashing the system update :D I'll let you kind folks know what happens. :highfive:

Edit- By the way, if I were wanting to swtich back to SuperSU? How can I make this work with Magisk? I currently have phh's SuperUser installed.

Edit 2 - Nevermind. Just disabled the phh package in magisk manager, flashed superSU then flashed magisk again. Still waiting for it to boot since I also installed the MIUI update. Will report back once it's completed but it's looking a-ok so far.

Edit 3 - Works like a charm. All my userdata is intact, I'm updated and I don't have to reconfigure everything. Thanks!
[Magisk] TubbyStubby:
when flashing magisk v9 i am getting an error unable to extract zip. using galaxy s4(i9500) stock lollipop with twrp 2.8.6.
[Magisk] hokiealumnus:
Use a PC to unzip and re-zip the file with 7-zip. The G3 has that problem with it too.
[Magisk] TubbyStubby:
Tried re-zipping. Although, unable to extract error has gone, now i am getting new error - unable to flash zip.
[Magisk] Shailesh1711:
Mobile not rooted after flashing Magisk & ph Supersu. as per instructions

I have installed Magisk & flashed ph Supersu mentioned as in instruction on my LEEco Le1s (x507). But my mobile shows not rooted. Please help.
[Magisk] Didgeridoohan:
If help is wanted, information is needed. At least a recovery log from the installation and a Magisk log would be useful as well.
[Magisk] Shailesh1711:
How to get these log files? Please advice.
[Magisk] JimSmith94:
This should probably have its own thread, since I'm sure many people would like to use this for Android Pay. Is the timeout required because Tasker would need root to turn root on?

This task doesn't seem to work for me. I'm not that great at Tasker, but the task"plays" without error. I assigned it to a profile that activates when Android Pay runs. I haven't tried to actually buy anything with Android Pay, but I do see Tasker getting superuser rights when it starts. However the Magisk app still shows rooted and it fails the SafetyNet check. Am I doing something wrong?
[Magisk] knpk13:
If you're talking about magisk, yes I've been using it on CM and custom kernel with systemless xposed and phh super user/ SuperSU from since it's launch.

If you're talking about Android Pay, then no I haven't used it yet.

Cyanogen OS (not CyanogenMod) can be considered as a "stock" rom since it come preinstalled on certain phones as the default ROM.

---------- Post added at 02:46 AM ---------- Previous post was at 02:45 AM ----------

:confused: there's already a separate thread for magisk phh superuser and Android pay discussion. Check the OP.

---------- Post added at 02:50 AM ---------- Previous post was at 02:46 AM ----------

Go total stock and remove all xposed (like wanam). Flash magisk and then SuperSU or phh superuser and then xposed systemless.
[Magisk] :
Can you try it with the Variable Set block deleted and the setprop magisk.timeout %TIMEOUT change TIMEOUT to 300?
[Magisk] knpk13:
Go total stock and remove all xposed (like wanam). Flash magisk and then SuperSU or phh superuser and then xposed systemless.
[Magisk] Apexpredator12:
Will try it thank you
[Magisk] knpk13:
Read the OP. Just restoring stock boot.img is enough. But remove all instances of all types of xposed before you follow the steps outlined. Also you can use the thanks button instead of writing thank you.
[Magisk] Apexpredator12:
That's the problem I have is removing xposed that's why I wanted magisk installed so I can log into snapchat again it's been almost a year. No uninstaller I find will remove xposed framework either bootloops or it won't flash
[Magisk] JimSmith94:
I don't see any mention of Tasker in that thread, but I agree that this discussion should be moved there or a new one started.

Sorry, that didn't make any difference. Does it work for you?
[Magisk] :
I'm on a custom ROM so Magisk don't work, I also happen to have a Nexus device so I'm really hosed. Those are the exact commands that Magisk Manager app runs which is weird.

Can you try this:

Open up a terminal

1. Type su

2. Type setprop magisk.timeout 300

3. Type setprop magisk.phhsu 0

Maybe tasker having problem running it as root, those above commands should work. Maybe [MENTION=4470081]topjohnwu[/MENTION] can shed some light?
[Magisk] JimSmith94:
No errors from the terminal, but no difference on the phone either. As I said, Tasker runs the task with no errors too. I'm running stock rooted on a Nexus 6.
[Magisk] devilloki:
thank u , where can i upload
[Magisk] bigorangekitty:
trying to install Magisk v3 on freshly rooted vzw samsung galaxy s5 5.0 BPB1. Custom stock rom (this thread http://xdaforums.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370/ ) with Kingroot set to allow access. Reboot to TWRP, and install the magisk v3 zip and it has been sitting at flashing new Magisk boot image for 20+ minutes. Not sure on process length or anything. Please advise. Please be gentle. I'm somewhat a newb and have been reading and reading and absorbing tons of info. Not worried about root or flashing back to stock or whatever. Got all that down.

Any guidance would be greatly appreciated.
[Magisk] mobileman88:
You might want to restore the stock boot before flashing magisk
[Magisk] rgawenda:
I'm running Magisk v3, phh's superuser, systemless xposed v86.4, and systemless hosts add blocker, on latest CyanogenOS. Everything works.
[Magisk] gohamstergo:
why dont you just reflash boot AND system? or backup your apps and wipe the phone? why would you wait over a year for someone to solve a problem that you could solve yourself in an hour max?.....
[Magisk] JudgeDread11:
I have successfully installed magical v3 and phh root and Xposed 86.4 on my Asus Zenfone 2 laser.

I guess not all Asus have a non standard boot partition.

(Not using Android pay)