yashsingh1/xdaforums huggingface dataset:
[Xiaomi Mi A2 Lite Themes, Apps, and Mods] mytowyn:
This method compatible with OTA and non-rooted.

So does rooted device . :)
[Xiaomi Mi A2 Lite Themes, Apps, and Mods] Mario_97:
So i can use fluid and give it the root's permission to hide navigation bar and than use this guide https://xdaforums.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952 to update with ota ? Do you have any experience ?
[Xiaomi Mi A2 Lite Themes, Apps, and Mods] newbi33:
If I install this app and give permissions though adb cmd, can't I receive OTA updates anymore? Just wondering, rookie here :confused:
[Xiaomi Mi A2 Lite Themes, Apps, and Mods] yaco96:
Yes you are able to keep dowloading OTA Updates
[Xiaomi Mi A2 Lite Themes, Apps, and Mods] Mellow971:
I tried this app some time ago, and for some unknown reason I didn't like it.

But trying again yesterday I found it great

So far the best one for me (even though still in beta...) :good:
[Xiaomi Mi A2 Lite Themes, Apps, and Mods] leitseleac:
using this now, worth a try

https://play.google.com/store/apps/details?id=com.conena.navigation.gesture.control
[Xiaomi Mi A2 Lite Themes, Apps, and Mods] Utontissimo:
Any of these solutions work plug and play on android pie without root?

Thanks
[Xiaomi Mi A2 Lite Themes, Apps, and Mods] quintas84:
[MENTION=9541502]Utontissimo[/MENTION]

You can enable full screen with ADB commands without root

Enviado do meu Mi A2 Lite através do Tapatalk

---------- Post added at 11:48 AM ---------- Previous post was at 11:45 AM ----------

On adb

policy_control immersive.full=com.android.chrome hide nav bar for chrome or other app

policy_control immersive.full=* for all apps

More info

https://www.google.com/amp/s/www.ho...ullscreen-immersive-mode-without-rooting/amp/
[Verizon Samsung Galaxy S8+ Themes, Apps, and Mods] philweser:
I didn't create this, but while trying and failing to get a permanent non-root solution to getting and keeping my notifications AMOLED. I found the easy sure fire way to do it. It's called Mod Edit And you just pick what you want dark, and boom, done! I know a lot of you are in the same boat, I tried the overlays listed below and got bootloops. It costs 2 bucks and takes about 2 minutes to custom overlay your phone.

P.S. if this is a violation of rules, go ahead and take this down. But I am no developer on this, I just know what a pain in the butt this generally is, and man this is the best 2 bucks I ever spent.
[Verizon Samsung Galaxy S8+ Themes, Apps, and Mods] FSadino:
Thread closed!

XDA Forum Rules

7. Do not sell or trade on the forums.

If you wish to advertise a product, simply contact us. We can provide ads but you are not permitted to just post it in the forums. If you do, it will be removed and you're likely to receive a ban.

The buying, selling, trading and / or exchanging of any item is now prohibited on XDA, in any forum or via Private Messages. We now use www.swappa.com
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
Reserved
[Google Pixel XL Guides, News, & Discussion] Juhler:
Once again, fantastic guide :D Big thanks :highfive:
[Google Pixel XL Guides, News, & Discussion] NepoRood:
Way to be on top of things [MENTION=4810220]Homeboy76[/MENTION], Job Well Done, once again :good:
[Google Pixel XL Guides, News, & Discussion] TENN3R:
Do OG Pixels need magisk 1671 or 1674?

Pixel 2 and 2 xl have some troubles, so there is a specific magisk version for them in the flash kernel thread, before flash I just wanna make sure 1671 won't cause issues, thank you.
[Google Pixel XL Guides, News, & Discussion] v8088:
Hi.

Can anyone tell me?

I want to flash Android Pie.

Now I'm on official Lineage OS 15.1 + twrp 3.2.2 + Magisk

I need to do step 3 (and flash all to both slots)?

Return Phone to Stock

Or I need to do step 4 (and flash all only once)?

Install Factory Image

Thanks in advance.
[Google Pixel XL Guides, News, & Discussion] djl236:
Did anyone dirty wipe (remove -w) when updating from July's 8.1 to today's (August) 9.0 on the Pixel XL?
[Google Pixel XL Guides, News, & Discussion] NepoRood:
I did, but I was running FireHound v4.7 (July Security), so I got a lot of different FCs, lol (Hey, I had to try). If you're on stock, you'll probably be fine.

I just installed TWRP 3.2.3, did a factory reset and setup fresh. No issues after that.

I had to use Magisk beta 16.7 to root. I did a restore with TiBu and all my previous apps are working fine.
[Google Pixel XL Guides, News, & Discussion] lesp4ul:
Hi, i followed this (already 9 with OTA) :

Boot Bootloader

Connect the phone to the Computer with USB cord.

Copy twrp-3.2.2-0-marlin.img to the platform-tools folder or folder that has fastboot in it and rename it twrp.img.

Open a Command Prompt on your computer.

At the Command Prompt type:

Code:

fastboot boot twrp.img

and press enter.

When TWRP boots

Disconnect phone from computer.

Swipe to allow modifications.

Tap Install select

twrp-pixel-installer-marlin-3.2.2-0.zip

Swipe the slider to install

After TWRP is installed

Reboot Recovery (Tap the back button, Tap reboot, Tap recovery.)

then

flash Magisk-v16.7(1671).zip - (BETA)

Swipe Slider to Install

Save Log

Reboot System

did not install custom recovery tho

it stuck at google logo. do i need to flash custom kernel?
[Google Pixel XL Guides, News, & Discussion] jeremyafrank:
I have this same problem, using 3.2.3. Not installing TWRP, I installed Elemental X alone and it works fine. It's when I try to install Magisk 16.7 that it bootloops on the Google Logo
[Google Pixel XL Guides, News, & Discussion] lesp4ul:
found this , magisk 16.7 1674

https://drive.google.com/file/d/106ZiqeQxNYtCHkOEc6niuHRcWiCzG_eA/view

didn't work either lol
[Google Pixel XL Guides, News, & Discussion] jeremyafrank:
I'm going to have to go back to 8.1 (had done a dirty flash, but I'm only running stock) until this is sorted. Some nice things I'd like to play with in Pie, but not at the expense of root.
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
1674 is for Pixel2/Pixel2XL

[TAIMEN/WALLEYE] [9.0.0] [4.4.146] [CLANG 7.… - Pg. 284 | Google Pixel 2 XL
[Google Pixel XL Guides, News, & Discussion] v8088:
Where is my mistake?

I flashed Pie image marlin-ppr1.180610.009-factory-90a4fa8b

(flash all.bat)

And had a lot of errors (Screenshot attached).

After reboot to system I have Lineage OS 15.1 that I had before.

View attachment 4566763

Thanks in advance.
[Google Pixel XL Guides, News, & Discussion] Ketawa:
Yes, this is how I updated.

- I was on stable Magisk 16.0 so I flashed the most recent Magisk uninstall ZIP in TWRP to be safe, since 9.0 requires the Magisk 16.7 beta

- boot to bootloader

- flash-all.bat removing -w

- fully boot to system

- turn off, boot to bootloader

- fastboot boot new TWRP 3.2.3-0

- install TWRP 3.2.3-0 ZIP

- install Magisk 16.7 ZIP

- boot to system

- I had to reauthorize root access for all root apps and enable systemless hosts in Magisk

Device passes SafetyNet and is certified in Play Store.
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
1674 is for Pixel2/Pixel2XL: [TAIMEN/WALLEYE] [9.0.0] [4.4.146] [CLANG 7.… - Pg. 284 | Google Pixel 2 XL
[Google Pixel XL Guides, News, & Discussion] boky38:
Anyone try going from 8.0.0 directly to 9? I haven't done updates in forever. Don't want to just try and end up messing things up for myself.
[Google Pixel XL Guides, News, & Discussion] bschatzow:
I did with no problem.
[Google Pixel XL Guides, News, & Discussion] pairedprototype:
I did a dirty install from Stock 8.1 with only Magisk.

Installed TWRP, Elemental and Magisk in that order rebooting to system in-between each one. It seems as soon as Magisk 16.7 is installed, many apps fail to launch or break, i.e. the Google Play Store can no longer open without force closing, Titanium Backup errors because it can't read the TB Pro key, going into settings and trying to change some things causes the UI to freeze up. But some apps like Twitch does work. Though Magisk is broken as well, i.e. Magisk Hide doesn't work but root access is detected. Safety, however, fails both on the inbuilt test in Magisk Manager and the SafetyNet app.

If I open Magisk Manager and install 16.0 apps goe back to working fine, but Magisk is still broken in the same way and SafetyNet still won't pass.

Reading back through the thread, I see that some get boot loops due to Magisk, but for others, it works fine and SafetyNet passes which I find odd... Either way, I guess we'll all have to wait for the next Magisk update!

EDIT:

Turns out, running the Magisk Uninstaller zip, then flashing the Magisk 16.7 zip seems to solve the issue! :D

Can confirm Magisk Hide now works and SafetyNet passes. Seems like running the uninstaller is a good step to add into this guide if the user was previously running Magisk.
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
[MENTION=738333]rubledub[/MENTION]

"... but i missed #7L, the step of flashing the Magisk uninstaller ... on both slots ... "

Step 7L is: "If you are rerooting, tap*Install, select Magisk's uninstaller.zip, Swipe the slider to*install."

"it was being recognized and recovery booted fine after several reboots of the recovery doing a reset if."

Do you mean reboot?

Somebody posted these, I don't know who maybe one of them will help with Pixel XL phone recognition:

A

1. Go to C:\Windows\INF

2. Find the file "wpdmtp.inf"

3. Right click the file and click 'Install'

4. Once that is done, simply plug your phone and it should work

B

Open device manager with phone plugged in, the phone that has the yellow on it, right click, choose disable driver. Then pick to select new driver. It should give you a choice between a USB & USB composite, choose composite and it should work.

When you Pixel XL phone is recognized:

a. Update SDK Platform-tools to r28.0.1

b. Use twrp-3.2.3-1.img and .zip.

c. flash the boot.img to both slots: Do #6 B

(You will not lose your Data)

d. Do #7
[Google Pixel XL Guides, News, & Discussion] BrikHaus:
After sideloading into twrp, did you flash the twrp.zip before flashing magisk?
[Google Pixel XL Guides, News, & Discussion] rubledub:
Ok that's how I read it during the process too. That is literally the only step i didn't do. ANY ideas why i cant boot into OS, or recovery now? Or why it all of a sudden quit showing in ADB?
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
That was only part of my answer, here is the complete answer: XDA App is not posting my 'complete' answer.

"... but i missed #7L, the step of flashing the Magisk uninstaller ... on both slots ... "

Step 7L is: "If you are rerooting, tap*Install, select Magisk's uninstaller.zip, Swipe the slider to*install."

"it was being recognized and recovery booted fine after several reboots of the recovery doing a reset if."

Do you mean reboot?

Somebody posted these, I don't know who maybe one of them will help with Pixel XL phone recognition:

A

1. Go to C:\Windows\INF

2. Find the file "wpdmtp.inf"

3. Right click the file and click 'Install'

4. Once that is done, simply plug your phone and it should work

B

Open device manager with phone plugged in, the phone that has the yellow on it, right click, choose disable driver. Then pick to select new driver. It should give you a choice between a USB & USB composite, choose composite and it should work.

When you Pixel XL phone is recognized:

a. Update SDK Platform-tools to r28.0.1

b. Use twrp-3.2.3-1.img and .zip.

c. flash the boot.img to both slots: Do #6 B

(You will not lose your Data)

d. Do #7
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
Is your computer recognizing your Pixel XL phone?
[Google Pixel XL Guides, News, & Discussion] rubledub:
Inf file "isnt installable using this method."

In Device Manager my "Android Device" is showing "Android Bootloader Interface" all ready to go and up to date in that tree. Yet I'm still get nothing returned running through adb devices prompt command.

I am using a fresh lite version official from Google for ADB.

Yes sir I did mean reboot! It just baffles me why after having adb and recovery, like I never even booted or tried to boot into the OS, and just attempting to reboot recovery started this. Tried to reboot recovery, get the bootloader unlocked message, google splash with unloack icon, and then starts back over back to bootloader message.

---------- Post added at 10:38 AM ---------- Previous post was at 10:04 AM ----------

so update.

out of desperation ... even immediately after running the adb devices command and getting zilch returned i ran the fast boot twrp.img command and got success!?! explain that one i can NOT. extracted factory boot.img, rebooted into bootloader, found joy on both slots and successfully got OS booted.

i am done phoning for the day gents! cheers to Homeboy for all your assistance and assurance i was aiming down the right track after being absent for so long.
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
"i ran the fast boot twrp.img command and u success!?! explain that one i can NOT."

:)Great!:)

What is the "...fresh lite version official from Google for ADB"?

Did you get it from here?: SDK Platform-Tools for Windows
[Google Pixel XL Guides, News, & Discussion] rubledub:
Yes. I simply got the sdk tools. The issue seems to be stemming from Magisk. I can boot after unlocking bootloader and flashing recovery. Could the no booting issue from the Harmony Kernel? Because it will install and then Magisk but then won't boot. So I reflash boot image through fastboot reinstall recovery and boot. Kernel still there. I'm so at a loss.

I'm done now ... Maybe it's been too long indeed. Is there any way to rid myself of this failed Android update OTA notification or is just going back stock my best option?

In returning to to stock and relocking bootloader ... On step #3B4 I am unsure if you are wanting to verify that -w is present in the file name or when you type the command or something else all together.

Sorry for all the trouble but thanks for the patience.
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
I wouldn't relock my bootloader. I would not risk bricking my phone.

If you want to lock the bootloader #3 B4 is verifying -w is present in flash-all.bat.
[Google Pixel XL Guides, News, & Discussion] CodeTrooper:
Also having the noboot bug after Magisk flash. Didn't change kernels or anything. Just TWRP and Magisk flash and it don't werk. Followed instructions correctly and watched a YouTube video with same instructions.

Okay from the start. Pixel XL. I'm pretty sure my phone has never been rooted. The original owner says he thinks the phone was with Verizon. I unlocked the bootloader yesterday. I Successfully installed TWRP. Then I reboot into recovery and try to flash Magisk (which works). However, when I try to reboot into the system, it hangs for a while at the G logo with a loady bar underneath it. Then it reboots into recovery/TWRP. I tried switching slots, installing in different slot places, etc. I also tried the method where Magisk app patches stuff, but that reboots into stock recovery.

I can fix it by flashing boot.img to both slots. But then TWRP is gone and I'm not rooted. I'm trying to figure out the differences in both crowds on here - the successful and the ones in bootloops. Differences could be the XL and the not XL, carriers like Verizon or Google Store, I dunno. There is just this little something that makes it work or not work. Unless those people are lying when they say they got it to work, which I doubt they lied.

Edit #iforgothowmanyedits

I had latest software I'm pretty sure, I downloaded SDK platform-tools stuff from the Google website yesterday and my phone is being detected. I also got Magisk and TWRP files yesterday.

Oh I forgot to say that when I used Magisk's patched boot image, once it begins to boot the system but then reboots into the stock recovery, the stock recovery says my system is corrupted or something. I can't check what exactly it said cause I'm using the phone to write this, but the problem may lie in the system not the bootloader. Like the system sees something it doesn't like to it aborts regular booting and reboots into recovery. Just a theory though.
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
Ok!

Use the flash-all.bat file to install the factory image

Don't forget to remove the -w from the flash-all.bat file.

Then root it.
[Google Pixel XL Guides, News, & Discussion] CodeTrooper:
Okay, the "flash all" file thing is new. But I forgot to remove "-w", so mid operation I stopped it, and removed "-w", but then it got a bunch of "can't write" errors. Anyways, I continued on after retrying, and it does the same thing. Reboots into TWRP.
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
:eek:... so mid operation I stopped it, and removed "-w", but then it got a bunch of "can't write" errors.

I wonder would it have worked without the 'mid operation' stop.

I guess we'll never know.
[Google Pixel XL Guides, News, & Discussion] CodeTrooper:
Haha, yeah that was reckless of me. I didn't want to mess stuff up by using the excecutable with -w though. I guess I might just reflash everything back to stock and relock. (It can be re-unlocked after if I wanna try again, right?) It's not like I need root urgently. Thanks for helping me anyways. ??
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
"It can be re-unlocked after if I wanna try again, right?"

Honestly, I don't know.

I wouldn't relock the bootloader. I wouldn't want to risk bricking my phone.
[Google Pixel XL Guides, News, & Discussion] oneders65:
Same problem

I am having the same problem. I tried using Magisk 17.0 and 17.1.

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

In settings for TWRP I unchecked (unselected) "Reboot after installation is complete" and I unchecked "Prompt to install TWRP app if not installed."
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
Were you able to install Magisk after unchecking reboot after installation is complete, and prompt to install TWRP app if not installed?
[Google Pixel XL Guides, News, & Discussion] oneders65:
Yes. Rebooted in TWPR manually.
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
Great!

I'm waiting for other Pixel XL users with twrp bootloop problem to confirm this works.

[MENTION=7807812]CodeTrooper[/MENTION] [MENTION=9383599]Snowpuppy[/MENTION] [MENTION=4244154]H0wdy[/MENTION] [MENTION=738333]rubledub[/MENTION]
[Google Pixel XL Guides, News, & Discussion] oneders65:
Premature fix.

Iost root. I can Magisk 17.1.zip flashed but it still boots into TWRP. Cannot get past custom recovery.
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
So, I guess the above solution doesn't work

Did you try fastbooting the boot.img to boot slots then flash the magisk uninstaller.zip before flashing magisk-v17.1.zip?
[Google Pixel XL Guides, News, & Discussion] Phalanx7621:
The problem with trying to fix an issue without wiping your phone cleanly is that we can't pinpoint whether the problem is within the system or a hardware defect or something else. So when diagnosing an issue, the first thing you should do is a clean install, wiping the entire phone by allowing the flash all bat file to do it's thing and flashing the latest system image. Remember that when that's done you have to allow the phone to boot up once into Android before rebooting into bootloader and booting into TWRP. If those steps are followed, we will have a much better idea of where the problem occurs.
[Google Pixel XL Guides, News, & Discussion] zomgqwert:
I went through it last night using my Pixel XL. It was running an older version of Android with super su, so I followed Step 3 of the guide to restore it to stock 9.0 with a full wipe. It worked fine with no issues. I then decided to do the Magisk install with TWRP and followed those steps. Did the flash, ran the initial setup to set PIN, powered off to recovery, booted to TWRP, installed it, rebooted to system fine. Then when I came to Magisk step, I rebooted back into TWRP after having booted the phone to system, ran the uninstaller for Magisk for good measure, rebooted back to TWRP, ran the Magisk installer, and hit the reboot to system button. System wouldn't boot up and after a few attempts to boot it went back to TWRP recovery. Running the uninstaller, the system booted with no issues, but of course no Magisk install.

For good measure I repeated the procedure for stock reset, and tried without TWRP running into the same issue. Also tried using 17.0 just in case.

Anything else I should try?
[Google Pixel XL Guides, News, & Discussion] Phalanx7621:
If no one else responds I'll give my exact steps tomorrow , I don't have time tonight.
[Google Pixel XL Guides, News, & Discussion] oneders65:
Is this the right fix

Is this the right fix?

I read this thread when I was looking for a fix.

Here's the trick... It doesn't mean you can't do these in any other way but you will NOT get stuck if you follow some simple rules...

Roms only flash while in Slot_A

Gapps only Flash in Slot_B

Kernels only flash in Slot_B

Magisk only flash in Slot_B

IMG Flash to Slot_B

TWRP 3.2.0-0 ONLY

TWRP 3.2.0-0 to either slot

Do NOT EVER Flash anything other then TWRP, Rom Gapps and Vendor until GOING through first boot. Yes you can but it increases your issues.

Always always always double check between every install the status of your Overlays folder. Before every rom install Mount System then Go to File Manager and Delete that folder from Slot B before you boot to Slot A to flash the rom. This can hold Data from Magisk and Mods that get all tore up Everytime... It also happens when you reflash Magisk or dirty flash a rom. I'm going to put together a fresh flash below and I'll get into that a little later.

https://xdaforums.com/pixel-xl/how-to/slota-b-how-to-flash-roms-magisk-kernel-t3754175

1. I reinstalled the latest TWRP following the installation thread instructions. When I was booting into the system in slot B TWRP was not I could not get the phone to reboot into TWRP recovery.

2. I made sure Magisk uninstall was flashed into slot A and B to remove as the instructions for Magisk says to do to remove from the system.

3. I flashed Magisk into slot A with TWPR and tried to booted into system slot A and the system would not boot. It would boot into TWRP.

4. I flashed Magisk into slot B with TWPR and booted into the system in slot A and Magisk was not in the system. I booted into the system in Slot B and Magisk was installed and I had root.

I came from Verizon Samsung Note 3 and the flashing and installation for Pixel is entirely different. The thread above was a great guide to give me an idea of how and where to install roms, Gapps, Kernels, IMG, and TWRP. It is an old guide but it shines light on what to do and what not to do. If you have other guides for tips please share.
[Google Pixel XL Guides, News, & Discussion] xdeathsbanex:
heres what i did when i was stuck in the loop back to twrp:

1: flashed the magisk uninstaller to slots A and B

2: flashed 8.1 with full wipe

3: once booted i OTA to 9.0

4: turned on usb debug

5: fastboot twrp

6: installed twrp on both slots

7: booted up Pie

8: reboot into twrp

9: flashed the uninstaller to both slots again

10: flashed magisk 17.1 on both slots

11: booted u pie without the annoying loop

that worked for me. hopefully it'll work for others as well
[Google Pixel XL Guides, News, & Discussion] zomgqwert:
Thanks for these two replies, I think I understand things better now. I'm completely new to how the two slots work on the pixel and this has cleared up a few things. I'll be attempting it again this weekend with this info in mind.
[Google Pixel XL Guides, News, & Discussion] altwu:
i don't flash the twrp zip. i just fastboot boot twrp and then flash magisk. i tried again with the lastest google sdk platform tools(r28.0.1) and twrp-3.2.3-1 and everything worked fine.
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
If your 'exact steps' are different from the steps/methods already posted for installing the factory image via the flash-all. bat file, side loading or OTA and rooting with magisk-v17.1.zip. Please share your 'exact steps'. Why? Some, Pixel XL owners are still 'boot looping' when trying to root with magisk-v17.1.zip.