Hi!
Just got an HTC Magic that was locked on Vodafone Spain. The phone is great, but I seem to have a problem, I can use it as a USB mass storage device.
When I plug it to the computer using the USB cable that came with the phone, the USB notification doesn't shows up, so I can't use the mass storage...
The microSD card has 8GB of capacity and it seems to be ok, at least I can take pictures and saved to the card...
I have tried on Linux(Ubuntu 9.04) and I got the following errors on syslog:
Code:
Sep 25 00:24:20 hotice kernel: [ 441.792088] usb 3-1: new full speed USB device using uhci_hcd and address 6
Sep 25 00:24:20 hotice kernel: [ 441.912044] usb 3-1: device descriptor read/64, error -71
Sep 25 00:24:20 hotice kernel: [ 442.136044] usb 3-1: device descriptor read/64, error -71
Sep 25 00:24:21 hotice kernel: [ 442.352116] usb 3-1: new full speed USB device using uhci_hcd and address 7
Sep 25 00:24:21 hotice kernel: [ 442.472079] usb 3-1: device descriptor read/64, error -71
Sep 25 00:24:21 hotice kernel: [ 442.696080] usb 3-1: device descriptor read/64, error -71
Sep 25 00:24:21 hotice kernel: [ 442.912091] usb 3-1: new full speed USB device using uhci_hcd and address 8
Sep 25 00:24:21 hotice kernel: [ 443.320083] usb 3-1: device not accepting address 8, error -71
Sep 25 00:24:22 hotice kernel: [ 443.432084] usb 3-1: new full speed USB device using uhci_hcd and address 9
Sep 25 00:24:22 hotice kernel: [ 443.840091] usb 3-1: device not accepting address 9, error -71
Sep 25 00:24:22 hotice kernel: [ 443.840117] hub 3-0:1.0: unable to enumerate USB device on port 1
I tried to connect it to Windows XP, it appears an error installing the hardware, then tried to install the USB driver that comes with the Android SDK but with no luck
I have already made a reset to defaults on the phone, but I still get the same problem.
Does anyone knows what could be happening and how can I solve it?
Thank you all.
I don't know if its important, but here is some more info on the phone:
SAPHIRE PVT 32B SHIP S-ON G
HBOOT-1.33.0007 (SAPP10000)
CPLD-10
RADIO-2.22.19.26I
Have you create the needed udev configuration for your HTC?
In order to mount correctly a HTC Magic you have to the following udev configuration file.
Code:
sudo gedit /etc/udev/rules.d/50-android.rules
And paste the two following lines. Do not forget to change USERNAME with your Ubuntu username
Code:
SUBSYSTEM=="usb",SYSFS{idVendor}=="0bb4",ATTR{idProduct}=="0c02",SYMLINK+="android_adb",MODE="0666",OWNER="USERNAME"
SUBSYSTEM=="usb",SYSFS{idVendor}=="0bb4",ATTR{idProduct}=="0c01",SYMLINK+="android_fastboot",MODE="0666",OWNER="USERNAME"
After that you have to either reload the udev configuration or restart udev. To be sure restart udev.
Code:
sudo /etc/init.d/udev restart
I hope this will help youto resolve your case
Thank you for the reply, but I have already done that...
Also, I have pluged in another HTC Magic(a 32A version) to the same laptop and it worked ok
I cant understand what is happening ... can anyone else help me?
If I put the phone in Fastboot Mode, connect it to the laptop, and run the command
Code:
fastboot devices
I can see the phone... but using it as a usb mass storage, nothing happens
its probably hardware then. get them to replace the phone for you.
Humm, thats bad news
The phone is in second hand and I don't have the receipt of the purchase. I will ask the seller if he has it, if not, I guess I will not have a chance to put it to repair under warranty
Also, I have already installed the Cyanogen recovery image, so I guess that would void the warranty, right?
Pushing this topic to the top, has anyone else had this problem?
I had the problem on mine once but it was just related to one pc.
Removed all the drivers off the PC and it worked when I reconnected
@skhell
I don't know where you would find it for a 32A, but assuming you did not change your SPL you can use Fastboot to completely flash a stock config (system, recovery, boot, data, etc)
For instance, Cyanogen's instructions have you fastboot a SAPPIMG.nbh for 32B devices, I am assuming such an image exists for 32a devices as well...
If you can completely re-flash the entire system your warranty claim should be fine.
Yeah, I can restore the phone right as it was originally, the problem is that I don't have a proof of purchase to put it into repair under warranty...
Related
Hi,
I recently acquired a TF101 and I am trying to do some development on it.
I have USB debugging on and tried to put it in APX mode by powering up using vol + and power button. It is connected to laptop running ubuntu 12.04 and I see following kernel messages
[ 3650.272049] usb 3-1: new low-speed USB device number 38 using ohci_hcd
[ 3650.452045] usb 3-1: device descriptor read/64, error -62
[ 3650.736044] usb 3-1: device descriptor read/64, error -62
[ 3651.016046] usb 3-1: new low-speed USB device number 39 using ohci_hcd
[ 3651.196038] usb 3-1: device descriptor read/64, error -62
[ 3651.484049] usb 3-1: device descriptor read/64, error -62
[ 3651.764103] usb 3-1: new low-speed USB device number 40 using ohci_hcd
[ 3652.172100] usb 3-1: device not accepting address 40, error -62
[ 3652.348103] usb 3-1: new low-speed USB device number 41 using ohci_hcd
[ 3652.756046] usb 3-1: device not accepting address 41, error -62
[ 3652.756060] hub 3-0:1.0: unable to enumerate USB device on port 1
any suggesstions ?
viewlessguru said:
Hi,
I recently acquired a TF101 and I am trying to do some development on it.
I have USB debugging on and tried to put it in APX mode by powering up using vol + and power button. It is connected to laptop running ubuntu 12.04 and I see following kernel messages
[ 3650.272049] usb 3-1: new low-speed USB device number 38 using ohci_hcd
[ 3650.452045] usb 3-1: device descriptor read/64, error -62
[ 3650.736044] usb 3-1: device descriptor read/64, error -62
[ 3651.016046] usb 3-1: new low-speed USB device number 39 using ohci_hcd
[ 3651.196038] usb 3-1: device descriptor read/64, error -62
[ 3651.484049] usb 3-1: device descriptor read/64, error -62
[ 3651.764103] usb 3-1: new low-speed USB device number 40 using ohci_hcd
[ 3652.172100] usb 3-1: device not accepting address 40, error -62
[ 3652.348103] usb 3-1: new low-speed USB device number 41 using ohci_hcd
[ 3652.756046] usb 3-1: device not accepting address 41, error -62
[ 3652.756060] hub 3-0:1.0: unable to enumerate USB device on port 1
any suggesstions ?
Click to expand...
Click to collapse
If your using USB 3.0 ports to connect the tablet try switching to a usb 2.0 port. usb3 has been known to cause add issues sometimes.
Try each of your USB ports. I have issues with my tablet not being seen on all but one port on my PC. Even though stuff works in the other ports It still was not seen.
Sent from my Transformer TF101 using xda premium
What do you see on "$lsusb"?
Can you see an Nvidia Device?
Hello,
I have an issue with my U8800.
It is not detected by my PC (Windows 7 x64). When I say it is not detected, I mean nothing happens. Tried all USB ports. In fact, I have tried the phone on 6 diferent PCs (4 with windows 7 x64, 1 with windows 7 x86 and one with Vista x86). The best I could get was usb not recognized (but very quickly) in one of them (x64) but not replicated. It doesn't matter if you go to Pink Screen, with battery, without battery, with sd card or without, etc. Have tried forcing all kinds of drivers, without success. Android SDK is fully installed, etc.
I also tried using 2 diferent Linux live OS's. On one of them, I was able to mount the "CD - the one with the drivers", but again, only once.
I was using Aurora with latest update when this issue started. Never partitioned. I have downgraded to Rom 136. Tried B517 and B528. I'm only able to root the device using Z4root with froyo.
Tried 3 different cables and all of them work without any issues with a Galaxy S3 and a ZTE Racer.
The funny thing is that the U8800 is detected by my car audio system (it uses windows CE 5.0) and plays media files fine. Even the USB Debugging shows up. On another car, with a "usb radio" it also works.
The device itself charges fine in every usb port i have tried
Any help would be appreciated.
Thank you
Hi guys, just an update.
I forgot to mention that the device itself does nothing while connected to the pc. No USB mount or USB Debugging icons. Just the charging message and the lightning icon.
I have tried the device on 5 more PCs and 3 more cables. Not much luck. I did get a few odd behaviours.
This is what I have found out:
Windows 7
With the phone OFF:
If I just plug in the usb cable, it will turn on and after a few seconds, the battery image will appear. While doing that, by using UsbDview, I can see USB Mass Storage Device with the idVendor=12d1, idProduct=1037.
Windows displays "Unrecognized usb device" and a pop up says that windows was unable to find/install drivers for the "unkown device" (error 45 - device is not connected).
Phone turned ON:
If I turn the phone on, no error is displayed and no attempts to install drivers are made. Nothing happens.
Ubuntu (12.0x) - Using the same method with the phone turned OFF:
Dmesg displays:
usb 5-1: new full-speed USB device number 5 using uhci_hcd
hub 5-0:1.0: unable to enumerate USB device on port 5
If I insist, by removing the usb cable, a few times, I get this:
"usb 5-1: new full-speed USB device number 2 using uhci_hcd
[ 2463.956220] usb 5-1: device descriptor read/64, error -71
[ 2464.180120] usb 5-1: device descriptor read/64, error -71
[ 2464.396215] usb 5-1: new full-speed USB device number 3 using uhci_hcd
[ 2464.516211] usb 5-1: device descriptor read/64, error -71
[ 2464.740204] usb 5-1: device descriptor read/64, error -71
[ 2464.956203] usb 5-1: new full-speed USB device number 4 using uhci_hcd
[ 2465.372073] usb 5-1: device not accepting address 4, error -71
[ 2465.484242] usb 5-1: new full-speed USB device number 5 using uhci_hcd
[ 2465.900220] usb 5-1: device not accepting address 5, error -71
[ 2465.900263] hub 5-0:1.0: unable to enumerate USB device on port 1
[ 2467.624209] hub 2-0:1.0: unable to enumerate USB device on port 1
[ 2467.876222] usb 5-1: new full-speed USB device number 6 using uhci_hcd
[ 2468.019363] usb 5-1: not running at top speed; connect to a high speed hub
[ 2468.038249] usb 5-1: New USB device found, idVendor=12d1, idProduct=1037
[ 2468.038262] usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2468.038270] usb 5-1: Product: Android Adapter
[ 2468.038276] usb 5-1: Manufacturer: Huawei Incorporated
[ 2468.038283] usb 5-1: SerialNumber: 20XXXXXXXXXX
[ 2468.130459] Initializing USB Mass Storage driver...
[ 2468.130622] scsi5 : usb-storage 5-1:1.0
[ 2468.130718] usbcore: registered new interface driver usb-storage
[ 2468.130720] USB Mass Storage support registered.
[ 2469.133463] scsi 5:0:0:0: Direct-Access Android Adapter 0100 PQ: 0 ANSI: 2
[ 2469.136395] scsi 5:0:0:1: CD-ROM Android Adapter 0100 PQ: 0 ANSI: 2
[ 2469.139317] scsi 5:0:0:2: Direct-Access Android Adapter 0100 PQ: 0 ANSI: 2
[ 2469.141053] sd 5:0:0:0: Attached scsi generic sg2 type 0
[ 2469.170237] sr1: scsi3-mmc drive: 0x/0x caddy
[ 2469.170496] sr 5:0:0:1: Attached scsi CD-ROM sr1
[ 2469.170578] sr 5:0:0:1: Attached scsi generic sg3 type 5
[ 2469.170762] sd 5:0:0:2: Attached scsi generic sg4 type 0
[ 2469.372234] sd 5:0:0:0: [sdb] Attached SCSI removable disk
[ 2469.421238] sd 5:0:0:2: [sdc] Attached SCSI removable disk"
Phone turned ON:
Only when this information is displayed, If I turn the phone on, it will connect to linux. Usb debugging will come up and I'm able to mount the SD card.
This is very weird. Can anyone help me with this issue?
Hello again,
Over 100 views and not a single idea???
One thing, when I connect the phone to Ubuntu (not in pink screen, as it doesn't work), the internal memory is seen as unallocated. Is this normal? It say 2.0GIG but no file system. I have access to the internal memory on the phone itself. Could this be a clue (The external SD card is visible and accessable).
When i type adb devices, no device is present or if I use adb shell, error: device not found.
lsusb and dmesg show the device.
Bus 006 Device 028: ID 12d1:1037 Huawei Technologies Co., Ltd. Ideos
ls -l /dev/bus/usb/006/028
crw-rw-rw-+ 1 root gabriel 189, 667 Sep 3 09:41 /dev/bus/usb/006/028
A have, at this moment, B517 installed (tried 136, 138, 518, 526, 528 with the same results).
Come on guys, I don't believe this to be a hardware issue. Please help!!!!!!!!!
P.S. I still have IMEI, serial, etc.
jcpbs said:
Hello again,
Over 100 views and not a single idea???
One thing, when I connect the phone to Ubuntu (not in pink screen, as it doesn't work), the internal memory is seen as unallocated. Is this normal? It say 2.0GIG but no file system. I have access to the internal memory on the phone itself. Could this be a clue (The external SD card is visible and accessable).
When i type adb devices, no device is present or if I use adb shell, error: device not found.
lsusb and dmesg show the device.
Bus 006 Device 028: ID 12d1:1037 Huawei Technologies Co., Ltd. Ideos
ls -l /dev/bus/usb/006/028
crw-rw-rw-+ 1 root gabriel 189, 667 Sep 3 09:41 /dev/bus/usb/006/028
A have, at this moment, B517 installed (tried 136, 138, 518, 526, 528 with the same results).
Come on guys, I don't believe this to be a hardware issue. Please help!!!!!!!!!
P.S. I still have IMEI, serial, etc.
Click to expand...
Click to collapse
It is a strange behaviour. The only thing I could recommend you is dial *#*#2846579#*#* and see the usb port setting. On stock ROMs you should be able to change it to something like "normal" or "google".
Blefish said:
It is a strange behaviour. The only thing I could recommend you is dial *#*#2846579#*#* and see the usb port setting. On stock ROMs you should be able to change it to something like "normal" or "google".
Click to expand...
Click to collapse
Belfish, thank you for the reply. I have already tried that. Same result. Someone has suggested if the vold.fstab file has been moddified. I have never touched it so I don't know what I'm looking for. This is what's inside the file:
# Copyright (c) 2010, Code Aurora Forum. All rights reserved.
#
# Redistribution and use in source and binary forms, with or without
# modification, are permitted provided that the following conditions are
# met:
# * Redistributions of source code must retain the above copyright
# notice, this list of conditions and the following disclaimer.
# * Redistributions in binary form must reproduce the above
# copyright notice, this list of conditions and the following
# disclaimer in the documentation and/or other materials provided
# with the distribution.
# * Neither the name of Code Aurora Forum, Inc. nor the names of its
# contributors may be used to endorse or promote products derived
# from this software without specific prior written permission.
#
# THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESS OR IMPLIED
# WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
# MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT
# ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS
# BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
# CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
# SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
# BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
# WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE
# OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN
# IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
# < DTS2010071700153 genghua 20100717 begin
# we modified this command according to our platform to support SD card recognization in user space
# dev_mount sdcard /mnt/sdcard auto /devices/platform/msm_sdcc.1/mmc_host/mmc0
## /* <DTS2010081001800 duangan 20100814 begin */
dev_mount sdcard2 /mnt/sdcard auto /devices/platform/msm_sdcc.4/mmc_host
dev_mount sdcard1 /mnt/sdcard 14 /devices/platform/msm_sdcc.2/mmc_host
## /* DTS2010081001800 duangan 20100814 end> */
# DTS2010071700153 genghua 20100717 end >
Is it supposed to be like that?
Thanks.
The vold.fstab shouldn't matter much. If it is wrong, then it would not let you mount sd card in android too.
I don't really know how to help you. I know there are some NV items that could alter the USB interface, but it's mostly in the kernel side. Maybe you can check your "dmesg" log on your phone. Using a Terminal Emulator, first write su for superuser and then dmesg. It gives you the kernel log messages in Android side (the phone).
Blefish said:
The vold.fstab shouldn't matter much. If it is wrong, then it would not let you mount sd card in android too.
I don't really know how to help you. I know there are some NV items that could alter the USB interface, but it's mostly in the kernel side. Maybe you can check your "dmesg" log on your phone. Using a Terminal Emulator, first write su for superuser and then dmesg. It gives you the kernel log messages in Android side (the phone).
Click to expand...
Click to collapse
Ok, I will do that. I just need to go back to 2.2 so I can root it. Once I have the Logs, I will post it. I really hope to solve this so I can try your new rom. Thank you Blefish
P.S. Is there anything I should be looking for?
Most of the times when i'm connection the device to my laptop (With ubuntu 12.10 on), the phone is connection and disconnection on a loop,
even if the device is on charge only mode. so i can't even charge the device from my laptop
The ubuntu syslog:
Oct 15 18:25:25 bnaya kernel: [260911.917518] usb 3-2: new high-speed USB device number 67 using xhci_hcd
Oct 15 18:25:25 bnaya kernel: [260911.934094] usb 3-2: New USB device found, idVendor=1004, idProduct=6300
Oct 15 18:25:25 bnaya kernel: [260911.934103] usb 3-2: New USB device strings: Mfr=2, Product=5, SerialNumber=0
Oct 15 18:25:25 bnaya kernel: [260911.934109] usb 3-2: Product: USB Charge Only Interface
Oct 15 18:25:25 bnaya kernel: [260911.934113] usb 3-2: Manufacturer: LG Electronics Inc.
Oct 15 18:25:25 bnaya kernel: [260911.936666] usbhid 3-2:1.0: couldn't find an input interrupt endpoint
Oct 15 18:25:25 bnaya mtp-probe: checking bus 3, device 67: "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-2"
Oct 15 18:25:25 bnaya mtp-probe: bus: 3, device: 67 was not an MTP device
Oct 15 18:25:27 bnaya kernel: [260913.907563] usb 3-2: USB disconnect, device number 67
Click to expand...
Click to collapse
And its repeating itself until i disconnect the cable.
Also i discovered only after i bought the device that its not have a mass storage decide connection mode.
I'm working on making the MTP to work, maybe it will solve the problem.
Thanks!
I'm seeing something similar when charging via usb in the car. If I'm listening to something via BT it will pause.
Sent from my VS980 4G using Tapatalk
I just got a new Nook GlowLight (NGL), and came here assuming I would find all sorts of wonderful information about rooting it, and cool hacks I could do to make it more usable. Imagine my surprise when I could only find a couple of threads about it at all, with almost zero information! Finding information is definitely hampered by the name of the device. Any time I google for Nook GlowLight, 99% of the results are instead about the completely different product, Nook Simple Touch with GlowLight. Frustrating!
Anyway, in an effort to get the ball rolling, I will post the little bit that I have been able to find out about my NGL.
I cannot seem to ADB into it. I plugged it in, but ADB does not recognize it. It shows up as a regular mass storage device. The USB VendorID is 2080, and the ProductID is 0007. There seems to be no information out there anywhere about 2080:0007, unfortunately.
I took the back cover off to see if there was a magical "press here to root" button. Sadly, there was not. Since there does not appear to be a NGL teardown annnnnnnnnnnnnywhere on the whole wide Interwebs, I took some amateur photos of mine to share. I didn't want to chance breaking it, as I can't really go and buy a new one right now, so it's not torn down to the individual components, sorry. Hopefully it will be enough to spark some ideas, at least.
I don't know much about hardware hacking, but I've heard about JTAG ports being used to get inside of plenty of Android devices. One of the things I noticed was four unmarked copper pads on the board. That seems about right, as apparently most JTAG interfaces have either 4 or 5 lines, plus Ground. I created a picture with the four unmarked pads + Ground marked.
I know it's not much, but hopefully this information will spark some ideas from people with more experience in cracking these devices! If anyone else has additional information to add, please post it here.
Wow, thanks for the photos.
It's really interesting how they reformulated the Nook to use the small PCB.
It seems to be the same hardware basically.
They are using a different WiFi module than the Jorjin in the old Nooks.
There might be hope for having Bluetooth.
No, those four point that you circled are definitely not JTAG.
Some of the tiny gold contact points near the OMAP 3621 processor could be.
There is a missing IC at the top which could be a TXB0104 level shifter for a UART.
I'd be interested to see if/what is on the bottom of the PCB.
VID 2080 is B&N. They have been using the PIDs sequentially, so 0007 is expected.
Presumably it presents a single USB interface and one UMS volume.
Try rebooting the Nook with the USB connected to a PC.
Does it ever say, "New device found"?
You are not going to find an ADB without modifying the INF file for the ADB driver.
Try downloading Microsoft's UsbView from here. (Thank you, FTDI.)
Run it and select the Nook on the left pane, select all on the right pane and copy it here, please.
Oh! Be sure to overwrite your serial number on the text dump.
It's not a big security risk, but still....
Just type "MYSERIALNUMBER" or something.
USBview
Renate NST said:
Wow, thanks for the photos.
It's really interesting how they reformulated the Nook to use the small PCB.
It seems to be the same hardware basically.
They are using a different WiFi module than the Jorjin in the old Nooks.
There might be hope for having Bluetooth.
No, those four point that you circled are definitely not JTAG.
Some of the tiny gold contact points near the OMAP 3621 processor could be.
There is a missing IC at the top which could be a TXB0104 level shifter for a UART.
I'd be interested to see if/what is on the bottom of the PCB.
VID 2080 is B&N. They have been using the PIDs sequentially, so 0007 is expected.
Presumably it presents a single USB interface and one UMS volume.
Try rebooting the Nook with the USB connected to a PC.
Does it ever say, "New device found"?
You are not going to find an ADB without modifying the INF file for the ADB driver.
Try downloading Microsoft's UsbView from. (Thank you, FTDI.)
Run it and select the Nook on the left pane, select all on the right pane and copy it here, please.
Oh! Be sure to overwrite your serial number on the text dump.
It's not a big security risk, but still....
Just type "MYSERIALNUMBER" or something.
Click to expand...
Click to collapse
I'm not sure if this gonna be help. Anyway, I will copy the data from mine.
Device Descriptor:
bcdUSB: 0x0200
bDeviceClass: 0x00
bDeviceSubClass: 0x00
bDeviceProtocol: 0x00
bMaxPacketSize0: 0x40 (64)
idVendor: 0x2080
idProduct: 0x0007
bcdDevice: 0x0216
iManufacturer: 0x01
0x0409: "B&N"
iProduct: 0x02
0x0409: "NOOK GlowLight"
iSerialNumber: 0x03
0x0409: "MYSERIALNUMBER"
bNumConfigurations: 0x01
ConnectionStatus: DeviceConnected
Current Config Value: 0x01
Device Bus Speed: High
Device Address: 0x02
Open Pipes: 2
Endpoint Descriptor:
bEndpointAddress: 0x81 IN
Transfer Type: Bulk
wMaxPacketSize: 0x0200 (512)
bInterval: 0x00
Endpoint Descriptor:
bEndpointAddress: 0x01 OUT
Transfer Type: Bulk
wMaxPacketSize: 0x0200 (512)
bInterval: 0x01
Configuration Descriptor:
wTotalLength: 0x0020
bNumInterfaces: 0x01
bConfigurationValue: 0x01
iConfiguration: 0x00
bmAttributes: 0xE0 (Bus Powered Self Powered Remote Wakeup)
MaxPower: 0xFA (500 Ma)
Interface Descriptor:
bInterfaceNumber: 0x00
bAlternateSetting: 0x00
bNumEndpoints: 0x02
bInterfaceClass: 0x08
bInterfaceSubClass: 0x06
bInterfaceProtocol: 0x50
iInterface: 0x00
Endpoint Descriptor:
bEndpointAddress: 0x81 IN
Transfer Type: Bulk
wMaxPacketSize: 0x0200 (512)
bInterval: 0x00
Endpoint Descriptor:
bEndpointAddress: 0x01 OUT
Transfer Type: Bulk
wMaxPacketSize: 0x0200 (512)
bInterval: 0x01
I got a little confused between this thread and private messages.
In short, the new Glow does not have ADB enabled out of the box.
The USB dumps are showing just a single UMS storage ("flash" drive) interface.
my nook just gives the same information
Renate NST said:
I got a little confused between this thread and private messages.
In short, the new Glow does not have ADB enabled out of the box.
The USB dumps are showing just a single UMS storage ("flash" drive) interface.
Click to expand...
Click to collapse
my nook just gives exactly the same information, is there any hope for hacking the new nook glowlight?
Sure, there is hope.
There doesn't seem to be any ADB over USB.
A port scan of the WiFi would be a confirmation of no ADB over WiFi.
Check to see if any different VID/PIDs pop up when rebooting with the USB connected.
That could indicate a bootloader, fastboot.
Check to see if recovery has any options besides factory restore.
(Power up with the bottom two buttons depressed.)
Then there are all the possibilities with the case open:
a console interface
a JTAG interface
bootloader jumpers
If B&N releases an update image it could be examined for exploits.
The image could probably be loaded onto an older Nook, rooted and played with.
I ran a complete nmap against the Nook on both TCP and UDP while it was connected to my WiFi. No open ports found.
The USB startup looks more promising, though --
PHP:
Dec 13 21:19:33 MyLinuxBox kernel: [ 741.701292] usb 5-1: new high-speed USB device number 5 using xhci_hcd
Dec 13 21:19:33 MyLinuxBox kernel: [ 741.719705] usb 5-1: unable to get BOS descriptor
Dec 13 21:19:33 MyLinuxBox kernel: [ 741.722625] usb 5-1: New USB device found, idVendor=0451, idProduct=d00e
Dec 13 21:19:33 MyLinuxBox kernel: [ 741.722634] usb 5-1: New USB device strings: Mfr=33, Product=37, SerialNumber=0
Dec 13 21:19:33 MyLinuxBox kernel: [ 741.722639] usb 5-1: Product: OMAP3630
Dec 13 21:19:33 MyLinuxBox kernel: [ 741.722643] usb 5-1: Manufacturer: Texas Instruments
Dec 13 21:19:33 MyLinuxBox mtp-probe: checking bus 5, device 5: "/sys/devices/pci0000:00/0000:00:10.0/usb5/5-1"
Dec 13 21:19:33 MyLinuxBox mtp-probe: bus: 5, device: 5 was not an MTP device
Dec 13 21:19:36 MyLinuxBox kernel: [ 744.721151] usb 5-1: USB disconnect, device number 5
Dec 13 21:19:48 MyLinuxBox kernel: [ 757.351633] usb 5-1: new high-speed USB device number 6 using xhci_hcd
Dec 13 21:19:48 MyLinuxBox kernel: [ 757.371138] usb 5-1: New USB device found, idVendor=2080, idProduct=0007
Dec 13 21:19:48 MyLinuxBox kernel: [ 757.371146] usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Dec 13 21:19:48 MyLinuxBox kernel: [ 757.371152] usb 5-1: Product: NOOK GlowLight
Dec 13 21:19:48 MyLinuxBox kernel: [ 757.371156] usb 5-1: Manufacturer: B&N
Dec 13 21:19:48 MyLinuxBox kernel: [ 757.371160] usb 5-1: SerialNumber: 303xxxxxxxxxxxxx
Dec 13 21:19:48 MyLinuxBox kernel: [ 757.378672] scsi6 : usb-storage 5-1:1.0
Dec 13 21:19:48 MyLinuxBox mtp-probe: checking bus 5, device 6: "/sys/devices/pci0000:00/0000:00:10.0/usb5/5-1"
Dec 13 21:19:48 MyLinuxBox mtp-probe: bus: 5, device: 6 was not an MTP device
Dec 13 21:19:49 MyLinuxBox kernel: [ 758.378396] scsi 6:0:0:0: Direct-Access B&N NOOK GlowLight 0100 PQ: 0 ANSI: 2
Dec 13 21:19:49 MyLinuxBox kernel: [ 758.378613] scsi 6:0:0:1: Direct-Access B&N NOOK GlowLight 0100 PQ: 0 ANSI: 2
Dec 13 21:19:49 MyLinuxBox kernel: [ 758.379838] sd 6:0:0:0: Attached scsi generic sg2 type 0
Dec 13 21:19:49 MyLinuxBox kernel: [ 758.380186] sd 6:0:0:1: Attached scsi generic sg3 type 0
Dec 13 21:19:49 MyLinuxBox kernel: [ 758.390847] sd 6:0:0:1: [sdc] Attached SCSI removable disk
Dec 13 21:19:49 MyLinuxBox kernel: [ 758.392285] sd 6:0:0:0: [sdb] Attached SCSI removable disk
Dec 13 21:20:06 MyLinuxBox kernel: [ 774.892800] sd 6:0:0:0: [sdb] 1040352 512-byte logical blocks: (532 MB/507 MiB)
Dec 13 21:20:06 MyLinuxBox kernel: [ 774.893133] sd 6:0:0:0: [sdb] No Caching mode page found
Dec 13 21:20:06 MyLinuxBox kernel: [ 774.893143] sd 6:0:0:0: [sdb] Assuming drive cache: write through
Dec 13 21:20:06 MyLinuxBox kernel: [ 774.894122] sd 6:0:0:0: [sdb] No Caching mode page found
Dec 13 21:20:06 MyLinuxBox kernel: [ 774.894129] sd 6:0:0:0: [sdb] Assuming drive cache: write through
Dec 13 21:20:06 MyLinuxBox kernel: [ 774.895708] sdb:
As you can see, when the NGL first powers on, it presents itself as VID 0451, PID d00e for three seconds.
This seems like good news! Some sort of TI OMAP boot mode?
Yup, that's the TI 1st stage bootloader (before x-loader & u-boot).
The good news is that it's the same as the Nook Touch.
That means that we can try a bunch of things with the old Nooks.
We also know already where the console UART is on the old Nooks.
Renate NST said:
Yup, that's the TI 1st stage bootloader (before x-loader & u-boot).
The good news is that it's the same as the Nook Touch.
That means that we can try a bunch of things with the old Nooks.
We also know already where the console UART is on the old Nooks.
Click to expand...
Click to collapse
Fantastic. Any suggestions on where to begin? I'm willing to try experiments (though I'd obviously prefer to avoid trying things with a high likelihood of bricking my reader!)
I did some googling to see what I could figure out on my own.
If I am understanding this correctly, that 3 second window between when it identifies itself as 0451:d00e and when it disconnects again, it is receptive to receiving xloader code over the USB.
So we could, in theory, send it an xloader that will read a u-boot over USB as well. Then use that to boot the device into a minimal configuration that would basically "dd" out all of the partitions from the internal flash and emit it over the USB, so we could have a complete image of the built-in disk?
Of course, I have no idea HOW to do those things... But if you can give me some pointers, I am willing to learn.
Yes, that 3 second window is the place.
But it's not a big deal.
As soon as you identify down the line it will pause and you have all the time in the world.
I think the thing to do is to get the concept working on an older Nook with SD card.
These (because the ROM bootloader checks the SD card) are unbrickable
and with the UART console dmesg output we'll have some feedback.
At some point we'll have to make the leap and try it on a SD-less new Nook.
Some of the work has been done for the Nook Color which also uses the OMAP 3630. There is a working boot from USB for the Nook Color. It boots over USB to CWM from Linux. We have CWM for the NST. So I thought this ought to be easy to boot my NST over USB to CWM by using the Nook Color USB boot process and replace the image and ramdisk with the NST CWM. If that works someone could try it on a Nook Glowlight. So I gave it a shot but no go. For some reason the usbboot program that tests every 250ms for an OMAP USB device to show up and then sends over the initial boot program never sees it. My log shows 0451:d00e appearing for 3 seconds and disappearing. If I run lsusb when I boot the NST I see 0451:d00e. But for some reason usbboot doesn't see it and just sits there waiting for an OMAP device. I looked at the code and its definitely looking for that VIDID. I tried recompiling usbboot but still no go. Anybody more familiar with USB internals want to take a look at usbboot and see if they can sort out why it doesn't recognize the NST? Here is some more doc on the OMAP USB boot process.
Edit: Oops, that solution is for Linux, for Windows this comment would be appropriate:
Do you have the generic USB device driver loaded for the OMAP3630?
straygecko said:
Some of the work has been done for the Nook Color which also uses the OMAP 3630. There is a working boot from USB for the Nook Color. It boots over USB to CWM from Linux. We have CWM for the NST. So I thought this ought to be easy to boot my NST over USB to CWM by using the Nook Color USB boot process and replace the image and ramdisk with the NST CWM. If that works someone could try it on a Nook Glowlight. So I gave it a shot but no go. For some reason the usbboot program that tests every 250ms for an OMAP USB device to show up and then sends over the initial boot program never sees it. My log shows 0451:d00e appearing for 3 seconds and disappearing. If I run lsusb when I boot the NST I see 0451:d00e. But for some reason usbboot doesn't see it and just sits there waiting for an OMAP device. I looked at the code and its definitely looking for that VIDID. I tried recompiling usbboot but still no go. Anybody more familiar with USB internals want to take a look at usbboot and see if they can sort out why it doesn't recognize the NST? Here is some more doc on the OMAP USB boot process.
Click to expand...
Click to collapse
Am I going to break my Nook if I try this as-is (the Nook Color version) to see how far the process gets?
That is, this process does not attempt to replace the recovery partition on the device or anything, right? Just boots it by loading an image over USB serial?
As long as it doesn't make any modifications to the Nook at this point, I don't mind trying it out.
Failure between chair and keyboard. Forgot to sudo when running it and couldn't claim the USB device. Now it gets through recognizing the NST and sending aboot & u-boot to the device. Now u-boot doesn't work. Its a Nook Color u-boot so I tried the u-boot from a noogie and the NST boots but not from USB. Looking into compiling a NST u-boot with USB enabled.
---------- Post added at 12:15 PM ---------- Previous post was at 12:10 PM ----------
Edgur said:
Am I going to break my Nook if I try this as-is (the Nook Color version) to see how far the process gets?
That is, this process does not attempt to replace the recovery partition on the device or anything, right? Just boots it by loading an image over USB serial?
As long as it doesn't make any modifications to the Nook at this point, I don't mind trying it out.
Click to expand...
Click to collapse
Its not breaking my NST so I don't think it will brick your Nook Glowlight. AFAIK your assumptions are correct but I make no guarantees as nearly the same process is used to flash a device. Might be better to wait for the process to get ironed out better on an NST where we can backup and restore the device with an SD card in case something goes wrong.
OK, I sorted out how to compile the NST u-boot and applied the patches to it from the diff file provided in the Nook Color usb boot package. I ran into an issue where it won't work using virtualbox so I had to boot with a live CD to get the NST to boot over USB into CWM but it worked! ADB works fine but for some reason backup doesn't seem to work. It hangs on "Backing up boot...." - the first partition to backup. But ADB is a good start so you can explore your Nook Glowlight.
I looked at the kernel source for the Nook Glowlight and it has a different u-boot config. I'm not sure how different but I think the best next step will be to compile a Nook Glowlight u-boot before giving this a try on a new glowlight.
straygecko said:
ADB works fine but for some reason backup doesn't seem to work.
Click to expand...
Click to collapse
The best way to make a backup - through noogie.img by this manual
blog.the-ebook-reader.com/2012/05/02/how-to-backup-and-restore-nook-glow-and-nook-simple-touch/
If this method will adapt, it will be very cool!
Sorry for my bad english.
Dimasio said:
The best way to make a backup - through noogie.img by this manual
blog.the-ebook-reader.com/2012/05/02/how-to-backup-and-restore-nook-glow-and-nook-simple-touch/
If this method will adapt, it will be very cool!
Sorry for my bad english.
Click to expand...
Click to collapse
Yeah, I might try booting a noogie image over USB and see if I can get a backup that way. I'm not sure how either a CWM backup or noogie backup will translate to the Nook Glowlight as both backup methods backup to the SD card which is non-existent on the Nook Glowlight.
Do you have any progress？
straygecko said:
Yeah, I might try booting a noogie image over USB and see if I can get a backup that way. I'm not sure how either a CWM backup or noogie backup will translate to the Nook Glowlight as both backup methods backup to the SD card which is non-existent on the Nook Glowlight.
Click to expand...
Click to collapse
Do you have any progress，I have the new Nook glowlight
As I started to build a u-boot.bin from the B&N source I noticed in the config that USB booting might be built into the new Nook Glowlight. Makes sense for a device without an SD slot. Would somebody with a new Glowlight try powering off then powering on while holding down the n button and see what happens?
1001st problem with bricked device. I tried to flash one of native ROM (jiayus3-5.1_20160121-212346_PC) to almost new phone (ok, almost just received). I replaced file "recovery.img" with TWRP one, checked all checkboxes in SP Flash Tool (as I understand it was fatal mistake), chosem "firmware upgrade" option and clicked "Download". After reboot I even unable to turn it on: LED does not works, looks like it does not charging, all buttons combination (power + volume up or power + volume down or just long power press, etc) does nothing.
On linux (I am using Ubuntu clone, latest Mint) it does not detected without battery. With battery installed in logs I see:
Code:
Aug 2 10:13:44 mobby kernel: [14104.033379] usb 3-6: USB disconnect, device number 40
Aug 2 10:13:46 mobby kernel: [14105.139306] usb 3-6: new full-speed USB device number 41 using xhci_hcd
Aug 2 10:13:46 mobby kernel: [14105.267790] usb 3-6: New USB device found, idVendor=0e8d, idProduct=0003
Aug 2 10:13:46 mobby kernel: [14105.267793] usb 3-6: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Aug 2 10:13:46 mobby kernel: [14105.268802] cdc_acm 3-6:1.0: ttyACM0: USB ACM device
Aug 2 10:13:46 mobby mtp-probe: checking bus 3, device 41: "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-6"
Aug 2 10:13:46 mobby mtp-probe: bus: 3, device: 41 was not an MTP device
Aug 2 10:13:48 mobby kernel: [14107.582861] usb 3-6: USB disconnect, device number 41
Aug 2 10:14:12 mobby kernel: [14131.531452] usb 3-6: new full-speed USB device number 42 using xhci_hcd
Aug 2 10:14:12 mobby kernel: [14131.659849] usb 3-6: New USB device found, idVendor=0e8d, idProduct=0003
Aug 2 10:14:12 mobby kernel: [14131.659854] usb 3-6: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Aug 2 10:14:12 mobby kernel: [14131.660664] cdc_acm 3-6:1.0: ttyACM0: USB ACM device
Aug 2 10:14:12 mobby mtp-probe: checking bus 3, device 42: "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-6"
Aug 2 10:14:12 mobby mtp-probe: bus: 3, device: 42 was not an MTP device
....... and so on until USB detached .....
I tried to connect it to windows host, installed drivers from autoinstaller then connected phone. I hear sound "device connected", see "drives installation" popup then in 2 seconds sound "device disconnected" and everything repeated infinitely.
So SP Flash Tool unable to connect to my device (without battery it is invisible for the system, nothing in logs) to flash another firmware back. Could you recommend something?
UPD: After researching I found that my Linux still can detect it:
Code:
$ lsusb
...............
Bus 003 Device 091: ID 0e8d:0003 MediaTek Inc. MT6227 phone
...............
Nevertheless I still cannot do anything with SP Flashtool
Well, connection coming up for 2 seconds, than disappearing again ... looks like the preloaded is still working and your phone lives. Did you install the VCOM driver (for Windows)? You should be able to flash your phone with SP flashtool.
Blackcrown said:
Well, connection coming up for 2 seconds, than disappearing again ... looks like the preloaded is still working and your phone lives. Did you install the VCOM driver (for Windows)? You should be able to flash your phone with SP flashtool.
Click to expand...
Click to collapse
Thank you for reply. Actually I fixed it already. Problem was in wrong firmware. I tried to flash unsupported firmware or something like this. Then I downloaded FW from Deutch site and it flashed like a charm.