Hi Everyone, In an attempt to fix my bricked device with all necessary flash files and drivers installed perfectly, my device is being detected under 'HUMAN INTERFACE DEVICE' as a 'USB INPUT DEVICE' in device manager, according to what i read, my device is suppose to display or be detected as "qulacom HS-USB qloader 9008" under com port. but that isn't happening, i repaired the drivers, re-installed them, formatted my pc and tried it on fresh windows installation. but still the problem is there. i even tried it on several computers but it still detects as USB INPUT DEVICE under Human Interface Devices in device manager. Now i am stuck here with my device dead for the past two weeks. please any one with an idea how to fix this issue?
i will be deeply grateful. Thanks!!
:crying:
Steps Parku said:
Hi Everyone, In an attempt to fix my bricked device with all necessary flash files and drivers installed perfectly, my device is being detected under 'HUMAN INTERFACE DEVICE' as a 'USB INPUT DEVICE' in device manager, according to what i read, my device is suppose to display or be detected as "qulacom HS-USB qloader 9008" under com port. but that isn't happening, i repaired the drivers, re-installed them, formatted my pc and tried it on fresh windows installation. but still the problem is there. i even tried it on several computers but it still detects as USB INPUT DEVICE under Human Interface Devices in device manager. Now i am stuck here with my device dead for the past two weeks. please any one with an idea how to fix this issue?
i will be deeply grateful. Thanks!!
:crying:
Click to expand...
Click to collapse
follow this
1. join in recovery mode (cwm)
2. go mounts and stroge and format system
3 reboot ur device ( Now the loop is eliminated, just a static imagen )
3. dowload drives, firmware , and QNCG
4. install drivers or repair it
5 when the step 4 is done, plug ur device on elife logo and wait for driver installation(like 10 min)
6 use winrar for descompress the firmware
7open GNQC select bp browser, and search in folder firmware a file called BP_imagen
8 try with genereal mode or emergency mode, and click dowload
i did it, its working
u must have patience dont worry
try it, its working
good luck
Still Not Helpful.
andresplata94 said:
follow this
1. join in recovery mode (cwm)
2. go mounts and stroge and format system
3 reboot ur device ( Now the loop is eliminated, just a static imagen )
3. dowload drives, firmware , and QNCG
4. install drivers or repair it
5 when the step 4 is done, plug ur device on elife logo and wait for driver installation(like 10 min)
6 use winrar for descompress the firmware
7open GNQC select bp browser, and search in folder firmware a file called BP_imagen
8 try with genereal mode or emergency mode, and click dowload
i did it, its working
u must have patience dont worry
try it, its working
good luck
Click to expand...
Click to collapse
Actually my device doesn't even come on for me to do all that you said, i tried repairing drivers and all that but it still detects as USB INPUT DEVICE under HUMAN INTERFACE DEVICES. i need my device to detect as qualcomm device before GNQC downloader can detect it. my issue is very different here. because GNQC can't see my device since my device is not being detected the rightful way after all. i will deeply appreciate the solution. Thanks
did u fix it??
U can fix ? I have the same problem since three weeks and nothing... this a a sh*t... only recognized by HID... In other ocassion before of this, i can flash my Gionee but now i cant:crying:
Another one here who saw how the phone bricked after being flashed with GnQc, now when I plug the Usb on the Pc or with wall charger, the red light keep lit and it seems like it will like this forever. I am thinking of trying to get out the screen and disconnect the battery, seems like the phone is stuck on some strange mode.
Thanks.
This feel that not have solution....
Can any one fix it ?
i also got stuck . have given to gionee care they are unable to figure what was the actuall problem
Steps Parku said:
Actually my device doesn't even come on for me to do all that you said, i tried repairing drivers and all that but it still detects as USB INPUT DEVICE under HUMAN INTERFACE DEVICES. i need my device to detect as qualcomm device before GNQC downloader can detect it. my issue is very different here. because GNQC can't see my device since my device is not being detected the rightful way after all. i will deeply appreciate the solution. Thanks
Click to expand...
Click to collapse
the problem for me is that it have recovery stock english(e3) and i can't do anything...
anyone fixed the problem? i have my gionee bricked....
Yesterday i flashed my Jiayu S3 to lolipop (i tought) and i just bricked my phone!
After reboot it was just dead.. when i plug into pc with USB i hear the connect sound and after 2 seconds the disconnect sound. This keeps on going until i pull the USB plug. When i look in DeviceManager i see it refresh after every sound, but nothing pops up (unknown device or whatever). I deletet all usb drivers with usbdeview, restart pc but still no changes.
I tried with or without battery, but without it does nothing at all.. i tried holding Vol+ or - or both or with power button, but nothing.
Read some threads about unbrick and install correct usb driver for jiayu s3, but all the options they came with does not work on my device!
I'm a little despered now and don't know what to do.. i get the feeling that my 2 weeks old phone is dead? :'(
My pc has windows 7
Did the flash with SP Flashtool 5.1516
Did not untick preload in flashtool, i guess i got the wrong preload or something??
Please help!
No one..? :crying:
Lowrida said:
Yesterday i flashed my Jiayu S3 to lolipop (i tought) and i just bricked my phone!
After reboot it was just dead.. when i plug into pc with USB i hear the connect sound and after 2 seconds the disconnect sound. This keeps on going until i pull the USB plug. When i look in DeviceManager i see it refresh after every sound, but nothing pops up (unknown device or whatever). I deletet all usb drivers with usbdeview, restart pc but still no changes.
I tried with or without battery, but without it does nothing at all.. i tried holding Vol+ or - or both or with power button, but nothing.
Read some threads about unbrick and install correct usb driver for jiayu s3, but all the options they came with does not work on my device!
I'm a little despered now and don't know what to do.. i get the feeling that my 2 weeks old phone is dead? :'(
My pc has windows 7
Did the flash with SP Flashtool 5.1516
Did not untick preload in flashtool, i guess i got the wrong preload or something??
Please help!
Click to expand...
Click to collapse
so you cannot boot into recovery or fastboot either?
Lowrida said:
Yesterday i flashed my Jiayu S3 to lolipop (i tought) and i just bricked my phone!
After reboot it was just dead.. when i plug into pc with USB i hear the connect sound and after 2 seconds the disconnect sound. This keeps on going until i pull the USB plug. When i look in DeviceManager i see it refresh after every sound, but nothing pops up (unknown device or whatever). I deletet all usb drivers with usbdeview, restart pc but still no changes.
I tried with or without battery, but without it does nothing at all.. i tried holding Vol+ or - or both or with power button, but nothing.
Read some threads about unbrick and install correct usb driver for jiayu s3, but all the options they came with does not work on my device!
I'm a little despered now and don't know what to do.. i get the feeling that my 2 weeks old phone is dead? :'(
My pc has windows 7
Did the flash with SP Flashtool 5.1516
Did not untick preload in flashtool, i guess i got the wrong preload or something??
Please help!
Click to expand...
Click to collapse
Just flash it again, but this time with "Firmware upgrade " in SP Flashtool instead of "Download". Change from KK to LL needs reepartitioning, so firmware upgrade.
The reason why you don´t "see" the S3 any longer on the pc is, that the USB storage mode from KK, which is driverless for windows, don´t work right now on LL.
Once flashed to LL you will need to install a driver, for windows to connect to the S3.
@ Dior DNA:
No i can't. Phone does nothing with the buttons. Only diference if i hold Vol - then time from connect sound and disconnect sound is a little longer.. about 10 seconds. But still nothing happens.
@1testi:
Flashtools can't see my phone. I tried it a hundred times. With battery, without battery, with Vol - and with Vol +.
When i connect the USB cable i hear the connect sound and after 2 a 3 seconds i hear disconnect sound. This goes on and on until i pull the USB cable out. In devicemanager i see a refresh going on, but nothing pops up.
I'm realy despered on what to do now?
Lowrida said:
@1testi:
Flashtools can't see my phone. I tried it a hundred times. With battery, without battery, with Vol - and with Vol +.
When i connect the USB cable i hear the connect sound and after 2 a 3 seconds i hear disconnect sound. This goes on and on until i pull the USB cable out. In devicemanager i see a refresh going on, but nothing pops up.
I'm realy despered on what to do now?
Click to expand...
Click to collapse
Why the SP Flashtool isn´t working any longer? You didn´t deinstalled the driver, did you? Just try to flash again with "Firmware Upgrade".
I don´t know a way to reinstall the driver in windows without the preloader. The only thing you can do, as far as i know, is to use a linux
pc to flash again. Linux don´t need a driver for SPF, only some rules.
Lowrida said:
@ Dior DNA:
No i can't. Phone does nothing with the buttons. Only diference if i hold Vol - then time from connect sound and disconnect sound is a little longer.. about 10 seconds. But still nothing happens.
(
Click to expand...
Click to collapse
Booting into recovery or flashtool I meant regardless of pc and/or spflashtool.
If I recall correctly:
hold volup and power boots recovery
hold voldn and power boots flashtool
If you can boot recovery then which one is it? Maybe you can restore something or manually flash preloader bin from there.
After the flash i reboot and then the connect and disconnect sound appears. So i tried differend things, but could not connect. I wanted to flash again, but flashtool did not reconice the phone and nothing in DeviceManager. That's why i thought to remove the driver and try to re-install it. But that did not help..
Holding Vol - or + button with power button or both Vol buttons with power button does nothing.. i tried to hold all combinations at least 30 seconds, but nothing at all.
I have no Linux pc or any knowhow to make a Linux pc.. or a pc to install Linux on..
One last thing you can try: remove the battery, wait a little, insert the battery again. Hold vol+ key, keep holding it and press power
button, while still holding the vol+. If you don´t see anything happening then you bricked the phone.
You will need help from a professional or at least from someone with a linux machine, sorry.
I'll try that.
You have any idea what could have caused the brick?
As i wrote above, moving from KK to LL with wrong parameter "Download" in SPF.
....and a not working recovery.
You should try this method :
darmowyinternet.net/forum/temat-poradnik-jak-uruchomic-uceglony-telefon-po-wgraniu-zlego-romu-test-point_383
unfortunately you have to translate before
Ok i tried that site with google translate and i could a little make up what they are saying.
But that is a very drastically operation, and i would like to give it some other tries before dismantling my phone.
So i googled and googled.. came here: http://forum.xda-developers.com/showthread.php?t=889128
Had enough electronics lying around from my former 27mc hobby, so searched for the right resistors,
cut up a micro usb cable and give it a try... well.. nothing! Tried for about an hour and gave up.
Then i googled on Unbrick Jigs, but for what i read they are only for Samsung phones, so i gues the trick
with the resistors were also?
So googling again... came here: http://forum.xda-developers.com/showthread.php?t=2454004
Reading the tread and the comments, someone mentioned a download for "Mediatek Driver Auto Installer".
Downloaded that and installed the drivers. Plugged in my phone and... whoohoo!! Something is happening! :silly:
My devicemanager saw an "Alcatel single RNDIS interface". I unplugged and plugged my phone a few times to
be sure it was my phone. Sooo... one step further! :good:
Then i googled on this device.. came up with all sorts of network devices, not helpfull. Then googled on Jiayu with
this device. Came up with this tread: https://www.china-devices.com/topic...vcomm-drivers-onto-your-pc-win-7vistaxp-only/
It's a tread about bricked Jiayu G3 devices, but i thought, 'What the heck, lets give it a try!'.
I downloaded the "MTK Megapack - All Tools Here!" and unpacked. Wend back to device manager and manually updated the driver
of the Alcatel device. Show all devices - browse - wend to Megapack map and there were MTK drivers for the 65xx device.
And yess.. when i plug in my phone there's the device: " MTK USB Port (COM7) "
SP Flashtools sees my phone again! :good:
Tried to flash a stock preloader, but got an error: "BROM ERROR : S_FT_ENABLE_DRAM_FAIL (4032) – [EMI] Enable DRAM failed!"
But for now that's a problem for tomorrow.. it's almost 2:30 and i have to got some sleep!
(sorry for the misspellings or telling things not clear, i'm tired and english is not my main language)
Grats!
You can google the error. This leds you in the right direction.
It's alive!!!!!! :laugh::silly::victory:
Because the kitkat stockrom i downloaded gave me the same error over and over i searched for something else.
So i downloaded TF Extreme lolipop 5.1 this morning and give it a try. And all went well. I pulled the usb plug and
pushed power button.. only vibration but nothing. Then pulled the battery and after few seconds put it back in
and try power again. Only 1 vibration.. then tried Vol + and - combinations but nothing. (dammn!)
Then plug the usb in and i saw the battery icon.. it was total empty! (because of a week trying).
So now it's charging and i hope it starts, can't wait!!
Thanx all for the effort in helping me out! :good:
Edit: Ok, so i could not wait and hit power! It shows green screen with Jiayu S3 logo and text "New Load". So i guess it's prepairing for first startup!
my s3 basic is not charging when on.. also when connected to pc thru usb, ipc shows device malfunctioning ,and there is no indication on phone..I try to connect to sp flash tool also no success..same error"usb device not recognized pops up every 2s.everything else is fine..Any method to upgrade to 5.1 now on official kk
Kinda need help, happened something similar
It happened something similar to me.
I flashed the whole ROM, bootloader included, I was very sure that my model, Jiayu S3 3GB ROM + 32GB RAM, was the correct, but still bricked my phone.
There's no problem at all when I plug it into my PC, I installed the lastest MTK drivers on windows 10, having to disable the signature enforcement.
The problem comes when I start flashing. I only mark the bootloader, then I press "Download" (on the lastest version of SP Flash Tools), and plug the phone, with the battery in it (I've tried without battery, pressing all possible combinations and does nothing), when I plug it in with the battery and pressing no buttons, the driver is detected as MTK USB Port. That's a good thing I guess. But It does not pass from the red bar, and gives me the known error "Enable DRAM Failed".
I've tried to google any possible solutions, reinstalling other version of the MTK drivers, on different versions of Windows, with other versions of official ROMs, and the result is always the same.
The only thing that's left to try is flashing it with an Ubuntu machine, which is something I do not expertise to be honest, but I'm gonna gather some info and try to do it.
However, if someone has any idea of what I might be doing wrong (excluding the part when I flashed the bootloader, I'll never do it again), I would be really grateful for any kind of help.
Thank you!
Kiei said:
It happened something similar to me.
I flashed the whole ROM, bootloader included, I was very sure that my model, Jiayu S3 3GB ROM + 32GB RAM, was the correct, but still bricked my phone.
There's no problem at all when I plug it into my PC, I installed the lastest MTK drivers on windows 10, having to disable the signature enforcement.
The problem comes when I start flashing. I only mark the bootloader, then I press "Download" (on the lastest version of SP Flash Tools), and plug the phone, with the battery in it (I've tried without battery, pressing all possible combinations and does nothing), when I plug it in with the battery and pressing no buttons, the driver is detected as MTK USB Port. That's a good thing I guess. But It does not pass from the red bar, and gives me the known error "Enable DRAM Failed".
I've tried to google any possible solutions, reinstalling other version of the MTK drivers, on different versions of Windows, with other versions of official ROMs, and the result is always the same.
The only thing that's left to try is flashing it with an Ubuntu machine, which is something I do not expertise to be honest, but I'm gonna gather some info and try to do it.
However, if someone has any idea of what I might be doing wrong (excluding the part when I flashed the bootloader, I'll never do it again), I would be really grateful for any kind of help.
Thank you!
Click to expand...
Click to collapse
Oeps it might be the same problem with the 32GB version as I have.
See http://forum.xda-developers.com/showpost.php?p=68036678&postcount=295
I am waiting for a stock ROM backup.
I have learned to never flash the original preloader again.
xtyphoon said:
Oeps it might be the same problem with the 32GB version as I have.
See http://forum.xda-developers.com/showpost.php?p=68036678&postcount=295
I am waiting for a stock ROM backup.
I have learned to never flash the original preloader again.
Click to expand...
Click to collapse
You're right, with the 32GB rom version (which is still unavaliable for public use) it worked! I still got it here, so anyone feel free to ask me the link too.
Thanks to xtyphoon and Dior DNA and everyone who made this possible, if you ever come to Girona city, I'll buy you a drink ;D
Kiei said:
[...]if you ever come to Girona city[...]
Click to expand...
Click to collapse
I was around there few weeks ago
Well. First things first. the root of the issue is probably a bad usb port i guess as it's very unstable it even sometimes reboots into download mode on its own when i plug my phone to charge or even gives a Not charging state until i replug it many times then it gives the normal charging (AC) so it's a really messy one.
that's the usual anyway i was rooted and flashed a lollipop rom normally then bugged some apps so i decided to reflash stock kitkat rom however like i said it's a bad usb connection so sometimes the flashing goes slowly and i have to replug the cable for it got smoothly again.
this time i noticed this at 15% and instead of staying in download mode stuck at that the phone rebooted and ofcourse this time only a black screen no download mode no recovery no nothing i guess a typical hard brick? this is my first time dealing with a hard brick so i didn't know what to do at all so i'm still figuring out stuff anyway i installed Qcomm drivers and checked the device manager it's the 9006 one not the 9008 and it shows many drives on my pc (windows 7 64-bit) but no partitions in windows xp 32-bit on another pc and on the laptop it gives no drives i think. i tried with SRK tools it says everything as it should but when it's done i unplug the cable then reboot however still shows many partitions and no download mode.
I don't use my phone alot however i don't own another one so i kinda need help fast please so if anyone has any ideas don't hesitate please.
Thanks in advance.:good:
Update: After following the linux method i now don't have a black screen only stuck on lg logo and still no download mode.
the phone isn't recognized by the pc at all not even 9006 or 9006
the recovery gets stuck at processing and it doesn't say fastboot either on the logo screen.
Croshio said:
Well. First things first. the root of the issue is probably a bad usb port i guess as it's very unstable it even sometimes reboots into download mode on its own when i plug my phone to charge or even gives a Not charging state until i replug it many times then it gives the normal charging (AC) so it's a really messy one.
that's the usual anyway i was rooted and flashed a lollipop rom normally then bugged some apps so i decided to reflash stock kitkat rom however like i said it's a bad usb connection so sometimes the flashing goes slowly and i have to replug the cable for it got smoothly again.
this time i noticed this at 15% and instead of staying in download mode stuck at that the phone rebooted and ofcourse this time only a black screen no download mode no recovery no nothing i guess a typical hard brick? this is my first time dealing with a hard brick so i didn't know what to do at all so i'm still figuring out stuff anyway i installed Qcomm drivers and checked the device manager it's the 9006 one not the 9008 and it shows many drives on my pc (windows 7 64-bit) but no partitions in windows xp 32-bit on another pc and on the laptop it gives no drives i think. i tried with SRK tools it says everything as it should but when it's done i unplug the cable then reboot however still shows many partitions and no download mode.
I don't use my phone alot however i don't own another one so i kinda need help fast please so if anyone has any ideas don't hesitate please.
Thanks in advance.:good:
Update: After following the linux method i now don't have a black screen only stuck on lg logo and still no download mode.
the phone isn't recognized by the pc at all not even 9006 or 9006
the recovery gets stuck at processing and it doesn't say fastboot either on the logo screen.
Click to expand...
Click to collapse
You must have flashed wrong version of the rom .
After trying the linux method, if you cant get into fastboot mode, recovery or not in download mode, then try this : http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
This requires you to open your phone so be cautious .
Thanks I followed that guide. Download mode after. Using the Windows tool instead of Linux then flash tool normally.
Three days ago, my phone went off by itself and I had a hard time starting again, it was just loading the bootanimation, I tried to reinstall the ROM, but it did not go into TWRP, although the message Recovery appears on the screen, I insisted and after several attempts, I got into the recovery, formatted everything and I installed the AICP ROM again, and I had to restart,my phone freezes in the LeEco bootloader, then again I insisted until the ROM finally started, but soon realized that it was taking too long to start (30 minutes waiting and nothing).
So I rebooted again, and from then on, I can not go into any mode anymore, trying to access the TWRP, the phone only stays on the Recovery screen until reboot after 2 minutes, when letting the phone try to start the ROM, it only stays on the LeEco screen and restart after 2 minutes, when entering Fastboot, it enters the screen in Fastboot mode, but is not recognized by the computer, not even as unknown device, the same for Download mode.
Is there anything I can try?
Doesn't seem like a a fried motherboard. In my experience, If you fried the CPU, you would still be able to access Fastboot, if you fried the GPU part of the chip, or if the LCD has failed you would feel vibrations..
Do you thin it is possible that you accidentally put the phone into EDL mode? It can sometimes be hard to get out of, and it will give you similar issues.
To leave EDL press and hold volume down and power for 1 minute or longer.
Try this
Install the All in One tool and use it to update your android and fastboot drivers. Afterwards see if the computer recognises the phone port connection by going to Control Panel>System> Device Manager* ( Even though, you may not see the drive, you will maybe still see unknown device or te port)
Maybe a Brick?
If it does not see the phone or show a unknown USB device with port 9008
Try placing the phone into EDL mode by pressing and holding the Vol Up (+) and Vol Down (-) together while simultaneously connecting the phone by USB cable to the computer. Do you see the port or phone now? If you see port 9008 you possibly are bricked, follow the steps on my unbricking thread., if you can not get back to TWRP, or fastboot,and the phone keeps a charge. Then I would think that you are definitely bricked.
Other possible issues
The issue could be the battery. Have you tried using other USB C Cables? If you can use a different usb cable let it charge for a couple of hours then see if you can get into TWRP again . If you can enter fastboot mode try reflashing TWRP, you can use the All in One tool for this.
tsongming said:
Doesn't seem like a a fried motherboard. In my experience, If you fried the CPU, you would still be able to access Fastboot, if you fried the GPU part of the chip, or if the LCD has failed you would feel vibrations..
Do you thin it is possible that you accidentally put the phone into EDL mode? It can sometimes be hard to get out of, and it will give you similar issues.
To leave EDL press and hold volume down and power for 1 minute or longer.
Try this
Install the All in One tool and use it to update your android and fastboot drivers. Afterwards see if the computer recognises the phone port connection by going to Control Panel>System> Device Manager* ( Even though, you may not see the drive, you will maybe still see unknown device or te port)
Maybe a Brick?
If it does not see the phone or show a unknown USB device with port 9008
Try placing the phone into EDL mode by pressing and holding the Vol Up (+) and Vol Down (-) together while simultaneously connecting the phone by USB cable to the computer. Do you see the port or phone now? If you see port 9008 you possibly are bricked, follow the steps on my unbricking thread., if you can not get back to TWRP, or fastboot,and the phone keeps a charge. Then I would think that you are definitely bricked.
Other possible issues
The issue could be the battery. Have you tried using other USB C Cables? If you can use a different usb cable let it charge for a couple of hours then see if you can get into TWRP again . If you can enter fastboot mode try reflashing TWRP, you can use the All in One tool for this.
Click to expand...
Click to collapse
Thanks for answering. I've tried everything.
But I can not see the smartphone when connected. USB drivers are properly installed (I used to recover other LeEco x651, x526 and x520 devices)
I left it restarting for more than hours holding the power button and volume down, no results.
The device does not appear in the Windows device manager in any way, not even as Unknown or 9008 port.
I tried several usb cables.
There is no communication with TWRP or ROM installed and neither with the computer, even though I enter into fastboot / 9008 mode. Only LeEco / recovery logo and Fastboot screen.
I think my main memory is damaged or something.
kakobr said:
Thanks for answering. I've tried everything.
But I can not see the smartphone when connected. USB drivers are properly installed (I used to recover other LeEco x651, x526 and x520 devices)
I left it restarting for more than hours holding the power button and volume down, no results.
The device does not appear in the Windows device manager in any way, not even as Unknown or 9008 port.
I tried several usb cables.
There is no communication with TWRP or ROM installed and neither with the computer, even though I enter into fastboot / 9008 mode.sl Only LeEco / recovery logo and Fastboot screen.
I think my main memory is damaged or something.
Click to expand...
Click to collapse
Well that sucks, if you feel like sending to the phone to China for repair, you can find several shops that are offering to repair any damaged Leeco for $10 and an average cost of $30 for resoldering. On the TaoBao website, use Chrome for translation. Some of their ads mention overseas repair
If it's memory it would be an easy fix for them.
If you don't want to fix it, I highly recommend the Mi8 if it's within your budget, its a perfect phone and you can find them for close to $300. My brother has a Redmi note 6 Pro which is also really nice. He paid $190.
Good Luck.
Sent from my Xiaomi MI 8 using XDA Labs
kakobr said:
Thanks for answering. I've tried everything.
But I can not see the smartphone when connected. USB drivers are properly installed (I used to recover other LeEco x651, x526 and x520 devices)
I left it restarting for more than hours holding the power button and volume down, no results.
The device does not appear in the Windows device manager in any way, not even as Unknown or 9008 port.
I tried several usb cables.
There is no communication with TWRP or ROM installed and neither with the computer, even though I enter into fastboot / 9008 mode. Only LeEco / recovery logo and Fastboot screen.
I think my main memory is damaged or something.
Click to expand...
Click to collapse
Check out this possible do it yourself fix : https://forum.xda-developers.com/showpost.php?p=79302729&postcount=71
Hello there, I was doing a flash attempting to downgrade my Lenovo M10 X606F so I could install UbuntuTouch. I had good luck with installing TWRP and finally found a missing step with the Bypass to allow SPFlashTool to see the device and actually flash to it. However when flashing a OS9 rom to the device, it immediately filled to a red 100%, and didn’t do anything after that. Waited about 10 minutes, then disconnected and tried to get to fastboot and restart the process. However now, the tablet won’t turn on, won’t go to fast boot, no response or vibration. Shows a red light when plugged in, and that’s it. When connecting to a Pc to try and fast boot via CLI, windows tells me the device is bad and couldn’t read device signature. Linux just doesn’t respond to the device at all. I’ve tried using two programs, one USBDriverFix and the others name I don’t remember to manually assign the driver to the device in windows. I can put LibUSB on it but doesn’t improve anything, and just gives errors when trying to add ABD driver to it. I’m worried it is now in a state that I won’t be able to do anything with. Any advice would be awesome.
I did the same thing. Knocked the cable during a flash. "Unknown USB Device (Device Descriptor Request Failed)" black screen, red light, won't boot anything.