Develop Bugs

Cannot boot into bootloader/fastboot

Hello guys I have H815 and I can't proceed with unlocking bootloader cause my phone cannot boot into bootloader/fastboot mode. I'm not newbie, but with this phone everything goes ****ing different than in instruction.
I the instruction there is adb reboot bootloader. Of course my phone is seen in adb mode but after this command it just reboot to system. I tried also key combinations with no luck...
What to do?
My system is android 6

remialfa said:
Hello guys I have H815 and I can't proceed with unlocking bootloader cause my phone cannot boot into bootloader/fastboot mode. I'm not newbie, but with this phone everything goes ****ing different than in instruction.
I the instruction there is adb reboot bootloader. Of course my phone is seen in adb mode but after this command it just reboot to system. I tried also key combinations with no luck...
What to do?
My system is android 6
Click to expand...
Click to collapse
Hi,
I'm the same...
looking for solution I found this on Youtube:
Pratically, you have to press vol up while connect USB on PC....
I haven't the G4 with my today and so I cannot test if this is a valid mode...
If you do this, let me know if you can enter in fastboot mode

auceto63 said:
Hi,
I'm the same...
looking for solution I found this on Youtube:
Pratically, you have to press vol up while connect USB on PC....
I haven't the G4 with my today and so I cannot test if this is a valid mode...
If you do this, let me know if you can enter in fastboot mode
Click to expand...
Click to collapse
I did that and yeah it entered this mode but it's not valid bootloader/fastboot mode. It's some service mode to update firmware. Anyway it's not visible in pc as a normal fastboot and I cannot proceed further with unlocking bootloader...
Edit: it's download mode... So as I said it's not fastboot mode.
Anyone can help?

Seriously nobody? I thought this phone has good community and support...

I'm facing the exact same problem with my H810 on 6.0. Sick of not being able to root atleast.
Seriously hasn't anyone on earth found a way to boot this **** in fastboot? I mean there are a number of tutorials but everything goes different as F*** with this thing. Hope someone will update with good news. :fingers-crossed::fingers-crossed:

charith262 said:
I'm facing the exact same problem with my H810 on 6.0. Sick of not being able to root atleast.
Seriously hasn't anyone on earth found a way to boot this **** in fastboot? I mean there are a number of tutorials but everything goes different as F*** with this thing. Hope someone will update with good news. :fingers-crossed::fingers-crossed:
Click to expand...
Click to collapse
You can check out UsU. That is an unofficial bootloader unlock

ThePiGuy said:
You can check out UsU. That is an unofficial bootloader unlock
Click to expand...
Click to collapse
Thanks yeah I checked but that's for ARB<=2 devices. I forgot to mention earlier this godforsaken thing is ARB3.

I have an H811 (T-Mo) running firmware H81120p, ARB3. Doesn't seem to be much that can be done with it as far as rooting. It also has no stock recovery, only boots to system.

you did follow this official guide right? it unlocked mine after a few angry moments
http://developer.lge.com/resource/mobile/RetrieveBootloader.dev
use minimal ADB https://forum.xda-developers.com/showthread.php?t=2317790
Only way to boot twrp later is to use fastboot with ADB, recovery with buttons doesn't work.
if the device wont boot a rom use adb to get back in recovery.
if you use bank apps, install magisk before installing rom, do not get SU

samadee3 said:
you did follow this official guide right? it unlocked mine after a few angry moments
http://developer.lge.com/resource/mobile/RetrieveBootloader.dev
use minimal ADB https://forum.xda-developers.com/showthread.php?t=2317790
Only way to boot twrp later is to use fastboot with ADB, recovery with buttons doesn't work.
if the device wont boot a rom use adb to get back in recovery.
Click to expand...
Click to collapse
Only problem is that the info linked to above applies to ONE G4 variant only - the H815 international model. The rest of us are SOL. The bootloader on US carrier G4 - AT&T, T-Mo, VzW, etc (most later firmware revisions for G3 as well) models has been nailed down. The only exception is a G4 with ARB <= 2 can be hacked with UsU in order to root it and install a custom recovery.

SofaSpud said:
Only problem is that the info linked to above applies to ONE G4 variant only - the H815 international model. The rest of us are SOL. The bootloader on US carrier G4 - AT&T, T-Mo, VzW, etc (most later firmware revisions for G3 as well) models has been nailed down. The only exception is a G4 with ARB <= 2 can be hacked with UsU in order to root it and install a custom recovery.
Click to expand...
Click to collapse
Tmo is very easy
Go to dev options and enable adb
Then run "adb reboot bootloader"
Once there, run "fastboot oem unlock" and voila, you have an officially unlocked bootloader with no restrictions related to UsU
Please be aware the above will factory reset your device

ThePiGuy said:
Tmo is very easy
Go to dev options and enable adb
Then run "adb reboot bootloader"
Once there, run "fastboot oem unlock" and voila, you have an officially unlocked bootloader with no restrictions related to UsU
Please be aware the above will factory reset your device
Click to expand...
Click to collapse
Do you know anyone who has done it with H81120o or later? I've seen posts for two yrs about doing it that way, but I don't remember reading about it being done on 20o or later.
Sent from my SAMSUNG-SM-G935A using Tapatalk

SofaSpud said:
Do you know anyone who has done it with H81120o or later? I've seen posts for two yrs about doing it that way, but I don't remember reading about it being done on 20o or later.
Click to expand...
Click to collapse
Why v20o
Remember, this has nothing to do with UsU and therefore ARB etc doesn't matter
Edit: ps there are loads of H811 users in my Lineage thread and the other ROMs too

ThePiGuy said:
Why v20o
Remember, this has nothing to do with UsU and therefore ARB etc doesn't matter
Edit: ps there are loads of H811 users in my Lineage thread and the other ROMs too
Click to expand...
Click to collapse
Got it. Guess that it makes sense. ARB prevents rolling back to earlier release than 20o, I'm ok. Will try the BL unlock today then.
Sent from my SAMSUNG-SM-G935A using Tapatalk

I actually managed to get my LG V20 F800L into same situation after messing up my rooting process.
First i was stuck at logo and factory reset did nothing. Bootloader was working then.
Then i downloaded new firmware through "Download Mode", and after that i lost access to bootloader.
I know the phone model is different, but process seems to be very similar for all LG devices.
Trying to troubleshoot that atm, if i'll have results i'll post them here.
P.S. I know original poster long left (probably after throwing phone into a grinder), but maybe for someone with same problem as us in the future the info will be useful.

Florimer said:
I actually managed to get my LG V20 F800L into same situation after messing up my rooting process.
First i was stuck at logo and factory reset did nothing. Bootloader was working then.
Then i downloaded new firmware through "Download Mode", and after that i lost access to bootloader.
I know the phone model is different, but process seems to be very similar for all LG devices.
Trying to troubleshoot that atm, if i'll have results i'll post them here.
P.S. I know original poster long left (probably after throwing phone into a grinder), but maybe for someone with same problem as us in the future the info will be useful.
Click to expand...
Click to collapse
Ok, now i have to reply to my own post, since i believe i understand now something important:
LG phones usually dont have bootloader open to access. Until you use some exploits to do so.
I did not know that at the time of writing that reply.

Florimer said:
Ok, now i have to reply to my own post, since i believe i understand now something important:
LG phones usually dont have bootloader open to access. Until you use some exploits to do so.
I did not know that at the time of writing that reply.
Click to expand...
Click to collapse
Do you have more details about this? I seem to be in a similar situation than you and I'm struggling to make it work.

sofrbrick/bootloop

Hi all,
I am new to this forum, but have some experience with rooting and custom roms(oneplus one and samsung)
Now with the Mi Max 3, which was unlocked, i have flashed the recovery twrp-3.2.3-0-nitrogen.img, but I did not realize that
i had to reboot into this recovery from the fastboot mode.
so I endet up with a locked bootloader and bottloop and am not able to unlock the bootloader again.
I think my only solution is the test-point method and a EDL authorized account.
Some help would be greatly appreciated.
thanks
Henry

You don't have to boot into the bootloader from fastboot mode, you can press the power button and volume up button like on almost all other Android phones to boot into TWRP recovery. Sometimes it takes a few attempts to get right, but you should learn how to do it eventually.
Unfortunately it sounds like you had one of the dodgy re-sold Chinese models that had been re-flashed with Global firmware and it's locked your bootloader again on reboot.
Your only option is to use the official Miui Flash tool to boot into fastboot mode, flash the latest Global Developer ROM, and then sign in with your account and apply to unlock the bootloader again using the Miui unlock program. It may be instant but, they'll probably make you wait 720 hours, as the entire point of the program was to stop phones like yours being re-sold outside China.
At least you'll have a usable, non-bricked device though.

Thanks for your answer.
now I have opened the backcover (yes was much work ( I succeded without destroying something) and could apply the test point method to get into the lde mode.
Win10 shows it as qualcomxx at com 3
what is the best way now to awake it to life again? even without unlocking.

hi,
with the test point method I could flash the chinese rom, and the mi max 3 is awaken to life again!
The bootloader is still locked.
I have applied for unlocking, but have to wait some 15 days.
One tip: if the case is open, one can apply a little bit of silicon grease to the small pins on the side of the plastic frame
before closing it. Opening it again is much easier then.
One question: if I replace the recovery.img of the chinese rom with a TWRP image (renamed to recovery.img)
and flash that modified rom with the test point method, could this probaly work?
With a working TWRP one could install other roms without unlocking bootloader.
If yes, which TWRP would you apply?
Thanks

freedoc said:
Hi all,
I am new to this forum, but have some experience with rooting and custom roms(oneplus one and samsung)
Now with the Mi Max 3, which was unlocked, i have flashed the recovery twrp-3.2.3-0-nitrogen.img, but I did not realize that
i had to reboot into this recovery from the fastboot mode.
so I endet up with a locked bootloader and bottloop and am not able to unlock the bootloader again.
I think my only solution is the test-point method and a EDL authorized account.
Some help would be greatly appreciated.
thanks
Henry
Click to expand...
Click to collapse
Flashing a recovery should not lock your bootloader, so I don't know how you did it. Note, that if you are using Xiaomi's firmware tool, you should not forget about unticking the box to lock the bootloader. But I would suggest to stay away from that tool and go command line instead with fastboot.
If you can access fastboot, I'd recommend to flash an official fastboot tgz ROM of your choice. Official ROM should boot even with an unlocked bootloader and you may start all over again more carefully.
So I think you might be able to avoid using EDL mode at this stage.

probally I forgot to untick that box. The bootloader is locked and I have to wait 319 hours.
I have got to love the test point EDL method which is simple and effective, and gave me control over the device again.
If I flash again the chinese fastboot rom (in which I have changed the original recovery.img into TWRP.img, named recovery.img) via the EDL
will that give me an installt TWRP (still with locked bootloader, but possible to install custom roms) or will i have a brick again?
thanks

freedoc said:
probally I forgot to untick that box. The bootloader is locked and I have to wait 319 hours.
I have got to love the test point EDL method which is simple and effective, and gave me control over the device again.
If I flash again the chinese fastboot rom (in which I have changed the original recovery.img into TWRP.img, named recovery.img) via the EDL
will that give me an installt TWRP (still with locked bootloader, but possible to install custom roms) or will i have a brick again?
thanks
Click to expand...
Click to collapse
Only you can answer that question by trying it out. Are you sure you have to wait for the unlocking again? Double check that! As I know you also need a priviliged xiaomi account to be able to resurrect a device in EDL mode.

OEM Locked, and Device is corrupt. Unfixable?

So, long story short I recently decided to try and root my oneplus7t I unfortunately made some mistakes and somehow corrupted some files. I read elsewhere in the forum that I could download the stock rom which I did and then use flash-all and that would allow me to go back to the factory settings so I could lock the oem and just go back to normal because I was tired of the headache. Unfortunately, after using flash-all I locked the oem thinking everything should be stock and it would work properly. But it says device is corrupt and trying to unlock the oem says oem unlocking is disabled.
So did I just completely brick my phone? I don't know of anyway to fix it at this point :/.

kschmitz4 said:
So, long story short I recently decided to try and root my oneplus7t I unfortunately made some mistakes and somehow corrupted some files. I read elsewhere in the forum that I could download the stock rom which I did and then use flash-all and that would allow me to go back to the factory settings so I could lock the oem and just go back to normal because I was tired of the headache. Unfortunately, after using flash-all I locked the oem thinking everything should be stock and it would work properly. But it says device is corrupt and trying to unlock the oem says oem unlocking is disabled.
So did I just completely brick my phone? I don't know of anyway to fix it at this point :/.
Click to expand...
Click to collapse
Can you still boot into bootloader via the hardware keys, whatever that combo is on the 7t?
Boot to bootloader or recovery and factory reset it or so.

Josh McGrath said:
Can you still boot into bootloader via the hardware keys, whatever that combo is on the 7t?
Boot to bootloader or recovery and factory reset it or so.
Click to expand...
Click to collapse
I can get to the bootloader but it's Device State -locked and when I tell it to boot into recovery it says the device is corrupt. When I use fastboot to oem unlock it says I cannot, and I can't flash when oem is locked either.

kschmitz4 said:
I can get to the bootloader but it's Device State -locked and when I tell it to boot into recovery it says the device is corrupt. When I use fastboot to oem unlock it says I cannot, and I can't flash when oem is locked either.
Click to expand...
Click to collapse
Try
fastboot erase userdata and
Fastboot erase cache
Let me know if that works or not we will move on. Probably won't work since it's bootloader locked
You may have to contact OP and while you're at it, get the MSM tool for us all :good:

It says erase is not allowed in locked state . I think this is probably all she wrote for this one. I think I'm just going to send it back tbh, the whole reason I was trying to root it was because it didn't work with Sprint like they said it would. and I was wondering if I could find a way too make it work with custom software. Thanks for trying

Are you able to flash one of these Fastboot ROMs?

Maybe Sideload can work!
https://support.oneplus.com/app/answers/detail/a_id/4583/kw/7t here is official stock file.
https://forums.oneplus.com/threads/how-to-do-flash-through-adb-sideload.509377/
https://www.the***********.com/sideload-ota-update-stock-recovery-adb/
Please refer above links for your knowledge purpose maybe it can help.....

I unfortunately no longer have Twrp installed as I did a flash-all with a stock rom already . If I try and flash recovery it says "flashing is not alllowed in lock state". Sideloading wasn't functional back when I had twrp either as the functionality for it is still in progress. I'll probably try contacting support one more time and see if I can get a T2 who can unbrick it, otherwise I'm just going to send it back. Thanks for the attempts guys!
Edit: As to the flashboot roms I flash-all'ed one of them and that's how I got into this mess :/.

kschmitz4 said:
I unfortunately no longer have Twrp installed as I did a flash-all with a stock rom already . If I try and flash recovery it says "flashing is not alllowed in lock state". Sideloading wasn't functional back when I had twrp either as the functionality for it is still in progress. I'll probably try contacting support one more time and see if I can get a T2 who can unbrick it, otherwise I'm just going to send it back. Thanks for the attempts guys!
Edit: As to the flashboot roms I flash-all'ed one of them and that's how I got into this mess :/.
Click to expand...
Click to collapse
I ended up needing to flash the fastboot 10.0.3 firmware and was able to do a local upgrade to 10.0.4 that way, then flashing a patched boot.img via fastboot

I can't run any flash commands as my oem is locked. I don't suppose there's anyway around that?

kschmitz4 said:
I can't run any flash commands as my oem is locked. I don't suppose there's anyway around that?
Click to expand...
Click to collapse
How did you flash twrp with it oem locked??That doesnt make sense

I had twrp on it when the oem was unlocked, I was trying to reset the device to stock, so I did a flash-all and then oem locked it. But for some reason the repair was unsuccessful, and now it says my device is corrupted and I forgot to turn on oem unlocking in the settings on my phone after the flash-all before I did the oem-lock.

kschmitz4 said:
I had twrp on it when the oem was unlocked, I was trying to reset the device to stock, so I did a flash-all and then oem locked it. But for some reason the repair was unsuccessful, and now it says my device is corrupted and I forgot to turn on oem unlocking in the settings on my phone after the flash-all before I did the oem-lock.
Click to expand...
Click to collapse
You should have no issues reflashing the stock images

I cannot flash anything. Because my OEM state is locked.

Boot to Stock Recovery ?
Holding for a long time Volume Down + Power Buttons while booting your phone ?

Volume down plus power button takes me to "Your device is corrupt and will not boot"

kschmitz4 said:
Volume down plus power button takes me to "Your device is corrupt and will not boot"
Click to expand...
Click to collapse
Looks like you will need the MSM tool to fix this issue. You'll have to contact OP support and they will remote in your PC, load their software and flash it 100pct back to stock.
Also, disconnect them before they can delete the MSM tool so we can have it here in the community

kschmitz4 said:
Volume down plus power button takes me to "Your device is corrupt and will not boot"
Click to expand...
Click to collapse
Press volume up/down and power, reboot to fastboot. Unlock bootloader again. Install update from settings, reboot and install it again. (local install)
Factory reset in setting, reboot fastboot, lock bootloader. Reboot and untick unlock bootloader in developer settings.

Don't know if it's too late but I believe there's a working MSM tool now

System Update Failed? Here is Possible Fix

This Is For those Who Stuck At Android 9 In WW Roms With ZS660KL Model
This Method Will Use Raw Firmware so there is risks if you do something wrong and maybe data loss so always backup​Bootloader Must Be Unlocked
How To Flash Raw Rom:​1-Bootloader Must be Unlocked! (To change fingerprint to ww and relock the bootloader to get OTA) If you are already on WW fingerprint this step aint needed or you want to stay on cn fingerprint just skip)
2-Install adb and fastboot
3-Download and extract the raw version you want i will give some below
4- reboot the phone to fastboot mode and connect it to the pc Use Side Port
5-in the raw firmware folder double click flashall_AFT.cmd This will take sometime and no progress will be shown so all you have to do is to wait till the phone reboot or get black screen if you got black screen just hold vol down and power button for some seconds
6-if your Fingerprint is cn Change it to WW With root explorer you can find posta about this step by step (skip this if you are already on WW Fingerprint)
Downloads:
Android 10:
https://drive.google.com/file/d/1NQI7SyCfPkBA15dVAim2yhEWD_6p0Kta/view
Android 9:
https://drive.google.com/file/d/16uIlYvFuXDEoRmtosqUwgVgM7aMdhaOp/view
Credits:
the custom droid site for the raw Firmwares
Some info:
After this method You will get ota updates if you relock bootloader
or you can install update zips from asus if you want to keep bootloader unlocked :silly:

You don't need to unlock the bootloader to flash the raw firmware. That is stupid to say you do..

joluke said:
You don't need to unlock the bootloader to flash the raw firmware. That is stupid to say you do..
Click to expand...
Click to collapse
The way you say stupid is stupid however mine didn't got flashed just rebooted when tried to flash the raw and couldn't update in system updates or zip files however having some respect ain't bad for your health.

shahram Ali said:
The way you say stupid is stupid however mine didn't got flashed just rebooted when tried to flash the raw and couldn't update in system updates or zip files however having some respect ain't bad for your health.
Click to expand...
Click to collapse
First of all, I just said it was a stupid thing to say because you don't need to unlock the bootloader and you must use the side USB c port to flash via fastboot. Second: learn to interpret proper English because I didn't offend anyone. End of conversation

joluke said:
First of all, I just said it was a stupid thing to say because you don't need to unlock the bootloader and you must use the side USB c port to flash via fastboot. Second: learn to interpret proper English because I didn't offend anyone. End of conversation
Click to expand...
Click to collapse
I mentioned the side port i don't write a paragraph about the phone as homework short and easy fix is the point there is nothing missing in the post so your reply wasn't necessary mate keep it cool :good:

How do I lock the bootloader after this?
I have some apps that wont work, whit the message "This app is not supported in rooted devices, please restore your device"
Thanks

Ricardo55467 said:
How do I lock the bootloader after this?
I have some apps that wont work, whit the message "This app is not supported in rooted devices, please restore your device"
Thanks
Click to expand...
Click to collapse
You will need to enter an command in fastboot mode but be aware backup every necessary things
If you didn't rooted or touched boot.img just use this command in fastboot and the bootloader will be locked again
fastboot oem asus-csc_lk

shahram Ali said:
You will need to enter an command in fastboot mode but be aware backup every necessary things
If you didn't rooted or touched boot.img just use this command in fastboot and the bootloader will be locked again
fastboot oem asus-csc_lk
Click to expand...
Click to collapse
What if I rooted?
I just followed all the instructions, I dont think I need my phone to be rooted, I dont want it to be rooted. gpay and some banking apps dont work.
I would like to get back to normal though and locked the boot loader, but keep my android 10 update.
I did all this just to update .

Ricardo55467 said:
What if I rooted?
I just followed all the instructions, I dont think I need my phone to be rooted, I dont want it to be rooted. gpay and some banking apps dont work.
I would like to get back to normal though and locked the boot loader, but keep my android 10 update.
I did all this just to update .
Click to expand...
Click to collapse
You'll need to flash stock boot img if your rom version (to remove root) before locking bootloader

Ricardo55467 said:
What if I rooted?
I just followed all the instructions, I dont think I need my phone to be rooted, I dont want it to be rooted. gpay and some banking apps dont work.
I would like to get back to normal though and locked the boot loader, but keep my android 10 update.
I did all this just to update .
Click to expand...
Click to collapse
Just reflash stock boot.img and you can use the command

Question Bootloop to fastboot logo and back in lock state

Hi everybody,
yesterday I tried flashing the stock pocof3 rom back onto my phone, but since it got stuck in a bootloop at the fastboot logo. Showing the poco logo for a milisecond and then straight to fastboot..
(before this I flashed twrp and the arrowOS recovery and images a few time trying, without succes, to install this rom)
Last thing I did was flash via the mi-flash tool and did't see the "clean and lock" selection so it's also in lock state again.
I cant get adb to find the phone although the mi-flashtool is finding it.
anyone any tips?
I tried the vol up power trick, but this didn't help, keeps loading into fastboot

Did Mi Flash give an error message after trying to flash?

dreamytom said:
Did Mi Flash give an error message after trying to flash?
Click to expand...
Click to collapse
I dont recall giving an error, so i dont think so
now it is though, when trying to flash the firmware. error erasing boot_ab (failed: erase not allowed in lock state)

Kaayman said:
I dont recall giving an error, so i dont think so
now it is though, when trying to flash the firmware. error erasing boot_ab (failed: erase not allowed in lock state)
Click to expand...
Click to collapse
I'm not sure, but you may still be able to flash official ROMs.
But in "Configuration" make sure Erase is disabled

Kaayman said:
I dont recall giving an error, so i dont think so
now it is though, when trying to flash the firmware. error erasing boot_ab (failed: erase not allowed in lock state)
Click to expand...
Click to collapse
BAD NEWS... your Poco is bricked. You cannot flash ANYTHING using a PC when your bootloader is locked.
(I did same thing on a Mi11 5g last week and ended up selling it on eBay for spare & repairs
I tried sideload flash, miflash, copying update.zip to internal storage via ADB, and many other options - all without success).
- if your POCO is under warranty in your country (i.e. not a chinese import)... contact Xiaomi Support they can re-flash correct ROM
- Ask your local phone repair store... they *might* be able to flash original ROM back by using "Chimera" engineering software.

dreamytom said:
I'm not sure, but you may still be able to flash official ROMs.
But in "Configuration" make sure Erase is disabled
Click to expand...
Click to collapse
this doesn't seem to be an option. there is a checkbox with "erase all" but all are already unchecked

dezborders said:
BAD NEWS... your Poco is bricked. You cannot flash ANYTHING using a PC when your bootloader is locked.
(I did same thing on a Mi11 5g last week and ended up selling it on eBay for spare & repairs
I tried sideload flash, miflash, copying update.zip to internal storage via ADB, and many other options - all without success).
- if your POCO is under warranty in your country (i.e. not a chinese import)... contact Xiaomi Support they can re-flash correct ROM
- Ask your local phone repair store... they *might* be able to flash original ROM back by using "Chimera" engineering software.
Click to expand...
Click to collapse
This is what I feared already..

Kaayman said:
This is what I feared already..
Click to expand...
Click to collapse
- Bootloader was re-locked whilst a custom ROM was in the phone.
(MIUI with Locked bootloader will not boot up where ROM is not stock or does not match the region/product code).
You cannot apply for bootoader unlock because you cannot boot up into Android and request the unlock via Developer mode.
You cannot remotely (via PC cable) flash any ROM into a Xiaomi / POCO phone whilst botloader is locked.
You are in a chicken and egg situation.,,, but if you find a way to repair your phone, please let us know how you achieved it.
Good luck!

If the system hasn't booted up yet there is a chance that you will be able to unlock bootloader again. Try it.

mar.ur said:
If the system hasn't booted up yet there is a chance that you will be able to unlock bootloader again. Try it.
Click to expand...
Click to collapse
That's what I'm thinking too ...
Connect the phone to pc and do the bootloader unlock again via the mi unlock app - you don't need to apply again and stuff as long as you're able to recognise the phone inside app correctly

Rstment ^m^ said:
That's what I'm thinking too ...
Connect the phone to pc and do the bootloader unlock again via the mi unlock app - you don't need to apply again and stuff as long as you're able to recognise the phone inside app correctly
Click to expand...
Click to collapse
thanks everyone for all the replies!
tried unlocking it via the mi unlock tool (latest) but it says (in chinese) its locked by nr 123***456 by searching the phone - can't unlock
edit:
google lens translates:
X The phone has been locked by the account number 661****647 by searching the phone, Can't unlock
but it's not the nr. of my account..

dezborders said:
- Bootloader was re-locked whilst a custom ROM was in the phone.
(MIUI with Locked bootloader will not boot up where ROM is not stock or does not match the region/product code).
You cannot apply for bootoader unlock because you cannot boot up into Android and request the unlock via Developer mode.
You cannot remotely (via PC cable) flash any ROM into a Xiaomi / POCO phone whilst botloader is locked.
You are in a chicken and egg situation.,,, but if you find a way to repair your phone, please let us know how you achieved it.
Good luck!
Click to expand...
Click to collapse
Is it not even possible to flash Official ROMs?
Isn't there like a system that it checks the signature of the ROM and if it's a signed ROM it allows the flash? Or am I mistaken?

dreamytom said:
Is it not even possible to flash Official ROMs?
Isn't there like a system that it checks the signature of the ROM and if it's a signed ROM it allows the flash? Or am I mistaken?
Click to expand...
Click to collapse
Nope bootload locked = no 'remote' flashes via pc
Apparently there is an 'authenticated user' mode for Xiaomi engineers in MiFlaah and also an EDL Emergency Download Mode which you can trigger by shorting out 2 pins on the motherboard so bypass bootloader lock and flash any ROM
Neither were available options for me

dezborders said:
Nope bootload locked = no 'remote' flashes via pc
Apparently there is an 'authenticated user' mode for Xiaomi engineers in MiFlaah and also an EDL Emergency Download Mode which you can trigger by shorting out 2 pins on the motherboard so bypass bootloader lock and flash any ROM
Neither were available options for me
Click to expand...
Click to collapse
I also tried to simulate a local OTA by copying update.zip to internal storage using ADB push command and booting into recovery mode to flash ... But it doesn't work for me

dezborders said:
Nope bootload locked = no 'remote' flashes via pc
Apparently there is an 'authenticated user' mode for Xiaomi engineers in MiFlaah and also an EDL Emergency Download Mode which you can trigger by shorting out 2 pins on the motherboard so bypass bootloader lock and flash any ROM
Neither were available options for me
Click to expand...
Click to collapse
I'm now in the procedure to sent it back under warranty. any idea if this is possible and what the cost would be if not under warranty?
If all fails i'll try the shorting by pins, should be interesting

I think a warranty repair claim is your best bet ... I have never read anywhere that unlocking bootloader invalidates Xiaomi warranty (Unlike Samsung and so many other brands!)
If warranty repair is re refused try a few independent repair shops
Last resort is get the back cover off the phone and short out the EDL pins
Good luck!
Let us know if you manage to get your phone booting up again

See this thread (last post) for a possible workaround via a 3rd party recovery image to flash EU rom
[Solved] Stuck in fastboot with locked bootloader
HI there! After multiple problems with the custom ROMs I tested, I finally decided to go back to the stock ROM by downloading it from the official thread. I extracted the .tgz archive, run the "flash_all.bat" program, which failed by saying it...
forum.xda-developers.com

Kaayman said:
I'm now in the procedure to sent it back under warranty. any idea if this is possible and what the cost would be if not under warranty?
If all fails i'll try the shorting by pins, should be interesting
Click to expand...
Click to collapse
I once hardbricked (complete blackscreen, not even Fastboot reachable) a Poco F3.
I requested a replacement from Amazon and that worked.
I said a software update bricked it.
Of course having to do that is really bad, but I was scared of opening the back.

dezborders said:
See this thread (last post) for a possible workaround via a 3rd party recovery image to flash EU rom
Bootloop to fastboot logo and back in lock state
Hi everybody, yesterday I tried flashing the stock pocof3 rom back onto my phone, but since it got stuck in a bootloop at the fastboot logo. Showing the poco logo for a milisecond and then straight to fastboot.. (before this I flashed twrp and...
forum.xda-developers.com
Click to expand...
Click to collapse
You pasted the current thread, do you have the link to the thread you meant?

Kaayman said:
You pasted the current thread, do you have the link to the thread you meant?
Click to expand...
Click to collapse