Database Users

[GUIDE]Android 11 how to root T-MOBILE OP8 5G - OnePlus 8 Guides, News, & Discussion

THIS GUIDE IS FOR THE T-MOBILE ONEPLUS 8 5G ONLY!!!!
This method has only been tested on the above mentioned device. It may be possible to use *parts* of this guide on other oneplus/android devices, but you do so at your own risk!
Furthermore no warranty or liability of any kind is offered or implied for any damages to any person(s), devices, or other property by following, or otherwise using any information contained in this guide be it inaccurate information or otherwise.
By using this guide you're agreeing to these terms.
MAKE SURE TO READ THROUGH THE ENTIRE GUIDE BEFORE ATTEMPTING TO FOLLOW IT!
That said I've done my best to ensure this guide is an accurate representaion of the steps I followed to do the things laid out in this guide.
Required items:
Bootloader unlock token from OnePlus.
adb fastboot drivers installed to path. (Not provided)
Now that all that is out of the way. Let's get started!​Rooting with provided boot.img
Spoiler: Click to show
1. Make sure that you are running some version of Android 11 via Settings>About phone.
2. Take note of your Build Number you'll need that later.
3. Click on build number five times to enable developer options.
4. Navigate to developer options under Settings>System>Developer options.
Turn on oem unlocking, as well as usb debugging & turn off automatic updates.
5. Open a cmd prompt on your pc, or terminal on linux. Enter the following lines.
Code:
adb devices
*Check the always allow from this device checkbox then hit allow.
You should see your device listed. If it says unrecognized re-enter the line above.
Code:
adb reboot bootloader
*Your device should reboot into fastboot. Once it has proceed.
6. Now we must unlock the bootloader. cd to the directory where you have saved your unlock token.
For example if you saved it to the Desktop of a windows machine the directory would most likely be
users/*yourusernamehere*/Desktop.
7. Enter the following lines. One at a time.
Code:
fastboot flash cust-unlock unlock_code.bin
Code:
fastboot oem unlock
*Follow the prompts on your device to unlock your bootloader *****THIS WILL WIPE YOUR DEVICE SO MAKE SURE TO BACKUP YOUR DATA*****
8. Get past setup on your device re-enable developer options, and usb debugging, turn off automatic updates.
9. Follow the process to get back into fastboot via adb.
10. Remember your build number. Download the boot image that matches your build number here:
https://www.androidfilehost.com/?w=files&flid=322713
(I've only tested this on the device I pulled from, but unless something drastic has changed since the last time I dealt with stuff like this these should work fine as long as the device is a Tmobile OP8, and the build number is the same.)
(I will try to keep this updated as new updates are released, but work keeps me rather busy so it may not always be quickly.)
11. Now open a cmd prompt (if you haven't already) navigate to where you saved the boot img. Enter the following.
Code:
fastboot devices
*You see your device listed in that case proceed.
Code:
fastboot flash boot_a boot.img
*If the process completes without errors then continue
then
Code:
fastboot flash boot_b boot.img
*If the process completes without errors then continue
finally
Code:
fastboot reboot
12. Your device should boot up. Install the magisk manager app if it is not installed. Open MM & follow the prompts to finish setup. Enable magisk hide, and reboot. SafetyNet should pass.
Congrats! You have a Tmobile Oneplus 8 with root!
Using/Acquiring your own boot.img
Spoiler: Click to show
This section of the guide will assume you are familiar with using adb/adb shell commands, as well as being familiar with android, and other terms.
To put it plainly it will be a lot less hand holdy lol. This process requires root. So technically you won't be required to pull you're own image.
However it should be noted that doing so will streamline the process for later in the event that you need to restore to stock, and re-root later on.
*****YOU MUST BEGIN ON ANDROID 10 TO USE THIS METHOD*****
If you are not downgrade via the msmtool, re-unlock your bootloader & make sure automatic updates are disabled in developer options.
Let's begin.
1. Connect your phone to your pc with usb debugging enabled & reboot into fastboot.
2. Copy a Magisk zip file to your internal storage.
3. Boot the latest twrp (DO NOT TRY TO BOOT OR INSTALL TWRP ON AN ANDROID 11 DEVICE TWRP DOES NOT CURRENTLY SUPPORT IT!!!!)
Code:
fastboot boot recovery "twrp.img"
*****replace twrp.img with the filename of your twrp minus the quotes.*****
4. Flash the magisk zip and reboot.
5. Download & install the latest update, but do not reboot.
6. Open magisk click install>Install to inactive slot(after ota).
*Before rebooting make a note of which slot magisk says it's installing to.
We will need this later to know which boot image slot to pull from.
7. Reboot through magisk.
*You should now be on the latest update with root.
8.Open a cmd prompt and enter the following
Code:
adb shell
then
Code:
su
*grant the su request on your device.
9. Now we must find the location of both boot paritiions. Enter the following
Code:
ls /dev/block/bootdevice/by-name/ -all
10. This will display a list of all partitions on the device there are 2 we must make a note of, and 1 that is optional but highly recommended.
These are boot_a, boot_b, and optionally persist.
Open a notepad, and copy and those lines into a txt document and save.
(You can optionally delete the part of the lines before boot_a, boot_b etc. To make it easier to read.)
11. Now whichever slot magisk flashed to is what we need to pull from open your previously saved txt document, and find the path to which slot it is
Ex: /dev/block/******
12. In the command propt enter the following.
Code:
dd if=/dev/block/***** of=/sdcard/boot.img
*****Replace the "*'s" with the rest of the path for the slot you need!*****
NOTE: If you wish to backup your persist partition then repeat step 12. Replacing the "if" path with that of the persist partition you made note of earlier, and the boot.img part of the "of" path with persist.img.
13. Copy those files from your internal storage to your pc using explorer or adb pull -p from the command prompt in the directory you would like them stored.
And that's it Congrats! You've learned how to pull your own boot.img from your device, and have root on android 11!
If you ever need to restore from stock you can just update back to android 11, and flash your boot images via fastboot.
Note: I would recommend storing your boot images in folders named as the Build Number to ensure you don't mix them up. YOU WILL NEED TO REPULL YOUR BOOT IMAGES AFTER EVERY UPDATE!
Updating in the future
Spoiler: Click to show
To update to new Android versions & keep root follow these steps.
1. Make sure automatic updates in developer options are off.
2. Download and install the update, BUT DO NOT REBOOT.
3. Open magisk select install>Install to inactive slot(after ota).
4. Reboot through magisk.
5. You should reboot into the update with root preserved.
6. Pull the new patched boot image if you wish.
A few things to leave you with.
It's been a while since I've dabbled with this side of development (I've mostly been focusing on app development, and occasionally magisk rom development.)
So.
Some things, and processes in this guide may change as future updates occur.
I'll try to update it as neccesary, but my work usually keeps me pretty busy.
Don't be afraid to ask any questions or suggest any corrections to this guide.
I'll do my best help anyone with any problems or issues, but be sure to provide as much information as humanly possbile to help me or others assist with the problem.​

(Reserved)

Does bootloader need unlocked through tmobile

wwe9112 said:
Does bootloader need unlocked through tmobile
Click to expand...
Click to collapse
Yes you still need your bootloader unlocked through OnePlus/T-Mobile. Sorry for the confusion. I'll add that to the Op. I just wanted to lay out how to obtain/provide a patched boot image for T-mobile users on Tmo's OxygenOS. Since all I've seen is global/Eu versions.

1 is there a way to unlock and root without wipe? :C
2 What could be the advantage of changing from t-mobile version to global? is there a hardware diference or something to be afraid of?
Thank you

rophiroth said:
1 is there a way to unlock and root without wipe? :C
2 What could be the advantage of changing from t-mobile version to global? is there a hardware diference or something to be afraid of?
Thank you
Click to expand...
Click to collapse
1. No unlocking the bootloader will always perform a factory reset.
2. This guide isn't for that. It serves as a repository for T-Mobile variant patched boot, or explains how to get your own images to flash via fastboot to be able to root past Android 10. Since Twrp doesn't support Android 11 yet.
As for the perks of switching to global a few I can think of would be.
No T-mo bloat.
Updates from Oneplus containing all features.
I believe it enables the local upgrade option for downloading, and installing updates downloaded via The OP website. (Only global/non tmo updates are available on the site).
I'm sure there are probably a few other minor differences.
As far as I'm aware the process isn't as straight forward as it used to be with the 6t, 7 etc. So there is more of a potential for something to go wrong. Could be off putting for some I suppose. For more details I suggest looking at one of the conversion guides.

TheLogicalGamer said:
1. No unlocking the bootloader will always perform a factory reset.
Click to expand...
Click to collapse
Why a factory reset should be needed in that part... :/
thank you

rophiroth said:
Why a factory reset should be needed in that part... :/
thank you
Click to expand...
Click to collapse
I'm not entirely sure as to why. It just part of the process (on every device with an unlockable bootloader).
Aside from potentially saving on troubleshooting down the line. Perhaps it's a liability issue. Since technically unlocking the bootloader does make your device less secure. The manufacturer can't be to blame for stolen/lost data since anything you would've put on the device would have been put there yourself. The warning message doesn't appear until after the bootloader is unlocked. So by wiping the device before hand/during the process it insures that you have seen the warning, and are choosing to put said data on the device of your own free will after having been warned.
So my best guess would be to protect themselves from potential lawsuits. Assuming that there is no technical reason for needing it. (Which I'm not entirely sure that there isn't).

Im in troubles. I do flash the cust-unlock, no errors but nothing really happens T,T im using android 11
Code:
PS C:\WINDOWS\system32> fastboot flash cust-unlock 'C:\Android\Oneplus 8\unlock_code.bin'
target reported max download size of 805306368 bytes
sending 'cust-unlock' (0 KB)...
OKAY [ 0.008s]
writing 'cust-unlock'...
(bootloader) Device is unlocked.
OKAY [ 0.014s]
finished. total time: 0.027s
When I try to flash anything else, it says:
PS C:\WINDOWS\system32> fastboot flash boot_a 'C:\Android\Oneplus 8\rooted boot tmobile.img'
target reported max download size of 805306368 bytes
sending 'boot_a' (98304 KB)...
OKAY [ 2.117s]
writing 'boot_a'...
FAILED (remote: Flashing is not allowed in Lock State)
finished. total time: 2.139s
Click to expand...
Click to collapse
I had to run an adittional command:
PS C:\WINDOWS\system32> fastboot flashing unlock
...
OKAY [ 0.035s]
finished. total time: 0.038s
Click to expand...
Click to collapse

rophiroth said:
Im in troubles. I do flash the cust-unlock, no errors but nothing really happens T,T im using android 11
Code:
PS C:\WINDOWS\system32> fastboot flash cust-unlock 'C:\Android\Oneplus 8\unlock_code.bin'
target reported max download size of 805306368 bytes
sending 'cust-unlock' (0 KB)...
OKAY [ 0.008s]
writing 'cust-unlock'...
(bootloader) Device is unlocked.
OKAY [ 0.014s]
finished. total time: 0.027s
When I try to flash anything else, it says:
Click to expand...
Click to collapse
Try running
Code:
fastboot getvar unlocked
And let me know what it says.
Also did you let the phone boot up all the way before attempting to flash the boot image?
Edit: Did you run the fastboot oem unlock command after flashing the unlock code?

rophiroth said:
Im in troubles. I do flash the cust-unlock, no errors but nothing really happens T,T im using android 11
Code:
PS C:\WINDOWS\system32> fastboot flash cust-unlock 'C:\Android\Oneplus 8\unlock_code.bin'
target reported max download size of 805306368 bytes
sending 'cust-unlock' (0 KB)...
OKAY [ 0.008s]
writing 'cust-unlock'...
(bootloader) Device is unlocked.
OKAY [ 0.014s]
finished. total time: 0.027s
When I try to flash anything else, it says:
I had to run an adittional command:
Click to expand...
Click to collapse
Yeah just looked at the guide, and it seems I forgot to include that step. Everything is fine. Your device is unlocked just not the bootloader. Before you can flash the boot image you'll need to run this:
Code:
fastboot oem unlock
Then confirm using the volume keys on your phone. Then you'll be able to flash the boot image. I've added that step to the guide. Sorry for the mistake.

TheLogicalGamer said:
Yeah just looked at the guide, and it seems I forgot to include that step. Everything is fine. Your device is unlocked just not the bootloader. Before you can flash the boot image you'll need to run this:
Code:
fastboot oem unlock
Then confirm using the volume keys on your phone. Then you'll be able to flash the boot image. I've added that step to the guide. Sorry for the mistake.
Click to expand...
Click to collapse
Yes, I unlock my phone, run magisk... and safety check mark everything wrong z,z Happen to anyonemore?

rophiroth said:
Yes, I unlock my phone, run magisk... and safety check mark everything wrong z,z Happen to anyonemore?
Click to expand...
Click to collapse
Try enabling magisk hide, and rebooting.

TheLogicalGamer said:
Try enabling magisk hide, and rebooting.
Click to expand...
Click to collapse
I'm sorry, I didn't see there wasn't enabled by default. That's works well.
Pd: some one experience heat after root? Maybe it's just te restoration of files and all..
Thank you

rophiroth said:
I'm sorry, I didn't see there wasn't enabled by default. That's works well.
Pd: some one experience heat after root? Maybe it's just te restoration of files and all..
Thank you
Click to expand...
Click to collapse
Sorry was doing some repairs on a phone. I haven't noticed any different. It could a get a bit hot during first boot from what I remember. Just keep an eye on it, see if it cools down. But rooting itself shouldn't cause that no.

If anyone needs to SIM UNLOCK & OEM UNLOCK the bootoader: goto Settings> WiFi&Network> SIM&Network> Network Unlock. If anyone can help on how to get the token unlock code, it would help some. For PUK and other unlocks https://www.t-mobile.com/support/devices/android/oneplus-8 and then scroll down to Security. There you have option to unlock several things.

How can you find out if your SIM Unlocked?

ink718 said:
If anyone needs to SIM UNLOCK & OEM UNLOCK the bootoader: goto Settings> WiFi&Network> SIM&Network> Network Unlock. If anyone can help on how to get the token unlock code, it would help some. For PUK and other unlocks https://www.t-mobile.com/support/devices/android/oneplus-8 and then scroll down to Security. There you have option to unlock several things.
Click to expand...
Click to collapse
You can only unlock the bootloader if you have the sim unlocked. Which usually happens when you paid off your device, but if you've been on the network for 40 days, and made a couple of payments you can usually get them to do it for you. Might have to annoy them a bit. As for the unlock token you have to submit an unlock request to oneplus, and they'll email it to you. However this must be done AFTER getting the sim unlocked. The sim & Bl unlocks are tied together. Can't do one without the other unless a work around is found.

Updating in the future
Spoiler: Click to show
To update to new Android versions & keep root follow these steps.
1. Make sure automatic updates in developer options are off.
2. Download and install the update, BUT DO NOT REBOOT.
3. Open magisk select install>Install to inactive slot(after ota).
4. Reboot through magisk.
5. You should reboot into the update with root preserved.
6. Pull the new patched boot image if you wish.
[/QUOTE]
How or where to download the update?
Thank you!

ink718 said:
If anyone needs to SIM UNLOCK & OEM UNLOCK the bootoader: goto Settings> WiFi&Network> SIM&Network> Network Unlock. If anyone can help on how to get the token unlock code, it would help some. For PUK and other unlocks https://www.t-mobile.com/support/devices/android/oneplus-8 and then scroll down to Security. There you have option to unlock several things.
Click to expand...
Click to collapse
Never Settle - OnePlus.com
OnePlus creates beautifully designed products with premium build quality & brings the best technology to users around the world. No tradeoffs, we #NeverSettle.
support.oneplus.com
Detailed unlock instructions

Related

The aim of this thread is to make an easy guide to flashing stock firmware. Owners of previous nexus devices already know all this stuff, this thread is aimed at making the process as simple as possible for new users. This will work regardless of what modifications you've done to your device. Remember to backup all your important data and do this with the knowledge that all flashing activity carries some risk.
Download
Factory image here
(for windows users) Minimal adb & fastboot
(for mac users) adb & fastboot for mac
Follow the instructions to install adb on your computer.
Prepare your tablet
Enable developer options in settings > about tablet and tapping build number 7 times
Open developer options and enable usb debugging. (If you haven't unlocked your bootloader yet, tick enable oem unlock)
Extract images
Place the downloaded factory image inside your adb folder and extract with 7zip.
A new folder will be there called something like volantis-lrx21. Open and extract "image-xxxxx-zip" to your adb folder. We are interested in these files:
bootloader-flounder-xxxxxx.img
boot.img
recovery.img
cache.img
system.img
vendor.img
Place these files directly into your adb folder.
# I recommend renaming the 'bootloader-flounder-xxxxxx.img' to just 'bootloader.img' to make it easier to type.
Now that everythings set up, we can start flashing
Plug in your device. Open the adb folder, hold shift and right click and select open command window here
(if your having driver issues try using Pdanet)
Run these commands one at a time
Code:
adb devices
adb reboot bootloader
if you haven't unlocked the bootloader yet run
Code:
fastboot oem unlock
and follow the instructions using the volume keys to scroll through the menu. This procedure will wipe all data.
Run the following commands one at a time
Code:
fastboot flash bootloader bootloader-flounder-xxxxxxx.img
[B] [I](replace 'bootloader-flounder-xxxxx.img' with full name of bootloader image[/I])[/B]
fastboot reboot-bootloader
fastboot -w
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash system system.img
fastboot flash vendor vendor.img
(OPTIONAL) At this stage you can relock the bootloader if you want by running the command
Code:
fastboot oem lock
finally reboot the device by running
Code:
fastboot reboot
Thats it. Enjoy your tablet in factory condition

Great. Is it possible to make a batch file to run all the commands at once?

albsat said:
Great. Is it possible to make a batch file to run all the commands at once?
Click to expand...
Click to collapse
There is already a flash all batch script that comes with the firmware files but I've noticed that some people have problems with it so I decided not to include it. It should work fine most of the time.

i am long-time familiar with htc,but new to nexus. i was looking thru a couple downloaded factory image files and having noticed that "rebootRUU" is an oem command,and that "image-xxxxx-zip" contains an android info document,i am curious if anyone has tried flashing image-xxxxx-zip as a zip file,in ruu mode?

Cool, thanks for the information.

Thanks for creating this! Will come in handy. Saving this for later

This has been useful as the update from 5.0.1 to 5.0.2 kept failing on my rooted device. It was successful and educational.

scotty1223 said:
i am long-time familiar with htc,but new to nexus. i was looking thru a couple downloaded factory image files and having noticed that "rebootRUU" is an oem command,and that "image-xxxxx-zip" contains an android info document,i am curious if anyone has tried flashing image-xxxxx-zip as a zip file,in ruu mode?
Click to expand...
Click to collapse
I indeed tried this as a last chance hoping it would bypass bootloader lock protection. It didn't work since I think the factory image is not signed by HTC as RUU are . It also lead to a fastboot crash. Now sending my nexus 9 for RMA
Sent from my HTC One using XDA Free mobile app

remedya said:
This has been useful as the update from 5.0.1 to 5.0.2 kept failing on my rooted device. It was successful and educational.
Click to expand...
Click to collapse
Same here. The manual flash method worked very well. Here's hoping that Google doesn't muck 5.1

cant flash stock rom
I'm trying to downgrade my nexus 9 from DU rom 5.1.1 to stock for everything. I'm running the flash-all.sh on linux while my tablet is in bootloader mode. Tab makes and few checks and reboots automatically in bootloader mode. I reboot tablet and still has the DU rom. Any tips

nyasha1935 said:
I'm trying to downgrade my nexus 9 from DU rom 5.1.1 to stock for everything. I'm running the flash-all.sh on linux while my tablet is in bootloader mode. Tab makes and few checks and reboots automatically in bootloader mode. I reboot tablet and still has the DU rom. Any tips
Click to expand...
Click to collapse
The flash all script doesn't seem to work on linux. You shouldn't have a problem if you write the commands out manually.

nyasha1935 said:
I'm trying to downgrade my nexus 9 from DU rom 5.1.1 to stock for everything. I'm running the flash-all.sh on linux while my tablet is in bootloader mode. Tab makes and few checks and reboots automatically in bootloader mode. I reboot tablet and still has the DU rom. Any tips
Click to expand...
Click to collapse
Art Vanderlay said:
The flash all script doesn't seem to work on linux. You shouldn't have a problem if you write the commands out manually.
Click to expand...
Click to collapse
As indicated, the flash all script doesn't work very well on any system. Flash each .img separately via fastboot.

cam30era said:
As indicated, the flash all script doesn't work very well on any system. Flash each .img separately via fastboot.
Click to expand...
Click to collapse
Problem is that the tgz is too big for the device's buffer, so it craps out before it actually writes the images. Its been this way for a while over several different nexus devices. Kind of like nobody at google ever even bothered to test the process.

doitright said:
Problem is that the tgz is too big for the device's buffer, so it craps out before it actually writes the images. Its been this way for a while over several different nexus devices. Kind of like nobody at google ever even bothered to test the process.
Click to expand...
Click to collapse
I agree.

I also used Linux but I executed the commands individually rather than using the script. It worked.

remedya said:
I also used Linux but I executed the commands individually rather than using the script. It worked.
Click to expand...
Click to collapse
I cant flash system.img I get error
sending 'system' (1108544 KB)...
FAILED (remote: data length is too large)
finished. total time: 0.105s

nyasha1935 said:
I cant flash system.img I get error
sending 'system' (1108544 KB)...
FAILED (remote: data length is too large)
finished. total time: 0.105s
Click to expand...
Click to collapse
Update your Android SDK.

These instructions also worked with 5.1.1

im trying to install back to facctory i erased my system and recovery and data and now when i try to flash bootloader i get error cannot open bootloader someone please im stuck in bootloader mode

maxtcee said:
im trying to install back to facctory i erased my system and recovery and data and now when i try to flash bootloader i get error cannot open bootloader someone please im stuck in bootloader mode
Click to expand...
Click to collapse
Are you writing the full name and file path for the bootloader img?

The instructions in this guide are outdated and way more complicated than necessary. Once the official release of Android 7.0 Nougat becomes available/rooted, I will update the procedures in this thread. In the meantime, I recommend referencing this post along with the original instructions.
A massive shout out to @cheep5k8 for all the hard work he did in getting root and recovery working on the Pixel C. Please donate to him if you can. He deserves it.
Disclaimer: This will wipe your device. Backup anything important before you start. I mostly made this guide for selfish reasons. cheep5k8 has done a great job but some of the instructions are a little vague. I like being spoon fed and I wanted a resource to refer to in the future. You know the drill. If it breaks, not my problem. Post in the forums or hop onto the XDA IRC channel.
There may be more efficient ways to do this, but this will get you where you need to be. If you find any problems or have any suggestions, feel free to reply (BE VERY SPECIFIC WITH STEPS) and I will do my best to update the instructions.
Prerequisites:
ADB/Fastboot - Minimal ADB and Fastboot
ADB/Fastboot Drivers - I recommend using Wugfresh's Nexus Root Toolkit and using the full driver installation guide. Alternatively, you can install them yourself using the official Google Drivers (no installer)
An easy way to access the ADB prompt is to navigate to the directory that ADB is installed in, hold shift and right click inside the directory. This will give you an expanded right click menu that includes an option to "Open command window here." Select this option and a command prompt will open that is already in the ADB directory, saving you from having to do a bunch of cd nonsense. You can check to see if your device is recognized in ADB by typing "adb devices." If ADB and the driver are all working correctly, it should come back with something like "5A20001071 device." You can also check to make sure your device is recognized in fastboot by booting to the bootloader and typing "fastboot devices." It will show something similar.
Necessary Files:
Pixel C Recovery - Cheap5k8's Recovery -- NYCHitman's Recovery (newer)
Pixel C Root files - Download the XCeeD kernel, su.img, and SuperUser.apk
Copy these files to your directory that contains the ADB and Fastboot executables.
Device Prep:
Enable developer mode
Go to Settings > About tablet
Tap on Build Number 7 times until it says "You are now a developer"
Enable OEM Unlocking
Go to Settings > Developer options
Enable OEM Unlocking
Tap on Enable when a disclaimer pops up
Enable USB Debugging (ADB)
Go to Settings > Developer options
Enable USB debugging
Tap on OK when prompted with a disclaimer
If the ADB USB driver has been installed, you will see a popup that says "The computer's RSA key fingerprint is: xx:xx:xx:xx(blah blah)"
Check the box next to "Always allow from this computer"
Tap on OK
Unlock Bootloader:
Open ADB prompt (see prerequisites)
Input the following:
Code:
adb reboot-bootloader
The device will now boot into the bootloader and say
Code:
Waiting for fastboot command...
Input the following to unlock the bootloader:
Code:
fastboot flashing unlock
You will be prompted on the tablet screen with a warning about unlocking the bootloader.
Press the power button to unlock the bootloader.
The device will reboot and say "Bootloader is unlocked and OS verification is OFF. Device will continue booting in 30 seconds." You will also hear an audible beep. You will then see the green android with some spinny stuff. This is the userdata being formatted.
When complete, the device will boot back into the bootloader and say
Code:
Waiting for fastboot command...
Boot back into Android by inputting:
Code:
fastboot reboot
Your Pixel C will be reset, so you will need to re-enable USB debugging. Connect to your wireless network and then skip past everything else in the initial setup, as all of this setup info will be wiped again later on. Refer to the "Enable USB Debugging (ADB)" steps above to re-enable USB debugging.
Install Custom Recovery:
Open ADB prompt (see prerequisites)
Input the following:
Code:
adb reboot-bootloader
The device will now boot into the bootloader and say
Code:
Waiting for fastboot command...
With the Pixel C in the Fastboot bootloader and the recovery file in your ADB directory, input the following:
Code:
fastboot flash recovery (replace with custom recovery filename).img
Example:
Code:
C:\>fastboot flash recovery twrp-2.8.7.0-dragon-ryu-01082016-2.img
target reported max download size of 268435456 bytes
erasing 'recovery'...
(bootloader) erasing flash
OKAY [ 0.054s]
sending 'recovery' (13760 KB)...
OKAY [ 0.349s]
writing 'recovery'...
(bootloader) writing flash
OKAY [ 0.375s]
finished. total time: 0.783s
Reboot into Recovery using the physical buttons. If you reboot the device back into Android, it will write over the custom recovery with the stock one. This will be fixed in the future.
Code:
Power + Volume down until screen turns off, keep pressing volume down to boot into Coreboot Bootloader. Navigate to Reboot into Android Recovery with volume down and then press power to select.
Install Root:
In TWRP, navigate to Wipe > Format Data
Type "yes" in the warning prompt and wait for the userdata partition to format. Again, this will wipe your tablet.
Press the Home button at the bottom when the format is complete
Navigate to Reboot > Bootloader to boot back into Fastboot
In the ADB prompt, flash the new kernel:
Code:
fastboot flash boot (replace with xCeeD kernel filename).img
Example:
Code:
C:\>fastboot flash boot xceed-kernel-google-dragon-02-01-2016-RC1.img
target reported max download size of 268435456 bytes
erasing 'boot'...
(bootloader) erasing flash
OKAY [ 0.064s]
sending 'boot' (6220 KB)...
OKAY [ 0.161s]
writing 'boot'...
(bootloader) writing flash
OKAY [ 0.197s]
finished. total time: 0.426s
Reboot into Android. The device may boot twice.
Code:
fastboot reboot
Reboot back into Recovery. Power + Volume down until screen turns off, keep pressing volume down to boot into Coreboot Bootloader. Navigate to Reboot into Android Recovery with volume down and then press power to select.
In TWRP, navigate to Mount and check only Data
In the ADB prompt move su.img to /data:
Code:
adb push su.img /data
Example:
Code:
C:\>adb push su.img /data
5677 KB/s (33554432 bytes in 5.772s)
In TWRP, navigate to Mount and uncheck Data
In TWRP, navigate to Reboot > System
Perform initial device setup
Once you are at the home launcher, re-enable USB debugging (Refer to Device Prep)
In the ADB prompt, install superuser.apk:
Code:
adb install Superuser.apk
Example:
Code:
C:\>adb install Superuser.apk
8612 KB/s (6227998 bytes in 0.706s)
pkg: /data/local/tmp/Superuser.apk
Success
Install Busybox from the Play Store: link
Congrats. You are now rooted (not in the Australian sense).

Big big thanks
Amazing, great job.

P.S. One thing to add, for those who bought SuperSU Pro, you can install that too from the Play Store instead of installing the APK, but at the moment, it will say that the su binary is outdated (because the xCeeD kernel comes with 2.66, but SuperSU is already at 2.67). There needs to be a somewhat better solution but it's a bit hard to come up with it.
xCeeD v1-RC4 will have SuperSU updated to 2.67, and I'm thinking of how to make it possible to flash the normal SuperSU ZIP in TWRP. I will probably modify TWRP in some way to make that possible.

Very good step by step, guide, I went through the same process myself yesterday, although without the benefit of your guide!
Just one additional suggestion I would make, especially for people who have already got things set up nicely on their device.
Before doing anything you can make a backup of your device data using adb.
I used the guide at - http://forum.xda-developers.com/galaxy-nexus/general/guide-phone-backup-unlock-root-t1420351
Although you cannot guarantee everything will restore perfectly (I recommend that for important apps that have the capability - backup the settings manually and remember to copy them off the device), it certainly saved me a heck of a lot of time in putting things back exactly as they were before - and it is a lot quicker than letting google backup restore things.

Does this void the warranty?
Great job,anyway
Enviado desde mi Pixel C mediante Tapatalk

Cool, but you don't mind make put the video or pictured for guides.
Keep it up!!

there no show up wipe/ fromat data when I into in reboot into android recovery look like said no command

Scarfacez2007 said:
there no show up wipe/ fromat data when I into in reboot into android recovery look like said no command
Click to expand...
Click to collapse
Are you booting into TWRP recovery or the stock Android recovery?

I have unlocked and I was install install custom recovery that all
---------- Post added at 01:11 AM ---------- Previous post was at 12:21 AM ----------
I just installed trwp then I into on reboot into android recovery but still no command

Thank you for this in depth tutorial.. GREATLY appreciated..my C will be in tomorrow just in time for RC4! Hopefully all goes smooth with this. So no need to swipe fastboot fix in twrp??

Scarfacez2007 said:
I have unlocked and I was install install custom recovery that all
---------- Post added at 01:11 AM ---------- Previous post was at 12:21 AM ----------
I just installed trwp then I into on reboot into android recovery but still no command
Click to expand...
Click to collapse
I had that too after my first attempt, I reinstalled TWRP and it worked after the second flash.
There were no errors shown either time.

The same thing - no command, though the TWRP is installed. Re-installing doesn't help at all.
UPD Just managed to do this step by manually booting into recovery without booting the ui.

I updated the instructions saying to use the physical buttons to boot into recovery immediately after writing TWRP to flash. I believe this should mitigate the issue with the device overwriting the custom recovery before the kernel is flashed.

You don't mind guide put with the video or picture?

Scarfacez2007 said:
You don't mind guide put with the video or picture?
Click to expand...
Click to collapse
I have no plans to make a video or pictures.

Finally I got rooted about time!!!! thanks oRAirwolf!!!!

I just wondering I can download Xposed 6.0.1 on my pixel c?

Scarfacez2007 said:
I just wondering I can download Xposed 6.0.1 on my pixel c?
Click to expand...
Click to collapse
I have no idea. I would probably start a new thread in the Q&A section.

Scarfacez2007 said:
I just wondering I can download Xposed 6.0.1 on my pixel c?
Click to expand...
Click to collapse
Yep xposed works fine

How did you get download xposed with arm64 for Google Pixel C? where get it? you don't mind can find for me on link?

Working On MM-WW-4.21.40.352 Z00A Z00AD And on Latest versions
MM-WW-4.21.40.327 Z00A Z00AD
MM-WW-4.21.40.223 Z00A Z00AD
Latest Stable Magisk : v16.3 Updated 28 March 2018. If there is update you will surely find it in telegram group. I don't visit xda much.
To download, Go to "Magisk" folder In download folder.
If you are using Magisk 12, Then first flash Magisk 12 uninstaller, then flash Latest Magisk from Twrp.
If Safetynet Fails, Then enable "Hide Magisk" in settings from magisk manager.​Warning:
Rooting voids warranty. Also If some damage occurs because of wrong steps taken by you, Neither me nor forum is responsible. Do at your Own risk. Though I'm sure If you follow the steps carefully you wont get problem.
Prefer to backup your device apps and data.
First read the post twice carefully then proceed.
I may change name of files in folder. Use common sense to identify them.
If you want to flash stock rom then visit here Flash Stock Rom Zenfone 2
Features:
Magisk ManagerNEW
MagiskLatest Warning: Never update magisk from the app. Flash the latest zip from here, otherwise you will get bootloop.
Systemless Xposed
TWRP Latest
UnRoot (Magisk SuperUser only)
Requirements:
1. Phone should be charged at least 60%.
2. Android USB Driver should be installed already, if it is not then install all drivers in the "Drivers Folder".
3. Enable USB Debugging.
For that go to "Settings" ,Scroll to bottom goto "about", goto "Software Information", tap "Build number" upto 7 times or till it
says "You are a developer now". Then go to "Settings" you will find "Developer Options", open it and enable "USB Debugging"
ALL .BAT FILES TO BE RUN IN FASTBOOT MODE ONLY, IF YOU DON'T KNOW ABOUT FASTBOOT MODE THEN GOOGLE "HOW TO GET FASTBOOT MODE IN ASUS ZENFONE 2.
"
There are two parts which should be followed precisely.
1. Unlock Bootloader and Install TWRP.
2. Root and Install Xposed*
*=Though Xposed is not necessary but Xposed is very helpful, so its your choice.
Part 1: Unlock Bootloader and Install TWRP.
Step 1: Connect your phone to PC, make sure usb debugging is "ON".
Step 2: Go to the folder and run "Bootloader Unlocker.bat" .
Wait for command to execute.
When you see "Unlock Successful" in your phone, your phone will shut down. Then keep hold Volume Up button on your phone until you see bootloader again. Then follow the instructions. If You Missed it, the close the application. Boot your phone into fastboot mode and try again..
Step 3: If you are in fastboot/bootloader mode then use "TWRP.bat" otherwise first go to fastboot/bootloader mode and then use "TWRP.bat"
It will install twrp. When you first go to twrp. Tick Always allow modifications.
Part 2: Root and Install Xposed
Step 1: Boot to fastboot mode.
Step 2: For rooting. First use "ROOT UNROOT MAGISK.bat", follow any given instruction in script.
Step 3: If you want Xposed, then use "XPOSED.bat" in fastboot mode and follow any instruction in script.
Step 4: Reboot to system.
Your phone may optimize for 5-10 minutes depending upon number of apps Installed.
YOUR PHONE SHOULD BE ROOTED NOW.
Unroot
Step 1: Boot to fastboot mode.
Step 2: For unrooting. First use "ROOT UNROOT MAGISK.bat", follow any given instruction in script for unroot.
For Any querry or doubt please ask.
Every Suggestion welcomed. Also you can join telegram group to get help and help others.
https://telegram.me/joinchat/ESGRD0Erde3o4dRPSzkBCQ
If the guide works for you or you want to thank me for development of tools then you can donate me via
Paypal paypal.me/KapilTapsi (You can donate any amount, It will be of great help)
FAQ
1. Stuck at white screen with asus logo?
Sol. a) White screen means you are unlocked (action of unlock.bat), so you may give a try to restore.bat in fastboot mode.
b) If you can go to recovery mode then you can go to previous state(before starting unlocking) by using adb command
First boot to recovery(it should be the stock one), you'll see dead android logo, keep pressing power -then vol up-then release vol up- now release power. (This should be quick, otherwise pressing power button for too long will shut you down)
When successfull, you'll see options, choose apply update from adb, and follow command
Code:
adb sideload mm.zip
You must rename the downloaded zip to mm.zip . Or you can replace mm.zip to xxxxxxxxxxx.zip (whatever the name of downloaded zip)
Warning Before that you must download same version full firmware from asus website Here
2. Having problems with device connection? like waiting for device.
Sol. Make sure you have enabled USB Debugging (Not applicable for BL Unlocking and TWRP Flashing)
Uninstall all drivers previously installed on computer(every driver of any device)
Reboot your computer. And then install all drivers given in the driver folder.
If the problem persists, try different computer and different usb cable.
3. Facing permission denied in fastboot mode or while running script files.
Sol. Try disabling your lock screen security to none.
4. Want to relock bootloader?
Sol. No possible way for now. The post will be updated if it ever comes.
5. Safetynet Failed?
Sol. 1. Have you enabled Magisk Hide in the settings of Magisk Manager? Try toggle to disable, and re-enable again.
2. If you are using SuperSU, you often need suhide, or maybe other solutions. Developer do not have control of how SuperSU behaves.
3. It might be due to xposed. Either you remove xposed or wait for future updates.
Download files from here
https://www.androidfilehost.com/?w=files&flid=273540 AFH Link
All Files in folder are not useful for this purpose, but are used for other purpose also. You can download them if you want.
File credits.
Giovix92
topjohnwu
Some tools are not made by me. This guide is genuine based on my experience.
Generous Donor(s):
1. Peter Fedorow (20 Canadian Dollar):good:
2. Nicola Roncari (20 Euro):good:

Hi, warranty will be void? Or still usable?

Hi, in the 5th step, installing twrp does not seem to work and my computer cannot find my device (using adb devices computer cannot find the phone)
flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (15316 KB)...
OKAY 0.686s
writing 'recovery'...
FAILED (remote: Permission denied)
finished. total time: 0.849s
---------- Post added at 11:11 PM ---------- Previous post was at 11:00 PM ----------
aguywithaname said:
Hi, in ​the 5th step, installing twrp does not seem to work and my computer cannot find my device (using adb devices computer cannot find the phone)
flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (15316 KB)...
OKAY 0.686s
writing 'recovery'...
FAILED (remote: Permission denied)
finished. total time: 0.849s
Click to expand...
Click to collapse
Ah nevermind I found the solution to the problem. From bootloader mode all I had to do was boot into recovery and then I got into twrp. Thanks anyway.

Hi it's me again. Why do I lose root after I reboot/restart my phone?

You bricked your phones 3 times, i also bricked mine can you tell me how to unbrick?? @Kapil Tapsi

biondo_92 said:
Hi, warranty will be void? Or still usable?
Click to expand...
Click to collapse
No. But if you unlock by this method you can get your warranty by flashing clean marshmallow or lollipop.

aguywithaname said:
Hi, in the 5th step, installing twrp does not seem to work and my computer cannot find my device (using adb devices computer cannot find the phone)
flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (15316 KB)...
OKAY 0.686s
writing 'recovery'...
FAILED (remote: Permission denied)
finished. total time: 0.849s
---------- Post added at 11:11 PM ---------- Previous post was at 11:00 PM ----------
Ah nevermind I found the solution to the problem. From bootloader mode all I had to do was boot into recovery and then I got into twrp. Thanks anyway.
Click to expand...
Click to collapse
Thanks. Permission denied to write means bootloader is still locked

aguywithaname said:
Hi it's me again. Why do I lose root after I reboot/restart my phone?
Click to expand...
Click to collapse
If you successfully followed these steps then root will persist. Check your steps. I've done this in 3 phones successfully.

ayush.gl said:
You bricked your phones 3 times, i also bricked mine can you tell me how to unbrick?? @Kapil Tapsi
Click to expand...
Click to collapse
Yes, But before that I need to know some things.
1. Your phone can be powered on(meaningless but still want to know.)
2. Can you reach bootloader.? I.e. fastboot mode.
3. Or you cannot see any bootloader while pressing volume + and power, but your phone is only showing asus logo.

Is there any way to access TWRP recovery after all is said and done? When ever I try to go into recovery via fastboot, it just takes me back to fastboot again.

shaza98 said:
Is there any way to access TWRP recovery after all is said and done? When ever I try to go into recovery via fastboot, it just takes me back to fastboot again.
Click to expand...
Click to collapse
Yes but you have to unlock bootloader again using unlock.bat and go to recovery menu flash whatever you want, reboot to bootloader again and run restore.bat.

Working guide as of 9/8/2016
Kapil Tapsi said:
I've been trying to root my Asus Zenfone 2 since the day Marshmallow Launched for it.
I bricked my phone 3 times. And finally I found true working process. I thought to share with you mates.​Rooting voids warranty. Also If some damage occurs because of wrong steps taken by you, Neither me nor forum is responsible. Do at your Own risk. Though Im sure If you follow the steps carefully you wont get problem.
Prefer to backup your device apps and data.
First read the post twice carefully then proceed.
There are two process which should be followed precisely.
1. Temporarily Unlock Bootloader.
2. Root and Install Xposed Installer*
*=Though Xposed is not necessary but Xposed is very helpful, so its your choice.
Download all Files given below
Step 1: Enable Usb Debugging
For that go to "Settings" ,Scroll to bottom goto "about", goto "Software Information", tap "Build number" upto 7 times or till it says
"You are a developer now". Connect phone to your computer via usb (Make sure you have Installed android drivers in your Pc, If not install pda.net from Here)
Step 2: Copy "Magisk-v6_repack_for_zf2_601.zip","phh-superuser-17-magisk-x86-fix.zip" and "xposed-v86.5-sdk23-topjohnwu_repack_for_zf2_601.zip" to your Internal Memory.
Step 3: Extract "unlock_for_zf2_551ml_6.0_20160703.zip" to your desktop. And run "Unlock.bat". It will restart your device to bootloader and install , and again reboot. Now it will struck at Asus logo with white background.
Step 4: Force Shutdown your phone by pressing power button for 10 seconds. Then start it into bootloader mode by pressing "Vol+"and "Power" buttons simultaneously. When it vibrates leave power button only(keep pressing "Vol+" until you see bootloader mode)
Step 5: Install twrp recovery from fastboot mode (google it if you dont know)
command " fastboot flash recovery twrp.img "
twrp is provided.
after successfull execution of command go to recovery mode by pressing down button on bootloader mode and allow modifications for twrp.
Step6: In TWRP, goto "Install" and browse three files which you copied to Internal Memory, And flash them In same order Which I say
"Magisk-v6_repack_for_zf2_601.zip"
"phh-superuser-17-magisk-x86-fix.zip"
"xposed-v86.5-sdk23-topjohnwu_repack_for_zf2_601.zip"
tap soft button for "Back" and tap "Reboot" And choose "Bootloader"
Step7: When in bootloader mode. Go back to your PC and double click "Restore.bat".
It will again lock your Bootloader(As it is necessary for your phone to boot) and reboot your phone. Your phone will optimize for 5-10 minutes depending upon number of apps Installed.
Step8: Install 3 Apps for accessing root and xposed given in folder.
named: Magisk manager apk
phh super user apk
xposed apk
YOUR PHONE IS ROOTED NOW.
Thanks.
For Any querry or doubt please ask.
Every Suggestion welcomed
Download files from here
https://drive.google.com/open?id=0B6SZRpR9Q7C5RzFDMUx0bFkycEE
Click to expand...
Click to collapse
I seriously thank you for this guide. I have been spending the last 12 hours looking for a working guide; though other guides were correct, it's your guide that lead me right to where I should be. I've completed the guide without problems.:good::highfive::good:

dhogthag said:
I seriously thank you for this guide. I have been spending the last 12 hours looking for a working guide; though other guides were correct, it's your guide that lead me right to where I should be. I've completed the guide without problems.:good::highfive::good:
Click to expand...
Click to collapse
Thanks. When I got my phone rooted after 3 times brick. I thought to help, so no one face problem.
Help others reach this post. And give me suggestion if any.

Kapil Tapsi said:
Thanks. Permission denied to write means bootloader is still locked
Click to expand...
Click to collapse
It can also mean you forgot to disable your lockscreen.
Sent from my ASUS_Z00AD using XDA Premium HD app

is there a way without unlocking bootloader first?

I was wondering with the TWRP provided in this root process, can we install a custom ROM with it? If so, can you provide any steps? (I want CyanogenMod)

I am totally confused, every time, the phone rebooted, it rolled back to unroot...
I had already followed any single instruction, as stated in this thread.

tm_muri said:
I am totally confused, every time, the phone rebooted, it rolled back to unroot...
I had already followed any single instruction, as stated in this thread.
Click to expand...
Click to collapse
Mine does the same.[emoji19]
Sent from my ASUS_Z00AD using XDA-Developers mobile app

any chance you guys didn't unlocked bootloader before upgrading to MM from LP

Thank you very much! I'm a rooted Zenfone owner.

Did not find any post mentioning rooting for 5C on EMUI. If there are any, let me know and I will take down this thread.
Note-
Applicable for Windows 7, Windows 8 and Windows 10
Similar steps are applicable for EMUI 4.X as well but TWRP file will change.
Saw many user on Honor 5C FB page and on XDA struggling to get root working on EMUI 5. most of the cases I saw, were for EMUI 5.X. I followed the steps mentioned or as applicable for any devices and I did not face any issue so though of compiling this guide for new users who may have faced issue or not able to root the phone. (may be mainly because of correct and working TWRP issue) . I will just simplify the steps so that any new users can do this without any problem and without any prior experience to rooting, it may be long but will be the simple enough for all the users.
Prerequisites-
Enable the developer option in settings-
Go to Settings--> About Phone-->Tab build number 7 times to enable this setting.
Go back in setting page, just above system update, you will see a new menu as -Developer Options
Scroll for the debugging section and enable the USB Debugging
You will be prompted for the confirmation with RSA key, just accept it.
Enable OEM Unlock in Developer Options (just above the USB debugging option) – Most probably this option will not be there on EMUI 5.0 (only few have seen on EMUI but it was there on EMUI 4.1 for all but rarely on EMUI 5.0 or may be because I have used dload most of the time which grayed out this)
Installation of required Drivers.
Connect your phone to PC and install Hi Suite on PC and it will additionally install all the necessary drivers to PC and HiSUite on Mobile.
Download and Install ADB from Link
Accept all the prompts and install ADB drive system wise.
Once installation is completed, if default options are chosen, it will be under C:\adb
Downloading the necessary files.
Download TWRP from Link Thanks to @OldDroid for his Original Thread . Rest of the contributor and credit in original thread by OldDroid.
Move the downloaded file under C:\adb or wherever you have installed the ADB.
Download the SuperSU file from this Link and put it in SD card or keep handy on PC so that you can copy to internal memory later.
Get the unlock as mentioned in this thread
Actual Procedure
Unlocking the bootloader-
Backup all your data as unlocking the bootloader will reset the device and all your data will be erased.
On windows machine, go to folder C:\adb or wherever you installed the adb drivers.
Press shift+right click together and select Open command prompt here
Run - adb reboot bootloader (this command may prompt for acceptance of RSA key if not already accepted)
This will boot the phone into bootloader mode.
Run - fastboot oem unlock <16 digit unlock code- Put your actual code you obtained from Huawei site > (This step will unlock the bootloader and will erase all your data)
Phone will restart automatically.
Installing TWRP
Once on the system, open the PowerShell or command prompt again in ADB folder (can use the previous instance as well)
Run - adb reboot bootloader
Once in bootloader, Run - fastboot flash recovery twrp-3.1.1-0-venus.img (This will install the TWRP recovery for EMUI 5.0 on your phone)
Once done with the flashing the TWRP, Run - fastboot reboot
Rooting
Once booted to system, open the PowerShell or command prompt in ADB folder (can use the previous instance as well)
Run - adb reboot recovery
And your phone will boot into the TWRP recovery.
Copy the SuperU file downloaded to SD card or Internal memory.
Install the SuperSU zip.
Reboot and enjoy.
Happy Flashing.

working twrp on NEM-L21 https://github.com/OpenKirin/android...0-2-hi6250.img
working supersu on NEM-L21 https://drive.google.com/file/d/0BxW...9ZRGxBTUE/view

Voutsjude said:
working twrp on NEM-L21 https://github.com/OpenKirin/android...0-2-hi6250.img
working supersu on NEM-L21 https://drive.google.com/file/d/0BxW...9ZRGxBTUE/view
Click to expand...
Click to collapse
Page not found for first and file not found for 2nd.
The links and the files mentioned in this thread will work on any honor 5C and are live files.

Nice and Thankssss
shashank1320 said:
did not find any post mentioning rooting for 5c on emui. If there are any, let me know and i will take down this thread.
note-
applicable for windows 7, windows 8 and windows 10
similar steps are applicable for emui 4.x as well but twrp file will change.
saw many user on honor 5c fb page and on xda struggling to get root working on emui 5. Most of the cases i saw, were for emui 5.x. I followed the steps mentioned or as applicable for any devices and i did not face any issue so though of compiling this guide for new users who may have faced issue or not able to root the phone. (may be mainly because of correct and working twrp issue) . I will just simplify the steps so that any new users can do this without any problem and without any prior experience to rooting, it may be long but will be the simple enough for all the users.
prerequisites-
enable the developer option in settings-
go to settings--> about phone-->tab build number 7 times to enable this setting.
go back in setting page, just above system update, you will see a new menu as -developer options
scroll for the debugging section and enable the usb debugging
you will be prompted for the confirmation with rsa key, just accept it.
enable oem unlock in developer options (just above the usb debugging option) – most probably this option will not be there on emui 5.0 (only few have seen on emui but it was there on emui 4.1 for all but rarely on emui 5.0 or may be because i have used dload most of the time which grayed out this)
installation of required drivers.
connect your phone to pc and install hi suite on pc and it will additionally install all the necessary drivers to pc and hisuite on mobile.
download and install adb from link
accept all the prompts and install adb drive system wise.
once installation is completed, if default options are chosen, it will be under c:\adb
downloading the necessary files.
download twrp from link thanks to @olddroid for his original thread . Rest of the contributor and credit in original thread by olddroid.
move the downloaded file under c:\adb or wherever you have installed the adb.
download the supersu file from this link and put it in sd card or keep handy on pc so that you can copy to internal memory later.
get the unlock as mentioned in this thread
actual procedure
unlocking the bootloader-
backup all your data as unlocking the bootloader will reset the device and all your data will be erased.
on windows machine, go to folder c:\adb or wherever you installed the adb drivers.
press shift+right click together and select open command prompt here
run - adb reboot bootloader (this command may prompt for acceptance of rsa key if not already accepted)
this will boot the phone into bootloader mode.
run - fastboot oem unlock <16 digit unlock code- put your actual code you obtained from huawei site > (this step will unlock the bootloader and will erase all your data)
phone will restart automatically.
installing twrp
once on the system, open the powershell or command prompt again in adb folder (can use the previous instance as well)
run - adb reboot bootloader
once in bootloader, run - fastboot flash recovery twrp-3.1.1-0-venus.img (this will install the twrp recovery for emui 5.0 on your phone)
once done with the flashing the twrp, run - fastboot reboot
rooting
once booted to system, open the powershell or command prompt in adb folder (can use the previous instance as well)
run - adb reboot recovery
and your phone will boot into the twrp recovery.
copy the superu file downloaded to sd card or internal memory.
install the supersu zip.
reboot and enjoy.
Happy flashing.
Click to expand...
Click to collapse
works perfect at me , thank you so much
here is my phone model and android version

Thank you so much... Love ya for this! I wish u all the success for future works..
shashank1320 said:
Did not find any post mentioning rooting for 5C on EMUI. If there are any, let me know and I will take down this thread.
Note-
Applicable for Windows 7, Windows 8 and Windows 10
Similar steps are applicable for EMUI 4.X as well but TWRP file will change.
Saw many user on Honor 5C FB page and on XDA struggling to get root working on EMUI 5. most of the cases I saw, were for EMUI 5.X. I followed the steps mentioned or as applicable for any devices and I did not face any issue so though of compiling this guide for new users who may have faced issue or not able to root the phone. (may be mainly because of correct and working TWRP issue) . I will just simplify the steps so that any new users can do this without any problem and without any prior experience to rooting, it may be long but will be the simple enough for all the users.
Prerequisites-
Enable the developer option in settings-
Go to Settings--> About Phone-->Tab build number 7 times to enable this setting.
Go back in setting page, just above system update, you will see a new menu as -Developer Options
Scroll for the debugging section and enable the USB Debugging
You will be prompted for the confirmation with RSA key, just accept it.
Enable OEM Unlock in Developer Options (just above the USB debugging option) – Most probably this option will not be there on EMUI 5.0 (only few have seen on EMUI but it was there on EMUI 4.1 for all but rarely on EMUI 5.0 or may be because I have used dload most of the time which grayed out this)
Installation of required Drivers.
Connect your phone to PC and install Hi Suite on PC and it will additionally install all the necessary drivers to PC and HiSUite on Mobile.
Download and Install ADB from Link
Accept all the prompts and install ADB drive system wise.
Once installation is completed, if default options are chosen, it will be under C:\adb
Downloading the necessary files.
Download TWRP from Link Thanks to @OldDroid for his Original Thread . Rest of the contributor and credit in original thread by OldDroid.
Move the downloaded file under C:\adb or wherever you have installed the ADB.
Download the SuperSU file from this Link and put it in SD card or keep handy on PC so that you can copy to internal memory later.
Get the unlock as mentioned in this thread
Actual Procedure
Unlocking the bootloader-
Backup all your data as unlocking the bootloader will reset the device and all your data will be erased.
On windows machine, go to folder C:\adb or wherever you installed the adb drivers.
Press shift+right click together and select Open command prompt here
Run - adb reboot bootloader (this command may prompt for acceptance of RSA key if not already accepted)
This will boot the phone into bootloader mode.
Run - fastboot oem unlock <16 digit unlock code- Put your actual code you obtained from Huawei site > (This step will unlock the bootloader and will erase all your data)
Phone will restart automatically.
Installing TWRP
Once on the system, open the PowerShell or command prompt again in ADB folder (can use the previous instance as well)
Run - adb reboot bootloader
Once in bootloader, Run - fastboot flash recovery twrp-3.1.1-0-venus.img (This will install the TWRP recovery for EMUI 5.0 on your phone)
Once done with the flashing the TWRP, Run - fastboot reboot
Rooting
Once booted to system, open the PowerShell or command prompt in ADB folder (can use the previous instance as well)
Run - adb reboot recovery
And your phone will boot into the TWRP recovery.
Copy the SuperU file downloaded to SD card or Internal memory.
Install the SuperSU zip.
Reboot and enjoy.
Happy Flashing.
Click to expand...
Click to collapse
Thank you so much... Love ya for this! I wish u all the success for future works..

tahahaiyat said:
Thank you so much... Love ya for this! I wish u all the success for future works..
Click to expand...
Click to collapse
Thanks for lovely wishes

Hi all.
I need help with installation ADB. Download file, start installation, accept all the prompts but 0 files copied and dont have file under C:\adb.
What is wrong? How install ADB?
Thanks

outcastWBC said:
Hi all.
I need help with installation ADB. Download file, start installation, accept all the prompts but 0 files copied and dont have file under C:\adb.
What is wrong? How install ADB?
Thanks
Click to expand...
Click to collapse
Method is same as given in instructions. It shoukd install without issue buddy

Hello,
I had the NEM-L51 from my mother running EMUI 4.0x, and decided to upgrade it to the latest version.
It was unlocked, with TWRP as recovery, and rooted.
I did flash back the stock recovery (from HuaweiUpdateExtractor/Update.app), rebooted the device, and applied the OTA (B350 first, then latest B357).
Until then everything is fine, but when I try to flash the TWRP recovery, it doesn't work :
D:\Android\platform-tools>fastboot flash recovery D:\Downloads\twrp-3.1.1-0-venus.img
target reported max download size of 471859200 bytes
sending 'recovery' (24464 KB)...
OKAY [ 0.719s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.734s
D:\Android\platform-tools>fastboot flash recovery D:\Downloads\twrp-3.2.1-0-nemo.img
target reported max download size of 471859200 bytes
sending 'recovery' (21972 KB)...
OKAY [ 0.672s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.672s
D:\Android\platform-tools>fastboot flash recovery D:\Downloads\twrp-3.1.1-0-nemo.img
target reported max download size of 471859200 bytes
sending 'recovery' (21918 KB)...
OKAY [ 0.641s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.656s
Click to expand...
Click to collapse
Neither the recommended Venus one, or the current / previous nemo one can be flashed.
Phone and FRP status in fastboot mode both shows Unlocked / Unlock, and the OEM Unlock option in EMUI Developper Settings is also enabled (I toggled it just to be sure).
I'm not sure what's wrong.
Would the update mess with the OEM unlock (by relocking and showing a wrong status) ?
I'd rather not try fastboot OEM unlock with the code (still have it somewhere) and lose data.
Thanks for any advice

Fr33L4nc3r said:
Hello,
I had the NEM-L51 from my mother running EMUI 4.0x, and decided to upgrade it to the latest version.
It was unlocked, with TWRP as recovery, and rooted.
I did flash back the stock recovery (from HuaweiUpdateExtractor/Update.app), rebooted the device, and applied the OTA (B350 first, then latest B357).
Until then everything is fine, but when I try to flash the TWRP recovery, it doesn't work :
Neither the recommended Venus one, or the current / previous nemo one can be flashed.
Phone and FRP status in fastboot mode both shows Unlocked / Unlock, and the OEM Unlock option in EMUI Developper Settings is also enabled (I toggled it just to be sure).
I'm not sure what's wrong.
Would the update mess with the OEM unlock (by relocking and showing a wrong status) ?
I'd rather not try fastboot OEM unlock with the code (still have it somewhere) and lose data.
Thanks for any advice
Click to expand...
Click to collapse
This should work fine but if not, can try Hassan's recovery

shashank1320 said:
This should work fine but if not, can try Hassan's recovery
Click to expand...
Click to collapse
Before trying that recovery, I just tried to flash the stock one from NEM-L51C432B357 full OTA package, and it doesn't work either
D:\Android\platform-tools>fastboot flash recovery D:\Android\HuaweiUpdateExtractor_0.9.9.5\RECOVERY.img
target reported max download size of 471859200 bytes
sending 'recovery' (35570 KB)...
OKAY [ 0.932s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.954s
Click to expand...
Click to collapse
So it's not a recovery issue.
How useful is the HiSuite backup ?
If I make a backup with it, will it be able to restore most user app's and system's data ?
I'd rather not re set everything up, and I'm afraid I'll have to retry to OEM unlock the device (so force wipe), even if it says it's unlocked (which it should have remained in the first place)

Fr33L4nc3r said:
Before trying that recovery, I just tried to flash the stock one from NEM-L51C432B357 full OTA package, and it doesn't work either
So it's not a recovery issue.
How useful is the HiSuite backup ?
If I make a backup with it, will it be able to restore most user app's and system's data ?
I'd rather not re set everything up, and I'm afraid I'll have to retry to OEM unlock the device (so force wipe), even if it says it's unlocked (which it should have remained in the first place)
Click to expand...
Click to collapse
Hisuite can be used for back.. reliable one but not same as titanium backup. Backup WhatsApp on local and g drive. Zip the WhatsApp folder in internal memory and then copy to pc.
Rest other apps, via hisuite (can backup WhatsApp as well here).

Fr33L4nc3r said:
Before trying that recovery, I just tried to flash the stock one from NEM-L51C432B357 full OTA package, and it doesn't work either
So it's not a recovery issue.
How useful is the HiSuite backup ?
If I make a backup with it, will it be able to restore most user app's and system's data ?
I'd rather not re set everything up, and I'm afraid I'll have to retry to OEM unlock the device (so force wipe), even if it says it's unlocked (which it should have remained in the first place)
Click to expand...
Click to collapse
You file should be in path D:\Android\platform-tools\ and not D:\Android\HuaweiUpdateExtractor_0.9.9.5\
I hope adb is installed under D:\Android\platform-tools\, if not, it will be udner C drive as C:\adb\
copy the recovery file whereever the adb is installed and then run the command
fastboot flash recovery twrp-3.1.1-0-venus.img (replace name with your actual file name)

Ok, so in fact fastboot OEM unlock status was not accurate, and something I didn't notice was the absence of dm-verity warning when booting (showing when it's actually unlocked)

Fr33L4nc3r said:
Ok, so in fact fastboot OEM unlock status was not accurate, and something I didn't notice was the absence of dm-verity warning when booting (showing when it's actually unlocked)
Click to expand...
Click to collapse
May be. try moving the files and then flashing from that folder and see if it works.

stopin phone
hello.please help me.last night i unlocked my gt3 and reseted factory data.but after these my phone stopped in page that typed "your device is booting now..." . but nothing going change.
when i hold power key or power key with volume up down , my phone get restart and show huawei mark and after that show the pervious page that i stoped in it and nothing change again.what can i do? :crying::crying::crying::crying:

please help me, my device is Huawei GT3 (honor 5c) (NMO L31) it was unlock bootloader before i bought it and now i want to install twrp, so i have to learn a lot of website and Follow me, I downloaded and installed Adb, installed the driver, then downloaded the twrp version with nemo honor for honor 5c, then open CMD or powershell to write commands like adb reboot bootloader then adb fastboot flash recovery twrp.img is under the writing that says Failed (remote: image verification error), I previously copied the twrp 3.0 file ... into the adb folder and renamed to twrp. Now I have to do to install twrp on my device. Please help me.

Hello, I have an NMO_L31 (honor 5c - huawei gr5 mini) device and I have experienced a Failed (remote: image verification error) error when installing TWRP while my phone was unlocked before. have searched from a lot of technology pages to find remedies but all failed. But my God, Jehovah listened to my plea and brought me to @shashank123, I contacted him through XDA and I got him a phone number to make friends on the telegram, he helped me out I and I have overcome the above error. I would like to explain how to overcome the error that I tried. First, I went back to emui 4.1.2 (you can see the instructions then allow OEM unlock, then I update the OTA to emui 5, allow usb debugging when the update is complete. Shift + Right click on CMD (or powershell) and enter "adb devices" to see the connected device, then enter "adb reboot bootloader" then enter "fastboot oem get-bootinfo" To check if the bootloader has been unlocked, then enter the command "fastboot oem unlock (code)" to unlock if the relock bootloader, then if the bootloader has been unlocked then the purpose of the command to factory reset. If that is the case, then go to the phone and see if factory reset is complete. Then develop and reconnect to adb, check the device connected to the "adb devices" command then go to the "adb reboot bootloader" command to get to the fastboot and then use the command "fastboot flash recovery recovery_name.img" (for example : Twrp) "Finally, if the word OKEY appears, you are successful. If you can not solve this problem, please send a message to @shashank123 in XDA and ask for his phone number to make friend through telegram and regular help message because he does not often use XDA. Thank you very much Shashank for helping me. Thanks be to my god JESU CHRIST and JEHOVAH.

tanhoang1702 said:
Hello, I have an NMO_L31 (honor 5c - huawei gr5 mini) device and I have experienced a Failed (remote: image verification error) error when installing TWRP while my phone was unlocked before. have searched from a lot of technology pages to find remedies but all failed. But my God, Jehovah listened to my plea and brought me to Shashank123, I contacted him through XDA and I got him a phone number to make friends on the telegram, he helped me out I and I have overcome the above error. I would like to explain how to overcome the error that I tried. First, I went back to emui 4.1.2 (you can see the instructions then allow OEM unlock, then I update the OTA to emui 5, allow usb debugging when the update is complete. Shift + Right click on CMD (or powershell) and enter "adb devices" to see the connected device, then enter "adb reboot bootloader" then enter "fastboot oem get-bootinfo" To check if the bootloader has been unlocked, then enter the command "fastboot oem unlock (code)" to unlock if the relock bootloader, then if the bootloader has been unlocked then the purpose of the command to factory reset. If that is the case, then go to the phone and see if factory reset is complete. Then develop and reconnect to adb, check the device connected to the "adb devices" command then go to the "adb reboot bootloader" command to get to the fastboot and then use the command "fastboot flash recovery recovery_name.img" (for example : Twrp) "Finally, if the word OKEY appears, you are successful. If you can not solve this problem, please send a message to Shashank123 in XDA and ask for his phone number to make friend through telegram and regular help message because he does not often use XDA. Thank you very much Shashank for helping me. Thanks be to my god JESU CHRIST and JEHOVAH.
Click to expand...
Click to collapse
No problem at all mate. Helping through telegram was quick in real time rather multiple post or message and then waiting for response from each other. Due to time crunch, I opted to quick help rather keep you waiting all day long
Good you got your phone as per your requirement and able to do what you wanted. Thanks and Enjoy.
You can edit your comment to say "@shashank1320" (use without double quotes) rather Shashank123 as users may send message or qoute him and get no response as that user may or may not exist :silly:

grand.mohammad said:
hello.please help me.last night i unlocked my gt3 and reseted factory data.but after these my phone stopped in page that typed "your device is booting now..." . but nothing going change.
when i hold power key or power key with volume up down , my phone get restart and show huawei mark and after that show the pervious page that i stoped in it and nothing change again.what can i do? :crying::crying::crying::crying:
Click to expand...
Click to collapse
Boot to bootloader again and see the bootloader state if locked or unlocked. Try unlocking it again.

Note: I am no expert at this. I used this to get TWRP and root, but it there is no guarentee it won't brick your phone. Only do this if you know what your doing. Before you start you must have an unlocked bootloader, which will delete all your data. Here's the instructions (If you need help, feel free to post a comment):
Download Magisk's installer zip on your phone from https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 (Google Pay only works with Magisk v19.0+)
Download arter97's kernel .img to your PC. This kernel currently is the only reliable way to get TWRP. https://forum.xda-developers.com/razer-phone-2/development/arter97-kernel-razer-phone-2-t3914996
Reboot your phone into bootloader mode (Turn off then back on while holding vol down).
Make sure your phone is recognized by Windows before proceeding. Follow this guide to setup the proper drivers and fastboot.
Flash arter97's kernel by running
Code:
fastboot flash boot arter97-kernel-*.img
If you run into any issues, then you will probably need to specify the slot to flash. Reboot back into your system.
Turn on Android Debugging and run
Code:
adb shell getprop ro.boot.slot_suffix
and make note if the output is _a or _b
Reboot back into bootloader
If _a use
Code:
fastboot flash boot_a arter97-kernel-*.img
if _b use
Code:
fastboot flash boot_b arter97-kernel-*.img
Reboot to recovery (either through bootloader mode or hold vol up while rebooting).
Install the Magisk .zip from TWRP.
Be amazed by the possibilities.
Old instructions (Should always work to get root):
Download the factory image from here: https://developer.razer.com/razer-phone-dev-tools/
Extract and copy the boot.img file to your device
Download and install Magisk Manager. If you have an SD card make sure it's installed on your internal storage, not the SD card.
Tap install, select Patch Boot Image File, and select the boot.img (If using the default file manager click the overflow menu and show internal storage)
Copy the patched_boot.img back over to your PC
Flash the patched_boot.img to your device via fastboot (Turn off then back on while holding vol down) and run
Code:
fastboot flash boot patched_boot.img
.
If you run into any issues, then you will need to specify the slot to flash.
Turn on Android Debugging and run
Code:
adb shell getprop ro.boot.slot_suffix
and make note if the output is _a or _b
Reboot back into bootloader
If _a use
Code:
fastboot flash boot_a patched_boot.img
if _b use
Code:
fastboot flash boot_b patched_boot.img
Reboot, and open up magisk manager to confirm everything is working. After an OTA update you may have to re-apply due to it using a different slot.
Note: the phone wasn't properly recognized by my computer when in bootloader mode so I had to install the Google adb drivers and manually set the driver used to Google Bootloader Interface (or something like that)

I found you needed to specify boot_a or boot_b specifically as the bootloader tended to mess up the suffix(it tried "bootb_b"????). So I had to first run "fastboot getvar all" to check the current slot.
I also found the commands are executed much more reliably if you enter the command first and press enter so fastboot goes into the "waiting for device" state and then boot into the bootloader and afterwards plug in the cable so fastboot executes the command as soon as it connects.

figured itd be as easy as that. this will be my first up to date device in years, att sending it to me in the mail. should get it by the 6th . but glad to see theres root! hopefully lineage to follow <3

Twiggy000b said:
figured itd be as easy as that. this will be my first up to date device in years, att sending it to me in the mail. should get it by the 6th . but glad to see theres root! hopefully lineage to follow <3
Click to expand...
Click to collapse
I know the feeling, my last device was the Nexus 5

my last "decent" device was the essential phone. then i went to the xperia xa2 ultra, then the iphone 6 then.... zte quest. -.-

CurtisMJ said:
I found you needed to specify boot_a or boot_b specifically as the bootloader tended to mess up the suffix(it tried "bootb_b"????). So I had to first run "fastboot getvar all" to check the current slot.
I also found the commands are executed much more reliably if you enter the command first and press enter so fastboot goes into the "waiting for device" state and then boot into the bootloader and afterwards plug in the cable so fastboot executes the command as soon as it connects.
Click to expand...
Click to collapse
Lol, bootb_b:laugh:. For me at least it worked fine without specifying the slot, though I may change the instructions to specify the slot

CalebQ42 said:
With the release of the factory images we can achieve root via Magisk boot image patching. Note: I am no expert at this. I used this to achieve root, but it there is no guarentee it won't brick your phone. Only do this if you know what your doing. Before you start you must have an unlocked bootloader. Here's the instructions (If you need help, feel free to post a comment):
Download the factory image from here: https://developer.razer.com/razer-phone-dev-tools/
Extract and copy the boot.img file to your device
Download and install Magisk Manager. If you have an SD card make sure it's installed on your internal storage, not the SD card.
Tap install, select Patch Boot Image File, and select the boot.img (If using the default file manager click the overflow menu and show internal storage)
Copy the patched_boot.img back over to your PC
Flash the patched_boot.img to your device via fastboot (Turn off then back on while holding vol down and run `fastboot flash boot patched_boot.img`.
Reboot, and open up magisk manager to confirm everything is working.
Note: the phone wasn't properly recognized by my computer so I had to install the Google adb drivers and manually set the driver to Google Bootloader interface (or something like that)
I also tried to install some Android Pie GSIs, but none of them worked.
Click to expand...
Click to collapse
Does this destroy all data? Do I need to unlock bootloader? Does it matter where I place the boot.img on my device?

CalebQ42 said:
Lol, bootb_b:laugh:. For me at least it worked fine without specifying the slot, though I may change the instructions to specify the slot
Click to expand...
Click to collapse
Interesting. The bootloader isn't exactly what I'd call a masterpiece of coding (weird cause I still maintain the ROM is excellent) so it might have just been a momentary glitch.
---------- Post added at 10:54 PM ---------- Previous post was at 10:53 PM ----------
ctakah27 said:
Does this destroy all data? Do I need to unlock bootloader? Does it matter where I place the boot.img on my device?
Click to expand...
Click to collapse
Yes, yes and not really (you get a file chooser so you just need to locate it)

I updated the post a bit with instructions on how to flash to a specific slot.
Tonight I'm going to try compiling TWRP for the first time ever (unless someone beats me to in). Wish me luck!

CalebQ42 said:
I updated the post a bit with instructions on how to flash to a specific slot.
Tonight I'm going to try compiling TWRP for the first time ever (unless someone beats me to in). Wish me luck!
Click to expand...
Click to collapse
Good luck it's a easier process compare to years ago. I would do it but I have no need for root or custom recovery. If you fail on the TWRP I will do it in time for people.

Is this working on the AT&T version of this phone? Or would you need to flash the global firmware in order for this to work? Looking to upgrade to this phone and I want to be sure I can get root. The rest looks to be coming fairly quickly.

CalebQ42 said:
I updated the post a bit with instructions on how to flash to a specific slot.
Tonight I'm going to try compiling TWRP for the first time ever (unless someone beats me to in). Wish me luck!
Click to expand...
Click to collapse
jonchance_84 said:
Is this working on the AT&T version of this phone? Or would you need to flash the global firmware in order for this to work? Looking to upgrade to this phone and I want to be sure I can get root. The rest looks to be coming fairly quickly.
Click to expand...
Click to collapse
They have the image for AT&T
EAIaIQobChMIwYzbk7j_3gIVRZRpCh0RMwdoEAEYASAAEgLPifD_BwE

Warrior1988 said:
They have the image for AT&T
EAIaIQobChMIwYzbk7j_3gIVRZRpCh0RMwdoEAEYASAAEgLPifD_BwE
Click to expand...
Click to collapse
I see the separate firmware. I'm only asking because of past shadyness from AT&T trying to tell manufacturers what to do. Years ago on my Xperia x10, if on AT&T firmware, you needed to flash the global generic firmware to get around their crap.

CalebQ42 said:
With the release of the factory images we can achieve root via Magisk boot image patching. Note: I am no expert at this. I used this to achieve root, but it there is no guarentee it won't brick your phone. Only do this if you know what your doing. Before you start you must have an unlocked bootloader, which will delete all your data. Here's the instructions (If you need help, feel free to post a comment):
Download the factory image from here: https://developer.razer.com/razer-phone-dev-tools/
Extract and copy the boot.img file to your device
Download and install Magisk Manager. If you have an SD card make sure it's installed on your internal storage, not the SD card.
Tap install, select Patch Boot Image File, and select the boot.img (If using the default file manager click the overflow menu and show internal storage)
Copy the patched_boot.img back over to your PC
Flash the patched_boot.img to your device via fastboot (Turn off then back on while holding vol down) and run
Code:
fastboot flash boot patched_boot.img
.
If you run into any issues, then you will need to specify the slot to flash.
Turn on Android Debugging and run
Code:
adb shell getprop ro.boot.slot_suffix
and make note if the output is _a or _b
Reboot back into bootloader
If _a use
Code:
fastboot flash boot_a patched_boot.img
if _b use
Code:
fastboot flash boot_b patched_boot.img
Reboot, and open up magisk manager to confirm everything is working. After an OTA update you may have to re-apply due to it using a different slot.
Note: the phone wasn't properly recognized by my computer so I had to install the Google adb drivers and manually set the driver to Google Bootloader interface (or something like that)
I also tried to install some Android Pie GSIs, but none of them worked.
Click to expand...
Click to collapse
Would this procedure be the same as far as mac/win?

I understand all of that, I am simply asking if someone has tried this with the AT&T variant yet. I want to know before I go order this phone.

I love a rooted phone, but as far as I know, if you unlock the bootloader, Netflix will no longer work in HD mode. To me, this is a deal-breaker. If anyone knows about a work-around, I'd love to know.

Razer phone 2 root
so im kinda new to rooting this type of phone and to the android boot scheme in general. i have a razer phone 2 and have attempted (febaly) to root it using this meathod. after installing the google adb drivers i was unable to see the device from my pc when it was in fastboot and unable to send commands, after installing the drivers again with windows update it ran even though no device was detected with this message
">fastboot flash boot patched_boot.img
Sending 'boot_b' (19268 KB) OKAY [ 0.523s]
Writing 'boot_b' OKAY [ 0.179s]
Finished. Total time: 0.718s"
it then blackscreened, i then tried a factory reset from recovery, and it is now in a bootloop... any advice?
update: no longer in boot loop but now is full blackscreen after a glitchy install screen

andy1011 said:
so im kinda new to rooting this type of phone and to the android boot scheme in general. i have a razer phone 2 and have attempted (febaly) to root it using this meathod. after installing the google adb drivers i was unable to see the device from my pc when it was in fastboot and unable to send commands, after installing the drivers again with windows update it ran even though no device was detected with this message
">fastboot flash boot patched_boot.img
Sending 'boot_b' (19268 KB) OKAY [ 0.523s]
Writing 'boot_b' OKAY [ 0.179s]
Finished. Total time: 0.718s"
it then blackscreened, i then tried a factory reset from recovery, and it is now in a bootloop... any advice?
update: no longer in boot loop but now is full blackscreen after a glitchy install screen
Click to expand...
Click to collapse
Since it's already wiped the easiest way to fix it is to probably flash the full factory image. Did you happen to update to the MR2 update prior to following this guide? Doing this on MR2 will soft brick. Not entirely sure in what way, but I assume it would be similar to what you experienced. If you were still on MR0 you can actually just fastboot flash the original kernel image to fix it. I just finished rooting MR2 so I'll post that next

CurtisMJ said:
Since it's already wiped the easiest way to fix it is to probably flash the full factory image. Did you happen to update to the MR2 update prior to following this guide? Doing this on MR2 will soft brick. Not entirely sure in what way, but I assume it would be similar to what you experienced. If you were still on MR0 you can actually just fastboot flash the original kernel image to fix it. I just finished rooting MR2 so I'll post that next
Click to expand...
Click to collapse
this is what im trying to do. however i have no way of flashing to the device as adb is unable to see the device.

andy1011 said:
this is what im trying to do. however i have no way of flashing to the device as adb is unable to see the device.
Click to expand...
Click to collapse
Adb and fastboot are separate things. You should only need download mode and fastboot. What are you trying to use ADB for? If in doubt, the guide on Razer's website should be quite sufficient
EDIT: You can get to download mode by holding Vol Down and Power Button while the device is off. You can force reboot by holding down power for approx 15s as well