Related
In short :
I had to unroot and relock for warranty purposes. I used Nexus 7 toolkit.
I selected option 9 "Download, Extract + Flash Google Factory Rom". Then, option 2 "Flash Google Factory Image" without going through option 1 "Download Google Stock Image" before. I thought I had already downloaded the image, which turned out I hadn't.
I don't know what it flashed, but now I'm stuck in fastboot mode, locked and unable to enable USB debugging. The only thing I can do is unlock/relock the N7.
Can some wizard help me out on that ?!?
Julien
jfpesant said:
In short :
I had to unroot and relock for warranty purposes. I used Nexus 7 toolkit.
I selected option 9 "Download, Extract + Flash Google Factory Rom". Then, option 2 "Flash Google Factory Image" without going through option 1 "Download Google Stock Image" before. I thought I had already downloaded the image, which turned out I hadn't.
I don't know what it flashed, but now I'm stuck in fastboot mode, locked and unable to enable USB debugging. The only thing I can do is unlock/relock the N7.
Can some wizard help me out on that ?!?
Julien
Click to expand...
Click to collapse
I'm in the same boat as you. I've tried 6 computers. 1 detects it and I can unlock/lock bootloader but fails when I try to flash stock image.The other 5 computers, when I plug it in it freezes my tab in fastboot. WTF
logan_izer10 said:
I'm in the same boat as you.
Click to expand...
Click to collapse
Welcome aboard !
in the toolkit make sure you have the right model number in the "change" section,in the back to stock section check the "cant boot up"bit,then click flash stock + unroot,works all the time for me
jfpesant said:
In short :
I had to unroot and relock for warranty purposes. I used Nexus 7 toolkit.
I selected option 9 "Download, Extract + Flash Google Factory Rom". Then, option 2 "Flash Google Factory Image" without going through option 1 "Download Google Stock Image" before. I thought I had already downloaded the image, which turned out I hadn't.
I don't know what it flashed, but now I'm stuck in fastboot mode, locked and unable to enable USB debugging. The only thing I can do is unlock/relock the N7.
Can some wizard help me out on that ?!?
Julien
Click to expand...
Click to collapse
As good as toolkits can be, I recommend using adb and fastboot directly. This will allow you to see what is happening every step of the way and is a good opportunity to learn. The following instructions assume some basic Windows command prompt skills.
Read all the directions before you begin and perform the steps at your own risk.
I want to assume that you have the correct drivers installed, but I wont. This and any following verbosity is not to be condescending, but rather not to assume anything. If you're certain the adb and fastboot drivers are correctly, skip to step 7.
To obtain the tools and drivers needed, download the Android SDK - http://developer.android.com/sdk/index.html
Run the SDK installer that you downloaded and follow the on-screen instructions.
Make note of the install location which defaults to: C:\Users\<user name>\AppData\Local\Android\android-sdk this is where the tools and drivers will be downloaded to. This will be referred to as your sdk directory
Note: Java SE JDK is required by Android SDK. Download and install the Java SE JDK from Oracle
Run SDK Manager.
Under Tools, check the box labeled "Android SDK Platform-tools" - this provides adb and fastboot
Under Extras, check the box labeled "Google USB Driver"
Press the "Install # Packages..." button and follow the on-screen instructions.
Install the abd driver - detailed instructions can be found at http://developer.android.com/tools/extras/oem-usb.html
Note: in order for your device to be detected, USB debugging must be enabled on the device
Once the driver is installed open a command prompt and change directories to <your sdk directory>\platform-tools (see #2). From the command prompt run "adb devices". This will list any adb-capable devices that are attached to the computer by their serial number assuming your drivers are installed correctly. Recap:
Code:
> cd \Users\<user name>\AppData\Local\Android\android-sdk\platform-tools
> adb devices
# the following output should be returned
List of devices attached
<device serial number> device
Use adb to boot the device to the bootloader:
Code:
> adb reboot-bootloader
The device should now be in fastboot mode and Windows should be attempting to install the fastboot driver. You can verify that the driver has been installed by running the following command:
Code:
> fastboot devices
# the following output should be returned
<device serial number> fastboot
Download the factory image for Nexus 7 from https://developers.google.com/android/nexus/images#nakasi. The resulting file will have the extension .tgz. You will need something that can reliably decompress and extract files from this archive. If in doubt at all, use 7-Zip http://www.7-zip.org/download.html.
Open the archive with 7-Zip you should see a single .tar file. Open the .tar file with 7-Zip as well.
Inside the .tar file is a directory that will resemble "nakasi-jro03d". Open that directory.
Extract the contents of the "nakasi-jro03d" directory to <your sdk directory>/platform-tools. The extracted files should be as follows: bootloader-grouper-3.34.img, image-nakasi-jro03d.zip, flash-all.sh, flash-base.sh
The flash-all.sh file is a shell script that contains all the commands required to flash the factory image using the fastboot command. In order to use fastboot, we need to boot the device to fastboot mode. This can be done with adb:
Code:
> adb reboot-bootloader
In order to do anything useful, the bootloader must be unlocked. Do that like so:
Code:
> fastboot oem unlock
Follow the directions on the device, using the volume and power buttons to select "Yes".
In fastboot with your device's bootloader unlocked, run the commands listed in flash-all.sh in sequence, waiting for each command to finish. For convenience I have them here:
Code:
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
> fastboot flash bootloader bootloader-grouper-3.34.img
> fastboot reboot-bootloader
> fastboot -w update image-nakasi-jro03d.zip
# optionally re-lock the bootloader.
# You may want to do this if you're returning the device for warranty work.
> fastboot oem lock
# finally, reboot
> fastboot reboot
That should do it.
tonybhoy said:
in the toolkit make sure you have the right model number in the "change" section,in the back to stock section check the "cant boot up"bit,then click flash stock + unroot,works all the time for me
Click to expand...
Click to collapse
Worked for me !!! Thanks bro !
(I previously have tried this, but didn't choose the right model number... so it didn't work)
comminus said:
As good as toolkits can be, I recommend using adb and fastboot directly. This will allow you to see what is happening every step of the way and is a good opportunity to learn. The following instructions assume some basic Windows command prompt skills.
Click to expand...
Click to collapse
Thanks a lot for the insight. I'm all about DIY so I'll definitely give this a try next time I have to play in android.
Julien
jfpesant said:
Thanks a lot for the insight. I'm all about DIY so I'll definitely give this a try next time I have to play in android.
Julien
Click to expand...
Click to collapse
No worries, I'm glad the simpler route worked!
[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.
Orea beta is great but battery drain so much.
for 30 min of screen use it used 11%, is it normal ?
and I am looking to go back to Nougat, could any one please tell me how can I go back.
Thank you.
are this instructions for downgrading ?
Set up your computer for flashing
Download the fastboot tool from the Android SDK Platform-Tools package
Add it to your path so the flash scripts can find it
Connect your Essential phone to your computer with a USB cable
Enable unlocking
Before you can flash a new image, ensure Developer options are enabled and OEM unlocking is turned on. To do this:
Tap Settings, then tap System > About phone
Scroll to the bottom of the page, then tap Build number multiple times until you see the pop-up message “You are now a developer” (It usually takes seven taps)
Go back one screen to System, then tap Developer options
Find the option: OEM Unlocking and turn it on
Fastboot mode
Put your Essential Phone into fastboot mode by doing either of the following:
Use the ADB tool packaged above to run the command: adb reboot bootloader
Reboot your phone while holding the Volume-down button
Unlock your bootloader
NOTE: Installing the factory image will erase all information from your device. So remember to backup your phone before continuing.
Run the command: fastboot flashing unlock
Press the Volume-down button to navigate to the YES option, then press the Power button to confirm
Flash your factory image
Download the factory image to your computer
Unzip the downloaded file
Go to where you unzipped the images
For Linux / Mac OS X - Run the command: flashall.sh
For Windows - Run the command: flashall.bat
https://forum.xda-developers.com/essential-phone/help
Yup those are them, I just did it yesterday.
Just an FYI, I found that putting Oreo on the phone resulted in ADB not working 100% anymore, such as attempting to reboot into recovery/etc. It would just reboot back into the O.S..
Here is what I did.
- download the current release you want to flash. (e.g. NMJ32F), then unzip it into a new folder.
- on your phone, verify that USB debugging and OEM unlocking are turned on in the developers menu.
- reboot your phone into the fastboot mode (power and volume down buttons)
- from your adb command line: type: fastboot flashing unlock
- This will make your phone show a new screen asking if you want to unlock the bootloader. Use the volume down to select YES, and hit the power button. It will now reboot and erase the phone. It will eventually end up booting up too request you setup the phone. (that is what it did for me.)
- reboot the phone back into the fastboot mode (power and volume down buttons)
- you should now see the bootloader listed as unlocked (vs locked)
- from your adb command line: type: fastboot devices (which should show your phones serial number and fastboot next too it.
- on your computer, using the command line, go to the unzipped folder of the NMJ32F build you downloaded
- in the folder there is a batch file you will run called flashall.bat. run it
- your phone will start flashing the NMJ32F build
- when it completes it will reboot a couple of times, erase the phone, and end up at the "lets get started" screen.
- reboot the phone back to the fastboot mode
- from your adb command line: type: fastboot flashing lock
- select the option to lock your bootloader. The phone will reboot/erase I believe, and then end up back to the "lets get started" screen.
- after you setup your phone, you can go back into the developers menu to turn off the oem unlocking
The above steps pretty much follow essentials instructions. (the essential instructions don't give some specifics.)
You are all done. (I recommend you review my instructions and the essential instructions carefully, don't copy paste commands as I may have spelled something wrong, etc.. Just wanted to give you a flow of the process.)
vjyrdy said:
are this instructions for downgrading ?
Set up your computer for flashing
Download the fastboot tool from the Android SDK Platform-Tools package
Add it to your path so the flash scripts can find it
Connect your Essential phone to your computer with a USB cable
Enable unlocking
Before you can flash a new image, ensure Developer options are enabled and OEM unlocking is turned on. To do this:
Tap Settings, then tap System > About phone
Scroll to the bottom of the page, then tap Build number multiple times until you see the pop-up message “You are now a developer” (It usually takes seven taps)
Go back one screen to System, then tap Developer options
Find the option: OEM Unlocking and turn it on
Fastboot mode
Put your Essential Phone into fastboot mode by doing either of the following:
Use the ADB tool packaged above to run the command: adb reboot bootloader
Reboot your phone while holding the Volume-down button
Unlock your bootloader
NOTE: Installing the factory image will erase all information from your device. So remember to backup your phone before continuing.
Run the command: fastboot flashing unlock
Press the Volume-down button to navigate to the YES option, then press the Power button to confirm
Flash your factory image
Download the factory image to your computer
Unzip the downloaded file
Go to where you unzipped the images
For Linux / Mac OS X - Run the command: flashall.sh
For Windows - Run the command: flashall.bat
https://forum.xda-developers.com/essential-phone/help
Click to expand...
Click to collapse
I cannot get past the flashall.sh command, says permission denied everytime. I am able to execute every command to that point with out any issues. I have downloaded the latest android platform tools, and my mac is on the latest version of macOS . I have also tried to flash every single image that is available on the essential dev webpage. Any ideas would be awesome, is in possible to side load using the adb commands from the recovery menu and avoid the fastboot mode all together.
swagglepuff said:
I cannot get past the flashall.sh command, says permission denied everytime. I am able to execute every command to that point with out any issues. I have downloaded the latest android platform tools, and my mac is on the latest version of macOS . I have also tried to flash every single image that is available on the essential dev webpage. Any ideas would be awesome, is in possible to side load using the adb commands from the recovery menu and avoid the fastboot mode all together.
Click to expand...
Click to collapse
unlock_critical.
You can't flash all the partitions is you have not performed and unlock AND and unlock_critical.
tech_head said:
unlock_critical.
You can't flash all the partitions is you have not performed and unlock AND and unlock_critical.
Click to expand...
Click to collapse
I have ran both unlock commands successfully and still get permission denied
swagglepuff said:
I have ran both unlock commands successfully and still get permission denied
Click to expand...
Click to collapse
And you checked the OEM unlock in developer options?
Hmmmm
tech_head said:
And you checked the OEM unlock in developer options?
Hmmmm
Click to expand...
Click to collapse
The issue has something to do with Mac and the platform tools. I was able to downgrade with no problem using a friend's Windows PC.
Sorry for the silly question, but what does this statements means?
"Add it to your path so the flash scripts can find it"
Is there any better instructions for first time user which dont include instructions like above? Thanks.
trizon2016 said:
Sorry for the silly question, but what does this statements means?
"Add it to your path so the flash scripts can find it"
Is there any better instructions for first time user which dont include instructions like above? Thanks.
Click to expand...
Click to collapse
Nothing confusing about that statement for Windows, MacOS or Linux.
A command path needs to exist so that when you type the command it can be found.
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/
This guide worked for every OREO version, and also is working for PIE ! :good:
You will enable camera2 on your phone, and keep it stock afterwards so it can receive future OTA updates. :victory:
1 - Unlocking bootloader
Unlocking bootloader, this command will delete/reset your phone, so do backup of files as needed.
First of all, enable the Developer Option.
To do this go to your Settings -> About -> Software Information -> More -> Now Tap on the Build Number 7-8 Times until you see a toast message “Developer option enabled”.
Now go back to settings -> Enable the OEM Unlock by going to Settings -> Developer Option and Enable OEM Unlock and USB Debugging.
Now connect the phone with your USB cable, use USB port 2.0 on your computer.
It should appear on your phone screen an asking for access privileges of your PC (device, maybe Linux), allow it.
Download ADB if you don't have it.
https://drive.google.com/file/d/1yCdMyAAOD46T4B8haFuZVF57E4-WK8l2/view?usp=sharing
In ADB folder, double click "Open CMD here.bat".
AND FROM THIS TIME, YOU DON'T CLOSE THIS CMD AT ALL, UNTILL YOU FINISH THE WHOLE GUIDE
Code:
adb devices
Your device should appear with some random numbers like this
https://www.howtogeek.com/wp-content/uploads/2012/10/image34.png
If it does, go to next stage, if it's not, you are not installed usb drivers corectly or did not enabled usb debugging.
Link for USB Drivers for Mi A2.
http://dl.adbdriver.com/upload/adbdriver.zip
Code:
adb reboot bootloader
Unlocking bootloader, this command will delete/reset your phone, so do backup of files as needed.
Code:
fastboot oem unlock
Phone will reboot, go to check developer options > usb debugging ON once again.
Code:
adb reboot bootloader
Again in fastboot we are unlocking critical partitions, and once again it will erase verything from the phone, so be sure to do the backup as needed.
Code:
fastboot flashing unlock_critical
Again when the phone reboot, check developer options > usb debugging ON.
2. Rooting the phone (temporarily)
Download stock boot and patched boot of android version you have, if you need versions for OREO, find somewhere in forum, here it is link for PIE.
10.0.9.0 https://drive.google.com/drive/folders/1ZP5jelFGT5z9EJvHRokzLJwAikKtWI8p?usp=sharing
10.0.8.0 https://drive.google.com/drive/folders/1XNE_veO_FvOLQ46oorUBa2g7TKA1PHRv?usp=sharing
10.0.7.0 https://drive.google.com/drive/folders/1kHLYXhaWFpjh58F79xnOkN3kjkuyEdHV?usp=sharing
10.0.5.0 https://drive.google.com/drive/folders/1qCIsk1MVVq_X-mR8BBWa2NeVLB_-4q5y?usp=sharing
10.0.4.0 https://drive.google.com/drive/folders/1piLD_9mQv0XgahyIZdxRqfdwaDbfx2_0?usp=sharing
10.0.3.0 https://drive.google.com/open?id=1uO3yfxHdTr4gv4DmCaLu-naIIt8mprBT
"It seems like 10.0.3.0 OTA is withdrawn by Xiaomi due to numerous bootloops in stock phones."
My recommendation is to skip flashing this version, until next stable comes up !
10.0.2.0 https://drive.google.com/drive/folders/1_cIM0ltKD_PU1mIiWwUE-nMba964NyvN?usp=sharing
10.0.1.0 https://drive.google.com/drive/folders/18tcBVaKwH9cy_RVczf-GSc_tAkFYvn15?usp=sharing
9.6.17.0 https://drive.google.com/drive/folders/1D9RlDZRupdriCyJM4p0ixvntPE2QPP9w?usp=sharing
Put the files in adb folder, both the stock boot.img and patched_boot.img.
NOW !
There are two methods, so you can choose between those two:
1. Faster and easier one with only booting patched boot
2. Slower with flashing, but this one will teach you how to flash and root your phone
1. ENABLING WITH BOOTING PATCHED_BOOT.IMG
In CMD type
Code:
adb reboot bootloader
Code:
fastboot boot patched_boot.img
When the phone starts, wait for magisk to appear in apps, or if it's not there, find it in apkmirror site, magisk manager, download, install from phone it is easier.
https://www.apkmirror.com/?post_type=app_release&searchtype=apk&s=magisk+manager
Then when you start magisk, it will ask you to download full zip, just skip it, your phone will now be rooted.
3. Enabling Camera2 api (lvl3)
In CMD type
Code:
adb shell
Code:
su
(this time look at the phone screen, allow root access ONCE)
Code:
setprop persist.camera.HAL3.enabled 1
For PIE and for using v6 Gcam ports three more commands, for OREO it is not needed.
Code:
setprop persist.vendor.camera.HAL3.enabled 1
Code:
setprop persist.camera.stats.test 5
Code:
setprop persist.vendor.camera.stats.test 5
Press ctrl+c to exit adb shell (windows) or just type "exit" and again "exit"
4. Unrooting the phone
Start magisk again, go to UNINSTALL, choose full uninstall, magisk will reboot the phone in process of uninstalling, and the phone should start normaly without Magisk installed, and with camera2 enabled, because nothing was flashed, you are DONE !
2. ENABLING WITH FLASHING PATCHED_BOOT.IMG
In CMD type
Code:
adb reboot bootloader
Code:
fastboot getvar current-slot
Then when you see your active partition, flash the patched image.
Code:
fastboot flash boot_a patched_boot.img
OR if it was b partition active
Code:
fastboot flash boot_b patched_boot.img
Code:
fastboot reboot
When the phone starts, wait for magisk to appear in apps, or if it's not there, find it in apkmirror site, magisk manager, download, install from phone it is easier.
https://www.apkmirror.com/?post_type=app_release&searchtype=apk&s=magisk+manager
Then when you start magisk, it will ask you to download full zip, just skip it, your phone will now be rooted.
3. Enabling Camera2 api (lvl3)
In CMD type
Code:
adb shell
Code:
su
(this time look at the phone screen, allow root access ONCE)
Code:
setprop persist.camera.HAL3.enabled 1
For PIE and for using v6 Gcam ports three more commands, for OREO it is not needed.
Code:
setprop persist.vendor.camera.HAL3.enabled 1
Code:
setprop persist.camera.stats.test 5
Code:
setprop persist.vendor.camera.stats.test 5
Press ctrl+c to exit adb shell (windows) or just type "exit" and again "exit"
4. Unrooting the phone
Start magisk again, go to UNINSTALL, choose full uninstall, magisk will reboot the phone in process of uninstalling, prepare and hold down the volume button when phone restarts, your phone will go into fastboot.
Type the command for active partition
Code:
fastboot getvar current-slot
Code:
fastboot flash boot_a boot.img
Or
Code:
fastboot flash boot_b boot.img
Code:
fastboot reboot
This is it guys, you have enabled lvl3 (camera2), and unrooted phone, ready for next OTA updates.
Install camera2 probe from gplay to confirm.
https://play.google.com/store/apps/details?id=de.weis.camera2probe&hl=en
Phone needs to stay with unlocked bootloader, because if you lock the phone, you will lose camera2, but do not worry, the future OTA updates will work.
If this guide helped you, please click the thanks button, that's all, cheers. :highfive:
If you're using temp recovery, just fastboot boot patched_boot.img, no need to flash, and once done just reboot
if i flash boot.img back i get stuck in android one screen
idriff said:
if i flash boot.img back i get stuck in android one screen
Click to expand...
Click to collapse
On what android version were you ?
pie, i just flashed back the modified boot and it worked but now im rooted
What version google camera you guys using?
minnuss said:
This guide worked for every OREO version, and also is working for PIE ! :good:
You will enable camera2 on your phone, and keep it stock afterwards so it can receive future OTA updates. :victory:
1 - Unlocking bootloader
Unlocking bootloader, this command will delete/reset your phone, so do backup of files as needed.
First of all, enable the Developer Option.
To do this go to your Settings -> About -> Software Information -> More -> Now Tap on the Build Number 7-8 Times until you see a toast message “Developer option enabled”.
Now go back to settings -> Enable the OEM Unlock by going to Settings -> Developer Option and Enable OEM Unlock and USB Debugging.
Now connect the phone with your USB cable, use USB port 2.0 on your computer.
It should appear on your phone screen an asking for access privileges of your PC (device, maybe Linux), allow it.
Download ADB if you don't have it.
https://drive.google.com/file/d/1yCdMyAAOD46T4B8haFuZVF57E4-WK8l2/view?usp=sharing
In ADB folder, double click "Open CMD here.bat".
AND FROM THIS TIME, YOU DON'T CLOSE THIS CMD AT ALL, UNTILL YOU FINISH THE WHOLE GUIDE
Code:
adb devices
Your device should appear with some random numbers like this
https://www.howtogeek.com/wp-content/uploads/2012/10/image34.png
If it does, go to next stage, if it's not, you are not installed usb drivers corectly or did not enabled usb debugging.
Code:
adb reboot bootloader
Unlocking bootloader, this command will delete/reset your phone, so do backup of files as needed.
Code:
fastboot oem unlock
Phone will reboot, go to check developer options > usb debugging ON once again.
Code:
adb reboot bootloader
Again in fastboot we are unlocking critical partitions, and once again it will erase verything from the phone, so be sure to do the backup as needed.
Code:
fastboot flashing unlock_critical
Again when the phone reboot, check developer options > usb debugging ON.
2. Rooting the phone (temporarily)
Download stock boot and patched boot of android version you have, if you need versions for OREO, find somewhere in forum, here it is link for PIE.
https://drive.google.com/drive/folders/18tcBVaKwH9cy_RVczf-GSc_tAkFYvn15?usp=sharing
Put the files in adb folder, both the stock boot.img and patched_boot.img.
Code:
adb reboot bootloader
Code:
fastboot getvar current-slot
Then when you see your active partition, flash the patched image.
Code:
fastboot flash boot_a patched_boot.img
OR if it was b partition active
Code:
fastboot flash boot_b patched_boot.img
Code:
fastboot reboot
When the phone starts, wait for magisk to appear in apps, or if it's not there, find it in apkmirror site, magisk manager, download, install from phone it is easier.
https://www.apkmirror.com/?post_type=app_release&searchtype=apk&s=magisk+manager
Then when you start magisk, it will ask you to download full zip, let him do it, install full zip, your phone will now be rooted.
3. Enabling Camera2 api (lvl3)
In CMD type
Code:
adb shell
Code:
su
(this time look at the phone screen, allow root access ONCE)
Code:
setprop.persist.camera.HAL3.enabled 1
For PIE one more command, for OREO it is not needed.
Code:
setprop persist.vendor.camera.HAL3 enabled 1
Press ctrl+c to exit adb shell.
4. Unrooting the phone
Start magisk again, go to UNINSTALL, choose full uninstall, magisk will reboot the phone in process of uninstalling, prepare and hold down the volume button when phone restarts, your phone will go into fastboot.
Type the command for active partition
Code:
fastboot getvar current-slot
Code:
fastboot flash boot_a boot.img
Or
Code:
fastboot flash boot_b boot.img
Code:
fastboot reboot
This is it guys, you have enabled lvl3 (camera2), and unrooted phone, ready for next OTA updates.
Install camera2 probe from gplay to confirm.
https://play.google.com/store/apps/details?id=de.weis.camera2probe&hl=en
Phone needs to stay with unlocked bootloader, because if you lock the phone, you will lose camera2, but do not worry, the future OTA updates will work.
If this guide helped you, please click the thanks button, that's all, cheers. :highfive:
Click to expand...
Click to collapse
For me it worked, but in stock camera cant see any diferences, can someone link me a gcam apk to install?
minnuss said:
This guide worked for every OREO version, and also is working for PIE ! :good:
You will enable camera2 on your phone, and keep it stock afterwards so it can receive future OTA updates. :victory:
1 - Unlocking bootloader
Unlocking bootloader, this command will delete/reset your phone, so do backup of files as needed.
First of all, enable the Developer Option.
To do this go to your Settings -> About -> Software Information -> More -> Now Tap on the Build Number 7-8 Times until you see a toast message “Developer option enabled”.
Now go back to settings -> Enable the OEM Unlock by going to Settings -> Developer Option and Enable OEM Unlock and USB Debugging.
Now connect the phone with your USB cable, use USB port 2.0 on your computer.
It should appear on your phone screen an asking for access privileges of your PC (device, maybe Linux), allow it.
Download ADB if you don't have it.
https://drive.google.com/file/d/1yCdMyAAOD46T4B8haFuZVF57E4-WK8l2/view?usp=sharing
In ADB folder, double click "Open CMD here.bat".
AND FROM THIS TIME, YOU DON'T CLOSE THIS CMD AT ALL, UNTILL YOU FINISH THE WHOLE GUIDE
Code:
adb devices
Your device should appear with some random numbers like this
https://www.howtogeek.com/wp-content/uploads/2012/10/image34.png
If it does, go to next stage, if it's not, you are not installed usb drivers corectly or did not enabled usb debugging.
Code:
adb reboot bootloader
Unlocking bootloader, this command will delete/reset your phone, so do backup of files as needed.
Code:
fastboot oem unlock
Phone will reboot, go to check developer options > usb debugging ON once again.
Code:
adb reboot bootloader
Again in fastboot we are unlocking critical partitions, and once again it will erase verything from the phone, so be sure to do the backup as needed.
Code:
fastboot flashing unlock_critical
Again when the phone reboot, check developer options > usb debugging ON.
2. Rooting the phone (temporarily)
Download stock boot and patched boot of android version you have, if you need versions for OREO, find somewhere in forum, here it is link for PIE.
https://drive.google.com/drive/folders/18tcBVaKwH9cy_RVczf-GSc_tAkFYvn15?usp=sharing
Put the files in adb folder, both the stock boot.img and patched_boot.img.
Code:
adb reboot bootloader
Code:
fastboot getvar current-slot
Then when you see your active partition, flash the patched image.
Code:
fastboot flash boot_a patched_boot.img
OR if it was b partition active
Code:
fastboot flash boot_b patched_boot.img
Code:
fastboot reboot
When the phone starts, wait for magisk to appear in apps, or if it's not there, find it in apkmirror site, magisk manager, download, install from phone it is easier.
https://www.apkmirror.com/?post_type=app_release&searchtype=apk&s=magisk+manager
Then when you start magisk, it will ask you to download full zip, let him do it, install full zip, your phone will now be rooted.
3. Enabling Camera2 api (lvl3)
In CMD type
Code:
adb shell
Code:
su
(this time look at the phone screen, allow root access ONCE)
Code:
setprop.persist.camera.HAL3.enabled 1
For PIE one more command, for OREO it is not needed.
Code:
setprop persist.vendor.camera.HAL3 enabled 1
Press ctrl+c to exit adb shell.
4. Unrooting the phone
Start magisk again, go to UNINSTALL, choose full uninstall, magisk will reboot the phone in process of uninstalling, prepare and hold down the volume button when phone restarts, your phone will go into fastboot.
Type the command for active partition
Code:
fastboot getvar current-slot
Code:
fastboot flash boot_a boot.img
Or
Code:
fastboot flash boot_b boot.img
Code:
fastboot reboot
This is it guys, you have enabled lvl3 (camera2), and unrooted phone, ready for next OTA updates.
Install camera2 probe from gplay to confirm.
https://play.google.com/store/apps/details?id=de.weis.camera2probe&hl=en
Phone needs to stay with unlocked bootloader, because if you lock the phone, you will lose camera2, but do not worry, the future OTA updates will work.
If this guide helped you, please click the thanks button, that's all, cheers. :highfive:
Click to expand...
Click to collapse
The post has some errors but I'm here to report you guys how I made it work.
adb devices
adb reboot bootloader
(I had the bootloader unlocked already so I didn't do those steps)
fastboot boot patched_boot.img
(Notice I didn't flash the patched image, you don't need to do that, my current partition was b, but that doesn't matter since I'm not flashing anything, I am just booting into the patched/rooted image)
(Installed magisk manager and rootchecker)
(magisk said it was rooted, so did root checker)
adb shell
su
(I gave the permission on my phone)
setprop persist.camera.HAL3.enabled 1
(If you check the post carefully, this line above is not the same one the OP has, that one is wrong, mine is right)
setprop persist.vendor.camera.HAL3.enabled 1
ctrl+c
adb reboot
(Notice I don't flash anything here as well, since I didn't flash the patched image, so if I reboot, it will boot into my stock boot image)
aaaaaaand it's done.
Thanks to the OP for his work, and please correct the line that is wrong. Cheers. :angel:
Google Camera working fine.
Jamesismo said:
The post has some errors but I'm here to report you guys how I made it work...
Click to expand...
Click to collapse
Hello, thanks a lot!
It's works perfect!
Best regards!!!
hugomoya said:
Hello, thanks a lot!
It's works perfect!
Best regards!!!
Click to expand...
Click to collapse
Please don't quote OP for a single line of comment.
@Jamesismo, thanx, I fixed the typo mistake, did not have the DOT in command line, it was not an error, just a typo, but thanx.
And yes, please guys, do not quote the first post.
In a guide, a neewbie can learn how to unlock bootloader, root the phone, enable cam2, and unroot the phone.
So he can choose, whether he wants to stay with rooted phone or not, or to unroot later if he wants...
I think that with this method, OTA will work even if he has Magisk installed, because nothing is changed in system, but that needs to be confirmed.
I noticed that many people want to lock the bootloader to recieve OTA. It is unnecessary you still receive OTA with an unlocked bootloader provided you have not changed the system folder etc.
Hey @minnuss good job! glad to see this.
I would change one thing i noticed: "Press ctrl+c to exit adb shell."
That's a Windows thing, doesn't work with Linux or Mac. Most people 'should' know how to exit a command prompt, but if not, safer to just say type 'exit' and hit enter. That works on all of the systems.
Cheers
This is it guys, you have enabled lvl3 (camera2), and unrooted phone, ready for next OTA updates.
Install camera2 probe from gplay to confirm.
https://play.google.com/store/apps/details?id=de.weis.camera2probe&hl=en
Phone needs to stay with unlocked bootloader, because if you lock the phone, you will lose camera2, but do not worry, the future OTA updates will work.
If this guide helped you, please click the thanks button, that's all, cheers. :highfive:[/QUOTE]
If may i ask what version of Gcam you recommend? I've tried
Arnova's v8.3b1 and the front facing camera doesn't work on photo mode, but work on video.
Thanks
@minnuss Hey bro, the post does still have a typo, after "setprop" there must be a space, not a dot. (First line)
---------- Post added at 06:09 PM ---------- Previous post was at 05:57 PM ----------
afajri said:
This is it guys, you have enabled lvl3 (camera2), and unrooted phone, ready for next OTA updates.
Install camera2 probe from gplay to confirm.
https://play.google.com/store/apps/details?id=de.weis.camera2probe&hl=en
Phone needs to stay with unlocked bootloader, because if you lock the phone, you will lose camera2, but do not worry, the future OTA updates will work.
If this guide helped you, please click the thanks button, that's all, cheers. :highfive:
Click to expand...
Click to collapse
If may i ask what version of Gcam you recommend? I've tried
Arnova's v8.3b1 and the front facing camera doesn't work on photo mode, but work on video.
Thanks[/QUOTE]
It does work in protrait mode 5mpx, and if you change it from 5mpx to 3mpx, normal selfie works as well.
@[email protected]
@AsItLies
@kishd
@Jamesismo
@afajri
Fix for front cam on Arnova 8.3b1 > go to settings > developer settings > camera.enable_micro UNCHECK (all the way down in developer settings)
Back, back, exit, remove cam from memory, restart the cam...done ! :fingers-crossed::good::laugh:
The google camera APK that I've used in oreo does not work in Pie. Any new suggestions? With night sight preferably! Thanks
@hugopg
There is no version 6 gcam mod that works for our PIE, but you can use this, it works nice, and do the fix for front cam, just a post up from this.
Arnova's v8.3b1: GCam-5.1.018-Pixel2Mod-Arnova8G2-V8.3b1.apk
minnuss said:
@[email protected]
@AsItLies
@kishd
@Jamesismo
@afajri
Fix for front cam on Arnova 8.3b1 > go to settings > developer settings > camera.enable_micro UNCHECK (all the way down in developer settings)
Back, back, exit, remove cam from memory, restart the cam...done ! :fingers-crossed::good::laugh:
Click to expand...
Click to collapse
Works perfectly!
setprop persist.camera.stats.test 5
According to a newly added thread this command makes the gcam 6 version work on pie.What specifically does this command do? The OP of the said thread didnt know.