I have discovered that I was easily able to unlock my device's bootloader using fastboot, even after OEM unlocking was disabled in development settings.
I want to know is it just me or is it a loophole found on all MI A1 devices, which needs to be fixed.
I have previously unlocked my bootloader and flashed TWRP recovery, but currently I am on the latest Global Stable Rom N2G47H.7.12.7 with no root or recovery installed.
You are right, I was able to unlock the bootloader and boot into TWRP.
I did reflash the official rom with wipe and lock last weekend, so the device is stock.
Related
My device is not connected in fastboot mode 2 pc and cannot unlock my bootloader 2 install gcam on it
You probably need to update the driver for the phone while it is connected to the computer in fastboot mode.
Have you unlocked A1 using MI official unlock site ?. A1 cant be unlocked by adb command. Go to their official unlock site and request for unlocking, then install Gcam.
I unlocked bootloader , then enabled camera 2 API and installed gcam.will it wipe data after may security patch when bootloader is relocked when relocked using abd??
Hey Guys,
My P10lite is a WAS-LX1A C432 B208 and runs under the Custom Rom Elemental V4 Android 7. I got no root, the bootloader is unlocked but Frp is on lock (Oem Unlock in Devs. Is greyed out). Custom Recovery is not installed. All 30mins the Phone boots in Erecovery. Bootloader Code is forgotten. The Huawei Site is offline. Fastboot Commands will not work propably cuz Frp lock. What can i do now? Need rollback to stock, root and the other stuff is wayne only want to stock system that works find.
Use Oreo service rom to upgrade. You can find it in this forum
Sent from my WAS-LX1 using Tapatalk
I updated to Pie today using OTA. This resulted in a bootloop. Since my bootloader was already unlocked, I booted TWRP (not flashed) and swapped slots. This resulted in booting to the recovery "no command" prompt instead. So I downloaded the only ROM Xiaomi has on their site - 8.1 - and flashed this with the "flash_all_except_storage" script. Still bootloops, only now the bootloader is relocked.
So, anyone know how to unlock the bootloader on a non-booting Android One device? Is there an EDL mode on these?
tin2001 said:
I updated to Pie today using OTA. This resulted in a bootloop. Since my bootloader was already unlocked, I booted TWRP (not flashed) and swapped slots. This resulted in booting to the recovery "no command" prompt instead. So I downloaded the only ROM Xiaomi has on their site - 8.1 - and flashed this with the "flash_all_except_storage" script. Still bootloops, only now the bootloader is relocked.
So, anyone know how to unlock the bootloader on a non-booting Android One device? Is there an EDL mode on these?
Click to expand...
Click to collapse
Seriously? No one reads thread online?! I quote to NEVER, EVER, FLASH OREO/NOUGAT ROMS AFTER UPDATING TO PIE!!!
I downloaded the latest OFFICIAL ROM when it was already bootlooping.... Seriously? I'm supposed to go searching online for 3rd party information rather than the official?
Now how about people with useful information instead of arrogance?
If I'm not wrong you just need to boot into bootloader and fastboot oem unlock. With unlocked bootloader, go fastboot mode and flash official stock pie fastboot rom
Hi everybody
I redid an installation of my xiaomi mi9t under miui 11.0.3 to start again on good bases because I had done a lot of trying to try to succeed in rooting it
So I relocked the bootloader and I followed the tutorial from A to Z to root the tel.
So these are the manipulations I did:
Unlock the bootloader with the miui tool
Fastboot flash recovery twrp.img
Fastboot boot twrp.img
Installation of the magisk zip.
Restart.
And then I restore my data with micloud and when I go to developer option it says that my bootloader and locked and OEM unlocking is no longer grayed out I can deactivate it when before it was not possible.
I don't know if it's the fact that I restored via micloud or that I used the xiaomi native security and cleaner app.
However my phone is well rooted and unlock bootloader because it is marked unlocked at startup and for rooting all the apps that request root rights have it.
Thank you for your answers.
Hello, I recently purchased the T-mobile version of the 6T (bad idea) that had a locked bootloader, and tried to flash it to the international version so I can root the device. I followed this post in hopes of achieving it. The device will no longer boot. The screen quickly flashes with a Oneplus logo with "fastboot mode" underneath then I am met with this error: "Build version and HW is not match!". Is it completely bricked? Can I flash back to a T-Mobile OS?
If it is truly bricked I am curious if someone could explain why it may have happened. As in, has T-Mobile changed some the checks involved with flashing to the international version? Or was it because the device was running the latest Oxygen OS, is it impossible to downgrade this way? I am genuinely curious and want to take this as a bitter learning experience.
Thanks for your input.
It depends, did you select oem unlock and usb debugging and then unlock the bootloader prior to trying to flash another rom to the device? If you successfully unlocked the bootloader, prior to messing around with flashing, then no, I doubt you hard bricked. If you did NOT unlock the bootloader, then yes, you may have hard bricked.
If you did unlock the BL, I would suggest flashing the fastboot rom for the build your currently on. Or, you could use the msm tool. Both of the above can be found in the forums for the 6t.
Pain-N-Panic said:
It depends, did you select oem unlock and usb debugging and then unlock the bootloader prior to trying to flash another rom to the device? If you successfully unlocked the bootloader, prior to messing around with flashing, then no, I doubt you hard bricked. If you did NOT unlock the bootloader, then yes, you may have hard bricked.
If you did unlock the BL, I would suggest flashing the fastboot rom for the build your currently on. Or, you could use the msm tool. Both of the above can be found in the forums for the 6t.
Click to expand...
Click to collapse
Thanks for the reply. Oem unlock and usb debugging were enabled but the bootloader was not unlocked. I was trying to avoid the 7-day wait time for the unlock bin from oneplus/tmobile.
I was able to flash back to tmobile OOS 9.0 found in this post using the v2 version. I was still able to update OTA to the latest 10.3.7.
Edit: Some_Random_Username has comented to include tmobile OOS 10.3.7
Did you get it all figured out? If not here's a semi detailed version of what I had to do with my tmobile 6t, because I had issues as well. Mainly my phone not showing up in msm tool. Only wanted to work after it had Android 9. Also I had little sleep the night I did this so I'm trying to recall the best I can.
Assuming your phone shows in msm tool at this point
Used msm tool to flashed older A9 ops https://androidfilehost.com/?fid=11410963190603895067
Boot in and enable adb and oem bootloader unlock
Boot to bootloader and unlock it
Flashed first A10 OOS https://androidfilehost.com/?fid=4349826312261819701
Flashed 10.3.7 to both slots with twrp https://androidfilehost.com/?fid=10763459528675591630
Flash rom
Flash Magisk
Profit
Some of this could be redundant, but my late night research and trial and error paid off.
GoldfishSnack said:
Thanks for the reply. Oem unlock and usb debugging were enabled but the bootloader was not unlocked. I was trying to avoid the 7-day wait time for the unlock bin from oneplus/tmobile.
I was able to flash back to tmobile OOS 9.0 found in this post using the v2 version. I was still able to update OTA to the latest 10.3.7.
Edit: Some_Random_Username has comented to include tmobile OOS 10.3.7
Click to expand...
Click to collapse
Well I'm glad you were able to get it up and running. I highly suggest unlocking that bootloader as soon as you can....having an unlocked BL is key to getting out of a lot of bricked situations.