Related
Hello all!
I recently bought a second hand Xiaomi MI A2 online however I found a problem.
The previous owner did a factory reset on it but I'm stuck in the initial set up configuration because it asks me for the google account credentials attached to the phone. I texted the previous owner but had no answer.
So I tried to flash the official ROM to bypass the issue but I get an error message from Xiaomi Flash Tool saying "remote: Flash is not allowed in Lock State".
I think this is happening for one of the following reasons:
The previous owner didn't enable USB Debugging (thing I can't do because I'm stuck in the set up configuration)
The bootloader is locked (and I can't unlock it because I don't have the credentials of the attached account)
Does anyone knows how can I solve this problem?
Thank you for your attention
Joaosacramento said:
Hello all!
I recently bought a second hand Xiaomi MI A2 online however I found a problem.
The previous owner did a factory reset on it but I'm stuck in the initial set up configuration because it asks me for the google account credentials attached to the phone. I texted the previous owner but had no answer.
So I tried to flash the official ROM to bypass the issue but I get an error message from Xiaomi Flash Tool saying "remote: Flash is not allowed in Lock State".
I think this is happening for one of the following reasons:
The previous owner didn't enable USB Debugging (thing I can't do because I'm stuck in the set up configuration)
The bootloader is locked (and I can't unlock it because I don't have the credentials of the attached account)
Does anyone knows how can I solve this problem?
Thank you for your attention
Click to expand...
Click to collapse
Maybe you can see/ask in this thread for mia2 toolkit (I'm not sure but you can ask there )
https://forum.xda-developers.com/mi-a2/how-to/mi-a2-toolkit-unlock-bootloader-root-t3834585
daitalos said:
Maybe you can see/ask in this thread for mia2 toolkit (I'm not sure but you can ask there )
https://forum.xda-developers.com/mi-a2/how-to/mi-a2-toolkit-unlock-bootloader-root-t3834585
Click to expand...
Click to collapse
Thank you, will give it a try!
EDIT: Not working, every time I try to execute the unlock I got an error message "remote: Flashing Unlock is not allowed"
Joaosacramento said:
Thank you, will give it a try!
EDIT: Not working, every time I try to execute the unlock I got an error message "remote: Flashing Unlock is not allowed"
Click to expand...
Click to collapse
(yes...normally, first you must enable "OEM unlocking" from developer option
_ https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-unlock-bootloader-xiaomi-t3831484
__but first for your problem with locked device, see here for FRP apk : https://www.google.gr/search?q=com.....69i57j0l5.14869j0j8&sourceid=chrome&ie=UTF-8
__and here frp mia2 : https://www.google.gr/search?q=frp+.....69i57j0l3.7035j0j8&sourceid=chrome&ie=UTF-8
first "unlock" your device & then you can unlock bootloader easy ....
sry for english
Just unlock bootloader(critical too) and use miflash
I also have a Mi A2 stuck in android logo screen can't can't boot into device developer options to unlock bootloader.
Fastboot oem unlock give me error flashing is not allowed.
Is there anyway around this?
You need to do an unlock of critical partitions - "fastboot flashing unlock_critical"
daitalos said:
(yes...normally, first you must enable "OEM unlocking" from developer option
_ https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-unlock-bootloader-xiaomi-t3831484
__but first for your problem with locked device, see here for FRP apk : https://www.google.gr/search?q=com.....69i57j0l5.14869j0j8&sourceid=chrome&ie=UTF-8
__and here frp mia2 : https://www.google.gr/search?q=frp+.....69i57j0l3.7035j0j8&sourceid=chrome&ie=UTF-8
first "unlock" your device & then you can unlock bootloader easy ....
sry for english
Click to expand...
Click to collapse
Hey! It worked, thank you very much!
Face_11 said:
I also have a Mi A2 stuck in android logo screen can't can't boot into device developer options to unlock bootloader.
Fastboot oem unlock give me error flashing is not allowed.
Is there anyway around this?
Click to expand...
Click to collapse
https://forum.xda-developers.com/mi-a2/how-to/mi-a2-toolkit-unlock-bootloader-root-t3834585
(or flash stock rom via mi flash tool/ fastboot files) : http://en.miui.com/download-353.html
follow / read fastboot quide : http://en.miui.com/a-234.html
daitalos said:
https://forum.xda-developers.com/mi-a2/how-to/mi-a2-toolkit-unlock-bootloader-root-t3834585
(or flash stock rom via mi flash tool/ fastboot files) : http://en.miui.com/download-353.html
follow / read fastboot quide : http://en.miui.com/a-234.html
Click to expand...
Click to collapse
Thanks. I've tried the MIFlash Tool and I get Error Flashing Not allowed in Lock State. I've also tried the MI A2 ToolKit and get the same message. Basically anything I try and do states device is locked or unable to run in Lock State.
Boot Loader is currently locked and I cannot access developer mode to enable OEM unlocking. Question I have is :
- Can I use EDL Cable to work around this or do EDL cables not longer work with Newer Xiaomi phones?
- If EDL cable doesn't work, is the tespoint method my only option.
thanks in advance
Face_11 said:
Thanks. I've tried the MIFlash Tool and I get Error Flashing Not allowed in Lock State. I've also tried the MI A2 ToolKit and get the same message. Basically anything I try and do states device is locked or unable to run in Lock State.
Boot Loader is currently locked and I cannot access developer mode to enable OEM unlocking. Question I have is :
- Can I use EDL Cable to work around this or do EDL cables not longer work with Newer Xiaomi phones?
- If EDL cable doesn't work, is the tespoint method my only option.
thanks in advance
Click to expand...
Click to collapse
yes it's difficult .... I understand
edl maybe work, but I'm not sure...maybe if you go to a repair shop is a better solution
(see & here : https://forum.xda-developers.com/mi-a2/help/edl-deep-flash-cable-t3828732 )
https://youtu.be/n_7RVmW2Rvs
https://forum.xda-developers.com/showpost.php?p=77327325&postcount=2
Gl
Face_11 said:
Thanks. I've tried the MIFlash Tool and I get Error Flashing Not allowed in Lock State. I've also tried the MI A2 ToolKit and get the same message. Basically anything I try and do states device is locked or unable to run in Lock State.
Boot Loader is currently locked and I cannot access developer mode to enable OEM unlocking. Question I have is :
- Can I use EDL Cable to work around this or do EDL cables not longer work with Newer Xiaomi phones?
- If EDL cable doesn't work, is the tespoint method my only option.
thanks in advance
Click to expand...
Click to collapse
I would try a wipe from the recovery but if that doesnt work then just test point the phone. It isnt that hard, I had to do it myself today because of a soft brick. You just need a T3 screwdriver really. Take out the 2 bottom screws. Take a razor and slide it under the corner of the display and lift it enough the get a credit card in there. Then just work around and you should be able to get the screen off. Take the small metal plate off just above the battery and disconnect the battery and the connector on the right. There will be the test points, short them out, connect the phone to the pc(you can stop shorting out the points when it gets detected) and you have like 10-15secs to start flashing the phone in miflash(obviously you need to have the drivers already set up).
I have same problem with xiaomi mi a2 which had bootloop. Was not able to start device at all so no oem unloco no developer options and no usb debug. It was possible only adb sideload and fastboot. Adb sideload did nothing. I was trying to flash with adb sideload but it stops at 47% with message 1.00 x. Did try several roms with same results. Then i tried fastboot options. Falied to unlock not allowed. Itsl was impossible to get even into phone to activate developer options so i can activate oem unlock and the rest. I tried edl mode which did flash but then i got error message in bootloader it failed to mount system etc. Then i tried mi x6 rom to convert phone to another which doesnt have usual recovery mode but a stripped oem recovery mode. Now when u go back to mi a2 rom its bricked so there is no option of adb at all now. I tried to use mi x6 mi assistant option but app wont recognize usb connection it shows try normal mode then switch. When activating mi assistant on phone it does recognize rom version from recovefy flash in mi assistant app but when it downloads update rom version it cant continue. With pixel you can do anything with adb and it is so easy but xiaomi sucks big time. You cant do anything. Fastboot flashing unlock critical and fastboot oem unlock gets error failed. Flashing not allowed. U tried diferent cables but no luck. So now what? Thats why i hate adb. On samsung odin you can do impossible possible. Even with sp tools on mtk. Even boxes works flawlessly but xiaomi system is just thr worse. It doesnt matter if you get soemthing lost there is always a solution to other phones.
After having device sit as a paper weight for a few months, i broke down and ordered a phone repair kit. Opened device up and flashed via test point method. Worked Flawless. Time to enable OEM unlock so i don't have to open it up again. Thanks to community for all the help.
Use cmd
- go to fastboot then "fastboot oem unlock"
- go to fastboot again "fastboot flashing unlock_critical"
Flash with mi flash
Done
Just stumbled upon this and while may be 18 months too late, here's the step by step process to flash ROM on MI A2 that's giving error "Flash is not allowed in Lock State":
1) switch off device
2) enter fastbood mode (press hold power+vol down few seconds)
3) connect device with laptop
4) install and open adb folder on laptop (https://forum.xda-developers.com/showthread.php?t=2588979)
5) within adb folder -- shift + right click = open powershell here
6) fastboot flashing unlock_critical
7) step #6 may be pointless if phone is bricked but do it anyway
8) fastboot oem edl
9) find and download latest stock rom for your device (FASTBOOT version). It'll be .tgz file
10) extract the image folder from within (would be the same name as .tgz file)
11) open miflash (coudln't find link but look it up, it's easy)
12 select the image folder you extracted in step #10
13) click refresh. device name appear means it's recognized
14) from bottom of mi flash tool select whatever you want. I do "clean all"
15) flash (top right mi flash tool)
Face_11 said:
Thanks. I've tried the MIFlash Tool and I get Error Flashing Not allowed in Lock State. I've also tried the MI A2 ToolKit and get the same message. Basically anything I try and do states device is locked or unable to run in Lock State.
Boot Loader is currently locked and I cannot access developer mode to enable OEM unlocking. Question I have is :
- Can I use EDL Cable to work around this or do EDL cables not longer work with Newer Xiaomi phones?
- If EDL cable doesn't work, is the tespoint method my only option.
thanks in advance
Click to expand...
Click to collapse
Flashing is not allowed in lock state
i got a error recently in my mi a2 no software is installed but locked.
when i try to flash from mi flash tool it says flashing is not allowed in lock state
when i try to unlock in cmd flashing is not allowed in lock state
is there any one to fix this
IamUmesh said:
i got a error recently in my mi a2 no software is installed but locked.
when i try to flash from mi flash tool it says flashing is not allowed in lock state
when i try to unlock in cmd flashing is not allowed in lock state
is there any one to fix this
Click to expand...
Click to collapse
you need to open phone with screwdriver & do the test point ..search for video on YouTube...then EDL deepflash state you can use miflash to put back OFFICIAL only rom to device.
Hi guys, it's my first post. I have my MI A2 bricked after the last update. It's stuck at android logo and I can access only fastboot, no adb. Via fastboot I tried to wipe the phone, install TWRP, unlock the bootloader, but the answer is always I cant flash or do anything with a locked phone. What can I do? Is it possible to save data?
With locked bootloader and critical all your attempts to flash anything via fastboot could not succed, unless .you have previously got developer rights and checked "OEM unlock" option. With this option ON, and using USB 2.x port, you could unlock bootloader and critical via fastboot, but have no ways to save data (which is erased with unlocking as with factory reset).
Try to reboot many times with external power off and on, phone is supposed to boot into now inactive A/B slot (which was active prior to OTA) sooner or later, then you can save data and unlock.
If nothing helps, you'll have to open case, connect "[email protected] (or EDL) pins and then flash stock ROM with MiFlash, and then unlock and reflash with fastboot.
Hi,
so i got a situation here that xiaomi mi a2 (6x) out of nowhere rebooted to factory recovery with message "cant load android system. your data may be corrupt. If you continue to get this message you may need to perform factory reset deleting all data stored on this device"
Now after turning it off and on, it shows black screen "failed to boot" with option to power off or restart.
When restarting it goes to factory recovery again with that message and option to factory reset or try again (restart)
Now i cant perform factory reset before backing up the data, but i cant find the way to backup.
There is no custom recovery to download files from phone. When tried to flash custom recovery found out i cant because bootloader locked. And when found the way (dont know i it works) to unlock it without loosing data - cant do even that because developer options must be enabled to allow unlocking and debugging, so i get message in adb console FAILED (remote: Flashing Unlock is not allowed.
Is there any other way to keep the data before doing factory reset ?
Maybe try to flash with miflash keeping the data
blazessdd said:
Maybe try to flash with miflash keeping the data
Click to expand...
Click to collapse
unfortunately miflash cant do anything with locked bootloader as well. Just when starts to flash, gets error with bluetoth_a.
After research i noticed that miflash does nothing special at all just automated flash commands. In rom directory you can find flashing .bat files and run them in adb console.
When did that got all the data log, that bluetooth a is the first file that is tried to flash and stuck on locked bootloader.
Hello. Did you manage to solve your problem?
I have the same saituation.
Hi, unfortunately the only way i found is EDL mode.
https://youtu.be/i3OU4DOd7aY
When you keep those pins shorted, plug usb to your pc, and then , simply said, pc sees it as another device that can be flashed with everything locked.
So i flashed with miflash with keeping files option, but all that was saved is locking pattern. All media files lost.
Anyway, now i rooted and installed custom recovery to avoid any incident like this.
andjar said:
Hi, unfortunately the only way i found is EDL mode.
https://youtu.be/i3OU4DOd7aY
When you keep those pins shorted, plug usb to your pc, and then , simply said, pc sees it as another device that can be flashed with everything locked.
So i flashed with miflash with keeping files option, but all that was saved is locking pattern. All media files lost.
Anyway, now i rooted and installed custom recovery to avoid any incident like this.
Click to expand...
Click to collapse
you should edited rawprogram0.xml to not flash userdata (for saving your data)
Well if i only had this info 2 moths ago...
At leats others with this problem can find solution here now.
I am having major issues with GFIL working. My bootloader showed locked, though I know it was unlocked. Now it is grey out and says it is unlocked, it there a way to get that back to showing locked so I can manually unlock it again.
I am thinking that is the only reason QFIL is not working
Thank you:good:
Qfil only works if you entered the bulk or 9008 mode only. If you have unlocked your bootloader and reflashed or flashed a stock kdz for your device you will now have to relock and unlock it again, a reason why its greyed out.
KouaV1 said:
Qfil only works if you entered the bulk or 9008 mode only. If you have unlocked your bootloader and reflashed or flashed a stock kdz for your device you will now have to relock and unlock it again, a reason why its greyed out.
Click to expand...
Click to collapse
It is unlocked, but greyed out. QFIL won't work so no way to get into fastboot, to lock and unlock. So I am pretty well SOL.. QFIL won't bring up the option to get into Partiton Manager.
You dont need qfil to get into fastboot as thats a method from Xsavi for bootloader unlocking. Use the files in Xsavis post https://forum.xda-developers.com/lg-v40/development/unlock-lg-v40-via-9008-root-t-mobile-t4042207 . how did you get into fastboot mode in the first place to unlock it? Does Qfil show 9008 mode? if not showing 9008 it mean you didnt do it right.You need to relock the bootloader after you flash back the original kdz, do the steps to unlock again or else you cant flash twrp.
KouaV1 said:
You dont need qfil to get into fastboot as thats a method from Xsavi for bootloader unlocking. Use the files in Xsavis post https://forum.xda-developers.com/lg-v40/development/unlock-lg-v40-via-9008-root-t-mobile-t4042207 . how did you get into fastboot mode in the first place to unlock it? Does Qfil show 9008 mode? if not showing 9008 it mean you didnt do it right.You need to relock the bootloader after you flash back the original kdz, do the steps to unlock again or else you cant flash twrp.
Click to expand...
Click to collapse
I installed US Pie through LGUP from Sprint. I lost fast boot in the process, and now when I try using QFIL the Partition Manager will now pop up for me to flash the Engineering Bootloader (abl_a"). All the drivers are installed and showing up correctly in Windows 10 Device Manager, and in QFIL.
Droidman61 said:
I installed US Pie through LGUP from Sprint. I lost fast boot in the process, and now when I try using QFIL the Partition Manager will now pop up for me to flash the Engineering Bootloader (abl_a"). All the drivers are installed and showing up correctly in Windows 10 Device Manager, and in QFIL.
Click to expand...
Click to collapse
Yeah flash the v35 eng image onto the abl_a partition but back up your abl_a first before doing that incase it messed up. After you have done that you should press and hold the Power and Volume Down buttons until your device reboots out of 9008. When you hear the disconnect sound, immediately hold volume down (only volume down) to enter fastboot right away.
If still no fastboot then after you have sucessfully unlocked bootloader and stuff then youll need qfil to flash twrp onto abl_a.
KouaV1 said:
Yeah flash the v35 eng image onto the abl_a partition but back up your abl_a first before doing that incase it messed up. After you have done that you should press and hold the Power and Volume Down buttons until your device reboots out of 9008. When you hear the disconnect sound, immediately hold volume down (only volume down) to enter fastboot right away.
If still no fastboot then after you have sucessfully unlocked bootloader and stuff then youll need qfil to flash twrp onto abl_a.
Click to expand...
Click to collapse
I lost fast boot in the process, and now when I try using QFIL the Partition Manager will NOT POP UP for me to flash the Engineering Bootloader (abl_a"). All the drivers are installed and showing up correctly in Windows 10 Device Manager, and in QFIL.
So I don't know why the "Partition Manager" in QFIL will not work so I can install abl_a!:
Droidman61 said:
I lost fast boot in the process, and now when I try using QFIL the Partition Manager will NOT POP UP for me to flash the Engineering Bootloader (abl_a"). All the drivers are installed and showing up correctly in Windows 10 Device Manager, and in QFIL.
So I don't know why the "Partition Manager" in QFIL will not work so I can install abl_a!:
Click to expand...
Click to collapse
Does device Manager show your in "Qualcomm HS-USB QDLoader 9008"? Are you setting storage type to "UFS" in Qfil? Are your COM ports correct in device manager and in QFil? I ask these questions just incase you did something wrong but All I know is if your device does not have fastboot then qfil will be the one you need to flash twrp. Also make sure your using a USB 2.0 port as 3.0 has issues with the V40. Other thing is if your phones developer setting has OEM unlock greyed out then you will need to relash original kdz and relock bootloader and unlock again otherwise youll have fastboot fail with twrp flash. You don't need fastboot for qfil to work unless your phone is bricked if its just black screen and no light and if you cant boot into your phone.
KouaV1 said:
Does device Manager show your in "Qualcomm HS-USB QDLoader 9008"? Are you setting storage type to "UFS" in Qfil? Are your COM ports correct in device manager and in QFil? I ask these questions just incase you did something wrong but All I know is if your device does not have fastboot then qfil will be the one you need to flash twrp. Also make sure your using a USB 2.0 port as 3.0 has issues with the V40. Other thing is if your phones developer setting has OEM unlock greyed out then you will need to relash original kdz and relock bootloader and unlock again otherwise youll have fastboot fail with twrp flash. You don't need fastboot for qfil to work unless your phone is bricked if its just black screen and no light and if you cant boot into your phone.
Click to expand...
Click to collapse
Wow thank you for the info, sadly I have Sprint and there is NO kdz for this. to lock and re-lock. I think I am screwed.
Thank you.:good:
Yeah your probably screwed if you locked it with a custom rom or twrp. This a reason why I rather go with US unlvoked variant. AT&T also never releases software or firmwares for their phones and verizon removing fastboot. US carriers want your money thats the reason they do all these
KouaV1 said:
Yeah your probably screwed if you locked it with a custom rom or twrp. This a reason why I rather go with US unlvoked variant. AT&T also never releases software or firmwares for their phones and verizon removing fastboot. US carriers want your money thats the reason they do all these
Click to expand...
Click to collapse
I re-installed Windows 10 and boot, instant QFIL.:fingers-crossed::fingers-crossed:
Droidman61 said:
I re-installed Windows 10 and boot, instant QFIL.:fingers-crossed::fingers-crossed:
Click to expand...
Click to collapse
awesome good for you
Hello all, I have a big problem - I tried to use last TWRP from L00 Kostyan LOS13 version. I bricked my phone :-(. I had Kostyan last LOS13. by mistake I installed recovery.img to oem info partition. When I start the mobile LEDs first blink is red then green. There is no logo. I can only go to FASTBOOT&RESCUE MODE. It say phone locked. I can connect to phone via fastboot, adb says there is no device. I found out via fastboot that bootloader is locked. I am not able to load anything - its say command not allowed probably due to locked bootloader. Coudl you help me please? I also tried to save an official Huawei ROM to SD card to dload folder, but nothing happens during starting phone (I tried all combinations - power button + only vol-, only vol+, both volume). I can go only to FASTBOOT&RESCUE MODE :-(
You may have messed up your oem partition, which is very important in order to boot your device properly.
Although your bootloader is locked, I think you should be able to flash EMUI properly.
Extract your update.app using the Huawei Update Extractor Tool (google it, you will be able to find it in a xda forum, in the first results).
Try to flash that oem partition, it should be inside your update.app.
If it doesn't work, you may be able to unlock your P7 without any code.
Try typing fastboot oem unlock .
If it doesn't work, then try booting that TWRP image
fastboot boot <nameofyourtwrp>.img
There you will be able to reflash your OEM partition properly.
Obviously, for all the previous steps, you need ADB & Fastboot drivers:
MEGA
MEGA provides free cloud storage with convenient and powerful always-on privacy. Claim your free 20GB now
mega.nz
masemoel said:
You may have messed up your oem partition, which is very important in order to boot your device properly.
Although your bootloader is locked, I think you should be able to flash EMUI properly.
Extract your update.app using the Huawei Update Extractor Tool (google it, you will be able to find it in a xda forum, in the first results).
Try to flash that oem partition, it should be inside your update.app.
If it doesn't work, you may be able to unlock your P7 without any code.
Try typing fastboot oem unlock .
If it doesn't work, then try booting that TWRP image
fastboot boot <nameofyourtwrp>.img
There you will be able to reflash your OEM partition properly.
Obviously, for all the previous steps, you need ADB & Fastboot drivers:
MEGA
MEGA provides free cloud storage with convenient and powerful always-on privacy. Claim your free 20GB now
mega.nz
Click to expand...
Click to collapse
Thank you very much for you quick response. I extracted the official P7-L10V100R001C00B609Esp ROM (I can try another but I do not think it matters). I do not see there anything similar to oem partition. I tried to flash recovery and boot section. But I always got "FAILED (remote: Command not allowed)". I tried also the TWRP with the same result.
I tried fastboot oem unlock but I got "FAILED (remote: data parse fail)" it probably requires a code.
I think I have to unlock bootloader but how to do it if my phone does not work?