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

System Has Been Destroyed. probably with the OEM LOCKED.

Hello,
So today I wanted to install a Magisk module, after rebooting, it got me to a bootloop, I erased ALL DATA on adb mode (power botton and volume up). then started all over.
But the Bootloader was still unlocked (because before, I had root), The febuary update was impossible to install, so I thought, maybe locking the OEM may fix it, so I tried tool called " TOOL ALL IN ONE " that claims to have full support for my device.
After trying to OEM Lock, I get a friendly greeting that says " System has been destroyed " .
Trying to go back into ADB mode isn't working.
I have no idea if the OEM was locked, nor how to fix the phone.
I've heard of Mi Flash, but will it work on a Android One device? if so, PLEASE provide me with how to do so (in a noobie friendly way if possible)
If it'll help, I'm running on Pie with January update. No TWRP/Magisk. no current Root access.
UPDATE: I wanted to wait for an answer from you guys but I took a leap of faith and typed " fastboot oem unlock " and the phone was unlocked (showing unlocked on Android One boot screen). That got the system to start a boot! But I think it's bootlooping now. I tried entering ADB mode and I was succefully able to! then I selected to delete all data ( This helped me before to fix the bootloop ). then rebooted.
and right while I am typing this. I see a beautiful Hi there sign!!!
Bois, The phone is up and Running!!! but with all data now gone (ofc).
But still, The OEM is unlocked, Can you please recommend me a proper way to lock it?

Install dump ota febuary update in fastboot

Vitor00 said:
Install dump ota febuary update in fastboot
Click to expand...
Click to collapse
How do I do that? in a noobie way please.

wynix black said:
How do I do that? in a noobie way please.
Click to expand...
Click to collapse
Download adb and fastboot.>>>>https://androiddatahost.com/uq6us
Download ota dump>>>>>https://drive.google.com/file/d/1SZ3rOyaViNZyUzoZDbueqMAJ_Q5vKLA1/view
install adb and fastboot, and paste files from ota in the folder of adb and fastboot
open adb and fastboot and paste the commands one by one>>>>>>https://drive.google.com/open?id=1oxRLyX1x4gAQga5vwn1epHrjqtitDWRB
EDIT: To lock bootloader again, paste "fastboot oem lock" in adb and fastboot

Vitor00 said:
Download adb and fastboot.>>>>
Download ota dump>>>>>
install adb and fastboot, and paste files from ota in the folder of adb and fastboot
open adb and fastboot and paste the commands one by one>>>>>>
EDIT: To lock bootloader again, paste "fastboot oem lock" in adb and fastboot
Click to expand...
Click to collapse
Is the "ota dump" is on February update?
can I auto update easily after this or will I have to install the ota(s) manually in the future?
Are you sure that locking the oem after installing the ota won't give a system has been destroyed?
and finally, is it possible to enable Camera 2 API in the middle of the operation? Before locking the oem.
Many thanks!

Vitor00 said:
Install dump ota febuary update in fastboot
Click to expand...
Click to collapse
Vitor00 said:
Download adb and fastboot.>>>>https://androiddatahost.com/uq6us
install adb and fastboot, and paste files from ota in the folder of adb and fastboot
open adb and fastboot and paste the commands one by one
EDIT: To lock bootloader again, paste "fastboot oem lock" in adb and fastboot
Click to expand...
Click to collapse
I extracted the OTA_DAIZY.zip that you provided in the folder of minimal adb and fastboot, then typed the first command (the bluetooth one) in cmd while the phone is in Fastboot mode, CMD says " error canont load 'bluetooth.img' : no such file or directory"
please, how do I exactly " paste files from ota in the folder of adb and fastboot " ?

You can use MiFlash on this phone and not get your hands dirty with the method mentioned above. Grab the latest available stock ROM from here: https://en.miui.com/download-354.html
Download MiFlash(latest if possible). Turn off the phone and go to fastboot mode (vol down + power). Connect the phone to PC. Open MiFlash and select ROM location then click refresh, your device should be seen now. On the bottom you have options choose one then click start. DON'T interrupt the process when it's flashing.

marstonpear said:
You can use MiFlash on this phone and not get your hands dirty with the method mentioned above. Grab the latest available stock ROM from here:
Download MiFlash(latest if possible). Turn off the phone and go to fastboot mode (vol down + power). Connect the phone to PC. Open MiFlash and select ROM location then click refresh, your device should be seen now. On the bottom you have options choose one then click start. DON'T interrupt the process when it's flashing.
Click to expand...
Click to collapse
Thank you, I'm currently dowloading the stock ROM from the link you provided.
I have some questions about this,
1-you mentioned the options at the bottom, can you explain every one of them, is it as good as it sounds? one of the options is " save user data " of course i'd prefer to save my data IF it's possible and won't ruin the procces. does the "clean data and lock" can result in the System has been destroyed sign? because currently, even if i have a fresh clean all data on my phone, whenever i try to lock the bootloader (from my pc) it says system has been destroyed, If yes, will updates work fine via the settings thing or I will have to do this manually anyways? in other words, will having the oem locked give me any benefits? I'm not intrested in any warrenty/security thing.
2- if I had Magisk with root, and some of it's modules and maybe Camera 2 API enabled and I installed an update rom using Mi Flash, are they going to be deleted?
3-will this rom replace the original that i have on my phone? and my og one will be perma deleted? if I deleted all data after this procces, will it take me to a fresh instalation of this rom? or the one I had before?
4- will my phone remain unlocked after using Mi Flash with the first two options in the bottom (not "clean all and lock" ) ?
I really apologize for asking so many questions!

1- you can try save user data but the phone may not boot, I don't know the reason but I had bricked mine once and tried to flash the stock and save my data, somehow it didn't work. Try it for yourself and if it doesn't boot, flash the ROM again via MiFlash and select clean all and lock. Clean all and lock basically cleans the device, returns it to stock ROM and locks the bootloader, makes your device basically unused, you will have to set it up from scratch. If you use the clean all and lock or the clean all option, phone will boot normally and you can have updates without any problems. Locked bootloader means you can't do any changes to partitions of the device, which is good if you're not planning on rooting etc. You can have updates with either locked or unlocked BL unless of course you haven't tampered with the partitions of the device. I like locked BL because when you unlock the BL it shows another screen when booting, which I personally don't like.
2-MiFlash returns everything to stock, you will definitely lose magisk and root and the modules you installed on Magisk because using MiFlash flashes the original boot.img which makes Magisk useless. You can however get temporary root access and enable cam2API via ADB then lock the bootloader but you need to be careful with the process because you may lose your data (Locking/Unlocking BL erases all data but there's a way to bypass that)
3-As of now, the link I provided has the 10.0.3.0 (january update), if you've downloaded it your phone will install stock(from xiaomi) Pie ROM with January security patches. I forgot to write this update has issues with SIM (reverses SIM1 to SIM2) so I suggest grabbing V10.0.2.0.PDLMIFJ (Fastboot image) from here: https://forum.xda-developers.com/mi-a2-lite/how-to/ota-v9-6-4-0-odlmiff-t3823913 then flashing it via MiFlash then updating to newer versions through settings.
4- if you choose "save user data" or "clean all" your phone will stay unlocked, if you choose "clean all and lock" you will have a locked bootloader. :good:

marstonpear said:
1- you can try save user data but the phone may not boot, I don't know the reason but I had bricked mine once and tried to flash the stock and save my data, somehow it didn't work. Try it for yourself and if it doesn't boot, flash the ROM again via MiFlash and select clean all and lock. Clean all and lock basically cleans the device, returns it to stock ROM and locks the bootloader, makes your device basically unused, you will have to set it up from scratch. If you use the clean all and lock or the clean all option, phone will boot normally and you can have updates without any problems. Locked bootloader means you can't do any changes to partitions of the device, which is good if you're not planning on rooting etc. You can have updates with either locked or unlocked BL unless of course you haven't tampered with the partitions of the device. I like locked BL because when you unlock the BL it shows another screen when booting, which I personally don't like.
2-MiFlash returns everything to stock, you will definitely lose magisk and root and the modules you installed on Magisk because using MiFlash flashes the original boot.img which makes Magisk useless. You can however get temporary root access and enable cam2API via ADB then lock the bootloader but you need to be careful with the process because you may lose your data (Locking/Unlocking BL erases all data but there's a way to bypass that)
3-As of now, the link I provided has the 10.0.3.0 (january update), if you've downloaded it your phone will install stock(from xiaomi) Pie ROM with January security patches. I forgot to write this update has issues with SIM (reverses SIM1 to SIM2) so I suggest grabbing V10.0.2.0.PDLMIFJ (Fastboot image) from here: https://forum.xda-developers.com/mi-a2-lite/how-to/ota-v9-6-4-0-odlmiff-t3823913 then flashing it via MiFlash then updating to newer versions through settings.
4- if you choose "save user data" or "clean all" your phone will stay unlocked, if you choose "clean all and lock" you will have a locked bootloader. :good:
Click to expand...
Click to collapse
Thank you so much for the helpful answers!
So I flashed my phone with the first link you provided ( January update ) using Mi Flash and the option to save user data, It worked perfectly fine. not just that, but I was Finally able to get the February update using the option in the settings, I'm not aware of the SIM problem you mentioned, but i'm not experiencing any major bugs right now.
I want to get camera 2 API but I'll wait till March update to bring it ( if it exists, and launched within the first 10 days ). If the March update didn't carry with Camera 2 API enabled, I'll have to do it myself.
One last question please, How to enable the cam 2 API without magisk or touching something that may stop the built-in updater from installing? how to make it (and maybe Magisk too) survive flashing an OTA?. Will the option "save user data" protect them from getting Snapped™ ?

wynix black said:
Thank you so much for the helpful answers!
So I flashed my phone with the first link you provided ( January update ) using Mi Flash and the option to save user data, It worked perfectly fine. not just that, but I was Finally able to get the February update using the option in the settings, I'm not aware of the SIM problem you mentioned, but i'm not experiencing any major bugs right now.
I want to get camera 2 API but I'll wait till March update to bring it ( if it exists, and launched within the first 10 days ). If the March update didn't carry with Camera 2 API enabled, I'll have to do it myself.
One last question please, How to enable the cam 2 API without magisk or touching something that may stop the built-in updater from installing? how to make it (and maybe Magisk too) survive flashing an OTA?. Will the option "save user data" protect them from getting Snapped™ ?
Click to expand...
Click to collapse
I don't think Xiaomi will ever let this phone have Cam2API. They even broke GCam functionality on Pie update (on Oreo Gcam worked fine but now every Gcam has focus issues). Follow this topic to have Magisk and keep it after updates: https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952 Follow this topic to have Cam2API enabled if you don't want root/Magisk: https://forum.xda-developers.com/mi-a2-lite/how-to/guide-how-to-enable-camera2-api-t3851414 :good:

Rooting pixel 2xl

I have a stock Pixel 2xl running android 10. Can't root it, no matter what i try. Any help would be greatly appreciated. Thanks

grunt0300 said:
I have a stock Pixel 2xl running android 10. Can't root it, no matter what i try. Any help would be greatly appreciated. Thanks
Click to expand...
Click to collapse
Is your bootloader unlocked?

Badger50 said:
Is your bootloader unlocked?
Click to expand...
Click to collapse
Yes it is.

grunt0300 said:
Yes it is.
Click to expand...
Click to collapse
Ok. So you've installed the latest platform-tools on your pc?
Downloaded the factory image that coincides with your current build?
Extracted the factory image, then extracted the image.zip, and moved the boot.img to your phones internal storage?
Magisk manager is installed on your phone. Then you patched the boot.img, and then moved it to your pc platform-tools?
Put your phone into bootloader mode, opened a command prompt on you platform-tools folder, typed in "fastboot devices" to make sure your pc recognizes your phone?
Then fastbooted your patched boot.img to both slots with...
fastboot flash boot magisk_patched.img --slot=all
And then booted up with root?

What happens when you run the fastboot command "fastboot flashing unlock"?

Badger50 said:
Ok. So you've installed the latest platform-tools on your pc?
Downloaded the factory image that coincides with your current build?
Extracted the factory image, then extracted the image.zip, and moved the boot.img to your phones internal storage?
Magisk manager is installed on your phone. Then you patched the boot.img, and then moved it to your pc platform-tools?
Put your phone into bootloader mode, opened a command prompt on you platform-tools folder, typed in "fastboot devices" to make sure your pc recognizes your phone?
Then fastbooted your patched boot.img to both slots with...
fastboot flash boot magisk_patched.img --slot=all
And then booted up with root?
Click to expand...
Click to collapse
Sorry, i've been trying to root this phone all afternoon and i'm burnt out. Maybe tomorrow. Thanks

OK, i tried to root it again, and this is what i got....Your device is corrupt. It can't be trusted and may not work properly. The phone is not recognized by my pc. I can get into "bootloader mode", but can't do a thing with it. I could sure use some help. In the meantime, i'll pop the sim card into my trusty nexus 6, and wait to hear from one of you nice people. Thanks.

grunt0300 said:
OK, i tried to root it again, and this is what i got....Your device is corrupt. It can't be trusted and may not work properly. The phone is not recognized by my pc. I can get into "bootloader mode", but can't do a thing with it. I could sure use some help. In the meantime, i'll pop the sim card into my trusty nexus 6, and wait to hear from one of you nice people. Thanks.
Click to expand...
Click to collapse
Go to the guide in my signature, follow the step by step instructions there.
Make sure you have done the following:
-SDK tools are up to date,
-the proper platform folders are unzipped (there are two),
-you have a couple different USB cables handy.

Az Biker said:
Go to the guide in my signature, follow the step by step instructions there.
Make sure you have done the following:
-SDK tools are up to date,
-the proper platform folders are unzipped (there are two),
-you have a couple different USB cables handy.
Click to expand...
Click to collapse
I just put the sim card back into the pixel 2xl, and it booted up as if it was brand new. Plugged it into pc, got into bootloader mode, typed in command "adb devices", and it recognized the phone. I have all those files downloaded onto my desktop, so what's my next move?

grunt0300 said:
I just put the sim card back into the pixel 2xl, and it booted up as if it was brand new. Plugged it into pc, got into bootloader mode, typed in command "adb devices", and it recognized the phone. I have all those files downloaded onto my desktop, so what's my next move?
Click to expand...
Click to collapse
Like @Az Biker said, follow the guide in his signature :good:

Badger50 said:
Like @Az Biker said, follow the guide in his signature :good:
Click to expand...
Click to collapse
Doesn't work. I can't "fastboot" into anything. When i try, the pc stops recognizing the phone.

grunt0300 said:
Doesn't work. I can't "fastboot" into anything. When i try, the pc stops recognizing the phone.
Click to expand...
Click to collapse
Did you try a different usb cable? And you activated "developer options" and turned on usb debugging?
Also, try typing CMD in the url line from within the same platform tool folder where the platform tools application is located.

Az Biker said:
Did you try a different usb cable? And you activated "developer options" and turned on usb debugging?
Also, try typing CMD in the url line from within the same platform tool folder where the platform tools application is located.
Click to expand...
Click to collapse
OK, after waiting an hour, i tried typing into that command line that popped up within the platform tools folder. I tried adb devices, and my phone was recognized. Now, my phone is not in fastboot mode, and i don't have the sim card in it. What's my next move, please.

grunt0300 said:
OK, after waiting an hour, i tried typing into that command line that popped up within the platform tools folder. I tried adb devices, and my phone was recognized. Now, my phone is not in fastboot mode, and i don't have the sim card in it. What's my next move, please.
Click to expand...
Click to collapse
Have you patched the boot.img with magisk yet? If you look a few posts ago, I gave you exact instructions on how to patch and flash the modified boot.img
Also, adb devices is a command while your in your OS. You need to power off the phone, then enter bootloader mode manually by holding the power + volume down button until you enter the bootloader screen.
Then plug your phone in, open the command prompt on your platform-tools folder, and type in "fastboot devices". If you see your phone's ID number, then you have a good interface. Then you can fastboot the patched boot.img :good:
https://forum.xda-developers.com/pixel-2-xl/help/rooting-pixel-2xl-t4033453/post81455679

Badger50 said:
Have you patched the boot.img with magisk yet? If you look a few posts ago, I gave you exact instructions on how to patch and flash the modified boot.img
Also, adb devices is a command while your in your OS. You need to power off the phone, then enter bootloader mode manually by holding the power + volume down button until you enter the bootloader screen.
Then plug your phone in, open the command prompt on your platform-tools folder, and type in "fastboot devices". If you see your phone's ID number, then you have a good interface. Then you can fastboot the patched boot.img :good:
https://forum.xda-developers.com/pixel-2-xl/help/rooting-pixel-2xl-t4033453/post81455679
Click to expand...
Click to collapse
Can't get into "recovery mode". I have all the files in the file mgr on the phone. Do i have to put the sim card back into the phone in order for this to work?

grunt0300 said:
Can't get into "recovery mode". I have all the files in the file mgr on the phone. Do i have to put the sim card back into the phone in order for this to work?
Click to expand...
Click to collapse
Recovery mode? You need to be in bootloader mode. What files exactly do you have on your phone that your talking about? Just curious, but have you read through any of the directions that myself and @Az Biker have given you? Things seem to be getting lost in translation.

Badger50 said:
Recovery mode? You need to be in bootloader mode. What files exactly do you have on your phone that your talking about? Just curious, but have you read through any of the directions that myself and @Az Biker have given you? Things seem to be getting lost in translation.
Click to expand...
Click to collapse
Right now, i'm so confused that i don't know what day it is. I've got files all over my desktop. If i can get this phone up and running, i'll sell it and use the money towards a Note 9(USA version). I still have my rooted Nexus 6, and i NEVER had this trouble rooting it. Anyway, i'm done with this for now. If you want, i'll send you the Pixel 2xl, and when you get it working send it back to me, and we'll figure out the compensation. Thanks for trying.

grunt0300 said:
Right now, i'm so confused that i don't know what day it is. I've got files all over my desktop. If i can get this phone up and running, i'll sell it and use the money towards a Note 9(USA version). I still have my rooted Nexus 6, and i NEVER had this trouble rooting it. Anyway, i'm done with this for now. If you want, i'll send you the Pixel 2xl, and when you get it working send it back to me, and we'll figure out the compensation. Thanks for trying.
Click to expand...
Click to collapse
Please follow the step by step guide in my sig.
It explains EVERYTHING from step one all the way through the final reboot.
If your SDK tools are up to date (link provided), and your have multiple USB cables (trust me it's a known, unexplained issue) and you've unzipped the platform tools folder AND unzipped the second platform tool folder (this is the one where you type CMD in the url line) and then follow each step as written, you should have NO problem at all.
If you skip steps or go ahead using your own or another process there's no guarantee, but if you follow the steps in the guide, you should have no problems at all. This guide has been followed by myself and many others with ZERO issues, so I know the written process works.

Az Biker said:
Please follow the step by step guide in my sig.
It explains EVERYTHING from step one all the way through the final reboot.
If your SDK tools are up to date (link provided), and your have multiple USB cables (trust me it's a known, unexplained issue) and you've unzipped the platform tools folder AND unzipped the second platform tool folder (this is the one where you type CMD in the url line) and then follow each step as written, you should have NO problem at all.
If you skip steps or go ahead using your own or another process there's no guarantee, but if you follow the steps in the guide, you should have no problems at all. This guide has been followed by myself and many others with ZERO issues, so I know the written process works.
Click to expand...
Click to collapse
Did i mention that i already have android 10 on the phone?

grunt0300 said:
Did i mention that i already have android 10 on the phone?
Click to expand...
Click to collapse
The guide process works the same for 9x and Android 10.
In the guide, it is stated:
NOTE: On Android 10, when flashing TWRP Installer, kernels, magisk , etc. in TWRP, ignore the warning "FAILED TO MOUNT '/system' (invalid argument) this is a known issue with TWRP + 10 but affects nothing
Once you verify 'fastboot devices' on command prompt
Type flash-all to install factory image (allow it to install, and boot into system)
Hold vol down and power button to boot into bootloader
Fastboot into twrp 3.3.0-0.IMG
Flash the twrp installer 3.3.0-0.ZIP,
Flash Cust Kernel (I use Flash -not supported after 3.19 Nov 2018 or Sultan Kernel or Elemental X (EX) kernel) BE SURE TO SELECT THE CORRECT 9X OR ANDROID 10 KERNEL
Let the system boot up to verify.
Reboot back into twrp and flash latest magisk
Reboot to system
Profit
I guess I'm confused as to why you are simply not just following the guide from step one.........

[GUIDE]UNBRICK NOTE 8 PRO - NO Authorised Service Account - YES Fastboot

Hello everyone.
Yesterday I bricked my Xiaomi Redmi Note 8 Pro, and today I managed to unbrick it without requiring anything special (no need for a Authorized Service Account).
I use Linux, so the scripts inside the Stock ROM end with the .sh file extension. If you're using Windows, use the .bat files.
Phone:
Xiaomi Redmi Note 8 Pro 128GB - Begonia (with NFC).
Bricked state:
Constant boot loop;
No access to bootloader;
No access to system;
Access to fastboot.
Phone requirement:
You must be able to load fastboot mode.
PC requirements:
1. You'll need adb tools (SDK Platform-Tools) to communicate with your phone. Official link is below;
2. Download and unpack the Stock ROM linked below.
Instructions:
1. You need to make sure your phone has some power in it;
2. Unpack the Stock Rom and enter its folder (begonia_global_images_V10.4.2.0.PGGMIXM_20191024.0000.00_9.0_global);
3. Put your phone into fastboot mode (Key Combo: Hold the Power button + Volume Down button until the fastboot logo appears);
4. Connect your phone to your PC;
5. Run the flash_all.* scripts according to your operating system:
5.1. Linux: "./flash_all.sh";
5.2. Windows (untested; I'm not using Windows): Run "flash_all.bat" (How to Run a BAT File on Windows);
6. Wait something between 5min to 10min. It's quite fast, and the flashing process is verbose enough.
7. Profit.
F.A.Q.:
1. How did you find this?
Well, none of the unbrick methods in the forum were working, except for the Authorised Service Account one which I didn' t test. I desperately wanted to unbrick my phone by myself, and I thought that it couldn't get worse (it could with a completely blank screen, but I got away with it).
2. Where did you get the Stock ROM from?
I can't remember. It likely was from a xda forum post but I'm unsure. If I can find the original post containing the Stock ROM I used I'll write it here.
3. Which Miui and Android version did you have prior to the brick?
MIUI Global 11.x + Android 9.
4. Which Miui and Android version does the Stock ROM you installed have?
MIUI Global 10.4.2 + Android 9.
5. Can I install any Stock ROM?
As long as it's compatible with your phone version, yes. I recommend not installing a Android 10 Stock ROM because of this: https://forum.xda-developers.com/showpost.php?p=82743011&postcount=3
6. What if can't enter fastboot mode (phone screen in dead blank)?
You won't be able to unbrick your phone using this method. It is worth trying to enter fastboot mode even though your phone has a dead screen, because fastboot might be working anyway (you'll have to test this yourself, as in trying to load fastboot with a blank screen). Read the next question.
7. How can I test if fastboot mode is working?
"adb devices" returns nothing;
"fastboot devices" returns your device (proof it works). Since "fastboot devices" finds your device, you can run the appropriate scripts.
8. What about your Mi Unlock Status before and after the brick?
Before: Unlocked.
After: Unlocked (I thought it would lock the bootloader again, but it didn't).
9. My phone is bricked and I don't know how much battery my phone has left. What should I do?
You should let it turn off due to 0% battery and charge it fully. I do not recommend you flash like I did, without knowing how much battery I had (yes, I took my chances there). As far as I know, any phone in fastboot mode does not charge its battery.
10. Why is fastboot working in your case?
I don't know. I suspect flashing the preloader and the lk from this OP Redmi Note 8 Pro - The Megathread helped, but it's just a hunch.
11. Will you attempt to flash a Custom ROM again?
After taking a break, yes.
12. Is this phone now unbrickable?
As long as fastboot mode works, perhaps. More feedback is required.
Files:
SDK Platform-Tools (adb/fastboot): https://developer.android.com/studio/releases/platform-tools
Stock ROM used: http://bigota.d.miui.com/V10.4.2.0.PGGMIXM/begonia_global_images_V10.4.2.0.PGGMIXM_20191024.0000.00_9.0_global_270117fdb2.tgz
Feedback:
Due to my job I'm currently very short on time during the week to follow this thread, so it would be immensely helpful to have your feedback on this procedure.
Feedback from people who's phones are bricked with blank screens would be very appreciated, specifically if they can enter fastboot mode without any visual cues from their phones. If any bricked state allows fastboot mode, it seems this phone is easily unbrickable.
Thanks:
strongst for his understanding and in reopening this thread.
Compass.

Thread open again
strongst
Forum Moderator

Hi there,
Is there anyway to fix the hardbrick without the authorized account?? If not how can i find someone to do this for me?

andrewff2 said:
Hi there,
Is there anyway to fix the hardbrick without the authorized account?? If not how can i find someone to do this for me?
Click to expand...
Click to collapse
Yes, if you can access fastboot mode in your phone like I mentioned above. If hardbrick means loss of access to fastboot mode/recovery/system/basically everything, you'll need to find some other unbrick method.
If fastboot mode is working for you, you can unbrick your device by yourself with nothing else than the fastboot command and the Stock ROM. No need for any extra tools/programs.
inb4: The fastboot command is in the SDK Platform-Tools package I linked in the OP.
Compass.

Compass Linux said:
Yes, if you can access fastboot mode in your phone like I mentioned above. If hardbrick means loss of access to fastboot mode/recovery/system/basically everything, you'll need to find some other unbrick method.
If fastboot mode is working for you, you can unbrick your device by yourself with nothing else than the fastboot command and the Stock ROM. No need for any extra tools/programs.
inb4: The fastboot command is in the SDK Platform-Tools package I linked in the OP.
Compass.
Click to expand...
Click to collapse
Yeah i tried this method but fastboot cannot even detect device

andrewff2 said:
Yeah i tried this method but fastboot cannot even detect device
Click to expand...
Click to collapse
That's a shame.
It's worth trying different USB ports, cables etc.
I usually enter fastboot mode first and only then I connect the phone to my PC.
Then "./fastboot devices" and my phone is listed.
Compass.

Compass Linux said:
Yes, if you can access fastboot mode in your phone like I mentioned above. If hardbrick means loss of access to fastboot mode/recovery/system/basically everything, you'll need to find some other unbrick method.
If fastboot mode is working for you, you can unbrick your device by yourself with nothing else than the fastboot command and the Stock ROM. No need for any extra tools/programs.
inb4: The fastboot command is in the SDK Platform-Tools package I linked in the OP.
Compass.
Click to expand...
Click to collapse
Yeah i tried this method but fastboot cannot even detect device in windows appear com5 in Windows but fastboot do nothing just white led that blinks

andrewff2 said:
Yeah i tried this method but fastboot cannot even detect device in windows appear com5 in Windows but fastboot do nothing just white led that blinks
Click to expand...
Click to collapse
I can't give support in this area, but do you have the proper Windows drivers installed?
If you do and it still doesn't work, try a different computer. If you can use a Linux machine somehow it's worth trying. With Linux I didn't need to install anything besides the SDK Platform-Tools package to communicate with my phone.
I think you can unbrick your phone, because fastboot mode is loading (if it's loading it should reply to fastboot commands).
Compass.

Compass Linux said:
I can't give support in this area, but do you have the proper Windows drivers installed?
If you do and it still doesn't work, try a different computer. If you can use a Linux machine somehow it's worth trying. With Linux I didn't need to install anything besides the SDK Platform-Tools package to communicate with my phone.
I think you can unbrick your phone, because fastboot mode is loading (if it's loading it should reply to fastboot commands).
Compass.
Click to expand...
Click to collapse
Thanks for the help man but no the only thing is the white led that sometimes blink nothing more no vibration no sound no screen nothing.....
I'm trying to find someone who can help me with this but no one responds... sad

andrewff2 said:
Thanks for the help man but no the only thing is the white led that sometimes blink nothing more no vibration no sound no screen nothing.....
I'm trying to find someone who can help me with this but no one responds... sad
Click to expand...
Click to collapse
It seems the only solution for you is this (for now): [GUIDE] [begonia] UNBRICK - stuck on DA mode / Authorised Service Account required
Which you've probably read already.
I think you either do that or wait to see if another unbrick method appears.
Compass.

I have the same problem as yours and tried your solution but after i run flash_all.bat it just opens and closes in a split-second and i have no idea whether it works or not. Should I wait a couple of minutes or just try again?

advan93 said:
I have the same problem as yours and tried your solution but after i run flash_all.bat it just opens and closes in a split-second and i have no idea whether it works or not. Should I wait a couple of minutes or just try again?
Click to expand...
Click to collapse
That's not normal.
What you should see are various files being flashed along with their progress meter.
I'm assuming you're double clicking the .bat file. Instead of doing that, open a CMD Prompt and use that instead.
Compass.

Question Bricked my phone, please help!!!

I tried ro go back from beta 13 to public 12 and stuck on fastboot. I tried to sideload from recovery the 13 beta or the 12 version but it said error because i didnt opened the usb debugging before i stucked at fastboot(adb devices not recognize the phone) what can i do??? Please helpppp!!
Edit:Fixed!!

@avivasaf
Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own)

roirraW edor ehT said:
@avivasaf
Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own)
Click to expand...
Click to collapse
I tried it, it said oem unlocking is not checked, go to developer options, which i cant do

@avivasaf There may not be anything you can do to fix it, then. To fool around with Android Betas, you really should unlock the bootloader first so that you have more recovery options. Hopefully, someone else with more experience recovering from such a situation responds with some other ideas.

avivasaf said:
I tried it, it said oem unlocking is not checked, go to developer options, which i cant do
Click to expand...
Click to collapse
Device Unlock Disabled​For security reasons, you need to enable "OEM unlocking" in order to flash your device. See the device preparation instructions for more information.

avivasaf said:
I tried ro go back from beta 13 to public 12 and stuck on fastboot. I tried to sideload from recovery the 13 beta or the 12 version but it said error because i didnt opened the usb debugging before i stucked at fastboot(adb devices not recognize the phone) what can i do??? Please helpppp!!
Click to expand...
Click to collapse
Have you tried going into recovery and then scrolling down to wipe data/factory reset and doing that?

You might be able to sideload the beta again.
get the ota here as some people have claimed USB debugging or OEM unlock is not required to sideload
Boot into recovery (power > volume up > tap volume up when you see the android with an exclamation mark)
Right-click on the downloaded ota.zip and open an terminal in your adb folder (platform tools)
Code:
adb sideload "paste the path here"
It's worth a shot. Good luck

Lughnasadh said:
Have you tried going into recovery and then scrolling down to wipe data/factory reset and doing that?
Click to expand...
Click to collapse
Tried it, didn't help

fil3s said:
You might be able to sideload the beta again.
get the ota here as some people have claimed USB debugging or OEM unlock is not required to sideload
Boot into recovery (power > volume up > tap volume up when you see the android with an exclamation mark)
Right-click on the downloaded ota.zip and open an terminal in your adb folder (platform tools)
Code:
adb sideload "paste the path here"
It's worth a shot. Good luck
Click to expand...
Click to collapse
Its start 0% to sideload and stopped after 1 second"failed", in the phone "success 1"

avivasaf said:
Its start 0% to sideload and stopped after 1 second"failed", in the phone "success 1"
Click to expand...
Click to collapse
I don't understand that one. Sideloading should be possible, you just can't downgrade, should just be able to tap 'apply update from adb' in recovery mode and be good to go.
The first thing one should do when getting an android is enable USB debugging.

fil3s said:
I don't understand that one. Sideloading should be possible, you just can't downgrade, should just be able to tap 'apply update from adb' in recovery mode and be good to go.
The first thing one should do when getting an android is enable USB debugging.
Click to expand...
Click to collapse
I know that, but in my case its to late, any suggestions?

avivasaf said:
I know that, but in my case its to late, any suggestions?
Click to expand...
Click to collapse
I'm sorry mate. It might be a brick. I know its a crappy thing to hear, but it's one of those life lessons learned the hard way I guess.
All I would try to do is remove the device in device manager, install google USB driver in fastboot and try again.

You can try to use Google's flash tool (it's reportedly worked for some with even locked bootloaders) to get a booting device.
Android Flash Tool
flash.android.com
If you can't get your PC to recognize your P6P while it's in bootloader mode, and you're using Google's own USB driver (which is obviously recommended) for Windows, I had this very issue today. I solved it by abandoning the Google driver for clockworkmod's universal adb driver which after installation, allowed my PC to finally recognize my P6P in bootloader mode...

You might have to wait for Official Android 13 to drop with a locked bootlaoder

Fixed!!!
I downloaded the ota file! Not the one that didnt worked from beta program, the ota file could sideload and phone back to life!
After that used android flash tool to return to public Android 12

fil3s said:
You might be able to sideload the beta again.
get the ota here as some people have claimed USB debugging or OEM unlock is not required to sideload
Boot into recovery (power > volume up > tap volume up when you see the android with an exclamation mark)
Right-click on the downloaded ota.zip and open an terminal in your adb folder (platform tools)
Code:
adb sideload "paste the path here"
It's worth a shot. Good luck
Click to expand...
Click to collapse
Your ota file saved me, thanks alot

avivasaf said:
Your ota file saved me, thanks alot
Click to expand...
Click to collapse
I'm kind of confused. That OTA file that was linked to you is the same as the latest official one for A13 Betas. Were you just trying to sideload the wrong OTA file to begin with?
Btw, glad you got it going

Lughnasadh said:
I'm kind of confused. That OTA file that was linked to you is the same as the latest official one for A13 Betas. Were you just trying to sideload the wrong OTA file to begin with?
Btw, glad you got it going
Click to expand...
Click to collapse
There are 2 files the one that call ota is the one that saved me, the other one is the the one from beta program