Related
Think I did the title pretty well, I can only access fastboot (Before you say anything I've already tried this guide:http://forum.xda-developers.com/hua...ow-to-unbrick-huawei-p8-failed-t3260704/page1) all it gets me is the screen to light up (black) that's it. At this point I have no clue how to bring it back, any useful tips or ideas would always be appreciated. Thanks.
EDIT: It would be helpful if anyone knew a way to unlock the bootloader through fastboot
EDIT: nvm unlocked the bootloader through adb
EDIT:Installed TWRP through FASTBOOT
EDIT: Had the future rom downloaded, installed through SD card. DEVICE BOOTS.
EDIT: Tried dload method, went back to square 1 (Device would only backlit screen on boot, bootloader locked) Repeated steps and used the Huawei P9 Updater 2.0 by Hajuuk (Godbless) IT WORKS. Currently on C185B170 will update to B180 and from there to Android N. IF anyone has a similar problem feel free to ask.
kyle_2103 said:
Think I did the title pretty well, I can only access fastboot (Before you say anything I've already tried this guide:http://forum.xda-developers.com/hua...ow-to-unbrick-huawei-p8-failed-t3260704/page1) all it gets me is the screen to light up (black) that's it. At this point I have no clue how to bring it back, any useful tips or ideas would always be appreciated. Thanks.
EDIT: It would be helpful if anyone knew a way to unlock the bootloader through fastboot
EDIT: nvm unlocked the bootloader through adb
EDIT:Installed TWRP through FASTBOOT
EDIT: Had the future rom downloaded, installed through SD card. DEVICE BOOTS.
EDIT: Tried dload method, went back to square 1 (Device would only backlit screen on boot, bootloader locked) Repeated steps and used the Huawei P9 Updater 2.0 by Hajuuk (Godbless) IT WORKS. Currently on C185B170 will update to B180 and from there to Android N. IF anyone has a similar problem feel free to ask.
Click to expand...
Click to collapse
Hi, I have problem. I have two Huawei P9. One is L19 and the other is L09.
My L19 is the C900
My L09 I do not remember what it is ... the problem is that it is no system, it only turns on fastboot recovery mode. I've tried combo keys with dload but it does not work or does not recognize. By Hisuite says that the model is not supported. Finally I tried the Firmware Update program by hajuuk https://forum.xda-developers.com/p9-...dater-t3435878 I used several firmwares inside the L09 option but in the middle of the installation it gives error.
I need to find a way to enable the OEM so I can flash boot.img, recovery.img and system.img because I can not flash anything at the momento because it gives the Not Allowed command.
The status is Bootloader locked and FRP locked.
I do not know what to do, I have no ideas.
ChaseRxx said:
Hi, I have problem. I have two Huawei P9. One is L19 and the other is L09.
My L19 is the C900
My L09 I do not remember what it is ... the problem is that it is no system, it only turns on fastboot recovery mode. I've tried combo keys with dload but it does not work or does not recognize. By Hisuite says that the model is not supported. Finally I tried the Firmware Update program by hajuuk https://forum.xda-developers.com/p9-...dater-t3435878 I used several firmwares inside the L09 option but in the middle of the installation it gives error.
I need to find a way to enable the OEM so I can flash boot.img, recovery.img and system.img because I can not flash anything at the momento because it gives the Not Allowed command.
The status is Bootloader locked and FRP locked.
I do not know what to do, I have no ideas.
Click to expand...
Click to collapse
I think there is not solution for this problem. We have to wait. (I have the same problem but in Al00 running Al19 rom)
How do you check for FRP lock on a Huawei phone just curious.
ChaseRxx said:
Hi, I have problem. I have two Huawei P9. One is L19 and the other is L09.
My L19 is the C900
My L09 I do not remember what it is ... the problem is that it is no system, it only turns on fastboot recovery mode. I've tried combo keys with dload but it does not work or does not recognize. By Hisuite says that the model is not supported. Finally I tried the Firmware Update program by hajuuk https://forum.xda-developers.com/p9-...dater-t3435878 I used several firmwares inside the L09 option but in the middle of the installation it gives error.
I need to find a way to enable the OEM so I can flash boot.img, recovery.img and system.img because I can not flash anything at the momento because it gives the Not Allowed command.
The status is Bootloader locked and FRP locked.
I do not know what to do, I have no ideas.
Click to expand...
Click to collapse
Okay to unlock the bootloader, go into fastboot and plug in the USB to your computer, then by either using SRK tool or adb you need to flash this command: fastboot oem unlock (insert bootloader code) *don't put brackets* if you are unaware of your bootloader code then I cannot help you, however if you do know it, then once you unlocked the bootloader flash system.img and stuff to see if that works for you
kyle_2103 said:
Okay to unlock the bootloader, go into fastboot and plug in the USB to your computer, then by either using SRK tool or adb you need to flash this command: fastboot oem unlock (insert bootloader code) *don't put brackets* if you are unaware of your bootloader code then I cannot help you, however if you do know it, then once you unlocked the bootloader flash system.img and stuff to see if that works for you
Click to expand...
Click to collapse
Already tried this, I have the unlocking password but can't unlock BL through fastboot oem unlock (code) because the OEM Unlock is disabled.
ChaseRxx said:
Already tried this, I have the unlocking password but can't unlock BL through fastboot oem unlock (code) because the OEM Unlock is disabled.
Click to expand...
Click to collapse
That's weird, OEM unlcok was also switched off in developer options for me, yet this still worked, can you tell me exactly what the error code says?
kyle_2103 said:
That's weird, OEM unlcok was also switched off in developer options for me, yet this still worked, can you tell me exactly what the error code says?
Click to expand...
Click to collapse
I've tried some command in fastboot mode but there's always an error: Remote: command not allowed.
I can't do anything with fastboot mode
1. Try to force update with Power Button + Min Vol Button + Max Vol Button, liked you said this isn't working try to do the button combination with the phone connect it to the PC; in my case some times dload din't works after I connected the phone to the computer.
2. Other thing, something happend if you turn of the phone and leave Max Vol Button pressed, you should be entering to eRecovery.
3. Remember that sometimes enter in eRecovery mode requires to the phone be turn off otherwise you can't access to Recovery. So if this is the case follow bullet #2 and them #1.
PD: OFC I'm assuming you already have the dload folder with an compatible version of stock ROM on your SDCARD. If you don't have any version tries this one: https://forum.xda-developers.com/p9...dload-file-p9-eva-l09-b136-t3382818?nocache=1
Hope I helped you, I already bricked twice my P9 corrupting System Table Partitions.
Jeremy Molina.
---------- Post added at 10:38 AM ---------- Previous post was at 10:36 AM ----------
kyle_2103 said:
That's weird, OEM unlcok was also switched off in developer options for me, yet this still worked, can you tell me exactly what the error code says?
Click to expand...
Click to collapse
If you did the change of Unlock OEM before the bricked in an previous authorized computer you will still have rights for, otherwise new Android Security features is going to rejected the request.
Exacly
Dload/ no network
ChaseRxx said:
Exacly
Click to expand...
Click to collapse
Hi guys! Im new sorry if posted in wrong place/topic, I did dload method as here https://forum.xda-developers.com/p9/development/stock-rom-dload-file-p9-eva-l09-b136-t3382818 to debrand my L09 Vodafone to stock software and now I end up in EVA-C900B136 and my sim card/network is not working anymmore I had download the software package is in the above post and did force flash.
Many thanks for help!!!
kyle_2103 said:
Think I did the title pretty well, I can only access fastboot (Before you say anything I've already tried this guide:http://forum.xda-developers.com/hua...ow-to-unbrick-huawei-p8-failed-t3260704/page1) all it gets me is the screen to light up (black) that's it. At this point I have no clue how to bring it back, any useful tips or ideas would always be appreciated. Thanks.
EDIT: It would be helpful if anyone knew a way to unlock the bootloader through fastboot
EDIT: nvm unlocked the bootloader through adb
EDIT:Installed TWRP through FASTBOOT
EDIT: Had the future rom downloaded, installed through SD card. DEVICE BOOTS.
EDIT: Tried dload method, went back to square 1 (Device would only backlit screen on boot, bootloader locked) Repeated steps and used the Huawei P9 Updater 2.0 by Hajuuk (Godbless) IT WORKS. Currently on C185B170 will update to B180 and from there to Android N. IF anyone has a similar problem feel free to ask.
Click to expand...
Click to collapse
How did you unlock the bootloader through adb ? I'm in the same position as you put I have a P9lite.
dondrog said:
How did you unlock the bootloader through adb ? I'm in the same position as you put I have a P9lite.
Click to expand...
Click to collapse
fastboot oem unlock (followed by bootloader code)
kyle_2103 said:
fastboot oem unlock (followed by bootloader code)
Click to expand...
Click to collapse
Hello gays i install nougat 7
install with TWRP after install my phone is no keybord no all problems and i can`t active oem waht i do all command
remote not allowed coomand and i try to install all veriosn but still problem please help me
i install
EVA-L19C432B322-update
and my phone 6369C-EVA L19
my mistake please help me
i try to swoftware sim but swoftware failed
--
incompatibility with current version please download the correct update package
i upload vedio on youtube see please https://www.youtube.com/watch?v=V2yH...ature=youtu.be
sry for my bad engilsh
Any help would be greatly appreciated
I have a P9 L09, i have unlocked the bootloader, flashed TWRP recovery, and started flashing some roms. I have succesfully flashed a cyanogenmod, and it booted properly, but when it started it asked me for a password which i did not know, so i google searched and found out that it is a common issue and i need to wipe data from recovery. I tryed that but it did not work it says failed, and nothing works in the wipe advanced section, beside system. And also in the custom recovery it says that the internal storage has 0MB ! I was able to put other custom roms on the SDcard and flash them, they booted but every single one asks for the password.. I then tryed to install stock rom with the dload method, but it crashes and 40% , and i tryied the System Recovery option in HiSuite and it says it is not compatible with my device. Any help would be greatly appreciated! Thank you!
kyle_2103 said:
fastboot oem unlock (followed by bootloader code)
Click to expand...
Click to collapse
Hello. I have the same problem. I have my unlock code but in fastboot, adb command says it failed. Sorry for bad english. What can i do?
FAILED: REMOTE COMMAND NOT ALLOWED FINISHED.
Same problem on my honor &x locked bootloader and bricked. unlocking the oem like you said above does not work
what I have done is this:
Rooted phone
Installed TWRP
than I updated (stupid)
Lost root than I wanted to install Custom frimware what didnt work
Factory resetted phone, phone doesnt boot anymore now.
I can only access fastboot but I can not get fastboot to work on pc installed many different drivers just dont work.
lucmaas99 said:
what I have done is this:
Rooted phone
Installed TWRP
than I updated (stupid)
Lost root than I wanted to install Custom frimware what didnt work
Factory resetted phone, phone doesnt boot anymore now.
I can only access fastboot but I can not get fastboot to work on pc installed many different drivers just dont work.
Click to expand...
Click to collapse
Every two or three days people report here they bricked phones by forcing update or Factory reset (or relocking Bootloader) from custom or rooted phones (or by having TWRP) - one must first go back to the original stock firmware he had, before upgrading/resetting/relocking...
And this thread will also not help to somebody else -
since 'somebody' will not read (before bricking the phone) ;(
---
Do you still have TWRP - use HWOTA to flash stock
https://forum.xda-developers.com/showpost.php?p=75787156&postcount=3
If you have no TWRP but Fastboot is showing Bootloader unlocked, you should be able to flash TWRP.
If Fastboot is showing Bootloader locked but FRP unlocked, you should be able to unlock Bootloader.
But if there is no more TWRP and Fastboot is showing FRP and Bootloader locked - maybe DC Phoenix can help you
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
I used this command in fastboot: fastboot oem device-info
But I get this error: FAILED (remote: Command not allowed)
On my phone it says: Phone: unlocked and FRP: Lock
lucmaas99 said:
I used this command in fastboot: fastboot oem device-info
But I get this error: FAILED (remote: Command not allowed)
On my phone it says: Phone: unlocked and FRP: Lock
Click to expand...
Click to collapse
Yeah, this is not adb/fastboot drivers problem but a fact that you either did not keep OEM Unlocking or it locked due to your procedures. But you have no system to boot in and to unlock.
Is TWRP still on? Press and keep pressing Power until phone shuts down (from Fastboot).
Try to boot to recovery by keeping pressed Vol + and Power -- if it boots to TWRP proceed by HWOTA as above.
If it boots to eRecovery instead, maybe you can try Factory reset (although, I don't believe it will work)
If you don't have recovery anymore (and you have no system and FRP is locked) then you really bricked the phone, you should pay for DC Phoenix and try to unbrick
zgfg said:
Yeah, this is not adb/fastboot drivers problem but a fact that you either did not keep OEM Unlocking or it locked due to your procedures. But you have no system to boot in and to unlock.
Is TWRP still on? Press and keep pressing Power until phone shuts down (from Fastboot).
Try to boot to recovery by keeping pressed Vol + and Power -- if it boots to TWRP proceed by HWOTA as above.
If it boots to eRecovery instead, maybe you can try Factory reset (although, I don't believe it will work)
If you don't have recovery anymore (and you have no system and FRP is locked) then you really bricked the phone, you should pay for DC Phoenix and try to unbrick
Click to expand...
Click to collapse
I cannot get into to recovery but when I let the phone die and than it starts normally,
but everytime it turns off its get back stuck in bootloop I got my oem key when it booted back but now I tried unlocking it agian but it says this:
C:\adb>fastboot oem unlock <code>
...
FAILED (remote: Command not allowed)
finished. total time: 0.016s
C:\adb>fastboot reboot bootloader
rebooting into bootloader...
OKAY [ 0.023s]
finished. total time: 0.024s
lucmaas99 said:
I cannot get into to recovery but when I let the phone die and than it starts normally,
but everytime it turns off its get back stuck in bootloop I got my oem key when it booted back but now I tried unlocking it agian but it says this:
C:\adb>fastboot oem unlock <code>
...
FAILED (remote: Command not allowed)
finished. total time: 0.016s
C:\adb>fastboot reboot bootloader
rebooting into bootloader...
OKAY [ 0.023s]
finished. total time: 0.024s
Click to expand...
Click to collapse
I cannot flash anything because I cannnot enable USB debugging in developers options
zgfg said:
Yeah, this is not adb/fastboot drivers problem but a fact that you either did not keep OEM Unlocking or it locked due to your procedures. But you have no system to boot in and to unlock.
Is TWRP still on? Press and keep pressing Power until phone shuts down (from Fastboot).
Try to boot to recovery by keeping pressed Vol + and Power -- if it boots to TWRP proceed by HWOTA as above.
If it boots to eRecovery instead, maybe you can try Factory reset (although, I don't believe it will work)
If you don't have recovery anymore (and you have no system and FRP is locked) then you really bricked the phone, you should pay for DC Phoenix and try to unbrick
Click to expand...
Click to collapse
What can I do I can access phone but cannot unlock bootloader because cannot use remote commands and I can not get into any recovery menu I am out of idea's
lucmaas99 said:
I cannot flash anything because I cannnot enable USB debugging in developers options
Click to expand...
Click to collapse
You can boot to system?
Which (full name) build it shows in About?
Can you enable Developer options - then why cannot you enable USB debugging?!
You must first enable Allow ADB debugging in charge... and only then USB debugging -otherwise USB debugging switches off
zgfg said:
You can boot to system?
Which (full name) build it shows in About?
Can you enable Developer options - then why cannot you enable USB debugging?!
You must first enable Allow ADB debugging in charge... and only then USB debugging -otherwise USB debugging switches off
Click to expand...
Click to collapse
Modelnumber: EVA-L19
Build: NRD90M test-keys
I think I should not supposed to have test-keys doesnt seem correct?
So I got my phone to boot but everytime I want to do something in recovery or something else It wont boot anymore and than I need to make the battery run out of juice. are there anyfix without needing root recovery or fastboot.
ADB wont work because usb debugging wont turn on (tried many things), Fastboot kinda works but gives the error (remote command not allowed)
Cannot get into any Recovery I can boot to OS
Hi all,
I got problem installing TWRP recovery on P10 buil number VTR-L29C432B171.
First of all i unlocked bootloader with Minimal ADB an Fastboot. Now bootloader shows "Phone Unlocked" and "FRP lock".
When i try fastboot flash recovery... it shows FAILED (remote: command not allowed).
Any suggestions?
you have to activate OEM unlock in settings/developers options
virusdunil said:
you have to activate OEM unlock in settings/developers options
Click to expand...
Click to collapse
This setting is inactive (grayed out) after unlocking.
Finally problem solved.
There was somethig wrong with adb interface driver. After unlocking bootloader i have to reset developer settings to defaults to get usb debbuging work again. After this OEM unlock setting resets to, but because it stays inactive its imposible to turn it on. So i relocked bootloader and used Huawei Multitool drivers to unlock again and install TWRP.
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.
Hello all,
I tried flashing a RR rom, and afterwards it failed to boot AND locked my device again. I have my unlock code still, but when trying to oem unlock in fastboot, I get an error: Check 'OEM unlocking' in Android Settings > Developer Options. Since the ROM won't boot, I can't check OEM unlocking. Is there any way around this? I'm afraid I've had a hard brick on my hands.
Reznor7 said:
Hello all,
I tried flashing a RR rom, and afterwards it failed to boot AND locked my device again. I have my unlock code still, but when trying to oem unlock in fastboot, I get an error: Check 'OEM unlocking' in Android Settings > Developer Options. Since the ROM won't boot, I can't check OEM unlocking. Is there any way around this? I'm afraid I've had a hard brick on my hands.
Click to expand...
Click to collapse
You can try LMSA's Flash rescue option
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Or if you have a pc with windows 7 try
RSD Lite
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my Moto E (4) using Tapatalk
I've tried both options, but neither appears to see my device. It's in bootloader mode and shows up in Windows Device Manager as "Motorola ADB Interface".
It's showing 0xFAILED for cid. Here's my current bootloader screen.
I've tried blank flash in both Linux and windows. Both just say "Waiting for device". I've never had a device brick like this before.
Reznor7 said:
I've tried both options, but neither appears to see my device. It's in bootloader mode and shows up in Windows Device Manager as "Motorola ADB Interface".
It's showing 0xFAILED for cid. Here's my current bootloader screen.
https://ibb.co/znCSvMR
I've tried blank flash in both Linux and windows. Both just say "Waiting for device". I've never had a device brick like this before. [emoji3525]
Click to expand...
Click to collapse
Blankflash only works if device is in EDL mode.
Sent from my Moto E (4) using Tapatalk
Edit: I think my issue is that I'm needing the latest firmware (including the May 2020 security update), and I can't find it anywhere. Trying to downgrade (even with an unlocked bootloader) is giving me the preflash validation error when trying to flash bootloader.img. Looks like I need ppws29.183-29-1-19
Final edit: I had to find the latest firmware for my device. Unfortunately, only a paid site had it, but after buying and installing everything is good again!