Database Develop

SOFT BRICK using tool Xiaomi Mi A2

Hi guys, i need some help pleeease!
I was with the November security patch on my cell phone, I unlock the bootloader and went to use the friend tool (https://forum.xda-developers.com/mi-a2/how-to/mi-a2-toolkit-unlock-bootloader-root-t3834585) to activate the camera2api.
But it gave problem and the cell phone did not turn on, it was locked in the screen of android one.
So I downloaded the patched_boot.img from the version I was in and put it via fastboot. did not work.
Now, my phone is in this situation: I tried to use MiFlash (three versison: 2018528, 2017720 and 20151028) and they fail in the middle of the process, accusing "FAILED (command write failed (Unknown error))".
And: when I try to connect the cell phone normally, it shows the unlocked bootloader warning and goes straight to the fastboot, even without my request. This is strange. Perhaps because the system is damaged by the miflash unfinished
Obs: bootloader are unlocked and i can access twrp
If anyone can help me I will be very grateful and happy

What exactly did the "tool" do? I mean if you don't know that, pretty difficult to diagnose what's wrong...

AsItLies said:
What exactly did the "tool" do? I mean if you don't know that, pretty difficult to diagnose what's wrong...
Click to expand...
Click to collapse
Hi.
The tool (her topic link is up there) promised to activate camera2api without root my device (allowing OTAs in the future).
I believe she did a "temporary root" with a "temporary" boot.img just to activate the camera2api, and when it rebooted, it would return to normal boot.img without root. I do not know if I could explain it well.
The current issue is that it seems that the system is currently "destroyed or corrupted". Can not I reinstall the entire system through TWRP? Or something like this

Like I said, you don't know what it actually did. What it promised is one thing, what it did... another
That's the problem with 'tools'.
Have you tried doing a factory reset? Hold Vol up and power until it gets to Recovery (hopefully), if you do a quick press of vol up, that gets past the 'no command'. Then use vol up and down for selection and press power when on 'factory reset'.
It might work

AsItLies said:
Like I said, you don't know what it actually did. What it promised is one thing, what it did... another
That's the problem with 'tools'.
Have you tried doing a factory reset? Hold Vol up and power until it gets to Recovery (hopefully), if you do a quick press of vol up, that gets past the 'no command'. Then use vol up and down for selection and press power when on 'factory reset'.
It might work
Click to expand...
Click to collapse
You are right, friend.. this is the problems with tools! I never use tools with my A1 and past phones.. just this time :crying:
I tried the factory reset now. And it did not work, unfortunately. On the first attempt (I was in fastboot mode) he showed a white circle with the writing "ERASING" and then went back to the screen of Android One, and then I tried again Vol Up + Power and he appeared "No command" , and after I rebooted and tried again, nothing appears, it just restarts to the static screen of "Android One"
Another ideas?

erickxd said:
You are right, friend.. this is the problems with tools! I never use tools with my A1 and past phones.. just this time :crying:
I tried the factory reset now. And it did not work, unfortunately. On the first attempt (I was in fastboot mode) he showed a white circle with the writing "ERASING" and then went back to the screen of Android One, and then I tried again Vol Up + Power and he appeared "No command" , and after I rebooted and tried again, nothing appears, it just restarts to the static screen of "Android One"
Another ideas?
Click to expand...
Click to collapse
The only other thing I can think of would be to change the current slot. If that works you would be booted into the prior version of the OS vs the latest update you did.
In fastboot, do fastboot getvar current-slot
Depending on what that slot is, change it to the other one (can only be a or b)
thus fastboot set_active a (or b, whichever is not the current one)
then fastboot reboot - and hope it boots.

AsItLies said:
The only other thing I can think of would be to change the current slot. If that works you would be booted into the prior version of the OS vs the latest update you did.
In fastboot, do fastboot getvar current-slot
Depending on what that slot is, change it to the other one (can only be a or b)
thus fastboot set_active a (or b, whichever is not the current one)
then fastboot reboot - and hope it boots.
Click to expand...
Click to collapse
Well... fastboot don't recognize this command, he show the list of avaible commands
And i don't know why, but for now i can't boot in twrp.img
i'm going crazy :crying::crying::crying:

erickxd said:
Well... fastboot don't recognize this command, he show the list of avaible commands
And i don't know why, but for now i can't boot in twrp.img
i'm going crazy :crying::crying::crying:
Click to expand...
Click to collapse
That's probably because you have an old version of fastboot installed. Upgrade to the newest version, which should recognize dual slots.
dual slots are quite new.

AsItLies said:
That's probably because you have an old version of fastboot installed. Upgrade to the newest version, which should recognize dual slots.
dual slots are quite new.
Click to expand...
Click to collapse
Fastboot updated now! I changed the slot from B to A.
But doesn't work, unfortunately. After reboot, the phone can't boot and appears the screen asking between Try Boot Again or Factory Reset. I tried Factory Reset, but don't work =( return to the same screen.
What seems very strange to me, is the Miflash doesn't work. With my Mi A1 miflash ever save me

erickxd said:
Fastboot updated now! I changed the slot from B to A.
But doesn't work, unfortunately. After reboot, the phone can't boot and appears the screen asking between Try Boot Again or Factory Reset. I tried Factory Reset, but don't work =( return to the same screen.
What seems very strange to me, is the Miflash doesn't work. With my Mi A1 miflash ever save me
Click to expand...
Click to collapse
I've never used miflash, so no help there.
I'd try flashing the correct boot.img (for your software version). You can find the various boot images in the following link (don't forget to thank user ckpv5 for uploading these).
https://sourceforge.net/projects/others/files/Xiaomi_MiA2/
you would do fastboot flash boot_b boot.img
I'd suggest using b slot, as that was originally active. After flashing, set it back to active, try to reboot... then cross your fingers

AsItLies said:
I've never used miflash, so no help there.
I'd try flashing the correct boot.img (for your software version). You can find the various boot images in the following link (don't forget to thank user ckpv5 for uploading these).
https://sourceforge.net/projects/others/files/Xiaomi_MiA2/
you would do fastboot flash boot_b boot.img
I'd suggest using b slot, as that was originally active. After flashing, set it back to active, try to reboot... then cross your fingers
Click to expand...
Click to collapse
Doesn't work man.. I went to twrp and checking there in the "WIPES session", I saw that the SYSTEM partition is 0kb used and 0kb free. Appears to be entirely empty
Do not have a way to install the whole system via twrp?

erickxd said:
Doesn't work man.. I went to twrp and checking there in the "WIPES session", I saw that the SYSTEM partition is 0kb used and 0kb free. Appears to be entirely empty
Do not have a way to install the whole system via twrp?
Click to expand...
Click to collapse
No, I don't. But I can tell you, twrp is a recovery app. It shouldn't be in the boot slot. And, with dual slot configurations, there is no recovery partition. The other slot is now used to do a recovery.
In other words, the way we *used* to use twrp doesn't work on dual slot phones. I think that's a big part of the confusion people are having. While the boot images do have a small recovery part to them, it's not a separate partition.
If you're flashing boot.img, and setting that slot active, I've no idea how you're getting into twrp.

Since now your fastboot is working why don't you use miflash to flash official stock ROM
1. You need unlocked bootloader which you already have.
2. Run these command to unlock critical partition
fastboot flashing unlock_critical
3 . Download the official fastboot V9.6.14.0 ROM from
https://forum.xda-developers.com/mi-a2/how-to/ota-v9-6-5-0-odimife-t3823445
Or here
http://en.miui.com/getrom.php?r=353&m=yes&app=false
4. Install with miflash (you already know the how-to)
5. Once up & running, do OTA to latest
Later .. redo what you want to do like enable camera api2 with proper guide.
E.g: https://forum.xda-developers.com/mi-a2/how-to/how-to-enable-cam2api-simply-ota-t3858861

ckpv5 said:
Since now your fastboot is working why don't you use miflash to flash official stock ROM
1. You need unlocked bootloader which you already have.
2. Run these command to unlock critical partition
fastboot flashing unlock_critical
3 . Download the official fastboot V9.6.14.0 ROM from
https://forum.xda-developers.com/mi-a2/how-to/ota-v9-6-5-0-odimife-t3823445
Or here
http://en.miui.com/getrom.php?r=353&m=yes&app=false
4. Install with miflash (you already know the how-to)
5. Once up & running, do OTA to latest
Later .. redo what you want to do like enable camera api2 with proper guide.
E.g: https://forum.xda-developers.com/mi-a2/how-to/how-to-enable-cam2api-simply-ota-t3858861
Click to expand...
Click to collapse
Hello.
I've tried using Miflash several times (3 different versions), but it never ends, it end up with an error every time that he will copy the file system.img to the mobile phone (I analyzed the log).
The miflash divides the file system.img into 5 or 6 smaller parts to be able to transfer to the mobile phone, and in some of these parts gives error, everytime :crying:

AsItLies said:
No, I don't. But I can tell you, twrp is a recovery app. It shouldn't be in the boot slot. And, with dual slot configurations, there is no recovery partition. The other slot is now used to do a recovery.
In other words, the way we *used* to use twrp doesn't work on dual slot phones. I think that's a big part of the confusion people are having. While the boot images do have a small recovery part to them, it's not a separate partition.
If you're flashing boot.img, and setting that slot active, I've no idea how you're getting into twrp.
Click to expand...
Click to collapse
I can access twrp when I flash ''fastboot boot twrp.img" in powershell, so until the next reboot I have access to twrp

erickxd said:
Hello.
I've tried using Miflash several times (3 different versions), but it never ends, it end up with an error every time that he will copy the file system.img to the mobile phone (I analyzed the log).
The miflash divides the file system.img into 5 or 6 smaller parts to be able to transfer to the mobile phone, and in some of these parts gives error, everytime :crying:
Click to expand...
Click to collapse
When I read your post here - https://forum.xda-developers.com/showpost.php?p=78085858&postcount=188
"flashing is not allowed for critical partitions" usually due to critical partitions not unlocked. So .. if you already run "fastboot flashing unlock_critical" and you still have error using miflash .. nothing much I can offer to help. Hopefully you'll be able to fix it.

ckpv5 said:
When I read your post here - https://forum.xda-developers.com/showpost.php?p=78085858&postcount=188
"flashing is not allowed for critical partitions" usually due to critical partitions not unlocked. So .. if you already run "fastboot flashing unlock_critical" and you still have error using miflash .. nothing much I can offer to help. Hopefully you'll be able to fix it.
Click to expand...
Click to collapse
Hmm thanks for the answer!
Even when the operation fails after transfer a couple of archives before the system.img??? (on the Miflash)
If my phone was locked, Miflash could transfer these couple of archives before the operation fails?? Or if bootloader is locked, zero files can be passed by Miflash, and the error is apresented at the beginning of the operation?

Have you successfully unlocked critical partitions?
If yes, try to run flash_all.bat from the official stock image you downloaded. No need to use MiFlash.

prokaryotic cell said:
Have you successfully unlocked critical partitions?
If yes, try to run flash_all.bat from the official stock image you downloaded. No need to use MiFlash.
Click to expand...
Click to collapse
well... When I just run flash_all.bat from the stock image folder, the .bat file will recognize that I am running it for the connected mobile?
how exactly should I run flash_all.bat? just double clicking it in stock image folder? or should I copy the .bat to /adb folder and open power shell prompt in adb folder and execute the .bat from there? sorry for my ignorance
Can you show me, please?

erickxd said:
well... When I just run flash_all.bat from the stock image folder, the .bat file will recognize that I am running it for the connected mobile?
how exactly should I run flash_all.bat? just double clicking it in stock image folder? or should I copy the .bat to /adb folder and open power shell prompt in adb folder and execute the .bat from there? sorry for my ignorance
Can you show me, please?
Click to expand...
Click to collapse
Before someone can explain that, why don't you answer the question asked .. in fact at least 3 people was asking/telling ...
"Have you successfully unlocked critical partitions?"
Without the proper answer from you, not easy to help.

Question regarding bootloop

Hi all,
First of let me start by saying I have a Mi 9T and I know that it has its own forum, but I didn't find a solution to my problem there, so I thought I'd ask in this forum as well, since the devices look a lot like each other but here are more people.
So my problem is I got stuck in a bootloop which I can't seem to get out of. I can boot into fastboot mode and adb fastboot AND Miflash recognize my device, so I'm able to flash things, but the bootloop still stays.
I started on global rom, and then installed twrp. Then I flashed the latest 9.7.25 ROM from mi-globe for MI 9T. It booted up fine, but my TWRP was removed and I couldn't install it anymore like the first time. For some reason I did a factory reset then. And tried to flash a new ROM by using MiFlash. It said it was succesfull, but it only took 1 second and it didn't automatically boot (it stayed in fastboot mode). I tried again and it said anti-rollback error.
So that didn't work, so I tried flashing boot.img, recovery.img and system,img seperately by using adb fastboot. That worked and it booted normally. I went through the startup configuration like selecting wifi network and gmail,etc. But after trying to set a fingerprint, the screen went completely black but the phone was still on. I could reboot it normally, but when the lockscreen came up or I tried to use fingerprint scanner it went black completeley every time.
I was desperate, so I used 'fastboot erase system -w' in adb fastboot, which is a factory reset apparently. Then I flashed the 3 .img files like I did before, but this time it didn't boot, but went into bootloop.
I also tried 'fastboot boot twrp.img' which also didn't get me into twrp, it just goes to bootloop again.
So to summarize: I CAN get into fastboot and adb fastboot and miflash DO recognize my device, but I can't get out of bootloop no matter what I flash.
Does anyone know a solution for this problem? I would be very thankful.
I also don't understand why flashing or booting TWRP doesn't work, while it worked the first time. I also don't understand why flashing the 3 .img files doesn't work this time, like it used to work the first time.
Btw my anti getvar is 1.

Are you using windows 10? Had same issue with MiFlash and had to use a laptop with earlier version of Windows to get it working

DaveHTC200 said:
Are you using windows 10? Had same issue with MiFlash and had to use a laptop with earlier version of Windows to get it working
Click to expand...
Click to collapse
I do, but I don't have anything else than that. Are you sure that was the problem and not something else?

Rapydax said:
I do, but I don't have anything else than that. Are you sure that was the problem and not something else?
Click to expand...
Click to collapse
I've not had your issue but that was causing the flash tool to just carry out the task in 1 second, which isn't possible

i have the same situation here. did your issue solve?

The system has been destroyed

Hello, after unsuccessful OTA update my phone doesnt boot into Android any more.
I had an original, untouched xiaomi system (not a custom one, not rooted etc).
Bootloader locked like default.
I think update.zip could be faulty - I have no idea how.
I am able to run Fastboot but due locked BL I cannot do much there.
I deasemble phone, pull out the battery, connected EDL pinouts with a wire, and all this togetcher connecter to PC.
Phone is visible by PC.
Downloaded ROM, and tried to flash via MI Flash..
On last moment I am getting error with information that my mi.com account is not athourised to do such a thing.
I tried also Mi Flash Pro founded on Cyanogenmod forum, but without luck - still getting same error.
Does anyone know how to get out from this situation or should I rather open warranty process in Gearbest?

sabbath88 said:
Hello, after unsuccessful OTA update my phone doesnt boot into Android any more.
I had an original, untouched xiaomi system (not a custom one, not rooted etc).
Bootloader locked like default.
I think update.zip could be faulty - I have no idea how.
I am able to run Fastboot but due locked BL I cannot do much there.
I deasemble phone, pull out the battery, connected EDL pinouts with a wire, and all this togetcher connecter to PC.
Phone is visible by PC.
Downloaded ROM, and tried to flash via MI Flash..
On last moment I am getting error with information that my mi.com account is not athourised to do such a thing.
I tried also Mi Flash Pro founded on Cyanogenmod forum, but without luck - still getting same error.
Does anyone know how to get out from this situation or should I rather open warranty process in Gearbest?
Click to expand...
Click to collapse
Just flash a custom recovery, the device even had the offical twrp. So?? Just not into fastboot and then flash the recovery by the -- command
fastboot flash recovery recovery.img
(You have to rename the twrp file to recovery or whatever, just write the image file name instead of recovery in the second one. Ex fastboot flash recovery 123.img)
Then command
Fastboot reboot
(Hold the power up button for booting into twrp before hitting enter)
Download a miui recovery rom for your device from anywhere, I don't know I'm lazy.
And before flashing, go into mount select vendor and system if not selected.
And then select wipe
Advanced wipe
Select vendor system data cache.
Swipe to clean
Move the rom to your device
(If your device does not show up in your pc, then go into mount (twrp) select enable MTP if it's disabled, if it shows disabled then enable it again)
After that just flash your rom and then a permissive patch you can ask anyone. Or just flash pitchblack recovery. Fixed my problem of not not booting.
Sorry for the wrong format, wrote it on mobile, as I am a lazy bum.
Wut bruh.

Something similar happened to my friend's Poco F1. It was locked and I only could boot into fastbook, looked everywhere for a solution and found this lifesaving tool . It may work for Redmi 8 too.

ChakibDEV said:
Something similar happened to my friend's Poco F1. It was locked and I only could boot into fastbook, looked everywhere for a solution and found this lifesaving tool . It may work for Redmi 8 too.
Click to expand...
Click to collapse
thanks so much, that helped

ASUS ROG2 SOFT BRICK

Hi ,
I have an ASUS ROG2 and I'm experiencing quite a problem here , I would like to know if this can still be rescue or not? or maybe I'm missing some steps here. here's what I've done so far.
Before it got to this dilemma my phone is suffering from autoshutdown so i rooted my phone using magisk and applied the thermal mode by one of the OP here. everything is working fine , the phone is not shutting down until today. it suddenly restart before me and it is stuck in ROG Logo.
what I've done.
1) i flash the stock boot img for my firmware version 2009.49 using fastboot flash boot 2009.49stock.img both slot A & B then followed by fastboot reboot so it can boot to system but it is still stock at the ROG Logo
2) i downloaded a RAW Firmware of 2009.49 , put my phone into fastboot mode. i made sure it was detected by the PC using the command fastboot devices and surely it was. i execute the flashall_AFT.cmd and waited , after it finishes my phone reboots but still stuck at the ROG Logo and here's the problem.
I reboot my phone into bootloader , scroll to Recovery after pressing Power button to select it , it boots and stuck at the ROG Logo at this point i'm confused since i need to factory reset it. so i downloaded TWRP for ROG2 Android 10 the one i usually use then i tried to boot from it using fastboot boot twrp10.img , it only boots and stuck at the ROG Logo again
3) I tried to flash a firmware using EDL mode , everything went well without any errors and there's the success message in Xiaomiflashtool , i reboot the phone to recovery and it is still stuck in ROG Logo.
any guesses? I'm kinda lost here since both RAW and EDL are not working.

KnowThyPro said:
Hi ,
I have an ASUS ROG2 and I'm experiencing quite a problem here , I would like to know if this can still be rescue or not? or maybe I'm missing some steps here. here's what I've done so far.
Before it got to this dilemma my phone is suffering from autoshutdown so i rooted my phone using magisk and applied the thermal mode by one of the OP here. everything is working fine , the phone is not shutting down until today. it suddenly restart before me and it is stuck in ROG Logo.
what I've done.
1) i flash the stock boot img for my firmware version 2009.49 using fastboot flash boot 2009.49stock.img both slot A & B then followed by fastboot reboot so it can boot to system but it is still stock at the ROG Logo
2) i downloaded a RAW Firmware of 2009.49 , put my phone into fastboot mode. i made sure it was detected by the PC using the command fastboot devices and surely it was. i execute the flashall_AFT.cmd and waited , after it finishes my phone reboots but still stuck at the ROG Logo and here's the problem.
I reboot my phone into bootloader , scroll to Recovery after pressing Power button to select it , it boots and stuck at the ROG Logo at this point i'm confused since i need to factory reset it. so i downloaded TWRP for ROG2 Android 10 the one i usually use then i tried to boot from it using fastboot boot twrp10.img , it only boots and stuck at the ROG Logo again
3) I tried to flash a firmware using EDL mode , everything went well without any errors and there's the success message in Xiaomiflashtool , i reboot the phone to recovery and it is still stuck in ROG Logo.
any guesses? I'm kinda lost here since both RAW and EDL are not working.
Click to expand...
Click to collapse
You could try booting into TWRP 3.4.0-0 Q Unofficial by mauronofrio without flashing ( fastboot boot twrp-3.4.0-0-I001D-Q-mauronofrio.img ) , then copy the zip over to root of internal storage, either 2009.49 or lastest 2012.65, from here. Be sure to check during flash which slot gets flashed first. Then repeat the process, booting twrp so that you can flash the other inactive slot. If you want to be sure you have changed slots, click on reboot in twrp and see which is active before flashing. Good luck
Hopefully flashing both slots successfully will do it. Let us know how you get on.

reg66 said:
You could try booting into TWRP 3.4.0-0 Q Unofficial by mauronofrio without flashing ( fastboot boot twrp-3.4.0-0-I001D-Q-mauronofrio.img ) , then copy the zip over to root of internal storage, either 2009.49 or lastest 2012.65, from here. Be sure to check during flash which slot gets flashed first. Then repeat the process, booting twrp so that you can flash the other inactive slot. If you want to be sure you have changed slots, click on reboot in twrp and see which is active before flashing. Good luck
Hopefully flashing both slots successfully will do it. Let us know how you get on.
Click to expand...
Click to collapse
Hi Reg !
Thanks for replying , i think I'm using the official version of TWRP so I'll give this a try , i should overcome the obstacle of booting into TWRP..
I'll let you know the outcome.

KnowThyPro said:
Hi Reg !
Thanks for replying , i think I'm using the official version of TWRP so I'll give this a try , i should overcome the obstacle of booting into TWRP..
I'll let you know the outcome.
Click to expand...
Click to collapse
Any news?

reg66 said:
Any news?
Click to expand...
Click to collapse
I used the TWRP you've linked. and i'm afraid that it is stuck on the rog logo again..
what i've done. ' fastboot boot twrpQ3400.img ' after i sent that command , the phone reboots and instead of going to twrp , it goes to rog logo and stuck there.
is there anyway i could check if there's partition? it feels like the phone has no partition that's why it is always going back to the rog logo.

KnowThyPro said:
I used the TWRP you've linked. and i'm afraid that it is stuck on the rog logo again..
what i've done. ' fastboot boot twrpQ3400.img ' after i sent that command , the phone reboots and instead of going to twrp , it goes to rog logo and stuck there.
is there anyway i could check if there's partition? it feels like the phone has no partition that's why it is always going back to the rog logo.
Click to expand...
Click to collapse
Did you change the name of the twrp file? the fastboot boot twrp-3.4.0-0-I001D-Q-mauronofrio.img cmd must have an identical name to the file, which as the original should be twrp-3.4.0-0-I001D-Q-mauronofrio.img
and just to be sure, you have the twrp img in fastboot folder, correct?

reg66 said:
Did you change the name of the twrp file? the fastboot boot twrp-3.4.0-0-I001D-Q-mauronofrio.img cmd must have an identical name to the file, which as the original should be twrp-3.4.0-0-I001D-Q-mauronofrio.img
and just to be sure, you have the twrp img in fastboot folder, correct?
Click to expand...
Click to collapse
Yes i did rename it as twrpQ3400.img and yes also , it is in the same folder as my adb & fastboot folder enviroment.
i'll try a different approach maybe using QFIL? although i don't know where to start like finding the XML / Programmer or firehose..
any ideas?

KnowThyPro said:
Yes i did rename it as twrpQ3400.img and yes also , it is in the same folder as my adb & fastboot folder enviroment.
i'll try a different approach maybe using QFIL? although i don't know where to start like finding the XML / Programmer or firehose..
any ideas?
Click to expand...
Click to collapse
Well i'm running out of ideas, never used QFIL so wouldn't know. since you cannot boot into twrp (i'm assuming you didn't relock bootloader? twrp won't work with locked bootloader), you could try this thread. be sure to use the supplied 1910.35 images as it tried and tested. read posts 1 and 2 at the very least, post 2 has useful steps
if successful, you'll then need to update 1910.64 before android 10 2004.60 to start with, then up to latest

reg66 said:
Well i'm running out of ideas, never used QFIL so wouldn't know. since you cannot boot into twrp (i'm assuming you didn't relock bootloader? twrp won't work with locked bootloader), you could try this thread. be sure to use the supplied 1910.35 images as it tried and tested. read posts 1 and 2 at the very least, post 2 has useful steps
if successful, you'll then need to update 1910.64 before android 10 2004.60 to start with, then up to latest
Click to expand...
Click to collapse
yes , i didn't lock my bootloader since i can still see the bootloader unlock message.. i'm also running low in ideas , for worst it is a bricked phone at best. i'll check the link.
thanks for helping. i'll still update this thread to maybe update u as well.
edit: i checked the link , i already did the xiaomi flash tool approach on the link.. everything was a success with no errors... maybe i shud give qpst tool a try? although i'm not familiar using it.

KnowThyPro said:
yes , i didn't lock my bootloader since i can still see the bootloader unlock message.. i'm also running low in ideas , for worst it is a bricked phone at best. i'll check the link.
thanks for helping. i'll still update this thread to maybe update u as well.
edit: i checked the link , i already did the xiaomi flash tool approach on the link.. everything was a success with no errors... maybe i shud give qpst tool a try? although i'm not familiar using it.
Click to expand...
Click to collapse
did you remember to shut the phone down after successfully flashing, boot into recovery and wipe data, then reboot? as per the instructions...?

reg66 said:
did you remember to shut the phone down after successfully flashing, boot into recovery and wipe data, then reboot? as per the instructions...?
Click to expand...
Click to collapse
yes , ofcourse since the phone is in EDL mode the only way to shut it down is by using Power + volume up + volume down like around 15 seconds then phone will shutdown since the 9008 COM in device manager will be gone this means that it's no longer in EDL mode. i wait like 1minute before i power it up to recovery by power + volume down then scroll to recovery in bootloader. then with no luck still stuck to Rog logo..
it's like the recovery partition is gone...

KnowThyPro said:
yes , ofcourse since the phone is in EDL mode the only way to shut it down is by using Power + volume up + volume down like around 15 seconds then phone will shutdown since the 9008 COM in device manager will be gone this means that it's no longer in EDL mode. i wait like 1minute before i power it up to recovery by power + volume down then scroll to recovery in bootloader. then with no luck still stuck to Rog logo..
it's like the recovery partition is gone...
Click to expand...
Click to collapse
I've been googling for you dude but no joy yet.... will have another look tomorrow

reg66 said:
I've been googling for you dude but no joy yet.... will have another look tomorrow
Click to expand...
Click to collapse
Thanks man , i'm searching for the qfil approach but i'm getting a sahara error. currently searching for fixes
edit : i manage to boot the phone using the link you've provided by using QFIL approach and not thru XiaomiFlashTool
the phone boots successfully and i can use the recovery again ! although there's a problem , it can't read my sim card and everything is like stock android without any skins or what.. i used the RAW firmware to update it but the problem with stuck logo is back :/
gonna re-flash using QFIL and i'll check some more ~ maybe use TWRP and flash the firmware there no?
edit: the one from the link is not working , stuck at rog logo.. but the one from the internet i was able to boot to system but can't detect simcard , also when plugging to PC it will go to crashdump mode.
also can't flash TWRP will result in stuck at ROG logo :/

was able to boot the phone but can't connect to wifi and is locked by google frp :/ any guides i can follow to remove that FRP without wifi connection ?

Sorry bud, really not sure what's going on with your phone or know much more. Good luck with it tho

KnowThyPro said:
was able to boot the phone but can't connect to wifi and is locked by google frp :/ any guides i can follow to remove that FRP without wifi connection ?
Click to expand...
Click to collapse
Actually, if you now have recovery, what about booting into twrp and flashing lastest 2012.65 zip from asus website, twice - both slots. see if that fixes your wifi issue
As you said using the QFIL approach worked to boot into system and recovery is back - boot to twrp from that state

KnowThyPro said:
Thanks man , i'm searching for the qfil approach but i'm getting a sahara error. currently searching for fixes
edit : i manage to boot the phone using the link you've provided by using QFIL approach and not thru XiaomiFlashTool
the phone boots successfully and i can use the recovery again ! although there's a problem , it can't read my sim card and everything is like stock android without any skins or what.. i used the RAW firmware to update it but the problem with stuck logo is back :/
gonna re-flash using QFIL and i'll check some more ~ maybe use TWRP and flash the firmware there no?
edit: the one from the link is not working , stuck at rog logo.. but the one from the internet i was able to boot to system but can't detect simcard , also when plugging to PC it will go to crashdump mode.
also can't flash TWRP will result in stuck at ROG logo :/
Click to expand...
Click to collapse
I think my i messed my phone like yours. Can you provide me step by step? I have tried those step one by one but still stuck at rog logo

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.