Related
[Guide] Pixel XL Android 7.1.2 (OREO) Unlock/Lock Bootloader + Install Stock Images/Custom kernels/TWRP Recovery/Systemless ROOT + August 2017 Security Patch
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'.
It also works for Pixel owners: If, they download the correct files for their Pixel.
This Guide is not for use with the Second Generation Pixel 2 or Pixel 2 XL devices.
Update(s):
Other - Added 'Other' after 'Prerequisites'
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 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 7.1.2 August 2017, Factory Image (NHG47Q - Verizon; NKG47S - T-Mobile, Fi carriers, and Rogers; NZH54D - Deutsche Telekom; NJH47F - all other carriers).
Note: If you want the latest OTA or Binaries. Tap the Menu icon (upper left corner) then tap Full OTA Images or Driver Binaries
PC - With the latest Android SDK or SDK Platform tools installed.
Important: Update Android SDK or Platform Tools, regularly, for optimal performance.
Need help installing Android SDK or SDK Platform Tools
How to Install ADB & Fastboot on Mac, Linux & Windows-(Method 1)
Easiest-way-to-install-androids-adb-and-fastboot
Other
Pixel XL Guides: Android 9.0.0 (Pie)Android 8.1.0 (Oreo), Android 8.0.0 (Oreo)
Pixel 3 XL Guide: Android 9.0.0 (Pie)
Credit/Thanks/Recognitions
TWRP
TWRP for Google Pixel XL
twrp-3.0.2-0-RC1-fastboot-marlin.img to your Computer.
twrp-pixel-installer-marlin-3.1.0-0RC1.zip to your phone.
twrp-pixel-installer-marlin-3.1.0-0RC2.zip to your phone
SuperSU
[BETA][2017.10.01] SuperSU v2.82 SR5 by Chainfire
Magisk/MagiskManager
[Unofficial] Google Pixel family support by goodwin_c
Custom Kernels
ElementalX kernel
Franco's Kernel
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
Other
pcriz -Fastboot Slot Commands, Custom ROM installion help, Magisk help, and help on many many other subjects.
Those I may have inadvertently forgotten.
Index
Open 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 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. Press 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 and press enter 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 a USB cable.
Type this at the prompt and press enter to test fastboot.
Code:
fastboot devices
It should return your device serial number.
Unlock Your 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 and press enter:
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 says Your device software can't be checked for corruption. Please lock the bootloader everytime you reboot. It's ok, as long as your bootloader is unlocked it will stay there.
Important: do not repeat 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 9 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 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
bootloader-marlin-9999-999999-9999999999.img
radio-marlin-9999-999999-9999999999.img
image-marlin-aaa99a.zip
Boot Bootloader
Connect phone to Computer with USB cable
Open a Command Prompt on your computer.
Type the following at the prompt and press enter.
Code:
flash-all
Install Factory Image and keep data
Backup your data and Internal storage
Download the factory image for your phone and carrier.
Unzip factory Image
Edit flash-all.bat: Remove -w
Copy the following files to the Platform Tools folder on your Computer
flash-all.bat
bootloader-marlin-9999-999999-9999999999.img
radio-marlin-9999-999999-9999999999.img
image-marlin-aaa99a.zip
Boot Bootloader
Connect phone to Computer with USB cable
Open a Command Prompt on your computer.
Type the following at the prompt and press enter.
Code:
flash-all
Install A Custom Recovery and Root with SuperSU
Important: Set Pin before installing TWRP: Setting > Security > Pin.
Important: Make and restore nandroid backups with TRWP RC1 zip. Some, users have reported problems creating/restoring nandroid backups with TWRP RC2 zip.
Backup your data and Internal storage
Download files:
twrp-3.0.2-0-RC1-fastboot-marlin.img to your Computer.
twrp-pixel-installer-marlin-3.1.0-0RC1.zip to your phone.
twrp-pixel-installer-marlin-3.1.0-0RC2.zip to your phone.
[STABLE][2017.05.27] SuperSU v2.82 by SuperSU Release to your phone.
Copy the following file to the platform-tools folder: twrp-3.0.2-0-RC1-fastboot-marlin.img rename it twrp.img
Boot Bootloader
Connect device/phone to computer
Open a Command Prompt on your computer.
Type the following at the Prompt.
Code:
fastboot boot twrp.img
When TWRP boots on your phone, tap the Install button, select twrp-pixel-installer-marlin-3.0.2-0-RC1.zip
Tap Add more ZIPs button, select SuperSU-v2.82-201705271822.zip
Swipe the slider to install.
Reboot system
Install A Custom Recovery and Root with Magisk (Clean Install)
Important: Set Pin before installing TWRP: Setting > Security > Pin.
Important: Make and restore nandroid backups with TRWP RC1 zip. Some, users have reported problems creating/restoring nandroid backups with TWRP RC2 zip.
Note:[Substratum] theme Spectrum does not work with Magisk root.
Backup your data and Internal storage
Download the following files:
ElementalX-P-1.14.zip for Pixel XL
twrp-3.0.2-0-RC1-fastboot-marlin.img
twrp-pixel-installer-marlin-3.0.2-0-RC2.zip
Magisk-v13.3-Pixel-b4.zip
MagiskManager-5_1_1.apk
Magisk-uninstaller-20170720.zip
Flash Boot.img - If you have TWRP, SuperSU, or a custom kernel installed.
Extract the contents of your factory image and open the folder it creates. From there, extract the second archive (image-marlin-aaa99a.zip)
Then open that folder and copy the boot.img file and paste it into the platform-tools folder.
Boot Bootloader
Connect the 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, your phone in bootloader mode and connected to your computer.
Install TWRP
Place twrp-3.0.2-0-RC1-fastboot-marlin.img in your platform-tools folder and Rename it twrp.img
Type the following command at the prompt:
Code:
fastboot boot twrp.img
When TWRP boots, tap the Install button and select twrp-pixel-installer-marlin-3.0.2-0-RC2.zip
Swipe the slider to install
Press the back button until you are on TWRP's main menu select Reboot > Recovery.
Flash the ZIPs
Disconnect your phone from your Computer.
Tap the Install button, then navigate to the files you downloaded.
Select the Magisk Uninstaller.zip, tap the Add more ZIPs button.
Select the twrp-pixel-installer-marlin-3.0.2-0-RC2.zip.
Swipe to install
Reboot Recovery
Tap the Install button select a Custom Kernel: ElementalX-P-1.1x.zip or Franco's Kernel-r1x.zip.
Tap Add more ZIPs button select Magisk-v13.3-Pixel-b4.zip, tap the Add more ZIPs button and select: twrp-pixel-installer-marlin-3.0.2-0-RC2.zip
Swipe to install
Note: During the Installation of ElementalX, ElementalX's AROMA installer interface, will require your input: So, tick I agree, then tap Next a few times and press Install ElementalX when prompted.
When ElementalX AROMA installer finishes, tap Next, and Finish. After, the other ZIPs are installed.
Reboot System
Note: If you're prompted to install the TWRP app at this point, remove check marks from two check boxes and select Do Not Install.
Install MagiskManager
Install Magisk Manager (5.1.1.apk)
Wipe data on Magisk Manager
Enable Magisk Hide
Enable Core Only Mode
Toggle on and off systemless hosts
Reboot system
Check for Latest Version, Root, and Saftey Net.
Update Magisk Dirty Flash
Download file:
Magisk-v13.3-Pixel-b4.zip or Magisk-v13.4-Pixel-beta2-build1.zip
Flash the ZIPs
Magisk-v13.3-Pixel-b4.zip or Magisk-v13.4-Pixel-beta2-build1.zip, tap the Add more ZIPs button.
Select twrp-pixel-installer-marlin-3.0.2-0-RC2.zip.
Swipe to install.
Reboot system
Check for Latest Version, Root, and Saftey Net.
Custom ROMs for Pixel/Pixel XL
[ROM][Pixel-XL][7.1.2_r24]★ Pure Nexus ★ Substratum | Fi | WiFi Calling ★[07/25/17] by BeansTown106
[ROM][Pixel-XL][7.1.2_r33][OMS] Pixel Dust for marlin [FINAL][2017/08/22] by spezi77
[ROM][Resurrection Remix v5.8.3][Android Nougat 7.1.2][OMS][07/24/17] by BDogg718
[ROM][UNOFFICIAL] LineageOS 14.1 Nightlies for the Google Pixel (marlin/sailfish) by invisiblek
Paranoid Android 7.2.1 - AOSPA - Pixel XL by freak_97
ROM][7/21/17][Marlin][7.1.2][WEEKLY]Team OctOs Oct-N by cjkacz
SCREW'D ROM
Install Custom Kernel
Franco's Kernel - SuperSu
Download file:
The latest Franco's kernel for Pixel/Pixel XL
Boot into TWRP
Press Install button select the file you downloaded
Swipe slider to install
Reboot System
ElementalX-PXL-1.xx by flar2 Kernel - SuperSU
Download files:
ElementalX kernel
[STABLE][2017.05.27] SuperSU v2.82 by SuperSU Release
Flash ElementalX zip in TWRP recovery (do not flash SuperSU-v2.82-201705271822.zip again if you're already rooted).
During the Installation, ElementalX's AROMA installer interface, will require your input: So, tick I agree, then tap Next a few times and tap Install ElementalX when prompted.
When ElementalX AROMA installer finishes, tap Next, and then Finish.
Note: If you're prompted to install the TWRP app at this point, remove check marks from two check boxes and select Do Not Install.
Franco's Kernel or ElementalX-PXL-1.xx by flar2 Kernel - Magisk
See [Unofficial] Google Pixel family support by goodwin_c for Installation Instructions.
Install Substratum Theme
SuperSU Root
Install Substratum Theme Engine from the play store.
Install [Substratum] Spectrum theme from the play store. Note: I used Substratum theme Spectrum to test the installation of Substratum with SuperSU root..
Magisk Root
Researching Information
Return to Stock and Lock Bootloader
Return to Stock
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
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-aaa99a.zip
Boot Bootloader
Connect phone to Computer with USB cable
Open a Command Prompt on your computer.
Type the following command at the prompt.
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 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
When your phone reboots disconnect your usb cable.
Audio Mod
Weta Audio Mod
we already have guides though
flex360 said:
we already have guides though
Click to expand...
Click to collapse
can't hurt to have an updated guide for those too lazy to read.. so many posts about "this guide is out of date" or "i dont have time to read 6 pages about other people's experiences"
Thanks for this updated guide, this was helpful. Although, in step 4 it looks like you forgot to mention flashing SuperSu.
jrhatfield said:
Thanks for this updated guide, this was helpful. Although, in step 4 it looks like you forgot to mention flashing SuperSu.
Click to expand...
Click to collapse
It has been posted several times that the June security update doesn't need the verified boot signer. Only the May update needed it.
JimSmith94 said:
It has been posted several times that the June security update doesn't need the verified boot signer. Only the May update needed it.
Click to expand...
Click to collapse
I'll research it and make changes if needed.
Great Job compiling all the information in one place. Appreciate your hard work. This should be helpful to many.
You could even update this to include flashing of Custom ROMs. And a little bit about the slot change etc. That way the guide would almost be complete.
iamjimmy said:
Great Job compiling all the information in one place. Appreciate your hard work. This should be helpful to many.
You could even update this to include flashing of Custom ROMs. And a little bit about the slot change etc. That way the guide would almost be complete.
Click to expand...
Click to collapse
Intro
The purpose of this thread is twofold:
First, it is for Pixel XL owners that want to Root their phone, and enjoy the benefits of rooting it without installing a custom ROM...
¯\_(ツ)_/¯
About to try this with the -w flag. Is there a reason to not use a -w if I intend on rooting njh47b on a google store pixel xl?
Avasta said:
About to try this with the -w flag. Is there a reason to not use a -w if I intend on rooting njh47b on a google store pixel xl?
Click to expand...
Click to collapse
2. Install Factory Image and wipe Data
Code:
fastboot -w update image-marlin-aaa99a.zip
3. Install Factory Image and keep Data
Code:
fastboot update image-marlin-aaa99a.zip
Homeboy76 said:
2. Install Factory Image and wipe Data
Code:
update -w image-marlin-aaa99a.zip
3. Install Factory Image and keep Data
Code:
update image-marlin-aaa99a.zip
Click to expand...
Click to collapse
I was asking if there was any affect to the rooting ability of the device if you did vs didn't use the -w command. I completed my update of my phone. I never like a dirty update since it only causes problem later on. I tested it without the -w switch and everything worked (kept my data, but as mentioned dirty flashes = no good), so I went back and repeated the steps with the -w switch. Everything works like a charm. Only issue I have noticed is that Netflix is no longer compatible with my device?!? Like not really sure why, but cant install it from the play store. Will contact Netflix about this later today.
Avasta said:
I was asking if there was any affect to the rooting ability of the device if you did vs didn't use the -w command. I completed my update of my phone. I never like a dirty update since it only causes problem later on. I tested it without the -w switch and everything worked (kept my data, but as mentioned dirty flashes = no good), so I went back and repeated the steps with the -w switch. Everything works like a charm. Only issue I have noticed is that Netflix is no longer compatible with my device?!? Like not really sure why, but cant install it from the play store. Will contact Netflix about this later today.
Click to expand...
Click to collapse
Gotcha, there are no 'effects to the rooting ability of the device'.
However, some apps will not work unless you 'hide Root' with Magisk i.e. Android Pay, Netflix's, etc.
Did you root with Magisk?
Homeboy76 said:
Gotcha, there are no 'effects to the rooting ability of the device'.
However, some apps will not work unless you 'hide Root' with Magisk i.e. Android Pay, Netflix's, etc.
Did you root with Magisk?
Click to expand...
Click to collapse
I dunno about you but I have magisk hide on and hid the playstore and a few other processes but if its checking your phone at a point before you can enable magisk hide and storing the results wouldn't it not make much difference? I ask this because magisk hide or not, netflix doesnt show up. Even on a clean boot its not listed as an app I can restore. The simple fix for me is to restore a back up or simply download from apk mirror.
I would say a BIG tks: I've been rooting my phones for years and this one is definitely a rollercoaster of information and success for me (boot loop over boot loop, random crash, random bugs... after following many guides..)
Will try this one (had to factory reset again yesterday: phone would not boot up).
One (major) thing is missing here: what to do with the slot a/b? I had crashes that automatically switched from one slot to the other slot, confusing the hell out of (the retarded?) me. It's still not clear what I'm suppose to double flash or not....
Tks!
parano666 said:
I would say a BIG tks: I've been rooting my phones for years and this one is definitely a rollercoaster of information and success for me (boot loop over boot loop, random crash, random bugs... after following many guides..)
Will try this one (had to factory reset again yesterday: phone would not boot up).
One (major) thing is missing here: what to do with the slot a/b? I had crashes that automatically switched from one slot to the other slot, confusing the hell out of (the retarded?) me. It's still not clear what I'm suppose to double flash or not....
Tks!
Click to expand...
Click to collapse
When you flash a factory image, flash it in both slots.
Flash all once
Boot into the bootloader again
Swap slots in bootloader
Flash all again
(tks!)
(update: needed twrp-pixel-installer-marlin-3.1.0-0RC2 installed and booted to install magisk v12 pixel (was getting error 1 with twrp-pixel-installer-marlin-3.0.2-0-RC1.zip))
(update2: safety net passed!)
pcriz said:
I dunno about you but I have magisk hide on and hid the playstore and a few other processes but if its checking your phone at a point before you can enable magisk hide and storing the results wouldn't it not make much difference? I ask this because magisk hide or not, netflix doesnt show up. Even on a clean boot its not listed as an app I can restore. The simple fix for me is to restore a back up or simply download from apk mirror.
Click to expand...
Click to collapse
Ok.
parano666 said:
I would say a BIG tks: I've been rooting my phones for years and this one is definitely a rollercoaster of information and success for me (boot loop over boot loop, random crash, random bugs... after following many guides..)
Will try this one (had to factory reset again yesterday: phone would not boot up).
One (major) thing is missing here: what to do with the slot a/b? I had crashes that automatically switched from one slot to the other slot, confusing the hell out of (the retarded?) me. It's still not clear what I'm suppose to double flash or not....
Tks!
Click to expand...
Click to collapse
Intro
The purpose of this thread is twofold:
First, it is for Pixel XL owners that want to Root their phone, and enjoy the benefits of rooting it without installing a custom ROM...
If you follow the instructions above you should not have to worry about slot a/b. The firmware will put it in the correct slot.
If you are installing Custom ROM this thread is not for you. You, should follow the installation instructions of the Custom ROM you want to install.
parano666 said:
(tks!)
(update: needed twrp-pixel-installer-marlin-3.1.0-0RC2 installed and booted to install magisk v12 pixel (was getting error 1 with twrp-pixel-installer-marlin-3.0.2-0-RC1.zip))
(update2: safety net passed!)
Click to expand...
Click to collapse
You're welcome!
[Guide] Pixel XL Android 8.1.0 (OREO) Unlock/Lock Bootloader + Install Stock Images/Custom kernels/TWRP Recovery/Systemless ROOT + July 2018 Security Patch
Intro
This Guide 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 XL'.
This Guide also works for the Pixel owners: If, they download the correct files for their phone.
This Guide is not for use with the Second Generation Pixel 2 or Pixel 2 XL devices.
Update(s):
Custom ROM - crDroid v4.7
Note: Some Custom ROM's have the latest Security Patch.
Install Custom Kernel: - See #7, or #8
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 Google Pixel XL or Verizon Pixel XL phone with an unlocked bootloader. ([How-to] Unlock bootloader on Verizon Pixel/XL by burduli - The unlock method was discovered by: Qu3ntin0) , and the latest Android 8.1.0 (Oreo) Factory Image: "marlin" for Pixel XL
marlin-opm4.171019.021.p1-factory-d5fc023e.zip
marlin-ota-opm4.171019.021.p1-f0709550.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 SDK Platform-Tools installed.
Important: Update Platform Tools, regularly, for optimal performance.
Need help installing or using SDK Platform tools: Easiest-way-to-install-androids-adb-and-fastboot
Other
Pixel XL Guides: Android 9.0.0 (Pie), Android 8.0.0 (Oreo), Android 7.1.2 (Nougat)
Pixel 3 XL Guide: Android 9.0.0 (Pie)
Credits/Thanks/Recognitions
Heisenberg RETIRED FORUM MODERATOR - He set the standard for creating, detailed, Guides.
Those I may have, inadvertently, forgotten.
Index
Open a 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 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.
Note: If your computer only has 'open powershell here' in the context menu. 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.
Test 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.
Note: If it does not return a version number type
Code:
adb reboot bootloader
and try
Code:
adb devices
again.
fastboot
Enable USB Debugging - Tap Settings > System > About Phone > Developer Options. Enable USB Debugging.
Open a Command Prompt on your computer.
Boot Bootloader
Connect the phone to the Computer with USB cord.
Type this at the prompt and press enter to test fastboot.
Code:
fastboot devices
It should return your device serial number.
Note: If it does not return a version number type
Code:
adb reboot bootloader
and try
Code:
fastboot devices
again.
Unlock Bootloader/Return Phone to Stock/Lock Bootloader
Unlock Bootloader
Backup your data and Internal storage
Activate Developer Options: Tap Settings > System > About Phone > Tap Build Number until you see you're a Developer. Tap back > Developer Options. Enable OEM Unlock and, USB Debugging.
Boot Bootloader
Connect the phone to the Computer with USB cord.
Open a Command Prompt on your computer and type
Code:
fastboot flashing unlock
and press enter.
This will erase all user data from the device!
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
Code:
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: Your device software can't be checked for corruption. Please lock the bootloader. You will see this warning until, you relock the bootloader.
Important: Do not relock your bootloader until you have returned the device to Stock..
Return Phone to Stock
Backup your data and Internal storage
Download the latest Factory Image
Extract factory Image to the platform-tools folder, or the folder that has fastboot in it.
Verify -w is present in flash-all.bat. Example: fastboot -w update image-marlin-aaa9.999999.999.zip
Note: This will erase all your Data and Internal Storage
Boot bootloader
Connect your phone to your Computer with a USB cable.
Open a Command Prompt:
Flash the Stock Factory Image on Both Slots
Type this at the Command Prompt:
Code:
flash-all
Let the phone boot.
Boot bootloader
Open Command Prompt:
Switch to the other slot.
Type this at the Command Prompt:
Code:
fastboot --set-active=other
Then type this at the Command Prompt:
Code:
flash-all
Let the phone boot.
Lock Bootloader
'B' must be completed before performing this step!
Boot bootloader
Open a Command Prompt and type this at the Prompt:
Code:
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:
Code:
fastboot reboot
Set up your phone.
Enable Developer Options: Settings > System > About phone > Tap Build number 7 times.
Tap Back > Developer options and toggle OEM unlocking to off.
Install Factory Image keep or wipe data
Important: When doing a major upgrade i.e., Android 7.x.x to Android 8.0.0/Android 8.1.0. I recommend wiping data.
Backup your data and Internal storage
Download the appropriate Factory Image: "marlin" for Pixel XL to your Computer.
Extract the factory Image to the platform-tools folder or the folder that has fastboot in it.
Keep Data
Open the folder you extracted the Factory Image to and Edit the flash-all.bat file to remove -w from this command: fastboot -w update image-marlin-aaa9.999999.999.zip
Note: If you do not remove the -w not only will your data be erased but also your internal storage will be erased.
Boot Bootloader
Connect the phone to the Computer with USB cord.
Open a Command Prompt on your computer.:
Type
Code:
flash-all
at the Command Prompt and press enter.
Do #7 or #8 to root/reroot
Wipe Data
Open the folder you extracted the Factory Image to and Verify the flash-all.bat file has the -w in this command: fastboot -w update image-marlin-aaa9.999999.999.zip
Note: This will erase your data and internal storage.
Boot Bootloader
Connect the phone to the Computer with USB cord.
Open a Command Prompt on your computer.:
Type
Code:
flash-all
at the Command Prompt and press enter.
Do #7 or #8 to root/reroot
ADB Sideload
Boot Recovery
-- On the Computer
Connect the phone to the Computer.
Open a Command Prompt.
-- On the Phone
Boot recovery
Tap Advanced > ADB Sideload.
Swipe the slider to start the ADB connection.
-- Sideload the ZIP
Copy and paste the Zip file you want sideload to the Platform-tools folder or the folder that 'adb.exe' is in.
At the Command Prompt type:
Code:
adb sideload <space> <file name>
Example: adb sideload example.zip
Press enter to begin the sideloading process.
When, you see a Reboot System button, tap it.
Extract/Flash boot.img
Extract boot.img
Use a File Explorer to extract the boot.img from the Factory Image.
Extract the Factory Image file (marlin-opm-9.999999.999-99a-factory-a9a9999.zip) to a folder.
Open the folder and, extract the Image file (image-marlin-aaa9.999999.999.99a.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 the platform-tools or to the folder that has fastboot in it.
Boot Bootloader
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
Root/Reroot with Magisk - Pass SafetyNet
Important: Set Pin before installing TWRP:
Settings > Security & location >Screen lock > Pin
Backup your data and Internal storage
Download files:
The files listed below are used with 7 and 8.
TWRP
TWRP 3.2.2-0 for Google Pixel XL
twrp-3.2.3-1-marlin.img - Download to your computer
twrp-pixel-installer-marlin-3.2.3-1.zip - Download to your phone
Magisk - Download to your phone
[2018.9.1] Magisk v17.1 - Root & Universal Systemless Interface [Android 5.0+] by topjohnwu
Magisk-uninstaller-20180901.zip - Post 1, Downloads
topjohnwu / Magisk
Custom kernels - Download to your phone
[KERNEL] [29 July] Pixel XL ElementalX 3.09 (8.1.0) 4.06 (P) by flar2
exNoShadez:. nine7nine/Apps
[*][MARLIN/SAILFISH] [8.1.0/9.0.0] [3.18.117] [CLANG 7.0] Flash Kernel 1.19 by nathanchance
[*][KERNEL][8.1.0][3.18.115] PureZ-Kernel-1.9 for Google Pixel XL [17/07/2018] by ZawZaw
[*]Boot Bootloader
[*]Connect the phone to the Computer with USB cord.
[*]Copy twrp-3.2.3-2-marlin.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:
Code:
fastboot boot twrp.img
and press enter.
[*]When TWRP boots, disconnect the phone from the computer.
[*]Tap Install select
twrp-pixel-installer-marlin-3.2.3-1.zip
[*]Swipe the slider to install
[*]After TWRP is installed
[*]Reboot Recovery (Tap the back button, Tap reboot, Tap recovery.)
[*]Install Custom Kernel and Root/Reroot (Optional)
Tap Install, select Custom Kernel:
ElementalX
ElementalX-P-3.09.zip
EX Kernel Manager by flar2
flashkernel-marlin-v1.19.zip
PureZ-Kernel-marlin-1.9.zip
Tap Add more Zips, select Magisk-v17.1(.zip - (Offical)
Swipe Slider to Install
Save Log
Reboot System
[*]Root/Reroot with Magisk
Tap Add more Zips, select Magisk-v17.1(.zip - (Offical)
Swipe Slider to Install
Save Log
Reboot System
[*]Install Modules - BusyBox, etc. (Optional)
Open Magisk Manager, tap Menu, tap downloads.
[*]Root/Reroot with Magisk - Pass SafetyNet without installing TWRP
Important: Set Pin before booting TWRP:
Settings > Security & location >Screen lock > Pin
Note: You might have noticed in the 'Install Custom kernel' section that some Custom kernels are installed before Magisk while others are installed after Magisk. The best answer I could find for when to flash a Custom Kernel when using Magisk for root is, if the Custom Kernel modifies/patches the boot image you install Magisk then the Custom Kernel otherwise you install the Custom Kernel then Magisk.
Backup your data and Internal storage
Download files:
See 'Download files' in #7 above - Do not download TWRP zip file.
Boot Bootloader
Connect the phone to the Computer with USB cord.
Open a Command Prompt on your computer.
Copy twrp-3.2.3-1-marlin.img to the platform-tools folder or the folder that fastboot is in and rename it twrp.img
Type
Code:
fastboot boot twrp.img
at the Command Prompt and press enter.
When TWRP boots, disconnect the phone from the computer.
Install Custom Kernel (Optional)
Yes
exNoShadez:. nine7nine/Apps
Tap Install, select Magisk-v17.1.zip - (Official)
Tap Add more Zips, select:
exns_eas_v3.8.1p_bca050b.zip
Or
(Stable) exNoShadez_eas_v2.8.2_f94351f.zip
Swipe Slider to Install
Save Log
Reboot System
ElementalX / Flash /PureZ
Tap Install, select Custom Kernel:
ElementalX-P-3.09.zip
EX Kernel Manager by flar2
flashkernel-marlin-v1.19.zip
PureZ-Kernel-marlin-1.9.zip
Tap Add more Zips, select Magisk-v17.1(.zip - (Offical)
Swipe Slider to Install
Save Log
Reboot System
No
Tap Add more Zips, select Magisk-v17.1(.zip - (Offical)
Swipe Slider to Install
Save Log
Reboot System
Install Modules - BusyBox, etc. (Optional)
Open Magisk Manager, tap Menu, tap downloads.
[*]Update Magisk
Important: "If you had the stable version or the official beta installed, you must first un-install the Magisk Manager, only, before you can install the unofficial version, because they are signed with different keys".
"The same holds true if, for example, you have @kantjer 's build installed and want to try @ianmacd 's builds". See kantjer and martyfender post: [UNOFFICIAL] next version Magisk and MagiskManager snapshots by stangri
Magisk Notification is on.
Turn on Magisk Manager update notification: Open MagiskManager > Tap menu icon > Settings > Update Channel > Select: Stable, Beta or Custom
Custom is used to get updates for Unofficial Magisk Builds.
When Magisk Manager notifies you of update availibility.
Tap install.
Select, Direct Install (Recommended)
When it finishes installing
Tap, Save Log
Tap, Reboot
Done!
Log location: /storage/emulated/0/MagiskManager/logs/install_log_...
Magisk Notification is off.
Open Magisk Manager
When asked 'Do you want to install Magisk-vxx.x.zip now?
Tap install.
Select, Direct Install (Recommended)
When it finishes installing
Tap, Save Log
Tap, Reboot
Done!
Log location: /storage/emulated/0/MagiskManager/logs/install_log_...
Unofficial Magisk Links and Channels
To set the Magisk Notification Update Channel for Unofficial Magisk Builds: Open MagiskManager > Tap menu icon > Settings > Update Channel > Select: Custom > Copy the link address below and paste it on the line:
ianmacd
Code:
https://raw.githubusercontent.com/ianmacd/MagiskBuilds/master/updates/ianmacd.json
kantjer
Code:
https://raw.githubusercontent.com/kantjer/MagiskFiles/master/updates/kantjer.json
topjohnwu has a new channel:
[DEV] Magisk Canary Channel - Bleeding Edge Builds by topjohnwu Please, read the OP for the URL.
When Magisk Manager notifies you of an update:
Tap install.
Select, Direct Install (Recommended)
When it finishes installing
Tap, Save Log
Tap, Reboot
Done!
Log location: /storage/emulated/0/MagiskManager/logs/install_log_...
[*][Magisk] Systemless Xposed v89.3/v90.1-beta3 (SDK 21-27)
Information only, see thread for instruction/use.
[2018.5.6][Magisk] Systemless Xposed v89.3/v90.2-beta3 (SDK 21-27) by*topjohnwu
[*]Custom ROMs for Pixel XL
Need help with a Custom ROM?
First, follow the Installation Instructions in the OP (Post 1) of the Custom ROM you want to install.
Second, if you have a problem Installing it, Search the thread of the Custom ROM you want to install for solutions to problem before posting a request for help on their thread.
Official
[ROM][Pixel-XL][8.1.0_r43] [OMS] Pixel Dust OREO for marlin [R8] by spezi77
pixeldust_marlin-oreo-release-eight-20180810.zip
[ROM][OPM4.171019.021.P1][07/21] Benzo Rom 8.1.0 OMS by xanaxdroid
benzorom-8.1.0-20180721-2013-marlin.zip
[ROM] [marlin] [8.1] [LOS-based] **crDroid**OMS**v4.7 (10/12/18) by hokiealumnus
crDroidAndroid-8.1-20181012-marlin-v4.7.zip
[ROM][OFFICIAL][8.1.0]FireHound-v4.8.1 For Google Pixel XL [Marlin] by NepoRood
FireHound-4.8.1-OFFICIAL-20180907-marlin.zip
[ROM][OFFICIAL]Resurrection Remix v6.0 [Android 8.1][05/20/18] by BDogg718
RR-O-v6.0.0-20180520-marlin-Official.zip
[8.1.x][OFFICIAL][WEEKLIES] CarbonROM | cr-6.1 [marlin] by shagbag913
CARBON-CR-6.1-NOCT-WEEKLY-marlin-20180529-1130.zip
[ROM]-[Official]-[10.07.18]-Havoc-OS-[8.1.0] by SKULSHADY
Havoc-OS-20180710-marlin-Official.zip
[ROM][OFFICIAL] lineage-15.1 for Pixels (sailfish/marlin) by razorloves.)
lineage-15.1-20180731-nightly-marlin-signed.zip
Unofficial
[ROM][UNOFFICIAL][7/29/18] AICP 13.1 by stebomurkn420
aicp_marlin_o-13.1-UNOFFICIAL-20180729.zip
[ROM] [8.1.0] BootleggersROM 2.3-STABLE [Unshishufied] by stebomurkn420
BootleggersROM-Oreo4marlin.2.3-Stable-Unshishufied-20180710.zip
AOSiP 8.1 *Flash Kernel* (Unofficial) by stebomurkn420
AOSiP-8.1-Derp-marlin-20180722.zip
[ROM][Unofficial][8.1.0] Resurrection Remix 6.1.0 by dylanneve1
RR-O-v6.1.0-20180818-marlin-Unofficial.zip
Android Devs
[*]Audio Mod
ViPER4Android, [MOD]Audio Modification Library , and Audio Compatibility Patch.
Note: Some, of there can be installed via 'Magisk Downloads'.
[*]Other: TWRP Backup/TWRP Update
TWRP Backup
Boot Recovery.
Tap Backup and select Partitions to backup
Boot
System Image
Vendor Image
Data (Optional)
EFS (Once per major upgrade)
Swipe Slider to backup
Your backup will be stored in /Storage/Emulated/0/TWRP/...
Note: If you are unable to make a backup to internal storage with trwp 3.2.2-0 try backing up to USB-OTG
Update TWRP
TWRP Installation Instructions:
"If you already have TWRP installed: Download the latest zip and install the zip using TWRP".
at #5 why do I need to wipe data if coming from 8.0.0? or is it just a precaution?
Papote3 said:
at #5 why do I need to wipe data if coming from 8.0.0? or is it just a precaution?
Click to expand...
Click to collapse
FWIW, I am on 8.1 from 8.0 Nov patch and did not factory reset, just flash-all with -w removed (actually I run each command in that file myself). Everything works fine and no data/app loss...
jk8260 said:
FWIW, I am on 8.1 from 8.0 Nov patch and did not factory reset, just flash-all with -w removed (actually I run each command in that file myself). Everything works fine and no data/app loss...
Click to expand...
Click to collapse
Yeah that's what I thought. I think he just writes it just as a precaution, in case anything goes wrong on 8.1, first factory reset and then write the problem if it still persist
Supersu or Magisk
Which rooting method is best for the Pixel XL. Supersu or Magisk
Update worked like a charm on my standard Pixel.
But somehow TWRP will not decrypt, keep asking for password even though I always had a pattern which worked flawlessly in TWRP. Any suggestions so I can get rooted again?
EDIT: After a few password attempts, removing the password altogether worked. When installing TWRP.zip the command window says E:This TWRP does not have synthetic password decrypt support, that must be why I had problems.
EDIT2: SuperSU does not seem to work
Juhler said:
Update worked like a charm on my standard Pixel.
But somehow TWRP will not decrypt, keep asking for password even though I always had a pattern which worked flawlessly in TWRP. Any suggestions so I can get rooted again?
EDIT: After a few password attempts, removing the password altogether worked. When installing TWRP.zip the command window says E:This TWRP does not have synthetic password decrypt support, that must be why I had problems.
EDIT2: SuperSU does not seem to work
Click to expand...
Click to collapse
Password Encryption isnt working on the new TWRP3.2.0 gotta wait for an update or remove passwords all together...
Juhler said:
Update worked like a charm on my standard Pixel.
But somehow TWRP will not decrypt, keep asking for password even though I always had a pattern which worked flawlessly in TWRP. Any suggestions so I can get rooted again?
EDIT: After a few password attempts, removing the password altogether worked. When installing TWRP.zip the command window says E:This TWRP does not have synthetic password decrypt support, that must be why I had problems.
EDIT2: SuperSU does not seem to work
Click to expand...
Click to collapse
Supersu wasn't even in my app drawer after flashing the zip so after rebooting I just went into the zip and installed the apk manually
Thank you for this thread....it worked. I did #9
Can confirm #10 works like a charm. Thanks for the separate thread. Both your guide threads should be stickies.
Just use adb sideload...
If you want to keep all your data, just sideload the OTA via adb, instead of flashing the full factory image...
My Steps:
1) Flash stock boot.img (November for me, I used TWRP)
2) Reboot recovery
3) Choose: Apply Update from ADB
4) adb sideload marlin-ota-opm1.171019.011-9e7f2bb8.zip
5) reboot system
6) set screen lock to "none"
7) copy twrp-pixel-installer-marlin-3.2.0-0.zip to your internal storage
8) reboot bootloader
9) fastboot twrp.img
10) Install: twrp-pixel-installer-marlin-3.2.0-0.zip
11) reboot recovery
12) Install: SR5-SuperSU-v2.82-SR5-20171001224502.zip
13) reboot system
14) profit!
If you knew this, great, if you didn't, you do now :good:
Regards,
Nepo
ekowwillis said:
Which rooting method is best for the Pixel XL. Supersu or Magisk
Click to expand...
Click to collapse
In my opinion Magisk.
NepoRood said:
If you want to keep all your data, just sideload the OTA via adb, instead of flashing the full factory image...
My Steps:
1) Flash stock boot.img (November for me, I used TWRP)
2) Reboot recovery
3) Choose: Apply Update from ADB
4) adb sideload marlin-ota-opm1.171019.011-9e7f2bb8.zip
5) reboot system
6) set screen lock to "none"
7) copy twrp-pixel-installer-marlin-3.2.0-0.zip to your internal storage
8) reboot bootloader
9) fastboot twrp.img
10) Install: twrp-pixel-installer-marlin-3.2.0-0.zip
11) reboot recovery
12) Install: SR5-SuperSU-v2.82-SR5-20171001224502.zip
13) reboot system
14) profit!
If you knew this, great, if you didn't, you do now :good:
Regards,
Nepo
Click to expand...
Click to collapse
Good Information!
Did you flash a Custom Kernel (ElementalX-P-3.00.zip) or UPDATE-suhide-v1.09-20171001222116.zip to pass SafetyNet?
Papote3 said:
Yeah that's what I thought. I think he just writes it just as a precaution, in case anything goes wrong on 8.1, first factory reset and then write the problem if it still persist
Click to expand...
Click to collapse
There are three reasons I recommend #4 - 'Wipe Data' prior to rooting:
a. I write all my guides with step by step instructions for noobs.
b. Some have reported data corruption when not doing #4 - 'Wipe Data'.
c. When upgrading the OS, I always start with a clean install.
If you want to upgrade without a clean installation that's ok too, but it is much easier to trouble shoot problems if you start with a clean installation.
Homeboy76 said:
Good Information!
Did you flash a Custom Kernel (ElementalX-P-3.00.zip) or UPDATE-suhide-v1.09-20171001222116.zip to pass SafetyNet?
Click to expand...
Click to collapse
I did not flash those, I have no real need for either...
Sent from my Pixel XL using XDA Labs
Everything went well up to "erasing userdata"..... its been stuck there for 5 min... any advice?
Cancel that....Just finished...
NepoRood said:
If you want to keep all your data, just sideload the OTA via adb, instead of flashing the full factory image...
My Steps:
1) Flash stock boot.img (November for me, I used TWRP)
2) Reboot recovery
3) Choose: Apply Update from ADB
4) adb sideload marlin-ota-opm1.171019.011-9e7f2bb8.zip
5) reboot system
6) set screen lock to "none"
7) copy twrp-pixel-installer-marlin-3.2.0-0.zip to your internal storage
8) reboot bootloader
9) fastboot twrp.img
10) Install: twrp-pixel-installer-marlin-3.2.0-0.zip
11) reboot recovery
12) Install: SR5-SuperSU-v2.82-SR5-20171001224502.zip
13) reboot system
14) profit!
If you knew this, great, if you didn't, you do now :good:
Regards,
Nepo
Click to expand...
Click to collapse
Thanks
Don't you need stock recovery to be able to apply OTA?
I don't see a step doing that, and I suppose you're on TWRP, or were you already on stock recovery?
If so, then better make that a clear step.
badabing2003 said:
Thanks
Don't you need stock recovery to be able to apply OTA?
I don't see a step doing that, and I suppose you're on TWRP, or were you already on stock recovery?
If so, then better make that a clear step.
Click to expand...
Click to collapse
That's covered with Step #1, friend
NepoRood said:
1) Flash stock boot.img (November for me, I used TWRP)
Click to expand...
Click to collapse
Since boot and recovery are on the same partition, flashing stock boot will give you stock recovery. I flashed my stock boot using TWRP, however, it can be flashed via fastboot as well.
AFAIK, this can be done for all updates (I've used this method since Oreo came out), it's just like taking the OTA from Gooble, you just download it yourself :good:
Regards,
Nepo
PS, I did flash full factory image when upgrading from Nougat to Oreo, just FYI
NepoRood said:
That's covered with Step #1, friend
Since boot and recovery are on the same partition, flashing stock boot will give you stock recovery. I flashed my stock boot using TWRP, however, it can be flashed via fastboot as well.
AFAIK, this can be done for all updates (I've used this method since Oreo came out), it's just like taking the OTA from Gooble, you just download it yourself :good:
Regards,
Nepo
PS, I did flash full factory image when upgrading from Nougat to Oreo, just FYI
Click to expand...
Click to collapse
Thanks for the clarification, didn't know that was the case.
I never flashed boot using twrp, would it do it for all slots, I guess it would.
Sent from my Pixel XL using Tapatalk
Is anyone getting this error?
Code:
wiping userdata...
/usr/local/bin/mke2fs failed with status 1
mke2fs failed: 1
error: Cannot generate image for userdata
I'm using the wipe option, but haven't ran into this one before.
My phone, the LeEco Le Pro 3 LEX727 ZL1_NA US model is on the latest EUI 5.8.021S. I am able to open the adb tools in command prompt and get my computer to recognize my phone with "adb devices", but when I go to the stock fastboot with the Chinese and English writing and use "fastboot devices" nothing shows up. I'm using the latest adb tools and am clueless as to what to do.
Unlock Bootloader - Le Eco Pro 3
If you are not seeing your phone ID in ADB
Did you enable enable Developer options, or chosen MTP?
Its possible that the Android driver driver is outdated, or just try another usb port, preferably in the back of the machine.
Go here to check a whole list of possible causes: https://appuals.com/android-phone-not-showing-up-on-pc/
More than you asked for:
Since you seem to be new to your Leeco phone and new to using custom roms, I am going to go ahead and answer your current question and provide you steps needed to move forward. No big deal, I just copy pasted my notes ( with a few edits)
First steps that you need to take:
1. You will first need to unlock the bootloader :
PHP:
https://forum.xda-developers.com/showpost.php?p=71566961&postcount=203
2. Install Twrp :
PHP:
https://twrp.me/leeco/leecolepro3.html
****** Scroll down to see: Fastboot Install Method (
3. Right now just use ADB. But for the future, I highly recommend that you buy an OTG drive: it makes the whole process a thousand times easier: They are cheap somewhere near $5 and worth ten times that
Unlocking the Bootloader
You can save your self alot of time by looking up how to give ADB system wide privileges: this will allow you to flash files without tying the directory path.
Mauronofrio created a tool called: "TOOL ALL IN ONE"" it's great, install it and check for updates.
PHP:
https://toolaio.tk
The all is one tool is excellent and you can use it to install everything if wanted.
I usually recommend it for novices that can use it to help with unlocking the bootloader and installing TWRP.
The tool will also update your copy of ADB, android Drivers and provide system wide privileges for ADB
LETS RECAP : Choose using the All in One Tool or the ADB Method
**********BEFORE DOING ANYTHING*******************
Make sure you have enabled the developer tools,
Turned on USB debugging
Authorized your computer on your device I.E: “MTP”
Make sure the All in One Tool can see your device
(*) Select your device from the drop down menu, then click check
(*) Choose to install drivers, and set ADB and fastboot privileges from advanced menu.
(*) First attempt to unlock, then check bootloader status
If you have a X727 you will need to flash : emmc_appsboot.mbn from this zip :
PHP:
https://androidfilehost.com/?fid=313042859668275431
Next, choose Recovery flasher and manually select your copy of TWRP
After you have received the success message, I recommend doing the rest of the install manually within Twrp Recovery.
(*) Reboot into TWRP and begin installation of your Rom, Gapps and Magisk.
Using the ADB Method
Install ADB/Fastboot tools on your computer
PHP:
https://wiki.lineageos.org/adb_fastboot_guide.html
1. Make sure you have enabled the developer tools,
2. Turned on USB debugging, and authorized your computer on your device “MTP”
3. Enter fastboot mode on phone (hold power and VOL -)
4. Make sure adb can see your device when you run "adb devices"
5. type: fastboot devices
6. fastboot flash aboot emmc_appsboot.mbn
7. Run { adb reboot bootloader } - No spaces (before/after)
8. Run { fastboot devices } to make sure you see your device
9. Run { fastboot oem unlock-go } to unlock your device temporarily
10. Run { fastboot oem device-info } to verify unlock status
11. Run { fastboot boot recovery_twrp-3.2.1-0-zl1.img }
12. 5. Reboot back to TWRP and begin installation of your Rom, Gapps and Magisk.
13. 6. If you wiped data, your device will now proceed to re-initialize itself as if from the factory
Concerning your device's storage,
When you boot into twrp you will see a message that states that the storage is encrypted.
*****************Important************************ ******************
Ensure that you have TWRP installed as the primary recovery
Ensure that you have TWRP installed as the primary recovery
Ensure that you have TWRP installed as the primary recovery
Ensure that you have TWRP installed as the primary recovery
To remove encryption you will need to format the storage
(Anyone who says otherwise has the X720 and not the X727)
You could also try to skip the formatting step. But you will very likely have permissions issues and get errors and you will eventually have to come back and format ( Again as long as Twrp recovery is install there is very slim chance of ever bricking your phone.
To format the storage
Go to Wipe, choose Format Data and follow the instructions.
This will erase all of photos , music, etc
If you wiped your data partition, you'll need to push the zip file to the newly formatted storage. - This is one BIG reason why using OTG is better. You can use Mauronofrio's "TOOL ALL IN ONE"" for pushing the ROM, Gapps, and Magisk to storage.
Root: You absolutely should root!
NOTE: If you have unlocked the bootloader and flashed TWRP to the recovery partition. But have not yet flashed a Custom Rom the OS will likely reset back to the factory recovery UNLESS YOU ROOT THE SYSTEM. Your device is still unlocked. But the recovery can be overwritten by the stock EUI system, so beware.
Installation of Rom, Gapps, Magisk
Boot into TWRP recovery
1. Go to "Wipe" and then to "Advanced Wipe".
2. Mark "Dalvik / ART Cache", "System", "Data" and "Cache".
3. "Swipe to Wipe" and proceed back the main menu.
4. Go to "Install".
5. Select the ROM zip file and then press "Add more Zips" and select the Gapps zip file, and then the Magisk file.
6. "Swipe to confirm Flash" and wait for some time.
7. After the flashing is finished, just reboot to system.
Finished!
If you need help or have a question message me, I would much rather help you with a successful install versus helping you unbrick your phone.
Thank you for your reply. I figured out the issue. Windows 10 updater wasn't auto installing the driver for some reason even though I have auto update ticked.
simpbrackets said:
Thank you for your reply. I figured out the issue. Windows 10 updater wasn't auto installing the driver for some reason even though I have auto update ticked.
Click to expand...
Click to collapse
You have manually install those drivers usually.
Sent from my LEX720 using xda premium
I have the same issue in Windows 10. All In One Tool sees my x720 in adb mode, but when I switch to bootloader, the phone is gone. Device manager then shows unrecognized android device. I have LTSB version of Windows, so maybe that's why it won't auto install the needed driver. Could anyone point out what kind of driver exactly do I need, so that I can install it manually?
[GUIDE/TUTORIAL/HOWTO] Xiaomi Redmi Note 4 Snapdragon stock to Android 12.1
[GUIDE/TUTORIAL/HOWTO] Xiaomi Redmi Note 4/4X Snapdragon SOC (codename mido) stock to Android 12 / LineageOS 19.1
Complete guide to install Android 12 on your Xiaomi Redmi Note 4 (Snapdragon or 4X).
This tutorial only applies to this model, to check the correct version:
in Android, go to Settings > About phone, make sure Device model is Redmi Note 4.
It must be Snapdragon: below Device model, CPU must be Octa-core Max 2.0Ghz
### If CPU is not Octa-core Max 2.0Ghz, you have the Mediatek version (codename Nikel), see here:
https://forum.xda-developers.com/f/xiaomi-redmi-note-4-mediatek-roms-kernels-reco.5784/
### If phone is not Redmi Note 4, quit this tutorial
CHANGELOG
v4. Minor improvements, Android 13 incoming (+ Google Camera) !
v3. Android 12.1 thanks to awesome Zeelog (and @anandsvm), migrate to MindTheGApps, upgrade TWRP
v2. BitGApps, updated TWRP + Magisk
v1. Initial release
1) WHAT YOU NEED
- djibe Redmi Note 4 pack: https://bit.ly/djibe-redminote4-pack
(contains all you need: USB drivers + Mi Unlock tool + fastboot & adb + TWRP Recovery 3.6.2_9-0 + Magisk root v23)
+ ROM LineageOS Unofficial 19.1: https://forum.xda-developers.com/t/...ineageos-18-1-mido-vanilla-by-zeelog.4186179/
Download latest build: https://github.com/zeelog/OTA/releases
+ MindTheGApps 12.1 ARM64: http://downloads.codefi.re/jdcteam/javelinanddart/gapps
or BitGApps ARM61 12.1 v1.4+: https://github.com/BiTGApps/BiTGApps-Release/releases
2) INSTALL DRIVERS
First uninstall all Oneplus, Oculus ... Android drivers.
Go to the folder you unzipped earlier.
navigate to usb_driver_r13-windows > usb_driver.
Right click on android_winusb.inf and select Install. Confirm with OK.
Restart Windows.
### If you experience problems with phone connection later, use https://github.com/lostindark/DriverStoreExplorer (thanks @Lysolus for sharing)
3) BACKUP YOUR DATA
Make sure Google/provider account is synchronized.
Backup photos, documents, contacts before going any further (ex: use the backupyourmobile app).
Connect phone to PC, search for all .jpg, .mp3, .mp4 files on your phone and retrieve data.
4) UNLOCK BOOTLOADER
### Before going further, you need the latest official firmware.
Go to Settings > About phone.
MIUI version must be 11.0.2.0 (NCFMIXM).
Unlock Developer settings:
Tap 7 times on MIUI version item.
If not: connect to Wifi, tap on System update > Check for updates.
### System won't update ? Download latest firmware from here: https://xiaomifirmwareupdater.com/firmware/mido/
MIUI Account
Insert your SIM card.
Enter Sim PIN and turn off wifi, turn on mobile data and sync.
Go to Settings > Mi Account
Enter your phone number adapted to prefix and create an account (if not yet done).
Make sure phone Mi Account is active, in Settings, besides Mi account is written an identifier.
Go to Settings > Additional settings > Developer options and scroll to Mi Unlock Status item.
Permission required, Agree
### Make sure Wifi is off and mobile data on, then tap on Add account and device, then Got it.
### As written, don't sign out of Mi account, perform factory reset or erase system data for now.
### Keep calm and carry on.
Now open the \Mi Unlock subfolder from my pack.
Launch miflash_unlock.exe ad administrator: right click on .exe > Run as administrator
Agree to terms.
Login to your Mi account (with phone number prefixed or email)
Confirm login with SMS verification.
### Alternative: Open this webpage from your PC: https://en.miui.com/unlock/
### Click on Unlock now, then Download Mi Unlock archive. Unzip and refer to previous steps.
Back to phone, turn it off.
Then hold Volume down + Power buttons until phone vibrates and displays Fastboot screen.
Connect phone to USB.
Back to PC, Mi Unlock now says "Phone connected".
Unlock button is available, click on it and confirm with Unlock anyway.
Wait until Unlocked successfully is displayed.
Click on Reboot phone.
Unlocked is written at the bottom of screen during boot.
### Need to quit Fastboot mode ? Hold Power until phone vibrates and restarts.
5) FLASH TWRP RECOVERY
Back to Android, go to Settings > Additional settings > Developer options,
switch OEM unlocking ON and USB debugging ON.
Connect phone to PC.
Open a Windows command prompt on the /flash subfolder folder you unziped earlier:
select folder with left click, right click while holding SHIFT on keyboard > Open command windows here
In command, enter
Code:
adb devices
Commands starts adb and returns: bfacf0c80104 unauthorized
On the phone, Allow USB debugging and send command again.
Command now returns: bfacf0c80104 device
Now enter
Code:
adb reboot bootloader
Phone restarts in bootloader/fastboot mode.
Enter
Code:
fastboot devices
Command returns: bfacf0c80104 fastboot
### If not, you may try to reinstall USB drivers or try another PC.
Now enter
Code:
fastboot flash recovery twrp-3.6.2_9-0-mido.img
Command returns: Finished. Total time: 1.540s
Now enter
Code:
fastboot boot twrp-3.6.2_9-0-mido.img
and wait while TWRP recovery boots.
TWRP asks: Decrypt data, tap on Cancel.
then Swipe to Allow Modifications.
Leave phone connected to PC.
We must remove encryption to access partitions.
From TWRP Home screen, go to Wipe > Format Data. This will remove all data on phone.
Type yes and confirm with bottom right icon.
6) BACKUP SYSTEM
Now go to Home screen > Backup.
Select System, Vendor, Boot, Bootloader, Firmware and EFS partitions.
Swipe to Backup and wait during Backup.
Back to Home > Mount.
Using Windows Explorer, access Redmi Note 4 and copy the TWRP folder from Internal Storage folder to somewhere safe.
Then copy LineageOS 19.1 and gapps.zip (+ magisk if you want root) to the same phone's Internal Storage folder.
### Copy both zip files straightforward. Don't unzip archives.
7) FLASH ANDROID 12.1
Once again Swipe to Allow Modifications.
Go to Install > lineage*.zip,
then Add more zips: mind*.zip.
### Optional: to flash Magisk root, go to Reboot > Recovery. Then Install > Magisk*.zip
Go to Reboot > System
8) ROOT ACCESS AND DEVELOPER MENU (OPTIONAL)
With Magisk, you are root once phone is started. No extra manipulation needed.
Superuser permissions can be managed from Magisk Manager app (it was flashed during Magisk flash. Or get it https://github.com/topjohnwu/Magisk/releases).
You can now remove install files from Internal storage.
For developer menu:
open the Settings menu, select "About Phone".
Tap on the "Build number" entry seven times. You should be notified, that the developer settings are now active.
Now go to Settings menu > System > Developer settings.
That's it.
Enjoy,
djibe
Thanks: Zeelog, @anandsvm, Aryan Kedare, @xtrymind @flex1911, LineageOS team, TWRP team, MindTheGApps team
Thanks for this... Will try it in 2-3 days
[email protected] said:
Thanks for this... Will try it in 2-3 days
Click to expand...
Click to collapse
Hi,
Any feedback is very welcome.
Normally you have all you need to hack it.
Enjoy
Will payment apps work after installing magisk? like Gpay, PhonePe
Also will it take 7 days to unlock bootloader?
[email protected] said:
Will payment apps work after installing magisk? like Gpay, PhonePe
Also will it take 7 days to unlock bootloader?
Click to expand...
Click to collapse
Hi, no idead for payment.
But MagiskHide normally does the trick.
Unlock bootloader is fast with all the tools in my pack.
[email protected] said:
Will payment apps work after installing magisk? like Gpay, PhonePe
Also will it take 7 days to unlock bootloader?
Click to expand...
Click to collapse
Root is optional.
Can't get majisk install after several times can't install it tried for super su but that too not installing in los 18.1
Jn1441 said:
Can't get majisk install after several times can't install it tried for super su but that too not installing in los 18.1
Click to expand...
Click to collapse
Hi, what is the error during flash in TWRP ?
Error1 displayed but after reflashing with mindgapps majisk is working now
Jn1441 said:
Error1 displayed but after reflashing with mindgapps majisk is working now
Click to expand...
Click to collapse
Cool, enjoy. The phone is still good
A very nice and clean tutorial, thanks for that!
I already unlocked bootloader with another tutorial and for now I will leave the device on the last stock firmware. But I already tested magisk. It's very new to me. The last phone I flashed is some years ago and I only knew SuperSU.
The Note 4 is only a "second device" and I won't use it as a daily driver. But it's fun to play around with it and test some things.
@djibe89 Good hint, that I have to use an older rom as an intermediate step to avoid problem, this is new to me.
Also I wondered when I looked up the partitions to backup. There are 15 (!?) partitions (Pics attached). You are writing, that following partitions have to be backed up: System, Vendor, Boot, Bootloader, Firmware and EFS partitions.
When I flash lineage and then want to go back, can I just restore the partitions? What happens to the other partitions when I flash a rom? Will they be deleted? Some years ago a phone just had 4 or 5 partitions...
Hi @tito_puente, you can start from step 7 to enjoy a clean Note 4.
Many thanks for the guide. Worked well. Can I remove Magisk to unroot or would I need to start Over?
the_real_grumpazoid said:
Many thanks for the guide. Worked well. Can I remove Magisk to unroot or would I need to start Over?
Click to expand...
Click to collapse
Hi, you can uninstall from the Magisk app
Installation
The Magic Mask for Android
topjohnwu.github.io
Great guide, Im new to flashing roms and this seems understandable. Is this usable for Xiaomi Redmi Note 4x (snapdragon)?
nysrin said:
Great guide, Im new to flashing roms and this seems understandable. Is this usable for Xiaomi Redmi Note 4x (snapdragon)?
Click to expand...
Click to collapse
Hi,
Yes.
Like written in the Title, it is for the snapdragon version, Aka 4X
Ooh i did not know the only difference between the note 4 and note 4x is that the 4x uses snapdragon.
The reason I was doubting is that I got a different device ID so I thought i my phone is a different model
List of devices attached
e640de900903 device
Click to expand...
Click to collapse
I will proceed later tonight, thank you for your quick response.
djibe89 said:
[GUIDE/TUTORIAL/HOWTO] Xiaomi Redmi Note 4 Snapdragon SOC (codename mido) stock to Android 11 R / LineageOS 18.1
Complete guide to install Android 11 on your Xiaomi Redmi Note 4 (Snapdragon).
This tutorial only applies to this model, to check the correct version:
in Android, go to Settings > About phone, make sure Device model is Redmi Note 4.
It must be Snapdragon: below Device model, CPU must be Octa-core Max 2.0Ghz
### If CPU is not Octa-core Max 2.0Ghz, you have the Mediatek version (codename Nikel), see here:
https://forum.xda-developers.com/f/xiaomi-redmi-note-4-mediatek-roms-kernels-reco.5784/
### If phone is not Redmi Note 4, quit this tutorial
CHANGELOG ----------------------------------------
v1. Initial release
1 ) WHAT YOU NEED
- djibe Redmi Note 4 pack: https://bit.ly/djibe-redminote4-pack
(contains all you need: USB drivers + Mi Unlock tool + fastboot & adb + TWRP Recovery 3.5.0_9-0 + OrangeFox recovery + Magisk root)
+ ROM LineageOS Unofficial 17.1: https://forum.xda-developers.com/t/ota-3-18-4-9-unofficial-lineageos-17-1-mido.4039907/
Download latest build: https://androidfilehost.com/?w=files&flid=309016&sort_by=date&sort_dir=DESC
Yes we need both LineageOS (LOS) ROMS !
+ ROM LineageOS Unofficial 18.1: https://forum.xda-developers.com/t/...ineageos-18-1-mido-vanilla-by-zeelog.4186179/
Download latest build: https://github.com/zeelog/OTA/releases
+ FlameGApps Basic: https://sourceforge.net/projects/flamegapps/files/arm64/android-11/BETA/
2 ) INSTALL DRIVERS
Go to the folder you unzipped earlier.
navigate to usb_driver_r13-windows > usb_driver.
Right click on android_winusb.inf and select Install. Confirm with OK.
Restart Windows.
3 ) BACKUP YOUR DATA
Make sure Google/provider account is synchronized.
Backup photos, documents, contacts before going any further (ex: use the backupyourmobile app).
Connect phone to PC, search for all .jpg, .mp3, .mp4 files on your phone and retrieve data.
4 ) UNLOCK BOOTLOADER
### Before going further, you need the latest official firmware.
Go to Settings > About phone.
MIUI version must be 11.0.2.0 (NCFMIXM).
Unlock Developer settings:
Tap 7 times on MIUI version item.
If not: connect to Wifi, tap on System update > Check for updates.
### System won't update ? Download latest firmware from here: https://xiaomifirmwareupdater.com/firmware/mido/
MIUI Account
Insert your SIM card.
Enter Sim PIN and turn off wifi, turn on mobile data and sync.
Go to Settings > Mi Account
Enter your phone number adapted to prefix and create an account (if not yet done).
Make sure phone Mi Account is active, in Settings, besides Mi account is written an identifier.
Go to Settings > Additional settings > Developer options and scroll to Mi Unlock Status item.
Permission required, Agree
### Make sure Wifi is off and mobile data on, then tap on Add account and device, then Got it.
### As written, don't sign out of Mi account, perform factory reset or erase system data for now.
### Keep calm and carry on.
Now open the \Mi Unlock subfolder from my pack.
Launch miflash_unlock.exe ad administrator: right click on .exe > Run as administrator
Agree to terms.
Login to your Mi account (with phone number prefixed or email)
Confirm login with SMS verification.
### Alternative: Open this webpage from your PC: https://en.miui.com/unlock/
### Click on Unlock now, then Download Mi Unlock archive. Unzip and refer to previous steps.
Back to phone, turn it off.
Then hold Volume down + Power buttons until phone vibrates and displays Fastboot screen.
Connect phone to USB.
Back to PC, Mi Unlock now says "Phone connected".
Unlock button is available, click on it and confirm with Unlock anyway.
Wait until Unlocked successfully is displayed.
Click on Reboot phone.
Unlocked is written at the bottom of screen during boot.
### Need to quit Fastboot mode ? Hold Power until phone vibrates and restarts.
5 ) FLASH TWRP RECOVERY
Back to Android, go to Settings > Additional settings > Developer options,
switch OEM unlocking ON and USB debugging ON.
Connect phone to PC.
Open a Windows command prompt on the /flash subfolder folder you unziped earlier:
select folder with left click, right click while holding SHIFT on keyboard > Open command windows here
In command, enter
Code:
adb devices
Commands starts adb and returns: bfacf0c80104 unauthorized
On the phone, Allow USB debugging and send command again.
Command now returns: bfacf0c80104 device
Now enter
Code:
adb reboot bootloader
Phone restarts in bootloader/fastboot mode.
Enter
Code:
fastboot devices
Command returns: bfacf0c80104 fastboot
### If not, you may try to reinstall USB drivers or try another PC.
Now enter
Code:
fastboot flash recovery twrp-3.5.0_9-0-mido.img
Command returns: Finished. Total time: 1.540s
Now enter
Code:
fastboot boot twrp-3.5.0_9-0-mido.img
and wait while TWRP recovery boots.
TWRP asks: Decrypt data, tap on Cancel.
then Swipe to Allow Modifications.
Leave phone connected to PC.
We must remove encryption to access partitions.
From TWRP Home screen, go to Wipe > Format Data. This will remove all data on phone.
Type yes and confirm with bottom right icon.
6 ) BACKUP SYSTEM
Now go to Home screen > Backup.
Select System, Vendor, Boot, Bootloader, Firmware and EFS partitions.
Swipe to Backup and wait during Backup.
Back to Home > Mount.
Using Windows Explorer, access Redmi Note 4 and copy the TWRP folder from Internal Storage folder to somewhere safe.
Then copy OrangeFox and LineageOS 17.1 to the same phone's Internal Storage folder.
7 ) FLASH ORANGEFOX RECOVERY
Now go to Home screen > Install
Select OrangeFox*.zip and Swipe to confirm Flash, recovery will auto-reboot.
8 ) FLASH LINEAGEOS 17.1
Coming from Android 7, we need to flash Android 10 to prevent bugs with fingerprint or bootloops...
Once again Swipe to Allow Modifications.
On bottom navigation bar, tap on Files.
Then select lineage-17.1*.zip and Swipe to Install.
Then tap on Wipe Caches > Swipe to wipe,
then Reboot System.
Wait during boot.
Quickly setup Android and try to skip configs.
Once finished, turn phone off.
9 ) FLASH LINEAGEOS 18.1
Boot in Recovery mode:
Hold Power + Volume+ until Mi logo shows up and release buttons.
Wait during OrangeFox recovery boot.
On bottom navigation bar, tap on Wipe.
Select Dalvik/ART cache, Cache, System, Data and Vendor partitions,
then Swipe to Wipe.
Back to Home > Menu (right icon of navigation bar) > Mount
Copy lineage-18.1*.zip, FlameGApps, Magisk*.zip and Magisk Manager*.apk on Internal Storage.
Then back to Files menu (left item of navigation bar).
Tap in lineage > Add to Queue > Magisk > Add to Queue > FlameGApps and Swipe to Install.
When flash is over > Wipe Caches and Reboot System.
10 ) ROOT ACCESS AND DEVELOPER MENU
With Magisk, you are root once phone is started. No extra manipulation needed.
Superuser permissions can be managed from Magisk Manager app (it was flashed during Magisk flash. Or get it https://github.com/topjohnwu/Magisk/releases).
You can now remove install files from Internal storage.
For developer menu:
open the Settings menu, select "About Phone".
Tap on the "Build number" entry seven times. You should be notified, that the developer settings are now active.
Now go to Settings menu > System > Developer settings.
That's it.
Enjoy,
djibe
Thanks: anandsvm, Zeelog, Aryan Kedare, @xtrymind @flex1911, LineageOS team, TWRP team, OrangeFox recovery team
Click to expand...
Click to collapse
Hi @syzw,
Can you reinstall USB drivers in Administrator mode ?
Or try another computer ?
djibe89 said:
Hi @syzw,
Can you reinstall USB drivers in Administrator mode ?
Or try another computer ?
Click to expand...
Click to collapse
I updated USB drivers in device manager of PC.
Now I am enjoying A11.
Thanks.
READ THIS WHOLE THING BEFORE STARTING. THERE ARE SEVERAL WARNINGS.
Flash eu firmware using msmtool mod (https://www.xda-developers.com/t-mobile-oneplus-8t-rebrand-without-bootloader-unlocking/) (if msmtool doesn’t work make sure windows is in test mode with proper qualcomm drivers) (if your device bootloops and you can’t recover it just flash it again with msmtool, power it off and power it back on holding both volume up and down) Recommended to use Command Prompt commands instead of powershell (type cmd in platform-tools directory) https://developer.android.com/studio/releases/platform-tools
Unlock oem bootloader
Enable developer options (click build number several times)(make sure you’re connected to internet)
Enable oem unlocking, advanced reboot, usb debugging
Reboot to bootloader/fastboot
fastboot oem unlock
Unlock bootloader
Boot back into oos, (repeat steps I. ii. And iii.) or (boot directly into fastboot by holding volume down while
booting)
Flash boot, dtbo, and recovery (https://mirror.math.princeton.edu/pub/lineageos/full/kebab/20220818/)
fastboot flash boot (path to boot.img)
fastboot flash dtbo (path to dtbo.img)
fastboot flash recovery (path to recovery.img)
Download firmware (https://kremowka.xyz/files/8fw/)
Enter recovery mode, enter fastbootd
Advanced > enter fastboot
Follow https://wiki.lineageos.org/devices/kebab/fw_update to flash it, and without rebooting sideload
LineageOS 19.1, sideload mindthegapps, then reboot. https://wiki.lineageos.org/devices/kebab/install fits in
there somewhere
Open notepad, copy commands from lineage, save as (file name).bat, drag into powershell from file explorer
(flash ram separately for safety) I named mine “flashfirmwareforoneplus8t.bat”
Be careful with ddr4 vs 5. do not brick your phone. Ddr4x is ddr4 for these purposes.
Without rebooting, enter recovery > apply update > apply from adb (it should say version 18.1 in the top left)
adb devices (to confirm phone is connected properly and device drivers are configured properly)
adb sideload (path to lineage 19.1 .zip)
Sideload will likely get stuck at 47%. This is normal. Just wait.
Volume up to go to back arrow, advanced, reboot to recovery (make sure it says version 19.1 now)
adb sideload (path to mindthegapps .zip) note that most gapps packages will not install properly as they are
too large. Just download them all from google play store once booted.
Signature verification failed will pop up, just confirm “yes”
Reboot recovery?
adb sideload (path to copy partitions .zip)
Back > Reboot system now
It may say “can’t load android system your data may be corrupt” just factory data reset it’s fine unless you have
data you want to keep then you’ll have to google it, I don’t know how to recover that and you should’ve done
that before this step (do it in fastboot, search up adb shell pull)
If the start page has clouds and blue then good job you loaded gapps properly. If it’s not then something
happened.
OPTIONAL (if you want magisk/root)
Go into settings, enable developer options (tap build number repeatedly) make sure usb debugging is on
Search in settings for “advanced”, click “advanced restart” and enable
Hold power button, restart, recovery
Apply update > apply from adb
adb devices
adb sideload (path to magisk .apk)
Signature verification failed, install anyway
Volume up to go to back arrow, reboot system now
Boot into device, reboot, magisk should appear, click on it and click accept on whatever it prompts
Open magisk, do whatever it prompts. To install a file, drag whatever module .zip you want in, make sure file
transfer is on
DO NOT USE ACC OR ACCA (battery manager) FROM F-DROID IT SOFT BRICKED MY PHONE
What I use: Safetynet universal fix and raven.A12L (spoofs as pixel 6 pro to let safetynet work)
Install from storage
Order I did it in was safetynet then raven, rebooting between each one but I'm not sure if it matters
Install safetynetfix, then go into settings, click zygisk, click enforce denylist, click 3 dots, show system apps, click
google play services, google play store, and carrier services (the square check box next to the name, make sure
every check below when you open it as a dropdown menu is checked
Reboot phone
Now you can download whatever you want
If you install twrp, make sure you are using android 12 version and not android 11, android 11 twrp will destroy
your recovery if you try to use it on android 12.
Add on: If your phone is not detected by your pc, or is detected as “MTP” with an exclamation mark, you do not
have the right drivers. There are plenty of resources online to fix this, but one that I had trouble with was that I
was on windows 10 N instead of whatever the other version is, which doesn’t come with “mediafeaturepack.”
You need to install that on your own from https://www.microsoft.com/en-us/software
download/mediafeaturepack, or, if your device isn’t listed, go to windows application “optional features” and
add it from there.
If your computer won’t download qdloader 9008 qualcomm drivers through device manager, there are a few
things i’ve tried to fix it. Make sure you have correct drivers
from https://www.catalog.update.microsoft.com/Search.aspx?q=qualcomm hs usb 9008
“The system cannot find the file specified”
Open command prompt as administrator
Type DISM /Online /Add-Package /PackagePath:"Full path of .cab file"
I put mine in C: drive folder but I'm not sure it matters
Also I'm not sure which one of the three I downloaded from the website. Did not cause any issue downloading
and trying to install all three, let me know if you figure out which one works. Maybe you need all three, I don’t
know.
If that doesn’t work, do sfc /scannow
Open windows update, make sure all updates are applied and restart windows (make sure you go to optional
updates and select qualcomm drivers)
Fastboot won’t connect
Make sure you’re using a usb 2.0 port instead of a usb 3.0 port, and make sure your usb cable is a data cable.
Google the difference if you don’t know what it is. Download usb drivers
from https://developer.android.com/studio/run/win-usb, open device manager, see if anything is there, if it
shows something in “other devices” click on it, click update drivers, browse my computer, let me pick, have disk,
and then browse to android_winusb.inf and click update, click bootloader interface. If you get “error 10 device
won’t start” when installing bootloader interface, one possible solution is to disable driver signing.
Open command prompt as an administrator (doesn’t have to be in platform tools directory)
bcedit /set testsigning on
Reboot, try to install driver again.
If your device is bootlooping, and you enter fastboot after updating to a12 firmware AND you have magisk\
modules downloaded AND you have twrp installed, do not press the up volume button, only cycle through
options with volume down, because it may enter an option cycle and you won’t be able to do anything unless
you fastboot flash boot twrp.img.
It’s recommended that as soon as you root, you backup persist.img, which contains imei info (you don’t want
that to get destroyed) I am unsure if there’s anything else device specific you need to backup, I've heard
vendor_image may be but it’d not as important as persist.
To backup persist.img, put phone in recovery, type in command prompt or powershell
adb shell dd if=/dev/block/bootdevice/by-name/persist of=/tmp/persist.img
adb pull /tmp/persist.img persist.img
This should save persist.img to your computer. Back it up somewhere you keep important things. Also don’t
give it out at random as it contains your imei number, not sure what the consequences of that could be but
nothing good is likely to come of it.
Important shortcuts:
Power + vol up – boot into system
Power + vol down – boot into fastboot
Power + vol up + vol down – boot into edl
IF DEVICE IS BOOTLOOPING AND YOU CAN’T ENTER ANY DIFFERENT MODES, CONTINUE HOLDING POWER +
VOL DOWN IN RANDOM PATTERNS. IT HAS TAKEN ME 20 MINUTES OF RANDOM BUTTON COMBINATIONS TO
GET INTO FASTBOOT FROM A BOOTLOOP. YOU WILL ALWAYS BE ABLE TO EXIT A BOOTLOOP IF YOUR PHONE
IS PHYSICALLY UNDAMAGED.
If VoWifi doesn’t work, pixelify dialer can get it working. Probably also just any custom dialer, but I like Google
dialer. Wait for the interface to change slightly, don’t clear data until you’ve waited at least a minute or two and
closed and reopened it a few times, but if it doesn’t change after installing pixelify then force close, clear data,
and wait a minute or two, reopen, and then wait. If it continuously doesn’t change you can reflash pixelify.
Note – If using pixelify module, disable auto update for android system intelligence, it will break gboard
translate and possibly slow down device.
You can also use magisk module “mindetach” to detach com.google.android.as from play store, which will fix
any auto update bugs. Credit to vewu for showing me that
https://github.com/j-hc/mindetach-magisk
https://github.com/Pixel-Props/raven/releases
https://github.com/kdrag0n/safetynet-fix
Dm me on here if you have any questions. I am not a dev, I learned these steps from others in the community.
Shoutout pizzalovingnerd, Luk1337, raven, poang, and nvcore for helping me out a lot.
Apologies for formatting, this is copied from a word doc. Please feel free to indent and number list yourself and
send me a better version
Does the third option work?
INTseed said:
Does the third option work?
Click to expand...
Click to collapse
did you configure the denylist? try clearing cache and data for google play services, google play store, and carrier services and rebooting
Mrmcfeffers said:
READ THIS WHOLE THING BEFORE STARTING. THERE ARE SEVERAL WARNINGS.
Flash eu firmware using msmtool mod (https://www.xda-developers.com/t-mobile-oneplus-8t-rebrand-without-bootloader-unlocking/) (if msmtool doesn’t work make sure windows is in test mode with proper qualcomm drivers) (if your device bootloops and you can’t recover it just flash it again with msmtool, power it off and power it back on holding both volume up and down)
a. Unlock oem bootloader
i. Enable developer options (click build number several times)(make sure you’re connected to internet)
ii. Enable oem unlocking, advanced reboot, usb debugging
iii. Reboot to bootloader/fastboot
iv. .\fastboot oem unlock
v. Unlock bootloader
b. Boot back into oos, (repeat steps I. ii. And iii.) or (boot directly into fastboot by holding
volume down while booting)
2. Flash boot, dtbo, and recovery (https://mirror.math.princeton.edu/pub/lineageos/full/kebab/20220818/)
a. .\fastboot flash boot (path to boot.img)
b. .\fastboot flash dtbo (path to dtbo.img)
c. .\fastboot flash recovery (path to recovery.img)
3. Download firmware (https://kremowka.xyz/files/8fw/)
4. Enter recovery mode, enter fastbootd
a. Advanced > enter fastboot
5. Follow https://wiki.lineageos.org/devices/kebab/fw_update to flash it, and without rebooting sideload LineageOS 19.1, sideload mindthegapps, then reboot. https://wiki.lineageos.org/devices/kebab/install fits in there somewhere
a. Open notepad, copy commands from lineage, add .\ before each line, save as (file name).bat, drag into powershell from file explorer (flash ram separately for safety) I named mine “flashfirmwareforoneplus8t.bat”
b. Be careful with ddr4 vs 5. do not brick your phone. Ddr4x is ddr4 for these purposes.
c. Without rebooting, enter recovery > apply update > apply from adb (it should say version 18.1 in the top left)
i. .\adb devices (to confirm phone is connected properly and device drivers are configured properly)
ii. .\adb sideload (path to lineage 19.1 .zip)
Sideload will likely get stuck at 47%. This is normal. Just wait.
d. Volume up to go to back arrow, advanced, reboot to recovery (make sure it says version 19.1 now)
i. .\adb sideload (path to mindthegapps .zip) note that most gapps packages will not install properly as they are too large. Just download them all from google play store once booted.
Signature verification failed will pop up, just confirm “yes”
e. Reboot recovery?
i. .\adb sideload (path to copy partitions .zip)
6. Back > Reboot system now
a. It may say “can’t load android system your data may be corrupt” just factory data reset it’s fine unless you have data you want to keep then you’ll have to google it, I don’t know how to recover that and you should’ve done that before this step (do it in fastboot, search up adb shell pull)
7. If the start page has clouds and blue then good job you loaded gapps properly. If it’s not then something happened.
8. OPTIONAL (if you want magisk/root)
9. Go into settings, enable developer options (tap build number repeatedly) make sure usb debugging is on
a. Search in settings for “advanced”, click “advanced restart” and enable
b. Hold power button, restart, recovery
10. Apply update > apply from adb
a. .\adb devices
b. .\adb sideload (path to magisk .apk)
i. Signature verification failed, install anyway
ii. Volume up to go to back arrow, reboot system now
11. Boot into device, reboot, magisk should appear, click on it and click accept on whatever it prompts
a. Open magisk, do whatever it prompts. To install a file, drag whatever module .zip you want in, make sure file transfer is on
12. DO NOT USE ACC OR ACCA (battery manager) FROM F-DROID IT SOFT BRICKED MY PHONE
a. What I use: Safetynet universal fix, disableflagsecure (lets you screenshot netflix lol), and raven.A12L (spoofs as pixel 6 pro to let safetynet work)
i. Install from storage
ii. Order I did it in was safetynet, then raven, then flag secure rebooting between each one but I'm not sure if it matters
b. Install safetynetfix, then go into settings, click zygisk, click enforce denylist, click 3 dots, show system apps, click google play services, google play store, and carrier services (the square check box next to the name, make sure every check below when you open it as a dropdown menu is checked
c. Reboot phone
13. Now you can download whatever you want
https://github.com/Pixel-Props/raven/releases
https://github.com/kdrag0n/safetynet-fix
https://forum.xda-developers.com/t/disable-flag-secure-magisk-module-v3-0-by-mehedi-hjoy.4490475/
Dm me on here if you have any questions. I am not a dev, I learned these steps from others in the community. Shoutout pizzalovingnerd, Luk1337, raven, poang, and nvcore for helping me out a lot.
Apologies for the ****ty formatting, i copied this from a word document. I don't know how to paste the indents.
Click to expand...
Click to collapse
How can you claim this 'works on locked bootloader', when right at your ( 2) you say 'unlock bootloader'. And if your instructions require unlocked bootloader (which they surely do), then they are useless, because once your bootloader is unlocked, you can simply flash Magisk with recovery.
optimumpro said:
How can you claim this 'works on locked bootloader', when right at your ( 2) you say 'unlock bootloader'. And if your instructions require unlocked bootloader (which they surely do), then they are useless, because once your bootloader is unlocked, you can simply flash Magisk with recovery.
Click to expand...
Click to collapse
modded msm tool allows bootloader unlocking
Mrmcfeffers said:
modded msm tool allows bootloader unlocking
Click to expand...
Click to collapse
What does this have to do with your 'working on locked bootloader'? That statement is false. You can't flash anything on locked bootloader, and if you unlock bootloader, then you can simply flash Magisk via recovery without the need for your 'method'.
optimumpro said:
What does this have to do with your 'working on locked bootloader'? That statement is false. You can't flash anything on locked bootloader, and if you unlock bootloader, then you can simply flash Magisk via recovery without the need for your 'method'.
Click to expand...
Click to collapse
seems to have worked for me. i meant "working on locked bootloader" as in it include steps to unlock. it's also a guide to installing lineage, not just magisk. i'm not sure what issue you have here, it's a specific tutorial for a specific problem.
Mrmcfeffers said:
seems to have worked for me. i meant "working on locked bootloader" as in it include steps to unlock. it's also a guide to installing lineage, not just magisk. i'm not sure what issue you have here, it's a specific tutorial for a specific problem.
Click to expand...
Click to collapse
It's just a decription in thread name that is a bit misleading.
At first it appears like it can be done on locked bootloader.
And it's obviously not, as stated in your instruction point #2.
Otherwise, nice tutorial.
Mrmcfeffers said:
DO NOT USE ACC OR ACCA (battery manager) FROM F-DROID IT SOFT BRICKED MY PHONE
Click to expand...
Click to collapse
So is acc incompatible with this device? Or is this a warning only at that step in the tutorial?
jinncarry said:
So is acc incompatible with this device? Or is this a warning only at that step in the tutorial?
Click to expand...
Click to collapse
Don't use acca from f-droid. Acc from the official GitHub (https://github.com/VR-25/acc) is fine and works perfectly