Hi all.
I'm looking for the Oppo Reno 10X to be my next device.
I've build custom roms in the past, when we were still on android 5, so I'm a bit rusty.
Kernel source is released, so that's nice!
Are there any developers currently working on this phone?
I'd like to combine our power, and share knowledge.
The first hurdle seems to be the proprietary blobs for this device, can anyone get them and provide them?
Can the bootloader be unlocked for this device?
mac231us said:
Can the bootloader be unlocked for this device?
Click to expand...
Click to collapse
good point, I assumed it could, because it's 2019. but apparently you can't...
It doesn't look hopeful, already months after release and no possibility to unlock the bootloader.
I asked Oppo (Netherlands) and they confirmed they won't release unlock codes for the Oppo reno.
I'd like to make 100% sure that it's not possible to unlock the bootloader, so if someone can confirm that [fastboot oem unlock] doesn't work,
and we can't request an unlock code here https://id.oppo.com/index.html ?
Then our next best option is through EDL:
- create twrp for oppo reno
- flash twrp through EDL
It's possible to flash a custom recovery through EDL. It has been possible on some devices to flash a custom rom through EDL with a locked bootloader.
Long short story(unlocked the bootloader,installed TWRP+magisk,damaged boot,bootloop,relocked bootloader ), i hard bricked my PCCM00 10x zoom, no stock recovery, locked bootloader and the bootloop with "The current image (boot/recovery) has been destroyed,please flash the correct image..)
I can only access the phone in EDL mode, in device manager appears under com ports- Qualcomm HS-USB QDloader 9008 .It s possible to flash boot/recovery using Qfil flashing tool of just with EDL commands?
mura69 said:
Long short story(unlocked the bootloader,installed TWRP+magisk,damaged boot,bootloop,relocked bootloader ), i hard bricked my PCCM00 10x zoom, no stock recovery, locked bootloader and the bootloop with "The current image (boot/recovery) has been destroyed,please flash the correct image..)
I can only access the phone in EDL mode, in device manager appears under com ports- Qualcomm HS-USB QDloader 9008 .It s possible to flash boot/recovery using Qfil flashing tool of just with EDL commands?
Click to expand...
Click to collapse
You've already posted this on your own thread. Avoid spamming the forums.
moozer said:
You've already posted this on your own thread. Avoid spamming the forums.
Click to expand...
Click to collapse
Thank you for your concern, this is not spam, it is related to the subject of this topic.In the future, try to avoid spamming topics with unnecessary posts.
Thank you
mura69 said:
Thank you for your concern, this is not spam, it is related to the subject of this topic.In the future, try to avoid spamming topics with unnecessary posts.
Thank you
Click to expand...
Click to collapse
Link to your original thread. Stop trying to be a smartass
Related
I've recently unlocked my bootloader and I wanted to re lock it. Well, I couldn't find any thread about this and I thought it would be good to open one. My question is obviously how to re lock the bootloader in Xiaomi Redmi Note 3 Snapdragon.
Xristomania said:
I've recently unlocked my bootloader and I wanted to re lock it. Well, I couldn't find any thread about this and I thought it would be good to open one. My question is obviously how to re lock the bootloader in Xiaomi Redmi Note 3 Snapdragon.
Click to expand...
Click to collapse
simply flash any official fastboot ROM using miflash.
sanjib734 said:
simply flash any official fastboot ROM using miflash.
Click to expand...
Click to collapse
With edl right?
sanjib734 said:
simply flash any official fastboot ROM using miflash.
Click to expand...
Click to collapse
Did it with the EDL and now i got hard brick. Now I am stuck at mi logo not even bootlooping and i can access fastboot mode but have no permision to do anything in there and cant flash from recovery. Any solution about this?
Xristomania said:
Did it with the EDL and now i got hard brick. Now I am stuck at mi logo not even bootlooping and i can access fastboot mode but have no permision to do anything in there and cant flash from recovery. Any solution about this?
Click to expand...
Click to collapse
Did you use unofficial bootloader unlock? If you did, you're really really f***ed right now. The only way to fix this is to physically open the device, unscrew the motherboard, plug in the usb and use a metal object to connect the two "testpoints", which will force the phone into edl mode.
justinxfan said:
Did you use unofficial bootloader unlock? If you did, you're really really f***ed right now. The only way to fix this is to physically open the device, unscrew the motherboard, plug in the usb and use a metal object to connect the two "testpoints", which will force the phone into edl mode.
Click to expand...
Click to collapse
I know about the testpoint but thank god i did wait for the unlock aproval.
Xristomania said:
I know about the testpoint but thank god i did wait for the unlock aproval.
Click to expand...
Click to collapse
In that case of official unlock, guess you can take to service center and get it repaired?
For unofficial unlock, there is simple way to lock bootloader by putting back original "emmc_appsboot.mbn" from fastboot rom.
fastboot flash aboot emmc_appsboot.mbn
fastboot flash abootbak emmc_appsboot.mbn
Xristomania said:
I know about the testpoint but thank god i did wait for the unlock aproval.
Click to expand...
Click to collapse
You used official unlocked and the phone still bricked?
mGforCe said:
In that case of official unlock, guess you can take to service center and get it repaired?
For unofficial unlock, there is simple way to lock bootloader by putting back original "emmc_appsboot.mbn" from fastboot rom.
fastboot flash aboot emmc_appsboot.mbn
fastboot flash abootbak emmc_appsboot.mbn
Click to expand...
Click to collapse
Greece doesn't have a service center for xiaomi phones. Yeap, this sucks.
justinxfan said:
You used official unlocked and the phone still bricked?
Click to expand...
Click to collapse
Yep, still bricked. Hard Bricked. I have used tespoint again but it was actually hard to trigger it because it caused phone to restart normally instead of going to edl.
When I tried to EDL Flash my phone normally when i had access to android, I got and max memory something problem in Mi Flash and when i tried again it sent a hello package to my phone and then it said catastrophic failure. So, don't know what that actually means and I hope not what it actually says. However i still have access to fastboot mode and recovery mode but i found out that I actually have locked bootloader after flashing this "emmc_appsboot.mbn" and had the phone alive in chinese dev rom and then i wanted to roll back to global stable via edl and got brick. Sadly I do not have access to this test mode where you test your phone's sensors, display and more.
Xristomania said:
When I tried to EDL Flash my phone normally when i had access to android, I got and max memory something problem in Mi Flash and when i tried again it sent a hello package to my phone and then it said catastrophic failure. So, don't know what that actually means and I hope not what it actually says. However i still have access to fastboot mode and recovery mode but i found out that I actually have locked bootloader after flashing this "emmc_appsboot.mbn" and had the phone alive in chinese dev rom and then i wanted to roll back to global stable via edl and got brick. Sadly I do not have access to this test mode where you test your phone's sensors, display and more.
Click to expand...
Click to collapse
Hey, you can go into EDL mode?
If yes, why don't you flash the Fastboot ROM - Global one if you don't want CHinese one
Refer this post for basic steps.
http://forum.xda-developers.com/showpost.php?p=66962198&postcount=7
mGforCe said:
Hey, you can go into EDL mode?
If yes, why don't you flash the Fastboot ROM - Global one if you don't want CHinese one
Refer this post for basic steps.
http://forum.xda-developers.com/showpost.php?p=66962198&postcount=7
Click to expand...
Click to collapse
I might can with the testpoint method. Although I can not boot into android.
Xristomania said:
I might can with the testpoint method. Although I can not boot into android.
Click to expand...
Click to collapse
Suggest trying @Rajdip's thread here
http://forum.xda-developers.com/redmi-note-3/how-to/unbricking-redmi-note3-hardbrickhs-usb-t3351325
EDL
mGforCe said:
Suggest trying @Rajdip's thread here
http://forum.xda-developers.com/redmi-note-3/how-to/unbricking-redmi-note3-hardbrickhs-usb-t3351325
Click to expand...
Click to collapse
Just got into edl mode with testpoint and flashed successfully global firm. I'll charge it fully and the find out if it actually works.
Xristomania said:
Just got into edl mode with testpoint and flashed successfully global firm. I'll charge it fully and the find out if it actually works.
Click to expand...
Click to collapse
Great! Happy to note that your phone is back.. If flash has been successful then it will work.
testpoint is risky and requires expertise right?
mGforCe said:
Great! Happy to note that your phone is back.. If flash has been successful then it will work.
testpoint is risky and requires expertise right?
Click to expand...
Click to collapse
Actually it is not that difficult but it is extremely tricky since if you press only the left one test point it will just reboot. You need to touch them at the same time. Although you'll need to be accommodated with electronics since they are sensitive.
mGforCe said:
Great! Happy to note that your phone is back.. If flash has been successful then it will work.
testpoint is risky and requires expertise right?
Click to expand...
Click to collapse
Weirdly enough, it shows battery sign when charging but button do not seem to respond for a weird reason. I'll check cables.
Oh god yes
Xristomania said:
Weirdly enough, it shows battery sign when charging but button do not seem to respond for a weird reason. I'll check cables.
Click to expand...
Click to collapse
I had a little heart attack because I thought That i had cut the Button Cable during the flash process but THANK GOD it was right underneath the motherboard and IT NOW WORKS. YES I AM IN MIUI GLOBAL. THANK GOD. Just for you to know, every failed bootloader unlock on any smartphone is equal to several heart attacks.
UPDATE (03/09/2019):
This thread is now dedicated to the development of the Vertu Aster P replica, which has MTK's MT6755 Helios P10 chipset.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Hi All,
I've just recently bought a Vertu Aster P replica, which came pre-loaded with a Vertu-themed (skinned) version of Android 6.0 Marshmallow. In the 'About Device' menu, however, the developers have (not so cleverly) disguised it to say Android 8.1.0 (Oreo). Why they would do this, rather than just taking Oreo and skinning it with the Vertu theme, I don't know. Anyway, I've gone and hard bricked the phone while trying to install a custom recovery, and it will not turn on or charge. It is still recognised when plugged into the laptop, so if I had the original ROM that it came with, I would be able to reflash it and have a working phone again. Sadly, I cannot find the ROM for it anywhere online. I can find the ROM's for the Vertu Signature Touch replica and Vertu Ti, and others, but not for the new Aster P replica, which uses the MT6755 chipset. Here are a few photos of the phone's OS. So, I'm wondering if anyone might be able to point me in the right direction of where I might be able to find this ROM. I have already been in contact with the company I bought it from. Still waiting to hear back from them. Hopefully they can just send me a download link.
Chris
Still living in hope that someone has access to the ROM for this phone.
Someone kind enough eventually came along and sent me the ROM. Flashed it and my phone now works again. Lesson learnt. ALWAYS DO A BACKUP BEFOREHAND.
I will upload it myself and make it available on here for other Aster P (replica) owners shortly.
Chris
Here it is.
https://www.needrom.com/download/vertu-aster-p-mt6755-chinese-clone-firmware/
I have also successfully managed to root the device using Magisk. If anyone else has the same device and wishes to root it, I'll guide you through the method if need be.
Chris
chris8189 said:
I have also successfully managed to root the device using Magisk. If anyone else has the same device and wishes to root it, I'll guide you through the method if need be.
Chris
Click to expand...
Click to collapse
Chris are you fastbooting to Recovery or actually flashing to the recovery partition?
I found a TWRP on XDA forums which @lopestom made for the BLU Pure XR P0030UU smartphone -
https://forum.xda-developers.com/pure-xr/development/twrp-twrp-3-1-x-x-blu-pure-xr-p0030-t3623865
The above phone also has the MT6755 P10 Helios chip, same as the Vertu Aster P clone, so I thought I would try and port the ROM over for the Vertu Aster P replica.
I got an error while doing the repack, however @ashyx managed to perform a successful repack on the image file and the phone does indeed boot up the TWRP. Problem is, there is no touch functionality. Plugging in an OTG mouse however might work, or likewise flashing the recovery image file to the boot partition, doing what you need to do in TWRP, and then flashing the stock (or modified) boot image back. I have put the feelers out for the kernel source, so (hopefully) we can then do the necessary tweaks to make TWRP function correctly, or even better, build a TWRP from source (if we can get it). Below is the link to the TWRP file.
https://mega.nz/#!J45FWIzJ!aFyFooO5aOtxjFany_osL4BpRRQSMljQjtfnYSFKDis
Chris
ashyx said:
Chris are you fastbooting to Recovery or actually flashing to the recovery partition?
Click to expand...
Click to collapse
I am flashing the recovery using SP Flash Tool (for MTK devices) to the recovery partition.
Chris
chris8189 said:
I am flashing the recovery using SP Flash Tool (for MTK devices) to the recovery partition.
Chris
Click to expand...
Click to collapse
Does this device not support fastboot?
Also does touch work if flashed to the boot partition?
ashyx said:
Does this device not support fastboot?
Also does touch work if flashed to the boot partition?
Click to expand...
Click to collapse
Yes, the device does support fastboot mode.
When flashing this TWRP to the boot partition, touch functionality, and all aspects of TWRP work perfectly.
Chris
chris8189 said:
Yes, the device does support fastboot mode.
When flashing this TWRP to the boot partition, touch functionality, and all aspects of TWRP work perfectly.
Chris
Click to expand...
Click to collapse
What happens if you just Fastboot boot 'recovery.img' rather than flashing it?
ashyx said:
What happens if you just Fastboot boot 'recovery.img' rather than flashing it?
Click to expand...
Click to collapse
When I do that, it says that oem unlock is false, however in the developer options on my phone, I have the OEM Unlock turned on, so I don't understand why it's saying that. When type in 'fastboot oem unlock', my phone gives me the option to unlok the bootloader, or not, with the volume up and down keys. Volume up being unlock the bootloader and volume down being don't unlock the bootloader. When I press volume up, nothing happens. If I press volume down, however, it allows me to not unlock the bootloader, lol. Has an extra layer of security been added to this device? Is the OEM unlock option in my dev options just a fake toggle switch?
Chris
chris8189 said:
When I do that, it says that oem unlock is false, however in the developer options on my phone, I have the OEM Unlock turned on, so I don't understand why it's saying that. When type in 'fastboot oem unlock', my phone gives me the option to unlok the bootloader, or not, with the volume up and down keys. Volume up being unlock the bootloader and volume down being don't unlock the bootloader. When I press volume up, nothing happens. If I press volume down, however, it allows me to not unlock the bootloader, lol. Has an extra layer of security been added to this device? Is the OEM unlock option in my dev options just a fake toggle switch?
Chris
Click to expand...
Click to collapse
What result do you get for:
fastboot oem device-info
I tried it and the command doesn't work.
chris8189 said:
I tried it and the command doesn't work.
Click to expand...
Click to collapse
Try:
fastboot getvar unlocked
Typing 'fastboot getvar unlocked' confirms that the bootloader is locked. It says 'unlocked :no'
Chris
chris8189 said:
Typing 'fastboot getvar unlocked' confirms that the bootloader is locked. It says 'unlocked :no'
Chris
Click to expand...
Click to collapse
It definitely says OEM_UNLOCK enabled in developer settings and you're issuing the oem unlock command while in FASTBOOT mode?
ashyx said:
It definitely says OEM_UNLOCK enabled in developer settings and you're issuing the oem unlock command while in FASTBOOT mode?
Click to expand...
Click to collapse
Correct.
I read up online about it and some MTK devices don't support bootloader unlocking. Or, you have to obtain an 'unlock code' from the manufacturer.
Chris
chris8189 said:
Correct.
I read up online about it and some MTK devices don't support bootloader unlocking. Or, you have to obtain an 'unlock code' from the manufacturer.
Chris
Click to expand...
Click to collapse
Probably a daft question, but have you actually tried booting the unpacked twrp recovery image?
If these devices are so similar maybe the kernel is too.
ashyx said:
Probably a daft question, but have you actually tried booting the unpacked twrp recovery image?
If these devices are so similar maybe the kernel is too.
Click to expand...
Click to collapse
It doesn't load. It bootloops. So they have different kernels.
Chris
I know it's only early day but has anyone found a root solution for the moto e6 plus?
Needing a new phone (hardware failure) and want one that can be easily rooted preferably with Twrp and Magisk,
McTRASH692 said:
I know it's only early day but has anyone found a root solution for the moto e6 plus?
Needing a new phone (hardware failure) and want one that can be easily rooted preferably with Twrp and Magisk,
Click to expand...
Click to collapse
I hope someone supports this device, since it is compatible with Proiect Treble
P o
I am planning to buy this, hope there is TWRP and Root soon!
Probably wont get support, cuz of the mediatek chip! I hope I am wrong [emoji1431]
Verstuurd vanaf mijn moto e(6) plus met Tapatalk
blanxlr said:
Probably wont get support, cuz of the mediatek chip! I hope I am wrong [emoji1431]
Verstuurd vanaf mijn moto e(6) plus met Tapatalk
Click to expand...
Click to collapse
The most E4 had a mediatek chipset and it had a few various root solutions,
yes, I'm waiting to root
Root is possible. The way I achieved it is first to follow the official bootloader unlock method given by Motorola. Then install Magisk Manager V 7.5.1 (latest as of today). After that have magisk patch the boot image and recovery image, and flash them both through fastboot. It will say the boot partition is signed but when you Flash it to the recovery partition it will tell you the image is either not signed or corrupt. Don't worry about this, it does not affect loading back into system or back into the bootloader or recovery. Remember, after this you will have to boot through recovery every time you reboot or you will not have root until you do. Unfortunately I am still trying to work on TWRP, and it is going rather slow as this is my first attempt at compiling a custom recovery and I am no developer, and am learning as I go... Hope I helped!!!
Hey guys, I Need some help, I'm trying to unlock bootloader, but my device doesn't recognize fastboot commands like "fastboot oem get_unlock_data" Or "fastboot oem flashing_unlock", why?
Ps: Motorola drivers ok, usb cable ok, oem unlock and usb debugging ok
Root
Hi extrnoob! Could you explain this process step by step? Inexperienced people like me don't understand your language xD
extrnoob said:
Root is possible. The way I achieved it is first to follow the official bootloader unlock method given by Motorola. Then install Magisk Manager V 7.5.1 (latest as of today). After that have magisk patch the boot image and recovery image, and flash them both through fastboot. It will say the boot partition is signed but when you Flash it to the recovery partition it will tell you the image is either not signed or corrupt. Don't worry about this, it does not affect loading back into system or back into the bootloader or recovery. Remember, after this you will have to boot through recovery every time you reboot or you will not have root until you do. Unfortunately I am still trying to work on TWRP, and it is going rather slow as this is my first attempt at compiling a custom recovery and I am no developer, and am learning as I go... Hope I helped!!!
Click to expand...
Click to collapse
I couldn't unlock bootloader. When i type the command fastboot devices i get a string, but when i type fastboot oem get_unlock_data, i get this message “FAILED (remote: unknown command)”.
risss said:
I couldn't unlock bootloader. When i type the command fastboot devices i get a string, but when i type fastboot oem get_unlock_data, i get this message “FAILED (remote: unknown command)”.
Click to expand...
Click to collapse
I have the same error ;_;
U are using CMD as admin, not PowerShell?
Vsx06 said:
U are using CMD as admin, not PowerShell?
Click to expand...
Click to collapse
I tried both ; -;
You can't unlock the bootloader. Don't bother with it. If you want something proper, get any device that's NOT from China, and especially form Lenovo (which is Motorola now).
**** LENOVO **** CHINA FREE HONG KONG.
I don't know if there's a moto e6 plus with enabled oem fastboot commands, it seems like Motorola didn't add support for oem unlock in this phone but maybe if we could get a hold of the download agent for Sp flash tool (since the device is a Mediatek powered device) and the auth file, we could get root via magisk patched boot.img
I searched for a little and i found nothing. I hope that someone manages to get a hold of those files, since the firmware is already available online.
Well, i managed to flash patched boot.img, but dm-verity is enabled and fstab is not on ramdisk because of project treble... now what
hookgab said:
You can't unlock the bootloader. Don't bother with it. If you want something proper, get any device that's NOT from China, and especially form Lenovo (which is Motorola now).
**** LENOVO **** CHINA FREE HONG KONG.
Click to expand...
Click to collapse
I beg to differ, as in developer option on the moto e6 plus there is a toggle for OEM unlocking,
I believe you need to get a code from Motorola to complete the unlock though,
I have not yet tested as I want to preserve warranty,
However with my moto e4 I was able to unlock bootloader and root without any issues,
Hell at one point I had to rebuild the entire system from an empty chip, (OS took me 4 Days) including rewriting the original imei numbers (that took me 2 weeks)
So no, lenovo is not as locked down as you seem to think it is,
As a side not, most phone are made with components that are built/assembled in China so it is actually quite hard to get a device that isn't at least partially made in China,
uanesgtgt2 said:
Well, i managed to flash patched boot.img, but dm-verity is enabled and fstab is not on ramdisk because of project treble... now what
Click to expand...
Click to collapse
I know the moto e4 required a no-verity flash to accept root,
Unsure if there is one that would work for the e6 yet,
Certainly something to look for,
uanesgtgt2 said:
I don't know if there's a moto e6 plus with enabled oem fastboot commands, it seems like Motorola didn't add support for oem unlock in this phone but maybe if we could get a hold of the download agent for Sp flash tool (since the device is a Mediatek powered device) and the auth file, we could get root via magisk patched boot.img
I searched for a little and i found nothing. I hope that someone manages to get a hold of those files, since the firmware is already available online.
Click to expand...
Click to collapse
It was added, it's hidden away in developer options,
May require an unlock code from Motorola though,
Hi everyone, first of all, thanks for reading and trying to help out.
I have a 1+7t Pro Indian unit. I unlocked the Bootloader on my device and installed Magisk but as I saw that there were not much benefits of rooting at the moment since twrp is not also available yet so no flashing of custom roms.
So I tried to relock the Bootloader. For that I Flashed the stock rom from scratch so that no modifications stay in the system and then tried "fastboot oem lock". This however got me into a bricked stage where I got following error:
"Your device is currept. It can not be trusted and will not boot."
This comes with a red exclamation mark and nothing happens means it gets bricked. I also tried "fastboot flashing lock". That did not work either. I did unbrick it without any issue but I want to relock the Bootloader just in case I need to sell the device.
Has anyone faced the same problem or could help me out here?
Any help much appreciated and thanks in advance!!
Chandler_Bing_1995 said:
Hi everyone, first of all, thanks for reading and trying to help out.
I have a 1+7t Pro Indian unit. I unlocked the Bootloader on my device and installed Magisk but as I saw that there were not much benefits of rooting at the moment since twrp is not also available yet so no flashing of custom roms.
So I tried to relock the Bootloader. For that I Flashed the stock rom from scratch so that no modifications stay in the system and then tried "fastboot oem lock". This however got me into a bricked stage where I got following error:
"Your device is currept. It can not be trusted and will not boot."
This comes with a red exclamation mark and nothing happens means it gets bricked. I also tried "fastboot flashing lock". That did not work either. I did unbrick it without any issue but I want to relock the Bootloader just in case I need to sell the device.
Has anyone faced the same problem or could help me out here?
Any help much appreciated and thanks in advance!!
Click to expand...
Click to collapse
Same here when I was trying to lock bootloader of my 7T (non pro) yesterday. I figured out a solution. Simply download unbrick tool, connect device in Qualcomm EDL mode and flash proper firmware (choose between india and O2 (which mean global) firmware. After restoring firmware with MSM tool your device bootloader will be locked again.
EugenStanis said:
Same here when I was trying to lock bootloader of my 7T (non pro) yesterday. I figured out a solution. Simply download unbrick tool, connect device in Qualcomm EDL mode and flash proper firmware (choose between india and O2 (which mean global) firmware. After restoring firmware with MSM tool your device bootloader will be locked again.
Click to expand...
Click to collapse
Thanks a lot, will try that.
Chandler_Bing_1995 said:
Thanks a lot, will try that.
Click to expand...
Click to collapse
https://androidfilehost.com/?fid=4349826312261684661
Hello,
i post my very first request on XDA because i have a serious problem.
My Xiaomi mi A3 doesn't boot.
I bought it one year ago and he didn't receive any update since the August 2020 patch. So today i decided to flash the last stable stock rom.
First i unlocked the bootloader and then i flashed "laurel_sprout_global_images_V12.0.&3.0RFQMIXM_20210810" version,
but when it reboot, it was stuck on the android one logo.
After that i decided to cancel everything to not take any more risk and i flash a previous version which is "Xiaomi_Mi_A3_V10.3.4.0.PFQMIXM_20190815.0000.00_Global_9.0_XFT".
I'm on linux so i executed "flash_lock.sh", i thought that it means "flash the rom, and then lock bootloader" but i don't know what it means precisely. So i used that, and when it finished the flash, the phone turn off and since this moment it doesn't want to boot, and even if a do the fastboot access combinaison, nothing boot.
This is my daily phone and I really need help ....
Thank you
I don't think you can do much seeing as you locked the bootloader.
When performing such tasks it is recommended to keep the bootloader unlocked in case anything goes wrong you can flash other ROMs in fastboot.
But because you locked the bootloader fastboot is pretty much useless now.
The only thing you could probably try is booting to EDL mode and flashing stock ROM with mi flash on a Windows computer.
The device is essentially hard bricked without access to fastboot but you should still be able to boot to EDL mode.
Maybe this will work, it's certainly worth a try
garylawwd said:
I don't think you can do much seeing as you locked the bootloader.
When performing such tasks it is recommended to keep the bootloader unlocked in case anything goes wrong you can flash other ROMs in fastboot.
But because you locked the bootloader fastboot is pretty much useless now.
The only thing you could probably try is booting to EDL mode and flashing stock ROM with mi flash on a Windows computer.
The device is essentially hard bricked without access to fastboot but you should still be able to boot to EDL mode.
Maybe this will work, it's certainly worth a try
Click to expand...
Click to collapse
Thank you very much for your answer. I will try the EDL mod and give updates.
garylawwd said:
I don't think you can do much seeing as you locked the bootloader.
When performing such tasks it is recommended to keep the bootloader unlocked in case anything goes wrong you can flash other ROMs in fastboot.
But because you locked the bootloader fastboot is pretty much useless now.
The only thing you could probably try is booting to EDL mode and flashing stock ROM with mi flash on a Windows computer.
The device is essentially hard bricked without access to fastboot but you should still be able to boot to EDL mode.
Maybe this will work, it's certainly worth a try
Click to expand...
Click to collapse
It works, with EDL. thank you very much for advising me on this method.
And now it even receives updates from XIaomi.
I used this guide:
https://c.mi.com/thread-3527044-1-0.html