[TUTO+VIDEO] Unlock Bootloader-Flash Recovery-Root-Restore Back the N7 FLO- KK 4.4.4 - Nexus 7 (2013) General

This tutorial All In One is for all owners of the NEW NEXUS 7 FLO (2013 Edition). I've tried to be clear, helpful and simple
....-ox=O=xo-....​POST #1 => [TUTO + VIDEO] AIO Unlock Bootloader, Flash Recovery (TWRP) and Root your Nexus 7 FLO​
....-ox=O=xo-....​POST #2 =>[TUTORIAL]Download Factory Images Nexus 7 FLO - Restore back STOCK with latest KK 4.4.4
....-ox=O=xo-....​POST #3 => [HOW TO] FLASH MORE FASTER WHEN YOU USE FASTBOOT LINE COMMAND
....-ox=O=xo-....
Warning!
This guide and its guidelines are meant only and only for the new Nexus 7 "FLO" (2013).
Do not attempt to try this on the older Nexus 7 or any other device.
Applying this to any other variant might brick the device.
Read and understand the instructions carefully before proceeding any further.​
Click to expand...
Click to collapse
....-ox=O=xo-....​
Pre-requisites:
Click to expand...
Click to collapse
THIS GUIDE IS ONLY FOR WINDOWS
1) This point is really important. You’re going to lose all your datas on the device including the internal storage. So back everything up.
2) Download and Install 7zip or any other archive manager as WinRAR etc...
3) Download and install Android SDK
OR
3Bis)Download The ADB and Fastboot Tools in the same Tool ==> platform-tools.zip - md5: 15e771613370afe3c70e0be1454d2ef1 - size: 346.8KB
4) Put these 3 files in where your fastboot folder is installed; ex => => disk C: root
Unzipped this file on the folder "platform-tools" and you will find 11 files:
- aapt
- adb
- AdbWinApi.dll
- AdbWinUsbApi.dll
- aidl
- dexdump
- llvm-rs-cc
- fastboot
- dx
- NOTICE
- source.properties
5) Enable USB Debugging Mode on the tablet to connect it with the computer and use Android SDK with it.
{ Press Menu =>> Settings =>> Applications. From there navigate and click on Development option then check the USB Debugging Mode.}
If you don’t see the Development Options, you'll need to open the Settings app and scroll down to the bottom. Once you get there, tap “About Phone”. Scroll to the bottom again, until you see the Build Number entry.
Now tap Build Number a total of seven times. You'll see friendly developer messages starting with the fourth tap. After the seventh, you'll see a message congratulating you for unlocking Developer Options. “Now you are a developer".
6) At least 70% battery power to avoid uncertain shutdowns during the process.
7) The tutorial is compatible only with the Nexus 7 wifi (2013) FLO.
....-ox=O=xo-....
Process to unlock bootloader of your Nexus 7 FLO
Click to expand...
Click to collapse
-1: Connect the Nexus 7 to the computer using USB cable.
-2: Open a Command Prompt window and type the following command to reboot the device into booltoader mode:
Code:
adb reboot bootloader
-3: Type the following command to lauch the unlock process:
Code:
fastboot oem unlock
-4: You will now be prompted with a dialogue to confirm the process, go through it.
Use the Volume buttons to highlight Yes and select it using the Power button
-5: The tablet will go back to the bootloader screen. Press Power button to select Start to reboot into the unlock device
Before to install the TWRP recovery and applying the root, you need to download the latest version of the TWRP recovery and the latest version of SUPER-SU that you need to push to the root of your sd card - For downloading these files follow the links below
Click to expand...
Click to collapse
....-ox=O=xo-....
Process to install TWRP recovery on your Nexus 7 FLO
Click to expand...
Click to collapse
-1: Download the latest TWRP recovery image file
Download link- TWRP
-2: Open the folder where the recovery image file has been downloaded and rename your recovery "recovery-twrp" simply. Re-open your previous Command Prompt window.
-3: Type the following command to flash the recovery image file
Code:
fastboot flash recovery recovery-twrp.img
-4: The recovery will be flashed and the progress could be observed in the CMD window itself.
Note: To boot the Nexus tablet into Recovery, press the Volume keys (up/down) until Recovery Mode is displayed. Use the Power button to select it and the device will reboot into the TWRP recovery Mode.
....-ox=O=xo-....
Process to root your Nexus 7 FLO - Update
Click to expand...
Click to collapse
-1: Download the SuperSU root package for Nexus 7
or you can use Download link: CF-Auto-Root-flo-razor-nexus7.zip
Explanations for understand why you must use CF-Auto Root => Go to read here the Central Post
-2: Download the ZIP file (see the link above) and Extract the ZIP file
-3: Connect the tablet to your PC using USB cable.
-4:Boot your device in bootloader/fastboot mode. Usually this can be done by turning your device off, then holding VolDown+Power to turn it on.
-5:Connect your device to your computer using USB
-6: Open a new CMD window and type the following command:
For Windows
Code:
root-windows.bat
For Linux
Code:
chmod +x root-linux.sh
root-linux.sh
For Mac OS X
Code:
chmod +x root-mac.sh
root-mac.sh
Follow the on-screen instructions - watch both the computer and the device !
Note that if your device had not been unlocked before, this procedure will wipe all your datas !
And if you have some problem with the process, go to see HERE
Now your Nexus 7 FLO running on Android 4.4.4. KitKat should have be rooted with latest TWRP recovery installed and bootloader unlocked. :victory: :good:
If you need more help, following my OP and this video from @clozecall
....-ox=O=xo-....
{
"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"
}
ISSUES
Click to expand...
Click to collapse
If you have some problem after to flash the recovery, and you stay stuck on during 5mn + You need to wipe data and factory reset on settings and normally all should be work perfectly after
Click to expand...
Click to collapse
....-ox=O=xo-....
USEFULL FILES:
Click to expand...
Click to collapse
Recovery_Stock_KK-4.4.4.img - Download link - Md5: 0ce33e5478a93f335f9be94c42057557 - size: 7.4MB ==> NEW
Recovery Stock -SS15QR.img - Download link
Recovery Stock -JSS15Q.img - Download link
Recovery_stock_JSS15J.img - Download link
Recovery_stock_ JRW66V - Download link
Google USB Drivers - md5: 1389bb2de0c9cacce27c76f1c71592ef - size: 8 MB
OEM USB Drivers
USB DRIVERS r_06 for Windows 7 & 8​Thanks to @clozecall for his video
and all members for their help
And don't forget to RATE FOR THIS THREAD -
if it's helped you
"Thanks in advance

[TUTORIAL]Download Factory Images Nexus 7 FLO - Restore back STOCK
[TUTORIAL]Download Factory Images Nexus 7 FLO - Restore back STOCK - With latest version KitKat 4.4.4​
Find your Factory image for your N7 FLO - KitKat KTU84P - Download Link - - is very useful if you need to restore back your device to Stock after any modification you’ve made. If you have rooted your N7 Flo, unlocked its bootloader, installed custom recovery and roms and finally you want decided to getting back to official firmware and then to get or accept future OTA updates again. It’s the best way to restore back your device to Stock.
Coming back to stock is also useful if you have some bugs (for fixing it), Bootloop, stuck in boot screen logo and freeeeezzziiiinnnngggg, etc....But before to going back to stock, you need to read completly the tutorial and need to know
Your bootloader will be “LOCKED or UNLOCKED” when you want.​
1 - Where I can can find the right Factory Image for my Nexus 7 Flo and which files I need for proceed ?
But first download and install the necessary files prior to execute this properly. Download the full factory image corresponding to your exact mode which includes the full system, bootloader, recovery, kernel (boot.img).
Unpack the TGZ Version (tar/gz) or Zip Version Archive into its own directory. I use 7-Zip, but you can use any tool that reads gz and tar.
Factory Images "razor" for Nexus 7 [2013] (Wi-Fi) - 4.4.4 (KTU84P) - Download link
If you have already installed those files, just check theirs.
Java Runtime Environment.
Android SDK | Android Developers.
Platform tools
Fastboot files
2 - PREREQUISITES
First make sure that your battery is fully charge 100% and BACKUP ALL YOUR PERSONNEL DATA
[1] - Make sure you have USB debugging turned on. For security purposes, you can turn it off after we're done
[2] - Plug-in USB cable and If you are booted into Android, open a command prompt to your ADB and Fastboot directory,
[3] - In case you are not unlock, you need to unlock your bootloader, enter the following commands:
Code:
fastboot oem unlock
If your tablet hasn't already rebooted automatically, type:
Code:
fastboot reboot
NOW WE ARE READY FOR PROCEED TO RETURN STOCK
3 - RUNNING FACTORY IMAGE
If you want to keep your data intact, don't skip this step, (if you do your data will be wiped )
With your text editor (for me it's Notepad ++,
[1] - Edit (be careful not to run it by accident instead of editing)
[2] - flash-all.bat (if you're on Windows)
[2a] - flash-all.sh (Mac, Linux)
[2b] - and remove "-w" from the fastboot update command
For example, if the line reads fastboot -w update image-razor-ktu84p.zip, it should now read: fastboot update image-razor-ktu84p.zip. The -w option instructs fastboot to wipe data.
Click to expand...
Click to collapse
[3] - Reboot into the bootloader and run the appropriate flash-all script:
Code:
flash-all.bat
​Done, your Nexus 7 Flo is now coming back and running Stock Android KK 4.4.4
In Case you want to come back completely to Stock, for warranty or security purpouses, you need to re-lock your bootloader now.
Enter the following commands
Code:
fastboot oem lock
If your tablet hasn't already rebooted automatically, type:
Code:
fastboot reboot
Done!
And don't forget to RATE FOR THIS THREAD -
if it's helped you and eventually click to "Newsworthy Thread? "Thanks in advance

Reserved

[HOW TO] FLASH MORE FASTER WHEN YOU USE FASTBOOT LINE COMMAND and FILES
FLASH MORE FASTER WHEN YOU USE FASTBOOT LINE COMMAND and FILES​
If you have got a problem with your adb or fastboot or recovery....it's very simply and faster
use this:
Download this file "fastboot.zip" or this tool : platform-tools.zip - md5: 15e771613370afe3c70e0be1454d2ef1 - size: 346.8KB
Install this file somewhere in one folder which is named "fastboot" on your PC
=> disk C: root
Unzipped this file on the folder "fastboot" and you will find 3 files:
- adb.exe
- AdbWinApi.dll
- fastboot.exe
OR
Unzipped this file on the folder "platform-tools" and you will find 11 files:
- aapt
- adb
- AdbWinApi.dll
- AdbWinUsbApi.dll
- aidl
- dexdump
- llvm-rs-cc
- fastboot
- dx
- NOTICE
- source.properties
and when you need to push something by the bootloader, you can use it.
Don't forget to push on this folder the file that you need. For exemple: boot.img or a recovery.img, etc...
CD to where your fastboot or platform tools were installed
The line command is :
Code:
[B]C:\Users\R2D2>cd c:\platform-tools[/B]
Code:
[B]C:\platform-tools>[/B]
OR
Code:
[B]C:\Users\R2D2>cd c:\fastboot[/B]
Code:
[B]C:\fastboot>[/B]
Enter
Code:
[B]C:\fastboot>fastboot flash recovery recovery.img[/B]
Enter
If you want to flash the "recovery.img" file
******************************************************************
******************************************************************
If you want to know all lines of command
Code:
c:\fastboot>fastboot
Code:
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default: 2048

From this part of your procedure:
"-5: The tablet will go back to the bootloader screen. Press Power button to select Start to reboot into the unlock device
Note: Those who wish to install TWRP and root the device further, do not reboot the device. Leave the device at the same screen."
I still say you have to start and boot before you install TWRP. If you don't you get 0 MB Internal Storage on screen and twrp needs password. Can you verify this?
I had to restore my system.img and start over.
Maybe your version of TWRP does not require a reboot (Start) after OEM unlock?

I've always used clockwork on my phones... can you use clockwork in place of twrp on the nexus 7 flo?

Bricked my N7
Not new to flashing, but I made a huuuuuuuuge mistake today. I accidently flashed the wrong recovery image for the 2012 N7 (yeah, I'm an idiot). I can boot into fastboot and recovery mode, but it fails to mount the sd card so I can't do **** anymore. Can't even get it back to stock t this point Any suggestions? I'm on a mac, but have access to PC. Have tried both CWM and TWRP. TWRP just gives me the password screen and 0mb storage. Can't figure out how to get around it or get my storage mounted. Help!

Stuck in boot screen
"I still say you have to start and boot before you install TWRP. If you don't you get 0 MB Internal Storage on screen and twrp needs password. Can you verify this?
I had to restore my system.img and start over."
Androidfr33k, can you specify how to restore system.img? I also do the following steps without rebooting, now I'm stuck in the boot screen.
Thanks in advanced!

Gareee said:
I've always used clockwork on my phones... can you use clockwork in place of twrp on the nexus 7 flo?
Click to expand...
Click to collapse
For the moment, TWRP recovery is the best way for most of my devices.
I've used CWM during a long time with my old devices (Htc Hero - Desire Z) - for my Desire S, I've used 4EXT recovery and now for all devices, it's TWRP
I'm waiting a CWM recovery for see.
But it's just my advice
Wwdcc said:
"I still say you have to start and boot before you install TWRP. If you don't you get 0 MB Internal Storage on screen and twrp needs password. Can you verify this?
I had to restore my system.img and start over."
Androidfr33k, can you specify how to restore system.img? I also do the following steps without rebooting, now I'm stuck in the boot screen.
Thanks in advanced!
Click to expand...
Click to collapse
I've updated the guide, so I advise you to reboot after unlock your Nexus 7, in order to validate the release.

philos64 said:
For the moment, TWRP recovery is the best way for most of my devices.
I've used CWM during a long time with my old devices (Htc Hero - Desire Z) - for my Desire S, I've used 4EXT recovery and now for all devices, it's TWRP
I'm waiting a CWM recovery for see.
But it's just my advice
I've updated the guide, so I advise you to reboot after unlock your Nexus 7, in order to validate the release.
Click to expand...
Click to collapse
Thanks philos64. My problem now is that I couldn't even boot into the OS, I can get into Bootloader mode or Recovery mode, but I couldn't factory reset (says "failed") or boot pass the Nexus screen. (stuck there for more than 15 minutes).
I'm sort of a noob, any help will be appreciated.

Wwdcc said:
Thanks philos64. My problem now is that I couldn't even boot into the OS, I can get into Bootloader mode or Recovery mode, but I couldn't factory reset (says "failed") or boot pass the Nexus screen. (stuck there for more than 15 minutes).
I'm sort of a noob, any help will be appreciated.
Click to expand...
Click to collapse
Ok, if you want you can try this process which works => For Those Who Semi-Bricked Their Nexus 7 0MB Interal Storage

Wwdcc said:
Thanks philos64. My problem now is that I couldn't even boot into the OS, I can get into Bootloader mode or Recovery mode, but I couldn't factory reset (says "failed") or boot pass the Nexus screen. (stuck there for more than 15 minutes).
I'm sort of a noob, any help will be appreciated.
Click to expand...
Click to collapse
this just happened to me. I fixed it by:
1. go into recovery and FORMAT DATA in the wipe menu
2. then FACTORY RESET
3. restart to os
i didnt need to download the system.img like the above link

decksy said:
this just happened to me. I fixed it by:
1. go into recovery and FORMAT DATA in the wipe menu
2. then FACTORY RESET
3. restart to os
i didnt need to download the system.img like the above link
Click to expand...
Click to collapse
Same here, and thanks for the tip!

decksy said:
this just happened to me. I fixed it by:
1. go into recovery and FORMAT DATA in the wipe menu
2. then FACTORY RESET
3. restart to os
i didnt need to download the system.img like the above link
Click to expand...
Click to collapse
Ok sounds good
Thanks :good:
I will insert in my OP asap

decksy said:
this just happened to me. I fixed it by:
1. go into recovery and FORMAT DATA in the wipe menu
2. then FACTORY RESET
3. restart to os
i didnt need to download the system.img like the above link
Click to expand...
Click to collapse
It worked! Thanks so much!

I unlocked and rooted my nexus 4 with this method. I already have SDK and fastboot on my Mac. I can go ahead with the N7, right? I don't need a different fastboot version? I'll make sure my SDK is up to date.
Sent from my Nexus 7

eep2378 said:
I unlocked and rooted my nexus 4 with this method. I already have SDK and fastboot on my Mac. I can go ahead with the N7, right? I don't need a different fastboot version? I'll make sure my SDK is up to date.
Sent from my Nexus 7
Click to expand...
Click to collapse
Yep, you should be all set

If "adb reboot bootloader" works when unlocking the bootloader but "fastboot flash recovery recovery-twrp.img" just sits there in Windows with "waiting for device" try using "adb reboot bootloader" again followed by "fastboot flash recovery recovery-twrp.img" to get the recovery image flashed. I don't take credit for it because it was said somewhere in this forum while trying to figure out the problem. My main rig has this problem but my HTPC does not. Same issue I had with my N7/2012.
Thank you OP!! I'm now running cleanrom 1.1 on my N7/2013. Let the ROM's rain!!!!

Video Tutorial
Hey guys, I've made a pretty simple video tutorial on how to Unlock the Bootloader and Root the new Nexus 7.
Here it is:
I know I don't have a well known name on the forums at all, but I thought it would at least be nice to post this. :good:

This guide worked well for me. I was able to unlock the bootloader, and it appeared that I was able to install the TWRP recovery image. However, when it went to reboot, the Nexus 'X' logo is looping. What's the best way to fix this? I can't access the device through the cmd prompt either.
EDIT: Nevermind, was able to get into the TWRP recovery image (I was panicking and didn't press the right buttons).
Note: I let TWRP install SuperSu for me, instead of downloading it and moving it on internal storage myself. Don't know that had anything to do with my issues but just wanted to share a heads-up.

Related

[How-to]Root Android 4.2.2 And Install CWM v6.0.2.3

Here We have the Root And CWM for Nexus 7 On Android 4.2.2!
Step 1 - Download Android SDK from the Android Developers website and install with USB drivers. See: How to Set Up Android SDK (Fastboot / ADB) on Windows.
Step 2 - Enable USB Debugging mode in your Nexus 7 tablet.
Step 3 - Download Fastboot and extract it in android-sdk-windowsplatform-tools directory. Create directory if not already there.
NOTE: Skip Steps 1, 2, 3 if you already have them.
Step 4 - Download SuperSU v1.04 (UPDATE-SuperSU-v1.04.zip) and copy it to your sdcard on your Nexus 7 tablet.
Step 5 - Make sure you have backup your data as it will be removed. Then switch OFF your Nexus 7.
Step 6 - Download recovery-clockwork-touch-6.0.2.3-grouper.img and copy/paste it in the android-sdk-windowsplatform-tools directory.
Step 7 - Now go into Fastboot Mode on Nexus 7. How? Press Volume Down + UP + Power key for a few seconds till you see some text on the screen.
Step 8 - Navigate to android-sdk-windowsplatform-tools directory and open Command Prompt (Shift + Right-click > Open Command Prompt).
Step 9 - Type in the following command and press Enter.
fastboot flash recovery recovery-clockwork-touch-6.0.2.3-grouper.img
Click to expand...
Click to collapse
Step 10 - Once completed, choose RECOVERY MODE from the Fastboot menu and enter Recovery Mode.
Step 11 - Then scroll down to “flash zip from SD card” and press the Power button to select it.
Step 12 - Press the Power button again and select “choose zip from sdcard”.
Step 13 - Now using your volume keys, navigate to the UPDATE-SuperSU-v1.04.zip file that you copied to your SD card and select it using the Power button. Confirm the installation on the next screen and the installation procedure should start now.
Step 14 - After the installation completes, go to “+++++Go Back” and reboot the phone by selecting “reboot system now” from the recovery menu. Then Choose yes flash recovery back (this will make CWM your permanent recovery mode)
That’s it. Your Nexus 7 is now rooted on Android 4.2.2 JDQ39 software version of Jelly Bean and even has a custom CWM recovery installed. Check for the SuperSU app in your apps list to verify.
Root and CWM for Nexus 4
Root and CWM for Nexus 10
Reserved...
udimars30 said:
Reserved...
Click to expand...
Click to collapse
Thank you a lot...but the link for the fastboot its not aviable
Nano23 said:
Thank you a lot...but the link for the fastboot its not aviable
Click to expand...
Click to collapse
link updated
and this belongs in original development how? why not post a thread in original development asking about need for speed too..
Step 4 and step 7
I am a little confused about step 4 as I didn't think any nexus 7's had a SD card slot. I purchased mine right from google. I just put the zip file directly on the device itself and I know from my experience with my old Nexus One that this works too, just wondering who is selling the one with SD card slots. My second question, and really the more important one is step 7. I have tried to make the device go into fastboot several times and when I hold the volume keys down, the device boots to a black screen with no ability to do anything after that. If I mess with the power button (meaning I hold it in for a long time then let it out, and do this several times) I can get the device to preform a normal boot. Any thoughts?
thanks
Thanks its worked for my nexus 7..
udimars30 said:
Here We have the Root And CWM for Nexus 7 On Android 4.2.2!
Step 1 - Download Android SDK from the Android Developers website and install with USB drivers. See: How to Set Up Android SDK (Fastboot / ADB) on Windows.
Step 2 - Enable USB Debugging mode in your Nexus 7 tablet.
Step 3 - Download Fastboot and extract it in android-sdk-windowsplatform-tools directory. Create directory if not already there.
NOTE: Skip Steps 1, 2, 3 if you already have them.
Step 4 - Download SuperSU v1.04 (UPDATE-SuperSU-v1.04.zip) and copy it to your sdcard on your Nexus 7 tablet.
Step 5 - Make sure you have backup your data as it will be removed. Then switch OFF your Nexus 7.
Step 6 - Download recovery-clockwork-touch-6.0.2.3-grouper.img and copy/paste it in the android-sdk-windowsplatform-tools directory.
Step 7 - Now go into Fastboot Mode on Nexus 7. How? Press Volume Down + UP + Power key for a few seconds till you see some text on the screen.
Step 8 - Navigate to android-sdk-windowsplatform-tools directory and open Command Prompt (Shift + Right-click > Open Command Prompt).
Step 9 - Type in the following command and press Enter.
Step 10 - Once completed, choose RECOVERY MODE from the Fastboot menu and enter Recovery Mode.
Step 11 - Then scroll down to “flash zip from SD card” and press the Power button to select it.
Step 12 - Press the Power button again and select “choose zip from sdcard”.
Step 13 - Now using your volume keys, navigate to the UPDATE-SuperSU-v1.04.zip file that you copied to your SD card and select it using the Power button. Confirm the installation on the next screen and the installation procedure should start now.
Step 14 - After the installation completes, go to “+++++Go Back” and reboot the phone by selecting “reboot system now” from the recovery menu. Then Choose yes flash recovery back (this will make CWM your permanent recovery mode)
That’s it. Your Nexus 7 is now rooted on Android 4.2.2 JDQ39 software version of Jelly Bean and even has a custom CWM recovery installed. Check for the SuperSU app in your apps list to verify.
Root and CWM for Nexus 4
Root and CWM for Nexus 10
Click to expand...
Click to collapse
Thanks a million man! I was having all kinds of trouble updating to 4.2.2 and finally figured that out. Then I was having problems rooting again until I found this. Your method worked great but I used TWRP instead and it still did the trick. Thanks again.
I tried this but when I want to flash the recovery, my fastboot.exe will then not respond and will try to close. What gives?
Step 7 - Now go into Fastboot Mode on Nexus 7. How? Press Volume Down + UP + Power key for a few seconds till you see some text on the screen.
Click to expand...
Click to collapse
Just a quick note here, to enter Fastboot Mode you just need to turn the Nexus 7 off, then turn on again, soon as you see the Google logo press the Volume Down key and hold (Hold both Power button and Volume Down Key).
No need for holding the power button, the vol down button does the whole trick
worked for me. thanks very much
sicameron32 said:
I am a little confused about step 4 as I didn't think any nexus 7's had a SD card slot. I purchased mine right from google. I just put the zip file directly on the device itself and I know from my experience with my old Nexus One that this works too, just wondering who is selling the one with SD card slots. My second question, and really the more important one is step 7. I have tried to make the device go into fastboot several times and when I hold the volume keys down, the device boots to a black screen with no ability to do anything after that. If I mess with the power button (meaning I hold it in for a long time then let it out, and do this several times) I can get the device to preform a normal boot. Any thoughts?
Click to expand...
Click to collapse
yes you can do that for the normal boot
Spenzert said:
Just a quick note here, to enter Fastboot Mode you just need to turn the Nexus 7 off, then turn on again, soon as you see the Google logo press the Volume Down key and hold (Hold both Power button and Volume Down Key).
Click to expand...
Click to collapse
Thanks..
I don't have N7 that's why did not know!
Leonhan said:
I tried this but when I want to flash the recovery, my fastboot.exe will then not respond and will try to close. What gives?
Click to expand...
Click to collapse
re-install the fastboot with all it's extensions in the same folder!
If you want to use fastboot by a easy way, use this guide you don't need adb line command, just fastboot line command and it's an child game by this way
If you have got a problem with your adb or fastboot or recovery....it's very simply and faster
use this:
Download this file "Fastboot.zip"
Install this file somewhere in one folder which is named "fastboot" on your PC
=> disk C: root
Unzipped this file on the folder "fastboot" and you will find 3 files:
- adb.exe
- AdbWinApi.dll
- fastboot.exe
and when you need to push something by the bootloader, you can use it.
Don't forget to push on this folder the file that you need. For exemple: boot.img or a recovery.img, etc...
The line command is :
Code:
c:\fastboot>
Enter
Code:
c:\fastboot>fastboot flash recovery recovery.img
Enter
If you want to flash the "recovery.img" file
If you want to flash a boot.img:
Code:
c:\fastboot>fastboot flash boot boot.img
******************************************************************
******************************************************************
If you want to know all lines of command
Code:
c:\fastboot>fastboot
Code:
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default: 2048
don´t i have to unlock bootloader first ?
Domx92 said:
don´t i have to unlock bootloader first ?
Click to expand...
Click to collapse
Yes, it is a prerequisite if you want to root your android device.
Ok, so I am running the 4.2.2 update, and after jumping through numerous hoops trying to have my device recognized by adb, I just want to make sure that my very first step should be to boot up in fastboot mode and then issue the following command...
"fastboot oem unlock"
???
Then I can go ahead and proceed to flashing the CWM recovery and flashing the SuperSU file...?
Sent from my SCH-I535 using Tapatalk 2
EDIT: I've tried multiple times, but everytime I boot into "fastboot" mode, which I guess is another way for saying the bootloader, ADB loses its connection with my Nexus 7! Also, if it helps anyone to know, I'm running Win7 64-bit.....I'm not sure if that matters, but the first time I booted up into fastboot mode, my computer recognized it and installed it as an "Android Bootloader Interface" in the Device Manager! When the device boots up normally, ADB does recognize it again, and it also shows up differently in the Device Manager (Android Composite ADB Interface)! ANY help or suggestions would be greatly appreciated, as I obviously can't issue commands to a device that ADB can't see when it's in fastboot mode!
vmancini3 said:
Ok, so I am running the 4.2.2 update, and after jumping through numerous hoops trying to have my device recognized by adb, I just want to make sure that my very first step should be to boot up in fastboot mode and then issue the following command...
"fastboot oem unlock"
???
Then I can go ahead and proceed to flashing the CWM recovery and flashing the SuperSU file...?
Sent from my SCH-I535 using Tapatalk 2
EDIT: I've tried multiple times, but everytime I boot into "fastboot" mode, which I guess is another way for saying the bootloader, ADB loses its connection with my Nexus 7! Also, if it helps anyone to know, I'm running Win7 64-bit.....I'm not sure if that matters, but the first time I booted up into fastboot mode, my computer recognized it and installed it as an "Android Bootloader Interface" in the Device Manager! When the device boots up normally, ADB does recognize it again, and it also shows up differently in the Device Manager (Android Composite ADB Interface)! ANY help or suggestions would be greatly appreciated, as I obviously can't issue commands to a device that ADB can't see when it's in fastboot mode!
Click to expand...
Click to collapse
Hi, vmancini3...
Forget about ADB when your tablet is in FASTBOOT/BOOTLOADER mode...
Here are the salient commands....
Code:
fastboot devices
- should return a serial number to confirm your FASTBOOT connection -
Code:
fastboot oem unlock
- will unlock the BOOTLOADER and will WIPE and FACTORY RESET THE DEVICE; unfortunate, but necessary .
--------------------
With the BOOTLOADER unlocked, begin to set up your Nexus 7 again... as though it was a brand new, just purchased tablet... ie., country, regionalization, WiFi key... etc.
Go online with your Nexus 7 browser (Chrome), and download Chainfire's SU Updater .ZIP package from here...
http://download.chainfire.eu/310/SuperSU/UPDATE-SuperSU-v1.04.zip
Upon completion of this download, shut down the tablet.
--------------------
Reboot again into FASTBOOT/BOOTLOADER mode... VOL down button + POWER ON button.
From your PC, run this command...
Code:
fastboot flash recovery recovery.img
....where the recovery.img is your CWM or TWRP .img file.
Both of which are available here...
CWM - http://www.clockworkmod.com/rommanager
TWRP - http://www.teamw.in/project/twrp2/103
--------------------
Congratulations.... you've just FLASHED a CUSTOM RECOVERY!!!
--------------------
When the self-congratulatory round of self applause has died down, ... and with the Nexus 7 still in FASTBOOT/ BOOTLOADER MODE, use the VOL buttons to navigate and the POWER button to select... reboot into RECOVERY.
Using the new CUSTOM RECOVERY, flash Chainfires SU updater package that you downloaded earlier... usually found in the /download folder...
Done.
Reboot.
Rooted.
--------------------
I really don't understand why some people seem to have a problem with this procedure... it takes less time doing it, than actually describing how to do it.
Rgrds,
Ged.

[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

[How To] Fix Otter X Install Errors, Partition sizes, Unable to Mount System...

19 May 2015: With the Fall of Goo.im I will be posting Mirrors OtterX files here:
Otter X Twrp and Bootloader Mirrors
Several people have had trouble Installing Cm12 and Slimpop Otter X Roms.
Seems to be a variety of reasons for this.
Did you watch my video? [YouTube] [How To] convert to OtterX ROM/TWRP/Bootloader
Did you read original OtterX thread? OtterX ROM/TWRP/Bootloader
Did you install otterx-u-boot_v2.05.zip and zip-otterx-twrp-2.7.1.0-recovery.zip in twrp?
Did you verify checksum(s) for all file(s) used? https://sites.google.com/site/sdshadowscollection/home/hash-checksums
Did you wipe cache, rebooted, Fomate Data, wipe partitions in wipe>advanced ?
-
For those having trouble with MTP on TWRP versions 2.8.X.X and Window 7
try Updating Windows Media Player
wicpp said:
I am having Windows XP SP3 and I was experiencing the same USB MTP installation failure, I updated my Windows Media Player and it fixed the problem. The option in Windows Media Player Help->Check for updates was not working, so I downloaded Media Player from Microsoft webiste and installed it and after that driver is now working fine.
Click to expand...
Click to collapse
Problem: Installed OtterX Bootloader, and now can't access bootmenu options with Power button, and just bootloops.
Solution 1: Try Disconnect from PC, Power off (Hold Power button for 10-20 secs), connect to wall charger
Solution 2 : Reflash TWRP
Solution 3 : Reflash 2.05 bootloader​
Problem: Twrp Cannot connect to PC. Device not found. In the device manager, Amazon OtterX is listed, but has an exclamation next it.
Solution:If drivers were working before, try selecting drivers for device.
Fixing OtterX Drivers: I posted screenshots of how Kindle should look like in Device manager, once converted to OtterX in post #9 here
In Device manager>select unknown device or device with a yellow triangle or ! >Update driver software>
browse my computer for driver software>Let me pick from a list of Device Drivers on my computer>
show all(uncheck show only compatible)>look for ADB interface or android phone
select yes to Ignore warning
may need to reboot both.​
Problem: Twrp is recognized by PC, but neither MPT mount, nor ADB push works. May get an unauthorized device error/warning
Problem: Installed TWRP 2.8..X.X now whenever i try to get into recovery it goes to teamwin logo and goes back to the kindle fire screen
Solution:If you are using Twrp 2.8.XX, use a Linux or Mac machine, or downgrade to 2.7.1.0 Twrp:
Downgrade 2.8.X.X Twrp to 2.7.1.0 TWRP see Flashing TWRP in OtterX bootloader​
Problem: When Installing Lollypop you get an :updater binary error"
Solution:If you are still using bootloader 2.04, upgrade to 2.05:
If you still can push files to Twrp, try pushing 2.05.zip, install, reboot, wipe cache, reboot, format data, wipe everything in wipe>advanced...​
Partition Sizes and File System
It seems that if you use TWRP 2.8.XX when switching from Amazon to OtterX partitions, sometimes things are getting fouled up, could be that this was an issue before, but has been more noticeable with lollipop.
Partitions sizes for OtterX partitions with 2.05 bootloader should be ...
all should say Present: Yes
system: Current file System: Ext4 - Size: 751MB (768MB)
Cache: _Current File System: Ext4 - Size: 503MB (512MB)
Data:__Current File System: _ f2fs - Size: 5820MB (5880mb)
see post #2 for screenshots​
If you have Twrp 2.7.1.0 and bootloader 2.05, and have wiped cache, rebooted, Fomated Data, wiped partitions in wipe>advanced and still have issues:
Solution:Reboot to bootloader, select Amazon partitions, select recovery, wipe cache, reboot to bootloader select OtterX partitions, select recovery, wipe cache, reboot, format data, wipe all partitions.​
Verify Partition sizes match post #2
Of course, all this assumes that drivers are installed correctly on you PC, none of the above will work if drivers are not correct.
If adb commands were working correctly before, and/or fastboot commands are still working, likely drivers are correct.
Please reply if this Guide helped
Please include: What errors you were having, and steps you took to fix.
I made Some videos that cover most of the steps
Flashing TWRP in OtterX bootloader
[How-To] Revert from OtterX Project to Stock Kindle Fire Partitions/Rom
Don't use the EMMC corruption fix
Hashcode said:
Why did you try EMMC corruption fix? That wipes out every partition on the device and attempts to restore the barebones xloader, bootloader
You'll need to flash a recovery.img via fastboot to get back up and running.
Click to expand...
Click to collapse
Hashcode said:
I think I'm seeing a bootloader bug:
- If you power on the device w/o USB plugged in, there's a MUSB interrupt issue causes 1 of 2 things to happen: device hangs during boot entirely and/or the USB port is completely unresponsive (till you reboot).
Right now, I'm still debugging this as I get time. But, when I power on with USB connected, I don't see any issues. You can unplug immediately after the bootanimation ends and re-plug all day.
The reason I'm saying this is a bootloader issue:
I've never seen this behavior on the old bootloader. I might need to shutdown the USB port after the fastboot loop in a cleaner way.
If others have seen this, please chime in.
Click to expand...
Click to collapse
Partition Screnshots
{
"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"
}
Data Partition:
Cache Partition
System Partition
Hashcode said:
...And all of the other partitions will be ext4, only userdata will be formatted f2fs.
Click to expand...
Click to collapse
Hashcode said:
The v2.04 otterx partitions are smaller:
system = 512MB)
cache = 265MB
Vs the newer larger partitions in v2.05:
system = 768MB
cache = 512MB
The idea was to protect from future required wipes do to low system/cache space.
The bootloader doesn't need to support f2fs only recovery and the ROM/kernel.
Click to expand...
Click to collapse
Flashing TWRP in OtterX bootloader
see [Video] Flashing TWRP in OtterX bootloader
Check drivers before flashing see Post #9
Verify MD5 checksums https://sites.google.com/site/sdshadowscollection/home/hash-checksums
Download adb-fastboot.zip,
and an OtterX TWRP .IMG file like otterx-twrp-2.7.1.0-recovery.img -
Size: 7528448 bytes MD5: ec8e8a67492d5fd06494f854bb59b2ae
for flashing OtterX Bootloader use otterx-u-boot_v2.05.bin
Size: 238720 bytes MD5: 241a3fd1edad0a0d95886ddeb4693e1c​Step 1:
Create a folder in c drive named adb,
unzip/extract files,
copy AdbWinUsbApi.dll, AdbWinApi.dll, adb.exe, fastboot.exe, and otterx-twrp-2.7.1.0-recovery.img to adb folder.​Step 2
connect Kindle Fire to pc, via usb, power off Kindle​Step 3
Open a Command Prompt (start>all programs>accessories>Command prompt)
change directory to adb with​
Code:
cd\adb
Send flash command
Code:
fastboot flash recovery otterx-twrp-2.7.1.0-recovery.img
Power ON Kindle
Code:
fastboot reboot
after reboot you should be able to enter recovery by pressing power button once and selecting recovery
if still unable to enter recovery, may need to reflash bootloader
same steps
Code:
fastboot flash bootloader otterx-u-boot_v2.05.bin
Code:
fastboot reboot
if unable to get partitions correct, or adb was working but now does not, could be that something wrong with the bootloader, flashing
otterx-u-boot_v2.04.bin may fix
download otterx-u-boot_v2.04.bin
verify md5: 30569AE834BAFD70D6E7EFB90338F4CB
Code:
flashboot flash bootloader otterx-u-boot_v2.04.bin
Code:
fastboot reboot
In Bootloader, select Amazon partitions
select recovery
in TWRP>Wipe>Advanced Wipe>check Cache>swipe to wipe
select reboot system (don't worry about system not rooted warning, or no rom installed, just select an option)
In bootloader>select OtterX partitions
reboot recovery
in TWRP>Wipe>Advanced Wipe>check Cache>swipe to wipe
reflash 2.05 bootloader
Code:
fastboot flash bootloader otterx-u-boot_v2.05.bin
Code:
fastboot reboot
In Bootloader, select Amazon partitions
select recovery
in TWRP>Wipe>Advanced Wipe>check Cache>swipe to wipe
In bootloader>select OtterX partitions
reboot recovery
in TWRP>Wipe>Advanced Wipe>check Cache>swipe to wipe
reboot recovery
Wipe>format data
Wipe>Advanced Wipe>check all>swipe to wipe
reboot recovery
if using 2.7.10 try adb push
if using 2.8.X.X try MTP
you have single handed saved so many kindles. thanks for your continued support. cheers steve. long live otterx
Sent from my Nexus 5 using Tapatalk
Thanks
Thanks so much @sd_shadow, your instructions saved my Kindle Fire. I flashed twrp v2.7.1.0 from v2.8.1.0 and it worked properly.
Still using TWRP 2.8.x.x
I have idea for using TWRP 2.8.x.x without error when flash new ROM
The steps to perform this is:
Step 1: Wipe Factory Reset
Step 2: Intall Slim-otterx-5.0.1.alpha.0.7-v0.3.zip
Step 3: Intall newest version: Slim-otterx-5.0.1.alpha.0.9-V0.8.zip
Step 4: Install Gapps and Restart
It is successful with me. You can try it and give me comment if you can't.
Partition info in TWRP 2.7.1.0 ?
Great stuff @sd_shadow, keep up the good work. Where in twrp are you seeing the screens in post #2?
Thanks,
The Don
DonDeLome said:
Great stuff @sd_shadow, keep up the good work. Where in twrp are you seeing the screens in post #2?
Thanks,
The Don
Click to expand...
Click to collapse
Good question,
Wipe> Advanced> check a partition (Cache, System, or Data) then select Repair or Change File System
Sent from my XT907 using Tapatalk
Screenshot of Device Manager and OtterX Drivers
If you have not used the install.drivers.bat from Kindle Fire Utility, download, unzip, run install.drivers.bat.
KFU mirrors: AFH - Mega
show all(uncheck show only compatible)>look for ADB interface or android phone
If that worked Kindle should now look like this
Hi,
i have a problem.... every step works fine until adb push after step 3.
when i try to push the zip files to my device i only get "error: device unauthorized. Please check the confirmation dialog on your device"
But after step 3 there is no OS anymore to boot in an confirm.
How to solve the problem?
OnkelKaethe said:
Hi,
i have a problem.... every step works fine until adb push after step 3.
when i try to push the zip files to my device i only get "error: device unauthorized. Please check the confirmation dialog on your device"
But after step 3 there is no OS anymore to boot in an confirm.
How to solve the problem?
Click to expand...
Click to collapse
use twrp 2.7.1.0
see Flashing TWRP in OtterX bootloader
Looks like I have the same problem as the other people do. In step 4 here:
http://forum.xda-developers.com/showthread.php?t=2671619
When I wiped the System, that's when I first noticed that my computer no longer recognized the device and a popup indicated that driver installation had failed. I continued on to Step 5 and went to ADB my files (I confirmed ADB worked at the beginning of the process) and no device was found. Per the original post, I'm running 2.05 for bootloader and 2.8.2.0 for recovery. I checked the partition sizes and they all match. I did manage to get the unrecognized device named Amazon Otterx to install drivers as an ADB interface. But now when I go look at ADB devices, mine is listed but it has an "unauthorized" next to it. I followed the instructions on the video to install 2.7.1 recovery but the device never goes into fastboot. It just boots into the bootloader, hangs out for a few seconds, then powers off.
I think I'm stuck.
Minjin said:
Looks like I have the same problem as the other people do. In step 4 here:
http://forum.xda-developers.com/showthread.php?t=2671619
When I wiped the System, that's when I first noticed that my computer no longer recognized the device and a popup indicated that driver installation had failed. I continued on to Step 5 and went to ADB my files (I confirmed ADB worked at the beginning of the process) and no device was found. Per the original post, I'm running 2.05 for bootloader and 2.8.2.0 for recovery. I checked the partition sizes and they all match. I did manage to get the unrecognized device named Amazon Otterx to install drivers as an ADB interface. But now when I go look at ADB devices, mine is listed but it has an "unauthorized" next to it. I followed the instructions on the video to install 2.7.1 recovery but the device never goes into fastboot. It just boots into the bootloader, hangs out for a few seconds, then powers off.
I think I'm stuck.
Click to expand...
Click to collapse
have access to a Linux or Mac?
2.8.2.0 should work with those.
Sent from my XT907 using Tapatalk
sd_shadow said:
have access to a Linux or Mac?
2.8.2.0 should work with those.
Sent from my XT907 using Tapatalk
Click to expand...
Click to collapse
I guess I could use a live cd. Any other option?
I've tried ADB sideload. That did nothing. Also, if I boot into bootloader from recovery, it comes up in Fastboot mode but I don't think that helps me.
could run flash command,
Code:
fastboot flash recovery filename
when in twrp, then select reboot bootloader
sd_shadow said:
could run flash command,
Code:
fastboot flash recovery filename
when in twrp, then select reboot bootloader
Click to expand...
Click to collapse
Yeah that's mostly the same thing as in your video. I've already tried that. Nothing happens. PC sits at waiting for device and kindle sits in Fastboot mode. Fastboot devices doesn't show anything. Oh, and strangely enough, when in recovery the ADB devices list no longer shows it as being unauthorized. It is now simply offline.
edit: killed and restarted the adb server and now it shows unauthorized again....
Minjin said:
Yeah that's mostly the same thing as in your video. I've already tried that. Nothing happens. PC sits at waiting for device and kindle sits in Fastboot mode. Fastboot devices doesn't show anything. Oh, and strangely enough, when in recovery the ADB devices list no longer shows it as being unauthorized. It is now simply offline.
edit: killed and restarted the adb server and now it shows unauthorized again....
Click to expand...
Click to collapse
Windows 7, 8?
you have used install.drivers.bat from Kindle Fire Utility v0.9.9?
Sent from my XT907 using Tapatalk
sd_shadow said:
Windows 7, 8?
you have used install.drivers.bat from Kindle Fire Utility v0.9.9?
Sent from my XT907 using Tapatalk
Click to expand...
Click to collapse
Windows 7. No, I didn't use the utility drivers because they didn't work. Instead, I used the drivers you showed in your video:
https://www.youtube.com/watch?v=WqY5AUcf0Vk
With them in place, I was able to do all adb fuctions perfectly fine.
Incidentally, the device currently shows an an "android composite adb interface" and not as an "adb composite device" as mentioned here:
http://forum.xda-developers.com/showpost.php?p=52595046&postcount=193
I don't know if that makes a difference. I've tried getting it to point to the folder where the unpacked kindle drivers are it doesn't like them. Something about the kindle is making it work with the wrong drivers. That's the only thing I can think of.
open device manager
reboot Kindle, at bootloader press power button once to open boot menu (stops boot process about 2 mins)
In Device manager>select unknown device>Update driver software>
browse my computer for driver software>Let me pick from a list of Device Drivers on my computer>
show all(uncheck show only compatible)>look for ADB interface or android phone
select yes to Ignore warning
may need to reboot both.
then try fastboot devices
of that doesn't work Retry install.drivers.bat from Kindle Fire Utility v0.9.9 use alt download mirror.
sd_shadow said:
open device manager
reboot Kindle, at bootloader press power button once to open boot menu (stops boot process about 2 mins)
In Device manager>select unknown device>Update driver software>
browse my computer for driver software>Let me pick from a list of Device Drivers on my computer>
show all(uncheck show only compatible)>look for ADB interface or android phone
select yes to Ignore warning
may need to reboot both.
then try fastboot devices
of that doesn't work Retry install.drivers.bat from Kindle Fire Utility v0.9.9 use alt download mirror.
Click to expand...
Click to collapse
FYI, when I use the drivers in the 0.9.9 utility, it installs as a Samsung Android phone and doesn't work. That's how I first went down this rabbit hole of "quickly" rooting the device and putting a non-stock rom on it. I was following your thread:
http://forum.xda-developers.com/kindle-fire/development/how-to-kindle-fire-1-update-6-3-3-t2814955
But the KFU drivers weren't working.
So I watched your video which showed to use these drivers instead (which worked):
http://forum.xda-developers.com/showthread.php?t=2544410
I've been uninstalling, rebooting, and installing drivers nonstop, trying small variations here and there. I don't know what's going on.
edit: so if I follow your directions, while in bootloader, nothing android or unknown shows up in the device manager. On my last boot, I uninstalled everything and nothing new has popped up. If I prompt to go into recovery, I finally get a single unknown device. If I browse to look for drivers, neither ADB interface nor Android phone are options. Next, I install the kindle fire drivers I linked above. Still unknown. Unplug and plug back in. Still unknown. I install the KFU drivers. And now I have a Samsung phone. ADB shows it attached but it is unauthorized.
edit: I finally got it to communicate in fastboot by NOT installing drivers. It was actually more functional as an unknown device. Flashed the older recovery and then ADB would communicate. Flashed CM11 and gapps. Everything is fine now (though dreadfully slow).

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

Guide: How To Unlock/Root/Flash for Pixel XL (Marlin)

[SIZE=+3]How-To Guide For Beginners[/SIZE]
[SIZE=+2]Pixel XL (Marlin)[/SIZE]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[SIZE=+3]Intro[/SIZE]
This thread will serve as a location for basic how-to guides for the Pixel XL (Marlin). I'm going to start off with a couple of the more obvious ones and go from there.
[size=+3]Prerequisites[/size]:
If you are on Verizon, please follow dePixel8 guidelines prior to using this thread
Always update your phone to the latest build available before starting the unlocking/rooting process.
You'll need a working adb/fastboot environment on your PC to get through some of these guides.
You must have Java installed and up to date in order to use the SDK Manager, please ensure that this is taken care of before installing the SDK.
Please do not install adb/fastboot via any means other than the Android SDK, using other tools (like Minimal adb & fastboot) can lead to an outdated setup and various problems with flashing. You've been warned, other tools will not be supported in this thread.
Go here to download the Android SDK, which will give you most updated version of adb and fastboot. Scroll to the bottom of the page and find Other Download Options>SDK Tools Only, and grab the right version for your OS. While it's downloading create a folder in C: called SDK (C:SDK). Once you've downloaded the zip you can extract it into your C:SDK folder. Navigate to C:SDKandroid-sdk-windows and open SDK Manager.exe. In SDK Manager you need to install the following packages:
Tools> Android SDK Tools, Android SDK Platform-tools
Extras> Android Support Library, Google USB Driver
Once you have installed those, inside C:SDK you should see some new folders, one of them will be called platform-tools, within that folder you should see fastboot.exe and adb.exe. I'll refer to this as your fastboot folder/directory or working folder/directory during this guide. To make sure adb is correctly installed, open a command prompt from within your fastboot folder (hold shift + right click, select open command prompt here) and issue this command:
Code:
adb version
If it returns a version number for Android Debug Bridge then you're good to go.
You can test adb by connecting your device to your PC while booted into Android (making sure that adb/usb debugging is enabled in Settings>Developer Options) with the screen unlocked and issuing this command:
Code:
adb devices
It should return your device serial number, if so, adb is working.
You can test fastboot by connecting your device to your PC while booted into the bootloader (power + volume down) and issuing this command:
Code:
fastboot devices
It should return your device serial number, if so, fastboot is working.
[SIZE=+3]Quick Tips[/SIZE]
How to boot into the bootloader:
Power off your device. Once it's powered off hold power + volume down and the phone will boot into the bootloader. You can also use the following adb command:
Code:
adb reboot bootloader
[SIZE=+3]Index[/SIZE]
Post #1
1. How To Unlock Your Bootloader
2. How To Install A Custom Recovery On Your Device
3. How To Root with TWRP Recovery
4. How To Root with via Fastboot (No Recovery)
Post #2
5. How To Install A ROM with TWRP Recovery
6. How To Install A Custom Kernel With TWRP Recovery
7. How To Install A Custom Kernel Using Fasboot
8. How To Flash The Factory Images (Return To Stock)
9. How To Flash The Factory Images (Return To Stock But Leaving Internal Storage Intact)
[SIZE=+3]1. How To Unlock Your Bootloader[/SIZE]
Go into Settings/About Phone, scroll down and click on “build number” continuously until you see a toast notification telling you that you've enabled Developer Options. Go back to your Settings menu and enter Developer Options, scroll down and click on the “Enable OEM Unlock” checkbox, also make sure you enable USB Debugging while you're in the Developer Options menu.
Power off your phone then boot into the bootloader (power + volume down).
Connect your phone to your PC via usb cable.
Open a command prompt from within your fastboot folder (navigate to where you have fastboot.exe located on your PC, shift + right click anywhere within that folder, select open command prompt here).
Check your fastboot connection by issuing this command:
Code:
fastboot devices
It should return your device serial number, if not you need to make sure your drivers are installed correctly.​
Once you've confirmed your fastboot connection issue the unlock command:
Code:
fastboot flashing unlock
This will erase all user data from the device!
You should now see a screen on your phone asking you to confirm this action, use the volume keys to scroll and the power key to confirm if you're sure you want to go ahead.
Allow the process to complete and then issue this command:
Code:
fastboot reboot
Allow everything to go ahead and once finished you can disconnect your usb cable.
Note: After unlocking your bootloader, each time your phone boots up you'll be greeted with a warning that says "Your device software can't be checked for corruption. Please lock the bootloader". This is nothing to worry about, it's normal to see this when you have an unlocked bootloader. You can't remove it, as long as your bootloader is unlocked it will stay there.
Important: do not relock your bootloader unless your phone is fully stock. You must flash the factory images first in order to remove root and custom recovery (if you have them), if this precaution isn't taken you may end up with a brick. Please see section 10 of this guide for full instructions on how to return to stock.
[SIZE=+3]2. How To Install TWRP On Your Device[/SIZE]
Prerequisites: unlocked bootloader (section 1).
Warning: TWRP is currently in RC1 phase and is not fully stable, flash at your own risk.
This guide assumes you have just unlocked your bootloader and are otherwise stock, NO root yet.
Download the necessary files (IMG and Zip) from the TWRP website and add the TWRP zip to your internal storage: https://dl.twrp.me/marlin/
Place the IMG file in your fastboot folder (this is where fastboot.exe is located on your PC)
Boot into the bootloader. Open a command prompt from within your fastboot folder (navigate to where you have fastboot.exe located on your PC, shift + right click anywhere within that folder, select open command prompt here), enter this command:
Code:
fastboot boot path/to/twrp.img
(The TWRP filename in the command will change depending on which recovery you're flashing)
This will temporarily boot TWRP on your device. If you are using a lockscreen pin/pattern/password and do not get prompted to enter your password, reboot to the bootloader and try again. Go to install and browse to the zip and install the TWRP zip
[SIZE=+3]3. How To Root[/SIZE]
Prerequisites: unlocked bootloader (section 1), TWRP recovery (section 2).
Download the latest SuperSU of your choosing to your phone:
https://download.chainfire.eu/1013/SuperSU/SR4-SuperSU-v2.78-SR4-20161115184928.zip
Boot into TWRP recovery and enter the install menu.
Navigate to where you have SuperSU stored on your internal storage and select it.
Swipe to install.
Thats it, reboot and you should have TWRP and SuperSU installed
[SIZE=+3]4. How To Root via Fastboot[/SIZE]
Prerequisites: unlocked bootloader (section 1)
Special Note: This is for users who do not have or want TWRP installed and want to run stock root
Download Chainfire's root-marlin-pixelxl.zip located here: https://download.chainfire.eu/1011/CF-Root1/root-marlin-pixelxl.zip
Extract Chainfire's zip and follow the instructions in the read me
Code:
***** The short guide *****
*BOOT* (do not flash!) the supplied image, and wait a few minutes:
fastboot boot boot-to-root.img
***** The long guide *****
Before you root your device, you need to unlock your bootloader, if you haven't done so yet.
If you are using a Verizon device, you need a special tool for that. Go find that first.
- Boot into Android
- Enable developer options
--- Settings -> About phone -> Build number: tap 7 times
- Enable OEM unlocking
--- Settings -> Developer Options -> OEM unlocking
- Go into bootloader mode
--- Turn off device
--- Hold volume down and power
- Run "fastboot flashing unlock" and follow the on-screen instructions
--- This will wipe your device
To root your device:
- Go into bootloader mode, if not there already
--- Turn off device
--- Hold volume down and power
- Run "fastboot boot boot-to-root.img"
--- Wait for a few minutes. The device will reboot at least twice
- You should be rooted once Android is fully booted up
*****
Enjoy!
- Chainfire
XDA:DevDB Information
Guide: How To Unlock/Root/Flash for Pixel XL (Marlin), Tool/Utility for the Google Pixel XL
Contributors
bajasur, The Flash, beanstown106, @micmars
Version Information
Status: Testing
Created 2016-11-27
Last Updated 2016-11-26
[SIZE=+3]5. How To Install A ROM with TWRP Recovery[/SIZE]
Prerequisites: unlocked bootloader (section 1), TWRP recovery (section 2).
Pending......
[SIZE=+3]6. How To Install A Custom Kernel With TWRP Recovery[/SIZE]
Prerequisites: unlocked bootloader (section 1), TWRP recovery (section 2).
A custom kernel can open up a new level of control over your device, such as overclocking/underclocking, undervolting, changing governors, changing I/O schedulers, adjusting colour calibrations, adjusting sound calibrations, and many other options.
Download a kernel that is compatible with your current ROM.
Check the md5 to verify its integrity.
Enter TWRP recovery.
Select the install option from the TWRP home screen.
Navigate to the kernel and select it.
Swipe to install.
You'll have an option to wipe cache/dalvik and an option to reboot system, hit the reboot system button.
Once your phone has booted up you can use a kernel tuning app to change governors, I/O scheduler, clock speed, and other options. Some of the popular kernel apps are Kernel Auditor, Trickster Mod, No Frills, Kernel Tuner, and many more.
[SIZE=+3]7. How To Install A Custom Kernel via Fastboot[/SIZE]
Prerequisites: unlocked bootloader (section 1)
This guide is for users who DO NOT have TWRP installed, and want to Fastboot flash custom kernels.
Check the md5 to verify its integrity.
Download the kernel file you want to flash from whichever kernel developer you'd like
Place the file in your fastboot folder
Open a command prompt within that folder and run
Code:
fastboot flash kernel kernel_binary
kernel_binary will be replaced with whatever the file name (ie fk-r5.gz for Franco's Kernel)
Reboot your device.
Special Note: You may lose root if you had SuperSU pre-installed, you will need to re root following Section 4 (How to Root via Fastboot)
[SIZE=+1]8. How To Flash The Factory Images (And Return To Stock)[/SIZE]
Prerequisites: unlocked bootloader (section 1).
This section will explain how to return the phone to be like it was when it came out of the box. This will wipe everything from the phone. If you wish to flash the factory images without wiping your personal data from the internal storage please move on to the next section.
Download the appropriate factory images for your model https://developers.google.com/android/images
Unzip the marlin-xxxxxx-factory-xxxxxxxx (marlin-nmf26o-factory-4f68765c) into a directory on your PC (for this guide we'll use C:\marlin\).
Once unzipped you should have a folder named marlin-xxxxxx (marlin-nmf26o).
Move the contents of this folder into your Fastboot/ADB environment so that you can run fastboot and adb commands. (Note: I do the opposite and move the most current fastboot and ADB from the Android SDK into this folder)
Look for the windows batch file named "flash-all.bat" and double click on it. This should begin the proper full clean flash of all images back to stock. This should take a few minutes, but eventually your phone should reboot on its own and take you to the Android set up screen.
If you wish to you can also relock the bootloader with this command:
Code:
fastboot flashing lock
(This command will wipe all user data from the device)
Important: do not lock the bootloader unless you have first flashed the stock images. Locking the bootloader while you have a custom recovery installed can result in a brick. Please also note that the locking procedure will wipe all user data from the device.
Once all commands/flashes are complete you can reboot the device:
Code:
fastboot reboot
[size=+4]Frequently Asked Questions[/size]
1. How do I boot into the bootloader?
Power off your device. Once it's powered off hold power + volume down and the phone will boot into the bootloader. You can also use the following adb command:
Code:
adb reboot bootloader
2. When issuing the fastboot flashing unlock command it doesn't work, I only get a list of possible commands. What's going on?
This is usually due to having an outdated adb/fastboot setup. If you installed adb/fastboot by any means other than via the Android SDK this is probably the cause. Visit the prerequisites section in the beginning of this guide to properly install adb/fastboot and ensure that it's up to date.​
3. After unlocking the bootloader I get a message that says "Your device software can't be checked for corruption. Please lock the bootloader". What's going on? Can I get rid of it?
This is nothing to worry about, it's normal to see this when you have an unlocked bootloader. You can't remove it, as long as your bootloader is locked it will stay there.​
4. How do I take an OTA or update if I have root or other system modifications on the stock ROM?
You can't take an OTA update while you have root or any system modifications. You'd need to use fastboot to flash the system, boot, and recovery images. It's much easier to just flash the newer build with fastboot.​
5. Does taking an OTA update wipe my user data?
No, it doesn't.​
6. Do I need to flash the userdata.img from the factory images?
You should never flash the userdata image. It doesn't take into consideration the storage capacity of the device and always allocates 32gb of storage. This is ok for the 32gb model, but for the 64gb and 128gb models you'll end up with much less storage capacity than you should have. If you wish to wipe your internal storage you'd use the following command instead:
Code:
fastboot format userdata
More to come, special thanks to @Heisenberg for his excellent guide format​
Reservation
Don't forget to pin this
Dude, awesome
Looking good @bajasur!
Nice! Great job...should definitely be pinned
Thanks so much @bajasur! I always used the one by the famous @Heisenberg for the 6P and its great to have one for the Pixel XL.
Any plans to also include the step-by-step for restoring back to stock?
MinimalistChris said:
Thanks so much @bajasur! I always used the one by the famous @Heisenberg for the 6P and its great to have one for the Pixel XL.
Any plans to also include the step-by-step for restoring back to stock?
Click to expand...
Click to collapse
Yes, there is a lot more to come. For now to restore to stock I recommend running the flash-all.bat file that comes within the factory image folder.
A detailed step by step image flashing guide will be linked in the next few days.
Sent from my Pixel XL using XDA-Developers mobile app
Thanks @bajasur! We can still use this to unlock and root from NDE63X correct?
oneandroidnut said:
Thanks @bajasur! We can still use this to unlock and root from NDE63X correct?
Click to expand...
Click to collapse
Negative
For Verizon you need to follow the unlock method provided by DePixel Devs. Once you have unlocked the rooting and twrp methods should work.
Sent from my Pixel XL using XDA-Developers mobile app
bajasur said:
Negative
For Verizon you need to follow the unlock method provided by DePixel Devs. Once you have unlocked the rooting and twrp methods should work.
Sent from my Pixel XL using XDA-Developers mobile app
Click to expand...
Click to collapse
Sorry I should have clarified it is a Google Store edition just with verizon sim and X software. I can just unlock it like normal correct?
oneandroidnut said:
Sorry I should have clarified it is a Google Store edition just with verizon sim and X software. I can just unlock it like normal correct?
Click to expand...
Click to collapse
Yep! That should work fine ☺
Sent from my Pixel XL using XDA-Developers mobile app
bajasur said:
Yep! That should work fine
Sent from my Pixel XL using XDA-Developers mobile app
Click to expand...
Click to collapse
Awesome I am trying to wait until TWRP is stable but im inpatient lol
So this is not the correct guide for a Verizon Pixel is it? Besides the sunshine website has anyone made a guide like this yet for the Verizon model
aholeinthewor1d said:
So this is not the correct guide for a Verizon Pixel is it? Besides the sunshine website has anyone made a guide like this yet for the Verizon model
Click to expand...
Click to collapse
Other than flashing dePixel8 to allow bootloader unlocking, all other steps are identical.
aholeinthewor1d said:
So this is not the correct guide for a Verizon Pixel is it? Besides the sunshine website has anyone made a guide like this yet for the Verizon model
Click to expand...
Click to collapse
I'll clarify in the OP regarding Verizon devices but yes that should be the case
Sent from my Pixel XL using XDA-Developers mobile app
Does rooting without TWRP cause bootloops on NDE63V? I tried it with the all-in-one tool and couldn't get my Pixel to boot past the 4 dots when I was on NDE63V.
I have since flashed the Npf26j update. Would it be safe to root via chainfire's method? Wanted to avoid TWRP for now incase I get the data drain bug.
Thanks!

Categories

Resources