Database Develop

Phone bricked after an OTA update

Sorry, I didn't know where to post this, but okay; I've installed an Oxygen OS update two days ago and I've had my phone rooted, my phone has been bricked since. Whenever I enter the bootloader my device isn't detected anymore by my laptop therefore I can't re-flash TWRP and now I'm completely stuck and don't know what to do, any help please?

u_ser_n_a_m_e said:
Sorry, I didn't know where to post this, but okay; I've installed an Oxygen OS update two days ago and I've had my phone rooted, ever since my phone has been bricked, whenever I enter the bootloader my device isn't detected anymore by my laptop therefore I can't re-flash TWRP and now I'm completely stuck and don't know what to do, any help please?
Click to expand...
Click to collapse
You're best bet would be to download the full OOS OTA and then ADB Sideload the OTA.
You should find all the files you need on*
http://downloads.oneplus.net/
First, you download the full OOS ROM and the stock recovery for Nougat.
Then you flash the stock recovery (fastboot flash recovery <file name>).
Then you boot into recovery and select "install from USB" to get into sideload mode.
And finally you sideload the latest OOS (ADB Sideload <filename>).
It will take some time, but your phone should work after it.
FYI, keep in mind that you'll have to manually flash updates when using a custom recovery
Hope this does the trick for ya!
Good luck and happy flashing!
Sent from my SM-G955U using XDA-Developers Legacy app

u_ser_n_a_m_e said:
Sorry, I didn't know where to post this, but okay; I've installed an Oxygen OS update two days ago and I've had my phone rooted, my phone has been bricked since. Whenever I enter the bootloader my device isn't detected anymore by my laptop therefore I can't re-flash TWRP and now I'm completely stuck and don't know what to do, any help please?
Click to expand...
Click to collapse
Assuming you have ADB on your laptop, does the command "adb devices" list your device?
I think your problem may have been caused by attempting an OTA update while using a custom recovery. I have learned this is not recommended.
Try and connect with ADB and if you can follow the instructions to sideload given by the other member
You may also like to check this thread
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306

dave457 said:
Assuming you have ADB on your laptop, does the command "adb devices" list your device?
I think your problem may have been caused by attempting an OTA update while using a custom recovery. I have learned this is not recommended.
Try and connect with ADB and if you can follow the instructions to sideload given by the other member
You may also like to check this thread
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Click to expand...
Click to collapse
It only lists my device when I'm in the booting process. Everywhere else, it does not

Use the usual Qualcomm recovery solution, it will work as long as you hold the buttons correctly and don't power it on, else you will not end up in Qualcomm preboot mode.
It's just like MTK recovery on Mediatek phones if you've owned one of many MTK-devices. ?

u_ser_n_a_m_e said:
Sorry, I didn't know where to post this, but okay; I've installed an Oxygen OS update two days ago and I've had my phone rooted, my phone has been bricked since. Whenever I enter the bootloader my device isn't detected anymore by my laptop therefore I can't re-flash TWRP and now I'm completely stuck and don't know what to do, any help please?
Click to expand...
Click to collapse
Yeah follow the unbrick thread
I just updated my own thread that has ULTRA-BRICK in the title a second ago for how I solved my issue haha
edit: if needed, can PM me too. I won't hold your hand, but since I just came out of the worst brick I've ever managed to do to myself, I might be able to help if you encounter the same things

Also brick is a misleading word, as you can't really brick this phone unless you tamper with other partitions than the visible ones, which nobody does as they don't see them. ? (unless your tampering with firmwares or trying to unlock frequency bands)

Alright guys, I solved it. I just had to flash TWRP really quickly in the bootloader and install a substratum legacy rescue zip or something through TWRP, thanks for the help.

MI 9 Bricked After trying to change CN rom to Global rom.

Hi Guys, I hope someone of you could help me out.
Recently a Chinese friend of mine gave me an MI 9 as a present. But unfortunately they ROM of the new phone was the CN version.
I found a way to change the ROM by doing the unlock bootloader and flashing TRWP, after that, I downloaded the MI9_Global_V9.5.30_vendor_fw_flash, went back to the Recovery and wiped the "Delvik, cache, SYSTEM and Data. When I was trying to install the rom I got an error telling me the Global rom file was corrupt and restarted the cellphone.
The problem is I am stuck in the Fastboot loop, can't access the recovery and my computer don't recognize the cellphone.
I know I ****ed it up, I was wondering if I can revert that or did I just lost a phone.
Thank you Guys.

pedrohwelerson said:
Guys,
I just solve my problem, I used MI Unlock tool and unlock the bootloader and all is good again.
I would like to thank you all for your help.
Best Regards
Click to expand...
Click to collapse
Hi,
How did you unlock your bootloader?
It asks for binding Mi account and it's not possible when your phone is bricked.

Yeah, the rule is simple. If it boots into fastboot, it can be recovered. Just flash the global you want with the MI flash tool and the fastboot file.

nudou350 said:
Yeah, the rule is simple. If it boots into fastboot, it can be recovered. Just flash the global you want with the MI flash tool and the fastboot file.
Click to expand...
Click to collapse
I'll try it later my friend, I'll come back if I succeed.
Thank you

pedrohwelerson said:
I'll try it later my friend, I'll come back if I succeed.
Thank you
Click to expand...
Click to collapse
You use Mi flash 2018.5.28
and Flash rom dev Global 9.6.27
or rom Stable Global
https://forum.xda-developers.com/showpost.php?p=80319431&postcount=3

Guys I am too stupid for this,
I flashed the fastboot global rom in my phone with MI flash but locked it in the end (can't believe I am that retard), now I believed I have bricked it for good.
Now I can't flash the correct fastboot ROM with miflash because I have locked the bootloader while trying to flash the Global ROM. I am at the fastboot loop again.
Can I do something now or I just have a expensive paper holder?
Thank you guys.

pedrohwelerson said:
Guys I am too stupid for this,
I flashed the fastboot global rom in my phone with MI flash but locked it in the end (can't believe I am that retard), now I believed I have bricked it for good.
Now I can't flash the correct fastboot ROM with miflash because I have locked the bootloader while trying to flash the Global ROM. I am at the fastboot loop again.
Can I do something now or I just have a expensive paper holder?
Thank you guys.
Click to expand...
Click to collapse
flash another official firmware on a locked bootloader BY XIAOMI TOOL V2 https://www.xiaomitool.com/v2
https://www.youtube.com/watch?v=UMkDAxiDdKs&t=10s
Here’s something VERY important before you flash or update the ROM.
1. Xiaomi Phones manufactured for Chinese market are not able to run MIUI Global ROM.
2. Xiaomi Phones manufactured for Global markets are not able to run MIUI China ROM.
We highly recommend you to buy Xiaomi Phones via official or authorized sales channels and double check the system information before flashing or updating.

hochocnua said:
flash another official firmware on a locked bootloader BY XIAOMI TOOL V2 https://www.xiaomitool.com/v2
https://www.youtube.com/watch?v=UMkDAxiDdKs&t=10s
Here’s something VERY important before you flash or update the ROM.
1. Xiaomi Phones manufactured for Chinese market are not able to run MIUI Global ROM.
2. Xiaomi Phones manufactured for Global markets are not able to run MIUI China ROM.
We highly recommend you to buy Xiaomi Phones via official or authorized sales channels and double check the system information before flashing or updating.
Click to expand...
Click to collapse
I think the problem is that he locked the bootloader after install the global ROM.
There are several user that flash global ROM in Xiaomi chinese market phones.
SDS

pedrohwelerson said:
Guys I am too stupid for this,
I flashed the fastboot global rom in my phone with MI flash but locked it in the end (can't believe I am that retard), now I believed I have bricked it for good.
Now I can't flash the correct fastboot ROM with miflash because I have locked the bootloader while trying to flash the Global ROM. I am at the fastboot loop again.
Can I do something now or I just have a expensive paper holder?
Thank you guys.
Click to expand...
Click to collapse
Hi guy,
Same thing happened to me, I felt very stupid, but it was on a MI 8 SE.
According to my experience, only there's a way to solve it and it's booting on EDL mode.
You'll need an authorized Mi account to flash the original ROM.
There's a complete guide on c . mi . com named [Guide] [All in One] MIUI Flashing Guide: Unbrick, EDL Method / Locked Bootloader, Unlock Bootloader, More, I can't post the url because I'm a new user
Best wishes!
Regards from Peru.

Jhnn11 said:
Hi guy,
Same thing happened to me, I felt very stupid, but it was on a MI 8 SE.
According to my experience, only there's a way to solve it and it's booting on EDL mode.
You'll need an authorized Mi account to flash the original ROM.
There's a complete guide on c . mi . com named [Guide] [All in One] MIUI Flashing Guide: Unbrick, EDL Method / Locked Bootloader, Unlock Bootloader, More, I can't post the url because I'm a new user
Best wishes!
Regards from Peru.
Click to expand...
Click to collapse
How were you able to get the authorized MI account? In the tutorial you mentioned, they didn't say anything about MI Account.
I'll try MItool first and let you guys know.
Thank you for the tip

hochocnua said:
flash another official firmware on a locked bootloader BY XIAOMI TOOL V2 https://www.xiaomitool.com/v2
https://www.youtube.com/watch?v=UMkDAxiDdKs&t=10s
Here’s something VERY important before you flash or update the ROM.
1. Xiaomi Phones manufactured for Chinese market are not able to run MIUI Global ROM.
2. Xiaomi Phones manufactured for Global markets are not able to run MIUI China ROM.
We highly recommend you to buy Xiaomi Phones via official or authorized sales channels and double-check the system information before flashing or updating.
Click to expand...
Click to collapse
Do you think I'll be able to use the MI TOOL V2, even in the fastboot loop.?
Thank you by the way

pedrohwelerson said:
Do you think I'll be able to use the MI TOOL V2, even in the fastboot loop.?
Thank you by the way
Click to expand...
Click to collapse
It should work, try to get the chinese rom back, unlock it again, flash twrp, give xiaomi.eu rom a try, they should work on any xiaomi phone regardless of region.

zipsu said:
It should work, try to get the chinese rom back, unlock it again, flash twrp, give xiaomi.eu rom a try, they should work on any xiaomi phone regardless of region.
Click to expand...
Click to collapse
I can't use MITOOL because the USB DEBUGGING isn't enabled, is there a way to do it in the fastboot loop?
Thank you

It should recongnize with no problems.. Just check if you have the ADB drivers and try unlocking the bootloader and then flashing the Rom with the miflash tool. Still, if you have access to fastboot, things should be fine! Don't panic hahha

nudou350 said:
It should recongnize with no problems.. Just check if you have the ADB drivers and try unlocking the bootloader and then flashing the Rom with the miflash tool. Still, if you have access to fastboot, things should be fine! Don't panic hahha
Click to expand...
Click to collapse
The MI tool v2 recognized my phone alright but it can't flash the rom coz I don't have the usd debugger enable and I can't turn on the bug to enable it since I Bricked the phone.
So I wondering if I can turn the usb debugger by other way.
Thank you

pedrohwelerson said:
Hi Guys, I hope someone of you could help me out.
Recently a Chinese friend of mine gave me an MI 9 as a present. But unfortunately they ROM of the new phone was the CN version.
I found a way to change the ROM by doing the unlock bootloader and flashing TRWP, after that, I downloaded the MI9_Global_V9.5.30_vendor_fw_flash, went back to the Recovery and wiped the "Delvik, cache, SYSTEM and Data. When I was trying to install the rom I got an error telling me the Global rom file was corrupt and restarted the cellphone.
The problem is I am stuck in the Fastboot loop, can't access the recovery and my computer don't recognize the cellphone.
I know I ****ed it up, I was wondering if I can revert that or did I just lost a phone.
Thank you Guys.
Click to expand...
Click to collapse
Read carefully and report
1. Try to hold down the buttons vol down and power, see if : fastboot devices sees it. If so XiaoMi Tool will restore it. If not do the same try recovery vol up + power. Do adb devices and see if anything shows up. Worst case you'll have to open the phone up and connect the EDL pins together and it will flash anything. I use minimal ADB and Fastboot phone plugged via USB cable into the computer and run those commands.
2. Fully bricks their device here is the unbrick factory method
https://c.mi.com/thread-1479882-1-0.html
that's connecting EDL pins with the phone case removed for a phone that doesn't boot at all
3. https://youtu.be/8mW0JzKow7E
here's the exact EDL test point required on Mi9
if you can't boot or recognize the device at all via fastboot or ADB. If this doesn't work nothing will...
But it will work, that's what the factory does. Obviously the last resort.

hochocnua said:
Read carefully and report
1. Try to hold down the buttons vol down and power, see if : fastboot devices sees it. If so XiaoMi Tool will restore it. If not do the same try recovery vol up + power. Do adb devices and see if anything shows up. Worst case you'll have to open the phone up and connect the EDL pins together and it will flash anything. I use minimal ADB and Fastboot phone plugged via USB cable into the computer and run those commands.
2. Fully bricks their device here is the unbrick factory method
https://c.mi.com/thread-1479882-1-0.html
that's connecting EDL pins with the phone case removed for a phone that doesn't boot at all
3. https://youtu.be/8mW0JzKow7E
here's the exact EDL test point required on Mi9
if you can't boot or recognize the device at all via fastboot or ADB. If this doesn't work nothing will...
But it will work, that's what the factory does. Obviously the last resort.
Click to expand...
Click to collapse
My pc identify my MI 9 alright the problem is that I can't flash anything with MItools coz I don't have enable the USB debugging and I can't enable it because of the fastboot loop.
Is there a way to enable it with a CMD command?
If no I'll have to open de device and do the EDL.
By the way thank you for your help.
REally appreciated it.

pedrohwelerson said:
My pc identify my MI 9 alright the problem is that I can't flash anything with MItools coz I don't have enable the USB debugging and I can't enable it because of the fastboot loop.
Is there a way to enable it with a CMD command?
If no I'll have to open de device and do the EDL.
By the way thank you for your help.
REally appreciated it.
Click to expand...
Click to collapse
like and share

pedrohwelerson said:
My pc identify my MI 9 alright the problem is that I can't flash anything with MItools coz I don't have enable the USB debugging and I can't enable it because of the fastboot loop.
Is there a way to enable it with a CMD command?
If no I'll have to open de device and do the EDL.
By the way thank you for your help.
REally appreciated it.
Click to expand...
Click to collapse
Op if you'd like help restoring your device to working order. I could help you through TeamViewer. If you'd like

andrew2401 said:
Op if you'd like help restoring your device to working order. I could help you through TeamViewer. If you'd like
Click to expand...
Click to collapse
I would really like it.
Thank you

pedrohwelerson said:
I would really like it.
Thank you
Click to expand...
Click to collapse
Where are you from? Asking so I can take time zone difference into account when arranging a time

Mi9 Global - Accidentally locked bootloader and stock in recovery/fastboot

Hi,
Recently purchased a Mi 9 Global version, got the OTA update to MIUI 11, and everything was well. It is a superb phone, but I like to have root on my phones (mostly for Adblocking and System2, better control overall). I tried to install TWRP (custom version for Mi9) because I wanted to install Magisk/Root or try a different rom eventually. Anyway... I made a huge mistake. After trying to reboot, I noticed things had gone wrong, and was stuck in a boot loop. I guess I panicked and tried to flash the phone back to the latest global MIUI rom (Version 11, Android 10, from official site), using the Xiaomi Flash App but I did not uncheck the "clean and lock bootloader" checkbox on the bottom right of the app, which is somehow enabled by default. The flash failed at that time, for unknown reason, but it seems like it succeeded in locking my bootloader, with an empty partition, except for fastboot access and Mi Recovery module. I have to admit I've always been pretty lucky with all my previous flashes on other devices, and I guess I got a little careless. That was pretty stupid of me, in retrospect.
Since then, I am stuck in either Mi Recovery or Fastboot, and it seems that my originally Global Mi 9 with unlock bootloader has now a locked bootloader. Any attempt at either using the Xiaomi Flash utility gives me an error message ("Erase boot error"), and if I boot into Fastboot and try to flash TWRP, I get the "Remote:Erase is not allowed in Lock State" error.
From what I understand, my options are pretty limited now. The phone is still powered on, stuck in Recovery mode and rebooting every 5 or 10 minutes by itself (probably a way to avoid screen burn-in?), but I can't seem to be able to shut it down in anyway, as there are no fastboot commands to send a shutdown signal. And no matter what button combination I press, the phone always ends up rebooting.
I tried the Xiaomi Unlocker utility, but it needs the phone to be out of recovery to check the credentials binding the phone to my account. All data on the phone has been wiped already, so that's not an option. Two options I have seen :
1. Open the battery cover (required a heat gun and risky), to short some pins and try to flash while there is a short to circumvent the security. I'm not that brave yet, and since the phone is still running and has probably about 80% battery, I don't want to use a heat gun on the device.
2. Shady stuff involving paying 30 or 40 Euros to a random guy who can somehow make everything work magically by remotely logging in on my computer via Teamviewer (Not happening in a million years).
I'm wondering if there is an alternative, other than bringing the device to an official Xiaomi store (I'm in Bangkok and they do have one official shop at Fortune Town), but even then, I don't know if they'll just tell me I got myself an expensive paperweight.
Any help/insight regarding this issue would be much, much appreciated!

Have you tried to press and hold power+vol down when your device reboots? Just before it turns on.

g_seva said:
Have you tried to press and hold power+vol down when your device reboots? Just before it turns on.
Click to expand...
Click to collapse
Every possible combination on reboot will either bring me to Fastboot or Mi Recovery. I have wiped the data partition, there is no OS on the phone as of now.

Twomby said:
Every possible combination on reboot will either bring me to Fastboot or Mi Recovery. I have wiped the data partition, there is no OS on the phone as of now.
Click to expand...
Click to collapse
So xiaomi unlock utility can't unlock bootloader in fastboot?
May be try to use xiaomitool v2.

g_seva said:
So xiaomi unlock utility can't unlock bootloader in fastboot?
May be try to use xiaomitool v2.
Click to expand...
Click to collapse
Xiaomitool V2 is completely useless. The "My phone is bricked" option is not implemented, and I cannot boot into the OS, unfortunately.

To enter fastboot mode, long press the volume down key and the power key. Then unlock bootloader with Xiaomi app.

zahdekar said:
To enter fastboot mode, long press the volume down key and the power key. Then flash stock rom.
Click to expand...
Click to collapse
I have managed to enter fastboot mode, as described in my initial post. The problem is that when I try to flash, I get the following error: "Flashing not allowed in lock state".

Twomby said:
Xiaomitool V2 is completely useless. The "My phone is bricked" option is not implemented, and I cannot boot into the OS, unfortunately.
Click to expand...
Click to collapse
Yep, but it has unlock option in the normal mode and it use scripts made by tool developer, so it worth to try.

g_seva said:
Yep, but it has unlock option in the normal mode and it use scripts made by tool developer, so it worth to try.
Click to expand...
Click to collapse
From what I understand, the "normal mode" needs the tool to be able to access the OS while it's running. I don't have an OS. I will give it a shot tomorrow (3 AM here, exhausted, and don't want to boot into Windows again!), but my hopes are not so high. Anyway, thanks for the help, much appreciated! Will let you know what happens! Cheers!

https://forum.xda-developers.com/Mi-9/how-to/unbrick-mi9-bootloader-locked-destroyed-t3924966/amp/
maybe it will help

zahdekar said:
https://forum.xda-developers.com/Mi-9/how-to/unbrick-mi9-bootloader-locked-destroyed-t3924966/amp/
maybe it will help
Click to expand...
Click to collapse
I've stumbled upon this link earlier today. But it's 404 on my end. Can you access it from where you are? Thanks!

http://c.mi.com/thread-2251372-1-1.html
This is on page 4

zahdekar said:
http://c.mi.com/thread-2251372-1-1.html
This is on page 4
Click to expand...
Click to collapse
Thanks. Tried it, but using these commands only cause a reboot, to recovery mode again. Thanks again for your kind help!

Twomby said:
Thanks. Tried it, but using these commands only cause a reboot, to recovery mode again. Thanks again for your kind help!
Click to expand...
Click to collapse
I have the same problem! "The system has been destroyed" (((
And mi unlock tool not work abount 2 days (authorization not passes)

https://forum.xda-developers.com/Mi-9/help/help-bricked-mi-9-t3921980/page2
The old version of miunlock is working ti unlock bootloader.

zahdekar said:
https://forum.xda-developers.com/Mi-9/help/help-bricked-mi-9-t3921980/page2
The old version of miunlock is working ti unlock bootloader.
Click to expand...
Click to collapse
Unfortunately, this is not true. I have downloaded an old version of Mi Unlock (2.2.406.5), which is supposed to work with Fastboot mode. The result is "Couldn't unlock --> Please download the latest version". And the latest version needs to access the OS to verify the Mi account credentials. I don't have an OS installed. So this won't work. Thanks for the suggestion though!

Twomby said:
Unfortunately, this is not true. I have downloaded an old version of Mi Unlock (2.2.406.5), which is supposed to work with Fastboot mode. The result is "Couldn't unlock --> Please download the latest version". And the latest version needs to access the OS to verify the Mi account credentials. I don't have an OS installed. So this won't work. Thanks for the suggestion though!
Click to expand...
Click to collapse
Hello @Twomby did you managed to get it working it the end?

Same issue here
Hi,
I am encouraging the same issue. Does someone found a solution to this?

tago4ever said:
Hi,
I am encouraging the same issue. Does someone found a solution to this?
Click to expand...
Click to collapse
I came across this Mi8 thread, not sure if it's possible on the Mi9, but he seems to have been able to flash it through EDL mode, you might ask him the question: https://xiaomi.eu/community/threads/mi-8-bricked-from-nowhere.55723/#post-543605
There's also this Mi9 thread: https://forum.xda-developers.com/Mi-9/how-to/unbrick-mi9-bootloader-locked-destroyed-t3924966

So I tried to unlock via EDL...

...and I thought it had worked but as it turns out, it did not. I found out it did not when I tried to root to which the phone proceeded to tell me it was lock.
Now, when I go into Recovery Mode, the phone does not come up in ADB even when trying to unlock after using the ASUS unlocker tool... Is the ADB bridge fried forever? How do I reinstate it to be able to root? I don't mind wiping, I just want to recover the possibility to root. Any way to do that? God I feel dumb right now...
Edit: I've gotten ADB to recognize the phone in Recovery Mode by installing the exact Manufacturer and Model ADB drivers but the second I get into Fastboot mode, it's like the side USB-C suddenly becomes non-existent, same goes for the bottom one. Feels like a kill.switch from ASUS to me :/
Edit 2: Is there a way to flash while in Recovery? Or in normal OS operations? (sounds like a bad idea but I'm out of ideas as of now)

So neither of the two USB ports in the phone seem to work for you in bootloader mode?

dennis96411 said:
So neither of the two USB ports in the phone seem to work for you in bootloader mode?
Click to expand...
Click to collapse
Exactly, the bootloader is also unlocked after using ASUS's tool .apk, I am on 1910.44 WW, I tried different ADB's while in Windows, tried to copy DeviceID, it all works when in normal boot OR in recovery mode but the second I am in fastboot mode, both USB's stop working. As if ASUS locked the access when I mistakenly tried to gain root while the bootloader was locked. Maybe if I could lock it back but that would require me being in fastboot afaik.
Can I lock it back while in recovery? If so, what would be the prompt?

I would be very careful about locking the bootloader at this point. I heard it can cause a brick if the planets aren't aligned correctly.
Jokes aside, does device manager refresh itself when you plug or unplug the phone in fastboot mode? That would indicate it saw something from the phone.

dennis96411 said:
I would be very careful about locking the bootloader at this point. I heard it can cause a brick if the planets aren't aligned correctly.
Jokes aside, does device manager refresh itself when you plug or unplug the phone in fastboot mode? That would indicate it saw something from the phone.
Click to expand...
Click to collapse
Sadly no, tried 3 different computers, a plethora of cables, different USB ports. It's like the Fastboot killed the function altogether so as of now, I have yet to find a way to get the phone recognized while in fastboot.

WhyKlwd said:
Sadly no, tried 3 different computers, a plethora of cables, different USB ports. It's like the Fastboot killed the function altogether so as of now, I have yet to find a way to get the phone recognized while in fastboot.
Click to expand...
Click to collapse
Is there an option to apply a full OTA from the stock recovery?

dennis96411 said:
Is there an option to apply a full OTA from the stock recovery?
Click to expand...
Click to collapse
Before anything, thanks for helping, it's greatly appreciated!
So, no sadly, when I get in Recovery Mode my options are:
Reboot system now
Reboot to bootloader
Wipe data/factory reset
Power off
As anyone would, I tried kicking into bootloader from recovery hoping that it would trigger something different to give me fastboot but to no avail, I wiped a couple of times as well, that didn't pan out.
Edit: I feel like my best chance at this point is when ASUS releases a new WW firmware update, that it HOPEFULLY brings Fastboot Mode to it's original value... But according to a thread somewhere on XDA, it does not install a full partitioned recovery so I'm not having my hopes up...
The other thing would be to butcher a USB-C cable and see if I get a response when connected on the orange USB-C but that's also a risk to take. So that doesn't work, that USB-C gets no response whatsoever.

What firmware version are you on? You could try grabbing the stock firmware zip of the firmware you're on now from https://www.asus.com/Phone/ROG-Phone-II/HelpDesk_Download/, and increase the firmware version in the zip name - for example, if you're on the latest .44 build now, change the .44 in the zip name to .45. Then simply push it to the root of your internal storage, and reboot. After boot you should get a message that a system update file has been found, and that you can install it.
I don't know if this will fix your problem, but it should reflash the stock partitions. And yes, it's true that it far from flashes all partitions, but it's worth a try at least.

HomerSp said:
What firmware version are you on? You could try grabbing the stock firmware zip of the firmware you're on now from https://www.asus.com/Phone/ROG-Phone-II/HelpDesk_Download/, and increase the firmware version in the zip name - for example, if you're on the latest .44 build now, change the .44 in the zip name to .45. Then simply push it to the root of your internal storage, and reboot. After boot you should get a message that a system update file has been found, and that you can install it.
I don't know if this will fix your problem, but it should reflash the stock partitions. And yes, it's true that it far from flashes all partitions, but it's worth a try at least.
Click to expand...
Click to collapse
I did put the stock firmware but I hadn't thought of changing the name to "force" the phone to try and update! Sadly, when it reached 100%, it said install failed and while trying fastboot mode, it still didn't restore ADB but that was brilliant and definitely worth the try. Thanks for your suggestion, here's hoping the next legit firmware will do it!
EDIT: AND YET IT DID WORK!!! That must have fixed it after all... I unplugged, replugged while in bootloader and finally, that USB chime! T-T
Thanks both of you for your suggestions, 3 brains work better than one!

WhyKlwd said:
I did put the stock firmware but I hadn't thought of changing the name to "force" the phone to try and update! Sadly, when it reached 100%, it said install failed and while trying fastboot mode, it still didn't restore ADB but that was brilliant and definitely worth the try. Thanks for your suggestion, here's hoping the next legit firmware will do it!
EDIT: AND YET IT DID WORK!!! That must have fixed it after all... I unplugged, replugged while in bootloader and finally, that USB chime! T-T
Thanks both of you for your suggestions, 3 brains work better than one!
Click to expand...
Click to collapse
Nice, glad to see it worked! I tried it myself and it also said update failed, but it had flashed, so I think the error message may just be because the firmware version doesn't change.
I'm assuming fastboot works now then? Do keep in mind that you'll need the abl, xbl and xbl_config images from the edl unlock thread to be able to actually unlock the bootloader without using the Asus tool.

HomerSp said:
Nice, glad to see it worked! I tried it myself and it also said update failed, but it had flashed, so I think the error message may just be because the firmware version doesn't change.
I'm assuming fastboot works now then? Do keep in mind that you'll need the abl, xbl and xbl_config images from the edl unlock thread to be able to actually unlock the bootloader without using the Asus tool.
Click to expand...
Click to collapse
Yeah it works, or at least it did long enough for me to be able to root. I haven't tried it since but I would assume that it fixed it, tomorrow I'll most likely do a RAW flash to fix all potential risks as well as try the latest CN firmware. EDL never worked, that's what got me in that situation in the first place... well that and me not paying full attention.

Question REDMI NOTE 10S (Your system has been destroyed+ locked bootloader) error

I have redmi note 10s. I bacame bored of miui because of several bugs. So i decided to mod the device with a nice custom rom. I started the process. Because it is a mtk device, it has complicated flashing process than snapdragon devices. I entered the fastbootD mode and cleared the system by using adb command(which i dont remember). Then i flashed the custom rom. By mistake, I locked the bootloader by typing adb command fastboot oem lock. But now due to complicated case, the device is showing your system has been destroyed and when i try to force reboot it into fastboot, it still give systen destroyed error(means fastboot mode is inaccessible). Can anyone please help me to fix this issue without using edl pins? I am in a great issue

I cant go to service center as my device is out of warranty

in google there is a pc program than can unlock bootloader of mediatek devices, search for it

Bro i cant access the bootloader, so unlocking it doesnt make any difference

I want to restore the bootloader.

Manmeet_2008 said:
I have redmi note 10s. I bacame bored of miui because of several bugs. So i decided to mod the device with a nice custom rom. I started the process. Because it is a mtk device, it has complicated flashing process than snapdragon devices. I entered the fastbootD mode and cleared the system by using adb command(which i dont remember). Then i flashed the custom rom. By mistake, I locked the bootloader by typing adb command fastboot oem lock. But now due to complicated case, the device is showing your system has been destroyed and when i try to force reboot it into fastboot, it still give systen destroyed error(means fastboot mode is inaccessible). Can anyone please help me to fix this issue without using edl pins? I am in a great issue
Click to expand...
Click to collapse
Okay so first of all download "mtk client"
Than open the mtk client
It will give you instructions on how to connect your phone, take back of everything except system(super),vendor and userdata. Tap on flash tab there you'll notice a option called unblock bootloader tap on it and your bootloader will be unlocked

Bro Will this restore my bootloader or only unlock it because if it only unlocks then your help wont work.

Manmeet_2008 said:
Bro Will this restore my bootloader or only unlock it because if it only unlocks then your help wont work.
Click to expand...
Click to collapse
you dummy, you need to unlock the bootloader in orden to restore it installing the firmware with miflashtool or mtk client .

Ok bro thanks for your help
tutibreaker said:
you dummy, you need to unlock the bootloader in orden to restore it installing the firmware with miflashtool or mtk client .
Click to expand...
Click to collapse

Manmeet_2008 said:
I have redmi note 10s. I bacame bored of miui because of several bugs. So i decided to mod the device with a nice custom rom. I started the process. Because it is a mtk device, it has complicated flashing process than snapdragon devices. I entered the fastbootD mode and cleared the system by using adb command(which i dont remember). Then i flashed the custom rom. By mistake, I locked the bootloader by typing adb command fastboot oem lock. But now due to complicated case, the device is showing your system has been destroyed and when i try to force reboot it into fastboot, it still give systen destroyed error(means fastboot mode is inaccessible). Can anyone please help me to fix this issue without using edl pins? I am in a great issue
Click to expand...
Click to collapse
try some sp flashtool that come with miflashtool , turn off phone and press volume- and plug the cable in , some type of mtk download mode

Ok bro i will try tomorrow

Hello everyone, today i used the tool but when i went through the tool i saw a 'erase flash' option in mtk universal tab. Can anyone please tell that what this option is used for and ticking it will lead to any sort of issues?

Manmeet_2008 said:
Hello everyone, today i used the tool but when i went through the tool i saw a 'erase flash' option in mtk universal tab. Can anyone please tell that what this option is used for and ticking it will lead to any sort of issues?
Click to expand...
Click to collapse
dont use it, will erase all the device data and partitions turning it into a useless brick, dude, in youtube there a lots of tutos to how restore original firmware go check them first

tutibreaker said:
dont use it, will erase all the device data and partitions turning it into a useless brick, dude, in youtube there a lots of tutos to how restore original firmware go check them first
Click to expand...
Click to collapse
Ok bro thanks for telling, will not use it for flashing

Did it work is it debricked?

Manmeet_2008 said:
I have redmi note 10s. I bacame bored of miui because of several bugs. So i decided to mod the device with a nice custom rom. I started the process. Because it is a mtk device, it has complicated flashing process than snapdragon devices. I entered the fastbootD mode and cleared the system by using adb command(which i dont remember). Then i flashed the custom rom. By mistake, I locked the bootloader by typing adb command fastboot oem lock. But now due to complicated case, the device is showing your system has been destroyed and when i try to force reboot it into fastboot, it still give systen destroyed error(means fastboot mode is inaccessible). Can anyone please help me to fix this issue without using edl pins? I am in a great issue
Click to expand...
Click to collapse
You need to sSee this video,
Make sure Disconnect your phone battery then start flash

hookkrox said:
You need to sSee this video,
Make sure Disconnect your phone battery then start flash
Click to expand...
Click to collapse
You need to see the PM I've sent to you. You will find it here.

Start from BROM mode - that is always available. Then you can use mtktool to restore everything. I have an article about it on my blog, but I am not supposed to post it here... find it in my profile, or send me a PM for help.