Can't Install app on Pixel using TWRP in fastboot - Google Pixel Questions & Answers

Can't Install app on Pixel using TWRP in fastboot - Google Pixel Questions & Answers

My phone is a Google Pixel (sailfish) and I am trying to flash the latest version of the Team Blackout zip for Google Voice. My goal is to install a dark themed google voice app in the easiest way possible without having to root and keeping stock recovery with over the air updates. The easiest method I came up with was to flash a Team Blackout Zip without installing but instead just booting into TWRP and flashing the zip file. I am open to other methods of getting a black google voice app on my phone. Thus far I have unlocked the bootloader and have tried the method listed below:
1- Download latest version of the Google Voice Team Blackout Zip on Computer
2- Go to Android Studio - scroll down to command line tools only and download windows sdk tools
3- Download latest TWRP.img file
4- Create new folder to put sdk tools in along with twrp.img along with zip file to flash from Team Blackout
5- Go to new created folder - hold down shift key and right click mouse button - select Open powershell window here - type adb devices - adb reboot bootloader - fastboot devices - fastboot boot twrp file(rename file to twrp.img then grab file and drag to powershell window - hit enter
6- Go to TWRP on phone - hit advanced button - hit adb sideload button - swipe bottom button
7- Go to powershell window and type adb sideload then drag and drop file.zip(change name of file) and hit enter
8- Then reboot phone
The whole process seems to work with no error messages in TWRP on my phone or in the powershell window/command prompt however I can't find the app on my phone. I have tried other Team Blackout zip files for other apps which also seem to get installed but after can't seem to find any of the apps. I am wondering if I am doing something wrong? Is the phone not allowing the apps to install because of the stock recovery, or am I somehow looking in the wrong place on my phone? I have tried looking in my file explorer app as well as apps in settings with no sign. I also don' t know if the apps have to be installed after being flashed?
Please let me know if you can figure out what I am doing wrong or if you can figure out a better method of getting a black themed google voice app on my phone without rooting and with keeping stock recovery along with future OTA updates?

Related

[TOOLKIT] SKIPSOFT ANDROID TOOLKIT - NEXUS 7 - Drivers, Root, Recovery + MORE

NEXUS 7 - SUPPORTS ALL AVAILABLE VERSIONS UP TO LATEST ANDROID BUILDS
SEE SUPPORT LIST FOR PUBLIC/PRO VERSIONS *HERE*
The Unified Android Toolkit brings together all the Nexus and Samsung Toolkits and supports many Nexus and Samsung devices. There is also an option at startup to run a Basic Android Toolkit which any Android device can use to install drivers, make app backups, install apk files, reboot the device into different modes and run a command prompt for manual input.
FUNCTIONS OF UNIFIED ANDROID TOOLKIT
* Install correct adb/fastboot drivers automatically on Windows xp/vista/7/8 32bit+64bit/Windows 10
* Backup/Restore a single package or all apps, user data and Internal Storage
* Backup your data from selectable folders [internal or external storage] to your PC for a Full Safe backup of data
* Unlock/Re-Lock your Bootloader [Nexus]
* Root Stock builds
* Various Root options using insecure boot image or custom recovery
* ALLINONE to Unlock, Root, Rename the Restore Files and install busybox [Nexus]
* ALLINONE to flash custom Recovery Root, Rename the Restore Files and install busybox [Samsung]
* [NEW] use SkipRoot boot image to Auto Root device, install Busybox Binaries and rename Recovery Restore files [selected devices]
* Install BusyBox on your device
* Perform a FULL NANDROID Backup of your system (Boot, Cache, Data, Recovery and System) via adb and save in Custom Recovery format on your PC which can be Restored via CWM Recovery [if insecure boot image available]
* Fix extSdCard write permissions from installed apps in Android 4.4+ [Samsung]
* Pull /data and /system folders, compress to a .tar file and save to your PC [if insecure boot image available]
* Dump selected Device Partitions, compress to a .zip file with md5 and save to your PC [if insecure boot image available]
* Extras, Tips and Tricks section
* Auto Update ToolKit to latest available version at startup (professional only feature)
* Program up to 10 Quickpick slots and run them very quickly (professional only feature)
* Mods section to automatically perform certain tasks on your device
* Download Google Stock Image directly to correct ToolKit folder for extracting and flashing [Nexus]
* Check md5 of stock image to make sure downloaded file isn’t corrupted before flashing [Nexus]
* Download Samsung Stock Firmware to PC for extracting and flashing via Odin [Samsung]
* Flash Custom Recovery or Google Stock Image to Device
* Flash any part of a stock Nexus image to device [boot, system, recovery] – Great for fixing broken parts of firmware
* Rename the Recovery Restore File present on some Stock Roms
* Boot into CWM Touch, TWRP, Philz Touch Recovery or Stock Recovery without Flashing it [Nexus]
* Flash Custom Recovery to Device
* Boot [Nexus] or Flash .img Files directly from your PC
* Install a single apk or multiple apk’s to your device
* Push Files from your PC to your device
* Pull Files from your device to your PC
* Disable forced encryption on Nexus6 and Nexus9 devices
* Install Root Checker app by Burrows Apps
* Install Backup/Restore app by MDroid Apps [calls log, sms, contacts]
* Install EFS/Partition Backup/Restore app by Wanam
* Dump selected LogCat buffers to your PC
* Dump BugReport to your PC
* Set Files Permissions on your device
* Open new Command Prompt for manual input
* Reboot device to Fastboot Mode or Android from fastboot mode [Nexus]
* Reboot device to Fastboot Mode [Nexus], Recovery, Android or Download Mode [Samsung] from adb mode
* Display Important Information about your device
--------------------------------------------------------------
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
--------------------------------------------------------------
SUPPORTED DEVICES AND LATEST SUPPORTED BUILDS *HERE*
DOWNLOAD THE SKIPSOFT UNIFIED ANDROID TOOLKIT *HERE* (FROM SKIPSOFT.NET)
NOTE: Key files are signed with a Digital Certificate from skipsoft.net but some ‘may’ get picked up as potentially harmful by Antivirus Programs and deleted. They are not harmful, this is a false positive given because of the compiler used. If this happens restore the file and exclude the folder from future scans to use it. This seems to happen mostly on AVG Free and Norton. If you are using the Auto Update feature on pro versions then you will need to disable the AV program or exclude the folder from scans before running the update again.
Credits: ChainsDD for Superuser, Chainfire for SuperSU and kernel patches, koush and the clockworkmod team for cwm and the universal driver pack, 1wayjonny for the adb/fastboot driver pack, Adam Lange for all his support and help with the insecure kernels, Viperboy for the Knox Disabler app, Stephen Erickson for the BusyBox installer app, BurrowsApps for the Root Checker app, NextApp for the SD Fix app, fOmey for TWRP for the Galaxy Gear.
--------------------------------------------------------------
WHAT IS THE DIFFERENCE BETWEEN PUBLIC (FREE) AND PROFESSIONAL (DONATE) VERSIONS?
THE PUBLIC VERSION OF THE TOOLKIT INCLUDES EVERYTHING YOU COULD NEED TO MANIPULATE AND ROOT YOUR DEVICE.
ACTIVATING THE PROFESSIONAL VERSION ADDS THE MOST USEFUL FUNCTION IN THE TOOLKIT, THE ABILITY TO CHECK FOR ‘AUTO UPDATES’ DIRECTLY VIA THE TOOLKIT AND HAVE THEM PUSHED TO YOUR PC RIGHT AWAY AS SOON AS THEY ARE UPLOADED WITHOUT NEEDING TO DOWNLOAD THE WHOLE TOOLKIT EVERY TIME. YOU WILL ALWAYS HAVE THE LATEST VERSION AS SOON AS IT IS MADE AVAILABLE. THIS MEANS SMALLER UPDATES CAN BE SENT OUT MORE FREQUENTLY, SUCH AS ADDING A SINGLE FUNCTION, FIXING A BUG OR ADDING COMPATIBILITY FOR A SINGLE CARRIER. THE SMALLER UPDATES WILL BE COMPILED AND RELEASED TO THE XDA COMMUNITY AS A FULL (PUBLIC) DOWNLOAD VERSION SO PROFESSIONAL VERSIONS ARE ALWAYS UPDATED SOONER.
THE PRO VERSION ALSO ADDS THE ABILITY TO CHECK FOR THE LATEST VERSION OF SUPERUSER AND RECOVERY FILES AND DOWNLOAD THEM DIRECTLY TO THE TOOLKIT.
THE ‘QUICK PICKS’ SECTION[/B] ALLOWS YOU TO PROGRAM UPTO 10 SLOTS WITH TASKS THAT YOU MAY PERFORM ON A REGULAR BASIS OR JUST WANT TO KEEP A SET OF TASKS IN 1 PLACE. THEN JUST SELECT THE SLOT AND IT WILL REMEMBER ALL YOUR SETTINGS FOR THAT TASK AND RUN IT.
PRO USERS CAN ALSO SELECT THE “ANY BUILD” OPTION IN THE BUILD SELECTION SCREEN TO ROOT ANY BUILD AS LONG AS THE VERSION IS SUPPORTED (USEFUL IF YOUR BUILD IS NOT LISTED).
MORE IMPORTANTLY DONATING SHOWS YOUR APPRECIATION AND ALLOWS THE TOOLKIT TO CONTINUE TO EVOLVE AND GROW.
AUTO REPLY LINKS FOR PAYPAL TO GET A CODE INSTANTLY CAN BE FOUND AT http://goo.gl/nyGqv
--------------------------------------------------------------
PLEASE READ THE *HELP* PAGE AT http://www.skipsoft.net/?page_id=1269 OR USE THE INFORMATION SECTION WITHIN THE TOOLKIT IF YOU HAVE ANY QUESTIONS. I HAVE TAKEN A LOT OF TIME TO WRITE IT AND SOMETHING ON THERE SHOULD ANSWER 99% OF PROBLEMS.
--------------------------------------------------------------
1. INSTALLING ADB/FASTBOOT DRIVERS
The first thing you need to do is to install the adb/fastboot drivers. These are needed so that you can unlock your bootloader, root your device and perform other adb/fastboot functions.
THE DRIVERS CAN BE INSTALLED DIRECTLY VIA THE TOOLKIT. OPTION 1 IN THE MAIN MENU.
If drivers are not installed or there is an exclamation mark next to the device:
Plug the device in to a usb cable directly connected to your motherboard.
In the Device Manager a new item, usually called Android 1.0 should pop up in the list.
Right click on the device item then left click on Update Driver Software. Select 'browse my computer' and then 'Let me pick from a list'.
If no adb interface driver appears in the list then untick 'Show compatible hardware' and find the Android or Samsung adb interface driver.
If you cannot find either of these click Have Disk, browse to the Toolkit install folder, drivers folder, click on android_winusb.inf and click Open.
Click OK and select Google ADB Interface.
Make sure you have USB debugging enabled in settings, developer options. In Android 4.2.2 or later you have to enable the developer options screen by going to settings, About on your device and click on Build number at the bottom 7 times until it says You are now a developer. If you have already enabled usb debugging then unplug/replug the usb cable.
On Android 4.2.2 or later when you replug the usb cable after enabling usb debugging for the first time you will get a popup asking you to authenticate your pc. Tick 'Always allow' then click 'ok'.
--------------------------------------------------------------
2. USING SKIPSOFT UNIFIED ANDROID TOOLKIT
When starting the Toolkit you will first be asked which device you want to work with. Working folders will be created and the device files downloaded. You will then be taken to the Model/Build selection screen where you can do a number of things (other than select your model/build): Type '00' to enter your activation code and enable pro features, 'i' will take you to the Information and Help Section, 'a' will give you information on how to add support for a new build.
Supported builds are listed in the Model/Build selection screen and typing the associated number (i.e. 11) will download needed boot and recovery files (stock and custom recovery) then check for and download the latest superuser files available and custom recovery (pro versions only), verify all the files and start the Main Menu. You can now use all the functions and tools the Android Toolkit offers. Pro users can select the "any build" option to root any build (useful if your build is not listed).
--------------------------------------------------------------
USEFUL INFORMATION
How to get into your FastBoot Mode
1. Turn your phone off
2. Unplug your usb cable if you have one plugged in
3. Keep holding the 'Volume Down' and 'Power' buttons to boot the phone into FastBoot Mode
How to get into Recovery
1. First boot into FastBoot Mode as described above
2. Scroll down with the 'Volume Down' button until it says 'Recovery mode' at the top and press the 'Power' button to enter Recovery
Show the Menu in the Stock Recovery Screen
1. Hold the Power button and keep holding as you press the Volume Up button quickly. The blue recovery menu screen should pop up.
--------------------------------------------------------------
*DISCLAIMER*
I take no responsibility for any fault or damage caused by any procedures within this guide. No warranties of any kind are given.

UPDATES:

VIDEOS:

Frequently Asked Questions:
Q. What is ADB Shell?
Adb shell is a linux command line tool (because android is based on linux) used to send commands to your android device. For S-ON devices, this is crucial for modifying files in the /system partition (where the rom sits) as you cannot modify anything in /system when the rom is running without S-OFF (e.g removing system apps).
From Google:
Android Debug Bridge (adb) is a versatile tool lets you manage the state of an emulator instance or Android-powered device. It is a client-server program that includes three components:
A client, which runs on your development machine. You can invoke a client from a shell by issuing an adb command. Other Android tools such as the ADT plugin and DDMS also create adb clients.
A server, which runs as a background process on your development machine. The server manages communication between the client and the adb daemon running on an emulator or device.
A daemon, which runs as a background process on each emulator or device instance.
----------------------------------------------------------------------------
Q. What is FASTBOOT?
Fastboot is 2 things. It is a mode on the phone, which looks a little like Bootloader. You can access it by holding 'Volume Up' and 'Volume Down' whilst turning on the phone.
It is also a way of flashing radios, recovery, boot images and system images in a command line method from a PC much like adb.
----------------------------------------------------------------------------
Q. I flashed CWM but each time I reboot the Stock Recovery is back
There is an auto recovery restore system on certain Stock Android Builds that will reflash the Stock Recovery if you flash CWM on a Stock Rom.
Use Root Explorer to Mount the system folder as R/W (or use a free app from Google Play such as ES File Explorer). Rename the files /system/recovery-from-boot.p and /system/etc/install-recovery.sh. Now when you flash CWM Recovery it will NOT be overwritten after a reboot.
OR you can use the ToolKit to rename the files (root access needed).
----------------------------------------------------------------------------
Q. I want to send my phone back so I need to flash a stock rom and relock the bootloader
1. Download, install and run the Google Nexus 4 Toolkit.
2. Install adb/fastboot drivers (if you havent already done so)
3. Option 9 to download a Google Factory Image.
4. After it finishes downloading you will be given the option to flash the image to your tablet. Do this.
4. Let the phone reboot, then shut the device down and reenter fastboot mode (or boot to fastboot mode via the Reboot Screen in the ToolKit).
5. Option3, 2 to relock the bootloader.
Your internal storage will be formatted and data and cache wiped. Your tablet will now be back to an out-of-the-box FULLY STOCK state and ready to send back.
----------------------------------------------------------------------------
Q. What is the difference between Nandroid and Titanium backup?
A NANDROID will backup the whole system including boot, system, data and recovery partitions so you can restore a complete rom and all data and settings.
Essentially Titanium Backup is used to backup apps and associated user data. These could be restored AFTER a full wipe and a new Rom had been flashed on your phone.
The other option now which google added into the new adb command list is the adb backup which is in the ToolKit and can do the same job as Titanium Backup but will store the data on your PC rather than on the phone (where it takes up space and could be deleted).
----------------------------------------------------------------------------
Q. When I try to open the ToolKit I get a box pop up for a split second and then it goes away. My AntiVirus program says the file may be harmful.
The exe files I compiled are not digitally signed with a Microsoft certificate (as they cost money) so certain AntiVirus programs (mainly Norton) will pick it up as potentially harmful when it is not. They will pick up ANY file that doesnt contain a purchased Microsoft certificate in the same way. Restore the deleted file and exclude it from further scans and it will be fine.
----------------------------------------------------------------------------
Q. The ToolKit recognises my tablet in adb mode but not in fastboot mode (or other way round).
Open the Device Manager on your pc and then boot your tablet into fastboot mode or adb mode (dont plug the usb cable in yet). Make sure USB debugging is enabled on your tablet in settings, developer options. Plug the cable in while watching the Device Manager and determine which item is added to the list with the device plugged in. Once you have found it right click on the item and select update driver. Select 'browse my computer' from the list and then browse to the 'drivers' folder in the ToolKit folder (wherever you installed the ToolKit to). Make sure sub folders is ticked and click next. Hopefully the driver will be picked up and installed.
You can check if a driver has been installed by looking at the top of the Main Menu in the ToolKit while in fastboot mode and adb modes. If a serial number is displayed in each mode then it will work fine.
----------------------------------------------------------------------------
Q. Can I back up my apps before unlocking the Bootloader so I don't lose everything?
Performing an APPS BACKUP (option2, 1) will backup all apps that were installed after you first used your device. This will include any associated user data (such as settings or high scores for games) and apps you installed from Google Play Store. Just follow the recommended options and remember to turn your phones screen on before starting it as you need to confirm on your screen.
This option will NOT require your bootloader to be unlocked first.
You can also backup your Internal Storage without unlocking using option 2, 3 from the main menu. This will backup anything you store on your Internal Storage such as game data, music, videos. This is just pulled from your /data/media folder so you can view or edit the files on your pc after they have been pulled.
You can then unlock the bootloader (wiping your device) and retore the apps (option 2, 10) and Internal Storage data (option 2, 11) after doing whatever you want to with your device.
The only thing you cannot do with the ToolKit is to save the system settings but some of those are backed up by google if you chose that option when turning your device on the first time.
----------------------------------------------------------------------------
Q. I have Windows 8 and cannot install the drivers
How to Disable Driver Signature Enforcement in Windows 8:
From the Metro Start Screen, open Settings (move your mouse to the bottom-right-corner of the screen and wait for the pop-out bar to appear, then click the Gear icon).
Click ‘More PC Settings’.
Click ‘General’.
Scroll down, and click ‘Restart now’ under ‘Advanced startup’.
Wait a bit.
Click ‘Troubleshoot’.
Click ‘Advanced Options’
Click ‘Windows Startup Settings’
Click Restart.
When your computer restarts, select ‘Disable driver signature enforcement‘ from the list. You can now load your modified driver. Reboot again once the driver is installed and all will be well.
----------------------------------------------------------------------------
Q. I cannot find Developer options to Enable USB Debugging
With Android 4.2 google have thought it would be funny to hide the Developer options screen in the Settings. This means you cannot enable usb debugging to communicate with your device. To show the Developers options screen do the following:
Goto Settings, About tablet and tap your finger on the the 'Build number' text at the bottom 7 times (not too fast).
When you have tapped 3 times you will be given a countdown of taps until you become a 'developer'.
Once you are told you are now a developer you can go back to the Settings screen and can see Developer options.
You can now go into Developer options and enable usb debugging.
----------------------------------------------------------------------------
Q. I tried to enter the code for the professional version but the Toolkit says the code is incorrect
Make sure the code entered is for the correct Toolkit being used.
You need to make sure you start the Toolkit with the toolkit.exe file when activating and not the tkmain.exe file so the settings can be initialised or the code will not be accepted.
Also make sure you enter the code correctly as the characters are case sensitive.

First... thanks for this...
Sent from my Galaxy Nexus using Tapatalk 2

Unboxed my replacement N7. Tuned it on, initial setup, connected to my desktop, ran the one-click routine and 5 minutes later I'm unlocked, rooted and ready to go. Well done, Mark!

Amazing work! I just got my Nexus 7 about an hour ago, and I was able to easily unlock and root it with your program. Thanks! :good:

How much do I have to donate to get the donate version?

My Nexus 7 arrives this morning and I find this software ready and waiting. Amazing.

you may want to add this
You may want to add this as step one if more people have this same problem. I was having a problem where I wasn't able to flash any recovery at all. You can one time boot into a recovery but it wouldn't flash. Since I had already renamed the original one and it had failed to flash CWM it just hung up at the google screen. After about a hour of trying.( uninstalling drivers, trying a different computer) I found this and it fixed it. If this turns out to be a widespread issue this is a pretty easy fix.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Browse to your SDK directory and futher into \extras\google\usb_driver
Open android_winusb.inf in your favorite text editor.
Find the appropriate section Google.NTx86 if your on 32bit or Google.NTamd64 if your on 64bit (doesnt matter that your using intel chip). Now find the ";Google Nexus 7" line inside that section and you'll see a series of settings below. Add the following lines at the end of that block.
Code:
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E44&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001
These are the identifiers for the Nexus 7 recovery and bootloader usb connections.
(Source- Napalm2) http://forum.xda-developers.com/show....php?t=1794203
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

PROlific666 said:
You may want to add this as step one if more people have this same problem. I was having a problem where I wasn't able to flash any recovery at all. You can one time boot into a recovery but it wouldn't flash. Since I had already renamed the original one and it had failed to flash CWM it just hung up at the google screen. After about a hour of trying.( uninstalling drivers, trying a different computer) I found this and it fixed it. If this turns out to be a widespread issue this is a pretty easy fix.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Browse to your SDK directory and futher into <SDK>\extras\google\usb_driver
Open android_winusb.inf in your favorite text editor.
Find the appropriate section Google.NTx86 if your on 32bit or Google.NTamd64 if your on 64bit (doesnt matter that your using intel chip). Now find the ";Google Nexus 7" line inside that section and you'll see a series of settings below. Add the following lines at the end of that block.
Code:
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E44&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001
These are the identifiers for the Nexus 7 recovery and bootloader usb connections.
(Source- Napalm2) http://forum.xda-developers.com/show....php?t=1794203
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Click to expand...
Click to collapse
Thanks for the info.
In the driver pack made by 1wayjonny (and the one used in the ToolKit) the first line is already included in the google nexus 7 section the inf. The second line is in the section for the samsung galaxy nexus.
Did you install your drivers through the ToolKit or via another method? Im just not sure if the second line can be added to the google nexus 7 section in the inf file which would mean both are included when drivers are installed.
The source you posted doesnt lead anywhere can you post where you found the info and if its good I can just add that extra line to install the driver.
Mark.

This is great! This is the only method that worked for me. I would lose root and stuff doing it any other way. Thanks for this!

Excellent I was wondering when you would show up on the N7 forum. Great work. Gonna unroot just to try it out. LOL
Great work as always!

rsxtypes72 said:
Excellent I was wondering when you would show up on the N7 forum. Great work. Gonna unroot just to try it out. LOL
Great work as always!
Click to expand...
Click to collapse
HAHA well give it a good test I need to know everything works
Mark.

I haven't even used this yet, but I wanted to donate for your work.
Confirmation number: 5M0683778X2063948
Is there any way to use TWRP instead of CWM for recovery? Or would that have to be changed after the fact?
Edit: Yes, there is! Option is available during the install process.

Great work! Thanks very much.
I will give it a try and if all OK will donate.
Sent from my Nexus 7 using Tapatalk 2

I used the toolkit first and when I had tried everything I could think of I uninstalled the drivers and tried the manual method. I thought it may have been some interference caused by my Gnex since my tablet was showing up as a Samsung phone in the device manager so I switched to my other laptop installed the kit and used the install method included in the kit. When that didn't work I went to the Asus website and downloaded then drivers directly from there and still no luck. I found that post after almost giving up for the night and after I changed the line ( I only added the bottom one bc the other was already there) the recovery finally stuck.
I sent a pm to the op to see where he got the info I will post when he gets back to me.
Sent from my Nexus 7 using Tapatalk 2

I was hoping you would show up with a tool kit like this for the N7! I have been using your toolkit for the Galaxy Nexus with great success and just had great success with yours on the N7

PROlific666 said:
I used the toolkit first and when I had tried everything I could think of I uninstalled the drivers and tried the manual method. I thought it may have been some interference caused by my Gnex since my tablet was showing up as a Samsung phone in the device manager so I switched to my other laptop installed the kit and used the install method included in the kit. When that didn't work I went to the Asus website and downloaded then drivers directly from there and still no luck. I found that post after almost giving up for the night and after I changed the line ( I only added the bottom one bc the other was already there) the recovery finally stuck.
I sent a pm to the op to see where he got the info I will post when he gets back to me.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
It could be implemented just as easily into the ToolKit's drivers from 1wayjonny by just adding the bottom line into the Nexus7 section. That line is already in the Galaxy Nexus section but it wouldnt do any harm adding it to another section if the driver is required as you said.
Im tempted to just add it anyway lol.
Mark.

mskip said:
It could be implemented just as easily into the ToolKit's drivers from 1wayjonny by just adding the bottom line into the Nexus7 section. That line is already in the Galaxy Nexus section but it wouldnt do any harm adding it to another section if the driver is required as you said.
Im tempted to just add it anyway lol.
Mark.
Click to expand...
Click to collapse
Worked a treat! My recovery is there when I reboot to recovery using Quick Reboot from the market. I did not have to add anything further to get the recovery to stick. Thanks very much for your work, and enjoy the pint I bought ya. :laugh:

Guide to install TWRP

Files to download:
river-TWRP-09-12-19.img
river-TWRP-installer-09-12-19.zip
Link to Downloads:
https://1drv.ms/u/s!AlxqpoojMfYn6XSvYmti53DphPbX?e=kQ84oI
1. Place river-TWRP-installer-09-12-19.zip on sdcard
2. Power off your device
3. Hold power button and volume down to start phone in bootloader mode
4. Navigate to download location of twrp files
5. Using Windows Explorer, navigate to the location of twrp-3.2.3-42-evert.img. Hold the Shift Key on your Keyboard. While holding Shift, Right Click in the window(not on the file). Depending on your windows version you should see either "Open PowerShell Window here" or "Open Command Window here." Select which ever one applies. You will see a black and white screen or a blue and white screen. The steps are the same no matter which screen you see.
6. In terminal window use command:
fastboot boot twrp-river-09-12-19.img
7. In twrp, tap install and navigate to river-TWRP-installer-09-12-19.zip and swipe to flash!
8. Done - TWRP can now be accessed using the recovery option in bootloader.

Hi thanks for the tutorial. I have a G7 plus(Lake). Will this method work using the correct files for LAKE? I read somewhere that there's some for of issue with dm verity.
Thanks is advance

U may need to post in the plus forum...akaik twfp for android 10 in general is broken and everyone is waiting for a 'TWRP 10' that their devs are working on. I'm so tired of waiting that I'm gonna root without twrp this weekend if I have some time, and use software BU like Titanium and flash twrp10 when/if it's released...smh

[Guide] Root Pixel 4 XL Android 10 (Q)

Root Pixel 4 XL Android 10 (Q) Unlock/Lock Bootloader + Systemless ROOT
Android Security Buletin-August 2020
Pixel Update Bulletin—August 2020
Introduction
This Guide is for Pixel 4 XL owners that want to Root their phone, and enjoy the benefits of rooting it without installing a Custom ROM. However, for those that just can't live without a Custom ROM, take a look at 'Custom ROMs for Pixel 4 XL'.
This Guide also works for Pixel 4 owners: If, they download the Pixel 4 files.
NEW
Gpay not working? Try this.
Tulsadiver's ADB Magisk Module Mod Installer has a LINUX instaler.
The best instuctions on how to Pass SafetyNet, i've ever read.
Update(s)
Factory/OTA Images - 08/05
Magisk Stable - Magisk-22.0 02/23
Magisk Beta - Magisk-22.0 02/23
Magisk Canary - Magisk-22001
TWRP - twrp-3.5.0_10-1-coral.img/zip 01/02
SafetyNet - SafetyNetFix v1.1.1 01/16
SDK Platform-tools - r31.0.0 03/01
Custom Kernels
No Updated Kernels
Custom ROMs
Waiting
Disclaimers
I assume no responsibility for the malfunctioning/bricking of your phone.
The order of listed items i.e., Custom Kernels, Custom ROMS, etc. Does not indicate my preference for them. It is your responsibility to do the research before selecting an item.
Prerequisites
A Pixel 4 XL phone with an unlocked bootloader.
The latest Android 10 (Q) Factory or OTA Image: "coral" for Pixel 4 XL
Factory Image
10.0.0 (QQ3A.200805.001, Aug 2020)
OTA Image
10.0.0 (QQ3A.200805.001, Aug 2020)
Computer - With the latest SDK Platform-Tools: r31.0.0 installed.
Important: Update Platform Tools, regularly, for optimal performance.
Other Guides
[Guide] Root Pixel 4 XL Android 11 (R)
Credits/Thanks/Recognitions
@topjohnwu - Magisk Canary
Those I may have, inadvertently, forgotten.
Index
(NOTE: Numbers 1-13 are not steps, they are individual sets of instructions).
Open a Command Prompt/Boot Fastboot Mode/Boot Recovery
Open Command Prompt on Computer
Option 1 - Open File Explorer, click the platform-tools folder, press shift, right click, and select open command prompt here.
Option 2 - Open File Explorer, click the platform-tools folder, highlight the directory information in the address bar or click the folder (left side of address bar) to highlight it type cmd and press enter.
Notes:
If your computer only has 'open powershell here' in the context menu. Use option 2.
If you do not want to open a Command Prompt every time you want to use fastboot, add the path to the Platform-tools folder to Windows environment variables.
Boot fastboot mode:
Power off phone, press and hold the power and volume down buttons until you see Start.
Boot Recovery
Power off phone, press and hold the power and volume down buttons until you see Start. Use volume up/down button until you see Recovery mode. Press power button.
Test fastboot
Enable Developer Options - Tap Settings > About phone > Build number 7 times or until you should see 'you are a Developer'.
Enable USB Debugging - Tap Settings > System > Advanced > Developer options >
Enable USB Debugging.
Open a Command Prompt on your computer in the Platform-tools folder.
Boot fastboot mode on your phone (#1)
Connect the phone to the Computer.
At the prompt type: fastboot devices to verify communication with phone. It should return your phone's serial number.
Unlock Bootloader/Return Phone to Stock/Lock Bootloader
Unlock Bootloader
This will erase all user data from the device!
Backup your data
Activate Developer Options: Tap Settings > About Phone > Tap Build Number 7 times or until you see you are a Developer. Tap back > System > Advanced > Developer Options. Enable OEM Unlock and, USB Debugging.
Boot fastboot mode
Connect the phone to the Computer with USB cord.
Open a Command Prompt on your computer and type fastboot flashing unlock and press enter.
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 and then type fastboot reboot at the Command Prompt and press enter.
When your phone reboots disconnect your usb cable.
Note: After unlocking your bootloader, you'll see a warning: You will see this warning until, you relock the bootloader.
Return Phone to Stock
Important: Do not relock your bootloader until you have returned the device to Stock..
Backup your data/Internal storage
Settings > System > Advanced > Reset Options > Erase all data (factory reset)
Log in
Set up phone
Lock Bootloader (Google Pixel 4 XL)
Return the phone to Stock before Locking the bootloader!
This will erase all user data from the device!
Boot fastboot mode
Open a Command Prompt and type this at the Prompt: 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: fastboot reboot
Enable Developer Options: Settings > About phone > Tap Build number 7 times or until you see 'you are a developer'.
Tap Back > Developer options and toggle OEM Unlock off.
Install/Update Factory Image keep or wipe data
Important Note(s):
When doing a major upgrade i.e., Android 10 (Q) to Android 11 (R): I recommend doing a clean install. What is a clean install?:
Doing a Factory reset prior to installing, major, update.
Using flash-all.bat file without removing the -w.
Always verify you have the latest version of SDK Platform-Tools installed on your computer before installing the Factory Image: Pixel 4 XL - coral.
If your phone is rooted and you have Modules installed and you want to 'Keep Data', remove them before you install the Factory Image:
Why? Some Modules need to be updated before use with a new Factory/OTA image because (sometime) Google makes changes to Factory/OTA images that break the Modules.
How to remove Magisk: Open Magisk App ==> Tap Uninstall == Tap Restore Images.
If you get an error: when flashing the Factory image, try one of these options:
Change the USB port to a non charging USB port.
Change the USB cord to one that doesn't have the blue color head or use a USB C to C cable.
Change Computers.
Backup your data
Download the latest Factory Image: Pixel 4 XL - coral to your Computer.
Extract the factory Image to a folder.
Keep Data
Open the folder you extracted the Factory Image to and Edit the flash-all.bat file with a file editor i.e. Notepad. Remove -w from this command: fastboot -w update image-coral-aa9a.999999.999.zip
Note: If you do not remove the -w your data and internal storage will be wiped.
After, you have edited the flash-all.bat file. Copy/Move these files to the Platform-tools folder:
bootloader-coral-....img
flash-all.bat
image-coral-....zip
radio-coral-....img
Open a Command Prompt on your computer in the Platform-tools folder ==> Boot fastboot mode on your phone ==> Connect the phone to the Computer.==> At the prompt type: flash-all and press enter.
Note: During the flashing you may notice the phone is in fastbootd mode that is a normal for Android 10 (Q).
System will reboot when flashing is complete.
Do #7 or #8 to root/reroot.
Wipe Data
Open the folder you extracted the Factory Image to and View the flash-all.bat file with a file editor i.e. Notepad. Verify the file has the -w in this command: fastboot -w update image-crosshatch-aa9a.999999.999.zip
Note: This will wipe your data and internal storage.
Copy/Move these files to the Platform-tools folder:
bootloader-coral-....img
flash-all.bat
image-coral-....zip
radio-coral-....img
Open a Command Prompt on your computer in the Platform-tools folder ==> Boot fastboot mode on your phone ==> Connect the phone to the Computer.==> At the prompt type: flash-all and press enter.
Note: During the flashing you may notice the phone is in fastbootd mode that is a normal for Android 10 (Q).
System will reboot when flashing is complete.
Do #7 or #8 to root/reroot.
ADB Sideload
Stock Recovery
Full OTA Images for Nexus and Pixel Devices - Updating instructions
Custom Recovery - TWRP
Important notes:
Charge your device.
Enable USB Debugging on your phone.
Install the latest version of SDK Platform-tools on your computer.
Open a command prompt in the computer's ADB folder: the folder with ADB.exe in it.
Put the (flashable zip) file you want to sideload in the computer's ADB folder.Copy the Zip file you want to install on your device to the ADB folder.
Connect your device to your computer using a USB cable.
Boot T.W.R.P.
T.W.R.P installed: Boot fastboot mode ==> use volume buttons up/down until you see Recovery mode ==> press power botton.
T.W.R.P. not installed: Boot T.W.R.P: Put twrp.img file in the computer's ADB folder ==> open a command prompt in ADB folder ==> at the prompt type fastboot flash boot "Name of twrp file.img" without the quotation marks.
When T.W.R.P boots tap Advanced ==> ADB Sideload.
✓ the wipe Dalvik cache box
Swipe to start
On your Computer: Enter the following command at the command prompt. adb sideload <filename.Zip> i.e., adb sideload myfile.zip
You will see the progress of the sideloaded file.
When the file finishes sidloading, reboot your device.
Done!
Extract/Flash boot.img
Extract boot.img
Download the latest Factory image to your phone.
Use a File Explorer to extract the boot.img from the Factory Image.
Extract the Factory Image file (coral-pda1a.999999.999-factory-99a9a99a.zip) to a folder.
Open the folder and, extract the Image file (image-crosshatch-aa9a.999999.999.zip).
Flash boot.img
Note: Flashing this file removes root.
Open the folder you extracted the 'image file' to and copy the boot.img file to your computer's platform-tools folder or to the folder that has fastboot.exe in it.
Boot fastboot mode
Connect the phone to the Computer
Open a Command Prompt and type the following command at the prompt:
Code:
fastboot flash boot --slot all boot.img
Reboot
Install T.W.R.P./Root/Reroot with Magisk and Pass SafetyNet.
Important Note(s):
Set Pin before installing TWRP: Settings > Security & location >Screen lock > Pin
Backup your data
Download files - The listed files are used with #7, and #8.
T.W.R.P
twrp-3.5.0_10-1-coral.img - Download to your computer
twrp-installer-3.5.0_10-1-coral.zip - Download to your phone
Magisk - Download to your phone
The latest Magisk Beta/Stable zip. - Download to your phone
The latest Magisk Canary - Download to your phone
Custom Kernels - Download to your phone
No Updated Custom Kernels
Kernel Manager - Download to your phone
EX Kernel Manager
Boot fastboot mode
Connect the phone to the Computer with USB cord.
Copy twrp-3.5.0_10-1-coral.img to the platform-tools folder or folder that has fastboot in it and rename it twrp.img.
Open a Command Prompt on your computer.
At the Command Prompt type: fastboot boot twrp.img and press enter.
When TWRP boots, disconnect the phone from computer.
If requested, swipe to allow modifications.
Tap Install select twrp-installer-3.5.0_10-1-coral.zip, Swipe Slider to install
Reboot Recovery
Root/Reroot
Note(s):
If you are rerooting, tap Install, select Magisk's uninstaller.zip, Swipe the slider to install.
Some Custom Kernels can be updated by flashing via Kernel Manager without losing root. Check the Custom Kernel thread (OP - Installation/Instructions) to find out which Custom Kernels.
With Custom Kernel (Optional)
No Updated Custom Kernels
Without Custom Kernel
Tap Install, select Magisk-Beta/Canary/Stable zip.
Swipe Slider to Install
Reboot System
Install Modules (Optional)
Boot T.W.R.P./Root/Reroot with Magisk and Pass SafetyNet.
Backup your data
Download files - See #7 - Skip the twrp-installer
Boot fastboot mode
Connect the phone to the Computer with USB cord.
Copy twrp-3.5.0_10-1-coral.img to the platform-tools folder or folder that has fastboot in it and rename it twrp.img.
Open a Command Prompt on your computer.
At the Command Prompt type: fastboot boot twrp.img and press enter.
When TWRP boots, disconnect the phone from computer.
If requested, swipe to allow modifications.
Root/Reroot
Note: If you are rerooting, tap Install, select the latest Magisk's uninstaller.zip, Swipe the slider to install.
With Custom Kernel (Optional)
No Updated Kernels
Without Custom Kernel
Tap Install, select Magisk-Beta/Canary/Stable zip.
Swipe Slider to Install
Reboot System
Install Modules (Optional)
Root/Reroot with Magisk and Pass SafetyNet.
Important Note(s):
When doing a major upgrade i.e., Android 10 (Q) to Android 11 (R): I recommend doing a clean install. What is a clean install?:
Doing a Factory reset prior to installing, major, update.
Using flash-all.bat file without removing the -w.
To root use Magisk App Beta, Canary or Stable App to patch the Stock boot.img.
Download files:
Magisk App - Download to your phone
Magisk Beta/Stable App
Magisk Canary App
Custom kernels - Download to your phone - install with Kernel Manager
No updated Kernels
Kernel Manager - Download to your phone
EX Kernel Manager
Patching the boot.img
Do #6 - Extract boot.img
Install Magisk (Beta or Canary) App
Open Magisk App
Depending on the version of Magisk App installed: Set the Update Channel to Beta, Canary or Stable.
Tap Install (next to Magisk)
Tap, Select and Patch a File
Select the boot.img file you extracted from the latest factory image.
Tap the ✓ (Check Mark)
Tap Let's Go
When you see done, the boot.img has been patched (magisk_patched_xxxxxx.img) and stored in the download folder.
The phone will reboot.
Copy the magisk_patched.img file to your computer's Platform-tools folder or the folder that has fastboot.exe in it.
Boot fastboot mode (See #1B)
Connect the phone to the Computer with USB cord.
Open a Command Prompt (See #1A) in the folder you copied the magisk_patched.img to.
Type fastboot flash boot magisk_patched.img at the Prompt and press enter.
Type fastboot reboot at the Prompt and press enter.
Important Notes: If your phone boot loops try one of the following options:
Flash the 'stock' boot.img to both slots: fastboot flash boot boot.img --slot all
Boot Safe Mode - Press Power Off button ==> Press Power Off until you see boot Safe Mode ==> Press Ok.
Pass SafetyNet: #12 Apps/Mods/Scripts/Tethering/Themes
OTA Installation - Keep Root -- No Computer Needed
OTA Installation
Set Magisk App Update Chanel/Update Magisk
Set Magisk App Update Chanel
Open Magisk App > Tap menu icon > Settings > Update Channel > Select Stable, Beta, Canary or Custom.
Update Magisk
When Magisk App notifies you of an update:
Tap install.
Select, Direct Install (Recommended)
When it finishes installing
Tap, Save Log
Log location: /storage/emulated/0/MagiskManager/logs/install_log_...
Tap, Reboot
Done!
Custom ROMs for Pixel 4 XL
Need help with a Custom ROM?
Follow the Installation Instructions of the Developer of the Custom ROM you are trying to install.
If you have a problem Installing the ROM, Search the thread of the Custom ROM you want to install for solutions to problem before posting a request for help on their thread.
Custom ROMS
Alpha/Beta
Waiting...
Official
Waiting...
Unofficial
Waiting...
Apps/Mods/Scripts/Tethering/Themes
MAGISK MODULE ❯ Universal SafetyNet Fix 1.1.0
T.W.R.P. 3.5.0_10-1 Backup/Restore
https://forum.xda-developers.com/t/twrp-coral-official.4111017/post-82764097

Great write up...as always. Is there an way to update security patches and keep root?

State.of.mind said:
Great write up...as always. Is there an way to update security patches and keep root?
Click to expand...
Click to collapse
Not really if you use factory images.
https://forum.xda-developers.com/pixel-4-xl/how-to/november-factory-images-t3997383/post80784067

Edit: nevermind

Badger50 said:
Not really if you use factory images.
https://forum.xda-developers.com/pixel-4-xl/how-to/november-factory-images-t3997383/post80784067
Click to expand...
Click to collapse
I guess it depends on what Factory Image information is needed.

State.of.mind said:
Great write up...as always. Is there an way to update security patches and keep root?
Click to expand...
Click to collapse
Thank you!
No, but look at # 9C

How do you know what November security patch to choose? When I go on the factory website there are three different versions of the update.
---------- Post added at 08:18 AM ---------- Previous post was at 08:15 AM ----------
State.of.mind said:
How do you know what November security patch to choose? When I go on the factory website there are three different versions of the update.
Click to expand...
Click to collapse
Never mind. I used this link to figure it out: https://support.google.com/pixelphone/thread/18553639?hl=en Hopefully it helps someone else

So this may be a dumb question but, does accepting an OTA relock the boot loader?

fredgar75 said:
So this may be a dumb question but, does accepting an OTA relock the boot loader?
Click to expand...
Click to collapse
No, but you must be Stock to accept the OTA, unless you do the Magisk OTA Installation.

State.of.mind said:
How do you know what November security patch to choose? When I go on the factory website there are three different versions of the update.
---------- Post added at 08:18 AM ---------- Previous post was at 08:15 AM ----------
Never mind. I used this link to figure it out: https://support.google.com/pixelphone/thread/18553639?hl=en Hopefully it helps someone else
Click to expand...
Click to collapse
I guess you didn't see the description of the Factory/OTA at the end of the download Factory/OTA links in 'Prerequisites'.

Will this work on the Verizon Pixel 4 XL??

SAMCR02018 said:
Will this work on the Verizon Pixel 4 XL??
Click to expand...
Click to collapse
If the bootloader is unlocked, it will work.

Homeboy76 said:
If the bootloader is unlocked, it will work.
Click to expand...
Click to collapse
That I know ok can the Verizon version get the BL unlocked?

SAMCR02018 said:
That I know ok can the Verizon version get the BL unlocked?
Click to expand...
Click to collapse
AFIK there is no method of unlocking the bootloader of a Verizon Pixel 4 XL after you activate it.
This thread suggest a possibility of unlocking A Verizon Pixel 4 XL bootloader if done before you activate it.
https://forum.xda-developers.com/pixel-4-xl/how-to/root-instructions-verizon-pixel-4-xl-t3990767

[deleted]

Factory/OTA Images - Dec 2019

Does someone have December boot.img? Ater updating got into bootloop, flashing previous magisk boot image with fastboot didn't worked

Can anyone definitively tell me whether re-locking the bootloader will wipe any data on the Pixel 4 XL? Thanks in advance!

fronc said:
Can anyone definitively tell me whether re-locking the bootloader will wipe any data on the Pixel 4 XL? Thanks in advance!
Click to expand...
Click to collapse
Yes....it definitely will! All of it!

Factory images are up. Does anyone know which one is for which?

[Guide] Root Pixel 4 XL with Magisk Android 13

[Guide] Root Pixel 4 XL With Magisk Android 13
Android Security Bulletin—Feburary 2023
Pixel Update Bulletin—Feburary 2023
Introduction
This Guide is for Pixel 4 XL owners that want to Root their phone, and enjoy the benefits of rooting it. The Guide is divided into three parts: Information, Instructions, and Other.
~ ~ ~ Part I - INFORMATION ~ ~ ~
Disclaimer
I assume no responsibility for the malfunctioning/bricking of your phone.
The order of listed items i.e., Custom Kernels, Custom ROMS, etc. Does not indicate my preference for them. It is your responsibility to do the research before selecting an item.
Prerequisites
A Pixel 4 XL phone with an unlocked bootloader.
A Computer with the latest working SDK Platform-tools 33.0.3 installed.
Important Notes:
a. Before installing SDK Platform-tools, check for older versions of fastboot on your computer: Open a Command prompt and type fastboot --version at the prompt. If a adb/fastboot is found delete the folder containing them. Also, check the path environment for paths to them and remove it.
b. Update Platform Tools, regularly, for optimal performance.
c. Need Google's USB Drivers for your Pixel Phone?
NEW
"...make a 100% clean install of ANY Magisk version or fork without PC or TWRP."
Magisk General Support / Discussion
This is the place for general support and discussion regarding "Public Releases", which includes both stable and beta releases. All information, including troubleshoot guides and notes, are in the Announcement Thread
forum.xda-developers.com
Update(s)
Magisk Alpha - app-release_709f25f6-26101.apk 12 Apr
Magisk Beta - Magisk v26.1.apk 11 Apr
Magisk Canary - app-release_a8c4a33e-26103.apk 23 Jun
Magisk Cygisk - Click Pages 5 for installation Instructions.
Magisk Delta -
app-release
Magisk Stable - Magisk v26.1.apk 11 Apr
SafetyNet - Displax's SafetyNet Fix, v2.4.0-MOD_1.3 17Jun
SDK Platform-tools 33.0.3 Aug 2022
Custom Kernels
Note: If you are using a Custom Kernel, please update using the method in the OP, Index, 4. Install/Update Factory Image keep data or wipe data, • Flash Factory Image Keep Data
Google Pixel 4 XL ROMs, Kernels, Recoveries, & Other
My Other Guides
Pixel 7 Pro
Pixel 6
Pixel 5
Pixel 4a (5G)
Pixel 3 XL
Pixel 1 XL
Credits/Thanks/Recognitions
bradical711 - Instructions to Pass Safety Net
Those I may have, inadvertently, forgotten.
~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~
(The Instructions listed below are not steps, they are individual sets of instructions.)
Open a Command Prompt/Boot Fastboot Mode/Boot Recovery
Open a Command Prompt on Computer
Open File Explorer, click the platform-tools folder ==> click the folder icon (left side of address bar) to highlight it type cmd and press enter.
Open a Powershell Command Prompt on Computer: Open File Explorer, click the platform-tools folder ==> click the folder icon (left side of address bar) to highlight it type powershell and press enter.
Notes:
Enable USB Debugging, on your phone: Settings ==> System ==> Advanced ==> Developer options ==> Scroll down to USB debugging and enable it.
When using the Powershell Command Prompt Commands must be preceeded with ./: i.e, ./fastboot devices
If you do not want to open a Command Prompt every time you want to use the fastboot command, add the path to the Platform-tools folder to Windows environment variables.
Boot fastboot mode (bootloader):
Power off phone, press and hold the power and volume down buttons until you see Start.
Boot Recovery
Power off phone, press and hold the power and volume down buttons until you see Start. Use volume up/down button until you see Recovery mode. Press power button.
Test fastboot
Enable Developer Options - Tap Settings > About phone > Build number 7 times or until you should see 'you are a Developer'.
Enable USB Debugging - Tap Settings > System > Advanced > Developer options >
Enable USB Debugging.
Open a Command Prompt on your computer in the Platform-tools folder.
Boot fastboot mode on your phone (#1)
Connect the phone to the Computer.
At the prompt type: fastboot devices to verify communication with phone. It should return your phone's serial number.
Unlock Bootloader/Return Phone to Stock/Lock Bootloader
Unlock Bootloader
This will erase all user data from the device!
Backup your data
Activate Developer Options: Tap Settings > About Phone > Tap Build Number 7 times or until you see you are a Developer. Tap back > System > Advanced > Developer Options. Enable OEM Unlock and, USB Debugging.
Boot fastboot mode
Connect the phone to the Computer with USB cord.
Open a Command Prompt on your computer and type fastboot flashing unlock and press enter.
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 and then type fastboot reboot at the Command Prompt and press enter.
When your phone reboots disconnect your usb cable.
Notes: After unlocking your bootloader, you'll see a warning: The bootloader is unlocked and... You will see this warning until, you relock the bootloader.
Do not relock your bootloader until you have returned the device to Stock.
Return Phone to Stock
Backup your data/Internal storage
Settings > System > Advanced > Reset Options > Erase all data (factory reset)
Log in
Set up phone
Lock Bootloader
Return the phone to Stock before locking the bootloader, failure to do so could brick your phone
This will erase all user data from the device!
Boot fastboot mode
Open a Command Prompt and type this at the Prompt: 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: fastboot reboot
Enable Developer Options: Settings > About phone > Tap Build number 7 times or until you see 'you are a developer'.
Tap Back > Developer options and toggle OEM Unlock off.
(NEW) Make Both Slots Bootable: Manually, Flash the OTA Image to Both Slots - One bootable and rooted, the other slot bootable without root.
Before you start
Backup your data
Make sure that there is no pending OTA update, by going to Settings > About phone > System updates, which should say Your system is up to date.
Download the latest Factory and OTA image for your device.
Verify the checksum of the Factory and OTA image. The last portion of the filename is the first 8 digits of its SHA-256 checksum; the full SHA-256 checksum is shown next to the download link.
Extract the boot/init_boot.image from the Factory image:
Extract the Factory Image file that you downloaded (coral-a9a9a.999999.999-factory-99a9a99a.zip) into a folder.
Open the folder you extracted the Factory image to and extract the Image file (image-coral-aa9a.999999.999.zip) into a folder. The stock boot/init_boot.img file should be in this folder.
Patch the boot/init_boot.img:
Open the Magisk Alpha/Beta/Canary/Delta/Stable App
The Update Channel should be set to Alpha/Beta/Canary/Delta/Stable, depending on the version you installed.
Tap Install (next to Magisk)
Tap, Select and Patch a File
Select the boot/init_boot.img file you extracted from the factory image.
Tap the ✓ (Check Mark)
Tap Let's Go
When you see done, the boot/init_boot.img has been patched (magisk_patched_xxxxxx.img), and is stored in the download folder.
Reboot
Copy/Move the magisk_patched....img file to your computer's Platform-tools folder or the folder that has fastboot.exe in it:
Boot Recovery mode
With the device powered on and USB debugging enabled, type: adb reboot recovery
If you're unable to use adb to reboot into recovery, you can use the key combination for your device: Press and hold Volume Down button, then press and hold Power button then use the Volume Down/Up button to select the Recovery option from the menu.
The device is now in recovery mode an Android logo with red exclamation mark should be on the screen.
Access the recovery menu:
Hold the Power button and press Volume button up once. The recovery text menu will appear.
Enter sideload mode:
Select the Apply update from ADB option from the recovery text menu
Run the following command: adb devices check that your device shows up with "sideload" next to its name.
Sideload the OTA zip file
Connect the phone to the PC via USB cable
On the phone: boot bootloader/fastboot mode
On the PC:
Open a command prompt in the SDK Platform-tools folder.
Type:
adb sideload coral-ota-tq3a.230605.012-f32168af.zip and press enter.
Once sideloading finishes, reboot the phone by choosing Reboot system now option on the The recovery text menu.
Sideload the OTA zip file to the other slot and Root it.
Boot Recovery mode
With the device powered on and USB debugging enabled, type: adb reboot recovery
If you're unable to use adb to reboot into recovery, you can use the key combination for your device: Press and hold Volume Down button, then press and hold Power button then use the Volume Down/Up button to select Recovery option from the menu.
The device is now in recovery mode an Android logo with red exclamation mark should appear on screen.
Access the recovery menu:
Hold the Power button and press Volume up button once.
The recovery text menu will appear.
Enter sideload mode:
Select the Apply update from ADB option on the recovery text menu.
[*]Sideload the OTA zip file
Connect the phone to the PC via USB cable
On the phone: boot bootloader/fastboot mode
On the PC:
Open a command prompt in the SDK Platform-tools folder.
Type: adb sideload coral-ota-tq3a.230605.012-f32168af.zip at the prompt and press enter.
Once sideloading finishes, choose Reboot system now option on the The recovery text menu.
Flash boot/init_boot.img to root
On the phone: Boot bootloader/fastboot mode
Connect the phone to the Computer with USB cord.
On the PC:
Open a Command Prompt in the SDK Platform-tools folder.
Type: fastboot flash boot/init_boot magic_patched....img at the Prompt and press enter.
Type: fastboot reboot at the Prompt and press enter.
Disconnect the phone from the PC.
Notes:
This slot is bootable and rooted. The other slot is bootable without root.
Check that the other slot is bootable and not rooted
On the Phone: Boot bootloader/fastboot mode
Connect the phone to the PC via USB cable
On the PC:
Open a command prompt in the SDK Platform-tools folder.
Type: fastboot --set-active=other at the prompt and press enter.
Type: fastboot reboot and press enter.
Disconnect the phone from the PC.
To return to the other slot that is bootable and rooted
On the Phone: Boot bootloader/fastboot mode
Connect the phone to the PC via USB cable
On the PC:
Open a command prompt in the SDK Platform-tools folder.
Type: fastboot --set-active=other at the prompt and press enter.
Type: fastboot reboot and press enter.
Disconnect the phone from the PC.
Done!
ADB Sideload
Stock Recovery
Full OTA Images for Nexus and Pixel Devices - Updating instructions
Custom Recovery TWRP
Waiting for Android 11 (R) T.W.R.P
Flash boot.img
Flashing the boot.img removes root.
Copy/Move the boot.img file to your computer's platform-tools folder or to the folder that has fastboot.exe in it.
Boot fastboot mode
Connect the phone to the Computer
Open a Command Prompt and type the following command at the prompt:
fastboot flash boot --slot all boot.img
Reboot
Pass SafetyNet with Magisk module.
Pass Safety Net with SafetyNet Fix Magisk Module
Download File(s)
Displax's latest SafetyNet Fix, a "fork" of kdrag0n safetynet-fix.
These are the NEW Magisk Module repositories:
Androidacy Module Manager
Androidacy Module Manager - Releases
Androidacy Download Center
This is the old Magisk Module repository:
https://github.com/Fox2Code/Fox Magisk Module Manager
Install Displax's safetyNet Fix
Open Magisk
Tap Modules icon
Tap Install from storage
Navigate to the Displax's SafetyNet Fix file you downloaded.
Tap the Displax's SafetyNet Fix file.
Tap the check mark (✓ at the bottom) to start the installation.
After it installs tap the Save icon to save the log
Tap Reboot.
Settings for Magisk Canary
Open Magisk App
Tap the Setup icon.
Scroll down to App and set the Update Channel to Canary.
Scroll down to Check Updates and enable it.
Scroll down to Magisk and enable Zygisk.
Enable Denylist
Tap Configure DenyList => Tap 3 Dot Menu => Check ✓ Show system apps => Check ✓ Google Play Store, Google Pay, Google Wallet etc.
(Optional) Scroll down to Superuser and enable Enable Biometric Authentication.
Get Device Certified
Turn Airplane mode on
Open Settings
Tap Apps & notifications
Tap see all...
Tap three dot menu
Tap Show system
Scroll to Google Play Store
Tap Storage and Cache
Tap Clear storage
Note: Repeat the 3 steps above for any app that needs Device Certification i.e., Google Play Services, Google Pay, Google Wallet, etc.
reboot
Turn Airplane mode off
Check Device Certification
Open Google Play Store app
Tap Menu - Circle top right
Tap Settings
Tap About
Check Play protect certification
It may take 24 hours for Device Certification to be updated.
Note: If after completeting Get Device Certified and Check Device Certification you've waited 24 hours your Device is not Certifed or your Device is Certified and certain Google Store apps (Google Pay, NetFliks, etc.) are not working. Use the Play Integrity API Checker app or the TB Checker - Safetynet and Root app to verify you are passing Play Integrity.
Set Magisk App Update Channel/Update Magisk
Set Magisk App Update Channel
Open Magisk App > Tap Settings icon > Update Channel > Select Stable, Beta, Canary or Custom.
Update Magisk
When Magisk App notifies you of an update:
Tap install.
Select, Direct Install (Recommended)
When it finishes installing
Tap, Save Log
Log location: /storage/emulated/0/Download
Tap, Reboot
Done!
Install/Update Magisk Modules
Download File(s)
Displax's latest SafetyNet Fix, a "fork" of kdrag0n safetynet-fix.
These are the NEW Magisk Module repositories:
Androidacy Module Manager
Androidacy Module Manager - Releases
Androidacy Download Center
This is the old Magisk Module repository:
https://github.com/Fox2Code/Fox Magisk Module Manager
LSposed Releases
Shamiko Releases
Install Modules from Storage
Open Magisk
Tap the Modules icon
Tap Install from storage
Navigate to the folder with the Module you want to install.
Tap the Module to highlite it and tap Select.
After it installs, tap the Disc Icon to save the install log.
Tap Reboot
Install Modules from Androidacy Module Manager
Open Androidacy Module Manager
Tap the Modules icon
Locate the Module you want to install
Tap Install
After it installs, tap the Disc Icon to save the install log.
Tap Reboot
Update Modules
Open Androidacy Module Manager
You, will see the Modules that have Updates.
Tap the Module you want to update.
Tap install.
After it installs, tap the Disc Icon to save the install log.
Tap Reboot
~ ~ ~ Part III - OTHER ~ ~ ~
Custom ROMs
Need help with a Custom ROM?
If you are trying to install or have installed a Custom ROM, read and follow the Installation Instructions in the OP of the Custom ROM thread or Try installing it with PixelFlasher, a GUI tool for flashing / updating / rooting / managing Pixel phones..
Search the thread of the Custom ROM you are trying to install or have installed for answer(s)/solution(s) to your question(s)/problem(s): If you don't find a answer(s)/solution(s) to your question(s)/problem(s). Post your question(s)/request(s) for help in the Custom ROM thread you are trying to install or have installed.
If you are trying to install a Addon(s) {Custom Kernel, Magisk, etc.} to the Custom ROM you installed: Search the thread of the Custom ROM you installed or the thread of the Addon you want to add to your Custom ROMfor answer(s)/solution(s) to your question(s)/problem(s). If you don't find an answer(s)/solution(s) to your question(s)/problem(s). Post your question(s)/request(s) for help in the Custom ROM or Addon (Custom Kernel, Magisk, etc.) thread.
ROMs
Google Pixel 4 XL ROMs, Kernels, Recoveries, & Other
Themes, Apps, and Mods
Google Pixel 4 XL Themes, Apps, and Mods
T.W.R.P. Backup/Restore
Waiting for Android 13 T.W.R.P.

U da man Homeboy76. Really appreciate all the work you did putting this together. Thanks.

fastboot flash boot magisk_patched.img.--slot all
i have to remove the period after the patched.img. if not i get a no such file in directory

mikepopo99 said:
fastboot flash boot magisk_patched.img.--slot all
i have to remove the period after the patched.img. if not i get a no such file in directory
Click to expand...
Click to collapse
:good:

Worked like a charm for me. I did a clean a clean install. No issues. Just like flashing a monthly update.

Bootlooping
no matter what I do I keep bootlooping. I'm doing everything on the instructions list. IM trying to root android 11 on my pixel 4 xl. I just flashed the update with the flash all and wiped everything. But when i try to root it gets stuck at the google logo. i have the Magisk Canary Channel installed and patched the boot image and everything. I get the no valid slot to boot in the bootloader.

mikepopo99 said:
no matter what I do I keep bootlooping. I'm doing everything on the instructions list. IM trying to root android 11 on my pixel 4 xl. I just flashed the update with the flash all and wiped everything. But when i try to root it gets stuck at the google logo. i have the Magisk Canary Channel installed and patched the boot image and everything. I get the no valid slot to boot in the bootloader.
Click to expand...
Click to collapse
Curious
- SDK Platform-tools r 30.0.4?
- What slot did the September 2020 Factory image flash to?

I'm not sure what slot. But yes I am using the newest platform tools. How can I check. I just did the flash all script from Google and did a clean install.

mikepopo99 said:
I'm not sure what slot. But yes I am using the newest platform tools. How can I check. I just did the flash all script from Google and did a clean install.
Click to expand...
Click to collapse
Check: Boot fastboot mode (#1 in the guide) see boot slot.

Best guide on xda.
I just wonder: Can I flash Android 11 on top of Android 10 and keep my data (by removing -w) or is it recommended to clean flash Android 11?

Utini said:
Best guide on xda.
I just wonder: Can I flash Android 11 on top of Android 10 and keep my data (by removing -w) or is it recommended to clean flash Android 11?
Click to expand...
Click to collapse
I recommend clean flashing.

Utini said:
Best guide on xda.
I just wonder: Can I flash Android 11 on top of Android 10 and keep my data (by removing -w) or is it recommended to clean flash Android 11?
Click to expand...
Click to collapse
I would never try to tell anyone which way is the correct way since opinions vary. Having said that, I updated without the -w and have had zero problems thus far. However, I would take all necessary precautions as usual:
1. Update your platform-tools.
2. Remove/disable all magisk modules.
3. Remove your face unlock before starting.
4. You'll need to be on the latest canary magisk if you want to root.
5. If you patch your boot.img, make sure the finished image is 32.55 mb. I personally patch the new boot.img before even starting the update process so it's ready to go.
Again, this is how I like to update my device, and is not the be all end all method that others may like to use. Best of luck to you no matter which method you may choose to use. :good:

Badger50 said:
I would never try to tell anyone which way is the correct way since opinions vary. Having said that, I updated without the -w and have had zero problems thus far. However, I would take all necessary precautions as usual:
1. Update your platform-tools.
2. Remove/disable all magisk modules.
3. Remove your face unlock before starting.
4. You'll need to be on the latest canary magisk if you want to root.
5. If you patch your boot.img, make sure the finished image is 32.55 mb. I personally patch the new boot.img before even starting the update process so it's ready to go.
Again, this is how I like to update my device, and is not the be all end all method that others may like to use. Best of luck to you no matter which method you may choose to use. :good:
Click to expand...
Click to collapse
A second opinion is good.

Any tricks to getting Safetynet to pass? I did a clean install and build updated everything and safetynet is still failing.
Thanks all.

great guide! i almost messed up bad when i flashed first time it froze up and stalled i realised my ssd main drive ran out of space. freed up some space and retried and all worked great! (its a lot bigger than i thought when installing)

Great guide. Boot image is patched and flashed on Android 11.
I can't pass SafetyNet however. Is anyone on Android 11 and passing? Any tips?

madmaverickmatt said:
Any tricks to getting Safetynet to pass? I did a clean install and build updated everything and safetynet is still failing.
Thanks all.
Click to expand...
Click to collapse
ucantescape1992 said:
Great guide. Boot image is patched and flashed on Android 11.
I can't pass SafetyNet however. Is anyone on Android 11 and passing? Any tips?
Click to expand...
Click to collapse
Safetynet
https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228

Post deleted!

So, I've been out of the flashing game for a long minute but I had to do something about all the ads I was getting. Blockada seemed to work okay but always left something to be desired. I missed Adaway, so....
I had a hard time getting Magisk installed in Android 11 on my Pixel 4xl. I followed this well written tutorial to a tee but when I flashed magisk_patched.img to boot, then "fastboot reboot," it would kick me back to fastboot after the "G" screen and spit out the error "no valid slot to boot." Three times in a row after clean flashing the factory image too!
I did end up getting it working. What I ended up doing was instead of "fastboot flash boot magisk_patched.img --slot all" I "fastboot flash boot magisk_patched.img" and for whatever reason that seemed to work.
I did not take the OTA update if it matters. I had intended to wipe the device with a clean install of Android 11, then Magisk (just for ad blocker) from the get so, I'm guessing slot b wasn't used? I'm honestly not really sure how it works.
Even then though, I had some trouble getting the order right from flashing the factory image to being rooted, so this is also what I found.
First, unlock the bootloader of your device, then clean install Android 11 and get it set up. Download Magisk manager canary, then adb push the boot.img from your computer to your device. Use Magisk manager to patch it, then adb pull magisk_patched.img back to your computer. From there, fastboot flash boot your magisk_patched.img and you're golden. Fastboot reboot should put you back in to Android and then Magisk manager will recognize root.
I had tried several times to use a boot.img I had already patched some days earlier but it never seemed to work. It would boot okay, once I figured out not to "--slot all," but Magisk would never recognize it was rooted unless Magisk manager patched it and I flashed that particular patched file. If I tried to flash any other patched file, Magisk manager wouldn't recognize root. Even recently patched boot.img's that were flashed to the device (not the days old one I had pre-prepped) wouldn't work. Magisk manager only seemed to recognize patched boot.img's that were made by it in that particular install. If I tried to use a boot.img from any other Magisk Manager install it wouldn't recognize it. Weird? I dunno, but, I got it up and running!
Thanks Homeboy76 for making this tutorial. Without it I would have been lost. :good:

TheDiabolicaL1 said:
...I did end up getting it working. What I ended up doing was instead of "fastboot flash boot magisk_patched.img --slot all" I "fastboot flash boot magisk_patched.img" and for whatever reason that seemed to work... :good:
Click to expand...
Click to collapse
@TheDiabolicaL1
Thanks for the kind words.
Glad you got it working and, thanks for posting this information: fastboot flash boot magisk_patched.img
It provides an alternative method of flashing the magisk_patched boot.img for the members getting boot loops.
However, fastboot flash boot magisk_patched.img --slot all does work without boot loops:
C:\android-sdk_windows\image-coral-rp1a.200720.009\platform-tools_r30.0.4-windows>fastboot flash boot magisk_patched.img --slot all
Sending 'boot_a' (33336 KB) OKAY [ 0.234s]
Writing 'boot_a' OKAY [ 0.326s]
Sending 'boot_b' (33336 KB) OKAY [ 0.234s]
Writing 'boot_b' OKAY [ 0.335s]
Finished. Total time: 2.509s

[Guide] Root Pixel 3 XL Android 12

[Guide] Root Pixel 3 XL Android 12 Unlock/Lock Bootloader + Install/Flash Custom ROMs
Introduction
This Guide is for Pixel 3 XL owners that want to Instal a Custom ROM, and enjoy the benefits of rooting it. The Guide is divided into three parts: Information, Instructions, and Other.
~ ~ ~ Part I - INFORMATION ~ ~ ~
Disclaimer
I assume no responsibility for the malfunctioning/bricking of your phone.
The order of listed items i.e., Custom Kernels, Custom ROMS, etc. Does not indicate my preference for them. It is your responsibility to do the research before selecting an item.
Prerequisites
A Pixel 3 XL phone with an unlocked bootloader.1
A Computer with the latest working SDK Platform-tools 33.0.3 installed.
Important Notes:
a. Before installing SDK Platform-tools, check for older versions of fastboot on your computer: Open a Command prompt and type fastboot --version at the prompt. If a adb/fastboot is found delete the folder containing them. Also, check the path environment for paths to them and remove it.
b. Update Platform Tools, regularly, for optimal performance.
c. Need Google's USB Drivers for your Pixel Phone?
Before installing SDK Platform-tools, check for older versions of fastboot on your computer: Open a Command prompt and type fastboot --version at the prompt. If a adb/fastboot is found delete the folder containing them. Also, check the path environment for paths to them and remove it.
Update Platform Tools, regularly, for optimal performance.
Need Google's USB Drivers for your Pixel Phone?
NEW
Waiting . . .
Update(s)
Magisk Alpha - app-release_709f25f6-26101.apk 12 Apr
Magisk Beta - Magisk v26.1.apk 11 Apr
Magisk Canary - app-release_a8c4a33e-26103.apk 23 Jun
Magisk Cygisk - Click Pages 5 for installation Instructions.
Magisk Delta -
app-release
Magisk Stable - Magisk v26.1.apk 11 Apr
SafetyNet - Displax's SafetyNet Fix, v2.4.0-MOD_1.3 17Jun
SDK Platform-tools 33.0.3 Aug 2022
Custom Kernels
Note: If you want to use a Custom Kernel, please follow the Installation instructions in the OP of the Custom Kernel you want to install.[[/I][/U]a. Google Pixel 3 XL ROMs, Kernels, Recoveries, & Otherb. ElementalX Kernel Manager
My Other Guides
Pixel 7 Pro
Pixel 6
Pixel 5
Pixel 4a (5G)
Pixel 4 XL
Pixel 1 XL
Credits/Thanks/Recognitions
Those I may have, inadvertently, forgotten.
~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~
(The Instructions listed below are not steps, they are individual sets of instructions.)
Unlock Bootloader/Return Phone to Stock/Lock Bootloader
Unlock Bootloader
Notes:
This will erase all user data from the device!
Backup your data
Activate Developer Options: Tap Settings > About Phone > Tap Build Number 7 times or until you see you are a Developer. Tap back > System > Advanced > Developer Options. Enable OEM Unlock and, USB Debugging.
Boot fastboot mode
Connect the phone to the Computer with USB cord.
Open a Command Prompt on your computer and type fastboot flashing unlock and press enter.
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 and then type fastboot reboot at the Command Prompt and press enter.
When your phone reboots disconnect your usb cable.
Notes:
After unlocking your bootloader, you'll see a warning: The bootloader is unlocked and... You will see this warning until, you relock the bootloader.
Do not relock your bootloader until you have returned the device to Stock.
Return Phone to Stock
Backup your data/Internal storage
Use the Android flash tool:
select Wipe => Force Flash Partitions => Lock Bootloader.
Lock Bootloader
If your phone is not 100 percent stock do Return Phone to Stock. If you don't you may brick your phone.
This will erase all user data from the device!
Boot fastboot mode
Open a Command Prompt in the SDK Platform- tools folder, and type this at the Prompt: 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: fastboot reboot
Enable Developer Options: Settings > About phone > Tap Build number 7 times or until you see 'you are a developer'.
Tap Back > Developer options and toggle OEM Unlock off.
Install/Update Factory Image keep data or wipe data
Important Note(s):
If you haven't updated your phones Factory image in awhile. It is not necessary to flash all the images in succession. Flash the latest Factory image.
If you are uncomfortable manually flashing the factory image, Try installing it with PixelFlasher, a GUI tool for flashing / updating / rooting / managing Pixel phones..
If the previous factory image was rooted (you used Magisk to patch the boot.img of the previous factory image). Open Magisk manager and disable all Magisk modules.
If you want to Upgrade to Android 13 or update the Factory Image without wiping your phone: Do Flash Factory Image Keep Data (below).
Always verify you have the latest version of SDK Platform-Tools installed on your computer before installing the Factory Image: Pixel 3 XL - crosshatch.
If you get an error: while flashing, try one of these options:
Change the USB port to a non charging USB port.
Change the USB cord.
Change Computers.
If you phone bootloops
Press the Power button until the phone turns off.
Press the Power and Volume Down to boot the bootloader.
Open a Command Prompt in the SDK-Platform-tools folder or the folder that has adb.exe in it, and type adb wait-for-device shell magisk --remove-modules
Then type: fastboot Reboot
If you are uncomfortable manually flashing the factory image. Try PixelFlasher by badabing2003.
Please post Comments/Discussions/Questions about PixelFlasher on that thread.
Backup your data
Download the latest Factory Image: Pixel 3 XL - crosshatch to your Computer.
Go to Part II - INSTRUCTIONS => 4. Extract Files from the FactoryImage/Flash boot.img and extract the flash-all.bat file.
Flash Factory Image Keep Data
Navigate to the folder you extracted the Factory Image to and open the flash-all.bat file with a file editor i.e., Notepad app and edit the flash-all.bat file:
Change this line: fastboot -w update image-crosshatch-aa1a.999999.999.zip
to this: fastboot update image-crosshatch-tp1a.999999.999.zip
Note: This removes the -w so your Internal Storage will NOT be wiped.
After, you have edited the flash-all.bat file. Copy/Move these files to the [U[Platform-tools[/U] folder:
bootloader-crosshatch-....img
flash-all.bat
image-crosshatch-....zip
radio-crosshatch-....img
On your phone: Boot the bootloader (Power off the phone => Press the Power and Down buttons until you see Start)
Connect your phone to the computer.
Open a Command Prompt on your computer in the Platform-tools folder and type: flash-all at the Command Prompt and press enter.
The phone will reboot when flashing is complete.
Go-to Part II - INSTRUCTIONS => 5. Root/Reroot with Magisk and Pass SafetyNet, • Patching the boot.img - to root/reroot.
Flash Factory Image Wipe Data
This will wipe your phone's Internal Storage.
Open the folder you extracted the Factory Image to and Copy/Move these files to the Platform-tools folder:
bootloader-crosshatch-....img
flash-all.bat
image-crosshatch-....zip
radio-crosshatch-....img
On your phone: Boot the bootloader (Power off the phone => Press the Power and Down buttons until you see Start)
Connect your phone to the computer.
Open a Command Prompt on your computer in the Platform-tools folder and type: flash-all at the Command Prompt and press enter.
The phone will reboot when flashing is complete.
Setup phone
Enable Developer Mode and USB Debugging
Setup => About phone => Tap Build number 7 times or untill you see you are a 'Developer'.
Setup => System => Developer options => Enable Developer options => enable USB Debugging
Go-to Part II - INSTRUCTIONS => 5. Root/Reroot with Magisk and Pass SafetyNet, • Patching the boot.img - to root/reroot.
(NEW) Make Both Slots Bootable: Manually, Flash the OTA Image to Both Slots - One bootable and rooted, the other slot bootable without root.
Before you start
Backup your data
Make sure that there is no pending OTA update, by going to Settings > About phone > System updates, which should say Your system is up to date.
Download the latest Factory and OTA image for your device.
Verify the checksum of the Factory and OTA image. The last portion of the filename is the first 8 digits of its SHA-256 checksum; the full SHA-256 checksum is shown next to the download link.
Extract the boot/init_boot.image from the Factory image:
Extract the Factory Image file that you downloaded (crosshatch-a9a9a.999999.999-factory-99a9a99a.zip) into a folder.
Open the folder you extracted the Factory image to and extract the Image file (image-crosshatch-aa9a.999999.999.zip) into a folder. The stock boot/init_boot.img file should be in this folder.
Patch the boot/init_boot.img:
Open the Magisk Alpha/Beta/Canary/Delta/Stable App
The Update Channel should be set to Alpha/Beta/Canary/Delta/Stable, depending on the version you installed.
Tap Install (next to Magisk)
Tap, Select and Patch a File
Select the boot/init_boot.img file you extracted from the factory image.
Tap the ✓ (Check Mark)
Tap Let's Go
When you see done, the boot/init_boot.img has been patched (magisk_patched_xxxxxx.img), and is stored in the download folder.
Reboot
Copy/Move the magisk_patched....img file to your computer's Platform-tools folder or the folder that has fastboot.exe in it:
Boot Recovery mode
With the device powered on and USB debugging enabled, type: adb reboot recovery
If you're unable to use adb to reboot into recovery, you can use the key combination for your device: Press and hold Volume Down button, then press and hold Power button then use the Volume Down/Up button to select the Recovery option from the menu.
The device is now in recovery mode an Android logo with red exclamation mark should be on the screen.
Access the recovery menu:
Hold the Power button and press Volume button up once. The recovery text menu will appear.
Enter sideload mode:
Select the Apply update from ADB option from the recovery text menu
Run the following command: adb devices check that your device shows up with "sideload" next to its name.
Sideload the OTA zip file
Connect the phone to the PC via USB cable
On the phone: boot bootloader/fastboot mode
On the PC:
Open a command prompt in the SDK Platform-tools folder.
Type:
adb sideload crosshatch-ota-tq3a.230605.012-f32168af.zip and press enter.
Once sideloading finishes, reboot the phone by choosing Reboot system now option on the The recovery text menu.
Sideload the OTA zip file to the other slot and Root it.
Boot Recovery mode
With the device powered on and USB debugging enabled, type: adb reboot recovery
If you're unable to use adb to reboot into recovery, you can use the key combination for your device: Press and hold Volume Down button, then press and hold Power button then use the Volume Down/Up button to select Recovery option from the menu.
The device is now in recovery mode an Android logo with red exclamation mark should appear on screen.
Access the recovery menu:
Hold the Power button and press Volume up button once.
The recovery text menu will appear.
Enter sideload mode:
Select the Apply update from ADB option on the recovery text menu.
[*]Sideload the OTA zip file
Connect the phone to the PC via USB cable
On the phone: boot bootloader/fastboot mode
On the PC:
Open a command prompt in the SDK Platform-tools folder.
Type: adb sideload crosshatch-ota-tq3a.230605.012-f32168af.zip at the prompt and press enter.
Once sideloading finishes, choose Reboot system now option on the The recovery text menu.
Flash boot/init_boot.img to root
On the phone: Boot bootloader/fastboot mode
Connect the phone to the Computer with USB cord.
On the PC:
Open a Command Prompt in the SDK Platform-tools folder.
Type: fastboot flash boot/init_boot magic_patched....img at the Prompt and press enter.
Type: fastboot reboot at the Prompt and press enter.
Disconnect the phone from the PC.
Notes:
This slot is bootable and rooted. The other slot is bootable without root.
Check that the other slot is bootable and not rooted
On the Phone: Boot bootloader/fastboot mode
Connect the phone to the PC via USB cable
On the PC:
Open a command prompt in the SDK Platform-tools folder.
Type: fastboot --set-active=other at the prompt and press enter.
Type: fastboot reboot and press enter.
Disconnect the phone from the PC.
To return to the other slot that is bootable and rooted
On the Phone: Boot bootloader/fastboot mode
Connect the phone to the PC via USB cable
On the PC:
Open a command prompt in the SDK Platform-tools folder.
Type: fastboot --set-active=other at the prompt and press enter.
Type: fastboot reboot and press enter.
Disconnect the phone from the PC.
Done!
Extract Files from Factory Image/Flash boot.img
Extract Files from Factory Image
Extract flash-all.bat and boot.img file
Download the latest Factory image to your phone.
Extract the Factory Image file (crosshatch-r2d1a.999999.999-factory-99a9a99a.zip) to a folder. The, stock, flash-all.bat file should be in this folder.
Open the folder you extracted the Factory image to and, extract the Image file (image-crosshatch-aa9a.999999.999.zip) into the folder. The, stock, boot.img file should be in this folder.
Flash boot.img
Flashing the boot.img removes root.
Open the folder you extracted the 'image...zip' file to and copy the boot.img file to your computer's platform-tools folder or to the folder that has fastboot.exe in it.
Boot fastboot mode
Connect the phone to the Computer
Open a Command Prompt and type the following command at the prompt:
fastboot flash boot --slot all boot.img
Reboot
Pass SafetyNet with Magisk moduke.
Pass Safety Net with SafetyNet Fix with Magisk module
Download File(s)
Displax's latest SafetyNet Fix, a "fork" of kdrag0n safetynet-fix.
These are the NEW Magisk Module repositories:
Androidacy Module Manager
Androidacy Module Manager - Releases
Androidacy Download Center
This is the old Magisk Module repository:
https://github.com/Fox2Code/Fox Magisk Module Manager
Install Displax's safetyNet Fix
Open Magisk
Tap Modules icon
Tap Install from storage
Navigate to the Displax's SafetyNet Fix file you downloaded.
Tap the Displax's SafetyNet Fix file.
Tap the check mark (✓ at the bottom) to start the installation.
After it installs tap the Save icon to save the log
Tap Reboot.
Settings for Magisk Canary
Open Magisk App
Tap the Setup icon.
Scroll down to App and set the Update Channel to Canary.
Scroll down to Check Updates and enable it.
Scroll down to Magisk and enable Zygisk.
Enable Denylist
Tap Configure DenyList => Tap 3 Dot Menu => Check ✓ Show system apps => Check ✓ Google Play Store, Google Pay, Google Wallet etc.
(Optional) Scroll down to Superuser and enable Enable Biometric Authentication.
Get Device Certified
Turn Airplane mode on
Open Settings
Tap Apps & notifications
Tap see all...
Tap three dot menu
Tap Show system
Scroll to Google Play Store
Tap Storage and Cache
Tap Clear storage
Note: Repeat the 3 steps above for any app that needs Device Certification i.e., Google Play Services, Google Pay, Google Wallet, etc.
reboot
Turn Airplane mode off
Check Device Certification
Open Google Play Store app
Tap Menu - Circle top right
Tap Settings
Tap About
Check Play protect certification
It may take 24 hours for Device Certification to be updated.
Note: If after completeting Get Device Certified and Check Device Certification you've waited 24 hours your Device is not Certifed or your Device is Certified and certain Google Store apps (Google Pay, NetFliks, etc.) are not working. Use the Play Integrity API Checker app or the TB Checker - Safetynet and Root app to verify you are passing Play Integrity.
Set Magisk App Update Channel/Update Magisk
Set Magisk App Update Channel
Open Magisk App > Tap Settings icon > Update Channel > Select Stable, Beta, Canary or Custom.
Update Magisk
When Magisk App notifies you of an update:
Tap install.
Select, Direct Install (Recommended)
When it finishes installing
Tap, Save Log
Log location: /storage/emulated/0/Download
Tap, Reboot
Done!
Install/Update Magisk Modules
Download File(s)
Displax's latest SafetyNet Fix, a "fork" of kdrag0n safetynet-fix.
These are the NEW Magisk Module repositories:
Androidacy Module Manager
Androidacy Module Manager - Releases
Androidacy Download Center
This is the old Magisk Module repository:
https://github.com/Fox2Code/Fox Magisk Module Manager
LSposed Releases
Shamiko Releases
Install Modules from Storage
Open Magisk
Tap the Modules icon
Tap Install from storage
Navigate to the folder with the Module you want to install.
Tap the Module to highlite it and tap Select.
After it installs, tap the Disc Icon to save the install log.
Tap Reboot
Install Modules from Androidacy Module Manager
Open Androidacy Module Manager
Tap the Modules icon
Locate the Module you want to install
Tap Install
After it installs, tap the Disc Icon to save the install log.
Tap Reboot
Update Modules
Open Androidacy Module Manager
You, will see the Modules that have Updates.
Tap the Module you want to update.
Tap install.
After it installs, tap the Disc Icon to save the install log.
Tap Reboot
Open a Command Prompt/Boot Fastboot Mode/Boot Recovery
Open a Command Prompt on Computer
Open File Explorer, click the platform-tools folder ==> click the folder icon (left side of address bar) to highlight it type cmd and press enter.
Open a Powershell Command Prompt on Computer: Open File Explorer, click the platform-tools folder ==> click the folder icon (left side of address bar) to highlight it type powershell and press enter.
Notes:
Enable USB Debugging, on your phone: Settings ==> System ==> Advanced ==> Developer options ==> Scroll down to USB debugging and enable it.
When using the Powershell Command Prompt Commands must be preceeded with ./: i.e, ./fastboot devices
If you do not want to open a Command Prompt every time you want to use the fastboot command, add the path to the Platform-tools folder to Windows environment variables.
Boot fastboot mode (bootloader):
Power off phone, press and hold the power and volume down buttons until you see Start.
Boot Recovery
Power off phone, press and hold the power and volume down buttons until you see Start. Use volume up/down button until you see Recovery mode. Press power button.
Test fastboot
Enable Developer Options - Tap Settings > About phone > Build number 7 times or until you should see 'you are a Developer'.
Enable USB Debugging - Tap Settings > System > Advanced > Developer options >
Enable USB Debugging.
Open a Command Prompt on your computer in the Platform-tools folder.
Boot fastboot mode on your phone
Connect the phone to the Computer.
At the prompt type: fastboot devices to verify communication with phone. It should return your phone's serial number.
ADB Sideload
Stock Recovery
Full OTA Images for Nexus and Pixel Devices - Updating instructions
Custom Recovery TWRP
Waiting for Android 11 (R) T.W.R.P
~ ~ ~ Part III - OTHER ~ ~ ~
Custom ROMs
Need help with a Custom ROM?
If you are trying to install or have installed a Custom ROM, read and follow the Installation Instructions in the OP of the Custom ROM thread or try installing it with PixelFlasher, a GUI tool for flashing / updating / rooting / managing Pixel phones..
Search the thread of the Custom ROM you are trying to install or have installed for answer(s)/solution(s) to your question(s)/problem(s): If you don't find a answer(s)/solution(s) to your question(s)/problem(s). Post your question(s)/request(s) for help in the Custom ROM thread you are trying to install or have installed.
If you are trying to install a Addon(s) {Custom Kernel, Magisk, etc.} to the Custom ROM you installed: Search the thread of the Custom ROM you installed or the thread of the Addon you want to add to your Custom ROMfor answer(s)/solution(s) to your question(s)/problem(s). If you don't find an answer(s)/solution(s) to your question(s)/problem(s). Post your question(s)/request(s) for help in the Custom ROM or Addon (Custom Kernel, Magisk, etc.) thread.
ROMs
Google Pixel 3 XL ROMs, Kernels, Recoveries, & Other
Other Custom ROMs
[ROM] [Android 13] [blueline/crosshatch] ArrowOS 13.0 | UNOFFICIAL | BETA by ReallySnow
Themes, Apps, and Mods
Google Pixel 3 XL Themes, Apps, and Mods
T.W.R.P.
Android 12 - 370_12.0... 10Oct

Attempted the update last night, when flashing Magisk Canary Patched boot.img, the touchscreen is non-responsive on boot.
Flashing the stock boot.img and the touchscreen works.
Tried flashing the full image (no -w) and OTA with same result both times. Tried switching between active slots as well, no dice.
Any ideas?

JONBOY345 said:
Attempted the update last night, when flashing Magisk Canary Patched boot.img, the touchscreen is non-responsive on boot.
Flashing the stock boot.img and the touchscreen works.
Tried flashing the full image (no -w) and OTA with same result both times. Tried switching between active slots as well, no dice.
Any ideas?
Click to expand...
Click to collapse
Are you using:
- Magisk 20-4.zip (Stable)?
- Magisk Manager Canary 424 to patch September 2020 boot.img?

Homeboy76 said:
Are you using:
- Magisk 20-4.zip (Stable)?
- Magisk Manager Canary 424 to patch September 2020 boot.img?
Click to expand...
Click to collapse
Yes. Using Magisk 20-4.zip stable, but I've not used that zip in anyway...
Magisk Manager app is Canary from: https://github.com/topjohnwu/magisk_files/find/canary?q= and using it to patch the boot.img
Also updated platform tools to latesst.

JONBOY345 said:
Yes. Using Magisk 20-4.zip stable, but I've not used that zip in anyway...
Magisk Manager app is Canary from: https://github.com/topjohnwu/magisk_files/find/canary?q= and using it to patch the boot.img
Also updated platform tools to latesst.
Click to expand...
Click to collapse
Ok. I guess it's the Gremlins are preventing it from working.
Seriously, I don't know why it is not working.
Maybe @sliding_billy has some advice.

Homeboy76 said:
Ok. I guess it's the Gremlins preventing it from working.
Seriously, I don't know why it is not working.
Maybe @sliding_billy has some advice.
Click to expand...
Click to collapse
For giggles, can anyone share a patched boot.img?

JONBOY345 said:
For giggles, can anyone share a patched boot.img?
Click to expand...
Click to collapse
Sure, Let me know if this works for you!
Edit: posted an actual patched img. Grabbed the wrong file at first
https://drive.google.com/file/d/13VhMOr3XqFsIQUmZo3sG3LRATlV-hju8/view?usp=sharing

laxattack said:
Sure, Let me know if this works for you!
https://drive.google.com/file/d/1dcXyMv0sttfyGno496Tbo6MFuUIuii2w/view?usp=sharing
Click to expand...
Click to collapse
Hmm. That one didn't work. It booted, touchscreen worked, but no root.
For giggles I reran by steps again this morning, and now the new Magisk patched image works.
Here's a link: https://drive.google.com/file/d/127G2MZ_Jq8cPPKs50rtTiOijSkk7DbtU/view?usp=sharing
I noticed that your patched image is 67.1MB, while the one that Magisk created/patched on my phone (and I uploaded just above), is only 32.8MB...
Thanks for your help!

JONBOY345 said:
Hmm. That one didn't work. It booted, touchscreen worked, but no root.
For giggles I reran by steps again this morning, and now the new Magisk patched image works.
Here's a link: https://drive.google.com/file/d/127G2MZ_Jq8cPPKs50rtTiOijSkk7DbtU/view?usp=sharing
I noticed that your patched image is 67.1MB, while the one that Magisk created/patched on my phone (and I uploaded just above), is only 32.8MB...
Thanks for your help!
Click to expand...
Click to collapse
I uploaded the wrong one at first and edited my original post, lol sorry about that

Is anyone that is on latest android 11 able to use Google Pay? Mine won't work and CTS Profile fails safetynet check. Bootloader is unlocked but not rooted.

Homeboy76 said:
Ok. I guess it's the Gremlins are preventing it from working.
Seriously, I don't know why it is not working.
Maybe @sliding_billy has some advice.
Click to expand...
Click to collapse
JONBOY345 said:
Hmm. That one didn't work. It booted, touchscreen worked, but no root.
For giggles I reran by steps again this morning, and now the new Magisk patched image works.
Here's a link: https://drive.google.com/file/d/127G2MZ_Jq8cPPKs50rtTiOijSkk7DbtU/view?usp=sharing
I noticed that your patched image is 67.1MB, while the one that Magisk created/patched on my phone (and I uploaded just above), is only 32.8MB...
Thanks for your help!
Click to expand...
Click to collapse
Sorry I missed all this. I just got back in front of a computer and got no emails of the @ mention. Is everything working now? My two thoughts for what it's worth would have been to sideload the OTA twice so that it hit both slots and to be sure to update the Magisk path to canary after installing the .apk and then to be sure to update magisk after changing the path.

berndt_toast said:
Is anyone that is on latest android 11 able to use Google Pay? Mine won't work and CTS Profile fails safetynet check. Bootloader is unlocked but not rooted.
Click to expand...
Click to collapse
are you using a custom kernel to hide the unlocked bootloader?

laxattack said:
are you using a custom kernel to hide the unlocked bootloader?
Click to expand...
Click to collapse
Nope, I was on stock. I realized that I wasn't using any rooted apps anymore, so the need to have my bootloader unlocked was null and void. I re-locked my bootloader and now google pay works like a charm.

I'll add my observation here:
OTA update via magisk OTA update method works, but for some reason I kept having frozen screen after a few minutes usage. Rebooted at least 4-5 times and it worked.
I was using Taichi and its Magisk module doesn't work. Reflashing the module causes bootloop.
So I flashed again factory image without "-w", booted fine. But installing root via magisk_patched.img from R boot.img causes bootloop.
Don't understand why.
EDIT: Is there a way to clean up magisk modules now that I am on stuck on bootloader whenever I flash magisk_patched.img?

ultimatepichu said:
I'll add my observation here:
OTA update via magisk OTA update method works, but for some reason I kept having frozen screen after a few minutes usage. Rebooted at least 4-5 times and it worked.
I was using Taichi and its Magisk module doesn't work. Reflashing the module causes bootloop.
So I flashed again factory image without "-w", booted fine. But installing root via magisk_patched.img from R boot.img causes bootloop.
Don't understand why.
EDIT: Is there a way to clean up magisk modules now that I am on stuck on bootloader whenever I flash magisk_patched.img?
Click to expand...
Click to collapse
Tulsadiver's [Guide] Magisk Modules Disabler for Modules gone wrong by tulsadiver would fix it. I don't know if he has had the time to update it for Android 11 (R).
Maybe Support Safe Mode detection would help.

Do you have to use Magisk canary with Android 11? I just updated to 11, lost root, and want to add it back.
Thanks,
Rick

C5Longhorn said:
Do you have to use Magisk canary with Android 11? I just updated to 11, lost root, and want to add it back.
Thanks,
Rick
Click to expand...
Click to collapse
Magisk Canary Manager 20424
Yes!

I upgraded from like June 2020 build to 11 via OTA, do I just have to sideload patched boot.img as I always have been for previous monthly Android 10 updates? The only difference is using the canary version of Magisk (i'm on stable channel at the moment)

walle4893 said:
I upgraded from like June 2020 build to 11 via OTA, do I just have to sideload patched boot.img as I always have been for previous monthly Android 10 updates? The only difference is using the canary version of Magisk (i'm on stable channel at the moment)
Click to expand...
Click to collapse
pretty much

Android 11, Magisk & SafetyNet
berndt_toast said:
Is anyone that is on latest android 11 able to use Google Pay? Mine won't work and CTS Profile fails safetynet check. Bootloader is unlocked but not rooted.
Click to expand...
Click to collapse
I lost root when I upgraded to Android 11 Beta and I forgot to uninstall Magisk beforehand. I left it that way with the Magisk Manager app still installed because I didn't want to do a full wipe. I didn't have any SafetyNet problem until I took the latest rp1a.200720.009 OTA and got a warning message on the first boot. I decided to try installing the latest Canary Magisk again by sideloading the patched boot.img and now I have root again and can pass the SafetyNet check.

Database Info

welcome