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?
Related
Just delete this if it's considered in the wrong place. If and when is the the Stylo 2 Plus getting its own forum and has anyone come up with an exploit for rooting this phone yet?
Hiya
Yes this is the wrong place. This is for the g stylo not the stylo 2 plus as can be seen in the name of the forum.
No there is not an exploit yet. Kingroot, kangoroot, one clove root, etc all do not work yet. Soon i would imagine
I even have trouble looking on the web for things because it seems we share a model number ms550 with the lg optimus m. Weird
You think my signature would say I probably know this. Granted, I haven't worked for them in a while, for XDA, even longer. I was talking to the mods of the forum, sorry, if I confused you.
Reserved
Root recovery and boot loader unlock have been achieved on the Gsm Variants . you can find the link if you look for it .
---------- Post added at 04:31 PM ---------- Previous post was at 04:14 PM ----------
mustangtim49 said:
You think my signature would say I probably know this. Granted, I haven't worked for them in a while, for XDA, even longer. I was talking to the mods of the forum, sorry, if I confused you.
Click to expand...
Click to collapse
http://forum.xda-developers.com/android/development/recovery-twrp-v3-lg-stylo-2-plus-t3482169/page6
Remote: unknown command
Rmontoya83 said:
Root recovery and boot loader unlock have been achieved on the Gsm Variants . you can find the link if you look for it .
---------- Post added at 04:31 PM ---------- Previous post was at 04:14 PM ----------
http://forum.xda-developers.com/android/development/recovery-twrp-v3-lg-stylo-2-plus-t3482169/page6
Click to expand...
Click to collapse
I am new here and I have also googled and searched extensively about this problem with no success.
C:\Users\Darin\Downloads\twrp>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.566s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.575s
I can't boot TWRP by command line or by recovery key sequence. I have flashed recovery with this TWRP image that I got directly from @messi2050 today, 1/18/2017. If I "adb reboot recovery", I get the Android crash screen - the android laying down, red triangle. My phone is a t-mobile stylo 2 plus K-550. I'm sure I followed every step in the process correctly. If there is another thread that addresses this problem, can you direct me to it please? I can't start my own thread because I'm too new, but the most relevant recent thread regarding this is locked. Yes I have rooted another phone before without a problem(Samsung). Thanks in advance for your help.
[email protected] said:
I am new here and I have also googled and searched extensively about this problem with no success.
C:\Users\Darin\Downloads\twrp>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.566s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.575s
I can't boot TWRP by command line or by recovery key sequence. I have flashed recovery with this TWRP image that I got directly from @messi2050 today, 1/18/2017. If I "adb reboot recovery", I get the Android crash screen - the android laying down, red triangle. My phone is a t-mobile stylo 2 plus K-550. I'm sure I followed every step in the process correctly. If there is another thread that addresses this problem, can you direct me to it please? I can't start my own thread because I'm too new, but the most relevant recent thread regarding this is locked. Yes I have rooted another phone before without a problem(Samsung). Thanks in advance for your help.
Click to expand...
Click to collapse
Install the android sdk tools with adb fastboot and drivers.
Click build number 5 times to unlock developer options
Enable usb debugging
Enable allow oem unlock
Navigate to the platform tools directory paste the recovery.img in that folder.
Hold shift key right click mouse in the said folder to open command window
Plug in the phone type adb devices
Should say lgsomthing
If it does adb reboot bootloader
Fastboot devices
Should say lg something
If it does fastboot oem unlock
Reboot the phone
Enable developer options again in the settings menu by clicking build number
Go back to command window put it back in boot loader screen type fastboot flash recovery recovery.img
Unplug phone Pull battery out once done hold vol down and power until you we the lg screen release power while holding vol down then re hold power again release both buttons
Select yes and yes to wipe phone.
Flash dm verify and super user zips
Click reboot recovery
Don't forget to format data type yes and prevail
Now click thanks!!! If I helped.
I followed all of these steps. Fastboot flash recovery recovery.img from the directory where the tools are. When I get to the part of pressing volume down, power, then releasing power, and pressing again, and releasing both this is what happens:
Factory data reset screen
Erase all user data & restore default settings?
No
Yes
I've already been through that and TWRP doesn't load if I pick Yes, it just wipes my phone data, fresh Android, start over.
Please help
Rmontoya83 said:
Install the android sdk tools with adb fastboot and drivers.
Click build number 5 times to unlock developer options
Enable usb debugging
Enable allow oem unlock
Navigate to the platform tools directory paste the recovery.img in that folder.
Hold shift key right click mouse in the said folder to open command window
Plug in the phone type adb devices
Should say lgsomthing
If it does adb reboot bootloader
Fastboot devices
Should say lg something
If it does fastboot oem unlock
Reboot the phone
Enable developer options again in the settings menu by clicking build number
Go back to command window put it back in boot loader screen type fastboot flash recovery recovery.img
Unplug phone Pull battery out once done hold vol down and power until you we the lg screen release power while holding vol down then re hold power again release both buttons
Select yes and yes to wipe phone.
Flash dm verify and super user zips
Click reboot recovery
Don't forget to format data type yes and prevail
Now click thanks!!! If I helped.
Click to expand...
Click to collapse
[email protected] said:
I followed all of these steps. Fastboot flash recovery recovery.img from the directory where the tools are. When I get to the part of pressing volume down, power, then releasing power, and pressing again, and releasing both this is what happens:
Factory data reset screen
Erase all user data & restore default settings?
No
Yes
I've already been through that and TWRP doesn't load if I pick Yes, it just wipes my phone data, fresh Android, start over.
Please help
Click to expand...
Click to collapse
Then Twrp didn't flash
Flashing
Rmontoya83 said:
Then Twrp didn't flash
Click to expand...
Click to collapse
Fastboot said it flashed successfully. It copies the file, says it's ok. I would think if it didn't flash, it would fail the fastboot flash command. So is my phone jacked? I've read about how Android can rewrite the recovery partition as a security measure, or disable flashing by other means. Some kind of added security possibly?
Why would it say OK when I flash recovery, but NOT actually flash it?
[email protected] said:
Fastboot said it flashed successfully. It copies the file, says it's ok. I would think if it didn't flash, it would fail the fastboot flash command. So is my phone jacked? I've read about how Android can rewrite the recovery partition as a security measure, or disable flashing by other means. Some kind of added security possibly?
Why would it say OK when I flash recovery, but NOT actually flash it?
Click to expand...
Click to collapse
What software version are you running?
[email protected] said:
I am new here and I have also googled and searched extensively about this problem with no success.
C:\Users\Darin\Downloads\twrp>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.566s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.575s
Wrong command your trying to boot twrp
The correct command is "fastboot flash recovery recovery.img"
Click to expand...
Click to collapse
It was something I found in another tutorial when I started trying other things, since the "fastboot flash recovery recovery.img" was not getting me past the standard Android recovery. I'm about to try the file you sent me last night. I'll let you know the result.
---------- Post added at 10:25 PM ---------- Previous post was at 10:13 PM ----------
Rmontoya83 said:
What software version are you running?
Click to expand...
Click to collapse
Android version 6.0.1
Android security patch level 2016-08-01
Kernel version 3.18.20
Windows 7 Pro x64
The recovery.img you sent also said it flashed, but I got to the same Android factory reset screen after the key press procedure (volume down, power, release power, repress power, release all)
Here's the latest:
C:\Users\Darin\Downloads\platform-tools-latest-windows\platform-tools>fastboot f
lash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (15518 KB)...
OKAY [ 0.495s]
writing 'recovery'...
OKAY [ 0.362s]
finished. total time: 0.865s
Once you boot into recovery, let the screen fully dim, do not touch it... once the screen is completely blacked out, turn it back on and all touch features will be up and running... and don't mess with the adoptable storage feature..migrating data.. because TWRP will not recognise any data if you have this enabled.
[email protected] said:
I am new here and I have also googled and searched extensively about this problem with no success.
C:\Users\Darin\Downloads\twrp>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.566s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.575s
I can't boot TWRP by command line or by recovery key sequence. I have flashed recovery with this TWRP image that I got directly from @messi2050 today, 1/18/2017. If I "adb reboot recovery", I get the Android crash screen - the android laying down, red triangle. My phone is a t-mobile stylo 2 plus K-550. I'm sure I followed every step in the process correctly. If there is another thread that addresses this problem, can you direct me to it please? I can't start my own thread because I'm too new, but the most relevant recent thread regarding this is locked. Yes I have rooted another phone before without a problem(Samsung). Thanks in advance for your help.
Click to expand...
Click to collapse
You have to push the ing to and directory. Fastboot push img
Sent from my LG-K550 using Tapatalk
[email protected] said:
Fastboot said it flashed successfully. It copies the file, says it's ok. I would think if it didn't flash, it would fail the fastboot flash command. So is my phone jacked? I've read about how Android can rewrite the recovery partition as a security measure, or disable flashing by other means. Some kind of added security possibly?
Why would it say OK when I flash recovery, but NOT actually flash it?
Click to expand...
Click to collapse
Are you on the newest firmware for that phone?
If you are downgrade that could be a fix to lock down the recovery
I have successfully enabled usbotg on the LG Stylo 2 plus who wants to know how I did it? Usbhost mode..mount
Usb pendrive-
Mouse
Usb hub
Keyboard...etc
They say LG STYLO 2 PLUS DOES NOT SUPPORT OTG...LIES....LIES....THEY JUST DISABLED IT...WHY?...WELL..
FOLLOW THESE STEPS TO ENABLE FULL OTG SUPPORT
1-in root explorer go to:
-/sys/devices/soc/78db000.usb/power_supply/usb/usb_otg and edit from =0 to 1save
then-/sys/devices/soc/78db000.usb/dpdm_pulldown_enable edit disabled to enable.. plug in otg cable..
Done
WoodEe23 said:
I have successfully enabled usbotg on the LG Stylo 2 plus who wants to know how I did it?
Click to expand...
Click to collapse
You enabled it by adding it to the build prop lol
Dig waaayyyy deeper ..like
/sys/devices/soc/78db000.usb/power_supply/usb/ scroll to usb_otg and edit it from disabled to enable.
Then /sys/devices/soc/78db000.usb/dpdm_pulldown_enable edit it to enabled..
VOILA!!!"PLUGIN OTG CABLE AND UR IN THERE LIKE SWIMWEAR
This guide will help mac users with rooting their Oneplus X
BEFORE STARTING!
This could void the warranty of your device.
I won’t be held responsible for anything that happens from doing this tutorial so please proceed at your own risk.
All your data will be erased, so please make a back-up!
Please enable usb debugging in developer options(tap 7 times on build number).
Connect your phone to your mac and you will see Oneplus Drivers in your finder.
Double click on AndroidFileTransfer(OSX).dmg
Drag Android File transfer to the programs folder.
Step 1: Setting up ADB and FASBOOT and unlocking the bootloader
- Power off your phone and hold power button+volume up
- The phone should enter fastboot mode
- Go to https://drive.google.com/drive/u/0/folders/0B-baud5R8XkwLWYxcHNmbGZTY1U
and download the 3 files.
- Go ahead and unzip fastboot.zip then copy over the recovery.img file into fastboot folder.
- Open Terminal
- In Terminal type the following with hitting enter at the end of each line:
cd downloads
cd fastboot
chmod 755 *
./fastboot-mac oem unlock
- Your phone will reboot and you will be asked to unlock the bootloader. Just hit the Power button and unplug
your phone
- Phone will reboot
- Setup your phone
- Copy the UPDATE-SuperSU-2.78.zip to the internal storage of your OnePlus X using Android File Transfer.
- Power off your phone and hold power button+volume up, you should enter fastboot.
- Re-connect the USB cable once in fastboot mode.
Step 2: Flashing custom recovery and rooting
- Open terminal
- In Terminal type the following with hitting enter at the end of each line:
./fastboot-mac flash recovery recovery.img
./fastboot-mac erase cache
- Wait for it to finish and unplug your phone
- Hold down power and volume down for 20 seconds.
- The phone should boot into recovery.
- Once in TWRP recovery, choose “Install”
- Choose the Super SU zip file you copied over to your phone earlier.
- Swipe to flash.
- Choose “Reboot System”.
- If twrp asks your to disable stock recovery, swipe to disable.
YOUR OPX WILL REBOOT AND IS NOW ROOTED!
To check, open to superSU app and check for errors, no errors=rooted!
Thanks to https://theunlockr.com/ for the windows tutorial.
Need help ? Post a comment and I will help. :good:
Noticed spelling mistakes? Please let me know
ᕕ( ಠ‿ಠ)ᕗ
Just hijacking this post here to say, way to go buddy !
jk, reserved
Sorry guys, I know this is a very old thread but I've tried this so many times and did not work. My problem is that nothing happens in my device when I type the command to unlock the bootloader using Terminal.
I get the following message: Brunos-MacBook-Pro:fastboot Brunolima$ ./fastboot-mac oem unlock
...
OKAY [ 0.001s]
finished. total time: 0.001s
Brunos-MacBook-Pro:fastboot Brunolima$
And then that's it. It doesn't reboot and when i manually reboot it is in the same state as before.
Any ideas guys?
Hey, I've been trying the same thing. Didn't have your specific issue but I think it may be related to the fact that it's already unlocked.
That said, I to make everything work I basically used this guide + the commands from the official TWRP guide at the page "TWRP for OnePlus X" + the command from a guide in the official OnePlus guide called "[GUIDE] ONYX: How to Unlock Bootloader, Install Custom Recovery, Root, Take EFS Backup & More !!" --- sorry but I can't post links.
All in all the commands I've used where:
adb reboot bootloader
fastboot devices
fastboot oem unlock
fastboot oem device-info
fastboot flash recovery twrp.img
fastboot boot twrp.img
brunolimaam said:
Sorry guys, I know this is a very old thread but I've tried this so many times and did not work. My problem is that nothing happens in my device when I type the command to unlock the bootloader using Terminal.
I get the following message: Brunos-MacBook-Pro:fastboot Brunolima$ ./fastboot-mac oem unlock
...
OKAY [ 0.001s]
finished. total time: 0.001s
Brunos-MacBook-Pro:fastboot Brunolima$
And then that's it. It doesn't reboot and when i manually reboot it is in the same state as before.
Any ideas guys?
Click to expand...
Click to collapse
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.
***MOD EDIT: BE WARNED THAT WHEN PERFORMING THESE INSTRUCTIONS, THAT ALL DATA WILL BE WIPED (FACTORY RESET) FROM THE DEVICE - THIS INCLUDES THE INTERNAL DEVICE STORAGE (INTERNAL SDCARD). YOUR EXTERNAL SD FILES, HOWEVER, ARE SAFE AND WILL NOT BE MODIFIED.***
Hello.
I will attempt to keep this tutorial as concise as humanly possible, without the expenditure of costly applicably valid information. There are many other persons (whom I do not know) to thank for the majority of this information (from XDA Developers and other sites around the world wide web). Without further adieu: Let's begin!
The base operating system that this tutorial references is a Windows distro (I am operating on: Windows 10 Home OEM).
Target phone specs (http://www.lg.com/us/cell-phones/lg-MS330-White-k7):
Carrier: MetroPCS®[*]
[*]Make: LG K7 ("HW" or "White")
[*]Model: LG MS330
[*]Build number: LMY47V
[*]Software version: MS33010m
[*]Android version: 5.1.1
[*]Android security patch level: 2017-04-01
[*]Kernel version: 3.10.49
Prerequisites:
A USB cable (able to transfer data)
A functional copy of Windows
An internet connection (to download the software tools)
If you opt to not download and install the stock firmware ROM (*.kdz) and LG UP (used for many things):
You are taking a great risk in the event something catastrophic occurs (no backup; Corrupted partition(s); Broken hard-key reset; etc).
The LG UP tool combined with the ROM file enables you to fully slate the drive on the phone (effectively restoring it to a manufacturers state; No partitions, no data, nothing!).
It also acts as a major fail-safe as previously iterated.
You can also (if you take the time of day) use it to create your own customized 'factory style' bloatware free, customized filled state *.KDZ ROM! Although TWRP backups should be capable of emulating this type of behavior.
The ROM is ~1GB in file size from the server (capped at ~10MB/s download rate at the time of the writing of this post). Translation: It takes a while (~30min) to download. Fortunately for me: I had it and had to use it earlier today (TWRP backup failed).
Software tools (ADB, TWRP, SuperSU, LG UP, ROM):
ADB (Android Debug Bridge): https://developer.android.com/studio/releases/platform-tools.html
TWRP (Team Win Recovery Project) v3.2.1.0: https://twrp.me/lg/lgk7.html
SuperSU (SuperUser) v2.82: http://www.supersu.com/download
LG UP Lab v1.10: https://www.mylgphones.com/download-lg-up-software
Stock ROM (MS33010i -- *.kdz): https://mega.nz/#F!sdwRDLbZ!yPOiRPv5QJS_9I4hzL4ptQ!ddJHSBhR
This will be a step-by-step process; If you skip a step: Make sure you have a good reason!
I will be assuming you have followed the links above and both downloaded and installed the appropriate software (ADB, LG UP). Keeping everything organized is key.
For instance: Create a folder on your main drive ("C" drive is common traditionally). Name this folder "Rooty." Create a short-cut of "adb.exe" and place it there. Place the SuperSU *.zip and *.kdz ROM data files in the same directory as well.
Overview of procedures:
Enable "OEM unlock"
Enable "USB debugging"
Unlock OEM bootloader
Install ("flash") TWRP
Using LG UP (after TWRP is either installed or live loaded)
Install SuperSU
Step 1) Enable developer options
Enabling developer options -- Navigate to "Settings," then to "About phone," then to "Software info," then tap on "Build number" until the dialog states: "No need, you are already a developer."
Step 1.1) Enable OEM unlock option
Traverse two levels up; Tick off "Enable OEM unlock"; Scroll down 2 options and tick off "USB debugging."
Step 2) Unlocking the OEM bootloader
Insert your USB cable to connect your desktop/laptop to your cellphone; When the dialog comes up asking for permission to debug: Accept it (OPTIONAL: Tick off the 'always allow this device'). Ensure "Media device (MTP)" option is selected (it will automatically install the drivers from your phone to your computer if enabled).
Step 2.1) Unlocking the OEM bootloader (for the not-so-technically-inclined)
Create a textfile and name it whatever you'd like (I prefer the filename: "OEM_Unlock.bat").
Copy and paste this script and simply place it in the same directory ('folder') as ADB.
Code:
REM This will reboot the phone into "bootloader" mode
adb reboot bootloader
REM This will unlock the OEM bootloader (a message will display on the starting logo afterwards)
fastboot oem unlock
REM This is just to verify that it was successfully unlocked ("unlocked: yes")
fastboot getvar unlocked
Alternatively: You can manually input the commands one at a time by typing them yourself or copying and pasting.
Step 3) Installing TWRP
You can just use ADB to directly flash the recovery partition of the ROM on the phone:
Code:
fastboot erase recovery
fastboot flash recovery C:/Android/recovery.img
You can also simply 'live boot' into TWRP (less risk of a faulty TWRP):
Code:
fastboot boot C:/Android/recovery.img
Now TWRP is installed (unless you simply loaded the image file into the phone's RAM).
Using LG UP to flash the ROM ("WIPE" every partition of the phone with TWRP; EVERYTHING will be lost:
To use LG UP: You only need to power down the phone fully (ensure it is not yet connected to the computer).
Hold the "VOLUME UP" key (do not release); Insert the USB cable. The phone should (within moments) place itself into "DOWNLOAD MODE." At which point LG UP will recognize the phone. There will be two options: "Refurbished" and "Upgrade"; Tick off 'upgrade' every time! Below that is "3 dots" which enables you to navigate (GUI) to the directory of your desired *.tot or *.kdz file. Simply hit "start" and it'll flash the phone (it usually takes ~300s or ~5m).
Step 4) Installing SuperSU
Through TWRP: Click on "Advanced"; Then click on "ADB Sideload"; Tick both the "Wipe Dalvik cache" and "Wipe cache" (these will force all APKs to be reinstalled via root level). Then slide the bar across. Return your attention to Windows.
You can just use ADB to directly sideload SuperSu onto the phone.
Code:
adb sideload C:/Android/SuperSU.zip
The final page asks if you would like to install the "official TWRP app" and also if you'd like to install it under "system" privileges (one less than root).
The end! You now have root accessible privileges through the "SuperSu" application (which contains root privilege at this point).
Alternatively to manually inputing everything by hand into ADB: I've whipped up this simple batch script for Windows:
Code:
ECHO OFF
CD\
CLS
ECHO Waiting for the device to communicate (ensure you are not in 'recovery,' 'sideload,' or 'bootloader' state)
adb wait-for-device
REM Reboots to the bootloader
adb reboot bootloader
REM Unlocks the OEM bootloader
fastboot oem unlock
REM Quick check to see if it successfully unlocked
fastboot getvar unlocked
REM Flashes (deleting the stock ROM recovery program)
fastboot erase recovery
REM Flashes (copies the TWRP custom recovery program)
fastboot flash recovery C:/Android/recovery.img
REM Loads the TWRP custom recovery program into memory (a "live boot")
fastboot boot C:/Android/recovery.img
REM Pauses execution until the phone boots into "recovery" state
ECHO Wait until the phone enters a "recovery" state...
adb wait-for-recovery
CLS
ECHO Traverse to "Advanced" then to "ADB Sideload"
ECHO Check off clearing both the Dalvik cache and cache
ECHO Press any key *after* you swipe the bar across
ECHO(
PAUSE
REM Copies over the APK to the ROM (security exploit to gain root permissions)
adb sideload C:/Android/SuperSU.zip
adb reboot
How to use the batch script file to root your phone with ADB, TWRP and SuperSU:
Place: SuperSU.zip and TWRP.img in the same directory as the ABD/fastboot executables
Modify the absolute paths and file names to your system (EG: "C:/Android/" and "recovery.img")
I hate to post this, but I feel it to be utterly important to express my deepest gratitude to all those who have posted this information that was scattered about the internet. This is my first Android or PHONE for that matter to root! It was quite the under-taking (nearly a 48 hour scourge of research). I've learned quite a bit how the Android OS works internally as a result; as well as the tool-kits that are commonly used in conjunction with modding the Android (out of the scope of this thread).
I hope this very recently updated and compiled information will help ease the suffering of another's entrance into the world of rooting Android phones. I also hope it really deepens the understanding of what they're doing (EG: The commands being utilized with abd and fastboot).
Here is a helpful link in regards to adb/fastboot:
- Quick reference to abd commands (syntax and meaning): https://developer.android.com/studio/command-line/adb.html
- Alternatively: You can use "adb help" to see a print-out of the commands and arguments (same applies to fastboot).
Happy rooting, y'all!
Thanks for the write-up!
The attached SuperSU.zip worked perfect to gain root on my K7 m1 using the adb sideload in Twrp and PC.
My bootloader I had already unlocked. Twrp, I flashed before I accomplished that feat!
Was rooted with Kingroot but wasn't satisfied with that.
Factory reset, and followed your adb sideload instructions to gain root with SuperSU.zip ..
Thanks again my friend.
Custom Roms for the K7 seem to be scarce, unless I am looking in all the wrong places.
Would be much appreciated if anyone could help me on that front?? ... Please let me know.
Good Day
With very insignificant changes to syntax used above I found this works perfectly on OSX as well.
Thanks
hi, i cant seem to unlock the bootloader. i have already enabled oem unlock and usb debuggin from settings but it always fails
Code:
PS C:\adb> adb devices
List of devices attached
ZSTSS8DUSWZD9LCE unauthorized
PS C:\adb> adb reboot bootloader
PS C:\adb> fastboot devices
ZSTSS8DUSWZD9LCE fastboot
PS C:\adb> fastboot oem unlock
...
(bootloader) Start unlock flow
FAILED (remote:
Unlock operation is not allowed
)
finished. total time: 9.294s
I should note that kingrot also failed to root
i dont know whats wrong, imma gonna try factory reset and try again
UPDATE
It seems the allow oem unlock option got disabled by itself somehow, i re enabled, tried again and unlocked succesfully
UPDATE 2
Aaaaand Bootloop, dunno what went wrong, iv'e reached step 4, flashed twrp, then tried to reboot into twrp and now im stuck in bootloop
Code:
PS C:\adb> adb reboot bootloader
PS C:\adb> fastboot oem unlock
...
(bootloader) Start unlock flow
OKAY [ 8.981s]
finished. total time: 8.983s
PS C:\adb> fastboot getvar unlocked
unlocked: yes
finished. total time: 0.003s
PS C:\adb> fastbot erase recovery
fastbot : The term 'fastbot' is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ fastbot erase recovery
+ ~~~~~~~
+ CategoryInfo : ObjectNotFound: (fastbot:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
PS C:\adb> fastboot erase recovery
erasing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.004s
PS C:\adb> fastboot flash recovery c:/adb/lg.img
target reported max download size of 134217728 bytes
sending 'recovery' (12010 KB)...
OKAY [ 0.394s]
writing 'recovery'...
OKAY [ 0.706s]
finished. total time: 1.103s
PS C:\adb> adb reboot recovery
error: device '(null)' not found
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