yashsingh1/xdaforums huggingface dataset:
[Magisk] basily:
Bootloops with Androind 9.0 Pie on Pixel 2 XL

The title says it all. Has anyone successfully installed Magisk with the update that dropped today? Just installed 9.0.0 (PPR1.180610.009, Aug 2018), all looks fine, but when I go into Magisk manager to patch boot, it fails to patch if I use the stable Magisk, patch works for beta magisk, but then I get bootloops. I have attached 2 logs, the earlier one is with the failed stable patch, and the later is the successful beta patch which gives me bootloops. Thanks in advance for any help.
[Magisk] BubuXP:
I don't know how (I have some suspects), I reflashed everything once again and this time it seems to work, both 16.0 and 16.7 versions. :confused:
[Magisk] Galactus:
I have but I did start from scratch

Flashed Android 9 factory image, restored all my apps etc

Fasboot booted twrp

Flashed Flash kernel

Flashed twrp

reboot to make sure the kernel flashed

reboot back to twrp

flashed magisk beta 1674

Sorted. No reboots, safetynet passed
[Magisk] basily:
Thanks. Good to know. I tried installing without TWRP (just flashing the patched boot image in bootloader) and without a wipe, so either one of those could be my issue. I guess installing TWRP *might* be the easier option? I thought it wasn't working on the Pixel 2 XL yet - is my info old?
[Magisk] newyesor:
Hi,you can tell me about flash kernel on Pixel 2XL.

My devices is Pixel 2XL .
[Magisk] Galactus:
Must be lol. I've been using TWRP since March.
[Magisk] Badger50:
It's arguably the best kernel out there. Made by the kernel ninja warrior himself! :good:
[Magisk] Galactus:
https://xdaforums.com/showpost.php?p=77264906&postcount=2878
[Magisk] basily:
Welp, installing Magisk via TWRP caused me bootloops too. I guess I either need to do a clean install or wait for an update... Bummer. I wish I hadn't updated to P...
[Magisk] thedesp:
I sideloaded Android 9 OTA image from 8.1 July patch then fastboot boot twrp and flash latest Magisk beta (1671).

Looked like it was gonna boot loop but after a few hold-down-the-buttons reboot it finally worked and now working flawlessly.
[Magisk] quietsche:
Did you wipe or used the modified version ( https://www.xda-developers.com/flash-monthly-security-update-google-pixel/ )?
[Magisk] thedesp:
No wipe.

Dirty flash using OTA image.
[Magisk] EstiR86:
Very interesting idea, hmm wonder if it's possible.
[Magisk] :
Still only flashable through Flashfire, TWRP still fails.

Flashfire's flashing queue was:

Magisk uninstaller + wipe dalvik/cache/storage + beta (b3da28e) + wipe dalvik/cache/storage; reboot:normal.

A7 2017 (SM-A720F, stock boot with no-verity-no-encrypt.zip, stock, debloated ROM).
[Magisk] Skittles9823:
You don't have a vendor partition then. Samsung devices normally (I don't think any have one except maybe the galaxy nexus?) Have a vendor partition.
[Magisk] slimdick:
When the viper module turned off safetynet pass, when enabled false [emoji14]

http://cloud.tapatalk.com/s/5941cbb9573c2/Screenshot_20170615-013756.png?

http://cloud.tapatalk.com/s/5941cbc6822a1/Screenshot_20170615-013745.png?

http://cloud.tapatalk.com/s/5941cbd8cf2f7/Screenshot_20170615-014836.png?

http://cloud.tapatalk.com/s/5941cbf1ec28a/Screenshot_20170615-013928.png?
[Magisk] wirelesskebab:
:crying: I posted logs, if I don't have a vendor partition, then that would mean that isn't the problem then :confused: :eek: Not sure why it won't mount. :( :eek:
[Magisk] Skittles9823:
Have you tried trying to install on a clean install?
[Magisk] dilshahdirar:
Does this beta version fix yesterday's Pokémon Go issue. I bricked my phone yesterday thinking the the issue was with magisk and reinstalled it.

Can you add a new option too? To make safety net bypass while Xposed is active? :laugh: :D
[Magisk] :
[MENTION=4470081]topjohnwu[/MENTION]

Multi-user (any of the modes) is not working.

Screenshot is from user #2, log is from owner.
[Magisk] Sterist:
the GameGuardian app stores its' real apk in the downloaded installer apk, and then installs the real app with a randomly generated gibberish name. the initial downloaded/installer apk is then

automatically uninstalled after the real one with obfuscated name is in place and no two devices or versions share a common name. seems bulletproof :) [MENTION=4470081]topjohnwu[/MENTION]
[Magisk] wirelesskebab:
Yes, that was the problem, I ended up just taking the new partition, flashing Magisk 12 and the app, using the flashfire app the person mentioned earlier, flashing the uninstall magisk zip and flashing the newest magisk 13, it even upgraded the app! :good::cowboy::highfive::victory::eek::cool::o
[Magisk] DragonSven:
Didn't work for me): I have a Xiaomi Mi5s with the same module installed, but doesn't bypass safety net.
[Magisk] Choobilsky:
12.0 passes safety net check in core mode

Activating any modules breaks safety net
[Magisk] The_Fry_Guy:
Passing safety net!!!

...NVM no it doesn't.
[Magisk] Ardany Jolón:
SafetyNet pass on muy LG L70.

Lineage OS 14.1 updated to the most recent build.
[Magisk] Ardany Jolón:
Errors log file.
[Magisk] BaTarrY:
Samsung uses Knox , you can't bypass bit.
[Magisk] jenslody:
I can on my J5 with latest stock + magisk v13, if I disable xposed module and osm0sis' busybox-module (in other words all modules I have installed).

If I use meefik's busybox (1.25) instead of osm0sis' busybox, I can also bypass safety-net with "active" busybox.

Even after the playstore update two days ago.
[Magisk] BaTarrY:
After all that you can use Sam pay?
[Magisk] Shen Ron:
Same problem as before, no change at all.
[Magisk] jenslody:
I don't use my phone for banking or paying.
[Magisk] Badger50:
Flash the magisk uninstaller in twrp, boot up, then go back to twrp and flash 1674 again.
[Magisk] FSOP:
That worked perfectly, thank you :)
[Magisk] spleenandcigars:
- Did a factory format

- Android P sideloaded (using official google OTA)

- flashed TWRP

- rebooted, everything fine

- flashed Magisk 16.7v

- bootloop directly into TWRP

- factory format > TWRP

- Magisk 16.0v

- bootloop

- uninstalled magisk and everything booted normally.

Well... Guess it's time to wait for another version ):
[Magisk] Badger50:
Did you run the magisk uninstaller before updating to the 1674 version of magisk?
[Magisk] spleenandcigars:
Tried with both versions, uninstalling after each one of them. In both cases, i only could boot after uninstal Magisk. Tried the 16.0v, uninstalled, tried the 16.7v, uninstalled.
[Magisk] spleenandcigars:
Pixel XL.
[Magisk] Badger50:
Then I'm not sure. I'm using a P2XL. However, it might be worthwhile to try a custom kernel as well. I ran the magisk uninstaller zip, then flashed a custom kernel and booted up. Then went back to twrp and flashed the magisk 16.7(4) version. However, that may only be compatible with taimen and walleye.
[Magisk] spleenandcigars:
I managed to brick an old Note 3 by flashing Kernel, since then, i don't like it very much. But thanks, i'll wait to see if an update come.
[Magisk] IlyaKol:
I have a P2XL too. So, this is the process I should follow? Can you confirm it's working for you?

1) Uninstall Magisk

2) Update to Pie (I usually use flash-all.bat without overwriting data)

3) Boot phone to let it finish updating anything internally

4) Flash latest TWRP

5) Reboot to TWRP

6) Flash Magisk 16.7(4) (where does one get this version...or is the download link the OP the right one? EDIT: Found it... https://xdaforums.com/pixel-2-xl/de...ernel-1-00-t3702057/post77240449#post77240449)

7) Flash ElementalX (my kernel of choice)

8) Profit?
[Magisk] Badger50:
Yep, that should do it my friend :good:
[Magisk] tyler19820201:
I was updating my magisk to the latest stable version. v16.0 because one of my banking app did not work...

After updating everything looks fine. I have a bunch of banking apps on my phone and all works well only this Santander UK app does not. I am applying the same settings for all the app so Magisk settings should be ok. Magisk Hide checked as well.

I was trying uninstall magisk from TWRP, then wipe chache & dalvik and then reinstall again but does not work.

I am using OP3T-- LineageOS--Multirom

Any clue?:confused:
[Magisk] IlyaKol:
Thanks for confirming. Gonna go get me some pie!
[Magisk] basily:
Maybe dumb question, but, isn't it redundant to uninstall magisk if you're going to use flash-all.bat? I also did flash-all.bat (with no wipe) and ended up with bootloops if i install magisk by flashing the patched boot image via fastboot in bootloader, and if i install via twrp it bootloops into twrp.

Could uninstalling magisk first make the difference??? I don't see how... Worth a try i suppose. I'm on P2XL btw.
[Magisk] Badger50:
The flash-all.bat will remove root, but doesn't remove all the system files associated with magisk. Hence, the uninstaller :good:
[Magisk] stewie2806:
Lloyds bank app update recognises root,

I even tried uninstalling both Lloyds and magisk, rebooting, installing Lloyds again and logging in, then installed magisk again, rebooting and then use hide on the banking app, reboot and it works the first time.

Then when I logout and login with llpyds it's boots me off with the 'we've detected root' warning.

*edit: I'm using magisk 16.7 on G930f with TGP

2.2.2
[Magisk] IlyaKol:
[MENTION=3730810]Badger50[/MENTION] ...how long did your phone sit at booting TWRP (to reflash it permanently)? I'm using 3.2.3.-0. Should I go back to the last version?
[Magisk] Badger50:
I always disable screen lock before I begin any of this. With that said, it only took about 15-30 seconds after I fastbooted it.
[Magisk] vMAC:
Has anyone else noticed that SafetyNet check no longer works with Android 9.0? When I try it it states "Received Invalid Response." Although GPay still works and all other "root checking" apps don't find root.

I have a Pixel 2XL with the August update to 9.0.

Let me know if anyone needs logs.
[Magisk] IlyaKol:
Good point. I'm going to do the same.
[Magisk] Ketawa:
I have a Pixel XL and the SafetyNet Test app answers successful on all tests on Android 9.0, my device is certified in Play Store, and I can use all root checking apps. I can't use the Magisk SafetyNet check because I always repackage Magisk with a random name.
[Magisk] tyler19820201:
I think you should use the latest stable 16.0 and try with preserve forced encryption and dm verity

However i do not know ur kernel...
[Magisk] GillRigged:
So, I been using Magisk quite a while my Verizon Pixel XL with unlocked bootloader and have been able to successfully OTA to download. However, if I use Skipsoft's software to flash the full image and reinstall Magisk by fastbooting TWRP everything goes back to working just fine UNTIL next month when it's OTA time again. Am I missing something here?

What I do:

1) remove fingerprints and go to swipe to unlock screen

2) use Skipsoft's software to download and install new image

3) go back to Skipsoft's software to fastboot TWRP and install Magisk with Manager already installed

Any help would be really appreciated here. My whole point to using Magisk is so that I no longer have to use my laptop for updates.
[Magisk] bunklung:
I have a Pixel 2 and have the same issues as vMAC. I have not confirmed if AP actually works. Ketawa, are you using 1674 or just 16.7?
[Magisk] Ketawa:
16.7 aka 1671. I have a regular Pixel XL.
[Magisk] bunklung:
I have only two apps that have Hide enabled. They don't even launch. Any app I add to hide does not launch. Anyone else notice this?
[Magisk] peterlee928:
apologies in advance, dunno if i should be posting in this thread or the general help thread.

running 1674 beta, pixel 2xl, no custom roms/kernels (except busybox... not sure if that counts). not passing safetynet but have read that some folks are... seems like a mixed bag?

see attached log :)
[Magisk] qianjie:
Mi mix2s is now Android P, tool support?
[Magisk] basily:
Quick question - I've searched but really can't figure this out - what are those toggles for exactly?

---------- Post added at 09:08 PM ---------- Previous post was at 08:53 PM ----------

Yup. I used the uninstaller, and now it's all good. Not a moment too soon either - I don't know how people live without root man! Now we just need someone to create a module that moves the clock back over to the right, and removes the phantom notch...
[Magisk] DanGLES3:
These toggles when enabled prevent magisk from removing either dm-verity (kernel level system integrity check) and Forced encryption(for devices that come encrypted by default)
[Magisk] Itachisasuke:
Correct me if I'm wrong here but those check boxes only apply when you are flashing something directly from Magisk Manager.

There is currently a bug on the 16.74 release for the Pixel 2 XL that doesn't keep the "Keep Forced Encryption" checked when closing and reopening the app.
[Magisk] greyhd:
Another pixel 2 xl owner with the same issue. I rolled back to 16.0 after starting from scratch and all is well now.
[Magisk] romracer:
Happens to me too on a P2XL running Android 9 Pie and 1674 magisk.
[Magisk] tennyleaz:
MIUI 10 oreo on Mi Note 3 (jason):

Magisk v16.7 flash successfully.

Modules works.

Will NOT past saftynet. Both cts profile and basic integrity failed.

Before magisk zip flashed, saftynet will pass, both cts profile and basic integrity will pass.

Any possible solution?

edit:

can't see any log in /cache/migisk.log or in magisk manager app.
[Magisk] fmotta:
Not working on Miui 10 Android P Mi Mix 2s XE model with Global Dev

It wasn't working also on previous Miui 10 Global Dev based on Oreo. While it was working with same room on XA models.

For XE I used SuperSU but now it's failing too on Android P. Hope someone finds a solution

Inviato dal mio Mi MIX 2S utilizzando Tapatalk
[Magisk] tyler19820201:
The verity and encyription features you have just thick in at the main screen of Magisk where you can see the version number . Under the Tap to start SafetyNet check.

However you can try alternativately to download an older version of the banking app apk if you find...

This is my struggle as well with my Santander banking app as well. However i have Lloyds also and just works fine.

It is quite strange...

Here i was succesfully installed the app:

Reinstall the app then Reboot

Install the app then hide it on Magisk then Reboot

Register the device and log in to the banking app

Everything looks fine but...

If i log out and later want to log in again it will detecting the rooted device again...:confused::rolleyes:
[Magisk] quietsche:
Working for me, did it quite similar to you. Having TWRP, ElementalX and Magisk on Pixel 2 patch July, so no OTA works.

1. removed magisk with magisk uninstaller

2. did a July patch with flash-all.bat without wiping

3. updated to Android 9.0 Pie

4. fired up bootloader, fastboot into TWRP

4. installed TWRP, ElementalX and Magisk 16.74

5. reboot

6. working :good:

7. waiting for Xposed pn framework 28 :silly:
[Magisk] look4alec:
I took similar steps on my PixelXL, but getting stuck at the G screen. When I uninstall, it works fine but no root so I can't restore with Titanium backup.

My steps:

1. Installed 9.0 Pie with flash-all.bat, wiping everything

2. fired up bootloader, fastboot into TWRP

3. installed TWRP (3.2.3-0), ElementalX and Magisk 16.74

4. reboot

5. Stuck at G, eventually resets to TWRP

I've tried 16.71, 16.7, 16.4, 16.0 (stable) and no luck. I tried a clean wipe and installing without ElementalX. I stupidly didn't make an image before wiping the second time so that wasted another few minutes. I'm now trying to force reset a bunch of times as someone in another thread said something about this working.

Anyone have a take on this? Thanks :)

edit: Would it change anything to flash Magisk via fastboot?
[Magisk] basily:
Did you try flashing the magisk uninstaller in TWRP first? That's what made the difference for me. What I did:

1. Flash all (no wipe) the full 9.0 firmware in bootloader, boot and allow to finish installing.

2. Installed TWRP, booted to see if all good, it was

3. Flashed magisk uninstaller in TWRP - booted, all good

4. Flashed Magisk 16.74 in TWRP.

5. Profit!
[Magisk] exist2resist:
I'm trying to patch boot for a Pixel XL2, I have Pie on the Pixel but Google changed the way the Images are delivered in the ZIPs now.

I used to just pull it out of the official google ota images.

Can I pull the boot.img from the OTAs or do I need to do it via fastboot after upgrading the phone?
[Magisk] The_Fry_Guy:
Is the latest beta download in the first post the 16.74 one?
[Magisk] Badger50:
That's likely the 1671 version. However, here's the 1674 version :laugh: https://drive.google.com/file/d/106ZiqeQxNYtCHkOEc6niuHRcWiCzG_eA/view?usp=drivesdk
[Magisk] Ingenium13:
get it from the factory image
[Magisk] exist2resist:
Thanks, didn't realize there were two download sections for the factory and ota images respectively.

Thought it was all on one page.

---------- Post added at 12:32 PM ---------- Previous post was at 12:26 PM ----------

Is there a way to force Magisk Manager to recognize a specific version of the ZIP?

I don't have TWRP.
[Magisk] Badger50:
Probably is, but I don't know it. You could always fastboot into twrp and use it temporarily. Then again, I don't know what device your using. So that may not be an option :confused:
[Magisk] exist2resist:
Yeah was thinking the same.

Pixel XL2
[Magisk] Badger50:
Same here. You shouldn't have any trouble then :good:
[Magisk] exist2resist:
I think that's a TWRP bug, I just got that trying to boot into TWRP via fastboot boot.
[Magisk] Homeboy76:
Isn't the 1674 version for the Pixel2/Pixel2 XL?
[Magisk] Badger50:
Yep :good:
[Magisk] exist2resist:
Thanks for the assistance got 16.74 running on the Pixel XL2.

TWRP is a bit messed up for the Pixel 2 running Android 9 but I managed to install the Zip.

TWRP crashes and hangs in some instances on Pie, specifically when you leave the USB cable plugged in or let the screen time out.

However way better process to temporarily boot into TWRP, will opt for that from here on in.
[Magisk] jollyb:
I'm trying to use DKB Tan2Go App, but no luck. Tan2GO app it's crashing. maybe i get till step where I need to enter the Password after I click on the button "Einrichten", but that's it.

3D Secure Option is also not working. The DKB Banking app is recognizing my root.

Magisk Version 16.0, OnePlus 3 OOS 5.0.4.

Does it work for you, on the Magisk Version 16.0?

EDIT: FOUND the solution.

In german:

es funktioniert mit Android 9 und magisk.

Ich musste magisk vertseckt installieren (Magisk/Einstellungen/Magisk Manager verbergen),

dann habe ich die app aus dem PlayStore installiert,

danach in megisk hide die app vor root rechten versteckt und die app hat super mit root funtioniert
[Magisk] mattman83:
Mix 2s XA global model was working fine on Oreo global betas (with magiskhide props module). Update to P beta, flash magisk patched boot image (I am told twrp not working yet) and magisk is there, root is functioning, basic integrity passes but cts does not.

No changes to config otherwise, was just a dirty flash over previous which worked perfect.

Using 16.7 of course.

M
[Magisk] Roi Danton:
Hello,

I was trying to get root with Magisk on a Xiaomi Mi A2 Global but this was not possible, yet. Unlocking the bootloader and installing TWRP worked good. I tried beta 16.7 (1671) and also 16.0 stable. And I discovered 16.7 (1674) here in the thread and also tried. No chance. It looks good without any errors in TWRP when installing Magisk but nothing is there when I boot the phone.

Are there issues with this phone? Did I do something wrong?

Cheers,

Roi
[Magisk] 3tes:
Hello i have a Samsung galaxy S8 and magisk hides my safety net not.
[Magisk] Didgeridoohan:
On Pie you can no longer change some props the way we've gotten used to. The build fingerprint is one of them, which means there's no easy fix for passing the ctsProfile if your ROM/device isn't certified.

But, don't loose hope. There should be a future update to the resetprop tool to fix this (no ETA).
[Magisk] Roi Danton:
I did it! Used this Magisk boot image and have Magisk 16.0 running on the A2.
[Magisk] mattman83:
Cheers for the reply and thanks for all the work so far on your module :) I figured it was something fingerprint related. And no stress, google pay is not running (not the end of the world, always carry wallet anyway) but Netflix, pogo etc and other root detect apps still all seem to be happy and are running the way things are even with the cts fail.

Will keep an eye on your thread :)

M.
[Magisk] AndrOmega:
latest 16.7 works flawless on my S7 Edge Oreo and passed safety check !

:good::good::highfive::highfive:
[Magisk] kalehrl:
Leeco le s3 x522, Lineage 14.1, Magisk 16.7 and safetynet check reports:

ctsProfile: false

basicintegrity: true

Is this normal?
[Magisk] ellrazor:
So I have this problem, in the first image safetynet passes, next second i repeat the test and the second image shows up and no more changes, i can't overpass this issue i'm running magisk 16.7 and manager 5.8, really need a solution because everything I tried doesn't work.

Thanks in advance
[Magisk] ryanfraser38:
My Google pay won't verify my card it briefly bring up a loading g circle then disappears, is this magisk related? It's hidden and tried everything I can think of
[Magisk] extreme79:
Samsung galaxy tab pro + lineageos 14.1+latest beta magisk: it fail safetynet and seems not hide root to apps (Banking app detect root, skygo app detect root too).

uninstalling from recovery seems to left traces because skygo works again, but Banking app still detect root (but device is not root ed anymore).

OnePlus one + lineage 15.1+latest magisk beta: root works, safetynet fail, hide root seems work partially (Banking app detect root, skygo not and it works but it's not the same tablet app)
[Magisk] Dreamer(3MF):
Check This Post https://xdaforums.com/oneplus-one/development/rom-tugapower-7-0-t3766296/post77287601#post77287601.
[Magisk] Parnas72:
Probably the banking app memorized in its own data that the phone is rooted, and won't work again unless you reinstall the app from scratch.
[Magisk] jcmm11:
I can't test (lost root and TWRP, no computer at the moment to get it back. Not happy. Plus I don't have Pie) but you may be able to get around this for the moment. Get a copy of build.prop, modify it as desired, mount it using simple mount. I can think of ways to automate this in fs-data, but it's not worth it for a temporary fix (script to get copy of build.prop, sed to make change, run global bind mount for build.prop)
[Magisk] extreme79:
Already done. Cleared cache+data, Uninstalled, reinstalled. Nothing. So strange.

My opo already result certified

Samsung result as not certified..
[Magisk] docluv01:
On android 8 and 9, tried 16.7, but magiskhide doesnt seem to be hiding root for my apps. Had to go back to android 8 , and v16.
[Magisk] WisdomWolf:
So I encountered a weird scenario on my Pixel 2 XL last night. I updated to Pie and then tried and failed several times to get Magisk installed without getting stuck on the G screen. Flashing the uninstaller, rebooting to OS, then rebooting back to TWRP to install Magisk finally worked, but I had to reinstall the Magisk apk afterwards. I thought I was finally good, but the next time that I rebooted my phone it got stuck at the G screen again, I had to reboot back to the bootloader and flash the stock boot.img to get it to boot. Has anyone that's got Magisk working on Pie on Pixel 2 [XL] confirmed that they can reboot without the phone messing it's proverbial bed?