Database Develop

MI8 Brick

Hi there,
unfortunately I bricked my Mi8 during a ROM Flash. I could not see the options as they were "hidden" because of the resolution of my screen. And unfortunately the standard option seems to be "lock", so it did and now I cannot flash any ROM anymore.
Is the method with opening the phone and get in touch with a doggy service to unlock it still up date?
Is there anything I could do? Will Xiaomi help me if I write them an email?
Help would be much appreciated.

Well, not knowing what you flashed and how you did it, it's hard to give an advice.
Can you boot to recovery, fastboot?
If you want some "output" you have to give more "input".
Is you phone recognized if you connect it to the pc? Perhaps you can revive it with mi flash and a complete rom (tgz). Be aware of the danger of relock!

I know I did a mistake as i flashed it wrong as I did not choose the correct setting (just clean instead of clean and lock). I did not see the options when I did the flash as they were "hidden". The Bootloader is locked and therefore I cannot flash another ROM.
I can get into fastboot, no problem. But I cannot load a ROM (Bootloaderbis locked).
I do wonder if there is any way instead of opening the phone and get in touch with a commercial unlocker service.

berndbrecht said:
I know I did a mistake as i flashed it wrong as I did not choose the correct setting (just clean instead of clean and lock). I did not see the options when I did the flash as they were "hidden". The Bootloader is locked and therefore I cannot flash another ROM.
I can get into fastboot, no problem. But I cannot load a ROM (Bootloaderbis locked).
I do wonder if there is any way instead of opening the phone and get in touch with a commercial unlocker service.
Click to expand...
Click to collapse
Can't you simply use the bootloader unlock tool from MI?

Unfortunately not, it stops at the second point and tells me that this is not connected to my mi account.

berndbrecht said:
Unfortunately not, it stops at the second point and tells me that this is not connected to my mi account.
Click to expand...
Click to collapse
Wipe data and try again. What's the issue with "resolution of screen"?

Why would the wipe help? I guess all data is errased anyway because iIflashed a fastbootrom via mi flasher. The problem was that a portion of the program (mi flasher) was hidden, the part on the bottom where you choose which flashmethod. Therefore standard is lock device and that happened...

berndbrecht said:
Why would the wipe help? I guess all data is errased anyway because iIflashed a fastbootrom via mi flasher. The problem was that a portion of the program (mi flasher) was hidden, the part on the bottom where you choose which flashmethod. Therefore standard is lock device and that happened...
Click to expand...
Click to collapse
I don't think your description of the issue is detailed enough for helping.

What else do you need to know?

berndbrecht said:
What else do you need to know?
Click to expand...
Click to collapse
Just try to unlock bootloader again. If it is not possible, you have to contact with someone who has Xiaomi account authorization.

Yeah, like the s unlock service. I think their my last chance after reading through the internet. Not looking forward to open my phone. pfffff...

berndbrecht said:
Yeah, like the s unlock service. I think their my last chance after reading through the internet. Not looking forward to open my phone. pfffff...
Click to expand...
Click to collapse
I paid 12$ when my previous Redmi 6 pro was relocked after xiaomi.eu update. It is very sad that you must pay for authorization. Shame of Xiaomi.

berndbrecht said:
Yeah, like the s unlock service. I think their my last chance after reading through the internet. Not looking forward to open my phone. pfffff...
Click to expand...
Click to collapse
Is your device a Global or Chinese device and how long ago did you buy it and where from? If the bootloader was unlocked when you attempted to flash whatever you flashed then it was unlocked by someones account. Are you saying that you did not unlock it?
If you did unlock it yourself, then you can unbrick it. If someone else unlock the bootloader you should try contacting that person to get their id and password to unlock the device again, and then you can remove their account from the device and replace it with yours.
Next
Since you have fastboot
You need to download the fastboot rom for whichever device you own. Also, your phone must be clean, you will lose all data.
Mi8 Global Rom: https://c.mi.com/oc/miuidownload/detail?device=1700346
Chinese Mi 8 Rom : http://www.miui.com/download-345.html
Unpack the Rom, on your desktop and then place your phone into EDL Mode or fastboot. - The fastboot Rom comes with the Fastboot flashall script, it will fully restore your phone to the a Stable Rom and Overwrite every partition..
If you unpack the rom and it unzips into a larger version of the rom, unpack the new unpacked larger version, it will unpack into a folder, inside the folder local the flashall.bat file and with the phone connected double click it and wait 5 to 10 minutes until it reboots by itself, you will see the screen to connect to wifi, and then to add you account credentials, enter credentials, enjoy your restored phone.
---------- Post added at 07:29 AM ---------- Previous post was at 07:23 AM ----------
mar.ur said:
I paid 12$ when my previous Redmi 6 pro was relocked after xiaomi.eu update. It is very sad that you must pay for authorization. Shame of Xiaomi.
Click to expand...
Click to collapse
You don't, ( well not anymore) you only pay someone to unlock if you do not have your account bound to the device. The person that you would pay has a vendors master unlocking account, these are very limited and these people are mostly located in Russia and Vietnam.

tsongming said:
Is your device a Global or Chinese device and how long ago did you buy it and where from? If the bootloader was unlocked when you attempted to flash whatever you flashed then it was unlocked by someones account. Are you saying that you did not unlock it?
If you did unlock it yourself, then you can unbrick it. If someone else unlock the bootloader you should try contacting that person to get their id and password to unlock the device again, and then you can remove their account from the device and replace it with yours.
Next
Since you have fastboot
You need to download the fastboot rom for whichever device you own. Also, your phone must be clean, you will lose all data.
Mi8 Global Rom: https://c.mi.com/oc/miuidownload/detail?device=1700346
Chinese Mi 8 Rom : http://www.miui.com/download-345.html
Unpack the Rom, on your desktop and then place your phone into EDL Mode or fastboot. - The fastboot Rom comes with the Fastboot flashall script, it will fully restore your phone to the a Stable Rom and Overwrite every partition..
If you unpack the rom and it unzips into a larger version of the rom, unpack the new unpacked larger version, it will unpack into a folder, inside the folder local the flashall.bat file and with the phone connected double click it and wait 5 to 10 minutes until it reboots by itself, you will see the screen to connect to wifi, and then to add you account credentials, enter credentials, enjoy your restored phone.
---------- Post added at 07:29 AM ---------- Previous post was at 07:23 AM ----------
You don't, ( well not anymore) you only pay someone to unlock if you do not have your account bound to the device. The person that you would pay has a vendors master unlocking account, these are very limited and these people are mostly located in Russia and Vietnam.
Click to expand...
Click to collapse
Hi there,
that brings some light into the darkness, although I am did not completely understood all you wrote.
1. I bought the device used in Germany and it is the German version. It was unlocked and I installed Havoc OS which worked fine. Then I thought I should update Havoc OS and that'S what I did. This ended in a Bootloop. I went into the Recovery and it was kinda weird as it asked me in chinese to enter my pattern. I did and after that the touchscreen stopped working. Still could get into recovery and also install a new one via fastboot. But same problem. Then I googled and as I understood the solution to other people was an earlier MIUI ROM which I installed via the Mi Flash tool and here I am chosing the wrong selection for the flash and ending up in a brick.
2. I don't have the device connected to my MI account. So I guess I need someone with a vendor account? S Unlock also offers a software (one has still to pay) which works without the help of someone logging into and using e.g. Teamviewer. (at least that is their claim)
3. I cannot connect the device with MI flash and therefore no flash of a ROM is possible which brings me to
4. In any case, I for sure have to ****ing open the phone and play with the EDL Touchpoints? Right?
If one has any further ideas let me know, I am really fed up with this ****.

berndbrecht said:
Hi there,
that brings some light into the darkness, although I am did not completely understood all you wrote.
1. I bought the device used in Germany and it is the German version. It was unlocked and I installed Havoc OS which worked fine. Then I thought I should update Havoc OS and that'S what I did. This ended in a Bootloop. I went into the Recovery and it was kinda weird as it asked me in chinese to enter my pattern. I did and after that the touchscreen stopped working. Still could get into recovery and also install a new one via fastboot. But same problem. Then I googled and as I understood the solution to other people was an earlier MIUI ROM which I installed via the Mi Flash tool and here I am chosing the wrong selection for the flash and ending up in a brick.
2. I don't have the device connected to my MI account. So I guess I need someone with a vendor account? S Unlock also offers a software (one has still to pay) which works without the help of someone logging into and using e.g. Teamviewer. (at least that is their claim)
3. I cannot connect the device with MI flash and therefore no flash of a ROM is possible which brings me to
4. In any case, I for sure have to ****ing open the phone and play with the EDL Touchpoints? Right?
If one has any further ideas let me know, I am really fed up with this ****.
Click to expand...
Click to collapse
Okay that better explains your real issue
You had an issue with the lockscreen, which could had been resolved by removing encryption ( formatting user data ) by using ADB or using the Tool All in One. ) Unfortunately, you misunderstood what the issue was and flashed a rom without unchecking unlock bootloader.
Since the bootloader has been relocked, you may need the original account info that unlocked the bootloader. ( If it's still bound to the device) If possible contact the person that you bought the phone from and get their account, then you can use the steps that I listed above by placing the phone into EDL.
If you are asked for a Mi account password, after restoration, then the phone is absolutely still bound to the previous owners account.
You do not necessarily need to open the phone :
You can probably use ADB to place the phone into EDL mode : adb reboot edl
You can use an EDL cable Such as this one
On some phones it is possible to enter EDL by pressing and holding the power button and the volume up and down simultaneously, you can very that the phone is in EDL by connecting it to your PC then go to Control Panel/System/ports <<<< Here you will see port 9008, that means you are in EDL mode.
After installing fastboot rom via flash all.bat method
After connecting to WIFI, you may be asked for the Mi Cloud account (if linked) If so contact the previous owner for that account info, then once the phone has gone through setup, remove the account from the phone in settings/Backup ( It is also possible that the phone is not bound to a account) If no account is linked then you will be able to link a new account and then wait 72 to 360 hours to be able to re-unlock the bootloader.
If the phone is bound to a previous user,
The only option is to use a reputable service company who has a master unlock account. if this is indeed the case, you should try contact Xiaomi and see if they can recommend someplace close to where you live.
@berndbrecht
I just found out via the Mi-Globe website that a XDA member has an official Xiaomi Unlock account and the price is extremely fair: I would suggest contacting @NikSalsa
You can read the same article that I did here : https://mi-globe.com/unbrick-your-xiaomi-phone-without-authorized-mi-account/
Also, there are a couple of additional options listed , if you have trouble reaching NikSalsa

[ROM][STOCK] Stock Firmware Packages (For Expanded EDL Tools)

Stock Firmware Packages
Yes, they are finally here! This thread is for stock firmware packages.
These packages are specifically made to be installed with this EDL tool: https://forum.xda-developers.com/ax...n-10-pro-5g-expanded-edl-tools-fixes-t4174667
READ THE WARNINGS IN THAT THREAD BEFORE USING THE TOOLS
These packages are UNOFFICIAL unless marked otherwise. ZTE has not released stock firmware packages for most phones and versions.​
How to install an EDL firmware package:
Note: These packages are specifically made for the EDL tools, not MiFlash or anything else.
1. Install the latest version of the EDL tools (in this thread)
2. Download a firmware package from this thread.
3. Unpack the firmware archive into the tool directory "Firmware_Package_Restore"
Make sure you unpack the firmware into Firmware_Package_Restore directory like this -​Just for example - the script would be located in:​"...\Axon10_(More)_EDL_Tools_v1_1b\Firmware_Package_Restore\Write Firmware v1.10 to A.ps1"​And the firmware files would be in:​"...\Axon10_(More)_EDL_Tools_v1_1b\Firmware_Package_Restore\firmware_1_10\"​4. Put phone in EDL mode and run Load Programmer
5. Run a backup of your phone! Even if it isn't booting.
6. Run whichever "Write Firmware vX to Y.ps1" you want (X = firmware version, Y = A or B partition) (If you don't know which partition is currently booting, just install both.)
7. Wait for the install to finish ("done")
8. Start the phone (hold the power button until it resets, or run the Reset script)
9. You might see a few bootloops and then the phone ask you to do a factory reset / system wipe.
10. If the phone does not boot - look in the tools thread for how to use the Fix Bootable tool and try that.
11. Done.
Firmware Package Downloads:
~~~ A2020U (US Version) (Non-5G) ~~~
Firmware Version: 1.10 (GEN_NA_A2020U_PROV1.10)
Android: 9 (Pie)
Source: UNOFFICIAL (bobthenormal)
Download: Axon10Pro A2020U EDL Firmware v1.10(A9)
(If you downloaded this firmware before 12/9/2020 the script had an error, re-download the firmware or simply replace the script files with these ones: Firmware 1.10 Script Fix)
Thanks:
@djkuz for the original EDL tool for Axon 7
@Unjustified Dev for his port of the tool and tons of other work
@rafyvitto for a ton of ROMs and his stock B12 backup
and @eKeith for requesting the firmware enough times I finally bothered to make it =P

Please keep issues with the firmware here, and issues with the EDL tools in that thread.
I will upload firmware versions for A2020U: 1.11, 1.13, 2.09 (A10) (locked and unlocked). I just need to get time to actually test these out to make sure they work.
I didn't test the 1.10 version either but it should work and some people are stuck on A10 without it so I'm trying to post it quickly.
If anyone can wants the tools or firmware packages like these for their phone version (EU, CN, whatever non-A2020U Non-5G) and can volunteer their phone/time, PM me - I can't do them myself as I don't have those phones, but I can give safe instructions on what to do so that I can change make a version of the tools for those phones.

Hi i want the Firmware for zte axon 10 pro 5g 6ram
Details in photo
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Axon 10 Pro (Non-5G) EDL Tool - Flash / Backup / Restore/ Bootloader Unlock
Axon 10 EDL Tool BAT-program for Flash / Backup / Restore/ Bootloader Unlock Qualcomm HS-USB QDLoader 9008 (COM ...) !!! Whatever you do, you do at your own risk !!!" !!! If you are not sure of yourself do not use this program !!! Special...
forum.xda-developers.com
My post

amooor said:
Hi i want the Firmware for zte axon 10 pro 5g 6ram
Details in photo
View attachment 5146295
Axon 10 Pro (Non-5G) EDL Tool - Flash / Backup / Restore/ Bootloader Unlock
Axon 10 EDL Tool BAT-program for Flash / Backup / Restore/ Bootloader Unlock Qualcomm HS-USB QDLoader 9008 (COM ...) !!! Whatever you do, you do at your own risk !!!" !!! If you are not sure of yourself do not use this program !!! Special...
forum.xda-developers.com
My post
Click to expand...
Click to collapse
I'd suggesta new thread. I haven't seen anyone with that phone or a firmware package for it. If you can find someone that has your phone with stock firmware who is willing to do a little work, I'll tell them what to do to make it.

bobthenormal said:
I'd suggesta new thread. I haven't seen anyone with that phone or a firmware package for it. If you can find someone that has your phone with stock firmware who is willing to do a little work, I'll tell them what to do to make it.
Click to expand...
Click to collapse
Am sure 100% the problem is Firmware.
Do you know why because the holder tray for your ZTE Axon 10 Pro 5g in my phone is making for 1 sim like oneplus 7t in t-mobile if you unlocked and change the holder tray to hybrid dual sim it will work

Hello, I tried to use your tools to restore my phone since its on the European version and my sim card doesn't work (its US). The Write Firmware v1.10 to A tells me that COMPort is not found even though I already launched the load programmer script and see a COMPort file in the folder. Any ideas on what I can do? Thank you for your time!

los95 said:
Hello, I tried to use your tools to restore my phone since its on the European version and my sim card doesn't work (its US). The Write Firmware v1.10 to A tells me that COMPort is not found even though I already launched the load programmer script and see a COMPort file in the folder. Any ideas on what I can do? Thank you for your time!
Click to expand...
Click to collapse
Make sure you unpack the firmware into Firmware_Package_Restore directory like this -
Just for example - the script would be located in:
"...\Axon10_(More)_EDL_Tools_v1_1b\Firmware_Package_Restore\Write Firmware v1.10 to A.ps1"
And the firmware files would be in:
"...\Axon10_(More)_EDL_Tools_v1_1b\Firmware_Package_Restore\firmware_1_10\"

bobthenormal said:
Make sure you unpack the firmware into Firmware_Package_Restore directory like this -
Just for example - the script would be located in:
"...\Axon10_(More)_EDL_Tools_v1_1b\Firmware_Package_Restore\Write Firmware v1.10 to A.ps1"
And the firmware files would be in:
"...\Axon10_(More)_EDL_Tools_v1_1b\Firmware_Package_Restore\firmware_1_10\"
Click to expand...
Click to collapse
Thanks for the response! I will try it on Tuesday as I have finals. Will update to see what happens.

Okay I tried it again with the steps and now its giving me this.
https://pastebin.com/LwbK3vf7
It tells me that it can't find the files even though I have put the folder in that directory. Sorry for being ignorant I thought this wouldn't be too bad since I used to root Samsung devices.
Update:
I downloaded the new version of the edl tools and it still can't find the firmware files. Here is the log.
https://pastebin.com/LRuXEx0y
Another Update:
Sorry for the updates just wanted to see if I can fix it but I figured out why it didn't find the files.
For some reason, it would try to find the files inside the Firmware_Package_Restore instead of its own folder.
Now, I am getting another error that is says that my device is not on the port although I put it in edl mode. Perhaps I am doing something wrong? Here is another log with this error.
https://pastebin.com/ZtXwhUB0

los95 said:
Okay I tried it again with the steps and now its giving me this.
https://pastebin.com/LwbK3vf7
It tells me that it can't find the files even though I have put the folder in that directory. Sorry for being ignorant I thought this wouldn't be too bad since I used to root Samsung devices.
Update:
I downloaded the new version of the edl tools and it still can't find the firmware files. Here is the log.
https://pastebin.com/LRuXEx0y
Another Update:
Sorry for the updates just wanted to see if I can fix it but I figured out why it didn't find the files.
For some reason, it would try to find the files inside the Firmware_Package_Restore instead of its own folder.
View attachment 5152479
Now, I am getting another error that is says that my device is not on the port although I put it in edl mode. Perhaps I am doing something wrong? Here is another log with this error.
https://pastebin.com/ZtXwhUB0
Click to expand...
Click to collapse
Hey! Thanks for attaching the log, that was perfect for finding the issue right away. The script is building the search_path incorrectly, here's corrected copies of the scripts. I'll update and re-upload the full firmware zip file as soon as I get a chance, but just replace the ones you have with these.
EDIT: Ah, yes hold on I'll take a look at the second issue. Sorry about that, didn't have a chance to test these.
So, the new problem appears to be something with the COM port communication. I have to get going in a minute but a few suggestions to try:
Reboot your phone into EDL then run the loader/firmware scripts right away. Sometimes the ports kind of time out.
Open Device Manager in windows and open the "Ports" list and make sure you see your phone on there. Edit the COMPort file to have the right one, or delete it to force the script to re-check if it's trying to connect to the wrong one.
Check the drivers - the tools have the stock A2020U drivers included, might need to reinstall them especially if you install drivers for other phones.
See if any of those help, let me know how it goes.

bobthenormal said:
Hey! Thanks for attaching the log, that was perfect for finding the issue right away. The script is building the search_path incorrectly, here's corrected copies of the scripts. I'll update and re-upload the full firmware zip file as soon as I get a chance, but just replace the ones you have with these.
EDIT: Ah, yes hold on I'll take a look at the second issue. Sorry about that, didn't have a chance to test these.
So, the new problem appears to be something with the COM port communication. I have to get going in a minute but a few suggestions to try:
Reboot your phone into EDL then run the loader/firmware scripts right away. Sometimes the ports kind of time out.
Open Device Manager in windows and open the "Ports" list and make sure you see your phone on there. Edit the COMPort file to have the right one, or delete it to force the script to re-check if it's trying to connect to the wrong one.
Check the drivers - the tools have the stock A2020U drivers included, might need to reinstall them especially if you install drivers for other phones.
See if any of those help, let me know how it goes.
Click to expand...
Click to collapse
Thanks I will try this.
Edit:
I ended up deleting the com port file, ran Load Programmer, and the scripted worked. However, when it finished and I go back to boot my phone (I had to use the other edl tool and asked it to unlock the google FRP since I don't know another method to boot it back to normal) it boot back to the old rom it had. Its like it didn't write anything to the phone although the script did show me it was doing its job and end with a success. Any ideas? Here is my phone with the same firmware still installed after using the script.
Update:
I decided to use the write firmware to b instead and now it is American. Thank you for all the hard work I thought I had to carry two phones with me everywhere lol. Now I have another question. When I reboot my phone, a message pops up saying that the phone is unlocked and to either press the power button to pause or continue. I read in the threads that this means that fast boot is disabled. Is there anyway I can get fast boot back?

los95 said:
Thanks I will try this.
Edit:
I ended up deleting the com port file, ran Load Programmer, and the scripted worked. However, when it finished and I go back to boot my phone (I had to use the other edl tool and asked it to unlock the google FRP since I don't know another method to boot it back to normal) it boot back to the old rom it had. Its like it didn't write anything to the phone although the script did show me it was doing its job and end with a success. Any ideas? Here is my phone with the same firmware still installed after using the script.
View attachment 5153355
Update:
I decided to use the write firmware to b instead and now it is American. Thank you for all the hard work I thought I had to carry two phones with me everywhere lol. Now I have another question. When I reboot my phone, a message pops up saying that the phone is unlocked and to either press the power button to pause or continue. I read in the threads that this means that fast boot is disabled. Is there anyway I can get fast boot back?
Click to expand...
Click to collapse
Nice! Super glad that it worked.
That A/B issue is why I considered just making the script automatically install it to both A and B. The only way I can tell which side is booting is to go into fastboot, which I find annoying. But if you install a ROM to A while you're booting from B, you won't see it obviously, so I generally just flash both sides at the same time since I always have full backups of both anyway.
As for that message, it sort-of means fastboot is disabled - it pops up when:
1. the bootloader is unlocked
AND
2. the stock bootloader is installed
So to get rid of the message you can either re-lock the phone OR install Unjustified Dev's patched bootloader. And since the stock bootloader does not have fastboot, the only way to have it is to install the unlocked bootloader.
You can do that either through the old tool ("unlock" the phone again), or through mine by running "write_UD-bootloader.ps1" in the Write_Unlocked_Bootloader_and_FRP folder.

bobthenormal said:
Nice! Super glad that it worked.
That A/B issue is why I considered just making the script automatically install it to both A and B. The only way I can tell which side is booting is to go into fastboot, which I find annoying. But if you install a ROM to A while you're booting from B, you won't see it obviously, so I generally just flash both sides at the same time since I always have full backups of both anyway.
As for that message, it sort-of means fastboot is disabled - it pops up when:
1. the bootloader is unlocked
AND
2. the stock bootloader is installed
So to get rid of the message you can either re-lock the phone OR install Unjustified Dev's patched bootloader. And since the stock bootloader does not have fastboot, the only way to have it is to install the unlocked bootloader.
You can do that either through the old tool ("unlock" the phone again), or through mine by running "write_UD-bootloader.ps1" in the Write_Unlocked_Bootloader_and_FRP folder.
Click to expand...
Click to collapse
Thanks for the great help. Now I have installed twrp and will most likely just put magisk and keep the stock rom as I am now terrified on installing a custom rom since it lead to me to a lot of trouble. Maybe I will touch lineage later on but for now I will just have twrp and root.

los95 said:
Thanks for the great help. Now I have installed twrp and will most likely just put magisk and keep the stock rom as I am now terrified on installing a custom rom since it lead to me to a lot of trouble. Maybe I will touch lineage later on but for now I will just have twrp and root.
Click to expand...
Click to collapse
You're welcome!
I wouldn't be afraid of doing custom roms once you do a full backup of your working phone with my tools! If you have the 256gb phone you can add the userdata backup to that and really have everything including settings, apps, and data. Then if anything goes wrong you just do a full restore back to exactly where you were.
I haven't been trying custom ROMs because I just don't have the hours to spend trying them out and re-configuring each one to find out which I want to use, otherwise I definitely would. The stock ROM is really kinda poop (I'm on A10).
Also, if you try flashing a custom ROM and it doesn't boot after you install it - before assuming it didn't work and restoring, FIRST try the "Fix bootable" tool. Some ROMs get installed to a different partition than they were made from, so they have that flag for which partition they think they are installed on. When it doesn't match it won't boot. Good luck!

bobthenormal said:
You're welcome!
I wouldn't be afraid of doing custom roms once you do a full backup of your working phone with my tools! If you have the 256gb phone you can add the userdata backup to that and really have everything including settings, apps, and data. Then if anything goes wrong you just do a full restore back to exactly where you were.
I haven't been trying custom ROMs because I just don't have the hours to spend trying them out and re-configuring each one to find out which I want to use, otherwise I definitely would. The stock ROM is really kinda poop (I'm on A10).
Also, if you try flashing a custom ROM and it doesn't boot after you install it - before assuming it didn't work and restoring, FIRST try the "Fix bootable" tool. Some ROMs get installed to a different partition than they were made from, so they have that flag for which partition they think they are installed on. When it doesn't match it won't boot. Good luck!
Click to expand...
Click to collapse
Thanks for the tip! I forgot to mention something strange about the reset from edl tool. When I was turning my phone back to American, I tried to use that and it gave me an error saying this
{ERROR: Command line argument 'reset=' is not recognized as a valid option}
On the shell window it shows different options and there is one that says reset but without = sign. I'm not sure if its some typo but wanted to let you know.

los95 said:
Thanks for the tip! I forgot to mention something strange about the reset from edl tool. When I was turning my phone back to American, I tried to use that and it gave me an error saying this
{ERROR: Command line argument 'reset=' is not recognized as a valid option}
On the shell window it shows different options and there is one that says reset but without = sign. I'm not sure if its some typo but wanted to let you know.
Click to expand...
Click to collapse
Ah that is weird! I must have forgot to save some changes to that script, it's supposed to use the XML file. Fixed that and threw on a script with a long delay ( version 1.1d now)
Thanks for pointing that out.. my quality control guy is slacking! (I'm the quality control guy...)
Lemme know if you find any other ones.

bobthenormal said:
Ah that is weird! I must have forgot to save some changes to that script, it's supposed to use the XML file. Fixed that and threw on a script with a long delay ( version 1.1d now)
Thanks for pointing that out.. my quality control guy is slacking! (I'm the quality control guy...)
Lemme know if you find any other ones.
Click to expand...
Click to collapse
Sorry for all the replies I just want to be sure everything is fine with the backup tool. I did the full back up and it looks like it worked but I was getting warnings that the files it was looking for returned as null. Is that supposed to happen? Here is the link with the log.
backup_all log - Pastebin.com

los95 said:
Sorry for all the replies I just want to be sure everything is fine with the backup tool. I did the full back up and it looks like it worked but I was getting warnings that the files it was looking for returned as null. Is that supposed to happen? Here is the link with the log.
backup_all log - Pastebin.com
Click to expand...
Click to collapse
Oh whew, you scared me if there was a problem with backup_all
That's the one I was especially careful about since I got burned by the original EDL backup tool.
No worries about bringing up potential issues, I can't guarantee the tools don't mess up anyone's phone but I'd still feel terrible if they did so I appreciate the "bug testing".
The warnings there are all good even though they look scary.
If you look in the log, you see the files are attempt to read (and returned NULL) first, then once it has gone through all of them it repeats the list. The way the EDL interface works is kind of odd. It doesn't take a "read" command, it takes a "write" command "reversed", so it executes it like a write command sort of. That means it looks for the files to "write" first to prepare, even though it doesn't actually use them (except to overwrite them if they do exist).
It makes sense from a programming perspective, efficient and saves ROM.

Hi, I am back again. Magisk had an update and after it was installed, the phone wouldn't boot up anymore. It just stayed at the bootloader and I had to wipe it and installed the original firmware as for some unknown reason, my backup is not there. I tried using the restore tool and it couldn't find my back up. I checked the specific files folders to see if the backup was there and nothing was found. The good thing is that the phone can be brought back life even if I have to start fresh ( I don't mind it to be honest since I don't use a lot of apps). This inspired me to install lineage but the link on that thread is broken. Someone asked the OP of the thread about it but I think he hasn't been active for a while. Do you by any chance have the lineage rom file? Sorry for asking but I don't know where to look. Thanks for reading!

los95 said:
Hi, I am back again. Magisk had an update and after it was installed, the phone wouldn't boot up anymore. It just stayed at the bootloader and I had to wipe it and installed the original firmware as for some unknown reason, my backup is not there. I tried using the restore tool and it couldn't find my back up. I checked the specific files folders to see if the backup was there and nothing was found. The good thing is that the phone can be brought back life even if I have to start fresh ( I don't mind it to be honest since I don't use a lot of apps). This inspired me to install lineage but the link on that thread is broken. Someone asked the OP of the thread about it but I think he hasn't been active for a while. Do you by any chance have the lineage rom file? Sorry for asking but I don't know where to look. Thanks for reading!
Click to expand...
Click to collapse
Damn that's not good. You checked in the Backup tool folder for the backups?
They would be named "backup_all-critical-(date/time)" and "backup_all-non-critical-(date/time)"
The Restore tool doesn't automatically try to find backups, you have to move the backup files you want to restore into the restore directories (critical to critical, non-critical to non-critical).
It's not super user friendly, but it's a ton of extra work to make it search for backups and pop up a menu and such. Hopefully that's the issue, but if not I'd like to know if you figure out why the backups aren't there.
I *think* I have the lineage ROM... but I can't upload it right now, on slow internet! Might be a few weeks before I get back, if rafy hasn't uploaded it by then I'll upload it.
Also, the magisk update - I've had that happen on several phones too where it tries to update itself and bricks, so I'm really careful about when I do updates. Not sure if there's a safe method, maybe uninstalling magisk and reinstalling the new version.

.

Question [CLOSED] Pls help to fix: dm-verify corruption

For my Redmi Note 10 5G bought from Vodafone UK, initially I used Xiaomi Tool V2 (https://www.xiaomitool.com/V2/) to install the ROM, but it failed with error. After that any power on/reboot shows this error:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then I went into Fastboot and used MiFlash tool to install a ROM, that installed successfully. But each time I reboot (or fresh power on) I get the above error and the phone switches off itself. But if I press the power on within the 5 seconds, it will power on and then the phone works fine.
Although the phone works fine, any reboot doesn't work automatically, I need to press power button within 5 seconds for it to work.
Now my question is how to fix the error in the screenshot?

fm663 said:
For my Redmi Note 10 5G bought from Vodafone UK, initially I used Xiaomi Tool V2 (https://www.xiaomitool.com/V2/) to install the ROM, but it failed with error. After that any power on/reboot shows this error:
View attachment 5458547
Then I went into Fastboot and used MiFlash tool to install a ROM, that installed successfully. But each time I reboot (or fresh power on) I get the above error and the phone switches off itself. But if I press the power on within the 5 seconds, it will power on and then the phone works fine.
Although the phone works fine, any reboot doesn't work automatically, I need to press power button within 5 seconds for it to work.
Now my question is how to fix the error in the screenshot?
Click to expand...
Click to collapse
Try with:
adb disable-verity
or flashing blank/null vbmeta:
fastboot --disable-verity flash vbmeta vbmeta.img or:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash vbmeta vbmeta.img

@SubwayChamp Thank you for help. However I am getting this error:
adb disable-verity
verity cannot be disabled/enabled - USER build​
If I were do do the fastboot commands, will it wipe out the ROM+data in the phone (Note I have already been using it for last 1-2 weeks)? Also where to get the vbmeta.img file?

fm663 said:
@SubwayChamp Thank you for help. However I am getting this error:
adb disable-verity
verity cannot be disabled/enabled - USER build​
If I were do do the fastboot commands, will it wipe out the ROM+data in the phone (Note I have already been using it for last 1-2 weeks)? Also where to get the vbmeta.img file?
Click to expand...
Click to collapse
This vbmeta will work https://forum.xda-developers.com/attachments/vbmeta-tar.5065875/ (unzip it) not sure if this solves it, but it is worth the try. And not, flashing the vbmeta won't wipe your data.
I guess your device is unlocked, or maybe you did try to flash something unofficial on it being locked?, what happened prior to this appear?

SubwayChamp said:
This vbmeta will work https://forum.xda-developers.com/attachments/vbmeta-tar.5065875/ (unzip it) not sure if this solves it, but it is worth the try. And not, flashing the vbmeta won't wipe your data.
I guess your device is unlocked, or maybe you did try to flash something unofficial on it being locked?, what happened prior to this appear?
Click to expand...
Click to collapse
Initially I unlocked the phone, then installed Indonesian ROM from Xiaomi website and locked it back.
Does the phone need to be unlocked again?

fm663 said:
Initially I unlocked the phone, then installed Indonesian ROM from Xiaomi website and locked it back.
Does the phone need to be unlocked again?
Click to expand...
Click to collapse
Yes, of course, this is why the warning message is appearing. In the other hand you were lucky to not brick your device, be careful not all the firmwares are interchangeable, specifically the Chinese, to be locked.
I mean, if you only are interested in this message to disappear, you should install again the same ROM that your device was in, but the Indonesian ROM is more attractive over the Global ROM despite the bloatware that can be uninstalled easily.

SubwayChamp said:
Yes, of course, this is why the warning message is appearing. In the other hand you were lucky to not brick your device, be careful not all the firmwares are interchangeable, specifically the Chinese, to be locked.
I mean, if you only are interested in this message to disappear, you should install again the same ROM that your device was in, but the Indonesian ROM is more attractive over the Global ROM despite the bloatware that can be uninstalled easily.
Click to expand...
Click to collapse
Yes, it is the best ROM for my requirements, except I couldn't get Dual Apps to work in it. Do you know how to?
As I want to use Google Pay + NFC, thus I need it locked.
Problem now is I'll loose all data and its time consuming to install everything all over again.
Maybe I'll leave with this error as is for now, unless I find an easier way

fm663 said:
Yes, it is the best ROM for my requirements, except I couldn't get Dual Apps to work in it. Do you know how to?
As I want to use Google Pay + NFC, thus I need it locked.
Problem now is I'll loose all data and its time consuming to install everything all over again.
Maybe I'll leave with this error as is for now, unless I find an easier way
Click to expand...
Click to collapse
Strange, I used Dual apps in my RN8 exactly in Indonesian ROM (I switched from global because of the absence of Phone and Message native apps) although you are fear to, probably you need to format data in order that can work.
There are some workarounds in the Magisk thread to use GPay and NFC, although rooted.
I don't think there is an easy way because of locked bootloader.

SubwayChamp said:
Strange, I used Dual apps in my RN8 exactly in Indonesian ROM (I switched from global because of the absence of Phone and Message native apps) although you are fear to, probably you need to format data in order that can work.
There are some workarounds in the Magisk thread to use GPay and NFC, although rooted.
I don't think there is an easy way because of locked bootloader.
Click to expand...
Click to collapse
I did not know it is possible to get GPay+NFC to work while rooted. Do you not get CTS Profile mismatch error this way?

fm663 said:
I did not know it is possible to get GPay+NFC to work while rooted. Do you not get CTS Profile mismatch error this way?
Click to expand...
Click to collapse
actually all you have been asking has been discussed already, we are all busy but at least spend 10 minutes searching, vbmeta, dm-verity, nfc+Google pay all well discussed already, please spend 10 minutes by searching

simika said:
actually all you have been asking has been discussed already, we are all busy but at least spend 10 minutes searching, vbmeta, dm-verity, nfc+Google pay all well discussed already, please spend 10 minutes by searching
Click to expand...
Click to collapse
Thank you for the tips.
Maybe I am not good at searching. I have many days of searching over the last few months and did not find the answers. I have another phone Mi Mix 2 that is unlocked and few things don't work in it due to CTS Profile issue. I would like to get that fixed too. Can you point to me specific pages please? Thank you

fm663 said:
Thank you for the tips.
Maybe I am not good at searching. I have many days of searching over the last few months and did not find the answers. I have another phone Mi Mix 2 that is unlocked and few things don't work in it due to CTS Profile issue. I would like to get that fixed too. Can you point to me specific pages please? Thank you
Click to expand...
Click to collapse
sure:
ROOT GAINED !!!!
THIS METHOD WORKS on both: POCO M3 Pro / Redmi Note 10 5G hey guys.. wonderful news.. been trying here and there and IT WORKS FINALLY i gained root of POCO m3 Pro 5G ! i'll write in steps how it works and post all files i've been using...
forum.xda-developers.com
here you'll find answers about root, dm-verity and much more, always related to poco m3 pro and redmi note

fm663 said:
I did not know it is possible to get GPay+NFC to work while rooted. Do you not get CTS Profile mismatch error this way?
Click to expand...
Click to collapse
If you want to stay locked no way to disable this warning message but if you decide to unlock your device and root it, it is pretty easy to fix it, one of the methods available is what I indicated, flashing a blank/null vbmeta through specific fastboot commands, there are other methods though, but this is the most universal and easy to use.
In regard to the CTS issue, I don't use GPay, so I can't tell you, but no better place that the Magisk Discussion Thread, it is the appropriate thread where you can find all the info from all the members affected on that, in the meantime you also can take a read on this https://droidholic.com/fix-safetynet-failed-cts-profile-false/

1. Hello friends, there are two ways to fix this problem. First, you need Root, and after using Root, you need to download any file manager and give Root permission. You need to backup your baseband, nvram nvdata nvcfg after backup Save, you also need an MTK Bypass You can search for MTK Auth Bypass Tool through Google. To download, you also need to use SP Flash to flash the machine. You need to download the official firmware package. You can download it through xiaomirom.com, download the corresponding version, and use SP Flash to read your firmware package, after the reading is completed, choose to format all and download, wait for the completion, press the power button after completion, you will find that the error has disappeared, but the baseband is lost, but you have backed up. Boot through fastboot to unlock the BL lock, and proceed fastboot flash nvram ....... fastboot flash nvdata ....... fastboot flash nvcfg ....... Fastboot reboot reboot. congratulations your baseband is back, i am a newbie and my instructions are very Not comprehensive, such as where is the baseband position, but I have too many characters, I will list the baseband position. 2. Replace a new motherboard, all mobile phone problems are solved.
Hope to help you.

THREAD LOCKED
As per the Forum Rules:
5. Create a thread topic or post a message only once, this includes external links & streaming media.
-snip-
-snip-
Duplicate threads and posts will be removed
Always post in an existing thread if a topic already exists, before creating a new thread.
-snip-
Click to expand...
Click to collapse
Please search the forum for existing/similar threads before posting a new thread. For continuing discussion, kindly use the existing thread: https://forum.xda-developers.com/t/how-to-get-rid-of-dm-verity-corruption-on-boot.4290677/
Regards,
shadowstep
Forum Moderator

Question I have a note 10 pro With a Mi account lock

I got this phone as a gift from my relative but its MI account locked(xiaomi frp) so I cant use it and my relatives just don't have access to their old account and phone number so I have no way of accessing the mi page and unlocking from there so anyone have a way to bypass this FRP or remove it? Please any help would be appreciated cuz I really need a phone and this would be very useful

Seeing some YouTube video suggestions. I wonder if there is a system app that can be updated via ADB that could resolve it?

Sheist! said:
Seeing some YouTube video suggestions. I wonder if there is a system app that can be updated via ADB that could resolve it?
Click to expand...
Click to collapse
I dont think i can access ADB cuz the phone is on the "this device is locked" screen (the Mi account lock)

Sheist! said:
Seeing some YouTube video suggestions. I wonder if there is a system app that can be updated via ADB that could resolve it?
Click to expand...
Click to collapse
so yea as in that video I cant access the setup I only have a black screen with that locked device thing

Qiikzx said:
so yea as in that video I cant access the setup I only have a black screen with that locked device thing
Click to expand...
Click to collapse
MI account locked, or Google account locked? You can delete the Google account from the phone. You can wipe the ROM via Fastboot and reinstall it using a stock image source, then get a fresh shot at logging into MIUI, but not sure it is required. You have to type in the account details, it isn't automatic. I did it to unlock it but now I see it no longer is logged in. My suspicion is because of system updates, etc.

Google frp is simple to remove, As for Mi Account, seems to be happening a lot on here, surely the previous owner wouldve removed his details and accounts and reset the phone before passing on or selling. NOT saying yours is, but this usually very common with found or stolen phones, hence the need for security. If its Mi account locked your probably going to have to get in touch with Xiaomi and maybe pay for a service center to do it, but they absolutley will want proof of purchase or gift to ensure it is what it is and indeed not a stolen phone.

gazza35 said:
Google frp is simple to remove, As for Mi Account, seems to be happening a lot on here, surely the previous owner wouldve removed his details and accounts and reset the phone before passing on or selling. NOT saying yours is, but this usually very common with found or stolen phones, hence the need for security. If its Mi account locked your probably going to have to get in touch with Xiaomi and maybe pay for a service center to do it, but they absolutley will want proof of purchase or gift to ensure it is what it is and indeed not a stolen phone.
Click to expand...
Click to collapse
I see a lot of this in phones donated to charity. They don't know or forget to remove and this happens.

RAMBO29 said:
I see a lot of this in phones donated to charity. They don't know or forget to remove and this happens.
Click to expand...
Click to collapse
Places like CEX in the UK now wont buy 2nd hand phones unless thats been dealt with or icloud locked Iphones, but you are right, if someone is passing on a phone they really need to make sure all associated ownership is removed, Xiaomi compared to others seems to be an issue getting it resolved.

RAMBO29 said:
I see a lot of this in phones donated to charity. They don't know or forget to remove and this happens.
Click to expand...
Click to collapse
Yeah i got it as charity kind of cuz my cousin gave his and he lost all his stuff on it so he has no way of recovering the phone for me

Sheist! said:
MI account locked, or Google account locked? You can delete the Google account from the phone. You can wipe the ROM via Fastboot and reinstall it using a stock image source, then get a fresh shot at logging into MIUI, but not sure it is required. You have to type in the account details, it isn't automatic. I did it to unlock it but now I see it no longer is logged in. My suspicion is because of system updates, etc.
Click to expand...
Click to collapse
Yea no its MI account locked sadly, if it was google account locked I would've dealt with it much more easily also my Fastboot is locked

Qiikzx said:
Yea no its MI account locked sadly, if it was google account locked I would've dealt with it much more easily also my Fastboot is locked
Click to expand...
Click to collapse
I assume you can't get into Recovery either? Any Xiaomi-created desktop tool will want you to log in. If it allows that, you could use different Xiaomi credentials. I know there is an ADB/Fastboot Xiaomi desktop tool but no experience if it will get you through a locked Fastboot.

Sheist! said:
I assume you can't get into Recovery either? Any Xiaomi-created desktop tool will want you to log in. If it allows that, you could use different Xiaomi credentials. I know there is an ADB/Fastboot Xiaomi desktop tool but no experience if it will get you through a locked Fastboot.
Click to expand...
Click to collapse
No I can go to recovery and ADB sideload also works

Qiikzx said:
No I can go to recovery and ADB sideload also works
Click to expand...
Click to collapse
Oh. Try wiping data, i.e. phone reset. If that doesn't help, it might be one of the system apps holding the Xiaomi acct. Since you can use ADB, that gives you a full ROM install capability. External SD will help for that. I do not have the ADB syntax handy. I have done this myself, but Googling will help. Recovery might allow you to connect to ADB via your PC, as well. You can isolate which Xiaomi app handles account verification and you could first try updating or removing it or wiping its data via ADB. The "Xiaomi ADB/Fastboot tools.jar" shows all the ADB features it does manually, for which you can use ADB manually. Be prepared to update your desktop java/jre if you get an error launching the .jar with a double-click. You can also reveal the complete ADB syntax. The syntax includes "adb shell" plus other required syntax commands in an Admin command prompt. Google is your friend. Good luck.

Sheist! said:
Oh. Try wiping data, i.e. phone reset. If that doesn't help, it might be one of the system apps holding the Xiaomi acct. Since you can use ADB, that gives you a full ROM install capability. External SD will help for that. I do not have the ADB syntax handy. I have done this myself, but Googling will help. Recovery might allow you to connect to ADB via your PC, as well. You can isolate which Xiaomi app handles account verification and you could first try updating or removing it or wiping its data via ADB. The "Xiaomi ADB/Fastboot tools.jar" shows all the ADB features it does manually, for which you can use ADB manually. Be prepared to update your desktop java/jre if you get an error launching the .jar with a double-click. You can also reveal the complete ADB syntax. The syntax includes "adb shell" plus other required syntax commands in an Admin command prompt. Google is your friend. Good luck.
Click to expand...
Click to collapse
uh no u cant install anything like twrp from the sideload(its not a full access adb)

Google should have some suggestions if someone else has an idea. I can't picture just sideload without full adb capability. Use an admin command prompt on your PC. Perhaps some info on how/why it became locked this way, even if the original owner can't or won't help, via Googling I mean. If some security feature in the phone was trippped, it might be intentional to keep you from using it, but I find it really hard to believe non-nubes can't just crack it.

Sheist! said:
Google should have some suggestions if someone else has an idea. I can't picture just sideload without full adb capability. Use an admin command prompt on your PC. Perhaps some info on how/why it became locked this way, even if the original owner can't or won't help, via Googling I mean. If some security feature in the phone was trippped, it might be intentional to keep you from using it, but I find it really hard to believe non-nubes can't just crack it.
Click to expand...
Click to collapse
The protection is there for a good reason, for both the owner and Xiaomi.
You can access EDL but you still need Xiaomi authorized service account to do anything in there. There's nothing you could do except go to Xiaomi service center along with complete materials of ownership that the real owner really cannot unlock it.
Some illegal box might be able to reset it via EDL, but beware their method is never guarantee worked and it might totally brick the phone.

Qiikzx said:
Yeah i got it as charity kind of cuz my cousin gave his and he lost all his stuff on it so he has no way of recovering the phone for me
Click to expand...
Click to collapse
If you have access to Cousin, all you need is his email. Then hopefully you can reset password and unlock it.
I am struggling with an ipad, same issue

Ok so I got it unlocked and bypassed the Google FRP as well but now I have MI unlock thing so I can use Fastboot to flash custom rom ofc I cant use MI account on the device so how will I unlock?

Qiikzx said:
Ok so I got it unlocked and bypassed the Google FRP as well but now I have MI unlock thing so I can use Fastboot to flash custom rom ofc I cant use MI account on the device so how will I unlock?
Click to expand...
Click to collapse
You can flash with fastboot without unlocked bootloader? I can't believe....

Laptapper said:
You can flash with fastboot without unlocked bootloader? I can't believe....
Click to expand...
Click to collapse
Nope i cant flash a recovery it says "failed cant flash in locked state"

Question Phone bricked, stuck in fastboot mode

Hi.
Updated my Pixel5a to latest android 13.
After unlocking bootloader and rooting the the phone with magisk the phone worked ok for a few days.
When suddenly after reboot it got to fastboot mode with failed to load/verify boot images error.
Tried to flash new image but every command I try now I get the "FAILED (remote: 'error getting device locked state Not Ready')" error
To make things worse i cannot switch the phone to recovery or rescue mode it always reboots to fastboot.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please help

Nobody encountered something similar?
First time since for me since I use smartphones(10+ years), a phone gets bricked so easily without a chance to revive it.

Here is your answer brother

Sorry I missed this.
Unfortunately, it looks like your bootloader is corrupted or malfunctioning, and the only way to fix this is by replacing the mainboard. There are special software tools that can perform a low level reflash, but they are not publicly available.

I have the same issue. After a broken screen replacement, my 5a would often freeze and turn off when these two conditions were met: Not connected to power + screen turned on.
I'm not 100% sure if it was connected to the screen replacement, given the problems only started occurring ~2 weeks later.
The phone would only turn on again when connected to power, even when the battery was already at 100%.
Unfortunately, I thought it was a software issue and didn't get it fixed immediately, so after one of the crashes I was greeted by the fastboot screen from the original poster above. Mine looks exactly the same (except for serial numbers etc.).
Current status:
Locked, unrooted, vanilla Android 13. Assume it's the January OTA, but could be December.
Recovery/Rescue modes don't work, I can only get into Fastboot. Selecting recovery will reboot into Fastboot.
Questions:
Is there a way to restore Android and how? Would it require a mainboard replacement like @V0latyle suggested?
Is the user data on the phone lost, or could it be saved in the process (no recent backups)?
What's the best way to back up an unrooted+locked+vanilla Pixel phone (without Google Cloud backup, given that's not E2E encrypted, afaik)?
Thank you!

niscy said:
I have the same issue. After a broken screen replacement, my 5a would often freeze and turn off when these two conditions were met: Not connected to power + screen turned on.
I'm not 100% sure if it was connected to the screen replacement, given the problems only started occurring ~2 weeks later.
The phone would only turn on again when connected to power, even when the battery was already at 100%.
Unfortunately, I thought it was a software issue and didn't get it fixed immediately, so after one of the crashes I was greeted by the fastboot screen from the original poster above. Mine looks exactly the same (except for serial numbers etc.).
Current status:
Locked, unrooted, vanilla Android 13. Assume it's the January OTA, but could be December.
Recovery/Rescue modes don't work, I can only get into Fastboot. Selecting recovery will reboot into Fastboot.
Questions:
Is there a way to restore Android and how? Would it require a mainboard replacement like @V0latyle suggested?
Is the user data on the phone lost, or could it be saved in the process (no recent backups)?
What's the best way to back up an unrooted+locked+vanilla Pixel phone (without Google Cloud backup, given that's not E2E encrypted, afaik)?
Thank you!
Click to expand...
Click to collapse
1. If I was current when the OP happened, I would've suggested powering on with the button combo to try and get into recovery -- Hold the Power and Volume Down; make sure to try and hold it down for as long as more than a minute. If that doesn't work, I might try Android Flash Tool as Noexcusses once suggested, but that usually requires an unlocked bootloader. Still...since it's officially from Google (the phone's maker), it might have some special "magic" that it can pull of, but don't get your hopes up on that...
3. The currently accepted best method is the Swift Backup app, My Backup Pro is an old and good staple, but without root, there's not much it will be able to save. I believe Swift (can) locks it to your Google account and/or you can password protect the backups, but I'm not totally sure if they encrypt it as well as locking it in such manner; I don't believe My Backup Pro does anything like this. There's always adb commands that might be able to save a little bit more, but again, not by much without root access. And I don't think any unrooted backup method bothers to back up the non-system internal storage.
Sorry for your troubles and hopefully you get it all back up and running! And not to be to "scoldy", but it's always a good idea to back things up (I usually do when I manually update the firmware & security updates each month); I know it's a bit harder to remember when it's an update OTA because it's a lot less involved, but it can be a good trigger to remind to...

simplepinoi177 said:
And not to be to "scoldy", but it's always a good idea to back things up
Click to expand...
Click to collapse
I agree... I had it on my todo list forever, but I just couldn't find a good way to back it up without root. And I didn't want root, because in the past that has prevented certain apps from working (e.g., some banking apps would see it as a security issue and refuse to start) and it has created trouble with OTAs.
Will look into this "Swift" app then. It's a shame, this is so trivial with iPhones (fully encrypted iTunes backups).
simplepinoi177 said:
Hold the Power and Volume Down
Click to expand...
Click to collapse
That combo takes me to Fastboot, but when I select "Recovery" from there, the phone just reboots into Fastboot again with the same errors. I can see the phone in "fastboot devices", though.
simplepinoi177 said:
Android Flash Tool as Noexcusses once suggested
Click to expand...
Click to collapse
Android Flash Tool = the thing that you run in the browser, by clicking the "Flash" link on the Google website? Is that better than adb/fastboot?
Also, do you mean for side-loading the OTA (see https://developers.google.com/android/ota)? I thought that required access to recovery?
Or are you talking about flashing the factory image (https://developers.google.com/android/images#barbet)? I haven't tried that, yet, but I assumed it would wipe my user data?
EDIT: I see the device in the Android Flash Tool, says "connected". It's in Fastboot mode and showing OP's screen. Let's see what I can do from here.
EDIT2: OUCH.

niscy said:
I have the same issue. After a broken screen replacement, my 5a would often freeze and turn off when these two conditions were met: Not connected to power + screen turned on.
I'm not 100% sure if it was connected to the screen replacement, given the problems only started occurring ~2 weeks later.
The phone would only turn on again when connected to power, even when the battery was already at 100%.
Unfortunately, I thought it was a software issue and didn't get it fixed immediately, so after one of the crashes I was greeted by the fastboot screen from the original poster above. Mine looks exactly the same (except for serial numbers etc.).
Current status:
Locked, unrooted, vanilla Android 13. Assume it's the January OTA, but could be December.
Recovery/Rescue modes don't work, I can only get into Fastboot. Selecting recovery will reboot into Fastboot.
Questions:
Is there a way to restore Android and how? Would it require a mainboard replacement like @V0latyle suggested?
Click to expand...
Click to collapse
With a locked bootloader, the only thing you can try to do is sideload an OTA, but if you can't get into recovery mode, I'm not sure there's anything you can do - a locked bootloader will reject commands such as boot, which would be useful in this case to live boot a good image...but if the bootloader was unlocked, you'd just be able to reflash /boot anyway
niscy said:
Is the user data on the phone lost, or could it be saved in the process (no recent backups)?
Click to expand...
Click to collapse
Unfortunately I believe nothing can be done to save it or back it up. If you could get into recovery and sideload an OTA, user data would be preserved, but since you can't get into recovery, that point is moot, because it looks like your only option to get the device working again is to have it repaired, which would most likely involve mainboard replacement and complete loss of all user data (except what was already backed up into the Google cloud)
niscy said:
What's the best way to back up an unrooted+locked+vanilla Pixel phone (without Google Cloud backup, given that's not E2E encrypted, afaik)?
Click to expand...
Click to collapse
There is none. Google cloud backup is the best way, but even this can't back up app data, and there is no way to back up app data without root, because of Scoped Storage - no app can access any other app's "private" data without root permissions.
simplepinoi177 said:
1. If I was current when the OP happened, I would've suggested powering on with the button combo to try and get into recovery -- Hold the Power and Volume Down; make sure to try and hold it down for as long as more than a minute. If that doesn't work, I might try Android Flash Tool as Noexcusses once suggested, but that usually requires an unlocked bootloader. Still...since it's officially from Google (the phone's maker), it might have some special "magic" that it can pull of, but don't get your hopes up on that...
Click to expand...
Click to collapse
Actually the only thing that is required is that OEM Unlocking be enabled in developer options. If it is not, the Flash Tool won't work.
simplepinoi177 said:
3. The currently accepted best method is the Swift Backup app, My Backup Pro is an old and good staple, but without root, there's not much it will be able to save. I believe Swift (can) locks it to your Google account and/or you can password protect the backups, but I'm not totally sure if they encrypt it as well as locking it in such manner; I don't believe My Backup Pro does anything like this. There's always adb commands that might be able to save a little bit more, but again, not by much without root access. And I don't think any unrooted backup method bothers to back up the non-system internal storage.
Click to expand...
Click to collapse
Again, due to scoped storage, root permissions would be required to access any other app's private data to effect a "full" backup.
niscy said:
Will look into this "Swift" app then. It's a shame, this is so trivial with iPhones (fully encrypted iTunes backups).
Click to expand...
Click to collapse
If you can boot into system, you'd be better off using Google Cloud Storage because at least that would back up device settings. Swift Backup won't do this, and is otherwise only able to access "generic" data - phone logs, texts, external storage, etc.
niscy said:
That combo takes me to Fastboot, but when I select "Recovery" from there, the phone just reboots into Fastboot again with the same errors. I can see the phone in "fastboot devices", though.
Click to expand...
Click to collapse
I think you're toast, bud.
niscy said:
Android Flash Tool = the thing that you run in the browser, by clicking the "Flash" link on the Google website? Is that better than adb/fastboot?
Click to expand...
Click to collapse
No, it's just a GUI alternative that only flashes official images. As I mentioned above this only works if OEM unlocking is enabled, or the bootloader is unlocked. A locked bootloader rejects commands like flash, boot, and update, so the flash tool unlocks the bootloader first (if not already unlocked) before proceeding with the flash.
niscy said:
Also, do you mean for side-loading the OTA (see https://developers.google.com/android/ota)? I thought that required access to recovery?
Click to expand...
Click to collapse
Yes, it does.
niscy said:
Or are you talking about flashing the factory image (https://developers.google.com/android/images#barbet)? I haven't tried that, yet, but I assumed it would wipe my user data?
Click to expand...
Click to collapse
You can only do this with an unlocked bootloader. Even though it's the factory image, as I mentioned a couple times already, the commands necessary to flash the image are rejected by a locked bootloader.
As for wiping data, this only happens if you use the included script without editing out the -w. Some people with unlocked bootloaders prefer to update using the script, they just change it so it doesn't wipe data. I personally prefer updating using the factory image but I do everything manually through fastboot and ADB because I'm stubbornly old fashioned.

niscy said:
I agree... I had it on my todo list forever, but I just couldn't find a good way to back it up without root. And I didn't want root, because in the past that has prevented certain apps from working (e.g., some banking apps would see it as a security issue and refuse to start) and it has created trouble with OTAs.
Click to expand...
Click to collapse
Just so you know, there are ways & methods to keep apps from detecting root; I would say (as far as Pixel 2XL, Pixel 5, and Pixel 7's are concerned) about 95% of apps could be made to hide root from; I get Wallet, 3 banking apps, Netflix, Xfinity apps, & certain games which all shouldn't work with a rooted device to work. And, usually, if for some reason hidden detection stops working, it usually is worked on and works again within a short amount of time.
niscy said:
Android Flash Tool = the thing that you run in the browser, by clicking the "Flash" link on the Google website? Is that better than adb/fastboot?
Click to expand...
Click to collapse
Surprisingly, it is a thing you run from the browser...! It surprised the heck out of me too! I would've thought it was a tool you actually download and run... Be aware you most likely need like 3-4GB+ free on your system (usually C drive...
niscy said:
Also, do you mean for side-loading the OTA (see https://developers.google.com/android/ota)? I thought that required access to recovery?
Or are you talking about flashing the factory image (https://developers.google.com/android/images#barbet)? I haven't tried that, yet, but I assumed it would wipe my user data?
Click to expand...
Click to collapse
I am talking about neither of those as they require you to have access to recovery mode and/or require an unlocked bootloader...
niscy said:
EDIT: I see the device in the Android Flash Tool, says "connected". It's in Fastboot mode and showing OP's screen. Let's see what I can do from here.
EDIT2: OUCH.
View attachment 5813733
Click to expand...
Click to collapse
Hey! At least that's something! And hopefully, at least it's not a total loss...could be worse; you might've/could've had to wait while a repair shop completely replaced the motherboard.
If you end up having to wipe the device to recover, consider the worst case scenario where they replace the motherboard...it would mean a wiped device anyway....

Okay guys, thank you for the help so far @V0latyle @simplepinoi177
This is where I'm now:
It only gives me the "wipe" warning when I select the "Lock Bootloader" box, otherwise it directly proceeds to download the image without giving the warning.
How come I'm getting this far while I'm in Fastboot? Am I on the right path?

The image download failed a few times due to supposedly insufficient disk space (a lie). Turns out the problem was Incognito mode, seems that has restrictions that break the flash tool.
But now I'm getting the below instead after the image downloaded. Does that mean that the tool won't work, because my device is locked?
Flash Failed
Fastboot command (flash:bootloader_b) failed: 'error getting device locked state Not Ready'

niscy said:
Okay guys, thank you for the help so far @V0latyle @simplepinoi177
This is where I'm now:
View attachment 5813743
It only gives me the "wipe" warning when I select the "Lock Bootloader" box, otherwise it directly proceeds to download the image without giving the warning.
How come I'm getting this far while I'm in Fastboot? Am I on the right path?
Click to expand...
Click to collapse
See if you can get away with not checking "wipe device" or "lock[ing] bootloader"...
It automatically downloads the factory image -- that's why I said you have to have 3-4GB free on your hard drive...
You get that far because the AFT works in fastboot, and you luckily are still able to see fastboot in your device manager & be in fastboot mode...
I'd say you are on the right path....at least a lot more hopeful than replacing your mobo. But if all doesn't work, you may be required to wipe the device and/or lock the bootloader as well...

Seems the next thing I would have to try is re-running the Flash Tool with the "Wipe device" and "Lock bootloader" boxes checked?
Just to confirm, would the motherboard replacement require a user data wipe? If yes, then I guess I have nothing to lose at this point.

niscy said:
The image download failed a few times due to supposedly insufficient disk space (a lie). Turns out the problem was Incognito mode, seems that has restrictions that break the flash tool.
But now I'm getting the below instead after the image downloaded. Does that mean that the tool won't work, because my device is locked?
Flash Failed
Fastboot command (flash:bootloader_b) failed: 'error getting device locked state Not Ready'
View attachment 5813745
Click to expand...
Click to collapse
Yes, unfortunately this is bad news...
Most likely, I imagine and maybe @V0latyle can concur and/or elaborate, but it is most likely due to you not having OEM unlock ticked in the Developer Mode and an unlocked bootloader -- I stated before, but wasn't exactly sure as I've never tried it not on an unlocked bootloader, but that tool most likely doesn't work without having an unlocked bootloader (& thus also having OEM unlocked ticked as well)...I was just holding out hope that, since it was an official Google tool, it might've been able to do something for you (especially considering you could still see it as a fastboot device in your device manager)....
niscy said:
Seems the next thing I would have to try is re-running the Flash Tool with the "Wipe device" and "Lock bootloader" boxes checked?
Just to confirm, would the motherboard replacement require a user data wipe? If yes, then I guess I have nothing to lose at this point.
Click to expand...
Click to collapse
Yes, motherboard replacement requires a user data wipe. I'm unsure if the technician either does this just as policy/practice, or if after installing the new mobo, the Android OS requires it...but I imagine it is the latter...
It might be worth a try to check those boxes, but most likely will not work. Your bootloader is already locked, so "lock[ing] bootloader" is kinda redundant and wouldn't be necessary for it to work...

Okay guys, I think I'm officially ****ed. No matter what boxes I check, I get the error mentioned above ("Fastboot command (flash:bootloader_b) failed: 'error getting device locked state Not Ready'").
But even worse, I checked with some repair shop and they told me they won't even do motherboard replacements for out-of-warranty devices (because thieves would often use this service to "refurbish" stolen phones).
So I can't even get the motherboard replaced, unless I do it myself? **** my life.

niscy said:
Okay guys, I think I'm officially ****ed. No matter what boxes I check, I get the error mentioned above ("Fastboot command (flash:bootloader_b) failed: 'error getting device locked state Not Ready'").
But even worse, I checked with some repair shop and they told me they won't even do motherboard replacements for out-of-warranty devices (because thieves would often use this service to "refurbish" stolen phones).
So I can't even get the motherboard replaced, unless I do it myself? **** my life.
Click to expand...
Click to collapse
Sorry to hear that it didn't work out...was a long shot...
Is there a uBreakiFix anywhere near you (they are the official repair company for Google)? If not, would it be possible to ship them the unit? Talk to Google versus talking to "some repair shop" (unless that repair shop you talked to was uBreakiFix, then that might be the policy; but I doubt it. Doesn't sound reasonable. I might try another store; even if you have to ship it to a distant one)...
Or course this all means you will have to spend $$$ to get it repaired, so be prepared for that...

niscy said:
Seems the next thing I would have to try is re-running the Flash Tool with the "Wipe device" and "Lock bootloader" boxes checked?
Click to expand...
Click to collapse
That would have no effect on whether the tool works
niscy said:
Just to confirm, would the motherboard replacement require a user data wipe? If yes, then I guess I have nothing to lose at this point.
Click to expand...
Click to collapse
All the storage lives in the flash devices, which live on the mainboard. A new mainboard would be preloaded with firmware, and would have to be programmed with your IMEI, but it would be like getting a brand new phone - no user data whatsoever.
simplepinoi177 said:
Yes, unfortunately this is bad news...
Click to expand...
Click to collapse
Well, hold on. We've got a lot of people all responding at once. @niscy if you could, hold off for a bit until we can get to the bottom of what your device state is and what you can and can't do.
simplepinoi177 said:
Most likely, I imagine and maybe @V0latyle can concur and/or elaborate, but it is most likely due to you not having OEM unlock ticked in the Developer Mode and an unlocked bootloader
Click to expand...
Click to collapse
Yes, one of these is required to use the Android Flash Tool (although if the bootloader is unlocked, OEM Unlocking is default "on"
simplepinoi177 said:
-- I stated before, but wasn't exactly sure as I've never tried it not on an unlocked bootloader, but that tool most likely doesn't work without having an unlocked bootloader (& thus also having OEM unlocked ticked as well)...
Click to expand...
Click to collapse
The bootloader doesn't have to start unlocked; as long as OEM Unlocking is enabled, the Flash Tool will automatically unlock the bootloader and perform the flash. I'm pretty sure this results in a data wipe.
simplepinoi177 said:
I was just holding out hope that, since it was an official Google tool, it might've been able to do something for you (especially considering you could still see it as a fastboot device in your device manager)....
Click to expand...
Click to collapse
Negative, the Flash Tool is simply a GUI interface for ADB Platform Tools and uses the same commands. Since, as I have explained multiple times, a locked bootloader rejects several commands required to flash the device, OEM Unlocking would have to be enabled at the very least to use the tool, which would then unlock the bootloader so that the commands will work.
The only "Google approved" way to update ALL devices regardless of OEM lock or bootloader lock is via OTA, because either update_engine in Android system, or the recovery kernel, is able to verify the update package. The bootloader is not capable of verifying packages applied externally; it can only compare certain partitions (such as /boot) against reference hashes (vbmeta images), which is why it's designed to reject all flashing and booting commands while locked
To be able to perform a complete factory reflash on a locked bootloader, the bootloader would have to have the ability to analyze and verify the entire update package, and it simply does not have the resources to do this. Bootloader only has three jobs:
Verify boot images
Load boot images
Provide USB interface (and must be unlocked to flash anything)
simplepinoi177 said:
Yes, motherboard replacement requires a user data wipe. I'm unsure if the technician either does this just as policy/practice, or if after installing the new mobo, the Android OS requires it...but I imagine it is the latter...
It might be worth a try to check those boxes, but most likely will not work. Your bootloader is already locked, so "lock[ing] bootloader" is kinda redundant and wouldn't be necessary for it to work...
Click to expand...
Click to collapse
As I explained, it's because you'd essentially be getting a brand new phone that has never had user data on it. Wiping data on the old mainboard is unnecessary, but most repair centers don't have a way to transfer user data.
@niscy Before you go any further, let's establish where exactly "Square One" is. Please answer these questions:
Are you able to boot into Android system? Is recovery the only thing not working?
What have you tried to get into recovery mode?
When you attempt to boot into recovery, do you see an error message at the bottom of the bootloader screen?
Do you have any particular issue with backing up your data to Google Cloud if that option is possible?

V0latyle said:
1) Are you able to boot into Android system? Is recovery the only thing not working?
2) What have you tried to get into recovery mode?
3) When you attempt to boot into recovery, do you see an error message at the bottom of the bootloader screen?
4) Do you have any particular issue with backing up your data to Google Cloud if that option is possible?
Click to expand...
Click to collapse
1) Can't get into Android system, just Fastboot.
2) Select recovery from Fastboot mode with the volume keys. I also tried "fastboot reboot recovery" (doesn't seem to work on the 5a). It doesn't make a difference how I get into fastboot (just turning it on vs. voldown + power key combo).
3) Screen just goes black and stays black for 30-60 seconds or so. Then it goes back to the fastboot screen.
4) While setting it up, the explanations in Android suggested that it was not fully end-to-end encrypted. However, I found some articles online that say the opposite. So maybe I just got confused by ambiguous language.
EDIT: flashing without the Android Flash Tool fails too, obviously...
barbet-tq1a.230105.001 % ./flash-all.sh
Sending 'bootloader_b' (8762 KB) OKAY [ 0.350s]
Writing 'bootloader_b' FAILED (remote: 'error getting device locked state Not Ready')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.080s]
Finished. Total time: 0.080s
EDIT2: Seems there's enough E2E encryption in Google backups ... see https://blog.elcomsoft.com/2021/01/...n-apple-icloud-google-and-microsoft-accounts/

V0latyle said:
As I explained, it's because you'd essentially be getting a brand new phone that has never had user data on it. Wiping data on the old mainboard is unnecessary, but most repair centers don't have a way to transfer user data.
Click to expand...
Click to collapse
Interesting...I am aware that, for computers, replacing the motherboard doesn't necessarily touch data because that's usually stored on the hard drive. I figure the internal storage on a smartphone might be set up similarly and have it separated in something the same way (i.e. I imagine it's something similar to a microsd internal circuitry), and thus might not be touched simply by replacing the mobo. I wasn't insinuating that the repair centers would wipe old data that they were going to toss anyway; thought it was separate from the mobo and could possibly survive the exchange.
Thanks for clarifying! Also, I posted this here instead of PMing it because it is somewhat useful information that might help someone else understand things better (like me)...but I do apologize for the off-topic...

I just went back and read your first post. Failure to load/verify boot images means there's a dm-verity issue - as I mentioned previously, the bootloader verifies the integrity of the boot image as it's loaded; this prevents things like persistent rootkits. In this case, it's coming up against an error - the hash of the boot image does not match the verification hash in /vbmeta, probably because it somehow got corrupted during the update. With an unlocked bootloader this would be a fairly simple fix - just reflash /boot - but with a locked bootloader, this is pretty much impossible to fix.
niscy said:
1) Can't get into Android system, just Fastboot.
Click to expand...
Click to collapse
Yeah, because as described above, the boot image is corrupted, and unfortunately, the boot image also contains recovery.
niscy said:
2) Select recovery from Fastboot mode with the volume keys. I also tried "fastboot reboot recovery" (doesn't seem to work on the 5a). It doesn't make a difference how I get into fastboot (just turning it on vs. voldown + power key combo).
3) Screen just goes black and stays black for 30-60 seconds or so. Then it goes back to the fastboot screen.
Click to expand...
Click to collapse
Not sure why the screen goes black for a while, it should just recycle back to the bootloader screen immediately
niscy said:
4) While setting it up, the explanations in Android suggested that it was not fully end-to-end encrypted. However, I found some articles online that say the opposite. So maybe I just got confused by ambiguous language.
Click to expand...
Click to collapse
Yeah. I won't be one of those people who advocates for using a product you don't believe in, but you also have to consider benefit vs risk - in this case, you really don't want to use your data, but you didn't implement an alternative for backups.
niscy said:
EDIT: flashing without the Android Flash Tool fails too, obviously...
barbet-tq1a.230105.001 % ./flash-all.sh
Sending 'bootloader_b' (8762 KB) OKAY [ 0.350s]
Writing 'bootloader_b' FAILED (remote: 'error getting device locked state Not Ready')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.080s]
Finished. Total time: 0.080s
EDIT2: Seems there's enough E2E encryption in Google backups ... see https://blog.elcomsoft.com/2021/01/...n-apple-icloud-google-and-microsoft-accounts/
Click to expand...
Click to collapse
Yeah. At this point, I think you're pretty much limited to two options:
Pay for a repair (expensive)
Buy a new device (even more expensive)
I'm sorry there's no better answer. If OEMs like Google (or in this case, Foxconn as the manufacturer) made a point of providing low level flash tools and training to repair stations, then it might be possible to reflash the boot image. But, they don't do this for a litany of reasons, ranging from "it's cheaper to replace than to fix" to "tools like this could be used for major exploits in the wrong hands".
simplepinoi177 said:
Interesting...I am aware that, for computers, replacing the motherboard doesn't necessarily touch data because that's usually stored on the hard drive. I figure the internal storage on a smartphone might be set up similarly and have it separated in something the same way (i.e. I imagine it's something similar to a microsd internal circuitry), and thus might not be touched simply by replacing the mobo. I wasn't insinuating that the repair centers would wipe old data that they were going to toss anyway; thought it was separate from the mobo and could possibly survive the exchange.
Thanks for clarifying! Also, I posted this here instead of PMing it because it is somewhat useful information that might help someone else understand things better (like me)...but I do apologize for the off-topic...
Click to expand...
Click to collapse
Yeah, mobile mainboards are generally "all in one", with the SoC, modem, and storage all located on the same board. There are sometimes small daughterboards for things like camera modules and microSD/SIM card slots but for the most part everything is on the same board. All flashable storage is located on the same memory devices - this includes the most basic things such as the bootloader itself and the baseband image, as well as the system partitions, and of course the "userspace" data. Imagine if your hard drive was built into your motherboard, and also hosted your BIOS/UEFI.
There is only one more thing I can advise trying, and it will most likely not work: Try to switch back to the A slot. You can do this through fastboot: fastboot --set-active=a
Again, this is not likely to work because I believe the bootloader will reject this command as well.
An interesting note that isn't of much help right now: The whole point of A/B slots (and seamless system updates) is not just being able to update "on the fly" without booting into recovery and waiting 5-10 minutes for an update to finish, but also a "fail safe" so that if an update fails for whatever reason, the system should recycle back to the last working configuration.
Spoiler: It works like this:
Let's assume for the sake of argument you're on slot A, running the January update.
When the February update becomes available, update_engine downloads the update package, extracts it, and writes it to the inactive slot - in this case, slot B.
The bootloader is then commanded to boot slot B on the next reboot
When user reboots device, bootloader marks slot B as active and attempts to boot from that slot. There are a couple of markers here - a slot can be marked active, bootable, and successful.
Once boot proceeds past a certain point, the slot is now marked bootable. Once loaded into Android system, the boot is marked successful.
If for any reason slot B fails to boot, or crashes at a certain point, the device should automatically reboot back to slot A, and upon successful boot of Android, notify the user that the update failed.
I don't know why it failed to do that in this case. Apparently it thought slot B was both bootable and successful, and the failure didn't occur early enough to recycle back to slot A.