Develop Bugs

Computer not "finding" device

Hi,
Before I start: I have "scoured the earth" for this, and I can't seem to find this exact problem in any other sites/threads.
I have an HTC Desire Z. I've switched a couple of times between CM7 and MIUI.
Any time I plug my device into a computer, the phone will charge, but the computer will not recognise that the device is plugged in.
The SD card works fine, because I can use it with an external reader.
The cable/drivers work fine, because I can plug in a Nexus S with the same cable.
Been tested on Windows 7, Fedora 15, Xubuntu 11.04.
Code:
~$ lsusb
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 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 003: ID 13d3:5702 IMC Networks
Bus 001 Device 002: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Would anybody be able to suggest a way I can go about rectifying this? (already: removed/cleaned sd card, rebooted computer(s), rebooted phone, changed cable)

What's your computer's OS?

As above, tested with fedora, windows 7, and xubuntu.
Sent from my HTC Vision using XDA App

denbeigh2000 said:
As above, tested with fedora, windows 7, and xubuntu.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Okay, that's what I get for not reading the whole OP. Did you try on regular old Ubuntu?

blackknightavalon said:
Okay, that's what I get for not reading the whole OP. Did you try on regular old Ubuntu?
Click to expand...
Click to collapse
I did when I had ubuntu installed. Still no dice

As an interesting side note, I think the last time this worked properly was when I was using the MoDaCo Custom ROM with Sense (Maybe this is a kernel issue/hardware driver issue?)
(Note, currently on CM7 nightly build (06252011), this feature did not work on MIUI or CM7.0.2 stable)

Did you check to see if USB debugging was enabled? Sometimes it's stupid things like that that do it.

blackknightavalon said:
Did you check to see if USB debugging was enabled? Sometimes it's stupid things like that that do it.
Click to expand...
Click to collapse
Yeah, it's been enabled the entire time
Sent from my HTC Vision using XDA App

Usually, it's one of the rules in etc/udev/rules.d, but in your case, lsusb doesn't even recognize your device. It should have a vendor ID of 0bb4, but isn't there.
Have you tried plugging your phone in someone else's computer? I suspect it is a hardware issue with your phone.

gee one said:
Usually, it's one of the rules in etc/udev/rules.d, but in your case, lsusb doesn't even recognize your device. It should have a vendor ID of 0bb4, but isn't there.
Have you tried plugging your phone in someone else's computer? I suspect it is a hardware issue with your phone.
Click to expand...
Click to collapse
Yes, I have. However, it worked under a MoDaCo custom ROM. So I'm feeling it might be an issue with the kernel... Is anybody else running CM7 or MIUI?
EDIT: (I'm operating under the impression that kernel configures the hardware for the software)

anybody had this before? :\

Ok: i've just flashed my DZ with sense 3.0 (virtuous fusion ROM), and the tethering and mounting work perfectly. So, there must be an issue with the software. Is anybody else on this forum running a DZ without sense? If so, do you get this bug?
Sent from my HTC Vision using XDA App

Fixed with a fix permissions from recovery. Thanks all round! (marking thread as solved)

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.

This device can perform faster

I get the following error message when plugging the LG G3 (D851) into one of my USB 3.0 ports:
This device can perform faster
This LGE Mobile USB Composite Device can transfer information if you connect it to a Super-Speed USB 3.0 port.
Click to expand...
Click to collapse
The port it's connected to is a Super-Speed USB 3.0 port. I have an external HDD that is correctly connected via SuperSpeed and used the same port. Though when the G3 is connected, it only connects as High-Speed.
I have the latest drivers from LG as well.
(I'm using USB Device Tree Viewer to verify this info)
Is it possible to connect this device via SuperSpeed?

Pretty sure the device itself only supports USB 2 so seems a weird message to get

joelnet said:
I get the following error message when plugging the LG G3 (D851) into one of my USB 3.0 ports:
The port it's connected to is a Super-Speed USB 3.0 port. I have an external HDD that is correctly connected via SuperSpeed and used the same port. Though when the G3 is connected, it only connects as High-Speed.
I have the latest drivers from LG as well.
(I'm using USB Device Tree Viewer to verify this info)
Is it possible to connect this device via SuperSpeed?
Click to expand...
Click to collapse
See my thread on the subject.

Quantumrabbit said:
See my thread on the subject.
Click to expand...
Click to collapse
Ok, from reading that other thread, it seems like the phone (and all Android phones) are only "2.0 High-Speed".
It seems weird I'd get that popup complaining about the ports, but I guess that's just windows.

OTG

Does Nokia N1 got OTG support? I have Tried to connect my USB Flash through OTG cable but doesn't work for me ....

Doesn't work for me either >_<

I don't have an otg cable myself (yet) but can you try to use USB Host Diagnostics (available in play store) and post the report?

FYI I got an OTG cable myself and it didn't work. I dug a bit deeper and found out that OTG is most likely not implemented because Nokia N1 is using legacy usb controller over usb C - see below:
Converting USB 2.0 OTG SoCs to USB Type-C
While existing Device, Host, and DRD devices can be converted to support the USB Type-C connection with some effort, it is not practical to convert existing OTG SoCs. OTG requires a new state machine using the configuration channel to support USB Type-C. Host Negotiation Protocol is used to swap host and device role for OTG, while Power Delivery communication is used to change roles for USB Type-C. Combined, these challenges preclude simple upgrades of OTC SoCs to USB Type-C. - See more at: https://www.synopsys.com/Company/Pu...esign-type-c-2015q1.aspx#sthash.Ri02Guwe.dpuf
Click to expand...
Click to collapse
The only chance to get otg to work is most likely preparing a kernel patch (are the sources even available?) to manually switch the connector to host mode and power the attached device externally

After a bit of hacking around I was able to enable usb otg on my N1!
I've had a look at kernel sources for device with similar SoC (Nexus Player) and saw an interesting debugfs entry. To my surprise it worked like a charm and immediately detected the attached usb hub with a thumb drive, it even powered the hub so I didn't have to use an external power source!
To enable host mode, the following command has to be enterted in root console:
echo A > /sys/kernel/debug/usb/dwc3_debugfs_root/otg_id
Caveats (will try to find a way to resolve them):
- after enabling host mode N1, won't charge from the usb port - a reboot is required to enable the charging again
- probably same is true for pheripherial mode (connecting n1 to a pc). In theory, changing a to b in the above echo command should bring the tablet back to normal mode but for some reason it won't charge without a reboot so I'm assuming that same is true for non otg usb connectivity. Will have a look at the sources and debug messages to find out what's going on

wodz69 said:
After a bit of hacking around I was able to enable usb otg on my N1!
I've had a look at kernel sources for device with similar SoC (Nexus Player) and saw an interesting debugfs entry. To my surprise it worked like a charm and immediately detected the attached usb hub with a thumb drive, it even powered the hub so I didn't have to use an external power source!
To enable host mode, the following command has to be enterted in root console:
echo A > /sys/kernel/debug/usb/dwc3_debugfs_root/otg_id
Caveats (will try to find a way to resolve them):
- after enabling host mode N1, won't charge from the usb port - a reboot is required to enable the charging again
- probably same is true for pheripherial mode (connecting n1 to a pc). In theory, changing a to b in the above echo command should bring the tablet back to normal mode but for some reason it won't charge without a reboot so I'm assuming that same is true for non otg usb connectivity. Will have a look at the sources and debug messages to find out what's going on
Click to expand...
Click to collapse
Thanks for your hard job.
I have tried on my N1. It is amazing that otg did work. However, the otg can not coexist with charging function as yours. Hope someone could find a solution.

adagiov said:
Thanks for your hard job.
I have tried on my N1. It is amazing that otg did work. However, the otg can not coexist with charging function as yours. Hope someone could find a solution.
Click to expand...
Click to collapse
Hey,
Are you on Android 5.1.1 or 5.0 ?
I've had a look at the code of the usb driver of the a phone with similar chipset (asus zenfone 5) and it seems that the source of the problem is that the tablet fails to detect an appropriate charger type, which could mean either that the otg cable does not support this or the code of the driver does not work properly with usb C. Was wondering if something changed around this after the update?

wodz69 said:
Hey,
Are you on Android 5.1.1 or 5.0 ?
I've had a look at the code of the usb driver of the a phone with similar chipset (asus zenfone 5) and it seems that the source of the problem is that the tablet fails to detect an appropriate charger type, which could mean either that the otg cable does not support this or the code of the driver does not work properly with usb C. Was wondering if something changed around this after the update?
Click to expand...
Click to collapse
Hi, mine N1 is still running the android 5.0.
I am afraid Root is the prerequisite to hack otg. Unfortunately, root is not available on android 5.1.1 till now, so even the android 5.1.1 driver support it, that won't help.
Thanks,dude.

Yeah exactly for that reason I haven't upgraded my tablet yet