Here We have the Root And CWM for Nexus 7 On Android 4.2.2!
Step 1 - Download Android SDK from the Android Developers website and install with USB drivers. See: How to Set Up Android SDK (Fastboot / ADB) on Windows.
Step 2 - Enable USB Debugging mode in your Nexus 7 tablet.
Step 3 - Download Fastboot and extract it in android-sdk-windowsplatform-tools directory. Create directory if not already there.
NOTE: Skip Steps 1, 2, 3 if you already have them.
Step 4 - Download SuperSU v1.04 (UPDATE-SuperSU-v1.04.zip) and copy it to your sdcard on your Nexus 7 tablet.
Step 5 - Make sure you have backup your data as it will be removed. Then switch OFF your Nexus 7.
Step 6 - Download recovery-clockwork-touch-6.0.2.3-grouper.img and copy/paste it in the android-sdk-windowsplatform-tools directory.
Step 7 - Now go into Fastboot Mode on Nexus 7. How? Press Volume Down + UP + Power key for a few seconds till you see some text on the screen.
Step 8 - Navigate to android-sdk-windowsplatform-tools directory and open Command Prompt (Shift + Right-click > Open Command Prompt).
Step 9 - Type in the following command and press Enter.
fastboot flash recovery recovery-clockwork-touch-6.0.2.3-grouper.img
Click to expand...
Click to collapse
Step 10 - Once completed, choose RECOVERY MODE from the Fastboot menu and enter Recovery Mode.
Step 11 - Then scroll down to “flash zip from SD card” and press the Power button to select it.
Step 12 - Press the Power button again and select “choose zip from sdcard”.
Step 13 - Now using your volume keys, navigate to the UPDATE-SuperSU-v1.04.zip file that you copied to your SD card and select it using the Power button. Confirm the installation on the next screen and the installation procedure should start now.
Step 14 - After the installation completes, go to “+++++Go Back” and reboot the phone by selecting “reboot system now” from the recovery menu. Then Choose yes flash recovery back (this will make CWM your permanent recovery mode)
That’s it. Your Nexus 7 is now rooted on Android 4.2.2 JDQ39 software version of Jelly Bean and even has a custom CWM recovery installed. Check for the SuperSU app in your apps list to verify.
Root and CWM for Nexus 4
Root and CWM for Nexus 10
Reserved...
udimars30 said:
Reserved...
Click to expand...
Click to collapse
Thank you a lot...but the link for the fastboot its not aviable
Nano23 said:
Thank you a lot...but the link for the fastboot its not aviable
Click to expand...
Click to collapse
link updated
and this belongs in original development how? why not post a thread in original development asking about need for speed too..
Step 4 and step 7
I am a little confused about step 4 as I didn't think any nexus 7's had a SD card slot. I purchased mine right from google. I just put the zip file directly on the device itself and I know from my experience with my old Nexus One that this works too, just wondering who is selling the one with SD card slots. My second question, and really the more important one is step 7. I have tried to make the device go into fastboot several times and when I hold the volume keys down, the device boots to a black screen with no ability to do anything after that. If I mess with the power button (meaning I hold it in for a long time then let it out, and do this several times) I can get the device to preform a normal boot. Any thoughts?
thanks
Thanks its worked for my nexus 7..
udimars30 said:
Here We have the Root And CWM for Nexus 7 On Android 4.2.2!
Step 1 - Download Android SDK from the Android Developers website and install with USB drivers. See: How to Set Up Android SDK (Fastboot / ADB) on Windows.
Step 2 - Enable USB Debugging mode in your Nexus 7 tablet.
Step 3 - Download Fastboot and extract it in android-sdk-windowsplatform-tools directory. Create directory if not already there.
NOTE: Skip Steps 1, 2, 3 if you already have them.
Step 4 - Download SuperSU v1.04 (UPDATE-SuperSU-v1.04.zip) and copy it to your sdcard on your Nexus 7 tablet.
Step 5 - Make sure you have backup your data as it will be removed. Then switch OFF your Nexus 7.
Step 6 - Download recovery-clockwork-touch-6.0.2.3-grouper.img and copy/paste it in the android-sdk-windowsplatform-tools directory.
Step 7 - Now go into Fastboot Mode on Nexus 7. How? Press Volume Down + UP + Power key for a few seconds till you see some text on the screen.
Step 8 - Navigate to android-sdk-windowsplatform-tools directory and open Command Prompt (Shift + Right-click > Open Command Prompt).
Step 9 - Type in the following command and press Enter.
Step 10 - Once completed, choose RECOVERY MODE from the Fastboot menu and enter Recovery Mode.
Step 11 - Then scroll down to “flash zip from SD card” and press the Power button to select it.
Step 12 - Press the Power button again and select “choose zip from sdcard”.
Step 13 - Now using your volume keys, navigate to the UPDATE-SuperSU-v1.04.zip file that you copied to your SD card and select it using the Power button. Confirm the installation on the next screen and the installation procedure should start now.
Step 14 - After the installation completes, go to “+++++Go Back” and reboot the phone by selecting “reboot system now” from the recovery menu. Then Choose yes flash recovery back (this will make CWM your permanent recovery mode)
That’s it. Your Nexus 7 is now rooted on Android 4.2.2 JDQ39 software version of Jelly Bean and even has a custom CWM recovery installed. Check for the SuperSU app in your apps list to verify.
Root and CWM for Nexus 4
Root and CWM for Nexus 10
Click to expand...
Click to collapse
Thanks a million man! I was having all kinds of trouble updating to 4.2.2 and finally figured that out. Then I was having problems rooting again until I found this. Your method worked great but I used TWRP instead and it still did the trick. Thanks again.
I tried this but when I want to flash the recovery, my fastboot.exe will then not respond and will try to close. What gives?
Step 7 - Now go into Fastboot Mode on Nexus 7. How? Press Volume Down + UP + Power key for a few seconds till you see some text on the screen.
Click to expand...
Click to collapse
Just a quick note here, to enter Fastboot Mode you just need to turn the Nexus 7 off, then turn on again, soon as you see the Google logo press the Volume Down key and hold (Hold both Power button and Volume Down Key).
No need for holding the power button, the vol down button does the whole trick
worked for me. thanks very much
sicameron32 said:
I am a little confused about step 4 as I didn't think any nexus 7's had a SD card slot. I purchased mine right from google. I just put the zip file directly on the device itself and I know from my experience with my old Nexus One that this works too, just wondering who is selling the one with SD card slots. My second question, and really the more important one is step 7. I have tried to make the device go into fastboot several times and when I hold the volume keys down, the device boots to a black screen with no ability to do anything after that. If I mess with the power button (meaning I hold it in for a long time then let it out, and do this several times) I can get the device to preform a normal boot. Any thoughts?
Click to expand...
Click to collapse
yes you can do that for the normal boot
Spenzert said:
Just a quick note here, to enter Fastboot Mode you just need to turn the Nexus 7 off, then turn on again, soon as you see the Google logo press the Volume Down key and hold (Hold both Power button and Volume Down Key).
Click to expand...
Click to collapse
Thanks..
I don't have N7 that's why did not know!
Leonhan said:
I tried this but when I want to flash the recovery, my fastboot.exe will then not respond and will try to close. What gives?
Click to expand...
Click to collapse
re-install the fastboot with all it's extensions in the same folder!
If you want to use fastboot by a easy way, use this guide you don't need adb line command, just fastboot line command and it's an child game by this way
If you have got a problem with your adb or fastboot or recovery....it's very simply and faster
use this:
Download this file "Fastboot.zip"
Install this file somewhere in one folder which is named "fastboot" on your PC
=> disk C: root
Unzipped this file on the folder "fastboot" and you will find 3 files:
- adb.exe
- AdbWinApi.dll
- fastboot.exe
and when you need to push something by the bootloader, you can use it.
Don't forget to push on this folder the file that you need. For exemple: boot.img or a recovery.img, etc...
The line command is :
Code:
c:\fastboot>
Enter
Code:
c:\fastboot>fastboot flash recovery recovery.img
Enter
If you want to flash the "recovery.img" file
If you want to flash a boot.img:
Code:
c:\fastboot>fastboot flash boot boot.img
******************************************************************
******************************************************************
If you want to know all lines of command
Code:
c:\fastboot>fastboot
Code:
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default: 2048
don´t i have to unlock bootloader first ?
Domx92 said:
don´t i have to unlock bootloader first ?
Click to expand...
Click to collapse
Yes, it is a prerequisite if you want to root your android device.
Ok, so I am running the 4.2.2 update, and after jumping through numerous hoops trying to have my device recognized by adb, I just want to make sure that my very first step should be to boot up in fastboot mode and then issue the following command...
"fastboot oem unlock"
???
Then I can go ahead and proceed to flashing the CWM recovery and flashing the SuperSU file...?
Sent from my SCH-I535 using Tapatalk 2
EDIT: I've tried multiple times, but everytime I boot into "fastboot" mode, which I guess is another way for saying the bootloader, ADB loses its connection with my Nexus 7! Also, if it helps anyone to know, I'm running Win7 64-bit.....I'm not sure if that matters, but the first time I booted up into fastboot mode, my computer recognized it and installed it as an "Android Bootloader Interface" in the Device Manager! When the device boots up normally, ADB does recognize it again, and it also shows up differently in the Device Manager (Android Composite ADB Interface)! ANY help or suggestions would be greatly appreciated, as I obviously can't issue commands to a device that ADB can't see when it's in fastboot mode!
vmancini3 said:
Ok, so I am running the 4.2.2 update, and after jumping through numerous hoops trying to have my device recognized by adb, I just want to make sure that my very first step should be to boot up in fastboot mode and then issue the following command...
"fastboot oem unlock"
???
Then I can go ahead and proceed to flashing the CWM recovery and flashing the SuperSU file...?
Sent from my SCH-I535 using Tapatalk 2
EDIT: I've tried multiple times, but everytime I boot into "fastboot" mode, which I guess is another way for saying the bootloader, ADB loses its connection with my Nexus 7! Also, if it helps anyone to know, I'm running Win7 64-bit.....I'm not sure if that matters, but the first time I booted up into fastboot mode, my computer recognized it and installed it as an "Android Bootloader Interface" in the Device Manager! When the device boots up normally, ADB does recognize it again, and it also shows up differently in the Device Manager (Android Composite ADB Interface)! ANY help or suggestions would be greatly appreciated, as I obviously can't issue commands to a device that ADB can't see when it's in fastboot mode!
Click to expand...
Click to collapse
Hi, vmancini3...
Forget about ADB when your tablet is in FASTBOOT/BOOTLOADER mode...
Here are the salient commands....
Code:
fastboot devices
- should return a serial number to confirm your FASTBOOT connection -
Code:
fastboot oem unlock
- will unlock the BOOTLOADER and will WIPE and FACTORY RESET THE DEVICE; unfortunate, but necessary .
--------------------
With the BOOTLOADER unlocked, begin to set up your Nexus 7 again... as though it was a brand new, just purchased tablet... ie., country, regionalization, WiFi key... etc.
Go online with your Nexus 7 browser (Chrome), and download Chainfire's SU Updater .ZIP package from here...
http://download.chainfire.eu/310/SuperSU/UPDATE-SuperSU-v1.04.zip
Upon completion of this download, shut down the tablet.
--------------------
Reboot again into FASTBOOT/BOOTLOADER mode... VOL down button + POWER ON button.
From your PC, run this command...
Code:
fastboot flash recovery recovery.img
....where the recovery.img is your CWM or TWRP .img file.
Both of which are available here...
CWM - http://www.clockworkmod.com/rommanager
TWRP - http://www.teamw.in/project/twrp2/103
--------------------
Congratulations.... you've just FLASHED a CUSTOM RECOVERY!!!
--------------------
When the self-congratulatory round of self applause has died down, ... and with the Nexus 7 still in FASTBOOT/ BOOTLOADER MODE, use the VOL buttons to navigate and the POWER button to select... reboot into RECOVERY.
Using the new CUSTOM RECOVERY, flash Chainfires SU updater package that you downloaded earlier... usually found in the /download folder...
Done.
Reboot.
Rooted.
--------------------
I really don't understand why some people seem to have a problem with this procedure... it takes less time doing it, than actually describing how to do it.
Rgrds,
Ged.
This is a guide how to root and install custom rom and recovery on ZTE Open C.
I tested it on Linux but it should work with Windows and Mac just fine.
1. Download and install Android SDK
2. Install Android SDK Tools, Android SDK Platform-tools, Android SDK Build-tools, API 19 and Google USB Driver(Windows only)
3. Download Recovery and keep it on you computer
Download Gapps and Rom and put it either on your sd card or keep it on your computer
Extract FFOS+to+Android from the rar DONT EXTRACT THE ZIP!
4. Enable external Debugging on settings>Device information>More Information>Developer>Remote Debugging
5. Connect your phone to your computer
6.
Code:
adb devices
If it shows a serial number you can skip the following and continue at step 7
If not try
Linux: type "sudo" before every command Windows:Right click on cmd and tick "Run as administrator"
If it fails try
Code:
adb kill-server
Code:
adb start-server
If it fails either try
Code:
adb shell
ctrl+c
If it fails either try to disable Remote Debugging and enable it again then repeat step 6
7.
Code:
adb reboot bootloader
Code:
fastboot flash recovery path to recovery
Example:
Code:
fastboot flash recovery /home/tobias/Downloads/cw_recovery_50.img
8. Flash Rom either via sd or via adb sideload
9. Rebbot
Select "Yes" both times
10. Reboot into recovery and flash SuperSu
Reboot
Select "Yes"
11. Reboot into recovery and flash gapps
Reboot
12. Done
Congratulations! You now have a rooted Andoid 4.4.2 Smartphone with Gapps.
Downloads
Recovery(by vampirefo)
Rom(official ZTE)
SuperSu(by Chainfire)
Gapps
if i want ffos back???
Back up with recovery before flashing anything ever. Then restore from recovery if needed
plmosqueda said:
if i want ffos back???
Click to expand...
Click to collapse
You can download FFOS from here and put it on your SD card.
Then you boot into recovery and install it.
7.
Code:
adb reboot bootloader
When i doing this , My pone Don't Turn On again. where its problem ? Any Sugtn ?
GamblerTobi said:
This is a guide how to root and install custom rom and recovery on ZTE Open C.
I tested it on Linux but it should work with Windows and Mac just fine.
1. Download and install Android SDK
2. Install Android SDK Tools, Android SDK Platform-tools, Android SDK Build-tools, API 19 and Google USB Driver(Windows only)
3. Download Recovery and keep it on you computer
Download Gapps and Rom and put it either on your sd card or keep it on your computer
Extract FFOS+to+Android from the rar DONT EXTRACT THE ZIP!
4. Enable external Debugging on settings>Device information>More Information>Developer>Remote Debugging
5. Connect your phone to your computer
6.
Code:
adb devices
If it shows a serial number you can skip the following and continue at step 7
If not try
Linux: type "sudo" before every command Windows:Right click on cmd and tick "Run as administrator"
If it fails try
Code:
adb kill-server
Code:
adb start-server
If it fails either try
Code:
adb shell
ctrl+c
If it fails either try to disable Remote Debugging and enable it again then repeat step 6
7.
Code:
adb reboot bootloader
Code:
fastboot flash recovery path to recovery
Example:
Code:
fastboot flash recovery /home/tobias/Downloads/cw_recovery_50.img
8. Flash Rom either via sd or via adb sideload
9. Rebbot
Select "Yes" both times
10. Reboot into recovery and flash SuperSu
Reboot
Select "Yes"
11. Reboot into recovery and flash gapps
Reboot
12. Done
Congratulations! You now have a rooted Andoid 4.4.2 Smartphone with Gapps.
Downloads
Recovery(by vampirefo)
Rom(official ZTE)
SuperSu(by Chainfire)
Gapps
Click to expand...
Click to collapse
Hello,
I own a FXOS Zte Open C (ebay EU one)
I work on Linux Mint
I suceeed from step 1 to 7 but then in the recovery I am not able to flash any ROM
- adb sideload: not working, it starts but fails at 59% with error message
adb sideload EU_FFOS+to+Android.zip
* failed to write data 'protocol fault (status len)' *
- flash ROM the file on external_sdcard: impossible because recovery is
not able to mount external_sdcard (whereas it isperfectly seen in FXOS)
It is not able to format it either....
I do not know how to move forward
adb devices return correct ID
fastboot devices also returns correct ID
Could anyone propose a solution ?
Thanks for your help
SuperThieu said:
Hello,
I own a FXOS Zte Open C (ebay EU one)
I work on Linux Mint
I suceeed from step 1 to 7 but then in the recovery I am not able to flash any ROM
- adb sideload: not working, it starts but fails at 59% with error message
adb sideload EU_FFOS+to+Android.zip
* failed to write data 'protocol fault (status len)' *
- flash ROM the file on external_sdcard: impossible because recovery is
not able to mount external_sdcard (whereas it isperfectly seen in FXOS)
It is not able to format it either....
I do not know how to move forward
adb devices return correct ID
fastboot devices also returns correct ID
Could anyone propose a solution ?
Thanks for your help
Click to expand...
Click to collapse
I found the problem: my sd card has been formatted by Windows and recovery did not appreciate....
I did format it with Linux and then everything went fine, I did flash the zip on sdexternal card.
Thanks for the tutorial !
This has not worked for me
adb reboot bootloader does nto seem to reboot not sure if it is supposed to or not.
i get to fastboot recovery and that seems to work
but when i adb sideload FFOS+to+Andorid.zip
it gives me and error: device not found
booting using the power button and volume up and selecting install zip and install zip sideload
halts at 59% and i get the error
* failed to write data 'protocol fault (status len)' *
any ideas whats wrong?
[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.
I just received a system update for build PPR1.180610.091 but I am rooted with a custom kernel.
I think it should be ok to take the system update if I restore my /boot to a stock image but I want to make sure before I take the update.
The rom is stock and has Magisk and ElementalX. Bootloader and Critical are unlocked.
Would it be ok if I restore my boot.img to the stock one and then accept the update via the system updater? or is there something else I need to do?
xNotta said:
I just received a system update for build PPR1.180610.091 but I am rooted with a custom kernel.
I think it should be ok to take the system update if I restore my /boot to a stock image but I want to make sure before I take the update.
The rom is stock and has Magisk and ElementalX. Bootloader and Critical are unlocked.
Would it be ok if I restore my boot.img to the stock one and then accept the update via the system updater? or is there something else I need to do?
Click to expand...
Click to collapse
Just reboot to stock recovery, apply update from adb, in terminal on pc, adb sideload, then drag and drop the ota zip from essential site, hit enter, it will update and u keep data
jacksummers said:
Just reboot to stock recovery, apply update from adb, in terminal on pc, adb sideload, then drag and drop the ota zip from essential site, hit enter, it will update and u keep data
Click to expand...
Click to collapse
If I sideload the Ota, do I need to flash the stock boot first?
xNotta said:
If I sideload the Ota, do I need to flash the stock boot first?
Click to expand...
Click to collapse
Nope. After the flash and reboot, u gotta re root though
jacksummers said:
Nope. After the flash and reboot, u gotta re root though
Click to expand...
Click to collapse
I just did the sideload but I got an error:
Code:
adb> adb sideload .\PH1-OTA-PPR1.180610.091.zip
opening '.\PH1-OTA-PPR1.180610.091.zip'...
connecting...
serving: '.\PH1-OTA-PPR1.180610.091.zip' (~94%) * failed to read command: No error
but the recovery said it was completed successfully. My phone booted fine and is running Pie.
Is this a normal error?
xNotta said:
I just did the sideload but I got an error:
Code:
adb> adb sideload .\PH1-OTA-PPR1.180610.091.zip
opening '.\PH1-OTA-PPR1.180610.091.zip'...
connecting...
serving: '.\PH1-OTA-PPR1.180610.091.zip' (~94%) * failed to read command: No error
but the recovery said it was completed successfully. My phone booted fine and is running Pie.
Is this a normal error?
Click to expand...
Click to collapse
I got the same error, but haven't had any issues.
I have been using this thread as my reference for how to take updates so I wanted to add some instructions and links that I found useful/necessary for completing the process.
Hopefully someone else can find this useful.
IMPORTANT! Remove screen lock pin before continuing!
TWRP will prompt for a password if you do not remove your lockscreen pin/pattern! There is no password!
This is caused due to Android encrypting the /data/ partition.
Settings > Security & Location > Device Security section > Screen Lock. Set it to None.
You can also search in settings for "Screen Lock"
Stock boot images:
https://drive.google.com/drive/folders/1iayS6YHYZvqkD1Y8oYV3ewzW5aAPe8C2
TWRP (twrp-mata_11.img) images:
https://download.invisiblek.org/mata/
Essential Phone downloads:
Download the OTA file for Sideloading
https://www.essential.com/developer/current-builds
Sideloading using stock recovery(my preferred method):
Ensure USB debugging is enabled on your Essential Phone. To do so, follow step four above.
Plug your Essential Phone into your computer with a USB cable.
Open a command window in the folder where you have ADB and fastboot installed.
In your command window, type adb devices and press enter. Your device’s serial number should appear in the command window.
If you see a notice on your phone asking if you’d like to allow USB debugging on this computer, check the box and select OK.
Reboot your phone into recovery mode. To do so, type adb reboot recovery into your command window. Your phone will reboot into recovery mode. You should see a little green bugdroid with a caution symbol. Despite your gut reaction, this is good.
Open the recovery menu on your Essential Phone. To do so, hold the power button and press the volume-up button once.
Scroll down to Apply update from ADB with your volume-down button, then press the power button to confirm.
Ensure that your phone is still being recognized by your computer. To do so, type adb devices in your command window and press enter. Your device’s serial number should appear in the window.
In your command window, type adb sideload update.zip (or whatever you named your file).
Source: https://www.androidauthority.com/how-to-install-android-p-essential-phone-863668/
Sideloading using TWRP:
Reboot your Essential Phone into Fastboot mode by restarting the phone and pressing and holding volume down and the power button at the same time. Once you’re in Fastboot mode, flash TWRP with the following ADB command: fastboot flash boot twrp.img
From within the Fastboot menu, select and boot into “recovery mode.” Once TWRP has booted up, type in: adb shell twrp sideload
Then type in: adb sideload magisk.zip
Once Magisk finishes installing completely, reboot back to Fastboot. You can do this via: adb reboot-bootloader
When you’re back in Fastboot mode, grab the modified boot.img (making sure to select the right one) and flash it via fastboot flash boot boot.img
Now reboot! You should now have root via Magisk!
Source: https://www.xda-developers.com/how-to-root-essential-phone-ph-1/