Database Info

Can't unlock bootloader after upgrade

Hi
My phone is international NXT-L29
I was on Ephemeral B180 rom but i decided to upgrade it to get emui 4.1
I flashed back stock b180 rom, and after I flashed stock b321 rom
ROM works great but i would like to get root and twrp back again, but everytime I try to go through fastboot i get this screen on picture.
I logged into my dc unlocker again and followed the procedures (manufacture mode, unlocking,...) and dc unloccker tool informs that the phone was unlocked...but no, when I do adb reboot bootloader i still get the same message on the picture.
I saw other suggestions here on XDA, i confirm oem unlock is activated on developer options...i made factory reset and then "vol+- power" (with or without phone connected to PC) but i dont't get any option to unlock bootloader. I always arrive to a menu saying that the phone is looking for upgrade and tries until 5% is reached... (if I keep waiting it does not fisplat error message, only waits and waits and after a while it reboots normally (i don't have any dload folder either on phone or sd card)
Any suggestion to solve this is highly appreciated
many thanks

Try to get ur unlock code from huawei website maybe this can help.

Did you run the bootloader unlock command with your unlock code again?

Ephemera said:
Did you run the bootloader unlock command with your unlock code again?
Click to expand...
Click to collapse
the only command my phone accept is adb reboot bootloader
Then i get the screen of picture that I posted, which says that it is a cold reboot (?)
Whem I reach this point it doens not respond to anything else taht I type on Command line (I type fastboot oem unlock (and the code) but on pc screen i read 'ewaiting device' and nothing happens on phone

gm007 said:
Try to get ur unlock code from huawei website maybe this can help.
Click to expand...
Click to collapse
I retrived my code from DC Unlocker (it has an option to read bootload code) but the problem is thar when I get de Fastboot&Rescue Mode the phone does not react to any command i can type on PC

Can I replace the stock boot.img that comes inside the UPDATE.APP file byone decrypted boot image of same rom?
If that would be possible then flashing this "modified" UPDATE.APP would solve the problem?
Many Thanks

pasil.pt said:
I retrived my code from DC Unlocker (it has an option to read bootload code) but the problem is thar when I get de Fastboot&Rescue Mode the phone does not react to any command i can type on PC
Click to expand...
Click to collapse
Hi pasil.pt,
try to update the fastboot mode driver
http://forum.xda-developers.com/showpost.php?p=69382774&postcount=202

grofock said:
Hi pasil.pt,
try to update the fastboot mode driver
http://forum.xda-developers.com/showpost.php?p=69382774&postcount=202
Click to expand...
Click to collapse
I don't see any kedacom usb device folder...

Check if the device isnfound by the computer. Restart in fastboot mode then on your computer type "fastboot devices" you should get a device and its serial. If you're not getting anything its a driver issue.

Ephemera said:
Check if the device isnfound by the computer. Restart in fastboot mode then on your computer type "fastboot devices" you should get a device and its serial. If you're not getting anything its a driver issue.
Click to expand...
Click to collapse
I did not try the command fastboot devices, but as per the new picture attached when I run adb devices the computer finds my phone
the problem is, then, when next i run 'adb reboot bootloader'...the device goes into fastboot&rescue mode and the device is not recognized by computer anymore

pasil.pt said:
I did not try the command fastboot devices, but as per the new picture attached when I run adb devices the computer finds my phone
the problem is, then, when next i run 'adb reboot bootloader'...the device goes into fastboot&rescue mode and the device is not recognized by computer anymore
Click to expand...
Click to collapse
Open control panel when your phone is in this state (it's fastboot mode) and you should see the folder I talked about.

It seems drivers issue, i hate windows 10
Try different usb port,and try to remove the drivers and install them again.
Make sure no usb device connected to any other ports.

grofock said:
Open control panel when your phone is in this state (it's fastboot mode) and you should see the folder I talked about.
Click to expand...
Click to collapse
YES!!!!!!
many thanks to you. grofock, and to ephemera, and XDA
At last i got it done. (Huawei are so tricky compared to samsung...but at least they do not explode

gm007 said:
It seems drivers issue, i hate windows 10
Try different usb port,and try to remove the drivers and install them again.
Make sure no usb device connected to any other ports.
Click to expand...
Click to collapse
You were probably right because i recently changed PC and aeverytime w10 upgrades I pray...

Have the the same problem, but didn't find the solution. Try different laptops and different cables. Windows can't recognise my Mate 8 L29 after B320 update cause of the wrong descriptor.

timasan said:
Have the the same problem, but didn't find the solution. Try different laptops and different cables. Windows can't recognise my Mate 8 L29 after B320 update cause of the wrong descriptor.
Click to expand...
Click to collapse
try grofock's hints about control panel and Device manager on windows....

pasil.pt said:
try grofock's hints about control panel and Device manager on windows....
Click to expand...
Click to collapse
I try it on four different PCs and still error 43 "wrong descriptor".

timasan said:
I try it on four different PCs and still error 43 "wrong descriptor".
Click to expand...
Click to collapse
Maybe explain more what you did,what are you trying to do and which tools you used.

gm007 said:
Maybe explain more what you did,what are you trying to do and which tools you used.
Click to expand...
Click to collapse
I'm trying to install drivers for Mate 8. I did it on different PC with Win 10 and 7. With different cables. Try to change or delete drivers for USB hub and etc. In fastboot mode and normal with usb debug and w/o.

timasan said:
I'm trying to install drivers for Mate 8. I did it on different PC with Win 10 and 7. With different cables. Try to change or delete drivers for USB hub and etc. In fastboot mode and normal with usb debug and w/o.
Click to expand...
Click to collapse
Did you install hisuite it has all the drivers and make sure to enable allow hisuite to use hdb in phone settings under security.

Question How would I use fastboot commands to retrieve my lockscreen pin code?

My daughter locked herself out of a nokia mediatek helio p22 by pin lock. During my relentless searching I came across an article showing how to use fastboot cmd commands to get the userdata pin password encryption and how to decipher it by taking out certain things. To be able to enter into the phone. I CAN'T FIND THE ARTICLE NOW!! . The phone itself will not hard reset by hardware keys. Will not enter into recovery mode only fastboot works. I've tried using many screen unlocking software but they all say device not supported o need usb debugging which I can't enable. Fastboot erase userdata ver throws up errors. Does anyone know the fastbood I'm looking for. I've tried all other possibilities that I can find. Any and all help would be greatly appreciated.

Fastboot operates on device's bootloader, not on Android OS. The FRP code is stored within Android file system what can only get accessed by ADB.

jwoegerbauer said:
Fastboot operates on device's bootloader, not on Android OS. The FRP code is stored within Android file system what can only get accessed by ADB.
Click to expand...
Click to collapse
Correct I know. But the device isn't recognized with adb only fastboot recognizes it. I've tried erasing the device with all fastboot commands and everything results in error. When I try to fastboot recovery it has the no command andriod guy and if I press any hardware buttons it reboot back to lock screen. Do u have any ideas on a work around. Or how to access the userdata using cmd promt?

Try to connect phone in USB-MTP mode via a USB-C cable - requires phone supports USB-C.

@Tlink00
Plug up to your PC and do:
sudo fastboot -w (push enter)
That will format data and erase everything on the device, pictures and all. If you are trying to get in your phone I've been able to delete lockscreen.db and a few other directories using TWRP file manager in the past on OnePlus 6t and also on a few Motorola phone's I've owned. But I believe you have to have encryption disabled to go that route. Best to just wipe it with fastboot -w. Just be sure you know your password to your Google account because if your phones signed in and has a Google account on it the password will be required to use the device again.

Tlink00 said:
My daughter locked herself out of a nokia mediatek helio p22 by pin lock. During my relentless searching I came across an article showing how to use fastboot cmd commands to get the userdata pin password encryption and how to decipher it by taking out certain things. To be able to enter into the phone. I CAN'T FIND THE ARTICLE NOW!! . The phone itself will not hard reset by hardware keys. Will not enter into recovery mode only fastboot works. I've tried using many screen unlocking software but they all say device not supported o need usb debugging which I can't enable. Fastboot erase userdata ver throws up errors. Does anyone know the fastbood I'm looking for. I've tried all other possibilities that I can find. Any and all help would be greatly appreciated.
Click to expand...
Click to collapse
I can send you tools that support the Nokia 2.2/2.3 (I'm assuming from chipset) that can erase user data and frp

areallydumbperson said:
I can send you tools that support the Nokia 2.2/2.3 (I'm assuming from chipset) that can erase user data and frp
Click to expand...
Click to collapse
Yeah...that be great! I'm willing to try anything. But the usb debugging isn't enabled.

flash713 said:
@Tlink00
Plug up to your PC and do:
sudo fastboot -w (push enter)
That will format data and erase everything on the device, pictures and all. If you are trying to get in your phone I've been able to delete lockscreen.db and a few other directories using TWRP file manager in the past on OnePlus 6t and also on a few Motorola phone's I've owned. But I believe you have to have encryption disabled to go that route. Best to just wipe it with fastboot -w. Just be sure you know your password to your Google account because if your phones signed in and has a Google account on it the password will be required to use the device again.
Click to expand...
Click to collapse
I've tried the fastboot -w but it comes up with an error about not having permission. Idk about the encryption being disabled or not. And I haven't been successful with TWRP even coming up. Maybe I'm missing something

jwoegerbauer said:
Try to connect phone in USB-MTP mode via a USB-C cable - requires phone supports USB-C.
Click to expand...
Click to collapse
Are you taking about changing it in the PC device manager properties? Bc I don't have access to change it on the device itself. I will try it though. I'll let u know what happens. Thanks for the idea!

Have found it that your Nokia 2.2 supports OTG.

Tlink00 said:
Yeah...that be great! I'm willing to try anything. But the usb debugging isn't enabled.
Click to expand...
Click to collapse
Doesn't matter because it uses fastboot and the way the tool works bypasses permission errors

areallydumbperson said:
Doesn't matter because it uses fastboot and the way the tool works bypasses permission errors
Click to expand...
Click to collapse
Ok thanks! I'll let u know if it works!

Tlink00 said:
Ok thanks! I'll let u know if it works!
Click to expand...
Click to collapse
did it work?

areallydumbperson said:
did it work?
Click to expand...
Click to collapse
I haven't had a chance to try it, yet. But I will really soon. I'm very eager to use it.

areallydumbperson said:
did it work?
Click to expand...
Click to collapse
It says request permission fail. I have phone in fastboot mode

Nvm I GOT IT!!! OMG u are a life savor. Thank you, thank you,thank you!!! I've been working on this for 2 months now. Thank u so much!!

Tlink00 said:
Nvm I GOT IT!!! OMG u are a life savor. Thank you, thank you,thank you!!! I've been working on this for 2 months now. Thank u so much!!
Click to expand...
Click to collapse
Haha np

Having the same issue here, my son locked his nokia with a passcode he can't remember. Unable to get it into recovery mode, stuck on "no command"

djekl said:
Having the same issue here, my son locked his nokia with a passcode he can't remember. Unable to get it into recovery mode, stuck on "no command"
Click to expand...
Click to collapse
should be able to get in by pressing power + volume up or power + volume down at that no command screen

Tried that, just got back from the local phone repair shop, and they were unable to factory reset it also, and get past the no command screen.

Forgot password vivo v17 pro

Good morning, I'm fixing my daughter's vivo v17 pro. Forgot her screen lock password. The phone doesn't have a forgot password option and Google's find my phone was not activated. USB debugging isn't enabled. What utility tool should I use? Thank you very much!

Tool will unlock your phone. But it will also erase your data from phone.

You may require to do factory reset your phone. It will remove password and data.

ciyan38284 said:
You may require to do factory reset your phone. It will remove password and data.
Click to expand...
Click to collapse
Thank you, I tried clear data option but it again asks for the password. USB debugging isn't enabled and google account was signed out before. I read that if you enter fastboot mode, USB debugging is not needed? But I ran it on windows 10 and I can't find it on device manager. It only shows up on devices and printers as an unspecified device when it is powered on.

kellystams said:
Tool will unlock your phone. But it will also erase your data from phone.
Click to expand...
Click to collapse
Thanks, what tool is it? SDK tools? Do I have to tear it down to get to the edl test points or will minimal adb and fastboot work? It's working properly but I need to reset it because the screen lock password was forgotten and it was logged out of Google beforehand. It's a vivo v17 pro 1910 with FBE encryption.

Rooting problem and strange phone behaviour while it

Hello. I'm an owner of a Xiaomi Redmi 9A and I have following rooting problems with it:
1. while beeing in phone's fastboot mode and after sending from the computer's terminal (after sucessfull connection):
"fastboot oem unlock"
the phone "thinks" for a short bit before restarting itself without doing anything
2. I have a Xiaomi account bound to the phone and when selecting the "check unlock state" the phone ask me to turn off wifi, enable the (paid) data transfer and bind the phone to the account
3. while using the official Xaiomi unlock tool (with was downloaded from the phone producer's website), the phone isn't even seen in it
Could anyone help me ?

Try installing usb drivers or the phone will never be detected.

VD171 said:
Try installing usb drivers or the phone . never be detected.
Click to expand...
Click to collapse
in case of adb and fastboot, I had used them on Linux.
Only the official unlocking tool was for Windows, on with the usb drivers were installed.
Linux detect it without any issue

Just use it to unlock on Linux:
XiaoMiTool V2 - Modding of Xiaomi devices made easy for everyone
XiaoMiTool V2 is a easy to use tool to install rom on your Xiaomi device. Modding made easy for everyone! Download it for free now!
xiaomitool.com

VD171 said:
Just use it to unlock on Linux:
XiaoMiTool V2 - Modding of Xiaomi devices made easy for everyone
XiaoMiTool V2 is a easy to use tool to install rom on your Xiaomi device. Modding made easy for everyone! Download it for free now!
xiaomitool.com
Click to expand...
Click to collapse
thanks, but it seem to don't work correctly with my phone.
After my phone had become detected when was in the fastboot mode and after clicking the "select" button in the app, the phone has rebooted to the normal mode and asked to scan again. It hasn't done anything except the mentioned above.

mcgiwer said:
thanks, but it seem to don't work correctly with my phone.
After my phone had become detected when was in the fastboot mode and after clicking the "select" button in the app, the phone has rebooted to the normal mode and asked to scan again. It hasn't done anything except the mentioned above.
Click to expand...
Click to collapse
Did you enable usb debugging on developer settings?
Did you allow the usb debugging for the actual computer?

VD171 said:
Did you enable usb debugging on developer settings?
Did you allow the usb debugging for the actual computer?
Click to expand...
Click to collapse
yes in both cases... I have even enabled the "oem unlock" option in the setting

Install windows on partition 30Gb, change cable

yaro666 said:
Install windows on partition 30Gb, change cable
Click to expand...
Click to collapse
The cable is new and I won't wipe my Linux to install a Windows (about with I have a bad opinion)

Make a dual boot, just resize partition, you need 30Gb and in 45min you will know what is the problem.
Or you can try to liveboot windows from usb stick.

yaro666 said:
Make a dual boot, just resize partition, you need 30Gb and in 45min you will know what is the problem.
Or you can try to liveboot windows from usb stick.
Click to expand...
Click to collapse
Question: Why do you push so much on me to install Windows?
This forum is dedicated to mobile phones and my topic is about anormal phone behaviour of a phone while attempt to root it. Wiping out a safe Linux and installing a Windows won't help at all....
I tryed to root the phone on friend's laptop with a Windows (with the latest drivers and software installed) and it didn't worked.
I suspect that the producer probably has fabrically instaled a damaged or improper firmware

As you wish. Windows is more device friendly. I just suggest to do it on W, nothing more.
You state that fastboot works, but Linux don't see your phone, like in case you don't have drivers for adb. We don't know if you installed everything on Linux properly

yaro666 said:
As you wish. Windows is more device friendly. I just suggest to do it on W, nothing more.
You state that fastboot works, but Linux don't see your phone, like in case you don't have drivers for adb. We don't know if you installed everything on Linux properly
Click to expand...
Click to collapse
hello. You had missread my post. I wrote that it isn't seen only in the unlock software. Fastboot and ADB detect it correctly

Xiaomi device bricked after reboot

My Xiaomi Redmi Note 8 Pro isn't booting anymore.
I'm stuck in the fastboot screen, I don't even reach the redmi logo in the boot, I need to recover the data on the phone but I have no idea about how to do that.
Any suggestions?
(Already tried going to recovery with power down + volume up, isn't working)

I'm stuck in the fastboot screen
Click to expand...
Click to collapse
I'm assuming you have Fastboot.
Was USB Debugging ON before the device got bricked? If yes then:
> Download TWRP Recovery for Redmi Note 8 Pro from twrp website. Rename the file to: twrp.img
> Download latest Xiaomi USB Drivers for PC from Internet.
> Download 15-Seconds-ADB-Installer for PC from Internet.
> After Installation is over, Restart PC > Windows Explorer > This PC/ My Computer > ADB Folder > Press SHIFT+Right Click Mouse+Open Powershell Window Here > New window opens
> Transfer the twrp.img file to ADB folder.
> Now you can try connecting the XRN8Pro to the PC (while the Fastboot screen is on)
> On the Powershell window you can type one by one:
1) fastboot devices
2) fastboot boot twrp.img
> Your XRN8Pro phone should boot to TWRP Custom Recovery.
> On PC open another Windows Explorer tab and check if your phones Internal Storage is displayed. If yes you can try to copy your phone data to PC.
> After that in TWRP recovery Press Reboot to Bootloader option, It will show Fastboot screen.
> Download XRN8Pro Stock Firmware/Fastboot ROM from Internet to Desktop only.
> Download Mi Flash Tool for XRN8Pro. Double Click on XiaoMiFlash.exe file.
> Connect XRN8Pro to PC (while fastboot screen is on)
> Then on MiFlash window click on folder to link to firmware file on desktop & click on refresh button, then click on Flash. It takes about 17 minutes (for RN8 devices) to flash MIUI ROM.

OldNoobOne said:
I'm assuming you have Fastboot.
Was USB Debugging ON before the device got bricked? If yes then:
> Download TWRP Recovery for Redmi Note 8 Pro from twrp website. Rename the file to: twrp.img
> Download latest Xiaomi USB Drivers for PC from Internet.
> Download 15-Seconds-ADB-Installer for PC from Internet.
> After Installation is over, Restart PC > Windows Explorer > This PC/ My Computer > ADB Folder > Press SHIFT+Right Click Mouse+Open Powershell Window Here > New window opens
> Transfer the twrp.img file to ADB folder.
> Now you can try connecting the XRN8Pro to the PC (while the Fastboot screen is on)
> On the Powershell window you can type one by one:
1) fastboot devices
2) fastboot boot twrp.img
> Your XRN8Pro phone should boot to TWRP Custom Recovery.
> On PC open another Windows Explorer tab and check if your phones Internal Storage is displayed. If yes you can try to copy your phone data to PC.
> After that in TWRP recovery Press Reboot to Bootloader option, It will show Fastboot screen.
> Download XRN8Pro Stock Firmware/Fastboot ROM from Internet to Desktop only.
> Download Mi Flash Tool for XRN8Pro. Double Click on XiaoMiFlash.exe file.
> Connect XRN8Pro to PC (while fastboot screen is on)
> Then on MiFlash window click on folder to link to firmware file on desktop & click on refresh button, then click on Flash. It takes about 17 minutes (for RN8 devices) to flash MIUI ROM.
Click to expand...
Click to collapse
Thanks for the reply, this game me some hope, but I don't think USB Debugging was enabled.
I've never rooted or changed rom, I just rebooted the phone and apparently I triggered the rm -rf / command.

BrickedXiaomi said:
Thanks for the reply, this game me some hope, but I don't think USB Debugging was enabled.
I've never rooted or changed rom, I just rebooted the phone and apparently I triggered the rm -rf / command.
Click to expand...
Click to collapse
No problem, even then TWRP should allow MTP file transfer to PC, so follow all the steps and tell me what happens ok

OldNoobOne said:
No problem, even then TWRP should allow MTP file transfer to PC, so follow all the steps and tell me what happens ok
Click to expand...
Click to collapse
I'll try tomorrow, thanks for all the precious details btw!

Just a question, shouldn't I unlock the phone with mi unlocker before that?

BrickedXiaomi said:
Just a question, shouldn't I unlock the phone with mi unlocker before that?
Click to expand...
Click to collapse
You hadn't already? OMG! Sorry. Yup probably would need bootloader unlocking but you can try to lookup steps for Fastboot commands to unlock bootloader on the internet. But it shouldn't trigger a wipe of any sort or you might lose the data inside. Also, no harm in trying to load TWRP using Fastboot i think, just in case TWRP loads.

OldNoobOne said:
You hadn't already? OMG! Sorry. Yup probably would need bootloader unlocking but you can try to lookup steps for Fastboot commands to unlock bootloader on the internet. But it shouldn't trigger a wipe of any sort or you might lose the data inside. Also, no harm in trying to load TWRP using Fastboot i think, just in case TWRP loads.
Click to expand...
Click to collapse
As said, I never modified this phone, is basically as if it was brand new, OS side.

Maybe I can use https://forum.xda-developers.com/t/unlock-bootloader-without-losing-data.3864667/ to unlock the bootloader without loosing data?

BrickedXiaomi said:
Maybe I can use https://forum.xda-developers.com/t/unlock-bootloader-without-losing-data.3864667/ to unlock the bootloader without loosing data?
Click to expand...
Click to collapse
Wow thats great link, I hope it works so you don't lose data.
The link is fresh so you can also ask there. All the Best

Update: I've tried to contact Xiaomi about the issue.
They said they should be able to help me out with this stuff, and that I shouldn't flash my phone because it's really easy to brick.
I understand that it's the usual support recommendation, but it is possible that they know how to fix this issue?
What should I do, go for their way or go for myself?

BrickedXiaomi said:
Update: I've tried to contact Xiaomi about the issue.
They said they should be able to help me out with this stuff, and that I shouldn't flash my phone because it's really easy to brick.
I understand that it's the usual support recommendation, but it is possible that they know how to fix this issue?
What should I do, go for their way or go for myself?
Click to expand...
Click to collapse
Is your phone In-Warranty? If yes or no i would suggest go your own way, once purchased an used any device, don't connect with OEM servers ever again for any OTA update coz lots of recent cases about OEM(Original Equipment Manufatureres) killing devices with OTA updates and after that the phone doesnt boot, no recovery no fastboot too, so careful with contacting/updating through OEMs if out -of-warranty specially. Once out-of-warranty always use ROM channels to upgrade to new handroid versions instead of direct OTA upgrade/update, that way you may still be able to roll back the OS to previous version in case you don't like the new handroid version, lots of people don't like handroid 12 but they cant roll back to handroid 11 .

> recent cases about OEM(Original Equipment Manufatureres) killing devices with OTA updates
This is considered highly illegal in Europe, I could sue Xiaomi for that, in case, and would be an easy win.
Btw, I'm the one who bought this phone first, it's just out of warranty since I've bought it in nov-19.
After this data recovery I'll be out of the Android world forever, I just care about my data, currently.

BrickedXiaomi said:
> recent cases about OEM(Original Equipment Manufatureres) killing devices with OTA updates
This is considered highly illegal in Europe, I could sue Xiaomi for that, in case, and would be an easy win.
Btw, I'm the one who bought this phone first, it's just out of warranty since I've bought it in nov-19.
After this data recovery I'll be out of the Android world forever, I just care about my data, currently.
Click to expand...
Click to collapse
Yes they might not try doing that with uropean customers but they might try in other countries where there no proper legal system for things like these, also they wont do it with everyone in a particular country to avoid suspicion, theyre smart enough to know what theyre doing, but unofficially speaking many retailers have told me about such a thing (OTA Kill Device) happening in Weaker-Law-N-Order countries, so just saying precaution is always good.

BTW i've put my Retmi Noat 10 up for sale, its still in warranty & I havent used it in the last 10 months, no sim card, unused totally, just once I loaded Gcam to check how the camera is, shamshung is always better than chyneez phones mainly coz better build and component-life, chyneez devices only look shiny from outside but it doesnt last beyond 3-5 yrs, not built to last, just use-n-throw devices u knw. Such devices are only made for mass-surveillance in mind not with customers-focus. This A/B partition thing and super partition thing is adding more bad than good.

I don't think that trick will work. even if it would be possible to cheat that easy, encryption key is bonded* to bootloader lock state. so if you somehow magically managed to unlock bootloader without triggering factory reset, your data could no longer decrypted from android OS and is therefore lost.
Xiaomi support answered they can fix your phone, but they didn't say they can safe your data on it, right!? So try to get a full backup off your device in preloader mode (SLA/DAA bypass and VCOM drivers needed)
After that important step you can unlock bootloader with mtkclient, install TWRP and *proof me wrong (xiaomi devices are hackable/have weak security implementations). In any case do not perform factory reset, your backup is always only backup of android OS and therefore incomplete (there are several OS on every device)
btw fastboot doesn't require usb-debugging (that's adb, not fastboot)

Do you have a tutorial about it?
aIecxs said:
I don't think that trick will work. even if it would be possible to cheat that easy, encryption key is bonded to bootloader lock state. so if you somehow magically managed to unlock bootloader without triggering factory reset, your data could no longer decrypted from android OS and is therefore lost.
Xiaomi support answered they can fix your phone, but they didn't say they can safe your data on it, right!? So try to get a full backup of your device in EDL mode (patched firehose programmer and deep flash cable needed)
Click to expand...
Click to collapse