Related
Hi
I have a BIG problem with my P10 (L29C432) on Oreo 365.
Tried downgrade to nougat through Firmware Finder but update failed. Now i have this warning at every reboot.
I have LOCKED bootloader (never rooted phone). And i cant get bootloader unlock code (website not working).
Also cant enter fastboot mode because of that error.
Is there anyway to RESTORE phone with locked bootloader? I have tried to flash previous firmware with sdcard method (hold power,+,- keys) but update fails everytime.
Is there other way to flash new firmware?
I can use phone but at every reboot i get this message?
If there is no other way to flash new firmware than with unlocked bootloader... Where to get code for unlocking bootloader?
Thanks.
Edit:
I can enter fastboot mode but my bootloader is locked.
you have to unlock bootloader by sending all the needed info per email.
you need to send them IMEI, model version, S/N number, and product id and request for bootloader unlocking code this email: [email protected]
next time read about how to rollback to nougat...
Thank you. So I need to unlock bootloader.
Will try to get code.
tomzzi said:
Thank you. So I need to unlock bootloader.
Will try to get code.
Click to expand...
Click to collapse
If you don't have your "product id", you can't have the code for unlock the bootloader :/
The "Product ID" is a code into the system info on android :s
I am waiting for code from Huawei. They will send me code in next days...
you can get product id on imei24. com by typing your imei.
Now i have another problem. I think phone is "dead" now. Unuseable.
Tried to root phone and now nothing works.
Phone does not recognize SIM card at all.
If I go into settings and system information there is no IMEI number?
Can i restore this?
Or need to take it to service center? Or dead phone?
send the device against wall. Buy another one and forget averything about rooting and unlocking bootloader. Its for your safety, trust me.
I have experience with rooting and flashing phones (Sony). Never had problem.
So there is no way to restore phone?
maybe in repair store. Never heard about bricked device without imei. You can still try to flash original firmware.
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
My redmi 4x (santoni) have twrp installed and I it is running on miui pro rom. But it's bootloader locking automatically after enabling usb debugging and switching off the phone. I can't boot into recovery and system, can only boot into fastboot mode, and I have to use mi flash tool to unlock bootloader again.
If someone face this problem, is there any solution of this. Please reply.
Thank you.
Bootloader can only be locked on all available official MIUI ROM, it can not be locked on modified MIUI versions.
There is no way that it'll get locked by itself by turning on USB Debugging and switching off phone. to lock unlocked bootloader one has to clean flash from Mi flash tools and needs to select lock bootloader before flashing.
I don't know how are you able to unlock bootloader on Mi flash tools because to unlock it official way one will need Mi unlock tool with permission from xiaomi(depending on region)
First make sure you are not on fake MIUI if so then flash official one through mi flash tools and then unlock it by mi unlock tools.
Once it is unlocked as i said earlier there is no way that it will get locked itself unless you choose to lock via mi flash tools.
about unlocking again
sorry for mistake, I have to use mi unlock tool again with my mi account signed in to unlock the bootloader again. And can't unlock by fastboot command "fastboot oem unlock".
yuyutsu said:
sorry for mistake, I have to use mi unlock tool again with my mi account signed in to unlock the bootloader again. And can't unlock by fastboot command "fastboot oem unlock".
Click to expand...
Click to collapse
I still do not get it what exact issue you have and what version of MIUI you are on.
You are saying you are on MIUI Pro and that confirms bootloader is unlocked and now you are saying
"I have to use mi unlock tool again with my mi account signed in to unlock the bootloader again. And can't unlock by fastboot command "fastboot oem unlock"
Click to expand...
Click to collapse
Please share exact and more details if you wish to resolve your issue and possibly some screenshot(s) of about phone and errors if any.
metelhammer said:
I still do not get it what exact issue you have and what version of MIUI you are on.
You are saying you are on MIUI Pro and that confirms bootloader is unlocked and now you are saying
Please share exact and more details if you wish to resolve your issue and possibly some screenshot(s) of about phone and errors if any.
Click to expand...
Click to collapse
I have a similar issue and came across this thread, usb debugging suddenly stopped working, it was working perfectly till yesterday. So when I went to developer options, I saw that the OEM unlocking option is clickable now ( it had remained grayed out ever since I unlocked the bootloader ). The Mi Unlock status option tells me that phone is locked. Toggling usb debugging is not making it work. When I restart the phone, I definitely see the unlocked padlock icon on the boot screen. So I am not sure what is going on. also, magisk is working fine.
In the screenshot you can see that it shows the device is locked. But from the status bar you can make out that exposed is working. I'll have to get another device though to get a picture of the padlock icon though.
Ontropy said:
I have a similar issue and came across this thread, usb debugging suddenly stopped working, it was working perfectly till yesterday. So when I went to developer options, I saw that the OEM unlocking option is clickable now ( it had remained grayed out ever since I unlocked the bootloader ). The Mi Unlock status option tells me that phone is locked. Toggling usb debugging is not making it work. When I restart the phone, I definitely see the unlocked padlock icon on the boot screen. So I am not sure what is going on. also, magisk is working fine.
In the screenshot you can see that it shows the device is locked. But from the status bar you can make out that exposed is working. I'll have to get another device though to get a picture of the padlock icon though.
Click to expand...
Click to collapse
Toggle OEM unlock enabled doesn´t mean that the device is unlocked, it only means that the bootloader can be unlocked, there is other item just lines after to check it; Mi Unlock status, enter to it and confirm it.
Also, you can confirm the bootloader status through fastboot with fastboot oem device-info
SubwayChamp said:
Toggle OEM unlock enabled doesn´t mean that the device is unlocked, it only means that the bootloader can be unlocked, there is other item just lines after to check it; Mi Unlock status, enter to it and confirm it.
Also, you can confirm the bootloader status through fastboot with fastboot oem device-info
Click to expand...
Click to collapse
Yea as I mentioned, the mi unlock status tells me that phone is locked.
Just check via fastboot, and it shows that phone is unlocked.
So do I just believe fastboot, or wait a month and then try to again unlock the bootloader via the mi unlock tool?
Ontropy said:
Yea as I mentioned, the mi unlock status tells me that phone is locked.
Just check via fastboot, and it shows that phone is unlocked.
So do I just believe fastboot, or wait a month and then try to again unlock the bootloader via the mi unlock tool?
Click to expand...
Click to collapse
You said "In the screenshot you can see that it shows the device is locked" but unfortunately the screenshot didn´t reveal that, I wonder, what exactly it says in the Mi Unlock status apart.
In older days, users share an aboot image, this served to unlock bootloader automatically without make the official process to unlock it, it could be that you flashed the official stock images, and it got re-locked. Anyway, we don´t know what happened with the fastboot command or with the Mi Unlock status section, so no respond to those points.
For the part you say to wait a certain time, definitely, no, the bootloader process is not monitored any more, for older devices, they can be unlocked instantly.
SubwayChamp said:
You said "In the screenshot you can see that it shows the device is locked" but unfortunately the screenshot didn´t reveal that, I wonder, what exactly it says in the Mi Unlock status apart.
In older days, users share an aboot image, this served to unlock bootloader automatically without make the official process to unlock it, it could be that you flashed the official stock images, and it got re-locked. Anyway, we don´t know what happened with the fastboot command or with the Mi Unlock status section, so no respond to those points.
For the part you say to wait a certain time, definitely, no, the bootloader process is not monitored any more, for older devices, they can be unlocked instantly.
Click to expand...
Click to collapse
My phone is about a month old, so it does tell me to wait. Contradictory screenshots attached below. After the boot unlock, I did flash flash a magisk edited boot.img and vbmeta.img to disable it. If I remember correctly though it was fine after that.
Yesterday, I was going to lock my bootloader to cell my Nokia 8 cuz' I needed money. Being the noobie that I'm I didn't have my unlock key saved anywhere. and couldn't get a new one because the stupid Bootloader unlock app doesn't work on Pie. I did know that locking the bootloader doesn't require a key. So I just went with it without remembering that I still had TWRP instead of stock boot img installed. So when I locked the bootloader the phone booted into a screen similar to the unlocked Bootloader warning screen. But it said "Your Device is corrupt. It can't be Trusted and will not boot." Instead. So now I have locked bootloader with TWRP that I can't boot into. I still can boot into fastboot mode but I can't do much Because LoCkEd BooTlOaDeR. The only sulotion is to unlock the bootloader with an unlock key Which I don't have and flash stock boot. So please help. You'll be literally saving my life. This is my first thread ever on the internet so forgive me If I made any mistakes:laugh:
EDIT: I took my phone to the service centre near me and they were able to fix it
CommieTurtle said:
Yesterday, I was going to lock my bootloader to cell my Nokia 8 cuz' I needed money. Being the noobie that I'm I didn't have my unlock key saved anywhere. and couldn't get a new one because the stupid Bootloader unlock app doesn't work on Pie. I did know that locking the bootloader doesn't require a key. So I just went with it without remembering that I still had TWRP instead of stock boot img installed. So when I locked the bootloader the phone booted into a screen similar to the unlocked Bootloader warning screen. But it said "Your Device is corrupt. It can't be Trusted and will not boot." Instead. So now I have locked bootloader with TWRP that I can't boot into. I still can boot into fastboot mode but I can't do much Because LoCkEd BooTlOaDeR. The only sulotion is to unlock the bootloader with an unlock key Which I don't have and flash stock boot. So please help. You'll be literally saving my life. This is my first thread ever on the internet so forgive me If I made any mistakes:laugh:
EDIT: I took my phone to the service centre near me and they were able to fix it
Click to expand...
Click to collapse
Hello! I have the same problem! (((You were not interested in what exactly or how you should do to correct the error? And how much money did you get for repair?
Well you can use original OST not NOST and flash signed images (.NB1) without unlocking bootloader.
KonikoO said:
Well you can use original OST not NOST and flash signed images (.NB1) without unlocking bootloader.
Click to expand...
Click to collapse
Only with service point authorization as far as I know. OST (and NOST by extension) usually show you a login prompt when you launch them. Service Points login to a server that generates a temporary unlock key, which allows OST to reflash the partitions. With the proper authorization, even NOST could flash .qlz files (as long as the images inside are official and signed) with a locked bootloader.
Since we don't have service point permission we have to patch the tool to ignore it (both NOST and the hacked OST). It will still try to request the temporary key, fail, and pass an empty value to the bootloader. To get the bootloader to accept the following flashing commands, you have to unlock it.
Hey Everyone,
I'm looking for help. I tried reverting my pixel 5 to stock from beta and am stuck at the boot screen with " your device is corrupt. It cannot be trusted and may not work properly."
I've spent days fiddling with it, and cannot get anywhere with the google repair website because it's saying my bootloader is locked. I don't understand how I purchased it unlocked. Anyway, I cannot get into the settings to unlock the bootloader. It's been a long time since I've been a tinkerer but I do have all the software downloaded to do so. I cannot get my PC to recognize the phone in the command prompt window to try and sideload a software install.
Has this happened to anyone and is there a solution out there somewhere?
Sean Hicks said:
Hey Everyone,
I'm looking for help. I tried reverting my pixel 5 to stock from beta and am stuck at the boot screen with " your device is corrupt. It cannot be trusted and may not work properly."
I've spent days fiddling with it, and cannot get anywhere with the google repair website because it's saying my bootloader is locked. I don't understand how I purchased it unlocked. Anyway, I cannot get into the settings to unlock the bootloader. It's been a long time since I've been a tinkerer but I do have all the software downloaded to do so. I cannot get my PC to recognize the phone in the command prompt window to try and sideload a software install.
Has this happened to anyone and is there a solution out there somewhere?
Click to expand...
Click to collapse
Buying it "unlocked" means you bought it free of a carrier, such as Verizon, who lock the bootloader, and can't be unlocked.
But you still need to unlock the bootloader, it comes locked, for security reasons. So if you never unlocked it, it's locked.
I haven't installed beta 12 yet.
Do you have the latest SDK tools? (adb, fastboot, etc)
I was under the impression though, that you can't downgrade with a locked bootloader. But not sure.
Sean Hicks said:
Hey Everyone,
I'm looking for help. I tried reverting my pixel 5 to stock from beta and am stuck at the boot screen with " your device is corrupt. It cannot be trusted and may not work properly."
I've spent days fiddling with it, and cannot get anywhere with the google repair website because it's saying my bootloader is locked. I don't understand how I purchased it unlocked. Anyway, I cannot get into the settings to unlock the bootloader. It's been a long time since I've been a tinkerer but I do have all the software downloaded to do so. I cannot get my PC to recognize the phone in the command prompt window to try and sideload a software install.
Has this happened to anyone and is there a solution out there somewhere?
Click to expand...
Click to collapse
This probably isn't of any help now, but going forward, it may be. In Developer options, you can enable 'OEM unlocking'. As you can see now, it may well be a very good idea to enable that **before** you start messing with the phone, because if something does go wrong (as it has for you), then you can (hopefully) still get to fastboot and do 'fastboot flashing unlock'.
So, knowing this, you may want to keep an eye out for some tool or something that will allow you to possibly turn on oem unlocking (because your device won't boot).
Another thing to try is switching slots and see if the other slot boots? If you can get to fastboot try; fastboot --set-active=(a or b), then fastboot reboot. (If you don't know which slot is active, do 'fastboot getvar all', in the output it will tell you which is current.
cheers
Your bootloader being locked should not affect your ability to restore factory images/OTAs from Google. They are signed by Google and will pass the signature checks. You should try to download the latest factory image (either 11 or 12beta) and flash it via recovery => adb sideload.