hi,
past few days back i have unlocked the bootloader and installed twrp in my realme x2 pro, i used lineage 17.1 rom then again i went back to RUI, but after that someone told me to install orange fox so i installed it as well, but after that i have seen that iam not able to enter in fastboot mode by pressing vol + power buttons nor from adb command....it comes for a while then phone automatically reboot itself due to this iam not able to use banking apps and not able to watch HDR movies in amazon prime and netflix....please help me to get back my fastboot mode so that i will lock my bootloader again....
thanks
Did you fix it?
mike_san said:
Did you fix it?
Click to expand...
Click to collapse
No i tried everything but nothing worked....i don't know why is not a single person resolved this issue
saurabh(India) said:
hi,
past few days back i have unlocked the bootloader and installed twrp in my realme x2 pro, i used lineage 17.1 rom then again i went back to RUI, but after that someone told me to install orange fox so i installed it as well, but after that i have seen that iam not able to enter in fastboot mode by pressing vol + power buttons nor from adb command....it comes for a while then phone automatically reboot itself due to this iam not able to use banking apps and not able to watch HDR movies in amazon prime and netflix....please help me to get back my fastboot mode so that i will lock my bootloader again....
thanks
Click to expand...
Click to collapse
I locked my bootloader and it now my phone is in soft brick.... If you want to lock you can downgrade your OS to ColorOS and you can acess Fastboot easily
Bhuprab said:
I locked my bootloader and it now my phone is in soft brick.... If you want to lock you can downgrade your OS to ColorOS and you can acess Fastboot easily
Click to expand...
Click to collapse
That's what I did with Auth-flash, even paid credits to revert back to ColorOS.
Now I'm at C.29 with Realme UI 1.0 with Bootloader unlocked but not able to access to Booloader.
At least I can use NFC and use the phone normally, only no root, no bootloader, no widevine.
I have similar issue. It seems that Realme has blacklisted our devices from entering bootloader. Tell me this, has your phone been sent to Realme for repairs after you tempered with the bootloader?
Milan-XDA said:
I have similar issue. It seems that Realme has blacklisted our devices from entering bootloader. Tell me this, has your phone been sent to Realme for repairs after you tempered with the bootloader?
Click to expand...
Click to collapse
Yes Milan in my case, I took to realme service center , but after getting repaired, i used unlocking tool again and it worked no problem but after the updates I felt like i should lock the bootloader , so i did with a command " fastboot flashing lock " now whenever i try to unlock it doesn't unlocks rather shows fastboot logo 2-3 sec, also i tried in color os 6 but nothing happend there also, now im using color os 6 which is still better in terms of performance as compared to realme ui , ui 2.0 and also i can't upgrade to android 10 or android 11 from coloros 6 due to the fact that the security patch won't match realme ui , ultimately leading to bootloop , which was the earlier case for me to go to service center .
RahulKumar_213 said:
Yes Milan in my case, I took to realme service center , but after getting repaired, i used unlocking tool again and it worked no problem but after the updates I felt like i should lock the bootloader , so i did with a command " fastboot flashing lock " now whenever i try to unlock it doesn't unlocks rather shows fastboot logo 2-3 sec, also i tried in color os 6 but nothing happend there also, now im using color os 6 which is still better in terms of performance as compared to realme ui , ui 2.0 and also i can't upgrade to android 10 or android 11 from coloros 6 due to the fact that the security patch won't match realme ui , ultimately leading to bootloop , which was the earlier case for me to go to service center .
Click to expand...
Click to collapse
I've reached out to the local Realme service center and I asked them if my bootloader was blacklisted. After running some checks with Realme HQ, they've told me to send the device to them, so that they could flash/update the software themselves in order to regain access to my bootloader. Which means that no matter what we try, we won't be able to get the bootloader unlocked ourselves without Realme's intervention.
Milan-XDA said:
I've reached out to the local Realme service center and I asked them if my bootloader was blacklisted. After running some checks with Realme HQ, they've told me to send the device to them, so that they could flash/update the software themselves in order to regain access to my bootloader. Which means that no matter what we try, we won't be able to get the bootloader unlocked ourselves without Realme's intervention.
Click to expand...
Click to collapse
Ok Milan, just inform us with your result once Realme intervenes and concludes your device!!
RahulKumar_213 said:
Ok Milan, just inform us with your result once Realme intervenes and concludes your device!!
Click to expand...
Click to collapse
Hi Rahul, I will keep you guys updated, however I need my device for work, so I won't be sending it in for service anytime soon. Maybe i'll get around to it in Q1 2022 once I get my next device
Related
Hello Community,
i have a Problem after the installation of the newest android Update (OTA).
The A2 just Boot till the white AndroidOne Logo and it hangs there after a time it seems it shut down itself.
My Device:
-USB Debugging is disabled, its a new testing device.
-I cant boot in recovery mode (vol-UP+Power) just boots to the white androidOne Screen and there it hangs
- I can enter fastboot(VOL-Down+power) mode and the device is listed when i type fastboot devices in my terminal on pc
- when i fire up MiFlash tool it list my device after clicking refresh, if i want flash the latest FW (http://en.miui.com/download-353.html) i get the error:
error:"Flash bluetooth_a error"
- My bootloader is locked.
Question:
How can I flash a offical Android with a locked bootloader?
is it a good idea? or better send it back for a warranty solution (i dont want wait)
is there another way to solve my problem? i really dont know whats the problem is. i did not rooted the device or anything.
would be lovely if someone could help me. with an instruction what i can try.
Thank you very much and have a nice day
Regards
If you have enabled 'OEM Unlock' setting in Developer settings, you will probably be good, you can unlock bootloader(oem/flashing/critical) and flash the official ROM ( as per now, 10.0.2.0 )
If not, you have 2 options
-Boot into EDL using short points and flash from there
-Warranty
Same thing happened to a friend's phone, it wasn't touched and just went brick after 10.0.2.0 OTA.
Guess everyone should enable 'OEM Unlock' in case this happens(Data Encrypted anyway, worst case stolen phone better than the chance of brick every time an OTA comes)
edit: If you want to save your data, you obviously shouldn't try the bootloader unlock way...EDL flashing allows flashing without wiping data, but haven't tested that personally
wow really? that are bad news...
thank you anyway :crying:
maybe someone other got a idea?
regards
Lot of users faced this after today's update including myself. Since my bootloader is locked, only option left is EDL flashing by connecting motherboard test points.
Just an advice for everyone reading this message from a Xiaomi Android One device: ALWAYS KEEP UR BOOTLOADER UNLOCKED, IT DOESNT MATTER IF USB DEBUG ISNT ACTIVE, JUST UNLOCK BOOTLOADER
sorry for caps, is just an important thing, i also had the issue but with unlocked bootloader i solved it easily
Just flash using fastboot
Sent from my LG-V930 using Tapatalk
Abrilabr said:
Just an advice for everyone reading this message from a Xiaomi Android One device: ALWAYS KEEP UR BOOTLOADER UNLOCKED, IT DOESNT MATTER IF USB DEBUG ISNT ACTIVE, JUST UNLOCK BOOTLOADER
sorry for caps, is just an important thing, i also had the issue but with unlocked bootloader i solved it easily
Click to expand...
Click to collapse
Yea, but if you want use it as enterprise Device the open Bootloader is a problem.
ilyas111 said:
Just flash using fastboot
Sent from my LG-V930 using Tapatalk
Click to expand...
Click to collapse
that seems not possible with a locked Bootloader (very new phone)
or can you provide a working solution with a locked bootloader? i wont use this EDL thing because its just new and i dont want open it.
Thank you all anyways
Try with this tool : https://forum.xda-developers.com/mi-a2/development/tool-mi-a2-xtrem-toolkit-t3879660
(edl included)
Same trouble here, we are fu...ed!
With Xiaomi mi flash tool, you can re active bootloader protection !
Simple flash with this tool with the option "clean and lock critical"
Works for me !
xotob said:
With Xiaomi mi flash tool, you can re active bootloader protection !
Simple flash with this tool with the option "clean and lock critical"
Works for me !
Click to expand...
Click to collapse
you had bootloader unlocked, i dont, i cant flash nothing with bootloader locked and i have unchecked the option in debug menù.
Reptant said:
If you have enabled 'OEM Unlock' setting in Developer settings, you will probably be good, you can unlock bootloader(oem/flashing/critical) and flash the official ROM ( as per now, 10.0.2.0 )
If not, you have 2 options
-Boot into EDL using short points and flash from there
-Warranty
Same thing happened to a friend's phone, it wasn't touched and just went brick after 10.0.2.0 OTA.
Guess everyone should enable 'OEM Unlock' in case this happens(Data Encrypted anyway, worst case stolen phone better than the chance of brick every time an OTA comes)
edit: If you want to save your data, you obviously shouldn't try the bootloader unlock way...EDL flashing allows flashing without wiping data, but haven't tested that personally
Click to expand...
Click to collapse
After got OTA update to 10.0.3.0 and Today i try to unlock bootloader but I can't unlock_critical and I can't flashing unlock
boonc said:
After got OTA update to 10.0.3.0 and Today i try to unlock bootloader but I can't unlock_critical and I can't flashing unlock
Click to expand...
Click to collapse
Same problem here, does anyone have a solution?
Does fastboot mode is detected in pc?
Sent from my MI 6X using Tapatalk
ilyas111 said:
Does fastboot mode is detected in pc?
Sent from my MI 6X using Tapatalk
Click to expand...
Click to collapse
yes, but i cant use more of fastboot comands, cause bootloader is locked, cant use "flashing unlock/unlock_critical"
Cizzle4 said:
you had bootloader unlocked, i dont, i cant flash nothing with bootloader locked and i have unchecked the option in debug menù.
Click to expand...
Click to collapse
I'm in your same situation
Exactly the same situation here... Waiting for a solution without losing warranty.
I think if your bootloader is not unlocked, the only possible solution left is to shorting the test points on motherboard. Those who have warranty can return the unit for claim. Yet another mess up from Xiaomi and this will be my last phone from them.
UnlimitedBB said:
I think if your bootloader is not unlocked, the only possible solution left is to shorting the test points on motherboard. Those who have warranty can return the unit for claim. Yet another mess up from Xiaomi and this will be my last phone from them.
Click to expand...
Click to collapse
I can understand that. I will claim warranty because its new and i dont want do that test point thing.
on private i would buy and recommend xiaomi anyways but if you want these hardware for some enterprise things then better not.
Iam out of this Thread now but if you want talk here some more feel free.. maybe somebody can bring a solution for all you guys who face this problem but i think its not possible without a open BL or the TestPoint Method.
Regards and have a nice day
Hi. I'm with locked bootloader. I received new January update. No change - stock variant updated to Pie. So it's safe to update or waiting for new one? Mi A2 4/64 micron ram
I have a converted A2 (+ARB 4), with UNLOCKED bootloader.
I read somewhere if you relock the BL , you will not able to UNLOCK it again ever after! (is it true?)
and other thing: If it try the MIUI BL Unlocker Official Application to unlock my device (even when it is still unlocked) what could be happen? (I've just followed the steps till the warning msg: "Unlocking Bootloader will erase user Data" ). (I read somewhere else that for unlocking miui devices you need to submit the request and you need to wait for a long time to get the code, and I was going to get the code for a case of necessity in future.)
I need to know how far I can play with these stuffs on my devices and left a practical way to recover a Bricked phone. ( I consider even TEST POINT as a practical option [tried once and it is damn easy and fun ] )
Im sorry bro but the actual model and serial code of your phone is a A2.And that means you probably wont unlock it it will give a hardware error.But pls try it and report.Dont worry there will be a fix!!
Tech_jetoncesaj said:
Im sorry bro but the actual model and serial code of your phone is a A2.And that means you probably wont unlock it it will give a hardware error.But pls try it and report.Dont worry there will be a fix!!
Click to expand...
Click to collapse
If it locked again my BL, what would be the solution? I didn't find any.
the mi unlock app requires a mi account with unlock permissions (account! not phone)
if you try to unlock an unlocked a2 you should either get unsuported - it's meant for miui devices - or already unlocked.
The app first checks the account and passes to further steps, then recognizes my phone, and warns me about wiping Data. ( At this step I declined and closed the app)
Your hypothesis seems correct, but if in any circumstances I would be left with relocked converted A2 , ist there any chance to reunlock it again?
that's why the test point method exists, for locked that you try to fastboot flash
I tried, and it just says: Device Unlocked, no need to reunlock again!
So now is it safe to lock my bootloader and try the app again?
if you lock the bootloader via fastboot commands it wont boot any more.
only way to safely lock is with miflash and you cannot miflash a wayne miui on a converted a2. it will see that it's the jasmine.
if you miflash the a2 fastboot rom it will relock ok - if the flashing works...might not cuz of the arb - but you wont be on miui any more.
what are you trying to do anyway?
i think what you dont understand is the unlock on miui and android one are the same end result but different steps. for miui you godda use the mi unlock, for and1 its just the dev options switch
laviniu_c said:
if you lock the bootloader via fastboot commands it wont boot any more.
Click to expand...
Click to collapse
So if I run the command and re-lock it by Fastboot, how can I re-unlock it again?
laviniu_c said:
only way to safely lock is with miflash and you cannot miflash a wayne miui on a converted a2. it will see that it's the jasmine.
if you miflash the a2 fastboot rom it will relock ok - if the flashing works...might not cuz of the arb - but you wont be on miui any more.
Click to expand...
Click to collapse
So do you mean there is no safety way to re-lock a converted A2 which runs MIUI ?
(and If I had a Banking app which needs a Locked BL to work, there will be no chance to run it at all?)
laviniu_c said:
what are you trying to do anyway?
Click to expand...
Click to collapse
As I said I want to know all the aspects of practical ways to deal with my phone, right now I am totally happy with it, but actually the opportunity of dealing with all these technical stuffs convinced me to buy this phone.
laviniu_c said:
i think what you dont understand is the unlock on miui and android one are the same end result but different steps. for miui you godda use the mi unlock, for and1 its just the dev options switch
Click to expand...
Click to collapse
I've heard that some ROMs may re-lock the phone, since then I would like to know if in any circumstances I would be stuck on that situation how can I re-unlock my phone.
any official miui rom that has the firmware folder in it might do it for example, so will bad ports....
try to use the magisk hide options to fix the banking app, add it to the list of apps for which it specifically hides root. add also the google services and make sure you pass the safetynet tests and your device shows as certified in the playstore settings. i think there were some modules to fix the bl check
laviniu_c said:
any official miui rom that has the firmware folder in it might do it for example, so will bad ports....
Click to expand...
Click to collapse
So lets assume it has been happened, what would be the procedure to rescue my phone? since as you said if the BL locked again it will not boot to OS.
laviniu_c said:
try to use the magisk hide options to fix the banking app, add it to the list of apps for which it specifically hides root. add also the google services and make sure you pass the safetynet tests and your device shows as certified in the playstore settings. i think there were some modules to fix the bl check
Click to expand...
Click to collapse
I would'nt like to root the phone, isn't there any other option?
if you lock the bootloader with any kind of non official rom for your phone (i.e. jasmine_sprout) which in your case is android one it wont boot. the end. only way out of that is the edl mode and miflash. that's the basic difference between locked and unlocked, it checks what os it loads and it makes sure the loaded os is the official rom for the phone. converting the a2 means it needs to be unlocked and you load a rom that's a ported miui10 from wayne to jasmine_sprout. if you flash the full rom, that has the locked bootloader from wayne which will fail to start since:
1 - the phone still isnt wayne
2- the rom isnt quite the official one (since it's renamed to work on jasmine)
3 - even if the phone was fully wayne, you dont really want the official mi 6x rom since that's china only. i.e. no google services
the only unknown in all this is the ARB, but edl should ignore that.
somehow i was under the impression you already have magisk (root/hide) up and running on the converted miui 10. yes, there are good miui 10 ports (for example xiaomi.eu) that give you the miui experience on a2 except they will never have the full ota support that the official rom has.
my advice? stick to the stock a2 rom. locked and full stock. the moment you need to start experimenting is when the android one support stops OR if you really want root.
if you wanted miui and you're outside china, mi 6x is still NOT the way to go. cuz it doesnt have an official global rom anyway. i dont get why everyone is jumping through hoops to get unofficial roms installed with stock support available.
laviniu_c said:
if you lock the bootloader with any kind of non official rom for your phone (i.e. jasmine_sprout) which in your case is android one it wont boot. the end. only way out of that is the edl mode and miflash.
Click to expand...
Click to collapse
So please consider these situations:
The phone is A2 converted to 6X &
The BL has been re-locked &
ARB 4 has been triggered
how can I use EDL mode to unlock it?
(I think miflash would not help because the LOCKED BL and the phone is actually A2)
(I think also Fastboot wont be able to unlock it since it is A2 Converted to 6X)
laviniu_c said:
yes, there are good miui 10 ports (for example xiaomi.eu) that give you the miui experience on a2 except they will never have the full ota support that the official rom has.
Click to expand...
Click to collapse
I'm afraid but I didt't get the point, now every week I receive Pie beta updates (besides there are stable versions too) which actually stable enough, almost Bug & Lag Free (it differs Rom to Rom, but believe me it is COOL ) , and by PitchBlack you can use direct update. (I prefer to install it by myself since I LOVE TWRP & its child PB). so what exactly we miss of original OTA service of XIAOMI?
laviniu_c said:
my advice? stick to the stock a2 rom. locked and full stock. the moment you need to start experimenting is when the android one support stops OR if you really want root..
Click to expand...
Click to collapse
But I think it wouldn't be an option for who has triggered ARB4! isn't it? (I read when you got ARB4 you must forget AndroidOne! even TestPoint won't help)
laviniu_c said:
if you wanted miui and you're outside china, mi 6x is still NOT the way to go. cuz it doesnt have an official global rom anyway. i dont get why everyone is jumping through hoops to get unofficial roms installed with stock support available.
Click to expand...
Click to collapse
Again I didn't get what do you mean, could you please explain it a bit more? (since my current MIUI 10.4 has almost everything)
http://bigota.d.miui.com/V10.0.2.0....0.PDIMIFJ_20181206.0000.00_9.0_02b8deeb6d.tgz this should work with the testpoint/edl method and miflash. (unless arb does something to stop it)
there's a few problems with your approach.
1) not official. any time the guys maintaining the custom rom can decide to stop producing it.
2) all work into these custom roms is voluntary. are they sometime better? sure, never said they werent but again, xiaomi/google/android have far far more resources at their disposal and while the phone is under the official period it will be maintained.
3) did you bother to read the first lines in any custom rom? they take 0 responsibility for whatever happens to your phone. they do not intend to break it, but they dont have to support you if you're in trouble either. if you dont have a valid warranty, that's understandable, you don't lose anything. but guess what? there are official vendors for xiaomi all over the world, offering official warranty. that holds as long as you're on STOCK.
4) though most custom roms are well intended, there is nothing assuring you there's nothing inside there that you dont want installed. you move your trust from xiaomi/google/android (which you can hold accountable) to whoever made that rom (who just carpet say, it's your phone you're doing the flashing, anything happens you're on your own). in most cases those devs don't mean harm, but they could and there's nothing to stop them (and they would never put in the hours of work if there was accountability for their action - i perfectly understand them. it's sortof like, i can try to do this, but because my work is not paid for by the end user they do not have any hold over me. it's correct and yet at the same time it's very very dangerous.). ever seen a custom miui built by a shop? i have, it's packed full of junk, bugs and malware. another thing here is testing. the official rom goes through a bunch of tests/beta versions. not saying it's perfect but it's better then the "known bugs: you tell me". custom rom devs cannot do it any other way, they dont have the time to test or the team to test.
5) the official devs don't have this option, they have a job and do it. it's a completely different approach.
this is not a rant against custom rom devs, i understand them 100%, they're trying to help. what i'm saying is there's always 2 sides to each story. there's no right or wrong, there's just what's best for each user. some of us will want the safe and easy way of the stock roms. some will want custom roms. in the end everyone is doing what they choose with their phone.
laviniu_c said:
http://bigota.d.miui.com/V10.0.2.0....0.PDIMIFJ_20181206.0000.00_9.0_02b8deeb6d.tgz this should work with the testpoint/edl method and miflash. (unless arb does something to stop it)
Click to expand...
Click to collapse
I think it will not work, the Actual duty of ARB4 is to preventing you to use these things! as much as I know after ARB4 you have two options: MIUI 10 or custom ROMs such as Havoc or so, for AndroidONE we need to wait a version of AndroidONE which be compatible with ARB4! otherwise flashing STOCK AndroidONE will simply brick your phone! THE whole IDEA of this THREAT is this!
And BTW as much as I know XIAOMI.EU is cooperating now with the XIAOMI ! besides we do not keep a phone for a whole life time, 2-3 years of supports would be far enough. and they do offer it right now!
and I would like to lock the BL for further security reasons but it seems to be impossible so far otherwise someone suggests a practical way for it.
I guess you need to contact me.
sz.hatef said:
If it locked again my BL, what would be the solution? I didn't find any.
Click to expand...
Click to collapse
Hey its not very good to talk here in xda.We can try some methods!
Chat with me in telegram.
@blackgryphon1
Dont worry about brick,bcz im the only one who can unbrick,downgrade a xiaomi phone even if its arb4.
Feel free to contact me.
Also join my group i will be there too.
Since i cant post links,search this on telegram <<its my group>><<iT HAS A BLACK PHONE WALLPAPER AND IT HAS 86 MEMBERS!
Mi A2 & Mi 6X
Tech_jetoncesaj said:
Hey its not very good to talk here in xda.We can try some methods!
Chat with me in telegram.
@blackgryphon1
Dont worry about brick,bcz im the only one who can unbrick,downgrade a xiaomi phone even if its arb4.
Feel free to contact me.
Also join my group i will be there too.
Since i cant post links,search this on telegram <<its my group>><<iT HAS A BLACK PHONE WALLPAPER AND IT HAS 86 MEMBERS!
Mi A2 & Mi 6X
Click to expand...
Click to collapse
Just as I said, I would like to know the possible ways, currently I haven't any problem, could you explain it a bit , how could it possible to reunlock my BL if it get locked on MIUI?
ahem.
There is NO way to unlock an A2 device that has been converted to an 6X with ARB anti 4.
Your bootloaders are important in this case (xbl.elf and abl.elf). ARB and bootloader status is also managed here.
If you are using A2, with 6X system without ARB anti 4, that phone uses A2 bootloader. So if you lock your bootloader, it will brick to fastboot (The system has been destroyed / Press any key to shutdown). EDL will still accept any flashes without authentication. You may or may not be able to unlock it again through fastboot.
If you are using A2, with 6X system and firmware with ARB anti 4, that phone uses 6X bootloader. So if you lock your bootloader, it will brick to fastboot (The system has been destroyed / Press any key to shutdown). EDL will not accept any flashes without authentication*. You cannot unlock the phone through fastboot**.
*There is a workaround to this but you need to open your phone's back.
**Because MIUI devices need Mi Unlock to be unlocked, and Mi Unlock wants you to log in, and the system is not accessible, your phone will stay bricked.
You can still unbrick the phone with the above workaround, but you will be stuck with China MIUI and won't be able to unlock your phone's bootloader even if you logged in because your phone is not registered on Mi Unlock database (since Android One devices do not need/use Mi Unlock because of Google's enforcements).
Too long, didn't read?
Do not attempt to lock your phone. Even if you are on fully stock with your phone's own firmware. Locking is extremely risky due to the fact that even unlocking the bootloader corrupts the system integrity in some way.
Letzen said:
ahem.
There is NO way to unlock an A2 device that has been converted to an 6X with ARB anti 4.
Your bootloaders are important in this case (xbl.elf and abl.elf). ARB and bootloader status is also managed here.
If you are using A2, with 6X system without ARB anti 4, that phone uses A2 bootloader. So if you lock your bootloader, it will brick to fastboot (The system has been destroyed / Press any key to shutdown). EDL will still accept any flashes without authentication. You may or may not be able to unlock it again through fastboot.
If you are using A2, with 6X system and firmware with ARB anti 4, that phone uses 6X bootloader. So if you lock your bootloader, it will brick to fastboot (The system has been destroyed / Press any key to shutdown). EDL will not accept any flashes without authentication*. You cannot unlock the phone through fastboot**.
*There is a workaround to this but you need to open your phone's back.
**Because MIUI devices need Mi Unlock to be unlocked, and Mi Unlock wants you to log in, and the system is not accessible, your phone will stay bricked.
You can still unbrick the phone with the above workaround, but you will be stuck with China MIUI and won't be able to unlock your phone's bootloader even if you logged in because your phone is not registered on Mi Unlock database (since Android One devices do not need/use Mi Unlock because of Google's enforcements).
Too long, didn't read?
Do not attempt to lock your phone. Even if you are on fully stock with your phone's own firmware. Locking is extremely risky due to the fact that even unlocking the bootloader corrupts the system integrity in some way.
Click to expand...
Click to collapse
Thanks a lot, it explains everything and totally sounds right to me,
Just couple questions:
so in any circumstances it could be again usable just with a Chinese ROM, and so there will be no way to install Google Play on it, since there will be no custom recovery , no root accessibility , ... , It will be for ever with a Pure Chinese ROM (which practically would be unusable for us). Am I right?
Considering above situation, sending the device to a Xiaomi Center could help us to get back to any kind of global ROM (AndroidONE / MIUI) or not?
Right now I am totally happy with Xiaomi.eu MIUI BETA roms, no need to switch to other projects, I need to know is there any chance to stuck with a locked BL while attempting the new Beta ROMs? I use PitchBlack to flash new ROMs every week. Or if I want to ask it in short: How to prevent to get a Locked BL?
Thanks a lot again.
sz.hatef said:
Thanks a lot, it explains everything and totally sounds right to me,
Just couple questions:
so in any circumstances it could be again usable just with a Chinese ROM, and so there will be no way to install Google Play on it, since there will be no custom recovery , no root accessibility , ... , It will be for ever with a Pure Chinese ROM (which practically would be unusable for us). Am I right?
Considering above situation, sending the device to a Xiaomi Center could help us to get back to any kind of global ROM (AndroidONE / MIUI) or not?
Right now I am totally happy with Xiaomi.eu MIUI BETA roms, no need to switch to other projects, I need to know is there any chance to stuck with a locked BL while attempting the new Beta ROMs? I use PitchBlack to flash new ROMs every week. Or if I want to ask it in short: How to prevent to get a Locked BL?
Thanks a lot again.
Click to expand...
Click to collapse
does flashing a MIUI.eu beta ROM without deleting the firmware folder lock the bootloader ?
what's the benefit from not deleting the firmware folder?
i'm using a converted MI A2
thanks
Hi, guys. Such an unpleasant thing happened to me today. I have received my new xiaomi mi 9... But it has came with unlocked bootloader so i have locked it. And when i locked it then the phone got stuck on the recovery mode saying "this miui version can't be installed on this device" but it already came with this MIUI i did not change nothing i just wanted to lock the bootloader. Now i am bricked and i can't do nothing, i have tried to wipe all data, but did not help...
Does anybody know what can i do in this case?
TommyKing18 said:
Hi, guys. Such an unpleasant thing happened to me today. I have received my new xiaomi mi 9... But it has came with unlocked bootloader so i have locked it. And when i locked it then the phone got stuck on the recovery mode saying "this miui version can't be installed on this device" but it already came with this MIUI i did not change nothing i just wanted to lock the bootloader. Now i am bricked and i can't do nothing, i have tried to wipe all data, but did not help...
Does anybody know what can i do in this case?
Click to expand...
Click to collapse
Follow these guides:
https://forum.xda-developers.com/Mi-9/how-to/unlocking-bootloader-immediately-t3926424
https://forum.xda-developers.com/Mi-9/how-to/guide-how-flashed-twrp-xiaomi-eu-rom-t3912952
reply
Laptapper said:
Follow these guides:
https://forum.xda-developers.com/Mi-9/how-to/unlocking-bootloader-immediately-t3926424
https://forum.xda-developers.com/Mi-9/how-to/guide-how-flashed-twrp-xiaomi-eu-rom-t3912952
Click to expand...
Click to collapse
Thank you very much for help. I have read both but unfortunately i can not UNLOCK my bootloader… when i was trying to unlock the bootloader through MI UNLOCK, it says "Current account is not bound to this device". Otherwise if this was succesful and i could unlock it, then it would be easy i believe.
F
F in the chat
Since you locked the boot loader, you'd have to flash (with fastboot) using the same flavor of miui which was installed. (example: chinese or eu variation), otherwise you won't be able to boot.
NikoSpeed said:
F in the chat
Click to expand...
Click to collapse
you think you would know what to do?
nahsha said:
Since you locked the boot loader, you'd have to flash (with fastboot) using the same flavor of miui which was installed. (example: chinese or eu variation), otherwise you won't be able to boot.
Click to expand...
Click to collapse
Yes, that i understood… There was EU variation with unlocked bootloader, which i do not know why, but okay…
But now i can not unlock it, it says, when i try to unlock it though fastboot with mi unlock, it says "Current acount is not bound to this device, ADD your acount and device in MIUI"s setting > developer options> mi unlock status.. but obviously i can not do it since i can not turn on my phone, its stuck on recovery mode.
TommyKing18 said:
Yes, that i understood… There was EU variation with unlocked bootloader, which i do not know why, but okay…
But now i can not unlock it, it says, when i try to unlock it though fastboot with mi unlock, it says "Current acount is not bound to this device, ADD your acount and device in MIUI"s setting > developer options> mi unlock status.. but obviously i can not do it since i can not turn on my phone, its stuck on recovery mode.
Click to expand...
Click to collapse
Try recovering using this: https://www.xiaomitool.com/V2/
nahsha said:
Try recovering using this: https://www.xiaomitool.com/V2/
Click to expand...
Click to collapse
When i choosed "my device is bricked i want to unbrick it" it says, this option is not available yet..
I can help you
First of all you need chinese mi assistant
Second you need try three versions of roms(eeu , china , global) but im pretty sure that your phone is chinese version that bought from gray market and they unlock bootloader to install global rom
After you download these tell me, i guide you
Be sure download recovery rom (not fastboot)
It has .zip extension not tgz
emprazol said:
I can help you
First of all you need chinese mi assistant
Second you need try three versions of roms(eeu , china , global) but im pretty sure that your phone is chinese version that bought from gray market and they unlock bootloader to install global rom
After you download these tell me, i guide you
Be sure download recovery rom (not fastboot)
It has .zip extension not tgz
Click to expand...
Click to collapse
Thanks a lot, i aprreciate your help! Now i am downloading Chinese ROM recovery ROM, chinese mi assistant i have already so let's see, i hope it will work.
TommyKing18 said:
Thanks a lot, i aprreciate your help! Now i am downloading Chinese ROM recovery ROM, chinese mi assistant i have already so let's see, i hope it will work.
Click to expand...
Click to collapse
If you know how to sideload the rom then everything is become okay dont worry
After successful debrick you must bound you mi account to your phone and wait for bl unlock then reflash with mi flash tool and global rom
AND DONT LOCK YOUR BOOTLOADER AGAIN
Yes, unfortunately i do not know how to sidload the rom... But when i have Chinese rom downloaded then what do i do with that? I connect the phone through mi assistant and there it can be flashed?
I had the same thing happen. You need to force a firmware flash ?
I had someone on xda recommend an excellent recovery tool.
It's called 'miflashpro'. It can be hard to find the English version. I did eventually but actually unbricked my Mi9 with the Italian version.
99% chance your cell can be fixed this way
bricked too
I'm having the same problem here, after wipe in twrp mode my phone restart and i'm blocked on bootloader screen.
Bryceicle1971 said:
I had the same thing happen. You need to force a firmware flash ?
I had someone on xda recommend an excellent recovery tool.
It's called 'miflashpro'. It can be hard to find the English version. I did eventually but actually unbricked my Mi9 with the Italian version.
99% chance your cell can be fixed this way
Click to expand...
Click to collapse
I am having the same probelm. .i have accidently locked the bootloader and now stuck in recovery loop. And can not unlock bootloader as i didnt bind my account. Can u plz share the link of miflashpro
That's so unfortunate
TommyKing18 said:
Yes, unfortunately i do not know how to sideload the rom... But when i have Chinese rom downloaded then what do i do with that? I connect the phone through mi assistant and there it can be flashed?
Click to expand...
Click to collapse
I did the same thing with a Mi CC9 relocked the bootloader by mistake thinking it was like any other android phone. Did you have a Xiaomi account associated with the phone and signed into after enabling oem unlock in developer options.
If tha'ts the case you can use https://en.miui.com/unlock/ tool from where but it checks your phone number to see whether its associated with mi unlock.
Otherwise you will have to use EDL method which involves disassembling back of phone and shorting out two pins to initialize EDL data transfer but you need a EDL associated account this (belief xiaomi has revoked everyone access to these)
Hello all members.I had same problem and I open this phone with suport from youtube .I try clean some connector and worming cpu and motherboard. After change the battery with new. When close the phone they suprised me and working good.After 10 hours again close and bricked. I try sake and again open .So....the real problem its not CPU and motherboard but some connector dont touch good. Sory for my English. I hope some other find which connector have problem in this phone and pm me. Now my MI 9 working good but I keep bickerful ...
I ordered a "Global ROM Xiaomi Redmi K20 Pro 12GB 512GB Exclusive Edition Smartphone Snapdragon 855 plus 4000mAh 48MP Triple Cameras 6.39'' on AliExpress (yes I know now it was mistake to get "Global ROM"...). Everything actually looked really good, Google Play store worked, device model showed up as "Mi 9T Pro", only thing I needed to do was lock bootloader for banking apps etc and everything has been working great.
At some point I was offered OTA update to MIUI 11, and I decided to install it last night. The install went until 65% and then the screen went black and the phone rebooted into the dreaded "The system has been destroyed" error. Now since my bootloader is locked I don't know how to recover from this - Mi Unlock Tool and fastboot both won't unlock, Mi tool wants me to add my account in developer options which of course isn't possible. I tried the "fastboot continue" method too with no effect. All I want is stock MIUI with locked bootloader and working OTA updates.
fastboot vars:
product: raphael
secure:yes
anti:1
board_version:4.9.2
hw-revision:20002
unlocked:no
Is EDL mode the only way to recover from this?
So you locked your bootloader and installed the OTA?
Unfortunately yes, bootloader was locked when OTA was installed.
A1a2Z7 said:
I ordered a "Global ROM Xiaomi Redmi K20 Pro 12GB 512GB Exclusive Edition Smartphone Snapdragon 855 plus 4000mAh 48MP Triple Cameras 6.39'' on AliExpress (yes I know now it was mistake to get "Global ROM"...). Everything actually looked really good, Google Play store worked, device model showed up as "Mi 9T Pro", only thing I needed to do was lock bootloader for banking apps etc and everything has been working great.
At some point I was offered OTA update to MIUI 11, and I decided to install it last night. The install went until 65% and then the screen went black and the phone rebooted into the dreaded "The system has been destroyed" error. Now since my bootloader is locked I don't know how to recover from this - Mi Unlock Tool and fastboot both won't unlock, Mi tool wants me to add my account in developer options which of course isn't possible. I tried the "fastboot continue" method too with no effect. All I want is stock MIUI with locked bootloader and working OTA updates.
fastboot vars:
product: raphael
secure:yes
anti:1
board_version:4.9.2
hw-revision:20002
unlocked:no
Is EDL mode the only way to recover from this?
Click to expand...
Click to collapse
Flash correct regional ROM through QPST/QFIL
You'll get a locked bootloader with OTA updates
Thanks for the response. It looks like QPST/QFIL only work if the device is already in EDL mode. Is there a way to boot to EDL without special cable / using motherboard test points? I tried fastboot oem edl and got "FAILED (remote: 'Oem edl command is not allowed Lock State')".
Following this Thread. Let me know If you get any Answer please mine stuck too and cant do aything and dont want to open my brand new device.
2VJ5 said:
Flash correct regional ROM through QPST/QFIL
You'll get a locked bootloader with OTA updates
Click to expand...
Click to collapse
It doesn't work with Raphael.
So an update for those wondering. To fix this I had to use EDL mode and flash the original China ROM. It seems EDL cables do not work on this phone, so I had to open it up and use the test point method to boot into EDL mode. Even in EDL mode and using QFIL, there is still an authentication process on the phone itself, which requires an authorized Xiaomi account in order to load firmware. Obviously my own account does not have that authorization, so I paid $30 to one of those shady looking "unbrick" services. They remoted into my PC with UltraViewer (TeamViewer ripoff) and logged into their account and the flash succeeded.
Lesson learned... never lock the bootloader on this phone!
hello, i have a problem with my redmi 9c
my phone just started bootloping alone, i went to sleep and i woke up with my phone dead
the phone is stock, no root, no custom recovery and still with bootloader locked because i don't need features who need it, i can access fastboot but recovery is not posible to reach because Vol+/Power is useless, the phone do nothing pressing those buttons, only with Vol-/Power, so i can't make a factory reset or wipe data, the only thing what i did a couple of hours before the phone broke was change my security pattern (i don't think it's related anyway...), and it was 8 or 10 hours before the issue. sadly the phone warranty expired in january and i have nothing to do at this moment
the phone stops the bootloop after draining the battery, with the bootloader locked of course i'm unable to flash a stock rom, even with MiFlash
what could be the problem?
thanks! (and sorry for my bad english, spanish native here)
aniangaZR said:
hello, i have a problem with my redmi 9c
my phone just started bootloping alone, i went to sleep and i woke up with my phone dead
the phone is stock, no root, no custom recovery and still with bootloader locked because i don't need features who need it, i can access fastboot but recovery is not posible to reach because Vol+/Power is useless, the phone do nothing pressing those buttons, only with Vol-/Power, so i can't make a factory reset or wipe data, the only thing what i did a couple of hours before the phone broke was change my security pattern (i don't think it's related anyway...), and it was 8 or 10 hours before the issue. sadly the phone warranty expired in january and i have nothing to do at this moment
the phone stops the bootloop after draining the battery, with the bootloader locked of course i'm unable to flash a stock rom, even with MiFlash
what could be the problem?
thanks! (and sorry for my bad english, spanish native here)
Click to expand...
Click to collapse
Hi, my first guess would be faulty hardware, for example a dead motherboard.
Is there any error when attempting to flash the Stock ROM with MiFlash? Afaik you should be able to flash Stock ROMs even with locked bootloader.
Fatal_Scythe said:
Hi, my first guess would be faulty hardware, for example a dead motherboard.
Is there any error when attempting to flash the Stock ROM with MiFlash? Afaik you should be able to flash Stock ROMs even with locked bootloader.
Click to expand...
Click to collapse
Thanks for the quick reply
MiFlash said "not allowed in locked state" and I guess it's because of locked bootloader, I should try with a specific stock rom?
aniangaZR said:
Thanks for the quick reply
MiFlash said "not allowed in locked state" and I guess it's because of locked bootloader, I should try with a specific stock rom?
Click to expand...
Click to collapse
Hmm okay, yeah that sounds like it's preventing you from flashing simply because your bootloader is locked.
Which Stock ROM did you try? Same as the currently installed version or an older one?
Fatal_Scythe said:
Hmm okay, yeah that sounds like it's preventing you from flashing simply because your bootloader is locked.
Which Stock ROM did you try? Same as the currently installed version or an older one?
Click to expand...
Click to collapse
I tried with the last available rom and the previous one, automatic updates were disabled, but I know I updated the phone after buying it
I don't remember if the phone was running last version...
MiFlash should let me flash the phone with the same installed ROM even with bootloader locked?
aniangaZR said:
I tried with the last available rom and the previous one, automatic updates were disabled, but I know I updated the phone after buying it
I don't remember if the phone was running last version...
MiFlash should let me flash the phone with the same installed ROM even with bootloader locked?
Click to expand...
Click to collapse
If you tried an older firmware, it's possible that it didn't flash because of Xiaomi's "Anti-Rollback" Feature which exists to prevent users from Downgrading.
But yes, it should let you flash the same version afaik.
What Region is your Device? On Locked Bootloader you can only flash Firmwares that are from the same Region. (For example Global or EEA)
Fatal_Scythe said:
If you tried an older firmware, it's possible that it didn't flash because of Xiaomi's "Anti-Rollback" Feature which exists to prevent users from Downgrading.
But yes, it should let you flash the same version afaik.
What Region is your Device? On Locked Bootloader you can only flash Firmwares that are from the same Region. (For example Global or EEA)
Click to expand...
Click to collapse
Device is global region, I will try with all versions available, I'll keep updated
Thanks!
aniangaZR said:
Device is global region, I will try with all versions available, I'll keep updated
Thanks!
Click to expand...
Click to collapse
Alright, have you btw tried flashing directly via fastboot?
Meaning opening terminal and from there flashing all partitions one by one for example "fastboot flash boot boot.img" ?
Fatal_Scythe said:
Alright, have you btw tried flashing directly via fastboot?
Meaning opening terminal and from there flashing all partitions one by one for example "fastboot flash boot boot.img" ?
Click to expand...
Click to collapse
Fastboot doesn't work either, said similar message related to locked bootloader
I'm downloading a couple of roms now
aniangaZR said:
Fastboot doesn't work either, said similar message related to locked bootloader
I'm downloading a couple of roms now
Click to expand...
Click to collapse
Oh okay then.
If in the worse case nothing works, your last (paid) solution would probably be to contact one of these "Mi Auth" Guys on Telegram. They have acess to Authorized Accounts that are able to flash your Phone in EDL Mode (might need to open your phone to short test-points though)
I had to pay them about 20€ to get my old Mi 11 (which I sold a while ago) running again after it got stuck in EDL Mode. :/
Fatal_Scythe said:
Oh okay then.
If in the worse case nothing works, your last (paid) solution would probably be to contact one of these "Mi Auth" Guys on Telegram. They have acess to Authorized Accounts that are able to flash your Phone in EDL Mode (might need to open your phone to short test-points though)
I had to pay them about 20€ to get my old Mi 11 (which I sold a while ago) running again after it got stuck in EDL Mode. :/
Click to expand...
Click to collapse
same problem with all ROMs, same message related to bootloader
thanks anyway!