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.
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:
Maze has finally published the Alpha Stock-Rom.
Download Link: https://goo.gl/9kCJiv :fingers-crossed:
The system.img file is incorrectly downloaded as a system 002.img file. It must be renamed. And then copy it to the folder "3. Maze_Alpha_V05_20170816 Official ROM".
Thanks!
Hope anyone can root this phone.
Hi!
I am in need of a new phone, and this one looks quite good at the price.. But what do you think can i expect from custom ROM scene here for it? I am a Xiaomi Fan, and my Mi4 was and is one of the best supported phones still. Do you think there will be a subforum for this device, custom ROMs (preferreable Lineage OS, or other close to AOSP ROMs? OFC nobody can know now, i understand, but what tells your experience of other new phones from new companys? It has created quite a buzz, so i think there will be a demand for sure..
Just am 2 afraid to get a phone without good custom ROM. Never had an Android in last 5 years with stock ROM. Total nightmare for me now to have to go back.
Root + TWRP 3.2.1
3 Methods to root MAZE Alpha
Note: Method II is the most universal and must works with almost any official ROM
I- Method 1 : flashing modified Magisk boot.img
1. make sure to have already installed the version 20170816
2. reboot the phone in fastboot mode (phone off -> Vol Up + Power or "adb reboot bootloader")
3. unlock the bootloader if not already done : fastboot flashing unlock (if not works, in android development setting set the unlock bootloader and then retry)
4. unzip and then flash the attached boot image : fastboot flash boot new-boot.img
5. reboot your phone: fastboot reboot
6. install the MagiskManager apk v14
7. Voila
I have used this Magisk guide to create it
I used old manual guide :
Code:
adb shell "rm -rf /data/local/tmp/*"
adb push META-INF/com/google/android/update-binary common magisk_inject boot.img /data/local/tmp
adb shell "cd /data/local/tmp/magisk_inject; mv ../common/* .; chmod 755 *; sh ../update-binary indep boot_patch.sh ../boot.img; mv ../bin/busybox busybox"
adb pull /data/local/tmp/magisk_inject/new-boot.img
adb shell "rm -rf /data/local/tmp/*"
II- Method 2 : using TWRP and Magisk.zip (External SDCARD or USB OTG cable needed)
1. reboot int bootloader mode : adb reboot bootloader
2. unzip and flash the the attached TWRP recovery : fastboot flash recovery recovery_maze_alpha_4G_twrp-321.img
3. In TWRP choose first "change language" then press the "cancel" button while asking you for decryption password for data
4. In your PC download the Magisk-v15.3.zip and put it in a USB key, or an SDCARD
5. Use an usb otg cable to connect the USB key to your phone running TWRP and install the Magisk-v14.zip from Usb-otg (or SDCARD)
6. bonus: do a complete backup of your phone : all partitions except cache and data to your Usb-otg (or SDCARD)
7. reboot and install the MagiskManager apk v14
III- Method 3 : using the phhusson modified boot image
1- flash the attached boot image, using fasboot (fastboot flash boot boot-super-bootimg-output-su-eng-r318.img) or SPFlashTools using the attached scatter, if you do not want to unlock your bootloader
2- reboot to Android then install from google play the phhsusson superuser
3- Voila
Important Notes:
1- In all case you can use SPFlashTools to flash boot image without unlocking bootloader.
2- windows SPFlashTools users : phone off, press VOL+ and connect it to your PC (running SPFlashTool and waiting for phone connetion)
3- linux SPFlashTools users : phone off and connected to PC , press VOL+ and POWER while your PC is running SPFlashTool (with sudo) and waiting for phone connetion.
Some useful tips
1- manual install of busybox :
a- root you phone with method II if not already done
b- stay in TWRP (or boot TWRP as in method II) then in advance->sideload slide the slider to confirm and after cancel that (we will not sideloading any thing, just to activate adb)
c- unzip and copy the attached busybox : adb push busybox /external_sd/
d- mount the system partition with the TWRP mount button
e- copy the busybox binary to /system/xbin : adb shell --> cp /external_sd/busybox /system/xbin/
f- make executable busybox and create links (the point at the end is a part of the command) : cd /system/xbin/; chmod 755 busybox; ./busybox --install -s .
g- umount the system partition in TWRP and reboot
2- manually install the OTA update.zip :
a- Google and download those 3 tools BlockImageUpdate, simg2img and img2simg.
b- In a terminal of your Linux PC do :
Code:
simg2img system.img system.raw.img # convert the sparse image to a normal raw (ext4) image
BlockImageUpdate system.raw.img system.transfer.list system.new.dat system.patch.dat # patch the newly created raw image
img2simg system.raw.img system.img # convert the patched raw image to a flashable sparse image
- system.img: you old system image (from 20170816 official rom)
- system.transfer.list, system.new.dat and system.patch.dat : inside the OTA update.zip
c- After that the original system.img will be patched and you will have an updated system.img.
d- Flash this patched system.img and also all .bin and .img files inside the update.zip (just replace old ones in the original 20170816 rom by those) and you will have the new official rom
3- Using supersu as root manager :
The last update at this time of supersu zip (2.82 SR5) works well, even it cannot update the su binary.
Credits to Magisk Devs, Phhusson and Jemmini
dreambo said:
Here how to root this phone.
1. make sure to have already installed the version 20170816
2. reboot the phone in fastboot mode (phone off -> Vol Up + Power or "adb reboot bootloader")
3. unlock the bootloader if not already done : fastboot flashing unlock (if not works, in android development setting set the unlock bootloader and then retry)
4. unzip and then flash the attached boot image : fastboot flash boot new-boot.img
5. reboot your phone: fastboot reboot
6. install the MagiskManager apk v13.6
7. Voila
I have used this Magisk guide to create it
Credits to Magisk Devs.
Click to expand...
Click to collapse
If I root my phone with this method, will I get further OTA Updates from Maze?
Following to see where this goes.
Cheers
CrashCrash123 said:
If I root my phone with this method, will I get further OTA Updates from Maze?
Click to expand...
Click to collapse
Yes.
You will only lost the root.
If the new update have the same kernel, the same methode with the same boot image can be used to root it again, othewise, we can follow the Magisk guide to create a new one.
I have tried this method. But it only works until the reboot. Then the root access is gone again.
SomeOneX said:
I have tried this method. But it only works until the reboot. Then the root access is gone again.
Click to expand...
Click to collapse
The root is permanent.
If you lost it, perhaps the first time we unlock the bootloader, the phone do a reset, and we lost the root (I suppose).
Just re-flash the new boot again, and it will be permanent : fastboot flash boot new-boot.img
Hi . I have locked the OEM lock but I can not install it through fastboot (remote: not allowed in lock state)
can we expect VOLTE on this device ?
and is there any chance of custom rom development for this device?
alfymon22 said:
can we expect VOLTE on this device ?
and is there any chance of custom rom development for this device?
Click to expand...
Click to collapse
It seems (take with a pinch of salt) that VoLTE is supported, but then most sites that announce that also make mistakes on other specs, so...)
As for custom ROMs, so far the square root of bugger all, but the consumer phones are just filtering in, so give it time.
dreambo said:
Here how to root this phone.
1. make sure to have already installed the version 20170816
2. reboot the phone in fastboot mode (phone off -> Vol Up + Power or "adb reboot bootloader")
3. unlock the bootloader if not already done : fastboot flashing unlock (if not works, in android development setting set the unlock bootloader and then retry)
4. unzip and then flash the attached boot image : fastboot flash boot new-boot.img
5. reboot your phone: fastboot reboot
6. install the MagiskManager apk v13.6
7. Voila
I have used this Magisk guide to create it
Credits to Magisk Devs.
Click to expand...
Click to collapse
it worked, but i have cts fail on safetynet check. how you fixed this?
PrimateaEu said:
it worked, but i have cts fail on safetynet check. how you fixed this?
Click to expand...
Click to collapse
install the universal safety net fix
Hey guys, does this root method wipe the data partition?
KilljoyTDA said:
Hey guys, does this root method wipe the data partition?
Click to expand...
Click to collapse
The flash of the boot image does not wipe the data, but unlocking the bootloader reset the phone and wipe the data.
If you phone is already unlocked, you will not loss the data, otherwise do a backup before.
Well, I don't remember unlocking it, unless Kingo's windows app does it without telling even when rooting fails, so I guess I'd better back up.
Thanks for the info
KilljoyTDA said:
Well, I don't remember unlocking it, unless Kingo's windows app does it without telling even when rooting fails, so I guess I'd better back up.
Thanks for the info
Click to expand...
Click to collapse
It is easy to know if your phone is locked or not : enter fastboot mode and then do : "fastboot getvar all".
Read the last lines of the output and you will know.
Thank you @dreambo for this method, but for me "fastboot flashing unlock" not work, "fastboot oem unlock" working for me, all ok
ps:excusez moi pour mon anglais
dreambo said:
It is easy to know if your phone is locked or not : enter fastboot mode and then do : "fastboot getvar all".
Read the last lines of the output and you will know.
Click to expand...
Click to collapse
Well I failed to back up for some reason anyways, so since I had almost nothing vital on the internal memory, I rooted (sucessfully) and now I'm reinstalling/reconfiguring my apps. Thanks anyways
Hey guys,
just got my Xiaomi Mi A3 today, so i wanted to install TWRP and root the phone with Magisk.
Well my problem is that the device is now stuck in "fastboot" mode. I mean there are tons of tutorials outside, but they are different. So it is really hard to known, which one will work. There are a lot of tutorials which are describing the way with an unofficial .img and and TWRP Installer with it.
So what have i done so far:
1. Installed the needed ADB and Xiaomi drivers and downloaded "Android Platform Tools"
2. Unlocked the bootloader on the device --> so far everything was OK
3. Then i found an tutorial and it is saying that i should use the following command "fastboot boot twrp-3.3.1-0-laurel_sprout.img"
Unfortunately, if i am trying to enter that i am getting the following error: fastboot error: command failed (remote - unknown command)
So after that i was searching for an Tutorial on YouTube and found an different way.
The guy in the tutorial is using the command: "fastboot flash boot twrp.img"
Well, the end of the story is at the moment, it doesn´t matter how i want to reboot my device it always lands in "fastboot" mode.
Is there an kind soul outside, which can help me out to install twrp on my phone? Hopefully with an "CORRECT" Tutorial?
Thank you.
Edit# 1: If i enter the command "fastboot set_active b" my phone loads up and says "Can´t load Android System. Your data may be corrupt. And i can choose between Try again and factory data reset.
Edit# 2: Okay, i made some research and tried the following commands:
fastboot erase userdata
fastboot getvar all
fastboot erase boot
fastboot set_active b
fastboot erase boot
fastboot flash boot twrp.img
fastboot reboot
The phone booted now directly to TWRP.
Edit# 3: Okay, so as far as i understand, i wiped my stock rom with the command: fastboot flash boot twrp.img , because i didn´t switched the slot to "b" before, correct?
After my commands in "Edit# 2" i wiped everything and installed TWRP permanently to slot "b". Just went through TWRP a little bit and if i click on "Install" all Storage devices are at 0MB. So how do i get my stock ROM back?
My Problem is that this device already had this faulty Android 10 version when i bought that. When i firsted turned that on, the phone was showing me that an Android Update is available. But when i wanted to install that, it was saying this update is for Android 9. I think you know what i am talking about.
So what are my options now? Where do i get that stock rom back and how should i proceed? I also saw some posts here that an downgrade is not that good, because a lot of sensors will not work after that.
I was on the latest Android 10 March Security Patch and had the same problem. However, I was able to figure it out and made it work. Here's what I did:
1. Flash the latest Android 10 fastboot rom (search in XDA)
2. Download this modified boot image: https://drive.google.com/file/d/1-dCUenlLq4C-l-LJWQUsOFhlIRRAb5xI/view?usp=drivesdk
3. On fastboot, execute: fastboot getvar current-slot (make sure you are on slot A)
3. If not on A, execute: fastboot set_active a
4. Execute: fastboot flash boot (image name).img
5. Fastboot reboot (make sure to press volume + before hitting enter)
6. You are now booted to TWRP
7. Flash the TWRP Installer zip (can be found in XDA)
8. Wipe dalvik cache
9. Reboot to fastboot
10. Execute: fastboot set_active b
11. Execute: fastboot reboot
Let me know if this works for you! Hope this is a great help.
kevinxjen said:
I was on the latest Android 10 March Security Patch and had the same problem. However, I was able to figure it out and made it work. Here's what I did:
1. Flash the latest Android 10 fastboot rom (search in XDA)
2. Download this modified boot image: https://drive.google.com/file/d/1-dCUenlLq4C-l-LJWQUsOFhlIRRAb5xI/view?usp=drivesdk
3. On fastboot, execute: fastboot getvar current-slot (make sure you are on slot A)
3. If not on A, execute: fastboot set_active a
4. Execute: fastboot flash boot (image name).img
5. Fastboot reboot (make sure to press volume + before hitting enter)
6. You are now booted to TWRP
7. Flash the TWRP Installer zip (can be found in XDA)
8. Wipe dalvik cache
9. Reboot to fastboot
10. Execute: fastboot set_active b
11. Execute: fastboot reboot
Let me know if this works for you! Hope this is a great help.
Click to expand...
Click to collapse
Hey there,
first of all thank you for your reply
Unfortunately those steps were not working for me or i am misunderstanding something.
So i followed your steps:
1. Flash the latest Android 10 fastboot rom (search in XDA) - found that here https://forum.xda-developers.com/mi-a3/how-to/fastboot-rom-android-10-v11-0-8-0-march-t4069077
Unzipped the files to my platform-tools folder and started the "flash_all.bat" file. No errors so far -> after the last command "fastboot reboot" device automatically booted up and it stucked on the "mi" logo. In the thread which i have mentioned above a few people had the same problem and they were told to execute an factory reset.
So i went back to fastbood mode and typed in "fastboot erase userdata" - but nothing happended. So i was stuck at the "mi" logo.
Then i thought i will go on and follow the next steps:
2. Download this modified boot image: - downloaded that
3. On fastboot, execute: fastboot getvar current-slot (make sure you are on slot A)
3. If not on A, execute: fastboot set_active a
4. Execute: fastboot flash boot (image name).img
5. Fastboot reboot (make sure to press volume + before hitting enter)
6. You are now booted to TWRP Endresult: NO TWRP was booting straight away back to fastboot mode
What am i doing wrong? I just want to go back to my Androis OS with latest March Security Patch and Install TWRP permanently,so after that i can root it with Magisk.
Edit# 1: I was not using your modified boot image, i took that one: https://forum.xda-developers.com/showpost.php?p=82087765&postcount=3 and could boot into TWRP after that.
But anyways it seems that there is nothing on my phone, i still stuck at the "mi" logo and when i go to TWRP, everything is empty on the storage device. I mean if i go to the Button "Wipe" --> "then Swipe for factory reset" i get the following errors.
"Could not mount /data and unable to find crypto footer."
"unable to mount storage"
Current state of the device:
Booting normally: Stucks on "Mi" Logo
Holding Volume Down + Power: boots to "FastBoot Mode"
Holding Volume Up + Power: boots to "TWRP"
Edit# 2: Phone is alive again
Followed these steps below and managed to install TWRP permanently and get back my Android OS.
If you have fastboot, simply flash TWRP, boot to TWRP recovery, do a full wipe, including formatting using data. Reboot to TWRP ( check boxes to install TWRP manager - if you see that screen)
Once rebooted to TWRP Recovery, Flash Rom of Choice, Gapps if needed, Flash Magisk again. Boot to system and setup.
The only issue i am having at the moment, everytime i Install the Magisk.zip over TWRP my A3 stucks at "mi" logo. So just need to figure that out.
But hey i´m almost done!
Edit# 3: Tried to install Disable_Dm-Verity_ForceEncrypt package, before Magiskv20.4 installation, but still getting bootloop after flashing the .zip file.
-----------------------------------------------------------------------------------------------------------------------------------------------------------
Final Update: Everything is working Oh god, that was my first day with an Android Phone and i really learned a lot about it. Even if i figured out everything by myself, i hope that this thread helps someone out, who is facing similiar issues.
Final Steps:
1. downloaded MiFlash and flashed my Mi A3 with the latest ROM - laurel_sprout_global_images_V11.0.8.0.QFQMIXM_79d650b0da_10.0 -
2. Device booted up with an error that the Android OS is corrupted and i had to reset it to factory settings
3. Device booted up to the Android OS.
4. Downloaded my stock boot.img and copied that to my Downloads folder
5. Installed Magisk Manager on my device and patched my stock boot image. If everything is done an new magisk_patched.img will be created under the same path.
6.Used following command to copy the .img file from my device to my PC "adb pull /sdcard/Download/magisk_patched.img"
7. Opened CMD --> navigated to my adb tools and typed in following code: adb reboot bootloader --> Enter --> fastboot flash boot magisk_patched.img --> Enter --> fastboot continue
8. Done, device booted up and Magisk was successfully installed.
Thank you.
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
Rooting the POCO M4 Pro 4G (fleur) turned out to be quite straightforward. Note, I have a 2201117PG (EEA), you may have a different experience, it's not my fault if you brick your phone etc. Backup before you start as this will wipe your phone.
The process can be broken down into 4 steps:
Unlock Bootloader
Source boot.img
Patch boot.img (using Magisk)
Flash patched boot.img (using adb)
1. Unlock BootloaderNote: This step will wipe your phone.
This can be done using the official tool from MIUI, using MediatekBootloaderUnlock (Windows 10/11, which reportedly does not wipe your user data), or using mtkclient (Any OS but requires Python). I will explain the mtkclient option as I'm on Linux and don't trust MIUI with more personal data than I have to.
Step-by-step (adapted from this How to Guide):
Install mtkclient and its dependencies (easier if familiar with installing python packages etc., straightforward for me on Linux)
On your phone activate developer mode and turn on USB debugging and OEM unlocking
Turn off phone and disconnect from computer
In the directory where you installed mtkclient run:
python mtk e metadata,userdata,md_udc
This erases your data
At this point plug your phone in (still turned off)
python mtk da seccfg unlock
This unlocks the bootloader
python mtk reset
This reboots the phone
Disconnect USB cable and reboot phone
When it boots a message is displayed warning that dm-verity is corrupted. Click the power button to dismiss and continue booting.
2. Source boot.img
Find your MIUI version in Settings -> About phone -> MIUI Version and look for the version number (e.g. 13.0.6.0(RKEEUXM))
Visit the MIUI Updates Tracker and download the matching Stable Fastboot update (if you can't find it scroll down to Extracting boot.img from Payload)
Unzip the TGZ and the TAR that it contains then navigate to the images directory and find the boot.img file
3. Patch boot.imgWe need to patch the boot.img to give it root powers. We do this on the phone using Magisk.
Step-by-step (adapted from the Magisk installation instructions):
On your phone, download Magisk and install it
Connect your phone to your computer and put the boot.img you extracted on your phone somewhere
Open Magisk and in "Magisk" section tap "Install"
Choose the "Select and Patch a File" option and select your boot.img in the file browser and let Magisk patch it
Find the patched boot image in Downloads (called magisk_patched_*.img) and copy it to your computer in the same directory as the vbmeta.img we extracted earlier
4. Flash patched boot.imgFinally we need to replace the current boot.img on the phone with our patched one that has root powers. This is called flashing and is done using adb.
Step-by-step:
Install the Android SDK platform tools which contains adb and fastboot
Install a USB driver that supports fastboot mode (you cannot use fastbootd for this or you'll bootloop)
Ensure your phone is connected, USB debugging is enabled and working, and OEM Unlocking is enabled
In the directory you copied the magisk_patched_*.img to run:
adb reboot bootloader
This reboots your phone into fastboot mode. Wait until "FASTBOOT" is displayed on the screen
fastboot flash boot magisk_patched_*.img
This flashes the patched boot.img to give you root
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
This flashes the vbmeta.img, disabling the dm-verity corruption message at startup
Once it's done reboot your phone by pressing and holding the power button
That's all there is to it! This took me about an hour as I was working out all the steps as I've not rooted in a phone in nearly a decade - I reckon with a fast internet connection you could get it done in about 15 minutes.
Extract boot.img from PayloadIf you can't find a fastboot image (boot.img) for your version then you might be able to extract it from the full firmware package. This will require the use of a third party tool such as payload-dumper (python) or payload-dumper-go. Note that you may be better off just waiting for the fastboot image to be released to the public.
Tidying upYou can delete all the stuff you downloaded onto your computer and the boot.img and magisk_patched_*.img from your phone.
It's a good idea to disable automatic OTA updates (Settings -> Additional settings -> Developer options -> Automatic sytem updates) so that you can update through Magisk.
Some apps will be able to tell that you have rooted your phone, and may stop you from using them. You can check this by downloading YASNAC onto your phone and seeing if it passes. If not (which it won't) the most straightforward solution is to add the Universal SafetyNet Fix module to Magisk, then enable Zygisk in Magisk settings and restart your phone, which will be enough to pass SafetyNet Attestation. If they're clever and still detect the root then in Magisk toggle Enforce DenyList and add the problematic apps to the DenyList.
Updating Magisk
You cannot update Magisk via the Magisk app, as this device does not allow writing to the boot partition at runtime.
Instead, update the Magisk app, then use it to patch your stock boot.img and flash it manually using fastboot, as if you were installing it from scratch (as above). This will not wipe your user data, but be sure to backup first in case something goes wrong.
aricooperdavis said:
Rooting the POCO M4 Pro 4G (fleur) turned out to be quite straightforward. Note, I have a 2201117PG (EEA), you may have a different experience, it's not my fault if you brick your phone etc.
The process can be broken down into 4 steps:
Unlock Bootloader
Source boot.img (using payload_dumper)
Patch boot.img (using Magisk)
Flash patched boot.img (using adb)
1. Unlock BootloaderThis can be done using the official tool from MIUI or using mtkclient. I went for the mtkclient option as I don't want to send more of my personal data to MIUI than I have to.
Step-by-step (adapted from this How to Guide):
Install mtkclient and its dependencies (easier if familiar with installing python packages etc., straightforward for me on Linux)
On your phone activate developer mode and turn on USB debugging and OEM unlocking
Turn off phone and disconnect from computer
In the directory where you installed mtkclient run:
python mtk e metadata,userdata,md_udc
At this point plug your phone in (still turned off)
python mtk da seccfg unlock
python mtk reset
Disconnect USB cable and reboot phone
When it boots a message is displayed saying it is corrupted. Click the power button to dismiss and continue booting.
2. Source boot.imgThe boot.img needs to be extracted from the official MIUI firmware package using payload_dumper.
Step-by-step:
Download the firmware package for your device (you can check what version you need in Settings -> About phone -> MIUI version (For POCO)
Extract the .zip and find the payload.bin file
Download the payload dumper, extract the zip, and place the payload.bin file in the payload_dumper folder
In the payload_dumper directory run:
python payload_dumper.py payload.bin
This will extract lots of files from the firmware package. You only need to keep boot.img and vbmeta.img
3. Patch boot.imgWe need to patch the boot.img to give it root powers. We do this on the phone using Magisk.
Step-by-step (adapted from the Magisk installation instructions):
On your phone, download Magisk and install it
Connect your phone to your computer and put the boot.img you extracted on your phone somewhere
Open Magisk and in "Magisk" section tap "Install"
Choose the "Select and Patch a File" option and select your boot.img in the file browser and let Magisk patch it
Find the patched boot image in Downloads (called magisk_patched_*.img) and copy it to your computer in the same directory as the vbmeta.img we extracted earlier
4. Flash patched boot.imgFinally we need to replace the current boot.img on the phone with our patched one that has root powers. This is called flashing and is done using adb.
Step-by-step:
Install the Android SDK platform tools which contains adb and fastboot
Install a USB driver that supports fastboot mode
Ensure your phone is connected, USB debugging is enabled and working, and OEM Unlocking is enabled
In the directory you copied the magisk_patched_*.img to run:
adb reboot bootloader
This reboots your phone into fastboot mode. Wait until "FASTBOOT" is displayed on the screen
fastboot flash boot magisk_patched_*.img
fastboot flash vbmeta --disable-verity --dsable-verification vbmeta.img
Once it's done reboot your phone by pressing and holding the power button
That's all there is to it! This took me about an hour as I was working out all the steps as I've not rooted in a phone in nearly a decade - I reckon with a fast internet connection you could get it done in about 15 minutes.
Tidying upYou can delete all the stuff you downloaded onto your computer and the boot.img and magisk_patched_*.img from your phone.
It's a good idea to disable automatic OTA updates (Settings -> Additional settings -> Developer options -> Automatic sytem updates) so that you can update through Magisk.
Some apps will be able to tell that you have rooted your phone, and may stop you from using them. You can check this by downloading YASNAC onto your phone and seeing if it passes. If not (which it won't) the most straightforward solution is to add the Universal SafetyNet Fix module to Magisk, then enable Zygisk in Magisk settings and restart your phone, which will be enough to pass SafetyNet Attestation. If they're clever and still detect the root then in Magisk toggle Enforce DenyList and add the problematic apps to the DenyList.
Click to expand...
Click to collapse
Wow, Thank you very much!
Very details!
Will try it in my spare time.
MarkLev said:
Wow, Thank you very much!
Very details!
Will try it in my spare time.
Click to expand...
Click to collapse
Good luck, let us know how it goes and what you do with your root! So far I've installed AdAway and De-Bloater
aricooperdavis. hi!I buy phone Poco M4 Pro (4G) (fleur). Please help me get ROOT rights for this phone.
I do not have PYTHON, but I have mtkclient - the bootloader is unlocked, and there is an Android SDK for fastboot firmware.
Global 13.0.7.0 RKEMIXM now. You have 2 file 1.magisk_patched_*.img and 2. vbmeta.img for Global 13.0.7.0 ? Can I save them for download?
After unlocking the bootloader, using the mtkclient method, a new notification appeared
- dm-verity coruption
You device is corrupt/
It can't be trusted and may not work properly
Press power button to contime
Or, device will power off in 5 sec. Always need PRESS POWER for contime again How to fix it?
It sounds like you've done everything right so far.
Lark5 said:
Global 13.0.7.0 RKEMIXM now. You have 2 file 1.magisk_patched_*.img and 2. vbmeta.img for Global 13.0.7.0 ? Can I save them for download?
Click to expand...
Click to collapse
Sorry, I have the EEA firmware; RKEEUXM.
If you want to extract the boot.img and vbmeta.img from your firmware package you will have to install python. This is worth doing as installing updates in the future may require you to do this extraction process again.
Alternatively you may be able to use mtk to dump these images directly from the phone, but I don't have any experience with this. To perform updates this way you would have to completely unroot and relock the bootloader, update the firmware, then re-dump the new boot and vbmeta images and root again. I think just installing python is probably easier...
The error message you're seeing is dm-verity, and we disable this when flashing the vbmeta.img in step 4, which I've edited to clarify. You can see that we disable it in the final fastboot command:
aricooperdavis said:
fastboot flash vbmeta --disable-verity --dsable-verification vbmeta.img
This flashes the vbmeta.img, disabling the dm-verity corruption message at startup
Click to expand...
Click to collapse
Good luck with your rooting!
Unlock Bootloade and Root and RECOVERY for Poco M4 Pro (4G) with out Pyton (on Windows 10\11):
Unlock Bootloader:
1.Download the MediatekBootloaderUnlock archive. Unpack the archive ZIP.
2. Open the Driver folder and right-click the cdc-acm.inf file, select "Install"
3.Now go back to the main folder and install the USBDK (x64 for 64-bit OS, x86 for 32-bit OS) on your PC (also right click - install).
4. Reboot the PC.
5.Turn off the phone.
6.Run the UnlockBootloader.bat file to start the bootloader unlock process. We keep it on, it is in a state of response from the phone, if the firewood, the cable is connected, then everything is ok, I’ll tell you right away that it turned out 3 times.
7.Now connect the phone to the computer with a cable by holding down the volume up + down + power button. (If the volume up button doesn't work, try using volume up or volume up + volume down or all three hardware buttons) while the UnlockBootloader.bat file is open.
8.Once the phone is detected, some commands will be run in the UnlockBootloader.bat file. Let the commands finish and as soon as the window closes. Your bootloader will be unlocked.
BY THE WAY! - You can lock the bootloader again by following the same steps without clearing. Just use LockBootloader.bat with the same steps.
Root:
Downloading the official firmware for the phone, I took fleur_global_images_V13.0.7.0.RKEMIXM_20220419.0000.00_11.0_global (approximately 5.6GB in weight)
Unpacked it ZIP, pulled out 2 files from there fleur_global_images_V13.0.7.0.RKEMIXM_20220419.0000.00_11.0_global\images
boot.img and vbmeta.img
Downloaded Magisk STABLE Version: 24.3 - download on telephone, setup APP
Launch Magisk Manager. When a pop-up window appears asking you to install Magisk, select INSTALL and select install again.
Click on "Fix Boot Image File".
Connect your device to PC via USB cable. Make sure USB debugging is enabled.
Download ADB \ fastoot (I took tools_r29.0.6-windows)
Run CMD as Administrator
We write -
adb devices - the phone must be determined (QX ********* device - so all drivers are correct)
adb reboot bootloader - The phone reboots into fastboot mode - an inscription on the screen if dm-verity corruption messages appear - press POWER to continue
fastboot flash boot boot_PATCH.img (file name how to change)
fastboot flash vbmeta --disable-verity --dsable-verification vbmeta.img - will remove the inscription dm-verity corruption
OrangeFox-R11 RECOVERY:
Downloads for : -Android- Generic Device/Other | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Download, and Run CMD as Administrator
We write -
fastboot flash boot XXXXNAMEXXXX.img
Flash !boot! not fastboot flash recovery XXXXNAMEXXXX.img
Well done, glad you've got it sorted!
To clarify, this essentially follows the same 4 steps outlined in my post but using different tools that don't require python:
Unlock Bootloader
- Used MediatekBootloaderUnlock rather than mtkclient
Source boot.img
- Managed to find the images online without having to extract them from a ROM. @Lark5, where?
Patch boot.img (using Magisk)
- Same
Flash patched boot.img (using adb)
- Same
I think there's also a custom recovery install too (OrangeFox [not yet officially supported]) at the end. I tend not to bother with custom recoveries as I stick with the stock MIUI ROM and a custom recovery would complicate applying OTA updates. However, if you wish to install a custom ROM (anything other than a stock MIUI signed boot.img) then a custom recovery would be necessary, and they can also facilitate taking device backups etc.
aricooperdavis said:
Well done, glad you've got it sorted!
To clarify, this essentially follows the same 4 steps outlined in my post but using different tools that don't require python:
Unlock Bootloader
- Used MediatekBootloaderUnlock rather than mtkclient
Source boot.img
- Managed to find the images online without having to extract them from a ROM. @Lark5, where?
Patch boot.img (using Magisk)
- Same
Flash patched boot.img (using adb)
- Same
I think there's also a custom recovery install too (OrangeFox). I tend not to bother, but it can be convenient.
Click to expand...
Click to collapse
2. Find ROM on this link: https://mirom.ezbox.idv.tw/en/phone/fleur/roms-global-stable/
Fastboot Download V13.0.7.0.RKEMIXM
Explanations:
For fastboot (~5.6Gb) - firmware version, just unzip the ZIP, inside there is boot.img and vbmeta
For recovery (-2.5Gb) needed to extract boot.img Through Pyton for example
thanks for the help aricooperdavis
Lark5 said:
Find ROM on this link: https://mirom.ezbox.idv.tw/en/phone/fleur/roms-global-stable/
Click to expand...
Click to collapse
That's a great resource - the files it links to seem to be hosted on MIUIs servers too, so they're verifiably official
The more general link for all regions (not just global) for this phone would be: https://mirom.ezbox.idv.tw/en/phone/fleur/
I've updated the instructions to reflect your experience, thanks @Lark5!
aricooperdavis said:
Rooting the POCO M4 Pro 4G (fleur) turned out to be quite straightforward. Note, I have a 2201117PG (EEA), you may have a different experience, it's not my fault if you brick your phone etc. Backup before you start as this will wipe your phone.
The process can be broken down into 4 steps:
Unlock Bootloader
Source boot.img
Patch boot.img (using Magisk)
Flash patched boot.img (using adb)
1. Unlock BootloaderNote: This step will wipe your phone.
This can be done using the official tool from MIUI, using MediatekBootloaderUnlock (Windows 10/11), or using mtkclient (Any OS but requires Python). I will explain the mtkclient option as I'm on Linux and don't trust MIUI with more personal data than I have to.
Step-by-step (adapted from this How to Guide):
Install mtkclient and its dependencies (easier if familiar with installing python packages etc., straightforward for me on Linux)
On your phone activate developer mode and turn on USB debugging and OEM unlocking
Turn off phone and disconnect from computer
In the directory where you installed mtkclient run:
python mtk e metadata,userdata,md_udc
This erases your data
At this point plug your phone in (still turned off)
python mtk da seccfg unlock
This unlocks the bootloader
python mtk reset
This reboots the phone
Disconnect USB cable and reboot phone
When it boots a message is displayed warning that dm-verity is corrupted. Click the power button to dismiss and continue booting.
2. Source boot.imgNote: if your MIUI version (Available at: Settings -> About phone -> MIUI version) has a "Fastboot" file listed here then you can download that file and unzip it to find the boot.img and vbmeta.img, then skip to step 3.
Otherwise you'll have to extract them from the official MIUI firmware package using payload_dumper as follows.
Step-by-step:
Download the firmware package for your device (you can check what version you need in Settings -> About phone -> MIUI version (For POCO))
Extract the .zip and find the payload.bin file
Download the payload dumper, extract the zip, and place the payload.bin file in the payload_dumper folder
In the payload_dumper directory run:
python payload_dumper.py payload.bin
This will extract lots of files from the firmware package. You only need to keep boot.img and vbmeta.img
3. Patch boot.imgWe need to patch the boot.img to give it root powers. We do this on the phone using Magisk.
Step-by-step (adapted from the Magisk installation instructions):
On your phone, download Magisk and install it
Connect your phone to your computer and put the boot.img you extracted on your phone somewhere
Open Magisk and in "Magisk" section tap "Install"
Choose the "Select and Patch a File" option and select your boot.img in the file browser and let Magisk patch it
Find the patched boot image in Downloads (called magisk_patched_*.img) and copy it to your computer in the same directory as the vbmeta.img we extracted earlier
4. Flash patched boot.imgFinally we need to replace the current boot.img on the phone with our patched one that has root powers. This is called flashing and is done using adb.
Step-by-step:
Install the Android SDK platform tools which contains adb and fastboot
Install a USB driver that supports fastboot mode
Ensure your phone is connected, USB debugging is enabled and working, and OEM Unlocking is enabled
In the directory you copied the magisk_patched_*.img to run:
adb reboot bootloader
This reboots your phone into fastboot mode. Wait until "FASTBOOT" is displayed on the screen
fastboot flash boot magisk_patched_*.img
This flashes the patched boot.img to give you root
fastboot flash vbmeta --disable-verity --dsable-verification vbmeta.img
This flashes the vbmeta.img, disabling the dm-verity corruption message at startup
Once it's done reboot your phone by pressing and holding the power button
That's all there is to it! This took me about an hour as I was working out all the steps as I've not rooted in a phone in nearly a decade - I reckon with a fast internet connection you could get it done in about 15 minutes.
Tidying upYou can delete all the stuff you downloaded onto your computer and the boot.img and magisk_patched_*.img from your phone.
It's a good idea to disable automatic OTA updates (Settings -> Additional settings -> Developer options -> Automatic sytem updates) so that you can update through Magisk.
Some apps will be able to tell that you have rooted your phone, and may stop you from using them. You can check this by downloading YASNAC onto your phone and seeing if it passes. If not (which it won't) the most straightforward solution is to add the Universal SafetyNet Fix module to Magisk, then enable Zygisk in Magisk settings and restart your phone, which will be enough to pass SafetyNet Attestation. If they're clever and still detect the root then in Magisk toggle Enforce DenyList and add the problematic apps to the DenyList.
Click to expand...
Click to collapse
When I gave this command fast boot flash dm verify it always unknown option in my cmd any solution ? can anybody help me??
Daafafagsgsgs said:
When I gave this command fast boot flash dm verify it always unknown option in my cmd any solution ? can anybody help me??
Click to expand...
Click to collapse
Make sure you're copying the command exactly - it's fastboot rather than fast boot and verity not verify. Did you install the Android SDK platform tools that contain fastboot? You may need to restart after this install to make the command available in your command prompt/shell.
aricooperdavis said:
Make sure you're copying the command exactly - it's fastboot rather than fast boot and verity not verify. Did you install the Android SDK platform tools that contain fastboot? You may need to restart after this install to make the command available in your command prompt/shell.
Click to expand...
Click to collapse
Yeah i copied the same command but how to install Android sdk tools can you suggest me a video?
Daafafagsgsgs said:
Yeah i copied the same command but how to install Android sdk tools can you suggest me a video?
Click to expand...
Click to collapse
Go to this link, scroll to the downloads section, and select the right download for your OS, then follow the instructions.
This video shows the process, but has very annoying music!
aricooperdavis said:
Make sure you're copying the command exactly - it's fastboot rather than fast boot and verity not verify. Did you install the Android SDK platform tools that contain fastboot? You may need to restart after this install to make the command available in your command prompt/shell.
Click to expand...
Click to collapse
I installed and tried everything this error comes
Interesting, that sounds like you've got an outdated version of fastbook. What does fastboot --version give you?
Can i flash it with my phone ??
Adb otg app??
I don't know, I can't help you with that.
aricooperdavis said:
Interesting, that sounds like you've got an outdated version of fastbook. What does fastboot --version give you?
Click to expand...
Click to collapse
Fastboot version
That's not an official version of fastboot, so it looks like it's missing the command you need. Download the proper Android SDK tools from Android (the same as the original link) and replace your "Minimal" version with it.
aricooperdavis said:
That's not an official version of fastboot, so it looks like it's missing the command you need. Download the proper Android SDK tools from Android (the same as the original link) and replace your "Minimal" version with it.
Click to expand...
Click to collapse
After many tries i found that the command given is wrong
fastboot flash vbmeta --disable-verity --dsable-verification vbmeta.img
This is given
It will be
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
I is Missing Now i have flashed vb meta and problem is solved with the fastboot version i have
By the way thanks