yashsingh1/xdaforums huggingface dataset:
[Google Pixel 3 XL Guides, News, & Discussion] yearn2burn:
I used TWRP for installation of magisk and have tried both the regular uninstaller and the Canary uninstaller. Without magisk manager, I can't get root access to explore those locations. Can I do it through adb?
[Google Pixel 3 XL Guides, News, & Discussion] jcmm11:
You can do it via TWRP. TWRP install log when installing Magisk may tell us something as well.

A logcat when running the Magisk Manager install should definitely tell us something.
[Google Pixel 3 XL Guides, News, & Discussion] pside15:
Yeah, that was the problem, many thanks. Got TWRP installed and all rooted up.
[Google Pixel 3 XL Guides, News, & Discussion] Homeboy76:
Try this if you are not rooted:

- Do #4 'keep data'

- Open a command prompt in the Platform-tools folder

- connect phone to computer

- at the prompt type fastboot boot twrp.img

- when twrp boots, tap install and select Magisk's uninstaller (If you had Magisk Canary installed before use that uninstaller).

- Swipe slider to install

- When that finishes, tap back until you see Install

- Tap install and select Magisk...zip Swipe slider to install.

- Reboot
[Google Pixel 3 XL Guides, News, & Discussion] yearn2burn:
I did a reflash of the factory image, booted with twrp.img from fastboot, flashed the canary uninstaller then flashed Magisk 18.0. On reboot, still can't install Magisk Manager. The installer thinks it's already installed.

I'm uploading the recovery log from TWRP. I ran the canary uninstaller then the Magisk installer.

I'd be happy to run a Logcat tomorrow evening. I haven't done it before. Just give me the adb command sequence.

I looked in the TWRP file manager, and no topjohn entries in those locations.
[Google Pixel 3 XL Guides, News, & Discussion] yearn2burn:
I'm attaching the unfiltered logcat encompassing the time of the failed installation of Magisk Manager.
[Google Pixel 3 XL Guides, News, & Discussion] jcmm11:
Did you by any chance have one of the unofficial Magisk builds installed (kantjer or ianmac)? The log is showing a signature mismatch, and I'm not sure where the package signatures are stored. You can try looking in /data/system/package_cache/1/ and see if there's any topjohn references in there.

Otherwise reinstall just the apk (you can extract it from the zip) from whichever unofficial build you had and then uninstall it. Then try again.

If you have sdmaid installed (pro version?) You can try running the corpse finder.
[Google Pixel 3 XL Guides, News, & Discussion] yearn2burn:
I was on Kantjer 18.1r10. That was the problem. When I updated to the January security build, I used the Magisk flashable uninstaller. Apparently the Kantjer Magisk Manager uses a different signature, which of course makes sense. But I guess by not going through the package uninstaller, that flashable uninstaller left the signature in package manager and hence the failure to install Magisk Manager with a different signature. Installing Kantjer apk, it again asked if I wanted to modify an installed app, but this time succeeded. I then deleted it and installed the stable version. Thank You All!!!!!

PS There was a topjohn file in /data/system/package_cache/1/ but deleting it didn't make any difference.
[Google Pixel 3 XL Guides, News, & Discussion] swxtr:
adb pull /sdcard/Download/patched_boot.img

says " device not found"
[Google Pixel 3 XL Guides, News, & Discussion] Homeboy76:
- latest SDK Platform-tools r28.0.1

- USB debugging enabled

- Phone in bootloader mode

- Phone connected to Computer

- command prompt opened in Platform-tools folder

- At the prompt type fastboot devices

Do you see device serial Number?

Yes, try again: adb pull /sdcard/Download/patched_boot.img

Did it work?

No, copy patched_boot.img from phone to USB, then copy it to Platform-tools folder on computer.
[Google Pixel 3 XL Guides, News, & Discussion] avetny:
Adb sideload

i just gonna post this here....if you trying to SIDELOAD and you can't find your OTA zip in adb sideload, it's because you renamed it!

type original download name (

example:

adb sideload crosshatch-ota-pq1a.190105.004-5f23d043) And if you installed all drivers etc it will work.

Regards

Avi
[Google Pixel 3 XL Guides, News, & Discussion] Homeboy76:
Are you suggesting that if you rename the OTA 'ota.zip' you cannot find the file to sideload?
[Google Pixel 3 XL Guides, News, & Discussion] Ozark_8125:
I'm another one with a soft brick.. this is the first time in many years this has happened. I was trying to flash back to stock and then lock the bootloader. Was not paying attention in settings / dev settings / disabled OEM unlocking and then relocked the bootloader from fastboot. After formatting, it wouldn't reboot and now Device state: locked and cannot boot into recovery. I think the problem was not doing the factory reset from within android in settings before returning to stock. I was just re-flashing the Jan image and since it wipes data, I wasn't thinking about doing a factory reset from within android itself. I've also seen several reports here in this thread and on reddit about this error of being unable to get into recovery because 'Cant find valid operating system. The device will not start.'

For some reason when reflashing the Jan image corrupted the recovery / bootloader - but not quite sure why that would result from the image flash. I tried to do a .\fastboot boot boot.img with the stock img, but still no dice.

Regardless. I think the stupid thing I did was to disable the OEM unlocking in the dev settings before getting everything cleaned up.

So... how do the 'pros' fix this in this state? Do they have some kind of 'force' re-write the partitions kind of device to do a low-level format? I remember that with the samsung devices, if you really jacked it up, you could go back to kies and reformat the partitions to get a clean start. It's rough that I can do something in the android system that I can't undo in fastboot.
[Google Pixel 3 XL Guides, News, & Discussion] Homeboy76:
Post your question here: [GUIDE] Recover from soft-BRICK - fix your dead/malfunctioning phone by CZ Eddie
[Google Pixel 3 XL Guides, News, & Discussion] Ozark_8125:
Thanks - but that thread is for an unlocked bootloader... slight typo in his thread, showing a picture of a 'locked' bootloader.. :p
[Google Pixel 3 XL Guides, News, & Discussion] Homeboy76:
My mistake misread your original post. :(
[Google Pixel 3 XL Guides, News, & Discussion] jcmm11:
See if Google will exchange it
[Google Pixel 3 XL Guides, News, & Discussion] Ozark_8125:
They are, should be here tomorrow. :good:

The real nightmare is though.. that because of the esim, and maybe because I tried my old sim from my old pixel in an old phone - it cancelled my account and released my number that I use for my business. I've been in a full panic for the last couple of days trying to get it fixed and just waiting for the engineers to pull it out of what they call a 'cool down tank' whatever that actually is.. I'm rapidly loosing faith in google fi and I've been an avid supporter for the last few years - but to automatically put something as serious as your number in jeapordy that easily is foolish in my books.
[Google Pixel 3 XL Guides, News, & Discussion] jcmm11:
But the cool down is actually just for situations like this. The account was cancelled (for whatever reason, that you should probably try to understand a bit more so you can more easily avoid a repetition) but the number isn't available for reassignment until the cool down period expires.

The simpler solution for a situation like this (although you would have had to incorporate it when setting up the business number) would be to have a Google Voice number and then, when getting Fi, use the Google Voice number for the Fi account. If the Fi account gets cancelled the number returns to being your Google Voice number. I don't know if numbers can be migrated to Voice.
[Google Pixel 3 XL Guides, News, & Discussion] Ozark_8125:
That makes me more hopeful that the cool down system will actually allow them to recover my number. My business was setup long before google voice was, so wouldn't have helped me in this case. I think for business users, this is a pretty risky system and not thought out with business customers in mind.

Here on out though, what I've learned is to

always

get a physical sim card. This e-sim thing doesn't benefit the end user in any way that I see.
[Google Pixel 3 XL Guides, News, & Discussion] Darkwing_Duck:
"Newbie"

Just came from a Nexus 6 I had with Cyanogen/Lineage for many moons. Seems I have forgotten a lot.

With my new Pixel 3 XL, I have done the following:

- Unlocked the bootloder successfully.

- Installed Magisk successfully. (double verified with Titanium Backup, Tasker,.. apps I use)

So, I got itchy to try new ROMs. Guessing I didn't need to? but went to install TWRP. (maybe a comfort level with the Nexus)

- Ran "fastboot boot path/to/twrp.img" successfully. (v3.2.3-3)

- In TWRP, installed twrp.zip successfully, by the screen. (v3.2.3-3)

- Rebooted to system and was bootlooped in TWRP.

- Ran "flash-all.bat" from extracted "crosshatch-pq1a.190105.004-factory-7165155c.zip" successfully.

- Currently on security patch "January 5, 2019", with bootloader still showing unlocked.

Feedback on where I went wrong is welcome. (being begged for)

Thank you!!!!
[Google Pixel 3 XL Guides, News, & Discussion] rickysidhu_:
I usually do the following, and it works:

Flash stock boot img

Fastboot boot TWRP

Flash TWRP

Flash custom kernel

Reboot recovery

Flash Magisk

Reboot system
[Google Pixel 3 XL Guides, News, & Discussion] Homeboy76:
If you want to flash a Custom ROM (#11) pick one then follow the instructions in the OP of the Custom ROM you picked to install it.
[Google Pixel 3 XL Guides, News, & Discussion] Darkwing_Duck:
Confusing, since on:

https://xdaforums.com/pixel-3/development/twrp-3-2-3-0-pixel-3-t3861622

On page one, they say:

fastboot boot path/to/twrp.img

This will temporarily boot TWRP on your device. If you are using a lockscreen pin/pattern/password and do not get prompted to enter your passord, reboot to the bootloader and try again. Go to install and browse to the zip and install the zip.

Which to me means to use the TWRP's install button.

But in this thread, and as you state, they say flash it. How?

---------- Post added at 09:24 PM ---------- Previous post was at 08:41 PM ----------

I haven't decided on a ROM yet, but don't see that a reason not to replace my recovery?
[Google Pixel 3 XL Guides, News, & Discussion] jcmm11:
Flash and install zip from TWRP are one and the same (although flash can also mean via fastboot). Flash is basically a generic term meaning install a flashable zip file in some manner.

As far as installing recovery 2 things:

1) topjohnwu (Magisk developer) recommends against it on a/b devices. There's no longer a separate recovery partition, recovery is stored in the boot image's ram disk. Which is just one more thing that can mess up a boot image.

2) if you really want to install it try installing it directly to a stock image, before applying either a custom kernel or Magisk. Also be aware that you will lose TWRP with every monthly OTA. Personally I just boot TWRP via the bootloader if I need it, which isn't very often - especially now that Franco Kernel Manager can flash pretty much any zip.
[Google Pixel 3 XL Guides, News, & Discussion] Darkwing_Duck:
That answers my " but don't see that a reason not to replace my recovery?", thank you.

Guess the old Nexus days are just that. :)
[Google Pixel 3 XL Guides, News, & Discussion] jcmm11:
If you want some more information about a/b phones (they are a somewhat different beast compared to what you're used to) you can start here https://xdaforums.com/oneplus-6/how-to/guide-noobs-guide-to-b-partitions-op6-t3816123
[Google Pixel 3 XL Guides, News, & Discussion] Gordietm:
For some reason I cannot file transfer anymore yo my PC. It doesn't recognize my phone. I tried to flash the complete system image and the PC is stalled waiting for phone.
[Google Pixel 3 XL Guides, News, & Discussion] Badger50:
What common fixes have you tried to resolve it?
[Google Pixel 3 XL Guides, News, & Discussion] Gordietm:
Checking that file transfer was selected, USB debugging. Tried reflashing the rolom on both slots. Redownloaded USB drivers on PC.
[Google Pixel 3 XL Guides, News, & Discussion] Badger50:
Different cables? What's a rolom? :confused:
[Google Pixel 3 XL Guides, News, & Discussion] Gordietm:
Sorry, the rom. I also tried different cables, still no luck.
[Google Pixel 3 XL Guides, News, & Discussion] Badger50:
And no response from the pc as well while in fastboot mode?
[Google Pixel 3 XL Guides, News, & Discussion] Gordietm:
No, nothing. I tried to flash the January system image. When I hit flash-all, it says waiting for device.
[Google Pixel 3 XL Guides, News, & Discussion] jd1639:
Have you checked in device manager if the pixel is reconized? And if it is what driver does it show?
[Google Pixel 3 XL Guides, News, & Discussion] Gordietm:
The device manager doesn't recognize the phone at all.
[Google Pixel 3 XL Guides, News, & Discussion] jcmm11:
That sounds like either cable or driver issues (cables do go bad, even if they worked previously)
[Google Pixel 3 XL Guides, News, & Discussion] Gordietm:
I got it working, simple as restarting my pc. Thanks for the help.
[Google Pixel 3 XL Guides, News, & Discussion] pr0adam:
If I am on a custom ROM and have TWRP installed, can I go back to stock by downloading the factory image .zip file and flash it as if I were flashing a custom ROM?

Wiping cache/data/system then flashing the zip in TWRP?

Similarly if I want to update the stock ROM can I do it as if I were updating a custom ROM or do I have to edit the .bat file and flash it through ADB?
[Google Pixel 3 XL Guides, News, & Discussion] jd1639:
No, the factory image will not flash in twrp. Extract the zip and run the flash-all batch file while booted into the bootloader. Edit the flash all to remove the -w if you don't want your device wiped. You'll have to reinstall twrp and root if you want those.
[Google Pixel 3 XL Guides, News, & Discussion] pr0adam:
Thanks for the quick response. Guess ill be doing that monthly since I want to use the squeeze feature on this phone.
[Google Pixel 3 XL Guides, News, & Discussion] State.of.mind:
Just in case anyone is curious the unofficial Xposed works great.
[Google Pixel 3 XL Guides, News, & Discussion] Homeboy76:
Link(s)?
[Google Pixel 3 XL Guides, News, & Discussion] ashayden:
I am unlocked.

On January factory image (full wipe).

booted into TWRP via fastboot

flashed twrp.zip

reboot recovery

flashed latest elemental kernel

reboot

flashed latest magisk

reboot

hangs of "G powered by android" with progress bar

auto reboots into TWRP

flash latest magisk uninstaller

reboot into stock rom no problems

any thoughts? Thanks.
[Google Pixel 3 XL Guides, News, & Discussion] Homeboy76:
- SDK Platform-tools r28.0.1

- twrp-3.2.3-3.img

- Just Do #7 to install kernel and root.

Note: If you are using EXKM to install ElementalX kernel. Do #7 to root then install the kernel you shouldn't lose root.
[Google Pixel 3 XL Guides, News, & Discussion] State.of.mind:
Xposed

https://www.xda-developers.com/xposed-framework-unofficial-port-android-pie/
[Google Pixel 3 XL Guides, News, & Discussion] ashayden:
I have twrp-3.2.3-3

Followed the steps in #7 (tried several times)

Still hanging on boot screen then looping back into recovery
[Google Pixel 3 XL Guides, News, & Discussion] Homeboy76:
¯\_(ツ)_/¯
[Google Pixel 3 XL Guides, News, & Discussion] jcmm11:
Try without flashing TWRP.

Flash stock boot.

Flash boot TWRP

Install custom kernel

Install Magisk

Reboot
[Google Pixel 3 XL Guides, News, & Discussion] ashayden:
Thanks for the suggestion. Unfortunately, I get the same result.
[Google Pixel 3 XL Guides, News, & Discussion] Badger50:
Sounds like your having the same problem that many of us did on the P2XL after the Pie update. There are several different sequences you could still try if you want to try.

Fastboot twrp.

Flash twrp.zip

Flash kernel

Boot up to OS

Flash magisk. If that doesn't boot...then do the same steps except, after you flash magisk, then flash the magisk uninstaller zip, then flash magisk again. If that doesn't boot, then...

Fastboot twrp

Flash kernel

Reboot to twrp

Flash magisk. If that doesn't boot, then do same steps except use the magisk uninstaller again, then flash magisk again.

Keep playing with the sequences until you get it my friend :good:
[Google Pixel 3 XL Guides, News, & Discussion] 808phoneaddict:
Apparently my fastboot permissions aren't there....

i can adb reboot bootloader - (goes to fastboot screen)

when on fastboot screen - I type in fastboot devices and I get a permissions denied response...

first time unlocking this bootloader (did this many times on other phones though)....help! lol
[Google Pixel 3 XL Guides, News, & Discussion] ashayden:
Thanks. I will keep at it. Strange that I did not have this problem until the Jan. update.
[Google Pixel 3 XL Guides, News, & Discussion] johnnywhojr:
"Lock Bootloader (Google Pixel 3 XL)

Note: 'B' must be completed before performing this step!

Boot fastboot mode

Open a Command Prompt and type this at the Prompt:

Code:

fastboot flashing lock

You should see a request for confirmation on your phone, use the volume keys to scroll and the power key to select.

Allow the process to complete, then type this at the Command Prompt:

Code:

fastboot reboot

Enable Developer Options: Settings > System > Abo

t phone > Tap Build number 7 times.

Tap Back > Developer options and toggle OEM Unlock off."

Have tried this on my Pixel 3 XL and am being told in terminal that it has failed. have reset to factory image with flash-all.

Help please would be great. thank you!
[Google Pixel 3 XL Guides, News, & Discussion] ashayden:
SOLVED:

Downloaded latest factory update (Jan 5)

Manually flashed (no flash-all script seems to have done the trick)

Reboot system

fastboot twrp.img

Flash Magisk 18

Reboot system

Success

Think it's safe to flash a custom kernels and twrp.zip?
[Google Pixel 3 XL Guides, News, & Discussion] jcmm11:
Depends on the custom kernel I think. Some preserve root, some don't. I'm using Kirisakura myself and am very happy with it. It does preserve root.

Personally I haven't flashed TWRP, I just boot to it when I need it (which isn't that often). I think that if you flash TWRP after Magisk you may lose root, but not sure about that. topjohnwu recommends not flashing TWRP.
[Google Pixel 3 XL Guides, News, & Discussion] 808phoneaddict:
ok so:

Ive flashed the stock img (wipe all), flashed the stock boot.img - and can get to boot again, the G comes up, but when android starts it force closes on the pixel setup....and doesn't open anything...

I dont know what to try...

---------- Post added at 04:15 PM ---------- Previous post was at 04:09 PM ----------

what items did you manually flash?
[Google Pixel 3 XL Guides, News, & Discussion] 808phoneaddict:
Ok I need serious help...sorry for the multiple posts...

Ive tried fastboot flashing the stock images but that doesn't get my phone working. I can get twrp running, but I also mistakenly wiped my data (zip, installer, image files) while on TWRP...

I'm trying to figure out how to just get my phone running again....and could use the help...
[Google Pixel 3 XL Guides, News, & Discussion] ashayden:
I will defer to the expertise of the devs and not flash TWRP. I have always had great battery and performance with Kirisakura, Elemental, and Franco, which, to my knowledge, all preserve root at this point. Thanks for the advice. Gonna flash Kirisakura.

---------- Post added at 04:26 AM ---------- Previous post was at 04:21 AM ----------

If you can boot to the bootloader, flash the latest factory image (don't alter the flash-all since you have already wiped your data).

If this doesn't work... make sure that you have the latest platform tools, try a different cable, try rebooting your computer, try a different computer, try flashing each .img individually:

fastboot flash bootloader bootloader-crosshatch-b1c1-0.1-5034669.img

fastboot reboot-bootloader

fastboot flash radio radio-crosshatch-g845-00023-180917-b-5014671.img

fastboot reboot-bootloader

fastboot update image-crosshatch-pq1a.190105.004.zip

(if you are on a mac, add "./" before fastboot)
[Google Pixel 3 XL Guides, News, & Discussion] 808phoneaddict:
issues...this is what I'm getting when flashing back stock image
[Google Pixel 3 XL Guides, News, & Discussion] ashayden:
I downloaded the factory image and moved the contents into my platform-tools folder

adb reboot bootloader

fastboot flash bootloader bootloader-crosshatch-b1c1-0.1-5034669.img

fastboot reboot-bootloader

fastboot flash radio radio-crosshatch-g845-00023-180917-b-5014671.img

fastboot reboot-bootloader

fastboot update image-crosshatch-pq1a.190105.004.zip

(if you are on a mac, add "./" before fastboot and adb)
[Google Pixel 3 XL Guides, News, & Discussion] 808phoneaddict:
Still haven't gotten it yet! Thanks for the info tho...

still can't boot. Everytime i try to flash (using the .bat file, or manually) it isn't able to flash the system for some reason
[Google Pixel 3 XL Guides, News, & Discussion] 808phoneaddict:
interestingly, I installed a AOSP rom and it got installed and runs! but when I flash the stock images it doesn't restore stock, i rebooted after flashing stock (flash-all) and it was still AOSP...?
[Google Pixel 3 XL Guides, News, & Discussion] jcmm11:
If Franco was making a Pixel 3 kernel I'd probably be running that - I've run his kernels for a long time. But I'm more than happy with Kirisakura. Elemental would be my next choice.
[Google Pixel 3 XL Guides, News, & Discussion] 808phoneaddict:
Just an FYI for others out there

I got it after doing two changes, although I'm not sure which made the difference.

1-changed to a USB a to c cord

2-moved all the files I needed to flash to my phone to the actual folder that had fastboot in it...worked!

Thanks for the help!
[Google Pixel 3 XL Guides, News, & Discussion] jd1639:
It's most likely the USB cable. It's been an issue for many people. And C to C just doesn't seem to work properly.
[Google Pixel 3 XL Guides, News, & Discussion] lingarajug:
stuck on google logo with grey updating bar below

i was able to BL unlock and set up device agaion, adb on, booted to temporary twrp, flashed twrp.zip, rebooted to recovery, flashed magisk and on reboot the device boots back to twrp and not the system and it said slot b was active and i changed to slot a and remoot to system again rebooted to twrp and now the phone stuck at google logo, what should i do?
[Google Pixel 3 XL Guides, News, & Discussion] 808phoneaddict:
Read my posts right above yours, I had similar results
[Google Pixel 3 XL Guides, News, & Discussion] 808phoneaddict:
so i finally got my phone working well, running stock rooted.

I see there's a feb security update as well as an update for magisk. to successfully update - would this work?

- reboot to bootloader

- fastboot boot twrp

- twrp flash unintstaller for magisk

- reboot to bootloader

- fastboot flash all (after removing -w)

- fastboot boot twrp

- fastboot flash magisk 18.1

?
[Google Pixel 3 XL Guides, News, & Discussion] Homeboy76:
Do #4, then #8 to reroot.
[Google Pixel 3 XL Guides, News, & Discussion] swxtr:
After rooted, How to install the new scurity update?
[Google Pixel 3 XL Guides, News, & Discussion] jd1639:
Why root if you don't know how to update the device? Your just asking for trouble. Just remove the -w in the flash all batch file. Run it and reroot.
[Google Pixel 3 XL Guides, News, & Discussion] mbonus:
[MENTION=4810220]Homeboy76[/MENTION] - excellent guide! Works perfectly using your steps with feb patch and Magisk 18.1. One step people probably forget is to flash the latest Magisk unistaller after rebooting into twrp when re-rooting after an update. I've done this every time and have not had an issue to date.