Database Develop

[Q] 1092 TWRP on 5.0 bootloop, stuck in recovery [SOLVED]

Hi,
I was on 5.0, running stock recovery and rooted. Today, installed TWRP for 5.0 on my device. I tried to flash the droid command center widget on my phone usng twrp, and it failed. I also hit the fix permissions option. After that the phone does not boot up, simply flashes the unlocked bootloader sign and shows the moto boot animation for a second or two before shutting down.
I can boot into recovery, and the computer detects the phone. But adb doesn't detect the device. I have the 1092 5.0 OTA on my computer and saved it on the phone in an attempt to flash it thru TWRP, but that failed with the message shown in the img attached. I also tried flashing stock 4.4.4, but that gave an error "Updating partition details" failed.
Can someone help me get back into my phone? :crying: ADB doesn't seem to be detecting my phone, else I'd have tried to install a rom via fastboot.
I have multi-tool v4.1 installed, would I be able to flash a rom (stock unrooted and full wipe is perfectly fine too) via that considering adb does not detect my phone, but the computer does?

Well, that looks annoying.
I've found myself in similar situations when I've accidentally flashed something I shouldn't have. The good news is that if you can boot to recovery you can also probably boot to the bootloader and use fastboot.
Have you tried wiping everything and going back to stock? It's time consuming but at least you'll end up with a working phone.
I had to do this when I put the wrong recovery on a phone and it mangled partitions. Device wouldn't boot.
There are instructions for the moto x here
http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657

oldcynic said:
Well, that looks annoying.
I've found myself in similar situations when I've accidentally flashed something I shouldn't have. The good news is that if you can boot to recovery you can also probably boot to the bootloader and use fastboot.
Have you tried wiping everything and going back to stock? It's time consuming but at least you'll end up with a working phone.
I had to do this when I put the wrong recovery on a phone and it mangled partitions. Device wouldn't boot.
There are instructions for the moto x here
http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657
Click to expand...
Click to collapse
Thanks for the reply! Color me silly, but would I be able to use fastboot given that when I run adb the 'adb devices' command does not show my phone?

HAXTREME said:
Thanks for the reply! Color me silly, but would I be able to use fastboot given that when I run adb the 'adb devices' command does not show my phone?
Click to expand...
Click to collapse
Because fastboot mode can start on your device even before Android loads (and can even run when Android isn't installed at all), fastboot mode is useful for updating the firmware quickly, without having to use a recovery mode.
Adb relies on android booting and usb debugging being enabled and the computer being authorized for debugging (L feature). Fastboot does not. Try booting into the bootloader and then run "fastboot devices" . Mine shows up. I suspect yours will too. If it doesn't then I'm out of my depth here.

oldcynic said:
Because fastboot mode can start on your device even before Android loads (and can even run when Android isn't installed at all), fastboot mode is useful for updating the firmware quickly, without having to use a recovery mode.
Adb relies on android booting and usb debugging being enabled and the computer being authorized for debugging (L feature). Fastboot does not. Try booting into the bootloader and then run "fastboot devices" . Mine shows up. I suspect yours will too. If it doesn't then I'm out of my depth here.
Click to expand...
Click to collapse
Ah yes. For some reason, my fastboot file had gotten deleted from the folder and so the command didn't run. Everything went smooth once I noticed that. Had to downgrade to 4.4.4., but w/e. Thanks @oldcynic

Flash Official ROM A2

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.

NEM-L21: Stucked with wrong version of boot.img, no more possibility of flashing

Hello everyone, it's my first time writing here, but I’ve tried everything, searched everywhere, and am desperate for help.
I screwed up big time while trying to flash a custom rom on my nem-l21, as I successfully did before with my xiaomi... So what I did:
I managed to unlock bootloader with dc unlocker. Then I got stucked flashing twrp with adb tools. Everything was looking to be fine, no error messages, “flashing successful”… But, I was never able to boot into flashed twrp. Always got stuck on “your phone has been unlocked blah blah. Your device is booting.” It never booted, not in twrp, nor in stock recovery. I tried different versions of twrp from different sources, always same result (flashing successful, booting into recovery not). Booting into the system was fine. And then I made that horrible mistake. Oh, how I wish I didn’t!!
I read on some website, that you are supposed to flash the twrp as boot.img, not as recovery.img. Seemed illogical and stupid to me, but in the end I tried it. Of course, this just bricked my phone, with no possibility to boot. After hours of googling, installing, trying and crying, I managed in the end to flash back stock boot.img. But at that time, I didn’t know my build number (b359), and I flashed boot.img b351. So now I have a phone which boots into the system b359 with boot.img b351, but with lot of errors.
- developer options, security options, display and factory reset option doesn’t work and just crashes. Therefore I am not able to flash the correct boot.img b359 or anything else at all from pc, no way to enable usb debugging and oem unlocking. Adb devices → nothing. I am able to use fastboot (fastboot devices sees the phone), but when try to flash something, I get error “command not allowed”. Also I can’t enable unknown sources installation, which bothers me a lot. And I can’t make factory reset to restore the crashing settings. Also I can’t change display timeout, and original 30 secs is super annoying.
- I am not able to uninstall even apps installed by me, always just restarts system UI and app stays.
What I tried so far:
- flashing correct boot.img from pc, not working because of dev options crashing
- go into recovery, but stock one is overwritten with unfunctioning twrp, always just get stuck on “your phone was unlocked blah blah… your device is booting now”, but it never does, have to hard reboot
- go into huawei erecovery, which is working, but when I try to resolve problem from there, always ends up with errors and crashes
- connect to pc and use HiSuite, system recovery tool here always says “no problem detected”
- updating to b361 through system update settings, always crashes on 5% and sends phone into “your phone was unlocked blah blah… your device is booting now” error
- downloading the proper b359 as and update.app file, put it in dload internal storage → same error during update, put it in dload sdcard → same error, no matter which way I use to start the update
- boot into twrp or stock recovery.img through fastboot without actually flashing it, anyway error “command not allowed”
- do factory reset or update through dial codes (i.e. *#*#123456#*#* …), nothing worked
My pc is windows 10, all drivers up to date. Using powershell as an admin. Am an idiot for not making backup of the phone before I started...
So, now I have more or less functioning phone, but I can’t uninstall any apps at all, can’t install from unknown sources, can’t do nothing from pc, can’t make any update, and lot of important settings keep crashing.
I can use the phone like this, but if somebody could think about some solution for this ****ed up situation I got myself into, I would be grateful to him/her for the rest of my life.
Sorry for a long post.
Thank you in advance and have a nice day

I think using Hisuit will help. Enter Fastboot and connect ur phone to ur computer and use system recovery toll

Xiao Mi A2 "Can't load Android system"

Hi Guys,
My phone suddenly stuck at this screen since may :
Android Recovery
Xiaomi/jasmine/jasmine_sprout
9/PKQ1.180904.001/V10.0.9.0.PDIMIXM
user/release-keys
Use volume up/down and power.
Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data store on this device.
- Try again
- Factory data reset
If i press try again, sometime it will go to fastboot screen.
I can go into recovery mode here but i not sure which step i should do next.
Reboot system nowreboot to bootloader
apply update from ADB
apply update from sd CARD
wipe data/factory reset
Mount/sstem
view recovery logs
run graphics test
run locale test
power off
I'm not a very tech savvy person, i would really appreciate some help as i have data inside my phone which i need. So if possible i would like to retain the data.
I tried like EDL,fastboot,and flashing none seem to work. Of course I may be doing it wrong.
Can anyone guide me step by step I be happy to give an reward via paypal.

I'm so sorry bro.... 80% of times this means you lost your data.
Is the bootloader unlocked?

blazessdd said:
I'm so sorry bro.... 80% of times this means you lost your data.
Is the bootloader unlocked?
Click to expand...
Click to collapse
Thank you so much for replying.
Nope, but I can do EDL to unlock bootloader, I already disassemble the device a few times.
Just that every time I try to flash it , it give me some error. like Bluetooth error or the version error .
Which I watch thousand of video to work but it's doesn't help. Or maybe I just watched the wrong video

Ok tell me exactly what are you doing and where you have downloaded the rom.
If it's corrupted and you try to flash it you will lose the data... Was debug USB activated on developer settings?

My device died too. After the October update, he never came back. It is looped on the home screen written "Android One".
I've tried several tutorials, it accesses the FastBoot screen, but when trying to use MI Flash appears a Bluetooth error and does not proceed.
I've tried using the adb flashing unlock_critical command, but it fails too.
He didn't have the bootloader unlocked, I now have a large paperweight.:crying:

epilifio said:
My device died too. After the October update, he never came back. It is looped on the home screen written "Android One".
I've tried several tutorials, it accesses the FastBoot screen, but when trying to use MI Flash appears a Bluetooth error and does not proceed.
I've tried using the adb flashing unlock_critical command, but it fails too.
He didn't have the bootloader unlocked, I now have a large paperweight.:crying:
Click to expand...
Click to collapse
You can try to short the edl points so you can flash the ROM again

blazessdd said:
You can try to short the edl points so you can flash the ROM again
Click to expand...
Click to collapse
I already made this attempt, "adb reboot edl" reports the message "error: '(null)' not found
Xiaomi never again

Question [Fixed] ASUS logo stucks on recovery, only access to bootloader

Hi all,
I'm encountering a very annoying issue with my brand new Zenfone 8.
I wanted to install the last LineageOS image, but now my phone seems stuck.
Here are what I did:
- Unlocked the bootloader: success with the ASUS APK after a few tries (error 11000 and 11006 ans eventually worked).
- Rebooted to bootloader
- Entered into recovery
- Used fastboot to flash the vendor partition.
At this point, everything looked OK. But then.... :
- Powered off the phone and restarted to bootloader.
- Tried to enter into recovery to flash the Lineage Recovery
But at this point, I had a ASUS logo stucked on the screen.
I can't do anything with adb or fastboot commands.
I tried the method explained here (https://www.asus.com/Content/Android-13-Beta/) to rollback to stock Android 12, but nothing happened too: I looked at the shell script (I'm on Linux) and I reckon that it stucks on fastboot command (the phone is in the bootloader).
Any idea about what failed? The last command used (vendor partition flash) said "OKAY".
And especially, what can I do now? Any way to reinstall the ASUS recovery?
Thanks in advance guys.

Not quite sure what your status is if you say "can't do anything with adb or fastboot commands". I've flashed Zenfones a couple of times (my household has 3 Zenfone 8's on LineageOS) and I had one that went into ramdump. I recovered from that using fastboot to manually reflash all 19 firmware partitions, in both slots. That got the phone out of ramdump, and I got to continue the upgrade to the new LineageOS. So: if you can boot to the fastboot environment, then that would be a road that might leaed you out. But if you can't even get a response to the command "fastboot devices" then I don't know of a course of action for you.

To use fastboot commands I had to run the phone into bootloader mode, then to "recovery" and eventually "fastboot" (I'm note 100% sure but it's what I remembered).
Without that, I was unable to use any fastboot commands like device or flash.
And now the issue is that I'm not able to go to recovery/fastboot again, because I have just the ASUS logo and nothing else.
It looks like that the stock recovery was dead, but I don't know why - and I don't know how to fix/reset it.

From the bootloader you should be able to flash the raw image again, it should flash everything

Adaoh said:
From the bootloader you should be able to flash the raw image again, it should flash everything
Click to expand...
Click to collapse
Good to know - but with which commands/tools?
As I said, I was unable to use fastboot commands from my computer on the Zenfone bootloader.
On the bootloader page, I just have "waiting for devices" and noting else. I had to go into the recovery > fastboot to make the commands work.

semurel said:
Good to know - but with which commands/tools?
As I said, I was unable to use fastboot commands from my computer on the Zenfone bootloader.
On the bootloader page, I just have "waiting for devices" and noting else. I had to go into the recovery > fastboot to make the commands work.
Click to expand...
Click to collapse
On Linux and maybe macs too you need to run fastboot commands as Root (sudo fastboot devices) for example. The raw image script should ask you for your Root password for this reason

Yes I know - I well used sudo for all commands.
The ASUS script asks me for password but then does absolutely nothing - not even a print. I waited a few minutes and finally canceled.
For you, fastboot commands should work on the bootloader screen? (I ask that because the script starts by a fastboot command).

semurel said:
Yes I know - I well used sudo for all commands.
The ASUS script asks me for password but then does absolutely nothing - not even a print. I waited a few minutes and finally canceled.
For you, fastboot commands should work on the bootloader screen? (I ask that because the script starts by a fastboot command).
Click to expand...
Click to collapse
Yes, they work from the bootloader, I always run the script from the BL too. Ironically, I had issues running fastboot commands from fastbootd for installing Omnirom, so I did it all in the bootloader and all worked fine.
I am not sure I can help you more at this point, it looks like it maybe got interrupted mid flashing and now something is wrong somewhere. Maybe if you look inside the bash script file you can find the command that it got stuck on and run that manually if you manage to get fastboot command access.

Strange - they have never worked from the bootloader. I tried that before according to the LineageOS wiki. I thought it was a mistake and use the recovery > fastboot to do that. I dont like that - I hope it's not a local version of the Zenfone or something like that.
I'm not at home tonight but yes I'll try to find commands not requiering the fastboot command.

Unfortunately all commands from the script are using fastboot. And as "fastboot devices" sees nothing, I can't do anything.
I've tried from the bootloader screen (with start, recovery, poweroff option) - from the start screen showing unlocked bootloader warning and from the ASUS logo when I try to start the recovery. I've tried the commands/scripts with Linux and Windows: same result.
So :
- I can't use any fastboot commands.
- I don't have the ASUS recovery.
Speaking of the ASUS recovery, I've found screenshots on internet and they don't have a "fastboot" submenu (I'm not sure it's a Zenfone 8). May had I a different version?
I don't like that. If I don't have others option, I guess that the warranty doesn't work because the phone is unlocked?

I eventually found a solution! I've tried with my old OnePlus cable and fastboot commands start working from the bootloader screen.
I have no idea why my other cable was faulty (it can charge the phone and executes commands from the Recovery > Fastboot menu - but not on the BL screen).
Anyway my problem is now fixed.
Thanks all for help and support.