Database Users

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!

[Guide][How-To] Root Android 8 Oreo - Pixel (XL) + SafetyNet Pass

This is how to root with SuperSU and includes flashing SuperSU Hide for Android O
Requirements:
Unlocked BootLoader
Latest fastbook/adb drivers (https://forum.xda-developers.com/android/software/guide-how-to-set-fastboot-adb-to-wide-t3591240)
Android O image (https://developer.android.com/about/versions/o/download.html#top)
SuperSU 2.82 SR3 (https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133)
Modded Version of the TWRP that works for Pixel/XL DP4/O (https://forum.xda-developers.com/pixel/development/mod-twrp-recovery-pixel-android-o-dp4-t3651896)
If you want SuperSU Hide for safety net passing (as of (8/21/2017 this is working) for Android Pay, Pokemon GO, Snapchat download SuperSU Lite from here (https://forum.xda-developers.com/apps/supersu/suhide-lite-t3653855)
The How to part
Flash the Android O factory image on your device
Let the divice boot and go through setup and i advise you set a lockscreen method (Pin, Pattern, Password whatever you want but this will allow TWRP to decrypt your data more consistently) then reboot to bootloader
boot into the TWRP linked above
Go to "Wipe" select "Advanced wipe" check just "internal storage" and swipe to wipe
your device's internal storage should now be accessible via your PC/Mac/Linux so copy of the linked SuperSU SR3 we downloaded from above
Back to TWRP and the device, flash the SuperSU you copied over
let it finish then swipe to reboot to system (do not install the TWRP installer app it asks you to install before the reboot)
let the system boot up and check to make sure supersu is there
reboot back to bootloader and boot into the TWRP
Enter your lockscreen login (Pattern will show up if you used a pattern otherwise type in you password or pin when it asked for password)
copy the supersu hide lite from your PC/Mac/Linux to the internal storage of the device
flash it in twrp then swipe to reboot to system
Finally when it boots you should have supersu and SUHide installed!
Few Notes:
-It is very important to know that we are not flashing TWRP to our system when in fastboot/bootloader. If you're coming from an older device or just new to the Pixel in general this will be kinda weird to you I'm sure. The reason we do no do this is (long story short) A/B partition devices like the Pixel's are a whole new ball game and there is still development being done to get traditional methods of installing aftermarket recoveries working. But till then we have to boot into things so the change is temporary and does not alter the device's recovery partition.
-How SuperSU Hide works is pretty self explanatory but if you're like me, the whole safety net thing is annoying and i haven't felt like reading about it. So using the "suhide" app you now have, you want to make sure root is hidden from the apps that watch for it and stop themselves from running is they see root (Snapchat, Android Pay and Pokemon GO are all examples of these apps)
the "About" tab in the "suhide" app is very helpful
Old instructions for Android O DPs
Early reports say boot-to-root (the method covered here) works for DP4
Rooting DP1-4 is very easy.
Make sure bootloader is unlocked
Make sure Fastboot/adb drivers are fully up to date. (Follow this guide to make sure: https://forum.xda-developers.com/android/software/guide-how-to-set-fastboot-adb-to-wide-t3591240 )
Download dp1-3 (https://developer.android.com/preview/download.html)
Download SuperSU 2.82 SR 1 for Pixel (or pixel xl) (https://forum.xda-developers.com/showpost.php?p=72686197&postcount=10481) [Updated to new fixed version that repaird system mounting issue]
Just flash Dev Preview like normal
boot into system and setup android
Reboot to bootloader
Exact the downloaded supersu
Reboot to bootloader
open a cmd in the extracted supersu location and type
Code:
fastboot boot boot-to-root.img
it will take about 7 minutes to boot but when it does you should have root
Original Instructions for rooting DP1
So after a few weeks of being without root on Android O for the Pixel user Sachi315 discovered how to get root on O by installing 7.1.2 on one slot and android O on the other. This allows Android O to fully boot after installing SuperSU. I wont go into the details of how it works because thus far its all speculation on my part and hopefully someone out there who knows more about these new partitions could better explain it. But for now I'm just going to show you how to do it.
Requirements
+Download 7.1.2 for your Pixel (XL)
-----N2G47E (https://developers.google.com/android/images)
+Download Android O for your Pixel (XL)
-----(https://developer.android.com/preview/download.html)
+SuperSU RS4 2.79 Extra Delay
-----(https://download.chainfire.eu/1024/...-SR4-20170323220017-ODP1-5X-6P-ExtraDelay.zip)
+TWRP RC1 bootable image & RC2 Flashable zip
-----For Pixel (https://dl.twrp.me/sailfish/)
-----For Pixel XL (https://dl.twrp.me/marlin/)
+Backup everything on you device, it will be purged
-----Make sure you have the latest fastboot binaries (I HIGHLY recomend you set this up manually. How to do so can be found in my tutorial here)
+Unlocked bootloader
To make sure you have the latest fastboot binaries press the windows key and type cmd. In the command line type "fastboot" This should return you get. Showing all the available fastboot commands including the new "--slot" commands. If this list has the options --set-active[=<slot>], --slot <slot> listed towards the bottom then you're all ready to move on. (see screenshot for list of other commands you should see)
{
"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"
}
​
Editing the flash-all.bat from your downloaded 7.1.2 and android o factory images
-Extract both to your working folder
-Find the "flash-all.bat" in the extracted 7.1.2 (N2G47E) right click and select "Edit"
-At this point we are going to clean the flash all up a bit. Its not a necessity but if you don't add some much needed line breaks it can get messy and confusing.
-Below i have a screen shot of what mine looks like cleaned up. Just press enter in the places i did. *Adding the line breaks does NOT mess with the code at all*
-----Toward the end of the commands you will see i added '--skip-reboot" between "update" and "image-sailfish-n2g47e.zip" This command makes it to where the device will not restart after the flash-all is finished. It is important you add this in the same place.
​-Now that we have this cleaned up, go ahead and save it really quick before we start adding to it.
-We are going to add a few "--slot" commands to it so it only installs to one slot. Below you can see what mine looks like after i added the commands. Match yours to mine (highlighted by red boxes)
-If you are on marlin, your image and zip names will be different but it's the same principal
​-after you add what i have above, save the flash-all.bat and close out of it.
Now we move over to the android o dev preview
-Open the extracted dev preview and right click on its flash-all.bat. Select "Edit"
-We are basically doing the exact same thing in this one BUT instead of the new commands being "slot _a" they will be "slot _b" (See below for the difference and we are still adding the "--skip-reboot" command)
​-Once your changes have been made in this flash-all.bat, save and close out.
Flashing the Images
Go ahead and get your Pixel into bootloader mode and plug it in.
before we start flashing we are going to clean the device up. This step will erase everything on the device.
Go into command prompt and type:
Code:
fastboot --slot _a -w
let it finish its thing then type
Code:
fastboot --slot _b -w
Device is cleaned. Now staying in bootloader type
Code:
fastboot --set-active=_b
then
Code:
fastboot reboot-bootloader
Now close out of this command prompt and run the flash-all.bat from the android o dev preview folder.
Let it do its thing and after its done, it should be left in bootloader.
now run the flash-all.bat from the 7.1.2 image folder you have.
Same thing; let it run its course and finish up.
Now you should be still in bootloader.
type in cmd
Code:
fastboot --set-active=_a
now type
Code:
fastboot reboot-bootloader
when it comes back up look at the phone and make sure is says the slot is "a" if it does, you're good to move on!
Installing TWRP and Root
From here; boot into TWRP (RC1)
-Make sure youre in slot A by going to "Reboot" then looking at the bottom (It should be slot A at this point, if its not something wasnt done correctly in the above steps)
+At this point i had the issue that my pixel would show up under "This PC" in explorer and was recognized by adb BUT none of the internal storage could be interacted with via my PC (this includes adb commands) so i couldnt get TWRP RC2 or SuperSU SR4 2.79 Extra Delay on the device to be flashed.
-To fix this: got to wipe>advanced wipe>check internal storage ONLY then wipe this partition.
-Unplug your phone and plug it back in and Windows Explorer should be able to work with the internal storage now.
-Now transfer TWRP RC2 and SuperSU sr4 2.79 Extra Delay to your Pixel
-From TWRP on your device, flash just TWRP RC2 for now. After it is installed, switch to slot b in TWRP. Then reboot to recovery.
-When TWRP comes back up, check to make sure youre in slot B still.
-If you are, now flash SuperSU SR4 2.79 Extra Delay.
-Now reboot.
-It should boot into android o, walk through setup and make sure supersu is installed.
-If it is, Congratulations you have rooted android O on your Pixel!
This method has was discovered by @Sachi315 (here)
Make sure you give him tons of thanks for getting the method up and running!
Im storing this here for my own sake testing wise please ignore https://forum.xda-developers.com/showpost.php?p=72604085&postcount=10323
Off Topic is welcome as long as its still Pixel/Root/TWRP/Development/Questions but back and forth bickering will be and should be reported.

finally, thx for this guide! will give it a try and feedback. BTW, can I share this guide with my native language? source url and your ID will be declaimed, of course.

can it be done on a locked BL?
like EE (uk) or Verizon?

y2grae said:
can it be done on a locked BL?
like EE (uk) or Verizon?
Click to expand...
Click to collapse
Nope, nor would you want to.

Queentus said:
finally, thx for this guide! will give it a try and feedback. BTW, can I share this guide with my native language? source url and your ID will be declaimed, of course.
Click to expand...
Click to collapse
As long as credit is given, by all means!!!

bobby janow said:
Nope, nor would you want to.
Click to expand...
Click to collapse
Why is that? Just curious.

bobby janow said:
Nope, nor would you want to.
Click to expand...
Click to collapse
awakenedwithin said:
Why is that? Just curious.
Click to expand...
Click to collapse
Yes I too am curious

awakenedwithin said:
Why is that? Just curious.
Click to expand...
Click to collapse
Because with a locked bootloader there are no means to recover if you screw something up. I mean none other than return the device and plead for mercy. If you want to play around, and I certainly do with my 5x, then make sure the bl is unlocked or that you can fastboot and unlock it if needed. The EE and Verizon models cannot be unlocked. I have one.

bobby janow said:
Because with a locked bootloader there are no means to recover if you screw something up. I mean none other than return the device and plead for mercy. If you want to play around, and I certainly do with my 5x, then make sure the bl is unlocked or that you can fastboot and unlock it if needed. The EE and Verizon models cannot be unlocked. I have one.
Click to expand...
Click to collapse
Oh I miss understood what you were trying to say.
Right. I should probably put unlocked bt as a requirement

eqbirvin said:
Oh I miss understood what you were trying to say.
Right. I should probably put unlocked bt as a requirement
Click to expand...
Click to collapse
You can, sure. But hopefully your walk through is read before attempting to do this and it clearly states to boot into TWRP. That's impossible with a locked bootloader.

bobby janow said:
Because with a locked bootloader there are no means to recover if you screw something up. I mean none other than return the device and plead for mercy. If you want to play around, and I certainly do with my 5x, then make sure the bl is unlocked or that you can fastboot and unlock it if needed. The EE and Verizon models cannot be unlocked. I have one.
Click to expand...
Click to collapse
Thank you for the reply!

Thanks for this. I just got a sailfish this evening. I should be trying this out tomorrow. :good:

sheesh.....becoming harder and harder to root now.....yikes

mikeprius said:
sheesh.....becoming harder and harder to root now.....yikes
Click to expand...
Click to collapse
Dev previews are always a bear at first, I do hope this doesn't become the norm though. Pixel doesn't make it any easier haha

Thanks
@eqbirvin
I successfully rooted my new sailfish with o preview following your instructions. :highfive:
One place I got stuck was not knowing that there is no recovery partition in Pixel. I tried
fastboot flash recovery twrp-3.0.2-0-RC1-fastboot-sailfish.img and obviously failed.
A little bit of searching led me to the right command
fastboot flash boot twrp-3.0.2-0-RC1-fastboot-sailfish.img
Thank you for decoding the rather cryptic post https://forum.xda-developers.com/showpost.php?p=71865004&postcount=1266 from @Sachi315 and creating a step-by-step process that works. :good::good::good:

Is that fastboot boot twrp or fastboot flash boot twrp?
Sent from my Pixel using XDA-Developers Legacy app

bobby janow said:
Is that fastboot boot twrp or fastboot flash boot twrp?
Click to expand...
Click to collapse
Boot TWRP.img, flash doesn't work on pixels

Do you always let the phone boot up normally after stock, then go into bootloader and boot TWRP, the flash the TWRP zip ?
Afterwards, do you reboot TWRP into recovery again then stock, or just flash the .zip of TWRP then go right into stock ?
The process for this has been more confusing than the Nexus b/c there are slots a and b.

eqbirvin said:
Boot TWRP.img, flash doesn't work on pixels
Click to expand...
Click to collapse
That's what I thought. Just correcting the above post is all.

mikeprius said:
Do you always let the phone boot up normally after stock, then go into bootloader and boot TWRP, the flash the TWRP zip ?
Afterwards, do you reboot TWRP into recovery again then stock, or just flash the .zip of TWRP then go right into stock ?
The process for this has been more confusing than the Nexus b/c there are slots a and b.
Click to expand...
Click to collapse
Don't boot into system after 7.1.2 flash or Android O flash. Just boot into TWRP, flash the TWRP rc2 (after dealing with internal storage issue) change to slot b (while still in TWRP) then reboot to recovery and make sure you are in slot b again. Finally flash SuperSU package.
Ugh I know. I love the pixel but is slot/partition change is a headache haha

Root question

So how do I root this thing?
Verstuurd vanaf mijn Moto E (4) met Tapatalk

aadvandersteeg said:
So how do I root this thing?
Verstuurd vanaf mijn Moto E (4) met Tapatalk
Click to expand...
Click to collapse
Did you try this?
Lucas Eugene said:
UNLOCK YOUR BOOTLOADER​
WARNING: UNLOCKING YOUR BOOTLOADER VOIDS YOUR WARRANTY.PROCEED AT YOUR OWN RISK.
NOTE: Unlocking the bootloader will Wipe/ factory reset your device, and will delete all personal data from your device such as apps, photos, messages, and settings.
INSTRUCTIONS:
Make sure to take a backup of your entire device data.
Download the Android SDK OR Download the Minimal ADB and Fastboot
Install the latest Motorola USB Drivers on your desktop. Download here.
Put your device in fastboot mode (power off, then press the power and volume down buttons simultaneously).
Open Command Prompt on androidsdk/platform-tools/ (Hold Shift and right click and press open command window here)
Connect your Phone to PC
Type this in the CMD prompt window - fastboot oem get_unlock_data
You will get a return string. Copy it. [Right Click-Mark- Mark the text by pressing the shift key-Now press Ctrl+C]
Paste all the lines together in a notepad. Remove the empty spaces.
Now go to the Motorola Site.Sign in using your Google account or Motorola ID. Scroll down the page and paste the copied string in the field at step #6. Then click on ‘Can my device be unlocked?’, after which a "REQUEST UNLOCK KEY" button will appear at the bottom of page.
To get your unlock key, select the ‘I Agree’ option. Note: You will receive an email with your Unlock Key at the email address you used to log in there.
Important – Copy the 20-character key that Motorola sent you via email. Make sure your device is connected.
Then in CMD type: fastboot devices (To check your device is connected)
Then type: fastboot oem unlock UNIQUE_KEY
NOTE: In above command, replace the word ‘UNIQUE_KEY’ with the unlock code that you got via email. Then hit enter and the unlocking process should begin. Wait for a while and soon you’ll see ‘Bootloader Unlocked’ warning on your Moto E.
To relock the bootloader:
Go to Fastboot and give the command fastboot oem lock
You can always appreciate my work by pressing the Thanks Button.:good:
Good Day
Click to expand...
Click to collapse
---------- Post added at 06:50 AM ---------- Previous post was at 06:48 AM ----------
After you unlock your bootloader you can flash SuperSU in a custom recovery but someone would need to make one of those

mendelgordon said:
Did you try this?
---------- Post added at 06:50 AM ---------- Previous post was at 06:48 AM ----------
After you unlock your bootloader you can flash SuperSU in a custom recovery but someone would need to make one of those
Click to expand...
Click to collapse
No I haven't.
Verstuurd vanaf mijn Moto E (4) met Tapatalk

Root Moto E4 (XT1768)
Here's what worked for me (I have the snapdragon version of this phone):
Follow the following at your own risk!
If you're an expert with rooting, the twrp build that works for this phone is at https://forum.xda-developers.com/g5/development/unofficial-twrp-3-1-0-0-moto-g5-t3574450. Otherwise, details are below.
I'm assuming whoever is reading this has some rooting familiarity.
The short version is:
1. Unlock the boot loader
2. Boot twrp
3. Flash su and no-verify zip
4. Reboot to root'd phone.
0. Prepare
Get the following:
i. Motorola usb drivers: your pc won't talk properly with the device without these. google around for these.
ii. adb and fastboot: used to unlock the bootloader and boot twrp https://developer.android.com/studio/releases/platform-tools.html
iii. su zip: I used phh's https://superuser.phh.me/superuser-r259.zip you can probably get chainfire's or whatever else working
iv. no-verity-opt-encrypt-5.1 zip: https://www.androidfilehost.com/?fid=24459283995297893
v. twrp: this build seems to work for the E4 https://forum.xda-developers.com/g5/development/unofficial-twrp-3-1-0-0-moto-g5-t3574450
vi: (optional) stock roms: in case you need to go back https://androidfilehost.com/?w=files&flid=195327 applying these with RSD lite (if RSD can *actually* detect your phone) or manually (https://www.youtube.com/watch?v=njXQYn53SPc) should work.
0.1 Prepare the phone:
Get developer options on android and turn on "OEM unlocking" and "USB debugging".
Test that your pc can see the phone by running:
Code:
adb devices
0.2 Dump your zips onto the phone:
For this, I dumped the superuser-r259.zip and no-verity-opt-encrypt-5.1 zip onto an sd card (formatted as external).
I didn't try this without an sd card.
0.3 (optional) install the superuser apk
Install the apk before flashing to get root immediately after booting back from twrp.
1. Unlock the boot loader
The post here details how to unlock the motorola boot loader. Keep in mind it will probably void any warranty on the phone. This process involves signing up for a motorola account to get the unlock code.
https://forum.xda-developers.com/showpost.php?p=72878183&postcount=2
2. Boot twrp
Read the warnings in https://forum.xda-developers.com/g5/development/unofficial-twrp-3-1-0-0-moto-g5-t3574450
Because we'll be flashing stuff here, the phone may refuse to boot afterwards since a part of it changed without its knowledge. That's why the no-verify zip is necessary, to bypass this check on boot.
Put your phone in fastboot and run:
Code:
fastboot boot twrp-3.1.0-0-cedric.img
3. Flash su and no-verify zip
In twrp, hit cancel on the decryption screen and start twrp in read.
Go to install, switch to sd card, find the the zip location and flash su then no-verify.
4. Reboot
That should be it. When you reboot back to android, install the superuser apk if you haven't already and feel free to use your root.

Moto e4 is not on the list of the phones that can be unlocked, I have already chatted with moto customer care and they told me its bootloader can't b unlocked yet.

fountain1 said:
Moto e4 is not on the list of the phones that can be unlocked, I have already chatted with moto customer care and they told me its bootloader can't b unlocked yet.
Click to expand...
Click to collapse
So how did mer2017 do it?

These are the important questions.
Like seriously. How the hell.

gogozombiii said:
These are the important questions.
Like seriously. How the hell.
Click to expand...
Click to collapse
I'm saying it obviously works because it's been done
---------- Post added at 10:11 PM ---------- Previous post was at 09:28 PM ----------
I just unlocked my bootloader so it obviously works
---------- Post added at 10:11 PM ---------- Previous post was at 10:11 PM ----------
I just unlocked my bootloader so it obviously works

Now my phone isn't booting, says it can't load the kernel, I flashed the no verify thing but that isn't helping
---------- Post added at 11:49 PM ---------- Previous post was at 11:44 PM ----------
And now after turning it on and off many times it's working!

I still can't figure out how to root it, any ideas? I flashed SuperSU in TWRP many times and it's still not working.

Maybe magisk 13?
Sent from my Moto G (5) Plus using Tapatalk

vettejock99 said:
Maybe magisk 13?
Sent from my Moto G (5) Plus using Tapatalk
Click to expand...
Click to collapse
I tried it, and magisk 12, and pph's superuser. Now what ?

mendelgordon said:
I tried it, and magisk 12, and pph's superuser. Now what ?
Click to expand...
Click to collapse
Kingoroot and kingroot and kingroot pc all don't work

mendelgordon said:
Kingoroot and kingroot and kingroot pc all don't work
Click to expand...
Click to collapse
Thanks for the update
Sent from my Moto G (5) Plus using Tapatalk

I've successfully gotten my Moto e4 rooted. Proof:
{
"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"
}

L551 said:
I've successfully gotten my Moto e4 rooted. Proof:
Click to expand...
Click to collapse
We know it's doable, we aren't looking for proof, we are looking for how to do it ourselves

mendelgordon said:
We know it's doable, we aren't looking for proof, we are looking for how to do it ourselves
Click to expand...
Click to collapse
First, I unlocked the bootloader through motorola's tool. Second, as there is no official TWRP for the e4, I used the Moto G5's TWRP img to BOOT from. (Flashing will not work, boot from it using fastboot) https://forum.xda-developers.com/g5/development/unofficial-twrp-3-1-0-0-moto-g5-t3574450
After in TWRP, I made a backup of stock everything. You'll need it if something goes wrong during the entire process.
After making sure that I was backed up, I then flashed Magisk 13.1. After that successfully flashed, I then flashed this file: https://www.androidfilehost.com/?fid=24459283995297893 . After rebooting (This may take a while), everything looked much the same, and it may look the same for you as well.
In my own case, the Magisk ZIP that I flashed did not install the Magisk Manager. Install that via the APK available in the Magisk 13.1 thread. After I did all that, I had successful root.

L551 said:
First, I unlocked the bootloader through motorola's tool. Second, as there is no official TWRP for the e4, I used the Moto G5's TWRP img to BOOT from. (Flashing will not work, boot from it using fastboot) https://forum.xda-developers.com/g5/development/unofficial-twrp-3-1-0-0-moto-g5-t3574450
After in TWRP, I made a backup of stock everything. You'll need it if something goes wrong during the entire process.
After making sure that I was backed up, I then flashed Magisk 13.1. After that successfully flashed, I then flashed this file: https://www.androidfilehost.com/?fid=24459283995297893 . After rebooting (This may take a while), everything looked much the same, and it may look the same for you as well.
In my own case, the Magisk ZIP that I flashed did not install the Magisk Manager. Install that via the APK available in the Magisk 13.1 thread. After I did all that, I had successful root.
Click to expand...
Click to collapse
I did all that but the magisk zip used to say it didn't Support my boot image and now it's just giving error 255

mendelgordon said:
I did all that but the magisk zip used to say it didn't Support my boot image and now it's just giving error 255
Click to expand...
Click to collapse
Hmm, I tried again and it gave an error that it couldn't mount the magisk image, here's some logs

Magisk won't install if your boot image is anything other than stock. So if you've attempted other methods, you'll need to restore the boot to stock.

this aint a phone.. Its Spawn from the darkest most vile debths of confusion!

First off i am not a noob. kinda.
the story:
I received this phone its a xt1625 prime variant (i think) already booting straight into boot loader (no system, recovery, bpmode, qmode)
just right into boot loader. So i figured it just needs flashed lets hit xda, get knowledge. it is now going on 6 months of off and on trying to flash this evil entity. this boot loader on here is like herpes, you cannot get rid of it (so i have heard). I have attempted every tutorial, downloaded every rom, twrp, firmware, etc possible to even imagine. Even tried all this in windows. ubuntu, etc. by every firmware i mean every link from here firmware.center/firmware/Motorola/Moto G4 (plus), add your own http, for every variant. and yet this boot loader remains. Even put it under a magnet from a 12' sub woofer over night. Taken the battery out for a week, overloading the chip with a car battery, nothing, the evil thing remains.
so my question is did i miss anything? also does anyone know the name and address of whomever wrote the coding for the gpt.bin,oem.img,modem,boot.img?
i'd like to have a chat with them personally.
oh and just for the record motorola will gladly replace the $159 dollar phone for $125 dollars, but have no idea how to fix it.
some of the firmware AMZ_NPJS25.93-14-7 through 14-10 will flash all the way then reboot into boot loader like nothing happened.
no blur or ota updates will flash/sideload stating that they are looking for athene and not athene_amz. yet no retail athene firmware will flash just athene_amz. absolutely no Mp firmware at all just Npjs. but only 7,8,10. which does nothing as i said before.

Can you post the get var info for this device please?
1) boot the device to bootloader
2) connect to your computer via USB
3) in the ADB terminal, type 'fastboot getvar all' without quotes and post the output here please, should be a list of device variables
Up to you if you wish to blank out the imei.

Have you unlocked your bootloader first?

motorola will not unlock the bootloader, which led me to believe its a prime.

i will do the getvar when i am home from work tonight.

and. thanks for responding

{
"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"
}

http://tinypic.com/r/qz554x/9

https://drive.google.com/file/d/1eF_el1N2Ve_APninuzEqvOlTSG1kSXCE/view?usp=drivesdk

those are getvar results.. or sad attempts at displaying them.

Thanks for the getvar log. According to the log:
The bootloader is locked (OEM_locked secure state), so no flashing any old ROMs. Also expected from devices with Amazon firmware, Motorola unlock keys won't work. G4 XT1625 as you mentioned
Unfortunately, the device is flashed with the latest NPJ25.93-14.7 US firmware for Amazon devices. Unfortunately we don't have access to that firmware (not been leaked on firmware.center or the Motorola Firmware Team on Android File Host), and because of the above locked bootloader, other firmware will be rejected as you've discovered. Therefore, you likely will have to wait for a leak of NPJ25.93-14.7 or later Amazon firmware for another try.
Can I ask what you mean by the device booting straight to bootloader - do you mean that powering on you'll only get the bootloader, and attempts to boot to recovery/start just send you back to the bootloader?

how would one go about formatting a phone like a hard drive just totally wipe it. Start new i am guessing it couldn't be that easy or every one would.

yes no attempt to start at all. everything leads back to fastboot mode.

its like the other partitions are not even there.

@Saul-66 as echo92 has previously said there is no latest stock images available to flash on your Amazon device,
but i have a little experiment to test,
you can try flashing older firmware but with latest gpt and Bootloader,
Also keep in mind if it boots, don't take OTA, it will brick again your device.
For safety, i will go steps by steps after confirmation of result.
First clean adb/fastboot folder if you have extracted any firmware in it, keep adb/fastboot files, or extract again in new folder, (Just for clean work and confusion)
Get OTA Update zip of September patch for Amazon device from here: https://forum.xda-developers.com/moto-g4-plus/how-to/amazon-prime-ads-moto-g4-september-t3703034
Take gpt.bin and Bootloader.img from that zip. (Delete remaining) put in adb/fastboot folder.
For now, use gpt and Bootloader commands only:
- fastboot flash partition gpt.bin
- fastboot flash bootloader bootloader.img
Tell us if those are getting flashed ?
Put screenshot of command prompt screen.
Then i will tell you next thing to go..

echo92 said:
Thanks for the getvar log. According to the log:
The bootloader is locked (OEM_locked secure state), so no flashing any old ROMs. Also expected from devices with Amazon firmware, Motorola unlock keys won't work. G4 XT1625 as you mentioned
Unfortunately, the device is flashed with the latest NPJ25.93-14.7 US firmware for Amazon devices. Unfortunately we don't have access to that firmware (not been leaked on firmware.center or the Motorola Firmware Team on Android File Host), and because of the above locked bootloader, other firmware will be rejected as you've discovered. Therefore, you likely will have to wait for a leak of NPJ25.93-14.7 or later Amazon firmware for another try.
Can I ask what you mean by the device booting straight to bootloader - do you mean that powering on you'll only get the bootloader, and attempts to boot to recovery/start just send you back to the bootloader?
Click to expand...
Click to collapse
Well if nothing else at least part of the mystery is solved. thank you for the light at the end of the tunnel!

____Mdd said:
@Saul-66 as echo92 has previously said there is no latest stock images available to flash on your Amazon device,
but i have a little experiment to test,
you can try flashing older firmware but with latest gpt and Bootloader,
Also keep in mind if it boots, don't take OTA, it will brick again your device.
For safety, i will go steps by steps after confirmation of result.
First clean adb/fastboot folder if you have extracted any firmware in it, keep adb/fastboot files, or extract again in new folder, (Just for clean work and confusion)
Get OTA Update zip of September patch for Amazon device from here: https://forum.xda-developers.com/moto-g4-plus/how-to/amazon-prime-ads-moto-g4-september-t3703034
Take gpt.bin and Bootloader.img from that zip. (Delete remaining) put in adb/fastboot folder.
For now, use gpt and Bootloader commands only:
- fastboot flash partition gpt.bin
- fastboot flash bootloader bootloader.img
Tell us if those are getting flashed ?
Put screenshot of command prompt screen.
Then i will tell you next thing to go..
Click to expand...
Click to collapse
There is no bootloader.img in Blur_Version.25.231.5.athene_amz.amz.en.US.zip
so i would have to probably take it out of ATHENE_AMZ_NPJ25.93-14.5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml ?
Edit: they both say BL:B1.06 so should be the same in theory.

Saul-66 said:
There is no bootloader.img in Blur_Version.25.231.5.athene_amz.amz.en.US.zip
so i would have to probably take it out of ATHENE_AMZ_NPJ25.93-14.5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml ?
Click to expand...
Click to collapse
In above post, you said, mystery is solved!
Then there is no need of those files right ? Or i didn't get it?
(Additionally: Bootloader wasn't updated in September patch, so it may be not included in that zip.)

____Mdd said:
In above post, you said, mystery is solved!
Then there is no need of those files right ? Or i didn't get it?
(Additionally: Bootloader wasn't updated in September patch, so it may be not included in that zip.)
Click to expand...
Click to collapse
part of the mystery is solved. tis what i said.

[GUIDE] Convert TMO to EU via MSM Tool, no SIM Unlock or Bootloader Unlock needed!

*** Use this at your very own risk.
*** You will lose all data
*** Backup your working modem and persist, just in case
*** Read the entire post and follow the steps closely before asking for help. Post all error messages and steps you took. Screenshots and MSM logs will be best.
!!! I have officially retired my 8T, and can no longer provide additional support on this device !!!​
It's finally here! A MSM tool that will convert your T-Mobile OnePlus8T+5G to EU KB05BA. From here you can local upgrade to any OOS flavor you want. This gives you Local Upgrade option, faster upgrades, open betas, dual SIM, and more! In fact, after conversion, you can unlock the bootloader without the unlock token (still need to be SIM unlocked, but in case you don't want to wait for the unlock token or if OnePlus's website is broken)!
If you are still SIM locked, you lose the Unlock app for when your device becomes unlocked, it's only available in the stock TMO ROM. If you want to go back to TMO ROM at any point, flash back with the TMO MSM: https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4180981/
Steps:
Download the MSM Conversion package:
AFH
MD5: 5ddb543c8a5e7587e0b2ad24d2025e77
Run MsmDownloadTool V4.0.exe (Windows 7 users may need to run the win7 version included)
Select User type: "Other" and press Next.
Press "Start". Don't mess with the default settings.
Put your phone in EDL mode.
Code:
adb reboot edl
or completely turn off your device, hold vol up + vol down and plug in the cable.
Wait about 5 minutes while it works.
Done! If you keep the bootloader locked and run it stock, the About Phone page will be missing some fields.
If you run into any MSM tool issues, most likely you have a driver problem. See the FAQ in @Some_Random_Username's post
Instructions to Bootloader Unlock a SIM locked device:
In ADB:
Code:
adb shell pm uninstall -k --user 0 com.qualcomm.qti.uim
Reboot
Go to dev settings and enable OEM Unlock
Reboot to bootloader
Code:
fastboot oem unlock
No unlock.bin needed
Old fastboot method
*** Know how to use the MSMTool, Don't start before figuring it out.
*** DO NOT ATTEMPT THIS IF YOU ARE NOT FAMILIAR WITH THE STEPS DESCRIBED IN THIS GUIDE
* The steps in this guide will convert your TMO KB2007/KB05CB to Global 11.0.5.6.KB05AA, or EU 11.0.3.4.KB05BA
* NR and LTE bands are flashed in nvRAM, not in modem.img or any other partition. You cannot get global bands by flashing a global ROM, nor can you lose TMO bands by flashing another ROM.
* Instructions are the same as running any other MSM unbrick tool.
* You can use this guide to convert to your own variant by extracting payload and flashing from a full OTA. See manual instructions towards the end.
* Use the latest platform tools: https://developer.android.com/studio/releases/platform-tools, https://forum.xda-developers.com/android/general/tool-adb-fastboot-installer-tool-windows-t3999445. DO NOT USE MINIMAL ADB, it has not been updated for years and will cause a crash where you'll need to MSM back to stock.
* Make sure your drivers are up to date. This guide will not walk you through setting up platform tools or updating drivers. When encountering fastboot issues, make sure to include the output of fastboot --version in your post.
* Do not ask for OTAs, MSMs, or anything else not related to the steps described herein. There are plenty of threads around for those.
* This guide does not pertain to Cyberpunk conversion. See other threads.
* This guide converts you to an older firmware so you can take a FULL OTA via Oxygen Updater. Do not skip this step if you want a stable build.
Steps to convert your device to Global or EU
As simple as possible:
You need your device bootloader and SIM unlocked. Follow the instructions here (It says 6T, but applies to all OP devices): https://support.oneplus.com/app/answers/detail/a_id/588/~/how-to-unlock-bootloader-for-oneplus-6t-(t-mobile-edition)
Download and unzip the conversion package:
Global 11.0.5.6
EU 11.0.3.4
Boot to fastbootd.
From adb:
Code:
adb reboot fastboot
From fastboot/bootloader:
Code:
fastboot reboot fastboot
If you are having trouble booting into fastbootd, and have a FC number at the bottom of the bootloader screen, you'll need to MSM to factory first.
[*]You should be at a screen that says "fastbootd" on top. DO NOT CONTINUE IF YOU ARE NOT HERE. SEE HIDDEN FOR AN EXAMPLE.
{
"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"
}
Execute "flash_all.bat" for Windows, or "flash_all.sh" for Linux, from the unzipped directory from step 2 as cwd.
Optional: Flash magisk'd boot
Code:
fastboot flash boot boot_magisk_patched.img
Reboot into recovery, and wipe everything.
Once fully booted, download Oxygen Updater, set your device to OnePlus 8T of your regional choice and local upgrade to the latest OTA of your regional choice.
Optional: You can re-lock your bootloader at thois point. DO NOT TRY before the full OTA upgrade above, or you'll have to MSM.
Manually:
Unlock bootloader
Download the full OTA of your choosing
Extract the OTA payload with https://github.com/vm03/payload_dumper or https://androidfilehost.com/?fid=818070582850510260
With the output of the payload as your cwd, execute:
Code:
fastboot flash product product.img
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash boot boot.img
fastboot flash cmnlib cmnlib.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash devcfg devcfg.img
fastboot flash dsp dsp.img
fastboot flash dtbo dtbo.img
fastboot flash featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash logo logo.img
fastboot flash mdm_oem_stanvbk mdm_oem_stanvbk.img
fastboot flash modem modem.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash odm odm.img
fastboot flash qupfw qupfw.img
fastboot flash recovery recovery.img
fastboot flash spunvm spunvm.img
fastboot flash storsec storsec.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot flash vendor vendor.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
Replace boot.img with your magisk'd boot if desired
Reboot to recovery and wipe everything
Troubleshooting
Error: "remote: no such file or directory"
You are not in the correct cwd. Fastboot needs to be accessible from the same directory as the .img files, so fix your PATH or make a copy fastboot.exe in the same directory as the .img files
Error: "remote: Flashing is not allowed for Critical Partitions"
You are not in fastbootd. Check step 4.
Error: "Invalid sparse file format at header magic"
Ignore this message, not an error
Special thanks to:
@jwarrior319 for the initial linux script
@cammykool and @awr128 for helping debug some of the steps and clarifying pain points
@radiohead7778580 for a better Global conversion
Fixing the About Phone page
These steps are optional, and will fix the "About Phone" page. There are no performance differences.
You need to rooted with Magisk
Download the fix: here
In the Modules page in MagiskManager, Install the downloaded zip file via "Install from storage"
Reboot, the About Phone page is filled out.
Issues so far (please post if you run into more):
In OOS11, "About phone" page does not work properly.
Use the magisk module above to fix it.
In OOS12, Dual SIM is not supported.
A11 based A12 ROMs support Dual SIM after conversion, use my enable_dsds module.
Unlocked bootloader without unlock_token must be done while in OOS11, as OOS12+ ABL will check that a token is needed

craznazn said:
*** Use this at your very own risk.
*** You will lose all data
*** Backup your working modem and persist, just in case
*** Know how to use the MSMTool, in case you do soft brick anything
*** DO NOT ATTEMPT THIS IF YOU ARE EASILY OFFENDED WHEN THINGS DON'T WORK PERFECTLY
* I've done this with the EU KB05BA.
* You can patched the boot.img prior to doing all this, to make things easier if you want root in your target build.
* This method should work for other builds, if you can find a full OTA of KB05AA (for Intl/Global)
Download the EU Full OTA. Or use another FULL OTA if you have it:
11.0.1.2
11.0.3.4
Extract the payload.bin, and dump the payload using Payload Dumper
The "About Phone" screen seems to be broken: Processor, Camera, and Screen all show "None"
5G
AOD
Fingerprint sensor
Click to expand...
Click to collapse
Nice! Thank you. So aside from the "About Phone" info not displaying correctly, am I understanding everything else appears to be working? My apologies if I missed something, reading this from mobile on XDA Labs.
Edit: I am SIM unlocked & I do have my bootloader unlock token so I should be good (just haven't actually unlocked my bootloader YET). I think you may want to mention those requirements in the OP, hopefully to help avoid unnecessary questions. It seems obvious, but you know... it's the internet.
Sent from my OnePlus 8T using XDA Labs

stmims1124 said:
Nice! Thank you. So aside from the "About Phone" info not displaying correctly, am I understanding everything else appears to be working? My apologies if I missed something, reading this from mobile on XDA Labs.
Sent from my OnePlus 8T using XDA Labs
Click to expand...
Click to collapse
I'm just starting to play with it now, so far everything I've been doing seems to work. I also can't get SafetyNET to pass, so that might be an issue for some.

craznazn said:
I'm just starting to play with it now, so far everything I've been doing seems to work. I also can't get SafetyNET to pass, so that might be an issue for some.
Click to expand...
Click to collapse
Perhaps an update to the very latest Magisk Canary & Magisk manager might help? Canary gets updated often, and I ran into that a few times on my 7 Pro. It's also entirely possible it may take extra work...I don't know, but I hope not!
Sent from my OnePlus 8T using XDA Labs
---------- Post added at 02:58 AM ---------- Previous post was at 02:57 AM ----------
craznazn said:
I'm just starting to play with it now, so far everything I've been doing seems to work. I also can't get SafetyNET to pass, so that might be an issue for some.
Click to expand...
Click to collapse
Oh, also I'm sure this is pretty obvious but I've also made this mistake... Forgot to turn on Magisk Hide and then scratch my head wondering why it won't pass.
Sent from my OnePlus 8T using XDA Labs

stmims1124 said:
Oh, also I'm sure this is pretty obvious but I've also made this mistake... Forgot to turn on Magisk Hide and then scratch my head wondering why it won't pass.
Click to expand...
Click to collapse
LOL that was it... feels like a dummy man

craznazn said:
LOL that was it... feels like a dummy man
Click to expand...
Click to collapse
Dude, I've doing this s**t since 2010 with the HTC Evo and still do that type of s**t all the damn time. I just get comfortable (cocky is more accurate), like, "oh I know what to do, I can do this in my sleep"...and then yeah, scratching my head, wiping my phone or some dumb s**t because I didn't do the easy trouble shooting stuff.
Sent from my OnePlus 8T using XDA Labs

SafetyNet is fine if you do the global Magisk Hide

So if I opt to not root. Will I just get OTAs like the normal global variant? I assume so. But just curious.

craznazn said:
*** Use this at your very own risk.
*** You will lose all data
*** Backup your working modem and persist, just in case
*** Know how to use the MSMTool, in case you do soft brick anything
*** DO NOT ATTEMPT THIS IF YOU ARE EASILY OFFENDED WHEN THINGS DON'T WORK PERFECTLY
* I've done this with the EU KB05BA.
* You can patched the boot.img prior to doing all this, to make things easier if you want root in your target build.
* This method should work for other builds, if you can find a full OTA of KB05AA (for Intl/Global)
You need your device bootloader unlocked. Follow instrustions here (It says 6T, but applies to all OP devices): https://support.oneplus.com/app/ans...-bootloader-for-oneplus-6t-(t-mobile-edition)
Download the EU Full OTA. Or use another FULL OTA if you have it:
11.0.1.2
11.0.2.3
11.0.3.4
Also check this thread
Extract the payload.bin, and dump the payload using Payload Dumper
Execute the following starting from ADB and in the payload output directory. You can start at Fastboot if you are already there:
I haven't used it much yet, but here's what I know so far:
Issues (please post if you run into more):
The "About Phone" screen seems to be broken: Processor, Camera, and Screen all show "None"
What appears to work:
5G
Dual SIM, though I can't test without a proper 2-SIM tray
AOD
Fingerprint sensor
Click to expand...
Click to collapse
If you have the dual SIM tray from the the 7T it will work in the 8T, doesn't fit perfectly flat to the body (if you have a case, probably wouldn't he able to tell) but it will read the sim card 1, I can't confirm it will read sim 2, maybe someone could try, or see if an 8 sim tray would work.

awr128 said:
If you have the dual SIM tray from the the 7T it will work in the 8T, doesn't fit perfectly flat to the body (if you have a case, probably wouldn't he able to tell) but it will read the sim card 1, I can't confirm it will read sim 2, maybe someone could try, or see if an 8 sim tray would work.
Click to expand...
Click to collapse
The dual sim tray made for the 8t can be bought on ebay
Sent from my OnePlus KB2007 using XDA Labs

jwarrior319 said:
The dual sim tray made for the 8t can be bought on ebay
Click to expand...
Click to collapse
Nice, I looked for one a few days ago and couldn't find any.

LLStarks said:
SafetyNet is fine if you do the global Magisk Hide
Click to expand...
Click to collapse
Whats going on buddy, nice to see you! Broke down and bought the 8t as well I see

I am successfully on the European. I extracted the payload before but I wasn't flashing correctly in fastboot, had everything working except the phone.
Now all good..
Thing to test is to see if I lose data like I did randomly with the 8.

cammykool said:
So if I opt to not root. Will I just get OTAs like the normal global variant? I assume so. But just curious.
Click to expand...
Click to collapse
Not sure yet, it might not but the local upgrade option is now available, at least in the EU version. I tested that to install the EU version on the second slot and it worked fine.

After we follow the guide can we just do the local upgrade option as normal

jwarrior319 said:
The dual sim tray made for the 8t can be bought on ebay
Sent from my OnePlus KB2007 using XDA Labs
Click to expand...
Click to collapse
I couldn't find one, but it looks like the 8 tray may fit so I got one of those. Even if it doesn't work, it's not that expensive until I can find a dual-tray 8T

cammykool said:
After we follow the guide can we just do the local upgrade option as normal
Click to expand...
Click to collapse
The option is there.

This doesn't seem as simple, I think I'll wait for a easier way using the MSM Tool method to convert like it was with the other T-Mobile OP devices

SmileBigNow said:
This doesn't seem as simple, I think I'll wait for a easier way using the MSM Tool method to convert like it was with the other T-Mobile OP devices
Click to expand...
Click to collapse
If ur BL is unlocked u shld be able to just dl oxygen updater, select whichever variant u want to convert to, dl the local upgrade apk and after dl'ing the update to internal go into an activity launcher and launch the local upgrade apk and install. Then once converted extract ur boot img from the OTA zip and patch magisk if u want root u don't even have to be rooted to covert

Shooter7889 said:
If ur BL is unlocked u shld be able to just dl oxygen updater, select whichever variant u want to convert to, dl the local upgrade apk and after dl'ing the update to internal go into an activity launcher and launch the local upgrade apk and install. Then once converted extract ur boot img from the OTA zip and patch magisk if u want root u don't even have to be rooted to covert
Click to expand...
Click to collapse
if this works ill do this, BUt currently bsdiff4 is kicking my ass and refuses to install