Develop Bugs

flashing question

So do I really have to remove my password Everytime I flash something via twrp?..

egren58 said:
So do I really have to remove my password Everytime I flash something via twrp?..
Click to expand...
Click to collapse
Yes
Sent from my Pixel 2 XL using Tapatalk

browniegirl said:
Yes
Click to expand...
Click to collapse
Damm all I want is center clock that's it lol

egren58 said:
Damm all I want is center clock that's it lol
Click to expand...
Click to collapse
It sucks I know
Sent from my Pixel 2 XL using Tapatalk

Not anymore. TWRP just got updated.

rickysidhu_ said:
Not anymore. TWRP just got updated.
Click to expand...
Click to collapse
Where can I update?..

rickysidhu_ said:
Not anymore. TWRP just got updated.
Click to expand...
Click to collapse
Be cared if your wanting to flash roms or switch slots. There are reports that the new version is not working in that regard!!?
egren58 said:
Where can I update?..
Click to expand...
Click to collapse
Right about here ?
https://dl.twrp.me/taimen/

Badger50 said:
Be cared if your wanting to flash roms or switch slots. There are reports that the new version is not working in that regard!!?
Click to expand...
Click to collapse
I'm still on stock and stick to one slot so this new update is very welcome, now that it can finally decrypt! Appreciate the heads up regardless though =) :highfive:

rickysidhu_ said:
I'm still on stock and stick to one slot so this new update is very welcome, now that it can finally decrypt! Appreciate the heads up regardless though =) :highfive:
Click to expand...
Click to collapse
I'm stock room. And I have kernal installed am I safe flashing this I have no idea what slot I am though

egren58 said:
I'm stock room. And I have kernal installed am I safe flashing this I have no idea what slot I am though
Click to expand...
Click to collapse
You should be okay to flash that mod (I don't know which one it is exactly so don't hold me responsible); but I'm pretty sure you should be okay without worrying about slots, for this at least

rickysidhu_ said:
You should be okay to flash that mod (I don't know which one it is exactly so don't hold me responsible); but I'm pretty sure you should be okay without worrying about slots, for this at least
Click to expand...
Click to collapse
Sorry I meant I should be okay updating to the latest twrp. I've heard people locking up their phone in the thread.. lol

egren58 said:
Sorry I meant I should be okay updating to the latest twrp. I've heard people locking up their phone in the thread.. lol
Click to expand...
Click to collapse
Yes, if your still on 8.1, there's no trouble with it at all. Fastboot the new twrp.img, enter twrp, flash the twrp.zip, then kernel.zip, then magisk.zip. I would, for this new update, still remove your screen lock security just to be safe. Then add it back in, and you'll be fine :good:

Badger50 said:
Yes, if your still on 8.1, there's no trouble with it at all. Fastboot the new twrp.img, enter twrp, flash the twrp.zip, then kernel.zip, then magisk.zip. I would, for this new update, still remove your screen lock security just to be safe. Then add it back in, and you'll be fine :good:
Click to expand...
Click to collapse
+1

rickysidhu_ said:
+1
Click to expand...
Click to collapse
I already have twrp install couldn't it just be as flashing the updated TWRP?.

egren58 said:
I already have twrp install couldn't it just be as flashing the updated TWRP?.
Click to expand...
Click to collapse
Go ahead if you'd like. I Was merely pointing out the safe and tested method that I, and many others use to upgrade. The P2XL is a little bit of a finicky beast. I've read too many stories over the last 3 months with bootloops and soft bricks by others doing simple flashing procedures that worked fine on other nexus devices, but crap a brick on this thing. Therefore, I don't take chances

Badger50 said:
Go ahead if you'd like. I Was merely pointing out the safe and tested method that I, and many others use to upgrade. The P2XL is a little bit of a finicky beast. I've read too many stories over the last 3 months with bootloops and soft bricks by others doing simple flashing procedures that worked fine on other nexus devices, but crap a brick on this thing. Therefore, I don't take chances
Click to expand...
Click to collapse
So I have to boot into temporary recovery with adb and than flash the updated trwp img

egren58 said:
So I have to boot into temporary recovery with adb and than flash the updated trwp img
Click to expand...
Click to collapse
The procedure is as follows...
1. Put the new twrp.img in your platform-tools folder.
2. In bootloader/fastboot mode type fastboot boot twrpxxxx.img. That'll boot you into temp twrp .
3. In temp twrp, flash the new twrp.zip, then kernel.zip, then magisk.zip
4. Reboot, done :good:

Badger50 said:
The procedure is as follows...
1. Put the new twrp.img in your platform-tools folder.
2. In bootloader/fastboot mode type fastboot boot twrpxxxx.img. That'll boot you into temp twrp .
3. In temp twrp, flash the new twrp.zip, then kernel.zip, then magisk.zip
4. Reboot, done :good:
Click to expand...
Click to collapse
So I have to reflash the boot I'm and magisk too

egren58 said:
So I have to reflash the boot I'm and magisk too
Click to expand...
Click to collapse
Yes. There have been reported issues with bootloops if you don't flash your custom kernel and magisk at the end.

Badger50 said:
The procedure is as follows...
1. Put the new twrp.img in your platform-tools folder.
2. In bootloader/fastboot mode type fastboot boot twrpxxxx.img. That'll boot you into temp twrp .
3. In temp twrp, flash the new twrp.zip, then kernel.zip, then magisk.zip
4. Reboot, done :good:
Click to expand...
Click to collapse
So I have to reflash the boot I'm and magisk too?

[AOKP][PROJECT_TREBLE][8.1.0][a/b devices only][4/2/18]

This is a GSI (generic system image) for AOKP for devices with treble support...
this requires fastboot to flash the system image, if you dont know how to use fastboot, you shouldnt be here...
Downloads
https://androidfilehost.com/?w=files&flid=261339
commands:
$: fastboot flash system_a system.img
(for pixel devices= $: fastboot flash vbmeta_a vbmeta.img)
then boot into twrp and wipe data and reboot.
tested on the Pixel 2 XL
credit goes to the AOKP gang and @phhusson who without i wouldnt have been able to compile this
screenshots:
https://ibb.co/dBnFPn
https://ibb.co/kvGEH7
https://ibb.co/hOLVqS
has GApps but no root, im working on that

First!
Sent from my Pixel 2 XL using Tapatalk

slothdabski said:
First!
Click to expand...
Click to collapse
Crap missed it..

sixohtew said:
This is a GSI (generic system image) for AOKP for devices with treble support...
this requires fastboot to flash the system image, if you dont know how to use fastboot, you shouldnt be here...
Downloads
https://androidfilehost.com/?w=files&flid=261339
commands:
$: fastboot flash system_a system.img
(for pixel devices= $: fastboot flash vbmeta_a vbmeta.img)
then boot into twrp and wipe data and reboot.
tested on the Pixel 2 XL
credit goes to the AOKP gang and @phhusson who without i wouldnt have been able to compile this
screenshots:
https://ibb.co/dBnFPn
https://ibb.co/kvGEH7
https://ibb.co/hOLVqS
has GApps but no root, im working on that
Click to expand...
Click to collapse
does google camera work with hdr+? do you get unlimited photo storage?

sixohtew said:
This is a GSI (generic system image) for AOKP for devices with treble support...
this requires fastboot to flash the system image, if you dont know how to use fastboot, you shouldnt be here...
Downloads
https://androidfilehost.com/?w=files&flid=261339
commands:
$: fastboot flash system_a system.img
(for pixel devices= $: fastboot flash vbmeta_a vbmeta.img)
then boot into twrp and wipe data and reboot.
tested on the Pixel 2 XL
credit goes to the AOKP gang and @phhusson who without i wouldnt have been able to compile this
screenshots:
https://ibb.co/dBnFPn
https://ibb.co/kvGEH7
https://ibb.co/hOLVqS
has GApps but no root, im working on that
Click to expand...
Click to collapse
We should all be here not everyone can do what you do..

I can't get twrp to load after flashing.....it just hangs at the start up screen. Any suggestions? I went back to stock and flashed over that.

cdnsnOw said:
We should all be here not everyone can do what you do..
Click to expand...
Click to collapse
What I meant was if you don't know how to use fastboot, you probably shouldn't be messing with your phone because you used the wrong code and bricked it..no offense

What is the difference flashing with TWRP and fastboot method?

So far no luck getting it to boot. This is what I did.
fastboot flash system_a system.img
fastboot flash vbmeta_a vbmeta.img
then boot into twrp and wipe data and reboot
Going to update to the leatest April image and try again.

gforceriders said:
So far no luck getting it to boot. This is what I did.
fastboot flash system_a system.img
fastboot flash vbmeta_a vbmeta.img
then boot into twrp and wipe data and reboot
Going to update to the leatest April image and try again.
Click to expand...
Click to collapse
Maybe after flashing vbmeta reboot bootloader then load up twrp

cdnsnOw said:
What is the difference flashing with TWRP and fastboot method?
Click to expand...
Click to collapse
This is a system.img and needs to be flashed to the system which requires fastboot..in twrp you MUST make sure you're flashing to the system_a partition

sixohtew said:
Maybe after flashing vbmeta reboot bootloader then load up twrp
Click to expand...
Click to collapse
Yeah did that still no luck getting it to boot. Can't even switch to slot A without getting an error after fastbooting the images.

abduleo77 said:
I can't get twrp to load after flashing.....it just hangs at the start up screen. Any suggestions? I went back to stock and flashed over that.
Click to expand...
Click to collapse
Try booting twrp right after the vbmeta.img

gforceriders said:
Yeah did that still no luck getting it to boot. Can't even switch to slot A without getting an error after fastbooting the images.
Click to expand...
Click to collapse
Which device? Pixel 2 xl?

sixohtew said:
Which device? Pixel 2 xl?
Click to expand...
Click to collapse
Yep, the pixel 2 XL.

gforceriders said:
Yep, the pixel 2 XL.
Click to expand...
Click to collapse
Did you come from another rom or were you stock? This boots just fine for me

sixohtew said:
Did you come from another rom or were you stock? This boots just fine for me
Click to expand...
Click to collapse
Yes, came from another rom and when that didn't work I went back to stock and still wouldn't boot.

gforceriders said:
Yes, came from another rom and when that didn't work I went back to stock and still wouldn't boot.
Click to expand...
Click to collapse
Does it bootloop? Or boot back to the bootloader? If it boot loops are you seeing the aokp boot animation? Could you possibly get a logcat?

sixohtew said:
Does it bootloop? Or boot back to the bootloader? If it boot loops are you seeing the aokp boot animation? Could you possibly get a logcat?
Click to expand...
Click to collapse
It bootloops. No aokp boot animation. I will try and use the bootloop fix script and flash full stock and test again here shortly.

gforceriders said:
It bootloops. No aokp boot animation. I will try and use the bootloop fix script and flash full stock and test again here shortly.
Click to expand...
Click to collapse
Yeah if you tried to flash it over another rom instead of stock, issues could arise..I'll put a script together that will flash stock with the new system.img and add the vbmeta.img to it so it flashes all the necessary files

Boot hang, TWRP Recovery unresponsive

Coming to you all with hat in hand.
Not sure what steps to take next.
Unlocked bootloader and all the rest of the steps here:
https://www.xda-developers.com/google-pixel-3-unlock-bootloader-root-magisk/
Symptom is a never ending booting "G".
I reboot and can choose recovery but the twrp screen in unresponsive. As in, I get the slider but cannot slide it.
I'm not sure what that means.
I do see the device and its listed as 'recovery' in adb.
I did see the issue of using old platform tools too late. :crying:
How bleak is my outlook?
Thank you for any help.

When you booted the twrp.img did you have the newest one and then install the newest twrp installer.zip?

Short version... Extract the boot.img from the system image file and install that to both partitions through fastboot (going to have to do some reading on how to do that, and you might learn a bit in the process). System should boot normally then with stock recovery. Now, you can use the current version of the twrp.img to root without even needing to permanently install it. Before you even do that though, spend some time getting to know your device and the current versions and options that are out there. That web page you pointed to was just a primer and was published when the device first came out. Their have been some small changes.

@edmodumb - What billy said^^. From your adb folder you can fastboot flash boot.img, then fastboot boot twrp.img right afterwards to get TWRP back (and the phone will boot System as well).

pixel 3xl unlocked bootloader - installed twrp.img via fastboot- installed twrp.zip in recovery-installed magisk 17.3 via
recovery
phone booted up , no problem then i went to magisk app and installed magisk installed by direct patch and rebooted,
now struck in booloop.
if i boot into recovery twrp is unresponsive even if i reinstall with fastboot.
i tried to install factory image but still stuck in bootloop????
i tried to flash boot.img to the a and b partions with fastboot but no sure if i'm doing it right?

motrac said:
pixel 3xl unlocked bootloader - installed twrp.img via fastboot- installed twrp.zip in recovery-installed magisk 17.3 via
recovery
phone booted up , no problem then i went to magisk app and installed magisk installed by direct patch and rebooted,
now struck in booloop.
if i boot into recovery twrp is unresponsive even if i reinstall with fastboot.
i tried to install factory image but still stuck in bootloop????
i tried to flash boot.img to the a and b partions with fastboot but no sure if i'm doing it right?
Click to expand...
Click to collapse
Flash the boot image to both slots #6 in the guide or flash the factory image #4 in the guide to return to stock. then do #7 in the guide to root. Done! Do not flash the patched_boot.img.
[Guide] Pixel 3 XL Android 9.0 (Pie) Unlock/Root/Install Images/Kernels/Recovery + November 2018 Security Patch

Homeboy76 said:
Flash the boot image to both slots #6 in the guide or flash the factory image #4 in the guide to return to stock. then do #7 in the guide to root. Done! Do not flash the patched_boot.img.
[Guide] Pixel 3 XL Android 9.0 (Pie) Unlock/Root/Install Images/Kernels/Recovery + November 2018 Security Patch
Click to expand...
Click to collapse
i flashed factory and it installs but at the end i get this:
"Erase successful, but not automatically formatting. File system type raw not supported."
is that ok or is it an error?
phone still doesn't boot.
when i flash boot file i get:
"FAILED (remote: Failed to write to partition Not Found)"

motrac said:
i flashed factory and it installs but at the end i get this:
"Erase successful, but not automatically formatting. File system type raw not supported."
is that ok or is it an error?
phone still doesn't boot.
when i flash boot file i get:
"FAILED (remote: Failed to write to partition Not Found)"
Click to expand...
Click to collapse
reflashed factory after updating fastboot and it boots now, good learning lesson for me. thanks for the help

Yikes ! I am not the expert, but . . . . it really sounds like 'rma' time to me...
.
If you do things on a low battery, it'll corrupt stuff. Is this thing fully charged up ?
.

motrac said:
reflashed factory after updating fastboot and it boots now, good learning lesson for me. thanks for the help
Click to expand...
Click to collapse

Homeboy76 said:
Click to expand...
Click to collapse
@motrac @Homeboy76
Woah sounds like my problem is similar --- I can't boot into anything but a dark screen except for bootloader.
I saw the "updated fastboot"
I tried flashing the boot.img and then the factory image
but no luck --- just blackscreen when I try to do anything other than bootloader
I had some errors when flashing factory image -- see screeen shot

jcrompton said:
@[email protected]
Woah sounds like my problem is similar --- I can't boot into anything but a dark screen except for bootloader.
I saw the "updated fastboot"
I tried flashing the boot.img and then the factory image
but no luck --- just blackscreen when I try to do anything other than bootloader
I had some errors when flashing factory image -- see screeen shot
Click to expand...
Click to collapse
Is "updated fastboot" r28.0.1?

Homeboy76 said:
Is "updated fastboot" r28.0.1?
Click to expand...
Click to collapse
Yes.
Sent from my [device_name] using XDA-Developers Legacy app

jd1639 said:
Yes.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Still can't boot my device -- just no luck after updating fastboot
PLEASE .. any help would be appreciated!!
This is another place where I was trying to solve the issue - sorry for doubling up
https://forum.xda-developers.com/showpost.php?p=78276952&postcount=258

Resurrecting. Had to set aside for a while, sorry.
@sliding_billy & @v12xke , thank you for the responses. Out of around six phones, this is the first time I've had issues rooting/flashing images. That's thanks to XDA.
After your responses and some more learning (this time paying more attention to post dates), I have the phone back up on its feet.
Off to re-root, wish me luck.
Thank you very much!

I did a backup on twrp and then it wouldn't boot ugh off to try it all again LOL

edmodumb said:
Resurrecting. Had to set aside for a while, sorry.
@sliding_billy & @v12xke , thank you for the responses. Out of around six phones, this is the first time I've had issues rooting/flashing images. That's thanks to XDA.
After your responses and some more learning (this time paying more attention to post dates), I have the phone back up on its feet.
Off to re-root, wish me luck.
Thank you very much!
Click to expand...
Click to collapse
Best of luck!

Bootloop back to twrp

Yesterday i sideloaded the December ota, today i decided im going to unlock the bootloader, root and install a custom kernel. I followed the instructions in the pined post in guides and well, now my pixel wont boot and its booting back to trwp.
What i did was boot twrp.img thru fastboot.
Once twrp booted i flashed the twrp zip, kernel and magisk beta zip.
How do i get out of this bootloop now?

welp, just tried to flash the factory image and got this:
error: failed to load 'image-crosshatch-pq1a.181205.006.zip': Not enough space

mac208x said:
Yesterday i sideloaded the December ota, today i decided im going to unlock the bootloader, root and install a custom kernel. I followed the instructions in the pined post in guides and well, now my pixel wont boot and its booting back to trwp.
What i did was boot twrp.img thru fastboot.
Once twrp booted i flashed the twrp zip, kernel and magisk beta zip.
How do i get out of this bootloop now?
Click to expand...
Click to collapse
fastboot flash boot --slot all boot.img
#6 in this guide.

Homeboy76 said:
fastboot flash boot --slot all boot.img
#6 in this guide.
Click to expand...
Click to collapse
Thank you! So would you know what i did wrong? Or what do i now to get root and custom kernel?

mac208x said:
Thank you! So would you know what i did wrong? Or what do i now to get root and custom kernel?
Click to expand...
Click to collapse
Pixel 3/Pixel 3 XL
- fastboot boot twrp-3.2.3-1...img
- install Magisk' uninstaller
- add more zips
- Edit: Kernel of your choice
- Add more zips
- magisk-17.3.zip
- reboot system

Homeboy76 said:
Pixel 3/Pixel 3 XL
- fastboot boot twrp-3.2.3-1...img
- install Magisk' uninstaller
- add more zips
- ElementalX 1.02.zip
- Add more zips
- magisk-17.3.zip
- reboot system
Click to expand...
Click to collapse
Did exactly that but instead of ElementalX kernel im trying to use Kirisakura now back to bootloop into recovery

mac208x said:
Did exactly that but instead of ElementalX kernel im trying to use Kirisakura now back to bootloop into recovery
Click to expand...
Click to collapse
After installing the TWRP.zip change slots in TWRP, reboot recovery and flash Magisk to the other slot, change slots back, then reboot.

airmaxx23 said:
Change slots in TWRP, reboot recovery and flash Magisk to the other slot, change slots back, then reboot.
Click to expand...
Click to collapse
Im so sorry but what do you mean by slot?

mac208x said:
Im so sorry but what do you mean by slot?
Click to expand...
Click to collapse
When you're in TWRP go to reboot, then switch from your current slot to the other.

airmaxx23 said:
When you're in TWRP go to reboot, then switch from your current slot to the other.
Click to expand...
Click to collapse
Alright this is becoming silly. Did exactly as you said and again, bootloop back too twrp....Should i use the twrp from dees_troy or it doesnt matter? I dont know what it can be
Edit: Nvm im using the right twrp

mac208x said:
Alright this is becoming silly. Did exactly as you said and again, bootloop back too twrp....Should i use the twrp from dees_troy or it doesnt matter? I dont know what it can be
Edit: Nvm im using the right twrp
Click to expand...
Click to collapse
Are you flashing Magisk in both slots?

airmaxx23 said:
Are you flashing Magisk in both slots?
Click to expand...
Click to collapse
No didn't do that.
Okay so fastboot boot twrp.img
Once it boots flash the twrp.zip and magisk
Change to slot b
Flash magisk
Reboot.
Right? What about kernel?

mac208x said:
No didn't do that.
Okay so fastboot boot twrp.img
Once it boots flash the twrp.zip and magisk
Change to slot b
Flash magisk
Reboot.
Right? What about kernel?
Click to expand...
Click to collapse
Try just that first and see if you can fully boot the phone.

airmaxx23 said:
Try just that first and see if you can fully boot the phone.
Click to expand...
Click to collapse
No bootloop back to trwp. Now its stuck on the white google logo screen wont go pass it

airmaxx23 said:
When you're in TWRP go to reboot, then switch from your current slot to the other.
Click to expand...
Click to collapse
Be careful with that. I did it bricked the device. It was like there was no system on that slot. I thought it was hard bricked but someone else did the same thing and eventually got it to boot.
Sent from my [device_name] using XDA-Developers Legacy app

I dont know what do now, wont boot, cant enter recovery, apparently there is no system image the only thing i can do is enter fastboot. Never had this much damn trouble with rooting and installing twrp on a device.

jd1639 said:
Be careful with that. I did it bricked the device. It was like there was no system on that slot. I thought it was hard bricked but someone else did the same thing and eventually got it to boot.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I've been doing it all along whenever I flash anything.
mac208x said:
I dont know what do now, wont boot, cant enter recovery, apparently there is no system image the only thing i can do is enter fastboot. Never had this much damn trouble with rooting and installing twrp on a device.
Click to expand...
Click to collapse
You'll have to flash back to stock in fastboot.

mac208x said:
I dont know what do now, wont boot, cant enter recovery, apparently there is no system image the only thing i can do is enter fastboot. Never had this much damn trouble with rooting and installing twrp on a device.
Click to expand...
Click to collapse
First, have you updated your sdk platform tools with the latest fastboot and adb? That's been causing a lot of people problems if they haven't updated them. If you have I would flash the stock boot image to boot slots.
fastboot flash boot_a boot.img. and
fastboot flash boot_b boot.img
If that's not enough then flash the system's image to boot slots.
Sent from my [device_name] using XDA-Developers Legacy app

airmaxx23 said:
I've been doing it all along whenever I flash anything.
You'll have to flash back to stock in fastboot.
Click to expand...
Click to collapse
jd1639 said:
First, have you updated your sdk platform tools with the latest fastboot and adb? That's been causing a lot of people problems if they haven't updated them. If you have I would flash the stock boot image to boot slots.
fastboot flash boot_a boot.img. and
fastboot flash boot_b boot.img
If that's not enough then flash the system's image to boot slots.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
How do i do this now? Flashing boot.img does nothing, phone still wont boot and hands on the boot logo. I cant enter recovery and apply from adb, nor flashing the factory image thru fastboot work, it keeps saying there isnt enough space for the .zip

mac208x said:
How do i do this now? Flashing boot.img does nothing, phone still wont boot and hands on the boot logo. I cant enter recovery and apply from adb, nor flashing the factory image thru fastboot work, it keeps saying there isnt enough space for the .zip
Click to expand...
Click to collapse
Do you have the latest sdk platform tools. If not Google that, download the zip and extract it. Replace what you do have. I create a folder c:adb and put everything in that. Then set an environment variable path in Windows so fastboot and adb are available no matter what folder I'm working in.
Sent from my [device_name] using XDA-Developers Legacy app

Issues Rooting Pixel XL with TWRP/Magisk

I'm following some guides to root my pixel xl but am running to some issues.
I tried using twrp-3.3.1-0-marlin.img to load Magisk-v19.3.zip but it gives me errors mounting system and vendor.
I then tried using twrp-3.3.0-0-marlin.img to load Magisk-v19.3.zip and it appears to succeed. I reboot, but Magisk Manager never appears. When I load it manually, it tells me that Magisk 19.3 isn't installed.
I'm not sure what I'm doing wrong. Is there some hidden step?
Thank you.

ookami007 said:
I'm following some guides to root my pixel xl but am running to some issues.
I tried using twrp-3.3.1-0-marlin.img to load Magisk-v19.3.zip but it gives me errors mounting system and vendor.
I then tried using twrp-3.3.0-0-marlin.img to load Magisk-v19.3.zip and it appears to succeed. I reboot, but Magisk Manager never appears. When I load it manually, it tells me that Magisk 19.3 isn't installed.
I'm not sure what I'm doing wrong. Is there some hidden step?
Thank you.
Click to expand...
Click to collapse
Mounting errors are normal. Use 3.3.1-0
Boot TWRP image
Flash TWRP zip
Flash magisk (latest canary channel)
Reboot
Install magisk manager if necessary (latest canary)
Open magisk manager and follow any instructions.

Tulsadiver said:
Mounting errors are normal. Use 3.3.1-0
Boot TWRP image
Flash TWRP zip
Flash magisk (latest canary channel)
Reboot
Install magisk manager if necessary (latest canary)
Open magisk manager and follow any instructions.
Click to expand...
Click to collapse
Need to try this soon, glad to see it's working ?
Sent from my Pixel XL using XDA Labs

Tulsadiver said:
Mounting errors are normal. Use 3.3.1-0
Boot TWRP image
Flash TWRP zip
Flash magisk (latest canary channel)
Reboot
Install magisk manager if necessary (latest canary)
Open magisk manager and follow any instructions.
Click to expand...
Click to collapse
I've followed this along with every other guide I could find at least 10x each or more, and still haven't achieved root. Everything seems to install fine, but everytime I open Magisk Manager, it shows "Magisk is not installed". And that seems to be the only thing keeping me from getting root. There has to be a missing step or something... It's been about 5 years since I've rooted a device(HTC M8), but I don't remember ever having so much difficulty. I've wiped the phone more times than I can count, uninstalled/reinstalled Magisk(regular and Canary), tried to do this on both Android 8 and 9, tried to complete this process on both LinuxMint and Windows, etc. I'm completely out of ideas at this point.

tyler.durden said:
I've followed this along with every other guide I could find at least 10x each or more, and still haven't achieved root. Everything seems to install fine, but everytime I open Magisk Manager, it shows "Magisk is not installed". And that seems to be the only thing keeping me from getting root. There has to be a missing step or something... It's been about 5 years since I've rooted a device(HTC M8), but I don't remember ever having so much difficulty. I've wiped the phone more times than I can count, uninstalled/reinstalled Magisk(regular and Canary), tried to do this on both Android 8 and 9, tried to complete this process on both LinuxMint and Windows, etc. I'm completely out of ideas at this point.
Click to expand...
Click to collapse
Have you tried fastboot flash boot magisk_patched.img after making one in magisk manager? Are you on Android 10?
This was made from a pixel XL boot.img, Android 10
https://mega.nz/#!lQg0RaiJ!_YRjiL3nHysUeLavKt0umJjrHbSPzJsqkPVi2qIQfZE
Make sure your ADB/fastboot platform tools are up to date.

Tulsadiver said:
Have you tried fastboot flash boot magisk_patched.img after making one in magisk manager? Are you on Android 10?
This was made from a pixel XL boot.img, Android 10
https://mega.nz/#!lQg0RaiJ!_YRjiL3nHysUeLavKt0umJjrHbSPzJsqkPVi2qIQfZE
Make sure your ADB/fastboot platform tools are up to date.
Click to expand...
Click to collapse
That's definitely one that I haven't tried yet. I'm still on Android 9 for now. I downloaded the latest Platform tools just a few days ago, so that part should be up to date. It doesn't seem like there's much for Android 10 yet, so I'm waiting a bit before I switch.

tyler.durden said:
That's definitely one that I haven't tried yet. I'm still on Android 9 for now. I downloaded the latest Platform tools just a few days ago, so that part should be up to date. It doesn't seem like there's much for Android 10 yet, so I'm waiting a bit before I switch.
Click to expand...
Click to collapse
Here is the boot and patched boot from 9 August update. I typically have firmware for recent Pixel phones.
https://mega.nz/#!gRBGhYAZ!Z7mEBEHVT9V4ut0p__g5BVboS8RjLSSPWXgjurSQxbU

Tulsadiver said:
Here is the boot and patched boot from 9 August update. I typically have firmware for recent Pixel phones.
https://mega.nz/#!gRBGhYAZ!Z7mEBEHVT9V4ut0p__g5BVboS8RjLSSPWXgjurSQxbU
Click to expand...
Click to collapse
Thank you! Magisk finally installed using the boot.img patching method, and now I have root access.

Tulsadiver said:
Have you tried fastboot flash boot magisk_patched.img after making one in magisk manager? Are you on Android 10?
This was made from a pixel XL boot.img, Android 10
https://mega.nz/#!lQg0RaiJ!_YRjiL3nHysUeLavKt0umJjrHbSPzJsqkPVi2qIQfZE
Make sure your ADB/fastboot platform tools are up to date.
Click to expand...
Click to collapse
I am having the same issue, but with the Oct patch. How do I make one of these with Magisk Manager? I tried making it with the bootloader img from the stock factory image, but it fails at repackaging step. Anyone else having issue with Oct patch?

smithilberry said:
I am having the same issue, but with the Oct patch. How do I make one of these with Magisk Manager? I tried making it with the bootloader img from the stock factory image, but it fails at repackaging step. Anyone else having issue with Oct patch?
Click to expand...
Click to collapse
You meant boot.img, right?
Edit. You need to unzip the image zip in order to get the boot.img.

Tulsadiver said:
You meant boot.img, right?
Edit. You need to unzip the image zip in order to get the boot.img.
Click to expand...
Click to collapse
Yes, that's what I meant. I also got it working. I used TWRP 3.3.0 and it worked. Not sure what the reason would be.

Tulsadiver said:
Mounting errors are normal. Use 3.3.1-0
Boot TWRP image
Flash TWRP zip
Flash magisk (latest canary channel)
Reboot
Install magisk manager if necessary (latest canary)
Open magisk manager and follow any instructions.
Click to expand...
Click to collapse
Sent from my marlin using XDA Labs
---------- Post added at 10:51 AM ---------- Previous post was at 10:45 AM ----------
Tulsadiver said:
Have you tried fastboot flash boot magisk_patched.img after making one in magisk manager? Are you on Android 10?
This was made from a pixel XL boot.img, Android 10
https://mega.nz/#!lQg0RaiJ!_YRjiL3nHysUeLavKt0umJjrHbSPzJsqkPVi2qIQfZE
Make sure your ADB/fastboot platform tools are up to date.
Click to expand...
Click to collapse
This was my dilemma. I have no PC so I am using Osmosis's static fastboot magisk mod and it works excellent but because the sdk must be an updated version it does not know the command when you flash the patched boot.img the " --slots all " it says unrecognizabled command in termux and terminal emulator but everything else will flash it's just that new --slots all that gets it. Is there any way for me to get the boot.img on both slots without using that command? Can I just fastboot the boot then reboot bootloader and repeat? Would that get it on both slots?
Is it possible to install the boot.img in one slot or will that mess things up? Guide has patched boot on both...Or just boot twrp 3300 and flash a rom? I'm weary about getting too brave because I bricked a device recently that was A/B. I been around for many years and never bricked anything till recently. ?
Sent from my marlin using XDA Labs

flash713 said:
Sent from my marlin using XDA Labs
---------- Post added at 10:51 AM ---------- Previous post was at 10:45 AM ----------
This was my dilemma. I have no PC so I am using Osmosis's static fastboot magisk mod and it works excellent but because the sdk must be an updated version it does not know the command when you flash the patched boot.img the " --slots all " it says unrecognizabled command in termux and terminal emulator but everything else will flash it's just that new --slots all that gets it. Is there any way for me to get the boot.img on both slots without using that command? Can I just fastboot the boot then reboot bootloader and repeat? Would that get it on both slots?
Is it possible to install the boot.img in one slot or will that mess things up? Guide has patched boot on both...Or just boot twrp 3300 and flash a rom? I'm weary about getting too brave because I bricked a device recently that was A/B. I been around for many years and never bricked anything till recently.
Sent from my marlin using XDA Labs
Click to expand...
Click to collapse
I personally have never flashed it to both slots. Just the current slot
fastboot flash boot magisk_patched.img

Tulsadiver said:
I personally have never flashed it to both slots. Just the current slot
fastboot flash boot magisk_patched.img
Click to expand...
Click to collapse
You rock! Appreciate you telling me this! I believe I understand more now that I've read about the A/B partition for a few weeks.. Pixel XL forums actually has the most detailed information of A/B that I've seen yet. Cheers.
Sent from my marlin using XDA Labs

Tulsadiver said:
I personally have never flashed it to both slots. Just the current slot
fastboot flash boot magisk_patched.img
Click to expand...
Click to collapse
Can I fastboot vendor and bootloader, or anything instead of the entire factory image if I want to roll back to August Pie from October 10? I'm going after DU and it's an August pie build.. Thanks for the info on slots! Somehow it helped me better understand the entire partition deal... I remember you from many years ago on some Nexus device that you made various mods for.. Anyway thanks! Alot!
Sent from my marlin using XDA Labs

flash713 said:
Can I fastboot vendor and bootloader, or anything instead of the entire factory image if I want to roll back to August Pie from October 10? I'm going after DU and it's an August pie build.. Thanks for the info on slots! Somehow it helped me better understand the entire partition deal... I remember you from many years ago on some Nexus device that you made various mods for.. Anyway thanks! Alot!
Sent from my marlin using XDA Labs
Click to expand...
Click to collapse
To roll back you not only have to flash the entire image but you'll have to wipe your phone.

TWRP boot looping?
I'm trying to root a Pixel XL Android 10, purchased form Google. I'm stuck at the point of trying to boot the phone to the temporary TWRP. Using command "fastboot boot twrp.img" .
I get the "Sending, Booting, Finished OKAY" messages, but the phone then shows a never ending flash of the TWRP logo every few seconds, with no functionality.
The twrp.img I'm using is twrp-3.0.2-0-RC1-fastboot-marlin.img
Any suggestions?

SeekMocha said:
I'm trying to root a Pixel XL Android 10, purchased form Google. I'm stuck at the point of trying to boot the phone to the temporary TWRP. Using command "fastboot boot twrp.img" .
I get the "Sending, Booting, Finished OKAY" messages, but the phone then shows a never ending flash of the TWRP logo every few seconds, with no functionality.
The twrp.img I'm using is twrp-3.0.2-0-RC1-fastboot-marlin.img
Any suggestions?
Click to expand...
Click to collapse
NEVER MIND: I was using wrong version of TWRP.

SeekMocha said:
NEVER MIND: I was using wrong version of TWRP.
Click to expand...
Click to collapse
What TWRP version did you use?