Tips and Tricks [Google Pixel] (sailfish)

[sd_shadow]

New device new rules/tricks

The main purpose for this thread is to post info that doesn't real justify it's own thread.
Most of what is posted is what interests me, usually in no particular order.
If you think something is missing, please share (include links or as much info you can)

General Info

• Index

Have a question? Please consider asking in the

• Help Thread

• How to Check if you have a Verizon or Google Model from CID info
• Custom Recovery info
• FAQs
• USB Drivers
• Using ADB and Fastboot commands
• Unlocking the Bootloader
• Rooting
• WiFi Tether
• Installing new security update with fastboot.exe for a bootloader-unlocked Pixel
• [GUIDE] Restore to stock after soft BRICKED Written for XL version, but a good reference
• Set/Change Active System Partition with Fastboot Command in Bootloader Mode
• [Re]Activate Google Voice on Pixel
• 46 Google Pixel XL & Google Pixel Tips and Tricks (www.droidviews.com)
• https://www.androidpit.com/google-pixel-tips-and-tricks

 

[sd_shadow]

USB Drivers for using ADB/Fastboot commands

• If using Mac or Linux drivers should not be an issue.
• If using Windows 10 correct drivers should already be installed but you likely will need to select them in Device manager
  
  
• If drivers are correct the Pixel should be listed in Device Manager as
• Android Phone
  • adb composite interface
  
  
• An easy way to install correct drivers on a Windows PC is using
  • [TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3 by Snoop05
  
  
• Official Google Drivers

 

[sd_shadow]

Unlocking the Bootloader - 06 Nov 2016

• If it's a pure Google device just run
  

  fastboot oem unlock

• If you bought the Pixel from Verizon, Best Buy.... dePixel8 method will be required to unlock the bootloader
  
  Note: Verizon, Build Version NDE63X, Nov 2016 can be unlocked,Builds after that cannot.
  
  • Using dePixel8
    • Be sure Drivers are correct
    • Change screen timeout to 30 mins in settings/display options
    • Enable Developer Options
      • In Settings/About Phone >Tap build version until it says "you are developer"
      • go back to main Settings screen
      • Open Developer Options
      • Enable ADB Debugging (in Developer Options)
      • Be sure ADB and Fastboot commands are working
      • Download dePixel8
        Run in Command prompt
        

        adb push dePixel8 /data/local/tmp

        adb shell chmod 755 /data/local/tmp/dePixel8

        then
        

        adb shell /data/local/tmp/dePixel8

        when you see
        

        [+] getting there, about 20 more seconds please

        open the Chrome app on the phone
        then you should see
        

        [+] done
        [+] rebooting your device to bootloader mode
        [+] run "fastboot oem unlock" to unlock your bootloader
        [+] P.S. Pixel is made by HTC, and dePixel8 was made by beaups
        [+] cheers jcase - copyright Streamlined Mobile Solutions, LLC

• Discussion Thread: BL unlock for Verizon Pixel just released by murryrulz

• Do not relock the bootloader
  • [PSA] Read before relocking your bootloader by jcase
    

 

[sd_shadow]

Rooting
Requires Unlocked Bootloader
[ROOT] SuperSU by Chainfire

 

[sd_shadow]

Hotspot/WiFi Tether
Hotspot should work out of the box for most data plans except Unlimited Data plans

Verizon Unlimited Data Plans

• Rooted method
  • Make sure your bootloader is unlocked and you are rooted.
  • Instal a Root File Manager (Root Browser / ES File Explorer)
  • enable root access in File Manager (it's off by default in some)
  • browse to /System > Long press build.prop > Open in Text Editor
  • Scroll all the way to the bottom. Type in "
    

    net.tethering.noprovisioning=true

  • .. Then save and exit. Reboot the phone and you're good to go.
  • Discussion Thread: Pixel Hotspot by polo2883
  
  
  
  [Mod][Systemless Root][Pixel/Pixel XL] TetherMod - Bypass provisioning checks. by Fenny
  http://forum.xda-developers.com/pixel-xl/themes/mod-tethermod-systemless-install-guide-t3501448
  
  
  
• Non Root method
  • Verizon native tether subscription bypass A Pixel XL thread

Sprint WiFi Tethering Thread

• [ROOT/Guide] Native Hotspot Working by stuntnmore A Pixel XL thread
  

 

[sd_shadow]

Setting up and Using ADB/Fastboot (Android Debugging Bridge)

For Mac or Linux: see Can ADB/Fastboot be used on Linux and Mac?


Setting up ADB/Fastboot (Windows)

• [Index] Setting up and Using ADB/Fastboot

Using ADB/Fastboot

• adb commands are used in normal boot/OS or in Recovery
• fastboot commands are used in fastboot/bootloader mode

Set/Change Active System Partition with Fastboot Command in Bootloader Mode

Fastboot set_active _a

Fastboot set_active _b

 

[sd_shadow]

Installing new security update with fastboot for a bootloader-unlocked Pixel.
Note: This is a work in progress, but it should be correct.
Even if it works for the Nov update, it may need to be written for future updates

Problem:
If you have modified the stock firmware (hosts file, root, kernel, etc.), the OTA update likely will fail

Solution:
This does not factory reset, user apps and data are not removed.
This will remove your custom kernel/root/hosts/recovery...

Install Verify Drivers

• see post #2

Setup ADB.exe see

• [Index] Setting up and Using ADB/Fastboot
• [INFO] How I restored to stock after soft bricking, then flashed new kernel & rooted by CZ Eddie

Download the system image for Sailfish (Pixel) from google
For November update, there are 3 versions:
NDE63U Europe
NDE63V US, except Verizon
NDE63X Verizon

Unzip the file
Unzip xxxxxxnde63v.zip from inside the new directory/folder
Copy files to same folder as adb.exe files (unnecessary if adb is setup as global)

Open open Command Prompt (with same directory path as firmware files)

Reboot into bootloader

adb reboot bootloader

or
Power off, Hold volume down button, power on

check your boot slot (_a or _b) and following line may need to be adjusted?

system_b system_other.img

Execute fastboot commands

fastboot flash bootloader bootloader-sailfish-*.img
fastboot reboot-bootloader
fastboot flash radio radio-sailfish-*.img
fastboot reboot-bootloader
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system system.img
fastboot flash system_b system_other.img
fastboot flash vendor vendor.img
fastboot flash modem modem.img
fastboot reboot

Custom Kernel, Root, and other mods will need to be reflashed


Credit
[GUIDE] Update with fastboot by @firewave

 

[sd_shadow]

Custom Recovery

Twrp links

• TWRP RC1 for Pixel Devices
• https://plus.google.com/+DeesTroy

 

[GeekMcLeod]

Thanks a lot for this thread. Very helpful for updating my pixel. Have linked it a few times to help out. This thread should be stickied.

 

[sd_shadow]

Thanks a lot for this thread. Very helpful for updating my pixel. Have linked it a few times to help out. This thread should be stickied.

Thanks, hope it helps.
It is linked in the index

 

[sturmeh]

check your boot slot (_a or _b) and following line may need to be adjusted?

system_b system_other.img

To be clear, you want the one used to match the one you're currently set to right? (My bootloader specifies boot slot a.)

 

[GeekMcLeod]

To be clear, you want the one used to match the one you're currently set to right? (My bootloader specifies boot slot a.)

I did it the other way. System other seemed like it shouldnt be your boot slot. I updated it already and it's working so I think I got it right.

 

[sd_shadow]

I did it the other way. System other seemed like it shouldnt be your boot slot. I updated it already and it's working so I think I got it right.

so boot slot was a in bootloader?
you use b command?
is it now b in bootloader?

Sent from my XT1254 using XDA Labs

 

[sd_shadow]

the Pixel has 2 system slots/partitions,
in theory you could have 2 different roms to choose from, that maybe an option in a future version of twrp


Sent from my XT1254 using XDA Labs

 

[GeekMcLeod]

so boot slot was a in bootloader?
you use b command?
is it now b in bootloader?

Sent from my XT1254 using XDA Labs

No, my bootloader still says my bootslot is a.

 

[sd_shadow]

No, my bootloader still says my bootslot is a.

thanks, sounds good

Sent from my XT1254 using XDA Labs

 

[sd_shadow]

new
[Mod][Systemless Root][Pixel/Pixel XL] TetherMod - Bypass provisioning checks. by Fenny
http://forum.xda-developers.com/pixel-xl/themes/mod-tethermod-systemless-install-guide-t3501448

Sent from my sailfish using XDA Labs

 

[Artnig]

I just tried reverting to stock and my phone is stuck in a bootloop and then eventually gets stuck on dead android with No command text. I followed all directions to the dot and I'm on boot slot b. Any ideas?

---------- Post added at 11:04 AM ---------- Previous post was at 10:43 AM ----------

Ok so I followed GeekMcLeod's advice about flashing system-other to the opposite partition. Since I was on boot_b I change the line in the OP to flash system_a and now my phone is booting. @sd_shadow I'm not sure if this is the case for everyone.

 

[k.s.deviate]

Just a short story about my experience so far with the Pixel.

When i first got my device it wanted to update. I let it update (OTA) and rebooted. Once that was done, I unlocked the bootloader, booted TWRP flashed it, rebooted TWRP and then flashed root. All was awesome, I went to reboot and noticed that TWRP shows which boot slot you're in (I was in B). I rebooted anyway and everything works as expected.

I was curious, so I booted back into TWRP, went to reboot and changed the boot slot to A, got an error but checked it again and it shows I was in fact in boot slot A. So i rebooted... it booted into non rooted, pre update android... so it looks to me that this seamless update system applies the update the opposite partition that your in. So if you're in A and take an OTA it applies it to B and then reboots into B (updated) and the opposite will happen if you take the OTA while in B. All apps and data you've collected is shared with either system partition.

So, in theory we could take the OTA as long as we flash the recovery and (possibly) boot images before downloading and applying it. We would only have to flash TWRP and root again.

And I agree, it looks like we should be able to dual boot two different ROMS, maybe even kernels without too much messing around.

I'm sure this is not new news but I just wanted to share and maybe someone will correct me or learn from it.

 

[sd_shadow]

thanks for the replies, good stuff

Sent from my sailfish using XDA Labs