Develop Bugs

[Guide] Unlock/Root/Update/Relock for BQ Aquaris X2 pro (zangyapro)

Introduction
I'm writing this thread to summarize useful information about the BQ Aquaris X2 pro such as:
preliminary actions (adb and fastboot configuration)
unlocking the bootloader
flash a factory image
root the device (currently without TWRP)
updating the device without losing root
relocking the bootloader
I own this phone since July 2018. I started writing my notes in August 2018 in the form of a Google document (link here). I shared this document with some telegram groups and some people I know.
Now I that I think it can be more useful to summarize all my notes here on XDA so that all interested people can access it.
DISCLAIMER:
By attempting any of the processes listed in this thread you accept full responsibility for your actions. I have no responsibility about your actions.​
1) Preliminary actions
1.1) Developer options, USB debugging and Unlock OEM
The first thing you need to do is to enable Developer options, USB debugging and Unlock OEM. Hence:
enable “Developer options” by hitting 7 times on the build number (Got to settings --> about phone)
enter the new menu “Developer options” and,
enable “USB debugging”
enable “Unlock OEM”
1.2) Download and configure abd and fastboot
All steps listed in this guide will require the use of Google Platform tools. I suggest the use of the one provided by Google here: https://developer.android.com/studio/releases/platform-tools.
Download the one for your operating system:
View attachment 4655394
Be sure that your terminal can access adb and fastboot from every position by configuring the PATH. I'm use to configure the PATH on the fly when I need it. As I said before, I work on Linux/macOS where you can set the PATH by:
opening a terminal and running:
Code:
export PATH=$PATH:path_to_platform_tools
2) Unlock the bootloader
Unlocking the booloader will wipe your phone. So backup your data first.
The good news here is that this phone can be handled like a Nexus/Pixel phone. Therefore, the procedure to unlock the bootloader is straightforward:
do all stuff at point 1.1 and 1.2
open a terminal
plug your phone to the PC
reboot into the bootloader
Code:
adb reboot bootloader
run the code:
Code:
fastboot flashing unlock
now you have to wait until your phone reboots. It takes a while, don't panic!!! When the phone is on the initial screen turn it off and reboot into the bottloader again by holing 'power + volume down'.
run the code:
Code:
fastboot flashing unlock_critical
it's done. Your bootloader is completely unlocked. Now, you only have to wait again for the reboot.
3) Flash a factory image
As you probably know, BQ releases a factory image at each update at this link factory images. Factory images are very useful to perform a very clean install. Are you experiencing some issues with your phone and none of the trick you tried solved it? If it is a software issue a clean flash with a factory image will likely remove the issue.
Keep in mind that by flashing a factory image you will wipe also the userdata partition. So backup your data first. Now let's see how to flash the factory image:
you need an unlocked bootloader (see previous sections)
download the factory image from this link
unzip the archive
open a terminal at this folder
be sure to have abd and fastboot properly configured (see previous sections)
run the script to flash all (*):
Code:
./sdm660_fastboot_all_images.sh
wait the end of the process. The phone will reboot.
(*) on Windows you have to deal with the file sdm660_fastboot_all_images.bat. I suppose it's similar but I've never done it on Windows.
4) Obtain ROOT privileges
Nowadays, the most common tool to obtain root privileges is Magisk. Many people here know very well what Magisk is and how to install it with TWRP. However, TWRP is not yet ready for BQ Aquaris X2 pro, hence, we must follow the procedure for installing it without the custom recovery.
When I wrote the document in August I find very informative this guide by @nathanchance. It's for the pixel 2XL but, as I told you before, it works perfectly also for the BQ Aquaris X2 pro (zangyapro). So here I summarize what @nathanchance already posted. All credits must go to him.
Here you have the steps:
Download the Magisk zip from the official thread and install the manager from the zip.
Grab a boot image to patch (either the one from the latest factory image or a custom kernel one) and push it to your device:
Code:
adb push <path_to_file> /sdcard/Download
Open Magisk Manager and click the Install button.
Click "Install" at the first prompt then choose "Patch Boot Image File". A file manager will pop up.
Select the boot image you want to patch and let Magisk Manager patch it.
Pull it off your device:
Code:
adb pull /sdcard/MagiskManager/patched_boot.img
Reboot into the bootloader:
Code:
adb reboot bootloader
Flash the boot image and reboot.
Code:
fastboot flash boot patched_boot.img
fastboot reboot
Open Magisk Manager and you should be rooted!
Please note that it exists also a specific thread where the author also provides the patched boot.img files for download. Hence, you can start from point 6 without patching the boot.img by yourself. Take care of selecting the right one. Here you have the thread link.
5) Update the ROM without loosing root
To the best of my knowledge, the only way to update keeping root is by using the factory images provided by BQ.
Download the factory image of the latest firmware (link)
Extract the file zip and upload the file boot.img on your phone
Code:
adb push <path_to_file> /sdcard/Download
Open Magisk Manager and click the Install button.
Click "Install" at the first prompt and then choose "Patch Boot Image File". A file manager will pop up.
Select the boot image you want to patch and let Magisk Manager patch it.
Pull it off your device:
Code:
adb pull /sdcard/MagiskManager/patched_boot.img
Place the file patched_boot.img in the folder of the BQ firmware unzipped at point 2
Make a copy of the file sdm660_fastboot_all_images (.sh in Mac/Liux and .bat on Windows).
Rename the file, I called it sdm660_fastboot_upgrade.sh
Change the following lines (this will preserve root privileges on your phone):
Code:
fastboot flash boot_a boot.img # <-- delete this line
fastboot flash boot_a patched_boot.img # <-- add this line
Delete the following line (this will prevent your data to be wiped):
Code:
fastboot flash userdata userdata.img # <-- delete this line
Run from your terminal
Code:
./sdm660_fastboot_upgrade.sh (or bat)
I think that one can also update using the OTA. This will make you lose the root privileges and therefore, you will have to repeat the procedure at section 4. I've never tested this so, if you decide to do it, you are on your own.
6) Relock the Bootloader
By relocking the bootloader you will lose all your data, hence, backup them first.
To relock the bootloader you only need the following commands:
Code:
fastboot flashing lock_critical
fastboot flashing lock
Each command will wipe your data and will reboot the phone. Be patient waiting for the reboot and do not panic.

Reserved.
(work in progress)

First: Thanks for this really nice and comprehensive thread!
I have an important addition to point:
3. Open Magisk Manager and click the Install button.
Click to expand...
Click to collapse
Install Button will only appear if the phone has internet connection (Wifi or Mobile Data)
with this I can patch the boot image successfully
But unfortunately I can not run the "sdm660_fastboot_upgrade.sh.bat" it does not recognize my device.
When checking the commands in the batch I found that my device is acting really strange, sometimes giving different errors for the same command like:
Code:
C:\Android\X2proRoot\1.7.1_WithRoot>fastboot set_active _a
error: Device does not support slots.
C:\Android\X2proRoot\1.7.1_WithRoot>fastboot set_active _a
Setting current slot to 'a'...
FAILED (remote: Invalid Slot)
finished. total time: 0.004s
C:\Android\X2proRoot\1.7.1_WithRoot>fastboot set_active _a
error: Device does not support slots.
also strange:
Code:
C:\Android\X2proRoot\1.7.1_WithRoot>fastboot flash boot patched_boot.img
target didn't report max-download-size
sending 'boot' (50749 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.004s
Probably some windows crap not working or an incompatibility of the installed platform tools / drivers and the ones from BQ...

raudidroid said:
First: Thanks for this really nice and comprehensive thread!
I have an important addition to point:
Install Button will only appear if the phone has internet connection (Wifi or Mobile Data)
Click to expand...
Click to collapse
Thanks. I was not aware of this. And now I can't check this on my device because I started using GPay and I prefer to stay with no root and locked bootloader.
Maybe I will play again with the bootloader when TWRP for this device will be released. If it will

got it running!
raudidroid said:
Probably some windows crap not working or an incompatibility of the installed platform tools / drivers and the ones from BQ...
Click to expand...
Click to collapse
Probably it was just that. I Installed Ubuntu 16.04 LTS in a Vmware machine and followed the tutorial (important note here: do everything in a Terminal running under root).
Short moments of panic due to boot-loop included (I flashed a defective boot image [vmware drag and drop files obviously did not copy the whole file] )
for everybody who ends in a bootloop: just keep calm, switch off phone (>10s press power button) an very quickly when it is of press power and volume down to get into flashmode again (I had to try several times)

Hey @raudidroid, when I answered to you the first time I did not read all the message or you edited it later. Only now I'm reading the issues you faced.
On Windows, what shell did you use? PowerShell?
I'm not sure about this because I banned Windows from my personal and working life several years ago, however, recently I read some posts of people having issues with PowerShell. If this is also your case next time try to use classic cmd.
Probably it was just that. I Installed Ubuntu 16.04 LTS in a Vmware machine and followed the tutorial (important note here: do everything in a Terminal running under root).
Click to expand...
Click to collapse
Regarding this the above quote, I'm quite sure that you do not need to be super user to apply any of the procedure listed in the guide.
for everybody who ends in a bootloop: just keep calm, switch off phone (>10s press power button) an very quickly when it is of press power and volume down to get into flashmode again (I had to try several times)
Click to expand...
Click to collapse
Since your are suggesting "... very quickly when it is of press power and volume down ... " I can imagine that you did this procedure while your phone was connected to the laptop/PC with the USB cable. In this condition, when you force the shutdown by pressing power for 10s, the phone reboots automatically. So my suggestion is to unplug it first, in this way the phone turn off without rebooting and you can comfortably enter in the bootloader with no hurry.

luk.giak said:
On Windows, what shell did you use? PowerShell?
I'm not sure about this because I banned Windows from my personal and working life several years ago, however, recently I read some posts of people having issues with PowerShell. If this is also your case next time try to use classic cmd.
Click to expand...
Click to collapse
I was using CMD / Command Prompt on win10, but maybe I have to many ADBs/Drivers/... installed. got a really weird behavior...
Regarding this the above quote, I'm quite sure that you do not need to be super user to apply any of the procedure listed in the guide.
Click to expand...
Click to collapse
without root it wouldn't work, i got "no permissions (user in plugdev group; are your udev rules wrong?)"
with root everything ran smoothly
Since your are suggesting "... very quickly when it is of press power and volume down ... " I can imagine that you did this procedure while your phone was connected to the laptop/PC with the USB cable. In this condition, when you force the shutdown by pressing power for 10s, the phone reboots automatically. So my suggestion is to unplug it first, in this way the phone turn off without rebooting and you can comfortably enter in the bootloader with no hurry.
Click to expand...
Click to collapse
Oh! Yep, that sounds like it would have been the better way to do it
Thanks for your post and your answers.
BTW: half-OT do you know any way to get netflix running after the rooting?

For your information.
I follow part 5 and updated my firmware to version 1.7.3 successfully. Thanks for this guide.

AndroidenKalle said:
For your information.
I follow part 5 and updated my firmware to version 1.7.3 successfully. Thanks for this guide.
Click to expand...
Click to collapse
Your welcome!

For your information.
I follow part 5 and updated my firmware to version 2.0.0 (Android Pie 9) successfully.

AndroidenKalle said:
For your information.
I follow part 5 and updated my firmware to version 2.0.0 (Android Pie 9) successfully.
Click to expand...
Click to collapse
Thanks for sharing.
I'm on PIE as well. Today I flashed the factory image to make a clean install.

Hello, maybe someone can be of help to my situation.
I had my phone rooted in the last firmware version (1.7.3), and I was getting notifications to update to Android 9 pie for some time, however I was waiting to have some time to spare and first backup my files and do a factory update to pie and then root.
However, last nigh without warning my phone just rebooted and updated to pie, (firmware ver 2.0.2) and I lost root obviously. However, all my files, apps, etc were intact.
So today I decided to root my phone again. I download the firmware zip from BQ's site and then used Magisk (ver. 19.2) to patch the boot.img.
I rebooted to fastboot and did "sudo fastboot flash magisk_patched.img", and rebooted but the phone got stuck in the logo screen.
Then I used method 5 of this tutorial and ran ./sdm660_fastboot_upgrade.sh (with the mentioned modifications), however it bootlooped again. Then I flashed the original boot img and my phone booted just fine again, I tried to patch the img again, did again step 4 and it bootlooped again.
Any clues on how to successfully root ? Never had any problems updating and rooting from firmware 1.4.0 to 1.7.3.
Thank you for your time

(GUIDE) Unlocking bootloader, Rooting - from start to finish UPDATED.

Hi all,
Have looked around the guides and such on these threads for the Oneplus 8 Pro and haven't found a full comprehensive guide outlining all parts of the bootloader unlocking and root process, so thought I'd put together my experience for anyone found in the same position, this is simply what I did, i'm sure there are other guides out there which offer different methods but I can confirm that this 100% works
NOTE* This guide is intended for all OnePlus 8 devices but the boot image files are for the EU version of the Oneplus 8 Pro on the most current firmware at the time of writing please don't use these files unless you meet the pre-requisites to the guide stated below
It is possible to extract the boot IMG from any firmware using the payload extractor tool which can be found online, then change the commands to reflect the files you obtain, for the sake of clarity I'll be using 10.5.12
Hope this helps.
Pre-requisites
A European variant of the Oneplus 8 Pro: IN2023
Running the following firmware: 10.5.12 IN11BA
ADB Access to your phone
A decent amount of charge, eg: 80%
A Windows 10 based computer
The cable that came with your phone
Obtaining ADB access to your device using your computer
1. Connect your phone to your computer using the cable that you charge it with
2. Allow it to see the device, if it automatically installs the driver (which it should) then you're good to go, if not then install the driver you can obtain from the drive which will appear on screen within "This PC" (i won't detail this as it's pretty self explanatory)
3. On your phone Open settings and navigate to "About phone"
4. Click "Build number" several times (5) then enter your PIN, this will enable "Developer Options"
5. Back out, then click "System"
6. Scroll down to "Developer Options" and open it.
7. Scroll down to "USB Debugging" and turn it on (if at this point you are prompted with a dialogue box asking for authorization then please check the box and allow it, also turn on) also turn on "OEM Unlocking" in the same section and agree to any prompts.
8. On your computer Download this folder https://drive.google.com/drive/folders/1S-yNzdvOvdZzPuxhYuEuwnelzfdEd0K2?usp=sharing
This is adb and fastboot so you can talk to your phone via your PC.
9. Move it to the root of the C: drive, so it looks like this in the filepath
C:\Android
10. Navigate to the folder and perform the following:
i) Hold shift and right click an empty space within the folder
ii) Click "Open Powershell Window here" or "Open a Command prompt Windows here"
iii) A black or blue window will appear with some text
11. In the window type the following command
adb devices
press enter
If you are now prompted with an authorization dialogue on your phone, please check the box and allow it.
You should see a readout of a device followed by a code, you now have ADB access and can continue.
Unlocking the bootloader
NOTE* THIS WILL WIPE YOUR ENTIRE DEVICE, IT'S UP TO YOU IF YOU WANT TO BACK UP OR NOT. I WOULD RECOMMEND DOING SO
1. Connect your phone to your computer
2. On your computer Navigate to C:\Android
i) Hold shift and right click an empty space within the folder
ii) Click "Open Powershell Window here" or "Open a Command prompt Windows here"
iii) A black or blue window will appear with some text
3. Type the following command into the window
adb reboot bootloader
press enter
On your phone
i) Your phone will reboot and show you a screen with 3 language choices, Choose "English" then "Advanced" and finally "Reboot to fastboot" and "Reboot to fastboot"
ii) You'll see a screen appear on your phone with some text, at the top you'll see the word "START" in green, you're now in Fastboot
4. On your computer Type the following command into the window
fastboot oem unlock
press enter
NOTE* THIS IS THE PART THAT WIPES YOUR PHONE IF YOU WANT TO BACK OUT, NOW IS THE TIME TO DO SO, ONCE STARTED DO NOT DISCONNECT THE CABLE OR FORCE A SHUTDOWN FOR ANY REASON THIS COULD RESULT IN A BRICKED DEVICE
5. Your phone will warn you and go through a set of screens, please agree and move forward until the device reboots
You have just unlocked the bootloader to your phone
Once the device has booted, set it up again and then follow the steps to unlock "developer options" and "USB Debugging" once more.
Installing Magisk Manager and obtaining Root access
Before you begin, please follow these two steps to install the magisk manager
Magisk manager
i) On your computer download this folder https://drive.google.com/drive/folders/1VH_2Ql6L5580rVYvRZ5l8t7cX2XENEAG?usp=sharing and move the file inside to your internal storage on your phone, the file is called "MagiskManager-v7.5.1.apk"
ii) On your phone using a file manager navigate to where you moved the file and open it, this will install the Magisk Manager used to manage root access, open the Magisk Manager once, you'll see it does not have root access.
Rooting
1. On your computer Go here https://drive.google.com/drive/folders/189DlZH1NSMrgVF996S7y3q5_IG9RAFIr?usp=sharing and download the folder
2. Copy the file inside the folder which is called "magisk_patched.img" to C:\Android
3. Navigate to C:\Android
i) Hold shift and right click an empty space within the folder
ii) Click "Open Powershell Window here" or "Open a Command prompt Windows here"
iii) A black or blue window will appear with some text
4. Type the following into the window
adb reboot fastboot
press enter
On your phone
i) Your phone will reboot and show you a screen with 3 language choices, Choose "English" then "Advanced" and finally "Reboot to fastboot" and "Reboot to fastboot"
ii) You'll see a screen appear on your phone with some text, at the top you'll see the word "START" in green, you're now in Fastboot
On your computer
5. There are two options for rooting, the first is to boot it first, this is safer as it is not permanent and a reboot will rejoice the booted image, the second is to flash it, this is a one step option but if the image isn't right then you could end up in a bootloop so id recommend the first.
Type the following into the window
To boot:
Fastboot boot magisk_patched.img
(Your phone will reboot automatically)
To flash:
fastboot flash boot_a magisk_patched.img
press enter
then
fastboot flash boot_b magisk_patched.img
press enter
then
NOTE* THIS WILL FLASH THE PATCHED BOOT IMG TO BOTH SLOTS, THIS IS WHAT I DID, I HAVEN'T EXPLORED IF ONE SLOT IS ADEQUATE OR NOT, IT MAY BE POSSIBLE TO ONLY FLASH THE BOOT.IMG TO ONE SLOT BUT AS I HAVEN'T I CAN'T ADVISE.
6.. Once complete, type in the following command
fastboot reboot
press enter, your device will reboot
7. On your phone open up "Magisk Manager" you should now have two green ticks signifying that you now have root access.
NOTE* If you booted the image then simply click the top install option then go to install directly, this will make root permanent.
That's it, you've now unlocked your bootloader and rooted using the most current boot img at the time of writing.
------------------------------------------------------------------------------------------------------------------------------------
Please don't quote the entire thread!!!!!
If i've missed anything out or anyone notices a mistake please let me know and i'll amend accordingly.
Alternate second guide here on post #55 thanks to @flushell
https://forum.xda-developers.com/showpost.php?p=83534273&postcount=55

dladz said:
Hi all,
Have looked around the guides and such on these threads for the Oneplus 8 Pro and haven't found a full comprehensive guide outlining all parts of the root process, so thought I'd put together my experience for anyone found in the same position, this is simply what I did, i'm sure there are other guides out there which offer different methods.
NOTE* This guide is intended for the EU version of the Oneplus 8 Pro on the most current firmware at the time of writing please don't use these files unless you meet the pre-requisites to the guide stated below
Hope this helps..
Click to expand...
Click to collapse
If you dont have 10.5.12 installed in both slots then I dont see any reason to flash patched image to A and B..I just fastboot flash boot magisk_patched.img and that worked fine. Ive been rooted for quite awhile though

pyry666 said:
If you dont have 10.5.12 installed in both slots then I dont see any reason to flash patched image to A and B..I just fastboot flash boot magisk_patched.img and that worked fine. Ive been rooted for quite awhile though
Click to expand...
Click to collapse
Ok so by not specifying a slot you are flashing to both afaik
I know that the way i've written this it works perfectly, if another slot is required then it can be used when the time comes.

dladz said:
Ok so by not specifying a slot you are flashing to both.
I know that the way i've written this it works perfectly, if another slot is required then it can be used when the time comes.
Also please don't quote the entire guide it makes reading threads awful, edit your post please.
Click to expand...
Click to collapse
Sorry about that, post edited.Afaik if you dont specify slot it flashes it to current slot being used. Or you could just boot twrp (not install) and flash magisk from there. That also works. Ive tried that too

pyry666 said:
Sorry about that, post edited.Afaik if you dont specify slot it flashes it to current slot being used. Or you could just boot twrp (not install) and flash magisk from there. That also works. Ive tried that too
Click to expand...
Click to collapse
Ah ok nice, and no worries, thanks for editing.
Im aware of TWRP but for the purpose of just getting rooted this has worked for me and there wasn't a fool proof place where all the guides were so i wanted to make sure everything to get rooted was in one place and was easy to understand.
I'll edit it for TWRP and maybe some other bits once i've got to use them, but for now, this is enough to get people onto Magisk ROM's at least.
Have read different things about the slots, when i didn't specify the slot, it didn't work, so i had to specify, but had no idea which slot to choose so i chose both, it then worked so didn't want to break it i kept it, hasn't broken anything.
How are you identifying which slot is actually in use?

dladz said:
Ah ok nice, and no worries, thanks for editing.
Im aware of TWRP but for the purpose of just getting rooted this has worked for me and there wasn't a fool proof place where all the guides were so i wanted to make sure everything to get rooted was in one place and was easy to understand.
I'll edit it for TWRP and maybe some other bits once i've got to use them, but for now, this is enough to get people onto Magisk ROM's at least.
Have read different things about the slots, when i didn't specify the slot, it didn't work, so i had to specify, but had no idea which slot to choose so i chose both, it then worked so didn't want to break it i kept it, hasn't broken anything.
How are you identifying which slot is actually in use?
Click to expand...
Click to collapse
In twrp it reads clearly. And there is a fastboot command to check witch slot you are currently on and you can change that also in fastboot but I have to admit that I cant remember those commands from the top of my head right now

pyry666 said:
In twrp it reads clearly. And there is a fastboot command to check witch slot you are currently on and you can change that also in fastboot but I have to admit that I cant remember those commands from the top of my head right now
Click to expand...
Click to collapse
Nah it's cool, perhaps there's an app which does the same. Seeing as this is a pretty integral part of the system I would imagine that there would be.
Will have a look, appreciate you helping. Couldn't find much on the subject myself. Will edit the guide to reflect it.
I haven't actually installed twrp. Not yet anyway

dladz said:
Nah it's cool, perhaps there's an app which does the same. Seeing as this is a pretty integral part of the system I would imagine that there would be.
Will have a look, appreciate you helping. Couldn't find much on the subject myself. Will edit the guide to reflect it.
I haven't actually installed twrp. Not yet anyway
Click to expand...
Click to collapse
Me neither, just booted it couple times. Btw its safer to patch boot.img yourself rather than use pre patched image. Just because then you now what magisk version was used to patch it in first place. Wrong magisk version can cause issues

pyry666 said:
Me neither, just booted it couple times. Btw its safer to patch boot.img yourself rather than use pre patched image. Just because then you now what magisk version was used to patch it in first place. Wrong magisk version can cause issues
Click to expand...
Click to collapse
Or just follow the above guide if you meet the requirements
Command for swapping slot is
fastboot --set-active=a
Or b

Thanks for the guide, but I'm using IN2020 and I'm on 10.5.13.IN11AA.
anyone can point me to the correct topic or guide to root/ unlock bootloader etc?

N'ash said:
Thanks for the guide, but I'm using IN2020 and I'm on 10.5.13.IN11AA.
anyone can point me to the correct topic or guide to root/ unlock bootloader etc?
Click to expand...
Click to collapse
Bootloader unlock works same no matter what model you are using. You can just boot twrp and flash magisk from there

N'ash said:
Thanks for the guide, but I'm using IN2020 and I'm on 10.5.13.IN11AA.
anyone can point me to the correct topic or guide to root/ unlock bootloader etc?
Click to expand...
Click to collapse
Guides the same but the files would not be.
You can use payload dumper to extract the boot.img, then patch using magisk, then extract and follow the guide.
This guide was made for the EU version of the phone, i couldn't comment further on your device and i would not recommend continuing with the files i've uploaded if you don't meet the pre-requisites.

dladz said:
Guides the same but the files would not be.
You can use payload dumper to extract the boot.img, then patch using magisk, then extract and follow the guide.
This guide was made for the EU version of the phone, i couldn't comment further on your device and i would not recommend continuing with the files i've uploaded if you don't meet the pre-requisites.
Click to expand...
Click to collapse
So I have to download the official rom for IN2020 10.5.13 then extract the boot.img, patch with magisk and flash the patched boot.img right?

N'ash said:
So I have to download the official rom for IN2020 10.5.13 then extract the boot.img, patch with magisk and flash the patched boot.img right?
Click to expand...
Click to collapse
So in order.
1 Download the full ROM for your device and region.
2 Open it in on a computer and extract the bin file called payload, it'll be about 2.4GB.
3 Then copy it to the payload dumper input folder and run the exe
4 You'll get the boot image as well as some other files, copy the boot image to your phone and patch it using magisk.
5 Then pull the output magisk patched.img to your adb folder and flash to slot A or B or both. I did both

N'ash said:
So I have to download the official rom for IN2020 10.5.13 then extract the boot.img, patch with magisk and flash the patched boot.img right?
Click to expand...
Click to collapse
So how did it go?? All good?

dladz said:
So how did it go?? All good?
Click to expand...
Click to collapse
Yeah I did as instructed and everything is good. I wish I could get rid of the bootscreen security error message though!

I was not thinking and did this on 10.5.7 global and now I'm in a boot loop; EDIT: Just restored 10.5.5 with unbrick tool and used the downgrade 10.5.7 global from here https://forum.xda-developers.com/oneplus-8-pro/how-to/oneplus-8-pro-repo-oxygen-os-builds-t4084315 --then, I made my own patched magisk from the boot.img I extracted. Here is that 10.5.7 magisk patched img for global if anyone needs: http://www.mediafire.com/file/xcrm53shf5km8jz/magisk_patched.img/file

A.Priori said:
I was not thinking and did this on 10.5.7 global and now I'm in a boot loop; EDIT: Just restored 10.5.5 with unbrick tool and used the downgrade 10.5.7 global from here https://forum.xda-developers.com/oneplus-8-pro/how-to/oneplus-8-pro-repo-oxygen-os-builds-t4084315 --then, I made my own patched magisk from the boot.img I extracted. Here is that 10.5.7 magisk patched img for global if anyone needs: http://www.mediafire.com/file/xcrm53shf5km8jz/magisk_patched.img/file
Click to expand...
Click to collapse
Well done, always good to come back from the dead

N'ash said:
Yeah I did as instructed and everything is good. I wish I could get rid of the bootscreen security error message though!
Click to expand...
Click to collapse
Yea that annoys me too.
There will be a way I'd imagine, but you wouldn't want to get that script wrong..
Might look into getting that gone, HTC had this too as do a few devices.
Possible a precious guide for an older device may work but using it to test would be a risk..

After doing this, is it still possible to install official OS builds from OnePlus whenever a new build comes out? Either via a zip or OTA?
For instance when 10.5.13.IN11BA comes out or whatever?

[Guide] Root Pixel 4a (5G) with Magisk + Unlock Bootloader + Pass SafetyNet + More

[Guide] Root Pixel 4a (5G) with Magisk + Unlock Bootloader + Pass SafetyNet + More
Android Security Bulletin—June 2023
Pixel Update Bulletin—June 2023​
Introduction
This Guide is for Pixel 4a 5(G) owners that want to Root their phone, and enjoy the benefits of rooting it. The Guide is divided into three parts: Information, Instructions, and Other.
~ ~ ~ Part I - INFORMATION ~ ~ ~
Disclaimer
I assume no responsibility for the malfunctioning/bricking of your phone.
If you choose to use a Custom Kernels, Custom ROM, etc. You should read the Installation Instructions in their thread before using this guide or attempting to install them. Additionally, the order of listed items i.e., Custom Kernels, Custom ROMS, etc. Does not indicate my preference for them. It is your responsibility to do the research before selecting them.
Prerequisites
A Pixel 4a 5(G) phone with an unlocked bootloader.
The latest Android Factory or OTA Image: "bramble" for Pixel 4a 5(G)
Factory Image
13.0.0 (TQ3A.230605.011, Jun 2023)
Which one should I use?
OTA Image
13.0.0 (TQ3A.230605.011, Jun 2023)
Which one should I use?
A Computer with the latest working SDK Platform-tools 33.0.3 installed.
Important Notes:
a. Before installing SDK Platform-tools, check for older versions of fastboot on your computer: Open a Command prompt and type fastboot --version at the prompt. If a adb/fastboot is found delete the folder containing them. Also, check the path environment for paths to them and remove it.​
b. Update Platform Tools, regularly, for optimal performance.​
c. Need Google's USB Drivers for your Pixel Phone?​
NEW
Both Slots Bootable
@badabing2003 has found a way to Have both slots bootable.
He has automated the procedure and added it to PixelFlasher.
@Lughnasadh tested the Both Slots Bootable procedure on his Google Pixel 7 Pro and Google Pixel 6 Pro phones: It works!
Android 14 Beta are up.
Builds are only available for the following Pixel devices:
Google Pixel 4a5(G)
Google Pixel 5 and 5a
Google Pixel 6 and 6 Pro
Google Pixel 6a
Google Pixel 7 and 7 Pro
* * * 64-bit-only system images * * *
Google Pixel 4a (5G)
Google Pixel 5
Google Pixel 6
Google Pixel 6 Pro
Android 14 GSI binaries and release
Pixel 4a5(G)
Pixel 5 and 5a
Pixel 6 and 6 Pro
Pixel 6a Pro
Pixel 7 and 7 Pro
Update(s)
Factory/OTA Images - 13 June
Android 14 DP
Factory images and OTA images
Android 14 GSI binaries and release
Magisk Alpha - app-release_709f25f6-26101.apk 12 Apr
Magisk Beta - Magisk v26.1.apk 11 Apr
Magisk Canary - app-release_a8c4a33e-26103.apk 23 Jun
Magisk Cygisk - Click Pages 5 for installation Instructions.
Magisk Delta -
app-release
Magisk Stable - Magisk v26.1.apk 11 Apr
SafetyNet - Displax's SafetyNet Fix, v2.4.0-MOD_1.3 17Jun
SDK Platform-tools 33.0.3 Aug 2022
Custom Kernels
a. Google Pixel 4a5(G) ROMs, Kernels, Recoveries, & Other​b. ElementalX Kernel Manager​
My Other Guides
Pixel 7 Pro
Pixel 6
Pixel 5
Pixel 4 XL
Pixel 3 XL
Pixel 1 XL
Credits/Thanks/Recognitions
@creezalird- Flash Android 12 factory image.
Those I may have, inadvertently, forgotten.
~ ~ ~ Part II - INSTRUCTIONS ~ ~ ~
(The Instructions listed below are not steps, they are individual sets of instructions.)
Unlock Bootloader/Return Phone to Stock/Lock Bootloader
Unlock Bootloader
Notes:
This will erase all user data from the device!
Backup your data
Activate Developer Options: Tap Settings > About Phone > Tap Build Number 7 times or until you see you are a Developer. Tap back > System > Advanced > Developer Options. Enable OEM Unlock and, USB Debugging.
Boot fastboot mode
Connect the phone to the Computer with USB cord.
Open a Command Prompt on your computer and type fastboot flashing unlock and press enter.
You should see a request for confirmation on your phone, use the volume keys to scroll and the power key to select.
Allow the process to complete and then type fastboot reboot at the Command Prompt and press enter.
When your phone reboots disconnect your usb cable.
Notes:
After unlocking your bootloader, you'll see a warning: The bootloader is unlocked and... You will see this warning until, you relock the bootloader.
Do not relock your bootloader until you have returned the device to Stock.
Return Phone to Stock
Backup your data/Internal storage
Use the Android flash tool:
select Wipe => Force Flash Partitions => Lock Bootloader.
Lock Bootloader
If your phone is not 100 percent stock do Return Phone to Stock. If you don't you may brick your phone.
This will erase all user data from the device!
Boot fastboot mode
Open a Command Prompt in the SDK Platform- tools folder, and type this at the Prompt: fastboot flashing lock
You should see a request for confirmation on your phone, use the volume keys to scroll and the power key to select.
Allow the process to complete, then type this at the Command Prompt: fastboot reboot
Enable Developer Options: Settings > About phone > Tap Build number 7 times or until you see 'you are a developer'.
Tap Back > Developer options and toggle OEM Unlock off.
Manually Install/Update Factory Image keep data or wipe data
Important Note(s):
If you haven't updated your phones Factory image in awhile. It is not necessary to flash all the missed images in succession. Flash the latest Factory image.
If you are uncomfortable manually flashing the factory image. Try PixelFlasher by badabing2003.
If your phone was previously rooted, open Magisk manager and disable all Magisk modules. If you hid the Magisk manager app the default name for the hidden Magisk app is settings.
If you want to Upgrade to Android 13 or update the Factory Image without wiping your phone: Do Flash the Factory Image Keep Data (below).
Always verify you have the latest working version of SDK Platform-Tools installed on your computer before installing the Factory Image: Pixel 4a 5(G) - bramble.
If you get an error: while flashing, try one of these options:
Change the USB port to a non charging USB port.
Change the USB cord.
Change Computers.
If you phone bootloops
Press the Power button until the phone turns off.
Press the Power and Volume Down to boot the bootloader.
Open a Command Prompt in the SDK-Platform-tools folder or the folder that has adb.exe in it, and type adb wait-for-device shell magisk --remove-modules
Then type: fastboot Reboot
Backup your data
Download the latest Factory Image: Pixel 4a 5(G) - bramble to your Computer.
Go to Part II - INSTRUCTIONS => 4. Extract Files from the FactoryImage/Flash boot.img and extract the flash-all.bat file.
Flash Factory Image Keep Data
Upgrading Android 13
* E D I T - flash-all.bat file *
Flash to current/Active Slot.
@Echo off
PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot flash bootloader bootloader-bramble-a9-9.9-9999999.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-bramble-a9999a-999999-999999-a-9999999.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot update image-bramble-tp1a.999999.999.zip
Note:The -w is removed to Keep Data.
echo Press any key to exit...
pause >nul
exit
Note: It is a good idea to flash the Google factory image to both slots (A & B) when Upgrading to a new Android Version.
See Flash Other Slot bat file... below, to flash to the other/inactive slot.
* * * * E N D - Edit * * * *
Updating Android 13
Flash to Other/Inactive Slot.
Note: See Flash Other Slot bat file... below.
* * * * * E N D * * * * *
Flash Other Slot bat file - Save as flash-other.bat
Note: To run this file type flash-other at the Command Prompt.
ECHO OFF
PATH=%PATH%;"%SYSTEMROOT%\System32"
echo This is the slot you are currently on.
fastboot getvar current-slot
echo Press any key to continue...
pause >nul
fastboot --set-active=other
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
echo This is the slot you switched to.
fastboot getvar current-slot
echo Press any key to continue...
pause >nul
flash-all
exit
* * E N D - Creating File * *
After, you have edited the flash-all.bat file. Copy/Move these files to the [U[Platform-tools[/U] folder:
bootloader-bramble-....img
flash-all.bat
image-bramble-....zip
radio-bramble-....img
On your phone: Boot the bootloader (Power off the phone => Press the Power and Down buttons until you see Start)
Connect your phone to the computer.
Open a Command Prompt on your computer in the Platform-tools folder and type: flash-all at the Command Prompt and press enter.
The phone will reboot when flashing is complete.
Go-to Part II - INSTRUCTIONS => 5. Root/Reroot with Magisk and Pass SafetyNet, • Patching the boot.img - to root/reroot.
Flash Factory Image Wipe Data
This will wipe your phone's Data/Internal Storage.
Do not edit the flash-all.bat file.
If you need to disable Verity and Verification: See Disabling Verity and Verification below.
Disabling Verity and Verification
* E D I T - flash-all.bat file *
@Echo off
PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot --set-active=other
fastboot reboot-bootloader
fastboot flash bootloader bootloader-bramble-aaaaaa-9.9-9999999.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-bramble-a99999-999999-999999-a-9999999.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot - w update --disable-verity --disable-verification image-bramble-AA1A.999999.999.A9.zip
echo Press any key to exit...
pause >nul
exit
Notes:
The first time you Disable Verity and Verification it will wipe your Data/Internal Storage.
When doing Subsequent updates and disabling Verity and Verification, the -w flag can be removed to Keep Data.
Once you start Disabling Verity and Verification you should continue doing it. If you skip disabling one time. The next time you Disable Verity and Verification it will wipe your phone.
Some kernels require Disabling verity and verification
To flash both slots (A & B partitions) see Flash Other Slot bat file... above.
* * * * E N D - Edit * * * *
Open the folder you extracted the Factory Image to and Copy/Move these files to the Platform-tools folder:
bootloader-bramble-....img
flash-all.bat
image-bramble-....zip
radio-bramble-....img
On your phone: Boot the bootloader (Power off the phone => Press the Power and Down buttons until you see Start)
Connect your phone to the computer.
Open a Command Prompt on your computer in the Platform-tools folder and type: flash-all at the Command Prompt and press enter.
The phone will reboot when flashing is complete.
Setup phone
Enable Developer Mode and USB Debugging
Setup => About phone => Tap Build number 7 times or untill you see you are a 'Developer'.
Setup => System => Developer options => Enable Developer options => enable USB Debugging
Go-to Part II - INSTRUCTIONS => 5. Root/Reroot with Magisk and Pass SafetyNet, • Patching the boot.img - to root/reroot.
(NEW) Make Both Slots Bootable: Manually, Flash the OTA Image to Both Slots - One bootable and rooted, the other slot bootable without root.
Before you start
Backup your data
Make sure that there is no pending OTA update, by going to Settings > About phone > System updates, which should say Your system is up to date.
Download the latest Factory and OTA image for your device.
Verify the checksum of the Factory and OTA image. The last portion of the filename is the first 8 digits of its SHA-256 checksum; the full SHA-256 checksum is shown next to the download link.
Extract the boot.image from the Factory image:
Extract the Factory Image file that you downloaded (bramble-a9a9a.999999.999-factory-99a9a99a.zip) into a folder.
Open the folder you extracted the Factory image to and extract the Image file (image-bramble-aa9a.999999.999.zip) into a folder. The stock boot.img file should be in this folder.
Patch the boot.img:
Open the Magisk (Alpha/Beta/Canary/Delta/Stable) App
The Update Channel should be set to Alpha/Beta/Canary/Delta/Stable, depending on the version you installed.
Tap Install (next to Magisk)
Tap, Select and Patch a File
Select the boot.img file you extracted from the factory image.
Tap the ✓ (Check Mark)
Tap Let's Go
When you see done, the boot.img has been patched (magisk_patched_xxxxxx.img), and is stored in the download folder.
Reboot
Copy/Move the magisk_patched....img file to your computer's Platform-tools folder or the folder that has fastboot.exe in it:
Sideload the OTA zip file
Boot Recovery mode
With the device powered on and USB debugging enabled, type: adb reboot recovery
If you're unable to use adb to reboot into recovery, you can use the key combination for your device: Press and hold Volume Down button, then press and hold Power button then use the Volume Down/Up button to select the Recovery option from the menu.
The device is now in recovery mode an Android logo with red exclamation mark should be on the screen.
Access the recovery menu:
Hold the Power button and press Volume up button up once. The recovery text menu will appear.
Connect the phone to the PC via USB cable
Enter sideload mode:
Select the Apply update from ADB option from the recovery text menu
(Optional) Verify Computer sees your device:
Type: adb devices and press return.
Your device number should shows up with "sideload" next to it.
Sideload the OTA zip file
Select the Apply update from ADB option from the recovery text menu
Type:
adb sideload bramble-ota-aa9a.999999.999-a99999aa.zip and press enter.
Once sideloading finishes, reboot the phone by choosing Reboot system now option on the The recovery text menu.
Note: This slot is bootable and NOT ROOTED
Sideload the OTA zip file to the other slot and Root it.
Boot Recovery mode
With the device powered on and USB debugging enabled, type: adb reboot recovery
If you're unable to use adb to reboot into recovery, you can use the key combination for your device: Press and hold Volume Down button, then press and hold Power button then use the Volume Down/Up button to select the Recovery option from the menu.
The device is now in recovery mode an Android logo with red exclamation mark should be on the screen.
Access the recovery menu:
Hold the Power button and press Volume up button up once. The recovery text menu will appear.
Connect the phone to the PC via USB cable
Enter sideload mode:
Select the Apply update from ADB option from the recovery text menu
Sideload the OTA zip file
Type: adb sideload bramble-ota-aa9a.999999.999-a99999aa.zip at the prompt and press enter.
Once sideloading finishes, choose Reboot system now option on the The recovery text menu.
Flash Magisk_patched....img to root
On the phone: Boot bootloader/fastboot mode
On the PC:
Open a Command Prompt in the SDK Platform-tools folder.
Type: fastboot flash boot magic_patched....img at the Prompt and press enter.
Type: fastboot reboot at the Prompt and press enter.
Disconnect the phone from the PC.
Note: This slot is bootable and ROOTED.
Done!
Extract Files from Factory Image: flash-all.bat boot/init_boot.img/Flash boot/init_boot.img
Extract Files from Factory Image
Extract flash-all.bat and boot.img file
Download the latest Factory image to your phone.
Extract the Factory Image file (bramble-r2d1a.999999.999-factory-99a9a99a.zip) to a folder. The, stock, flash-all.bat file should be in this folder.
Open the folder you extracted the Factory image to and, extract the Image file (image-bramble-aa9a.999999.999.zip) into the folder. The, stock, boot.img file should be in this folder.
Flash boot/init_boot.img
Flashing the boot/init_boot.img removes root.
Open the folder you extracted the 'image...zip' file to and copy the boot.img file to your computer's platform-tools folder or to the folder that has fastboot.exe in it.
Boot fastboot mode
Connect the phone to the Computer
Open a Command Prompt and type the following command at the prompt:
fastboot flash boot --slot all boot.img
Reboot
Root/Reroot with Magisk and Pass SafetyNet.
Android 13
Upgrade to Android 13: OP, Part II - INSTRUCTIONS, 2. Install/Update Factory Image keep data or wipe data, Keep data
Patching the boot.img - to root/reroot.
If your phone was previously rooted, DO NOT repeat DO NOT install another Magisk Manager app. Do this before you patch the boot/init_boot image:
Open the Magisk Manager app and disable all Magisk modules. If you hid the Magisk manager app the default name for the hidden Magisk app is settings.
If you gave it a different name and you've forgotten the name. Use TB checker to find the name of the hidden Magisk Manager. You can also use TB Checker to check if you have more than one Magisk Manager app installed.
Extract the boot/init_boot.img file from the Factory Image.
Download the latest Factory image to your phone.
Extract the Factory Image file (branble-a9a9a.999999.999-factory-99a9a99a.zip) to a folder.
Open the folder you extracted the Factory image to and extract the Image file (image-bramble-aa9a.999999.999.zip) into the folder. The, stock, boot/init_boot.img file should be in this folder.
Install Magisk Canary - Download app-release.apk
or
Magisk Beta 25.0/Stable 24.3 App
Open Magisk Beta/Canary/Stable App
The Update Channel should be set to Beta/Canary/Stable, depending on the version you Installed.
Tap Install (next to Magisk)
Tap, Select and Patch a File
Select the boot.img file you extracted from the latest factory image.
Tap the ✓ (Check Mark)
Tap Let's Go
When you see done, the boot.img has been patched (magisk_patched_xxxxxx.img), and stored in the download folder.
Reboot
Copy/Move the patched boot.img file to your computer's Platform-tools folder or the folder that has fastboot.exe in it:
Copy it to a USB drive and transfer it to your computer.
Move it to your computer using adb push
Boot fastboot mode
Connect the phone to the Computer with USB cord.
Open a Command Prompt in the folder you copied the patched boot.img to.
Type fastboot flash boot "name of patched boot".img without the quote marks at the Prompt and press enter.
Type fastboot reboot at the Prompt and press enter.
Important, if your phone boot loops try one of the following options:
Flash the 'stock' boot.img to both slots: fastboot flash boot boot.img --slot all
Remove Modules
Press the Power button until the phone turns off.
Press the Power and Volume Down to boot the bootloader.
Open a Command Prompt in the SDK-Platform-tools folder or the folder that has adb.exe in it, and type adb wait-for-device shell magisk --remove-modules
fastboot Reboot.
Important, if the Magisk Manager app has the Superuser and Module buttons greyed out:
Read @badabing2003 post
Pass Safety Net with SafetyNet Fix
Download File(s)
Displax's latest SafetyNet Fix, a "fork" of kdrag0n safetynet-fix.
These are the NEW Magisk Module repositories:
Androidacy Module Manager
Androidacy Module Manager - Releases
Androidacy Download Center
This is the old Magisk Module repository:
https://github.com/Fox2Code/Fox Magisk Module Manager
Install Displax's safetyNet Fix
Open Magisk
Tap Modules icon
Tap Install from storage
Navigate to the Displax's SafetyNet Fix file you downloaded.
Tap the Displax's SafetyNet Fix file.
Tap the check mark (✓ at the bottom) to start the installation.
After it installs tap the Save icon to save the log
Tap Reboot.
Settings for Magisk Canary
Open Magisk App
Tap the Setup icon.
Scroll down to App and set the Update Channel to Canary.
Scroll down to Check Updates and enable it.
Scroll down to Magisk and enable Zygisk.
Enable Denylist
Tap Configure DenyList => Tap 3 Dot Menu => Check ✓ Show system apps => Check ✓ Google Play Store, Google Pay, Google Wallet etc.
(Optional) Scroll down to Superuser and enable Enable Biometric Authentication.
Get Device Certified
Turn Airplane mode on
Open Settings
Tap Apps & notifications
Tap see all...
Tap three dot menu
Tap Show system
Scroll to Google Play Store
Tap Storage and Cache
Tap Clear storage
Note: Repeat the 3 steps above for any app that needs Device Certification i.e., Google Play Services, Google Pay, Google Wallet, etc.
reboot
Turn Airplane mode off
Check Device Certification
Open Google Play Store app
Tap Menu - Circle top right
Tap Settings
Tap About
Check Play protect certification
It may take 24 hours for Device Certification to be updated.
Note: If after completeting Get Device Certified and Check Device Certification you've waited 24 hours your Device is not Certifed or your Device is Certified and certain Google Store apps (Google Pay, NetFliks, etc.) are not working. Use the Play Integrity API Checker app or the TB Checker - Safetynet and Root app to verify you are passing Play Integrity.
Set Magisk App Update Channel/Update Magisk
Set Magisk App Update Channel
Open Magisk App > Tap Settings icon > Update Channel > Select Stable, Beta, Canary or Custom.
Update Magisk
When Magisk App notifies you of an update:
Tap install.
Select, Direct Install (Recommended)
When it finishes installing
Tap, Save Log
Log location: /storage/emulated/0/Download
Tap, Reboot
Done!
Install/Update Magisk Modules
Download File(s)
Displax's latest SafetyNet Fix, a "fork" of kdrag0n safetynet-fix.
These are the NEW Magisk Module repositories:
Androidacy Module Manager
Androidacy Module Manager - Releases
Androidacy Download Center
This is the old Magisk Module repository:
https://github.com/Fox2Code/Fox Magisk Module Manager
LSposed Releases
Shamiko Releases
Install Modules from Storage
Open Magisk
Tap the Modules icon
Tap Install from storage
Navigate to the folder with the Module you want to install.
Tap the Module to highlite it and tap Select.
After it installs, tap the Disc Icon to save the install log.
Tap Reboot
Install Modules from Androidacy Module Manager
Open Androidacy Module Manager
Tap the Modules icon
Locate the Module you want to install
Tap Install
After it installs, tap the Disc Icon to save the install log.
Tap Reboot
Update Modules
Open Androidacy Module Manager
You, will see the Modules that have Updates.
Tap the Module you want to update.
Tap install.
After it installs, tap the Disc Icon to save the install log.
Tap Reboot
Open a Command Prompt/Boot Fastboot Mode/Boot Recovery
Open a Command Prompt on Computer
Open File Explorer, click the platform-tools folder ==> click the folder icon (left side of address bar) to highlight it type cmd and press enter.
Open a Powershell Command Prompt on Computer: Open File Explorer, click the platform-tools folder ==> click the folder icon (left side of address bar) to highlight it type powershell and press enter.
Notes:
Enable USB Debugging, on your phone: Settings ==> System ==> Advanced ==> Developer options ==> Scroll down to USB debugging and enable it.
When using the Powershell Command Prompt Commands must be preceeded with ./: i.e, ./fastboot devices
If you do not want to open a Command Prompt every time you want to use the fastboot command, add the path to the Platform-tools folder to Windows environment variables.
Boot fastboot mode (bootloader):
Power off phone, press and hold the power and volume down buttons until you see Start.
Boot Recovery
Power off phone, press and hold the power and volume down buttons until you see Start. Use volume up/down button until you see Recovery mode. Press power button.
Test fastboot
Enable Developer Options - Tap Settings > About phone > Build number 7 times or until you should see 'you are a Developer'.
Enable USB Debugging - Tap Settings > System > Advanced > Developer options >
Enable USB Debugging.
Open a Command Prompt on your computer in the Platform-tools folder.
Boot fastboot mode on your phone
Connect the phone to the Computer.
At the prompt type: fastboot devices to verify communication with phone. It should return your phone's serial number.
ADB Sideload
Stock Recovery
Full OTA Images for Nexus and Pixel Devices - Updating instructions
Custom Recovery TWRP
Waiting for Android 11 (R) T.W.R.P
~ ~ ~ Part III - Other ~ ~ ~
Custom ROMs
Need help with a Custom ROM?
If you are you are trying to install or have installed a Custom ROM, read and follow the Installation Instructions in the OP of the Custom ROM thread.
Search the thread of the Custom ROM you are trying to install or have installed for answer(s)/solution(s) to your question(s)/problem(s): If you don't find a answer(s)/solution(s) to your question(s)/problem(s). Post your question(s)/request(s) for help in the Custom ROM thread you are trying to install or have installed.
If you are trying to install a Addon(s) {Custom Kernel, Magisk, etc.} to the Custom ROM you installed: Search the thread of the Custom ROM you installed or the thread of the Addon you want to add to your Custom ROMfor answer(s)/solution(s) to your question(s)/problem(s). If you don't find an answer(s)/solution(s) to your question(s)/problem(s). Post your question(s)/request(s) for help in the Custom ROM or Addon (Custom Kernel, Magisk, etc.) thread.
ROMs
Google Pixel 4a5(G) ROMs, Kernels, Recoveries, & Other
Other Custom ROMs
lineageOS 20.0 for the Google Pixel 4a5(G) (bramble) Nightly
[ROM] [UNOFFICIAL] LineageOS 19.0 - microG Edition By: dic1911
Themes, Apps, and Mods
Google Pixel 4a5(G) Themes, Apps, and Mods
T.W.R.P. Backup/Restore
Waiting for Android 13 T.W.R.P.

As this is my first device that supports unlocking the bootloader, before I proceed with root, I want to make sure I can return to stock with a locked bootloader if desired. Based on my understanding of the directions, 1) wipe phone 2) flash stock image 3) relock bootloader will safely return the phone to its original state after rooting and/or installing a custom rom. Am I understanding correctly? Thanx.

rmckay1763 said:
As this is my first device that supports unlocking the bootloader, before I proceed with root, I want to make sure I can return to stock with a locked bootloader if desired. Based on my understanding of the directions, 1) wipe phone 2) flash stock image 3) relock bootloader will safely return the phone to its original state after rooting and/or installing a custom rom. Am I understanding correctly? Thanx.
Click to expand...
Click to collapse
Do #3 Return to stock

Just unlocked the bootloader on my 4a 5G and I'd like to ADB Push all sdcard files from my old phone to the 4a 5G before I do the initial setup. Is this possible?
Command Prompt tells me adb is unauthorized (was authorized until I unlocked the bootloader).

Homeboy76 said:
Do #3 Return to stock
Click to expand...
Click to collapse
okay, I just wanted to make sure I did not do anything irrevocable. thanks for putting together a comprehensive guide.

kha1rul said:
Just unlocked the bootloader on my 4a 5G and I'd like to ADB Push all sdcard files from my old phone to the 4a 5G before I do the initial setup. Is this possible?
Command Prompt tells me adb is unauthorized (was authorized until I unlocked the bootloader).
Click to expand...
Click to collapse
Do you have the latest SDK Platform-tools?
There is a link in the OP - Prerequisites , if you need to update it.

@LastQuestion
If your phone had root and you did #4 'Keep data' to install the latest factory image. Your bootloop is probably caused by a rouge Magisk module.
That is why I, always, recommend uninstalling Magisk before installing/updating the factory image.
Do you have the latest SDK Platform-tools r 30.0.3? If not, there is s link in the OP - Prerequisites to get the latest SDK Platform-tools.
Have you tried flashing the stock boot.img to both slots to stop the bootloop?
fastboot flash boot --slot all boot.img
If flashing the stock boot.img stops the bootloop and your phone boots.
- boot Safe Mode
- Reboot - To remove all residual files, Magisk modules, etc.
- If your phone has the latest factory image do #7 to root/reroot. Otherwise, Do #4 'keep data', then do #7 to root/reroot.

Homeboy76 said:
Do you have the latest SDK Platform-tools?
There is a link in the OP - Prerequisites , if you need to update it.
Click to expand...
Click to collapse
I do have the latest.

kha1rul said:
I do have the latest.
Click to expand...
Click to collapse
@kha1rul
Ok!
I never used adb push files from and old device to a new device.
What is your old device?
Maybe one of these links will help:
- ADB Android Device Unauthorized
- ADB Android Device Unauthorized
Or
You could copy the files from your old device to your computer. Then copy them from your computer to your Pixel 4a (5)
I shouldn't matter how you transfer the files as long as you get the files transfered.

Homeboy76 said:
@kha1rul
Ok!
I never used adb push files from and old device to a new device.
What is your old device?
Maybe one of these links will help:
- ADB Android Device Unauthorized
- ADB Android Device Unauthorized
Or
You could copy the files from your old device to your computer. Then copy them from your computer to your Pixel 4a (5)
I shouldn't matter how you transfer the files as long as you get the files transfered.
Click to expand...
Click to collapse
I wanted to push because it's much more reliable and faster than MTP.
Regarding my previous dilemma, I made a noob mistake, didn't press power+UP to get into recovery!
Even so, problem is it seems that stock recovery only allows sideload, not push, if I'm not mistaken?
So I decided to set up the device and install the apps, and THEN do adb push.
The problem I have now is that there are certain files which can't be pushed for permission reasons, and the whole operation then stops. Is there a way to get adb to simply skip those files and only do the ones it can?

kha1rul said:
I wanted to push because it's much more reliable and faster than MTP.
Regarding my previous dilemma, I made a noob mistake, didn't press power+UP to get into recovery!
Even so, problem is it seems that stock recovery only allows sideload, not push, if I'm not mistaken?
So I decided to set up the device and install the apps, and THEN do adb push.
The problem I have now is that there are certain files which can't be pushed for permission reasons, and the whole operation then stops. Is there a way to get adb to simply skip those files and only do the ones it can?
Click to expand...
Click to collapse
¯\_(ツ)_/¯

Great work, AGAIN!!

Thanks for the write-up. Just got one of these as I dropped my old phone, and I was due anyways. So question regarding Safetynet. I went ahead and went with the latest Feb factory image, patched the boot and rooted with Magisk, then tried the safety net and attestation fails. Anybody have the feb patch and passing safetynet? if so what was the sequence you used? thanks

lu270bro said:
Thanks for the write-up. Just got one of these as I dropped my old phone, and I was due anyways. So question regarding Safetynet. I went ahead and went with the latest Feb factory image, patched the boot and rooted with Magisk, then tried the safety net and attestation fails. Anybody have the feb patch and passing safetynet? if so what was the sequence you used? thanks
Click to expand...
Click to collapse
You need Universal Safetynet fix v 1.1.1 Magisk module.

lu270bro said:
Thanks for the write-up. Just got one of these as I dropped my old phone, and I was due anyways. So question regarding Safetynet. I went ahead and went with the latest Feb factory image, patched the boot and rooted with Magisk, then tried the safety net and attestation fails. Anybody have the feb patch and passing safetynet? if so what was the sequence you used? thanks
Click to expand...
Click to collapse
- Root with Magisk patched img
- Open Magisk Manager install SafetyNet module
- Reboot
- Open Magisk Manager Enable Magisk hide
- Hide Google Play store, Google pay, etc
- Clear cache and storage for the above apps
- Reboot

Homeboy76 said:
- Root with Magisk patched img
- Open Magisk Manager install SafetyNet module
- Reboot
- Open Magisk Manager Enable Magisk hide
- Hide Google Play store, Google pay, etc
- Clear cache and storage for the above apps
- Reboot
Click to expand...
Click to collapse
yeah, im an idiot, got it sorted before i seen your post but thank you tho. stupid freakin basic crap.......i never did magisk hide and have it repackaged. I did have to use the universal zip, but once i did all that, worked perfect. but again, thank you very much

kha1rul said:
Just unlocked the bootloader on my 4a 5G and I'd like to ADB Push all sdcard files from my old phone to the 4a 5G before I do the initial setup. Is this possible?
Command Prompt tells me adb is unauthorized (was authorized until I unlocked the bootloader).
Click to expand...
Click to collapse
Not sure if you still need it, but might be usefule for others.
Unlocking bootloader wipes everything including ADB prompt for your computer. You need to boot system, open developer options , enable ADB debugging and grant access to your computer again when the little popup window appears.

Hi ! Please help me my Pixel 4a 5g unlock bootloader Root Magisk and I have update of MAgisk I make it but bootloop !? And my usb debogging not check... And Test to flash-all but permission denied ?
I don't know how do to restart it ? Please

I'm looking to buy one of these (used) and was wondering if the G025E variant is able to be bootloader unlocked or not?

fremont85 said:
I'm looking to buy one of these (used) and was wondering if the G025E variant is able to be bootloader unlocked or not?
Click to expand...
Click to collapse
In case anyone else is curious... Yes, the G025E variant is able to be bootloader unlocked.

Collection of Useful Guides and Files (Unlock Bootloader, Fix Softbrick, Update to EMUI 5, Update to EMUI 8, Upgrade to AOSP 10)

Description
None of the work in this thread is actually made by me. Credit will be given where credit is due.
This is simply a collection of everything required so that it is easier for people to tinker with their Honor 6X, and be able to restore to a working phone quickly if something goes wrong.
All text placed in quotations are either adb or fastboot commands that are to be executed.
Your phone will be connected to the computer for most parts of the process, so unless the instructions specifically says to disconnect the cable, keep it connected.
The power button for my Honor 6X is broken, so some things I do in this guide might seem weird if you have a working one.
Leave any questions, concerns, or feedback below, and I might be able to help with them.
Credits
PotatoNV - mashed-potatoes on GitHub
Unbrick and Update to EMUI 5 - FY03 ganesh bakare on Youtube
Update to EMUI 8 - FY03 ganesh bakare on Youtube
HWOTA Update Method - @Kentoto2021
Huawei Update Extractor - @worstenbrood
AOSP 10 Tutorial - @Venkata Lochan Nune
AOSP 10 - @phhusson
Prerequisites
Huawei Honor 6X (any model)
Windows Computer
USB to micro-b cable
Micro SD card (>4GB)
Micro SD card adapter
adb and fastboot
winrar or alternative archive manager
something to touch testpoints with (i.e. tweezers)
Unlocking Bootloader (REQUIRED FILES: PotatoNV-next-v2.1.0-x86.exe | 2.7MB)
We will be using PotatoNV to be able to unlock the bootloader and get the unlock code.
Full tutorial and troubleshooting can be found here if this explanation is not in depth enough.
Turn off the device. While touching the appropriate testpoints on the motherboard, connect the phone to your computer.
Location of testpoints are beside the fingerprint sensor connector, and can be found in detail here: Honor 6X Testpoints.png | 114 KB
I'm not exactly sure how these testpoints work, but the tutorial on GitHub says connecting point A to ground will put the phone into edl mode once you connect to a computer.
In a video I saw that they bridged the gap between point A and B with a tweezer, and this worked for me reliably so you should use this method if you can.
Open PotatoNV.
Verify that the target device is correct and that it is using COM3.
Select "Kirin 65x (A)" in the bootloader dropdown.
Click start, and the process should unlock the bootloader and output the new unlock code in the console on the right hand side.
Create a text file and paste the code into it! Do not lose the code or you will have to repeat this process again.
Soft Bricked Device to EMUI 2 (REQUIRED FILES: Honor 6X BRICK to EMUI 2.rar | 564.3 MB)
This is an OS designed for testing purposes and is only used for updating to a newer OS in this guide.
Extract [Honor 6X BRICK to EMUI 2.rar]
Install drivers in [Handset ProductLine 2.01.02.00] by launching [DriverSetup.exe]
Launch [idt.exe] in [IDT_V2.0.0.9]
In the toolbar on the top of the screen, click the toolbox icon to the right of the stop icon.
In the file selection prompt that comes up, select [HL2BLNTMBD001051_Download.xml] from [HL2BLNTMBD001051], and press OK.
Turn off the device. While touching the same testpoints on the motherboard as before, connect the phone to your computer.
In the toolbar at the top of the screen, click the play icon to start the flashing process.
After flashing is done, you should be booted into an OS that only has a couple of testing applications.
EMUI 2 to EMUI 5 (REQUIRED FILES: Honor 6X EMUI 2 to EMUI 5.rar | 1.35GB)
You can stop after these steps if you are happy with using stock EMUI 5.
Extract [Honor 6x EMUI 2 to EMUI 5.rar]
"adb reboot bootloader" to reboot to fastboot mode.
Pick any model from the [HonorOEMINFO] folder and move/copy the corresponding file to the adb root folder.
As an example, I used BLN-AL20C00 as it is the most similar to my original model BLN-AL10C00.
If you do not have a preference, you can just do exactly what I did for convenience.
"fastboot flash oeminfo BLN-AL20C00"
Flashing oeminfo relocks the bootloader.
Even if it says your phone is unlocked in the fastboot mode, you are unable to flash images like TWRP.
To find out how to install TWRP on EMUI 5 you can read through the EMUI 5 to EMUI 8 section after.
"fastboot reboot"
Using a computer and an SD card adaptor, create a folder named [dload] in the root directory of the SD card, and move/copy the [update.app] file into this folder.
Insert the SD card back into the phone, unlock the device, and click the software update icon on the home screen.
Click "1. SD card upgrade", and confirm any prompts that pop up.
Your phone should reboot, start the update process, and boot when its done.
The first boot may take a while (~5 min?) so be patient.
EMUI 5 to EMUI 8 (REQUIRED FILES: Honor 6X EMUI 5 to EMUI 8.rar | 1.86GB)
You can stop after these steps if you are happy with using stock EMUI 8.
"fastboot oem unlock code"
Replace code with the actual unlock code that you saved in the text file before.
Ex. "fastboot oem unlock code 71WTJ3N3Q425ASJ4"
A prompt will pop up on your phone display, asking you to confirm if you want to unlock the bootloader. Use volume buttons to scroll to yes and press the power button to confirm.
Your phone will restart and start factory resetting. The factory reset will fail, as expected, but it is fine, just click restart system. Again, this is the first boot and might take a while (~5 min?).
Once your phone has booted up, "adb reboot bootloader"
Move the file [twrp-3.1.1-0-berlin.img] to the [adb] folder.
Once your phone enters fastboot mode, "fastboot flash recovery twrp-3.1.1-0-berlin.img"
"fastboot reboot", once your phone boots, "adb reboot recovery"
For some reason "fastboot reboot recovery" does not actually boot you into the recovery, so we will boot into the OS first.
Move the [adb] folder to your C:/ drive, and put the [HWOTA_BLN_Eng] in the [adb] folder.
Open the [HWOTA8_BLN] folder in the [HWOTA_BLN_Eng] folder. Execute [update_eng.bat] by clicking it.
Enter 1 and press enter. (Repack)
Once that is complete, "adb reboot bootloader"
The script wants to install TWRP, but the recovery that the script wants to install does not seem to work according to my testing.
This is fine because the process of flashing it will fail, as the script tries to execute "fastboot flash recovery_ramdisk image" for some reason.
The recovery_ramdisk parition does not exist on EMUI 5.
Just ignore the error it gives in the console, as we already have TWRP installed anyway, and press enter.
"fastboot reboot", once your phone boots, "adb reboot recovery"
Once your phone boots into TWRP, press enter.
Enter 2 and press enter. (Using the Script)
Enter 1 and press enter. (Change Firmware)
Press enter to continue, and your phone will reboot to TWRP and start flashing the required files.
Once the process is done, go to Reboot -> System, and you should be booting into EMUI 8 in some time.
EMUI 8 to AOSP 10 (REQUIRED FILES: Honor 6x EMUI 8 to AOSP 10.rar | 553.3MB)
"adb reboot bootloader"
Move all of the files in the [Honor 6X EMUI 8 to AOSP 10] folder to the [adb] folder.
"fastboot flash recovery_ramdisk RECOVERY-V2.img"
"fastboot reboot", once your phone boots, "adb reboot recovery"
"adb push -p system-quack-arm64-aonly-vanilla.img /sdcard/"
After that is complete, click on install -> install image button on the bottom right -> click [system-quack-arm64-aonly-vanilla.img] -> choose system image -> swipe to flash.
After the image finishes flashing, go to reboot -> fastboot
"fastboot flash recovery_ramdisk RECOVERY_RAMDIS.img"
We are flashing our stock recovery back in order to be able to reset our phone properly.
Do not factory reset using TWRP as it will softbrick your device, and you will have to start over again.
"fastboot reboot", once your phone boots, "adb reboot recovery"
In the eRecovery, click on clear cache partition, wait for it to complete, then go back and click on factory reset.
The phone will then reboot and factory reset, which will fail, but it is fine, just click reboot and you should be booting into your new OS soon!

lmaohelp said:
Description
None of the work in this thread is actually made by me. Credit will be given where credit is due.
This is simply a collection of everything required so that it is easier for people to tinker with their Honor 6X, and be able to restore to a working phone quickly if something goes wrong.
All text placed in quotations are either adb or fastboot commands that are to be executed.
Your phone will be connected to the computer for most parts of the process, so unless the instructions specifically says to disconnect the cable, keep it connected.
The power button for my Honor 6X is broken, so some things I do in this guide might seem weird if you have a working one.
Leave any questions, concerns, or feedback below, and I might be able to help with them.
Credits
PotatoNV - mashed-potatoes on GitHub
Unbrick and Update to EMUI 5 - FY03 ganesh bakare on Youtube
Update to EMUI 8 - FY03 ganesh bakare on Youtube
HWOTA Update Method - @Kentoto2021
Huawei Update Extractor - @worstenbrood
AOSP 10 Tutorial - @Venkata Lochan Nune
AOSP 10 - @phhusson
Prerequisites
Huawei Honor 6X (any model)
Windows Computer
USB to micro-b cable
Micro SD card (>4GB)
Micro SD card adapter
adb and fastboot
winrar or alternative archive manager
something to touch testpoints with (i.e. tweezers)
Unlocking Bootloader (REQUIRED FILES: PotatoNV-next-v2.1.0-x86.exe | 2.7MB)
We will be using PotatoNV to be able to unlock the bootloader and get the unlock code.
Full tutorial and troubleshooting can be found here if this explanation is not in depth enough.
Turn off the device. While touching the appropriate testpoints on the motherboard, connect the phone to your computer.
Location of testpoints are beside the fingerprint sensor connector, and can be found in detail here: Honor 6X Testpoints.png | 114 KB
I'm not exactly sure how these testpoints work, but the tutorial on GitHub says connecting point A to ground will put the phone into edl mode once you connect to a computer.
In a video I saw that they bridged the gap between point A and B with a tweezer, and this worked for me reliably so you should use this method if you can.
Open PotatoNV.
Verify that the target device is correct and that it is using COM3.
Select "Kirin 65x (A)" in the bootloader dropdown.
Click start, and the process should unlock the bootloader and output the new unlock code in the console on the right hand side.
Create a text file and paste the code into it! Do not lose the code or you will have to repeat this process again.
Soft Bricked Device to EMUI 2 (REQUIRED FILES: Honor 6X BRICK to EMUI 2.rar | 564.3 MB)
This is an OS designed for testing purposes and is only used for updating to a newer OS in this guide.
Extract [Honor 6X BRICK to EMUI 2.rar]
Install drivers in [Handset ProductLine 2.01.02.00] by launching [DriverSetup.exe]
Launch [idt.exe] in [IDT_V2.0.0.9]
In the toolbar on the top of the screen, click the toolbox icon to the right of the stop icon.
In the file selection prompt that comes up, select [HL2BLNTMBD001051_Download.xml] from [HL2BLNTMBD001051], and press OK.
Turn off the device. While touching the same testpoints on the motherboard as before, connect the phone to your computer.
In the toolbar at the top of the screen, click the play icon to start the flashing process.
After flashing is done, you should be booted into an OS that only has a couple of testing applications.
EMUI 2 to EMUI 5 (REQUIRED FILES: Honor 6X EMUI 2 to EMUI 5.rar | 1.35GB)
You can stop after these steps if you are happy with using stock EMUI 5.
Extract [Honor 6x EMUI 2 to EMUI 5.rar]
"adb reboot bootloader" to reboot to fastboot mode.
Pick any model from the [HonorOEMINFO] folder and move/copy the corresponding file to the adb root folder.
As an example, I used BLN-AL20C00 as it is the most similar to my original model BLN-AL10C00.
If you do not have a preference, you can just do exactly what I did for convenience.
"fastboot flash oeminfo BLN-AL20C00"
Flashing oeminfo relocks the bootloader.
Even if it says your phone is unlocked in the fastboot mode, you are unable to flash images like TWRP.
To find out how to install TWRP on EMUI 5 you can read through the EMUI 5 to EMUI 8 section after.
"fastboot reboot"
Using a computer and an SD card adaptor, create a folder named [dload] in the root directory of the SD card, and move/copy the [update.app] file into this folder.
Insert the SD card back into the phone, unlock the device, and click the software update icon on the home screen.
Click "1. SD card upgrade", and confirm any prompts that pop up.
Your phone should reboot, start the update process, and boot when its done.
The first boot may take a while (~5 min?) so be patient.
EMUI 5 to EMUI 8 (REQUIRED FILES: Honor 6X EMUI 5 to EMUI 8.rar | 1.86GB)
You can stop after these steps if you are happy with using stock EMUI 8.
"fastboot oem unlock code"
Replace code with the actual unlock code that you saved in the text file before.
Ex. "fastboot oem unlock code 71WTJ3N3Q425ASJ4"
A prompt will pop up on your phone display, asking you to confirm if you want to unlock the bootloader. Use volume buttons to scroll to yes and press the power button to confirm.
Your phone will restart and start factory resetting. The factory reset will fail, as expected, but it is fine, just click restart system. Again, this is the first boot and might take a while (~5 min?).
Once your phone has booted up, "adb reboot bootloader"
Move the file [twrp-3.1.1-0-berlin.img] to the [adb] folder.
Once your phone enters fastboot mode, "fastboot flash recovery twrp-3.1.1-0-berlin.img"
"fastboot reboot", once your phone boots, "adb reboot recovery"
For some reason "fastboot reboot recovery" does not actually boot you into the recovery, so we will boot into the OS first.
Move the [adb] folder to your C:/ drive, and put the [HWOTA_BLN_Eng] in the [adb] folder.
Open the [HWOTA8_BLN] folder in the [HWOTA_BLN_Eng] folder. Execute [update_eng.bat] by clicking it.
Enter 1 and press enter. (Repack)
Once that is complete, "adb reboot bootloader"
The script wants to install TWRP, but the recovery that the script wants to install does not seem to work according to my testing.
This is fine because the process of flashing it will fail, as the script tries to execute "fastboot flash recovery_ramdisk image" for some reason.
The recovery_ramdisk parition does not exist on EMUI 5.
Just ignore the error it gives in the console, as we already have TWRP installed anyway, and press enter.
"fastboot reboot", once your phone boots, "adb reboot recovery"
Once your phone boots into TWRP, press enter.
Enter 2 and press enter. (Using the Script)
Enter 1 and press enter. (Change Firmware)
Press enter to continue, and your phone will reboot to TWRP and start flashing the required files.
Once the process is done, go to Reboot -> System, and you should be booting into EMUI 8 in some time.
EMUI 8 to AOSP 10 (REQUIRED FILES: Honor 6x EMUI 8 to AOSP 10.rar | 553.3MB)
"adb reboot bootloader"
Move all of the files in the [Honor 6X EMUI 8 to AOSP 10] folder to the [adb] folder.
"fastboot flash recovery_ramdisk RECOVERY-V2.img"
"fastboot reboot", once your phone boots, "adb reboot recovery"
"adb push -p system-quack-arm64-aonly-vanilla.img /sdcard/"
After that is complete, click on install -> install image button on the bottom right -> click [system-quack-arm64-aonly-vanilla.img] -> choose system image -> swipe to flash.
After the image finishes flashing, go to reboot -> fastboot
"fastboot flash recovery_ramdisk RECOVERY_RAMDIS.img"
We are flashing our stock recovery back in order to be able to reset our phone properly.
Do not factory reset using TWRP as it will softbrick your device, and you will have to start over again.
"fastboot reboot", once your phone boots, "adb reboot recovery"
In the eRecovery, click on clear cache partition, wait for it to complete, then go back and click on factory reset.
The phone will then reboot and factory reset, which will fail, but it is fine, just click reboot and you should be booting into your new OS soon!
Click to expand...
Click to collapse
That's a really great post! Hats off to your effort...
Include a way to get back to emui 8 from custom ones too that will be quite helpful.
EDIT : I opened a new thread of getting back to EMUI 8 if someone needs.

Venkata Lochan Nune said:
That's a really great post! Hats off to your effort...
Include a way to get back to emui 8 from custom ones too that will be quite helpful.
Click to expand...
Click to collapse
That will be perfect

it would be better if you update about how to get back to emui 8 original rom form ASOP 10

Hi,
I'm failing @ this step (install Huawei USB COM 1.0 driver.
I tried checked every method shown on YT, and no help; I also tried on a different machine, same output

jottect said:
Hi,
I'm failing @ this step (install Huawei USB COM 1.0 driver.
I tried checked every method shown on YT, and no help; I also tried on a different machine, same output
Click to expand...
Click to collapse
check out my solution in Fluid OS - 11 thread. and tell me if it worked.
Edit : you can find it here.

Hello, I am on a model GR5 BLL-L22 EMUI5 and I want to go up to Emui 8. Is it necessary that I first go down to Emui 2 then Emui 5 or can I directly go to Emui 8?

VarianWrynn said:
Hello, I am on a model GR5 BLL-L22 EMUI5 and I want to go up to Emui 8. Is it necessary that I first go down to Emui 2 then Emui 5 or can I directly go to Emui 8?
Click to expand...
Click to collapse
You can directly go to EMUI 8.

Thanks for the reply, I'm trying it out now and I'm an ultra noob. I have not yet unlocked my bootloader because I am afraid of not being able to connect to the machine anymore because each time I enter bootloader mode with the "adb reboot bootloarder" function my phone disconnects and the functions " fastboot devices "and" adb devices "no longer see it. I am using minimal adb and fastboot app and have already enabled usb debugging in my phone. I do not know if it's normal

VarianWrynn said:
Thanks for the reply, I'm trying it out now and I'm an ultra noob. I have not yet unlocked my bootloader because I am afraid of not being able to connect to the machine anymore because each time I enter bootloader mode with the "adb reboot bootloarder" function my phone disconnects and the functions " fastboot devices "and" adb devices "no longer see it. I am using minimal adb and fastboot app and have already enabled usb debugging in my phone. I do not know if it's normal
Click to expand...
Click to collapse
Check the link in post 6. Install the drivers from attachments of that post.
That's because you don't have the right drivers(Huawei COM) installed.

I did it, it works now. I just watched the video to use Potatonv, I'm not able to open my phone now, there is not a method to get around that?

VarianWrynn said:
I did it, it works now. I just watched the video to use Potatonv, I'm not able to open my phone now, there is not a method to get around that?
Click to expand...
Click to collapse
You have to open the phone to access the Test Point. There's no workaround for this.
TBH, even I hate this step in the whole procedure but you have to do it. Sorry, theres no workaround.

No Lucky for me, i try it another Day

VarianWrynn said:
No Lucky for me, i try it another Day
Click to expand...
Click to collapse
Do it when you're free. GOOD LUCK !

I unlock my bootloader but thé factory reset don't fail . can I still continue the procedure for emui8?

Now my phone is unauthorized in adb and fastboot minimal. When i enter adb reboot bootloader he say unauthorized and this adb serveurs $adb vendor keys is not set

VarianWrynn said:
I unlock my bootloader but thé factory reset don't fail . can I still continue the procedure for emui8?
Click to expand...
Click to collapse
It will not fail when you are on EMUI 5. So, you can continue to upgrade to EMUI 8.

VarianWrynn said:
Now my phone is unauthorized in adb and fastboot minimal. When i enter adb reboot bootloader he say unauthorized and this adb serveurs $adb vendor keys is not set
Click to expand...
Click to collapse
Are you still in EMUI 5?
I did not try using adb on EMUI 5 after unlocking bootloader. It worked perfectly for me on EMUI 8.
If you want to access bootloader or fastboot, turn off your device. Wait for some time. Press and hold Volume down button and plug in usb.
That will take you to fastboot mode.

Yes im on emui5.

VarianWrynn said:
Yes im on emui5.
Click to expand...
Click to collapse
Well then update to EMUI 8. You'll no longer have this problem.

Question Update to January HELP

I am rooted and I am not sure how to update to January. I see a lot of different ways. Can someone point me to the easiest. I tried just doing the OTA update and then re-root but got an error message. Thank you very much

I just updated from Dec/rooted to Jan/rooted by running Flash-all -nowipe while having my phone in Fastboot mode. I then patched the boot.img. Went very smoothly.

clipdawg05 said:
I am rooted and I am not sure how to update to January. I see a lot of different ways. Can someone point me to the easiest. I tried just doing the OTA update and then re-root but got an error message. Thank you very much
Click to expand...
Click to collapse
Here ya go. Let's try to keep all rooting questions in this forum. It will make it easier to get an answer and the OP has put in a lot of work to keep this up to date. Otherwise we have 'update to January help' which says nothing. Give it a try and there are a lot of people there willing to help you.
[GUIDE] Pixel 6 Pro "raven": Unlock Bootloader, Update, Root, Pass SafetyNet
⚠️⚠️⚠️ WARNING! IF YOU ARE UPDATING TO ANDROID 13 FOR THE FIRST TIME, READ THIS FIRST!⚠️⚠️⚠️ If you are looking for my guide on a different Pixel, find it here: Pixel 3 Pixel 3XL Pixel 3a Pixel 3aXL Pixel 4 Pixel 4XL Pixel 4a Pixel 4a (5G)...
forum.xda-developers.com

bobby janow said:
Here ya go. Let's try to keep all rooting questions in this forum. It will make it easier to get an answer and the OP has put in a lot of work to keep this up to date. Otherwise we have 'update to January help' which says nothing. Give it a try and there are a lot of people there willing to help you.
[GUIDE] Pixel 6 Pro "raven": Unlock Bootloader, Update, Root, Pass SafetyNet
⚠️⚠️⚠️ WARNING! IF YOU ARE UPDATING TO ANDROID 13 FOR THE FIRST TIME, READ THIS FIRST!⚠️⚠️⚠️ If you are looking for my guide on a different Pixel, find it here: Pixel 3 Pixel 3XL Pixel 3a Pixel 3aXL Pixel 4 Pixel 4XL Pixel 4a Pixel 4a (5G)...
forum.xda-developers.com
Click to expand...
Click to collapse
ok thank you

clipdawg05 said:
I am rooted and I am not sure how to update to January. I see a lot of different ways. Can someone point me to the easiest. I tried just doing the OTA update and then re-root but got an error message. Thank you very much
Click to expand...
Click to collapse
I'd recommend using this method from the linked Thread above
Don't forget to get the boot.img from the new Firmware (extract factory image, find it) and patch that with Magisk, then transfer it back to your PC ADB folder and use that as "master root").

Morgrain said:
I'd recommend using this method from the linked Thread above
View attachment 5509367
Don't forget to get the boot.img from the new Firmware (extract factory image, find it) and patch that with Magisk, then transfer it back to your PC ADB folder and use that as "master root").
Click to expand...
Click to collapse
This is the boot img from when I rooted the phone the first time, or do I have to patch the boot from this new January update

clipdawg05 said:
This is the boot img from when I rooted the phone the first time, or do I have to patch the boot from this new January update
Click to expand...
Click to collapse
Patch the new January boot image and use that instead of the old one.
Also when you do step 4, (after the system boots normally and you see the update bar slowly rising until the OS comes), unlock the phone and look into notifications, it will say something like "finishing updates", only when that finishes you reboot into bootloader.

This happened as soon as i pressed enter. What to do now

What I did (p6p, november update, rooted, bootloader unlocked):
1. Downloaded latest Jan factory image https://dl.google.com/dl/android/aosp/raven-sq1d.220105.007-factory-d8f6b8a4.zip, extracted boot.img and put it aside for step 6.
2. Disabled all magisk modules (not necessary, just in case).
3. Went to flash.android.com via Edge, agreed to all prompts on the page and phone screen.
4. UNCHECKED all checkboxes. There were 3 of them, something like Wipe All, Lock Bootlocker, Flash All Partitions).
5. Follow all prompts - "Reselect your device" etc.
6. Successfully rebooted, put boot.img file into phone's memory, run Magisk app and patched boot file.
7. Moved the patched file "magisk_patched-23016_IVwVbT.img" (your file name may be different) back to my pc and run via cmd "fastboot flash boot <location of your patched boot img file>".
8. Rebooted and re-enabled all magisk modules.
With the January update I experience no issues and honestly no changes that I could notice. At least I'm happy there is nothing worse

clipdawg05 said:
This happened as soon as i pressed enter. What to do now
Click to expand...
Click to collapse
If you reboot and come back to the same screen I'm afraid your only option is to wipe data/factory reset.

asdor said:
If you reboot and come back to the same screen I'm afraid your only option is to wipe data/factory reset.
Click to expand...
Click to collapse
ok i will reset. i tried adb devices and it says unauthorized

I think there is something wrong with my phone. When i try a normal update it fails. When i try the android flash tool it tells me my phone is already in use and sideloading does not work.
Finally got past the phone already in use by restarting, only to have another failure flashing

clipdawg05 said:
This happened as soon as i pressed enter. What to do now
Click to expand...
Click to collapse
What does that even mean? What're you doing when you hit enter to get that screen? I'm assuming you're issuing a fastboot command but you need to provide more details.
clipdawg05 said:
ok i will reset. i tried adb devices and it says unauthorized
Click to expand...
Click to collapse
You need to enable developer options on your phone if you haven't already. Go into settings > about phone > click on build number until it says "you're a developer" at the bottom. Then, go into settings > system > developer options and enable USB debugging. Try running adb devices again and clock on "allow" prompt on your phone when it pops up.
clipdawg05 said:
I think there is something wrong with my phone. When i try a normal update it fails. When i try the android flash tool it tells me my phone is already in use and sideloading does not work.
Finally got past the phone already in use by restarting, only to have another failure flashing
Click to expand...
Click to collapse
It says phone is in use because you need to issue a "adb kill-server" command and then try the flash tool again.
I had the same OTA issue yesterday. You can try using the flash tool again once you issue the "adb kill-server" command, but if it doesn't work try applying the update via sideload.
Download the OTA image from here - https://dl.google.com/dl/android/aosp/raven-ota-sq1d.220105.007-3a7aafbf.zip
You will also need the stock image so you can extract the boot img. Get it from here - https://dl.google.com/dl/android/aosp/raven-sq1d.220105.007-factory-d8f6b8a4.zip
Once you do that, follow these steps.
Reboot to recovery and sideload the OTA: select Apply Update via ADB, then on your PC:
Code:
adb sideload ota.zip
When the OTA completes, you will be in recovery mode. Select "Reboot to system now".
Allow system to boot and wait for the update to complete. You must let the system do this before proceeding.
Reboot to bootloader.
Boot the master root image:
Code:
fastboot boot <drag and drop master root.img here>
Note: If you prefer, you can download the factory zip and manually patch the new boot image. Do not flash an older boot image after updating.
Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
Reboot your device. You should now be updated with root.
You can find full instructions in this thread:
https://forum.xda-developers.com/t/guide-root-pixel-6-pro-raven-with-magisk.4356231

RetroTech07 said:
What does that even mean? What're you doing when you hit enter to get that screen? I'm assuming you're issuing a fastboot command but you need to provide more details.
You need to enable developer options on your phone if you haven't already. Go into settings > about phone > click on build number until it says "you're a developer" at the bottom. Then, go into settings > system > developer options and enable USB debugging. Try running adb devices again and clock on "allow" prompt on your phone when it pops up.
It says phone is in use because you need to issue a "adb kill-server" command and then try the flash tool again.
I had the same OTA issue yesterday. You can try using the flash tool again once you issue the "adb kill-server" command, but if it doesn't work try applying the update via sideload.
Download the OTA image from here - https://dl.google.com/dl/android/aosp/raven-ota-sq1d.220105.007-3a7aafbf.zip
You will also need the stock image so you can extract the boot img. Get it from here - https://dl.google.com/dl/android/aosp/raven-sq1d.220105.007-factory-d8f6b8a4.zip
Once you do that, follow these steps.
Reboot to recovery and sideload the OTA: select Apply Update via ADB, then on your PC:
Code:
adb sideload ota.zip
When the OTA completes, you will be in recovery mode. Select "Reboot to system now".
Allow system to boot and wait for the update to complete. You must let the system do this before proceeding.
Reboot to bootloader.
Boot the master root image:
Code:
fastboot boot <drag and drop master root.img here>
Note: If you prefer, you can download the factory zip and manually patch the new boot image. Do not flash an older boot image after updating.
Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
Reboot your device. You should now be updated with root.
You can find full instructions in this thread:
https://forum.xda-developers.com/t/guide-root-pixel-6-pro-raven-with-magisk.4356231/[/CODE]
[/LIST]
Click to expand...
Click to collapse
The first picture of a failure was when I was trying to sideload the update.
Thanks for your response but i finally got it done on Android flash tool with the wipe enabled