Related
Heisenberg's How-To Guide For Beginners
Nexus 6P
{
"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"
}
Intro
This thread will serve as a location for basic how-to guides for the Nexus 6P. 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 #3 before creating a post to ask a question.
Prerequisites
Always update your phone to the latest build available before starting the unlocking/rooting process. This guide is always current/correct as per the requirements of the most recent build available.
You'll need a working adb/fastboot environment on your PC to get through some of these guides.
Google have finally decided to allow us to install adb & fastboot without needing to install the entire Android SDK. Hurrah! What does this mean for you? Much less mucking around. Grab the appropriate version for your OS:
Platform tools for Windows | Google USB driver for Windows
Platform tools for Linux
Platform tools for Mac
Main Page
Simply download and extract the archive (and follow the linked instructions for the Google USB Driver for Windows). Once you've extracted the download you should have a platform-tools folder, within that folder you should see fastboot and adb. I'll refer to this as your fastboot folder/directory or working folder/directory during this guide. To make sure adb is correctly installed, open a command prompt from within your fastboot folder (hold shift + right click, select open command prompt here) and issue this command:
Code:
adb version
If it returns a version number for Android Debug Bridge then you're good to go.
You can test adb by connecting your device to your PC while booted into Android (making sure that adb/usb debugging is enabled in Settings>Developer Options) with the screen unlocked and issuing this command:
Code:
adb devices
It should return your device serial number, if so, adb is working.
You can test fastboot by connecting your device to your PC while booted into the bootloader (power + volume down) and issuing this command:
Code:
fastboot devices
It should return your device serial number, if so, fastboot is working.
Please see older method for installing adb/fastboot here:
You must have Java installed and up to date in order to use the SDK Manager, please ensure that this is taken care of before installing the SDK.
Please do not install adb/fastboot via any means other than the Android SDK, using other tools (like Minimal adb & fastboot) can lead to an outdated setup and various problems with flashing. You've been warned, other tools will not be supported in this thread.
Go here to download the Android SDK, which will give you most updated version of adb and fastboot. Scroll to the bottom of the page and find Other Download Options>SDK Tools Only, and grab the right version for your OS. While it's downloading create a folder in C:\ called SDK (C:\SDK). Once you've downloaded the zip you can extract it into your C:\SDK folder. Navigate to C:\SDK\android-sdk-windows and open SDK Manager.exe. In SDK Manager you need to install the following packages:
Tools> Android SDK Tools, Android SDK Platform-tools
Extras> Android Support Library, Google USB Driver
Once you have installed those, inside C:\SDK you should see some new folders, one of them will be called platform-tools, within that folder you should see fastboot.exe and adb.exe. I'll refer to this as your fastboot folder/directory or working folder/directory during this guide. To make sure adb is correctly installed, open a command prompt from within your fastboot folder (hold shift + right click, select open command prompt here) and issue this command:
Code:
adb version
If it returns a version number for Android Debug Bridge then you're good to go.
You can test adb by connecting your device to your PC while booted into Android (making sure that adb/usb debugging is enabled in Settings>Developer Options) with the screen unlocked and issuing this command:
Code:
adb devices
It should return your device serial number, if so, adb is working.
You can test fastboot by connecting your device to your PC while booted into the bootloader (power + volume down) and issuing this command:
Code:
fastboot devices
It should return your device serial number, if so, fastboot is working.
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.
Quick Tips
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).
Index
Post #1
1. How To Unlock Your Bootloader
2. How To Install A Custom Recovery On Your Device
3. How To Decrypt Your Data Partition
4. How To Make A Nandroid Backup With TWRP Recovery
5. How To Make An EFS Backup With TWRP Recovery
6. How To Root
Post #2
7. How To Install A ROM with TWRP Recovery
8. How To Install A Custom Kernel With TWRP Recovery
9. How To Update To A New Build Of The Stock ROM
10. How To Flash The Factory Images (Return To Stock)
11. How To Flash The Factory Images (Return To Stock But Leaving Internal Storage Intact)
12. How To ADB Sideload an incremental OTA update package.
13. How To ADB Sideload a full OTA update package.
14. How To Update To Android 7.0 Nougat
FAQ can be found in post #3!
1. How To Unlock Your Bootloader
Go into Settings/About Phone, scroll down and click on “build number†continuously until you see a toast notification telling you that you've enabled Developer Options. Go back to your Settings menu and enter Developer Options, scroll down and click on the “Enable OEM Unlock†checkbox, also make sure you enable USB Debugging while you're in the Developer Options menu.
Power off your phone then boot into the bootloader (power + volume down).
Connect your phone to your PC via usb cable.
Open a command prompt from within your fastboot folder (navigate to where you have fastboot.exe located on your PC, shift + right click anywhere within that folder, select open command prompt here).
Check your fastboot connection by issuing this command:
Code:
fastboot devices
It should return your device serial number, if not you need to make sure your drivers are installed correctly.
Once you've confirmed your fastboot connection issue the unlock command:
Code:
fastboot flashing unlock
This will erase all user data from the device!
You should now see a screen on your phone asking you to confirm this action, use the volume keys to scroll and the power key to confirm if you're sure you want to go ahead.
Allow the process to complete and then issue this command:
Code:
fastboot reboot
Allow everything to go ahead and once finished you can disconnect your usb cable.
Note: After unlocking your bootloader, each time your phone boots up you'll be greeted with a warning that says "Your device software can't be checked for corruption. Please lock the bootloader". This is nothing to worry about, it's normal to see this when you have an unlocked bootloader. You can't remove it, as long as your bootloader is unlocked it will stay there.
Important: do not relock your bootloader unless your phone is fully stock. You must flash the factory images first in order to remove root and custom recovery (if you have them), if this precaution isn't taken you may end up with a brick. Please see section 10 of this guide for full instructions on how to return to stock.
2. How To Install A Custom Recovery On Your Device
Prerequisites: unlocked bootloader (section 1).
Download the latest TWRP Recovery.
Make sure you check the md5 of the file to verify its integrity (where possible).
Place the file in your fastboot folder (this is where fastboot.exe is located on your PC).
Boot into the bootloader. Open a command prompt from within your fastboot folder (navigate to where you have fastboot.exe located on your PC, shift + right click anywhere within that folder, select open command prompt here), enter this command:
Code:
fastboot 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 you can 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.
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.
On Nougat you need to flash SuperSU after booting into TWRP otherwise TWRP won't stick (see section 6).
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.
3. How To Decrypt Your Data Partition
This is no longer necessary as long as you use TWRP 2.8.7.1 or newer, unless you are using the Android N developer preview, in which case you must decrypt.
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
4. How To Make A Nandroid Backup With TWRP Recovery
Prerequisites: unlocked bootloader (section 1), TWRP recovery (section 2).
Warning: before you make a backup with TWRP you must remove all lockscreen security. If you do not do this you will not be able to unlock your device after restoring your backup (entering your pin will result in an "incorrect pin" message), you'll be forced to perform a factory reset to boot into Android. To remove lockscreen security go to Settings>Security>Screen Lock and set it to swipe/none.
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 into TWRP and select the backup option from the TWRP home screen, check the system/data/boor boxes, and swipe to backup. The process will take a few minutes.
Note: If you happened to forget to remove lockscreen security (PIN/Pattern/Fingerprint) before creating your backup, and you cannot get into your OS after restoring, you can do the following to fix the issue. Boot into TWRP and use the built in file manager to delete /data/sytem/locksettings.db. This should be enough to get you into your OS again. If it isn't you can also try deleting /data/system/locksettings.db-shm and /data/system/locksettings.db-wal. If this still doesn't fix your issue you can delete /data/system/gatekeeper.password.key and /data/system/gatekeeper.pattern.key.
5. How To Make An EFS Backup With TWRP Recovery
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.
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.
6. How To Root
Prerequisites: unlocked bootloader (section 1), TWRP recovery (section 2).
Download the latest root version (Magisk, SuperSU) of your choosing to your phone:
Magisk Stable
Magisk Beta
SuperSU Stable
SuperSU Beta
Boot into TWRP recovery and enter the install menu.
Navigate to where you have the root zip stored on your internal storage and select it.
Swipe to install.
Once the zip has installed 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.
FAQ can be found in post #3!
Donate To Me
FAQ can be found in post #3!
7. How To Install A ROM with TWRP Recovery
Prerequisites: unlocked bootloader (section 1), TWRP recovery (section 2).
Installing a ROM is a pretty straight forward and easy process. Before you install anything you should make a nandroid backup (instructions above).
Download a ROM and appropriate Gapps package and place on your device. You'll also need to find out what build your ROM is based on and download the vendor image for that build, you'll find the latest in my index here.
Boot into your custom recovery.
Perform a full wipe.
Select the wipe option from the TWRP home screen.
Select advanced wipe.
Check the system, data, cache, and dalvik cache options.
Swipe to wipe.
Install the ROM.
Select the install option from the TWRP home screen.
Navigate to where you have the ROM zip stored on your internal storage and select it. You can hit the "add more zips" button now to queue up your gapps package to be flashed after the ROM zip.
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.
Hit the home button once everything has finished installing.
Install the appropriate vendor image.
Select the install option from the TWRP home screen.
Click the "install image" button in the bottom-right corner.
Navigate to where you have the vendor image stored on your internal storage and select it.
You'll now be asked which partition to flash the image to, select vendor.
Swipe to install.
Once you've installed all necessary zips/images you'll have an option to wipe cache/dalvik and an option to reboot system, hit the reboot system button and you'll boot into your new ROM.
8. How To Install A Custom Kernel With TWRP Recovery
Prerequisites: unlocked bootloader (section 1), TWRP recovery (section 2).
A custom kernel can open up a new level of control over your device, such as overclocking/underclocking, undervolting, changing governors, changing I/O schedulers, adjusting colour calibrations, adjusting sound calibrations, and many other options.
Download a kernel that is compatible with your current ROM.
Check the md5 to verify its integrity.
Enter TWRP recovery.
Select the install option from the TWRP home screen.
Navigate to the kernel and select it.
Swipe to install.
You'll have an option to wipe cache/dalvik and an option to reboot system, hit the reboot system button.
Once your phone has booted up you can use a kernel tuning app to change governors, I/O scheduler, clock speed, and other options. Some of the popular kernel apps are Kernel Auditor, Trickster Mod, No Frills, Kernel Tuner, and many more.
9. How To Update To A New Build Of The Stock ROM
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 6P/Angler) here.
Unzip the angler-xxxxxx-factory-xxxxxxxx (x's replace variables) into a directory on your PC (for this guide we'll use C:\angler\).
Once unzipped you should have a folder named angler-xxxxxx (x's replace variables). Open it and move the following files to a new directory named C:\angler\images\:
bootloader-angler-angler-xx.xx.img
radio-angler-angler-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:\angler\angler-xxxxxx\ you'll see another zip archive named image-angler-xxxxxx, unzip the contents of that zip into the C:\angler\images\ folder we created before. Now within C:\angler\images\ you should have the following files:
android-info.txt
boot.img
bootloader-angler-angler-xx.xx.img
cache.img (not present on Android 7.1.2 and above)
radio-angler-angler-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:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
(above command is unnecessary on Android 7.1.2 and above)
fastboot flash cache C:\angler\images\cache.img
(above command is unnecessary on Android 7.1.2 and above)
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
On 7.1.2 and above you'll also need to boot into TWRP recovery and wipe cache and dalvik cache.
Once all operations are complete you can reboot the device.
You'll have to flash SuperSU again now, plus add any mods that you previously had.
10. How To Flash The Factory Images (And Return To Stock)
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.
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 angler-xxxxxx-factory-xxxxxxxx (x's replace variables) into a directory on your PC (for this guide we'll use C:\angler\).
Once unzipped you should have a folder named angler-xxxxxx (x's replace variables). Open it and move the following files to a new directory named C:\angler\images\:
bootloader-angler-angler-xx.xx.img
radio-angler-angler-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:\angler\angler-xxxxxx\ you'll see another zip archive named image-angler-xxxxxx, unzip the contents of that zip into the C:\angler\images\ folder we created before. Now within C:\angler\images\ you should have the following files:
android-info.txt
boot.img
bootloader-angler-angler-xx.xx.img
cache.img (not present on Android 7.1.2 and above)
radio-angler-angler-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:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
(above command is unnecessary on Android 7.1.2 and above)
fastboot flash cache C:\angler\images\cache.img
(above command is unnecessary on Android 7.1.2 and above)
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
On 7.1.2 and above you'll also need to boot into TWRP recovery and wipe cache and dalvik cache.
If you wish to you can also relock the bootloader with this command:
Code:
fastboot flashing lock
(This command will wipe all user data from the device)
Important: do not lock the bootloader unless you have first flashed the stock images. Locking the bootloader while you have a custom recovery installed can result in a brick. Please also note that the locking procedure will wipe all user data from the device.
Once all operations are complete you can reboot the device.
11. How To Flash The Factory Images (Return To Stock But Leaving Internal Storage Intact)
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, except it will not wipe any of your personal data (photos, music, etc) from the internak storage.
Download the appropriate factory images for your model here.
Unzip the angler-xxxxxx-factory-xxxxxxxx (x's replace variables) into a directory on your PC (for this guide we'll use C:\angler\).
Once unzipped you should have a folder named angler-xxxxxx (x's replace variables). Open it and move the following files to a new directory named C:\angler\images\:
bootloader-angler-angler-xx.xx.img
radio-angler-angler-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:\angler\angler-xxxxxx\ you'll see another zip archive named image-angler-xxxxxx, unzip the contents of that zip into the C:\angler\images\ folder we created before. Now within C:\angler\images\ you should have the following files:
android-info.txt
boot.img
bootloader-angler-angler-xx.xx.img
cache.img (not present on Android 7.1.2 and above)
radio-angler-angler-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:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
(above command is unnecessary on Android 7.1.2 and above)
fastboot flash cache C:\angler\images\cache.img
(above command is unnecessary on Android 7.1.2 and above)
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
On 7.1.2 and above you'll also need to boot into TWRP recovery and wipe cache and dalvik cache.
12. How To ADB Sideload an incremental OTA update package.
Prerequisites: Completely stock setup (the only modification allowed on the phone is the unlocked bootloader).
Download the appropriate OTA zip from my index. OTA updates must be taken in order so you must select the right zip. For example, if you're currently on the MMB29Q build you must select the MMB29Q --> MHC19I zip. The filename will be quite long so to make things easier you can rename it to something easier. For the purposes of this guide let's say we'll rename it to "ota.zip". Place the file in your fastboot folder on your PC.
Boot into the bootloader, use the volume buttons to scroll the options and use the power button to select recovery mode.
Once the phone has booted into the stock recovery (you should see Andy Android with an exclamation mark) hold power and tap volume up to get into the recovery menu. Use the volume buttons to scroll and use the power button (you might need to hold it) to select "apply update from adb".
On your PC navigate to your fastboot folder, hold shift and right-click your mouse, select "open command prompt here". Issue the following command:
Code:
adb sideload ota.zip
Wait for the operation to complete (it'll tell you once it's finished) and once it's all done you can reboot your phone, the first boot might take a while.
13. How To ADB Sideload a full OTA update package.
Prerequisites: Completely stock setup (the only modification allowed on the phone is the unlocked bootloader).
Download the OTA zip that you want to upgrade to from my index. You don't need to be on any specific build prior to flashing a full OTA package. You can only move to a higher build though. The filename will be quite long so to make things easier you can rename it to something easier. For the purposes of this guide let's say we'll rename it to "fullota.zip". Place the file in your fastboot folder on your PC.
Boot into the bootloader, use the volume buttons to scroll the options and use the power button to select recovery mode.
Once the phone has booted into the stock recovery (you should see Andy Android with an exclamation mark) hold power and tap volume up to get into the recovery menu. Use the volume buttons to scroll and use the power button (you might need to hold it) to select "apply update from adb".
On your PC navigate to your fastboot folder, hold shift and right-click your mouse, select "open command prompt here". Issue the following command:
Code:
adb sideload fullota.zip
Wait for the operation to complete (it'll tell you once it's finished) and once it's all done you can reboot your phone, the first boot might take a while.
14. How To Update To Android 7.0 Nougat
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 Nougat factory images for your model (Nexus 6P/Angler) here.
Unzip the angler-xxxxxx-factory-xxxxxxxx (x's replace variables) into a directory on your PC (for this guide we'll use C:\angler\).
Once unzipped you should have a folder named angler-xxxxxx (x's replace variables). Open it and move the following files to a new directory named C:\angler\images\:
bootloader-angler-angler-xx.xx.img
radio-angler-angler-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:\angler\angler-xxxxxx\ you'll see another zip archive named image-angler-xxxxxx, unzip the contents of that zip into the C:\angler\images\ folder we created before. Now within C:\angler\images\ you should have the following files:
android-info.txt
boot.img
bootloader-angler-angler-xx.xx.img
cache.img
radio-angler-angler-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:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\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.
Note: Do not flash the userdata.img
Once all commands/flashes are complete you can reboot the device:
Code:
fastboot reboot
You'll have to flash SuperSU again now, plus add any mods that you previously had.
FAQ can be found in post #3!
Donate To Me
Frequently Asked Questions
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:
[/INDENT]
[INDENT]adb reboot bootloader[/INDENT]
[INDENT]
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:
[/INDENT]
[INDENT]adb reboot recovery[/INDENT]
[INDENT]
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. After unlocking the bootloader I get a message that says "Your device software can't be checked for corruption. Please lock the bootloader". What's going on? Can I get rid of it?
This is nothing to worry about, it's normal to see this when you have an unlocked bootloader. You can't remove it, as long as your bootloader is locked it will stay there.
5. 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.
6. Does taking an OTA update wipe my user data?
No, it doesn't.
7. Do I need to make an EFS backup?
Yes. 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.
8. Do I need to flash the userdata.img from the factory images?
You should never flash the userdata image. It doesn't take into consideration the storage capacity of the device and always allocates 32gb of storage. This is ok for the 32gb model, but for the 64gb and 128gb models you'll end up with much less storage capacity than you should have. If you wish to wipe your internal storage you'd use the following command instead:
Code:
[/INDENT]
[INDENT]fastboot format userdata[/INDENT]
[INDENT]
Reserved
Reserved
Reserved
Reserved
thanks
works great
The_android_Modder said:
works great
Click to expand...
Click to collapse
Lol, how?
Heisenberg said:
Lol, how?
Click to expand...
Click to collapse
Magic
tyvar1 said:
Magic
Click to expand...
Click to collapse
xxtruplayaxx16 said:
lmao
Click to expand...
Click to collapse
He must be from the future...
The_android_Modder said:
works great
Click to expand...
Click to collapse
thank you for the morning lolz
If we wanted, could we just go to step 4, and not do the rest? I.e just root stock and leave it as is?
Is that safe?
If it is, can I flash a rom on later?
Thanks
(I know the device isn't out yet, just getting prepared for it.)
tf2manu994 said:
If we wanted, could we just go to step 4, and not do the rest? I.e just root stock and leave it as is?
Is that safe?
If it is, can I flash a rom on later?
Thanks
(I know the device isn't out yet, just getting prepared for it.)
Click to expand...
Click to collapse
No, because you need a custom recovery in order to flash SuperSU, and you need an unlocked bootloader to flash a custom recovery. Why not just unlock the bootloader?
Heisenberg said:
No, because you need a custom recovery in order to flash SuperSU, and you need an unlocked bootloader to flash a custom recovery. Why not just unlock the bootloader?
Click to expand...
Click to collapse
Ah you misunderstood me, I mean like do all steps upto 4, and then not do the rest?
Sorry for misunderstanding
tf2manu994 said:
Ah you misunderstood me, I mean like do all steps upto 4, and then not do the rest?
Sorry for misunderstanding
Click to expand...
Click to collapse
Ahh ok, now I understand. Yes of course, they're not actually steps that all need to be completed, they're just numbered sections. So if all you want to achieve is to root your stock ROM then you only need to follow steps 1-4.
Hemm sorry but are we talking about a phone that doesn't exist?
Fentadroid said:
Hemm sorry but are we talking about a phone that doesn't exist?
Click to expand...
Click to collapse
It certainly does exist, it just hasn't been released yet. And as it says in the OP these processes remain virtually unchanged from model to model in the Nexus line.
Heisenberg said:
It certainly does exist, it just hasn't been released yet. And as it says in the OP these processes remain virtually unchanged from model to model in the Nexus line.
Click to expand...
Click to collapse
I hope that too!!!
Great Job
Thanks for your Hardwork:good:
There's a ton of information out there, but finding it can sometimes be a challenge, especially for a newbie. And then there's posts to read through, in case a process has changed and it's only talked about in a single place, buried any number of pages back. So this is my attempt to put all Pixel 3 how-to's into a single thread. Everything below is what worked for me, from start to finish, with a fresh phone directly from Google that was bootloader-locked, unrooted, and running stock Android. Comments are welcome and encouraged: if something doesn't work for you, or you have a better/quicker/more reliable way of doing something, or maybe I made a mistake...let me know!
A few things:
Everything in this guide was tested on a "regular" Pixel 3 (blueline). It should all work exactly the same on a Pixel 3 XL (crosshatch), as long as you download the appropriate files (specifically the factory/OTA images and TWRP). I'm posting this in both blueline and crosshatch forums.
This first post will have links to files and the tools you need, as well as general things (like how to enable debugging and boot into recovery). The second post has how-to's for the big stuff (flashing images, TWRP, unlocking, etc).
I'm not responsible for anything you do. Follow these guides at your own risk. Doing so may also void your warranty.
Files and URLs
Official Android files
Factory (wipes device and requires unlocked bootloader): https://developers.google.com/android/images
Full OTA (leaves data intact, can be done via ADB sideload): https://developers.google.com/android/ota
Preview/beta OTA: https://developer.android.com/preview/download-ota.html
TWRP
XDA thread: https://forum.xda-developers.com/pixel-3/development/twrp-3-2-3-0-pixel-3-t3861622
Download: https://dl.twrp.me/blueline/
Magisk
XDA thread: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
GitHub: https://github.com/topjohnwu/Magisk/releases
ADB and Fastboot
Google USB drivers: https://developer.android.com/studio/run/win-usb
SDK platform tools: https://developer.android.com/studio/releases/platform-tools
Download the ZIP and open (no need to extract the whole thing)
Copy the files below to their own directory (you will use this directory for all ADB/Fastboot commands):
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot.exe
General
Enable USB debugging
Download Google USB drivers (see above)
Download SDK platform tools and copy required files to their own directory (see above)
Enable USB debugging (Settings > About > tap Build 7 times > back > Developer options)
Plug phone into computer and when "Allow USB debugging" box comes up, check the box and allow (may need to have adb daemon running on the computer already, see below)
Fastboot mode (using hardware keys) aka bootloader
Power off
Hold VOL- and press/hold PWR until bootloader (fastboot) comes up
Recovery mode (using hardware keys)
Get into Fastboot mode (see above)
Use VOL buttons to find Recovery in the list, use PWR to select (should boot to broken android image)
Hold PWR and press VOL+ once to get into recovery
Useful ADB and Fastboot commands
Enable USB debugging (see above)
ADB (used while phone is "on" and booted up):
Use "adb devices" to ensure the computer is authorized
Use "adb reboot bootloader" to get into Fastboot
Fastboot mode
Use "fastboot devices" to verify computer can see your phone
Update #1: Items below marked through were removed since they don't really apply to Android 10.
Update #2: Edited to reflect changes in root with Android 11.
A quick note: everything below is assuming you're using Windows 10. When it says "Type...", this assumes you've opened a command window in the location of adb/fastboot and that all files referenced are in the same directory and (in some cases) renamed as I reference them (short names without spaces simplifies things). If you're using Powershell, you will probably need to change "adb" and "fastboot" to read ".\adb" and ".\fastboot" so Powershell will use the local files.
Unlocking the bootloader
THIS WILL WIPE YOUR PHONE, SO MAKE SURE EVERYTHING IS BACKED UP!
In Developer Options, enable OEM unlocking and confirm (it may ask you to input fingerprint or PIN/pattern/password)
Boot into Fastboot mode (see above)
Type to unlock:
Code:
fastboot flashing unlock
Use VOL+ key to get the options on the screen to read "Unlock the bootloader" and use PWR button to select
Type to reboot:
Code:
fastboot reboot
Locking the bootloader
THIS WILL WIPE YOUR PHONE, SO MAKE SURE EVERYTHING IS BACKED UP!
Boot into Fastboot mode (see above)
IMPORTANT: restore stock recovery if you replaced it with TWRP (this should prevent the "Can't find valid operating system" issue)
Type to lock:
Code:
fastboot flashing lock
Use VOL buttons to find "Lock the bootloader" and use PWR to select
Type to reboot:
Code:
fastboot reboot
Factory reset via fastboot (can also do this without wiping data)
THIS COULD WIPE YOUR PHONE, SO MAKE SURE EVERYTHING IS BACKED UP!
Download factory image ZIP and unzip all files into their own folder
Unlock bootloader (see above)
Reboot into Fastboot mode
You have 2 options:
Register the location of fastboot.exe with the PATH system variable and run "flash-all.bat"
Wipe data: just run "flash-all.bat" and call it a day
Do not wipe data: open "flash-all.bat" in a text editor (careful not to double-click and run it!), remove the "-w" from the last line to disable the wiping of data, then save, close, and run
Move the 3 files (bootloader IMG, radio IMG, image ZIP) into the ADB folder, rename for simplicity if you want, launch cmd or Powershell, and run the commands below (which come from "flash-all.bat")
Wipe data: type out commands below, but at last line, add "-w" flag: fastboot -w update image.zip
Do not wipe data: type out commands below as written (no "-w" flag)
The commands:
Code:
fastboot flash bootloader bootloader-blueline-XXXX.img
fastboot reboot bootloader
[wait for reboot]
fastboot flash radio radio-blueline-XXXX.img
fastboot reboot bootloader
[wait for reboot]
fastboot update image-blueline-XXXX.zip
Note: The last command (update image) will launch the red "fastbootd" screen, so don't worry and be patient while the command line tells you what's happening. The phone will reboot on its own into the Android system (not fastboot) afterward.
Root Android 10+ using Magisk (Canary channel)
This must be done after every update, and you cannot use the patched file from a different phone!
Unlock bootloader (see above)
Download factory image (not OTA, see link above)
Download and install Magisk Manager Canary (see link above)
In Magisk Manager settings, set Update Channel to "Canary"
Extract boot.img from image-blueline-XXXX.zip found in the factory image you downloaded
Place boot.img on your phone's internal storage
Open Magisk Manager and do:
tap "Install" button (next to "Magisk" in first block on the main screen)
"Select and Patch a File" option
Find boot.img file you just placed on your phone
tap "Let's Go"
When finished, move the newly-created magisk_patched.img file over to your computer's ADB directory
Reboot into bootloader
Type:
Code:
fastboot flash boot magisk_patched.img
fastboot reboot
Open up Magisk Manager and make sure everything's good!
Note : if you get stuck in fastboot mode or in a boot loop, flash the stock boot.img to both slots and try again
Code:
fastboot flash boot boot.img --slot all
Optional:
for adblocking, tap "Systemless hosts" in Magisk Manager, then install AdAway using F-Droid
install a performance kernel like Kirisakura for Bluecross (R)
Updating Android 10+ while rooted
You can't take an OTA while rooted, so updating Android 10+ (as in monthly updates) can be one of two ways.
Method #1 (faster, but more chance for issues)
Download OTA ZIP and move it to ADB folder (don't unzip it)
This does not require an unlocked bootloader, but does require USB debugging (see above)
Get boot.img from the factory image (see first post on where to download this) and place your ADB directory
Reboot into bootloader / fastboot and type to restore stock boot to both slots:
Code:
fastboot flash boot --slot all boot.img
fastboot reboot bootloader
[wait for reboot]
Use VOL buttons to select "Apply update from ADB"
Type (where filename is the name of the file you want to sideload):
Code:
adb sideload filename.zip
Wait for it to finish, will take you back to Recovery when it's done
Reboot using menu
Method #2 (takes longer, but best bet for minimal issues)
Follow "Factory reset via fastboot" instructions (see above, make sure you don't wipe your data!)
Take the OTA in the official way (through Android)
Follow "Root Android 10+ using Magisk Canary" instructions (see above)
Boot into TWRP (3.3.0-0 or higher)
Download TWRP IMG and place in ADB folder (rename the file to twrp.img)
If not already done, unlock the bootloader (see above)
Reboot into bootloader
Type to boot TWRP (it will restart and should boot into TWRP):
Code:
fastboot boot twrp.img
OPTIONAL: Replace recovery by installing TWRP
Your phone should automatically mount, so move twrp.img from PC to Download folder on phone's internal storage
Advanced > Install Recovery Ramdisk > choose TWRP IMG > Swipe to install
Back > Fix Recovery Bootloop > Reboot System > Do Not Install when asked if TWRP should install app
Root using Magisk (18.1 or higher)
Download Magisk ZIP and move to device
Boot into TWRP (see above)
Enter your PIN/pattern/password to decrypt (unnecessary if you are not using security on your phone)
Swipe to Allow Modifications (to system)
Install > find and select the Magisk ZIP > Slide to install
Wipe cache > Reboot system > Do Not Install when asked if TWRP should install app
Open Magisk Manager to verify latest and to install modules
"Can't find valid operating system" booting issue
Unlock your bootloader again (see above)
Follow steps for "Factory reset via fastboot" (see above) and keep the wipe flag
After it reboots, power off (press PWR and select "Power off" from menu)
Follow steps for "Locking the bootloader" (see above)
After it reboots into Fastboot mode, have it start using the PWR button
Android Recovery / "Cannot load Android system" booting issue
This can happen for a number of reasons, but the fix is the same: "Factory reset via fastboot" (see above). You probably do not need to wipe user data, so you can omit the "-w" flag.
If you still get the error message, select the "Try again" option. If it still doesn't work, try "Factory reset via fastboot" again, as well as "Try again". If it doesn't work this time, you probably have no choice but to do a factory reset (in which you will definitely lose your data).
If it happens after flashing Magisk in TWRP, though, you've got a slightly different issue and the problem will persist no matter how many times you flash the factory images and re-install Magisk. This is probably due to something leftover in the previous Magisk installation that conflicts with the new installation. There are two ways to handle this.
First and easiest: uninstall Magisk Manager app before rebooting into the bootloader and running fastboot commands. Then proceed as usual (sideload OTA or flash factory images via fastboot, boot TWRP, and flash Magisk). All guides for this are above. This method preserves any modules you have installed.
Second and more complete (if the above method still gives you trouble):
download to your phone the Magisk ZIP, Magisk Uninstaller ZIP, and Magisk APK from this XDA thread
uninstall the Magisk Manager app
reboot to bootloader
using fastboot, boot into TWRP using IMG (you don't need to replace boot with TWRP)
flash Magisk Uninstaller ZIP
wipe Dalvik
flash Magisk ZIP
wipe Dalvik
reboot system (do not install TWRP)
install Magisk Manager APK and re-install any modules
Number 3 in "Applying OTA via ADB sideload" should be flash stock boot.img I think.
wangdaning said:
Number 3 in "Applying OTA via ADB sideload" should be flash stock boot.img I think.
Click to expand...
Click to collapse
I wrote it like that because the file isn't actually called "boot.img", but rather "bootloader-blueline-blahblahblah.img" where "blahblahblah" is the release. Since it changes, I figured just calling it the "bootloader IMG" would make more sense.
rczrider said:
I wrote it like that because the file isn't actually called "boot.img", but rather "bootloader-blueline-blahblahblah.img" where "blahblahblah" is the release. Since it changes, I figured just calling it the "bootloader IMG" would make more sense.
Click to expand...
Click to collapse
Was my misunderstanding. I thought you were implying people should go back to stock recovery to flash ota. You are talking about flashing ota in twrp. You might clear that up a little bit in that section.
Great post.
Unfortunately, if you are writing a process, then writing everything out is a requirement. Especially with item numbers or using an outline format. Not everyone understands shortcuts taken or abbreviated words, unless they are spelled out in the beginning. IMO, wrote and read too many processes. Including software requirement documentation.
Hi,
thanks for the thread :good:
wangdaning said:
Number 3 in "Applying OTA via ADB sideload" should be flash stock boot.img I think.
Click to expand...
Click to collapse
Yes, I think so too.
rczrider said:
I wrote it like that because the file isn't actually called "boot.img", but rather "bootloader-blueline-blahblahblah.img" where "blahblahblah" is the release. Since it changes, I figured just calling it the "bootloader IMG" would make more sense.
Click to expand...
Click to collapse
The boot.img is into "image.zip"
Then I suggest to flash into a and b (or both)
Code:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
or
fastboot flash boot --slot all boot.img
Edit
be careful here: Factory reset via ADB sideload (can also do this without wiping data)
bootloader is bootloader, boot is boot, bootloader.img isn't boot.img
so, maybe better to write:
fastboot flash bootloader nameofbootloader.img or if simply renamed fastboot flash bootloader bootloader.img
deleted, bug.
trouble flashing files
When I try to flash twrp.img or boot.img this is what I get back " FAILED (Write to device failed in Send Buffer() (Too many links)) fastboot: error: Command failed.
Any thoughts?
fyrmd said:
When I try to flash twrp.img or boot.img this is what I get back " FAILED (Write to device failed in Send Buffer() (Too many links)) fastboot: error: Command failed.
Any thoughts?
Click to expand...
Click to collapse
Please read the instructions carefully. You cannot flash twrp directly. "fastboot boot twrp.img" then when twrp boots you can use it or make it permanent by flashing the install zip or the internal twrp option. I go with the install zip as it seems more stable to me (placebo I suppose).
wangdaning said:
Please read the instructions carefully. You cannot flash twrp directly. "fastboot boot twrp.img" then when twrp boots you can use it or make it permanent by flashing the install zip or the internal twrp option. I go with the install zip as it seems more stable to me (placebo I suppose).
Click to expand...
Click to collapse
Thanks, but still no luck.
fyrmd said:
When I try to flash twrp.img or boot.img this is what I get back " FAILED (Write to device failed in Send Buffer() (Too many links)) fastboot: error: Command failed.
Any thoughts?
Click to expand...
Click to collapse
Turns out it was the cable, it is an expensive one from Amazon so not sure what I should be purchasing for next time.
fyrmd said:
Turns out it was the cable, it is an expensive one from Amazon so not sure what I should be purchasing for next time.
Click to expand...
Click to collapse
I always buy Anker cables and chargers. All have been good so far.
Now,my pixel 3 can not work,the bootload is locked.when I select recovery by fastboot,The phone noticed me can not find vaild operating system,the device will not start.
xiaowei666 said:
Now,my pixel 3 can not work,the bootload is locked.when I select recovery by fastboot,The phone noticed me can not find vaild operating system,the device will not start.
Click to expand...
Click to collapse
Are you able to get into recovery? If so, download the full ota to your pc and side load it with adb.
xiaowei666 said:
Now,my pixel 3 can not work,the bootload is locked.when I select recovery by fastboot,The phone noticed me can not find vaild operating system,the device will not start.
Click to expand...
Click to collapse
i same issue
rczrider said:
[*]Copy the files below to their own directory (you will use this directory for all ADB/Fastboot commands):
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot.exe
Click to expand...
Click to collapse
why not copy all files?
---------- Post added at 11:58 AM ---------- Previous post was at 11:55 AM ----------
fyrmd said:
Thanks, but still no luck.
Click to expand...
Click to collapse
boot to the twrp.img and flash the twrp.zip, unless you are on android 10 you should have no problem unless you are doing it wrong. not exactly hard to do.
How to enable oem unlock in this case?
pedro5148 said:
How to enable oem unlock in this case?
Click to expand...
Click to collapse
There are a few suggestions at https://www.theandroidsoul.com/how-to-fix-oem-unlock-greyed-out-or-oem-unlock-disabled-problem/
However, if the network carrier has locked the bootloader, you cannot unlock it. In the U.S., Verizon and AT&T phones generally cannot be unlocked due to locked bootloaders.
Devices that started to be received today have Oxygen OS 10.5 out of the box.
No flashable zip for that software release is publicly available, meaning its stock boot.img cannot be extracted.
You then need to update to a newer build first. You can do so from my OxygenOS builds repo thread.
Once done, enable developers options and enable OEM unlock.
Reboot to fastboot (enable USB debugging in dev options and use adb reboot bootloader)
Type fastboot oem unlock and accept to unlock bootloader (warning: as a safety measure Android will wipe your userdata)
Go through OxygenOS setup
Install Magisk Manager from https://github.com/topjohnwu/Magisk/releases/download/manager-v7.5.1/MagiskManager-v7.5.1.apk
Move stock boot.img to your phone internal storage (please open spoiler)
For your convenience, 10.5.2 stock boot.img for EU and India have been extracted
EU download: https://drive.google.com/file/d/18aPqErEMbRqmN4BpdvHE4OKgizDcEbou/view?usp=sharing
India download: https://drive.google.com/file/d/1ZIEYWH2PYkKyojq_S_i_onBstejHKDTJ/view?usp=sharing
For future builds, you can use payload dumper (Windows) , (Linux ) to extract stock boot.img
Click on Install
Choose "Select and patch a file"
Select your stock boot.img
Wait until Magisk patches your boot.img, and once patched it can be found in the Downloads folder
Copy that patched boot.img (which should be named magisk_patched.img) to your computer
Boot into fastboot again
Type fastboot getvar current-slot into your terminal window and press Enter.
If the output is a , type fastboot flash boot_a magisk_patched.img into your terminal window and press Enter.
If the output is b , type fastboot flash boot_b magisk_patched.img into your terminal window and press Enter.
Reboot to OxygenOS
Open Magisk Manager and your device should now be rooted.
TIPS:
- Ensure you got latest platform tools installed from https://developer.android.com/studio/releases/platform-tools
- Backup your /persist once rooted (dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img) and save it somewhere on your cloud/computer, this might save you from a broken fingerprint sensor and an RMA in the future if it turns out this device has same issue as 8-series when it comes to crossflash regional builds of OOS.
Credits:
@topjohnwu for making Magisk
/u/Jisifus for testing on his device and for screenshots
Some_Random_Username said:
TIPS:
- Ensure you got latest platform tools installed from https://developer.android.com/studio/releases/platform-tools
- Backup your /persist once rooted (dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img) and save it somewhere on your cloud/computer, this might save you from a broken fingerprint sensor and an RMA in the future if it turns out this device has same issue as 8-series when it comes to crossflash regional builds of OOS.
Click to expand...
Click to collapse
Great to see it works this way and thanks for the tip.:good:
do u lose all data while rooting?
#edit1
nevermind, cannot read right
OK, will give this a try asap,have the device here now...
I gave it a try, works like a charm! Thanks for this! Small tip, unlock bootload before u copy your files
now my phone is a bit laggy. with magisk on it.. i will test it later if its getting better
Some_Random_Username said:
Type fastboot getvar current-slot into your terminal window and press Enter.
If the output is a , type fastboot flash boot_a magisk_patched.img into your terminal window and press Enter.
If the output is b , type fastboot flash boot_b magisk_patched.img into your terminal window and press Enter.
Click to expand...
Click to collapse
You can simply type "fastboot flash boot magisk_patched.img" - it flash boot to current active slot. Just for note.
Can confirm that it works, just tried it myself
If WiFi/data does not work (usually happens when you flash wrong version, but can also happen if you flash correct one), fastboot boot the image, then do a direct install in Magisk Manager.
Also, big thumbs up for adding tips for persist backup, I see too many people needing to send their device back because they messed it up somehow.
Failed for me
Hi and thanks for the tips.
Running 10.5.2 (latest build) and Bootloader is unlocked.
1: Downloaded EU BootImage File suggested (10.5.2.AC01BA.boot.img - 101MB)
2: Went to Magisk Manager, Advanced Settings, Recovery Mode Ticked, Install Magisk, Install, Select and Patch a File - Browse to 10.5.2.AC01BA.boot.img in Downloads and select.
3: Command Window appears detailing successful patching of ramdisk and also location of the newly created magisk_patched.img (37.52MB???????????????)
4: Size of new boot image looks suspiciously small.
5: Copied magisk_patched.img to PC and rebooted phone into fastboot.
6: Issued the fastboot getvar current-slot command - mine is reported as b
7: Issued the fastboot flash boot_b magisk_patched.img - File flashed OK - Reboot (Start) Phone.
8: 30 seconds of unlocked bootloader warning screen followed by 10 secs black screen followed by Qualcom Crash Dump. Rebooted phone three times - same result.
9: Rebooted phone into fastboot mode, reflashed the stock boot image and all now OK (but obviously not rooted).
Would be grateful if anyone could advise - the magisk_patched.img looks suspiciously small to me at 37.52MB compared to 101MB for the original boot image.
Thanks
10: Double checked the patching process again in Magisk and again, patched bootimage filesize is on 37.52MB.
11: I have saved log from patching process and on reading, all looks OK.
jmwengineering said:
Hi and thanks for the tips.
Running 10.5.2 (latest build) and Bootloader is unlocked.
1: Downloaded EU BootImage File suggested (10.5.2.AC01BA.boot.img - 101MB)
2: Went to Magisk Manager, Advanced Settings, Recovery Mode Ticked, Install Magisk, Install, Select and Patch a File - Browse to 10.5.2.AC01BA.boot.img in Downloads and select.
3: Command Window appears detailing successful patching of ramdisk and also location of the newly created magisk_patched.img (37.52MB???????????????)
4: Size of new boot image looks suspiciously small.
5: Copied magisk_patched.img to PC and rebooted phone into fastboot.
6: Issued the fastboot getvar current-slot command - mine is reported as b
7: Issued the fastboot flash boot_b magisk_patched.img - File flashed OK - Reboot (Start) Phone.
8: 30 seconds of unlocked bootloader warning screen followed by 10 secs black screen followed by Qualcom Crash Dump. Rebooted phone three times - same result.
9: Rebooted phone into fastboot mode, reflashed the stock boot image and all now OK (but obviously not rooted).
Would be grateful if anyone could advise - the magisk_patched.img looks suspiciously small to me at 37.52MB compared to 101MB for the original boot image.
Thanks
10: Double checked the patching process again in Magisk and again, patched bootimage filesize is on 37.52MB.
11: I have saved log from patching process and on reading, all looks OK.
Click to expand...
Click to collapse
The size is normal.
When patching your image you have to select "Preserve Force Encryption" and "Preserve AVB 2.0/dm-verity" under advanced settings in the main screen where you patch the image.
jmwengineering said:
Hi and thanks for the tips.
Running 10.5.2 (latest build) and Bootloader is unlocked.
1: Downloaded EU BootImage File suggested (10.5.2.AC01BA.boot.img - 101MB)
2: Went to Magisk Manager, Advanced Settings, Recovery Mode Ticked, Install Magisk, Install, Select and Patch a File - Browse to 10.5.2.AC01BA.boot.img in Downloads and select.
3: Command Window appears detailing successful patching of ramdisk and also location of the newly created magisk_patched.img (37.52MB???????????????)
4: Size of new boot image looks suspiciously small.
5: Copied magisk_patched.img to PC and rebooted phone into fastboot.
6: Issued the fastboot getvar current-slot command - mine is reported as b
7: Issued the fastboot flash boot_b magisk_patched.img - File flashed OK - Reboot (Start) Phone.
8: 30 seconds of unlocked bootloader warning screen followed by 10 secs black screen followed by Qualcom Crash Dump. Rebooted phone three times - same result.
9: Rebooted phone into fastboot mode, reflashed the stock boot image and all now OK (but obviously not rooted).
Would be grateful if anyone could advise - the magisk_patched.img looks suspiciously small to me at 37.52MB compared to 101MB for the original boot image.
Thanks
10: Double checked the patching process again in Magisk and again, patched bootimage filesize is on 37.52MB.
11: I have saved log from patching process and on reading, all looks OK.
Click to expand...
Click to collapse
And that's why it's recommended to boot the patched image first.
Thanks
Lossyx said:
The size is normal.
When patching your image you have to select "Preserve Force Encryption" and "Preserve AVB 2.0/dm-verity" under advanced settings in the main screen where you patch the image.
Click to expand...
Click to collapse
Thanks for confirming file size - Preserve Force Encryption and Preserve AVB 2.0/dm-verity were ticked during the patching process. Guess I'll have to wait until TWRP is verified as Nord compatible.
---------- Post added at 07:06 PM ---------- Previous post was at 06:59 PM ----------
Kollachi said:
And that's why it's recommended to boot the patched image first.
Click to expand...
Click to collapse
Thanks for the reply. Not sure what you mean by booting the patched image first. You have to create the patched image on the phone first before you can flash and then boot it. Step 7 in my post above details the flashing of the patched image and subsequent attempt to reboot Oxygen OS. I can't boot the patched image until I've created and flashed it!
jmwengineering said:
Thanks for the reply. Not sure what you mean by booting the patched image first. You have to create the patched image on the phone first before you can flash and then boot it. Step 7 in my post above details the flashing of the patched image and subsequent attempt to reboot Oxygen OS. I can't boot the patched image until I've created and flashed it!
Click to expand...
Click to collapse
Nah, instead of flash the patched boot image you can boot it only. Not sure why it's not working for you. But usually it should work.
Command: fastboot boot "patched boot image"
Edit: that's also what lossyx said. Boot image and than install it with magisk manager.
And if you boot the image and something went wrong you aren't bricked or anything. It's a safe way to test something.
Thanks for the advice - will boot the image file on my PC rather than flashing first.
Sent from my AC2003 using Tapatalk
Does unlocking the bootloader break widewine L1 on this device like it did with 7/7T/7P/7TP/8/8P
..
CryllicBuster273 said:
Does unlocking the bootloader break widewine L1 on this device like it did with 7/7T/7P/7TP/8/8P
Click to expand...
Click to collapse
Yeah I guess when you unlock your phone it will break L1 as always.
---------- Post added at 12:17 PM ---------- Previous post was at 12:15 PM ----------
DIR49DNOR0N said:
I will try this unless twrp is cooked on release. Where did you get the OTA zips from actually?
I want to, extract boot.img, save it, patch boot.img, boot it, use some apps that require root and remove some packages, uninstall magisk, power down, use normal image, relock bootloader. Does this work how i expect it to work ?
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-nord/how-to/oneplus-nord-repo-oxygen-os-builds-t4138085
DIR49DNOR0N said:
I will try this unless twrp is cooked on release. Where did you get the OTA zips from actually?
I want to, extract boot.img, save it, patch boot.img, boot it, use some apps that require root and remove some packages, uninstall magisk, power down, use normal image, relock bootloader. Does this work how i expect it to work ?
Click to expand...
Click to collapse
No, keep the bootloader unlocked if your phone is modified, else it can cause some issues.
Btw when you lock/unlock the bootloader, data will be wiped. apps will be reinstated again so that's useless
The guide worked perfectly and I'm up and running with Root!
One thing I have noticed is that the Google Play store is no longer Play Protect Certified.
I've tried registering my device with Google using this XDA guide but I haven't found any change to the Play Store certification.
I should probably wait for a while to see if the registration takes some time. I also couldn't use the adb commands that Google recommends and I had to use the Device ID app to get the Google Service Framework (GSF).
I've read in a few places that it may be because the Bootloader is unlocked and I'm wondering if I should re-lock it now that I have root. Not sure how/if that will affect my ability to keep root when future updates come out though.
Anyone have any thoughts/experience with this?
Possible TWRP without waiting?
Can anyone use this and try? Might be used as an alternate Method for Rooting via TWRP
https://forum.xda-developers.com/an...g/guide-how-to-port-twrp-to-qualcomm-t3420013
[GUIDE][WINDOWS] Bootloader Unlock/Re-Lock, Rooting with Magisk and flashing FirmwaresIntroducing this GuideHello there and welcome to My Guide for Your Xperia Smartphone. This Guide will walk with You thru the whole Process of installing Drivers, getting an unlock Key for Your Bootloader, rooting with Magisk and even flashing GSI Custom ROMs up to re-locking Your Bootloader and re-flashing Stock for the total Factory Reset. This Thread/Guide is not meant as Wiki n'or will it teach You about Android at all. Inform Yourself using Google to enjoy the total Freedom and Customization of Android... If You can't solve Problems Yourself, by communicating and research, don't touch Your Bootloader!
IMPORTANT:
2020+ Xperias are using fastbootd, and equivalent to fastboot which runs in Userspace (Same as Recoveries).
You can access Your Recovery on Your Xperia by holding VolumeDown (-) & the Powerbutton (Your Device needs to be turned off before ofc). Release the Powerbutton after the Display turned on and hold VolumeDown (-) until You see the Recovery Screen. From there, You can enter fastbootd and fastboot. Labled as "Fastboot" for fastbootd and "Bootloader" which is the old fastboot. You can flash Kernels, Recoveries and other stuff from fastboot. Everything else like System Images (GSIs for example), Product Images, System_ext Images and any Userspace stuff has to be flashed from fastbootd. 2019 Xperias are still using fastboot only...
Fastboot and Fastbootd has nothing to do with SONYs Flashmode on Xperias!
INDEX:
Requirements
Installing Drivers
Firmware Flashing
Bootloader Unlocking & Magisk Root
GSI ROM flashing with Fastboot (Optional)
Bootloader Re-Locking (TheWayBack)
Firmware Restoring after Re-Locking
1. Requirements:
Read! Inform Yourself about the Tools You use...
Xperia Basics:
Your Device is turned Off...
Blue LED=Fastboot (Hold VolumeUp (+) & Connect to USB)
Green LED=Flashmode (Hold VoumeDown (-) & Connect to USB)
Windows 10/11 for Firmware flashing & downloading
Xperia Bootloader Unlock Key (From HERE)
Platform Tools alias ADB and Fastboot (From HERE)
Fastboot and Flashmode Drivers (From HERE and HERE)
EMMA for Firmware Updates (From HERE)
XperiFirm for Firmware Downloads (From XDA)
Unsin to extract the Kernel .sin from XperiFirm (From XDA)
Magisk Manager to patch the extracted Kernel .sin (From GitHub)
A working Android System for the Magisk Kernel patching
GSI & vbmeta Image (From Google) (Optional)
A Backup of Your Internal Devices Storage (Optional)
2. Installing Drivers:
Download the Drivers from the Links above and extract them
Install the downloaded and extracted Drivers by right clicking on the ***.inf Files "Install"
3. Flashing Firmwares with EMMA:
Download EMMA and install it
Start EMMA and connect Your Device to USB (Flashmode)
3.1. Downloading Firmwares with XperiFirm:
Download and extract XperiFirm from the link above
Run XperiFirm and Download the right Firmware for Your Device
4. Bootloader Unlocking and Magisk Root:
Note: Since You are going to unlock Your Bootloader, You may surely want to get Root. So let's start with Magisk or it will take more Time afterwards...
Download UnSin from the link above and extract it somewhere
Download the "Platform Tools" from Google and extract it to the root of Your main Windows Drive
Download and install the Magisk Manager on Your Android Device
Extract the File boot_********.sin (60MB+ File) with the Unsin Exe (Drag and drop the Image on the Exe)
You will get a .img File which You can patch now with the Magisk Manager on Your Android Device
Open the Magisk Manager and Install Magisk by selecting the Image File You just got from UnSin
Copy the magisk_patched.img in /download from Your Device to the Platform Tools Folder
Grab Your Device again, go to "About Phone" in the Settings and tap several Times on the build Version
Go now to the Developer Settings under "System" and enable "OEM-Unlock" and "USB-Debugging"
Use now the Platform Tools with this Commands (In Powershell):
Type now (Step by Step):
Code:
cd\
cd platform-tools
Note: To use the Platform Tools Folder as environment for Fastboot and ADB. Or hold Shift and Make a right Click in the Platform Tools Folder to open the Command prompt there...
Type now:
Code:
adb reboot bootloader
You will get a prompt on Your Xperia Device. Your Device will Reboot afterwards...
Now Your Bootloader Unlock Code:
Code:
fastboot oem unlock 0xYOURKEY
Wait for it... And type now:
Code:
fastboot reboot
Wait for Your Device to Wipe and Start. Once in the Android System, turn Your Device off without USB Connected
Press and hold now the VolumeUp (+) Button while connecting to USB to enable the fastboot Mode
Continue with flashing the Images for Root (Step by Step):
Code:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
Wipe and Reboot:
Code:
fastboot -w
fastboot reboot
Note: Your are unlocked and rooted now! Enjoy Your Unleashed Device
{
"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"
}
5. GSI flashing with Fastboot:
Note: GSI ROMs can be found around the Web. Like here...
Treble-Enabled Device Development A/AB ROMS
Treble-Enabled Device Development A/AB ROMS
forum.xda-developers.com
Not all GSIs require the vbmeta change. You can use all GSIs that are made for ARM64 + A/B Devices. Play around. Systems can't damage Your Device since You keep the Stock Vendor & Kernel! You can use any Android Version! Don't forget to make backups if needed. You are going to Format Your Device!
Download a GSI Zip from Google
Extract the system.img and the vbmeta.img to Your Platform-Tools
Connect Your Device in Fastboot Mode and use Fastboot with:
(On 2020+ Xperias run: "fastboot reboot fastboot" first after You booted into fastboot)
Code:
fastboot flash system_a system.img
fastboot flash system_b system.img
[Optional] fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta.img
[Optional] fastboot --disable-verity --disable-verification flash vbmeta_b vbmeta.img
fastboot -w (This does Format Your Device and is needed everytime You change the GSI!)
fastboot reboot
6. Bootloader Re-Lock:
Flash the latest Firmware for Your Device with EMMA
Erase all Userdata before You continue (like with fastboot -w or via Recovery)
Just go into Fastboot mode and type in the command prompt (like before in this Guide):
Code:
fastboot oem lock
Wait for Your Device and disconnect it from USB
Done... Continue with Step 7.
7. Firmware Restoring after Re-Locking:
Download and Install the "Xperia Companion" from SONY
Open the Xperia Companion and select Software Repair
Select that Your Device can't get recognized (or is a Smartwatch 3 lol)
Go to the next Page and select the Xperia Smartphone Option
Continue and wait for the Initialization
Press and hold Volume DOWN while connecting to USB (You will see the Green Flashmode LED again)
Continue once Your Device gets recognized and let the Xperia Companion do his work...
Done. Your Bootloader is locked again and almost all of Your DRMs are restored.
So I haven't rooted a phone in a long time. I have gotten my Xperia 5 IV, and I really want to get back into it. Your post looks like a great place to start. However, I have a question, do you think a custom recovery is needed? If so, would you recommend any? I don't see anything about installing TWRP on the 5 IV, and my quick search online hasn't yielded better results.
Anyone know what models can be unlocked? Previous thread says you can't unlock CQ62 (US). CQ44 (Japan) apparently can be unlocked going by same thread, but what about CQ54 (Europe) and CQ72 (Asia)?
Thanks, that's a very helpful guide! I'm now running the latest available Android 13 image for my phone, happily rooted
As it's in the Sony Xperia 5 IV section of the forum it's important to note that you must use fastbootd or you won't be able to wipe the phone. As such, to summarise, the rooting steps are:
- Unlock bootloader
- Download and extract boot.img (on PC)
- Download Magisk and patch boot.img (on phone)
- Reboot to bootloader (adb reboot fastboot) then to fastboot (fastboot reboot fastboot)
- Flash patched boot.img, wipe phone, and reboot
Once rooted you probably want to:
- Install Displax's safetynet-fix to get Google Wallet, Netflix etc working
- Remove unwated bloatware using something like De-Bloater
asdf2345 said:
what about CQ54 (Europe)
Click to expand...
Click to collapse
You can definitely unlock CQ54, as I have just done it.
SekiGamer said:
do you think a custom recovery is needed?
Click to expand...
Click to collapse
I never use custom recoveries, personally, as they're another potential point of failure without any real benefit (you can backup and perform updates easily by other means).
aricooperdavis said:
You can definitely unlock CQ54, as I have just done it.
I never use custom recoveries, personally, as they're another potential point of failure without any real benefit (you can backup and perform updates easily by other means).
Click to expand...
Click to collapse
Ah, that's very good to know. What are the other means that you prefer?
Just got my Japanese SO-54C and went to follow this guide only to find out "Bootloader Unlock Allowed: No".
However, I just got that changed to "Bootloader Unlock Allowed: Yes" so I will follow this guide tonight and unlock my SO-54C bootloader! Can't wait.
Bootloader is now unlocked. However, no matter what I try, the device is never actually rooted.
I'm using the Docomo firmware (xperifirm) 64.1.C.0.102 and I use UnSin on boot_X-FLASH-ALL-C220.sin to get .img. Then I instal MAGISK and push the img file to the phone. Then I use magisk to patch the img and retrieve it from the /Download folder on the device.
I use adb pull to my desktop and I do the fastboot flash boot_a and boot_b, wipe and reboot. After going through the new phone setup, I use Root Checker and it says my phone is NOT rooted.
Am I missing something?
Edit: couple reboots later and magisk did something (some kind of update) and it says rooted.
Kevbodian said:
Just got my Japanese SO-54C and went to follow this guide only to find out "Bootloader Unlock Allowed: No".
However, I just got that changed to "Bootloader Unlock Allowed: Yes" so I will follow this guide tonight and unlock my SO-54C bootloader! Can't wait.
Click to expand...
Click to collapse
How did you get it changed? The removed guide only worked up to the III series.
asdf2345 said:
How did you get it changed? The removed guide only worked up to the III series.
Click to expand...
Click to collapse
I paid for credits on Infinity Online Service - qUnlockTool. The software didn't work, I notified Infinity Team and they gave me a new exe that changed from NO to YES. Then I followed the guide to BLU and root.
Hmm interesting, wonder if it can be used on American devices for the American 4G/5G bands.
How much was it?
asdf2345 said:
Hmm interesting, wonder if it can be used on American devices for the American 4G/5G bands.
How much was it?
Click to expand...
Click to collapse
$30 USD. But DM me if you want more info as I believe paid stuff is not welcome.
As far as bands, I have no idea. I quickly soft-bricked my device tonight and just got it back (bootloader unlocked but root is gone).
Well I mean unlock American devices for those 4G/5G bands not in the overseas phones. Otherwise a method to unlock the bands of the 256GB overseas model would be better.
I find it funny that $30 for a $1000 (or $700) phone bad, but for the Motorola Droid Razr M where the unlock costs more than the phone itself it's completely fine to talk about.
Kevbodian said:
Edit: couple reboots later and magisk did something (some kind of update) and it says rooted.
Click to expand...
Click to collapse
This is one of the devices that Magsik has to install some early hooks for, so indeed to finish root you'll need to open Magisk and it'll tell you that 'additional setup required' and to reboot your device. Then it'll be rooted.
SekiGamer said:
Ah, that's very good to know. What are the other means that you prefer?
Click to expand...
Click to collapse
I use titanium backup and update directly through Magisk or using fastboot.
i never got into titanium to backup my system like i used to with TWRP.....i loved TWRP
Why doesn't anyone try reverse engineering these paid bootloader unlock methods?
gram-hours said:
[GUIDE][WINDOWS] Bootloader Unlock/Re-Lock, Rooting with Magisk and flashing FirmwaresIntroducing this GuideHello there and welcome to My Guide for Your Xperia Smartphone. This Guide will walk with You thru the whole Process of installing Drivers, getting an unlock Key for Your Bootloader, rooting with Magisk and even flashing GSI Custom ROMs up to re-locking Your Bootloader and re-flashing Stock for the total Factory Reset. This Thread/Guide is not meant as Wiki n'or will it teach You about Android at all. Inform Yourself using Google to enjoy the total Freedom and Customization of Android... If You can't solve Problems Yourself, by communicating and research, don't touch Your Bootloader!
IMPORTANT:
2020+ Xperias are using fastbootd, and equivalent to fastboot which runs in Userspace (Same as Recoveries).
You can access Your Recovery on Your Xperia by holding VolumeDown (-) & the Powerbutton (Your Device needs to be turned off before ofc). Release the Powerbutton after the Display turned on and hold VolumeDown (-) until You see the Recovery Screen. From there, You can enter fastbootd and fastboot. Labled as "Fastboot" for fastbootd and "Bootloader" which is the old fastboot. You can flash Kernels, Recoveries and other stuff from fastboot. Everything else like System Images (GSIs for example), Product Images, System_ext Images and any Userspace stuff has to be flashed from fastbootd. 2019 Xperias are still using fastboot only...
Fastboot and Fastbootd has nothing to do with SONYs Flashmode on Xperias!
INDEX:
Requirements
Installing Drivers
Firmware Flashing
Bootloader Unlocking & Magisk Root
GSI ROM flashing with Fastboot (Optional)
Bootloader Re-Locking (TheWayBack)
Firmware Restoring after Re-Locking
1. Requirements:
Read! Inform Yourself about the Tools You use...
Xperia Basics:
Your Device is turned Off...
Blue LED=Fastboot (Hold VolumeUp (+) & Connect to USB)
Green LED=Flashmode (Hold VoumeDown (-) & Connect to USB)
Windows 10/11 for Firmware flashing & downloading
Xperia Bootloader Unlock Key (From HERE)
Platform Tools alias ADB and Fastboot (From HERE)
Fastboot and Flashmode Drivers (From HERE and HERE)
EMMA for Firmware Updates (From HERE)
XperiFirm for Firmware Downloads (From XDA)
Unsin to extract the Kernel .sin from XperiFirm (From XDA)
Magisk Manager to patch the extracted Kernel .sin (From GitHub)
A working Android System for the Magisk Kernel patching
GSI & vbmeta Image (From Google) (Optional)
A Backup of Your Internal Devices Storage (Optional)
2. Installing Drivers:
Download the Drivers from the Links above and extract them
Install the downloaded and extracted Drivers by right clicking on the ***.inf Files "Install"
3. Flashing Firmwares with EMMA:
Download EMMA and install it
Start EMMA and connect Your Device to USB (Flashmode)
3.1. Downloading Firmwares with XperiFirm:
Download and extract XperiFirm from the link above
Run XperiFirm and Download the right Firmware for Your Device
4. Bootloader Unlocking and Magisk Root:
Note: Since You are going to unlock Your Bootloader, You may surely want to get Root. So let's start with Magisk or it will take more Time afterwards...
Download UnSin from the link above and extract it somewhere
Download the "Platform Tools" from Google and extract it to the root of Your main Windows Drive
Download and install the Magisk Manager on Your Android Device
Extract the File boot_********.sin (60MB+ File) with the Unsin Exe (Drag and drop the Image on the Exe)
You will get a .img File which You can patch now with the Magisk Manager on Your Android Device
Open the Magisk Manager and Install Magisk by selecting the Image File You just got from UnSin
Copy the magisk_patched.img in /download from Your Device to the Platform Tools Folder
Grab Your Device again, go to "About Phone" in the Settings and tap several Times on the build Version
Go now to the Developer Settings under "System" and enable "OEM-Unlock" and "USB-Debugging"
Use now the Platform Tools with this Commands (In Powershell):
Type now (Step by Step):
Code:
cd\
cd platform-tools
Note: To use the Platform Tools Folder as environment for Fastboot and ADB. Or hold Shift and Make a right Click in the Platform Tools Folder to open the Command prompt there...
Type now:
Code:
adb reboot bootloader
You will get a prompt on Your Xperia Device. Your Device will Reboot afterwards...
Now Your Bootloader Unlock Code:
Code:
fastboot oem unlock 0xYOURKEY
Wait for it... And type now:
Code:
fastboot reboot
Wait for Your Device to Wipe and Start. Once in the Android System, turn Your Device off without USB Connected
Press and hold now the VolumeUp (+) Button while connecting to USB to enable the fastboot Mode
Continue with flashing the Images for Root (Step by Step):
Code:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
Wipe and Reboot:
Code:
fastboot -w
fastboot reboot
Note: Your are unlocked and rooted now! Enjoy Your Unleashed Device
5. GSI flashing with Fastboot:
Note: GSI ROMs can be found around the Web. Like here...
Treble-Enabled Device Development A/AB ROMS
Treble-Enabled Device Development A/AB ROMS
forum.xda-developers.com
Not all GSIs require the vbmeta change. You can use all GSIs that are made for ARM64 + A/B Devices. Play around. Systems can't damage Your Device since You keep the Stock Vendor & Kernel! You can use any Android Version! Don't forget to make backups if needed. You are going to Format Your Device!
Download a GSI Zip from Google
Extract the system.img and the vbmeta.img to Your Platform-Tools
Connect Your Device in Fastboot Mode and use Fastboot with:
(On 2020+ Xperias run: "fastboot reboot fastboot" first after You booted into fastboot)
Code:
fastboot flash system_a system.img
fastboot flash system_b system.img
[Optional] fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta.img
[Optional] fastboot --disable-verity --disable-verification flash vbmeta_b vbmeta.img
fastboot -w (This does Format Your Device and is needed everytime You change the GSI!)
fastboot reboot
6. Bootloader Re-Lock:
Flash the latest Firmware for Your Device with EMMA
Erase all Userdata before You continue (like with fastboot -w or via Recovery)
Just go into Fastboot mode and type in the command prompt (like before in this Guide):
Code:
fastboot oem lock
Wait for Your Device and disconnect it from USB
Done... Continue with Step 7.
7. Firmware Restoring after Re-Locking:
Download and Install the "Xperia Companion" from SONY
Open the Xperia Companion and select Software Repair
Select that Your Device can't get recognized (or is a Smartwatch 3 lol)
Go to the next Page and select the Xperia Smartphone Option
Continue and wait for the Initialization
Press and hold Volume DOWN while connecting to USB (You will see the Green Flashmode LED again)
Continue once Your Device gets recognized and let the Xperia Companion do his work...
Done. Your Bootloader is locked again and almost all of Your DRMs are restored.
Click to expand...
Click to collapse
Many thanks for your guide. Im just about to receive my phone in 2weeks time.
Is it a good idea to update android to the latest one before unlocking the bootloader and rooting the device or doesn't matter?
Make sure the device is up-to-date before rooting.
Note: the arms race between those rooting their devices and Google/app developers is particularly fierce at the moment. This means that you are likely to face issues hiding your rooted status from apps.
For example there is currently no way to root and still use both Google Pay and the Starling banking app. This is because Google Pay requires you to use Displax's Universal Safety Net Fix Mod to pass Play Integrity, whilst Starling detects any use of Zygisk (by means currently unknown) which UNSF relies on.
My Zenfone9 AI2202 (JP) Stopped at bootloader screen.
When I select recovery, it reboots and goes back to "Start" screen.
I used the following as a reference
Rooting Zenfone 9 with Magisk
Guide has been reworked to be more clear and based on comments. [Part One] Backup Data Update phone to latest version [Part Two] Download the Firmware for the Zenfone 9...
forum.xda-developers.com
Steps
- I have implemented the following steps
- Update OTA with Version WW-33.0804.2060.113 (2023/03/31)
- Download Same version of firmware
- dump boot.img using Payload Dumper GUI
- I patched boot.img with Magisk
- Execute the following command.
$fastboot flash boot patched_boot.img
I fell into a bootloop.
It is recognized as a fastboot device by Windows11.
Tried
I flashed boot.img before modifying it with Magisk.
Maybe I had wrong version on my device.
ASUS Flash Tool v2.0.1.0 only recognizes it as State: Fast boot device
I referred to the following
https://www.getdroidtips.com/asus-zenfone-9-ai2202-firmware-flash-file/
It says I can select "apply update from sd card." in Recovery mode,
But when I press the power button in Recovery mode, it reboots and won't let me enter recovery mode.
Question
How do I write the whole firmware?
I wish there was a flash-all.bat in the firmware like in Pixel series...
couldn't start from TWRP
$fastboot oem device-info
Device unlocked: false
The device may not have been successfully unlocked.
But then shouldn't fastboot flash boot boot.img fail?
Can boot.img be written without unlocking?
pompom252 said:
couldn't start from TWRP
Click to expand...
Click to collapse
I couldn't boot twrp after flashing magisk too until i remove magisk completely
pompom252 said:
My Zenfone9 AI2202 (JP) Stopped at bootloader screen.
When I select recovery, it reboots and goes back to "Start" screen.
I used the following as a reference
Rooting Zenfone 9 with Magisk
Guide has been reworked to be more clear and based on comments. [Part One] Backup Data Update phone to latest version [Part Two] Download the Firmware for the Zenfone 9...
forum.xda-developers.com
Steps
- I have implemented the following steps
- Update OTA with Version WW-33.0804.2060.113 (2023/03/31)
- Download Same version of firmware
- dump boot.img using Payload Dumper GUI
- I patched boot.img with Magisk
- Execute the following command.
$fastboot flash boot patched_boot.img
I fell into a bootloop.
It is recognized as a fastboot device by Windows11.
Tried
I flashed boot.img before modifying it with Magisk.
Maybe I had wrong version on my device.
ASUS Flash Tool v2.0.1.0 only recognizes it as State: Fast boot device
I referred to the following
https://www.getdroidtips.com/asus-zenfone-9-ai2202-firmware-flash-file/
It says I can select "apply update from sd card." in Recovery mode,
But when I press the power button in Recovery mode, it reboots and won't let me enter recovery mode.
Question
How do I write the whole firmware?
I wish there was a flash-all.bat in the firmware like in Pixel series...
Click to expand...
Click to collapse
Did you unlock your phone via Asus unlock app tool?
this is the link thread to restore back to stock
ZenFone 9 (AI2202) Repair to bootloader package
Download: Link 🔗 Steps: 1. Only works on EDL mode. 2. Run script 0-8475_update_image_EDL_fh_loader.bat 3. Update Official OTA package in recovery or install UserRAW in bootloader Thanks ASUS Taiwan, @EdwardWu6688 , and don't use it for...
forum.xda-developers.com
and for future reference, do not ever ever EVER
"Fastboot boot twrp.img"
Read the thread below, Asus have boot protection so fastboot boot is blocked and can lead to brick
[RECOVERY][OFFICIAL] TWRP for ASUS ZenFone 9
Official TWRP is now available: https://twrp.me/asus/zenfone9.html IMPORTANT NOTES: CleanSlate custom kernel is not currently compatible with TWRP for this device (Kirisakura is compatible as of v2.0.6). This device has a recovery partition (2...
forum.xda-developers.com
Jairus980 said:
and for future reference, do not ever ever EVER
"Fastboot boot twrp.img"
Read the thread below, Asus have boot protection so fastboot boot is blocked and can lead to brick
[RECOVERY][OFFICIAL] TWRP for ASUS ZenFone 9
Official TWRP is now available: https://twrp.me/asus/zenfone9.html IMPORTANT NOTES: CleanSlate custom kernel is not currently compatible with TWRP for this device (Kirisakura is compatible as of v2.0.6). This device has a recovery partition (2...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks for the reply.
Yes, I used Asus unlock app tool.
However, seeing that it is not locked, it may be that the unlocking was not successful.
I have attached a screenshot.
Is an EDL cable required to enter EDL mode?
pompom252 said:
Thanks for the reply.
Yes, I used Asus unlock app tool.
However, seeing that it is not locked, it may be that the unlocking was not successful.
I have attached a screenshot.
Is an EDL cable required to enter EDL mode?
Click to expand...
Click to collapse
adb dont work while on fastboot mode, you cant do via "adb"
I suggest you read the thread above
"ZenFone 9 (AI2202) Repair to bootloader package"
Take your time to read one by one
Jairus980 said:
adb dont work while on fastboot mode, you cant do via "adb"
I suggest you read the thread above
"ZenFone 9 (AI2202) Repair to bootloader package"
Take your time to read one by one
Click to expand...
Click to collapse
Thank you very much. In the relevant thread, you had the information after exchange about whether "EDL cable" is needed or not.
It is important to read carefully.
I solved the problem by running "flashall_AFT.cmd" with device recognized as fastboot device.
Android 12 is now booted!
I was worried that IMEI would disappear, but I was able to keep IMEI.
My device was purchased in Japan, so it was equipped with Felica, which could also continue to be used.
Thank you very much for your good advice.