[Blade General] dz_radon:
Good day people of the internet and this forum..

I'm not sure if this is the good place to ask for help, you can move this topic if you consider it put in the wrong section but don't delete it please, however any help would be appreaciated... So there's the problem:

I got a ZTE Blade L110 to repair or mostly, wishing to flash a custom recovery (TWRP to be clear) to it and from what I heard not only it will straight work by "Unlocking the OEM" from the Developer Options, but I also heard I must unlock it via restarting it into "Fastboot Mode" by ADB or via booting it from the "Recovery Mode" if not the ADB option. Althought whenever it is on the Fastboot mode, and I also connected the phone to the computer, it gets connected as I installed the drivers myself. The "fastboot devices" command in the cmd it also recorgnizes it but whenever I want to type in "fastboot oem unlock" in the cmd prompt screen it just shows out "..." in which in that step it should show anything in the phone's screen like a screen confirmation but nothing, it remains the same screen statistically as from booting into bootloader along with the white ZTE splash screen and showing in the left top corner "fastboot mode" along in a black sqaure background for the text... And the only way to stop it is by unplugging the phone and plugging it in again the USB cable and throwing me an error of "FAILED: Too many links" or something like that but didn't anything to the phone thought.. However some commands such as "fastboot reboot" works and so on but not the ones which needs prompt confirmation / authorization from the phone as it doesn't pop up anything as said above.

I'm also going to share out some screens so you might not get confused that easily from what I said above:

[IMG="cmd"]https://i.imgur.com/lDYBRUy.png[/IMG]

[IMG="fastboot mode"]https://i.imgur.com/zKntMO4.jpg[/IMG]

As if you can see, it is EXACTLY at the same time process, so basically as I mentioned many times above it doesn't show anything on the screen on the phone apart from that same screen before doing anything to it.

And also if my driver showoff is required, you're welcome

[IMG="driver"]https://i.imgur.com/AJBmbgl.png[/IMG]

[IMG="folder"]https://i.imgur.com/Nh9iy7y.png[/IMG]

[IMG="driver content"]https://i.imgur.com/hXjFHHv.png[/IMG]

I also tried to uninstall the driver too but it won't work and it will show out "fastboot_Gadget" as device name with an error in it as no drivers were found for it..

I also tried different set of drivers, even non-signed and signed ones but didn't changed anything

Weirdly I also tried different ADB / Fastboot tools but the ones from the SDK source didn't even bothered to show out "..." whenever I executed the "fastboot oem unlock" or "fastboot unlock(ing) flash" command it simply just didn't showed anything after and it simply threw the same error of "too many links" one after some time not even touching or doing anything.

So on the screen above I'm using the "15 seconds ADB / Fastboot" one with all options marked as yes including the driver installation ones as the other ones won't work or sort of...

I'm not sure if it is from my drivers or the phone itself or the firmware from it, as it is its stock one. Thus I also ran the cmd even as administrator and not before, both ways but didn't changed ****.

And also lastly I found out a silimar case to the one I got from another forum and another user by searching in google:

https: //android.stackexchange.com/questions/187159/what-is-csc-fastboot-mode-and-how-to-get-rid-of-it

(you'll have to remove the space in between the "https:" and the "//" in order to get the link as I cannot post it straight due to account limitations)

Thanks for reading and I hope someone can come up with a solution or anything as soon as possible.