Database Info

Systemless Root Help

So I have been struggling the past few hours trying to get the Systemless root to work. I've followed all of the guides on this and the Magisk forum and yet the SafetyNet fails. Here are the steps I have taken:
Downloaded H830 10i ZIP
Downloaded Magisk v7 ZIP
Downloaded phh superuser magisk r259 ZIP
Boot into TWRP
Format Data
Flash the three ZIP files one at a time in the order mentioned
Flash no-veirfy
Reboot System
Step through setup page
Install Magisk Manager apk
Install phh SuperUser apk
Install SafetyNetHelper
The end result of all of that is a failed SafetyNet. Am I missing something? I would really appreciate any help. Thanks

SafetyNet has been undergoing an impressive number of revisions over the past few weeks. Most recently, this past weekend, it effectively shut out the majority of rooted users. There are reports of it shutting out folks purely for having an unlocked bootloader, particularly with the Nexus 6P.
Specifically for our G5, here's my history:
Magisk v7 and earlier was working well up until a few weeks ago. Safetynet was updated to detect Magisk in general. End of that chapter.
Chainfire and phhusson, the 2 main root leaders in Android, each came up with their own workarounds to evade SafetyNet. Chainfire came up with suhide, to be flashed after his supersu zip, and phhusson released his own version of phh root which also hid root from SafetyNet.
These worked for about a week until SafetyNet adapted. suhide was then updated with a manual script to run which evaded it again for several more days. This was working for me on Sunday morning. And then it didn't anymore. There were many variations people then advertised (using different root switch apps, etc), but none worked for me.
Magisk v8 was just released, which includes a setting to hide Magisk and root from SafetyNet. However, this does not work to fully evade Safetynet, and thus Android Pay won't start. It may be that SafetyNet is now looking at other things, such as unlocked bootloader status, and Magisk's presence is irrelevant.
Specifically, while working with these, I accidentally reset my G5 to near stock conditions (no root, encrypted data partition), except for the TWRP recovery and unlocked bootloader. Safetynet checker apps FAILED on this near pristine stock phone. This is disconcerting.
In short, there's no way I've found to get a SafetyNet pass since this past weekend. You could try returning completely to stock and relocking the bootloader, which will also probably wipe all your data, to test this theory, but not worth it in my book.

seconding what waylo said. i was trying all day to get safetynet to pass but i flashed the stock rom, did a factory reset, and still couldn't get safetynet to pass (all i had was unlocked bootloader + TWRP)
i think we just have to wait until we get a custom kernel with the boot verify checker that safetynet uses patched

Thanks for your help a few months ago. Given the time for Magisk to mature I was wondering if Magisk on the H830 is now possible. From reading throughout this forum, some users have had success but no one has an official guide. I just got a new LG G5 (gps issue) and I finally unlocked the bootloader and installed TWRP following the Noob Friendly Guide. Along the way I had to enter in the following code to keep my device from TWRP boot looping:
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1 conv=notrunc
Once I got the 20a software version up and running I went ahead and flashed Magisk 12.0, went into the Magisk Manager Settings, turned on Busybox/Magisk Hide/Systemless Host, and performed a SafetyNet Check. The end result is a failed CTS Profile Mismatch. Did I miss something or did Google patch SafetyNet again?

SomeguynamedBentley said:
Thanks for your help a few months ago. Given the time for Magisk to mature I was wondering if Magisk on the H830 is now possible. From reading throughout this forum, some users have had success but no one has an official guide. I just got a new LG G5 (gps issue) and I finally unlocked the bootloader and installed TWRP following the Noob Friendly Guide. Along the way I had to enter in the following code to keep my device from TWRP boot looping:
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1 conv=notrunc
Once I got the 20a software version up and running I went ahead and flashed Magisk 12.0, went into the Magisk Manager Settings, turned on Busybox/Magisk Hide/Systemless Host, and performed a SafetyNet Check. The end result is a failed CTS Profile Mismatch. Did I miss something or did Google patch SafetyNet again?
Click to expand...
Click to collapse
You need to install the latest v13 beta. It's on the magisk threads. Uninstall v12 with the magisk uninstaller and immediately install v13.

waylo said:
You need to install the latest v13 beta. It's on the magisk threads. Uninstall v12 with the magisk uninstaller and immediately install v13.
Click to expand...
Click to collapse
Awesome! Got it. Hopefully the learning curve from here on out as Google rolls out patches is not as steep so I can keep up!
A word to those reading this thread: you need to reboot after turning on Magisk Hide and Systemless Host in settings (as of 6/19/17).

Magisk v9 with 6045

Hi to all
I am trying to install magisk v9 in stock ROM without any success. Always after the installation phone boot to bootloader.
The Bootloader is unlock and when I un-install the magisk v9 the phone working properly.
Any idea how we could install magisk v9

Try factory reset or another version. I had installed Magisk v7, and few days ago updated to v9.

Great finding!!!
In Stock 6045 it is possible to install magisk-v7 or Magisk-v8.

In stock 6045 (5.0.2-010 02) it isn't possible to install Magisk-v9 via Manager or temp TWRP.
In case of temp TWRP device is stack to bootloader. It is possible to uninstall Magisk to work properly or install Magisk-v8
Any idea how to overcome the issue

totalcmdext said:
In stock 6045 (5.0.2-010 02) it isn't possible to install Magisk-v9 via Manager or temp TWRP.
In case of temp TWRP device is stack to bootloader. It is possible to uninstall Magisk to work properly or install Magisk-v8
Any idea how to overcome the issue
Click to expand...
Click to collapse
root your device, install permamently TWRP and no problem then

Stuck on Android splash image during boot, after downloading and installing Magisk Manager and Apk 12.0. I was rooted through KingRoot, SuperSu installed busybox as well. I uninstalled SuperSu (through in app options) getting ready for MagiskSU.
Heres the deal. Even though I have twrp working, I cant use it cuz of a broke screen. Im thinking a factory reset via hardware buttons is my best option. But how?
6045O running the Panasonic Eluga Switch. Rooted, twrp satana 3.0.0.1 installed

Magisk on Note Edge

Hi Folks
I searched for rooting the new Galaxy S8 (I might get one) and came across an app called Magisk
to root the device and it sounds pretty good.
My question is, would this work on the Note Edge, (in my case the G variant)with 6.0.1 stock rom...

hingerl said:
Hi Folks
I searched for rooting the new Galaxy S8 (I might get one) and came across an app called Magisk
to root the device and it sounds pretty good.
My question is, would this work on the Note Edge, (in my case the G variant)with 6.0.1 stock rom...
Click to expand...
Click to collapse
Yes, it will work on all Android phones. Nowadays, Magisk became a famous root because it has cool features. The best feature of it is that you can hide root for specific games or programs like banking app wich can't open while the phone is rooted. I will write quick and simple below for how to flash Magisk.
1. If your phone is rooted flash unSU.zip
2. Flash Magisk v12.0
3. Wipe Dalvik/cache
4. Reboot and wait to update the programs about 10-15mins
5. When the phone is booted install the MagiskManager v4.3.3. which is not available in PlayStore anymore
6. Open Magisk and go to settings
7. Enable BusyBox and Magisk Hide (This will pass the SafetyNet security)
8. Go back tap to check SafetyNet (It will be green coloured) and you're done
Now u have Magisk with a rooted phone and a lot of features inside

Sweet...Thanks a million... I think I start from scratch anyway with flashing a stock rom...
so, just to be safe, I flash stock (let it boot and make the initial setup)
then flash recovery, and there I flash the Magisk file and at last install the
Magisk app and thats it... or is there something else, I've seen ont the S8 tutorial
that there is another file to be flashed in recovery... but I assume this has something to do with security features from Android 7/Samsung...

So, i have a Note Edge SN 915G stock ROM 6.0.1
Tried to flash in ODIN custom recovery TWRP so I can flash Magisk from recovery. It didn't work, because the reboot restores the stock recovery back.
Tried again by not rebooting and removing the battery after flashing in ODIN the TWRP. The custom recovery remained flashed, this time, but it didn't open: recovery is not seandroid enforcing error.
Flashed CWM second time with ODIN, removed battery, boot into recovery (CWM worked and opened successfully).
Flashed Magisk zip from the custom recovery, but after reboot ended into boot loop, soft brick with error Set Warranty Bit: kernel.
Reflashed stock firmware with ODIN, back to normal.
Any adivce on how to flash that darn Magisk properly?
Thank you.
PS: I did not wipe davlik after flashing Magisk, though. Could this be it?

ufukan said:
Yes, it will work on all Android phones. Nowadays, Magisk became a famous root because it has cool features. The best feature of it is that you can hide root for specific games or programs like banking app wich can't open while the phone is rooted. I will write quick and simple below for how to flash Magisk.
1. If your phone is rooted flash unSU.zip
2. Flash Magisk v12.0
3. Wipe Dalvik/cache
4. Reboot and wait to update the programs about 10-15mins
5. When the phone is booted install the MagiskManager v4.3.3. which is not available in PlayStore anymore
6. Open Magisk and go to settings
7. Enable BusyBox and Magisk Hide (This will pass the SafetyNet security)
8. Go back tap to check SafetyNet (It will be green coloured) and you're done
Now u have Magisk with a rooted phone and a lot of features inside
Click to expand...
Click to collapse
Thanks a lot for the tips I have a question: After installing Magisk, I want to get Xposed installed, but it bootloops me at the Samsung logo every time, with the zip sdk23 of xposed by the official thread of rovo89 (thanks for his great work), and also with the xposed 23 at Magisk Manager. Did you get it systemless Xposed to work with Magisk in our Note Edge?

telefon notum kenar n915f magisk'in en son sürümünü indirmek istiyorum ancak indirmek istediğim sürümü indiremiyorum v 22.0

I want to download the latest version of magisk but I cannot download the version I want to download is v 22.0

[Help]Can't bypass Safetynet 1.27.401.5

I have tried everything to bypass safetynet I even tried flashing stock rom with untouched system image and I still get safetynet fails
does the new update adds verified boot meaning that if the device has an unlocked bootloader it won't bypass safetynet ?

AlMaghraby said:
I have tried everything to bypass safetynet I even tried flashing stock rom with untouched system image and I still get safetynet fails
does the new update adds verified boot meaning that if the device has an unlocked bootloader it won't bypass safetynet ?
Click to expand...
Click to collapse
You need magisk to pass safety net since you unlocked your bootloader

Just flash LeeDroid and be done with it. Easy.

I formated restored untouched system image installed magisk and universal safetynet fix v2beta5 and all good thanks for the info.

Official Xposed for Nougat is out! Post your Xperiences...

Have you installed official Xposed for Nougat?
Does it work fine on your MotoZ?
Any performance issues/lags?
Please add details on your ROM version, root method and if you have Magisk installed too or not...
Thank you.

I have this rom
Android Nougat on Moto Z (All Unlocked Versions) and rooted in the way that post says.
Installed xposed OK via TWRP, modules are correctly checked and enabled but didn't work, for example greenify didn't recognize that xposed is installed so didn't show the option.
Now I have missed data connection so am going to reinstall the same rom on the dirty way to not lose data and reinstall everything.

lilloscar said:
I have this rom
Android Nougat on Moto Z (All Unlocked Versions) and rooted in the way that post says.
Installed xposed OK via TWRP, modules are correctly checked and enabled but didn't work, for example greenify didn't recognize that xposed is installed so didn't show the option.
Now I have missed data connection so am going to reinstall the same rom on the dirty way to not lose data and reinstall everything.
Click to expand...
Click to collapse
Two things...
- Greenify needs to fix its compatibility with Nougat, it's a known bug
- It is *needed* to use new official Xposed apk v.3.1.2 to manage modules activation. I've seen that unofficial or old version aren't able to enable them properly...

Thanks I have just read that about greenify, the list of compatible modules with nougat is short at this time guess so
Sent from my XT1650 using Tapatalk

Mine doesn't boot with xposed installed.
Stock 7.1.1 with turboZ and magisk

I remember that installing magisk caused a bootloop on my stock 7.0

I had forgotten what modifications I did to my 7.0 stock (retus), trying to flash Xposed on it prevented it from booting (probably because of verity-dm) so I restarted from scratch.
1) Downloaded 7.1.1 stock from here and flashed it. Downloaded and installed 2 OTAs from system updates then.
2) Flashed latest TWRP (3.1.1-0).
3) I've read various reports of latest Magisk not working on Moto Z. Gave it a try though. Flashed Magisk v14.0, everything went well and I got back root access.
4) Tried installing systemless Xposed, however install failed from Magisk Manager, flashing the zip succeeded in recovery but Xposed wasn't recognized after reboot.
5) So I flashed classic Xposed (arm64) following these instructions, everything went fine (after one very long reboot).

Hi my fried. How long time this reboot in minuts?
Thanks
Ano59 said:
I had forgotten what modifications I did to my 7.0 stock (retus), trying to flash Xposed on it prevented it from booting (probably because of verity-dm) so I restarted from scratch.
1) Downloaded 7.1.1 stock from here and flashed it. Downloaded and installed 2 OTAs from system updates then.
2) Flashed latest TWRP (3.1.1-0).
3) I've read various reports of latest Magisk not working on Moto Z. Gave it a try though. Flashed Magisk v14.0, everything went well and I got back root access.
4) Tried installing systemless Xposed, however install failed from Magisk Manager, flashing the zip succeeded in recovery but Xposed wasn't recognized after reboot.
5) So I flashed classic Xposed (arm64) following these instructions, everything went fine (after one very long reboot).
Click to expand...
Click to collapse

josenilsantana said:
Hi my fried. How long time this reboot in minuts?
Thanks
Click to expand...
Click to collapse
It took maybe 15-20 minutes for the first reboot.

For me systemless Xposed install e worked properly too.
Ano59 said:
It took maybe 15-20 minutes for the first reboot.
Click to expand...
Click to collapse