Database Info

[Q] Bricked USB !!! is there a fix ? lil Help Needed !!!

I cant use my usb ? Device not recognize when plugged in via usb i have all the necessary drivers installed and they work when i use other htc phones with adb . i have search for days now and all i can find is htc desire "bravo" usb brick fix . which is to push misc version file and flash an image file of some sort . but i cant push anything because i cant use the usb to connect with adb i have managed to find and install a wireless adb but how do i find the misc version for the desire s "saga" and flash_image file to push and flash ? any help with this would be great... thanks in advance...

scaffman said:
I cant use my usb ? Device not recognize when plugged in via usb i have all the necessary drivers installed and they work when i use other htc phones with adb . i have search for days now and all i can find is htc desire "bravo" usb brick fix . which is to push misc version file and flash an image file of some sort . but i cant push anything because i cant use the usb to connect with adb i have managed to find and install a wireless adb but how do i find the misc version for the desire s "saga" and flash_image file to push and flash ? any help with this would be great... thanks in advance...
Click to expand...
Click to collapse
Does you USB work when in fastboot mode?
Also, it would really help if you could boot into Linux on your computer (using e.g. a Fedora live CD) and post a dmesg after plugging in your phone.

no got nothing in fastboot mode .. downloading Fedora live CD now . i don't know how to use linux much . if you could me help with any commands i would need that would be magic . i'm a bit of a noob but smarter than average noob , i can follow instructions lol

R ya s-on or s-off? Do u have recovery? 4ext recovery has a built in usb unbrick option

jmcclue said:
R ya s-on or s-off? Do u have recovery? 4ext recovery has a built in usb unbrick option
Click to expand...
Click to collapse
Hi , my device is S-on with no recovery its stock running 2.3.5 on 2.10.401.8 build . i have been trying to push root files over wireless adb to install recovery but i'm not having much luck atm.

scaffman said:
no got nothing in fastboot mode .. downloading Fedora live CD now . i don't know how to use linux much . if you could me help with any commands i would need that would be magic . i'm a bit of a noob but smarter than average noob , i can follow instructions lol
Click to expand...
Click to collapse
All you need to do is:
plug in your phone when it's booted into Android
open a terminal
type the following: dmesg>logfile
then open up the file manager (or just type: nautilus&) and you'll find a text file named 'logfile' in your home folder, attach that here

Aquous said:
All you need to do is:
plug in your phone when it's booted into Android
open a terminal
type the following: dmesg>logfile
then open up the file manager (or just type: nautilus&) and you'll find a text file named 'logfile' in your home folder, attach that here
Click to expand...
Click to collapse
Hi , i just tried that but terminal gives error message "can't create logfile: read only file system"...
even tho my sd is in the phone ? i've tried changing home folder to /sdcard/data/data/jackpal.androidterm/app_HOME
but i think i've got the sd path name wrong lol this is right pathive found /mnt/sdcard/jackpal.androidterm/app_HOME/ but still get the same error "can't create logfile: read only file system"...
i have installed Anjedi which has lolcat in tools and when i plug in usb i get a log says (1267): Ignoring unknown switch 'usb_mass_storage' in warnings tab and some others sorry i'm tring to find a way to copy this logcat info to show.

scaffman said:
Hi , i just tried that but terminal gives error message "can't create logfile: read only file system"...
even tho my sd is in the phone ? i've tried changing home folder to /sdcard/data/data/jackpal.androidterm/app_HOME
but i think i've got the sd path name wrong lol this is right pathive found /mnt/sdcard/jackpal.androidterm/app_HOME/ but still get the same error "can't create logfile: read only file system"...
i have installed Anjedi which has lolcat in tools and when i plug in usb i get a log says (1267): Ignoring unknown switch 'usb_mass_storage' in warnings tab and some others sorry i'm tring to find a way to copy this logcat info to show.
Click to expand...
Click to collapse
I'm asking for the dmesg from your computer when it's booted into Linux, not for a dmesg from your phone.

Aquous said:
I'm asking for the dmesg from your computer when it's booted into Linux, not for a dmesg from your phone.
Click to expand...
Click to collapse
Hi , sorry lol . yes i got it now . attached . thanks

scaffman said:
Hi , sorry lol . yes i got it now . attached . thanks
Click to expand...
Click to collapse
Yep, that's what I was looking for.
[ 522.472578] usb 3-2: new full-speed USB device number 6 using uhci_hcd
[ 522.596060] usb 3-2: device descriptor read/64, error -71
[ 522.811129] usb 3-2: device descriptor read/64, error -71
[ 523.014066] usb 3-2: new full-speed USB device number 7 using uhci_hcd
[ 523.128032] usb 3-2: device descriptor read/64, error -71
[ 523.342051] usb 3-2: device descriptor read/64, error -71
[ 523.548273] usb 3-2: new full-speed USB device number 8 using uhci_hcd
[ 523.958045] usb 3-2: device not accepting address 8, error -71
[ 524.060049] usb 3-2: new full-speed USB device number 9 using uhci_hcd
[ 524.470046] usb 3-2: device not accepting address 9, error -71
[ 524.470076] hub 3-0:1.0: unable to enumerate USB device on port 2
Click to expand...
Click to collapse
I've had this problem too, and it's a problem with the USB port on your phone. You can try plugging in the cable while holding the phone differently, or pushing the connector slightly up after it's been plugged in, and you can try rebooting your phone, but ultimately this is a hardware problem caused by old age.

Aquous said:
Yep, that's what I was looking for.
I've had this problem too, and it's a problem with the USB port on your phone. You can try plugging in the cable while holding the phone differently, or pushing the connector slightly up after it's been plugged in, and you can try rebooting your phone, but ultimately this is a hardware problem caused by old age.
Click to expand...
Click to collapse
Thanks for your help !!! knowing that the hardware failed i have now installed a new usb flex cable and it works like a charm ive s-offed and about to flash custom roms now so happy days

Unlock Nexus Player

This is how you unlock the bootloader (warning!!!! This will erase everything you have on your device!)
1. adb reboot fastboot
2. fastboot oem unlock(x2. It will prompt you to enter it again to confirm)

Awesome. First thing I'm going to do out of the box.
Sent from my Oneplus One with Tapatalk Pro.

peppy6582 said:
This is how you unlock the bootloader (warning!!!! This will erase everything you have on your device!)
1. adb reboot fastboot
2. fastboot oem unlock(x2. It will prompt you to enter it again to confirm)
Click to expand...
Click to collapse
And don't forget, to put device in fastboot, press and hold button that is located on the bottom of the player, plug in the power cord and hold until led light flashes repeatedly.

Fastboot
On Ubuntu, ADB is not ever seeing my NP. I can get it in fastboot mode with the button, and my USB devices enumerate (2 different ones), but ADB never shows it connected.
Code:
[376711.228958] usb 3-2.4: new high-speed USB device number 12 using xhci_hcd
[376711.246426] usb 3-2.4: New USB device found, idVendor=18d1, idProduct=4ee0
[376711.246436] usb 3-2.4: New USB device strings: Mfr=2, Product=3, SerialNumber=4
[376711.246441] usb 3-2.4: Product: fugu
[376711.246445] usb 3-2.4: Manufacturer: Android
[376711.246450] usb 3-2.4: SerialNumber: 13737740
[376772.269599] usb 3-2.4: USB disconnect, device number 12
[376773.252023] usb 3-2.4: new high-speed USB device number 13 using xhci_hcd
[376773.282912] usb 3-2.4: New USB device found, idVendor=8086, idProduct=0a2c
[376773.282919] usb 3-2.4: New USB device strings: Mfr=2, Product=1, SerialNumber=3
[376773.282923] usb 3-2.4: Product: MOOREFIELD
[376773.282926] usb 3-2.4: Manufacturer: INTEL
[376773.282943] usb 3-2.4: SerialNumber: <redacted>

Ahh, I forgot I had to enable USB debugging in the developer menu. The dev menu is enabled by clicking "Build" a handful of times from the "About" menu.

figured it out : windows , device manager , let me choose driver , selected ADB TESTING INTErFACE , all is good. hope this helps others,.
================================================================================================================
using windows 8 , holding down bottom button i get to fastboot , when i run "fastboot devices" i get nothing , when run adb devices i get " emulator-5554 device " ( that was bluestacks ) i had to end task . but still no luck. when i run "fastboot devices" i get nothing , when run adb devices i get nothing
i double checked developer mode , all good , windows 8 calls it FUGU , , in control panel . if i run 'fastboot oem unlock" all i get is "waiting for device "
what step did i miss? any help appreciated./.

I have the same problems running Linux Mint 17.
"adb shell" works OK when booting normally.
"sudo fastboot devices" shows nothing in bootloader/fastboot mode, and no other fastboot commands work. Also see:
<6>[84128.968111] usb 1-5: new high-speed USB device number 55 using ehci-pci
<6>[84129.106293] usb 1-5: New USB device found, idVendor=18d1, idProduct=4ee0
<6>[84129.106305] usb 1-5: New USB device strings: Mfr=2, Product=3, SerialNumber=4
<6>[84129.106313] usb 1-5: Product: fugu
<6>[84129.106319] usb 1-5: Manufacturer: Android
<6>[84129.106324] usb 1-5: SerialNumber: DA4D....
I'm itching for root to explore more.

fastboot problem is due to need for new fastboot.
I've attached the Linux version in my updated SDK. Windows version is in SDK on Google site somewhere I guess.

Just thought that I'd point out that holding down the button on the bottom of the device while plugging in will load the bootloader...just another way to get there is all.

bsara said:
Just thought that I'd point out that holding down the button on the bottom of the device while plugging in will load the bootloader...just another way to get there is all.
Click to expand...
Click to collapse
And one that doesn't require a working adb connection first.

Device not found
Trying to unlock Nexus Player but getting error, device not found. I enable USB debugging in the Developer menu and turn on developer by hitting Build in About menu.
I am using a windows 7 computer and i get the following when i try to unlock,
C:\Program Files\Android\android-sdk\platform-tools>adb reboot fastboot
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
C:\Program Files\Android\android-sdk\platform-tools>adb reboot fastboot
error: device not found
C:\Program Files\Android\android-sdk\platform-tools>

dreadprinz said:
Trying to unlock Nexus Player but getting error, device not found. I enable USB debugging in the Developer menu and turn on developer by hitting Build in About menu.
I am using a windows 7 computer and i get the following when i try to unlock,
C:\Program Files\Android\android-sdk\platform-tools>adb reboot fastboot
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
C:\Program Files\Android\android-sdk\platform-tools>adb reboot fastboot
error: device not found
C:\Program Files\Android\android-sdk\platform-tools>
Click to expand...
Click to collapse
The command is "adb reboot-bootloader" not "fastboot"
Also, double check that you have the latest platform tools installed from the SDK manager.

Just go straight into the bootlloader by holding the button as you plug it in, then wait for the light as BSaras post states . No driver needed

volwrath said:
Just go straight into the bootlloader by holding the button as you plug it in, then wait for the light as BSaras post states . No driver needed
Click to expand...
Click to collapse
Very good point...though you will still need the latest version of the android SDK platform tools for fastboot to detect the player.

bsara said:
Very good point...though you will still need the latest version of the android SDK platform tools for fastboot to detect the player.
Click to expand...
Click to collapse
I don't think so.
I haven't upgraded mine in quite a while and fastboot had no problem seeing the player. I am updating my sdk platform tools as we speak.
But then again I guess they are fairly new since I updated them to play with my google watch

Device not found
I tried the command "adb reboot-bootloader" still got error device not found .
I think i have the latest platform tools Revision 23.0.5.

Try this:
After you unlock Developer options,
Go into Developer options
You will see "Enable OEM unlock" make sure that is checked then you should be able to proceed

vitald2 said:
Try this:
After you unlock Developer options,
Go into Developer options
You will see "Enable OEM unlock" make sure that is checked then you should be able to proceed
Click to expand...
Click to collapse
Hmm I don't see Enable oem unlock anywhere.

vitald2 said:
Try this:
After you unlock Developer options,
Go into Developer options
You will see "Enable OEM unlock" make sure that is checked then you should be able to proceed
Click to expand...
Click to collapse
Maybe i am missing something here, but i don't see "Enable OEM unlock" anywhere.

dreadprinz said:
I tried the command "adb reboot-bootloader" still got error device not found .
I think i have the latest platform tools Revision 23.0.5.
Click to expand...
Click to collapse
You've listed the version of you "Android SDK Tools" not the "Android SDK Platform-tools" (which is found right below it in the SDK manager). At any rate, you probably are having a driver issue (I'm assuming that you're using Windows). I personally can't help you much there since I use Ubuntu, but this tool for Nexus devices might help: http://www.wugfresh.com/nrt. I know that the Player isn't listed there...but with that tool you can install the generic drivers...perhaps it will fix things for you.
Also, as stated before, you can (for the time being) just hold down the button on the bottom of the device while you plug in the device and it will boot into the bootloader (I.E. fastboot mode). Then run "fastboot devices" to see if anything shows up, if not...I would keep looking into the driver instructions on the tool I listed above. Also, to ensure that adb is seeing your device, you can also run "adb devices". Also, make sure that no other android devices that have USB debugging enabled are plugged in while you run your command, otherwise it won't succeed because it won't know which device to pick...or just run "adb -s [DEVICE_ID] reboot-bootloader" where [DEVICE_ID] is the id listed when running adb devices. Good luck.
And that "Enable OEM unlock" stuff is not true...just ignore it. Once in fastboot, you'll just need to run "fastboot oem unlock" twice in a row for the unlock to occur.

Low Level access to storage via chipset to restore damaged bootloader in Nexus 4

I have a Nexus 4 and I have accidentaly damaged the bootloader so I cannot access my device to flash again a bootloader to fix it. When I connect my phone to my PC via USB my phone seems to be alive (see below) but with no functional software.
I would like to know if there is any tool like nvflash (http://forum.xda-developers.com/wiki/Nvflash) to access in a low level way to my storage via Qualcomm APQ8064 Snapdragon S4 Pro chipset. There should be a way to flash a new bootloader via the chipset. How does the manufacturer install the software after having the finished hardware so?
If you know any other kind solution please let me know, too.
Please Help!
Thanks!
$ dmesg | tail
[ 4956.392041] usb 9-4: new high-speed USB device number 11 using xhci_hcd
[ 4956.410551] usb 9-4: New USB device found, idVendor=05c6, idProduct=9008
[ 4956.410555] usb 9-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 4956.410558] usb 9-4: Product: QHSUSB_DLOAD
[ 4956.410561] usb 9-4: Manufacturer: Qualcomm CDMA Technologies MSM
[ 4956.410832] qcserial 9-4:1.0: Qualcomm USB modem converter detected
[ 4956.411044] usb 9-4: Qualcomm USB modem converter now attached to ttyUSB0

Updating ADT-3 to Android 11 with OTA bricks it

I had official Android 11 Beta on it (there was the guide how to update it).
Got OTA with Android 11 today.
And now it does not boot - staying on "androidtv" splash screen.
Does anyone have it? How to get to recover or something on it? Any way to perform reset on it or manual update while PC (adb) does not see it.
Reported this issue to google's tracker: https://issuetracker.google.com/issues/169172450
Linux machine sees USB device connected but obviously no ADB at this point:
Code:
[ +8,588816] usb 3-5: new high-speed USB device number 24 using xhci_hcd
[ +0,150146] usb 3-5: New USB device found, idVendor=1b8e, idProduct=c003, bcdDevice= 0.07
[ +0,000002] usb 3-5: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Code:
$ adb kill-server
$ adb devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached

Issue solved: Most probably booting sequence was blocked by USB connection to my linux host machine (yeah, development device is connected to linux machine for development). Unplugging USB (keeping power line from Y-shaped usb cable) make it bootable.

Soft-bricked tablet, can not wipe/factory reset from recovery menu

Hello, guys
first i read the diff between soft/hard brick, and i think i'm in the soft case, cause i can get in recovery menu.
adb dont see the phone at all,
fastboot can, but not 'fastboot oem unlock' , neither 'fastboot boot recover.img' works. Actually command prompt wait there for ever, untin the PC kernel ( linux deb 11), break fastboot usb connection, with a reason of connection timeout. this timeout is after 30minutes ....
i manage to backup user data for the recovery menu, in 3 files 2x2G 1x1.7G ( i think because of fat ),
but the revcovery menu fail to [ wipe data/factory reset ]. Strange ? Any ideas?
here is the model f the tablet,
==> /var/log/syslog <==
Nov 6 20:12:48 localhost kernel: [1024828.830129] usb 5-2: New USB device found, idVendor=0bb4, idProduct=0c01, bcdDevice= 1.00
Nov 6 20:12:48 localhost kernel: [1024828.830135] usb 5-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Nov 6 20:12:48 localhost kernel: [1024828.830138] usb 5-2: Product: Android
Nov 6 20:12:48 localhost kernel: [1024828.830140] usb 5-2: Manufacturer: MediaTek
Nov 6 20:12:48 localhost kernel: [1024828.830142] usb 5-2: SerialNumber: mt6582_phone
#---------------------------------------------------------------------------------------------------
# ID 0bb4:0c01 HTC (High Tech Computer Corp.) Dream / ADP1 / G1 / Magic / Tattoo / FP1
#---------------------------------------------------------------------------------------------------
# Android system recovery (3e)
# A7-30DC_S0000129_150831_ROW
#---------------------------------------------------------------------------------------------------

1. To successfully run ADB and/or Fastboot commands you need to have installed on computer the "Android USB Driver" provided by device's manufacturer.
2. ADB only will work if it got enabled on Android device.

jwoegerbauer said:
1. To successfully run ADB and/or Fastboot commands you need to have installed on computer the "Android USB Driver" provided by device's manufacturer.
2. ADB only will work if it got enabled on Android device.
Click to expand...
Click to collapse
i know, everythinks works just fine, with other android devices.
( i'm using linux by the way )
My problem right now is,
why the stock recovery fail to wipe/factory reset ?
no fastboot or adb
The tablet stuck in he lenovo logo on boot for ever,
so adb dont have any way in this stage
I try 'update cache from ADB' just to see if adb can see it, but no
when 'fastboot boot recovery.img'
the phone (tablet), report get some bytes
but nothing else
when 'fastboot oem unlock', nothing happens, both the phone and the terminal
i use this links for recovery images:
https://forum.xda-developers.com/attachments/recovery_p780_cwm_6-0-1-5-7z.2840100/
https://forum.xda-developers.com/attachments/p780_recovery_twrp_2-6-3-0-zip.2840101

any pins on hardware, to triger factory reset .... ?