Related
[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 am using LG X-Cam K580DS( Dual SIM )
'abd reboot bootloader' works, the phone did boot into fastboot
'fastboot oem unlock' works, you'll wipe your phone by doing so
unfortunately we do not have any Recovery like CWM or TWRP, so I have no way to flash a superSU, anyone have any idea?
Yes ...
use any guide or tool for porting recoveries ..first download .kdz & extract stock recovery ..use tool to port a twrp for your device ..
Put latest magisk zip on SD card
On device
/settings/about
-enable developer options by clicking on build number
-enable adb
-uncheck verify apps by USB
-allow unknown sources
-authorize PC connection
then using adb
adb reboot bootloader
PUT PORTED RECOVERY INTO FASTBOOT/ADB FOLDER
fastboot boot recovery (name of recovery).IMG
I use :
fastboot boot recovery recovery.img
*if & when recovery boots
-swipe to allow changes
- REBOOT SYSTEM
*IGNORE CORRUPTED DEVICE MESSAGE
-boot recovery again using fastboot
-swipe to allow changes
-in fastboot flash latest magisk .zip
-reboot system & and you will have "systemless" root without custom recovery
*Hints ..look for device with similar specs and see if the recovery will boot so port won't be necessary
*DO NOT FLASH RECOVERY IMG BECAUSE LITTLE KERNEL WILL PREVENT DEVICE FROM BOOTING
*DO NOT USE SUPERSU SYSYEM DEVICE WON'T
BOOT
*COPY .ZIP TO DECOMPRESS FILE SYSYEM IF YOU WANT TO SUPERSU SYSTEMLESS OR WON'T BOOT
*CHECK OUT lg k8 thread by Gottlaz for tips on twrp porting & experience....
Good luck bro
Hey guys
I just thought we should have a 1-stop-guide for our amazing Moto Z Play. Generally people have to look through various threads before obtaining the real info, this thread was created so that people would find the resources easily without wasting time, looking here and there for information.. I will try to update the thread on regular basis as and when the new developments arrive...
Note: I want to thank all the devs for their efforts. None of this is my creation , i just collected & compiled all the info from various sources, credit as usual goes to original devs
PS: The thread is complete now...Just have to add the images for easy understanding...All the info posted here is latest development with correct info...There is no chance you will brick your phone by following this guide unless you do something wrong...
************************************************** ************************************************** ***************
INDEX************************************************** ************************************************** ***************
Drivers | ADB installer
Unlocking Bootloader (Official Method)
Flashing TWRP and Rooting via TWRP
Back up / Restoring EFS (IMEI)
Restoring original Boot Logo after unlocking bootloader
Installing Xposed Framework
Flashing/ Restoring back to Stock Rom
Changing DPI without root
Remove Ascending Ringtones/Notifications
************************************************** ************************************************** **************
1) Drivers | ADB installer
1) Motorola Drivers (https://motorola-global-portal.custh...ail/a_id/88481)
2) ADB installer (https://forum.xda-developers.com/sho....php?t=2317790) or (http://forum.xda-developers.com/show...8#post48915118)
_______________________________________
2) Unlocking Bootloader (Official Method)
Files needed:
1) Motorola Drivers (https://motorola-global-portal.custh...ail/a_id/88481)
2) ADB installed (https://forum.xda-developers.com/sho....php?t=2317790) or (http://forum.xda-developers.com/show...8#post48915118)
Note: Unlocking the bootloader erases all the data on the phone, make a backup of your imp stuff before unlocking
Method:
1) First of all visit this official Moto Unlocking site & register yourself or login via Google
https://motorola-global-portal.custh...-a/action/auth
2) Enable USB debugging & OEM unlock on the phone (Go to settings -> development options (if they do not have it enabled go to settings-> about the phone and below where it says "Compilation number" tap 7 times to activate the development options).. In the developer options, select "OEM unlock" it will ask for password / PIN / pattern and once activated, we look for "Debugging via USB" and we activate it also, then proceed to turn off the phone)
3) Turn on the phone by pressing Vol down + Power button together for 5 seconds until we get a screen like this:
4) Open adb command window and type:
Code:
fastboot devices
If your device appears on the command window you can continue with the guide, if your phone is not listed, install the Moto drivers correctly and verify if adb is working or not...
5) In the same adb command window type:
Code:
fastboot oem get_unlock_data
You will see numbers displayed like this, copy the code and paste it into notepad..Now eliminate the paragraph break so that there is only one line without spaces… Copy the entire code & login into your Moto account…Now paste the code on the same Moto webpage which was given above…
The unlock code will be sent to your registered email. There will appear an email with the number similar to this:
5)Without disconnecting the phone from the PC & without closing the window of the CMD, we return & we put this code:
Code:
fastboot oem unlock (enter code that was provided in the email)
6) You will be asked to re-enter the same command again, re-enter the code to confirm and finally unblock the bootloader
7) After re-entering the command, you will bootloader unlocked message
_______________________________________
3) Flashing TWRP and Rooting via TWRP
Note: Custom recovery (TWRP) woks only after unlocking your bootloader… Before flashing this recovery unlock your bootloader and enable USB debugging…
Files required:
1) Motorola drivers (https://motorola-global-portal.custh...ail/a_id/88481)
2) ADB installed (https://forum.xda-developers.com/sho....php?t=2317790) or (http://forum.xda-developers.com/show...8#post48915118)
3) TWRP for Moto Z Play (https://mega.nz/#!yZ4lUCYB!-nN0jj2Ws5Z7RNyBT7S8m4gsrdOxTlK3nTjn9zOtx6s)
Method:
1) Download the above recovery, boot the phone in fastboot mode & open adb command window
2) In the adb command window type
Code:
fastboot flash recovery recovery.img
3) After executing the command, disconnect your phone & with the volume + or volume keys - we move until it says "Recovery Mode" . Press the power button to confirm the entry to the recovery.
4) Once you enter the recovery, select the right button & a menu to choose the language is displayed, it only brings Chinese and English so we will put it in English to know what to do.
5) We will see that it asks for a password, it is the same password that you put to encrypt the phone at the beginning when they set up the factory phone and always asks them to turn on the phone, it can be a password / PIN / pattern
6) Once the password has been entered, the recovery main menu will appear, we will go to "Advanced" and then "Install SU", it will ask if we want to root the phone, we accept by sliding and we wait for it to do the process. Then we give in "Reboot System" to restart and the phone will ignite with root
_______________________________________
4) Backing up / Restoring EFS (IMEI)
Note: This works only if you have TWRP recovery... Please backup your EFS using the method below before flashing any rom including stock rom
Backing up EFS (IMEI):
Method:
1) Boot the phone into TWRP recovery
2) Go to "Backup"
3) Select EFS
4) Create backup by sliding
5) Once finished, restart the phone
6) After restarting the phone, copy the TWRP folder from the internal memory to the SD, DO NOT CUT and PASTE, just copy with a file browser. Later from the SD card can be copied to the PC
Restoring lost IMEI / EFS:
Method:
1) Boot the phone into TWRP recovery
2) Go to "Restore"
3) Select folder (location where you have kept a backup of your EFS)
4) Restore by sliding
5) Wipe cache and dalvik and start phone normally
_______________________________________
5) Restoring original Boot Logo after unlocking bootloader
PS: This is used to remove unlocked bootloader warning when the phone is turned on (the black screen with letters)
Credit goes to : G4liant
Files needed:
1) Motorola drivers (https://motorola-global-portal.custh...ail/a_id/88481)
2) ADB installed (https://forum.xda-developers.com/sho....php?t=2317790) or (http://forum.xda-developers.com/show...8#post48915118)
3) Original Motorola Bootlogo (https://mega.nz/#!zNIFHBiY!hbdgUwl9oWjrXbirwXKijviWW0nS_06MViU48yHmSD4)
Method:
1) Boot the phone in fastboot mode, open adb window on pc and type
Code:
fastboot flash logo logo.bin
2) Once the flashing is finished, restart the phone with this command:
Code:
fastboot reboot
When you turn it on, we will notice that we have the original motorola boot logo again and that the previous warning does not appear even when the bootloader of our device is unlocked
_______________________________________
6) Installing Xposed Framework
Files needed:
1) [FONT="]Have TWRP installed (If not installed refer to section #3 on this thread)
2) Download latest Xposed Installer.zip (http://dl-xda.xposed.info/framework/sdk23/arm/ )
3) Download latest Xposed Apk (https://forum.xda-developers.com/showthread.php?t=3034811)
Optional: Download latest Xposed un-installer but ARM 32 version not ARM 64 (http://dl-xda.xposed.info/framework/uninstaller/ )[/FONT]
Method:
1) Copy Xposed installation .zip, Xposed uninstaller (optional) and the Xposed APK to the internal memory (the TWRP does not mount the external SD so do not bother copying it to the External Memory)
2) Install the Xposed APK but DO NOT open it.
3) Enter recovery mode and open TWRP, Choose language and enter password to decrypt your device
4) Once the password is entered, the main recovery menu will appear, select "Install" and a file manager will appear, we will navigate the file down and look for the Xposed installer .zip, something like this:
5) Select the Xposed installer .zip and it will open a zip installer, slide to accept the flash of the .zip and wait for the process to finish. Then we give in "Wipe Dalvik / cache" and then to "Reboot System" to reboot and the phone will light up with Xposed already working.
_______________________________________
7) Flashing/ Restoring back to Stock Rom
IMPORTANT: First locate the firmware for your country / operator / area / continent to avoid changing baseband or other things that make the phone does not work as it should.
Credit goes to: Khanov XDA
Stock Rom links:
[FONT="]Stock China
http://www.filefactory.com/file/6814...LT_CFC.xml.zip
Rogers Canada
http://www.filefactory.com/file/57g6...LT_CFC.xml.zip
Retail Latino America
http://www.filefactory.com/file/6pt8...%20%281%29.zip
Retail Latin America
https://mega.nz/#!WBYX3awb!qR1zitz1O...M1tnq1OwWDYDYA
Retail Europe
http://www.filefactory.com/file/4ora...C_EMEA.xml.zip
Retail Canada
http://www.filefactory.com/file/64wm...LT_CFC.xml.zip
Movistar Colombia
http://www.filefactory.com/file/10sv...LT_CFC.xml.zip.
Verizon
http://www.filefactory.com/file/60ty...LT_CFC.xml.zip
A Repository with several firmwares including Indian:
https://mirrors.lolinet.com/firmware...ison/official/[/FONT]
[FONT="]
Files needed: [/FONT]
[FONT="]1) Motorola drivers (https://motorola-global-portal.custh...ail/a_id/88481)
2) ADB installed (https://forum.xda-developers.com/sho....php?t=2317790) or (http://forum.xda-developers.com/show...8#post48915118)
3) Firmware chosen from above links[/FONT]
[FONT="]
[/FONT]
Method 1 (Manually by using adb commands):
1) Boot the phone into fastboot mode and open adb command window on pc
Code:
fastboot devices
This will show us if the phone is correctly connected and installed the drivers, it will detect the PC in fastboot mode and we can continue with the tutorial we will put these commands in the order they are, you can put them one at a time and pressing enter to execute it
Code:
[SIZE=2][B][FONT=Century Gothic]fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash NON-HLOS.bin modem [COLOR=Red]([/COLOR][COLOR=Red][I]can skip this and thus [U]would[/U] prevent loss of IMEI)[/I][/COLOR]
fastboot erase modemst1 [I] [COLOR=Red](can skip this and thus [U]would[/U] prevent loss of IMEI)[/COLOR][/I]
fastboot erase modemst2 [COLOR=Red][I]([/I][/COLOR][COLOR=Red][I]can skip this and thus [U]would[/U] prevent loss of IMEI)[/I][/COLOR]
fastboot flash fsg fsg.mbn [COLOR=Red][I](can skip this and thus [U]would[/U] prevent loss of IMEI)[/I][/COLOR]
fastboot erase cache
fastboot erase userdata [COLOR=Red]([/COLOR][COLOR=Red][I]can skip this and thus [U]would[/U] prevent loss of your data (Internal storage)[/I][/COLOR]
[/FONT][/B][/SIZE][SIZE=2][B][FONT=Century Gothic] fastboot oem fb_mode_clear
fastboot reboot
[/FONT][/B][/SIZE]
Your phone will reboot and will be restored to stock rom
In case an error occurs during OTA, even after doing the above step flash the modem by typing:
NOTE: You will find these files (NON-HLOS.bin, fsg.mbn, adspso.bin etc) along with the systemchunk files you downloaded
Code:
[/FONT][/B][/SIZE][/SIZE][SIZE=2][SIZE=2][B][FONT=Century Gothic]fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
Now reboot the phone and apply OTA... It will succeed
Method 2 (Using software ; RSD lite to flash) :
Files needed:
1) Motorola drivers (https://motorola-global-portal.custh...ail/a_id/88481)
2) ADB installed (https://forum.xda-developers.com/sho....php?t=2317790) or (http://forum.xda-developers.com/show...8#post48915118)
3) RSD lite (http://rsdlite.com/rsd-lite-download/)
4) Stock Rom from the links provided above
Method:
1) Enable USB debugging
2) Download RSDlite and Stock Rom zip file
3) Open RSDlite and browse button (next to file name textbox)... Find and select "flashfile.xml" from the downloaded zip file (extract the zip file)
4) Boot the phone into fastboot mode and connect the phone to pc; RSD lite shows ID if connected
5) Click start button…Now flashing process has started…It will flash files one by one…Wait for it till it shows reboot…
[FONT="]6) Handset will automatically restart after flashing process completes[/FONT]
_______________________________________
8) Changing DPI without root
Files needed:
1) Motorola drivers (https://motorola-global-portal.custh...ail/a_id/88481)
2) ADB installed (https://forum.xda-developers.com/sho....php?t=2317790) or (http://forum.xda-developers.com/show...8#post48915118)
Method:
Note: The DPI used here is 420... You can adjust the DPI according to your own taste... The default DPI is 480
1) Open ADB command window and enter:
Code:
[FONT=Century Gothic][B][B][B][FONT=Century Gothic][B][B][B]adb shell wm density 420[/B][/B][/B][/FONT][/B][/B][/B][/FONT]
2) Reboot your phone to apply the effects system wide
Reverting back to stock DPI:
Method:
1) Open ADB command window and enter:
Code:
[FONT=Century Gothic][B][B][B][FONT=Century Gothic][B][B][B][FONT=Century Gothic][B][B][B][FONT=Century Gothic][B][B][B]adb shell wm density 480"[/B][/B][/B][/FONT] or "[/B][/B][/B][/FONT][FONT=Century Gothic][B][B][B][FONT=Century Gothic][B][B][B][FONT=Century Gothic][B][B][B]adb shell wm size reset" (If the 1st one doesnt work or some apps show wrong layouts like Snapchat etc[/B][/B][/B][/FONT][/B][/B][/B][/FONT][/B][/B][/B][/FONT][/B][/B][/B][/FONT][/B][/B][/B][/FONT]
2) Reboot your phone to apply the effects system wide
_______________________________________
9) Remove Ascending Ringtones/Notifications
Files needed:
1) TWRP
2) Ringtones / Notifications mod (http://cloud.tapatalk.com/s/58221f724bc3b/Ascending_audio_fix_motozplay.zip)
Method:
1) Download the mod and copy it to internal storage. Boot the phone in TWRP
2) Select install and locate the file in the file manager... Select the file and flash it
Reverting back to stock (Ascending ringtones):
Method:
1) Download this file [FONT="]https://www.dropbox.com/s/otsir98jjlqnb85/Ascending_audio_stock_motozplay.zip?dl=0https://www.dropbox.com/s/otsir98jjlqnb85/Ascending_audio_stock_motozplay.zip?dl=0
2) Copy it to internal storage & boot the phone in TWRP... Select install and locate the file
3) Select the file and flash it[/FONT]
reserved...
reserved
Nicely work
Really nice thread. Just one thing...
Could you credit me for the modified logo.bin?
https://forum.xda-developers.com/showpost.php?p=69273602&postcount=37
Can I flash logo.bin zip in twrp?
Nope, has to be unzipped and flashed in fastboot, which shouldn't make much of a difference, as it has only to be done once. No need for reflashing after switching your custom rom.
G4liant said:
Really nice thread. Just one thing...
Could you credit me for the modified logo.bin?
https://forum.xda-developers.com/showpost.php?p=69273602&postcount=37
Click to expand...
Click to collapse
Sure man...Edited the OP... :good: Actually i found it on another site it didnt mention anyone so i posted like that only....Anyways nice work
Thanks and very useful.
Hey guys, it takes an incredibly long time to download the stock ROM, anybody have a solution for this? It also just stops and says 'network error' at 0.3gb. So I can't unbrick my phone really.
coolkingler1 said:
Hey guys, it takes an incredibly long time to download the stock ROM, anybody have a solution for this? It also just stops and says 'network error' at 0.3gb. So I can't unbrick my phone really.
Click to expand...
Click to collapse
More firmware found here https://mirrors.lolinet.com/firmware/moto/addison/official/
Sent from my XT1635-02 using XDA-Developers Legacy app
flashallthetime said:
More firmware found here https://mirrors.lolinet.com/firmware/moto/addison/official/
Sent from my XT1635-02 using XDA-Developers Legacy app
Click to expand...
Click to collapse
I found a good mirror at the Rooting thread but thanks!
TWRP flashing file download link dead
3rd section file needed are not expanding when that button is clicked some kind of glitch I think can you share the link directly.
abhilash_s_j said:
3rd section file needed are not expanding when that button is clicked some kind of glitch I think can you share the link directly.
Click to expand...
Click to collapse
Nope works fine for me...anyways here is the direct link:
https://mega.nz/#%21yZ4lUCYB%21-nN0jj2Ws5Z7RNyBT7S8m4gsrdOxTlK3nTjn9zOtx6s
Thank you for the effort
Thanks for your work!
Sent from my Nexus 6 using XDA-Developers Legacy app
TWRP flashing file download link dead
3rd section file needed are not expanding when that button is clicked some kind of glitch I think can you share the link directly.
---------- Post added at 01:37 AM ---------- Previous post was at 01:14 AM ----------
After flashing the original firmware of my device, there is no network signal, i cannot make calls, cannot use data, in general the SIM does not work. Does anyone knows how to solve this?
kkarora said:
TWRP flashing file download link dead
3rd section file needed are not expanding when that button is clicked some kind of glitch I think can you share the link directly.
---------- Post added at 01:37 AM ---------- Previous post was at 01:14 AM ----------
After flashing the original firmware of my device, there is no network signal, i cannot make calls, cannot use data, in general the SIM does not work. Does anyone knows how to solve this?
Click to expand...
Click to collapse
Check your IMEI, I think that you have lost It.
Hitachy said:
Check your IMEI, I think that you have lost It.
Click to expand...
Click to collapse
Yes IMEI is showing 0. How to restore it back...?
kkarora said:
Yes IMEI is showing 0. How to restore it back...?
Click to expand...
Click to collapse
If you have a twrp backup, restore It. If you don't have, assistance.
Hey Guys,
I have a redmi 3s prime and i tried to install lineage os on it, during the process i accidentaly flashed twrp over both the recovery and the boot. Now i cannot get into the recovery (and fastboot) unless i flash it over boot before rebooting my phone. After that i AM able to flash an new rom but it seems to always have wifi issues.
atm i am trying to flash the xiaomi developers global rom to see if it makes any difference. My main goal is to flash TWRP and a curstom rom (linage or resurrectionremix).
Can anyone help me?
Thanks alot!
Update #1
The flashing of the global developer rom worked and the wifi seems to work aswell, i will try to boot into fastboot and recovery.
Update #2
Its seems i am able to boot into fastboot and recovery again
Update #3
Following a tutorial for flashing TWRP and a custom rom but cant se2 anyone help me here?:
Code:
>>> Check then next step to root :
- launch minimal adb tool (previously installed)
- type : adb devices (to list phone connected) it will appear "unauthorized"
- on the phone : accept the computer
- re type : adb devices
it has changed in "authorized"
- type : adb reboot bootloader
it will go in fastboot mode (the same that power + vol down)
- type : fastboot devices
your phone will appear as in adb mode (unless the bad signed driver is choosen in win10 ; i won't repeat it again)
- type (optional) : fastboot oem device-info (to verify if bootloader is locked or unlocked)
now, we go to root
- type : fastboot boot twrp.img (if it is your renamed twrp copied in the minimal adb folder)
link for TWRP guide at the end if needed
!!! it will boot temporary in this recovery but it will keep your original recovery !!!
> allow to modify system (don't keep the "read only" if you want to root or flash recovery later)
go to settings to set date, hours, language, set custom options...
My optional advices :
- save your EFS & persist partitions or all whole partitions (except cache) to make a backup
- export this backup in computer or SD card in case of future problem
(EFS, persist are usefull to save and restore your IMEI in particular)
- you can flash directly TWRP with fastboot command : fastboot flash recovery twrp.img
>>> Root :
Now flash DM-verity patch, then superSU.zip to root and accept to wipe dalvik/cache after, finally reboot !
Device is rooted ! and you have kept the original recovery.
the reboot is quite long like rom update (because of cache rebuild)
sometimes, parts of theme are lost after rooting : just restore your theme
some devices don't need DM-verity patch as explained upper
superSU app shows "systemless root" from android 6+, it is normal, read below
>>> Change the Recovery by TWRP (optional) :
Now you are rooted, you have 2 methods :
- Install one TWRP app with googleplay and flash recovery through app on rooted device.
New official app in development (flash/backup .img & .tar)
- OR reboot in fastboot mode (with TWRP app method or power+vol- method or adb reboot recovery method)
in fastboot mode, and type commands :
fastboot devices
fastboot flash recovery twrp.img
(be sure your twrp.img is unlocked and correctly copied/renamed in minimal adb folder)
Now, long press power to turn OFF phone
power + vol+ (release power at vibration) to enter in TWRP or by TWRP app or Updater app or under Windows with minimal adb reboot recovery command
Note for devices with DM-verity : flashing TWRP needs to have patched system with DM-verity patch before because you will modify system most of time - generally, you don't need to patch again because you have ever done it in previous steps - in case of bootloop : go to fastboot mode, boot in TWRP with command and patch it.
Chainfire has recently modified superSU for android 6+ devices with DM-verity to install root without modify the system : it's called "systemless root". When you flash superSU.zip, it detects automatically android version, cleans old files and installs with appropriate method. Maybe no need to patch boot in this case with DM patch.
Hello,
Many people report, that their TWRP/PBRP is black and they can't install custom ROM or flash stock ROM by recovery.
Problem occurs in devices with Jdi display.
It is recommended to flash Oreo, then recovery work, but if you want use Android Pie you must be on this stock firmware (I tried Oreo and flash Havoc (Pie) = bootloop).
We need:
Unlocked bootloader
Turned on android debugging
ADB (minimum 1.4.3)
TWRP/PBRP (.img file)
ROM, GAPPS,...
YOUR DATA/PHOTOS/DOWNLOADS WILL BE REMOVED, SO MAKE A BACKUP!
Let's get started:
1. FLASHING ROM
/the phone is on/
1. Use cmd and type: adb reboot-bootloader
<phone will turn on in fastboot mode>
2. Type: fastboot set_active b
Then: fastboot boot <your_recovery.img>, e.g. fastboot boot twrp.img
<phone will reboot, the screen will be black>
<wait to Windows new device sound>
3. Type: adb shell
twrp wipe cache
twrp wipe dalvik
twrp wipe system
twrp wipe data <- NOW YOUR DATA WILL BE REMOVED, SO MAKE A BACKUP BEFORE!
twrp sideload
adb sideload <location_of_your_ROM.zip>, e.g. adb sideload C:\Havoc.zip
When the installation is completed you will see "Total xfer X.XXx".
2. FLASHING GAPPS
Now: adb reboot-bootloader
<phone will turn on in fastboot mode>
fastboot set_active a
fastboot boot <your_recovery.img>, e.g. fastboot boot twrp.img
<phone will reboot, the screen will be black>
<wait to Windows new device sound>
adb shell
twrp wipe cache
twrp wipe dalvik
twrp sideload
adb sideload <location_of_your_GApps.zip>, e.g. adb sideload C:\GApps.zip
When the installation is completed you will see "Total xfer X.XXx".
3. FLASHING PATCHED BOOT IMAGE (MAGISK + ROOT)
adb reboot-bootloader
fastboot flash boot <your_patched_boot.img>, e.g. fastboot flash patched_boot.img
fastboot reboot
<phone will start, the first start may take some time>
It's instruction for performing these three steps sequentially.
System will be installed on slot B, the Gapps and patched boot on slot A.
Now you can enjoy custom ROM
Greetings
Flash999 said:
Hello,
Many people report, that their TWRP/PBRP is black and they can't install custom ROM or flash stock ROM by recovery.
Problem occurs in devices with Jdi display.
It is recommended to flash Oreo, then recovery work, but if you want use Android Pie you must be on this stock firmware (I tried Oreo and flash Havoc (Pie) = bootloop).
We need:
Unlocked bootloader
Turned on android debugging
ADB (minimum 1.4.3)
TWRP/PBRP (.img file)
ROM, GAPPS,...
YOUR DATA/PHOTOS/DOWNLOADS WILL BE REMOVED, SO MAKE A BACKUP!
Let's get started:
1. FLASHING ROM
/the phone is on/
1. Use cmd and type: adb reboot-bootloader
<phone will turn on in fastboot mode>
2. Type: fastboot set_active b
Then: fastboot boot <your_recovery.img>, e.g. fastboot boot twrp.img
<phone will reboot, the screen will be black>
<wait to Windows new device sound>
3. Type: adb shell
twrp wipe cache
twrp wipe dalvik
twrp wipe system
twrp wipe data <- NOW YOUR DATA WILL BE REMOVED, SO MAKE A BACKUP BEFORE!
twrp sideload
adb sideload <location_of_your_ROM.zip>, e.g. adb sideload C:\Havoc.zip
When the installation is completed you will see "Total xfer X.XXx".
2. FLASHING GAPPS
Now: adb reboot-bootloader
<phone will turn on in fastboot mode>
fastboot set_active a
fastboot boot <your_recovery.img>, e.g. fastboot boot twrp.img
<phone will reboot, the screen will be black>
<wait to Windows new device sound>
adb shell
twrp wipe cache
twrp wipe dalvik
twrp sideload
adb sideload <location_of_your_GApps.zip>, e.g. adb sideload C:\GApps.zip
When the installation is completed you will see "Total xfer X.XXx".
3. FLASHING PATCHED BOOT IMAGE (MAGISK + ROOT)
adb reboot-bootloader
fastboot flash boot <your_patched_boot.img>, e.g. fastboot flash patched_boot.img
fastboot reboot
<phone will start, the first start may take some time>
It's instruction for performing these three steps sequentially.
System will be installed on slot B, the Gapps and patched boot on slot A.
Now you can enjoy custom ROM
Greetings
Click to expand...
Click to collapse
Work well.. buuuut.... i think tha hard drive of phone is encrypted... and inwritable, so... works! but is not functional
Wormboymx said:
Work well.. buuuut.... i think tha hard drive of phone is encrypted... and inwritable, so... works! but is not functional
Click to expand...
Click to collapse
The data partition is encrypted. If you want to access this partition you have to format it by TWRP. When you start system with forced encryption, the data will be again encrypted (or use custom ROM without encryption or install script to disable it on stock software).
Flash999 said:
The data partition is encrypted. If you want to access this partition you have to format it by TWRP. When you start system with forced encryption, the data will be again encrypted (or use custom ROM without encryption or install script to disable it on stock software).
Click to expand...
Click to collapse
Ok, can you help me with that? I think with you excellent guide maybe is missing one step to avoid this.
Thanks!
Wormboymx said:
Ok, can you help me with that? I think with you excellent guide maybe is missing one step to avoid this.
Thanks!
Click to expand...
Click to collapse
I had a similar problem while using twrp to copy files to the phone storage, try this command before doing anything:
fastboot -w
Note: This wipes all data.
This made the phone storage accessible.
mma_1494 said:
I had a similar problem while using twrp to copy files to the phone storage, try this command before doing anything:
fastboot -w
Note: This wipes all data.
This made the phone storage accessible.
Click to expand...
Click to collapse
Doesn´t work too =(
"fastboot -w
wiping userdata...
CreateProcess failed: El sistema no puede encontrar el archivo especificado. (2)
error: Cannot generate image for userdata"
i Will back to stock rom Pie...
P.D. the encryption is when finishi whole process in the installed custom rom the hard drive doesn't work e.g... Open the camera and system say "Don't have sd card to save the files"
where will get patched_boot.img for mi a2 10.0.2 or 10.0.4
where will get patched_boot.img for mi a2 10.0.2 or 10.0.4
asad0181 said:
where will get patched_boot.img for mi a2 10.0.2 or 10.0.4
Click to expand...
Click to collapse
On this Youtube channel https://www.youtube.com/channel/UCuEtuySiR1DDYCRerutqvnA/videos
You can get some files...
Hello! How do I know if my device has a Jdi display panel? If it does have, do I need to follow this guide every time I flash or update a rom?
chrisdlc119 said:
Hello! How do I know if my device has a Jdi display panel? If it does have, do I need to follow this guide every time I flash or update a rom?
Click to expand...
Click to collapse
Try to boot TWRP on Pie, if you see TWRP GUI mean you don't have Jdi display. You don't have to flash anything, only boot by fastboot.
It depends of your ROM and system updater, I follow the guide to flash new version and all is working ok.
Flash999 said:
Try to boot TWRP on Pie, if you see TWRP GUI mean you don't have Jdi display. You don't have to flash anything, only boot by fastboot.
It depends of your ROM and system updater, I follow the guide to flash new version and all is working ok.
Click to expand...
Click to collapse
I think my display is tianman (ss atached). Is that right? Do you know if any display is affected with burning effect? It's just that I had a RN5 and I changed from MIUI to a custom ROM and one day the display just got the burning effect
Thanks for your reply.
Wormboymx said:
Doesn´t work too =(
"fastboot -w
wiping userdata...
CreateProcess failed: El sistema no puede encontrar el archivo especificado. (2)
error: Cannot generate image for userdata"
i Will back to stock rom Pie...
Click to expand...
Click to collapse
I'm getting the same error when doing fastboot -w, and the ROM I flashed (Resurrection Remix) is stuck on startup splash screen.
Any idea what can cause this, and how I can recover?
mma_1494 said:
I had a similar problem while using twrp to copy files to the phone storage, try this command before doing anything:
fastboot -w
Note: This wipes all data.
This made the phone storage accessible.
Click to expand...
Click to collapse
Thanks! Now I could install Havoc and have access to my files!
Op you should include ,,fastboot -w" in your guide.
Finally i can boot PitchBlack recovery without Blackscreen in JDI panels::
Boot this recovery file: https://sourceforge.net/projects/pitchblack-twrp/files/jasmine_sprout/
Only one difference between the guide of this Thread....
I can´t change the partitions in PitchBlack recovery... i used the command in the op to change the partitions.... NOW i can flashed the Resurection remix rom in my phone
hlg1 said:
I'm getting the same error when doing fastboot -w, and the ROM I flashed (Resurrection Remix) is stuck on startup splash screen.
Any idea what can cause this, and how I can recover?
Click to expand...
Click to collapse
So, I was able to recover from this by using Xiaomi Flash Tool (v20170425) to flash the V10.0.7.0 stock rom. That got me back to a working stock Android.
I then retried the steps from this guide (except Gapps and patched boot), and this time I was able to get my Resurrection Remix started. However, the userdata file structure looks like rubbish, and none of the apps can write to or read from it. I tried to do a factory reset (from within custom rom) to fix this, but then the phone turned off and would not boot to custom rom again. fastboot -w still doesn't work.
Any ideas how to make the userdata partition great again?
hlg1 said:
So, I was able to recover from this by using Xiaomi Flash Tool (v20170425) to flash the V10.0.7.0 stock rom. That got me back to a working stock Android.
I then retried the steps from this guide (except Gapps and patched boot), and this time I was able to get my Resurrection Remix started. However, the userdata file structure looks like rubbish, and none of the apps can write to or read from it. I tried to do a factory reset (from within custom rom) to fix this, but then the phone turned off and would not boot to custom rom again. fastboot -w still doesn't work.
Any ideas how to make the userdata partition great again?
Click to expand...
Click to collapse
I made it work by doing the first 2 steps from the OP and then after booting into system the first time I booted into bootloader and then used fastboot -w. I did this with Havoc OS though so it might not work for everyone.
When I wanted root and didn't know how to get a patched boot image for my ROM, I just followed the steps to access TWRP through ADB again and then wiped cache and dalvik, afterwards I used the sideload command to flash Magisk on my phone.
hlg1 said:
Any ideas how to make the userdata partition great again?
Click to expand...
Click to collapse
I eventually figured out that all my problems occurred because I was using old versions of ADB and fastboot. After updating to latest platform-tools (currently r28.0.2) I was able to run fastboot -w without problems. And once that worked I was able to set up a fully working system following the steps of this guide.
Thanks for a very useful guide, it saved my day!
i got failed command write failed. any suggestion?
I was also having the black screen problem
Can i flash twrp recovery while keeping the stock rom? If can sombody please help me
Sarath_sh said:
I was also having the black screen problem
Can i flash twrp recovery while keeping the stock rom? If can sombody please help me
Click to expand...
Click to collapse
I'm not entirely sure I understand your question, but please note that by following the OP instructions you never flash TWRP, you just boot right into it from RAM. So should be no problem to do that while keeping stock ROM.