Database Users

Bootloop With locked bootloader 7.0

My 6p is stuck in a bootloop. nbd90x build my bootloader is locked is there anyway to unlock from adb. I have already tried sideloading ndb90x through adb wipping chache and user data and still no luck. Help me Xda youre my only hope..

So you previously enabled USB debugging, how about OEM unlocking? If so, use 'fastboot flashing unlock' to unlock the bootloader. Note that internal storage will be completely wiped. Everything. Though with USB debugging enabled, you should be able to adb pull the contents of you SD card first. If you can unlock the bootloader you can try flashing factory images with fastboot. Otherwise, not much else besides RMA it with Google. There's been a few reports of stock N6Ps bootlooping. Haven't seen anyone post that Google denied the claim.

no bootloader is locked so cant flash using flashboot but debugging is enabled so I am able to use adb .

I know. What I'm asking is if you enabled allow OEM unlocking in developer settings? That doesn't unlock your bootloader in itself. You still need to use fastboot to do it. However if that setting IS enabled what you can do is... Use ADB to pull your internal storage to PC. Then use fastboot to unlock the bootloader and flash factory images. If the setting is not enabled, and wiping data and flashing an OTA don't work, I'm not sure what else can be done.
You can try downloading the 7.1 dev preview OTA and seeing if it updates whatever is causing it to fail. Other than those, RMA would be your best bet.
https://developer.android.com/preview/download.html#device-preview

After sideloading a ton of times between 7.0 and 7.1, one time i got it to boot up then i immediately enabled oem unlock then it crashed again... so now I am able to flash through fastboot although I havent been able to get it to boot again. Is it normal for bootloops to not get fixed by flashing?

Hijacking your post to report what is happening to me. I posted the same thing on the Android Beta program community on G+.
Have been using the latest beta since it came out on completely stock 6P (locked bootloader, unrooted). Everything working normally when yesterday around 10 or 11AM, phone starts to bootloop OUT OF NOWHERE, it was just sitting there on the table while I was working. I could still get to bootloader/recovery, so that was a bit of a relief. First thing I tried: clear cache, nothing. Then proceed to wipe/factory reset the device, to no avail. Immediately downloaded the latest factory image from Google's page, tried flashing it but couldn't since the bootloader was locked (OEM unlock option also disabled). Then downloaded the beta OTA and sideloaded it, process went through OK but device still bootloops. Tried sideloading the latest stable OTA but didn't work since it was from a previous build. Ran out of ideas. So there I was creating a thread on XDA for help while the device was still on its bootloop rush, about to hit the Submit button when again OUT OF THE BLUE SKY the device decides to boot itself back up. First thing I did was unlock the bootloader. Phone worked normally for 6 or 7 hours, when I'm doing something on it and then again, screen froze and bootloop starts again. This time I only reset the device and left the it bootlooping, after about 30 minutes it boots up again. I unenrolled from the beta and installed the latest 7.0 build. Everything working fine for the last 12 hours. Anyone have any idea on what can cause the device to bootloop like that? Never seen anything like it.

Yea I signed up for the beta program too do you have the link to unenroll? So you just reset and let it sit?

Here you go
google.com/android/beta

do you remember what you did to get it to boot?

noetre said:
do you remember what you did to get it to boot?
Click to expand...
Click to collapse
Well, that's the thing. Everything I tried didn't seem to work. I couldn't flash the factory image since the bootloader was locked. I was able to sideload the beta OTA but the device still bootlooped after that. So I just left it bootlooping and after around 20 or 30 minutes the device booted normally. I have no idea what caused it and what I did to make it work again.
P.S: device restarted 2 times while I was typing this.

noetre said:
do you remember what you did to get it to boot?
Click to expand...
Click to collapse
If your boot loader is locked you are screwed, sorry to say, I would RMA it. Unbelievable an update can mess a phone up...that's why I always unlock the bootloader first thing and never lock it. I need complete control of my phone.
Edit: Only thing I can think of is delete the partitions with fastboot or adb and reflash factory image.

boot loader is unlocked now Ive tried flashing using the flash-all script but the phone still wont boot

noetre said:
boot loader is unlocked now Ive tried flashing using the flash-all script but the phone still wont boot
Click to expand...
Click to collapse
As a last resort, flash all of the images manually with fastboot. This will wipe all userdata and completely format the SDcard. Nothing will be left. Extract the bootloader and radio images from the factory images zip. Flash them in fastboot. Reboot to fastboot again. Extract the next zip in the same folder as BL & radio images and flash the vendor, system, boot, recovery & userdata image files. Just for good measure, boot to recovery (stock Android recovery) and perform a factory reset & cache wipe. If the phone still fails to boot, your only option would be to RMA it at this point.
Note: As per Heisenberg's sticky thread, do NOT flash userdata.img if you have anything besides the 32gb model as you will only have the ~32gb storage available. If you're using a model with more storage, just use fastboot to format userdata but don't flash the image.

Ill try that.. but isnt the warranty voided because the bootloader is unlocked?

noetre said:
Ill try that.. but isnt the warranty voided because the bootloader is unlocked?
Click to expand...
Click to collapse
Not on a Nexus, no.
Added: I had to RMA mine after the phone got its first update. I unlocked the bootloader and stayed stock for a long time (until N came out). I took the OTA in About Phone and it applied with no problems but the phone would not boot. Factory images also couldn't get it running. Stock recovery and all. RMA'd without issues. I didn't tell them, just sent it in. If they tried to boot it they would've seen the unlock symbol. There's also a thread somewhere buried in the general section where someone called Google and asked and they confirmed to them that unlocking does not void warranty. I'll try to find it for you.
Found it: http://forum.xda-developers.com/nexus-6p/general/unlocking-bootloader-warranty-google-t3229804/page1
I also returned 4 faulty Nexus 5's (mostly screen artifacts) all unlocked with no problems.

No Recovery

I think i made i grave mistake. I want to upgrade my p9 lite to nougat so I decided to unroot my phone. The unrooting is successful with the device still booting. So next thing i want is to flash back my stock recovery so I can update my phone through OTA (this is where I made a mistake.) I tried doing it by flashing a full MM Rom that i got directly from huawei through dload method. The flashing went smoothly or so I thought. My phone got stuck in a boot loop and I cant seem to access recovery. eRecovery is also inaccessible so I tried reflashing the full MM Rom through dload method but I can't get it to work anymore. I tried it several times with no luck. I also tried reflashing meticulus' twrp through fastboot method but I always get an error saying "remote command not allowed". The bootloader is still unlock btw.
Someone help me. I don't know what to do anymore... :crying:

NikkoVicedo said:
I think i made i grave mistake. I want to upgrade my p9 lite to nougat so I decided to unroot my phone. The unrooting is successful with the device still booting. So next thing i want is to flash back my stock recovery so I can update my phone through OTA (this is where I made a mistake.) I tried doing it by flashing a full MM Rom that i got directly from huawei through dload method. The flashing went smoothly or so I thought. My phone got stuck in a boot loop and I cant seem to access recovery. eRecovery is also inaccessible so I tried reflashing the full MM Rom through dload method but I can't get it to work anymore. I tried it several times with no luck. I also tried reflashing meticulus' twrp through fastboot method but I always get an error saying "remote command not allowed". The bootloader is still unlock btw.
Someone help me. I don't know what to do anymore... :crying:
Click to expand...
Click to collapse
The bootloader appears unlocked, and says so, but it's not...I encountered the same situation with my colleagues device, you need to unlock it either way(careful this will wipe all your data if on nougat, but if on MM after unlocking keep phone connected to PC as it reboots and quickly press vol down+ power to get back to bootloader In order to flash TWRP, this will preserve your data partition and system), and try again, you need format that data partition by using changing format to f2fs then ext4...after this reboot, if it can't, reinstall the file In dload folder and go to stock recovery(disconnect phone from PC to do this if it fails) and do a factory reset.
.... if this fails, debrand And install MM or NOUGAT for your newly debranded system.
If this fails, which is highly unlikely,PM for un orthodox methods.
_New World Order (NWO)_

daner[email protected] said:
The bootloader appears unlocked, and says so, but it's not...I encountered the same situation with my colleagues device, you need to unlock it either way(careful this will wipe all your data if on nougat, but if on MM after unlocking keep phone connected to PC as it reboots and quickly press vol down+ power to get back to bootloader In order to flash TWRP, this will preserve your data partition and system), and try again, you need format that data partition by using changing format to f2fs then ext4...after this reboot, if it can't, reinstall the file In dload folder and go to stock recovery(disconnect phone from PC to do this if it fails) and do a factory reset.
.... if this fails, debrand And install MM or NOUGAT for your newly debranded system.
If this fails, which is highly unlikely,PM for un orthodox methods.
_New World Order (NWO)_
Click to expand...
Click to collapse
The problem is I cannot access recovery anymore. After trying to flash back full rom from huawei, i cannot access recovery anymore no matter how hard i try. eRecovery is also not accessible so i cannot turn off my phone. I tried flashing twrp trough fastboot i keep getting an error saying "remote command not allowed". Dload method is not working anymore. If only I can find a way to flash twrp, then I can restore the dump i made using meticulus' twrp.

NikkoVicedo said:
The problem is I cannot access recovery anymore. After trying to flash back full rom from huawei, i cannot access recovery anymore no matter how hard i try. eRecovery is also not accessible so i cannot turn off my phone. I tried flashing twrp trough fastboot i keep getting an error saying "remote command not allowed". Dload method is not working anymore. If only I can find a way to flash twrp, then I can restore the dump i made using meticulus' twrp.
Click to expand...
Click to collapse
Assuming that you have the unlock code, what happens if you try unlock bootloader again irrespective what status it is now?
_New World Order (NWO)_

[email protected] said:
Assuming that you have the unlock code, what happens if you try unlock bootloader again irrespective what status it is now?
_New World Order (NWO)_
Click to expand...
Click to collapse
It shows in fastboot that the phone is unlocked with frp locked. Unlocking it again through fastboot is not possible since I always get an error saying remote command not allowed.

NikkoVicedo said:
It shows in fastboot that the phone is unlocked with frp locked. Unlocking it again through fastboot is not possible since I always get an error saying remote command not allowed.
Click to expand...
Click to collapse
Hi guys, i Got the SAAAAAME Problem, this is all about what i PMd to you danerrickcuba FRP lock and bootloader unlocked. can't go to recovery, but has access to fastboot and wasn't able to do anything to fastboot.

Already fixed my phone. Had to pay 15 euros for DC Phoenix (this software saved me from bringing my phone to huawei service center to have it fix. Thank god!) so I can fix my phone. Recovery, eRecovery, Dload method working, and relocked bootloader. Currently updating my phone through OTA. Tnx danerrickcuba for suggesting methods to fix my phone....

NikkoVicedo said:
It shows in fastboot that the phone is unlocked with frp locked. Unlocking it again through fastboot is not possible since I always get an error saying remote command not allowed.
Click to expand...
Click to collapse
i have the same problem
bootloader unlock and frp lock ,bootlooping,rec&e-rec destoryed
if you do not log out google /shut down "find my phone"/check oem-unlock in developer mode before downgrading or flashing ,you will get "frp lock" warning
bootlooping may come from wrong update.app. eg. i use dload method to flash rollback(5.0-B300) pkg in EMUI4.1 , my rec and e-rec are destoryed
however, i think fastboot command could do nothing to "bootloader unlock ,frp lock,rec and e-rec destoryed ". i do not know how DC-phoenix fix this and i pay a new motherboard for my mistake

try https://forum.xda-developers.com/showpost.php?p=71338813&postcount=29

Help! Nexus 6p is boot looped !

I`ve decided to return to stock and I wish I didn`t!
After flashing the files for the latest stock image , I was unable to pass the boot animation.
That was six hours ago.
I tried to reinstall another full image from google website.
I did and then my computer doesn`t recognize my device on adb mode.
Tried to update the drivers via Android Studio and through the usb drivers folder , it gives an error of not being able to download the update because of disabling the automatic windows update even though I did.
Help, people what can I do?
Should I just get a new phone?
It`s a very tough option for me right now due to some financial issues.
:crying::crying::crying:

I have also unlocked the bootloader afterwards.
That was such a stupid move!

Sulieman 91 said:
I have also unlocked the bootloader afterwards.
That was such a stupid move!
Click to expand...
Click to collapse
Hi... Explain how exactly you flashed your phone. Fastboot? Adb sideload?
What was your android version prior to your problem.
What version did you try to flash? Did you use the flash all.bat/sh? Or flashed each image manually?
Are you stuck in bootloader? Can you still access recovery? Or does it bootloop when trying to reboot into recovery?

Sulieman 91 said:
I have also unlocked the bootloader afterwards. That was such a stupid move!
Click to expand...
Click to collapse
No, unlocking the bootloader may make the difference in being able to recover your phone. Did you also enable USB debugging in Developer Options when you unlocked your bootloader? Was ADB working before and now has stopped working? I would first focus on getting ADB/fastboot binaries (and USB drivers) set up and working properly on your PC.

5.1 said:
Hi... Explain how exactly you flashed your phone. Fastboot? Adb sideload?
What was your android version prior to your problem.
What version did you try to flash? Did you use the flash all.bat/sh? Or flashed each image manually?
Are you stuck in bootloader? Can you still access recovery? Or does it bootloop when trying to reboot into recovery?
Click to expand...
Click to collapse
I flashed the latest version of Android 7.1.1 with March update
I flashed each image manaually
Not stuck on boot loader but stuck on the animation of booting without accessing anything on the phone so it`s a bootloop.
I flashed stock all and unlocked the bootloader afterwards....... Trying to unlock it now with no hope of how to unlock it and flash anything and save myself from this problem!

v12xke said:
No, unlocking the bootloader may make the difference in being able to recover your phone. Did you also enable USB debugging in Developer Options when you unlocked your bootloader? Was ADB working before and now has stopped working? I would first focus on getting ADB/fastboot binaries (and USB drivers) set up and working properly on your PC.
Click to expand...
Click to collapse
Please tell me that there is a way to unlock the bootloader without enabling usb debugging :\
This is gonna save my butt from a lot of trouble!

Sulieman 91 said:
I have also unlocked the bootloader afterwards. That was such a stupid move!
Click to expand...
Click to collapse
You said you UNLOCKED your bootloader, and that is what I responded to. Did you mean you LOCKED it?
Sulieman 91 said:
Please tell me that there is a way to unlock the bootloader without enabling usb debugging :\
This is gonna save my butt from a lot of trouble!
Click to expand...
Click to collapse
No you just need fastboot working to unlock (this is assuming you already had it unlocked before)... but again this depends on you having your PC set up correctly.
fastboot flashing unlock - try that and see if it finishes successfully or not.
Edit: That and try to answer @5.1 's questions

v12xke said:
You said you UNLOCKED your bootloader, and that is what I responded to. Did you mean you LOCKED it?
No you just need fastboot working to unlock (this is assuming you already had it unlocked before)... but again this depends on you having your PC set up correctly.
fastboot flashing unlock - try that and see if it finishes successfully or not.
Edit: That and try to answer @5.1 's questions
Click to expand...
Click to collapse
I unlocked it before but now did a full recovery to Stock and locked the bootloader.
I need to access the usb debugging option before I can type in that command in the CMD
My PC is set up correctly .
My only problem is that I don`t have access to my phone in order to enable that option and don`t know how to unlock the bootloader with any other way.
That is all

Sulieman 91 said:
I flashed the latest version of Android 7.1.1 with March update
I flashed each image manaually
Not stuck on boot loader but stuck on the animation of booting without accessing anything on the phone so it`s a bootloop.
I flashed stock all and unlocked the bootloader afterwards....... Trying to unlock it now with no hope of how to unlock it and flash anything and save myself from this problem!
Click to expand...
Click to collapse
Not answering what I asked, doesn't help me to help you...

5.1 said:
Not answering what I asked, doesn't help me to help you...
Click to expand...
Click to collapse
I flashed my phone using fastboot
after that unlocked the boot loader
and then I tried to boot the phone normally.
I couldn`t and it stuck on the boot animation for over 6 hours now.

Hi... Explain how exactly you flashed your phone. Fastboot? Adb sideload?
Fastboot
What was your android version prior to your problem.
7.1.1
What version did you try to flash? Did you use the flash all.bat/sh? Or flashed each image manually?
The same version again after flashing a pure nexus rom , flashed each image manually
Are you stuck in bootloader? Can you still access recovery? Or does it bootloop when trying to reboot into recovery?
not stuck on bootloader , still have access to the recovery mode (stock one not TWRP) it bootloops only when I try to turn on the phone.

5.1 said:
Hi... Explain how exactly you flashed your phone. Fastboot? Adb sideload?
Fastboot
What was your android version prior to your problem.
7.1.1 Pure Nexus Rom
What version did you try to flash? Did you use the flash all.bat/sh? Or flashed each image manually?
7.1.1 with March Update , each image manually
Are you stuck in bootloader? Can you still access recovery? Or does it bootloop when trying to reboot into recovery?
Click to expand...
Click to collapse
stuck in boot animation , have access to bootloader & recovery both in stock with no TWRP or Unlocked bootloader

Sulieman 91 said:
I flashed my phone using fastboot
after that unlocked the boot loader
and then I tried to boot the phone normally.
I couldn`t and it stuck on the boot animation for over 6 hours now.
Click to expand...
Click to collapse
Yet you didn't answer the last question...
Do you still have access to recovery?
Try this just in case:
fastboot erase cache
fastboot format userdata
---------- Post added at 07:56 PM ---------- Previous post was at 07:54 PM ----------
Sulieman 91 said:
stuck in boot animation , have access to bootloader & recovery both in stock with no TWRP or Unlocked bootloader
Click to expand...
Click to collapse
Well... Enter recovery and try a factory reset...
Though I find it really strange that your bootloader was unlocked and now... Locked?

5.1 said:
Yet you didn't answer the last question...
Do you still have access to recovery?
Try this just in case:
fastboot erase cache
fastboot format userdata
Click to expand...
Click to collapse
Stock recovery only without any ability to edit or fix anything because of flashing stock android
....... I can`t fix anything from the boot loader as it is locked and need a way to unlock it without the usb debugging that I have no access to.

5.1 said:
Yet you didn't answer the last question...
Do you still have access to recovery?
Try this just in case:
fastboot erase cache
fastboot format userdata
---------- Post added at 07:56 PM ---------- Previous post was at 07:54 PM ----------
Well... Enter recovery and try a factory reset...
Though I find it really strange that your bootloader was unlocked and now... Locked?
Click to expand...
Click to collapse
I locked the bootloader after flashing the system image to return fully to stock but now I realize I`ve blocked myself from even accessing the phone in case such a situation takes place

Sulieman 91 said:
Stock recovery only without any ability to edit or fix anything because of flashing stock android
....... I can`t fix anything from the boot loader as it is locked and need a way to unlock it without the usb debugging that I have no access to.
Click to expand...
Click to collapse
Recovery > wipe data/factory reset
Doesn't work?

5.1 said:
Recovery > wipe data/factory reset
Doesn't work?
Click to expand...
Click to collapse
I just did that and will wait for 4 to 5 minutes to check whether it worked or not.
Stand by

Sulieman 91 said:
I just did that and will wait for 4 to 5 minutes to check whether it worked or not.
Stand by
Click to expand...
Click to collapse
Sure... Good luck...

5.1 said:
Sure... Good luck...
Click to expand...
Click to collapse
Still with the same problem ........ I don`t know what to do , brother !

Sulieman 91 said:
Still with the same problem ........ I don`t know what to do , brother !
Click to expand...
Click to collapse
Neither do I...
What version are you on? 7.1.1?
Try sideloading the beta 7.1.2 ota. You can find it on the N6P general section I think.
I'm not saying it will solve your problem. If factory reset didn't fix your bootloop, I don't know what else to do... Good luck!

How to Stock FW and Relock Bootloader? OP5

Hi all,
I've wanted to go back to Stock OS but when i type "fastboot oem lock" it says "FAILED <remote: Flashing Lock is not allowed."
Everything boots normally to OS 4.5.2. In DEV options the Unlock Bootloader is greyed out and says bootloader is already unlocked.
What can i do?
Cheers

These instructions did work for me with the OnePlus 3/3T. They should also work for the OnePlus5, just make sure that you download the OnePlus5 version of the software and recovery.
https://forums.oneplus.net/threads/...-3-3t-and-go-back-completely-to-stock.456232/
Use this link for the stock recovery: https://forum.xda-developers.com/showpost.php?p=72748921&postcount=5

reayard said:
These instructions did work for me with the OnePlus 3/3T. They should also work for the OnePlus5, just make sure that you download the OnePlus5 version of the software and recovery.
https://forums.oneplus.net/threads/...-3-3t-and-go-back-completely-to-stock.456232/
Use this link for the stock recovery: https://forum.xda-developers.com/showpost.php?p=72748921&postcount=5
Click to expand...
Click to collapse
Hi i tried but does the same when i get to fastboot oem lock (it says Flashing Lock is not allowed).

r1card0amr said:
Hi i tried but does the same when i get to fastboot oem lock (it says Flashing Lock is not allowed).
Click to expand...
Click to collapse
Thanks I asked the same question earlier glad u tried it..I want to make sure we can relock it before I get the phone. Did u enable oem unlocking in the developer options before doing a fastboot oem lock? Also, make sure you are on stock everything including recovery..

mohan_kr said:
Thanks I asked the same question earlier glad u tried it..I want to make sure we can relock it before I get the phone. Did u enable oem unlocking in the developer options before doing a fastboot oem lock? Also, make sure you are on stock everything including recovery..
Click to expand...
Click to collapse
Hello. I first thing I do always is to install drivers. I start by connecting the phone to the laptop in charge mode, then in transfer files mode, MTP or camera. In this way he will recognise all the drivers your laptop needs.
Also I enter in fastboot mode and recovery so the laptop can recognise the drivers and always reboot laptop and phone just to double check.
What I did was: go to Developer Options and enabled Unlock Bootloader and USB Debugging.
Then I accepted the laptop request on my phone and all drives were OK.
I run CMD and typed fastboot devices to see if it recognises my phone and it displayed a serial number. So I proceed next to type fastboot oem unlock and the process went OK and on my phone it asked Yes or No to unlock and I choose yes.
Then I flash a twrp image by typing on CMD: fastboot flash recovery recovery.img (my twrp I'm had other name so I rename it. You need to enable "Show file extensions" in Windows so you can see what the extension is).
I then type fastboot boot recovery.img and the phone entered in Recovery Mode in this case TWRP.
My phone was always connected to the laptop and he open the internal storage window so I drag the supersu inside.
Then on TWRP I wiped dalvik and cache and I went to Install and installed the SupeSU on my internal memory root.
The phone then rebooted and ready to go.
But then I went to developer options and the Unlock bootloader was greyed out. I unroot my phone and flashed a stock recovery for OP5 and the stock image 4.5.2 and when I type fastboot oem lock it always says it can't be flashed.
I need to stock it since I'm giving to a family member and they don't understand much about phones and If there's a problem the warranty doesn't cover.
Just installed supersu to try an app. I never install 3rd party roms.

r1card0amr said:
I need to stock it since I'm giving to a family member and they don't understand much about phones and If there's a problem the warranty doesn't cover.
Click to expand...
Click to collapse
the warranty is not voided with unlocked bootloader..
https://oneplus.net/hk/support/answer/will-rooting-or-unlocking-the-bootloader-void-my-warranty

I found now that if i take pictures or screenshots the Album Folder is empty. I think my phone is bricked. Hence i can't lock the bootloader.

r1card0amr said:
I found now that if i take pictures or screenshots the Album Folder is empty. I think my phone is bricked. Hence i can't lock the bootloader.
Click to expand...
Click to collapse
if your phones boots its not bricked... My guess is that you data is corrupted, i would wipe everything including userdata en reflashing the stock with recovery.

Hogyoku said:
if your phones boots its not bricked... My guess is that you data is corrupted, i would wipe everything including userdata en reflashing the stock with recovery.
Click to expand...
Click to collapse
Hi right before your comment i managed lol.
I re-flash the stock recovery and in recovery i reset and wipe everything. then i install the OS4.5.3 by ADB Sideload and it's working now.
Just wanted to get rid of the inital warning that my bootloader is unlocked. I want to lock again.

I rooted my device with Magisk, and now I want to restore it to factory state.
I flashed stock recovery and OOS several times, wiped everything but fastboot oem lock failed all times (FAILED (remote: Flashing Lock is not allowed)).
Can you help me?
What should I do to relock bootloader?

here is your solution
r1card0amr said:
Hi right before your comment i managed lol.
I re-flash the stock recovery and in recovery i reset and wipe everything. then i install the OS4.5.3 by ADB Sideload and it's working now.
Just wanted to get rid of the inital warning that my bootloader is unlocked. I want to lock again.
Click to expand...
Click to collapse
here in this video u can see in detail how to lock bootloader. hope this help you
https://www.youtube.com/watch?v=CQYCSdDUdAU

HOW TO RELOCK..
Install TWRP and Magisk if you don't have them yet.
Magisk should allow you to slide "OEM unlocking" to "enabled"
Reboot to fastboot
Flash stock recovery via fastboot.
Run locking via fastboot flashing lock
Allow it to reboot and upon start up it will say device corrupted (THIS IS NORMAL)
Boot to recovery via the warning start screen.
Once in recovery, sideload latest FW.
Profit.

I usually do it this way (successfully):
Wipe everything but OTG in TWRP
Format data
Reboot to TWRP
Flash the full stock OOS zip
Reboot to fastboot
Flash stock recovery
Lock bootloader with the fastboot lock command

Has anyone made any progress with this? I too am having the issue as described and have tried the solution by Ricyksydhu, along with solutions from various other places around the net.

Bootloop and locked bootloader

Hello guys, I have a problem. I updated my Mi A1 and now I am in bootloop. I can't use MiFlash because I have locked bootloader.
I have tried fastboot oem edl, adb sideload in recovery but it didnt help. Any solution?

bad luck !! Test point method is the only way ? i faced the same situation ... please don't go to the service centre , they will tell you that the motherboard of your device needs a change .. and ask for a big amount of money if your phone is out of warranty ..!! search for the test point method here .. follow the video , and then follow the steps to go back to stock oreo from pie .. that's the only way ??

Same problem happened with me
My internal storage gets full and mobile automatically got switched off and bootloop
I tried to flash my self with adb command fastboot oem unlock
And successfully unlocked the bootloader & flashing process started but it keep flashing for long time whole night
So i decided to go near shop and gave him he tried with EDL test point and then phone goes in black screen He gave up :crying:
Now I'm thinking to go mi service centre but i get to know their ans is to change motherboard

PepeDaFrog said:
Hello guys, I have a problem. I updated my Mi A1 and now I am in bootloop. I can't use MiFlash because I have locked bootloader.
I have tried fastboot oem edl, adb sideload in recovery but it didnt help. Any solution?
Click to expand...
Click to collapse
What did u update? Stock rom? When did you buy the device? Can you get into fastboot? Can you get into recovery?

i just flashed the device for my wife with stock fastboot and locked the bootloader and of course it ends in bootloop.
i removed sim and micro sd and it boots up.

cheffy11 said:
What did u update? Stock rom? When did you buy the device? Can you get into fastboot? Can you get into recovery?
Click to expand...
Click to collapse
I have downgraded from pie to 8.1 oreo. Yes, i can get into fastboot and recovery but cant unlock the bootloader.

PepeDaFrog said:
I have downgraded from pie to 8.1 oreo. Yes, i can get into fastboot and recovery but cant unlock the bootloader.
Click to expand...
Click to collapse
did you try fastboot oem unlock?

Gamestrav said:
did you try fastboot oem unlock?
Click to expand...
Click to collapse
Yes, I have. I didnt work because I have OEM Unlock disabled and cant get into system.

PepeDaFrog said:
Yes, I have. I didnt work because I have OEM Unlock disabled and cant get into system.
Click to expand...
Click to collapse
What recovery do u have?

PepeDaFrog said:
I have downgraded from pie to 8.1 oreo. Yes, i can get into fastboot and recovery but cant unlock the bootloader.
Click to expand...
Click to collapse
You messed up because from stock Pie onwards, Xiaomi has implemented ARB which will bootloop your phone if you downgrade your rom.

barrack1 said:
You messed up because from stock Pie onwards, Xiaomi has implemented ARB which will bootloop your phone if you downgrade your rom.
Click to expand...
Click to collapse
Hi! Does testpoint method works here?

I'll try with a home made EDL cable, if this does not work I'll have to drive to the office for tools and try the test point. I'll update, but if anyone knows if this or that works and see this post on time, let me know!

UPDATE:
- EDL cable didn't work.
- Test point method worked fine, I thought that opening this phone would be harder, search for dissasembly tutorials on youtube and for test point method, the brick got back to life and it's fully working!