Database Users

[GUIDE] Unlock/Root/Flash for OnePlus One

[SIZE=+3]Heisenberg's How-To Guide For Beginners[/SIZE]
[SIZE=+2]OnePlus One[/SIZE]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[SIZE=+1]See Also:
[INDEX] OnePlus One
[FAQ] OnePlus One Frequently Asked Questions[/size]
[SIZE=+1]Intro[/SIZE]
This thread will serve as a location for basic how-to guides for the OnePlus One (Bacon). I'm going to start off with a couple of the more obvious ones and go from there. If anyone has any suggestions for additions please feel free to let me know.
[size=+1]Prerequisites[/size]:
You'll need a working adb/fastboot environment on your PC to get through some of these guides. Go here to download the Android SDK, which will give you most updated version of adb and fastboot. Scroll to the bottom of the page and find Other Download Options>SDK Tools Only, and grab the right version for your OS. While it's downloading create a folder in C:\ called SDK (C:\SDK). Once you've downloaded the zip you can extract it into your C:\SDK folder. Navigate to C:\SDK\android-sdk-windows and open SDK Manager.exe. In SDK Manager you need to install the following packages:
Tools> Android SDK Tools, Android SDK Platform-tools
Extras> Android Support Library
Once you have installed those, inside C:\SDK you should see some new folders, one of them will be called platform-tools, within that folder you should see fastboot.exe and adb.exe. I'll refer to this as your fastboot folder/directory or working folder/directory during this guide. To make sure adb is correctly installed, open a command prompt from within your fastboot folder (hold shift + right click, select open command prompt here) and issue this command:
Code:
adb version
If it returns a version number for Android Debug Bridge then you're good to go.
You'll find universal adb/fastboot drivers here, download it and follow the installer, then reboot your PC.
You can test adb by connecting your device to your PC while booted into Android (making sure that adb/usb debugging is enabled in Settings>Developer Options) with the screen unlocked and issuing this command:
Code:
adb devices
It should return your device serial number, if so, adb is working.
You can test fastboot by connecting your device to your PC while booted into fastboot mode (power + volume up) and issuing this command:
Code:
fastboot devices
It should return your device serial number, if so, fastboot is working.
By attempting any of the processes listed this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches on fire, or turns into a hipster and claims to have been modified before it was cool. Make sure you read a section and fully understand it before attempting it.
[SIZE=+1]Index[/SIZE]
How To Unlock Your Bootloader
How To Install A Custom Recovery On Your Device
How To Make A Nandroid Backup With TWRP Recovery
How To Root Your Stock Rom
How To Install A ROM with TWRP Recovery
How To Install A Custom Kernel With TWRP Recovery
How To Flash The Stock Kernel With Fastboot
How To Flash The Cyanogen OS Fastboot Images
How To Update Modem/Firmware When Switching From KitKat To Lollipop (and vice versa)
How To Make Sure You Can Pretty Much Always Recover From An Accidentally Wiped System
How To Backup & Restore Your EFS Partition
[SIZE=+1]1. How To Unlock Your Bootloader[/SIZE]
Power off your phone then boot into fastboot mode (power + volume up).
Connect your phone to your PC via usb cable.
Open a command prompt from within your fastboot folder (navigate to where you have fastboot.exe located on your PC, shift + right click anywhere within that folder, select open command prompt here).
Check your fastboot connection by issuing this command:
Code:
fastboot devices
It should return your device serial number, if not you need to make sure your drivers are installed correctly.​
Once you've confirmed your fastboot connection issue this command:
Code:
fastboot oem unlock
The device will now go through the automated unlocking process, just let it do its thing and it'll boot up into Android.​
Go back to fastboot mode and issue this command to ensure that it worked:
Code:
fastboot oem device-info
It should have a couple of lines there, both with the flag set to true.​
You can now reboot your phone using this command:
Code:
fastboot reboot
It's now safe to disconnect your usb cable.
Please note: this will erase all user data from your device, it is best to do this before you really start using the device and installing apps or putting data on the internal storage.
[SIZE=+1]2. How To Install A Custom Recovery On Your Device[/SIZE]
Prerequisites: unlocked bootloader.
You first need to go into Settings/Developer Options and uncheck the "Update recovery with system updates" option (to enable Developer Options go into Settings/About Phone and click 'build number' about seven or eight times).
Download the recovery of your choice (my preferred recovery is TWRP, and we'll be using that for this guide, grab it here).
Make sure you check the md5 to verify its integrity.
Place the file in your fastboot folder (this is where fastboot.exe is located on your PC).
Put the phone in fastboot mode and connect it to your PC via usb cable.
Open a command prompt from within your fastboot folder (shift + right click, select open command prompt here), and enter the following commands:
Code:
fastboot flash recovery openrecovery-twrp-2.8.1.0-bacon.img
(The recovery filename in the command will change depending on which recovery you're flashing)
Code:
fastboot format cache
Code:
fastboot reboot
Let the device reboot, it's now safe to disconnect your usb cable.
Now you can use the advanced power menu (or the power + volume down button combo) to enter your custom recovery.
Please note, if you have taken the stock Lollipop update please read the following:
For some reason CM12S doesn't respect the on/off toggle for the "update CM recovery" option in Developer Options, it just replaces whatever custom recovery you've flashed with the CM recovery regardless of whether that option is unelected.
Flash your custom recovery again, but after flashing don't do a normal reboot. After the flash has succeeded disconnect the usb cable, then power down the phone by holding the power button down, once it's powered off use the power + volume down button combo to boot directly into recovery. This first forced reboot into recovery somehow subverts what was keeping it from staying flashed and all subsequent normal reboots into recovery will boot into the custom recovery of your choice.
[SIZE=+1]3. How To Make A Nandroid Backup With TWRP Recovery[/SIZE]
Prerequisites: unlocked bootloader, TWRP recovery.
A nandroid backup is a very important thing to have before installing any custom software on your device. It's basically a backup of your stock system that you can fall back on if anything goes wrong or if you just want your stock ROM back. You can also use the backup tool to create a backup of your favourite ROM set up exactly the way you like it. The backup you create can be easily restored using the restore tool in TWRP recovery.
All you need to do is enter TWRP recovery, select the backup option from the TWRP home screen, check the system/data/boot boxes, and swipe to backup. The process will take a few minutes.
[SIZE=+1]4. How To Root Your Stock Rom[/SIZE]
Prerequisites: unlocked bootloader, TWRP recovery.
First you need to download SuperSU.
Enter TWRP recovery via the advanced power menu (or power + volume down).
Select the install option from the TWRP home screen.
Navigate to where you have SuperSU stored on your sd card and select it.
Swipe to install.
Once you've installed SuperSU you'll have an option to wipe cache/dalvik and an option to reboot system. Wipe the cache/dalvik, hit the back button, and hit the reboot system button. That's it.
[SIZE=+1]5. How To Install A ROM with TWRP Recovery[/SIZE]
Prerequisites: unlocked bootloader, TWRP recovery.
Installing a ROM is a pretty straight forward and easy process. Before you install anything you should make a nandroid backup (instructions above).
Download a ROM and appropriate Gapps package and place on your device.
Boot into your custom recovery.
Perform a full wipe.
Select the wipe option from the TWRP home screen.
Select advanced wipe.
Check the system, data, cache, and dalvik cache options.
Swipe to wipe.
Install the ROM.
Select the install option from the TWRP home screen.
Navigate to where you have the ROM zip stored on your sd card and select it.
Swipe to install.
Most ROMs will run an installer script at this point but some ROMs have what is called an Aroma Installer which allow you to choose some install options before the script runs.​
You will also need to install the appropriate gapps package directly after installing the ROM.
Once you've installed all necessary zips you'll have an option to wipe cache/dalvik and an option to reboot system. Wipe the cache/dalvik, hit the back button, and hit the reboot system button.
[SIZE=+1]6. How To Install A Custom Kernel With TWRP Recovery[/SIZE]
Prerequisites: unlocked bootloader, TWRP recovery.
A custom kernel can open up a new level of control over your device, such as overclocking/underclocking, undervolting, changing governors, changing I/O schedulers, adjusting colour calibrations, adjusting sound calibrations, and many other options.
Download a kernel that is compatible with your current ROM.
Check the md5 to verify its integrity.
Enter TWRP recovery.
Select the install option from the TWRP home screen.
Navigate to the kernel and select it.
Swipe to install.
You'll have an option to wipe cache/dalvik and an option to reboot system. Wipe the cache/dalvik, hit the back button, and hit the reboot system button.
Once your phone has booted up you can use a kernel tuning app to change governors, I/O scheduler, clock speed, and other options. Some of the popular kernel apps are Trickster Mod, No Frills, Kernel Tuner, and many more.
[SIZE=+1]7. How To Flash The Stock Kernel (boot.img) With Fastboot[/SIZE]
Prerequisites: unlocked bootloader.
If you're running a custom kernel on Cyanogen OS you'll need to flash the stock kernel back in order to take an OTA update.
Download the appropriate set of stock images from this thread. Extract the zip and grab the "boot.img" file.
Put it in your fastboot folder (where you have fastboot.exe located) on your PC.
Boot into fastboot mode (power + volume up) and connect your phone to your PC via usb cable.
Open a command prompt from within your fastboot folder (shift + right click, select open command prompt here).
Issue this fastboot command:
Code:
fastboot flash boot boot.img
It'll take a few seconds to flash the boot.img, once it's finished you can manually reboot your phone or use the following command to reboot it:
Code:
fastboot reboot
It's now safe to disconnect your usb cable.
Now you have the stock kernel back on your device.
[SIZE=+1]8. How To Flash The Cyanogen OS Fastboot Images[/SIZE]
Prerequisites: unlocked bootloader.
Please note: This procedure requires an unlocked bootloader. This procedure will factory reset your device! All user data (settings, apps, data on internal storage) will be wiped!
Download the latest stock images to your PC from here. If you don't want the latest build you can find all stock images mirrored here thanks to @Spannaa.
Reboot your device into Fastboot Mode (power + volume up) and connect your phone to your PC via usb cable.
Unzip the file you downloaded and put its contents into your fastboot folder (the same folder that you have adb.exe and fastboot.exe located in on your PC).
Open a command prompt from within your adb/fastboot folder (shift + right click, select open command prompt here).
Issue these fastboot commands:
Code:
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot flash oppostanvbk static_nvbk.bin
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata_64G.img
or fastboot flash userdata userdata.img if you have the 16gb model)
Please note: flashing the userdata will wipe your internal storage (your virtual sd card). It's possible to flash these images without that command if a full wipe isn't completely necessary in your situation.
Reboot your device with this command:
Code:
fastboot reboot
It's now safe to disconnect your usb cable.
[SIZE=+1]9. How To Update Modem/Firmware When Switching From KitKat To Lollipop (and vice versa)[/SIZE]
Prerequisites: unlocked bootloader.
To update from KitKat to Lollipop download the YOG4PAS1N0 firmware zip here:
cm-12.1-YOG4PAS1N0-bacon-firmwareonly-fastboot.zip
To revert from Lollipop to KitKat download the XNPH44s or XNPH05Q firmware zip here:
cm-11s-XNPH44S-bacon-firmwareonly-fastboot.zip
cm-11s-XNPH05Q-bacon-firmwareonly-fastboot.zip
Reboot your device into Fastboot Mode (power + volume up) and connect your phone to your PC via usb cable.
Unzip the file you downloaded and put its contents into your fastboot folder (the same folder that you have adb.exe and fastboot.exe located in on your PC).
Open a command prompt from within your adb/fastboot folder (shift + right click, select open command prompt here).
Issue these fastboot commands:
Code:
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot flash oppostanvbk static_nvbk.bin
Reboot your device with this command:
Code:
fastboot reboot
It is now safe to disconnect your usb cable.
[SIZE=+1]10. How To Make Sure You Can Pretty Much Always Recover From An Accidentally Wiped System[/SIZE]
Prerequisites: unlocked bootloader, TWRP recovery.
There may come a time when you accidentally wipe your OS while trying to perform a basic cache wipe in recovery. Don't laugh, it can happen to the best of us. The best way to insure yourself against being stuck in recovery is to keep a ROM zip or a TWRP/CWM backup (a nandroid backup) on your sd card at all times.
This solution seems like common sense but apparently there are quite a few people out there who don't store a ROM or backup on their phone. You might think it's easy to just mount the OTG storage and copy a ROM across to your phone from your PC (which is definitely an option), but there's always a chance that you won't be near your HDD or sd card at the time, or it won't recognise your phone properly. Basically you need to insure yourself against Murphy's law.
[SIZE=+1]11. How To Backup & Restore Your EFS Partition[/SIZE]
Prerequisites: unlocked bootloader, root.
All too often on this device I've seen folks who have a corrupted or missing EFS Partition. This results in your IMEI being lost and no cellular activity on the device at all. This can be a royal PITA to fix, and some folks haven't been able to fix it at all. You can take a precautionary measure to safeguard yourself against this by taking a couple of minutes to back up your modemst files.
Open up Terminal Emulator on your phone (if you don't have it you can download it here).
Once it's open you'll be greeted with a command line prompt, in which you can enter text commands, the first thing you need to do is enable root access by entering this line (press the enter key on your on-screen keyboard after each command to issue it):
Code:
su
If this is the first time you've used Terminal Emulator a Superuser or SuperSU popup will appear, make sure you grant root access.​
Now enter these two commands:
Code:
dd if=/dev/block/mmcblk0p10 of=/sdcard/modemst1.bin bs=512
Code:
dd if=/dev/block/mmcblk0p11 of=/sdcard/modemst2.bin bs=512
The result should look like this:
This will place two files (modemst1.bin & modemst2.bin) on the root of your internal storage, make sure you copy them to your PC immediately so that you have a backup there to use if you need to restore it in future.
If by chance you end up with a corrupt EFS partition all you need to do is flash the files back to your device using fastboot.
Boot into fastboot mode (power + volume up) and connect your phone to your PC via usb cable.
Make sure the two files are in your fastboot folder on your PC.
These fastboot commands will restore the files:
Code:
fastboot flash modemst1 modemst1.bin
Code:
fastboot flash modemst2 modemst2.bin
Reboot your device:
Code:
fastboot reboot
It's now safe to disconnect your usb cable.
Credit goes to @Vonnegut for originally posting this method in the TWRP thread.
Donate To Me

Nice guide!
Sent from my One using Tapatalk

Great guide. Short and simple, just how I like it. :good:

timmaaa said:
The best way to insure yourself against being stuck in recovery is to keep a ROM zip or a TWRP/CWM backup (a nandroid backup) on your sd card at all times.​
Click to expand...
Click to collapse
Can you confirm that backups made through CW recovery are fully functional? I remember that my previous phone's kernel wasn't backing up /preload while making nandroid backups...

ksoze11 said:
Can you confirm that backups made through CW recovery are fully functional? I remember that my previous phone's kernel wasn't backing up /preload while making nandroid backups...
Click to expand...
Click to collapse
I don't use CWM recovery so I can't confirm that personally. I use TWRP and can confirm that backups are fully functional with that recovery.
Transmitted via Bacon

Ive rooted my OPO, how do i perform a nandroid backup ? when i rooted i dont know if i put a custom recovery on it.. i followed this guide https://forums.oneplus.net/threads/...snt-wipe-your-data.66270/page-16#post-3809224

Quinnaay said:
Ive rooted my OPO, how do i perform a nandroid backup ? when i rooted i dont know if i put a custom recovery on it.. i followed this guide https://forums.oneplus.net/threads/...snt-wipe-your-data.66270/page-16#post-3809224
Click to expand...
Click to collapse
You didn't install a custom recovery or unlock your bootloader if you followed that tutorial. Just unlock your bootloader, it'll wipe your data so just backup anything that's important first. Then you can flash TWRP recovery and make a nandroid backup.
Transmitted via Bacon

urgh, i was hoping i could keep all my data. Think ill give it a miss, it was only so i can install Xposed, but that should work anyway right?

Quinnaay said:
urgh, i was hoping i could keep all my data. Think ill give it a miss, it was only so i can install Xposed, but that should work anyway right?
Click to expand...
Click to collapse
If you're rooted you can just install the Xposed Framework apk and away you go. But, I'd strongly recommend you actually unlock your bootloader now, it's only gonna get harder to do the longer you wait.
Transmitted via Bacon

Come to think of it, there's a method around that'll unlock your bootloader without wiping any data, it's in the general section I think, have a look.
Transmitted via Bacon

Found it, @quinnay, here's what you want:
http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
Once you've done that you can follow my instructions to install a custom recovery and make a nandroid.
Transmitted via Bacon

Thanks Timmaaa yr a true contributor !!!!!!!!!!!!!!!!!:good:

Ive moved the "backups" folder containing all the files from my nandroid backup to PC if anything ever happens is it ok just on my PC or does it need to be on my phone?
edit: does this look right?

Quinnaay said:
Ive moved the "backups" folder containing all the files from my nandroid backup to PC if anything ever happens is it ok just on my PC or does it need to be on my phone?
edit: does this look right?
Click to expand...
Click to collapse
It's fine to store it on your PC. But, you should have either a backup or a ROM zip on your phone at all times. If your system accidentally gets wiped or you run into some kinda trouble and you don't have one of those on your phone you're gonna kick yourself big time.
Yes it looks just fine.
Transmitted via Bacon

timmaaa said:
It's fine to store it on your PC. But, you should have either a backup or a ROM zip on your phone at all times. If your system accidentally gets wiped or you run into some kinda trouble and you don't have one of those on your phone you're gonna kick yourself big time.
Yes it looks just fine.
Transmitted via Bacon
Click to expand...
Click to collapse
whats the best thing to leave on my phone? should i put the backup back then?

It's up to you. Being that the phone has a mammoth amount of internal storage I'd just leave a backup on it because that's the easiest solution (restore it and boot, no setup required). I currently have four full backups on my device.
Transmitted via Bacon

I have a backup on the phone and my PC. Are you suggesting a flashable ROM on the phone also? I have the international 64 GB model rooted unlocked running stock. Which flashable ROM are you suggesting. I am very happy with 11s.
Sent from my One using Tapatalk

26.2man said:
I have a backup on the phone and my PC. Are you suggesting a flashable ROM on the phone also? I have the international 64 GB model rooted unlocked running stock. Which flashable ROM are you suggesting. I am very happy with 11s.
Sent from my One using Tapatalk
Click to expand...
Click to collapse
You don't need both, just one or the other is fine. It's just there as a failsafe. As for the ROM question:
Asking which ROM is best/most stable/fastest/prettiest, or asking for a suggestion isn't allowed so I can't answer that, here's why. To say one ROM is better is to infer that the others are inferior in some way. This is disrespectful to the devs who spend their spare time bringing us these awesome ROMs free of charge. Each user has different tastes anyway, the best way to see which ROM suits you is to flash a few and find out for yourself.
Transmitted via Bacon

Thanks. I think you misunderstood me. I know better than to get into the best ROM stuff. I was referring to the factory cm11s ROM and was wondering if there was a flashable one I could leave on my phone.
Sent from my One using Tapatalk

26.2man said:
Thanks. I think you misunderstood me. I know better than to get into the best ROM stuff. I was referring to the factory cm11s ROM and was wondering if there was a flashable one I could leave on my phone.
Sent from my One using Tapatalk
Click to expand...
Click to collapse
Ahh I see, there is a recovery flashable version of cm11s available, it's in the dev section or general section.
Transmitted via Bacon

[GUIDE] Unlock/Root/Flash for Nexus 5X

[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.

Root Moto G 2nd Gen XT1068 running on 6.0 Marshmallow

http://www.datafilehost.com/d/59efbc15mfastboot with custom Recovery Link
http://www.datafilehost.com/d/bf3a2c6d
Super SU
http://www.datafilehost.com/d/bab6821a
insure you have Unlock Bootloader if aren't see the Post by Lucas
http://forum.xda-developers.com/moto-g-2014/general/wip-unlock-bootloader-moto-g-2nd-gen-t2875728
After unlock Bootloader
1. Put Super SU in Internal Storage
2. Extract Rar file in pc
3. In Folder Shift+Right click Of mouse and Start Command Mode
4. Enter Command "mfastboot Devices" And see your serial No. of device
5. Then next Command "mfastboot flash recovery twrp-2.8.3.0-titan.img" Done
6. Next Command "mfastboot reboot"
5. Then Reboot in Recovery and Flash Super Su
done !!! See super Su in Device

My moto g2 stuck on bootloader unlock warning after rooting
My moto g2 stuck on bootloader unlock warning after rooting

Follow the instructions here instead:
www . gammerson . com /2015/11/how-to-root-moto-g2-on-marshmallow. html
(remove spaces from link, as I'm not permitted to post an actual link)

1st boot take time after unlock bootloader .. if take more
then try to reset from recovery when Power off your device
-for recovery first press volume down button during power button
-select recovery in option
-when android logo comes press again both volume button during press power button and wipe data reset and wipe cache partition too
if you want remove unlocked bootloader logo
-Make sure you have setup ADB and mfastboot on your PC. (Download from above)
-Download the logo file and extract the zip file to get the logo.bin file. Transfer the logo.bin file to some place you can track it easily. Its better if you use the folder where you setup the mfastboot.
-Power off your device and keep it unplugged from your PC.
-Boot into bootloader. To do so, press and hold volume down and the power button for 5-6 seconds.
-You will see the bootloader screen. Now plug in your device to the PC.
-Navigate to the location of the logo.bin file. While the folder with the logo file is open, hold shift on keyboard and right-click on an empty space and select “Open command window here” option to launch a cmd window.
Now type the following in the command prompt to get a code
mfastboot flash logo logo.bin
Now type the following in command prompt to reboot.
mfastboot reboot
Once you reboot, you will no longer see the bootloader warning as it has been replaced with the Motorola logo. You can choose a custom image you like but be sure it is in .bin
link for logo file
https://www.datafilehost.com/d/TekaWiCcHE

Root Failed?
I followed your steps and after I flash recovery, It says boot failed when i try to boot in recovery. It says failed to boot?

Rushaan9912 said:
I followed your steps and after I flash recovery, It says boot failed when i try to boot in recovery. It says failed to boot?
Click to expand...
Click to collapse
well make sure that you have unlock bootloader,
are you able to start fastboot ?
then try this commands
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot

Locker49 said:
well make sure that you have unlock bootloader,
are you able to start fastboot ?
then try this commands
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
Click to expand...
Click to collapse
Tried it. It formatted my phone, Stilll wont root. WHenever I select REcovery it says "Failed to boot"

Rushaan9912 said:
Tried it. It formatted my phone, Stilll wont root. WHenever I select REcovery it says "Failed to boot"
Click to expand...
Click to collapse
Tried to flash recovery by fastboot ?
still face problem then you need to flash your stock rom
Instruction to Restore Stock Firmware on Moto G 2014
See the Post by @bhu999
http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-original-motorola-t3155774
first you needto Flash lollipop(link below) then in recovery you upgrade MM
https://docs.google.com/uc?id=0B665WEdcrNV2dnpDYjdJaTh5aGc
marshmallow (indian) Dual sim
https://drive.google.com/file/d/0B7BRotdWEAc5TXJQc091Vk5RQU0
https://drive.google.com/file/d/0Bw0NmnatfFOxVEotMFZlMkQzZkk
Kit-kat to MarshMallow
https://mega.nz/#F!Q9YHCQzY!dgyvAJ8eNA3t7az4vizwOQ

Locker49 said:
Tried to flash recovery by fastboot ?
still face problem then you need to flash your stock rom
Instruction to Restore Stock Firmware on Moto G 2014
See the Post by @bhu999
http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-original-motorola-t3155774
first you needto Flash lollipop(link below) then in recovery you upgrade MM
https://docs.google.com/uc?id=0B665WEdcrNV2dnpDYjdJaTh5aGc
marshmallow (indian) Dual sim
https://drive.google.com/file/d/0B7BRotdWEAc5TXJQc091Vk5RQU0
https://drive.google.com/file/d/0Bw0NmnatfFOxVEotMFZlMkQzZkk
Kit-kat to MarshMallow
https://mega.nz/#F!Q9YHCQzY!dgyvAJ8eNA3t7az4vizwOQ
Click to expand...
Click to collapse
Is it possible that this doesnt work on my phone because I have the 4G-LTE model?

Rushaan9912 said:
Is it possible that this doesnt work on my phone because I have the 4G-LTE model?
Click to expand...
Click to collapse
i uploded for moto g2 2014 (lte)

Rushaan9912 said:
Tried it. It formatted my phone, Stilll wont root. WHenever I select REcovery it says "Failed to boot"
Click to expand...
Click to collapse
Try using this SU as its the only one that has worked for me
http://forum.xda-developers.com/showpost.php?p=67670718&postcount=2

The issue is in the SuperSU updater script, which can't detect the system and is trying to install root in system mode (it should use systemless mode)
For those users who are stuck at bootloader logo after flash supersu, is necesary to reflash stock rom and flash this SuperSU (I've edited the updater-script to force systemless install)
After flash this SuperSU (updated to 2016-09-01), all updates can be installed directly from the store

Stuck at the start page
The root was done,but while rebooting the phone,the phone stuck on the unlock bootloader window and nothing happens.If anybody had the same problem please tell me how to repair it.

Locker49 said:
http://www.datafilehost.com/d/59efbc15mfastboot with custom Recovery Link
http://www.datafilehost.com/d/bf3a2c6d
Super SU
http://www.datafilehost.com/d/bab6821a
insure you have Unlock Bootloader if aren't see the Post by Lucas
http://forum.xda-developers.com/moto-g-2014/general/wip-unlock-bootloader-moto-g-2nd-gen-t2875728
After unlock Bootloader
1. Put Super SU in Internal Storage
2. Extract Rar file in pc
3. In Folder Shift+Right click Of mouse and Start Command Mode
4. Enter Command "mfastboot Devices" And see your serial No. of device
5. Then next Command "mfastboot flash recovery twrp-2.8.3.0-titan.img" Done
6. Next Command "mfastboot reboot"
5. Then Reboot in Recovery and Flash Super Su
done !!! See super Su in Device
Click to expand...
Click to collapse
Does this work on the XT1064?

bootloader is unlocked successfully but it is showing no command while trying to superuser in recovery option with a android bot lying down with an exclamatory mark on it in red background, what does it mean?

can moto g2 support VOLTE?

Facing same issues while trying to flash su. Result: stuck at bootloader screen

After running successful "fastboot flash recovery twrp.IMG " when i select recovery option in my moto g(titan) an error occur that is"boot failed"
How can i fix it please help asap?

Need help fixing my bricked phone

Hey Guys,
I have a redmi 3s prime and i tried to install lineage os on it, during the process i accidentaly flashed twrp over both the recovery and the boot. Now i cannot get into the recovery (and fastboot) unless i flash it over boot before rebooting my phone. After that i AM able to flash an new rom but it seems to always have wifi issues.
atm i am trying to flash the xiaomi developers global rom to see if it makes any difference. My main goal is to flash TWRP and a curstom rom (linage or resurrectionremix).
Can anyone help me?
Thanks alot!
Update #1
The flashing of the global developer rom worked and the wifi seems to work aswell, i will try to boot into fastboot and recovery.
Update #2
Its seems i am able to boot into fastboot and recovery again
Update #3
Following a tutorial for flashing TWRP and a custom rom but cant se2 anyone help me here?:
Code:
>>> Check then next step to root :
- launch minimal adb tool (previously installed)
- type : adb devices (to list phone connected) it will appear "unauthorized"
- on the phone : accept the computer
- re type : adb devices
it has changed in "authorized"
- type : adb reboot bootloader
it will go in fastboot mode (the same that power + vol down)
- type : fastboot devices
your phone will appear as in adb mode (unless the bad signed driver is choosen in win10 ; i won't repeat it again)
- type (optional) : fastboot oem device-info (to verify if bootloader is locked or unlocked)
now, we go to root
- type : fastboot boot twrp.img (if it is your renamed twrp copied in the minimal adb folder)
link for TWRP guide at the end if needed
!!! it will boot temporary in this recovery but it will keep your original recovery !!!
> allow to modify system (don't keep the "read only" if you want to root or flash recovery later)
go to settings to set date, hours, language, set custom options...
My optional advices :
- save your EFS & persist partitions or all whole partitions (except cache) to make a backup
- export this backup in computer or SD card in case of future problem
(EFS, persist are usefull to save and restore your IMEI in particular)
- you can flash directly TWRP with fastboot command : fastboot flash recovery twrp.img
>>> Root :
Now flash DM-verity patch, then superSU.zip to root and accept to wipe dalvik/cache after, finally reboot !
Device is rooted ! and you have kept the original recovery.
the reboot is quite long like rom update (because of cache rebuild)
sometimes, parts of theme are lost after rooting : just restore your theme
some devices don't need DM-verity patch as explained upper
superSU app shows "systemless root" from android 6+, it is normal, read below
>>> Change the Recovery by TWRP (optional) :
Now you are rooted, you have 2 methods :
- Install one TWRP app with googleplay and flash recovery through app on rooted device.
New official app in development (flash/backup .img & .tar)
- OR reboot in fastboot mode (with TWRP app method or power+vol- method or adb reboot recovery method)
in fastboot mode, and type commands :
fastboot devices
fastboot flash recovery twrp.img
(be sure your twrp.img is unlocked and correctly copied/renamed in minimal adb folder)
Now, long press power to turn OFF phone
power + vol+ (release power at vibration) to enter in TWRP or by TWRP app or Updater app or under Windows with minimal adb reboot recovery command
Note for devices with DM-verity : flashing TWRP needs to have patched system with DM-verity patch before because you will modify system most of time - generally, you don't need to patch again because you have ever done it in previous steps - in case of bootloop : go to fastboot mode, boot in TWRP with command and patch it.
Chainfire has recently modified superSU for android 6+ devices with DM-verity to install root without modify the system : it's called "systemless root". When you flash superSU.zip, it detects automatically android version, cleans old files and installs with appropriate method. Maybe no need to patch boot in this case with DM patch.

Unicorn Unlocker & TWRP for Telstra Evoke Plus - A.K.A ZTE Blade A7 2019-T

ZTE Blade A7 2019-T Bootloader Unlock and TWRP Install Guide
I have recently ported a similar MT6761 devices TWRP 3 to suit our needs on the ZTE Blade A7 2019-T.
It has take a few solid days messing around, but here's everything I've got on the Telstra Evoke Plus Variation.
You MUST UPDATE to M01 Version First !!! Important !!!
- WokeWorld
Click to expand...
Click to collapse
Specifications,
Android 9.0
Firmware Update M01
CPU MT6761
RAM 2GB
KERNEL 4.9.117+
I was going to make a complete BATCH Script for Windows PC's however I gave up after a while.
Everything is compiled into a ZIP folder called Unicorn
First, Extract the Unicorn ZIP.
If you want to do everything manually, then open Assets Folder and copy out the Files needed.
recovery.img
vbmeta.img
twrp.img
Once you've got your files, Skip past the Automatic Instructions if you're planning to go manually.
Auto Instructions
Open Auto Install TWRP.bat
Follow on-screen instructions
Manual Instructions
Enable USB Debugging and OEM Unlocking;
Open Settings
Open System
Open Advanced
Tap Build-Number 7 Times to Unlock Dev Options
Go Back Once
Open Development Options
Find USB Debugging and Enable it
Find OEM Unlocking and Enable It
Plug Device Into Computer
Start the Unlocking and Installation,
Enter following commands
Code:
adb reboot bootloader
Code:
fastboot flashing unlock_critical
Press Volume UP to Accept on Device
Code:
fastboot flashing unlock
Press Volume Up to Accept on Device
Code:
fastboot --disable-verification --disable-verity flash vbmeta vbmeta.img
Code:
fastboot flash recovery twrp.img
Now the Tricky Part is Rebooting without Automatically Replacing the Recovery with Stock.
Hold Power until Screen Turns OFF
Immediately Release Power and Press Volume UP + Power Again for 5 seconds
Release after 5 seconds and wait until TWRP boots Up for First Time.
STOPPING THE STOCK RECOVERY REPLACEMENT,
Open TWRP
Open MOUNT
Mount the System
Go back to File Manager
Open System > System >
Delete `recovery-from-boot.p` or Rename It
FILES
all files are packed in the zip "Unicorn.zip" on my Google Drive - Sorry can't post links yet, you have to copy paste it
Google Drive Folder
https://drive.google.com/folderview?id=11XmE_hg6sC6JLAL6qK6E9PJ9kwbUo49j
• A newer Port of TWRP is available in the folder until I can upload here, hopefully soon.
WHAT'S NEW ?
• Fixed Prop.default with correct Device information from TECNO KB8 to Blade A7
• Added NV RAM & NV DATA to Backup Section, not Sure about Restore Section yet.
TWRP REQUIRES YOU ERASE YOUR DATA PARTITION INSIDE TWRP TO FIX ENCRYPTION PASSWORD.
Please do a backup of your data first, Unlocking the bootloader will Erase the DATA Partition with all your precious files on it.

So .. where's the file

so this would work for the a7 prime?

Hey buddy
Do u have stock rom for this to flash via Sp FlashTool? I get mine A7 zte on bootloop