Develop Bugs

[Q] Kindle 1st gen working BUT "Unknown Device" in Device Manager

Hi all.
I have seen this in another kind of devices but haven't found thread related about Kindle Fire (1st gen).
A little introduction:
- My kindle was in CM10 and I noticed it started to be detected as Unknown Device in Windows, so
- I used TWRP to flash 6.3.1 stock ROM BUT forgot to wipe before flashing and rebooting. In that moment my situation was an endless loop wih the Kindle being rebooted after 15 seconds aproximately.
- I modified a cable to make it "factory cable" but even in fastboot (plain kindle fire logo) the Unknown Device was there.
- After many tries I managed to make a Reset to factory defaults in Android in the 15 seconds
- Currently the kindle is in stock ROM but still is not correctly detected.
Of course, I have re-installed the drivers in my computer and even tried in a fresh windows installation with no previous drivers without luck. Also, booted an Ubuntu USB with SoupKit and no lsusb changes after plugin the device (just a few dmesg messages about being unable to enumerate USB device on port).
So, if some of you have any idea to try, please tell me. I have the factory cable and the back cover of the kindle removed... ready for anything!
Thank you for your time!

soukron said:
Hi all.
Also, booted an Ubuntu USB with SoupKit and no lsusb changes after plugin the device (just a few dmesg messages about being unable to enumerate USB device on port).
Click to expand...
Click to collapse
This is the part I mentioned before about dmesg messages:
Code:
[ 234.956030] usb 2-5: >new full-speed USB device number 4 using ohci_hcd
[ 235.136035] usb 2-5: >device descriptor read/64, error -62
[ 235.420038] usb 2-5: >device descriptor read/64, error -62
[ 235.700026] usb 2-5: >new full-speed USB device number 5 using ohci_hcd
[ 235.880055] usb 2-5: >device descriptor read/64, error -62
[ 236.164040] usb 2-5: >device descriptor read/64, error -62
[ 236.444025] usb 2-5: >new full-speed USB device number 6 using ohci_hcd
[ 236.852030] usb 2-5: >device not accepting address 6, error -62
[ 237.028025] usb 2-5: >new full-speed USB device number 7 using ohci_hcd
[ 237.436025] usb 2-5: >device not accepting address 7, error -62
[ 237.436037] hub 2-0:1.0: >unable to enumerate USB device on port 5
And there's no reference in lsusb:
Code:
[email protected]:~$ lsusb
Bus 001 Device 004: ID 1307:0163 Transcend Information, Inc. 256MB/512MB/1GB Flash Drive
Bus 001 Device 005: ID 0bda:8187 Realtek Semiconductor Corp. RTL8187 Wireless Adapter
Bus 002 Device 002: ID 04ca:0022 Lite-On Technology Corp.
Bus 002 Device 003: ID 046d:0a0b Logitech, Inc. ClearChat Pro USB
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
[email protected]:~$ lsusb -t
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci_hcd/10p, 12M
|__ Port 3: Dev 2, If 0, Class=HID, Driver=usbhid, 1.5M
|__ Port 4: Dev 3, If 0, Class=audio, Driver=snd-usb-audio, 12M
|__ Port 4: Dev 3, If 1, Class=audio, Driver=snd-usb-audio, 12M
|__ Port 4: Dev 3, If 2, Class=audio, Driver=snd-usb-audio, 12M
|__ Port 4: Dev 3, If 3, Class=HID, Driver=usbhid, 12M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/10p, 480M
|__ Port 9: Dev 5, If 0, Class=>ifc, Driver=rtl8187, 480M

From what I've seen, this is usually a problem with the bootloader. How or why, I don't know. That being said, Firekit w/shorting trick seems to be the most successful at resolving this issue.

soupmagnet said:
From what I've seen, this is usually a problem with the bootloader. How or why, I don't know. That being said, Firekit w/shorting trick seems to be the most successful at resolving this issue.
Click to expand...
Click to collapse
I'm trying to follow this thread http://forum.xda-developers.com/showthread.php?t=1636883 but I don't know how to check if the "short trick" is well performed or not. Is there anything I should notice? At this moment if I make the short trick and plug in the usb connector, nothing seems to be working in the kindle but dmesg is continuously showing errors like previous ones.
Regards,

Are you using Firekit? What command?
"That's a special kind of stupid. The kind that makes me laugh"

I'm still in the step of the process when I make the short trick, plug the usb and the kindle should be detected. Should I try the usbboot commands even when there's no kindle entry in lsusb output?

YES absolutely! And hold the power button for 15 seconds to make sure the CPU isn't running before attempting the short.
"That's a special kind of stupid. The kind that makes me laugh."

soupmagnet said:
YES absolutely! And hold the power button for 15 seconds to make sure the CPU isn't running before attempting the short.
Click to expand...
Click to collapse
The command is ./usbboot aboot.bin u-boot.bin; ./fastboot boot twrp-blaze-2.0.0RC0.img but it keeps stopped in waiting for OMAP44xx device....
I'm going to try a few times more. Thank you!
BTW, what are the next steps? Because this unit is working properly but the USB port to transfer data between computer and device: it boots, it loads stock firmware, and works properly.

soukron said:
The command is ./usbboot aboot.bin u-boot.bin; ./fastboot boot twrp-blaze-2.0.0RC0.img but it keeps stopped in waiting for OMAP44xx device....
I'm going to try a few times more. Thank you!
BTW, what are the next steps? Because this unit is working properly but the USB port to transfer data between computer and device: it boots, it loads stock firmware, and works properly.
Click to expand...
Click to collapse
Are you using a 32bit or 64bit machine? If you have SoupKit installed, option 2 should have installed 32bit libs, but sometimes it fails...mostly due to Ubuntu servers and them trying to make 32bit libs obsolete. If you're running a 64bit machine, try installing 32bit libs again and see if you get any errors.
Code:
sudo apt-get install ia32-libs
Also since you have SoupKit installed, run it and select option 4 to launch the Firekit. There's really no difference in using Firekit and manually entering the commands for Rekindle but it makes things a little easier. Select "usb_install_fff_twrp". The important thing to know about the "usb_fix_parts..." and "usb_install..." commands in Firekit is that they both use "fastboot boot ..." instead of "fastboot flash ..." to install TWRP and FFF. Meaning, if you reboot or shut the device down before actually installing a bootloader, the device won't turn back on and you'll have to do the shorting trick again.
That being said, from the moment you make the short, you only have about 2 seconds to plug the device in and have Linux detect it before the CPU resets and you have to start all over again.
Hold the power button for 10-15 seconds to make sure the CPU is off before attempting the short.
Launch Firekit and select "usb_install_fff_twrp". When the command is run, you will get the "Waiting for OMAP4 device..." prompt. Let it wait.
To do the shorting trick...
Something I have found to be most useful in this situation is to use a sharp pair of tweezers or safety pin to make the short.
Keep the device flat on a desk or table with the USB connection pointed away from you. Use one hand to hold the short, one hand to plug the device in, and use your body against the other end of the device as leverage as you plug it in.
Using a safety pin, stick the sharp end of the safety pin into the short point and press it in a little to keep it from sliding off when you plug the device in. Squeeze the other end of the safety pin or tweezers to make contact with the metal frame and immediately plug the device in while holding the short.
If the tweezers slip or make contact with the frame before you are ready, hold the power button for 10-15 seconds to make sure the device is completely shut down and try again.
You should see something going on in the terminal to let you know it's working...let it finish.
It might take a few attempts to get the timing right but persistence (and practice) is key...don't give up.
Follow these instructions and I'm positive you'll get it working again. Good luck.

OK, it's a matter of time and try it.
My computer is 64bit, but I am booting a LiveUSB with Ubuntu 12.10 32bits, so no problem around it.
About the short, one friend of mine solded a thin wire in the point in the board and I only have to connect the other side to the wire to the frame each time, so it also seems to be fine. http://forum.xda-developers.com/attachment.php?attachmentid=1045562&d=1336355873
My main concern: once I manage to make properly the short trick and the process goes forward, what will be the next step? What should I expect of this usb_install_fff_twrp command? Will it fix the hardware detection problem automatically?
Thank you again for all your help, I know you answer a lot this kind of questions and your help is very valuable.

soukron said:
OK, it's a matter of time and try it.
My computer is 64bit, but I am booting a LiveUSB with Ubuntu 12.10 32bits, so no problem around it.
About the short, one friend of mine solded a thin wire in the point in the board and I only have to connect the other side to the wire to the frame each time, so it also seems to be fine. http://forum.xda-developers.com/attachment.php?attachmentid=1045562&d=1336355873
My main concern: once I manage to make properly the short trick and the process goes forward, what will be the next step? What should I expect of this usb_install_fff_twrp command? Will it fix the hardware detection problem automatically?
Thank you again for all your help, I know you answer a lot this kind of questions and your help is very valuable.
Click to expand...
Click to collapse
When the OMAP4 device is detected, you will see something similar to this in the terminal:
http://forum.xda-developers.com/attachment.php?attachmentid=1262650&d=1345043823
That will temporarily install the bootloader, which is likely the cause of Linux not being able to detect it in the first place. When you see the yellow triangle on your Kindle, you'll know the Firekit worked. But you still have to permanently install the bootloader via fastboot (or TWRP if accessible) before you reboot the device.
Will it work to get Linux to detect it? Most likely, but there's no way to know for sure until you get a new bootloader installed.
On second thought...
I just realized you may not even have to do that in the first place. Lucky you? If your device is working properly as you said, boot into Android and open up the Terminal Emulator. Make sure the u-boot.bin is on your sdcard and enter the following:
Code:
su
dd if=/sdcard/u-boot.bin of=/dev/block/mmcblk0p2
reboot
See if that works.

Yes, working with stock ROM but without root access. If there's any way of rooting it without connecting it to the computer I can do it and then use dd to override the block device.

soukron said:
Yes, working with stock ROM but without root access. If there's any way of rooting it without connecting it to the computer I can do it and then use dd to override the block device.
Click to expand...
Click to collapse
Nope...you need root access to use the 'dd' command.

soupmagnet said:
Nope...you need root access to use the 'dd' command.
Click to expand...
Click to collapse
Dude, thank you for your all work but I'm giving up. I'll close it and use it without data cable. I always can use dropbox like applications to transfer data.
Again, thank you, I really appreciate your help.

soukron said:
Dude, thank you for your all work but I'm giving up. I'll close it and use it without data cable. I always can use dropbox like applications to transfer data.
Again, thank you, I really appreciate your help.
Click to expand...
Click to collapse
If y wer on windows, u could have just grabbed a copy of kindle fire utility and had rooted it in merely seconds..
Sent from my GT-I8350 using Board Express

prahladvarda said:
If y wer on windows, u could have just grabbed a copy of kindle fire utility and had rooted it in merely seconds.
Click to expand...
Click to collapse
Unfortunately, it won't work in this situation.

[Q] Data transfer via MTP on ubuntu

Hi there,
has anyone tried to use the MTP file transfer option of the Fairphone with Ubuntu (I'm using 13.04 at the moment). It seems that the phone is recognized by my system:
Code:
[49875.145923] usb 1-1.2: new high-speed USB device number 12 using ehci-pci
[49875.240046] usb 1-1.2: New USB device found, idVendor=0bb4, idProduct=0c02
[49875.240057] usb 1-1.2: New USB device strings: Mfr=2, Product=3, SerialNumber=4
[49875.240063] usb 1-1.2: Product: MT65xx Android Phone
[49875.240068] usb 1-1.2: Manufacturer: MediaTek
[49875.240072] usb 1-1.2: SerialNumber: ...
but the device is not shown in Nautilus.
Who knows how to fix that?
Thanks,
Tobi

prinz.z said:
Hi there,
has anyone tried to use the MTP file transfer option of the Fairphone with Ubuntu (I'm using 13.04 at the moment). It seems that the phone is recognized by my system. but the device is not shown in Nautilus.
Who knows how to fix that?
Thanks,
Tobi
Click to expand...
Click to collapse
I guess this is more an Ubuntu issue/question than Fairphone's..
You can follow instructions here
Code:
$ sudo mtpfs -o allow_other /media/MTPdevice
Unable to open ~/.mtpz-data for reading, MTPZ disabled.Listing raw device(s)
Device 0 (VID=0bb4 and PID=2008) is UNKNOWN.
Please report this VID/PID and the device model to the libmtp development team
Found 1 device(s):
0bb4:2008 @ bus 2, dev 20
Attempting to connect device
Android device detected, assigning default bug flags
Listing File Information on Device with name: FP1
Nautilus gave me read-only access to content under the custom mount point /media/MTPdevice. dmesg gave me the same log as yours when recognizing the device...

It doesn't work for me either. But this is an issue that is usual in Ubuntu. Even though it is not an issue in Ubuntu.
* libMTP with a detailed description
* gvfs-mtp
* go-mtpfs
I use either the USB storage or PTP.
(MTP is buggy.)

Okay, I see.. With my former phone (LG O4x, cm-11) it was working flawlessly with mtp on Ubuntu, that's the rason I asked.. With the fairphone, I'm simply using adb for the moment to copy single files..
elchi1234 said:
It doesn't work for me either. But this is an issue that is usual in Ubuntu. Even though it is not an issue in Ubuntu.
* libMTP with a detailed description
* gvfs-mtp
* go-mtpfs
I use either the USB storage or PTP.
(MTP is buggy.)
Click to expand...
Click to collapse

[Q] Bricked Find 7

Hey guys. I tried to flash TeamEOS rom latest nightly on my device,and the flashing process went fine. I was using the TWRP gummified version and it said it was all successfull. This is the link,and on the download pages there is Find7 version.
http://www.oppoforums.com/threads/rom-4-4-4-teameos-the-revival-nightlies.16320/page-25
The problem is,after flashed everything,my phone died. I think i made a mistake when flashed the modem package,which is supposed to be for the find5.. I didn't thought that it could make the difference,but it might have made.
Now my phone won't start,boot or anything. Simply died. Is there anyway i could try to bring him back to life before i send it to the warranty?
I can't reach recovery,fastboot or anything
Any help would be much appreciated. Thank's a lot

bcuraman said:
Hey guys. I tried to flash TeamEOS rom latest nightly on my device,and the flashing process went fine. I was using the TWRP gummified version and it said it was all successfull. This is the link,and on the download pages there is Find7 version.
http://www.oppoforums.com/threads/rom-4-4-4-teameos-the-revival-nightlies.16320/page-25
The problem is,after flashed everything,my phone died. I think i made a mistake when flashed the modem package,which is supposed to be for the find5.. I didn't thought that it could make the difference,but it might have made.
Now my phone won't start,boot or anything. Simply died. Is there anyway i could try to bring him back to life before i send it to the warranty?
I can't reach recovery,fastboot or anything
Any help would be much appreciated. Thank's a lot
Click to expand...
Click to collapse
Okay. Try to connect your phone to your PC and see if your phone is showed as "QHSUSB BULK" Or qualcomm 9008/9006
Let me know if it shows that.
(go to device manager on pc to check that)
If it doesnt show, try taking the battery out and putting it back and then connecting to pc.

suraj.das said:
Okay. Try to connect your phone to your PC and see if your phone is showed as "QHSUSB BULK" Or qualcomm 9008/9006
Let me know if it shows that.
(go to device manager on pc to check that)
If it doesnt show, try taking the battery out and putting it back and then connecting to pc.
Click to expand...
Click to collapse
yeah: This is the result of the command line:
" 50149.656170] wlan0: associate with 9c:97:26:9d:78:05 (try 1/3)
[50149.663938] wlan0: RX AssocResp from 9c:97:26:9d:78:05 (capab=0x411 status=0 aid=2)
[50149.664014] wlan0: associated
[51146.796129] usb 1-4: new high-speed USB device number 13 using ehci-pci
[51146.928956] usb 1-4: New USB device found, idVendor=05c6, idProduct=9008
[51146.928964] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[51146.928969] usb 1-4: Product: QHSUSB__BULK
[51146.928974] usb 1-4: Manufacturer: Qualcomm CDMA Technologies MSM
[51146.929416] qcserial 1-4:1.0: Qualcomm USB modem converter detected
[51146.930584] usb 1-4: Qualcomm USB modem converter now attached to ttyUSB0

bcuraman said:
yeah: This is the result of the command line:
" 50149.656170] wlan0: associate with 9c:97:26:9d:78:05 (try 1/3)
[50149.663938] wlan0: RX AssocResp from 9c:97:26:9d:78:05 (capab=0x411 status=0 aid=2)
[50149.664014] wlan0: associated
[51146.796129] usb 1-4: new high-speed USB device number 13 using ehci-pci
[51146.928956] usb 1-4: New USB device found, idVendor=05c6, idProduct=9008
[51146.928964] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[51146.928969] usb 1-4: Product: QHSUSB__BULK
[51146.928974] usb 1-4: Manufacturer: Qualcomm CDMA Technologies MSM
[51146.929416] qcserial 1-4:1.0: Qualcomm USB modem converter detected
[51146.930584] usb 1-4: Qualcomm USB modem converter now attached to ttyUSB0
Click to expand...
Click to collapse
Great. Now download this file, http://d3bzg7dsosz4ht.cloudfront.net/OTA/Find7/FIND7WX_12_A.09_140810.tgz
Extract it. Connect your phone and then click on the msm 8974download.exe..
Wait till it turns green and then reboot your phone
Thanks to Addel from oppoforums.

suraj.das said:
Great. Now download this file, http://d3bzg7dsosz4ht.cloudfront.net/OTA/Find7/FIND7WX_12_A.09_140810.tgz
Extract it. Connect your phone and then click on the msm 8974download.exe..
Wait till it turns green and then reboot your phone
Thanks to Addel from oppoforums.
Click to expand...
Click to collapse
Hmmm if i were on a windows machine,that would be easy,but i'm running Linux Mint 17.. what shall i do then?

bcuraman said:
Hmmm if i were on a windows machine,that would be easy,but i'm running Linux Mint 17.. what shall i do then?
Click to expand...
Click to collapse
I have no idea. Sorry. Maybe use your friend's pc? OR VM?

Hi there. I too am having issues with my Find 7 as well. I just bought it today. The previous owner apparently went to flash cm11 and he soft bricked it. The phone will power on to the start screen the the screen stays black and goes on and off. I can get to fastboot but not recovery. I have read in the oppo forums that I need to push the stock recovery too it but am unfamiliar with fastboot. I am willing to pay someone to get this phone working. Any input would be greatly appreciated.

MsmDownloader works great from inside an Windows XP VMWare virtual machine.

Fire TV 1 Bricked with Marshall London HS-USB Diagnostic 9006

My Fire TV bricked and none of the described un-bricking method works.
When connecting through USB I can see "Marshall London HS-USB Diagnostics 9006 (COM21)" port in Device Manager. I also observed that MiFlash tool recognize it as "\\?\usbstor#disk$ven_qualcomm&prod_mmc_storage&rev_1.00#7&5313ab4&0&1234567890abcdef&0#{53f6307-b6bf-11d0-94f2-00a0c91efb8b}"
I have unbricked my Mi Phone using this tool and it requires a ROM containing boot, kernel, system etc. images and other flashing scripts. Do we have similar kind of ROM available for Fire TV?

I am in the same boat.

Did you try this

{ParanoiA} said:
Did you try this
Click to expand...
Click to collapse
Looks like I goofed up big time. Now I only see QHUSB_DLOAD and I am not able to see any drive on OSX or Linux. I am suspecting the Mi Flash tool that I was using to check it did something. Instead of showing "\usbstor#disk$ven_qualcomm&prod_mmc_storage&re v_1.00#7&5313ab4&0&1234567890abcdef&0#{53f6307-b6bf-11d0-94f2-00a0c91efb8b}" it is now showing COM20.
On linux I tried this command
Code:
dmesg | tail
and it shows following output
usb 1-2: new ISB device strings: Mfr=1, Product=2, SerialNumber=0
usb 1-2: Product: QHSUSB_DLOAD
usb 1-2: Manufacturer: Qualcomm CDMA Technologies MSM
usbcore: registered new interface driver usbserial
usbcore: registered new interface driver usbserial_generic
usbserial: USB Serial support registered for generic
usbcore: registered new interface driver qcserial
usbserial: USB Serial support registered for Qualcomm USB modem
qcserial: 1-2:1.0: Qualcomm USB mode converter detected
usb 1-2: Qualcomm USB modem converter now attached to ttyUSB0
Any help in this regard is appreciated.

{ParanoiA} said:
Did you try this
Click to expand...
Click to collapse
Ok.. I have a Linux VM (ubuntu 16.x) booted up, and the FireTV is recognized as a /dev/sdb device. I have downloaded the .bin file from amazon. How do I decompress the BIN file to get the images folder to dd over to the firetv partitions?
I am a linux newbie, so missing that key step
NEVERMIND - Figured it out

Thanks Rbox & {ParanoiA} for hte unbricking guide. I successfully recovered my FireTV and am back up and running.

Rbox/{ParanoiA} any way to recover my fire TV from the state it is currently in.
One more observation. Now it is showing the connection as "Marshall London HS-USB Diagnostic 9008"

After googling a bit I zeroed in that it should be recoverable. I a following this link
http://www.androidbrick.com/unbrick-all-qualcomm-snapdragons-from-qualcomm-hs-usb-qdloader-9008-if-you-have-the-right-kind-of-rom-qhsusb_dload/
However I need following files (MPRG8064T.hex and 8064T_msimage.mbn) in addition to what mentioned in this. I am not able to find anything other than MPRG8064.hex and 8064_msimage.mbn anywhere. I am not sure whether I can use these files or not

MPRG8064.hex and 8064_msimage.mbn did not work
Can Anyone provide MPRG8064T.hex and 8064T_msimage.mbn file?

Just uploaded the requested - http://www.mediafire.com/download/jqfx835f5ompvf4/q.7z
the link contains the non T variant of the requested files

In an attempt to get the device from 9008 to 9006 mode, I attempted http://cellphonetrackers.org/qhsusb_dload-fix-qualcomm-soc.html without success

After two months of reading and testing every trick i've read on blogs, youtube, russian or chinese forums, and still at the exact same place. No matter what I do or try, I can't get out of the bloody 9008 state. Did any of you had any breakthrough on the problem? Thanks!

[D855P] Model "Unknow" in LGUP, after use LG FlashTool

Hi everybody.
I try to install Cyanogenmod on my LG G3 (model D855P bought on Brazil), but the install stopped after some minutes before finish.
I received the LG loop logo. After read some topic's about this error, I try to write a original firmware (.TOT D855AT European). The install runing with any problems. But now, my smartphone is show in LGUP with "Unknow" in the model, but show me the connection port is COM3.
I used the Boarddiag to verify the phone and any error founded. I try to re-write the SDRAM with files extract from LGD855PAT-01-V10a-370-02-JUN-10-2014-16G-32G+3, but not work. I install, but the problem continue the same.
I try the process when you change the COMxx port to COM41 and using a specified .dll, but the process stop in the first steps of validation.
Now, when I turn-on my phone, after some minutes I receive the message: Kernel Crash Handler. If I press Power+Down, the fastboot interface is started, but when I try to access using ADB (in Linux or Windows 10), the device is not listed with command ADB DEVICES. In the Windows 10, my device is recognize in "Manager Devices" with the name "Kedacom USB Device > Android Bootloader Interface".
I try to create the file on .android folder, but not work.
When run the command DMESG in the Linux, my device have this information:
usb 1-5: new high-speed USB device number 3 using ehci-pci
usb 1-5: New USB device found, idVendor=18d1, idProduct=d00d
usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 1-5: Product: Android
usb 1-5: Manufacturer: Google
Anyone have some idea to help me about this problem???

fdelago said:
Hi everybody.
I try to install Cyanogenmod on my LG G3 (model D855P bought on Brazil), but the install stopped after some minutes before finish.
I received the LG loop logo. After read some topic's about this error, I try to write a original firmware (.TOT D855AT European). The install runing with any problems. But now, my smartphone is show in LGUP with "Unknow" in the model, but show me the connection port is COM3.
I used the Boarddiag to verify the phone and any error founded. I try to re-write the SDRAM with files extract from LGD855PAT-01-V10a-370-02-JUN-10-2014-16G-32G+3, but not work. I install, but the problem continue the same.
I try the process when you change the COMxx port to COM41 and using a specified .dll, but the process stop in the first steps of validation.
Now, when I turn-on my phone, after some minutes I receive the message: Kernel Crash Handler. If I press Power+Down, the fastboot interface is started, but when I try to access using ADB (in Linux or Windows 10), the device is not listed with command ADB DEVICES. In the Windows 10, my device is recognize in "Manager Devices" with the name "Kedacom USB Device > Android Bootloader Interface".
I try to create the file on .android folder, but not work.
When run the command DMESG in the Linux, my device have this information:
usb 1-5: new high-speed USB device number 3 using ehci-pci
usb 1-5: New USB device found, idVendor=18d1, idProduct=d00d
usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 1-5: Product: Android
usb 1-5: Manufacturer: Google
Anyone have some idea to help me about this problem???
Click to expand...
Click to collapse
Any luck unbricking your device?
I have the same problem here