yashsingh1/xdaforums huggingface dataset:
[Google Pixel XL Guides, News, & Discussion] kinfolk248:
[MENTION=4810220]Homeboy76[/MENTION]
[MENTION=4609886]sliding_billy[/MENTION]
[MENTION=4881692]post-mortem[/MENTION]

Do you guys like rotel? I ask because I am about to make a big a$$ pot and you are MORE than welcome to come grab some and a cold one!!!!!!! I'm on 9.0 and rooted, unlocked BL, with Magisk!

I will say that for some reason the rename to 'twrp.img' didn't work for me, I had to leave it it's original name but whatever it worked in the end.

Now my next task is to get all my fav root apps going and replace some of these boring regular ones with some modded apks. Oh and get rid of this bang borked up status bar expansion dot after so many notifications come in you get a dot, just flood my status bar lol but hopefully there's a mod for that cuz i have ROOT now babyyyyyyy!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! :silly::victory::highfive::highfive::highfive:
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
Yes! :):eek::)
[Google Pixel XL Guides, News, & Discussion] sliding_billy:
Congratulations! Sounds like your rename ended up turning it into twrp.img.img. Gotta love how Windows still uses file extensions but in a very different way than in the old days. Easier to just leave the file name intact no matter how obnoxiously long and F2 CTRL+C it then paste the name into the command line with the .img added to the pasted name.
[Google Pixel XL Guides, News, & Discussion] kinfolk248:
youtube

adaway

titanium backup

kernel......coming VERY soon

dual speaker mod

all here i come lol
[Google Pixel XL Guides, News, & Discussion] alecthenice:
I think we have to re install the --user 0 com.android.phone after fastboot is toggled but when I try to do this it says javalang.illegalargumentexception error: cannot open file 0 com.android.phone
[Google Pixel XL Guides, News, & Discussion] leondestiny:
sorry but what does that post you quoted mean for us verizon (unrooted stock peasants) !??
[Google Pixel XL Guides, News, & Discussion] post-mortem:
Glad you finally got it!

Install YouTube Vanced (black, if you prefer) through Magisk Manager. Definitely look for the Tulsadiver mod for your phone; it'll let you put the clock back on the right, and make other, similar changes. I'd post links, but I'm on mobile right now, and it's a pain in the butt to look for all the right threads and make links.

:highfive:

Never heard of rotel, LOL.
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
Nothing, unless you decide to unlock your Pixel/Pixel XL bootloader and root. If you do decide to unlock your Pixel/Pixel XL bootloader and root. Take a look at my post, sixth one down, on page 47.
[Google Pixel XL Guides, News, & Discussion] leondestiny:
you mean this post right ?

will this guide work for the pixel 2 xl .. ?
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
Yes .

No, but here are links to the Pixel 2 and Pixel 2 XL forums (Intro c.).
[Google Pixel XL Guides, News, & Discussion] leondestiny:
where ?

is it unlockable yet or no ? :confused:
[Google Pixel XL Guides, News, & Discussion] nolanjb:
No it only works on Pixel 1 / Pixel XL 1
[Google Pixel XL Guides, News, & Discussion] kinfolk248:
Tulsadiver aye? Hmmm let me see, tulsadiver or a custom rom...decisions decisions lol

Never heard of rotel, ro-tel...? u are not living your best life smh lol
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
The Pixel 2/Pixel 2 XL forum because you have a Pixel 2 phone.

No, at least not with the instructions in this thread.
[Google Pixel XL Guides, News, & Discussion] mrkhigh:
1)P2/p2xl not rootable or unlockable yet.

2)You've been living life wrong if you havent had melted cheese and Rotel with corn chips.
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
I may have tasted it but didn't know it was 'Rotel'.

Please tell me what Rotel is?
[Google Pixel XL Guides, News, & Discussion] kinfolk248:
Rotel = nacho x 10^9
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
So, you add a can of RO*TEL (Hot) to some melted cheese, Nachos or Corn Chips and some other spices and wash it down with a cold one? :)
[Google Pixel XL Guides, News, & Discussion] kinfolk248:
:highfive::highfive::highfive::highfive::highfive::highfive::highfive::highfive:
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
Sounds (Reads) Delicious!
[Google Pixel XL Guides, News, & Discussion] kinfolk248:
Well I can say that I am down by 1 hr of battery after moving to android 9. Might be going to a custom rom after all. Any suggestions?

Oh and phone gets warm now for whatever reason

ps...me likes all the bells and whistles and customization...
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
You can take a look at #11 in my guide, it has links to Custom ROMs for Android 9 (Pie). Read their features list and choose one.

Been using it a lot since installing Pie? Let it rest awhile :).

Keep your Pixel/Pixel XL from feeling to warm or hot
[Google Pixel XL Guides, News, & Discussion] iamnotexisting:
Works wonderfully, I'm surprised!
[Google Pixel XL Guides, News, & Discussion] Neo:
I got 5 1/2 hour SOT and 2 days 14 hours worth of battery life, on the stock rom (rooted). So, it's not the ROM causing the problem. It's all in how you use it ;)
[Google Pixel XL Guides, News, & Discussion] kinfolk248:
text and spotify... :confused:
[Google Pixel XL Guides, News, & Discussion] kingbri:
There's a bug in the os that ramps up the CPU clock at boot, I would suggest a custom kernel. Check your apps there may be battery drain from them
[Google Pixel XL Guides, News, & Discussion] kinfolk248:
i turned off 3 apps, cant recall which three which the system showed as high usage. Also, I moved to a custom rom and battery is back to normal, i guess...
[Google Pixel XL Guides, News, & Discussion] kingbri:
Even with the AI improvements, I still think that the system is broken when seeing battery draining apps. Use battery historian to check. Greenify helps a lot as well when rooted
[Google Pixel XL Guides, News, & Discussion] kinfolk248:
Thanks. I am on track for 4 hrs sot as of now, which is better than 9 stock but still one hour short of the 5 hour sot I could get with oreo. But I will try greenify tho. isnt it a app to put your apps into doze super fast?

gotta go read a greenify tutorial lol
[Google Pixel XL Guides, News, & Discussion] PrettyPistol555:
Well, my Verizon Pixel XL just Kicked the Bucket, and it looks like VZW will be shipping me out a new one, so I'm SUPER stoked that it *appears* there shouldn't be any problem (assuming I follow the instructions) Unlocking the new phone's Bootloader so I can use it like the last one.

Can anybody confirm that the replacements for Pixel XL warranty claims are BL Unlock-able via these wonderful instructions?

Thanks!
[Google Pixel XL Guides, News, & Discussion] Silent25r:
I could some help. I guess I'm not understanding how to use adb. Here is the step I'm stuck on: Open CMD in adb directory and type

Code:

adb shell pm uninstall --user 0 com.android.phone

So I go into my adb folder. For me, that's C:Users\'Username'\adb.

Once there I hold shift and right click to open the cmd and type in the code you have here. It isn't working for me and I'm sure I'm doing something wrong.
[Google Pixel XL Guides, News, & Discussion] post-mortem:
If you phone is connected to your computer, and you have the correct drivers installed, your computer should be able to communicate with the phone. From a command prompt (cmd), if you type adb devices, it should show the serial # of your phone, indicating that your computer sees the phone. If not, then something's wrong.

Try that, and let us know what happens.
[Google Pixel XL Guides, News, & Discussion] Silent25r:
It shows the SN for my device. Once it said success but my boot loader did not unlock. This is a refurbished Verizon pixel that I just got from google.

I'm getting Failure [not installed for 0]

I've tried to hard resetting it again. Ran the code and it said success. Rebooted and connected to wifi to open a website. Boot loader unlock is still grayed out. Tried to code again and I'm back to the Failure not installed for 0.

I also tried disabling phone and messaging services.
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
Do you have the latest SDK Platform Tools r28.0.1

for Windows/Linux?
[Google Pixel XL Guides, News, & Discussion] post-mortem:
So the bootloader is still locked? Have you tried following Google's instructions?
[Google Pixel XL Guides, News, & Discussion] Silent25r:
I did not have the latest SDK Platform but I do now. Still isn't solving my problem. I resetted the device and tried again after updating the SDK. Unfortunately that didn't work.

I've tried. Says oem unlock is not allowed. Also tried the one for older devices.

Does this message mean anything? Here is what I'm saying instead of the unlock option:

Wait for debugger

Debugged application waits for debugger to attach before executing.

I've tried more than one cable to see if maybe that was the issue. Now I'm trying to update to the latest version. Currently on 9.0. It's taking a long time to install the next update over wifi that was getting over 300 Mbps on my phone. Once it's done updating I'll format the device and try again. Then I'll try another cable. After that, I'm out of ideas. I've yet to put my sim card in it. Could that be part of my issue?

I'm done for the night. This phone might be DOA. Tried putting the sim in to make a call with it and it can't find it. The sim that still works in another phone. Going to take it to Verizon tomorrow and let them try a different sim. Then it's off to google for another refurbish adventure. Going to vacation in a week and I really need my phone working. Locked boot loader or not.
[Google Pixel XL Guides, News, & Discussion] Silent25r:
Sorry for the double post. A reset allowed me to use my sim card again. Took the sim card back out to try the unlock again and it isn't working for me. Am I the only one not able to get this working?

When I first run the code it says success but that's it. I can't toggle the unlock. Right now, it still says contact carrier. I can run adb reboot and I get my model number. So it isn't the cables, right?

Under the grayed out unlock I get the message to connect to the internet or contact your carrier. I'm connected to the internet. Opened a few web pages. Turned off screen time out.

I'm at step 9 in the pictures uploaded. Really I am hoping that I just missed something simple.
[Google Pixel XL Guides, News, & Discussion] post-mortem:
When I did it on my Pixel, I opened a page to Google and let it sit for a coue minutes. I kept waiting for the grayed-out option to become toggleable, but it wouldn't. When I exited the menu and reentered it, I was then able to toggle the setting. The rest was easy.

I think I read someone saying that they had to connect over mobile data to get it to work. If that messes something up, you can always start over... again.
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
[MENTION=2171394]Silent25r[/MENTION]

Is 'Developer Options > Wait for Debugging App on?
[Google Pixel XL Guides, News, & Discussion] Silent25r:
I tried that. Waited, left, came back, rebooted. I tried every hint I could find here. My guess is we don't know what we are doing to get this to work because the steps aren't repeatable. Some people have to wait. Some need to reboot twice. Something is causing it to trigger.

I can't put my sim card in later. The phone will not see it. I don't know why. Each time I've had to reset it after adding the sim. Nothing else would work. So I can't try the mobile data trick on step 8.

What is this wait for debugging app? Both screen unlocked and waiting for debugger are grayed out.

I'll revisit this later in the week. I'm still hoping someone will come up with something I haven't tried. Still happy Google replaced my way out of warranty pixel for free. Not many companies would do that.
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
Sorry, it was 'Wait for debugger'.:(
[Google Pixel XL Guides, News, & Discussion] nolanjb:
I don't know if this will help but this is how I get it to work on my Pixel 2 (up to the point of going into bootloader and actually unlocking, of course)

After doing

adb shell pm uninstall --user 0 com.android.phone

I waited about 30 seconds and rebooted.

Then I connected to WiFi and ran

adb shell am start com.android.chrome

It just opens chrome. I then went to a couple of webpages and after about 30 seconds I went back to developer options and oem unlock was toggleable.

I'm able to reproduce it every time.
[Google Pixel XL Guides, News, & Discussion] PrettyPistol555:
Can this be performed on new devices shipping from VZW?

I'm receiving my Warranty replacement today, and hoping beyond hope that I can get BL unlocked, and Root like my last Pixel XL (May it Rest In Peace)...

If phone is NOT on Oreo, would I have to update first, or can I run on older version also?

Thanks.
[Google Pixel XL Guides, News, & Discussion] bruman2012:
Someone help, please? This is my main phone.

Google Pixel on 8.1.0.

Unlocked the bootloader easy.

Downloaded the following files to install TWRP from

https://dl.twrp.me/sailfish/

- twrp-3.1.1-1-fastboot-sailfish.img

- twrp-3.2.3-1-sailfish.img

- twrp-pixel-installer-sailfish-3.2.3-1.zip

So I booted into recovery mode, did the following commands in Admistrator Powershell

PS C:\AdbInstaller> fastboot boot twrp311.img

downloading 'boot.img'...

OKAY [ 0.621s]

booting...

OKAY [ 0.803s]

finished. total time: 1.428s

And my phone instantly shut down.

It's been off for like 30 minutes now, and no matter how long I press the power button, or if I try to reboot to recovery -- nothing. It won't turn on. Just a black screen. I know it has battery power so that's not the issue. I just flashed the fastboot and it shut down, won't turn back on.

My plan was to install the fastboot, then flash the twrp-pixel-installer-sailfish-3.2.3-1.zip, and then install Magisk to get root.

But now I'm clueless.. it won't turn on after the fastboot command.

Please help anyone! Hoping I didn't just create a brick.

---------- Post added at 06:24 PM ---------- Previous post was at 05:38 PM ----------

After holding Volume Down and Power for about 20 seconds I finally got to to turn on again. I have no recovery, but I was somehow able to boot into Safe Mode (keeping it this way till I know for sure what to do).

Can someone please clarify if I'm doing this in the right order? twrp-3.1.1-1-fastboot-sailfish.img already flashed.. then twrp-pixel-installer-sailfish-3.2.3-1.zip also in ADB shell mode? This will get me TWRP? Shpuld I do anything with twrp-3.2.3-1-sailfish.img?

Sorry If I'm being a bit paranoid now, for a minute there I thought I just killed my phone and it would never turn on again. So any input would be hugely appreciated :)
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
Take a look at this Guide: [Guide] Pixel XL Android 9.0.0 (Pie) Unlock/Lock Bootloader + Install Stock Images/Custom kernels/TWRP Recovery/Systemless ROOT + September 2018 Security Patch

Do #4 'keep data' then Do # 7 to Root.
[Google Pixel XL Guides, News, & Discussion] bruman2012:
That's for the XL though, Marlin, right? Correct me if I'm wrong (I'm new to Pixel's and their intricacies from sub-model to model), but based off prior rooting experience installing a rom or recovery for another device is an almost sure way to make a mess and break things?

Still, looks like some good info and might point me in the right direction.

I was there was a clear step-by-step for this! It's confusing with all the different versions and what not.

Just got home from work so I'll try to research some more.. will let know if I make progress... and any other input would be much appreciated!

---------- Post added at 10:44 PM ---------- Previous post was at 10:16 PM ----------

Okay well I researched some more and felt confident enough to connect my phone to my USB with debugging enabled and this is how the adb went down

PS C:\> cd pixel
PS C:\pixel> adb devices
List of devices attached
FA68R0313404 unauthorized

PS C:\pixel> adb reboot bootloader
PS C:\pixel> fastboot flash recovery twrp-3.2.3-1-sailfish.img
target reported max download size of 536870912 bytes
sending 'recovery' (30736 KB)...
OKAY [ 0.758s]
writing 'recovery'...
(bootloader) Flashing active slot "_a"
FAILED (remote: partition [recovery] doesn't exist)
finished. total time: 0.821s
PS C:\pixel> fastboot continue
resuming boot...
OKAY [ 0.036s]
finished. total time: 0.036s
PS C:\pixel> adb devices
List of devices attached
FA68R0313404 device

PS C:\pixel> adb reboot bootloader
PS C:\pixel> adb devices
List of devices attached

PS C:\pixel> adb devices
List of devices attached

PS C:\pixel>

Baffled again! This seems like a pertinent error..

(bootloader) Flashing active slot "_a"
FAILED (remote: partition [recovery] doesn't exist)

?

Also confusing when I did an

adb devices

the first time while in the bootloader it recognized it, but as

unknown

edit:: reread it, the error code is

unathorized

not

unknown

like I first said. Not sure what that means in adb terms :/

.. the secondtime I reset and went into the bootloader it didn't even detect that it was connected.

II read some into it and some suggested I update adb and fastboot and maybe it will work.. (although I am not sure I even have an outdated version at the moment).. I feel I'm close.... but so far

AND at least I'm out of safe mode and can go into the unlocked bootloader without issue... freaked me out when it died for almost an hour, but I apparently didn't brick the thing :)
[Google Pixel XL Guides, News, & Discussion] post-mortem:
Reinstall the factory image, with the modification to keep data. This will restore your partition structure, and give you back stock recovery. Then start over again with TWRP. Do not use old versions of TWRP.
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
Yes.

The guide will also work for Pixel (Sailfish) phones:

a. With an unlocked bootloader and OEM unlocking enabled

(Settings > System > Advanced > OEM unlocking).

b. Download the latest SDK Platform Tools r28.0.1 ( link is under 'Prerequisites c'.

c. Download Pixel (Sailfish) Factory Image for October 2018.

d. Go here and download:

1. twrp-3.2.3-1-sailfish.img

2. twrp-pixel-installer-3.2.3-1.zip

e. Extract SDK Platform Tools

f. open Command prompt to Platform Tools Folder.

g. adb devices if you get device number Do #4.

h. If you want root Do #7

NOTE: These are not steps #1-#13, The are individual sets of instruction .

---------- Post added at 12:34 AM ---------- Previous post was at 12:28 AM ----------

Man you're fast lol
[Google Pixel XL Guides, News, & Discussion] bruman2012:
You are both fast, I was expecting my phone to be a shell of itself (I backed up the data and did a factory reset before this whole thing) for maybe a couple of days before at least I could maybe figure it out. Thanks to people who know yeah hha. I'm going to try this now and get back.
[Google Pixel XL Guides, News, & Discussion] bruman2012:
Are we talking this one for the Factory Image

(d)

?

https://developers.google.com/android/images

Just want to make triple sure I'm not flashing something stupid :p

the rest of it looks pretty straightforward. adb twrp-3.2.3-1-sailfish.img and twrp-pixel-installer-3.2.3-1.zip and reference your previous link for #4 and #7.

Should be good (assuming no weird adb errors or anything -- previously I used AdbInstaller (some program someone on here created as an easy way to get adb installed), and I'm guessing my error previously was I tried to flash 'twrp-3.1.1-1-fastboot-sailfish.img' first? I only did so because it had fastboot in the image, so I thought that was what I should fastboot with first was my logic.. anyways, assuming that's the right factory image I'm gonna get this in gear thanks for the help!

---------- Post added at 01:47 AM ---------- Previous post was at 01:37 AM ----------

Nevermind I found it here apparently :).. I suppose I'll trust the community more than the manufacturer in this case

https://xdaforums.com/pixel/how-to/october-factory-ota-images-available-t3849254
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
Yes, scroll down to "sailfish" for Pixel

fastboot boot twrp-3.2.3-1-sailfish.img. Once twrp boots flash twrp-pixel-installer-3.2.3-1.zip
[Google Pixel XL Guides, News, & Discussion] bruman2012:
Yeah I tried to do that first but adb won't detect my device when it's in the bootloader or the (broken) recovery mode.

Downloading the factory image right now and am going to try to flash that in the same folder as flashboot and try to adb them again..
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
If, you download the Factory image Do #4 'keep data'.
[Google Pixel XL Guides, News, & Discussion] bruman2012:
Okay, you might have saved me there. Like I said I already factory reset before I even unlocked the bootloader, so I didn't think there was any reason to keep the non-existent data. Guess I will now.

---------- Post added at 03:00 AM ---------- Previous post was at 02:36 AM ----------

No luck.

Downloaded the latest factory images from the official site, but can't even get that far. My phone isn't being detected in either bootloader or recovery mode (dead android with 'No Command'). I've tried restarting both my computer and phone... getting in Powershell:

PS E:\Backup\PixelOctober2018\platform-tools> adb.exe devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *

PS E:\Backup\PixelOctober2018\platform-tools> adb.exe devices
List of devices attached

PS E:\Backup\PixelOctober2018\platform-tools>

Any idea what the issue could be? Should I maybe try it on a different computer? Is it something with my phone?
[Google Pixel XL Guides, News, & Discussion] post-mortem:
Try a different USB port. If you're using a USB 3.0 port, try a 2.0 port.

You're still able to charge it?

Edit: For clarification, are you able to boot into bootloader mode, or only in safe mode?
[Google Pixel XL Guides, News, & Discussion] jisoo:
When you are in bootloader mode, you need to use fastboot. ADB only works when the OS is running (either system or recovery OS).

I know the two commands are often mixed, but fastboot and ADB are totally different protocols and work in completely different situations.
[Google Pixel XL Guides, News, & Discussion] Homeboy76:
Power Off your phone, the press and hold the power and volume down buttons until you see "Start".

Do you see "device is unlocked"?

Press Power button

When device reboots, open settings > System > Advanced. Do you see Developer Options?

Somebody posted these, I don't know who maybe one of them will help with Pixel 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.
[Google Pixel XL Guides, News, & Discussion] bruman2012:
Thanks everyone, I'll try these all out in a few hours.
[Google Pixel XL Guides, News, & Discussion] Silent25r:
I am happy your not local. I would have given you the biggest hug ever! It worked! Apparently opening chrome myself was causing something to go wrong. I couldn't believe my eyes when I saw I could toggle it.