OnePlus 5T: Unlock Bootloader | Flash TWRP | Root | Nandroid & EFS Backup & More !! - OnePlus 5T Guides, News, & Discussion

OnePlus 5T: Unlock Bootloader | Flash TWRP | Root | Nandroid & EFS Backup & More !!
OnePlus 5T: Unlock Bootloader | Flash TWRP | Root | Nandroid & EFS Backup & More !!​
{
"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"
}
Before you start, OTA up to the latest System Update available.
Settings > System Updates > Download & Install the latest available
Thank You all for your support :highfive:
Never Settle :fingers-crossed:​

Introduction​​
Rooting this device is actually quite a simple and easy process. Before you begin, it is recommended that you at least try to understand what each part of the process will do. Although this guide will elongate each step in order to show all of the details, the method used can be broken up into 3 main steps: ​
1. Unlocking the Bootloader
2. Installing a Custom Recovery
3. Gaining Root Access
Each new step relies on the previous step so please follow the entire process and a basic summary of each part is described as below:
Unlocking Bootloader​​Opens the door to the internal memory of the device to be written on to. This allows you to flash images onto the main partitions of the phone.​
Installing a Custom Recovery​​A custom recovery is flashed onto the recovery partition of the device and overwrites the stock recovery that exists by default. Custom recoveries bring lots of functionality and give you the ability to perform wipes, install flashable zips, create full backups of your device (Nandroid backup), and various other features. An unlocked bootloader is needed to install a custom recovery.
Gaining Root Access​​You can gain root by either flashing via recovery a pre-rooted custom rom, or flashing a zip containing the SuperSU binaries or by Flashing Magisk Zip for a system less root. A custom recovery is necessary to do this.
After completing these steps your phone will be rooted, the phone will have a custom recovery installed and an unlocked bootloader. This, in my opinion, is the a practical and beneficial method for rooting your phone. It will give you some basic adb/fastboot knowledge, and should hopefully help you have a decent understanding of the entire process. This method will work regardless of any android version on the phone.
If you are confused by anything in this guide, I highly suggest getting it clarified being before moving on. Ask your question in this thread and I or someone else will likely answer. Also we would suggest that you read over the whole thread a few times before actually doing anything to the phone.​

Setup, Preparation & Prerequisites​​
Basic tasks that may be referred to throughout this guide:​​Open Command Prompt: Press Shift + Right Click anywhere on the screen and select Open Command Window here
Enter Fastboot/Bootloader Mode: Turn the phone off. Hold volume up + power until the "fastboot" screen appears. [Alternatively, if Advanced Reboot is enabled, you can press Reboot > Bootloader from the power menu.]
Enter Recovery Mode: Turn the phone off. Hold volume down + power until the "OnePlus Logo" screen appears. [Alternatively, if Advanced Reboot is enabled, you can press Reboot -> Recovery from the power menu.]
ADB and Fastboot Installation​1. Download the ADB For Windows here Or Manually update Fastboot and ADB binaries from Here or Here
2. Run the .exe file downloaded from above as Administrator.
3. Press 'Y' every time the installer asks for.
4. Continue Driver Installation.
Now, ADB and Fastboot have been installed on your PC and should be Working as desired.
Things To Remember​Show File Extensions :good:
Open a command prompt window and run "Control folders" (without the quotes). Go to the View tab and uncheck the "Hide extensions for known file types" option. This will help avoid confusion when renaming files.
Battery :good:
Ensure that your phone has at least 60% battery remaining, and that your PC is plugged in and wont shut down spontaneously during the process. The procedure doesn't take very long , but its best to have enough charge in case something goes wrong.
Backup (Optional) :good:
Unlocking the bootloader will/should completely wipe all data from the device. This includes apps, settings and even the contents of the internal sdcard (pictures, music, etc.). Copy all important files off the phone onto a PC or upload them to a cloud.
USB Debugging :good:
On your phone go to Settings > About phone > Tap on Build number 7 times. This will enable Developer options. Now go back to Settings > Developer options > Enable USB debugging
Enable OEM Unlocking :good:
On your phone go to Settings > Developer options. Then enable the 'OEM Unlocking' option. Also make sure that from now on, OEM unlocking option is enabled before you reboot as sometimes, it might get disabled itself.
Enable Advanced Reboot :good:
On your phone go to Settings > Developer options. Then enable the 'Advanced Reboot' option.

Unlocking Bootloader​
Turn the phone off. Then boot it into fastboot mode by holding volume up + power or select reboot to bootloader if advanced reboot is activated via developer options. The phone will display "fastboot" text indicating that it has successfully entered fastboot mode.
Plug the phone into your PC, then open a command prompt window on the desktop (Shift + Right Click -> Open Command Window here) and type:
Code:
fastboot devices
This command will list the connected devices. If your phones serial number shows up you are good to go and may continue. If the phone is NOT listed this indicates that your drivers are not installed correctly. In order for you to continue you must fix your drivers so that your phone is listed under fastboot devices.
If the phone has been recognized by the command above, proceed to unlocking the bootloader with the following command:
Remember this Step will WIPE EVERYTHING off the phone so Backup all your Data
Code:
fastboot oem unlock
You would be greeted with a Unlock Bootloader Warning page, Hit the Vol button to select Yes and turn it Blue and Hit the Power Button to Execute the selection
Your device will reboot, show you a Secure boot warning, reboot into stock recovery and wipe all data. Once done, your phone will reboot into the OS.
Please continue and follow the next post to install Custom Recovery

Flashing TWRP Recovery​
Downloads:
Codeworkx TWRP | Blu_Spark
Magisk​
Wait until the phone has fully booted up into android, then adjust the following settings on the phone:
USB Debugging
On your phone go to Settings > About phone > Tap on Build number 7 times. This will enable Developer options. Now go back to Settings > Developer options > Enable USB debugging
Enable OEM Unlocking
On your phone go to Settings > Developer options. Then enable the 'OEM Unlocking' option and make sure that from now on, OEM unlocking option is enabled before you reboot. Sometimes, it might get disabled itself.
Enable Advanced Reboot
On your phone go to Settings > Developer options. Then enable the 'Advanced Reboot' option.
Download all the files, place SuperSU or Magisk on Device Internal Memory and TWRP img on your PC
Then boot it into fastboot/bootloader mode by holding volume up + power or selecting the reboot to bootloader via advanced reboot options.
Open a new command prompt in the same location and run the following commands:
Code:
fastboot flash recovery (file name).img
Once the flash has completed, Don't use the "Fastboot Reboot" Command Instead Unplug Your phone then Manually boot it into recovery by pressing the Vol Button for a couple of times till you see recovery in red at the top and then hit the power button to reboot
Alternatively you can also use the command:
Code:
fastboot boot recovery.img
PS: DO NOT BOOT IN OS JUST YET & CONTINUE TO THE ROOTING POST

Gaining Root Access​
This is a continued post from the above post...
1. Boot into TWRP Recovery
2. If you want to stay systemless continue without swiping right else Swipe and enable modifications.
3. Select your preferred Language, Tap “Never show this screen on boot again,” and Swipe allow modification.
4. Navigate to Install and select SuperSU Beta Or Magisk Beta to root OnePlus 5T.
5. Swipe to confirm the flash
6. Reboot System
Keep in mind that the first boot after wiping the phone may take longer than usual, as the phone will need to rebuild the dalvik cache and initialize other first boot and would reboot a few times due to SuperSU Flash.
* MTP, known as Media Transfer Protocol, is the same way you transfer files from your PC to your device when booted into system.
Congrats! Your Device now has an unlocked bootloader, a custom recovery installed and is rooted !!
Warning: Do not flash partial update OTAs (under 1 GB) on a modified device! If you want to use partial OTAs, you must first flash a full OTA that it applies to, and then flash the partial OTA from stock recovery. Flashing partial OTAs from TWRP will either fail or soft brick your device. You can return to a usable state by flashing full zips in recovery.
Enjoy :fingers-crossed:

Making a Nandroid Backup​
Warning: before you make a backup with TWRP you must remove all Lockscreen Security. If you do not do this you will not be able to unlock your device after restoring your backup (entering your pin/pattern/password will result in an "incorrect pin/pattern/password" message), you'll be forced to perform a factory reset to boot into Android.
To remove lockscreen security go to
Settings > Security > Screen Lock and set it to Swipe/None.
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 Nandroid Bckup to create a backup of your favorite ROM set up exactly the way you like it. The backup you create can be easily restored using the restore tool in TWRP recovery.
To Create Nandroid Backup:
1. Boot into TWRP Recovery .
2. Go to Backup Menu and select all the listed partitions.
3. Name the Backup if needed (Optional)
4. Swipe to take Backup.
This proces should take 4 to 8 minutes depending upon the size of data.
5. Reboot System when done.
Your Nandroid will be stored in the Backup Folder inside TWRP Folder /sdcard/TWRP/BACKUPS

Restoring a Nandroid Backup​
1. Boot into TWRP Recovery
2. Go to Restore Menu and select the backup you want to restore.
3. Select the partitions you want to restore.
4. Swipe to Restore. The process will take 6 to 10 minutes.
5. Reboot system once done
Note: If you happened to forget to remove lockscreen security (PIN/Pattern/Password) before creating your backup, and you cannot get into your OS after restoring, you can do the following to fix the issue.
Boot into TWRP
Use the TWRP File Manager and Navigate to /data/sytem/ and delete the following files:
locksettings.db
locksettings.db-shm
locksettings.db-wal.
gatekeeper.password.key
gatekeeper.pattern.key
You may or may not have all the above files so delete the ones you have.
Reboot the phone and (if you've set a PIN) enter it to decrypt the storage one more time. After that you can simply unlock your phone with a swipe.
Upon Boot > Go into Settings > Security > set your preferred unlock method
Android will ask you if you want to set a boot-time code too so select as per convenience.

Making an EFS Backup​All too often, we've seen folks who have a corrupted or missing EFS Partition. This results in your IMEI being lost and no cellular activity on the device at all. This can be a royal PITA to fix, and some folks haven't been able to fix it at all. You can take a precautionary measure to safeguard yourself against this by taking a couple of minutes to back up your modemst files.
Download & Open up Terminal Emulator on your phone from here
Once it's open you'll be greeted with a command line prompt, in which you can enter text commands, the first thing you need to do is enable root access by entering this line (press the enter key on your on-screen keyboard after each command to issue it):
Code:
su
If this is the first time you've used Terminal Emulator a Superuser or SuperSU popup will appear, make sure you grant root access.
Now enter these two commands:
Code:
dd if=/dev/block/sdf1 of=/sdcard/modemst1.bin bs=512
Code:
dd if=/dev/block/sdf2 of=/sdcard/modemst2.bin bs=512
This will place two files (modemst1.bin & modemst2.bin) on your internal storage.
Make sure you copy them to your PC and Cloud immediately so that you have a backup there to use if you need to restore it in future.
That's it !! In case you ever need to restore Nanroid or EFS Backups, please continue and follow the next post...

Restoring an EFS Backup​If by chance you end up with a corrupt EFS partition all you need to do is flash the files back to your device using fastboot.
Boot into fastboot mode (power + volume up) and connect your phone to your PC via usb cable.
Keep modemst1.bin and modemst2.bin (backed up earlier) on your desktop and open command window there.
These fastboot commands will restore the files:
Code:
fastboot flash modemst1 modemst1.bin
Code:
fastboot flash modemst2 modemst2.bin
Reboot your device.
Code:
fastboot reboot
Now disconnect phone from PC. Your IMEI should be back.
That's it for this guide, Enjoy :highfive:

Changelog:
Oxygen OS 4.7.2 Update logs:
• Optimizations for fingerprint unlock
• Optimizations for face unlock
• Improved accuracy for screen off gestures
• Improved EIS during 4K video recording
• Wi-Fi WPA2 security patch (Krack vulnerability patch)
• General stability improvements and bug fixes
Download: http://otafsg1.h2os.com/patch/amazo...en_43_OTA_004_all_1711152324_9a7ca8ad1c7d.zip
Mirror: https://www.androidfilehost.com/?fid=817906626617948432
Oxygen OS 4.7.1 Full Zip Stock Rom
Update logs:
• Optimizations for fingerprint unlock
• Optimizations for face unlock
• Improved accuracy of screen off gestures
• Improved EIS during 4K video recording
• Wi-Fi WPA2 security patch (Krack vulnerability patch)
• General stability improvements and bug fixes
Downloads:
Official | Drive

If someone want to try to flash twrp, please contact me before do it, i will help him to extract the stock recovery

mauronofrio said:
If someone want to try to flash twrp, please contact me before do it, i will help him to extract the stock recovery
Click to expand...
Click to collapse
I'm happy to try Just got my 5T. What do you need from me?

edent said:
I'm happy to try Just got my 5T. What do you need from me?
Click to expand...
Click to collapse
I need to connect to your pc (with teamviewer), unlock your op5t bootloader and extract the stock recovery. If you have already flashed twrp i cant get stock recovery anymore. When you have op5t and you are ready contact me in pm or on telegram (@mauronofrio)

mauronofrio said:
I need to connect to your pc (with teamviewer), unlock your op5t bootloader and extract the stock recovery. If you have already flashed twrp i cant get stock recovery anymore. When you have op5t and you are ready contact me in pm or on telegram (@mauronofrio)
Click to expand...
Click to collapse
My 5t ordered time to cook up some kernel love

My OP5T will arrive on 24
once i'll get it, i want to install twrp + magisk, doing that can i still receive updates? Or i need to download manually the rom and dirty-flash every new update?

Hi,
I have made an error deleting the ROM in TWRP, nom i am trying to reinstall the original rom from the above post but i have an error 7 when trying to flash it.
Any idea how to solve that problem ?

dabug123 said:
My 5t ordered time to cook up some kernel love
Click to expand...
Click to collapse
...and Liquid Remix Oreo!

EasyDeath said:
My OP5T will arrive on 24
once i'll get it, i want to install twrp + magisk, doing that can i still receive updates? Or i need to download manually the rom and dirty-flash every new update?
Click to expand...
Click to collapse
If you are rooted you would need to download and dirty flash the full zip Everytime there is an update. I will open a separate thread for update for stable and beta as and when out with the files required and easy instructions.
NanouMu said:
Hi,
I have made an error deleting the ROM in TWRP, nom i am trying to reinstall the original rom from the above post but i have an error 7 when trying to flash it.
Any idea how to solve that problem ?
Click to expand...
Click to collapse
Try Wipe dalvik and cache and then flash the full zip. Keep in mind that twrp is still unofficial and may have some glitches.
Sent from my OnePlus 5 using XDA Labs

So you need to remove lock screen security every time you want to do a backup in TWRP? Does it matter if you are encrypted or not?

Related

[GUIDE] Unlock/Root/Flash for OnePlus One

[SIZE=+3]Heisenberg's How-To Guide For Beginners[/SIZE]
[SIZE=+2]OnePlus One[/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]See Also:
[INDEX] OnePlus One
[FAQ] OnePlus One Frequently Asked Questions[/size]
[SIZE=+1]Intro[/SIZE]
This thread will serve as a location for basic how-to guides for the OnePlus One (Bacon). 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.
[size=+1]Prerequisites[/size]:
You'll need a working adb/fastboot environment on your PC to get through some of these guides. 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 Library
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. To 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'll find universal adb/fastboot drivers here, download it and follow the installer, then reboot your PC.
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 fastboot mode (power + volume up) 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. Make sure you read a section and fully understand it before attempting it.
[SIZE=+1]Index[/SIZE]
How To Unlock Your Bootloader
How To Install A Custom Recovery On Your Device
How To Make A Nandroid Backup With TWRP Recovery
How To Root Your Stock Rom
How To Install A ROM with TWRP Recovery
How To Install A Custom Kernel With TWRP Recovery
How To Flash The Stock Kernel With Fastboot
How To Flash The Cyanogen OS Fastboot Images
How To Update Modem/Firmware When Switching From KitKat To Lollipop (and vice versa)
How To Make Sure You Can Pretty Much Always Recover From An Accidentally Wiped System
How To Backup & Restore Your EFS Partition
[SIZE=+1]1. How To Unlock Your Bootloader[/SIZE]
Power off your phone then boot into fastboot mode (power + volume up).
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
The device will now go through the automated unlocking process, just let it do its thing and it'll boot up into Android.​
Go back to fastboot mode and issue this command to ensure that it worked:
Code:
fastboot oem device-info
It should have a couple of lines there, both with the flag set to true.​
You can now reboot your phone using this command:
Code:
fastboot reboot
It's now safe to disconnect your usb cable.
Please note: this will erase all user data from your device, it is best to do this before you really start using the device and installing apps or putting data on the internal storage.
[SIZE=+1]2. How To Install A Custom Recovery On Your Device[/SIZE]
Prerequisites: unlocked bootloader.
You first need to go into Settings/Developer Options and uncheck the "Update recovery with system updates" option (to enable Developer Options go into Settings/About Phone and click 'build number' about seven or eight times).
Download the recovery of your choice (my preferred recovery is TWRP, and we'll be using that for this guide, grab it here).
Make sure you check the md5 to verify its integrity.
Place the file in your fastboot folder (this is where fastboot.exe is located on your PC).
Put the phone in fastboot mode and connect it to your PC via usb cable.
Open a command prompt from within your fastboot folder (shift + right click, select open command prompt here), and enter the following commands:
Code:
fastboot flash recovery openrecovery-twrp-2.8.1.0-bacon.img
(The recovery filename in the command will change depending on which recovery you're flashing)
Code:
fastboot format cache
Code:
fastboot reboot
Let the device reboot, it's now safe to disconnect your usb cable.
Now you can use the advanced power menu (or the power + volume down button combo) to enter your custom recovery.
Please note, if you have taken the stock Lollipop update please read the following:
For some reason CM12S doesn't respect the on/off toggle for the "update CM recovery" option in Developer Options, it just replaces whatever custom recovery you've flashed with the CM recovery regardless of whether that option is unelected.
Flash your custom recovery again, but after flashing don't do a normal reboot. After the flash has succeeded disconnect the usb cable, then power down the phone by holding the power button down, once it's powered off use the power + volume down button combo to boot directly into recovery. This first forced reboot into recovery somehow subverts what was keeping it from staying flashed and all subsequent normal reboots into recovery will boot into the custom recovery of your choice.
[SIZE=+1]3. How To Make A Nandroid Backup With TWRP Recovery[/SIZE]
Prerequisites: unlocked bootloader, TWRP recovery.
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.
All you need to do is enter 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]4. How To Root Your Stock Rom[/SIZE]
Prerequisites: unlocked bootloader, TWRP recovery.
First you need to download SuperSU.
Enter TWRP recovery via the advanced power menu (or power + volume down).
Select the install option from the TWRP home screen.
Navigate to where you have SuperSU stored on your sd card 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.
[SIZE=+1]5. How To Install A ROM with TWRP Recovery[/SIZE]
Prerequisites: unlocked bootloader, TWRP recovery.
Installing a ROM is a pretty straight forward and easy process. Before you install anything you should make a nandroid backup (instructions above).
Download a ROM and appropriate Gapps package and place on your device.
Boot into your custom recovery.
Perform a full wipe.
Select the wipe option from the TWRP home screen.
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]6. How To Install A Custom Kernel With TWRP Recovery[/SIZE]
Prerequisites: unlocked bootloader, TWRP recovery.
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 Trickster Mod, No Frills, Kernel Tuner, and many more.
[SIZE=+1]7. How To Flash The Stock Kernel (boot.img) With Fastboot[/SIZE]
Prerequisites: unlocked bootloader.
If you're running a custom kernel on Cyanogen OS you'll need to flash the stock kernel back in order to take an OTA update.
Download the appropriate set of stock images from this thread. Extract the zip and grab the "boot.img" file.
Put it in your fastboot folder (where you have fastboot.exe located) on your PC.
Boot into fastboot mode (power + volume up) and connect your phone to your PC via usb cable.
Open a command prompt from within your fastboot folder (shift + right click, select open command prompt here).
Issue this fastboot command:
Code:
fastboot flash boot boot.img
It'll take a few seconds to flash the boot.img, once it's finished you can manually reboot your phone or use the following command to reboot it:
Code:
fastboot reboot
It's now safe to disconnect your usb cable.
Now you have the stock kernel back on your device.
[SIZE=+1]8. How To Flash The Cyanogen OS Fastboot Images[/SIZE]
Prerequisites: unlocked bootloader.
Please note: This procedure requires an unlocked bootloader. This procedure will factory reset your device! All user data (settings, apps, data on internal storage) will be wiped!
Download the latest stock images to your PC from here. If you don't want the latest build you can find all stock images mirrored here thanks to @Spannaa.
Reboot your device into Fastboot Mode (power + volume up) and connect your phone to your PC via usb cable.
Unzip the file you downloaded and put its contents into your fastboot folder (the same folder that you have adb.exe and fastboot.exe located in on your PC).
Open a command prompt from within your adb/fastboot folder (shift + right click, select open command prompt here).
Issue these fastboot commands:
Code:
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot flash oppostanvbk static_nvbk.bin
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata_64G.img
or fastboot flash userdata userdata.img if you have the 16gb model)
Please note: flashing the userdata will wipe your internal storage (your virtual sd card). It's possible to flash these images without that command if a full wipe isn't completely necessary in your situation.
Reboot your device with this command:
Code:
fastboot reboot
It's now safe to disconnect your usb cable.
[SIZE=+1]9. How To Update Modem/Firmware When Switching From KitKat To Lollipop (and vice versa)[/SIZE]
Prerequisites: unlocked bootloader.
To update from KitKat to Lollipop download the YOG4PAS1N0 firmware zip here:
cm-12.1-YOG4PAS1N0-bacon-firmwareonly-fastboot.zip
To revert from Lollipop to KitKat download the XNPH44s or XNPH05Q firmware zip here:
cm-11s-XNPH44S-bacon-firmwareonly-fastboot.zip
cm-11s-XNPH05Q-bacon-firmwareonly-fastboot.zip
Reboot your device into Fastboot Mode (power + volume up) and connect your phone to your PC via usb cable.
Unzip the file you downloaded and put its contents into your fastboot folder (the same folder that you have adb.exe and fastboot.exe located in on your PC).
Open a command prompt from within your adb/fastboot folder (shift + right click, select open command prompt here).
Issue these fastboot commands:
Code:
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot flash oppostanvbk static_nvbk.bin
Reboot your device with this command:
Code:
fastboot reboot
It is now safe to disconnect your usb cable.
[SIZE=+1]10. How To Make Sure You Can Pretty Much Always Recover From An Accidentally Wiped System[/SIZE]
Prerequisites: unlocked bootloader, TWRP recovery.
There may come a time when you accidentally wipe your OS while trying to perform a basic cache wipe in recovery. Don't laugh, it can happen to the best of us. The best way to insure yourself against being stuck in recovery is to keep a ROM zip or a TWRP/CWM backup (a nandroid backup) on your sd card at all times.
This solution seems like common sense but apparently there are quite a few people out there who don't store a ROM or backup on their phone. You might think it's easy to just mount the OTG storage and copy a ROM across to your phone from your PC (which is definitely an option), but there's always a chance that you won't be near your HDD or sd card at the time, or it won't recognise your phone properly. Basically you need to insure yourself against Murphy's law.
[SIZE=+1]11. How To Backup & Restore Your EFS Partition[/SIZE]
Prerequisites: unlocked bootloader, root.
All too often on this device I've seen folks who have a corrupted or missing EFS Partition. This results in your IMEI being lost and no cellular activity on the device at all. This can be a royal PITA to fix, and some folks haven't been able to fix it at all. You can take a precautionary measure to safeguard yourself against this by taking a couple of minutes to back up your modemst files.
Open up Terminal Emulator on your phone (if you don't have it you can download it here).
Once it's open you'll be greeted with a command line prompt, in which you can enter text commands, the first thing you need to do is enable root access by entering this line (press the enter key on your on-screen keyboard after each command to issue it):
Code:
su
If this is the first time you've used Terminal Emulator a Superuser or SuperSU popup will appear, make sure you grant root access.​
Now enter these two commands:
Code:
dd if=/dev/block/mmcblk0p10 of=/sdcard/modemst1.bin bs=512
Code:
dd if=/dev/block/mmcblk0p11 of=/sdcard/modemst2.bin bs=512
The result should look like this:
This will place two files (modemst1.bin & modemst2.bin) on the root of your internal storage, make sure you copy them to your PC immediately so that you have a backup there to use if you need to restore it in future.
If by chance you end up with a corrupt EFS partition all you need to do is flash the files back to your device using fastboot.
Boot into fastboot mode (power + volume up) and connect your phone to your PC via usb cable.
Make sure the two files are in your fastboot folder on your PC.
These fastboot commands will restore the files:
Code:
fastboot flash modemst1 modemst1.bin
Code:
fastboot flash modemst2 modemst2.bin
Reboot your device:
Code:
fastboot reboot
It's now safe to disconnect your usb cable.
Credit goes to @Vonnegut for originally posting this method in the TWRP thread.
Donate To Me
Nice guide!
Sent from my One using Tapatalk
Great guide. Short and simple, just how I like it. :good:
timmaaa said:
The best way to insure yourself against being stuck in recovery is to keep a ROM zip or a TWRP/CWM backup (a nandroid backup) on your sd card at all times.​
Click to expand...
Click to collapse
Can you confirm that backups made through CW recovery are fully functional? I remember that my previous phone's kernel wasn't backing up /preload while making nandroid backups...
ksoze11 said:
Can you confirm that backups made through CW recovery are fully functional? I remember that my previous phone's kernel wasn't backing up /preload while making nandroid backups...
Click to expand...
Click to collapse
I don't use CWM recovery so I can't confirm that personally. I use TWRP and can confirm that backups are fully functional with that recovery.
Transmitted via Bacon
Ive rooted my OPO, how do i perform a nandroid backup ? when i rooted i dont know if i put a custom recovery on it.. i followed this guide https://forums.oneplus.net/threads/...snt-wipe-your-data.66270/page-16#post-3809224
Quinnaay said:
Ive rooted my OPO, how do i perform a nandroid backup ? when i rooted i dont know if i put a custom recovery on it.. i followed this guide https://forums.oneplus.net/threads/...snt-wipe-your-data.66270/page-16#post-3809224
Click to expand...
Click to collapse
You didn't install a custom recovery or unlock your bootloader if you followed that tutorial. Just unlock your bootloader, it'll wipe your data so just backup anything that's important first. Then you can flash TWRP recovery and make a nandroid backup.
Transmitted via Bacon
urgh, i was hoping i could keep all my data. Think ill give it a miss, it was only so i can install Xposed, but that should work anyway right?
Quinnaay said:
urgh, i was hoping i could keep all my data. Think ill give it a miss, it was only so i can install Xposed, but that should work anyway right?
Click to expand...
Click to collapse
If you're rooted you can just install the Xposed Framework apk and away you go. But, I'd strongly recommend you actually unlock your bootloader now, it's only gonna get harder to do the longer you wait.
Transmitted via Bacon
Come to think of it, there's a method around that'll unlock your bootloader without wiping any data, it's in the general section I think, have a look.
Transmitted via Bacon
Found it, @quinnay, here's what you want:
http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
Once you've done that you can follow my instructions to install a custom recovery and make a nandroid.
Transmitted via Bacon
Thanks Timmaaa yr a true contributor !!!!!!!!!!!!!!!!!:good:
Ive moved the "backups" folder containing all the files from my nandroid backup to PC if anything ever happens is it ok just on my PC or does it need to be on my phone?
edit: does this look right?
Quinnaay said:
Ive moved the "backups" folder containing all the files from my nandroid backup to PC if anything ever happens is it ok just on my PC or does it need to be on my phone?
edit: does this look right?
Click to expand...
Click to collapse
It's fine to store it on your PC. But, you should have either a backup or a ROM zip on your phone at all times. If your system accidentally gets wiped or you run into some kinda trouble and you don't have one of those on your phone you're gonna kick yourself big time.
Yes it looks just fine.
Transmitted via Bacon
timmaaa said:
It's fine to store it on your PC. But, you should have either a backup or a ROM zip on your phone at all times. If your system accidentally gets wiped or you run into some kinda trouble and you don't have one of those on your phone you're gonna kick yourself big time.
Yes it looks just fine.
Transmitted via Bacon
Click to expand...
Click to collapse
whats the best thing to leave on my phone? should i put the backup back then?
It's up to you. Being that the phone has a mammoth amount of internal storage I'd just leave a backup on it because that's the easiest solution (restore it and boot, no setup required). I currently have four full backups on my device.
Transmitted via Bacon
I have a backup on the phone and my PC. Are you suggesting a flashable ROM on the phone also? I have the international 64 GB model rooted unlocked running stock. Which flashable ROM are you suggesting. I am very happy with 11s.
Sent from my One using Tapatalk
26.2man said:
I have a backup on the phone and my PC. Are you suggesting a flashable ROM on the phone also? I have the international 64 GB model rooted unlocked running stock. Which flashable ROM are you suggesting. I am very happy with 11s.
Sent from my One using Tapatalk
Click to expand...
Click to collapse
You don't need both, just one or the other is fine. It's just there as a failsafe. As for the ROM question:
Asking which ROM is best/most stable/fastest/prettiest, or asking for a suggestion isn't allowed so I can't answer that, here's why. To say one ROM is better is to infer that the others are inferior in some way. This is disrespectful to the devs who spend their spare time bringing us these awesome ROMs free of charge. Each user has different tastes anyway, the best way to see which ROM suits you is to flash a few and find out for yourself.
Transmitted via Bacon
Thanks. I think you misunderstood me. I know better than to get into the best ROM stuff. I was referring to the factory cm11s ROM and was wondering if there was a flashable one I could leave on my phone.
Sent from my One using Tapatalk
26.2man said:
Thanks. I think you misunderstood me. I know better than to get into the best ROM stuff. I was referring to the factory cm11s ROM and was wondering if there was a flashable one I could leave on my phone.
Sent from my One using Tapatalk
Click to expand...
Click to collapse
Ahh I see, there is a recovery flashable version of cm11s available, it's in the dev section or general section.
Transmitted via Bacon

[HOW-TO] The Nexus 6 All-In-One Beginner's Guide

{
"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"
}
Welcome to the Nexus 6 All-In-One Guide. If you are a new user that is looking for the opportunity to take advantage of your device and do it right the first time, this guide is here to point the way. This thread exists to keep all the necessary methods and material in one common place just for you. As always: Do your homework first.
If followed correctly, this guide can be a useful tool. These steps are listed in the order in which they should be completed. The intent is to seamlessly unlock, root, backup and/or flash, leaving as little room for error as possible. This process will erase and/or reset everything on your device. All steps are assuming you have backed up your contacts, texts, pictures, videos, etc. I do not take credit for any of this material or information.
This guide is a compilation of work from across XDA, most specifically users like @Chainfire and @Chromium, that I have simply brought together.​
Step 1: Read. Read. Succeed.
Your journey down the Android path of rooting and modifying can be smooth, fun and educational, based on your attempt at learning everything you can before you begin. This is entirely up to you, the user. There is some excellent material here on XDA that I highly recommend reading over as part of step 1. Even though these 2 informational links were written for the Nexus 5, the knowledge still applies so don't skip this information!
A message from the moderators - All users please read
Yep, read it. It's for your own good. Included with some very useful general forum information, it also contains the forum rules which should also be read and understood.
[FAQ][REF]★All you need to know about Android | Read this before you post/root★
This awesome thread by @abaaaabbbb63 is a *noob friendly* collection of information every user that wants to root their phone should know. Many people blindly follow guides without even knowing what "Rooting" means. Hopefully, this will help new users (and old ones, why not?) understand what is happening with their phone, and what they will put up with. Get on over there and read it.
Be sure to checkout Post #2 below for additional information regarding your Nexus 6​
Step 2: Installing The Necessary Desktop Tools
ADB and Fastboot Installation
Download the full Android SDK here (scroll to the bottom of the page>DOWNLOAD FOR OTHER PLATFORMS>SDK Tools Only).
Extract the zip and place the android-sdk-windows folder on your desktop.
**If you chose to download the slimmed sdk skip to step 5**
Only if you downloaded the full sdk: Go into the android-sdk-windows folder and run SDK Manager.exe. Install the following packages (there are a total of 4 packages):
- Tools > Android SDK Tools, Android SDK Platform-tools
- Extras > Android Support Library, Google USB Driver
Only if you downloaded the full sdk: Go back into the android-sdk-windows directory, and you should see a new folder named platform-tools. If you don't see this new folder, repeat the step above.
To confirm that it is indeed working, open a command prompt window and enter the following commands:
Code:
cd Desktop/android-sdk-windows/platform-tools
adb version
If it displays "Android Debug Bridge version x.x.xx" it is working. If it is gives an error saying that adb is not a recognized command, it has not been successful. Carefully repeat the steps above if this is the case. Close the command prompt window when you are done.
Step 3: Unlock, Root & Custom Recovery
For those of you who want to get most out of your Nexus 6, you will certainly want to root it. Rooting your device provides you as the user many, many benefits. That's why you're here right now reading this. You want it all. Please note that there is always the chance of error during these processes. Bad or faulty USB cables, USB ports, bad/old device drivers on the computer, an active virus scanner. These are a few of the issues that can cause your device to fail to connect or prohibit a successful root/flash. Use good and original OEM USB cables. Uninstall any drivers you may have installed for previous mobile devices and disable your virus scanner.
>>>>>>Before you begin, make sure your N6 has USB Debugging Mode switched on<<<<<<
Before continuing, users must enable Developer Options in the devices settings and select the OEM Unlock option. To do so:​
- Go into Settings
- Under About Phone, you'll be able to locate your Build Number
- Tap Build Number until you are notified that you have activated Developer options
- Go into Developer Options, ensure it is enabled and check the Enable OEM Unlock box
- While in Developer Options, ensure the USB Debugging box is checked
Unlock The Bootloader
Turn the phone off. Then boot it into the bootloader/fastboot mode by holding volume down + power.
Plug the phone into your PC, then open a command prompt window window and type:
Code:
cd Desktop/android-sdk-windows/platform-tools
Code:
fastboot devices
This command will list the connected devices. If your phones serial number shows up you are good to go and may continue. If the phone is NOT listed this indicates that your drivers are not installed correctly. In order for you to continue you must fix your drivers so that your phone is listed under fastboot devices.
If the phone has been recognized by the command above, proceed to unlocking the bootloader with the following command:
Remember that this step will wipe EVERYTHING off the phone
Code:
fastboot oem unlock
On the phone a screen should pop up asking whether or not you would like to unlock the bootloader. Use the volume rockers to highlight "Yes" then press power to confirm the action.
After the above command has finished executing, run the following (DO NOT skip this step, it is more important than you think):
Code:
fastboot reboot
The phone will reboot. Next you will be presented with a screen containing an android logo and a progress bar (this may take up to ten minutes to complete). Wait until the phone has fully booted up into android, then proceed onto the next section of the guide.
Close the command prompt window.
Obtain Root
The instructions below and the zip file are the work of our beloved @Chainfire. CF-Root is the root for "rooting beginners" and those who want to keep as close to stock as possible. CF-Root is meant to be used in combination with stock firmware and be the quickest and easiest way for your first root.
- Download the ZIP file
- Extract the ZIP file
- Boot your device in bootloader/fastboot mode. Usually this can be done by turning your device off, then holding VolUp+VolDown+Power to turn it on.
- Connect your device to your computer using USB
- Windows:
--- Run root-windows.bat
- Linux
--- chmod +x root-linux.sh
--- Run root-linux.sh
- Mac OS X
--- chmod +x root-mac.sh
--- Run root-mac.sh
Follow the on-screen instructions - watch both the computer and the device!
**If you want to have root access only you can stop here.**​
A word on custom recoveries: A recovery image is the system level software for your Android that lets you perform several maintenance and recovery tasks. The stock recovery image is quite limited in what it allows you to do and therefore, flashing a custom recovery image is required to gain full control of your device’s administration. A custom recovery image allows you to perform the following tasks:
- Wipe your phone’s data (Factory reset) and cache
- Make, restore and manage backups of your phone’s operating system and software
- Mount, unmount and format your phone’s internal as well as external storage partitions
- Install a custom ROM or application from a zip file to your phone
- Wipe Dalvik cache and battery statistics
- Make logs for error reporting and debugging
Additionally, you can download the Goo Manager app to install TWRP updates.
*NOTE: I do not recommend Rom Manager as a tool to do anything but just install and/or update your recovery Do not flash ROMs from this application.
Installing A Custom Recovery
Go HERE to download the latest TWRP recovery for the Nexus 6.
Turn the phone off. Then boot it into the bootloader/fastboot mode by holding volume down + power.
Rename the recovery file that you downloaded above to recovery.img. *Make sure that you rename it to recovery.img NOT recovery.img.img* Remember that you should place the file in the platform-tools folder inside of the android-sdk-windows folder on your desktop.
Open command prompt and run the following commands:
Code:
cd Desktop/android-sdk-windows/platform-tools
Code:
fastboot flash recovery recovery.img
On the phone, use the volume buttons to scroll onto "Restart Bootloader" and hit power to select it. After the bootloader reloads, use the volume buttons to scroll onto "Recovery Mode" and power to select it. You should then be greeted with your newly installed custom recovery.
Close the command prompt window.
STEP 4: Making A Backup
Making a Nandroid will allow you to try out new ROMs while still keeping a safe backup in the event you experience issues during or after a custom OS or kernel installation. Be sure your device is fully charged before proceeding to the backup and flashing procedures.
If you are not already booted into recovery then do so now.
1. Boot into fastboot mode (Volume Down + Power)
2. Browse with the volume keys to Recovery Mode and press the power button
3. You are now in custom recovery.
4. In CWM go to Backup and Restore and select Backup. In TWRP select Backup. Name and select the options you want. Swipe to backup.
5. In TWRP, go to Backup and proceed to the next step(s).
6. After backup is finished, select reboot system now or stay in recovery to continue with this guide.
*NOTE: Be sure to save a copy of these backups to your computer and/or micro sd card. Having a recent backup saved to your computer and micro SD card can be useful if something happens to your phones internal memory.
Step 5A: Wiping Your Device
When flashing any ROM, it is always important to follow the proper wipe procedures in order for everything to function properly. There are various levels of wiping based on what sort of transition you may be making. In this guide, I will list the procedures for a full wipe, presuming that you are coming from the stock firmware and changing your OS completely. This is all assuming you have made the appropriate backups. ALWAYS perform the appropriate wipe before flashing a new ROM or update!
1. If you are not already in recovery, boot in now.
In CWM:
2. Select Wipe data/factory reset
3. Select Wipe Cache
4. Select Advanced and Wipe Dalvik Cache
5. Select Mounts and Storage and format /system
6. If you are transitioning from Android versions (4.4 to 4.x, etc) you must also format /data. You will lose all personal data so back it up first.
In TWRP:
2. Select Wipe
3. Select Factory Reset and wipe
4. Select System and wipe
5. If you are transitioning from Android versions (5.0 to 5.x, etc) you must also select Wipe Data and wipe. You will lose all personal data so back it up first.
Step 5B: Flashing a Custom ROM
Once you have selected a ROM for your Nexus 6:
1. Download the ROM. Be sure to download the appropriate Gapps as well.
2. From your PC, place the ROM/Gapps on your internal storage. Remember where they are.
3. Boot into custom recovery.
4. Perform the wipe listed above if you have not already.
5. From the main recovery screen:
>>CWM - Choose the "install .zip from SD Card" and confirm.
>>TWRP - Choose Install and locate the desired ROM on your internal storage.
6. Repeat step 5 and select the Gapps package.
7. Reboot system. It will take several minutes to load so be patient and don't worry. Once the phone is booted, let it sit for 5 minutes, reboot and enjoy!
>>Additional Information
Want the performance boost available with disabling forced encryption? Check out @bbedward's guide linked below for more information and instructions.
[How-To] Disable Forced Encryption
Running Windows 8.x and having device detection issues? Be sure to grab the Google USB drivers and follow the instructions from the link below.
Nexus 6 Driver (ADB, Fastboot and MTP) for Windows and MAC
Need to return your Nexus 6 to stock for resale, OTA or warranty purposes?
Checkout @Mr hOaX's excellent guide. The procedures require the use of the fastboot tool from the Android SDK. See post #1 above for information on installing this if you have not done so already. In his guide, you have the option of returning completely to stock or select specific portions to flash (radio, recovery, etc).
[Guide][How To] Flash Factory Images For Nexus 6
Looking for stock recovery? If you need to revert to stock to receive an OTA, here's the LRX22C Android recovery:
Unzip the image and flash per the norm in fastboot.
View attachment recovery.zip
Maybe I missed it while skimming the guide, but shouldn't there be instructions for people to get Developer Options? Allowing the PC access to your phone on first plug in (ADB won't discover the device without this)? And, most importantly for Nexus 6 (and 9), checking the "OEM Unlock" option in Developer Options?
Added. Thanks for catching that, @Kusanagi Fire :good:
I was just wondering but where are there custom ROMs? Im assuming there are none, but I cant get many things to work
Thanks for all the great info! Would it be possible to add information about removing encryption to this guide?
welp,I got the phone in the mail yesterday and had plans to stay completely stock for a couple weeks,but just couldn't help myself,grabbed the chainfire and twrp files with this guide unlocked bootloader/rooted/ installed custom recovery so here we go ...made my first nandroid already[emoji4]
bogus83 said:
Thanks for all the great info! Would it be possible to add information about removing encryption to this guide?
Click to expand...
Click to collapse
i'll think about it.
http://forum.xda-developers.com/nexus-6/development/disable-forced-encryption-gain-root-t2946715
So if all I do is unlock the bootloader and root, I can still receive OTAs directly?
Sent from my Moto X using Tapatalk
Are the steps the same for a mac?
gotsoot said:
So if all I do is unlock the bootloader and root, I can still receive OTAs directly?
Sent from my Moto X using Tapatalk
Click to expand...
Click to collapse
yup, but you may lose root and your bootloader may be re-locked if they push a bootloader update with it. just fyi.
the likely (hopefully) worst case is likely that you you have to unlock it again (thus wiping your data) and you have to re-setup the phone and re-root.
i cant guarantee success or failure so you assume all risk when you begin ANY modifications on your device.
Are bootloader updates common for Nexus phones? I can't recall hearing about one (though this will be my first Nexus).
Sent from my Moto X using Tapatalk
There were one or two for the nexus 5
Fastboot
Can somebody confirm that fastboot is working on Windows 8.1 because last time I tried it didn't work and I had to use Ubuntu to fastboot my htc.
I'm running Windows 8.1 but my computer would detect my Nexus 6 after installing the drivers via SDK manager. I followed these additional steps and installed the google USB drivers, and that worked for me:
http://www.theandroidsoul.com/nexus-6-driver-adb-fastboot-mtp-windows-mac/
Great stuff, thanks so much for putting this together!
No need for toolkit or drivers on Mac/Linux
Here's Mac/Linux way.
First create a file on your home folder named something like nexus 6. (This is where your going to save your files.)
Download su(I'll let op point to zip)
Download recovery (same as above from op)
Put them both in that file you created. (Make sure it is in home or you'll have to cd to wherever you put it)
OK make sure you back up your data(this will wipe everything.)
Boot into fastboot.
(Hold power and up/down button)
(Ensure you have adb and fastboot installed on your comp)
cd RootNexus (or whatever you named that folder you created)
*First things first...
./fastboot devices
Should see your device.(if not double check adb and fastboot are installed properly. Follow link. http://forum.xda-developers.com/showthread.php?t=1917237(make sure to click thanks button over there for easy setup.)
.
./fastboot oem unlock
(Follow on screen instructions, this will wipe data. )
./Fastboot restart bootloader.
(Linux users remove ./ in front of fastboot.)
Start up phone and sign in and let it completely boot. Then put SuperSU on device.
On your Mac/Linux
(Ensure you are still in root nexus folder)
./fastboot flash recovery recovery.img where recovery.img is the name of your recovery image file
Once that is done on your phone press the volume up (twice) until you see "Recovery". Then press the power button.*
Once inside recovery go to back up and back up your device.
Flash SuperSU after. Then restart and applaud yourself. Your now rooted. I've been doing it this way since forever
Because decrypting makes such a big change in performance, that would be good to have in this thread as well.
gamewarden234 said:
Because decrypting makes such a big change in performance, that would be good to have in this thread as well.
Click to expand...
Click to collapse
I'm putting together some additional information for post #2 of this thread. It will include decryption. :good:
gotsoot said:
So if all I do is unlock the bootloader and root, I can still receive OTAs directly?
Sent from my Moto X using Tapatalk
Click to expand...
Click to collapse
I would like to know this also.
*nevermind*

Guide: How To Unlock/Root/Flash for Pixel XL (Marlin)

[SIZE=+3]How-To Guide For Beginners[/SIZE]
[SIZE=+2]Pixel XL (Marlin)[/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=+3]Intro[/SIZE]
This thread will serve as a location for basic how-to guides for the Pixel XL (Marlin). I'm going to start off with a couple of the more obvious ones and go from there.
[size=+3]Prerequisites[/size]:
If you are on Verizon, please follow dePixel8 guidelines prior to using this thread
Always update your phone to the latest build available before starting the unlocking/rooting process.
You'll need a working adb/fastboot environment on your PC to get through some of these guides.
You must have Java installed and up to date in order to use the SDK Manager, please ensure that this is taken care of before installing the SDK.
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.
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:SDKandroid-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 Library, 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. To 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.
[SIZE=+3]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
[SIZE=+3]Index[/SIZE]
Post #1
1. How To Unlock Your Bootloader
2. How To Install A Custom Recovery On Your Device
3. How To Root with TWRP Recovery
4. How To Root with via Fastboot (No Recovery)
Post #2
5. How To Install A ROM with TWRP Recovery
6. How To Install A Custom Kernel With TWRP Recovery
7. How To Install A Custom Kernel Using Fasboot
8. How To Flash The Factory Images (Return To Stock)
9. How To Flash The Factory Images (Return To Stock But Leaving Internal Storage Intact)
[SIZE=+3]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 the unlock command:
Code:
fastboot flashing 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.
Note: After unlocking your bootloader, each time your phone boots up you'll be greeted with a warning that says "Your device software can't be checked for corruption. Please lock the bootloader". This is nothing to worry about, it's normal to see this when you have an unlocked bootloader. You can't remove it, as long as your bootloader is unlocked it will stay there.
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=+3]2. How To Install TWRP On Your Device[/SIZE]
Prerequisites: unlocked bootloader (section 1).
Warning: TWRP is currently in RC1 phase and is not fully stable, flash at your own risk.
This guide assumes you have just unlocked your bootloader and are otherwise stock, NO root yet.
Download the necessary files (IMG and Zip) from the TWRP website and add the TWRP zip to your internal storage: https://dl.twrp.me/marlin/
Place the IMG file in your fastboot folder (this is where fastboot.exe is located on your PC)
Boot into the bootloader. 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 boot path/to/twrp.img
(The TWRP filename in the command will change depending on which recovery you're flashing)
This will temporarily boot TWRP on your device. If you are using a lockscreen pin/pattern/password and do not get prompted to enter your password, reboot to the bootloader and try again. Go to install and browse to the zip and install the TWRP zip
[SIZE=+3]3. How To Root[/SIZE]
Prerequisites: unlocked bootloader (section 1), TWRP recovery (section 2).
Download the latest SuperSU of your choosing to your phone:
https://download.chainfire.eu/1013/SuperSU/SR4-SuperSU-v2.78-SR4-20161115184928.zip
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.
Thats it, reboot and you should have TWRP and SuperSU installed
[SIZE=+3]4. How To Root via Fastboot[/SIZE]
Prerequisites: unlocked bootloader (section 1)
Special Note: This is for users who do not have or want TWRP installed and want to run stock root
Download Chainfire's root-marlin-pixelxl.zip located here: https://download.chainfire.eu/1011/CF-Root1/root-marlin-pixelxl.zip
Extract Chainfire's zip and follow the instructions in the read me
Code:
***** The short guide *****
*BOOT* (do not flash!) the supplied image, and wait a few minutes:
fastboot boot boot-to-root.img
***** The long guide *****
Before you root your device, you need to unlock your bootloader, if you haven't done so yet.
If you are using a Verizon device, you need a special tool for that. Go find that first.
- Boot into Android
- Enable developer options
--- Settings -> About phone -> Build number: tap 7 times
- Enable OEM unlocking
--- Settings -> Developer Options -> OEM unlocking
- Go into bootloader mode
--- Turn off device
--- Hold volume down and power
- Run "fastboot flashing unlock" and follow the on-screen instructions
--- This will wipe your device
To root your device:
- Go into bootloader mode, if not there already
--- Turn off device
--- Hold volume down and power
- Run "fastboot boot boot-to-root.img"
--- Wait for a few minutes. The device will reboot at least twice
- You should be rooted once Android is fully booted up
*****
Enjoy!
- Chainfire
XDA:DevDB Information
Guide: How To Unlock/Root/Flash for Pixel XL (Marlin), Tool/Utility for the Google Pixel XL
Contributors
bajasur, The Flash, beanstown106, @micmars
Version Information
Status: Testing
Created 2016-11-27
Last Updated 2016-11-26
[SIZE=+3]5. How To Install A ROM with TWRP Recovery[/SIZE]
Prerequisites: unlocked bootloader (section 1), TWRP recovery (section 2).
Pending......
[SIZE=+3]6. 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, 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, Trickster Mod, No Frills, Kernel Tuner, and many more.
[SIZE=+3]7. How To Install A Custom Kernel via Fastboot[/SIZE]
Prerequisites: unlocked bootloader (section 1)
This guide is for users who DO NOT have TWRP installed, and want to Fastboot flash custom kernels.
Check the md5 to verify its integrity.
Download the kernel file you want to flash from whichever kernel developer you'd like
Place the file in your fastboot folder
Open a command prompt within that folder and run
Code:
fastboot flash kernel kernel_binary
kernel_binary will be replaced with whatever the file name (ie fk-r5.gz for Franco's Kernel)
Reboot your device.
Special Note: You may lose root if you had SuperSU pre-installed, you will need to re root following Section 4 (How to Root via Fastboot)
[SIZE=+1]8. 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.
Download the appropriate factory images for your model https://developers.google.com/android/images
Unzip the marlin-xxxxxx-factory-xxxxxxxx (marlin-nmf26o-factory-4f68765c) into a directory on your PC (for this guide we'll use C:\marlin\).
Once unzipped you should have a folder named marlin-xxxxxx (marlin-nmf26o).
Move the contents of this folder into your Fastboot/ADB environment so that you can run fastboot and adb commands. (Note: I do the opposite and move the most current fastboot and ADB from the Android SDK into this folder)
Look for the windows batch file named "flash-all.bat" and double click on it. This should begin the proper full clean flash of all images back to stock. This should take a few minutes, but eventually your phone should reboot on its own and take you to the Android set up screen.
If you wish to you can also relock the bootloader with this command:
Code:
fastboot flashing 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 user data from the device.
Once all commands/flashes are complete you can reboot the device:
Code:
fastboot reboot
[size=+4]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
2. 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.​
3. After unlocking the bootloader I get a message that says "Your device software can't be checked for corruption. Please lock the bootloader". What's going on? Can I get rid of it?
This is nothing to worry about, it's normal to see this when you have an unlocked bootloader. You can't remove it, as long as your bootloader is locked it will stay there.​
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.​
5. Does taking an OTA update wipe my user data?
No, it doesn't.​
6. Do I need to flash the userdata.img from the factory images?
You should never flash the userdata image. It doesn't take into consideration the storage capacity of the device and always allocates 32gb of storage. This is ok for the 32gb model, but for the 64gb and 128gb models you'll end up with much less storage capacity than you should have. If you wish to wipe your internal storage you'd use the following command instead:
Code:
fastboot format userdata
More to come, special thanks to @Heisenberg for his excellent guide format​
Reservation
Don't forget to pin this
Dude, awesome
Looking good @bajasur!
Nice! Great job...should definitely be pinned
Thanks so much @bajasur! I always used the one by the famous @Heisenberg for the 6P and its great to have one for the Pixel XL.
Any plans to also include the step-by-step for restoring back to stock?
MinimalistChris said:
Thanks so much @bajasur! I always used the one by the famous @Heisenberg for the 6P and its great to have one for the Pixel XL.
Any plans to also include the step-by-step for restoring back to stock?
Click to expand...
Click to collapse
Yes, there is a lot more to come. For now to restore to stock I recommend running the flash-all.bat file that comes within the factory image folder.
A detailed step by step image flashing guide will be linked in the next few days.
Sent from my Pixel XL using XDA-Developers mobile app
Thanks @bajasur! We can still use this to unlock and root from NDE63X correct?
oneandroidnut said:
Thanks @bajasur! We can still use this to unlock and root from NDE63X correct?
Click to expand...
Click to collapse
Negative
For Verizon you need to follow the unlock method provided by DePixel Devs. Once you have unlocked the rooting and twrp methods should work.
Sent from my Pixel XL using XDA-Developers mobile app
bajasur said:
Negative
For Verizon you need to follow the unlock method provided by DePixel Devs. Once you have unlocked the rooting and twrp methods should work.
Sent from my Pixel XL using XDA-Developers mobile app
Click to expand...
Click to collapse
Sorry I should have clarified it is a Google Store edition just with verizon sim and X software. I can just unlock it like normal correct?
oneandroidnut said:
Sorry I should have clarified it is a Google Store edition just with verizon sim and X software. I can just unlock it like normal correct?
Click to expand...
Click to collapse
Yep! That should work fine ☺
Sent from my Pixel XL using XDA-Developers mobile app
bajasur said:
Yep! That should work fine
Sent from my Pixel XL using XDA-Developers mobile app
Click to expand...
Click to collapse
Awesome I am trying to wait until TWRP is stable but im inpatient lol
So this is not the correct guide for a Verizon Pixel is it? Besides the sunshine website has anyone made a guide like this yet for the Verizon model
aholeinthewor1d said:
So this is not the correct guide for a Verizon Pixel is it? Besides the sunshine website has anyone made a guide like this yet for the Verizon model
Click to expand...
Click to collapse
Other than flashing dePixel8 to allow bootloader unlocking, all other steps are identical.
aholeinthewor1d said:
So this is not the correct guide for a Verizon Pixel is it? Besides the sunshine website has anyone made a guide like this yet for the Verizon model
Click to expand...
Click to collapse
I'll clarify in the OP regarding Verizon devices but yes that should be the case
Sent from my Pixel XL using XDA-Developers mobile app
Does rooting without TWRP cause bootloops on NDE63V? I tried it with the all-in-one tool and couldn't get my Pixel to boot past the 4 dots when I was on NDE63V.
I have since flashed the Npf26j update. Would it be safe to root via chainfire's method? Wanted to avoid TWRP for now incase I get the data drain bug.
Thanks!

(Working Method, Latest MIUI 8) - Unlock bootloader + twrp recovery + install SuperSu

How to Unlock bootloader + flash twrp recovery + root and install SuperSu in Xiaomi Redmi Note 3 (Snapdragon) without waiting for permission on the Latest MIUI 8 - V8.0.6.0.LHOMIDG. (as of 22-11-16)
Here you have the step by step procedures to successfully unlock your Redmi Note 3 SnapDragon global variant with latest global stable rom MIUI 8. Please follow the steps carefully.
The rom used for this procedure is the latest global stable fastboot rom MIUI V8.0.6.0.LHOMIDG.
This is the working guide for the Xiaomi redmi note 3 (SD) on latest MIUI 8.0.6.0 as on 22-11-2016. I did lots of experiments, bricked my device several times to find this working guide for latest rom, however you are free to link to this page for reference.
You dont need to apply for official unlocking and wait for a month or more to get the sms confirmation from xiaomi to officially unlock the bootloader, the problem with the official method is many users have reported that they did not receive the confirmation sms from xiaomi, even if they receive the confirmation sms the unlocking process stucks at some percentage and fails to unlock the bootloader. So for everyone here is the easy way to Unlock bootloader + flash twrp recovery + root and install SuperSu in Xiaomi Redmi Note 3 (Snapdragon) without waiting for permission.
First of all take a backup of all important files from your phone to your PC before starting. Because all data will be formatted while flashing the rom.
I have simplified most of the procedures and complicated works for this guide. A good part of the credit goes to some other developers because their works were helpful to me for experimenting to find this working full unlocking guide for the latest miui rom for redmi note 3 (SD) as of 22-11-2016.
REQUIREMENTS:
Xiaomi Redmi Note 3 (SD) Mobile
Micro USB data cable (or) compatible usb cable
Desktop or Laptop (Widows based)
Download all the tools, rom and other files from this androidfilehost folder link and keep all files in one folder for easy access:
https://www.androidfilehost.com/?w=files&flid=137618​Files List:
1. AnF.zip
2. fastboot_edl.zip
3. Fastboot Rom: "kenzo_global_images_V8.0.6.0.LHOMIDG PreRooted by SUBI.tgz"
4. MiFLash_v2016.08.30.0.zip
5. minimal_adb_fastboot_v1.4_setup _working.exe
6. MiPcSuiteSetup_v3.2.1.3111_2717.exe
7. Root Checker Basic v5.9.7.apk
8. SR1-SuperSU-v2.78-SR1-20160915123031.zip
9. twrp-3.0.2-2-kenzo for Redmi Note 3 _SD.zip
10. ADBdriversetup.zip (alternate use, in case device specific drivers are not properly installed)​
***Carefully remove your sim card & sd card from mobile (if inserted) before you begin and do not connect to internet until all steps are completed, because the phone would automatically sync with Xiaomi servers at first boot and may cause problems.
Make sure your phone is charged 60% and above.
The complete video go through of step by step procedures in this guide is available in this YouTube video,
https://www.youtube.com/watch?v=rj4gVMk3y0o​
FOLLOW THE STEPS CAREFULLY, IF YOU FACE ANY TROUBLE, START OVER AGAIN FROM STEP 1, IF YOU FACE ANY OTHER ERROR OR BOOTLOOP OR STUCK IN LOGO LOOK AT THE TROUBLE SHOOT SECTION AT THE BOTTOM.
Step 1:
Enable Usb Debugging, if not done before:
Open Settings in your device"Redmi note 3 (SD)", scroll to bottom in settings and click on "About phone" and now tap on MIUI version 7 times, it will show a message like "You are now a developer" and Developer options will be revealed.
Next go back to Settings main screen and then -> Additional settings -> Developer options -> Enable Developer options, Enable OEM Unlock, Usb Debugging.
{
"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"
}
Note: After that when you connect your phone to the Pc to execute adb commands, a prompt may appear on your phone with computer's fingerprint key, you should confirm it when it appears. In case if you already done this for your computer with proper adb drivers installed, you don't need to bother about this.
Step 2:
DISABLE DRIVER SIGNATURE ENFORCEMENT IN YOUR PC:
You now have to disable driver signature enforcement in your PC, to do this you have to open the settings window by pressing the shortcuts"Windows button + i -> Update & Security -> Recovery -> Advanced startup -> Restart now. Now the system will logout and show Recovery options, from there select Troubleshoot -> Startup Settings in Advanced options -> Restart. Your system will now reboot and show the "Startup settings" screen, a list of options will be available, you have to choose option number 7 to disable driver signature enforcement. Then the system will boot into the OS with driver signature enforcement disabled. After that do not restart your pc until all the below steps are completed, in case if you restart your pc for any reason you need to redo this step again because system reboot might enable driver signature enforcement again. That's it. Refer this video if you need further guidance.
Step 3:
To install ADB, Fastboot and other drivers in your PC:
Install the " minimal_adb_fastboot_v1.4_setup _working " file downloaded from the link I provided above. If any security prompts appear on your screen, allow all prompts.
Install the " MiPcSuiteSetup_v3.2.1.3111_2717.exe " file downloaded from the link I provided above. If any security prompts appear on your screen, allow all prompts.
Install the " MiFLash_v2016.08.30.0.zip " file downloaded from the link I provided above. If any security prompts appear on your screen, allow all prompts.
Step 4:
Extract AnF.zip file and execute the commands:
Now extract the "AnF.zip" file downloaded from the link I provided above. Connect your phone to Pc using the Usb cable. Open the extracted AnF folder and double click on the cmd.exe file, which will open a adb command window from there.
Execute the below command through adb command window to check and confirm the phone is connected via adb interface. If connected properly it should show device serial like "******** device"
adb devices​
Incase if your phone shows a prompt for computer's fingerprint key approval, allow it. Then execute the command again. You should see your phone serial number as shown in the image below, which means your phone is properly connected via adb. Incase if the device is not connect properly via adb, disable and enable USB debugging on your phone. If that also helping to install the phone's adb drivers, extract and run the"ADBdriversetup.zip" downloaded from the link I provided above to install the specific drivers for your phone.
Step 5:
Reboot the phone to EDL mode:
Now you have to reboot your phone to edl mode aka Emergency download mode. To do this execute the below command via adb window with phone still connected to Pc.
adb reboot edl​
Your phone will now reboot into blank screen or edl mode and new driver named "qshusb qloader 9008" will be installed in your Pc, now only red led notification light will be blinking on your phone. Once the driver is installed properly, the phone is now connected in edl mode. Now close the adb command window.
Step 6:
Setup MiFlash Tool & Flash the ROM:
Open the MiFlash tool (MiFLash_v2016.08.30.0.zip) application you installed earlier, click refresh button and your phone will be visible as port number (ex: COM10) in MiFlash tool. Exe file is in this path,"C:\Xiaomi\XiaoMiFlash"
Now extract the "kenzo_global_images_V8.0.6.0.LHOMIDG PreRooted by SUBI.tgz" fastboot rom file downloaded from the link I provided above. In your MiFlash tool window, click the Browse button and locate the extracted fastboot rom folder. Then select "clean all" button at the bottom of MiFlash window. The flash tool is now configured. Now click the Flash button.
Wait for few minutes for the flashing process to complete, once the process is complete and MiFlash tool window will show task finished. But do not disconnect the phone.
Step 7:
Reboot to Fastboot mode & execute Fastboot commands:
Now while the phone is still connected to your pc, reboot your phone to fastboot mode by pressing Volume down button and Power button simultaneously until you see the boot screen and release, the phone will now enter into fastboot mode.
Now double click and open the cmd.exe file from AnF folder you extracted earlier to open the command window. Then execute the below command.
fastboot oem device-info​
This command will show you the current bootloader status. The bootloader status shows "Device Unlocked: False", execute the below command in command widow, it will Unlock the bootloader.
fastboot oem unlock-go​
Your device might restart now, if restarts press Volume down button and Power button simultaneously to reboot phone to fastboot mode again to check your bootloader status again by executing the below command. It should show "Device Unlocked: True" in the command window. Which means the device's bootloader is unlocked.
fastboot oem device-info​
Now to flash TWRP recovery and Supersu for root permissions, jump to step 8, or if your aim is to unlock the bootloader only, you may restart your phone and skip all below steps.
Step 8:
Flash TWRP:
Now restart phone to fastboot mode by pressing Volume down button and Power button simultaneously until you see the fastboot screen.
Extract the "twrp-3.0.2-2-kenzo for Redmi Note 3 _SD.zip" file downloaded from the link I provided above to the AnF folder.
Then open the AnF folder, double click and open the cmd.exe file, paste the below command in the command window to flash twrp recovery.
fastboot flash recovery twrp-3.0.2-2-kenzo.img​
After flashing the recovery image reboot the phone to TWRP recovery by pressing Volume Up button and Power button simultaneously until you see the boot screen. It will boot the phone into TWRP recovery, on the front screen just swipe the slider to mount system as read only. That's it now to flash supersu proceed to step 9.
Step 9:
Flash SuperSu:
While the phone is in TWRP recovery connect the phone to Pc, it will be detected as mass storage device, just copy the "SR1-SuperSU-v2.78-SR1-20160915123031.zip" file downloaded from the link I provided above to your phone's mass storage device.
On the twrp menu click on Install option and locate the "SR1-SuperSU-v2.78-SR1-20160915123031.zip" to install via twrp, now swipe the slider to right to install supersu to have root access in your phone's OS and then wipe dalvik cache using the button below in twrp.
If twrp shows any read/write error while flashing supersu, on the twrp mainscreen choose mount option and click on system in the next menu, then go back to main screen and try again to install.
That's it, now supersu is installed, to check the root status follow to step 10.
Step 10:
Check root status:
After completing all the steps successfully, reboot the phone into the system normally and complete the initial setup without Sim card, the first boot may take a little more time to boot into OS, In case if the phone stuck in boot screen for very long(10+ mins), go to troubleshoot section at the bottom and start over the steps. Otherwise you are good to go.
Connect device to Pc after initial setup completes, now copy the "Root Checker.apk" file to your phone and install it, open the root checker app and click on verify root, you will be prompted by Supersu for root permission, allow it, your root access will be verified. Voila, you have successfully rooted, flashed twrp and installed supersu on your Redmi Note 3 with latest rom installed.
That's it. Now you are ready to rock.
KNOWN ISSUES:
No issues found so far, in case if you find any issues after successfully unlocking using the above method, kindly let me know.
After successfully unlocking your bootloader, incase if you update your rom via official updates, your will lose root access and twrp custom recovery and may end up with locked bootloader again, if you face this situation by some reason, you may start over and follow this guide from step 1 to revert back to unlocked bootloader. Do not update the rom and turn off automatic updates in settings as a precautionary measure.
Troubleshoot:
If your device gets bricked or Stuck in Boot logo, try this,
Reboot your phone into edl mode by following below step.
If you are stuck on bootscreen, you may not be able to enter into edl mode using the normal method above because of bootloop or Stuck in Boot logo, in that case try this method to enter into edl mode from fastboot, download "fastboot_edl.zip" file from the link I provided above, extract the zip file and open the extracted folder, connect the phone to your Pc in fastboot mode(vol down + power), double click and run this file "edl.cmd", the phone will automatically enter into edl mode if the phone's drivers and adb drivers are installed properly.​Now follow step 6 and follow on from this step.​
If QHUSB_BULK drivers are not properly installed while the phone in edl mode,
If QHUSB_BULK drivers are not installed while the phone in edl mode, your device may not be visible in MiFlash tool(ex:COM10) even after you click refresh button, in this case open the device manager in your Pc, the phone will be visible as QHUSB_BULK with some alert sign, right click on it and select Update driver software. Then click browse my computer and browse to the location of the driver files in path "C:\Program Files\Xiaomi\MiPhone\Qualcomm\Driver" and proceed and when prompted to Install this Driver Software anyway, allow it and complete the driver installation. Now open MiFash tool and click refresh button your device will be detected in MiFash tool, now you can flash the fastboot rom by following the steps above.​
Does this work for Kate version also? OP doesn't specify
Will I lose my warranty by using this method of bootloader unlock?
This method still works for Global Snapdragon phone. Finally got it last night after 2 days of torture (I didn't sleep).
The important part is firstly the image with the modified file you are going to flash to the phone. Here he is using v8.0.6.0 which is the newest (and now last) update for android 5.1 (which is needed, phone will not flash 6.0 without a proper Cache and data clear). I ended up using version 7.3.2.0 which is 1 patch before the version my phone came with (7.3.7.0). Then I replaced emmc_appsboot.mbn with the one from here then flashed the file in EDL mode.
After the flash is done is just as important I found. You place it in fastboot mode (power button + vol down) and run a script. I wasn't able to manually unlock the device via cmd line 'fastboot oem unlock-go'. Instead I found a script that worked from here called 'Root_Folder' (this site also has majority of the files needed). You use the script called 'Root' in the folder to finish the unlock. Notice there is a 'recovery.img' in the folder as well, I replaced it with ZCX TWRP.
Now run through the script after the flash in fastboot mode. Follow the instructions from script, sometimes you take cable out or force phone back into fastboot mode. The key goal here is to have the script boot into TWRP in the end. If this happens you can do all that's needed now.
Another thing I noticed was you have to give debug permission to computer your using and save permission. Debug mode/oem unlock - connect cable, on phone you should get a prompt to accept PC and save permission. If you don't get this prompt make sure you have ADB and Fastboot installed.
Important steps are:
1. Phone connect to computer via debug/oem mode.
2. Flash correct modified ROM with MiFlash in EDL mode.
3. Once flash is done hold power and volume down button for fastboot mode.
4. Run script to attempt to unlock bootloader and/or install TWRP.
MikeyLee said:
Does this work for Kate version also? OP doesn't specify
Click to expand...
Click to collapse
You would have to look it up for Kate specifically. If anything at all that changes it's the Image you use to flash the phone.
zeon321 said:
Will I lose my warranty by using this method of bootloader unlock?
Click to expand...
Click to collapse
Don't think so. You don't 'officially unlock it' and you can flash a stock image that relocks the phone automatically.
Thank you works 100% !!!! :laugh:
After booting to TWRP it's asking me for a decrypt password and I cannot mount any partitions. Then I tried rebooting but phone is stuck on MI logo.
zeon321 said:
After booting to TWRP it's asking me for a decrypt password and I cannot mount any partitions. Then I tried rebooting but phone is stuck on MI logo.
Click to expand...
Click to collapse
Can you boot back into TWRP? If not you'll have to reinstall from EDL mode and try to unlock bootloader again.
A decrypt password to access any of the internal storage? Did you have a password with last install of MIUI? Also boot into fastboot and see if your bootloader is unlocked with 'fastboot oem device-info'. If your bootloader is unlocked, you might have to reformat data files on phone, which will wipe system completely and remove encryption.
Oh you probably also need to put a SD card into the device to use to flash from, if your flashing a new ROM. You have to wipe main system with advance wipe, wipe everything but internal storage and micro sdcard (in TWRP).
Narcle said:
Can you boot back into TWRP? If not you'll have to reinstall from EDL mode and try to unlock bootloader again.
A decrypt password to access any of the internal storage? Did you have a password with last install of MIUI? Also boot into fastboot and see if your bootloader is unlocked with 'fastboot oem device-info'. If your bootloader is unlocked, you might have to reformat data files on phone, which will wipe system completely and remove encryption.
Oh you probably also need to put a SD card into the device to use to flash from, if your flashing a new ROM. You have to wipe main system with advance wipe, wipe everything but internal storage and micro sdcard (in TWRP).
Click to expand...
Click to collapse
Thanks, I flashed old version of twrp and formatted the storage. Now phone is working fine.
Can i use this tuto on a Redmi note 4 MTK?
Great job !!! I have redmi note 3 pro kenzo with 3 gb ram and 32 gb internal .... so can i use the same guide and files or the files are different !!! confused
hoping for the reply soon ... thanks !!
Great job !!! I have redmi note 3 pro kenzo with 3 gb ram and 32 gb internal .... so can i use the same guide and files or the files are different !!! confused
hoping for the reply soon ... thanks !! @Sci Subi
Yes Praw Zoll, you can use this method for your device, I have tested this method working on Redmi Note 3 pro or Kenzo or Snapdragon variant.
You can also refer this miui thread for this same method with images and video, en.miui(dot)com/thread-461694-1-1.html
W7nstroll said:
Can i use this tuto on a Redmi note 4 MTK?
Click to expand...
Click to collapse
This method is for Redmi Note 3 pro, (Kenzo) variant.
can i use it for global stable 8.2.3 ??
The heart of this - the unofficial bootloader unlock - are taken from: http://en.miui.com/thread-345728-1-1.html (It's generally polite to link your sources).
This _does_ work on `kate`. However, this is using a modified 'emmc_appsboot.mbn'. If you flash an original emmc_appsboot.mbn, you may well find your bootloader no longer unlocked and you needing to reflash your device back to stock.
Also, for those wanting to use it on kate (because Xiaomi seems singularly incompetent when it comes to supporting the official bootloader unlock for that devcie): your device will identify itself as a kenzo, so you may have trouble flashing things like the 'miuifirmware_x.zip' updates for kate. Also, those 'miuifirmware_x.zip' files often include the emmc_appsboot.mbn, so be careful.
On another note, if anyone has an actual infallible method to get an official bootloader unlock for the kate device, please let me know.
Can I use this method for 2GB / 16 GB version of Redmi Note 3 Pro (Snapdragon)?
Thanks
Works Thanks
Tested On 18/05/17
This method works But You are stuck on a older rom with no OTA/Later Updates. Method Does not work with MM Roms.(Maybe with different emmc_appsboot.mbn it would work.
Some Pointers
I was on MIUI8 before using this.
1. This downgrades your ROM from the latest ROM, therefore Points to follow.
2. Use This Method Instead Works with latest firmware as on date.
Works, Simply Nicely Perfectly Done, Just follow the steps things will never goes wrong. :highfive:
Sci Subi said:
Yes Praw Zoll, you can use this method for your device, I have tested this method working on Redmi Note 3 pro or Kenzo or Snapdragon variant.
You can also refer this miui thread for this same method with images and video, en.miui(dot)com/thread-461694-1-1.html
Click to expand...
Click to collapse
hi my phone was on miui 8 marshmallow i used the above method nd flashed the rom ( rom is 5.1.1) which is given after that unlocked bootloader nd installed twrp also but now i downloaded a new rom nd i want to flash it i placed the rom in micro sd card nd wiped everything in phone nd flashed the rom with gapps now phone boots but its stuck at the boot logo of the rom i also tried many other roms of 7.1.1 but same is happening phone is not going ahead its stuck in the rom boot logo what should i do also when i flashed that given rom when i charge the phone the red light blinks which seems like edl light help me out of this !! thanks in advance !!
You have flashed a recovery rom and that's why you are in bootloop.
Try to flash in EDL mode a fastboot rom.
PS: Hope you haven't tried to downgrade already because you can loose IMEI and baseband.

[Guide] Pixel XL Android 9.0 (Pie) Unlock/Root/Install Images/Kernels/Recovery +

[Guide] Pixel XL Android 9.0.0 (Pie) Unlock/Lock Bootloader + Install Stock Images/Custom kernels/TWRP Recovery/Systemless ROOT
Security Patch - December 2019​
Introduction
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 Pixel, Pixel 2, Pixel 2 XL, Pixel 3a, or Pixel 3a XL phones.
NEW
Android 11 (R) ROM
Update(s)
Factory/OTA Images - 12/02
Magisk Stable - Magisk-25.2
Magisk Beta - Magisk-25.3
Magisk Canary - Magisk-25205
T.W.R.P - twrp-3.4.0-0-marlin.img/zip[/URL]
SDK Platform-tools - r33.0.3
Custom Kernels
No Updated Custom Kernels
Custom ROMs Android 10 (Q)
Pixel Experience 10/25
Custom ROMs Android 11 (R)
[UNOFFICIAL][ROM][11][Marlin/Sailfish] LineageOS 18.0 [06/10/2020] by*Lunarixus
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.
The latest Android 9.0.0 (Pie) Factory or OTA Image: "marlin" for Pixel XL
Factory Image
10.0.0 (QP1A.191005.007.A3, Dec 2019)
OTA Image
10.0.0 (QP1A.191005.007.A3, Dec 2019)
Computer - With the latest SDK Platform-Tools: r30.0.5 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
Pixel XL Android 10 (Q)
Credits/Thanks/Recognitions
Heisenberg RETIRED FORUM MODERATOR - He set the standard for creating, detailed, Guides.
Those I may have, inadvertently, forgotten.
Index
(NOTE: These are not steps 1-13, they are individual sets of information/instructions).
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.
Notes:
If your computer only has 'open powershell here' in the context menu. Use option 2.
If you do not want to open a Command Prompt every time you want to use fastboot, add the path to the Platform-tools folder to Windows environment variables.
Boot 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.
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 the phone to the Computer with USB cord.
Type this at the prompt and press enter to test fastboot.
fastboot devices
It should return your device serial number.
Unlock Bootloader/Return Phone to Stock/Lock Bootloader
Unlock Bootloader (Google Pixel XL)
Backup your data/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 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 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/Internal storage
Settings > System > Advanced > Reset Options > Erase all data (factory reset)
Log in
Set up phone
Lock Bootloader (Google Pixel XL)
'B' must be completed before performing this step!
Boot bootloader
Open a Command Prompt and type this at the Prompt: fastboot flashing lock
You should see a request for confirmation on your phone, use the volume keys to scroll and the power key to select.
Allow the process to complete, then type this at the Command Prompt: fastboot reboot
Set up your phone.
Enable Developer Options: Settings > System > About phone > Tap Build number 7 times.
Tap Back > Developer options and toggle OEM Unlock off.
Install Factory Image keep or wipe data
When doing a major upgrade, Android 8.1.0 (Oreo) to Android 9.0.0 (Pie). I suggest wiping data/Clean Install.
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 flash-all at the Command Prompt and press enter.
Reboot
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 flash-all at the Command Prompt and press enter.
Reboot
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: 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:
fastboot flash boot boot.img --slot all
Reboot
Install T.W.R.P./Root/Reroot with Magisk and 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.3.1-3 for Google Pixel XL
twrp-3.4.0-0-marlin.img - Download to your computer
twrp-pixel-installer-marlin-3.4.0-0.zip - Download to your phone
Magisk - Download to your phone
The latest Stable/Beta Magisk Manager from Magisk by topjohnwu
[DEV] Magisk Canary Channel - Bleeding Edge Builds by topjohnwu
Custom kernels - Download to your phone
No Updated Custom Kernels
Kernel Managers - Download to your phone
EX Kernel Manager
FK Kernel Manager
Boot Bootloader
Connect the phone to the Computer with USB cord.
Copy twrp-3.5.0-0-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: fastboot boot twrp.img and press enter.
When TWRP boots, disconnect phone from computer.
Swipe to allow modifications.
Tap Install select
twrp-pixel-installer-marlin-3.4.0-0.zip
Swipe the slider to install
Reboot Recovery
If you are rerooting, tap Install, select the latest Magisk's uninstaller.zip, and Swipe the Slider to Install.
Note: If you have Modules installed, please read these posts by @jcmm11 'RC' before flashing/installing Magisk's Uninstaller.zip: Post 329 and Post 333
Install Custom Kernel and Root/Reroot (Optional)
Note(s):
Some Custom Kernels can be updated by flashing via twrp or Kernel Manager without losing root. Check the Custom Kernel thread (OP - Installation/Instructions) to find out which Custom Kernels.
Some Custom Kernels can also be Flashed with a Kernel Manager.
If you want to flash the kernel via the Kernel Manager instead of twrp skip #7 L1 do #7 L2 then install kernel via Kernel Manager.
Yes
No Updated Custom Kernels
No
Tap Install, select Magisk-20.4.zip - Stable/Beta
Swipe Slider to Install
Save Log
Reboot System
Boot T.W.R.P./Root/Reroot with Magisk and Pass SafetyNet.
Important: Remove Pin before booting TWRP:
Settings > Security & location >Screen lock > None
Backup your data and Internal storage
Download files:
See #7 - Skip the twrp-pixel-installer-marlin-3.4.0-0.zip
Boot Bootloader
Connect the phone to the Computer with USB cord.
Open a Command Prompt on your computer.
Copy twrp-3.4.0-0-marlin.img to the platform-tools folder or the folder that fastboot is in and rename it twrp.img
Type fastboot boot twrp.img at the Command Prompt and press enter.
When TWRP boots, disconnect phone from computer.
If requested Swipe to allow modifications.
If you are rerooting, tap Install, select the latest Magisk's uninstaller.zip, and Swipe the Slider to Install.
Note: If you have Modules installed, please read these posts by @jcmm11 'RC' before flashing/installing Magisk's Uninstaller.zip: Post 329 and Post 333
Install Custom Kernel and Root/Reroot (Optional)
Note(s):
Some Custom Kernels can be updated by flashing via twrp or Kernel Manager without losing root. Check the Custom Kernel thread (OP - Installation/Instructions) to find out which Custom Kernels.
Some Custom Kernels can also be Flashed with a Kernel Manager.
If you want to flash the kernel via the Kernel Manager instead of twrp skip #8 I1 do #8 I2 then install kernel via Kernel Manager.
Yes
No Updated Custom Kernels
No
Tap Install, select Magisk-20.4.zip - Stable/Beta
Swipe Slider to Install
Save Log
Reboot System
Set Magisk Manager's Update Chanel/Update Magisk
Set Magisk Manager's Update Channel - Stable/Beta/Custom
Open Magisk Manager > Tap menu icon > Settings > Update Channel > Select Stable, Beta or Custom.
Custom is used to switch to Canary. Paste the URL below in the Custom Channel: https://raw.githubusercontent.com/topjohnwu/magisk_files/canary/debug.json
Update Magisk
When Magisk Manager notifies you of an update:
Tap install.
Select, Direct Install (Recommended)
When it finishes installing
Tap, Save Log
Log location: /storage/emulated/0/MagiskManager/logs/install_log_...
Tap, Reboot
Done!
Custom ROMs for Pixel XL
Need help with a Custom ROM?
First, follow the Installation Instructions in the OP of the Custom ROM you are trying 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.
Alpha/Beta
None
Official
None
Unofficial
[ROM][10.0][marlin] Pixel Experience [AOSP][2020/10/25] by*PixelBoot
Audio Mod
ViPER4Android FX/XHiFI, [MOD]Audio Modification Library , and Audio Compatibility Patch.
Note: These Mods can be installed via Magisk Manager: Tap Magisk Manager > Tap Menu > Tap Downloads > Select Mod > Tap Install.
Other: TWRP Backup/TWRP Update
TWRP Backup
To Internal Storage
Boot bootloader
fastboot boot twrp-3.4.0-0.img
[*]When twrp-3.4.0-0 boots, tap Backup and select Partitions to backup
[LIST="(1)"]
[*]Boot
[*]System Image
[*]Data
[/LIST]
[*]Tap Select Storage ==> internal storage
[*]Tap ok
[*]Swipe Slider to backup
[*][B]Your backup will be stored in /Storage/TWRP/...[/B]
[/LIST]
[/HIDE]
[*]To OTG-USB Storage
[HIDE]
[LIST="a"]
[*]Boot fastboot mode (#1B)
[*][ICODE]fastboot boot twrp-3.4.0-0.img
[*]When twrp-3.3.1-3 boots, tap Backup and select Partitions to backup
[LIST="(1)"]
[*]Boot
[*]System Image
[*]Data
[/LIST]
[*]Insert USB-OTG
[*]Tap Select Storage ==> OTG-USB
[*]Tap ok
[*]Swipe Slider to backup
[*][B]Your backup will be stored in /Storage/TWRP/...[/B]
[/LIST]
[/HIDE]
[/LIST]
[/HIDE]
[*][B]Update[URL="https://twrp.me/google/googlepixelxl.html"]TWRP[/URL][/B]
[/LIST]
[/HIDE]
[/LIST]
Reserved
Reserved
Once again, fantastic guide Big thanks :highfive:
Way to be on top of things @Homeboy76, Job Well Done, once again :good:
Do OG Pixels need magisk 1671 or 1674?
Pixel 2 and 2 xl have some troubles, so there is a specific magisk version for them in the flash kernel thread, before flash I just wanna make sure 1671 won't cause issues, thank you.
Hi.
Can anyone tell me?
I want to flash Android Pie.
Now I'm on official Lineage OS 15.1 + twrp 3.2.2 + Magisk
I need to do step 3 (and flash all to both slots)?
Return Phone to Stock
Or I need to do step 4 (and flash all only once)?
Install Factory Image
Thanks in advance.
Did anyone dirty wipe (remove -w) when updating from July's 8.1 to today's (August) 9.0 on the Pixel XL?
djl236 said:
Did anyone dirty wipe (remove -w) when updating from July's 8.1 to today's (August) 9.0 on the Pixel XL?
Click to expand...
Click to collapse
I did, but I was running FireHound v4.7 (July Security), so I got a lot of different FCs, lol (Hey, I had to try). If you're on stock, you'll probably be fine.
I just installed TWRP 3.2.3, did a factory reset and setup fresh. No issues after that.
I had to use Magisk beta 16.7 to root. I did a restore with TiBu and all my previous apps are working fine.
Hi, i followed this (already 9 with OTA) :
Boot Bootloader
Connect the phone to the Computer with USB cord.
Copy twrp-3.2.2-0-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 phone from computer.
Swipe to allow modifications.
Tap Install select
twrp-pixel-installer-marlin-3.2.2-0.zip
Swipe the slider to install
After TWRP is installed
Reboot Recovery (Tap the back button, Tap reboot, Tap recovery.)
then
flash Magisk-v16.7(1671).zip - (BETA)
Swipe Slider to Install
Save Log
Reboot System
did not install custom recovery tho
it stuck at google logo. do i need to flash custom kernel?
I have this same problem, using 3.2.3. Not installing TWRP, I installed Elemental X alone and it works fine. It's when I try to install Magisk 16.7 that it bootloops on the Google Logo
lesp4ul said:
Hi, i followed this (already 9 with OTA) :
Boot Bootloader
Connect the phone to the Computer with USB cord.
Copy twrp-3.2.2-0-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 phone from computer.
Swipe to allow modifications.
Tap Install select
twrp-pixel-installer-marlin-3.2.2-0.zip
Swipe the slider to install
After TWRP is installed
Reboot Recovery (Tap the back button, Tap reboot, Tap recovery.)
then
flash Magisk-v16.7(1671).zip - (BETA)
Swipe Slider to Install
Save Log
Reboot System
did not install custom recovery tho
it stuck at google logo. do i need to flash custom kernel?
Click to expand...
Click to collapse
jeremyafrank said:
I have this same problem, using 3.2.3. I installed Elemental X alone and it works fine. It's when I try to install Magisk 16.7 that is bootloops on the Google Logo
Click to expand...
Click to collapse
found this , magisk 16.7 1674
https://drive.google.com/file/d/106ZiqeQxNYtCHkOEc6niuHRcWiCzG_eA/view
didn't work either lol
I'm going to have to go back to 8.1 (had done a dirty flash, but I'm only running stock) until this is sorted. Some nice things I'd like to play with in Pie, but not at the expense of root.
lesp4ul said:
found this , magisk 16.7 1674
https://drive.google.com/file/d/106ZiqeQxNYtCHkOEc6niuHRcWiCzG_eA/view
didn't work either lol
Click to expand...
Click to collapse
TENN3R said:
Do OG Pixels need magisk 1671 or 1674?
Pixel 2 and 2 xl have some troubles, so there is a specific magisk version for them in the flash kernel thread, before flash I just wanna make sure 1671 won't cause issues, thank you.
Click to expand...
Click to collapse
1674 is for Pixel2/Pixel2XL
[TAIMEN/WALLEYE] [9.0.0] [4.4.146] [CLANG 7.… - Pg. 284 | Google Pixel 2 XL
Where is my mistake?
I flashed Pie image marlin-ppr1.180610.009-factory-90a4fa8b
(flash all.bat)
And had a lot of errors (Screenshot attached).
After reboot to system I have Lineage OS 15.1 that I had before.
{
"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"
}
Thanks in advance.
djl236 said:
Did anyone dirty wipe (remove -w) when updating from July's 8.1 to today's (August) 9.0 on the Pixel XL?
Click to expand...
Click to collapse
Yes, this is how I updated.
- I was on stable Magisk 16.0 so I flashed the most recent Magisk uninstall ZIP in TWRP to be safe, since 9.0 requires the Magisk 16.7 beta
- boot to bootloader
- flash-all.bat removing -w
- fully boot to system
- turn off, boot to bootloader
- fastboot boot new TWRP 3.2.3-0
- install TWRP 3.2.3-0 ZIP
- install Magisk 16.7 ZIP
- boot to system
- I had to reauthorize root access for all root apps and enable systemless hosts in Magisk
Device passes SafetyNet and is certified in Play Store.
jeremyafrank said:
I'm going to have to go back to 8.1 (had done a dirty flash, but I'm only running stock) until this is sorted. Some nice things I'd like to play with in Pie, but not at the expense of root.
Click to expand...
Click to collapse
1674 is for Pixel2/Pixel2XL: [TAIMEN/WALLEYE] [9.0.0] [4.4.146] [CLANG 7.… - Pg. 284 | Google Pixel 2 XL
Anyone try going from 8.0.0 directly to 9? I haven't done updates in forever. Don't want to just try and end up messing things up for myself.
djl236 said:
Did anyone dirty wipe (remove -w) when updating from July's 8.1 to today's (August) 9.0 on the Pixel XL?
Click to expand...
Click to collapse
I did with no problem.
I did a dirty install from Stock 8.1 with only Magisk.
Installed TWRP, Elemental and Magisk in that order rebooting to system in-between each one. It seems as soon as Magisk 16.7 is installed, many apps fail to launch or break, i.e. the Google Play Store can no longer open without force closing, Titanium Backup errors because it can't read the TB Pro key, going into settings and trying to change some things causes the UI to freeze up. But some apps like Twitch does work. Though Magisk is broken as well, i.e. Magisk Hide doesn't work but root access is detected. Safety, however, fails both on the inbuilt test in Magisk Manager and the SafetyNet app.
If I open Magisk Manager and install 16.0 apps goe back to working fine, but Magisk is still broken in the same way and SafetyNet still won't pass.
Reading back through the thread, I see that some get boot loops due to Magisk, but for others, it works fine and SafetyNet passes which I find odd... Either way, I guess we'll all have to wait for the next Magisk update!
EDIT:
Turns out, running the Magisk Uninstaller zip, then flashing the Magisk 16.7 zip seems to solve the issue!
Can confirm Magisk Hide now works and SafetyNet passes. Seems like running the uninstaller is a good step to add into this guide if the user was previously running Magisk.

Categories

Resources