Database Develop

Is my phone's bootloader really unlockable?

Model Number - Samsung-SM-G920A
Android Version - 7.0
Android Security Patch Level - August 1, 2017
Baseband Version - G920AUCS6EQH1
Kernel Version - 3.10.61-10950877, [email protected] #1, Aug 10 2017
Build Number - NRD90M.G920AUCS6EQH1
Knox Version 2.7.1
So I've just finished spending about 6 hours trying to root this phone. I've tried about 8 different root methods involving one-click applications, odin, and minimal adb fastboot tool without any success. I've also tried installing several different S6 specific TWRP .tar files using odin without any success. At this point, I'm thinking all this failure has to be due to a locked bootloader, however, I also can't even successfully check the bootloader status. None of the service menu dial codes I've come across have opened a menu that has the "service info" option needed to check the bootloader status. And all the other methods for checking bootloader status involve putting the phone into fastboot mode, which I don't think this phone has (only odin mode and recovery mode). When I issue the "adb reboot bootloader" command into the adb it just restarts the phone normally (no fastboot mode). My developer options screen also doesn't have that "OEM unlocking" option I keep reading about.
So my question is - Is there some step I'm missing, or is this phone's bootloader just unlockable? And if it is unlockable, is there any other way I can root the phone? All I want to do is delete all the bloatware off the phone, nothing fancy. Thank you to whoever takes the time to offer their help

jbora1788 said:
Model Number - Samsung-SM-G920A
Android Version - 7.0
Android Security Patch Level - August 1, 2017
Baseband Version - G920AUCS6EQH1
Kernel Version - 3.10.61-10950877, [email protected] #1, Aug 10 2017
Build Number - NRD90M.G920AUCS6EQH1
Knox Version 2.7.1
So I've just finished spending about 6 hours trying to root this phone. I've tried about 8 different root methods involving one-click applications, odin, and minimal adb fastboot tool without any success. I've also tried installing several different S6 specific TWRP .tar files using odin without any success. At this point, I'm thinking all this failure has to be due to a locked bootloader, however, I also can't even successfully check the bootloader status. None of the service menu dial codes I've come across have opened a menu that has the "service info" option needed to check the bootloader status. And all the other methods for checking bootloader status involve putting the phone into fastboot mode, which I don't think this phone has (only odin mode and recovery mode). When I issue the "adb reboot bootloader" command into the adb it just restarts the phone normally (no fastboot mode). My developer options screen also doesn't have that "OEM unlocking" option I keep reading about.
So my question is - Is there some step I'm missing, or is this phone's bootloader just unlockable? And if it is unlockable, is there any other way I can root the phone? All I want to do is delete all the bloatware off the phone, nothing fancy. Thank you to whoever takes the time to offer their help
Click to expand...
Click to collapse
Mine is the same. However you can use minimal ADB Fastboot to manually uninstall most apps. I used the 'app inspector' app to see what to type to uninstall them. Be sure you know what you are uninstalling! .youtube.com/watch?v=VjDn56jNTbQ

Huawei P9 - Failed TWRP attempt

Hello friends, I'm Berat, living in Istanbul, Turkey.
I tried to install TWRP on my device (HUAWEI P9) for root yesterday. I couldn't go further from the Fastboot - ADB method. Although I do one-to-one with source videos from Youtube, I have encountered error messages. The phone is running like stable but I have a few problems with my phone.
1- I want to complete root if i can do that.
2- OEM Unlocking is unclickable now and this is disable now, and of course it can't be changed. :victory:
3- I wanted to go back to the original version but it doesn't work either, OEM Unlocking is same; unclickable. I did enter the Fastboot menu and i saw the last status: Phone - Unlocked / FRP - Locked
How should I proceed? Which one is the easier, ROOT or the original version?
Thank you!

beratkazal said:
Hello friends, I'm Berat, living in Istanbul, Turkey.
I tried to install TWRP on my device (HUAWEI P9) for root yesterday. I couldn't go further from the Fastboot - ADB method. Although I do one-to-one with source videos from Youtube, I have encountered error messages. The phone is running like stable but I have a few problems with my phone.
1- I want to complete root if i can do that.
2- OEM Unlocking is unclickable now and this is disable now, and of course it can't be changed. :victory:
3- I wanted to go back to the original version but it doesn't work either, OEM Unlocking is same; unclickable. I did enter the Fastboot menu and i saw the last status: Phone - Unlocked / FRP - Locked
How should I proceed? Which one is the easier, ROOT or the original version?
Thank you!
Click to expand...
Click to collapse
- Which stock Android do you have, Marshmallow, Nougat or Oreo
- Which TWRP are you flashing
EMUI versions are different, each has different organization of partitions (names and sizes, different encryption types).
You must use different port of TWRP for different version of stock Android.
Wrong TWRP may not work or may even cause a brick
For Nougat, instructions are in this thread:
https://forum.xda-developers.com/newreply.php?do=newreply&noquote=1&p=71244945
but a little bit newer version of TWRP for Nougat is in the post #1 here:
https://forum.xda-developers.com/p9/development/rom-huawei-p9-magicrainbow-v4-t3759292
---
For disabled and grayed out OEM Unlocking:
Boot to eRecovery (switch off, connect to charger, press and keep pressing Vol+, press Power).
From eRecovery, choose Download and Install latest firmware and recovery.
Upon installation (before booting to System), choose Factory reset and Clear Cache
You will need to enable again Developer options and OEM unlock (it should not be gray anymore).
If Bootloader will be locked, unlock with the same, previous code

zgfg said:
- Which stock Android do you have, Marshmallow, Nougat or Oreo
- Which TWRP are you flashing
EMUI versions are different, each has different organization of partitions (names and sizes, different encryption types).
You must use different port of TWRP for different version of stock Android.
Wrong TWRP may not work or may even cause a brick
For Nougat, instructions are in this thread:
https://forum.xda-developers.com/newreply.php?do=newreply&noquote=1&p=71244945
but a little bit newer version of TWRP for Nougat is in the post #1 here:
https://forum.xda-developers.com/p9/development/rom-huawei-p9-magicrainbow-v4-t3759292
---
For disabled and grayed out OEM Unlocking:
Boot to eRecovery (switch off, connect to charger, press and keep pressing Vol+, press Power).
From eRecovery, choose Download and Install latest firmware and recovery.
Upon installation (before booting to System), choose Factory reset and Clear Cache
You will need to enable again Developer options and OEM unlock (it should not be gray anymore).
If Bootloader will be locked, unlock with the same, previous code
Click to expand...
Click to collapse
Thank you for answer to me. But i have another problem... Visit here please: https://forum.xda-developers.com/p9/help/help-huawei-p9-device-unlocked-booting-t3932699
Thanks...

[Guide] T-Mobile OP 7 Pro, Flash Firmware - Unlock Bootloader - TWRP & ROOT

Greetings, and a brief disclaimer;
--Disclaimer--
I am not responsible if you lose data or your device grows legs and runs away from you...
by following any of the instructions in this post, you take sole responsibility whatever happens to you or your device and any one else involved.
--Throughout this process we will be continuously wiping the device.--
--This tutorial flashes the International Firmware, you will not be running T-Mobiles Firmware.--
--If you want T-Mobiles Firmware this is not for you.--
---------------
Greetings fellow T-Mobile OnePlus 7 Pro Users and Developers!
I am excited after much frustration and beating my head against the wall, screaming profanities at T-Mobile & OnePlus for locking down this amazing phone.
Me and my Friend have FINALLY found out how to Bootloader Unlock, TWRP and ROOT the OnePlus 7 Pro from T-Mobile!
I know this is a longer guide, but that is because there were quite a few steps for the T-Mobile variant. A few snags were hit with the T-Mobile variant so that's why this guide is so lengthy.
The extra benefit of this guide is:
* You will have the DUAL SIM feature working. - I can confirm as I have placed two SIM's in the device and switched between them, T-Mobile disabled one of the OP 7 Pro SIM Slots, but with the Firmware Flash you get it back, I find that Flashing to International Firmware an important step as your getting a major feature of the device back. --Though you will need to buy a Dual SIM tray if you want to use two SIM's, this is where I bought mine: OnePlus 7 Pro DUAL SIM Tray
* You will get working Sound, if you go straight to Android Q from the flash and install TWRP * Magisk you will have audio issues. - I didn't think to test what else went wrong, but that I know did.
* DRM is working, I can stream Netflix content.
* Audio Fixes and Camera Features appear and sound great.
* I have not had stability issues such as crashes, reboot or other unwanted.
* WiFi, Bluetooth, DUAL GSM Radio's working properly.
* You can switch between the services of both SIM's properly via the pulldown menu, as well you can set up SIM defaults for particular actions.
* T-Mobiles VoLTE is working, as is VoWiFi. - Nice if your like me and live primarily in a basement apartment and get crap signal.
* You will not need to get T-Mobile's stupid Bootloader Unlock Token (BUT), that can take upwards of two weeks to get, to unlock the bootloader with this method. -- Skip the line, Yes please! I like skipping past BUT's.
--What you need to do first!--
You MUST get your phone Permanently CARRIER UNLOCKED BEFORE YOU ATTEMPT ANYTHING HERE!!!
----
--GUIDE--
1. I applied T-Mobiles: (9.5.9 Security Patch) I saw and installed it on July 23rd 2019 - This was needed in order to get the Flashing tool to work as it would get stuck on Param because without that patch the EDL would not allow the tool to flash the OnePlus 7 Pro.
2. I enabled ADB Debugging and used: TOOL ALL IN ONE to install my OnePlus 7 Pro Drivers, I also enabled Advanced Reboot in Developer Options.
2a. If you don't know how to enable Developer Options or ADB Debugging & Advanced Reboot here is how...
2b. Go into Settings, About Phone, TAP Build Number until it pops up that you are a developer (if you have a password/fingerprint set up it will ask you to put it in.).
2c. Go to Settings, System, Advanced Options, Developer Options.
2d. Enable, Advanced Reboot, USB Debugging.
3. I followed the Tutorial on this link to install the International Firmware (WARNING THIS WILL WIPE YOUR Phones DATA!!!): [GUIDE]How to convert TMobile OP7 to International.
4. I then updated the phone through the phones OTA updater via Settings, System, System Updates all the way until it had no more updates. ( If we installed Android Q before this we found that the speaker had issues during a Google Duo call. So something about how this all stacks and builds up together breaks if you don't do this in order.)
5. We then downloaded and placed: Android Q Beta onto the root of the OnePlus 7 Pro storage.
5a I went to Settings, System, System Update, Options, Local Upgrade.
5b If you have the Android Q firmware in the right place you will get that as an option to flash, once it's done click the button to reboot.
6. Unlocking the Bootloader.
6a. Enable Developer Options.
6b. Now we enable OEM Unlocking, and Advanced Reboot if not already. ( If you did not previously get your device Permanently SIM Unlocked you will not be able to enable OEM Unlocking, and you will be stuck unless you flash back to T-Mobile's Firmware and use their proprietary SIM Unlock APP. ).
6c. Press power button and reboot to Bootloader.
6d. Run the command ( fastboot oem unlock ). It should ask you on the phones screen if you want to, say yes.
6e. Run the command ( fastboot oem device-info ). Check to see if the bootloader unlock is True or False, True is expected. If False unlock the bootloader via other methods.
7. Booting TWRP & Flashing TWIRP + Magisk.
This was a bit tricky as the existing tutorials did not work with my device and I had to add a step.
First get the TWRP.IMG & TWRP Installer ZIP files ready as well grab Magisk by downloading them here: Official/Unofficial TWRP recovery for OnePlus 7 Pro. & Magisk
7a. Run the command ( fastboot boot TWRP.IMG ) The phone should then boot into what looks like full TWRP, well sorta, it's not really installed yet.
7b. If 7a fails as it did with me Run the Command ( fastboot set_active b ) then try 7a command again, if that fails as well run ( fastboot set_active a ). and repeat.
7c. Once you have booted TWRP put the TWRP installer ZIP on the phone in the root directory.
7d. Now we get the Magisk installer zip on the root of the phone as well.
7e. Now we install TWRP installer ZIP first then Magisk installer ZIP.
Reboot - Enjoy and install custom ROMs & Kernels!

--reserved--

<Mod edit - quoted OP removed>
I get the failed message you talk about in step 7b. When I try to run the commands "fastboot set_active b" it doesn't recognize that command or the other to set to a. I'm stuck not being able to install TWRP and proceed to root. Any ideas?

kevnfl77 said:
<Mod edit - quoted OP removed>
I get the failed message you talk about in step 7b. When I try to run the commands "fastboot set_active b" it doesn't recognize that command or the other to set to a. I'm stuck not being able to install TWRP and proceed to root. Any ideas?
Click to expand...
Click to collapse
I'm having the same issue, though I didnt carrier unlock my phone. Have you done that?
---------- Post added at 07:53 PM ---------- Previous post was at 07:35 PM ----------
@Inductive Soul would appreciate any feedback you might have regarding this. I followed the process using the Q Preview 3

weakNPCdotCom said:
I'm having the same issue, though I didnt carrier unlock my phone. Have you done that?
---------- Post added at 07:53 PM ---------- Previous post was at 07:35 PM ----------
@Inductive Soul would appreciate any feedback you might have regarding this. I followed the process using the Q Preview 3
Click to expand...
Click to collapse
Yes I was carrier unlocked.

If anybody comes here looking to root, this guide does not work. You need to follow the guide to convert to international

Help please, unlocked bootloader and tried to install twrp image. Screen stayed stuck on fastboot screen with the one + symbol.?

I was wondering if network bands change after flashing to international rom. Will it continue to be NA region or will it change?

Correct you need to first flash to international version. Then use this guide.
Tool ALL in one does not work anymore with this phone. - I recommend you do not use this method any more as its method I used will no longer work.
weakNPCdotCom said:
If anybody comes here looking to root, this guide does not work. You need to follow the guide to convert to international
Click to expand...
Click to collapse

kevnfl77 said:
<Mod edit - quoted OP removed>
I get the failed message you talk about in step 7b. When I try to run the commands "fastboot set_active b" it doesn't recognize that command or the other to set to a. I'm stuck not being able to install TWRP and proceed to root. Any ideas?
Click to expand...
Click to collapse
Yes, change it back and forth (Your goal is to get Fastboot Boot TWRP.IMg to boot.... so switch your active... A-B partition with step 7b and try 7a again on each partition.... a and b. one or the other will work depending on what partition is currently active.):
7A: fastboot boot TWRP.IMG
7B: fastboot set_active a - to - fastboot set_active b

gearmaker said:
I was wondering if network bands change after flashing to international rom. Will it continue to be NA region or will it change?
Click to expand...
Click to collapse
My experience has been that all the existing bands have worked the same... I have continued to connect to T-Mobile's 600 + 700 Mhz spectrum.
I have been running the International Firmware since the initial posting of this guide.

I thought that they would be the same after flashing.Just wanted to confirm.
Thank you

Just got this phone today, and I just want to make sure I'm clear. If I go through these steps, I'll be on Q DP3, but I don't need to go through the waiting period via T-Mobile (I bought my phone outright) but after I get on DP3, can I then flash the International stock ROM and be good, or will I always have to use a custom ROM after doing these steps?? I saw somewhere that Bootloader unlocked is grayed out after you go to DP3 and then International ROMs. Thanks.

Hi, On my T-Mobile O7pro
I tried the command
Fastboot boot TWRP.img
It replaced my stock boot image and now I can't boot again, even to the supposed TWRP recovery
I also switched partitions countless times and tried same process.
I'll appreciate if I get a feedback. Thanks

Hi,
Please someone experienced a black screen in Qhd and 90Hz after doing that, in the 11.0.2.* ??
thx in advance.

Question The current image (boot/recovery) have been destroyed

Welp, first day of owning the OnePlus Ace and I've already bricked it lmao. Need some help in trying to unbrick it.
So last night I successfully rooted my device using magisk, but after experimenting I just decided to revert back to being unrooted, since I realised I didn't actually need many of the functions root allows. Derooted using Magisk, checked that it was unrooted, then went into fastboot mode to re-lock the bootloader. Did so, restarted and I was presented with the dreaded "The current image (boot/recovery) have been destroyed" error screen and endless bootlooping. I cannot access fastboot mode or recovery mode with button combinations, tried holding Vol + and power, Vol - and power but no dice. I believe I ended up bricking because I forgot to flash the stock vbmeta.img before locking the bootloader.
I've made some progress in getting to the MediaTek Emergency Download Mode (which I believe is also either called BROM or Preloader) in order to flash a stock rom. I found out that holding down both Vol + and Vol - at boot will enable this emergency download mode for a few seconds, before going to the destroyed boot/recovery error screen. The issue is, while I've managed to get the phone detected by my computer in this state in COM5 as a 'MediaTek PreLoader USB VCOM_V1632 (Android), none of the programs said to flash a stock rom will detect it. I've tried mtk_client, mtk bypass tool, SP Flash, even regular fastboot and adb tools, but none of them will detect the device, even though Windows does.
The only smart thing I did was refraining from transferring all of my files from my old phone to this one, so luckily I've got a phone to fall back on. Basically, until I find a fix, the Ace will have to stay in it's box makes me wish I never messed with root in the first place lmao. And because I imported the phone there's no warranty and no service centres for OnePlus in my country that can help.
Anyone have any ideas for how I can get the phone detected in these applications? Is it an issue of the SoC not being supported yet by these programs because it's relatively new? Are there any alternate ways to get to the fastboot menu? Any help would be greatly appreciated!
Thanks!

Update: If someone would be able to extract a scatter file from their own OnePlus Ace too, I think that may help me

Sorry that you've ran into this, but thanks for confirming bootloader can be unlocked, and root is possible.
Getting the 10R over the Realme GT 2 (sad situation of bootloader unlock not possible). Hope you get an extract soon

Made some progress!
Got my hands on the Ace's firmware files, which included the scatter file. Redownloaded the newest 6.2 version of SP Flash Tool and loaded the scatter and auth files successfully. Clicked download, connected USB to phone while holding Vol + and Vol - and finally! Sp Flash Tool connected to the phone! However, now I've run into another problem: SP Flash Tool will show a red progress bar at the bottom saying 'Download DA', it will reach 100% quickly then throw me a very vague error simply saying 'error_msg'. And that's it. Tried unchecking different boxes, reinstalled drivers but it will always throw back this error.
Any ideas to figure out what the error is and fix it would be amazing

hello, im here to show support. My ace also bricked because i want to change from color os to oxygen. I used fastboot enhanced, might have missed a step and bricked. Mine also import, but the shop i bought offers 1 year warranty. Shop says have to wait for msm download tools to reflash or i have to pay $60 to send back to China because my own fault. Man, it is going to be a long wait for msm tools. haha

KeepingKeyes said:
saying 'error_msg'.
Click to expand...
Click to collapse
try the mtk client and command - python mtk payload,and try sp flashtool again.please also share the files for firmware

DimRim said:
try the mtk client and command - python mtk payload,and try sp flashtool again.please also share the files for firmware
Click to expand...
Click to collapse
Tried this method, but didn't work. Kept giving me a "Handshake failed: retrying" error when connecting the phone to the computer.
Here's a link the the firmware: OnePlus Ace Firmware

KeepingKeyes said:
Tried this method, but didn't work. Kept giving me a "Handshake failed: retrying" error when connecting the phone to the computer.
Here's a link the the firmware: OnePlus Ace Firmware
Click to expand...
Click to collapse
maybe this is because of the new chip and there is no support for bypassing it.I thought the method would work.also a tip-edit the scatter file, namely partition_name: super or system,changing the value is_download: false to is_download: true.hopefully help
And thank you for sharing the files

I too am stuck with Brick.
Is there a Bypass for the Demesity 8100 being developed?
This device is mostly Oppo, but there is no Oppo flash Tool?
There is very little information available.

KeepingKeyes said:
Welp, first day of owning the OnePlus Ace and I've already bricked it lmao. Need some help in trying to unbrick it.
So last night I successfully rooted my device using magisk, but after experimenting I just decided to revert back to being unrooted, since I realised I didn't actually need many of the functions root allows. Derooted using Magisk, checked that it was unrooted, then went into fastboot mode to re-lock the bootloader. Did so, restarted and I was presented with the dreaded "The current image (boot/recovery) have been destroyed" error screen and endless bootlooping. I cannot access fastboot mode or recovery mode with button combinations, tried holding Vol + and power, Vol - and power but no dice. I believe I ended up bricking because I forgot to flash the stock vbmeta.img before locking the bootloader.
I've made some progress in getting to the MediaTek Emergency Download Mode (which I believe is also either called BROM or Preloader) in order to flash a stock rom. I found out that holding down both Vol + and Vol - at boot will enable this emergency download mode for a few seconds, before going to the destroyed boot/recovery error screen. The issue is, while I've managed to get the phone detected by my computer in this state in COM5 as a 'MediaTek PreLoader USB VCOM_V1632 (Android), none of the programs said to flash a stock rom will detect it. I've tried mtk_client, mtk bypass tool, SP Flash, even regular fastboot and adb tools, but none of them will detect the device, even though Windows does.
The only smart thing I did was refraining from transferring all of my files from my old phone to this one, so luckily I've got a phone to fall back on. Basically, until I find a fix, the Ace will have to stay in it's box makes me wish I never messed with root in the first place lmao. And because I imported the phone there's no warranty and no service centres for OnePlus in my country that can help.
Anyone have any ideas for how I can get the phone detected in these applications? Is it an issue of the SoC not being supported yet by these programs because it's relatively new? Are there any alternate ways to get to the fastboot menu? Any help would be greatly appreciated!
Thanks!
Click to expand...
Click to collapse
Still stuck or were you able to find any solution?

yashaswee1708 said:
Still stuck or were you able to find any solution?
Click to expand...
Click to collapse
Unfortunately not yet, the most promising option will be to wait for an MTK Auth Bypass utility to be developed for the Dimensity 8100 chipset. There might be active development on this front, so hopefully it will come soon.
The other option would be to find someone to do a remote flash, someone who has official Oppo/OnePlus flashing software and an account to use it. I believe I've found the official firmware to flash the phone in this state, however you need credentials to log in to it and access it. I think it will also specifically have to be Chinese credentials, as India login details may not allow you to flash a OnePlus Ace model. I tried to get someone over at (<Moderator Edit>: unallowed site name removed) to do a remote flash, and he couldn't because he had India credentials, but not Chinese credentials

KeepingKeyes said:
Unfortunately not yet, the most promising option will be to wait for an MTK Auth Bypass utility to be developed for the Dimensity 8100 chipset. There might be active development on this front, so hopefully it will come soon.
The other option would be to find someone to do a remote flash, someone who has official Oppo/OnePlus flashing software and an account to use it. I believe I've found the official firmware to flash the phone in this state, however you need credentials to log in to it and access it. I think it will also specifically have to be Chinese credentials, as India login details may not allow you to flash a OnePlus Ace model. I tried to get someone over at (<Moderator Edit>: unallowed site name removed) to do a remote flash, and he couldn't because he had India credentials, but not Chinese credentials
Click to expand...
Click to collapse
Oh. I had OnePlus 7 previously, there were few ways to flash stock firmware. The common one was MSM Tool, other one was Fastboot enhance.
But few times I flashed stock firmware manually like payload dump payload.bin and flash partitions manually from fastboot. Maybe this could work.

yashaswee1708 said:
Oh. I had OnePlus 7 previously, there were few ways to flash stock firmware. The common one was MSM Tool, other one was Fastboot enhance.
But few times I flashed stock firmware manually like payload dump payload.bin and flash partitions manually from fastboot. Maybe this could work.
Click to expand...
Click to collapse
I seem to have made fastboot inaccessible on my device, so I've been unable to use Fastboot enhance or utilise any ways to flash using fastboot

Damn!! I hope you find some way to fix your device. Good luck.

关于一加ACE如何优雅的刷入氧OS12.1这件事 来自 天伞桜 - 酷安

I create instruction, if you phone boot to fastboot mode
OnePlus 10R/Ace - Официальные прошивки - 4PDA
OnePlus 10R/Ace - Официальные прошивки
4pda.to
i`ts in russian, but you can use translate

GTAstar said:
I create instruction, if you phone boot to fastboot mode
OnePlus 10R/Ace - Официальные прошивки - 4PDA
OnePlus 10R/Ace - Официальные прошивки
4pda.to
i`ts in russian, but you can use translate
Click to expand...
Click to collapse
Hello. after unlocking the bootloader I have the message "Orange State. OS Not Being Verified Or Custom OS. Dismiss After 5 Seconds." but the system booted up. After uploading boot.img, the phone got stuck in bootloop. Unfortunately, the guide above did not help.

hamsteer said:
Hello. after unlocking the bootloader I have the message "Orange State. OS Not Being Verified Or Custom OS. Dismiss After 5 Seconds." but the system booted up. After uploading boot.img, the phone got stuck in bootloop. Unfortunately, the guide above did not help.
Click to expand...
Click to collapse
Are you still able to boot to Fastboot?

yashaswee1708 said:
Are you still able to boot to Fastboot?
Click to expand...
Click to collapse
Yes. I can flash files in cmd and FastbootEnhance but in practice it looks like they were not saved.

hamsteer said:
Yes. I can flash files in cmd and FastbootEnhance but in practice it looks like they were not saved.
Click to expand...
Click to collapse
So you are not able to boot right?
If not, you can try flashing the partitions manually from fastboot. (If you are willing to try I can provide the steps. This works for other OnePlus devices.)

phone flash with "flash_all_lock.bat", now I can't do anything

I accidentally flash my phone with official rom in miflassh with flash_all_lock.bat option now after i reboot my phone there had a message file storage corrupted your device is unsafe now. I try to again unlock the bootloader but mi account cannot activate my sim. tried with new sim and account but no reasult. Always says couldnt verify your sim card. for this, i cannot turn on the find device and add account with my phone. I tried all searched ways but no reasult. i tried downgrade with rename rom method, try xiamitoolv2 no reasult.
Now pleas can anyone help me to unlock the bootloader with any idea. It will be really appreciated. Thanks in advance.

Can you still boot into fastboot mode?
If so,
1. For newer devices (2015 and higher):
fastboot flashing unlock
2. For older devices (2014 and lower)
fastboot oem unlock

I had the same problem a month ago and finally solved, you should make some changes to a file of the official ROM released by Xiaomi and re-flash it by activating the Qualcomm 9008 mode, in which you can ignore the bootloader lock