[Guide] Pixel XL Android 7(Nougat) Unlock/Install Stock Images + Kernels/Recovery +

lloydsw

Senior Member
Feb 19, 2012
159
18
38
Now I've gone and done it. Just flashing the radio didn't change anything so I flashed it all. Now I'm stuck only being able to boot into TWRP. Not sure what I did...I also tried the flashall bat file after editing out the -w to preserve data. Within TWRP, I've tried rebooting into system and bootloader, but always end up back in TWRP. Any ideas?
 

lloydsw

Senior Member
Feb 19, 2012
159
18
38
Got it fixed somehow by changing to slot b, flashing boot, rebooting, changing back to slot a. Still not sure why the zip in the archive wouldn't flash
 

lloydsw

Senior Member
Feb 19, 2012
159
18
38
For some reason I couldn't see it before. Is your adb/fastboot up to date
Funny that you asked, I was thinking about that this morning while mowing. I'm pretty sure they're from two years ago when I installed them to have my way with my Nexus. I'll wait until the next update for the phone before I try again with the (now) updated adb/fastboot. Thanks for the hint!
 

pcriz

Senior Member
Aug 23, 2008
5,038
2,936
253
Funny that you asked, I was thinking about that this morning while mowing. I'm pretty sure they're from two years ago when I installed them to have my way with my Nexus. I'll wait until the next update for the phone before I try again with the (now) updated adb/fastboot. Thanks for the hint!
Yeah older versions of adb/fastboot don't support the a/b setup of the pixel so when it gets a command like flash boot_a or something like that it doesn't recognize it and it fails. Google now offers adb/fastboot separate of the full sdk so it's a considerably smaller download.

https://www.xda-developers.com/google-releases-separate-adb-and-fastboot-binary-downloads/
 
  • Like
Reactions: lloydsw

lloydsw

Senior Member
Feb 19, 2012
159
18
38
Yeah older versions of adb/fastboot don't support the a/b setup of the pixel so when it gets a command like flash boot_a or something like that it doesn't recognize it and it fails. Google now offers adb/fastboot separate of the full sdk so it's a considerably smaller download.

https://www.xda-developers.com/google-releases-separate-adb-and-fastboot-binary-downloads/
Thanks! Tried it yesterday on my wife's phone & it worked perfectly!

However, she lost TWRP. Before I do something stupid like I did with mine & end up in a TWRP loop at boot, I've verified via SU app that root is gone, so should I just be able to just reflash TWRP & reinstall root within TWRP?
 

Homeboy76

Senior Member
Aug 24, 2012
2,365
1,114
188
Thanks! Tried it yesterday on my wife's phone & it worked perfectly!

However, she lost TWRP. Before I do something stupid like I did with mine & end up in a TWRP loop at boot, I've verified via SU app that root is gone, so should I just be able to just reflash TWRP & reinstall root within TWRP?
Fastboot Twrp.img, Flash TWRP.zip (RC1) and SuperSu [See #6]
 
Last edited:
  • Like
Reactions: lloydsw

DMK1111

Member
Jan 7, 2010
10
1
0
Austin, Texas
First of all thank you so much for putting together all this information!!! I have a Pixel XL that I bought directly from Google so it came with the bootloader unlocked. I have since rooted and installed TWRP and Had Flashfire installed so I could update without losing root. I had my backup in Flashfire. I am stuck in a bootloop!!!! I have been reading through the threads trying to figure out how to get it out of this loop. In ADB when I type in adb devices it is not recognized!! However I can adb fastboot boot twrp.img and get to TWRP. From there I mount/ OTG/ insert my usb that has my twrp-pixel-installer-marlin-3.1.0-0RC2.zip and my SR1-SuperSU-v2.82-SR1-20170608224931.zip files. I flash the marlin zip file and try to reboot into recovery and it just goes back to the loop??? Someone Please Help!!! I have been hesitant to post because I know how irritated people get when users don't read... I have been reading but know just enough to be dangerous. Obviously!!!! Any help will be appreciated. Thanks DKERR1111
 

pcriz

Senior Member
Aug 23, 2008
5,038
2,936
253
First of all thank you so much for putting together all this information!!! I have a Pixel XL that I bought directly from Google so it came with the bootloader unlocked. I have since rooted and installed TWRP and Had Flashfire installed so I could update without losing root. I had my backup in Flashfire. I am stuck in a bootloop!!!! I have been reading through the threads trying to figure out how to get it out of this loop. In ADB when I type in adb devices it is not recognized!! However I can adb fastboot boot twrp.img and get to TWRP. From there I mount/ OTG/ insert my usb that has my twrp-pixel-installer-marlin-3.1.0-0RC2.zip and my SR1-SuperSU-v2.82-SR1-20170608224931.zip files. I flash the marlin zip file and try to reboot into recovery and it just goes back to the loop??? Someone Please Help!!! I have been hesitant to post because I know how irritated people get when users don't read... I have been reading but know just enough to be dangerous. Obviously!!!! Any help will be appreciated. Thanks DKERR1111
What is the marlin zip?

Also you can fastboot because you can get to the bootloader. Fastboot works in the boot loader and adb works in the booted os and recovery
 
  • Like
Reactions: DMK1111

Master Cylinder

Senior Member
Oct 31, 2013
1,253
531
143
Albuquerque
Is there any compelling reason to stick with this phone?

Is there any compelling reason to stick with this phone? It's a Pixel 5" with 128GB. I'm not one to be following the manufacturers into every new gimmick or have to have the coolest thing anymore, so I'll have to live with it a couple of years at least.

Just jumped on Pixel because of fi (15 years of Verizon was an education, and I've vowed to never let them have another penny of mine if possible. I realize these alt-carriers are just jumping on the backs of the majors, but oh well ...) and I wanted to have an unlocked bootloader.

So coming from my S3 that I screwed around with one too many times (with no case and only a ZAGG screen protector, 1000+ drops was not the problem) that was hacked 4 years ago, I'm having to learn some new concepts. I'd heard of "fastboot" here and there but am learning on this thread as I go.

I still have a week to send it back if I want - can't say I'm crazy about the phone physically. As a dilettante artist and sculpture, it was when I put the S3 in my hands that I knew it was the one back then. There's nothing physical about this phone to recommend it - anonymous as can be, and all of the cool colors disappeared long ago. Now you can only get black or white with some silver on it. Can't change the batt out or put the mem card in your computer. The screen scratched within 2 days, though there could be no reason for this to happen except maybe a plastic button on my back pocket of one of my pants.(Maybe it came that way?) Have hardly even used it yet!

Thanks to one and all for being in the xda community! Invaluable. :highfive:
 
Last edited:

GroovinChip

Senior Member
Aug 7, 2016
370
177
0
Is there any compelling reason to stick with this phone? It's a Pixel 5" with 128GB. I'm not one to be following the manufacturers into every new gimmick or have to have the coolest thing anymore, so I'll have to live with it a couple of years at least.

Just jumped on Pixel because of fi (15 years of Verizon was an education, and I've vowed to never let them have another penny of mine if possible. I realize these alt-carriers are just jumping on the backs of the majors, but oh well ...) and I wanted to have an unlocked bootloader.

So coming from my S3 that I screwed around with one too many times (with no case and only a ZAGG screen protector, 1000+ drops was not the problem) that was hacked 4 years ago, I'm having to learn some new concepts. I'd heard of "fastboot" here and there but am learning on this thread as I go.

I still have a week to send it back if I want - can't say I'm crazy about the phone physically. As a dilettante artist and sculpture, it was when I put the S3 in my hands that I knew it was the one back then. There's nothing physical about this phone to recommend it - anonymous as can be, and all of the cool colors disappeared long ago. Now you can only get black or white with some silver on it. Can't change the batt out or put the mem card in your computer. The screen scratched within 2 days, though there could be no reason for this to happen except maybe a plastic button on my back pocket of one of my pants.(Maybe it came that way?) Have hardly even used it yet!

Thanks to one and all for being in the xda community! Invaluable. :highfive:
My view of the Pixel is that this is a phone that will last me a good 4-6 years. It'll get OS updates through Android Phone, and the developer community will continue to support it for years, as with many other devices. I'd say keep it.

As far as looks, all my phones go in cases immediately. As much as I'd love to admire the beauty of a smartphone, I'd rather it last me and let me get my money's worth.

128 GB of storage should be fine, I can't imagine needing more.

Through reading posts here on XDA you'll learn all the terms and processes for unlocking your bootloader, rooting, flashing custom ROMs, etc etc.

I'd say keep the phone.

Sent from my Google Pixel XL using XDA Labs
 
  • Like
Reactions: dcillusions77

vlucchetti

Senior Member
Dec 3, 2009
655
121
63
Latrobe, PA
I'm getting this phone as a warranty replacement for my Nexus 6P which is suffering from serious battery drain after almost two years. Bought from Google with the device protection program, best $99 I ever spent.

If the 6P would have survived, I'd be keeping it until the Pixel 3 XL comes out, but this will be a very serviceable replacement, and if I get as many years out of it as the 6P, I'll be happy.

Like was posted above, goes in a case, get's tempered glass, and Pure Nexus will be installed and life will go on as before....