Develop Bugs

[Q]stuck on kindle fire logo - tried KFU&Soupkit

Kindle stuck on kindle fire logo, try using kindle fire utlity with windows xp and 7(64bit):
xp> 'unkonown device' ("install failedand (unsigned)", In system properties I changed the default driver signing option but nothing)
KFU adb status offline and boot status unknown SOUPKIT nothing
w7> driver ok but unknown usb device when plugin. nothing with KFU or linux+soupkit
tried all with normal usb cable. then opened the back and tried with "short the point". nothing. retry today with a factory cable...nothing!
used also firekit in linux...nothing at all.
I don't know anything about this kindle, because I got it from a friend that got it somewhere!!

In Linux, what is the output of 'lsusb' with the device plugged in?
"That's a special kind of stupid. The kind that makes me laugh."

[email protected]:~$ lsusb
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
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 079b:004a Sagem XG-760A 802.11bg
Bus 001 Device 005: ID 058f:6387 Alcor Micro Corp. Transcend JetFlash Flash Drive
Bus 001 Device 006: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader
Bus 003 Device 002: ID 0461:0010 Primax Electronics, Ltd
Bus 003 Device 003: ID 0461:4d20 Primax Electronics, Ltd HP Optical Mouse
ADD> could be a problem of the kindles usb? cable ok, tried 2 different

When you tried the short trick, did you use it with Firekit? How exactly did you implement it? Did you make sure the device was completely powered down before trying it?
"That's a special kind of stupid. The kind that makes me laugh."

used firekit and soupkit...tried different ways. kindle completely powered down, short trick, reconnected usb. <waiting for divice> ...so repowered down, ecc ecc...nothing. tried also with factory cable, same results

trinitylau said:
used firekit and soupkit...tried different ways. kindle completely powered down, short trick, reconnected usb. <waiting for divice> ...so repowered down, ecc ecc...nothing. tried also with factory cable, same results
Click to expand...
Click to collapse
Are you using a 32 or 64 bit linux install?
"That's a special kind of stupid. The kind that makes me laugh."

ubuntu-12.04.1-desktop-i386.iso

so...there is something that I can try to do? some advice, some procedure to follow?

In windows, does device manager recognize it?

trinitylau said:
so...there is something that I can try to do? some advice, some procedure to follow?
Click to expand...
Click to collapse
[Edit:] Confused this with another thread

awidawad said:
In windows, does device manager recognize it?
Click to expand...
Click to collapse
xp> 'unkonown device' ("install failedand (unsigned)", In system properties I changed the default driver signing option but nothing)
w7> driver ok but unknown usb device when plugin.

soupmagnet said:
All I can really say is that Firekit works for what it does. What it can't do is make up human error. And I have no way to see exactly what your are doing so I have no idea if your problem is related to your procedure/technique/whatever, or if there is something more going on. The best advice I can giver you is to keep trying...be persistent and don't give up.
Click to expand...
Click to collapse
I followed all the instructions ... keep trying!!
always better to try with linux?

trinitylau said:
I followed all the instructions ... keep trying!!
always better to try with linux?
Click to expand...
Click to collapse
SoupKit will only work with Linux...
Yes, use Linux.
"That's a special kind of stupid. The kind that makes me laugh."

I'll post a custom driver in a bit try it on windows 7 when I post link
---------- Post added at 01:32 PM ---------- Previous post was at 12:55 PM ----------
HERE is the custom driver. Replace the driver in the KFU driver folder with this one, then re-run the driver installation (run.bat) and rename it to "android_winusb.inf" without the quotes

soupmagnet said:
SoupKit will only work with Linux...
Click to expand...
Click to collapse
yes, sorry, I meant to continue with linux

trinitylau said:
yes, sorry, I meant to continue with linux
Click to expand...
Click to collapse
Try the windows 7 drivers... It might work

awidawad said:
I'll post a custom driver in a bit try it on windows 7 when I post link
Click to expand...
Click to collapse
ok, thanks! try also this way!

nothing...driver install without problems but still "unknown usb"

trinitylau said:
nothing...driver install without problems but still "unknown usb"
Click to expand...
Click to collapse
Very strange... What firmware was your device running?

I don't know, I got it from a friend, stuck at kindle fire logo

[Q] Kindle Fire stuck at boot animation after LCD Density change

Hi everyone,this is my first post on the XDA forum.Recently,i had installed the Stock Jelly Bean 4.2.1_r1 for the Kindle Fire made by Hashcode.Things have been working well,untill today.I found an app call LCD density modder(2.4.2) and i installed it.After i apply my density change(160 to 200),the system reboot.However,it only passed the Kindle Fire Red logo and then stuck at the Jelly Bean 4.2.1 animation boot.
I have tried to connect the Kindle Fire to my pc and tried to use the Kindle Fire Utility but my ADB is set at offline.I have tried everything,uninstall driver to normal boot-turn off device trick,but none of them has work.I'm a newbie,so this is really confusing for me right now.If anyone know how to fix this,please help me !!!
P.S:Sorry for my bad English.It isn't my native language !!!
UPDATE:
So I've try using Ubuntu 12.10, install Soupkit, It didn't work: ADB status is Offline.
Switch to Ubuntu 12.04. and tried to test something, and I think maybe there is sth wrong.
First I hit this, with my KF plug in
[email protected]:~$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 003 Device 002: ID 046d:c52f Logitech, Inc. Wireless Mouse M305
Bus 001 Device 003: ID 0cf3:3005 Atheros Communications, Inc. AR3011 Bluetooth
Bus 001 Device 004: ID 058f:a014 Alcor Micro Corp.
Bus 001 Device 005: ID 0bda:0139 Realtek Semiconductor Corp.
Bus 002 Device 003: ID 8564:1000
Bus 002 Device 007: ID 1949:0005 Lab126
Click to expand...
Click to collapse
Then I remove my KF and did it again, this time it showed this
[email protected]:~$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 003 Device 002: ID 046d:c52f Logitech, Inc. Wireless Mouse M305
Bus 001 Device 003: ID 0cf3:3005 Atheros Communications, Inc. AR3011 Bluetooth
Bus 001 Device 004: ID 058f:a014 Alcor Micro Corp.
Bus 001 Device 005: ID 0bda:0139 Realtek Semiconductor Corp.
Bus 002 Device 003: ID 8564:1000
Click to expand...
Click to collapse
So my guess it my PC still recognised it as Lab126.
Then I did another test, I type in
sudo gedit /etc/udev/rules.s/51-android.rules
Click to expand...
Click to collapse
And this showed up:
# adb protocol for blaze / otter (Amazon Kindle Fire)
SUBSYSTEM=="usb", ATTR{idVendor}=="1949", MODE="0666", OWNER="root", GROUP="androiddev", SYMLINK+="android%n"
# fastboot protocol for blaze / otter (Amazon Kindle Fire)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0660", OWNER="root", GROUP="androiddev", SYMLINK+="android%n"
Click to expand...
Click to collapse
So I think that my system need some adjust. Can anyone help me please?
Update: I saw that on when I got lsusb it supposed to say Bus 003 Device 026: ID 1949:0006 Lab126 or something. but I got 0005.
Maybe this is the problem, I don't really know. Can anyone take a look and see what happend to my KF Id.

if you boot to your recovery (twrp) you should have adb available.
then you can set the density back in the build.prop in the system folder.
take care of the permissions !

But i can't boot into TWRP.
My kindle doesn't show up the yellow triangle.It just show up the regular kindle fire logo

gave you a pm ...

I'm trying on Soupkit but it said that "Device Offine", and I really don't know what to do next, first time on Ubuntu and have tried some solutions but they just don't work. Anyone can help?

with ubuntu no drivers are needed - try a other cable first - then maybe contact soupmagnet for further help

Two things...
1) In your PM you said "sudo gedit /etc/udev/rules.d/51-android.rules" opens a blank document, but here you state otherwise. So which is correct?
2) I've seen the PID of 0005 in only one other situation before and it resulted in having to replace the bootloader. But your device has moved past the bootloader and on to the boot animation so your situation may be different...or not. You could try to change your udev rules to match the PID indicated by the device and then reload the udev rules:
Code:
sudo udevadm control --reload-rules
...if that doesn't work, you'll need a factory cable to get the device into fastboot so you can access recovery. Even then, you may be looking at usbboot to fix the bootloader.
"That's a special kind of stupid. The kind that makes me laugh"

1) In your PM you said "sudo gedit /etc/udev/rules.d/51-android.rules" opens a blank document, but here you state otherwise. So which is correct?
Click to expand...
Click to collapse
The PM was wrong, the code when I used was wrong, I type in
Code:
sudo gedit /etc/[B]e[/B]dev/rules.d/51-android.rules
So It was obviously wrong ( but I copy the code from your thread )
Gonna try your suggestion now, Right now I'm in Window so can't try it yet.
Try to get a factory cable in a day or two. May have to build one myself because I live in Vietnam. Or I can try to buy one from China, idk.
Posting the result soon, I hope.

Can one of you guys PM me? I came through a page on the Internet (which XDA won't allow me to post) and I think I found a guy who successfuly solved one similar problem. But I don't understand what he said, so can you help me. The link is on linuxsleuthing blogspot, page :Rubbing Sticks: Lighting The Kindle Fire . Plz have a quick look

raulmadrid1998 said:
Gonna try your suggestion now, Right now I'm in Window so can't try it yet.
Try to get a factory cable in a day or two. May have to build one myself because I live in Vietnam. Or I can try to buy one from China, idk.
Posting the result soon, I hope.
Click to expand...
Click to collapse
What an interesting coincidence...the one other situation where I've seen a PID of 0005 was from a guy in Vietnam. I wonder if there is a connection somehow.
raulmadrid1998 said:
Can one of you guys PM me? I came through a page on the Internet (which XDA won't allow me to post) and I think I found a guy who successfuly solved one similar problem. But I don't understand what he said, so can you help me. The link is on linuxsleuthing blogspot, page :Rubbing Sticks: Lighting The Kindle Fire . Plz have a quick look
Click to expand...
Click to collapse
Everything that guy is talking about, is done automatically in SoupKit when you install it.
Get your factory cable then we can work from there.

Please help
b63 said:
gave you a pm ...
Click to expand...
Click to collapse
My kindles TWRP is gone after i tried installing the kindle os so i can remove jelly bean. Now my kindle wont boot, and wont show up in KFU so i can fix it. When i turn it on it show KINDLE FIRES original logo bright then black outs in like 5 seconds and show it again with a dimmer light. Do you have any idea how i can fix this because ive been searching for 4 weeks now and cant find one thing. thank you.

4 weeks really? Okay well a couple things did you do a full wipe when you flashed stock? My guess is no. What was the charge level of your battery when you flashed update.zip? If you didn't do a full wipe your kindle is stuck trying to handle the data left behind. This requires a factory cable to fix. If your battery was near depleted when you flashed it the problem could be compounded by a 5 second boot loop. My guess is the prior improperly flashing of stock without a full wipe buying a cable and leaving it on charger is your best bet for a fix. Cables can be puchased here http://forum.xda-developers.com/showthread.php?t=1392693 post 9 and worth every penny. Good luck

Another bricked Kindle Fire post. No fastboot, no adb, help!

First of all, I've spent many, many hours reading everything and trying everything I could find so sincere apologies if I have missed the solution to my problem.
So I have a Kindle Fire which I got months ago and have never been able to make work. It appears to have been almost completely wiped. It can do two things as of now:
1. Be stuck in a bootloop: displays FireFireFire logo, restarts, rinse, repeat.
2. Get into TWRP
Regardless of which of these states the device is in, neither my Windows PC (which has drivers, SDK, tools etc installed) OR my Ubuntu machine (on which I used SoupKit to install the necessaries) can see the device. It doesn't show in Device Manager in Windows and neither fastboot nor adb show any entries for the device when I run them on EITHER platform and in either of the states I can get the device into.
Any input from people more experienced than me would be appreciated. I got a factory cable in the post today so if that will help I have that option available to go. Oh and finally solutions using my Ubuntu machine rather than the Windows one would be strongly preferred although I can do either if I have to.

Boot into TWRP and see if your device shows up under 'lsusb'
...if it does, then use TWRP to "reboot bootloader" and check 'lsusb' again.

Thanks for the quick reply, and sorry for my slow reply back
The device isn't showing when I run lsusb - I assume you would have mentioned if it was not going to obviously be the KF. Anyway just in case, here is the output:
Bus 001 Device 003: ID 0ac8:c33e Z-Star Microelectronics Corp.
Bus 003 Device 002: ID 04f3:0234 Elan Microelectronics Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Anybody got any insight as to what I should do next?

kindlesean said:
Anybody got any insight as to what I should do next?
Click to expand...
Click to collapse
Is it safe to assume you don't have a factory cable?
Also, does the usb cable you're using seated tightly or is it kind of loose?
If it's loose, try this...
Enter the following command in the terminal (Linux) and try to finagle the USB to see if it is a bad connection:
Code:
while true; do lsusb | grep 'Lab126'; done
If you have a bad connection, due to the cable or USB connector, as soon as a good connection is made you will see it output to the terminal. Just remember to ctrl+c to end the loop when you're done with it.

some inforeff
Hey Thanks for the very quick reply!
I actually do have a factory cable, I bought one this week So if the factory cable is likely to be the easiest way to fix things then I have it ready.
I used multiple different USB cables on the two different machines. Should I still try the thing you mentioned or is there something else I should proceed with using the factory cable?
Thanks for the help Soup.

kindlesean said:
Hey Thanks for the very quick reply!
I actually do have a factory cable, I bought one this week So if the factory cable is likely to be the easiest way to fix things then I have it ready.
I used multiple different USB cables on the two different machines. Should I still try the thing you mentioned or is there something else I should proceed with using the factory cable?
Thanks for the help Soup.
Click to expand...
Click to collapse
Before I switched to the black USB cables from Amazon for their quick chargers, my device would do sort of the same thing. I had to pull up or push down on the connection before it would detect. If you have a factory cable made by Skorpn try that one to see if a connection is made. IIRC, Skorpn's factory cables fit very tightly so it might make a difference. Either way, try what I suggested earlier to rule out any hardware based issues with the USB.

I just tried what you suggested with both two different regular USB to Micro USB cables and also with my factory cable. In all cases there was no output in the terminal. I tried it both from TWRP and from the FFF logo screen (which no longer bootloops btw, it seems to just be hanging at the FFF logo now if I don't press power to get into TWRP).
Thanks again

Anyone able to help further? Situation is still the same as in my last post.

kindlesean said:
Anyone able to help further? Situation is still the same as in my last post.
Click to expand...
Click to collapse
You can try to usbboot, but it would require opening your device.

soupmagnet said:
You can try to usbboot, but it would require opening your device.
Click to expand...
Click to collapse
Thanks for the response.
I can open the device if necessary, right now I have a very expensive paperweight so it's not as if I have anything to lose
I assume that there are guides available for the whole procedure i.e. from opening up the device to doing the usbboot?

kindlesean said:
Thanks for the response.
I can open the device if necessary, right now I have a very expensive paperweight so it's not as if I have anything to lose
I assume that there are guides available for the whole procedure i.e. from opening up the device to doing the usbboot?
Click to expand...
Click to collapse
Check the Firekit thread in the Dev section

soupmagnet said:
Check the Firekit thread in the Dev section
Click to expand...
Click to collapse
Will do, thanks again Soup!

[Q] Recover an hardbricked SGH-T999v

Hello,
First of all, sorry for not posting in an existing thread, but this forum prevent users with less than 10 messages to post to the dev forum (where all the relevant threads seem to be). So here we go. Last year (yes, I am lazy) I hard bricked my S3. I had CyanogenMod 4.2, but some google play update soft-broked Android (apps using GooglePlay service would crash on startup). So I tried to upgrade, but the recovery said I had to update the firmware first for some reasons. I looked at XDA, looked at the "System info" page from the setting, it said the model number was SGH-T999, so I took this image and flashed it. The phone would not do anything anymore. I later found out that the model number from the setting page is incomplete and I had in fact an SGH-T999v.
Now absolutely nothing happen, no LEDs when charging, no screen, so circuit noise when I put my ear close, nothing. Over the last few months I tried to find someone with the right JTAG, but had no luck (I haven't found one, and the eBay price is simply not worth it). I tried this before ( http://forum.xda-developers.com/showthread.php?t=2439367&nocache=1 ) with no luck.
Looking at the forum, I havn't found any solution (there is a lot of signal to noise ration when searching for "hard brick"). So as you might have guessed if you read to this point, is there a way to unbrick the thing?
Thanks

Plug into the computer. If it says QHSUSB, or something to that effect, only jtag, or the method you linked above will work. From what I can tell you need to use a debrick image that is the same or newer than the firmware you are running. If you had updated to 4.3 firmware, only an image made from a device running 4.3 will work. And the sd must be at least 16gb, preferably class 6 or 10.
Also, make sure the batrery is charged still. It can drain fast when trying to fix it.
(If the debrick image is good, it should charge while turned off).
Sent from my SM-N900T using Tapatalk

Thanks for replaying, here is the dmesg:
Code:
[26066.592471] usb 1-8: default language 0x0409
[26066.592720] usb 1-8: udev 16, busnum 1, minor = 15
[26066.592725] usb 1-8: New USB device found, idVendor=05c6, idProduct=9008
[26066.592729] usb 1-8: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[26066.592733] usb 1-8: Product: QHSUSB_DLOAD
[26066.592737] usb 1-8: Manufacturer: Qualcomm CDMA Technologies MSM
[26066.592862] usb 1-8: usb_probe_device
[26066.592867] usb 1-8: configuration #1 chosen from 1 choice
[26066.592976] usb 1-8: adding 1-8:1.0 (config #1, interface 0)
I see there is a "DLOAD" string, Is there anything good in that. How do I know if I am in download mode if the screen doesn't open and adb doesn't see it?

If you see the QHSUSB_DLOAD, it means its bricked. Only a jtag repair or the debrick method in development section will fix.
Look in device manager on the computer, does it have the QHSUSB DLOAD there?
Sent from my SM-N900T using Tapatalk

I already know it is bricked I have no doubts about that
I use linux, so dmesg is as close as I can get to a device manager, lsusb also show
Code:
Bus 001 Device 017: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
Bus 001 Device 015: ID ffee:0100
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 003: ID 046d:c043 Logitech, Inc. MX320/MX400 Laser Mouse
Bus 002 Device 002: ID 046d:c22d Logitech, Inc. G510 Gaming Keyboard
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Whan you say "jtag or debrick method in development section will fix.", if that method the link I mentioned above. I have tried with a 16gb class 10 sd card. What is supposed to happen. My naive guess would have been than adb would list the device, but it doesn't

just to be sure I did this:
Code:
badblocks -s -w -t 0xff /dev/sdc
before flashing the rom using dd. It didn't worked. I also plugged my scope on the 2 pins on the back (I guess they are to "download" the raw radio signal) and nothing happen when I press the vol down + home + poweron buttons. At least no noise my scope can detect.

When you have the debrick method working, you should be able to at least boot download mode, possibly recovery and system as well.
Id try again, with a different sd card if possible. Otherwise youll probably have to send it somewhere for jtag.
Sent from my SM-N900T using Tapatalk

ok, last question. There is 2 images
SGH-T999v ***NOT FOR 4.3*** Debrick Image
SGH-T999v 4.3 only Debrick Image @cLogic for the T999v 4.3 upload
Click to expand...
Click to collapse
I picked the "not for 4.3" one. Before the brick, I had 4.2.2. But I tried to upgrade to the newer firmware to upgrade to 4.4. Did I picked the right image (as a mater of fact, I already tried both, but I am curious)? I have no other SD card to test with, so I guess it is time to consider being lazy and sending the thing to jtag
Thanks for your help

You mean you were on 4.1.2 right? If so, the first should work, unless, when you attempted to update to 4.3 it wrote the 4.3 bootloader. Like I said though, id try again. 1st with the 4.1.2 image, then with the 4.3 image.
Also, one of the canadian carriers has 2 4.3 builds out. If you are with this carrier, the first 4.3 image likely would not work on the latest build. This probably wont apply since you bricked while on 4.1.2 and havent been able to boot at all since then.
It's your call if you want to send it for jtag repair, its not cheap though. Maybe someone will let you borrow another sd card?
Sent from my SM-N900T using Tapatalk
---------- Post added at 04:12 AM ---------- Previous post was at 04:08 AM ----------
Just reread your op. Did the brick occur when you tried to flash the T999 firmware? How did you ago about trying to update? I only ask because odin shouldnt have tried to flash when it detected your model was not the T999.
Sent from my SM-N900T using Tapatalk

Maybe ODIN cannot detect the difference between T999 and T999v? I was on Android 4.2 (CyanogenMod 10.** nightly), the last build before they forced users to upgrade to the newer firmware. I was trying to install KitKat. Yes, I tried to flash the T999 firmware on a T999v, the device shut down to never give a sign of life again. I was aware of my mistake a few minute later... At first I wanted to try to JTag it myself, but I haven't found anyone with a Riff JTAG so far and 200$ is more expansive then the phone itself.

Odin should detect all variants. Im really surprised it bricked your phone as it should have failed at the md5sum check. I checks the bootloader version in download mode, so it wouldnt matter what rom you have. Were you using an older version such as 1.85?
Another option is if you have insurance. Still expensive, but less than $200.
Sent from my SM-N900T using Tapatalk

Thank you!!!! Soooooo much! I at least got my phone to boot and Odin was able to see it. I still have more to do but it's progress! I should've finish doing this before ordering a JTag but I'm sure it'll come in handy in the future.

[SOLVED] help resetting back to stock (flo) (Q)

hi, I just installed the beta build of the AOSP Oreo Rom and soon after finding working-ish gapps twrp was gone, and I hadn't had a chance to root yet, and so i went to my computer to manually flash recovery but my device refuses to get recongized, i have installed latest google and universal drivers, but they dont show up for me to set them to my nexus. Im running Latest win10 on my desktop, using a known good usb cable and have switched between the only usb 2.0 ports i have (2) i've tried in normal boot state and in fastboot, but the drivers wont match up to proceed. does anyone know anything about this, is this an issue with win10 or is it something else?

Do assuming that no one has encountered this before I guess I'll just wait until a app that can root comes out for Oreo and hopefully that can get me fixed up but if in the meantime someone comes across this and actually has some insight any help would be very much appreciated.

deathblade said:
someone comes across this and actually has some insight any help would be very much appreciated.
Click to expand...
Click to collapse
Since fastboot does not work then do the following:
win10 may be broken, check for flo ID = 18D1:4EE0 using alternative OS - if it still does not work then...
repair broken N7 USB port or re-seat the wide silver cable to fix USB data lines
:good:

Thank for your suggestion, I'm downloading the iso right now, will post back after following instructions, hope this works

ok, just followed your instructions, and this is what i got
[email protected] ~ $ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 13fe:5500 Kingston Technology Company Inc.
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 004: ID 04f2:b40e Chicony Electronics Co., Ltd HP Truevision HD camera
Bus 002 Device 003: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[email protected] ~ $
I dont see the ID you are referring to

Also I reseated the cables with no change and visually inspected the port and solder joints and all seem ok, here are a few pics ( I apologise about any quality issues, I'm not a photographer) EDIT: so I verified the data connection works just fine, was able to view contents on an otg flash drive, is there anyway to use an otg flash drive to force auto install a custom recovery?

deathblade said:
EDIT: so I verified the data connection works just fine, was able to view contents on an otg flash drive
Click to expand...
Click to collapse
I see that your laptop has both USB2 and USB3 ports. Please boot N7 in fastboot mode, connect it to USB2 then USB3 while checking lsusb for the ID. Note that the ports use different PC hardware and drivers and one of them appear to be either unsupported or faulty.
Also "a known good usb cable" may be good for charging but not for data transfer so just try another one.

Had a comparable issue recently due to win10 preferring some default driver over Google driver for fastboot.

k23m said:
I see that your laptop has both USB2 and USB3 ports. Please boot N7 in fastboot mode, connect it to USB2 then USB3 while checking lsusb for the ID. Note that the ports use different PC hardware and drivers and one of them appear to be either unsupported or faulty.
Also "a known good usb cable" may be good for charging but not for data transfer so just try another one.
Click to expand...
Click to collapse
Ok just tried with usb 2 and 3.0 ports same result, but oddly the listing does differ from my previous, it is now show an Intel device (I assume my CPU or a chipset) that wasn't listed before. But still no Nexus. Will try with a different cables later today as I have to hunt one down (just moved)

ok, so i just found another cable (with builtin otg usb port ) and even in windows 10 it worked just fine, thank you so much for your help. the cable i was using before was an anker gold tipped nylon braided 10ft usb cable, my guess is that at 10ft it has too much resistance to actually work properly for such data based tasks. I will at some point get another (smaller) anker cable to test this theory