I want to fix my bricked Nook (8g), in order to fix it I loaded cwm into a microsd card and my plan was getting adb to work while the Nook is in cwm recovery. The problem here is that my pc (Debian Wheezy) doesn't seem very happy with the tablet and I couldn't get it recognized.
Using Android SDK Manager I got the following in the usb.ini
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x2080
Click to expand...
Click to collapse
worth saying (probably), I also edited /etc/udev/rules.d/51-android.rules as follows:
SUBSYSTEM=="usb", ATTR{idVendor}=="2080", MODE="0666"
SUBSYSTEM=="usb",ATTR{idVendor}=="2080",ATTR{idProduct}=="0004",SYMLINK+="android_adb"
SUBSYSTEM=="usb",ATTR{idVendor}=="2080",ATTR{idProduct}=="0004",SYMLINK+="android_fastboot"
Click to expand...
Click to collapse
When I finished doing that and still didn't work, I looked up what happens when I plug the tablet into the usb port,
[ 9634.796053] usb 2-9: new full-speed USB device number 39 using ohci_hcd
[ 9634.980037] usb 2-9: device descriptor read/64, error -62
[ 9635.268035] usb 2-9: device descriptor read/64, error -62
[ 9635.548038] usb 2-9: new full-speed USB device number 40 using ohci_hcd
[ 9635.732041] usb 2-9: device descriptor read/64, error -62
[ 9636.020041] usb 2-9: device descriptor read/64, error -62
Click to expand...
Click to collapse
so this seems to be the error. Is it possible to fix it? I tried a few things I found (like killing the usb services and start them again) but you can tell it wasn't exactly successful. Is there anything I can try?
You might want to consider the unbrick method described at http://raywaldo.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/.
Related
Hi people,
A few days ago the problem began. The headset icon was in the screen and was not leaving. Also I could not mount my SD card.
Fortunately, the icon automatically avoided, but the problem still exists with the SD. (Also I can not sync)
I already tried the following:
- New ROM flashed
- New RADIO flashed
- New USB cable tried
- Multiple OS's tried
log in /var/log/kern.log:
Code:
kernel: [11267.304066] usb 6-1: new low speed USB device using uhci_hcd and address 120
kernel: [11267.485057] usb 6-1: device descriptor read/64, error -71
kernel: [11267.712055] usb 6-1: device descriptor read/64, error -71
kernel: [11267.984093] usb 6-1: new low speed USB device using uhci_hcd and address 121
kernel: [11268.108056] usb 6-1: device descriptor read/64, error -71
kernel: [11268.333053] usb 6-1: device descriptor read/64, error -71
kernel: [11268.549060] usb 6-1: new low speed USB device using uhci_hcd and address 122
kernel: [11268.960050] usb 6-1: device not accepting address 122, error -71
kernel: [11269.072078] usb 6-1: new low speed USB device using uhci_hcd and address 123
kernel: [11269.481132] usb 6-1: device not accepting address 123, error -71
kernel: [11269.481160] hub 6-0:1.0: unable to enumerate USB device on port 1
Thanks.
goingwrong said:
Hi people,
A few days ago the problem began. The headset icon was in the screen and was not leaving. Also I could not mount my SD card.
Fortunately, the icon automatically avoided, but the problem still exists with the SD. (Also I can not sync)
I already tried the following:
- New ROM flashed
- New RADIO flashed
- New USB cable tried
- Multiple OS's tried
log in /var/log/kern.log:
Code:
kernel: [11267.304066] usb 6-1: new low speed USB device using uhci_hcd and address 120
kernel: [11267.485057] usb 6-1: device descriptor read/64, error -71
kernel: [11267.712055] usb 6-1: device descriptor read/64, error -71
kernel: [11267.984093] usb 6-1: new low speed USB device using uhci_hcd and address 121
kernel: [11268.108056] usb 6-1: device descriptor read/64, error -71
kernel: [11268.333053] usb 6-1: device descriptor read/64, error -71
kernel: [11268.549060] usb 6-1: new low speed USB device using uhci_hcd and address 122
kernel: [11268.960050] usb 6-1: device not accepting address 122, error -71
kernel: [11269.072078] usb 6-1: new low speed USB device using uhci_hcd and address 123
kernel: [11269.481132] usb 6-1: device not accepting address 123, error -71
kernel: [11269.481160] hub 6-0:1.0: unable to enumerate USB device on port 1
Thanks.
Click to expand...
Click to collapse
Did you do anything with your SD card? Like partitioning it for Apps2SD?
C0mpu13rFr34k said:
Did you do anything with your SD card? Like partitioning it for Apps2SD?
Click to expand...
Click to collapse
No, nothing.
Are the icons in the notifications bar coming up?
Andyt95 said:
Are the icons in the notifications bar coming up?
Click to expand...
Click to collapse
Nope, nothing happens when i plug in the cable.
The only thing that happens is that the battery LED lights.
goingwrong said:
Nope, nothing happens when i plug in the cable.
The only thing that happens is that the battery LED lights.
Click to expand...
Click to collapse
Then the problem is unrelated to your phone. You have tried a new USB cable, so you should try a different USB slot or a different computer. If that doesn't work, get and micro-SD adapter and format (deselect quick format as that won't do anything). After all else has failed, you should look into a new SD card...
Not necessarily a cable issue. I had an issue a few months ago where the phone went into some qxdm debug mode which meant that it disabled both SD and the UART (which controlled USB and Wi-Fi amongst other things).
Try these threads
http://forum.xda-developers.com/showthread.php?t=708776
http://forum.xda-developers.com/showthread.php?t=681583
They both refer to a page at modaco.com that solved it for me. You have to use fastboot oem commands, and then I had to load a new SPL (but it depends what your handset has, other people have been able to avoid that bit).
Andyt95 said:
Then the problem is unrelated to your phone. You have tried a new USB cable, so you should try a different USB slot or a different computer. If that doesn't work, get and micro-SD adapter and format (deselect quick format as that won't do anything). After all else has failed, you should look into a new SD card...
Click to expand...
Click to collapse
sync doenst work either..
I have noticed this morning that while my Xperia S is connected via USB cable to the PC it does not charge, ie. it indicates charging but battery level goes down rather than up. Also I've noticed that my OS (Fedora 16) stopped mounting Xperia's internal memory. Dmesg output is just that:
Code:
[34723.804074] usb 2-1.2: new full-speed USB device number 61 using ehci_hcd
[34723.877051] usb 2-1.2: device descriptor read/64, error -32
[34724.050920] usb 2-1.2: device descriptor read/64, error -32
[34724.224867] usb 2-1.2: new full-speed USB device number 62 using ehci_hcd
[34724.287808] usb 2-1.2: device descriptor read/64, error -32
[34724.461715] usb 2-1.2: device descriptor read/64, error -32
[34724.635655] usb 2-1.2: new full-speed USB device number 63 using ehci_hcd
[34725.037264] usb 2-1.2: device not accepting address 63, error -32
[34725.110414] usb 2-1.2: new full-speed USB device number 64 using ehci_hcd
[34725.512050] usb 2-1.2: device not accepting address 64, error -32
[34725.512180] hub 2-1:1.0: unable to enumerate USB device on port 2
Did a bit of research around the interwebs, found advice to clear data of the MtpApp app (settings -> applications -> all -> MtpApp), which I did but that didn't solve the problem, yet dmesg output changed a bit:
Code:
[34734.683275] usb 3-1: new full-speed USB device number 67 using xhci_hcd
[34734.686432] usb 3-1: Device not responding to set address.
[34734.890333] usb 3-1: Device not responding to set address.
[34735.091046] usb 3-1: device not accepting address 67, error -71
[34735.243993] usb 3-1: new full-speed USB device number 68 using xhci_hcd
[34735.247164] usb 3-1: Device not responding to set address.
[34735.451046] usb 3-1: Device not responding to set address.
[34735.651757] usb 3-1: device not accepting address 68, error -71
[34735.804727] usb 3-1: new full-speed USB device number 69 using xhci_hcd
[34735.807836] usb 3-1: Device not responding to set address.
[34736.011768] usb 3-1: Device not responding to set address.
[34736.212469] usb 3-1: device not accepting address 69, error -71
[34736.365416] usb 3-1: new full-speed USB device number 70 using xhci_hcd
[34736.368521] usb 3-1: Device not responding to set address.
[34736.572448] usb 3-1: Device not responding to set address.
[34736.773180] usb 3-1: device not accepting address 70, error -71
[34736.773208] hub 3-0:1.0: unable to enumerate USB device on port 1
Seems to also depend on the USB port I use in my laptop, ie. in one port it says "Device not responding", while on the other "device descriptor read/64, error -32". UPDATE: On double check it seems like USB 3.0 ports saying "not responding", while USB 2.0 port returns "descriptor error".
I obviously tried rebooting (including hard-reboot with volume-up key held), tried different cables, different PCs, including Windows one which just popped a balloon saying something about "unrecognized device". Nothing seems to rectify the issue. Needless to say it was working perfectly up until today.
Thankfully, it seems that's a software-related issue rather than physically borked USB port as I successfully managed to put device into flashmode (volume-up + usb plug). UPDATE: Unfortunately, even if physical plug to the port is recognized and green or blue light comes up, dmesg still returns "descriptor errors" and device is turning itself into charging-only mode (I initially thought just seeing blue/green light means either of modes is entered).
Running out of ideas what else I could do to get USB work again, apart from hard reset. Any suggestions more than welcome.
UPDATE: Out of the sudden, after 1525th reboot cycle somehow charging via USB cable works fine again, however internal storage is still not mounted to the PC. Doh! I guess I'll end up with warranty repair/replacement.
FINAL UPDATE: USB port died completely, plugging USB cable to the PC doesn't trigger any dmesg activity at all and handset after a while of doubt recognises connection as a standard wall charger. Sorting out warranty replacement as we speak.
Have you tried cleaning of the USB port/connector (of your phone)?
cognosco said:
Have you tried cleaning of the USB port/connector (of your phone)?
Click to expand...
Click to collapse
No, I haven't, but I doubt that's the case, as it wouldn't enter flashmode either.
Newbie in need for help - Unknown BRICKED State….and Unknown how was bricked
ASUS TF201 / 64 gb. – No access to specific blob files.
I think I have APX mode after I run the below commands in Ubuntu
lsusb...
Bus 002 Device 085: ID 0955:7330 NVidia Corp.
and when I run
dmesg |tail
[15614.715848] usb 2-1.2: new high-speed USB device number 84 using ehci-pci
[15615.539331] usb 2-1.2: device not accepting address 84, error -71
[15615.539592] hub 2-1:1.0: unable to enumerate USB device on port 2
[15616.495015] usb 2-1.2: new high-speed USB device number 85 using ehci-pci
[15616.588212] usb 2-1.2: New USB device found, idVendor=0955, idProduct=7330
[15616.588224] usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[15616.588230] usb 2-1.2: Product: APX
[15616.588236] usb 2-1.2: Manufacturer: NVIDIA Corp.
[16007.391552] systemd-hostnamed[7142]: Warning: nss-myhostname is not installed. Changing the local hostname might make it unresolveable. Please install nss-myhostname!
[16008.688244] perf samples too long (2501 > 2500), lowering kernel.perf_event_max_sample_rate to 50000
I have tried Windows before Ubuntu, I was able to identify as APX in device manager but I could not understand and get any results, and decide to move to Ubuntu.
I appreciate if I can get straight answer that I can’t seem to find:
Since it’s visible as APX in ubuntu and Windows what are % chances to be recoverable?
I’m newbie and I have tried to learn as much as I can…but after a week of frustration I’m very down on energy, and lost …in commands that don’t seem to work as specified on forum.
I appreciate any help and direction on where should I start.
Thanks
reexon said:
Newbie in need for help - Unknown BRICKED State….and Unknown how was bricked
ASUS TF201 / 64 gb. – No access to specific blob files.
I think I have APX mode after I run the below commands in Ubuntu
lsusb...
Bus 002 Device 085: ID 0955:7330 NVidia Corp.
and when I run
dmesg |tail
[15614.715848] usb 2-1.2: new high-speed USB device number 84 using ehci-pci
[15615.539331] usb 2-1.2: device not accepting address 84, error -71
[15615.539592] hub 2-1:1.0: unable to enumerate USB device on port 2
[15616.495015] usb 2-1.2: new high-speed USB device number 85 using ehci-pci
[15616.588212] usb 2-1.2: New USB device found, idVendor=0955, idProduct=7330
[15616.588224] usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[15616.588230] usb 2-1.2: Product: APX
[15616.588236] usb 2-1.2: Manufacturer: NVIDIA Corp.
[16007.391552] systemd-hostnamed[7142]: Warning: nss-myhostname is not installed. Changing the local hostname might make it unresolveable. Please install nss-myhostname!
[16008.688244] perf samples too long (2501 > 2500), lowering kernel.perf_event_max_sample_rate to 50000
I have tried Windows before Ubuntu, I was able to identify as APX in device manager but I could not understand and get any results, and decide to move to Ubuntu.
I appreciate if I can get straight answer that I can’t seem to find:
Since it’s visible as APX in ubuntu and Windows what are % chances to be recoverable?
I’m newbie and I have tried to learn as much as I can…but after a week of frustration I’m very down on energy, and lost …in commands that don’t seem to work as specified on forum.
I appreciate any help and direction on where should I start.
Thanks
Click to expand...
Click to collapse
Sorry to say, but as you don't have the nvflash back up files APX mode is of no use to you, try buying a second hand motherboard of eBay and replacing it
Sent from my TF300T using XDA Premium HD app
Hi, suddenly (without any ROM flash attempt) my IAIWAI AW920 tablet got in a bootloop.
IIRC it's a RK3066 but the RKAndroidTool/Finn Flash Tool didn't recognized the tablet with either PWR Vol+ or PWR Vol- boot modes.
In the past I got the tablet successfully rooted through some tools, so in some past era I was able to communicate with ADB from the Android SDK (Linux Mint Kernel +3.10) but before it got soft-bricked I had not the USB debugging bridge set and due a failing HDD I lost that environment setup.
While being connected to my laptop through USB cable I can access two modes:
USB + PWR + Vol+: Blank black screen but I detect a USB device with VID: 10d6 PID: 10d6 that doesn't seems to be an adb client.
USB + PWR + Vol-: Appears a Fastboot kind of picture (Android mascot laying in the floor with his chest open and a Red Warning Symbol ) but no output whatsoever in [dmesg] or [udev monitor]
In neither these modes adb or fastboot detect something
---- For the Vol+ mode with the 10d6:10d6 device ----
I can't get adb or fastboot to work, even with adb_usb.ini edited in windows or linux or several different udev rules
The only udev rule I could trigger was
#IAIWAI
SUBSYSTEM=="usb", ENV{ID_VENDOR_ID}=="10d6", SYMLINK+="android_adb", MODE="0666", GROUP="plugdev"
Click to expand...
Click to collapse
But it seems android_usb is not a link to a proper block device (the last number increases on each test)
ls -l /dev/
android_adb -> bus/usb/001/010
Click to expand...
Click to collapse
Or at least I can't make it work with
adb -p /dev/android_adb devices
or
fastboot -s /dev/android_adb devices
Extra information of the device found in Vol+ mode
lsusb:
Bus 001 Device 003: ID 10d6:10d6 Actions Semiconductor Co., Ltd
dmesg:
[11102.331560] usb 1-2: new high-speed USB device number 10 using ehci-pci
[11102.464620] usb 1-2: New USB device found, idVendor=10d6, idProduct=10d6
[11102.464633] usb 1-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
udevadm monitor:
KERNEL[8596.157794] add /devices/pci0000:00/0000:00:12.2/usb1/1-2 (usb)
KERNEL[8596.158995] add /devices/pci0000:00/0000:00:12.2/usb1/1-2/1-2:1.0 (usb)
UDEV [8596.167280] add /devices/pci0000:00/0000:00:12.2/usb1/1-2 (usb)
UDEV [8596.171388] add /devices/pci0000:00/0000:00:12.2/usb1/1-2/1-2:1.0 (usb)
udevadm info --query=all --path=/devices/pci0000:00/0000:00:12.2/usb1/1-2/1-2:1.0
P: /devices/pci0000:00/0000:00:12.2/usb1/1-2/1-2:1.0
E: DEVPATH=/devices/pci0000:00/0000:00:12.2/usb1/1-2/1-2:1.0
E: DEVTYPE=usb_interface
E: ID_VENDOR_FROM_DATABASE=Actions Semiconductor Co., Ltd
E: INTERFACE=255/255/255
E: MODALIAS=usb:v10D6p10D6d0100dc00dsc00dp00icFFiscFFipFFin00
E: PRODUCT=10d6/10d6/100
E: SUBSYSTEM=usb
E: TYPE=0/0/0
E: USEC_INITIALIZED=434099056
udevadm info --query=all --path=/devices/pci0000:00/0000:00:12.2/usb1/1-2/1-2:1.0 --attribute-walk:
looking at device '/devices/pci0000:00/0000:00:12.2/usb1/1-2/1-2:1.0':
KERNEL=="1-2:1.0"
SUBSYSTEM=="usb"
DRIVER==""
ATTR{bInterfaceClass}=="ff"
ATTR{bInterfaceSubClass}=="ff"
ATTR{bInterfaceProtocol}=="ff"
ATTR{bNumEndpoints}=="02"
ATTR{supports_autosuspend}=="1"
ATTR{bAlternateSetting}==" 0"
ATTR{bInterfaceNumber}=="00"
looking at parent device '/devices/pci0000:00/0000:00:12.2/usb1/1-2':
KERNELS=="1-2"
SUBSYSTEMS=="usb"
DRIVERS=="usb"
ATTRS{bDeviceSubClass}=="00"
ATTRS{bDeviceProtocol}=="00"
ATTRS{devpath}=="2"
ATTRS{idVendor}=="10d6"
ATTRS{speed}=="480"
ATTRS{bNumInterfaces}==" 1"
ATTRS{bConfigurationValue}=="1"
ATTRS{bMaxPacketSize0}=="64"
ATTRS{busnum}=="1"
ATTRS{devnum}=="4"
ATTRS{configuration}==""
ATTRS{bMaxPower}=="128mA"
ATTRS{authorized}=="1"
ATTRS{bmAttributes}=="80"
ATTRS{bNumConfigurations}=="1"
ATTRS{maxchild}=="0"
ATTRS{bcdDevice}=="0100"
ATTRS{avoid_reset_quirk}=="0"
ATTRS{quirks}=="0x0"
ATTRS{version}==" 2.00"
ATTRS{urbnum}=="6"
ATTRS{ltm_capable}=="no"
ATTRS{removable}=="removable"
ATTRS{idProduct}=="10d6"
ATTRS{bDeviceClass}=="00"
looking at parent device '/devices/pci0000:00/0000:00:12.2/usb1':
KERNELS=="usb1"
SUBSYSTEMS=="usb"
DRIVERS=="usb"
ATTRS{bDeviceSubClass}=="00"
ATTRS{bDeviceProtocol}=="00"
ATTRS{devpath}=="0"
ATTRS{idVendor}=="1d6b"
ATTRS{speed}=="480"
ATTRS{bNumInterfaces}==" 1"
ATTRS{bConfigurationValue}=="1"
ATTRS{bMaxPacketSize0}=="64"
ATTRS{authorized_default}=="1"
ATTRS{busnum}=="1"
ATTRS{devnum}=="1"
ATTRS{configuration}==""
ATTRS{bMaxPower}=="0mA"
ATTRS{authorized}=="1"
ATTRS{bmAttributes}=="e0"
ATTRS{bNumConfigurations}=="1"
ATTRS{maxchild}=="5"
ATTRS{bcdDevice}=="0313"
ATTRS{avoid_reset_quirk}=="0"
ATTRS{quirks}=="0x0"
ATTRS{serial}=="0000:00:12.2"
ATTRS{version}==" 2.00"
ATTRS{urbnum}=="91"
ATTRS{ltm_capable}=="no"
ATTRS{manufacturer}=="Linux 3.13.0-37-generic ehci_hcd"
ATTRS{removable}=="unknown"
ATTRS{idProduct}=="0002"
ATTRS{bDeviceClass}=="09"
ATTRS{product}=="EHCI Host Controller"
looking at parent device '/devices/pci0000:00/0000:00:12.2':
KERNELS=="0000:00:12.2"
SUBSYSTEMS=="pci"
DRIVERS=="ehci-pci"
ATTRS{irq}=="17"
ATTRS{subsystem_vendor}=="0x1179"
ATTRS{broken_parity_status}=="0"
ATTRS{class}=="0x0c0320"
ATTRS{companion}==""
ATTRS{enabled}=="1"
ATTRS{consistent_dma_mask_bits}=="32"
ATTRS{dma_mask_bits}=="32"
ATTRS{local_cpus}=="00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000003"
ATTRS{device}=="0x4396"
ATTRS{uframe_periodic_max}=="100"
ATTRS{msi_bus}==""
ATTRS{local_cpulist}=="0-1"
ATTRS{vendor}=="0x1002"
ATTRS{subsystem_device}=="0xff1e"
ATTRS{numa_node}=="0"
ATTRS{d3cold_allowed}=="1"
looking at parent device '/devices/pci0000:00':
KERNELS=="pci0000:00"
SUBSYSTEMS==""
DRIVERS==""
Click to expand...
Click to collapse
I am trying to resurrect my old Samsung Galaxy i5500. A couple of years ago I tried installing some custom rom but failed and bricked the phone. The boot process halts at the Samsung logo (the very first logo to appear.)
Putting the phone into recovery mode (using the volume down button + center button + power button) works, at least i presume that it works - the logo with the android shoveling dirt and the word "Downloading..." beneath it appears - but neither adb nor fastboot can see the device.
My troubleshooting so far:
Code:
[email protected]:~# dmesg
...
[823736.755555] usb 2-1.1: new high-speed USB device number 6 using ehci-pci
[823736.851772] usb 2-1.1: unable to get BOS descriptor
[823736.857819] usb 2-1.1: New USB device found, idVendor=04e8, idProduct=6601
[823736.857829] usb 2-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[823736.857835] usb 2-1.1: Product: MSM7x27
[823736.857839] usb 2-1.1: Manufacturer: Sasmsung
[823739.903177] cdc_acm 2-1.1:2.0: ttyACM0: USB ACM device
[823739.903553] usbcore: registered new interface driver cdc_acm
[823739.903557] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[823761.102222] cdc_acm 2-1.1:2.0: failed to set dtr/rts
[email protected]:~# lsusb
...
Bus 002 Device 011: ID 04e8:6601 Samsung Electronics Co., Ltd Mobile Phone
...
[email protected]:~# adb devices
List of devices attached
[email protected]:~# fastboot devices
[email protected]:~#
I am running Lubuntu 12.04 on my laptop.
What do I need to do to be able to connect to the phone using adb and fastboot?
Thanks!
The "recovery mode" that you mentioned, is actually download mode and it's used to flash packages with Odin.
Use it to flash a custom recovery and then use that to flash a custom ROM. Format /system and /data as ext4 before flashing the ROM.
Sent from my LG G2 Mini using XDA Labs