Related
hello guyz please help I am install bnd L34 firmware ton my bnd-Al10 from firmware finder app and it successfully installed but I am rebooting my phone its boot on erecovery mode and my frp is locked and the bootloader unlock site is down what can I do ,?
[email protected] said:
hello guyz please help I am install bnd L34 firmware ton my bnd-Al10 from firmware finder app and it successfully installed but I am rebooting my phone its boot on erecovery mode and my frp is locked and the bootloader unlock site is down what can I do ,
Click to expand...
Click to collapse
bootloader unlock code different from frp unlock code.
installing other device firmware has chance to replace oeminfo.img partition. Changing this partitin often causes locked frp.
If lucky you can wipe from the erecovery that is loading. maybe even couple times. Then maybe it will boot. Other that that there has been no public mention of any fix.
do your best to fix it using hisuite or other methods if you can. if you have twrp that can help if you have stock recovery and locked frp your only hope might be hisuite and if that fails you will need a paid option like dc-phoenix or funkyhuewei. i only have experience with dc-phoenix, and it did fix my locked frp completely bricked phone, but i read that funky also works well but is nearly 3 times as expensive. (15€ vs 50€)
[email protected] said:
hello guyz please help I am install bnd L34 firmware ton my bnd-Al10 from firmware finder app and it successfully installed but I am rebooting my phone its boot on erecovery mode and my frp is locked and the bootloader unlock site is down what can I do ,?
Click to expand...
Click to collapse
Hello friend i had done the same i installed L21 firmware from firmwarefinder to my BND-AL10 and same happened my phone was bricked it was directly taking me to the stock recovery but my bootloader was locked and lucky i had Kept my bootloader unlock code with me when the site was up so when i unlocked my bootloader it did factory reset and booted normally and Oreo was installed but the only problem im facing is my build number is still showing the old one which is BND-AL10C675 B161 and i don't have face unlock and ride mode which comes with Oreo i had face unlock with BND-AL10C675 B161 . My frp was unlocked already .
sygladiator said:
Hello friend i had done the same i installed L21 firmware from firmwarefinder to my BND-AL10 and same happened my phone was bricked it was directly taking me to the stock recovery but my bootloader was locked and lucky i had Kept my bootloader unlock code with me when the site was up so when i unlocked my bootloader it did factory reset and booted normally and Oreo was installed but the only problem im facing is my build number is still showing the old one which is BND-AL10C675 B161 and i don't have face unlock and ride mode which comes with Oreo i had face unlock with BND-AL10C675 B161 . My frp was unlocked already .
Click to expand...
Click to collapse
The displayed build number comes from the data part of the update. (Update_*hw_*.zip)
If you reflash again all three files , might be fixed
mrmazak said:
The displayed build number comes from the data part of the update. (Update_*hw_*.zip)
If you reflash again all three files , might be fixed
Click to expand...
Click to collapse
How should i reflash it , can you please provide me the procedure to do so , it would be very helpfull
sygladiator said:
How should i reflash it , can you please provide me the procedure to do so , it would be very helpfull
Click to expand...
Click to collapse
If flashing again is the answer to solve problem. Use my guide here.
You are on Oreo now so use the top portion. "Flash update"
https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649
mrmazak said:
If flashing again is the answer to solve problem. Use my guide here.
You are on Oreo now so use the top portion. "Flash update"
https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649
Click to expand...
Click to collapse
It all goes above my head , what exactly i have to do please elaborate .
sygladiator said:
It all goes above my head , what exactly i have to do please elaborate .
Click to expand...
Click to collapse
I don't want to sound like rude or anything.
But I put it all pretty simple, I thought. Like 4 steps
Download files
Put files on SD card
Install twrp
Install file I shared
If that is over your head, maybe you should not have modify and phone.
mrmazak said:
I don't want to sound like rude or anything.
But I put it all pretty simple, I thought. Like 4 steps
Download files
Put files on SD card
Install twrp
Install file I shared
If that is over your head, maybe you should not have modify and phone.
Click to expand...
Click to collapse
Sorry for silly questions by the way thankyou for your help
There is no other options to install other than installing through twrp???
Will i get OTA updates of my bootloader is unlocked ??
If not then i vl be happy to install RROS 8.1 coz am on oreo that means i have treble support so i can just install it
So far so good
sygladiator said:
Sorry for silly questions by the way thankyou for your help
There is no other options to install other than installing through twrp???
Will i get OTA updates of my bootloader is unlocked ??
If not then i vl be happy to install RROS 8.1 coz am on oreo that means i have treble support so i can just install it
So far so good
Click to expand...
Click to collapse
I know each device has it's own proceedure to, flash and all, and they are similar but different.
So can be confussing
I have one Moto Z2 Force (XT1789-05), bought from coolicool.com, I didn't know device came Unlocked Bootloader, Device rom had problem with many apps, I googled and found one topic in XDA developer to Install Stock Rom, I downloaded and Installed India Rom, it's worked somehow fine, but still had problem, I downloaded Verizon Rom, Android 8, after Installed Android 8 Verizon Rom, Locked device bootloader immediately, now device stuck at Welcome Wizard in Android 8, after select language I got this message: (Please wait, this may take a few minutes) this is proof video (http://ahmn.co/Upload/IMG_0161.MOV), after this issue, device already locked, I can't unlock, because need to go to the Developer Option in Setting, I stucked in Welcome Wizard, there isn't any bypass, So, I start to search in Google, XDA-Forum, Android Central and more, I created many threads, many requests, no one can't help me, I tried to reach google developer support to the tell to me how can I bypass Android 8 Welcome Wizard, there is must be a way, but I can't find it, now I can access to Android Recovery and Bootloader
1. if you help me to FORCE UNLOCK device without need Developer Option in setting my problem will solve
2. If you help me to Bypass Android Welcome Wizard, access setting and enable OEM Unlock
3. If you help me to update the device from Android 8 to Android 9 Verizon ROM via ADB Sideload or Update from SD card in Recovery mode
4. If you have any idea to how can I fix it
Extra Information: I bought Belkin and Uni USB-C to Ethernet Adaptor to help me bypass Android 8 Welcome Wizard, I bought WSKY WIFI Adaptor because device Wifi can't find any network (I found QR setup by tap several times in Language Selection), after this section need to download google device policy apk, my device can't find any Wifi Network and my Ethernet Adaptor can't help me either, So, I just remained with my phone, and I can't do anything,
Please, someone, help me
My Device SKU: XT1789-05
These coolicool phones always come with the wrong firmware install, the simple solution to that is to flash the correct firmware which is plain old RETAIL. Solved. That's for anyone who might have or end up with one of these phones.
As for your phone and since you're in the situation you are I'd flash VZW pie. That isn't the correct firmware for your phone, but you've got a locked BL with VZW on it now and nothing is working. Since your ultimate goal is to flash pie anyways, that's what I'd do. Maybe that will clean up your system enough to enable oem unlock. If you can get your BL unlocked, then you're half way there. Surely by now you've realized that you haven't got many if any options.
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Yes, I put my self in prison by locking bootloader, I already downloaded this firmware, but how can I update this firmware via ADB Sideload or Micro SD?
as you know bootloader locked and there isn't a simple way, with locked bootloader I can't flash this file, (Remote Failure) error
thanks a lot
41rw4lk said:
These coolicool phones always come with the wrong firmware install, the simple solution to that is to flash the correct firmware which is plain old RETAIL. Solved. That's for anyone who might have or end up with one of these phones.
As for your phone and since you're in the situation you are I'd flash VZW pie. That isn't the correct firmware for your phone, but you've got a locked BL with VZW on it now and nothing is working. Since your ultimate goal is to flash pie anyways, that's what I'd do. Maybe that will clean up your system enough to enable oem unlock. If you can get your BL unlocked, then you're half way there. Surely by now you've realized that you haven't got many if any options.
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
Hello, anybody?????
There is any way to Upgrade Android 8 to Android 9 with locked bootloader?
My Device state: flashing_locked
is it possible to FORCE UNLOCK?
or is it possible to open hardware device and make it force unlock?
please help me,
someone?
solution
I need help, PLEAAAAAAAAAAAAAAAAAAAASSSSSSSSSSSSSEEEE
Have you tried using Lenovo moto smart assistant?
Leonardoliveira said:
Have you tried using Lenovo moto smart assistant?
Click to expand...
Click to collapse
Yes, I did, not work
Hi, could you solve your problem? I have a moto xt1789-05 with the bootloader locked and it doesn't allow me to start the developer options. I'm looking for a solution if you could?
gamc01 said:
Hi, could you solve your problem? I have a moto xt1789-05 with the bootloader locked and it doesn't allow me to start the developer options. I'm looking for a solution if you could?
Click to expand...
Click to collapse
You need to elaborate. Is oem unlocking grey out? Are you signed into google services? Do you have wifi and/or radio?
gamc01 said:
Hi, could you solve your problem? I have a moto xt1789-05 with the bootloader locked and it doesn't allow me to start the developer options. I'm looking for a solution if you could?
Click to expand...
Click to collapse
I couldn't do anything, I just send to Motorola repair and they change mainboard
sorry, I didn't find any solution
Ok I'll keep looking for some solution thanks
---------- Post added at 04:27 AM ---------- Previous post was at 04:13 AM ----------
41rw4lk said:
You need to elaborate. Is oem unlocking grey out? Are you signed into google services? Do you have wifi and/or radio?
Click to expand...
Click to collapse
thank you for responding 41rw4lk, what happens is that I can not access because it does not pass from the logo of motorola then it restarts when i try flash whith the retail version of brazil, but when i flash whith the versions at&t oreo or amx of telcel when turning on the moto I get the message your device is corrupt it cant be trusted and will not boot. I have seen some videos In which it has worked but not specify the bootloader status
gamc01 said:
Ok I'll keep looking for some solution thanks
---------- Post added at 04:27 AM ---------- Previous post was at 04:13 AM ----------
thank you for responding 41rw4lk, what happens is that I can not access because it does not pass from the logo of motorola then it restarts when i try flash whith the retail version of brazil, but when i flash whith the versions at&t oreo or amx of telcel when turning on the moto I get the message your device is corrupt it cant be trusted and will not boot. I have seen some videos In which it has worked but not specify the bootloader status
Click to expand...
Click to collapse
You shouldn't flash firmware from other variants like att, etc. However, if you're able to flash those firmwares and not get any permission denied errors then your bootloader is unlocked, which is good. If you have NOT flashed a pie firmware, good, do NOT do it until everything is up and running and you're sorted. If you have, then you'll need to use pie firmware to fix it since once you flash a pie modem there is no going back to an oreo modem.
Run this command from bootloader/fastboot mode and post back your output.
PHP:
fastboot getvar all
You can omit your imei and your serial no. for privacy.
Hi guys,
I recently got a Moto Z2 Force XT1789-05 variant from Brazil which apparently tried to force an update to the pie but it must have been the wrong firmware so it lost imei and wifi. And it seems to relock the boot loader and have returned to oreo. Then I can not activate the OEM unlock, I even tried to use the internet from the PC via USB but still does not enable the option. I'm not sure what else to do does anyone know what to do ??? Help
Sorry my bad english
What software channel does it have listed in about phone settings?
Here
41rw4lk said:
What software channel does it have listed in about phone settings?
Click to expand...
Click to collapse
Its here
Since it's an -05 variant, with retbr, and has had pie flashed in some form I'd try flashing retbr pie firmware.
Firmware - https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Flashall - https://forum.xda-developers.com/attachment.php?attachmentid=4812854&d=1567089696
adb and fasboot files - https://forum.xda-developers.com/attachment.php?attachmentid=4781024&d=1561215357
General guide on how to flash. Use the firmware and flashall I posted. - https://forum.xda-developers.com/z2-force/how-to/how-to-return-to-stock-sprint-t3694783
It might not correct your problem, not sure how much of a mess is going on there, but this will be a good starting point. Just pay attention to what is going on and what (if any) errors you receive.
41rw4lk said:
Since it's an -05 variant, with retbr, and has had pie flashed in some form I'd try flashing retbr pie firmware.
Firmware - https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Flashall - https://forum.xda-developers.com/attachment.php?attachmentid=4812854&d=1567089696
adb and fasboot files - https://forum.xda-developers.com/attachment.php?attachmentid=4781024&d=1561215357
General guide on how to flash. Use the firmware and flashall I posted. - https://forum.xda-developers.com/z2-force/how-to/how-to-return-to-stock-sprint-t3694783
It might not correct your problem, not sure how much of a mess is going on there, but this will be a good starting point. Just pay attention to what is going on and what (if any) errors you receive.
Click to expand...
Click to collapse
Nothing yet, I tried what you sent but as it has the bootloader locked I believe it is preventing.
Will I have to stay connected 7 days to enable OEM unlock?
crpcnt.cpc said:
Nothing yet, I tried what you sent but as it has the bootloader locked I believe it is preventing.
Will I have to stay connected 7 days to enable OEM unlock?
Click to expand...
Click to collapse
No. You just need to sign into google on your phone to enable oem unlocking. Might try pairing bluetooth to get a connection if possible. Might try using the lenovo moto smart tool to see if it'll do a rescue on it. With a locked bootloader typically you can only flash official signed firmware that is either the version or newer. Again, depending on what kind of mess you've got there you might not get anything to flash.
41rw4lk said:
No. You just need to sign into google on your phone to enable oem unlocking. Might try pairing bluetooth to get a connection if possible. Might try using the lenovo moto smart tool to see if it'll do a rescue on it. With a locked bootloader typically you can only flash official signed firmware that is either the version or newer. Again, depending on what kind of mess you've got there you might not get anything to flash.
Click to expand...
Click to collapse
I logged into my google account, but it doesn't enable OEM unlock yet, so the mess was big on it.
crpcnt.cpc said:
Hi guys,
I recently got a Moto Z2 Force XT1789-05 variant from Brazil which apparently tried to force an update to the pie but it must have been the wrong firmware so it lost imei and wifi. And it seems to relock the boot loader and have returned to oreo. Then I can not activate the OEM unlock, I even tried to use the internet from the PC via USB but still does not enable the option. I'm not sure what else to do does anyone know what to do ??? Help
Sorry my bad english
Click to expand...
Click to collapse
I'm in the same situation, I've tried everything, I've had several people helping me, I have the same model and variant and I can't recover at all.
Success is disgusted by some people, and will not share any files for free in the future.
If relock, how about OTA uptdate?
dungnghien said:
If relock, how about OTA uptdate?
Click to expand...
Click to collapse
yes，you can！only support CN firmware，but WW firmware upgrades are not supported. The WW version of the firmware upgrade, you need to download the update package to the root directory, restart the phone to detect the update.
Will this process factory reset or no ???
zinou213 said:
Will this process factory reset or no ???
Click to expand...
Click to collapse
YES！
Damn! I should have waited for this. Too late. I used unlock tool. Now Asus has my unlock info.
One question. Can I relock if I originally unlocked using asus unlock apk tool???
to confirm.......
i have a factory locked, untouched WW 512 unit. If i use this tool, i can unlock WITHOUT Asus knowing? no downsides?
@johnny886,
Thank for this, I waited for something like this, wanted to unlock the bootloader without using that app that gives IMEI to asus, a total offline boot-loader unlock.
although i stuck in step 3 ".update_image_EDL.bat”, dos prompt instantly closes. It may be a driver issue, as im not familiar with drivers for this phone, can you upload the drivers, only thing missing in this pack.
BakaValen said:
to confirm.......
i have a factory locked, untouched WW 512 unit. If i use this tool, i can unlock WITHOUT Asus knowing? no downsides?
Click to expand...
Click to collapse
There are no disadvantages, the only benefit is that you can unlock your phone through EDL mode, no need to install UnlockTool.apk to apply for unlock! The ASUS server will not get your unlocked status, you can get upgrades via OTA later.
Extreme184X said:
@johnny886,
Thank for this, I waited for something like this, wanted to unlock the bootloader without using that app that gives IMEI to asus, a total offline boot-loader unlock.
although i stuck in step 3 ".update_image_EDL.bat”, dos prompt instantly closes. It may be a driver issue, as im not familiar with drivers for this phone, can you upload the drivers, only thing missing in this pack.
Click to expand...
Click to collapse
Oh sorry, I forgot to upload the driver for Qualcomm! You can download and install this tool on your computer, and then follow the steps to unlock it! Download link:https://drive.google.com/open?id=1PRw4jcg0zQKLQnMz7gApMZtCYex1PfJM
How about Burnt Fuses? Does something like this occur? Basically, i want to ensure that the fact that ive unlocked is hidden for warrenty. (I can always re-lock before sending back if i need to)
It would suck for them to tell me, that they wont service it because it was previously unlocked.
BakaValen said:
How about Burnt Fuses? Does something like this occur? Basically, i want to ensure that the fact that ive unlocked is hidden for warrenty. (I can always re-lock before sending back if i need to)
It would suck for them to tell me, that they wont service it because it was previously unlocked.
Click to expand...
Click to collapse
By unlocking this way, you can enjoy the warranty!
had anyone tried this method on previous unlocked device? did it will regain CN FOTA? thanks!
Hi, i tried but stuck on step 3, any way to solve? tried to change the usb port but same thing happened.
on step 3:.Double click to open “1.update_image_EDL.bat”,
it said: {ERROR: WritePort:5164 Could not write to '\\.\COM10', Windows API WriteFile failed! Your device is probably *not* on this port, attempted 100 times
@johnny886,
Hi, I installed the Qualcomm drivers but for step 3 "1.update_image_EDL.bat”, it still prompts and closes immediately and I'm not sure how to QPST or QFIL. Are there ways to fix the bat file or provide a more detaisl on using QPST or QFIL please?
You can root without unlock bootloader?
Deleted, misread, don't think it's relevant...
So I did this and now my headphones jack isn't working. Has this happened to anyone else?
Update: The current workaround is to use the headphone jack of the included cooling fan.
Update 2: So it may have something to do with the bootloader that was flashed during the EDL unlocking process, which seems to be a generic SD855 bootloader. I came to this conclusion after I noticed that I was being limited to 70% battery charge. I flashed the WW 1910.35 OTA from ASUS' site and the battery now charges to 100%, but the headphone jack still remains broken. I will try to flash the WW 1910.44 update through fastboot when I get home, which I'm hoping will have whatever partition that was overwritten during the unlocking process.
Update 3: I figured it out. After using "fastboot flash boot TWRP.img" to boot into TWRP initially, I didn't flash the stock boot image again. This broke the headphone jack. So after booting into TWRP using that command, I had to flash the stock boot image first, then flash the TWRP and Magisk installers in that order. Hope this helps someone.
dennis96411 said:
So I did this and now my headphones jack isn't working. Has this happened to anyone else?
Update: The current workaround is to use the headphone jack of the included cooling fan.
Update 2: So it may have something to do with the bootloader that was flashed during the EDL unlocking process, which seems to be a generic SD855 bootloader. I came to this conclusion after I noticed that I was being limited to 70% battery charge. I flashed the WW 1910.35 OTA from ASUS' site and the battery now charges to 100%, but the headphone jack still remains broken. I will try to flash the WW 1910.44 update through fastboot when I get home, which I'm hoping will have whatever partition that was overwritten during the unlocking process.
Update 3: I figured it out. After using "fastboot flash boot TWRP.img" to boot into TWRP initially, I didn't flash the stock boot image again. This broke the headphone jack. So after booting into TWRP using that command, I had to flash the stock boot image first, then flash the TWRP and Magisk installers in that order. Hope this helps someone.
Click to expand...
Click to collapse
Hey, can you please tell me where to get the stock boot image for 1910.44?
Edit: Okay nevermind got it.
Stuck on step 1.update_image_EDL.bat
Almost all of us are stuck on step 1.update_image_EDL.bat . The CMD window just shows and closes fast, and phone doesnt enter fastboot mode. I installed all drivers. Can you post guide on how to do that step using QPST or Miflash tools?
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