Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Welcome to the Nexus 6 All-In-One Guide. If you are a new user that is looking for the opportunity to take advantage of your device and do it right the first time, this guide is here to point the way. This thread exists to keep all the necessary methods and material in one common place just for you. As always: Do your homework first.
If followed correctly, this guide can be a useful tool. These steps are listed in the order in which they should be completed. The intent is to seamlessly unlock, root, backup and/or flash, leaving as little room for error as possible. This process will erase and/or reset everything on your device. All steps are assuming you have backed up your contacts, texts, pictures, videos, etc. I do not take credit for any of this material or information.
This guide is a compilation of work from across XDA, most specifically users like @Chainfire and @Chromium, that I have simply brought together.
Step 1: Read. Read. Succeed.
Your journey down the Android path of rooting and modifying can be smooth, fun and educational, based on your attempt at learning everything you can before you begin. This is entirely up to you, the user. There is some excellent material here on XDA that I highly recommend reading over as part of step 1. Even though these 2 informational links were written for the Nexus 5, the knowledge still applies so don't skip this information!
A message from the moderators - All users please read
Yep, read it. It's for your own good. Included with some very useful general forum information, it also contains the forum rules which should also be read and understood.
[FAQ][REF]★All you need to know about Android | Read this before you post/root★
This awesome thread by @abaaaabbbb63 is a *noob friendly* collection of information every user that wants to root their phone should know. Many people blindly follow guides without even knowing what "Rooting" means. Hopefully, this will help new users (and old ones, why not?) understand what is happening with their phone, and what they will put up with. Get on over there and read it.
Be sure to checkout Post #2 below for additional information regarding your Nexus 6
Step 2: Installing The Necessary Desktop Tools
ADB and Fastboot Installation
Download the full Android SDK here (scroll to the bottom of the page>DOWNLOAD FOR OTHER PLATFORMS>SDK Tools Only).
Extract the zip and place the android-sdk-windows folder on your desktop.
**If you chose to download the slimmed sdk skip to step 5**
Only if you downloaded the full sdk: Go into the android-sdk-windows folder and run SDK Manager.exe. Install the following packages (there are a total of 4 packages):
- Tools > Android SDK Tools, Android SDK Platform-tools
- Extras > Android Support Library, Google USB Driver
Only if you downloaded the full sdk: Go back into the android-sdk-windows directory, and you should see a new folder named platform-tools. If you don't see this new folder, repeat the step above.
To confirm that it is indeed working, open a command prompt window and enter the following commands:
Code:
cd Desktop/android-sdk-windows/platform-tools
adb version
If it displays "Android Debug Bridge version x.x.xx" it is working. If it is gives an error saying that adb is not a recognized command, it has not been successful. Carefully repeat the steps above if this is the case. Close the command prompt window when you are done.
Step 3: Unlock, Root & Custom Recovery
For those of you who want to get most out of your Nexus 6, you will certainly want to root it. Rooting your device provides you as the user many, many benefits. That's why you're here right now reading this. You want it all. Please note that there is always the chance of error during these processes. Bad or faulty USB cables, USB ports, bad/old device drivers on the computer, an active virus scanner. These are a few of the issues that can cause your device to fail to connect or prohibit a successful root/flash. Use good and original OEM USB cables. Uninstall any drivers you may have installed for previous mobile devices and disable your virus scanner.
>>>>>>Before you begin, make sure your N6 has USB Debugging Mode switched on<<<<<<
Before continuing, users must enable Developer Options in the devices settings and select the OEM Unlock option. To do so:
- Go into Settings
- Under About Phone, you'll be able to locate your Build Number
- Tap Build Number until you are notified that you have activated Developer options
- Go into Developer Options, ensure it is enabled and check the Enable OEM Unlock box
- While in Developer Options, ensure the USB Debugging box is checked
Unlock The Bootloader
Turn the phone off. Then boot it into the bootloader/fastboot mode by holding volume down + power.
Plug the phone into your PC, then open a command prompt window window and type:
Code:
cd Desktop/android-sdk-windows/platform-tools
Code:
fastboot devices
This command will list the connected devices. If your phones serial number shows up you are good to go and may continue. If the phone is NOT listed this indicates that your drivers are not installed correctly. In order for you to continue you must fix your drivers so that your phone is listed under fastboot devices.
If the phone has been recognized by the command above, proceed to unlocking the bootloader with the following command:
Remember that this step will wipe EVERYTHING off the phone
Code:
fastboot oem unlock
On the phone a screen should pop up asking whether or not you would like to unlock the bootloader. Use the volume rockers to highlight "Yes" then press power to confirm the action.
After the above command has finished executing, run the following (DO NOT skip this step, it is more important than you think):
Code:
fastboot reboot
The phone will reboot. Next you will be presented with a screen containing an android logo and a progress bar (this may take up to ten minutes to complete). Wait until the phone has fully booted up into android, then proceed onto the next section of the guide.
Close the command prompt window.
Obtain Root
The instructions below and the zip file are the work of our beloved @Chainfire. CF-Root is the root for "rooting beginners" and those who want to keep as close to stock as possible. CF-Root is meant to be used in combination with stock firmware and be the quickest and easiest way for your first root.
- Download the ZIP file
- Extract the ZIP file
- Boot your device in bootloader/fastboot mode. Usually this can be done by turning your device off, then holding VolUp+VolDown+Power to turn it on.
- Connect your device to your computer using USB
- Windows:
--- Run root-windows.bat
- Linux
--- chmod +x root-linux.sh
--- Run root-linux.sh
- Mac OS X
--- chmod +x root-mac.sh
--- Run root-mac.sh
Follow the on-screen instructions - watch both the computer and the device!
**If you want to have root access only you can stop here.**
A word on custom recoveries: A recovery image is the system level software for your Android that lets you perform several maintenance and recovery tasks. The stock recovery image is quite limited in what it allows you to do and therefore, flashing a custom recovery image is required to gain full control of your device’s administration. A custom recovery image allows you to perform the following tasks:
- Wipe your phone’s data (Factory reset) and cache
- Make, restore and manage backups of your phone’s operating system and software
- Mount, unmount and format your phone’s internal as well as external storage partitions
- Install a custom ROM or application from a zip file to your phone
- Wipe Dalvik cache and battery statistics
- Make logs for error reporting and debugging
Additionally, you can download the Goo Manager app to install TWRP updates.
*NOTE: I do not recommend Rom Manager as a tool to do anything but just install and/or update your recovery Do not flash ROMs from this application.
Installing A Custom Recovery
Go HERE to download the latest TWRP recovery for the Nexus 6.
Turn the phone off. Then boot it into the bootloader/fastboot mode by holding volume down + power.
Rename the recovery file that you downloaded above to recovery.img. *Make sure that you rename it to recovery.img NOT recovery.img.img* Remember that you should place the file in the platform-tools folder inside of the android-sdk-windows folder on your desktop.
Open command prompt and run the following commands:
Code:
cd Desktop/android-sdk-windows/platform-tools
Code:
fastboot flash recovery recovery.img
On the phone, use the volume buttons to scroll onto "Restart Bootloader" and hit power to select it. After the bootloader reloads, use the volume buttons to scroll onto "Recovery Mode" and power to select it. You should then be greeted with your newly installed custom recovery.
Close the command prompt window.
STEP 4: Making A Backup
Making a Nandroid will allow you to try out new ROMs while still keeping a safe backup in the event you experience issues during or after a custom OS or kernel installation. Be sure your device is fully charged before proceeding to the backup and flashing procedures.
If you are not already booted into recovery then do so now.
1. Boot into fastboot mode (Volume Down + Power)
2. Browse with the volume keys to Recovery Mode and press the power button
3. You are now in custom recovery.
4. In CWM go to Backup and Restore and select Backup. In TWRP select Backup. Name and select the options you want. Swipe to backup.
5. In TWRP, go to Backup and proceed to the next step(s).
6. After backup is finished, select reboot system now or stay in recovery to continue with this guide.
*NOTE: Be sure to save a copy of these backups to your computer and/or micro sd card. Having a recent backup saved to your computer and micro SD card can be useful if something happens to your phones internal memory.
Step 5A: Wiping Your Device
When flashing any ROM, it is always important to follow the proper wipe procedures in order for everything to function properly. There are various levels of wiping based on what sort of transition you may be making. In this guide, I will list the procedures for a full wipe, presuming that you are coming from the stock firmware and changing your OS completely. This is all assuming you have made the appropriate backups. ALWAYS perform the appropriate wipe before flashing a new ROM or update!
1. If you are not already in recovery, boot in now.
In CWM:
2. Select Wipe data/factory reset
3. Select Wipe Cache
4. Select Advanced and Wipe Dalvik Cache
5. Select Mounts and Storage and format /system
6. If you are transitioning from Android versions (4.4 to 4.x, etc) you must also format /data. You will lose all personal data so back it up first.
In TWRP:
2. Select Wipe
3. Select Factory Reset and wipe
4. Select System and wipe
5. If you are transitioning from Android versions (5.0 to 5.x, etc) you must also select Wipe Data and wipe. You will lose all personal data so back it up first.
Step 5B: Flashing a Custom ROM
Once you have selected a ROM for your Nexus 6:
1. Download the ROM. Be sure to download the appropriate Gapps as well.
2. From your PC, place the ROM/Gapps on your internal storage. Remember where they are.
3. Boot into custom recovery.
4. Perform the wipe listed above if you have not already.
5. From the main recovery screen:
>>CWM - Choose the "install .zip from SD Card" and confirm.
>>TWRP - Choose Install and locate the desired ROM on your internal storage.
6. Repeat step 5 and select the Gapps package.
7. Reboot system. It will take several minutes to load so be patient and don't worry. Once the phone is booted, let it sit for 5 minutes, reboot and enjoy!
>>Additional Information
Want the performance boost available with disabling forced encryption? Check out @bbedward's guide linked below for more information and instructions.
[How-To] Disable Forced Encryption
Running Windows 8.x and having device detection issues? Be sure to grab the Google USB drivers and follow the instructions from the link below.
Nexus 6 Driver (ADB, Fastboot and MTP) for Windows and MAC
Need to return your Nexus 6 to stock for resale, OTA or warranty purposes?
Checkout @Mr hOaX's excellent guide. The procedures require the use of the fastboot tool from the Android SDK. See post #1 above for information on installing this if you have not done so already. In his guide, you have the option of returning completely to stock or select specific portions to flash (radio, recovery, etc).
[Guide][How To] Flash Factory Images For Nexus 6
Looking for stock recovery? If you need to revert to stock to receive an OTA, here's the LRX22C Android recovery:
Unzip the image and flash per the norm in fastboot.
View attachment recovery.zip
Maybe I missed it while skimming the guide, but shouldn't there be instructions for people to get Developer Options? Allowing the PC access to your phone on first plug in (ADB won't discover the device without this)? And, most importantly for Nexus 6 (and 9), checking the "OEM Unlock" option in Developer Options?
Added. Thanks for catching that, @Kusanagi Fire :good:
I was just wondering but where are there custom ROMs? Im assuming there are none, but I cant get many things to work
Thanks for all the great info! Would it be possible to add information about removing encryption to this guide?
welp,I got the phone in the mail yesterday and had plans to stay completely stock for a couple weeks,but just couldn't help myself,grabbed the chainfire and twrp files with this guide unlocked bootloader/rooted/ installed custom recovery so here we go ...made my first nandroid already[emoji4]
bogus83 said:
Thanks for all the great info! Would it be possible to add information about removing encryption to this guide?
Click to expand...
Click to collapse
i'll think about it.
http://forum.xda-developers.com/nexus-6/development/disable-forced-encryption-gain-root-t2946715
So if all I do is unlock the bootloader and root, I can still receive OTAs directly?
Sent from my Moto X using Tapatalk
Are the steps the same for a mac?
gotsoot said:
So if all I do is unlock the bootloader and root, I can still receive OTAs directly?
Sent from my Moto X using Tapatalk
Click to expand...
Click to collapse
yup, but you may lose root and your bootloader may be re-locked if they push a bootloader update with it. just fyi.
the likely (hopefully) worst case is likely that you you have to unlock it again (thus wiping your data) and you have to re-setup the phone and re-root.
i cant guarantee success or failure so you assume all risk when you begin ANY modifications on your device.
Are bootloader updates common for Nexus phones? I can't recall hearing about one (though this will be my first Nexus).
Sent from my Moto X using Tapatalk
There were one or two for the nexus 5
Fastboot
Can somebody confirm that fastboot is working on Windows 8.1 because last time I tried it didn't work and I had to use Ubuntu to fastboot my htc.
I'm running Windows 8.1 but my computer would detect my Nexus 6 after installing the drivers via SDK manager. I followed these additional steps and installed the google USB drivers, and that worked for me:
http://www.theandroidsoul.com/nexus-6-driver-adb-fastboot-mtp-windows-mac/
Great stuff, thanks so much for putting this together!
No need for toolkit or drivers on Mac/Linux
Here's Mac/Linux way.
First create a file on your home folder named something like nexus 6. (This is where your going to save your files.)
Download su(I'll let op point to zip)
Download recovery (same as above from op)
Put them both in that file you created. (Make sure it is in home or you'll have to cd to wherever you put it)
OK make sure you back up your data(this will wipe everything.)
Boot into fastboot.
(Hold power and up/down button)
(Ensure you have adb and fastboot installed on your comp)
cd RootNexus (or whatever you named that folder you created)
*First things first...
./fastboot devices
Should see your device.(if not double check adb and fastboot are installed properly. Follow link. http://forum.xda-developers.com/showthread.php?t=1917237(make sure to click thanks button over there for easy setup.)
.
./fastboot oem unlock
(Follow on screen instructions, this will wipe data. )
./Fastboot restart bootloader.
(Linux users remove ./ in front of fastboot.)
Start up phone and sign in and let it completely boot. Then put SuperSU on device.
On your Mac/Linux
(Ensure you are still in root nexus folder)
./fastboot flash recovery recovery.img where recovery.img is the name of your recovery image file
Once that is done on your phone press the volume up (twice) until you see "Recovery". Then press the power button.*
Once inside recovery go to back up and back up your device.
Flash SuperSU after. Then restart and applaud yourself. Your now rooted. I've been doing it this way since forever
Because decrypting makes such a big change in performance, that would be good to have in this thread as well.
gamewarden234 said:
Because decrypting makes such a big change in performance, that would be good to have in this thread as well.
Click to expand...
Click to collapse
I'm putting together some additional information for post #2 of this thread. It will include decryption. :good:
gotsoot said:
So if all I do is unlock the bootloader and root, I can still receive OTAs directly?
Sent from my Moto X using Tapatalk
Click to expand...
Click to collapse
I would like to know this also.
*nevermind*
[SIZE=+3]Heisenberg's How-To Guide For Beginners[/SIZE]
[SIZE=+2]Nexus 5X[/SIZE]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[SIZE=+1]Intro[/SIZE]
This thread will serve as a location for basic how-to guides for the Nexus 5X. I'm going to start off with a couple of the more obvious ones and go from there. If anyone has any suggestions for additions please feel free to let me know.
If you're unsure about something please read the FAQ section in post #2 before creating a post to ask a question.
[size=+1]Prerequisites[/size]:
You'll need a working adb/fastboot environment on your PC to get through some of these guides. Below are two options for install.
Please do not install adb/fastboot via any means other than the Android SDK, using other tools (like Minimal adb & fastboot) can lead to an outdated setup and various problems with flashing. You've been warned, other tools will not be supported in this thread.
Option A
Google hosts ADB/Fastboot (platform-tools) for Windows, OSX, and Linux. This is a minimal download, in contrast to Option 2. These links and file sizes may be updated periodically by Google. If using Windows, download the Google USB Driver and follow the driver install instructions. Once you have downloaded the platform-tools zip, extract the file then transfer the platform-tools folder to your desktop. The platform-tools folder contains adb, fastboot, and several other files. Note that clicking any link for platform-tools will immediately start a download.
*Windows: platform-tools. Google USB Driver install.
*OSX: platform-tools. For additional details on how to use OSX and adb/fastboot commands, see post #3.
*Linux: platform-tools.
See Option B below for old method to install adb/fastboot:
Option B
Go here to download the Android SDK, which will give you most updated version of adb and fastboot. Scroll to the bottom of the page and find Other Download Options>SDK Tools Only, and grab the right version for your OS. While it's downloading create a folder in C:\ called SDK (C:\SDK). Once you've downloaded the zip you can extract it into your C:\SDK folder. Navigate to C:\SDK\android-sdk-windows and open SDK Manager.exe. In SDK Manager you need to install the following packages:
Tools> Android SDK Tools, Android SDK Platform-tools
Extras> Android Support Repository, Google USB Driver
Once you have installed those, inside C:\SDK you should see some new folders, one of them will be called platform-tools, within that folder you should see fastboot.exe and adb.exe. I'll refer to this as your fastboot folder/directory or working folder/directory during this guide.
For Option A and B, make sure adb is correctly installed. Open a command prompt from within your fastboot folder (hold shift + right click, select open command prompt here) and issue this command:
Code:
adb version
If it returns a version number for Android Debug Bridge then you're good to go.
You can test adb by connecting your device to your PC while booted into Android (making sure that adb/usb debugging is enabled in Settings>Developer Options) with the screen unlocked and issuing this command:
Code:
adb devices
It should return your device serial number, if so, adb is working.
You can test fastboot by connecting your device to your PC while booted into the bootloader (power + volume down) and issuing this command:
Code:
fastboot devices
It should return your device serial number, if so, fastboot is working.
By attempting any of the processes listed this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches on fire, or turns into a hipster and claims to have been modified before it was cool.
[SIZE=+1]Quick Tips[/SIZE]
How to boot into the bootloader:
Power off your device. Once it's powered off hold power + volume down and the phone will boot into the bootloader. You can also use the following adb command:
Code:
adb reboot bootloader
You can also use an app called Quick Boot to boot into the bootloader directly from Android (root required).
How to boot into recovery:
Boot into the bootloader (see above), use the volume keys to scroll through the options and use the power button to select the recovery mode option. You can also use the following adb command:
Code:
adb reboot recovery
You can also use an app called Quick Boot to boot into the recovery directly from Android (root required).
[SIZE=+1]Index[/SIZE]
How To Unlock Your Bootloader
How To Install A Custom Recovery On Your Device
How To Decrypt Your Data Partition
How To Make A Nandroid Backup With TWRP Recovery
How To Make An EFS Backup With TWRP Recovery
How To Root
How To Install A ROM with TWRP Recovery
How To Install A Custom Kernel With TWRP Recovery
How To Update To A New Build Of The Stock ROM
How To Flash The Factory Images (Return To Stock)
How To Flash The Factory Images (Return To Stock But Leaving Internal Storage Intact)
FAQ can be found in post #2!
[SIZE=+1]1. How To Unlock Your Bootloader[/SIZE]
Go into Settings/About Phone, scroll down and click on ?build number? continuously until you see a toast notification telling you that you've enabled Developer Options. Go back to your Settings menu and enter Developer Options, scroll down and click on the ?Enable OEM Unlock? checkbox, also make sure you enable USB Debugging while you're in the Developer Options menu.
Power off your phone then boot into the bootloader (power + volume down).
Connect your phone to your PC via usb cable.
Open a command prompt from within your fastboot folder (navigate to where you have fastboot.exe located on your PC, shift + right click anywhere within that folder, select open command prompt here).
Check your fastboot connection by issuing this command:
Code:
fastboot devices
It should return your device serial number, if not you need to make sure your drivers are installed correctly.
Once you've confirmed your fastboot connection issue this command:
Code:
fastboot oem unlock
This will erase all user data from the device!
You should now see a screen on your phone asking you to confirm this action, use the volume keys to scroll and the power key to confirm if you're sure you want to go ahead.
Allow the process to complete and then issue this command:
Code:
fastboot reboot
Allow everything to go ahead and once finished you can disconnect your usb cable.
Important: do not relock your bootloader unless your phone is fully stock. You must flash the factory images first in order to remove root and custom recovery (if you have them), if this precaution isn't taken you may end up with a brick. Please see section 10 of this guide for full instructions on how to return to stock.
[SIZE=+1]2. How To Install A Custom Recovery On Your Device[/SIZE]
Prerequisites: unlocked bootloader (section 1). Please read FAQ #7 if using TWRP 3.0.2-1 or 3.0.2-2.
Download TWRP Recovery onto your PC.
Make sure you check the md5 to verify its integrity (where possible).
Place the file in your fastboot folder (this is where fastboot.exe is located on your PC).
Power off your phone then boot into the bootloader (power + volume down).
Open a command prompt from within your fastboot folder (navigate to where you have fastboot.exe located on your PC, shift + right click anywhere within that folder, select open command prompt here), enter this command:
Code:
fastboot flash recovery filename.img
(The recovery filename in the command will change depending on which recovery you're flashing)
Use the volume keys to scroll and power key to select the Reboot Bootloader option. Once the phone has booted back into the bootloader, use the volume keys to scroll and the power key to boot into your newly flashed recovery. It's now safe to disconnect your usb cable. If using Nougat 7.0 or newer, you must now boot directly into TWRP and flash SuperSU (or your preferred root alternative) so that TWRP will persist between reboots.
When TWRP boots up you'll be asked whether you want to allow system modifications or to keep it read-only, choose to allow system modifications, there's no benefit to keeping it read-only.
Do not flash the version of SuperSU that TWRP offers to flash for you in order to give you root, it is not compatible and will cause problems. When you attempt to reboot out of TWRP it will tell you that it's detecting that you don't have root and it will offer to root for you, skip past this.
Some users need a custom recovery for a temporary period, so they live boot the recovery. In this scenario, the custom recovery replaces the stock recovery until a reboot is performed. Place the file in your fastboot folder then enter this command:
Code:
fastboot boot filename.img
(The recovery filename in the command will change depending on which recovery you're flashing)
[SIZE=+1]3. How To Decrypt Your Data Partition[/SIZE]
This is no longer necessary as long as you use TWRP 2.8.7.1 or newer
Prerequisites: unlocked bootloader (section 1).
TWRP recovery cannot decrypt your data partition at this stage. In order for TWRP to be able to read/write on your data partition (to root or create a nandroid backup) you will need to format it, a format will remove encryption.
Boot into the bootloader and connect your phone to your PC via usb cable.
Open a command prompt from within your fastboot folder (navigate to where you have fastboot.exe located on your PC, shift + right click anywhere within that folder, select open command prompt here), enter this command:
Code:
fastboot format userdata
Please note: this will erase all user data from the device!
Once the process has completed you can either reboot normally:
Code:
fastboot reboot
Or you can reboot back to the bootloader in order to undertake another task:
Code:
fastboot reboot-bootloader
[SIZE=+1]4. How To Make A Nandroid Backup With TWRP Recovery[/SIZE]
Prerequisites: unlocked bootloader (section 1), TWRP recovery (section 2).
A nandroid backup is a very important thing to have before installing any custom software on your device. It's basically a backup of your stock system that you can fall back on if anything goes wrong or if you just want your stock ROM back. You can also use the backup tool to create a backup of your favourite ROM set up exactly the way you like it. The backup you create can be easily restored using the restore tool in TWRP recovery.
Boot TWRP recovery, select the backup option from the TWRP home screen, check the system/data/boot boxes, and swipe to backup. The process will take a few minutes.
[SIZE=+1]5. How To Make An EFS Backup With TWRP Recovery[/SIZE]
An EFS backup is very important to have, if your EFS partition becomes corrupt you will have no IMEI, and therefore will not be able to use the phone as a phone. Making an EFS backup is insurance against this catastrophic event. Without a backup, restoring your EFS can be extremely difficult or impossible. The backup you create can be easily restored using the restore tool in TWRP recovery.
Please read FAQ #7 if using TWRP 3.0.2-1 or 3.0.2-2. Boot into TWRP and select the backup option from the TWRP home screen, make sure only the EFS box is selected, and swipe to backup. The process will take a few seconds. Keep a copy of the backup on your phone and also keep another copy somewhere safe.
[SIZE=+1]6. How To Root[/SIZE]
Prerequisites: unlocked bootloader (section 1), TWRP recovery (section 2).
Download the latest root method of your choosing to your phone:
Magisk
SuperSU Stable
SuperSU Service Release (SuperSU beta channel)
Or to root Android Nougat 7.0 visit this thread: Use SuperSU 2.78 or newer.
[WIP] Android N Preview
Boot into TWRP recovery and enter the install menu.
Navigate to where you have SuperSU stored on your internal storage and select it.
Swipe to install.
Once you've installed SuperSU you'll have an option to wipe cache/dalvik and an option to reboot system. Wipe the cache/dalvik, hit the back button, and hit the reboot system button. That's it.
Do not flash the version of SuperSU that TWRP offers to flash for you in order to give you root, it is not compatible and will cause problems. When you attempt to reboot out of TWRP it will tell you that it's detecting that you don't have root and it will offer to root for you, skip past this. You do have root, ignore this every time it comes up.
[SIZE=+1]7. How To Install A ROM with TWRP Recovery[/SIZE]
Prerequisites: unlocked bootloader (section 1), TWRP recovery (section 2), vendor.img (section 9).
Installing a ROM is a straight forward and easy process. Before you install anything you should make a nandroid backup (instructions above). Next, install the vendor.img that matches the Google security OTA that the ROM you want to install is based on. Find the vendor.img inside the factory images provided by Google then flash this file with fastboot (section 9).
Download a ROM and appropriate Gapps package and place on your device.
Boot into your custom recovery.
Select the wipe option from the TWRP home screen.
Perform a Factory Reset.
Select advanced wipe.
Check the system, data, cache, and dalvik cache options.
Swipe to wipe.
Install the ROM.
Select the install option from the TWRP home screen.
Navigate to where you have the ROM zip stored on your sd card and select it.
Swipe to install.
Most ROMs will run an installer script at this point but some ROMs have what is called an Aroma Installer which allow you to choose some install options before the script runs.
You will also need to install the appropriate gapps package directly after installing the ROM.
Once you've installed all necessary zips you'll have an option to wipe cache/dalvik and an option to reboot system. Wipe the cache/dalvik, hit the back button, and hit the reboot system button.
[SIZE=+1]8. How To Install A Custom Kernel With TWRP Recovery[/SIZE]
Prerequisites: unlocked bootloader (section 1), TWRP recovery (section 2).
A custom kernel can open up a new level of control over your device, such as overclocking/underclocking, undervolting, changing governors, changing I/O schedulers, adjusting colour calibrations, adjusting sound calibrations, and many other options.
Download a kernel that is compatible with your current ROM.
Check the md5 to verify its integrity.
Enter TWRP recovery.
Select the install option from the TWRP home screen.
Navigate to the kernel and select it.
Swipe to install.
You'll have an option to wipe cache/dalvik and an option to reboot system. Wipe the cache/dalvik, hit the back button, and hit the reboot system button.
Once your phone has booted up you can use a kernel tuning app to change governors, I/O scheduler, clock speed, and other options. Some of the popular kernel apps are Kernel Auditor, EX Kernel Manager, Trickster Mod, No Frills, Kernel Tuner, and many more.
[SIZE=+1]9. How To Update To A New Build Of The Stock ROM[/SIZE]
Prerequisites: unlocked bootloader (section 1).
This method does not wipe your data, so you will keep your apps and settings. You should have no problems, however, if you experience problems you may need to perform a factory reset and flash again. Make a backup first and transfer it to your PC.
Download the latest build via the appropriate factory images for your model (Nexus 5X/Bullhead) here.
Note: Android 7.1.2 and newer factory images do not contain cache.img. Do not wipe the cache.img for this process when using or moving to Android 7.1.2 or newer. If you have wiped cache.img, download the most recent Android 7.1.1 factory image and flash the cache.img from that zip archive.
Unzip the bullhead-xxxxxx-factory-xxxxxxxx (x's replace variables) into a directory on your PC (for this guide we'll use C:\bullhead\).
Once unzipped you should have a folder named bullhead-xxxxxx (x's replace variables). Open it and move the following files to a new directory named C:\bullhead\images\:
bootloader-bullhead-bullhead-xx.xx.img
radio-bullhead-bullhead-xx.xx.img
(Please note that radio and bootloader naming changes from build to build so the filenames and below commands will change with them)
Within C:\bullhead\bullhead-xxxxxx\ you'll see another zip archive named image-bullhead-xxxxxx, unzip the contents of that zip into the C:\bullhead\images\ folder we created before. Now within C:\bullhead\images\ you should have the following files:
android-info.txt
boot.img
bootloader-bullhead-bullhead-xx.xx.img
cache.img
radio-bullhead-bullhead-xx.xx.img
recovery.img
system.img
userdata.img
vendor.img
Boot into the bootloader and connect your phone to your PC via usb cable.
Open a command prompt from within your fastboot folder (navigate to where you have fastboot.exe located on your PC, shift + right click anywhere within that folder, select open command prompt here), enter these commands to flash:
Code:
fastboot flash bootloader C:\bullhead\images\bootloader-bullhead-bullhead-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\bullhead\images\radio-bullhead-bullhead-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\bullhead\images\boot.img
fastboot erase cache
fastboot flash cache C:\bullhead\images\cache.img
fastboot flash recovery C:\bullhead\images\recovery.img
fastboot flash system C:\bullhead\images\system.img
fastboot flash vendor C:\bullhead\images\vendor.img
You can skip flashing the recovery if you wish, but even if you do the stock recovery may be patched on the first boot anyway. So you'll need to flash TWRP and SuperSU again if you need/want those, as well as any other system modifications you may have had.
You'll have to flash SuperSU again now, plus add any mods that you previously had.
[SIZE=+1]10. How To Flash The Factory Images (And Return To Stock)[/SIZE]
Prerequisites: unlocked bootloader (section 1).
This section will explain how to return the phone to be like it was when it came out of the box. This will wipe everything from the phone. If you wish to flash the factory images without wiping your personal data from the internal storage please move on to the next section.
Note: Android 7.1.2 and newer factory images do not contain cache.img. Do not wipe the cache.img for this process when using or moving to Android 7.1.2 or newer. If you have wiped cache.img, download the most recent Android 7.1.1 factory image and flash the cache.img from that zip archive.
Go to Settings/Backup & Reset and perform a factory data reset. This will remove all of your user data from the device (apps, settings, photos, music, etc).
Download the appropriate factory images for your model here.
Unzip the bullhead-xxxxxx-factory-xxxxxxxx (x's replace variables) into a directory on your PC (for this guide we'll use C:\bullhead\).
Once unzipped you should have a folder named bullhead-xxxxxx (x's replace variables). Open it and move the following files to a new directory named C:\bullhead\images\:
bootloader-bullhead-bullhead-xx.xx.img
radio-bullhead-bullhead-xx.xx.img
(Please note that radio and bootloader naming changes from build to build so the filenames and below commands will change with them)
Within C:\bullhead\bullhead-xxxxxx\ you'll see another zip archive named image-bullhead-xxxxxx, unzip the contents of that zip into the C:\bullhead\images\ folder we created before. Now within C:\bullhead\images\ you should have the following files:
android-info.txt
boot.img
bootloader-bullhead-bullhead-xx.xx.img
cache.img
radio-bullhead-bullhead-xx.xx.img
recovery.img
system.img
userdata.img
vendor.img
Boot into the bootloader and connect your phone to your PC via usb cable.
Open a command prompt from within your fastboot folder (navigate to where you have fastboot.exe located on your PC, shift + right click anywhere within that folder, select open command prompt here), enter these commands to flash:
Code:
fastboot flash bootloader C:\bullhead\images\bootloader-bullhead-bullhead-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\bullhead\images\radio-bullhead-bullhead-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\bullhead\images\boot.img
fastboot erase cache
fastboot flash cache C:\bullhead\images\cache.img
fastboot flash recovery C:\bullhead\images\recovery.img
fastboot flash system C:\bullhead\images\system.img
fastboot flash vendor C:\bullhead\images\vendor.img
If you wish to you can also relock the bootloader with this command:
Code:
fastboot oem lock
(This command will wipe all user data from the device)
Important: do not lock the bootloader unless you have first flashed the stock images. Locking the bootloader while you have a custom recovery installed can result in a brick. Please also note that the locking procedure will wipe all data on an encrypted device.
Once all commands/flashes are complete you can reboot the device:
Code:
fastboot reboot
[SIZE=+1]11. How To Flash The Factory Images (Return To Stock But Leaving Internal Storage Intact)[/SIZE]
Prerequisites: unlocked bootloader (section 1), TWRP recovery (section 2). Note: Android 7.1.2 and newer factory images do not contain cache.img. Do not wipe the cache.img for this process when using or moving to Android 7.1.2 or newer. If you have wiped cache.img, download the most recent Android 7.1.1 factory image and flash the cache.img from that zip archive.
This section will explain how to return the phone to be like it was when it came out of the box, except it will not wipe any of your personal data (photos, music, etc) from the internal storage.
Download the appropriate factory images for your model here.
Unzip the bullhead-xxxxxx-factory-xxxxxxxx (x's replace variables) into a directory on your PC (for this guide we'll use C:\bullhead\).
Once unzipped you should have a folder named bullhead-xxxxxx (x's replace variables). Open it and move the following files to a new directory named C:\bullhead\images\:
bootloader-bullhead-bullhead-xx.xx.img
radio-bullhead-bullhead-xx.xx.img
(Please note that radio and bootloader naming changes from build to build so the filenames and below commands will change with them)
Within C:\bullhead\bullhead-xxxxxx\ you'll see another zip archive named image-bullhead-xxxxxx, unzip the contents of that zip into the C:\bullhead\images\ folder we created before. Now within C:\bullhead\images\ you should have the following files:
android-info.txt
boot.img
bootloader-bullhead-bullhead-xx.xx.img
cache.img
radio-bullhead-bullhead-xx.xx.img
recovery.img
system.img
userdata.img
vendor.img
Boot into TWRP recovery and enter the wipe menu, select advanced wipe, check only the data box and swipe to wipe.
Go to the TWRP main menu and enter the reboot menu, select bootloader. The phone will now boot into the bootloader, once it has you can connect your phone to your PC via usb cable.
Open a command prompt from within your fastboot folder (navigate to where you have fastboot.exe located on your PC, shift + right click anywhere within that folder, select open command prompt here), enter these commands to flash:
Code:
fastboot flash bootloader C:\bullhead\images\bootloader-bullhead-bullhead-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\bullhead\images\radio-bullhead-bullhead-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\bullhead\images\boot.img
fastboot erase cache
fastboot flash cache C:\bullhead\images\cache.img
fastboot flash recovery C:\bullhead\images\recovery.img
fastboot flash system C:\bullhead\images\system.img
fastboot flash vendor C:\bullhead\images\vendor.img
Once all commands/flashes are complete you can reboot the device:
Code:
fastboot reboot
FAQ can be found in post #2!
Donate To Me
[size=+1]Frequently Asked Questions[/size]
1. How do I boot into the bootloader?
Power off your device. Once it's powered off hold power + volume down and the phone will boot into the bootloader. You can also use the following adb command:
Code:
adb reboot bootloader
You can also use an app called Quick Boot to boot into the bootloader directly from Android (root required).
2. How do I boot into recovery?
Boot into the bootloader (see above), use the volume keys to scroll through the options and use the power button to select the recovery mode option. You can also use the following adb command:
Code:
adb reboot recovery
You can also use an app called Quick Boot to boot into the recovery directly from Android (root required).
3. When issuing the fastboot flashing unlock command it doesn't work, I only get a list of possible commands. What's going on?
This is usually due to having an outdated adb/fastboot setup. If you installed adb/fastboot by any means other than via the Android SDK this is probably the cause. Visit the prerequisites section in the beginning of this guide to properly install adb/fastboot and ensure that it's up to date.
4. How do I take an OTA or update if I have root or other system modifications on the stock ROM?
You can't take an OTA update while you have root or any system modifications. You'd need to use fastboot to flash the system, boot, and recovery images. It's much easier to just flash the newer build with fastboot, see section 9 of this guide for full instructions.
5. Does taking an OTA update wipe my user data?
No, it doesn't.
6. Do I need to make an EFS backup?
Absolutely yes. An EFS backup is extremely important. If your EFS partition becomes corrupt, your IMEI will disappear and you will not be able to use the phone as a phone. Without a backup it can be extremely difficult (or impossible) to restore your EFS. See the next question for an EFS backup related issue and solution.
7. I have a bootloop after restoring my EFS backup in TWRP 3.0.2-1. What can I do?
TWRP 3.0.2-1 and 3.0.2-2 are the first official TWRP releases with Nougat 7.0 or newer compatibility. Unfortunately, there are separate bugs affecting TWRP 3.0.2-1 and 3.0.2-2. A member of the TWRP development team details these issues right here. This link redirects to a thread in the Nexus 6P forums but also applies to the Nexus 5X. Read the original post of that same thread to learn how to resolve this EFS restore bootloop. You must use ADB and the phone must be booted in TWRP to resolve this issue. These ADB commands work on the Nexus 5X and 6P.
8. Can I flash just the xxxxxx.img from the factory image without losing my data?
Flashing userdata.img will format your entire phone (personal data including SMS/MMS, pictures, downloaded files, etc). You can flash any combination of these partitions (boot, system, vendor, radio, or bootloader) and this will leave your personal data intact. However, any mods that you have installed into system, vendor, or boot will be overwritten and returned to the default factory image setup when you flash these partitions. Flashing recovery.img or a newer version of your custom recovery will replace your existing recovery.
9. After updating my ROM, I get this message on every boot: "There's an internal problem with your device. Contact your manufacturer."
This warning indicates a mismatched vendor and system partition. The vendor partition was formerly integrated in the system partition for previous Nexus devices but is now a separate partition that must be flashed for each Google security update. Download a factory image and update your vendor partition using fastboot so that it matches your rom's OS build and monthly security update. If you have a file explorer installed on your phone, you can determine which vendor.img is installed by navigating to /vendor/build.prop and clicking on the build.prop. The specific vendor installed will be a combination of six numbers and letters listed in all capitals (example: NMF26F) in the ro.vendor.build.fingerprint line. These will always match up with the factory image of the same Android build (six digit alphanumeric name) for this device.
Vendor.img is specific to each OTA and contains proprietary binaries for the phone that regularly receive updates to resolve security risks. If you are a custom rom user, make sure that you flash the vendor.img for the Google monthly security update that you are moving to. Be aware that sometimes AOSP roms utilize the AOSP master branch which has a newer Android build than the monthly security update for this device. You will still need to install that month's vendor.img.
The phone will fail to boot if you mismatch the vendor.img with a different Android version. For instance, a 6.0 Marshmallow vendor.img will not allow your phone to boot on 7.0 Nougat. The vendor.img is typically not included in the custom rom zip but is often available as a separate download in the custom rom thread's first post.
Reserved #2
Reserved #3
OSX, ADB and Fastboot commands!
So you use OSX and would like to use ADB/fastboot, unlock, root, or simply have a working knowledge of your phone. Welcome! Most of the information in the guide above applies to OSX, however there are a few key changes.
Google hosts ADB/Fastboot (platform-tools) for Windows, OSX, and Linux. This is a minimal download, however these links and file sizes may be updated periodically by Google. Download the OSX platform-tools. Note that clicking the link for platform-tools will immediately start a download.
*OSX: platform-tools.
Once you have downloaded the platform-tools zip, extract the file then transfer the platform-tools folder to your desktop. The platform-tools folder contains adb, fastboot, and several other files.
To make sure your ADB is installed correctly, open a terminal command prompt and issue this cd command (change directory) to the platform-tools folder:
Code:
cd /users/username/desktop/platform-tools
then issue this command to check your adb version:
Code:
./adb version
If it returns a version number for Android Debug Bridge then you're good to go.
Using ADB/Fastboot commands
OSX natively requires "./" to prefix any ADB or Fastboot commands. If following the guide in post #1, commands issued in OSX must be written as follows ./adb [command] or ./fastboot [command]. Below are example scenarios.
To check if your device sees ADB, enable USB Debugging from within Android in Settings/Developer options. Go into Settings/About Phone, scroll down and click on build number continuously until you see a toast notification telling you that you've enabled Developer Options. Go back to your Settings menu and enter Developer Options, scroll down and enable USB Debugging.
Code:
./adb devices
It should return your device serial number, if so, adb is working.
Reboot into the bootloader:
Code:
./adb reboot bootloader
Reboot into the recovery:
Code:
./adb reboot recovery
Fastboot commands must be performed while in the bootloader. Power off your phone then boot into the bootloader (power + volume down). Below are some example OSX fastboot commands that can be used throughout the guide:
Check if your device sees fastboot:
Code:
./fastboot devices
Install a factory image:
cd into the platform-tools folder with the following command:
Code:
cd /users/username/desktop/platform-tools
Now enter commands to flash a factory image:
Code:
./fastboot flash bootloader /users/username/desktop/bullhead/images/bootloader-bullhead-bullhead-xx.xx.img
./fastboot reboot-bootloader
./fastboot flash radio /users/username/desktop/bullhead/images/radio-bullhead-bullhead-xx.xx.img
./fastboot reboot-bootloader
./fastboot flash boot /users/username/desktop/bullhead/images/boot.img
./fastboot erase cache
./fastboot flash cache /users/username/desktop/bullhead/images/cache.img
./fastboot flash recovery /users/username/desktop/bullhead/images/recovery.img
./fastboot flash system /users/username/desktop/bullhead/images/system.img
./fastboot flash vendor /users/username/desktop/bullhead/images/vendor.img
@Heisenberg you mind if i create an index thread?
reyscott1968 said:
@Heisenberg you mind if i create an index thread?
Click to expand...
Click to collapse
Go right ahead, first in best dressed as far as I'm concerned. It is a fair bit of work to keep an index maintained though, as long as you're aware. There's a new template for indexes too, using your Google goggles you should be able to track it down pretty easily.
Heisenberg said:
Go right ahead, first in best dressed as far as I'm concerned. It is a fair bit of work to keep an index maintained though, as long as you're aware. There's a new template for indexes too, using your Google goggles you should be able to track it down pretty easily.
Click to expand...
Click to collapse
il take note.. il update the thread once im back on my pc.. now still at work ...
Deleted...
Should have read the first lines in the OP
Cant wait, should have mine around october 30th.
Might want to point out the cable /adapter required to connect to pc. (I just saw that it's not included with the phone.)
AquilaDroid said:
Might want to point out the cable /adapter required to connect to pc. (I just saw that it's not included with the phone.)
Click to expand...
Click to collapse
I picked up a few of these to get me by for now until the price of Type-C goes down a bit http://www.ebay.com/itm/381344035966
I ordered one along with my phone, will be helpful for flashing.
Thanks, a friend of mine pre order this phone, I'll follow these steps
Thanks for starting this, these were some of the most helpful threads in the N5 forum.
For Mac users who have upgraded to El Capitan, the adb/fastboot installation doesn't necessarily work perfectly right now. I'm sure the Android SDK package will update for this, but in the mean time:
Install adb/fastboot as usual similar to this thread, or for specifics:
http://forum.xda-developers.com/showthread.php?t=1917237
but, once you test this with [adb devices] or [fastboot devices] you'll most likely get a command not found error.
You'll need to add a line to your ~/.bash_profile, per this reddit thread
add the following line to your ~/.bash_profile, changing username to your mac username
Code:
export PATH="/usr/local/lib/node_modules:/usr/local/apache-maven-3.0.3/bin:/Users/[B]username[/B]/.composer/vendor/bin:/Users/[B]username[/B]/Library/Android/sdk/platform-tools:$PATH"
exit, save, then run
Code:
source ~/.bash_profile
then adb/fastboot should be good to go like before!
OP has best username ever
Sent from my Nexus 5 using Tapatalk
Doesn't work!
Code:
C:\Users\Kevin\Downloads\Nexus 5x>fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.017s
C:\Users\Kevin\Downloads\Nexus 5x>fastboot flashing unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.014s
C:\Users\Kevin\Downloads\Nexus 5x>fastboot flashing unlock_critical
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.011s
C:\Users\Kevin\Downloads\Nexus 5x>fastboot flashing get_unlock_ability
...
(bootloader) get_unlock_ability: 0
OKAY [ 0.020s]
finished. total time: 0.022s
The-Kevster said:
Doesn't work!
Click to expand...
Click to collapse
Did you allow OEM Unlock in developer options?
Go into Settings/About Phone, scroll down and click on “build number” continuously until you see a toast notification telling you that you've enabled Developer Options. Go back to your Settings menu and enter Developer Options, scroll down and click on the “Enable OEM Unlock” checkbox, also make sure you enable USB Debugging while you're in the Developer Options menu.
Click to expand...
Click to collapse
Does the 5X have the hardware QFuse that that pops when you unlock the bootloader like the 6P?
KidWave said:
Does the 5X have the hardware QFuse that that pops when you unlock the bootloader like the 6P?
Click to expand...
Click to collapse
They both use Qualcomm based chips so yes the same thing would happen on the 5X.
Notice: Rooting your device will break OTAs because they require an unmodified system, so you might want to check for updates before rooting your X. However, there is a workaround:
Boot into TWRP via step 5E below, but DO NOT flash it (step 5D)!!
Do a backup of your completely stock, unrooted ROM
Root the device by flashing SuperSU...zip
When an OTA hits, you can get it by doing this:
Boot into TWRP again without flashing it (same as step 1 above)
Restore your stock, unrooted ROM (from step 2 above)
Apply the update from stock recovery
Backup the unmodified ROM with the update if you want, then re-root as above.
Note: You will lose any changes, mods or app data since you did the backup, but hey, at least the OTA is applied.
If you get stuck with an update that won't flash and you haven't backed-up your unrooted ROM as above, look here:
[Guide] How to Install OTA's with TWRP, and please hit thanks for @SpiritBreak3r :good:
_____________________
Disclaimer: Rooting does not void the OnePlus X’s warranty, though damaging your hardware (i.e., burning up your CPU by overclocking, hardbricking the device) will. You proceed at your own risk! I accept no responsibility for what you do with your phone. Follow the directions closely, and the odds are you will succeed without any trouble. If you are not sure what you are doing, do some more research before you try. If you get confused with terminology, try looking here for answers or Google it. If you get stuck, post a question in the thread—we're here to help you.
Preliminary steps
1. Make sure that your phone is always charged above 50%!!!
Running out of battery in the middle of flashing something could brick your phone.
2. Make sure that your computer can properly communicate with the device:
We will be issuing commands to the phone from your PC via the USB cable using Android’s SDK tools, in particular ADB and fastboot. If you have not done so already, you must install the following on your Windows computer for this to work:
Java runtime
The Universal Android ADB Driver for Windows.
SDK tools for Android (alternately just ADB & fastboot). Remember where this is installed on your harddrive for later!
You can verify the connection between your PC and phone by running the following procedure:
A. With the phone booted normally, connect it to your computer with the USB cable.
B. Enable Android debugging by going to Settings > About phone and tapping on “Build number” 7 times.
C. Go to Settings > Developer options and check “Android debugging”. A dialogue box will appear asking you to authorize your computer’s RSA fingerprint. Click “Always allow...”
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
D. Open a command prompt in Windows and navigate to the folder where you put SDK tools for Android (ADB & fastboot) above.
E. Type the following command:
Code:
adb devices
You should get a return like this:
If you cannot get the connection to work:
1. Check your USB connection, then verify that Android debugging is enabled in settings and that your computer’s RSA fingerprint has been authorized.
2. Still not working? Open Device Manager in Windows and make sure that you don’t have a yellow exclamation point next to something like “Android Device” or “One.” This would indicate a driver problem that must be resolved. Try re-installing the Universal Android ADB Driver for Windows, and make sure to restart your computer. Once you’ve rebooted, if you still have a yellow triangle, right-click on the device and select “Update Driver Software,” then “Search automatically for updated driver software.”
3. If you still have a yellow exclamation point, then try forcing the driver to install:
In Device Manager, right-click on the device and select “Update Driver Software.”
Select “Browse my computer for driver software”
Select “Let me pick from a list of device drivers on my computer”
Select “ADB Interface” from the list
Select manufacturer “Google”
Select “Android Testing Interface Version xxx”
Click “Next.” If you get a warning, select “Yes” to continue and wait for the driver to install properly.
3. Know how to enter “fastboot mode” on the OnePlus X
To root the device, you must be competent at booting it into fastboot mode. There are two ways to accomplish this:
Power off the phone. Then simultaneously hold down the volume up & power buttons until it vibrates. When done correctly, you will see the words “Fastboot Mode” on a black screen. If not, you dumb-thumbed it, and the device will boot normally into Android. Power off the device and try again.
With the phone running Android normally and Android debugging enabled (see above), open a command prompt in Windows, navigate to the folder where you installed SDK tools (ADB & fastboot) and type:
Code:
adb reboot bootloader
Rooting the OnePlus X
There are three essential steps to rooting the device:
Unlock the bootloader
Flash or boot into TWRP custom recovery [For OxygenOS 3.1.3 use TWRP blu_sp★rk r175]
Flash SuperSU...zip from recovery [For OxygenOS 3.1.3 use SuperSU v2.78 SR1 beta]
However, we're going to add a few more to protect your data and device in case something gets borked.
1. Backup your phone’s data
Unlocking the bootloader will involve doing a factory reset resulting in the loss of all accounts, emails, texts, apps and app data, pictures, music, etc. on the device. Move anything you need to keep onto your PC or a cloud service like DropBox.
2. Unlock the bootloader
2A.Go into Developer Options and enable bootloader unlocking
2B. Boot the device into fastboot mode. (Simultaneously hold down the volume up & power buttons until it vibrates.) You should see a black screen with the words “Fastboot Mode”.
2C. Plug in the USB cable.
2D. Verify that your device is connected with this command:
Code:
fastboot devices
You should get a return like the image above under Preliminary Steps
2E. Unlock the bootloader using the following commands:
Code:
fastboot oem unlock
The device will unlock the bootloader, erase all user data and reboot itself into Android. You will have to set up everything from scratch.
3. Re-enable Android debugging
3A. Re-enable Developer options by going to Settings > About phone and tapping on “Build number” 7 times.
3B. Go to Settings > Developer options. Check “Android debugging” and re-authorize your computer’s RSA fingerprint.
4. Download SuperSU zip
4A. Head over to Chainfire’s CF-Root thread and download the SuperSU access management tool from the “CWM / TWRP / MobileODIN installable ZIP” link. It will probably called something like UPDATE-SuperSU-v2.XX.zip. This zip file will root your device and install the SuperSU access management app in one smooth motion. Hit the thanks button for Chainfire or donate to his Paypal account and buy him a Coke.
NOTE: For OxygenOS 3.1.3 use SuperSU v2.78 SR1 beta
4B. Copy UPDATE-SuperSU-v2.XX.zip to your phone’s SD card.
5. Flash TWRP custom recovery
5A. Download TWRP recovery.
NOTE: For OxygenOS 3.1.3 use TWRP blu_sp★rk r175
5B. Place file you downloaded above to the location where you installed SDK tools (ADB & fastboot).
5C. Boot the device into fastboot mode and connect it to your computer with the USB cable.
5D. In this step, we will replace your stock recovery with TWRP recovery.
Note: This step is optional. If you want to root but preserve stock recovery, skip straight ahead to step 5E below. Thanks @rockuppl for the reminder. :good:
Open a command prompt in Windows and navigate to the folder where you installed SDK tools (ADB & fastboot). Type the following commands:
Code:
fastboot flash recovery twrp-3.0.0-0-onyx.img
5E. Reboot into TWRP recovery with the following command.
Code:
fastboot boot twrp-3.0.0-0-onyx.img
You should now see the custom recovery you just flashed, not the stock recovery.
6. Backup your stock ROM before making any changes
In TWRP press “Backup.” <--- See how simple this is???
Don’t be a noob—backup your device!!! Right now we don't have stock boot debuggable image files for the OnePlus X, so borking your device could leave you with a nice paperweight until we do. :crying: Restoring from a backup in recovery is easy, and only works if you've backed-up first
7. Root the device
7A. The device should still be in recovery from step 6 above. Go back to the main menu and press “Install,” find UPDATE-SuperSU-v2.XX.zip on the SD card, then flash it.
7B. Reboot the phone. It is now rooted!
7C. Go to the app drawer and open SuperSU. Update the binary if prompted. Its icon looks like this:
7D. Download and install Root Checker from the Play Store to verify that you have root access.
Yes I already own the phone and I see the bootloader unlock switch in dev options. I also checked the stock recovery which gives options to flash files from phone memory or otg. So it must be fairly easy. But I still don't want to risk it without it being tried and tested. If there were a custom recovery I could have also backed up the factory image. Only choice is to wait and see I guess
I could try today evening... will update here.
@CafeKampuchia
Is it ok to flash supersu.zip with stock recovery.
Before flashing supersu.zip, will unlock bootloader . Will follow the guide from oneplue two procedure to unlock..
Flashing supersu is safe on hundreds of devices, but I don't have the X so I can't say one way or the other.
I tried the OnePlus One tutorial to unlock bootloader and root it thanks to this guide.
When it comes to install TWRP, adb tells me it's ok but when I boot into recovery, it's the "official" one that show up.
Even from this recovery, I tried to install the SuperSU.zip, but it keeps telling me it failed, so I think I'll just wait for someone to do it correctly
Knockys said:
I tried the OnePlus One tutorial to unlock bootloader and root it thanks to this guide.
When it comes to install TWRP, adb tells me it's ok but when I boot into recovery, it's the "official" one that show up.
Even from this recovery, I tried to install the SuperSU.zip, but it keeps telling me it failed, so I think I'll just wait for someone to do it correctly
Click to expand...
Click to collapse
I wouldn't try flashing a recovery for another device, especially if the stock recovery isn't available.
I'm surprised that supersu wouldn't flash from stock, though.
CafeKampuchia said:
I wouldn't try flashing a recovery for another device, especially if the stock recovery isn't available.
I'm surprised that supersu wouldn't flash from stock, though.
Click to expand...
Click to collapse
Well I thought that TWRP was for all devices and I already went to the stock one before installing TWRP without success to flash SuperSU.
But apprently, installing TWRP the way I did wasn't the right way because I still boot to the stock recovery :/
Knockys said:
I tried the OnePlus One tutorial to unlock bootloader and root it thanks to this guide.
When it comes to install TWRP, adb tells me it's ok but when I boot into recovery, it's the "official" one that show up.
Even from this recovery, I tried to install the SuperSU.zip, but it keeps telling me it failed, so I think I'll just wait for someone to do it correctly
Click to expand...
Click to collapse
Hi, after unlocking bootloader, you are not able to update/flash supersu.zip from stock recovery? right?
if it so, then we need to wait for custom recovery to flash root.
Thanks.
Knockys said:
Well I thought that TWRP was for all devices and I already went to the stock one before installing TWRP without success to flash SuperSU.
But apprently, installing TWRP the way I did wasn't the right way because I still boot to the stock recovery :/
Click to expand...
Click to collapse
No, TWRP is definitely not for every device. You have to use the version made for your specific device.
CafeKampuchia said:
No, TWRP is definitely not for every device. You have to use the version made for your specific device.
Click to expand...
Click to collapse
My bad then ahah
mjose said:
Hi, after unlocking bootloader, you are not able to update/flash supersu.zip from stock recovery? right?
if it so, then we need to wait for custom recovery to flash root.
Thanks.
Click to expand...
Click to collapse
Yes it fails on stock recovery, we'll have to wait for a custom one indeed...
Hi, finally its available in oneplus forum
https://forums.oneplus.net/threads/...om-recovery-root-take-efs-backup-more.401713/
Thanks.
mjose said:
Hi, finally its available in oneplus forum
https://forums.oneplus.net/threads/...om-recovery-root-take-efs-backup-more.401713/
Thanks.
Click to expand...
Click to collapse
THIS WORKS! But beware using the recovery imagine provided there as in is in Mandarin, not English. Other than that it works fine! Already rooted
Savya said:
THIS WORKS! But beware using the recovery imagine provided there as in is in Mandarin, not English. Other than that it works fine! Already rooted
Click to expand...
Click to collapse
Hey i need your help, i installed the custom recovery in Mandarin but i don't understand anything! Could you please tell me where i should go in this recovery to wipe dalvik cache and flash super su? Step by step? Thanks!
Works for me too ! I'll try to install Xposed now ahah !
Hope they'll release TWRP in English soon !
EDIT : Xposed installed and working ! For those who don't know how to do, see here
mjose said:
Hi, finally its available in oneplus forum
https://forums.oneplus.net/threads/...om-recovery-root-take-efs-backup-more.401713/
Thanks.
Click to expand...
Click to collapse
I'll update the OP, but I won't make it a noob friendly guide until we have an English TWRP from a known/trusted developer.
Edit: I tried thanking your post, but I'm out of thanks for the day--8 post limit
CafeKampuchia said:
I'll update the OP, but I won't make it a noob friendly guide until we have an English TWRP from a known/trusted developer.
Edit: I tried thanking your post, but I'm out of thanks for the day--8 post limit
Click to expand...
Click to collapse
I've requested the OP for an English version and hopefully he'll post a link soon.
And that's okay you can thank me later xD
Savya said:
I've requested the OP for an English version and hopefully he'll post a link soon.
And that's okay you can thank me later xD
Click to expand...
Click to collapse
I have english version repacked from original source
https://www.dropbox.com/s/zypo7b41lvj0r2h/en-recovery-twrp-onyx-.img?dl=0
ukanth said:
I have english version repacked from original source
https://www.dropbox.com/s/zypo7b41lvj0r2h/en-recovery-twrp-onyx-.img?dl=0
Click to expand...
Click to collapse
Just flashed it now!
Confirmed that its working and its in English!
Thanks a ton mate!
Also do i have your permission to post your link in the oneplus forums? As there are many users there too waiting for an english version.
@ukanth : shared the recovery on my post on the OP forums
https://forums.oneplus.net/threads/...om-recovery-root-take-efs-backup-more.401713/
How to Unlock bootloader + flash twrp recovery + root and install SuperSu in Xiaomi Redmi Note 3 (Snapdragon) without waiting for permission on the Latest MIUI 8 - V8.0.6.0.LHOMIDG. (as of 22-11-16)
Here you have the step by step procedures to successfully unlock your Redmi Note 3 SnapDragon global variant with latest global stable rom MIUI 8. Please follow the steps carefully.
The rom used for this procedure is the latest global stable fastboot rom MIUI V8.0.6.0.LHOMIDG.
This is the working guide for the Xiaomi redmi note 3 (SD) on latest MIUI 8.0.6.0 as on 22-11-2016. I did lots of experiments, bricked my device several times to find this working guide for latest rom, however you are free to link to this page for reference.
You dont need to apply for official unlocking and wait for a month or more to get the sms confirmation from xiaomi to officially unlock the bootloader, the problem with the official method is many users have reported that they did not receive the confirmation sms from xiaomi, even if they receive the confirmation sms the unlocking process stucks at some percentage and fails to unlock the bootloader. So for everyone here is the easy way to Unlock bootloader + flash twrp recovery + root and install SuperSu in Xiaomi Redmi Note 3 (Snapdragon) without waiting for permission.
First of all take a backup of all important files from your phone to your PC before starting. Because all data will be formatted while flashing the rom.
I have simplified most of the procedures and complicated works for this guide. A good part of the credit goes to some other developers because their works were helpful to me for experimenting to find this working full unlocking guide for the latest miui rom for redmi note 3 (SD) as of 22-11-2016.
REQUIREMENTS:
Xiaomi Redmi Note 3 (SD) Mobile
Micro USB data cable (or) compatible usb cable
Desktop or Laptop (Widows based)
Download all the tools, rom and other files from this androidfilehost folder link and keep all files in one folder for easy access:
https://www.androidfilehost.com/?w=files&flid=137618Files List:
1. AnF.zip
2. fastboot_edl.zip
3. Fastboot Rom: "kenzo_global_images_V8.0.6.0.LHOMIDG PreRooted by SUBI.tgz"
4. MiFLash_v2016.08.30.0.zip
5. minimal_adb_fastboot_v1.4_setup _working.exe
6. MiPcSuiteSetup_v3.2.1.3111_2717.exe
7. Root Checker Basic v5.9.7.apk
8. SR1-SuperSU-v2.78-SR1-20160915123031.zip
9. twrp-3.0.2-2-kenzo for Redmi Note 3 _SD.zip
10. ADBdriversetup.zip (alternate use, in case device specific drivers are not properly installed)
***Carefully remove your sim card & sd card from mobile (if inserted) before you begin and do not connect to internet until all steps are completed, because the phone would automatically sync with Xiaomi servers at first boot and may cause problems.
Make sure your phone is charged 60% and above.
The complete video go through of step by step procedures in this guide is available in this YouTube video,
https://www.youtube.com/watch?v=rj4gVMk3y0o
FOLLOW THE STEPS CAREFULLY, IF YOU FACE ANY TROUBLE, START OVER AGAIN FROM STEP 1, IF YOU FACE ANY OTHER ERROR OR BOOTLOOP OR STUCK IN LOGO LOOK AT THE TROUBLE SHOOT SECTION AT THE BOTTOM.
Step 1:
Enable Usb Debugging, if not done before:
Open Settings in your device"Redmi note 3 (SD)", scroll to bottom in settings and click on "About phone" and now tap on MIUI version 7 times, it will show a message like "You are now a developer" and Developer options will be revealed.
Next go back to Settings main screen and then -> Additional settings -> Developer options -> Enable Developer options, Enable OEM Unlock, Usb Debugging.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Note: After that when you connect your phone to the Pc to execute adb commands, a prompt may appear on your phone with computer's fingerprint key, you should confirm it when it appears. In case if you already done this for your computer with proper adb drivers installed, you don't need to bother about this.
Step 2:
DISABLE DRIVER SIGNATURE ENFORCEMENT IN YOUR PC:
You now have to disable driver signature enforcement in your PC, to do this you have to open the settings window by pressing the shortcuts"Windows button + i -> Update & Security -> Recovery -> Advanced startup -> Restart now. Now the system will logout and show Recovery options, from there select Troubleshoot -> Startup Settings in Advanced options -> Restart. Your system will now reboot and show the "Startup settings" screen, a list of options will be available, you have to choose option number 7 to disable driver signature enforcement. Then the system will boot into the OS with driver signature enforcement disabled. After that do not restart your pc until all the below steps are completed, in case if you restart your pc for any reason you need to redo this step again because system reboot might enable driver signature enforcement again. That's it. Refer this video if you need further guidance.
Step 3:
To install ADB, Fastboot and other drivers in your PC:
Install the " minimal_adb_fastboot_v1.4_setup _working " file downloaded from the link I provided above. If any security prompts appear on your screen, allow all prompts.
Install the " MiPcSuiteSetup_v3.2.1.3111_2717.exe " file downloaded from the link I provided above. If any security prompts appear on your screen, allow all prompts.
Install the " MiFLash_v2016.08.30.0.zip " file downloaded from the link I provided above. If any security prompts appear on your screen, allow all prompts.
Step 4:
Extract AnF.zip file and execute the commands:
Now extract the "AnF.zip" file downloaded from the link I provided above. Connect your phone to Pc using the Usb cable. Open the extracted AnF folder and double click on the cmd.exe file, which will open a adb command window from there.
Execute the below command through adb command window to check and confirm the phone is connected via adb interface. If connected properly it should show device serial like "******** device"
adb devices
Incase if your phone shows a prompt for computer's fingerprint key approval, allow it. Then execute the command again. You should see your phone serial number as shown in the image below, which means your phone is properly connected via adb. Incase if the device is not connect properly via adb, disable and enable USB debugging on your phone. If that also helping to install the phone's adb drivers, extract and run the"ADBdriversetup.zip" downloaded from the link I provided above to install the specific drivers for your phone.
Step 5:
Reboot the phone to EDL mode:
Now you have to reboot your phone to edl mode aka Emergency download mode. To do this execute the below command via adb window with phone still connected to Pc.
adb reboot edl
Your phone will now reboot into blank screen or edl mode and new driver named "qshusb qloader 9008" will be installed in your Pc, now only red led notification light will be blinking on your phone. Once the driver is installed properly, the phone is now connected in edl mode. Now close the adb command window.
Step 6:
Setup MiFlash Tool & Flash the ROM:
Open the MiFlash tool (MiFLash_v2016.08.30.0.zip) application you installed earlier, click refresh button and your phone will be visible as port number (ex: COM10) in MiFlash tool. Exe file is in this path,"C:\Xiaomi\XiaoMiFlash"
Now extract the "kenzo_global_images_V8.0.6.0.LHOMIDG PreRooted by SUBI.tgz" fastboot rom file downloaded from the link I provided above. In your MiFlash tool window, click the Browse button and locate the extracted fastboot rom folder. Then select "clean all" button at the bottom of MiFlash window. The flash tool is now configured. Now click the Flash button.
Wait for few minutes for the flashing process to complete, once the process is complete and MiFlash tool window will show task finished. But do not disconnect the phone.
Step 7:
Reboot to Fastboot mode & execute Fastboot commands:
Now while the phone is still connected to your pc, reboot your phone to fastboot mode by pressing Volume down button and Power button simultaneously until you see the boot screen and release, the phone will now enter into fastboot mode.
Now double click and open the cmd.exe file from AnF folder you extracted earlier to open the command window. Then execute the below command.
fastboot oem device-info
This command will show you the current bootloader status. The bootloader status shows "Device Unlocked: False", execute the below command in command widow, it will Unlock the bootloader.
fastboot oem unlock-go
Your device might restart now, if restarts press Volume down button and Power button simultaneously to reboot phone to fastboot mode again to check your bootloader status again by executing the below command. It should show "Device Unlocked: True" in the command window. Which means the device's bootloader is unlocked.
fastboot oem device-info
Now to flash TWRP recovery and Supersu for root permissions, jump to step 8, or if your aim is to unlock the bootloader only, you may restart your phone and skip all below steps.
Step 8:
Flash TWRP:
Now restart phone to fastboot mode by pressing Volume down button and Power button simultaneously until you see the fastboot screen.
Extract the "twrp-3.0.2-2-kenzo for Redmi Note 3 _SD.zip" file downloaded from the link I provided above to the AnF folder.
Then open the AnF folder, double click and open the cmd.exe file, paste the below command in the command window to flash twrp recovery.
fastboot flash recovery twrp-3.0.2-2-kenzo.img
After flashing the recovery image reboot the phone to TWRP recovery by pressing Volume Up button and Power button simultaneously until you see the boot screen. It will boot the phone into TWRP recovery, on the front screen just swipe the slider to mount system as read only. That's it now to flash supersu proceed to step 9.
Step 9:
Flash SuperSu:
While the phone is in TWRP recovery connect the phone to Pc, it will be detected as mass storage device, just copy the "SR1-SuperSU-v2.78-SR1-20160915123031.zip" file downloaded from the link I provided above to your phone's mass storage device.
On the twrp menu click on Install option and locate the "SR1-SuperSU-v2.78-SR1-20160915123031.zip" to install via twrp, now swipe the slider to right to install supersu to have root access in your phone's OS and then wipe dalvik cache using the button below in twrp.
If twrp shows any read/write error while flashing supersu, on the twrp mainscreen choose mount option and click on system in the next menu, then go back to main screen and try again to install.
That's it, now supersu is installed, to check the root status follow to step 10.
Step 10:
Check root status:
After completing all the steps successfully, reboot the phone into the system normally and complete the initial setup without Sim card, the first boot may take a little more time to boot into OS, In case if the phone stuck in boot screen for very long(10+ mins), go to troubleshoot section at the bottom and start over the steps. Otherwise you are good to go.
Connect device to Pc after initial setup completes, now copy the "Root Checker.apk" file to your phone and install it, open the root checker app and click on verify root, you will be prompted by Supersu for root permission, allow it, your root access will be verified. Voila, you have successfully rooted, flashed twrp and installed supersu on your Redmi Note 3 with latest rom installed.
That's it. Now you are ready to rock.
KNOWN ISSUES:
No issues found so far, in case if you find any issues after successfully unlocking using the above method, kindly let me know.
After successfully unlocking your bootloader, incase if you update your rom via official updates, your will lose root access and twrp custom recovery and may end up with locked bootloader again, if you face this situation by some reason, you may start over and follow this guide from step 1 to revert back to unlocked bootloader. Do not update the rom and turn off automatic updates in settings as a precautionary measure.
Troubleshoot:
If your device gets bricked or Stuck in Boot logo, try this,
Reboot your phone into edl mode by following below step.
If you are stuck on bootscreen, you may not be able to enter into edl mode using the normal method above because of bootloop or Stuck in Boot logo, in that case try this method to enter into edl mode from fastboot, download "fastboot_edl.zip" file from the link I provided above, extract the zip file and open the extracted folder, connect the phone to your Pc in fastboot mode(vol down + power), double click and run this file "edl.cmd", the phone will automatically enter into edl mode if the phone's drivers and adb drivers are installed properly.Now follow step 6 and follow on from this step.
If QHUSB_BULK drivers are not properly installed while the phone in edl mode,
If QHUSB_BULK drivers are not installed while the phone in edl mode, your device may not be visible in MiFlash tool(ex:COM10) even after you click refresh button, in this case open the device manager in your Pc, the phone will be visible as QHUSB_BULK with some alert sign, right click on it and select Update driver software. Then click browse my computer and browse to the location of the driver files in path "C:\Program Files\Xiaomi\MiPhone\Qualcomm\Driver" and proceed and when prompted to Install this Driver Software anyway, allow it and complete the driver installation. Now open MiFash tool and click refresh button your device will be detected in MiFash tool, now you can flash the fastboot rom by following the steps above.
Does this work for Kate version also? OP doesn't specify
Will I lose my warranty by using this method of bootloader unlock?
This method still works for Global Snapdragon phone. Finally got it last night after 2 days of torture (I didn't sleep).
The important part is firstly the image with the modified file you are going to flash to the phone. Here he is using v8.0.6.0 which is the newest (and now last) update for android 5.1 (which is needed, phone will not flash 6.0 without a proper Cache and data clear). I ended up using version 7.3.2.0 which is 1 patch before the version my phone came with (7.3.7.0). Then I replaced emmc_appsboot.mbn with the one from here then flashed the file in EDL mode.
After the flash is done is just as important I found. You place it in fastboot mode (power button + vol down) and run a script. I wasn't able to manually unlock the device via cmd line 'fastboot oem unlock-go'. Instead I found a script that worked from here called 'Root_Folder' (this site also has majority of the files needed). You use the script called 'Root' in the folder to finish the unlock. Notice there is a 'recovery.img' in the folder as well, I replaced it with ZCX TWRP.
Now run through the script after the flash in fastboot mode. Follow the instructions from script, sometimes you take cable out or force phone back into fastboot mode. The key goal here is to have the script boot into TWRP in the end. If this happens you can do all that's needed now.
Another thing I noticed was you have to give debug permission to computer your using and save permission. Debug mode/oem unlock - connect cable, on phone you should get a prompt to accept PC and save permission. If you don't get this prompt make sure you have ADB and Fastboot installed.
Important steps are:
1. Phone connect to computer via debug/oem mode.
2. Flash correct modified ROM with MiFlash in EDL mode.
3. Once flash is done hold power and volume down button for fastboot mode.
4. Run script to attempt to unlock bootloader and/or install TWRP.
MikeyLee said:
Does this work for Kate version also? OP doesn't specify
Click to expand...
Click to collapse
You would have to look it up for Kate specifically. If anything at all that changes it's the Image you use to flash the phone.
zeon321 said:
Will I lose my warranty by using this method of bootloader unlock?
Click to expand...
Click to collapse
Don't think so. You don't 'officially unlock it' and you can flash a stock image that relocks the phone automatically.
Thank you works 100% !!!! :laugh:
After booting to TWRP it's asking me for a decrypt password and I cannot mount any partitions. Then I tried rebooting but phone is stuck on MI logo.
zeon321 said:
After booting to TWRP it's asking me for a decrypt password and I cannot mount any partitions. Then I tried rebooting but phone is stuck on MI logo.
Click to expand...
Click to collapse
Can you boot back into TWRP? If not you'll have to reinstall from EDL mode and try to unlock bootloader again.
A decrypt password to access any of the internal storage? Did you have a password with last install of MIUI? Also boot into fastboot and see if your bootloader is unlocked with 'fastboot oem device-info'. If your bootloader is unlocked, you might have to reformat data files on phone, which will wipe system completely and remove encryption.
Oh you probably also need to put a SD card into the device to use to flash from, if your flashing a new ROM. You have to wipe main system with advance wipe, wipe everything but internal storage and micro sdcard (in TWRP).
Narcle said:
Can you boot back into TWRP? If not you'll have to reinstall from EDL mode and try to unlock bootloader again.
A decrypt password to access any of the internal storage? Did you have a password with last install of MIUI? Also boot into fastboot and see if your bootloader is unlocked with 'fastboot oem device-info'. If your bootloader is unlocked, you might have to reformat data files on phone, which will wipe system completely and remove encryption.
Oh you probably also need to put a SD card into the device to use to flash from, if your flashing a new ROM. You have to wipe main system with advance wipe, wipe everything but internal storage and micro sdcard (in TWRP).
Click to expand...
Click to collapse
Thanks, I flashed old version of twrp and formatted the storage. Now phone is working fine.
Can i use this tuto on a Redmi note 4 MTK?
Great job !!! I have redmi note 3 pro kenzo with 3 gb ram and 32 gb internal .... so can i use the same guide and files or the files are different !!! confused
hoping for the reply soon ... thanks !!
Great job !!! I have redmi note 3 pro kenzo with 3 gb ram and 32 gb internal .... so can i use the same guide and files or the files are different !!! confused
hoping for the reply soon ... thanks !! @Sci Subi
Yes Praw Zoll, you can use this method for your device, I have tested this method working on Redmi Note 3 pro or Kenzo or Snapdragon variant.
You can also refer this miui thread for this same method with images and video, en.miui(dot)com/thread-461694-1-1.html
W7nstroll said:
Can i use this tuto on a Redmi note 4 MTK?
Click to expand...
Click to collapse
This method is for Redmi Note 3 pro, (Kenzo) variant.
can i use it for global stable 8.2.3 ??
The heart of this - the unofficial bootloader unlock - are taken from: http://en.miui.com/thread-345728-1-1.html (It's generally polite to link your sources).
This _does_ work on `kate`. However, this is using a modified 'emmc_appsboot.mbn'. If you flash an original emmc_appsboot.mbn, you may well find your bootloader no longer unlocked and you needing to reflash your device back to stock.
Also, for those wanting to use it on kate (because Xiaomi seems singularly incompetent when it comes to supporting the official bootloader unlock for that devcie): your device will identify itself as a kenzo, so you may have trouble flashing things like the 'miuifirmware_x.zip' updates for kate. Also, those 'miuifirmware_x.zip' files often include the emmc_appsboot.mbn, so be careful.
On another note, if anyone has an actual infallible method to get an official bootloader unlock for the kate device, please let me know.
Can I use this method for 2GB / 16 GB version of Redmi Note 3 Pro (Snapdragon)?
Thanks
Works Thanks
Tested On 18/05/17
This method works But You are stuck on a older rom with no OTA/Later Updates. Method Does not work with MM Roms.(Maybe with different emmc_appsboot.mbn it would work.
Some Pointers
I was on MIUI8 before using this.
1. This downgrades your ROM from the latest ROM, therefore Points to follow.
2. Use This Method Instead Works with latest firmware as on date.
Works, Simply Nicely Perfectly Done, Just follow the steps things will never goes wrong. :highfive:
Sci Subi said:
Yes Praw Zoll, you can use this method for your device, I have tested this method working on Redmi Note 3 pro or Kenzo or Snapdragon variant.
You can also refer this miui thread for this same method with images and video, en.miui(dot)com/thread-461694-1-1.html
Click to expand...
Click to collapse
hi my phone was on miui 8 marshmallow i used the above method nd flashed the rom ( rom is 5.1.1) which is given after that unlocked bootloader nd installed twrp also but now i downloaded a new rom nd i want to flash it i placed the rom in micro sd card nd wiped everything in phone nd flashed the rom with gapps now phone boots but its stuck at the boot logo of the rom i also tried many other roms of 7.1.1 but same is happening phone is not going ahead its stuck in the rom boot logo what should i do also when i flashed that given rom when i charge the phone the red light blinks which seems like edl light help me out of this !! thanks in advance !!
You have flashed a recovery rom and that's why you are in bootloop.
Try to flash in EDL mode a fastboot rom.
PS: Hope you haven't tried to downgrade already because you can loose IMEI and baseband.
Onn Surf 7 (1st Gen)
Model No. 100005206
7" WiFi Android Tablet
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Bootloader Unlocking
And Rooting GuideOVERVIEW:The 1st Gen Surf 7 is a low-end budget tablet manufactured by the Walmart-owned electronics brand Onn (stylized onn.). Under the hood is the MediaTek MT8167B, a battery efficient quad-core Cortex-A35 chipset with a max clock speed of 1.3 GHz, paired with 1 GB RAM and 16 GB of internal storage (12.2 GB useable). The tablet ships with Android 9 Pie Go Edition, compiled using the armv7l (32-bit) architecture.
This guide outlines instructions for unlocking the bootloader and rooting the 1st Gen Onn Surf 7. IMPORTANT NOTE: THIS GUIDE IS FOR MODEL NUMBER 100005206 ONLY.
The method for rooting this device is the Magisk systemless root solution. The most common procedure for rooting with Magisk involves boot image patching support. During this process, the boot-ramdisk is patched to configure the boot image for systemless root. On this model tablet, the stock boot image is devoid of a ramdisk (boot-ramdisk), so the only alternative to achieving root is to use the ramdisk from the stock recovery image and systematically install Magisk on the /recovery partition. In essence, this configuration allows Magisk to hijack the /recovery partition to attain root access to the Android OS. The caveat is, anytime you reboot your tablet, in order to have root privileges, you will need to manually boot to recovery mode by way of using the hardware key combo. But, more on that later. In the meantime, and before we begin, if you would like to read a more detailed synopsis on running Magisk in recovery, see the official Magisk installation docs at GitHub here
Official GitHub Magisk DocsREQUIREMENTS:1. Onn Surf 7 (Model No 100005206 ONLY);2. A Windows PC or laptop with the ADB & Fastboot tools installed. For purposes of this guide, keeping simplicity in mind, I would recommend using the Minimal ADB & Fastboot tools. I have provided a link in the downloads section below for this utility. If you do not already have ADB & fastboot installed on your computer, go ahead and download the program from the link below and install it. For better ease of access, once installation is complete, open your C drive, open the Program Files (x86) folder, and locate the Minimal ADB & Fastboot folder. Copy it and paste it to your desktop. NOTE: this guide can be performed using Windows, Linux or Mac. This particular guide, however, focuses on a Windows-based setup;3. A quality USB to micro USB data syncing/charging cable;4. An internet connection to download the files I have linked below;
DISCLAIMER:
Unlocking the bootloader and rooting an Android-based mobile device are tasks that both carry inherent risks. By proceeding further, you are assuming full responsibility for the integrity and operability of your device. In effect, this serves to absolve me of any liability in the event you corrupt your tablet or otherwise render it inoperable. I have thoroughly tested these instructions and have the utmost confidence that things will go smoothly as long as you follow this guide carefully. In the unfortunate event things go south, we are dealing with a MediaTek-based tablet, which are known to be quite impervious to hard bricking. Remain calm, stop everything you're doing, and write a complete summary below in comments of every step you took and precisely what went wrong. Feel free to include photos or screenshots, and don't be bashful with details. Because this is a noob-friendly thread, I will provide all support possible to get you back in running order.
Moreover, it should be emphasized here that unlocking the bootloader of your Onn Surf 7 will trigger a native security protocol which forces the device into a factory data reset during the initial boot sequence following the unlocking process. Before proceeding further, create a full backup of any saved data, apps, app data, photos, media, videos or any other files you wish to keep. Again, all userdata will be erased following the bootloader unlocking procedure.
INSTRUCTIONS: I. UNLOCKING THE BOOTLOADER
This section assumes that you have installed the Minimal ADB & Fastboot tools on your Windows computer, and that your device is charged to a minimum of 60%.
In the Developer Options menu, enable USB Debugging & OEM Unlocking. To enable the Developer Options menu, go to device Settings>About tablet and tap Build number 7 times. You will see a toast informing you that Developer Options have been enabled, which will be located in Settings>System;
Boot your tablet into fastboot mode. From the Android OS, you can connect the tablet to your PC or laptop with a suitable micro USB to USB-A data sync/charging cable. Keep an eye on your tablet display for a USB Debugging authorization prompt, which needs to be granted. Open the Minimal ADB & Fastboot folder on your desktop and double click the file named cmd-here. This will open a command window, in which this command should be executed
Code:
adb devices
If properly connected, the command window will return with an alphanumeric string followed by the word device. Next, execute the command
Code:
adb reboot bootloader
Your tablet should now boot to fastboot mode, which will be indicated by a black backlit display with FASTBOOT mode displayed in white text at the bottom of the display;
In the command window, execute the command
Code:
fastboot devices
Just as before, if you are properly connected, the command window will display your device's serial number followed by the word fastboot;
Now execute
Code:
fastboot flashing unlock
On your table display you will be prompted to press the Volume Up key to initiate the bootloader unlock. Once you have done so, and the unlock is complete, use this command to reboot your tablet:
Code:
fastboot reboot
II. ROOTING THE DEVICE
Now that the bootloader is unlocked, we will not be using TWRP or any other custom recovery to achieve root. As mentioned previously, this root method involves running Magisk in recovery. Using this configuration, it is not even possible to install Magisk using a custom recovery. Once the recovery image has been patched using the image patching feature of the Magisk app, fastboot mode must then be used to install the patched image. I have alleviated all the leg work of Magisk image patching by creating a pre-patched recovery image configured for Magisk systemless root. To root your tablet, you need only to flash the patched recovery image I have provided below.
Boot your tablet into fastboot mode. With the device powered off, hold the Power and Volume Up buttons for several seconds, until a boot mode menu appears on your tablet display. Use Volume Up to navigate to Fastboot Mode and then press Volume Down to select it.;
Connect your tablet to your computer by using a good quality USB to micro USB charge/sync cable;
Download the Magisk patched recovery image from the DOWNLOADS heading below. Save it in the ADB/Fastboot directory on your computer;
Open a command window on your computer in the path of your ADB/Fastboot directory. Ensure proper syncing by executing the fastboot devices command.
Once proper syncing is established, execute the following command:
Code:
fastboot flash recovery patched_recovery.img
Your Onn Surf 7 is now configured for root access. Now the fun part -- booting a rooted Android OS via recovery mode. As referenced previously, due to there being no boot-ramdisk, Magisk must be installed to the /recovery partition. Therefore, anytime you reboot the device, in order to enable root access, it will be necessary to manually boot to recovery. Because Magisk has effectively hijacked the /recovery partition, booting to recovery actually boots the Android OS with Magisk systemless root enabled. If you select the normal boot option, Android will boot up, but without root enabled.So at this time, hold the Power button until the tablet shuts down from fastboot mode and powers off. Once off, hold the Power and Volume Up keys together until the boot mode menu appears. Using Volume Up, navigate to Recovery Mode, then press Volume Down to select the option and initiate boot up. Once booted into the Android OS, if you do not see the Magisk app installed, or its
placeholder shortcut, go ahead and install the latest Magisk APK file from the official GitHub repo. I have added a link below. Open Magisk and allow any additional setup that may be pending. And that's it. Good luck and enjoy.
DOWNLOADS:
Magisk Patched Recovery Image
Minimal ADB & Fastboot v1.4.3
Official Magisk Release Repo
9.0-PPR1.180610.011 Firmware
Where is the whole stock rom?
It's available on numerous repos and websites. Here's a direct link. This is build number PPR1.180610.011 release keys_20191023-1452 / Android.9.Pie Go Edition
680.62 MB file on MEGA
mega.nz
Viva La Android said:
It's available on numerous repos and websites. Here's a direct link. This is build number PPR1.180610.011 release keys_20191023-1452 / Android.9.Pie Go Edition
680.62 MB file on MEGA
mega.nz
Click to expand...
Click to collapse
does it work for the
100026191bc Im looking for that one
I have the 100026191 and Im looking for that one
[email protected] said:
does it work for the
100026191
bc Im looking for that one
Click to expand...
Click to collapse
No. This works only for the 100005206 model. I'll try to find the firmware you need.
It failed and bricked for the sp bc it wasn't for the 100026191 I needed the one with Android 11 Go
Viva La Android said:
No. This works only for the 100005206 model. I'll try to find the firmware you need.
Click to expand...
Click to collapse
Ok thank you
Viva La Android said:
No. This works only for the 100005206 model. I'll try to find the firmware
Click to expand...
Click to collapse
@Jfuchs2007 head over to this XDA thread. There are members there that have the Onn Surf 7 (2nd Gen) like yours with Android 11 Go Edition. The firmware you need may be available there. If not, post a reply in the thread and request it. https://forum.xda-developers.com/t/...ts-android-11-versions-of-surf-gen-2.4321555/
Viva La Android said:
No. This works only for the 100005206 model. I'll try to find the firmware you need.
Click to expand...
Click to collapse
Ok thank you
Viva La Android said:
@Jfuchs2007 head over to this XDA thread. There are members there that have the Onn Surf 7 (2nd Gen) like yours with Android 11 Go Edition. The firmware you need may be available there. If not, post a reply in the thread and request it. https://forum.xda-developers.com/t/...ts-android-11-versions-of-surf-gen-2.4321555/
Click to expand...
Click to collapse
I did and he did not reply in like a day
[email protected] said:
Ok thank you
I did and he did not reply in like a day
Click to expand...
Click to collapse
This 2nd Gen firmware appears difficult to locate on the mainstream sites and repos. I'll do an in-depth search and I'll also reach out to some people that may have info on a source.
Update: @[email protected], I have located firmware for your tablet on two different platforms. Unfortunately, these are predatory platforms that charge a fee for firmware to which they own no rights. Charging money for firmware is highly akin to somebody charging money for rain water. Just as the person doesn't own the water they are selling, these pay-based firmware repos do not own the firmware that they host. Anyway I am ranting. I'm fairly certain that if Dante were around today, he would designate a level in purgatory to the purveyors of such business practices.
While I don't support or condone pay-based firmware services, I will get you the links if you don't already have them. I am still searching for a free download..
Viva La Android said:
This 2nd Gen firmware appears difficult to locate on the mainstream sites and repos. I'll do an in-depth search and I'll also reach out to some people that may have info on a source.
Update: @[email protected], I have located firmware for your tablet on two different platforms. Unfortunately, these are predatory platforms that charge a fee for firmware to which they own no rights. Charging money for firmware is highly akin to somebody charging money for rain water. Just as the person doesn't own the water they are selling, these pay-based firmware repos do not own the firmware that they host. Anyway I am ranting. I'm fairly certain that if Dante were around today, he would designate a level in purgatory to the purveyors of such business practices.
While I don't support or condone pay-based firmware services, I will get you the links if you don't already have them. I am still searching for a free download..
Click to expand...
Click to collapse
I dont have it yet
[email protected] said:
I dont have it yet
Click to expand...
Click to collapse
My search has yielded no positive results for free firmware. The firmware appears to be available only on pay-to-download firmware hosting sites.
First off, thank you for this, but I can't quite follow these instructions. Boot into fastboot mode but put Magisk on the tablet first?
It's been a while using fastboot commands for me.
I downloaded everything but just can't remember how to put together the fastboot stuff.
USB debugging IS enabled on the tablet and It does go into Fastboot mode from the menu & volume commands.
Thanks in advance for any help!
djphooka said:
First off, thank you for this, but I can't quite follow these instructions. Boot into fastboot mode but put Magisk on the tablet first?
It's been a while using fastboot commands for me.
I downloaded everything but just can't remember how to put together the fastboot stuff.
USB debugging IS enabled on the tablet and It does go into Fastboot mode from the menu & volume commands.
Thanks in advance for any help!
Click to expand...
Click to collapse
First things first, you need to install the Minimal ADB & Fastboot tools on your Windows computer. After installing it, open your C drive and double click on Program Files (x86). Inside you should find the Minimal ADB & Fastboot folder. Copy that folder and paste it to your desktop. Next follow my instructions above. In Step 3, when you download the patched recovery image, save it in the Minimal ADB & Fastboot folder on your desktop. In Step 4, to open a command window, open your Minimal ADB & Fastboot folder and double click the file that contains CMD. Now you'll be able to execute the command to flash the patched recovery image. Once you flash it, Magisk will be on your tablet. But follow my instructions for booting up after you flash it. It's a bit tricky, but not bad once you get accustomed to booting recovery mode from a powered off state.
Let me know how it goes, and if you get stuck or have any more questions, just let me know. I'll be on XDA pretty much all night to catch up on some work.
Viva La Android said:
First things first, you need to install the Minimal ADB & Fastboot tools on your Windows computer. After installing it, open your C drive and double click on Program Files (x86). Inside you should find the Minimal ADB & Fastboot folder. Copy that folder and paste it to your desktop. Next follow my instructions above. In Step 3, when you download the patched recovery image, save it in the Minimal ADB & Fastboot folder on your desktop. In Step 4, to open a command window, open your Minimal ADB & Fastboot folder and double click the file that contains CMD. Now you'll be able to execute the command to flash the patched recovery image. Once you flash it, Magisk will be on your tablet. But follow my instructions for booting up after you flash it. It's a bit tricky, but not bad once you get accustomed to booting recovery mode from a powered off state.
Let me know how it goes, and if you get stuck or have any more questions, just let me know. I'll be on XDA pretty much all night to catch up on some work.
Click to expand...
Click to collapse
I've installed all ADB & fastboot. It doesn't find the device. Isn't there a way to list devices?
It is on the menu that says -> FASTBOOT mode..
Just stays "waiting for any device" in command window.
Also, What do the platform tools have to do with it?
Ugh. OK. I don't think my bootloader is unlocked so how do I do that? I've done it with a few phones in the past.
It IS going into fastboot mode and even recovery to where I can factory reset & such.
Thanks again for the help!
Okay, so to unlock your bootloader, you'll need the Minimal ADB & Fastboot tools also. Install it and put the folder onto your desktop like I outlined in my last post. Unlocking your bootloader will fully.wipe your tablet, so make a backup first.
On your tablet, be sure you have enabled the USB Debugging and OEM Unlocking toggles in the Developer Options menu. To access Developer Options, open your device Settings app, scroll down to System>About tablet and tap on Build number 7 times. The menu can then be found under Settings>System>Developer options.
Next, boot your tablet into fastboot mode by first powering your device off, then press the power and volume up buttons simultaneously for several seconds, until a Boot Mode menu appears on your screen. Use the volume up key to navigate to Fastboot Mode, then volume down to select it. Connect the tablet to your PC using a suitable data sync/charging cable. Open your Minimal ADB & Fastboot folder and double click the file named cmd-here. A command window will open. To make sure you're properly connected and that the drivers are configured correctly, execute this command:
Code:
fastboot devices
You should see your serial number return in the command window, followed by the word fastboot. Now execute this command:
Code:
fastboot flashing unlock
On your tablet display, you will be prompted to press the Volume Up key to proceed with unlocking. Once you do that, execute this command.
Code:
fastboot reboot
This will reboot your tablet.However, as mentioned earlier, the tablet will first initiate a factory data reset, and then boot into the Android setup sequence.
Your post enlightened me to the fact that I probably need to add a bootloader unlocking section to the guide. I will be doing that sometime today, so keep me posted on your progress.
Viva La Android said:
Boot your tablet into fastboot mode. From the Android OS, you can connect the tablet to your PC or laptop with a suitable micro USB to USB-A data sync/charging cable. Keep an eye on your tablet display for a USB Debugging authorization prompt, which needs to be granted. Open the Minimal ADB & Fastboot folder on your desktop and double click the file named cmd-here. This will open a command window, in which this command should be executed
Click to expand...
Click to collapse
This never pops up and I think is the issue.
I've tried on my desktop and laptop and the tablet isn't recognized in fastboot cmd under attached devices. It is definitely in FASTBOOT mode... I've booted into regular and recovery mode to see if any other drivers install.
hmm