Database Users

[TUTO+VIDEO] Unlock Bootloader-Flash Recovery-Root-Restore Back the N7 FLO- KK 4.4.4

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.

[GUIDE] Unlock/Root/Flash for OnePlus One

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

Nice guide!
Sent from my One using Tapatalk

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[SIZE=+3]Heisenberg's How-To Guide For Beginners[/SIZE]
[SIZE=+2]Nexus 5X[/SIZE]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[SIZE=+1]Intro[/SIZE]
This thread will serve as a location for basic how-to guides for the Nexus 5X. I'm going to start off with a couple of the more obvious ones and go from there. If anyone has any suggestions for additions please feel free to let me know.
If you're unsure about something please read the FAQ section in post #2 before creating a post to ask a question.
[size=+1]Prerequisites[/size]:
You'll need a working adb/fastboot environment on your PC to get through some of these guides. Below are two options for install.
Please do not install adb/fastboot via any means other than the Android SDK, using other tools (like Minimal adb & fastboot) can lead to an outdated setup and various problems with flashing. You've been warned, other tools will not be supported in this thread.
Option A
Google hosts ADB/Fastboot (platform-tools) for Windows, OSX, and Linux. This is a minimal download, in contrast to Option 2. These links and file sizes may be updated periodically by Google. If using Windows, download the Google USB Driver and follow the driver install instructions. Once you have downloaded the platform-tools zip, extract the file then transfer the platform-tools folder to your desktop. The platform-tools folder contains adb, fastboot, and several other files. Note that clicking any link for platform-tools will immediately start a download.
*Windows: platform-tools. Google USB Driver install.
*OSX: platform-tools. For additional details on how to use OSX and adb/fastboot commands, see post #3.
*Linux: platform-tools.
See Option B below for old method to install adb/fastboot:
Option B
Go here to download the Android SDK, which will give you most updated version of adb and fastboot. Scroll to the bottom of the page and find Other Download Options>SDK Tools Only, and grab the right version for your OS. While it's downloading create a folder in C:\ called SDK (C:\SDK). Once you've downloaded the zip you can extract it into your C:\SDK folder. Navigate to C:\SDK\android-sdk-windows and open SDK Manager.exe. In SDK Manager you need to install the following packages:
Tools> Android SDK Tools, Android SDK Platform-tools
Extras> Android Support Repository, Google USB Driver
Once you have installed those, inside C:\SDK you should see some new folders, one of them will be called platform-tools, within that folder you should see fastboot.exe and adb.exe. I'll refer to this as your fastboot folder/directory or working folder/directory during this guide.
For Option A and B, make sure adb is correctly installed. Open a command prompt from within your fastboot folder (hold shift + right click, select open command prompt here) and issue this command:
Code:
adb version
If it returns a version number for Android Debug Bridge then you're good to go.
You can test adb by connecting your device to your PC while booted into Android (making sure that adb/usb debugging is enabled in Settings>Developer Options) with the screen unlocked and issuing this command:
Code:
adb devices
It should return your device serial number, if so, adb is working.
You can test fastboot by connecting your device to your PC while booted into the bootloader (power + volume down) and issuing this command:
Code:
fastboot devices
It should return your device serial number, if so, fastboot is working.
By attempting any of the processes listed this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches on fire, or turns into a hipster and claims to have been modified before it was cool.
[SIZE=+1]Quick Tips[/SIZE]
How to boot into the bootloader:
Power off your device. Once it's powered off hold power + volume down and the phone will boot into the bootloader. You can also use the following adb command:
Code:
adb reboot bootloader
You can also use an app called Quick Boot to boot into the bootloader directly from Android (root required).
How to boot into recovery:
Boot into the bootloader (see above), use the volume keys to scroll through the options and use the power button to select the recovery mode option. You can also use the following adb command:
Code:
adb reboot recovery
You can also use an app called Quick Boot to boot into the recovery directly from Android (root required).
[SIZE=+1]Index[/SIZE]
How To Unlock Your Bootloader
How To Install A Custom Recovery On Your Device
How To Decrypt Your Data Partition
How To Make A Nandroid Backup With TWRP Recovery
How To Make An EFS Backup With TWRP Recovery
How To Root
How To Install A ROM with TWRP Recovery
How To Install A Custom Kernel With TWRP Recovery
How To Update To A New Build Of The Stock ROM
How To Flash The Factory Images (Return To Stock)
How To Flash The Factory Images (Return To Stock But Leaving Internal Storage Intact)
FAQ can be found in post #2!
[SIZE=+1]1. How To Unlock Your Bootloader[/SIZE]
Go into Settings/About Phone, scroll down and click on ?build number? continuously until you see a toast notification telling you that you've enabled Developer Options. Go back to your Settings menu and enter Developer Options, scroll down and click on the ?Enable OEM Unlock? checkbox, also make sure you enable USB Debugging while you're in the Developer Options menu.
Power off your phone then boot into the bootloader (power + volume down).
Connect your phone to your PC via usb cable.
Open a command prompt from within your fastboot folder (navigate to where you have fastboot.exe located on your PC, shift + right click anywhere within that folder, select open command prompt here).
Check your fastboot connection by issuing this command:
Code:
fastboot devices
It should return your device serial number, if not you need to make sure your drivers are installed correctly.​
Once you've confirmed your fastboot connection issue this command:
Code:
fastboot oem unlock
This will erase all user data from the device!
You should now see a screen on your phone asking you to confirm this action, use the volume keys to scroll and the power key to confirm if you're sure you want to go ahead.
Allow the process to complete and then issue this command:
Code:
fastboot reboot
Allow everything to go ahead and once finished you can disconnect your usb cable.
Important: do not relock your bootloader unless your phone is fully stock. You must flash the factory images first in order to remove root and custom recovery (if you have them), if this precaution isn't taken you may end up with a brick. Please see section 10 of this guide for full instructions on how to return to stock.
[SIZE=+1]2. How To Install A Custom Recovery On Your Device[/SIZE]
Prerequisites: unlocked bootloader (section 1). Please read FAQ #7 if using TWRP 3.0.2-1 or 3.0.2-2.
Download TWRP Recovery onto your PC.
Make sure you check the md5 to verify its integrity (where possible).
Place the file in your fastboot folder (this is where fastboot.exe is located on your PC).
Power off your phone then boot into the bootloader (power + volume down).
Open a command prompt from within your fastboot folder (navigate to where you have fastboot.exe located on your PC, shift + right click anywhere within that folder, select open command prompt here), enter this command:
Code:
fastboot flash recovery filename.img
(The recovery filename in the command will change depending on which recovery you're flashing)
Use the volume keys to scroll and power key to select the Reboot Bootloader option. Once the phone has booted back into the bootloader, use the volume keys to scroll and the power key to boot into your newly flashed recovery. It's now safe to disconnect your usb cable. If using Nougat 7.0 or newer, you must now boot directly into TWRP and flash SuperSU (or your preferred root alternative) so that TWRP will persist between reboots.
When TWRP boots up you'll be asked whether you want to allow system modifications or to keep it read-only, choose to allow system modifications, there's no benefit to keeping it read-only.
Do not flash the version of SuperSU that TWRP offers to flash for you in order to give you root, it is not compatible and will cause problems. When you attempt to reboot out of TWRP it will tell you that it's detecting that you don't have root and it will offer to root for you, skip past this.
Some users need a custom recovery for a temporary period, so they live boot the recovery. In this scenario, the custom recovery replaces the stock recovery until a reboot is performed. Place the file in your fastboot folder then enter this command:
Code:
fastboot boot filename.img
(The recovery filename in the command will change depending on which recovery you're flashing)
[SIZE=+1]3. How To Decrypt Your Data Partition[/SIZE]
This is no longer necessary as long as you use TWRP 2.8.7.1 or newer
Prerequisites: unlocked bootloader (section 1).
TWRP recovery cannot decrypt your data partition at this stage. In order for TWRP to be able to read/write on your data partition (to root or create a nandroid backup) you will need to format it, a format will remove encryption.
Boot into the bootloader and connect your phone to your PC via usb cable.
Open a command prompt from within your fastboot folder (navigate to where you have fastboot.exe located on your PC, shift + right click anywhere within that folder, select open command prompt here), enter this command:
Code:
fastboot format userdata
Please note: this will erase all user data from the device!
Once the process has completed you can either reboot normally:
Code:
fastboot reboot
Or you can reboot back to the bootloader in order to undertake another task:
Code:
fastboot reboot-bootloader
[SIZE=+1]4. How To Make A Nandroid Backup With TWRP Recovery[/SIZE]
Prerequisites: unlocked bootloader (section 1), TWRP recovery (section 2).
A nandroid backup is a very important thing to have before installing any custom software on your device. It's basically a backup of your stock system that you can fall back on if anything goes wrong or if you just want your stock ROM back. You can also use the backup tool to create a backup of your favourite ROM set up exactly the way you like it. The backup you create can be easily restored using the restore tool in TWRP recovery.
Boot TWRP recovery, select the backup option from the TWRP home screen, check the system/data/boot boxes, and swipe to backup. The process will take a few minutes.
[SIZE=+1]5. How To Make An EFS Backup With TWRP Recovery[/SIZE]
An EFS backup is very important to have, if your EFS partition becomes corrupt you will have no IMEI, and therefore will not be able to use the phone as a phone. Making an EFS backup is insurance against this catastrophic event. Without a backup, restoring your EFS can be extremely difficult or impossible. The backup you create can be easily restored using the restore tool in TWRP recovery.
Please read FAQ #7 if using TWRP 3.0.2-1 or 3.0.2-2. Boot into TWRP and select the backup option from the TWRP home screen, make sure only the EFS box is selected, and swipe to backup. The process will take a few seconds. Keep a copy of the backup on your phone and also keep another copy somewhere safe.
[SIZE=+1]6. How To Root[/SIZE]
Prerequisites: unlocked bootloader (section 1), TWRP recovery (section 2).
Download the latest root method of your choosing to your phone:
Magisk
SuperSU Stable
SuperSU Service Release (SuperSU beta channel)
Or to root Android Nougat 7.0 visit this thread: Use SuperSU 2.78 or newer.
[WIP] Android N Preview
Boot into TWRP recovery and enter the install menu.
Navigate to where you have SuperSU stored on your internal storage and select it.
Swipe to install.
Once you've installed SuperSU you'll have an option to wipe cache/dalvik and an option to reboot system. Wipe the cache/dalvik, hit the back button, and hit the reboot system button. That's it.
Do not flash the version of SuperSU that TWRP offers to flash for you in order to give you root, it is not compatible and will cause problems. When you attempt to reboot out of TWRP it will tell you that it's detecting that you don't have root and it will offer to root for you, skip past this. You do have root, ignore this every time it comes up.
[SIZE=+1]7. How To Install A ROM with TWRP Recovery[/SIZE]
Prerequisites: unlocked bootloader (section 1), TWRP recovery (section 2), vendor.img (section 9).
Installing a ROM is a straight forward and easy process. Before you install anything you should make a nandroid backup (instructions above). Next, install the vendor.img that matches the Google security OTA that the ROM you want to install is based on. Find the vendor.img inside the factory images provided by Google then flash this file with fastboot (section 9).
Download a ROM and appropriate Gapps package and place on your device.
Boot into your custom recovery.
Select the wipe option from the TWRP home screen.
Perform a Factory Reset.
Select advanced wipe.
Check the system, data, cache, and dalvik cache options.
Swipe to wipe.
Install the ROM.
Select the install option from the TWRP home screen.
Navigate to where you have the ROM zip stored on your sd card and select it.
Swipe to install.
Most ROMs will run an installer script at this point but some ROMs have what is called an Aroma Installer which allow you to choose some install options before the script runs.​
You will also need to install the appropriate gapps package directly after installing the ROM.
Once you've installed all necessary zips you'll have an option to wipe cache/dalvik and an option to reboot system. Wipe the cache/dalvik, hit the back button, and hit the reboot system button.
[SIZE=+1]8. How To Install A Custom Kernel With TWRP Recovery[/SIZE]
Prerequisites: unlocked bootloader (section 1), TWRP recovery (section 2).
A custom kernel can open up a new level of control over your device, such as overclocking/underclocking, undervolting, changing governors, changing I/O schedulers, adjusting colour calibrations, adjusting sound calibrations, and many other options.
Download a kernel that is compatible with your current ROM.
Check the md5 to verify its integrity.
Enter TWRP recovery.
Select the install option from the TWRP home screen.
Navigate to the kernel and select it.
Swipe to install.
You'll have an option to wipe cache/dalvik and an option to reboot system. Wipe the cache/dalvik, hit the back button, and hit the reboot system button.
Once your phone has booted up you can use a kernel tuning app to change governors, I/O scheduler, clock speed, and other options. Some of the popular kernel apps are Kernel Auditor, EX Kernel Manager, Trickster Mod, No Frills, Kernel Tuner, and many more.
[SIZE=+1]9. How To Update To A New Build Of The Stock ROM[/SIZE]
Prerequisites: unlocked bootloader (section 1).
This method does not wipe your data, so you will keep your apps and settings. You should have no problems, however, if you experience problems you may need to perform a factory reset and flash again. Make a backup first and transfer it to your PC.
Download the latest build via the appropriate factory images for your model (Nexus 5X/Bullhead) here.
Note: Android 7.1.2 and newer factory images do not contain cache.img. Do not wipe the cache.img for this process when using or moving to Android 7.1.2 or newer. If you have wiped cache.img, download the most recent Android 7.1.1 factory image and flash the cache.img from that zip archive.
Unzip the bullhead-xxxxxx-factory-xxxxxxxx (x's replace variables) into a directory on your PC (for this guide we'll use C:\bullhead\).
Once unzipped you should have a folder named bullhead-xxxxxx (x's replace variables). Open it and move the following files to a new directory named C:\bullhead\images\:
bootloader-bullhead-bullhead-xx.xx.img
radio-bullhead-bullhead-xx.xx.img
(Please note that radio and bootloader naming changes from build to build so the filenames and below commands will change with them)
Within C:\bullhead\bullhead-xxxxxx\ you'll see another zip archive named image-bullhead-xxxxxx, unzip the contents of that zip into the C:\bullhead\images\ folder we created before. Now within C:\bullhead\images\ you should have the following files:
android-info.txt
boot.img
bootloader-bullhead-bullhead-xx.xx.img
cache.img
radio-bullhead-bullhead-xx.xx.img
recovery.img
system.img
userdata.img
vendor.img
Boot into the bootloader and connect your phone to your PC via usb cable.
Open a command prompt from within your fastboot folder (navigate to where you have fastboot.exe located on your PC, shift + right click anywhere within that folder, select open command prompt here), enter these commands to flash:
Code:
fastboot flash bootloader C:\bullhead\images\bootloader-bullhead-bullhead-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\bullhead\images\radio-bullhead-bullhead-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\bullhead\images\boot.img
fastboot erase cache
fastboot flash cache C:\bullhead\images\cache.img
fastboot flash recovery C:\bullhead\images\recovery.img
fastboot flash system C:\bullhead\images\system.img
fastboot flash vendor C:\bullhead\images\vendor.img
You can skip flashing the recovery if you wish, but even if you do the stock recovery may be patched on the first boot anyway. So you'll need to flash TWRP and SuperSU again if you need/want those, as well as any other system modifications you may have had.
You'll have to flash SuperSU again now, plus add any mods that you previously had.
[SIZE=+1]10. How To Flash The Factory Images (And Return To Stock)[/SIZE]
Prerequisites: unlocked bootloader (section 1).
This section will explain how to return the phone to be like it was when it came out of the box. This will wipe everything from the phone. If you wish to flash the factory images without wiping your personal data from the internal storage please move on to the next section.
Note: Android 7.1.2 and newer factory images do not contain cache.img. Do not wipe the cache.img for this process when using or moving to Android 7.1.2 or newer. If you have wiped cache.img, download the most recent Android 7.1.1 factory image and flash the cache.img from that zip archive.
Go to Settings/Backup & Reset and perform a factory data reset. This will remove all of your user data from the device (apps, settings, photos, music, etc).
Download the appropriate factory images for your model here.
Unzip the bullhead-xxxxxx-factory-xxxxxxxx (x's replace variables) into a directory on your PC (for this guide we'll use C:\bullhead\).
Once unzipped you should have a folder named bullhead-xxxxxx (x's replace variables). Open it and move the following files to a new directory named C:\bullhead\images\:
bootloader-bullhead-bullhead-xx.xx.img
radio-bullhead-bullhead-xx.xx.img
(Please note that radio and bootloader naming changes from build to build so the filenames and below commands will change with them)
Within C:\bullhead\bullhead-xxxxxx\ you'll see another zip archive named image-bullhead-xxxxxx, unzip the contents of that zip into the C:\bullhead\images\ folder we created before. Now within C:\bullhead\images\ you should have the following files:
android-info.txt
boot.img
bootloader-bullhead-bullhead-xx.xx.img
cache.img
radio-bullhead-bullhead-xx.xx.img
recovery.img
system.img
userdata.img
vendor.img
Boot into the bootloader and connect your phone to your PC via usb cable.
Open a command prompt from within your fastboot folder (navigate to where you have fastboot.exe located on your PC, shift + right click anywhere within that folder, select open command prompt here), enter these commands to flash:
Code:
fastboot flash bootloader C:\bullhead\images\bootloader-bullhead-bullhead-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\bullhead\images\radio-bullhead-bullhead-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\bullhead\images\boot.img
fastboot erase cache
fastboot flash cache C:\bullhead\images\cache.img
fastboot flash recovery C:\bullhead\images\recovery.img
fastboot flash system C:\bullhead\images\system.img
fastboot flash vendor C:\bullhead\images\vendor.img
If you wish to you can also relock the bootloader with this command:
Code:
fastboot oem lock
(This command will wipe all user data from the device)
Important: do not lock the bootloader unless you have first flashed the stock images. Locking the bootloader while you have a custom recovery installed can result in a brick. Please also note that the locking procedure will wipe all data on an encrypted device.
Once all commands/flashes are complete you can reboot the device:
Code:
fastboot reboot
[SIZE=+1]11. How To Flash The Factory Images (Return To Stock But Leaving Internal Storage Intact)[/SIZE]
Prerequisites: unlocked bootloader (section 1), TWRP recovery (section 2). Note: Android 7.1.2 and newer factory images do not contain cache.img. Do not wipe the cache.img for this process when using or moving to Android 7.1.2 or newer. If you have wiped cache.img, download the most recent Android 7.1.1 factory image and flash the cache.img from that zip archive.
This section will explain how to return the phone to be like it was when it came out of the box, except it will not wipe any of your personal data (photos, music, etc) from the internal storage.
Download the appropriate factory images for your model here.
Unzip the bullhead-xxxxxx-factory-xxxxxxxx (x's replace variables) into a directory on your PC (for this guide we'll use C:\bullhead\).
Once unzipped you should have a folder named bullhead-xxxxxx (x's replace variables). Open it and move the following files to a new directory named C:\bullhead\images\:
bootloader-bullhead-bullhead-xx.xx.img
radio-bullhead-bullhead-xx.xx.img
(Please note that radio and bootloader naming changes from build to build so the filenames and below commands will change with them)
Within C:\bullhead\bullhead-xxxxxx\ you'll see another zip archive named image-bullhead-xxxxxx, unzip the contents of that zip into the C:\bullhead\images\ folder we created before. Now within C:\bullhead\images\ you should have the following files:
android-info.txt
boot.img
bootloader-bullhead-bullhead-xx.xx.img
cache.img
radio-bullhead-bullhead-xx.xx.img
recovery.img
system.img
userdata.img
vendor.img
Boot into TWRP recovery and enter the wipe menu, select advanced wipe, check only the data box and swipe to wipe.
Go to the TWRP main menu and enter the reboot menu, select bootloader. The phone will now boot into the bootloader, once it has you can connect your phone to your PC via usb cable.
Open a command prompt from within your fastboot folder (navigate to where you have fastboot.exe located on your PC, shift + right click anywhere within that folder, select open command prompt here), enter these commands to flash:
Code:
fastboot flash bootloader C:\bullhead\images\bootloader-bullhead-bullhead-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\bullhead\images\radio-bullhead-bullhead-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\bullhead\images\boot.img
fastboot erase cache
fastboot flash cache C:\bullhead\images\cache.img
fastboot flash recovery C:\bullhead\images\recovery.img
fastboot flash system C:\bullhead\images\system.img
fastboot flash vendor C:\bullhead\images\vendor.img
Once all commands/flashes are complete you can reboot the device:
Code:
fastboot reboot
FAQ can be found in post #2!
Donate To Me

[size=+1]Frequently Asked Questions[/size]
1. How do I boot into the bootloader?
Power off your device. Once it's powered off hold power + volume down and the phone will boot into the bootloader. You can also use the following adb command:
Code:
adb reboot bootloader
You can also use an app called Quick Boot to boot into the bootloader directly from Android (root required).
2. How do I boot into recovery?
Boot into the bootloader (see above), use the volume keys to scroll through the options and use the power button to select the recovery mode option. You can also use the following adb command:
Code:
adb reboot recovery
You can also use an app called Quick Boot to boot into the recovery directly from Android (root required).
3. When issuing the fastboot flashing unlock command it doesn't work, I only get a list of possible commands. What's going on?
This is usually due to having an outdated adb/fastboot setup. If you installed adb/fastboot by any means other than via the Android SDK this is probably the cause. Visit the prerequisites section in the beginning of this guide to properly install adb/fastboot and ensure that it's up to date.
4. How do I take an OTA or update if I have root or other system modifications on the stock ROM?
You can't take an OTA update while you have root or any system modifications. You'd need to use fastboot to flash the system, boot, and recovery images. It's much easier to just flash the newer build with fastboot, see section 9 of this guide for full instructions.
5. Does taking an OTA update wipe my user data?
No, it doesn't.
6. Do I need to make an EFS backup?
Absolutely yes. An EFS backup is extremely important. If your EFS partition becomes corrupt, your IMEI will disappear and you will not be able to use the phone as a phone. Without a backup it can be extremely difficult (or impossible) to restore your EFS. See the next question for an EFS backup related issue and solution.
7. I have a bootloop after restoring my EFS backup in TWRP 3.0.2-1. What can I do?
TWRP 3.0.2-1 and 3.0.2-2 are the first official TWRP releases with Nougat 7.0 or newer compatibility. Unfortunately, there are separate bugs affecting TWRP 3.0.2-1 and 3.0.2-2. A member of the TWRP development team details these issues right here. This link redirects to a thread in the Nexus 6P forums but also applies to the Nexus 5X. Read the original post of that same thread to learn how to resolve this EFS restore bootloop. You must use ADB and the phone must be booted in TWRP to resolve this issue. These ADB commands work on the Nexus 5X and 6P.
8. Can I flash just the xxxxxx.img from the factory image without losing my data?
Flashing userdata.img will format your entire phone (personal data including SMS/MMS, pictures, downloaded files, etc). You can flash any combination of these partitions (boot, system, vendor, radio, or bootloader) and this will leave your personal data intact. However, any mods that you have installed into system, vendor, or boot will be overwritten and returned to the default factory image setup when you flash these partitions. Flashing recovery.img or a newer version of your custom recovery will replace your existing recovery.
9. After updating my ROM, I get this message on every boot: "There's an internal problem with your device. Contact your manufacturer."
This warning indicates a mismatched vendor and system partition. The vendor partition was formerly integrated in the system partition for previous Nexus devices but is now a separate partition that must be flashed for each Google security update. Download a factory image and update your vendor partition using fastboot so that it matches your rom's OS build and monthly security update. If you have a file explorer installed on your phone, you can determine which vendor.img is installed by navigating to /vendor/build.prop and clicking on the build.prop. The specific vendor installed will be a combination of six numbers and letters listed in all capitals (example: NMF26F) in the ro.vendor.build.fingerprint line. These will always match up with the factory image of the same Android build (six digit alphanumeric name) for this device.
Vendor.img is specific to each OTA and contains proprietary binaries for the phone that regularly receive updates to resolve security risks. If you are a custom rom user, make sure that you flash the vendor.img for the Google monthly security update that you are moving to. Be aware that sometimes AOSP roms utilize the AOSP master branch which has a newer Android build than the monthly security update for this device. You will still need to install that month's vendor.img.
The phone will fail to boot if you mismatch the vendor.img with a different Android version. For instance, a 6.0 Marshmallow vendor.img will not allow your phone to boot on 7.0 Nougat. The vendor.img is typically not included in the custom rom zip but is often available as a separate download in the custom rom thread's first post.

Reserved #2

Reserved #3

OSX, ADB and Fastboot commands!
So you use OSX and would like to use ADB/fastboot, unlock, root, or simply have a working knowledge of your phone. Welcome! Most of the information in the guide above applies to OSX, however there are a few key changes.
Google hosts ADB/Fastboot (platform-tools) for Windows, OSX, and Linux. This is a minimal download, however these links and file sizes may be updated periodically by Google. Download the OSX platform-tools. Note that clicking the link for platform-tools will immediately start a download.
*OSX: platform-tools.
Once you have downloaded the platform-tools zip, extract the file then transfer the platform-tools folder to your desktop. The platform-tools folder contains adb, fastboot, and several other files.
To make sure your ADB is installed correctly, open a terminal command prompt and issue this cd command (change directory) to the platform-tools folder:
Code:
cd /users/username/desktop/platform-tools
then issue this command to check your adb version:
Code:
./adb version
If it returns a version number for Android Debug Bridge then you're good to go.
Using ADB/Fastboot commands
OSX natively requires "./" to prefix any ADB or Fastboot commands. If following the guide in post #1, commands issued in OSX must be written as follows ./adb [command] or ./fastboot [command]. Below are example scenarios.
To check if your device sees ADB, enable USB Debugging from within Android in Settings/Developer options. Go into Settings/About Phone, scroll down and click on build number continuously until you see a toast notification telling you that you've enabled Developer Options. Go back to your Settings menu and enter Developer Options, scroll down and enable USB Debugging.
Code:
./adb devices
It should return your device serial number, if so, adb is working.
Reboot into the bootloader:
Code:
./adb reboot bootloader
Reboot into the recovery:
Code:
./adb reboot recovery
Fastboot commands must be performed while in the bootloader. Power off your phone then boot into the bootloader (power + volume down). Below are some example OSX fastboot commands that can be used throughout the guide:
Check if your device sees fastboot:
Code:
./fastboot devices
Install a factory image:
cd into the platform-tools folder with the following command:
Code:
cd /users/username/desktop/platform-tools
Now enter commands to flash a factory image:
Code:
./fastboot flash bootloader /users/username/desktop/bullhead/images/bootloader-bullhead-bullhead-xx.xx.img
./fastboot reboot-bootloader
./fastboot flash radio /users/username/desktop/bullhead/images/radio-bullhead-bullhead-xx.xx.img
./fastboot reboot-bootloader
./fastboot flash boot /users/username/desktop/bullhead/images/boot.img
./fastboot erase cache
./fastboot flash cache /users/username/desktop/bullhead/images/cache.img
./fastboot flash recovery /users/username/desktop/bullhead/images/recovery.img
./fastboot flash system /users/username/desktop/bullhead/images/system.img
./fastboot flash vendor /users/username/desktop/bullhead/images/vendor.img

@Heisenberg you mind if i create an index thread?

reyscott1968 said:
@Heisenberg you mind if i create an index thread?
Click to expand...
Click to collapse
Go right ahead, first in best dressed as far as I'm concerned. It is a fair bit of work to keep an index maintained though, as long as you're aware. There's a new template for indexes too, using your Google goggles you should be able to track it down pretty easily.

Heisenberg said:
Go right ahead, first in best dressed as far as I'm concerned. It is a fair bit of work to keep an index maintained though, as long as you're aware. There's a new template for indexes too, using your Google goggles you should be able to track it down pretty easily.
Click to expand...
Click to collapse
il take note.. il update the thread once im back on my pc.. now still at work ...

Deleted...
Should have read the first lines in the OP

Cant wait, should have mine around october 30th.

Might want to point out the cable /adapter required to connect to pc. (I just saw that it's not included with the phone.)

AquilaDroid said:
Might want to point out the cable /adapter required to connect to pc. (I just saw that it's not included with the phone.)
Click to expand...
Click to collapse
I picked up a few of these to get me by for now until the price of Type-C goes down a bit http://www.ebay.com/itm/381344035966

I ordered one along with my phone, will be helpful for flashing.

Thanks, a friend of mine pre order this phone, I'll follow these steps

Thanks for starting this, these were some of the most helpful threads in the N5 forum.
For Mac users who have upgraded to El Capitan, the adb/fastboot installation doesn't necessarily work perfectly right now. I'm sure the Android SDK package will update for this, but in the mean time:
Install adb/fastboot as usual similar to this thread, or for specifics:
http://forum.xda-developers.com/showthread.php?t=1917237
but, once you test this with [adb devices] or [fastboot devices] you'll most likely get a command not found error.
You'll need to add a line to your ~/.bash_profile, per this reddit thread
add the following line to your ~/.bash_profile, changing username to your mac username
Code:
export PATH="/usr/local/lib/node_modules:/usr/local/apache-maven-3.0.3/bin:/Users/[B]username[/B]/.composer/vendor/bin:/Users/[B]username[/B]/Library/Android/sdk/platform-tools:$PATH"
exit, save, then run
Code:
source ~/.bash_profile
then adb/fastboot should be good to go like before!

OP has best username ever
Sent from my Nexus 5 using Tapatalk

Doesn't work!
Code:
C:\Users\Kevin\Downloads\Nexus 5x>fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.017s
C:\Users\Kevin\Downloads\Nexus 5x>fastboot flashing unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.014s
C:\Users\Kevin\Downloads\Nexus 5x>fastboot flashing unlock_critical
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.011s
C:\Users\Kevin\Downloads\Nexus 5x>fastboot flashing get_unlock_ability
...
(bootloader) get_unlock_ability: 0
OKAY [ 0.020s]
finished. total time: 0.022s

The-Kevster said:
Doesn't work!
Click to expand...
Click to collapse
Did you allow OEM Unlock in developer options?
Go into Settings/About Phone, scroll down and click on “build number” continuously until you see a toast notification telling you that you've enabled Developer Options. Go back to your Settings menu and enter Developer Options, scroll down and click on the “Enable OEM Unlock” checkbox, also make sure you enable USB Debugging while you're in the Developer Options menu.
Click to expand...
Click to collapse

Does the 5X have the hardware QFuse that that pops when you unlock the bootloader like the 6P?

KidWave said:
Does the 5X have the hardware QFuse that that pops when you unlock the bootloader like the 6P?
Click to expand...
Click to collapse
They both use Qualcomm based chips so yes the same thing would happen on the 5X.

[TUTORIAL][ZS550KL][ZS570KL/PRO] How to change device SKU to WW [29-09-2017]

Zenfone 3 Deluxe ZS550KL / ZS570KL / ZS570KL PRO
How to change device SKU to WW​Disclaimer
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about procedures,
* tools or terms in this thread before proceeding! YOU are choosing to
* make these modifications, and if you point the finger at me for
* messing up your device, I will laugh at you.
*/
The are two main reasons to change our SKU from TIM, CN or JP to WW. Firstly, the WW firmware is apparently getting OTA updates first. In second place, Marshmallow 6.0 Bootloader Unlock process requires 4.12.40.1698 firmware version and above, but only WW got the update (you may find this useless as 7.0 update is here, but some 6.0 users may need it). This will guide you in the process.
Warning!
Always have your original firmware, recovery and boot files in case things don't go as expected
Backup all of your personal data!
PLEASE MAKE SURE you are using the respective files for your CPU (ZS570KL SD820 2.15Ghz - ZS570KL PRO SD821 2.3GHz)
Prerequisites
Adb and Fastboot installed. I recommend you to install it from HERE.
Drivers installed. Try using these or Universal ADB Drivers
Python 2.X or 3.X installed.
WW target firmware. You can download it from the ASUS official website or from AndroidFileHost mirror: ZS570KL SD820 or ZS570KL PRO SD821.
Respective firmware stock recovery. You can download it from here: ZS570KL SD820 or ZS570KL PRO SD821
sdat2simg toolkit (you can find img2simg linux binary in second post).
Guide
In this case we are going to change a ZS570KL using the UL-Z016-WW-4.12.40.1698 firmware (the version needed to unlock the bootloader in Android 6.0) and it's respective recovery.
1. Extract the sdat2simg toolkit
Extract the sdat2simg_toolkit.rar and you will have this folder structure:
- sdat2simg_toolkit/
|-> bin / > necessary tools
|-> input/ > input system files
|-> output/ > output system files for flashing
|-> sdat2simg.bat > tool execution​2. Extract system files from firmware
Open the firmware zip and extract system.new.dat and system.transfer.list into the input folder.
{
"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"
}
​3. Run the tool
Now open the sdat2simg.bat file. There must no be trouble if you have properly installed python.
The tool will first convert the system.new.dat and system.transfer.list into a raw ext4 image, then it will be converted into a sparse flashable image.
When the process has finished, check the output folder. The system.img file is what we are interested in. This is our flashable system image.​4. Flash the WW system image
Now we need to reboot into bootloader mode. Turn off the device and press Volume up + Power button. Or by using adb command:
Code:
adb reboot bootloader
Now open a terminal inside output folder and flash the system image by using the fastboot command:
Code:
fastboot flash system system.img
5. Flash the WW recovery image
Then we are going to flash the WW recovery image. Open a terminal where you placed the recovery image and flash it by using fastboot command:
Code:
fastboot flash recovery Z016-WW-4.12.40.1698_recovery.img
5.a. (Optional) Flash WW boot image
You can optionally flash the WW boot image contained inside the firmware zip. Extract it, open a terminal next to the boot.img file and flash it by using the fastboot command:
Code:
fastboot flash boot boot.img
(Not tested)​6. Factory reset
Reboot your device by using fastboot command:
Code:
fastboot reboot
Wait until it boots up and power it off. Then boot to recovery mode: Volume down + Power button, wait for the "No command" sign
and keep pressed power button + tap Volume up to show the recovery menu.
To factory reset the device choose the following options:
Code:
Wipe data/factory reset
Wipe cache partition
7. Reboot!
Now you are all up! You can Reboot your device by choosing the Reboot device now option
and you will boot into your new WW firmware. If you changed to WW to unlock the bootloader now you are able to do it.
You can also download OTA updates for WW firmware or you can manually download it and place the firmware in the internal storage, reboot and a window will prompt asking to install the new firmware.​
Special thanks
@xpirt
@A.S._id

Additional Information
Building...
Building...
Building...
Building...
Building...

i need ZS550KL CN -> WW :angel:

ken2006i said:
i need ZS550KL CN -> WW :angel:
Click to expand...
Click to collapse
Just follow the steps... I have uploaded CN firmware to AndroidFileHost. I have not been able to find CN stock recovery image... but you can make a dump of yours (and share it!).. Follow this guide https://forum.xda-developers.com/showthread.php?t=2450045

Help me, please! During flash recovery appear this message: FAILED (remote: partition flashing is not allowed

elenanole said:
Help me, please! During flash recovery appear this message: FAILED (remote: partition flashing is not allowed
Click to expand...
Click to collapse
Are you flashing the stock recovery? Try flashing the system partition, reboot and the go to fastboot mode to flash the recovery.

sebastiandg7 said:
Are you flashing the stock recovery? Try flashing the system partition, reboot and the go to fastboot mode to flash the recovery.
Click to expand...
Click to collapse
Yes I want to flash stock recovery but when I try to flash system image once it went well and then when I tried to flash recovery image it came a message partition is not allowed. Now appear partition is protected.
Please you can explain well what I have to do exsactly? Sorry for my english but I thank you for help me.

sebastiandg7 said:
Are you flashing the stock recovery? Try flashing the system partition, reboot and the go to fastboot mode to flash the recovery.
Click to expand...
Click to collapse
this is error

elenanole said:
View attachment 4266710 this is error
Click to expand...
Click to collapse
Show me the exact command you are using. You must do this:
1. Flash the system.img image in the system partiton.
Code:
fastboot flash system system.img
2. Reboot your device and wait until it boots up.
3. Reboot to fastboot mode.
4. Flash the stock recovery image to the recovery partition.
Code:
fastboot flash recovery <stock recoery name>.img
If you need more help you can find me in Telegram as @sebastiandg7

hello to all the guys, before proceeding to the flash, i want to make a backup of my (TIM) recovery because i do not find it. How can I do? Where was stock WW recovery taken?
P.S. My phone is not rooted

xtia87x said:
hello to all the guys, before proceeding to the flash, i want to make a backup of my (TIM) recovery because i do not find it. How can I do? Where was stock WW recovery taken?
P.S. My phone is not rooted
Click to expand...
Click to collapse
Are you able to boot twrp recovery? (Not installing it, check this thread)

sebastiandg7 said:
Are you able to boot twrp recovery? (Not installing it, check this thread)
Click to expand...
Click to collapse
Yes, I'm able to start twrp without installing it. From here how do I save my original recovery?
edit: Sorry I made a mistake i can't boot twrp without installing... The error: FAILED (remote: unlock device to use this command) is there a way to save the recovery without unlocking the bootloader?

Hi, I've been able to make the move finally! And when it gave me a mistake, partition is not allowed was why I had to do a factory reset and clean everything because it seemed to be insufficient memory. Sorry for my english and I hope that I help you

Some one have sotck recovery Z016D_CN please give me .tks

sebastiandg7 said:
Are you able to boot twrp recovery? (Not installing it, check this thread)
Click to expand...
Click to collapse
Do I need to flash the recovery and the firmware in one go? Is there any order I must proceed in? Are you sure I don't need to unlock the bootloader first? ASUS told me the bootloader unlock app also works with my TIM branded version.
---------- Post added at 12:14 AM ---------- Previous post was at 12:10 AM ----------
Also, what do I do if I already have TIM firmware with Android 7? Can I still follow the steps in the tutorial, or how should I proceed? Can/must I downgrade to Android MM, and if yes how? Thanks in advance.

What about dat to img by stupdroid.com? Which is newer? Does it make a difference if i want to get oreo system image?
I tried both tools and dat to img by stupdroid makes a system image with 3,65 GB but sdat2simg 3,54 GB...

How To Guide [GUIDE][HowTo] Unlock and root Nothing Phone (1)

ANNOUNCEMENT: I'M STOPPING THE FOLLOW UP AND UPDATE OF THIS TOPIC TODAY, IF SOMEONE WANTS TO TAKE OVER, CONTACT THE MODERATOR IN THIS LINK.
THE TOPIC REMAINS AS IT IS AND WILL NOT BE UPDATED ANYMORE (BY ME ANYWAY!)
GOOD CONTINUATION TO ALL​
Hey everyone,
It's been a few days since the Phone(1) went on sale. And already, Nothing is doing things right by making the Phone(1) Kernel available. The next step was to unlock the bootloader and root it. Both are already available and ready to use.
So don't deprive yourself and here is the process of the two operations.
You've already unlocked the bootloader and rooted a carrierless variant of either a Google Pixel or OnePlus, you should have no problem unlocking your Nothing Phone (1) and installing Magisk. For those of you with a memory lapse, here is a tutorial to guide you through the process.
- Disclaimer: I don't take any responsibility for anything you do to your tablet, which is to transform it into brick, break, or transform it into coffee machine - ​
Click to expand...
Click to collapse
How to bootloader unlock and root the Nothing Phone 1​After unlocking the bootloader, you can use Magisk to root the device.
You must first unlock the bootloader in order to be able to start third-party software. Here's how to do it:
Step 1: Unlock the Nothing Phone 1’s bootloader​
Open the Settings app on your Nothing Phone 1.
Tap on About phone.
Locate the section named Software info and tap on it.
On the next screen, tap on the Build number 7 times until it says you’re now a developer.
Go back to the main Settings page, tap on System, and near the bottom of the list, you should see Developer options. Tap on it.
You should see an OEM unlocking option. Enable it. For security purposes, it may ask you to input your lock screen PIN/password if you have one set.
Scroll down a bit until you see USB debugging. Enable it as well.
Plug in your Nothing Phone 1 into your PC/Mac/Chromebook. Make sure you have the Latest version of ADB and Fastboot (33.0.3) binaries installed.
Now open up a terminal window/Command Prompt instance and enter the following command: adb devices
If you see your device’s serial number and it says “authorized,” then you’re good to go. If this is your first time setting up ADB for this device, then you may see a prompt on your phone to enable USB Debugging for your PC. Grant it permission.
If you’re having trouble getting your Windows PC to recognize your device, try installing the latest Android USB Drivers.
Now, reboot to the bootloader menu. You can either do this by holding the power and volume down buttons while booting up, or by entering the following ADB command: adb reboot bootloader
Once you’re on the bootloader menu, you’ll now have to switch to using fastboot command to communicate with your device. To unlock the Nothing Phone 1’s bootloader, enter the following command: fastboot flashing unlock
In case you need to flash low-level firmware partitions like the bootloader images, you will have to execute another command afterwards: fastboot flashing unlock_critical
[NOT A MANDATORY TO UNLOCK CRITICAL, IT'S FOR ME BETTER TO NOT USE THIS COMMAND, THIS COMMAND COULD BE THE REASON SOME PEOPLE HAVE BRICK OR NOT WHEN GO BACK STOCK NOS]
You should now see text on screen warning you about the potential risks of unlocking the bootloader. On the screen next to the power and volume buttons, you should see some text. Press the volume up key until it says “unlock the bootloader.” Once it says this, press the power button.
The phone will unlock the bootloader and reboot back to the bootloader menu. This time, the bootloader will show a red warning icon and “unlocked” text.
Now, reboot your phone back to the Android OS. You can do this by sending the following fastboot command: fastboot reboot
Congratulations, your Nothing Phone 1 now has an unlocked bootloader!
You’ll see a warning message that your phone’s bootloader is unlocked on every boot, but don’t worry about that as it doesn’t affect your day-to-day use.
Step 2 - Rooting your Nothing Phone 1 with Magisk​With an unlocked bootloader, you can now boot modified boot images. For Magisk to work, you’ll need to patch the Nothing Phone 1’s stock boot image.
Since your device has been wiped earlier, you’ll need to go back and re-enable Developer Options and then re-enable USB Debugging. Make sure your Nothing Phone 1 is still recognized by your PC.
Download the full OTA package corresponding to the installed software version on the Nothing Phone 1.
Depending of your model, you have Global or EEA (European) firmware availables.
You can download the latest full OTA firmware package here.
Extract the stock boot image from the OTA package. For more information, take a look the “You have access to the recovery-flashable ZIP file” section our “How to Install Magisk on your Android Phone” tutorial.
In case you don’t want to download the whole OTA file, you can separately download the boot image just to the post #2 or from this post. However, to avoid version mismatch and other unforeseen errors, it is always advised to extract the boot image yourself.
Now that we have the stock boot image to patch, push it to your device with this command: adb push <path_to_file> /sdcard/Download
Download and install the Magisk app on the Nothing Phone 1.
Open the Magisk app and tap on the Install button.
Choose Select and Patch a File. A file manager will pop up.
Select the boot image that you pushed earlier and let Magisk patch it.
Pull it off your phone with this command: adb pull /sdcard/Download/magisk_patched_[random_strings].img
Reboot the Phone 1 into the bootloader: adb reboot bootloader
Flash the patched boot image: fastboot flash boot /path/to/magisk_patched_boot.img
Reboot the phone: fastboot reboot
Open the Magisk app and your Nothing Phone 1 should be rooted.
Keep in mind that unlocking the bootloader and rooting your Nothing Phone 1 will impact how you take advantage of updates. You'll have to learn to manually load monthly security patch updates. But don't worry, it's easy enough to do.​
-=o#0#o=-​
WARNING: I wrote this step to allow you to re-lock your bootloader, but it seems that for this step, there are some problems. So after this warning, if you continue on this path, I could not be held responsible for what you will have as a result: soft-bricked, bootloop, etc.​
Spoiler: Relock the bootloader of your Phone(1)
menu. You can either do this by holding the power and volume down buttons while booting up, or by entering the following ADB command: adb reboot bootloader
[*]Once you’re on the bootloader menu, you’ll now have to switch to using fastboot command to communicate with your device. To unlock the Nothing Phone 1’s bootloader, enter the following command: fastboot flashing lock
[*]Reboot your phone back to the Android OS. You can do this by sending the following fastboot command: fastboot reboot
Many thanks to Skanda Hazarika for his tutorial which you can read on the xda news page.
And thanks to Qiyue_ for the 1st Boot Magisk Patched for the Phone1
#root #nothingphone

Unbricking Nothing phone 1: Flash Stock Firmware with Fastboot
- Disclaimer: I don't take any responsibility for anything you do to your tablet, which is to transform it into brick, break, or transform it into coffee machine -​
Click to expand...
Click to collapse
Warning : The process below will erase all the data on your device. So, I invite you to make a full backup of the device beforehand.
Unfortunately, as I don't own the Phone(1) yet, I am unable to take screenshots with the Phone(1) at the moment. As soon as I can, I will put them online to finalize the tutorial. Thank you for your understanding
STEP 1: What you need and read before the process.
It’s really important for a process without problems
Install Android SDK and the Platform-tools folder
Download the Nothing OS version you need (see this post)
Extract the "payload bin" file from the rom
Extract the Firmware Stock "boot.img" from the rom (see this tutorial)
Unlock the bootloader of your Phone(1) (see this tutorial)
STEP 2: Boot the bricked phone 1 into Fastboot mode
Very often, a soft-bricked or boot-looped device may already be in Fastboot mode. However, if you are stuck in a boot-loop, long press the Power key to turn it off.
Then press and hold the Power and Volume Down keys (or Power and Volume Up keys on some devices) simultaneously to boot your device into Fastboot mode.
In case you are unable to turn off your device, let the battery discharge. Once it is drained, connect it to the charger. Then, as soon as it is about to start, use the Power and Volume Up/Down keys and it will start directly in Fastboot mode.
STEP 3: Format the device via Fastboot
1.Go to the platform-tools folder where the extracted ROM is located.
2.Then go to its address bar, type CMD in its address, and press Enter. This will launch the CMD window.
3.Now run the following command to perform a factory reset (optional but recommended)
Code:
fastboot -w
STEP 4: Flash the Nothing Phone 1 firmware via the Fastboot commands
Run the commands below in the CMD window [which is open in the platform-tools folder] to flash the partition file.
Very Important: Only run one command at a time. If you get an error, however, do not exit the process halfway, but go on to the next flashing command instead.
Don't forget to check your command line before validating it, because often a small error blocks you!
Spoiler: Command Lines
Code:
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash boot boot.img
fastboot flash cpucp cpucp.img
fastboot flash devcfg devcfg.img
flash fastboot dsp dsp.img
flash fastboot dtbo dtbo.img
fastboot flash featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash modem modem.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash odm odm.img fastboot
fastboot flash product product.img
fastboot flash qupfw qupfw.img
flash fastboot shrm shrm.img
flash fastboot system system.img
flash fastboot system_ext system_ext.img
flash fastboot tz tz.img
flash fastboot uefisecapp uefisecapp.img
flash fastboot vbmeta vbmeta.img
flash fastboot vbmeta_system vbmeta_system.img
fastboot flash vendor vendor.img
fastboot flash vendor_boot vendor_boot.img
flash fastboot xbl xbl.img
fastboot flash xbl_config xbl_config.img
Step 5: If you have not had any errors, then you can run the command below to boot your device onto the operating system.
Code:
fastboot reboot
Well done , you have just debricked your Nothing Phone 1 by flashing the stock firmware via the fastboot commands.
I hope this tutorial has helped you find your Phone(1).
Thanks

Reserved

FILES FOR NOTHING OS - (stock-boot, etc. )
UPDATE 15/12/2022
Stock_Boot for Nothing OS here
Be carefull, be sure to select the good Stock Boot "Global" or "EEA" for your device.​

Extract Payload.bin via Payload Dumper Go
To start, download the payload-dumper-go 1.0.0 from Github [Credits: XDA Member @ssssut].
Then extract it to any convenient location on your PC. The file name will be something like payload-dumper-go_1.0.0_windows_amd64.
Rename it to payload-dumper-go.
Next, download the liblzma-5.dll file and transfer it to the same folder where the payload-dumper-go.exe file is located.
After that, transfer the payload.bin file to this folder as well.
So, from now on, you should have the 3 files payload-dumper-go.exe, payload.bin and liblzma-5.dll in one folder.
{
"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"
}
Now go to the address bar of that folder, type "cmd" and press Enter. This will launch the command prompt window.
Type the command below to extract the payload.bin file:
Code:
payload-dumper-go payload.bin
The extraction process will now begin and will only take a few seconds.
Once this is done, all extracted files will be placed in a folder named extract_date_time which is created in this directory like this name : extracted_20220731_145751
The process is very simple and very fast. Anyone can do it. So don't hesitate, you have everything you need to do this yourself.
it's up to you now
If this has helped you, and if you appreciate my help.
Thanks

Is it possible to relock the bootloader?
Is it possible to relock the bootloader on an third party ROM?

@Sib64 does the device keep Widevine L1 when the bootloader has been unlocked?

Krullendhaar said:
Is it possible to relock the bootloader?
Click to expand...
Click to collapse
Yes.
Krullendhaar said:
Is it possible to relock the bootloader on an third party ROM?
Click to expand...
Click to collapse
No.

Could you also do a tutorial on how to update the OS when you're rooted?

I hope to find an EDL QPST full rom... better to stay safe and restore It in any case...
Mod is coming...

I tried this with the latest 1.1.0 ROM (got the ROM from https://www.xda-developers.com/nothing-phone-1-nothing-os-1-1-0-update/) but after relocking the bootloader the phone says that it's corrupt and can't get to boot Android.

ErChisus said:
I tried this with the latest 1.1.0 ROM (got the ROM from https://www.xda-developers.com/nothing-phone-1-nothing-os-1-1-0-update/) but after relocking the bootloader the phone says that it's corrupt and can't get to boot Android.
Click to expand...
Click to collapse
Is rooting success with 1.1.0 Rom?

Naveenakash said:
Is rooting success with 1.1.0 Rom?
Click to expand...
Click to collapse
I didn't try it with an actual app, but it was showing properly in Magisk. But bootloader needs to stay unlocked.

ErChisus said:
I tried this with the latest 1.1.0 ROM (got the ROM from https://www.xda-developers.com/nothing-phone-1-nothing-os-1-1-0-update/) but after relocking the bootloader the phone says that it's corrupt and can't get to boot Android.
Click to expand...
Click to collapse
Did you fix that issue?

Naveenakash said:
Did you fix that issue?
Click to expand...
Click to collapse
I didn't. I'm trying to factory reset the phone, but I can't seem to flash the ROM from bootloader.

ErChisus said:
I tried this with the latest 1.1.0 ROM (got the ROM from https://www.xda-developers.com/nothing-phone-1-nothing-os-1-1-0-update/) but after relocking the bootloader the phone says that it's corrupt and can't get to boot Android.
Click to expand...
Click to collapse
Hi! I don't know what the best solution would be, but I would definitely try it if I access the fastboot mode from recovery, reunlock the previously modded and closed bootloader, that is currently on the phone. Ater restarting the phone and its boots up, i would put back the one corresponding to the original software's in recovery fastboot mode and then close it. if the phone started, I do the next sw ota update, restart it and patch its bootloader with magic, then open again the new sw's bootloader from fastboot then flash the magisk patched one. But with thiese solution, you will lose all of your data and application from the phone, same like after you first unlocked the bootloader. ( like factory reset ). I hope it's understandable, unfortunately my English is not very good.

No matter from which partition (A/B)
lba810701 said:
Hi! I don't know what the best solution would be, but I would definitely try it if I access the fastboot mode from recovery, reunlock the previously modded and closed bootloader, that is currently on the phone. Ater restarting the phone and its boots up, i would put back the one corresponding to the original software's in recovery fastboot mode and then close it. if the phone started, I do the next sw ota update, restart it and patch its bootloader with magic, then open again the new sw's bootloader from fastboot then flash the magisk patched one. But with thiese solution, you will lose all of your data and application from the phone, same like after you first unlocked the bootloader. ( like factory reset ). I hope it's understandable, unfortunately my English is not very good.
Click to expand...
Click to collapse
I'm just testing the phone (driving another one yet) so I have no issues with losing data. But the only thing that worked for me was to unlock again the bootloader and then change the active partition (from B to A) within fastboot. After that I could boot the system and do a factory reset.
My issue now is that I'm still with an unlocked bootloader and whether I lock it with one partition marked as active or the other I can't boot to system.

ErChisus said:
No matter from which partition (A/B)
I'm just testing the phone (driving another one yet) so I have no issues with losing data. But the only thing that worked for me was to unlock again the bootloader and then change the active partition (from B to A) within fastboot. After that I could boot the system and do a factory reset.
My issue now is that I'm still with an unlocked bootloader and whether I lock it with one partition marked as active or the other I can't boot to system.
Click to expand...
Click to collapse
And what if you flash back the original bootloader to over the unlocked one, and after it you close it, not the modded one?

ErChisus said:
No matter from which partition (A/B)
I'm just testing the phone (driving another one yet) so I have no issues with losing data. But the only thing that worked for me was to unlock again the bootloader and then change the active partition (from B to A) within fastboot. After that I could boot the system and do a factory reset.
My issue now is that I'm still with an unlocked bootloader and whether I lock it with one partition marked as active or the other I can't boot to system.
Click to expand...
Click to collapse
Also, doing a factory reset from recovery doesn't relock the bootloader either.

I've tried now to sideload the .zip but it seems that even the supposed 1.1.0 full OTA zip available in the other post is older than my current ROM, so it can't be flashed like that. I'll have to wait for the next update.