Database Users

[GUIDE] Unlock/Root/Flash for Nexus 5X

[SIZE=+3]Heisenberg's How-To Guide For Beginners[/SIZE]
[SIZE=+2]Nexus 5X[/SIZE]
{
"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"
}
[SIZE=+1]Intro[/SIZE]
This thread will serve as a location for basic how-to guides for the Nexus 5X. I'm going to start off with a couple of the more obvious ones and go from there. If anyone has any suggestions for additions please feel free to let me know.
If you're unsure about something please read the FAQ section in post #2 before creating a post to ask a question.
[size=+1]Prerequisites[/size]:
You'll need a working adb/fastboot environment on your PC to get through some of these guides. Below are two options for install.
Please do not install adb/fastboot via any means other than the Android SDK, using other tools (like Minimal adb & fastboot) can lead to an outdated setup and various problems with flashing. You've been warned, other tools will not be supported in this thread.
Option A
Google hosts ADB/Fastboot (platform-tools) for Windows, OSX, and Linux. This is a minimal download, in contrast to Option 2. These links and file sizes may be updated periodically by Google. If using Windows, download the Google USB Driver and follow the driver install instructions. Once you have downloaded the platform-tools zip, extract the file then transfer the platform-tools folder to your desktop. The platform-tools folder contains adb, fastboot, and several other files. Note that clicking any link for platform-tools will immediately start a download.
*Windows: platform-tools. Google USB Driver install.
*OSX: platform-tools. For additional details on how to use OSX and adb/fastboot commands, see post #3.
*Linux: platform-tools.
See Option B below for old method to install adb/fastboot:
Option B
Go here to download the Android SDK, which will give you most updated version of adb and fastboot. Scroll to the bottom of the page and find Other Download Options>SDK Tools Only, and grab the right version for your OS. While it's downloading create a folder in C:\ called SDK (C:\SDK). Once you've downloaded the zip you can extract it into your C:\SDK folder. Navigate to C:\SDK\android-sdk-windows and open SDK Manager.exe. In SDK Manager you need to install the following packages:
Tools> Android SDK Tools, Android SDK Platform-tools
Extras> Android Support Repository, Google USB Driver
Once you have installed those, inside C:\SDK you should see some new folders, one of them will be called platform-tools, within that folder you should see fastboot.exe and adb.exe. I'll refer to this as your fastboot folder/directory or working folder/directory during this guide.
For Option A and B, make sure adb is correctly installed. Open a command prompt from within your fastboot folder (hold shift + right click, select open command prompt here) and issue this command:
Code:
adb version
If it returns a version number for Android Debug Bridge then you're good to go.
You can test adb by connecting your device to your PC while booted into Android (making sure that adb/usb debugging is enabled in Settings>Developer Options) with the screen unlocked and issuing this command:
Code:
adb devices
It should return your device serial number, if so, adb is working.
You can test fastboot by connecting your device to your PC while booted into the bootloader (power + volume down) and issuing this command:
Code:
fastboot devices
It should return your device serial number, if so, fastboot is working.
By attempting any of the processes listed this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches on fire, or turns into a hipster and claims to have been modified before it was cool.
[SIZE=+1]Quick Tips[/SIZE]
How to boot into the bootloader:
Power off your device. Once it's powered off hold power + volume down and the phone will boot into the bootloader. You can also use the following adb command:
Code:
adb reboot bootloader
You can also use an app called Quick Boot to boot into the bootloader directly from Android (root required).
How to boot into recovery:
Boot into the bootloader (see above), use the volume keys to scroll through the options and use the power button to select the recovery mode option. You can also use the following adb command:
Code:
adb reboot recovery
You can also use an app called Quick Boot to boot into the recovery directly from Android (root required).
[SIZE=+1]Index[/SIZE]
How To Unlock Your Bootloader
How To Install A Custom Recovery On Your Device
How To Decrypt Your Data Partition
How To Make A Nandroid Backup With TWRP Recovery
How To Make An EFS Backup With TWRP Recovery
How To Root
How To Install A ROM with TWRP Recovery
How To Install A Custom Kernel With TWRP Recovery
How To Update To A New Build Of The Stock ROM
How To Flash The Factory Images (Return To Stock)
How To Flash The Factory Images (Return To Stock But Leaving Internal Storage Intact)
FAQ can be found in post #2!
[SIZE=+1]1. How To Unlock Your Bootloader[/SIZE]
Go into Settings/About Phone, scroll down and click on ?build number? continuously until you see a toast notification telling you that you've enabled Developer Options. Go back to your Settings menu and enter Developer Options, scroll down and click on the ?Enable OEM Unlock? checkbox, also make sure you enable USB Debugging while you're in the Developer Options menu.
Power off your phone then boot into the bootloader (power + volume down).
Connect your phone to your PC via usb cable.
Open a command prompt from within your fastboot folder (navigate to where you have fastboot.exe located on your PC, shift + right click anywhere within that folder, select open command prompt here).
Check your fastboot connection by issuing this command:
Code:
fastboot devices
It should return your device serial number, if not you need to make sure your drivers are installed correctly.​
Once you've confirmed your fastboot connection issue this command:
Code:
fastboot oem unlock
This will erase all user data from the device!
You should now see a screen on your phone asking you to confirm this action, use the volume keys to scroll and the power key to confirm if you're sure you want to go ahead.
Allow the process to complete and then issue this command:
Code:
fastboot reboot
Allow everything to go ahead and once finished you can disconnect your usb cable.
Important: do not relock your bootloader unless your phone is fully stock. You must flash the factory images first in order to remove root and custom recovery (if you have them), if this precaution isn't taken you may end up with a brick. Please see section 10 of this guide for full instructions on how to return to stock.
[SIZE=+1]2. How To Install A Custom Recovery On Your Device[/SIZE]
Prerequisites: unlocked bootloader (section 1). Please read FAQ #7 if using TWRP 3.0.2-1 or 3.0.2-2.
Download TWRP Recovery onto your PC.
Make sure you check the md5 to verify its integrity (where possible).
Place the file in your fastboot folder (this is where fastboot.exe is located on your PC).
Power off your phone then boot into the bootloader (power + volume down).
Open a command prompt from within your fastboot folder (navigate to where you have fastboot.exe located on your PC, shift + right click anywhere within that folder, select open command prompt here), enter this command:
Code:
fastboot flash recovery filename.img
(The recovery filename in the command will change depending on which recovery you're flashing)
Use the volume keys to scroll and power key to select the Reboot Bootloader option. Once the phone has booted back into the bootloader, use the volume keys to scroll and the power key to boot into your newly flashed recovery. It's now safe to disconnect your usb cable. If using Nougat 7.0 or newer, you must now boot directly into TWRP and flash SuperSU (or your preferred root alternative) so that TWRP will persist between reboots.
When TWRP boots up you'll be asked whether you want to allow system modifications or to keep it read-only, choose to allow system modifications, there's no benefit to keeping it read-only.
Do not flash the version of SuperSU that TWRP offers to flash for you in order to give you root, it is not compatible and will cause problems. When you attempt to reboot out of TWRP it will tell you that it's detecting that you don't have root and it will offer to root for you, skip past this.
Some users need a custom recovery for a temporary period, so they live boot the recovery. In this scenario, the custom recovery replaces the stock recovery until a reboot is performed. Place the file in your fastboot folder then enter this command:
Code:
fastboot boot filename.img
(The recovery filename in the command will change depending on which recovery you're flashing)
[SIZE=+1]3. How To Decrypt Your Data Partition[/SIZE]
This is no longer necessary as long as you use TWRP 2.8.7.1 or newer
Prerequisites: unlocked bootloader (section 1).
TWRP recovery cannot decrypt your data partition at this stage. In order for TWRP to be able to read/write on your data partition (to root or create a nandroid backup) you will need to format it, a format will remove encryption.
Boot into the bootloader and connect your phone to your PC via usb cable.
Open a command prompt from within your fastboot folder (navigate to where you have fastboot.exe located on your PC, shift + right click anywhere within that folder, select open command prompt here), enter this command:
Code:
fastboot format userdata
Please note: this will erase all user data from the device!
Once the process has completed you can either reboot normally:
Code:
fastboot reboot
Or you can reboot back to the bootloader in order to undertake another task:
Code:
fastboot reboot-bootloader
[SIZE=+1]4. How To Make A Nandroid Backup With TWRP Recovery[/SIZE]
Prerequisites: unlocked bootloader (section 1), TWRP recovery (section 2).
A nandroid backup is a very important thing to have before installing any custom software on your device. It's basically a backup of your stock system that you can fall back on if anything goes wrong or if you just want your stock ROM back. You can also use the backup tool to create a backup of your favourite ROM set up exactly the way you like it. The backup you create can be easily restored using the restore tool in TWRP recovery.
Boot TWRP recovery, select the backup option from the TWRP home screen, check the system/data/boot boxes, and swipe to backup. The process will take a few minutes.
[SIZE=+1]5. How To Make An EFS Backup With TWRP Recovery[/SIZE]
An EFS backup is very important to have, if your EFS partition becomes corrupt you will have no IMEI, and therefore will not be able to use the phone as a phone. Making an EFS backup is insurance against this catastrophic event. Without a backup, restoring your EFS can be extremely difficult or impossible. The backup you create can be easily restored using the restore tool in TWRP recovery.
Please read FAQ #7 if using TWRP 3.0.2-1 or 3.0.2-2. Boot into TWRP and select the backup option from the TWRP home screen, make sure only the EFS box is selected, and swipe to backup. The process will take a few seconds. Keep a copy of the backup on your phone and also keep another copy somewhere safe.
[SIZE=+1]6. How To Root[/SIZE]
Prerequisites: unlocked bootloader (section 1), TWRP recovery (section 2).
Download the latest root method of your choosing to your phone:
Magisk
SuperSU Stable
SuperSU Service Release (SuperSU beta channel)
Or to root Android Nougat 7.0 visit this thread: Use SuperSU 2.78 or newer.
[WIP] Android N Preview
Boot into TWRP recovery and enter the install menu.
Navigate to where you have SuperSU stored on your internal storage and select it.
Swipe to install.
Once you've installed SuperSU you'll have an option to wipe cache/dalvik and an option to reboot system. Wipe the cache/dalvik, hit the back button, and hit the reboot system button. That's it.
Do not flash the version of SuperSU that TWRP offers to flash for you in order to give you root, it is not compatible and will cause problems. When you attempt to reboot out of TWRP it will tell you that it's detecting that you don't have root and it will offer to root for you, skip past this. You do have root, ignore this every time it comes up.
[SIZE=+1]7. How To Install A ROM with TWRP Recovery[/SIZE]
Prerequisites: unlocked bootloader (section 1), TWRP recovery (section 2), vendor.img (section 9).
Installing a ROM is a straight forward and easy process. Before you install anything you should make a nandroid backup (instructions above). Next, install the vendor.img that matches the Google security OTA that the ROM you want to install is based on. Find the vendor.img inside the factory images provided by Google then flash this file with fastboot (section 9).
Download a ROM and appropriate Gapps package and place on your device.
Boot into your custom recovery.
Select the wipe option from the TWRP home screen.
Perform a Factory Reset.
Select advanced wipe.
Check the system, data, cache, and dalvik cache options.
Swipe to wipe.
Install the ROM.
Select the install option from the TWRP home screen.
Navigate to where you have the ROM zip stored on your sd card and select it.
Swipe to install.
Most ROMs will run an installer script at this point but some ROMs have what is called an Aroma Installer which allow you to choose some install options before the script runs.​
You will also need to install the appropriate gapps package directly after installing the ROM.
Once you've installed all necessary zips you'll have an option to wipe cache/dalvik and an option to reboot system. Wipe the cache/dalvik, hit the back button, and hit the reboot system button.
[SIZE=+1]8. How To Install A Custom Kernel With TWRP Recovery[/SIZE]
Prerequisites: unlocked bootloader (section 1), TWRP recovery (section 2).
A custom kernel can open up a new level of control over your device, such as overclocking/underclocking, undervolting, changing governors, changing I/O schedulers, adjusting colour calibrations, adjusting sound calibrations, and many other options.
Download a kernel that is compatible with your current ROM.
Check the md5 to verify its integrity.
Enter TWRP recovery.
Select the install option from the TWRP home screen.
Navigate to the kernel and select it.
Swipe to install.
You'll have an option to wipe cache/dalvik and an option to reboot system. Wipe the cache/dalvik, hit the back button, and hit the reboot system button.
Once your phone has booted up you can use a kernel tuning app to change governors, I/O scheduler, clock speed, and other options. Some of the popular kernel apps are Kernel Auditor, EX Kernel Manager, Trickster Mod, No Frills, Kernel Tuner, and many more.
[SIZE=+1]9. How To Update To A New Build Of The Stock ROM[/SIZE]
Prerequisites: unlocked bootloader (section 1).
This method does not wipe your data, so you will keep your apps and settings. You should have no problems, however, if you experience problems you may need to perform a factory reset and flash again. Make a backup first and transfer it to your PC.
Download the latest build via the appropriate factory images for your model (Nexus 5X/Bullhead) here.
Note: Android 7.1.2 and newer factory images do not contain cache.img. Do not wipe the cache.img for this process when using or moving to Android 7.1.2 or newer. If you have wiped cache.img, download the most recent Android 7.1.1 factory image and flash the cache.img from that zip archive.
Unzip the bullhead-xxxxxx-factory-xxxxxxxx (x's replace variables) into a directory on your PC (for this guide we'll use C:\bullhead\).
Once unzipped you should have a folder named bullhead-xxxxxx (x's replace variables). Open it and move the following files to a new directory named C:\bullhead\images\:
bootloader-bullhead-bullhead-xx.xx.img
radio-bullhead-bullhead-xx.xx.img
(Please note that radio and bootloader naming changes from build to build so the filenames and below commands will change with them)
Within C:\bullhead\bullhead-xxxxxx\ you'll see another zip archive named image-bullhead-xxxxxx, unzip the contents of that zip into the C:\bullhead\images\ folder we created before. Now within C:\bullhead\images\ you should have the following files:
android-info.txt
boot.img
bootloader-bullhead-bullhead-xx.xx.img
cache.img
radio-bullhead-bullhead-xx.xx.img
recovery.img
system.img
userdata.img
vendor.img
Boot into the bootloader and connect your phone to your PC via usb cable.
Open a command prompt from within your fastboot folder (navigate to where you have fastboot.exe located on your PC, shift + right click anywhere within that folder, select open command prompt here), enter these commands to flash:
Code:
fastboot flash bootloader C:\bullhead\images\bootloader-bullhead-bullhead-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\bullhead\images\radio-bullhead-bullhead-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\bullhead\images\boot.img
fastboot erase cache
fastboot flash cache C:\bullhead\images\cache.img
fastboot flash recovery C:\bullhead\images\recovery.img
fastboot flash system C:\bullhead\images\system.img
fastboot flash vendor C:\bullhead\images\vendor.img
You can skip flashing the recovery if you wish, but even if you do the stock recovery may be patched on the first boot anyway. So you'll need to flash TWRP and SuperSU again if you need/want those, as well as any other system modifications you may have had.
You'll have to flash SuperSU again now, plus add any mods that you previously had.
[SIZE=+1]10. How To Flash The Factory Images (And Return To Stock)[/SIZE]
Prerequisites: unlocked bootloader (section 1).
This section will explain how to return the phone to be like it was when it came out of the box. This will wipe everything from the phone. If you wish to flash the factory images without wiping your personal data from the internal storage please move on to the next section.
Note: Android 7.1.2 and newer factory images do not contain cache.img. Do not wipe the cache.img for this process when using or moving to Android 7.1.2 or newer. If you have wiped cache.img, download the most recent Android 7.1.1 factory image and flash the cache.img from that zip archive.
Go to Settings/Backup & Reset and perform a factory data reset. This will remove all of your user data from the device (apps, settings, photos, music, etc).
Download the appropriate factory images for your model here.
Unzip the bullhead-xxxxxx-factory-xxxxxxxx (x's replace variables) into a directory on your PC (for this guide we'll use C:\bullhead\).
Once unzipped you should have a folder named bullhead-xxxxxx (x's replace variables). Open it and move the following files to a new directory named C:\bullhead\images\:
bootloader-bullhead-bullhead-xx.xx.img
radio-bullhead-bullhead-xx.xx.img
(Please note that radio and bootloader naming changes from build to build so the filenames and below commands will change with them)
Within C:\bullhead\bullhead-xxxxxx\ you'll see another zip archive named image-bullhead-xxxxxx, unzip the contents of that zip into the C:\bullhead\images\ folder we created before. Now within C:\bullhead\images\ you should have the following files:
android-info.txt
boot.img
bootloader-bullhead-bullhead-xx.xx.img
cache.img
radio-bullhead-bullhead-xx.xx.img
recovery.img
system.img
userdata.img
vendor.img
Boot into the bootloader and connect your phone to your PC via usb cable.
Open a command prompt from within your fastboot folder (navigate to where you have fastboot.exe located on your PC, shift + right click anywhere within that folder, select open command prompt here), enter these commands to flash:
Code:
fastboot flash bootloader C:\bullhead\images\bootloader-bullhead-bullhead-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\bullhead\images\radio-bullhead-bullhead-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\bullhead\images\boot.img
fastboot erase cache
fastboot flash cache C:\bullhead\images\cache.img
fastboot flash recovery C:\bullhead\images\recovery.img
fastboot flash system C:\bullhead\images\system.img
fastboot flash vendor C:\bullhead\images\vendor.img
If you wish to you can also relock the bootloader with this command:
Code:
fastboot oem lock
(This command will wipe all user data from the device)
Important: do not lock the bootloader unless you have first flashed the stock images. Locking the bootloader while you have a custom recovery installed can result in a brick. Please also note that the locking procedure will wipe all data on an encrypted device.
Once all commands/flashes are complete you can reboot the device:
Code:
fastboot reboot
[SIZE=+1]11. How To Flash The Factory Images (Return To Stock But Leaving Internal Storage Intact)[/SIZE]
Prerequisites: unlocked bootloader (section 1), TWRP recovery (section 2). Note: Android 7.1.2 and newer factory images do not contain cache.img. Do not wipe the cache.img for this process when using or moving to Android 7.1.2 or newer. If you have wiped cache.img, download the most recent Android 7.1.1 factory image and flash the cache.img from that zip archive.
This section will explain how to return the phone to be like it was when it came out of the box, except it will not wipe any of your personal data (photos, music, etc) from the internal storage.
Download the appropriate factory images for your model here.
Unzip the bullhead-xxxxxx-factory-xxxxxxxx (x's replace variables) into a directory on your PC (for this guide we'll use C:\bullhead\).
Once unzipped you should have a folder named bullhead-xxxxxx (x's replace variables). Open it and move the following files to a new directory named C:\bullhead\images\:
bootloader-bullhead-bullhead-xx.xx.img
radio-bullhead-bullhead-xx.xx.img
(Please note that radio and bootloader naming changes from build to build so the filenames and below commands will change with them)
Within C:\bullhead\bullhead-xxxxxx\ you'll see another zip archive named image-bullhead-xxxxxx, unzip the contents of that zip into the C:\bullhead\images\ folder we created before. Now within C:\bullhead\images\ you should have the following files:
android-info.txt
boot.img
bootloader-bullhead-bullhead-xx.xx.img
cache.img
radio-bullhead-bullhead-xx.xx.img
recovery.img
system.img
userdata.img
vendor.img
Boot into TWRP recovery and enter the wipe menu, select advanced wipe, check only the data box and swipe to wipe.
Go to the TWRP main menu and enter the reboot menu, select bootloader. The phone will now boot into the bootloader, once it has you can connect your phone to your PC via usb cable.
Open a command prompt from within your fastboot folder (navigate to where you have fastboot.exe located on your PC, shift + right click anywhere within that folder, select open command prompt here), enter these commands to flash:
Code:
fastboot flash bootloader C:\bullhead\images\bootloader-bullhead-bullhead-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\bullhead\images\radio-bullhead-bullhead-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\bullhead\images\boot.img
fastboot erase cache
fastboot flash cache C:\bullhead\images\cache.img
fastboot flash recovery C:\bullhead\images\recovery.img
fastboot flash system C:\bullhead\images\system.img
fastboot flash vendor C:\bullhead\images\vendor.img
Once all commands/flashes are complete you can reboot the device:
Code:
fastboot reboot
FAQ can be found in post #2!
Donate To Me

[size=+1]Frequently Asked Questions[/size]
1. How do I boot into the bootloader?
Power off your device. Once it's powered off hold power + volume down and the phone will boot into the bootloader. You can also use the following adb command:
Code:
adb reboot bootloader
You can also use an app called Quick Boot to boot into the bootloader directly from Android (root required).
2. How do I boot into recovery?
Boot into the bootloader (see above), use the volume keys to scroll through the options and use the power button to select the recovery mode option. You can also use the following adb command:
Code:
adb reboot recovery
You can also use an app called Quick Boot to boot into the recovery directly from Android (root required).
3. When issuing the fastboot flashing unlock command it doesn't work, I only get a list of possible commands. What's going on?
This is usually due to having an outdated adb/fastboot setup. If you installed adb/fastboot by any means other than via the Android SDK this is probably the cause. Visit the prerequisites section in the beginning of this guide to properly install adb/fastboot and ensure that it's up to date.
4. How do I take an OTA or update if I have root or other system modifications on the stock ROM?
You can't take an OTA update while you have root or any system modifications. You'd need to use fastboot to flash the system, boot, and recovery images. It's much easier to just flash the newer build with fastboot, see section 9 of this guide for full instructions.
5. Does taking an OTA update wipe my user data?
No, it doesn't.
6. Do I need to make an EFS backup?
Absolutely yes. An EFS backup is extremely important. If your EFS partition becomes corrupt, your IMEI will disappear and you will not be able to use the phone as a phone. Without a backup it can be extremely difficult (or impossible) to restore your EFS. See the next question for an EFS backup related issue and solution.
7. I have a bootloop after restoring my EFS backup in TWRP 3.0.2-1. What can I do?
TWRP 3.0.2-1 and 3.0.2-2 are the first official TWRP releases with Nougat 7.0 or newer compatibility. Unfortunately, there are separate bugs affecting TWRP 3.0.2-1 and 3.0.2-2. A member of the TWRP development team details these issues right here. This link redirects to a thread in the Nexus 6P forums but also applies to the Nexus 5X. Read the original post of that same thread to learn how to resolve this EFS restore bootloop. You must use ADB and the phone must be booted in TWRP to resolve this issue. These ADB commands work on the Nexus 5X and 6P.
8. Can I flash just the xxxxxx.img from the factory image without losing my data?
Flashing userdata.img will format your entire phone (personal data including SMS/MMS, pictures, downloaded files, etc). You can flash any combination of these partitions (boot, system, vendor, radio, or bootloader) and this will leave your personal data intact. However, any mods that you have installed into system, vendor, or boot will be overwritten and returned to the default factory image setup when you flash these partitions. Flashing recovery.img or a newer version of your custom recovery will replace your existing recovery.
9. After updating my ROM, I get this message on every boot: "There's an internal problem with your device. Contact your manufacturer."
This warning indicates a mismatched vendor and system partition. The vendor partition was formerly integrated in the system partition for previous Nexus devices but is now a separate partition that must be flashed for each Google security update. Download a factory image and update your vendor partition using fastboot so that it matches your rom's OS build and monthly security update. If you have a file explorer installed on your phone, you can determine which vendor.img is installed by navigating to /vendor/build.prop and clicking on the build.prop. The specific vendor installed will be a combination of six numbers and letters listed in all capitals (example: NMF26F) in the ro.vendor.build.fingerprint line. These will always match up with the factory image of the same Android build (six digit alphanumeric name) for this device.
Vendor.img is specific to each OTA and contains proprietary binaries for the phone that regularly receive updates to resolve security risks. If you are a custom rom user, make sure that you flash the vendor.img for the Google monthly security update that you are moving to. Be aware that sometimes AOSP roms utilize the AOSP master branch which has a newer Android build than the monthly security update for this device. You will still need to install that month's vendor.img.
The phone will fail to boot if you mismatch the vendor.img with a different Android version. For instance, a 6.0 Marshmallow vendor.img will not allow your phone to boot on 7.0 Nougat. The vendor.img is typically not included in the custom rom zip but is often available as a separate download in the custom rom thread's first post.

Reserved #2

Reserved #3

OSX, ADB and Fastboot commands!
So you use OSX and would like to use ADB/fastboot, unlock, root, or simply have a working knowledge of your phone. Welcome! Most of the information in the guide above applies to OSX, however there are a few key changes.
Google hosts ADB/Fastboot (platform-tools) for Windows, OSX, and Linux. This is a minimal download, however these links and file sizes may be updated periodically by Google. Download the OSX platform-tools. Note that clicking the link for platform-tools will immediately start a download.
*OSX: platform-tools.
Once you have downloaded the platform-tools zip, extract the file then transfer the platform-tools folder to your desktop. The platform-tools folder contains adb, fastboot, and several other files.
To make sure your ADB is installed correctly, open a terminal command prompt and issue this cd command (change directory) to the platform-tools folder:
Code:
cd /users/username/desktop/platform-tools
then issue this command to check your adb version:
Code:
./adb version
If it returns a version number for Android Debug Bridge then you're good to go.
Using ADB/Fastboot commands
OSX natively requires "./" to prefix any ADB or Fastboot commands. If following the guide in post #1, commands issued in OSX must be written as follows ./adb [command] or ./fastboot [command]. Below are example scenarios.
To check if your device sees ADB, enable USB Debugging from within Android in Settings/Developer options. Go into Settings/About Phone, scroll down and click on build number continuously until you see a toast notification telling you that you've enabled Developer Options. Go back to your Settings menu and enter Developer Options, scroll down and enable USB Debugging.
Code:
./adb devices
It should return your device serial number, if so, adb is working.
Reboot into the bootloader:
Code:
./adb reboot bootloader
Reboot into the recovery:
Code:
./adb reboot recovery
Fastboot commands must be performed while in the bootloader. Power off your phone then boot into the bootloader (power + volume down). Below are some example OSX fastboot commands that can be used throughout the guide:
Check if your device sees fastboot:
Code:
./fastboot devices
Install a factory image:
cd into the platform-tools folder with the following command:
Code:
cd /users/username/desktop/platform-tools
Now enter commands to flash a factory image:
Code:
./fastboot flash bootloader /users/username/desktop/bullhead/images/bootloader-bullhead-bullhead-xx.xx.img
./fastboot reboot-bootloader
./fastboot flash radio /users/username/desktop/bullhead/images/radio-bullhead-bullhead-xx.xx.img
./fastboot reboot-bootloader
./fastboot flash boot /users/username/desktop/bullhead/images/boot.img
./fastboot erase cache
./fastboot flash cache /users/username/desktop/bullhead/images/cache.img
./fastboot flash recovery /users/username/desktop/bullhead/images/recovery.img
./fastboot flash system /users/username/desktop/bullhead/images/system.img
./fastboot flash vendor /users/username/desktop/bullhead/images/vendor.img

@Heisenberg you mind if i create an index thread?

reyscott1968 said:
@Heisenberg you mind if i create an index thread?
Click to expand...
Click to collapse
Go right ahead, first in best dressed as far as I'm concerned. It is a fair bit of work to keep an index maintained though, as long as you're aware. There's a new template for indexes too, using your Google goggles you should be able to track it down pretty easily.

Heisenberg said:
Go right ahead, first in best dressed as far as I'm concerned. It is a fair bit of work to keep an index maintained though, as long as you're aware. There's a new template for indexes too, using your Google goggles you should be able to track it down pretty easily.
Click to expand...
Click to collapse
il take note.. il update the thread once im back on my pc.. now still at work ...

Deleted...
Should have read the first lines in the OP

Cant wait, should have mine around october 30th.

Might want to point out the cable /adapter required to connect to pc. (I just saw that it's not included with the phone.)

AquilaDroid said:
Might want to point out the cable /adapter required to connect to pc. (I just saw that it's not included with the phone.)
Click to expand...
Click to collapse
I picked up a few of these to get me by for now until the price of Type-C goes down a bit http://www.ebay.com/itm/381344035966

I ordered one along with my phone, will be helpful for flashing.

Thanks, a friend of mine pre order this phone, I'll follow these steps

Thanks for starting this, these were some of the most helpful threads in the N5 forum.
For Mac users who have upgraded to El Capitan, the adb/fastboot installation doesn't necessarily work perfectly right now. I'm sure the Android SDK package will update for this, but in the mean time:
Install adb/fastboot as usual similar to this thread, or for specifics:
http://forum.xda-developers.com/showthread.php?t=1917237
but, once you test this with [adb devices] or [fastboot devices] you'll most likely get a command not found error.
You'll need to add a line to your ~/.bash_profile, per this reddit thread
add the following line to your ~/.bash_profile, changing username to your mac username
Code:
export PATH="/usr/local/lib/node_modules:/usr/local/apache-maven-3.0.3/bin:/Users/[B]username[/B]/.composer/vendor/bin:/Users/[B]username[/B]/Library/Android/sdk/platform-tools:$PATH"
exit, save, then run
Code:
source ~/.bash_profile
then adb/fastboot should be good to go like before!

OP has best username ever
Sent from my Nexus 5 using Tapatalk

Doesn't work!
Code:
C:\Users\Kevin\Downloads\Nexus 5x>fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.017s
C:\Users\Kevin\Downloads\Nexus 5x>fastboot flashing unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.014s
C:\Users\Kevin\Downloads\Nexus 5x>fastboot flashing unlock_critical
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.011s
C:\Users\Kevin\Downloads\Nexus 5x>fastboot flashing get_unlock_ability
...
(bootloader) get_unlock_ability: 0
OKAY [ 0.020s]
finished. total time: 0.022s

The-Kevster said:
Doesn't work!
Click to expand...
Click to collapse
Did you allow OEM Unlock in developer options?
Go into Settings/About Phone, scroll down and click on “build number” continuously until you see a toast notification telling you that you've enabled Developer Options. Go back to your Settings menu and enter Developer Options, scroll down and click on the “Enable OEM Unlock” checkbox, also make sure you enable USB Debugging while you're in the Developer Options menu.
Click to expand...
Click to collapse

Does the 5X have the hardware QFuse that that pops when you unlock the bootloader like the 6P?

KidWave said:
Does the 5X have the hardware QFuse that that pops when you unlock the bootloader like the 6P?
Click to expand...
Click to collapse
They both use Qualcomm based chips so yes the same thing would happen on the 5X.

[GUIDE] Pixel XL Android 8(OREO) Unlock/Install Stock Images + Kernels/Recovery +

[Guide] Pixel XL Android 8.0.0 (OREO) Unlock/Lock Bootloader + Install Stock Images/Custom kernels/TWRP Recovery/Systemless ROOT + November Security Patch
Other Pixel XL Guides:
Android 9.0.0 (Pie), Android 8.1.0 (Oreo), Android 7.1.2 (Nougat)​
Intro
This thread is for Pixel 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/Pixel XL'.
This Guide also works for the Pixel: If, you download the correct files for the Pixel.
Disclaimer
I assume no responsibility for the malfunctioning/bricking of your phone.
Prerequisites
A Google Pixel XL or Verizon Pixel XL phone with an unlockable Bootloader, ([How-to] Unlock bootloader on Verizon Pixel/XL by burduli) - The unlock method was discovered by: Qu3ntin0), and the latest Android8/Oreo Factory Image
Pixel XL (Fi/Canada) - marlin-opr1.170623.032-factory-990d8d51.zip
Pixel XL (other carriers) - marlin-opr3.170623.013-factory-af0b6564.zip
Note: If you want the latest OTA or Binaries. Tap the Menu icon (upper left corner) then tap Full OTA Images or Driver Binaries
Computer - With the latest Android SDK or Platform tools installed.
Important: Update Android SDK or Platform Tools, regularly, for optimal performance.
Need help installing Android SDK or using SDK Platform tools:
How to Install ADB & Fastboot on Mac, Linux & Windows-(Method 1)
Using the SDK Platform-Tools
Credits/Thanks/Recognitions
TWRP
TEAM TWRP - TWRP 3.2.0-0 for Google Pixel XL
Special thanks to @gubacsek - for [MOD][RECOVERY] Working TWRP recovery for Pixel/Pixel XL on Android O
SuperSU/suhide/Flashfire
[BETA][2017.10.01] SuperSU v2.82 SR5 by Chainfire
SuperSU v2.82-SR5 and suhide v1.09 Released Notes
[Android 4.2+][ROOT][2017.09.21] FlashFire v0.73 by Chainfire
FlashFire Documentation
Magisk/MagiskManager
[BETA][2017.11.24] Magisk v14.5 (1456) by*topjohnwu
[DEV] [Magisk] Official Pixel (XL) Support is Here! by topjohnwu
Magisk Manager Releases topjohnwu
[2017.10.15] Magisk v14.0 - Root & Universal Systemless Interface [Android 5.0+] by topjohnwu - Magisk-uninstaller-20171123.zip
Special thanks to @goodwin_c - for [Unofficial] Google Pixel family support
Custom Kernels
[KERNEL] [November 16] ElementalX 2.03 (Oreo) by flar2
[KERNEL][28.11.2017] Kirisakura-Harmony-O 2.12 [3.18.84][ANDROID OREO][SCHEDUTIL] by Freak07
[KERNEL/ROM]Sharkey Kernel and Uberstock for Pixel/Pixel XL by DespairFactor
Busybox/Busybox Checker
[MODS] Android Oreo Aroma installer misc. Mods by Tulsadiver
UPDATE-Busybox.Installer.v1.26.2-ALL-signed.zip
meekfik, download from PlayStore
Busybox Free (Stericson), download from PlayStore
[TOOLS][ZIPS][SCRIPTS] osm0sis' Odds and Ends [Multiple Devices/Platforms] by osm0sis
UPDATE-Busybox.Installer.v1.27.2-ALL-signed.zip
Busybox Checker, download from PlayStore
Custom ROMs
[ROM][Pixel-XL][8.0.0_r17] Pixel Dust OREO for marlin [ALPHA] by spezi77
Other
spaceman860 - TWRP 3.1.1-1 Backup
Special Thanks to LeMoise - for the Root with Magisk remain Stock - Pass SafetyNet and Receive OTA Updates. It was nice while it lasted. Sorry, it stopped working with the November Security Patch.
Those I may have, inadvertently, forgotten.
Index
Command Prompt/Boot Bootloader/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 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.
Note: If your computer only has 'open powershell here' in the context menu and you do not want to change it or add open 'command prompt here' use option 2.
Boot 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.
Testing ADB (Android Debug Bridge)/fastboot
ADB
Enable USB Debugging - Tap Settings > System > About Phone > Developer Options. Enable USB Debugging.
Open a Command Prompt on your computer.
Type this at the prompt to test ADB.
Code:
adb version
It should return a version number for ADB.
fastboot
Enable USB Debugging - Tap Settings > System > About Phone > Developer Options. Enable USB Debugging.
Open a Command Prompt on your computer.
Boot Bootloader
Connect your phone to your Computer with USB cable.
Type this at the prompt and press enter to test fastboot.
Code:
fastboot devices
It should return your device serial number.
Unlock Bootloader
Backup your data and Internal storage
Activate Developer Options: Tap Settings > System > About Phone > Build number. Tap Build Number until you see you're a Developer. Tap back > Developer Options. Enable OEM Unlock and, USB Debugging.
Boot Bootloader
Connect your phone to your Computer via USB cable.
Open a Command Prompt on your computer.
Type the following at the prompt:
Code:
fastboot flashing unlock
This will erase all user data from the device!
You should see a screen on your phone asking you to confirm this action, use the volume keys to scroll and the power key to make your selection.
Allow the process to complete and then issue this command:
Code:
fastboot reboot
When your phone reboots disconnect your usb cable.
Note: After unlocking your bootloader, you'll be greeted with a warning that reads 'Your device software can't be checked for corruption. Please lock the bootloader' You will receive this warning until, you relock the bootloader.
Important: do not repeat do not relock your bootloader unless your phone is fully stock. You must flash the factory image first in order to remove root and custom recovery (if you have them), if this precaution isn't taken you may end up with a brick. Please see #13 of this guide for instructions on how to return to stock and lock the boot loader.
Install Factory Image and wipe data
Backup your data and Internal storage
Download the appropriate Factory/System Image for your phone and carrier.
Unzip factory Image
Copy the following files to the Platform Tools folder on your Computer
flash-all.bat
Verify -w is present in flash-all.bat. Example: fastboot -w update image-marlin-aaa9.999999.999.zip
bootloader-marlin-9999-999999-9999999999.img
radio-marlin-9999-999999-9999999999.img
image-marlin-aaa9.999999.999.zip
Boot Bootloader
Connect phone to Computer with USB cable
Open a Command Prompt on your computer.
Type the following and press enter.
Code:
flash-all
Install Factory Image and keep data
Important: If upgrading to Android8/Oreo from Android7/Nougat 7.x.x. Do #4 - Install Factory Image and wipe data
Backup your data and Internal storage
Download the appropriate Factory Image for your phone and carrier.
Unzip factory Image
Copy the following files to the Platform Tools folder on your Computer
flash-all.bat
Edit flash-all.bat: remove -w
bootloader-marlin-9999-999999-9999999999.img
radio-marlin-9999-999999-9999999999.img
image-marlin-aaa9.999999.999.zip
Boot Bootloader
Connect phone to Computer with USB cable
Open a Command Prompt on your computer.
Type the following and press enter.
Code:
flash-all
Install Custom Kernel
Flash with TWRP
Important: Set Pin before installing TWRP: Setting > Security > Pin.
Backup your data and Internal storage
Download files:
Factory Image for Nexus/Pixel Devices to your Computer
TWRP 3.2.0-0 for Google Pixel XL
Custom Kernel - to your Phone
[KERNEL] [November 16] ElementalX 2.03 (Oreo) by flar2
[KERNEL][28.11.2017] Kirisakura-Harmony-O 2.12 [3.18.84][ANDROID OREO][SCHEDUTIL] by Freak07
[KERNEL/ROM]Sharkey Kernel and Uberstock for Pixel/Pixel XL by DespairFactor
SuperSU - to your Phone
[BETA][2017.10.01] SuperSU v2.82 SR5 by Chainfire
SuperSU v2.82-SR5 and suhide v1.09 Released Notes
Fastboot the boot.img.
Use a File Explorer to extract the contents of your factory image.Open the folder it creates and, extract the second archive (image-marlin-aaa9.999999.999.zip)
Then open the folder it creates and copy the boot.img file and paste it into the platform-tools folder.
Boot Bootloader
Connect the device/phone to your Computer
Open a Command Prompt on your computer.
Type the following command at the prompt:
Code:
fastboot flash boot --slot all boot.img
When it finishes, leave the command prompt window open, and leave your phone in bootloader mode, and connected to your Computer.
Install TWRP
Place twrp-3.2.0-0-marlin.img in your platform-tools folder and Rename it twrp.img
Type the following command at the prompt:
Code:
fastboot boot twrp.img
Flash Zips.
When TWRP boots on your phone, Tap the Install button, and select twrp-pixel-installer-marlin-3.2.0-0.zip
Reboot Recovery
Tap the Install button, and select a Custom Kernel
ElementalX-P-2.03.zip
Kirisakura-Harmony-O-2.12_3.18.84.zip
Sharkey.R3.marlin.zip
Swipe the slider to install.
Reboot System
Boot Recovery
Tap the Install button, and select SR5-SuperSU-v2.82-SR5-20171001224502.zip
Swipe the slider to install.
Note: The sequence of flashing the zips is important
Reboot System
Install BusyBox to/sbin/supersu/xbin.
Flash with Flashfire
Warning: "FlashFire is an extremely powerful application, it should be used with caution. Data loss, soft-bricks, and even hard-bricks are possible if used incorrectly. Unless you are an expert user, consult FlashFire's website and this thread before doing anything potentially destructive."
Backup your data and Internal storage
Install Application:
Install Flashfire Application from Google's Play Store
Open Flashfire Grant Root
Tap Plus Sign (+)
Tap Flash ZIP or OTA
Locate/Navigate to ZIP File location
ElementalX-P-2.03.zip
Kirisakura-Harmony-O-2.12_3.18.84.zip
Sharkey.R3.marlin.zip
Tap file
ElementalX-P-2.03.zip
Kirisakura-Harmony-O-2.12_3.18.84.zip
Sharkey.R3.marlin.zip
Check the Restore boot and recovery images box
Tap Checkmark (Top right corner)
Verify before you Flash
Flash ZIP or OTA - Has the file you want to flash and ✓ Restore boot and recovery images is present.
If not repeat 2. Flash with Flashfire d through h above.
EverRoot - ✓ Inject SuperSU is present.
If not, Tap EverRoot Select Inject SuperSU
Reboot should default to ✓ Normal.
Tap Flashfire symbol to Flash file
Root with SuperSU
Important: Set Pin before installing TWRP: Setting > Security > Pin.
Backup your data and Internal storage
Download files:
TWRP 3.2.0-0 for Google Pixel XL
[BETA][2017.10.01] SuperSU v2.82 SR5 by Chainfire to your Phone
SuperSU v2.82-SR5 and suhide v1.09 Released Notes
Copy the following file to the platform-tools folder:
twrp-3.2.0-0-marlin.img and Rename it twrp.img
Boot Bootloader
Connect device/phone to Computer
Open a Command Prompt on your computer.
Type the following command at the prompt and press enter.
Code:
fastboot boot twrp.img
When TWRP boots on your phone, tap the Install button, and select
twrp-pixel-installer-marlin-3.2.0-0.zip
Reboot Recovery
Tap the Install button, and select
SR5-SuperSU-v2.82-SR5-20171001224502.zip
Swipe the slider to install.
Reboot System.
Note: Install BusyBox to/sbin/supersu/xbin.
Root with SuperSU - Pass Safetynet
Important: Set Pin before installing TWRP: Setting > Security > Pin.
Note: If you did #6 - Install Custom Kernel or #7 - Root with SuperSU, above you already have root. Start at m..
Backup your data and Internal storage
Download files:
TWRP 3.2.0-0 for Google Pixel XL
[BETA][2017.10.01] SuperSU v2.82 SR5 by Chainfire
SR5-SuperSU-v2.82-SR5-20171001224502.zip to your Phone
UPDATE-suhide-v1.09-20171001222116.zip to your Phone
SuperSU v2.82-SR5 and suhide v1.09 Released Notes
Busybox
There are several different versions (Free and Pro, see Credits/Thanks/Recognitions above) find one that works for you.
Copy the following file to the platform-tools folder:
twrp-3.2.0-0-marlin.img and Rename it twrp.img
Boot Bootloader
Connect device/phone to Computer
Open a Command Prompt on your computer.
Type the following Command at the prompt and press enter.
Code:
fastboot boot twrp.img
When TWRP boots on your phone, tap the Install button, select twrp-pixel-installer-marlin-3.2.0-0.zip
Reboot Recovery
Tap the Install button, select SR5-SuperSU-v2.82-SR5-20171001224502.zip
Swipe the slider to install.
Reboot System.
Boot Recovery
When TWRP boots on your phone, tap the Install button, Select
UPDATE-suhide-v1.09-20171001222116.zip
Swipe the slider to install.
Reboot System
Note: Install BusyBox to /sbin/supersu/xbin.
Root with Magisk - Pass SafetyNet
Important: I haven't tested Magisk 14.5 or Magisk Manager 5.4.3. If you have problems redo #9 substitute Magisk 14.3 for Magisk 14.5 and Magisk Manager 5.4.0 for Magisk Manager 5.4.3.
Important: Set Pin before installing TWRP: Setting > Security > Pin.
Install TWRP, Custom Kernel, Magisk, and Busybox.
Backup your data and Internal storage
Download files:
TWRP 3.2.0-0 for Google Pixel XL
twrp-3.2.0-0-marlin.img to your Computer.
twrp-pixel-installer-marlin-3.2.0-0.zip to your Phone.
Custom Kernel (Optional) - to your Phone
[KERNEL] [November 16] ElementalX 2.03 (Oreo) by flar2
[KERNEL][28.11.2017] Kirisakura-Harmony-O 2.12 [3.18.84][ANDROID OREO][SCHEDUTIL] by Freak07
[KERNEL/ROM]Sharkey Kernel and Uberstock for Pixel/Pixel XL by DespairFactor
Magisk
[BETA][2017.11.24] Magisk v14.5 (1456) by*topjohnwu
Magisk-v14.5 (1456).zip to your Phone.
[2017.10.15] Magisk v14.0 - Root & Universal Systemless Interface [Android 5.0+] by topjohnwu
Magisk-uninstaller-20170928.zip to your Phone
Flash boot.img.
Use a File Explorer to extract the contents of your factory image. Open the folder it creates and, extract the second archive (image-marlin-aaa9.999999.999.zip)
Then open the folder it creates and copy the boot.img file and paste it into the platform-tools folder.
Boot Bootloader
Connect the device/phone to your Computer
Open a Command Prompt on your computer.
Type the following command at the prompt:
Code:
fastboot flash boot --slot all boot.img
When it finishes, leave the command prompt window open, leave your phone in bootloader mode and connected to the Computer.
Copy the following file to the platform-tools folder:
twrp-3.2.0-0-marlin.img and Rename it twrp.img
Type the following Command at the prompt and press enter.
Code:
fastboot boot twrp.img
When TWRP boots on your phone, tap the Install button, select
twrp-pixel-installer-marlin-3.2.0-0.zip
Swipe the slider to install
Reboot Recovery
Tap Install, select Custom kernel (Optional)
Note: If you do not want to install a Custom Kernel go to n below.
ElementalX-P-2.03.zip
Kirisakura-Harmony-O-2.12_3.18.84.zip
Sharkey.R3.marlin.zip
Swipe slider to install
Reboot System
Boot Recovery
Tap Install, select Magisk-v14.5 (1456).zip
Swipe slider to install.
Reboot System
Install BusyBox (Optional)
Open Magisk Manager, tap Menu, tap Modules, verify Busybox for Android NDK is checked.
Root with Magisk - Pass SafetyNet without installing TWRP
thanks stryker09
Important: Set Pin before using TWRP: Setting > Security > Pin.
Backup your data and Internal storage
Read/Do (as applicable) #1 - Command Prompt/Boot Bootloader/Boot Recovery; #2 - Testing ADB (Android Debug Bridge)/fastboot; #3 - Unlock Bootloader; #5 - Install Factory Image and keep data; and Tips and Tricks -OTA Installation Tips
Download files:
TWRP 3.2.0-0 for Google Pixel XL to your Computer.
[BETA] Magisk v14.5 (1456) by topjohnwu
Magisk-v14.5 (1456).zip to your Phone.
Flash boot.img.
Use a File Explorer to extract the contents of your factory image. Open the folder it creates and, extract the second archive (image-marlin-aaa9.999999.999.zip)
Then open the folder it creates and copy the boot.img file and paste it into the platform-tools folder.
Boot Bootloader
Connect the phone to your Computer via USB cable.
Open a Command Prompt on your computer.
Type the following command at the prompt:
Code:
fastboot flash boot --slot all boot.img
When it finishes, leave the command prompt window open, leave your phone in bootloader mode and connected to the Computer.
Copy the following file to the platform-tools folder:
twrp-3.2.0-0-marlin.img and Rename it twrp.img
Type the following Command at the prompt and press enter.
Code:
fastboot boot twrp.img
When TWRP boots up, tap Install, select Magisk-v14.5 (1456).zip
Swipe Slider to Install
Reboot System
Install BusyBox (Optional)
Open Magisk Manager, tap Menu, tap Modules, verify Busybox for Android NDK is checked.
Custom ROMs for Pixel XL
[ROM][Pixel-XL][8.0.0_r17] Pixel Dust OREO for marlin [ALPHA] by spezi77
Other - TWRP Backup
Boot Recovery.
Tap Backup and select Partitions to backup
Boot
System Image
Vendor Image
Data (Optional)
Swipe Slider to backup
Reboot System
Your backup will be stored in /Storage/Emulated/0/TWRP/...
Return to Stock and Lock Bootloader
Return to Stock
Backup Internal storage
Download the appropriate factory image for your phone and carrier.
Unzip factory Image
Copy the following files to the Platform Tools folder on your Computer
flash-all.bat
Verify -w is present in flash-all.bat. Example: fastboot -w update image-marlin-aaa9.999999.999.zip
bootloader-marlin-9999-999999-9999999999.img
radio-marlin-9999-999999-9999999999.img
image-marlin-aaa9.999999.999.zip
Boot Bootloader
Connect phone to Computer with USB cable
Open a Command Prompt on your computer.:
Type the following command at the prompt, and press enter.
Code:
flash-all
Lock Bootloader
Phone
Boot Bootloader
Connect your phone to your Computer with USB cable.
Computer
Open a Command Prompt on your computer.
Type the following command at the prompt:
Code:
fastboot flashing lock
When it finishes the bootloader is locked.
The next step won't be needed if your Pixel XL reboots into system after bootloader relock.
You need to boot into system now, either press Power button to reboot OR issue the following command:
Code:
fastboot reboot
Audio Mod
[GUIDE] How to install ARISE sound on 8.0 Magisk by kingbri
[GUIDE] ARISE magnum OPUS on magisk android 8.0 by kingbri

getting viper4android to work would be great.
busybox refused to install

TheUndertaker21 said:
getting viper4android to work would be great.
busybox refused to install
Click to expand...
Click to collapse
Arise works perfectly.

jaxenroth said:
Arise works perfectly.
Click to expand...
Click to collapse
which one did you flash ?

jaxenroth said:
Arise works perfectly.
Click to expand...
Click to collapse
Please more info about version and install settings!
I am trying at the moment v4a get to work with bootable twrp..... Would appreciate further info a lot.

Hi, step 3, first code should be fastboot flash bootloader bootloader.img and not fastboot flashbootloader bootloader.img
(i.e there is a gap between flash and bootloader)

To root mine all I did was chainfires boot-to-root. Then you can install and substratum theme with O support. I'm using the Swift black theme. You have to install only 5 at a time or it won't work. It says in the description for the app. My Android O is blacked out now and I'm happy.

Why is it claiming it must be a Google purchased phone? Many Verizon users have an unlocked bootloader.

TheUndertaker21 said:
which one did you flash ?
Click to expand...
Click to collapse
ARISE+Deuteronomy+2.94+Modular Aroma Installer

jaxenroth said:
ARISE+Deuteronomy+2.94+Modular Aroma Installer
Click to expand...
Click to collapse
getting abnormal when i flashed that
it worked when i use supersuconfig in permissive mode but i lost root when i do
do you still have root ? and how did you manage to get it

{
"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"
}
I flashed SU from TWRP, booted into system, from there adb'd back to BL and booted TWRP again and flashed aroma installer.

Is the aroma installer necessary for just being stock rooted with adaway? Or would I just fastboot boot twrp then flash latest SuperSU and reboot?
Sent from my Nexus 6P using Tapatalk

waiting for nexus 6p

TheUndertaker21 said:
getting viper4android to work would be great.
busybox refused to install
Click to expand...
Click to collapse
Updated OP with BusyBox path information.

grifforama said:
Hi, step 3, first code should be fastboot flash bootloader bootloader.img and not fastboot flashbootloader bootloader.img
(i.e there is a gap between flash and bootloader)
Click to expand...
Click to collapse
Thanks for the 'editing' help.

encephalon9986 said:
To root mine all I did was chainfires boot-to-root. Then you can install and substratum theme with O support. I'm using the Swift black theme. You have to install only 5 at a time or it won't work. It says in the description for the app. My Android O is blacked out now and I'm happy.
Click to expand...
Click to collapse
Yeah, there's more than one way to root, I prefer Chainfire's SuperSU. Thanks for the Substratum information.
Which Substratum theme engine and version did you use?

Mike02z said:
Why is it claiming it must be a Google purchased phone? Many Verizon users have an unlocked bootloader.
Click to expand...
Click to collapse
A case of CRS (can't remember s#*t) Lol. I just forgot to change it. Thanks for the reminder.

jaxenroth said:
View attachment 4249400 I flashed SU from TWRP, booted into system, from there adb'd back to BL and booted TWRP again and flashed aroma installer.
Click to expand...
Click to collapse
Great!

Neverendingxsin said:
Is the aroma installer necessary for just being stock rooted with adaway? Or would I just fastboot boot twrp then flash latest SuperSU and reboot?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
No, "just fastboot boot twrp then flash latest SuperSU and reboot"
This is a Pixel XL thread.

Chouiyekh said:
waiting for nexus 6p
Click to expand...
Click to collapse
This is a Pixel XP thread.

EMUI 8 and Project Treble - How to Run Custom ROMs

If you're one of the lucky few to receive Oreo (EMUI 8) on your Nova 2 Plus, then you can rejoice knowing you can finally run custom ROMs. Here's how.
I'm not responsible if you somehow ruin your device. Bear in mind, Treble ROMs are still largely in development, and there are many bugs and there isn't a single ROM that passes SafetyNet - so apps like Snapchat don't work. Read the instructions for reverting to EMUI before you proceed with installing a custom ROM.
First off, check if you're on Oreo and your phone have Project Treble.
Open Settings, About Phone
Make sure that your Android version is 8.0 or 8.1
Follow this guide
If your phone supports Treble, continue
Next, you have to unlock your bootloader. Follow this guide, under "Unlocking Bootloader". FYI: You can reboot into your bootloader by holding down the Power Button and Volume Down. When you reboot it will say "FRP unlocked and bootloader unlocked". If it doesn't, you messed up.
Go to this thread and go window shopping for a cool ROM under the title "Generic System Images (GSI) Projects & Complete ROM". I don't recommend you choose phh's AOSP, as that has the least support. Personally, I chose Resurrection Remix Official. You're also looking for an arm64 A-only GSI.
If you're like me, you won't have a TWRP image installed, because there isn't one that works 100%. Choose a GSI that has gapps installed for this reason.
Grab the GSI and drop it along with your adb.exe on your PC. Reboot back into your bootloader (remember: Power Button and Volume Down).
Execute
Code:
fastboot erase system
in your cmd/terminal/powershell window. This will erase your system partition. Don't worry, you can get this back from Firmware Finder.
Execute
Code:
fastboot -u flash system [B]GSI_File_Name[/B].img
Allow the image to flash, it could take a few minutes. Once it has completed, reboot your device either manually via power key or by entering
Code:
fastboot reboot
.
You have successfully flashed a custom ROM. Congratulations.
---
Read on for rooting and reverting back to EMUI.
The beginning steps are the same for both. You'll need Firmware Finder and Huawei Update Extractor , which is sadly only for Windows.
Open Firmware Finder and search for your model number (BAC-L21, BAC-AL00, etc)
Sort by date to find the latest Oreo release, download it
To revert to EMUI 8
Extract UPDATE.APP and place in Huawei Extractor's root
Open Huawei Update Extractor
Go to Settings, uncheck everything that begins with "Verify..."
Go back to Extract, and open the UPDATE.APP
Extract SYSTEM.img, and save it in some place. If you rooted using the method below, get your RAMDISK.img out as well.
Place it in the folder where you have adb.exe
Reboot phone into fastboot
Execute
Code:
fastboot erase system
in your cmd/terminal/powershell window. This will erase your system partition.
Execute
Code:
fastboot -u flash system SYSTEM.img
If you rooted, then flash the original RAMDISK.img as well
Allow the images to flash, it could take a few minutes. Once it has completed, reboot your device either manually via power key or by entering
Code:
fastboot reboot
.
Grats, you are now back to EMUI 8.
---
To root your phone using Magisk
Extract UPDATE.APP and place in Huawei Extractor's root
Open Huawei Update Extractor
Go to Settings, uncheck everything that begins with "Verify..."
Go back to Extract, and open the UPDATE.APP
Extract RAMDISK.img, and save it in some place - have a backup copy saved to your PC in case you want to unroot
Move it to your phone using MTP, and remember where you saved it
Download Magisk apk
Install it on your phone
Open the app, go to Settings and change the Update Channel to beta
Go back to the opening page, make sure it's installing Magisk 16.6, then press Install, then press Patch Boot Image
Select the RAMDISK.img you just saved, let it do its thing. It won't show you any progress bars, but trust me, it's working.
Once it's finished, move the patched_boot.img from the MagiskManager folder to your PC
Place it in the folder where you have adb.exe
Reboot phone into fastboot
Execute
Code:
fastboot erase ramdisk
in your cmd/terminal/powershell window.
Execute
Code:
fastboot flash ramdisk patched_boot.img
Allow the image to flash, it could take a few minutes. Once it has completed, reboot your device either manually via power key or by entering
Code:
fastboot reboot
.
Grats, you got Magisk root.
Once you have root, you can also fix a fingerprint gesture issue with Treble ROMs by following this guide.
---
Thanks for reading and enjoy your Oreo custom ROM.

Can u make a detailed tut how to root bac L21 running oreo? And how to flash a stock firmware if messed up.. Coz i screwed up my phone before and tried sd card method but could not flash a stock firmware.

Deleted

delete guide

delete guide

--reserved--

Hoe can i tell what image matches for my phone stil on 8.1 november 1st security patch n a unlocked boot

rob420p said:
Hoe can i tell what image matches for my phone stil on 8.1 november 1st security patch n a unlocked boot
Click to expand...
Click to collapse
Check your build and download the right file.
Matteo

While uninstalling Magisk(from rooted stock), do we need to find the current active slot and flash the stock image to it? In the guide flashing to both partitions is mentioned.

mujtahid1494. said:
While uninstalling Magisk(from rooted stock), do we need to find the current active slot and flash the stock image to it? In the guide flashing to both partitions is mentioned.
Click to expand...
Click to collapse
Flash a both slot just to be sure to pass OTA if needed.
Matteo

Matteo said:
Welcome to AIO Magisk Sub Guide.
Here you will find best methods for root Mi A2. I will maintain this guide with all safe, update methods. Currently only patched boot method is out for Stock Roms. I will add Twrp methods when we have decryption on pie.
Code:
Your warranty is now void.
We are not responsible for bricked devices, bootloop... Please
do some research if you have any concerns about mods
included in these GUIDES before using them! YOU are choosing to
make these modifications.
Install Magisk on Stock Roms Oreo & Pie
Needs:
- Bootloader unlocked, check this (currently not out) guide.
- Magisk Manager apk check Dowloads Section
- A brain
Procedure:
- Download the correct PatchedBoot file for your build from Downloads Section
- Rename the patched boot file to "patched_boot.img" and past it to your adb folder.
- Download Magisk Manager apk from Downloads Section
- Move apk to phone sdcard
- Reboot phone to bootloader by pressing Power + Volume Down until phone show the fastboot logo.
- Now open adb(fastboot) command prompt and type :
Code:
fastboot boot patched_boot.img
Your phone shoulds boot
- Install Magisk Manager apk
- Open Magisk Manager
- Click Install then choose Direct install. Reboot.
Done, you have Magisk on your device.
To uninstall Magisk just flash stock boot.img using fastboot:
"fasboot flash boot_a boot.img" and "fasboot flash boot_b boot.img"
Install Magisk on Custom Roms
Needs:
- Be on a Custom Rom
- Latest Magisk Beta zip check Dowloads Section
- Twrp latest file.img check Dowloads Section
- A brain
Procedure:
Sideload method. (It's for people who want to install Magisk on their phone during Custom Rom installation process without any permanent Twrp (usefull for people who want to root their phone when they have MTP issue during Custom Rom installation)
- Download the latest Magisk Beta zip from Downloads Section
- Rename the Magisk file to "magisk.zip" and past it to your adb folder.
- Download the latest TWRP img from Downloads Section
- Rename the twrp file to "twrp.img" and past it to your adb folder.
- Reboot phone to bootloader by pressing Power + Volume Down until phone show the fastboot logo.
Phone is now in fastboot.
- Type :
Code:
fastboot boot twrp.img
- Phone will boot Twrp.
- Navigate to Advanced > Adb Sideload
- Swipe to allow
- Open adb (fastboot) command prompt on your pc, type
Code:
adb sideload magisk.zip
Reboot and done, you have Magisk on your device.
Normal temp Twrp method. (It's for people who want to install Magisk on their phone when they are already running a Custom Rom without permanent Twrp.
- Download the latest Magisk Beta zip from Downloads Section
- Rename the Magisk file to "magisk.zip" and past it to your phone sdcard.
- Download the latest TWRP img from Downloads Section
- Rename the twrp file to "twrp.img" and past it to your adb folder.
- Reboot phone to bootloader by pressing Power + Volume Down until phone show the fastboot logo.
Phone is now in fastboot.
- Type :
Code:
fastboot boot twrp.img
- Phone will boot Twrp.
- Click Install, choose magisk.zip
- Swipe to confirm, wait for the process...
Reboot and done, you have Magisk on your device.
To uninstall Magisk just flash stock boot.img using fastboot:
"fasboot flash boot_a boot.img" and "fasboot flash boot_b boot.img"
If you have any issue, or if i make any type error, reply.
don't forget to ckick the TX button.
Downloads Section:
Boot / Patched Boot images
Magisk Thread for Beta zip / Apk file
Twrp images & zip
Click to expand...
Click to collapse
Hello, the stock boot v10.0.1.0.img, does not have mirrors, please could upload it again, I need it urgently, thank you very much

ofuen said:
Hello, the stock boot v10.0.1.0.img, does not have mirrors, please could upload it again, I need it urgently, thank you very much
Click to expand...
Click to collapse
No. If you have issue with androidfilehost it's not my problem.
Matteo

Matteo said:
Welcome to AIO Magisk Sub Guide.
Here you will find best methods for root Mi A2. I will maintain this guide with all safe, update methods. Currently only patched boot method is out for Stock Roms. I will add Twrp methods when we have decryption on pie.
Code:
Your warranty is now void.
We are not responsible for bricked devices, bootloop... Please
do some research if you have any concerns about mods
included in these GUIDES before using them! YOU are choosing to
make these modifications.
Install Magisk on Stock Roms Oreo & Pie
Needs:
- Bootloader unlocked, check this (currently not out) guide.
- Magisk Manager apk check Dowloads Section
- A brain
Procedure:
- Download the correct PatchedBoot file for your build from Downloads Section
- Rename the patched boot file to "patched_boot.img" and past it to your adb folder.
- Download Magisk Manager apk from Downloads Section
- Move apk to phone sdcard
- Reboot phone to bootloader by pressing Power + Volume Down until phone show the fastboot logo.
- Now open adb(fastboot) command prompt and type :
Code:
fastboot boot patched_boot.img
Your phone shoulds boot
- Install Magisk Manager apk
- Open Magisk Manager
- Click Install then choose Direct install. Reboot.
Done, you have Magisk on your device.
To uninstall Magisk just flash stock boot.img using fastboot:
"fasboot flash boot_a boot.img" and "fasboot flash boot_b boot.img"
Install Magisk on Custom Roms
Needs:
- Be on a Custom Rom
- Latest Magisk Beta zip check Dowloads Section
- Twrp latest file.img check Dowloads Section
- A brain
Procedure:
Sideload method. (It's for people who want to install Magisk on their phone during Custom Rom installation process without any permanent Twrp (usefull for people who want to root their phone when they have MTP issue during Custom Rom installation)
- Download the latest Magisk Beta zip from Downloads Section
- Rename the Magisk file to "magisk.zip" and past it to your adb folder.
- Download the latest TWRP img from Downloads Section
- Rename the twrp file to "twrp.img" and past it to your adb folder.
- Reboot phone to bootloader by pressing Power + Volume Down until phone show the fastboot logo.
Phone is now in fastboot.
- Type :
Code:
fastboot boot twrp.img
- Phone will boot Twrp.
- Navigate to Advanced > Adb Sideload
- Swipe to allow
- Open adb (fastboot) command prompt on your pc, type
Code:
adb sideload magisk.zip
Reboot and done, you have Magisk on your device.
Normal temp Twrp method. (It's for people who want to install Magisk on their phone when they are already running a Custom Rom without permanent Twrp.
- Download the latest Magisk Beta zip from Downloads Section
- Rename the Magisk file to "magisk.zip" and past it to your phone sdcard.
- Download the latest TWRP img from Downloads Section
- Rename the twrp file to "twrp.img" and past it to your adb folder.
- Reboot phone to bootloader by pressing Power + Volume Down until phone show the fastboot logo.
Phone is now in fastboot.
- Type :
Code:
fastboot boot twrp.img
- Phone will boot Twrp.
- Click Install, choose magisk.zip
- Swipe to confirm, wait for the process...
Reboot and done, you have Magisk on your device.
To uninstall Magisk just flash stock boot.img using fastboot:
"fasboot flash boot_a boot.img" and "fasboot flash boot_b boot.img"
If you have any issue, or if i make any type error, reply.
don't forget to ckick the TX button.
Downloads Section:
Boot / Patched Boot images
Magisk Thread for Beta zip / Apk file
Twrp images & zip
Click to expand...
Click to collapse
Thank you very much. It works for my stock rom. already clicked the thanks icon

dipankar.roy said:
Thank you very much. It works for my stock rom. already clicked the thanks icon
Click to expand...
Click to collapse
Thank you man, but plz next time don't quote the entire guide
Have a nice day
Matteo

No links available for stock boot 9.6.17.0
Edit: Oh I see, not his problem, dang.

Matteo said:
Welcome to AIO Magisk Sub Guide.
Here you will find best methods for root Mi A2. I will maintain this guide with all safe, update methods. Currently only patched boot method is out for Stock Roms. I will add Twrp methods when we have decryption on pie.
Code:
Your warranty is now void.
We are not responsible for bricked devices, bootloop... Please
do some research if you have any concerns about mods
included in these GUIDES before using them! YOU are choosing to
make these modifications.
Install Magisk on Stock Roms Oreo & Pie
Needs:
- Bootloader unlocked, check this (currently not out) guide.
- Magisk Manager apk check Dowloads Section
- A brain
Procedure:
- Download the correct PatchedBoot file for your build from Downloads Section
- Rename the patched boot file to "patched_boot.img" and past it to your adb folder.
- Download Magisk Manager apk from Downloads Section
- Move apk to phone sdcard
- Reboot phone to bootloader by pressing Power + Volume Down until phone show the fastboot logo.
- Now open adb(fastboot) command prompt and type :
Code:
fastboot boot patched_boot.img
Your phone shoulds boot
- Install Magisk Manager apk
- Open Magisk Manager
- Click Install then choose Direct install. Reboot.
Done, you have Magisk on your device.
To uninstall Magisk just flash stock boot.img using fastboot:
"fasboot flash boot_a boot.img" and "fasboot flash boot_b boot.img"
To uninstall Magisk just flash stock boot.img using fastboot:
"fasboot flash boot_a boot.img" and "fasboot flash boot_b boot.img"[/HIDE][/SIZE]
If you have any issue, or if i make any type error, reply.
don't forget to ckick the TX button.
[/SIZE]
Click to expand...
Click to collapse
After installing the patched boot image to my device (MI A2), android version 9. build number V10.0.2.0.PDIMIFJ,
the Magisk working properly. But when I turned off my phone and insert the power cable for charging, the phone start booting and stuck at "AndroidOne" logo.
Waiting for your advice...
Thanks..

dipankar.roy said:
After installing the patched boot image to my device (MI A2), android version 9. build number V10.0.2.0.PDIMIFJ,
the Magisk working properly. But when I turned off my phone and insert the power cable for charging, the phone start booting and stuck at "AndroidOne" logo.
Waiting for your advice...
Thanks..
Click to expand...
Click to collapse
That's a normal stock rom issue with magisk, you can't fix it. but if you want, we don't have this issue on custom roms
( next time plz don't quote the entire thread )
Matteo

Hey Matteo,
I've got a problem while booting with the patched boot image. Whenever I start the 'fastboot boot image' stuff, it ends with following message:
downloading 'boot.img'...
FAILED (command write failed (no error))
finished. Total time 0.002s
Phone screen goes black and says 'press any key to continue' or something like that. I tried several different USB ports and also different boot images, I cant even boot with the stock image.
When I unlocked the bootloader I had a problem that while booting the phone said I should perform a factroy reset because of a corrupt file system...after doing that, the phone itself works fine. But I really want the root access.
Have you ever encountered that message?
Thanks in advance
Update: Did the same procedure with my notebook and ironically it worked without a flaw. USB driver conflicts maybe?

On Pie V10.0.2.0, applied the patched_boot.img, Magisk was not installed at the beginning.
Installed Magisk manually but the phone was not rooted.
Applied the patched_boot.img again and I got root.
Now, every time I reboot the phone, root is gone and I have to apply the patched_boot.img again.

Thread closed on OP request

Message of dm-verity on TWRP Recovery website

I'm using android Pie(stock rom) on mi a1. I want to flash Lineageos for microG. On TWRP Recovery website, it says this device(mi a1-tissot) uses dm-verity and in order to bypass dm-verity's boot prevention, you will have to install a kernel that has dm-verity disabled in fastboot.
I'm completely new in the realm of flashing custom roms. And no website and youtube video talks about dm-verity in a clear manner:crying:. So what steps exactly should I follow to install Lineageos for microG?
Also, my phone(data) is encrypted. And I can't find a way to decrypt it. Will it affect flashing TWRP Recovery or Lineageos?

wHY did not anybody answer guys?

Here are the steps to install TWRP and maybe a custom ROM:
1.Make sure to have USB Debugging activated
2.Put the Mi A1 in Fastboot Mode(Volume Down+Power)
3.Connect your phone to your PC
4.Make sure to have downloaded platform-tools
5.Download the .img TWRP file and copy it in the platform-tools folder
6.Hold Shift and right Click in the platform-tools folder,and click onpen a PowerShell window here
7.Type fastboot devices or .\fastboot devices(for me the second worked)
8.Now write fastboot boot twrp.xx.xx.xx.img(here Goes the name of your .img TWRP file)
9.After 15 seconds,you will probably see a warning that asks You to swipe to allow modifications.Don't swipe.Press on:Keep read only.
10.From this point,You can install every custom ROM,You can install Magisk.
Hope this helped You out!

TheAlmigthyOne said:
Here are the steps to install TWRP and maybe a custom ROM:
1.Make sure to have USB Debugging activated
2.Put the Mi A1 in Fastboot Mode(Volume Down+Power)
3.Connect your phone to your PC
4.Make sure to have downloaded platform-tools
5.Download the .img TWRP file and copy it in the platform-tools folder
6.Hold Shift and right Click in the platform-tools folder,and click onpen a PowerShell window here
7.Type fastboot devices or .\fastboot devices(for me the second worked)
8.Now write fastboot boot twrp.xx.xx.xx.img(here Goes the name of your .img TWRP file)
9.After 15 seconds,you will probably see a warning that asks You to swipe to allow modifications.Don't swipe.Press on:Keep read only.
10.From this point,You can install every custom ROM,You can install Magisk.
Hope this helped You out!
Click to expand...
Click to collapse
I found this thread by doing something wrong that you mentioned. I didn't swipe to allow modifications and now the TWRP can't flash anything. Tried every remedy I can find but nothing. It can wipe system though, but not restore it so now I'm stuck in bootloops. Damn, idk what to do.

Dear Zentom,for me,that method worked.But,I can help you get out of that situation
1.Make sure to have your bootloader unlocked
2.Download the stock ROM for Mi A1
3.Boot into Fastboot Mode
4.Extract the stock ROM archive
5.Copy all the extracted files into the platform-tools folder
6.Find a .bat file names "flash-all"
7.Open it
8.After 15 minutes or so,your phone will boot.
Hope I helped you!

TheAlmigthyOne said:
Dear Zentom,for me,that method worked.But,I can help you get out of that situation
1.Make sure to have your bootloader unlocked
2.Download the stock ROM for Mi A1
3.Boot into Fastboot Mode
4.Extract the stock ROM archive
5.Copy all the extracted files into the platform-tools folder
6.Find a .bat file names "flash-all"
7.Open it
8.After 15 minutes or so,your phone will boot.
Hope I helped you!
Click to expand...
Click to collapse
Thanks, but I flashed the stock rom from twrp anyway. Though I had to flash the October 2019 ROM. Do you know anywhere where one can get an updated one?

If You want the latest stock ROM,this is:https://drive.google.com/file/d/1yVWv4hiTSk-3zai-4u2c2OcLpRdFL_J6/view