Related
Hello!
How do i mount my HTC hero on ubuntu?
I have tried everything i know about.
Here's some info about it!
It's connected to the machine now.
Code:
[email protected]:~# dmesg|tail
[167350.745833] VFS: Can't find a valid FAT filesystem on dev sda2.
[167350.746019] qnx4: wrong fsid in superblock.
[167392.539945] FAT: bogus number of reserved sectors
[167392.539952] VFS: Can't find a valid FAT filesystem on dev loop0.
[167392.540057] qnx4: wrong fsid in superblock.
[167429.744606] attempt to access beyond end of device
[167429.744614] loop0: rw=0, want=4, limit=2
[167429.744619] EXT3-fs: unable to read superblock
[167584.269145] FAT: bogus number of reserved sectors
[167584.269154] VFS: Can't find a valid FAT filesystem on dev loop0.
[email protected]:~# sfdisk -l
Disk /dev/sda: 19457 cylinders, 255 heads, 63 sectors/track
Warning: extended partition does not start at a cylinder boundary.
DOS and Linux will interpret the contents differently.
Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0
Device Boot Start End #cyls #blocks Id System
/dev/sda1 0 - 0 0 0 Empty
/dev/sda2 * 0+ 18768- 18769- 150759362 f W95 Ext'd (LBA)
/dev/sda3 18768+ 19457- 689- 5529600 8e Linux LVM
/dev/sda4 0 - 0 0 0 Empty
/dev/sda5 3916+ 18768- 14853- 119300096 7 HPFS/NTFS
/dev/sda6 0+ 3915 3916- 31455207 83 Linux
[email protected]:~# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda6 30G 3.3G 25G 12% /
udev 438M 276K 438M 1% /dev
none 438M 0 438M 0% /dev/shm
none 438M 200K 438M 1% /var/run
none 438M 0 438M 0% /var/lock
none 438M 0 438M 0% /lib/init/rw
/dev/sda5 114G 30G 85G 26% /mnt/sda5
/dev/sda6 30G 3.3G 25G 12% /mnt/sda6
[email protected]:~#
First, you should have your data partition of your SD card formatted as FAT32.
Then connect your Hero to your PC using original USB table (you can use non-original, but not everyone of them works).
You should see notification on hero about connected USB, click on this notification and Hero will ask you if you want to connect it as storage device.
Linux should now recognize your Hero as standard USB flash drive.
This works for me.
hELLO!
How can i format my data-partition on my SD-card to FAT32?
And when i connect the hero to the machine, there is no notification on the notification bar!
sorry for bad english.
Broken USB
Hmm, it seems you have some trouble with USB since Hero does not recognize it. My dmesg looks like this, when I connect my Hero (but before I enable it as storage device):
Code:
[47693.001261] usb 6-2: new full speed USB device using uhci_hcd and address 2
[47693.130013] usb 6-2: device descriptor read/64, error -71
[47693.370011] usb 6-2: device descriptor read/64, error -71
[47693.600011] usb 6-2: new full speed USB device using uhci_hcd and address 3
[47693.730011] usb 6-2: device descriptor read/64, error -71
[47693.971260] usb 6-2: device descriptor read/64, error -71
[47694.201263] usb 6-2: new full speed USB device using uhci_hcd and address 4
[47694.621263] usb 6-2: device not accepting address 4, error -71
[47694.680042] hub 6-0:1.0: unable to enumerate USB device on port 2
[47694.961263] usb 2-4: new high speed USB device using ehci_hcd and address 3
[47695.123330] usb 2-4: configuration #1 chosen from 1 choice
[47695.526904] Initializing USB Mass Storage driver...
[47695.527144] scsi6 : SCSI emulation for USB Mass Storage devices
[47695.527234] usb-storage: device found at 3
[47695.527236] usb-storage: waiting for device to settle before scanning
[47695.527250] usbcore: registered new interface driver usb-storage
[47695.527253] USB Mass Storage support registered.
[47700.521271] usb-storage: device scan complete
[47700.523257] scsi 6:0:0:0: Direct-Access HTC Android Phone 0100 PQ: 0 ANSI: 2
[47700.523603] sd 6:0:0:0: Attached scsi generic sg3 type 0
[47700.533243] sd 6:0:0:0: [sdc] Attached SCSI removable disk
i'd try repartitioning the card, looks like a corrupted filesystem.
I don't think repartitioning will help here. /dev/sda is the disk in his computer, because /dev/sda6 is mounted as /. The dmesg output doesn't say anything about /dev/sdb, and there is not even anything about trying to connect a USB device.
My guess is either the cable is bad, or the USB socket on the computer is not connected.
Hi,
I get the same - in Windows it comes up as an unregognised device, and in linux i get
[ 1724.760062] usb 7-1: new full speed USB device using uhci_hcd and address 18
[ 1724.890058] usb 7-1: device descriptor read/64, error -71
[ 1725.130036] usb 7-1: device descriptor read/64, error -71
[ 1725.360077] usb 7-1: new full speed USB device using uhci_hcd and address 19
[ 1725.492549] usb 7-1: device descriptor read/64, error -71
[ 1725.730242] usb 7-1: device descriptor read/64, error -71
[ 1725.960394] usb 7-1: new full speed USB device using uhci_hcd and address 20
[ 1726.380063] usb 7-1: device not accepting address 20, error -71
[ 1726.500053] usb 7-1: new full speed USB device using uhci_hcd and address 21
[ 1726.920281] usb 7-1: device not accepting address 21, error -71
[ 1726.920302] hub 7-0:1.0: unable to enumerate USB device on port 1
and no option on the Hero to mount the partition. I'm open to suggestions
Try another cable and/or another USB port. E.g. the USB ports at the back of your PC are directly soldered to the mainboard, without a shoddy connector and cable in between.
I have 2 questions. I did a search and found that usb devices should work with the gtab, so I'm trying to mount it.
Any idea how I can mount the devices?
I'm trying to mount
1. 500 GB drive
2. Canon Camera with 32 GB SD card
Second question: Can I mount them both at the same time? It looks like the gtab has 2 USB ports, 1 regular, 1 mini
I'm trying to offload the video clips so I can record some more.
Thanks in advance for the help.
Mini is for Slave
Normal is for Host
I think someone found a way to make the Mini a Host, not to sure.
Does this mean I can only use the regular port to connect to a storage device?
I have no need to swap them....just a need to use both to connect to external hard drives:-D
Can I use a usb hub to connect 2 USB devices? (camera and 500 GB drive)
Well, I can tell you this much as least:
If one wanted to connect 2 USB mass storage devices to their g Tab and were hard pressed to find an alternative, the docking station that fits the proprietary plug has an additional USB port as well as an HDMI port and an ethernet port.
Unfortunately I can't tell you anything else with certainty.
scyld said:
Well, I can tell you this much as least:
If one wanted to connect 2 USB mass storage devices to their g Tab and were hard pressed to find an alternative, the docking station that fits the proprietary plug has an additional USB port as well as an HDMI port and an ethernet port.
Unfortunately I can't tell you anything else with certainty.
Click to expand...
Click to collapse
Thanks
I guess I should still get a netbook for this purpose then.
By the way, for the host port (regular USB port). It seems to connect (I have power on the usb device), but the files are not showing up in the file manager (ES file manager) or ifilemanager. Is there anything else I have to do for it to recognize the drive?
TheFlyingPig said:
By the way, for the host port (regular USB port). It seems to connect (I have power on the usb device), but the files are not showing up in the file manager (ES file manager) or ifilemanager. Is there anything else I have to do for it to recognize the drive?
Click to expand...
Click to collapse
We'll have to take things step by step.
First, is the SD card on the camera a removable microSDHC card? If it is, you could just remove it and insert it into the gTablet's microSDHC slot instead of connecting the camera to a USB hub.
Second, have the 2 devices been detected correctly by the kernel? Both individually and then together on a USB-hub?
For example, if I connect my 1TB Maxtor USB HDD to the gTablet, the status bar message informs me that "SD card blank or has unsupported filesystem". This means that the drive was detected, but the NTFS filesystem on it was not recognized, and therefore the drive was not mounted (the vold program which does the mounting only likes ext4 or VFAT filesystems for automounting). I'm assuming that since you have a 500GB drive, it is formatted as NTFS?
If Android does not detect a drive insertion, check the kernel messages. In a Terminal, after I insert a USB drive, I do:
Code:
$ [B]dmesg | tail -n 20[/B]
[144874.547211] usb 1-1.1: New USB device found, idVendor=0d49, idProduct=7410
[144874.554415] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[144874.562368] usb 1-1.1: Product: Basics Desktop
[144874.567435] usb 1-1.1: Manufacturer: Maxtor
[144874.572010] usb 1-1.1: SerialNumber: 2HBEWHZR
[144874.580165] usb 1-1.1: configuration #1 chosen from 1 choice
[144874.589418] scsi0 : SCSI emulation for USB Mass Storage devices
[144874.601098] usb-storage: device found at 3
[144874.601123] usb-storage: waiting for device to settle before scanning
[144879.597766] scsi 0:0:0:0: Direct-Access Maxtor Basics Desktop 0125 PQ: 0 ANSI: 4
[144879.617283] sd 0:0:0:0: Attached scsi generic sg0 type 0
[144879.624170] sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
[144879.634583] sd 0:0:0:0: [sda] Write Protect is off
[144879.639482] sd 0:0:0:0: [sda] Mode Sense: 2d 08 00 00
[144879.639505] sd 0:0:0:0: [sda] Assuming drive cache: write through
[144879.647662] sd 0:0:0:0: [sda] Assuming drive cache: write through
[144879.653918] sda: sda1
[144879.688927] sd 0:0:0:0: [sda] Assuming drive cache: write through
[144879.695477] sd 0:0:0:0: [sda] Attached SCSI disk
[144879.813410] usb-storage: device scan complete
to check if the drive was detected. I can see by the messages that the Maxtor drive was detected by the kernel and that I can mount it manually by using the /dev/block/sda1 device. If you don't see similar messages, you're out of luck. If the camera is also detected, it may show up as /dev/block/sdbn.
If everything is detected properly, but, just not mounted, you can mount things manually.
For this, you have to know which kernel you're running. There are 2 kernels that are commonly used on the gTablet: clemsyn's and pershoot's. I use pershoot's kernel so my instructions will be for that. The pershoot kernel supports NTFS filesystems, but, this support is not built into the kernel. Support is instead provided using kernel modules which you'll have to download first from the author's website and then load manually.
Download the correct kernel modules file for the running kernel. Find the kernel version first:
Code:
$ [B]uname -a[/B]
Linux localhost 2.6.32.40-cyanogenmod #1 SMP PREEMPT Fri May 13 17:37:53 EDT 2011 armv7l GNU/Linux
The kernel version is 2.6.32.40. I go to http://droidbasement.com/db-blog/ and download the kernel modules file for that kernel version which would be this file for Gingerbased ROMs: lib-2632.40_gb.tar.gz, or, this file for Froyo based ROMS: lib-2632.40.tar.gz. Note the "_gb" suffix. Extract the file on your PC and then transfer these 2 file onto the gTablet: nls_utf8.ko and ntfs.ko. You should, ideally, put them in /system/lib/modules, but, it you can just leave it on the gTablet's SD card.
Load the kernel modules (I'm assuming now that they're on /mnt/sdcard), then mount the HDD:
Code:
$ [B]su[/B]
# [B]insmod /mnt/sdcard/nls_utf8.ko[/B]
# [B]insmod /mnt/sdcard/ntfs.ko[/B]
# [B]mount -t ntfs -o nls=utf8 /dev/block/sda1 /mnt/usbdisk[/B]
The HDD's contents will now be present in /mnt/usbdisk which is a directory that already exists for mounting USB devices. The /dev/block/sda1 device name we determined using the kernel messages. If you have partitions on the HDD, you can mount them individually using their device names which look like /dev/block/sdan, where n is a number. Look in /dev/block/ to see what partitions can be mounted.
To mount the camera, create a new directory somewhere else, let's say /mnt/sdcard/tmp, and then mount it in that directory. I'm assuming here that the camera's SD card was detected as /dev/block/sdb1 and that it has a VFAT (aka FAT32) filesystem on it.
Code:
$ [B]su[/B]
# [B]mount -t vfat /dev/block/sdb1 /mnt/sdcard/tmp[/B]
After you've finished, unmount both devices before you unplug:
Code:
$ [B]su[/B]
# [B]umount /mnt/usbdisk[/B]
# [B]umount /mnt/sdcard/tmp[/B]
TheFlyingPig said:
By the way, for the host port (regular USB port). It seems to connect (I have power on the usb device), but the files are not showing up in the file manager (ES file manager) or ifilemanager. Is there anything else I have to do for it to recognize the drive?
Click to expand...
Click to collapse
The files are in a folder called USBDISK - hunt around, you will find it.
Hi,
I have enabled USB-Debugging in the settings and connected the phone to my computer (running linux), but there is no notification that USB-Debugging was/is actually enabled on the phone and Eclipse doesn't recognize the Evo.
Might I be missing something, is this a bug of the ROM (I know that on Android < 4.0 there was a notification if USB-Debugging was enabled) or something else?
This is the output of dmesg when disabling USB-Debugging:
Code:
[130921.297574] usb 1-8: USB disconnect, device number 109
[130921.672047] usb 1-8: new high-speed USB device number 110 using ehci_hcd
[130921.808493] scsi79 : usb-storage 1-8:1.0
[130922.809698] scsi 79:0:0:0: Direct-Access HTC Android Phone 0000 PQ: 0 ANSI: 2
[130922.810846] sd 79:0:0:0: Attached scsi generic sg2 type 0
[130922.815181] sd 79:0:0:0: [sdb] Attached SCSI removable disk
This is the output when enabling USB-Debugging:
Code:
[131010.824084] usb 1-8: USB disconnect, device number 110
[131011.204101] usb 1-8: new high-speed USB device number 111 using ehci_hcd
[131011.347364] scsi80 : usb-storage 1-8:1.0
[131012.345085] scsi 80:0:0:0: Direct-Access HTC Android Phone 0000 PQ: 0 ANSI: 2
[131012.351805] sd 80:0:0:0: [sdb] Attached SCSI removable disk
[131012.353054] sd 80:0:0:0: Attached scsi generic sg2 type 0
Any hints?
Thank you.
exic
Anyone?
Maybe try a different ROM and see if it works. I'm not GSM, but I've heard that Leedroid is pretty good.
I tried NonSense 3.0.0 which shows the notification "USB-Debugging enabled", but it still isn't recognized by Eclipse. Since LeeDroid unfortunately has no ICS version, I guess I'll have to go with a non-ICS version.
exic said:
Since LeeDroid unfortunately has no ICS version, I guess I'll have to go with a non-ICS version.
Click to expand...
Click to collapse
What I meant was to try Leedroid just to see if it works on a Gingerbread ROM. If it does, then it is the ICS GSM leak. If not, then it could be something else (like your computer).
Last week I tried again with LeeDroid and obviously nothing worked because I hadn't made my computer ready. I was confused because I was used to seeing "USB debugging enabled" in the notifications which didn't appear on LeeDroid either.
Hello guys!
I have a Huawei Ascend Y300 phone.
What did I do? - I was trying to expand the data partition. So I tried partitioning my sd card (external flash). I was very careful not to touch anything that said blk0 in /dev/mmcblk . My external flash was at /dev/mmcblk1 and the internal flash was at /dev/mmcblk0. I was clear and was doing everything right. But, I formatted the /dev/mmcblk0p2 accidentally while copy-pasting the code :crying: :crying: :crying: :crying: ....
Then I did "reboot to recovery" from ClockWork Recovery. (I was running a CWM recovery and CyanogenMod, very smoothly with no problems in the past 2-3 months).
That was the last time my phone was ever alive. :crying:
How is it now?
Super bricked with the following symptoms
- Power button / volume buttons won't work.
- The phone won't turn on in any mode whatsoever.
When I ran lsusb, the only mode that was detected was Qualcomm modem.
I used some tutorials and QPST to do some 'fixes'. It didn't seem to work though.
The tutorial I referred to was this: http://forum.xda-developers.com/showthread.php?t=2341320
I only went till getting the phone recognized as an sd card (even when the battery is off). Power buttons still don't work. On linux it shows 4 partitions:
/dev/sdb1 20KB
/dev/sdb2 150KB
/dev/sdb3 5KB
/dev/sdb4 600KB
Unallocated Space 3.64 GB
I am stuck here now. Is there a way I could simply flash an image/kernel onto this space and get my phone working again?
I have a few questions:
1. Is this a hard-brick? Can I get my phone working again?
2. Can the partition where fastboot or boot lies be deleted?
3. If the boot manager is deleted, the phone will not know what to do when it is powered on right? So it will look as dead as it looks in my case?
4. Are there any parts of the phone that are write proof?
Any help is greatly appreciated!
Thank you so much.
p.s. would it not be so easy if phones had BIOS like computers have - on a real ROM or EEPROM and not flash ? And if android came in a bootable flash SD card; so that we could boot from SD card and install android like we install other OS's ....?
ksatyaki said:
Hello guys!
I have a Huawei Ascend Y300 phone.
What did I do? - I was trying to expand the data partition. So I tried partitioning my sd card (external flash). I was very careful not to touch anything that said blk0 in /dev/mmcblk . My external flash was at /dev/mmcblk1 and the internal flash was at /dev/mmcblk0. I was clear and was doing everything right. But, I formatted the /dev/mmcblk0p2 accidentally while copy-pasting the code :crying: :crying: :crying: :crying: ....
Then I did "reboot to recovery" from ClockWork Recovery. (I was running a CWM recovery and CyanogenMod, very smoothly with no problems in the past 2-3 months).
That was the last time my phone was ever alive. :crying:
How is it now?
Super bricked with the following symptoms
- Power button / volume buttons won't work.
- The phone won't turn on in any mode whatsoever.
When I ran lsusb, the only mode that was detected was Qualcomm modem.
I used some tutorials and QPST to do some 'fixes'. It didn't seem to work though.
The tutorial I referred to was this: http://forum.xda-developers.com/showthread.php?t=2341320
I only went till getting the phone recognized as an sd card (even when the battery is off). Power buttons still don't work. On linux it shows 4 partitions:
/dev/sdb1 20KB
/dev/sdb2 150KB
/dev/sdb3 5KB
/dev/sdb4 600KB
Unallocated Space 3.64 GB
I am stuck here now. Is there a way I could simply flash an image/kernel onto this space and get my phone working again?
I have a few questions:
1. Is this a hard-brick? Can I get my phone working again?
2. Can the partition where fastboot or boot lies be deleted?
3. If the boot manager is deleted, the phone will not know what to do when it is powered on right? So it will look as dead as it looks in my case?
4. Are there any parts of the phone that are write proof?
Any help is greatly appreciated!
Thank you so much.
p.s. would it not be so easy if phones had BIOS like computers have - on a real ROM or EEPROM and not flash ? And if android came in a bootable flash SD card; so that we could boot from SD card and install android like we install other OS's ....?
Click to expand...
Click to collapse
OK, before you follow anymore "guides" let's try and get a understanding of what you have, where you are and where its possible to go from here.
Start by researching and posting about the device, its CPU etc, I can help once I know what it is, I don't have time to research every device I get asked to look at. Check the partition super thread too and see if your device is listed.
darkspr1te
Sent from my Nexus 7 using Tapatalk
darkspr1te said:
OK, before you follow anymore "guides" let's try and get a understanding of what you have, where you are and where its possible to go from here.
Start by researching and posting about the device, its CPU etc, I can help once I know what it is, I don't have time to research every device I get asked to look at. Check the partition super thread too and see if your device is listed.
darkspr1te
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
The processor is a Snapdragon S4 MSM8225 - the same is used in HTC Desire SV, HTC Desire X, Huawei Ascend G510, LG Optimus L7 II
http://forum.xda-developers.com/showthread.php?t=1959445 = This thread doesn't have my phone's info. Is this the one you were talking about?
Thank you so much for replying!!!
Chittaranjan
ksatyaki said:
The processor is a Snapdragon S4 MSM8225 - the same is used in HTC Desire SV, HTC Desire X, Huawei Ascend G510, LG Optimus L7 II
http://forum.xda-developers.com/showthread.php?t=1959445 = This thread doesn't have my phone's info. Is this the one you were talking about?
Thank you so much for replying!!!
Chittaranjan
Click to expand...
Click to collapse
try this might help you unbricking your device : http://en.club.vmall.com/forum.php?mod=viewthread&tid=13433&highlight=unbrick+huawei
rophaq said:
try this might help you unbricking your device : http://en.club.vmall.com/forum.php?mod=viewthread&tid=13433&highlight=unbrick+huawei
Click to expand...
Click to collapse
That guide seems to be aimed at mediatek chip set.
Sent from my Nexus 7 using Tapatalk
---------- Post added at 09:00 AM ---------- Previous post was at 08:03 AM ----------
ksatyaki said:
The processor is a Snapdragon S4 MSM8225 - the same is used in HTC Desire SV, HTC Desire X, Huawei Ascend G510, LG Optimus L7 II
http://forum.xda-developers.com/showthread.php?t=1959445 = This thread doesn't have my phone's info. Is this the one you were talking about?
Thank you so much for replying!!!
Chittaranjan
Click to expand...
Click to collapse
What is the devices pid/vid in Linux or windows, in Linux do
lsusb
at prompt, in windows, goto device manager,
Sent from my Nexus 7 using Tapatalk
darkspr1te said:
That guide seems to be aimed at mediatek chip set.
Sent from my Nexus 7 using Tapatalk
---------- Post added at 09:00 AM ---------- Previous post was at 08:03 AM ----------
What is the devices pid/vid in Linux or windows, in Linux do
lsusb
at prompt, in windows, goto device manager,
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
lsusb returns:
Bus 002 Device 003: ID 05c6:9006 Qualcomm, Inc.
dmesg (with battery):
[ 5961.920193] usb 2-1.3: new high-speed USB device number 4 using ehci_hcd
[ 5962.013745] usb 2-1.3: config 1 has an invalid interface number: 20 but max is 1
[ 5962.013757] usb 2-1.3: config 1 has no interface number 1
[ 5962.015114] usb 2-1.3: New USB device found, idVendor=05c6, idProduct=9006
[ 5962.015126] usb 2-1.3: New USB device strings: Mfr=3, Product=2, SerialNumber=0
[ 5962.015132] usb 2-1.3: Product: Qualcomm CDMA Technologies MSM
[ 5962.015138] usb 2-1.3: Manufacturer: Qualcomm, Incorporated
[ 5962.017375] scsi7 : usb-storage 2-1.3:1.20
[ 5963.018250] scsi 7:0:0:0: Direct-Access Qualcomm MMC Storage 2.31 PQ: 0 ANSI: 2
[ 5963.020249] sd 7:0:0:0: Attached scsi generic sg2 type 0
[ 5963.021533] sd 7:0:0:0: [sdb] 7634944 512-byte logical blocks: (3.90 GB/3.64 GiB)
[ 5963.022398] sd 7:0:0:0: [sdb] Write Protect is off
[ 5963.022409] sd 7:0:0:0: [sdb] Mode Sense: 0f 0e 00 00
[ 5963.023242] sd 7:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 5963.030465] sdb: sdb1 sdb2 sdb3 sdb4
[ 5963.036936] sd 7:0:0:0: [sdb] Attached SCSI removable disk
lsusb when battery removed:
Bus 002 Device 005: ID 05c6:f006 Qualcomm, Inc.
dmesg when I remove the battery:
[ 6010.193475] usb 2-1.3: USB disconnect, device number 4
[ 6010.196912] sd 7:0:0:0: [sdb] Synchronizing SCSI cache
[ 6010.197026] sd 7:0:0:0: [sdb]
[ 6010.197033] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[ 6010.904344] usb 2-1.3: new high-speed USB device number 5 using ehci_hcd
[ 6011.038520] usb 2-1.3: New USB device found, idVendor=05c6, idProduct=f006
[ 6011.038523] usb 2-1.3: New USB device strings: Mfr=3, Product=2, SerialNumber=0
[ 6011.038525] usb 2-1.3: Product: Qualcomm CDMA Technologies MSM
[ 6011.038527] usb 2-1.3: Manufacturer: Qualcomm, Incorporated
[ 6011.108889] usbcore: registered new interface driver usbhid
[ 6011.108897] usbhid: USB HID core driver
[ 6011.131114] hid-generic 0003:05C6:F006.0001: hiddev0,hidraw0: USB HID v1.10 Device [Qualcomm, Incorporated Qualcomm CDMA Technologies MSM] on usb-0000:00:1d.0-1.3/input0
Any insights yet?
ksatyaki said:
Any insights yet?
Click to expand...
Click to collapse
When the device is in sd card mode, does it always boot like.that with the battery?
darkspr1te said:
When the device is in sd card mode, does it always boot like.that with the battery?
Click to expand...
Click to collapse
I don't understand what sd card mode is. How do you put it in sd card mode?
ksatyaki said:
lsusb returns:
Bus 002 Device 003: ID 05c6:9006 Qualcomm, Inc.
dmesg (with battery):
[ 5961.920193] usb 2-1.3: new high-speed USB device number 4 using ehci_hcd
[ 5962.013745] usb 2-1.3: config 1 has an invalid interface number: 20 but max is 1
[ 5962.013757] usb 2-1.3: config 1 has no interface number 1
[ 5962.015114] usb 2-1.3: New USB device found, idVendor=05c6, idProduct=9006
[ 5962.015126] usb 2-1.3: New USB device strings: Mfr=3, Product=2, SerialNumber=0
[ 5962.015132] usb 2-1.3: Product: Qualcomm CDMA Technologies MSM
[ 5962.015138] usb 2-1.3: Manufacturer: Qualcomm, Incorporated
[ 5962.017375] scsi7 : usb-storage 2-1.3:1.20
[ 5963.018250] scsi 7:0:0:0: Direct-Access Qualcomm MMC Storage 2.31 PQ: 0 ANSI: 2
[ 5963.020249] sd 7:0:0:0: Attached scsi generic sg2 type 0
[ 5963.021533] sd 7:0:0:0: [sdb] 7634944 512-byte logical blocks: (3.90 GB/3.64 GiB)
[ 5963.022398] sd 7:0:0:0: [sdb] Write Protect is off
[ 5963.022409] sd 7:0:0:0: [sdb] Mode Sense: 0f 0e 00 00
[ 5963.023242] sd 7:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 5963.030465] sdb: sdb1 sdb2 sdb3 sdb4
[ 5963.036936] sd 7:0:0:0: [sdb] Attached SCSI removable disk
lsusb when battery removed:
Bus 002 Device 005: ID 05c6:f006 Qualcomm, Inc.
dmesg when I remove the battery:
[ 6010.193475] usb 2-1.3: USB disconnect, device number 4
[ 6010.196912] sd 7:0:0:0: [sdb] Synchronizing SCSI cache
[ 6010.197026] sd 7:0:0:0: [sdb]
[ 6010.197033] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[ 6010.904344] usb 2-1.3: new high-speed USB device number 5 using ehci_hcd
[ 6011.038520] usb 2-1.3: New USB device found, idVendor=05c6, idProduct=f006
[ 6011.038523] usb 2-1.3: New USB device strings: Mfr=3, Product=2, SerialNumber=0
[ 6011.038525] usb 2-1.3: Product: Qualcomm CDMA Technologies MSM
[ 6011.038527] usb 2-1.3: Manufacturer: Qualcomm, Incorporated
[ 6011.108889] usbcore: registered new interface driver usbhid
[ 6011.108897] usbhid: USB HID core driver
[ 6011.131114] hid-generic 0003:05C6:F006.0001: hiddev0,hidraw0: USB HID v1.10 Device [Qualcomm, Incorporated Qualcomm CDMA Technologies MSM] on usb-0000:00:1d.0-1.3/input0
Click to expand...
Click to collapse
In the log it shows a 3gb partition sdb when battery is in, this is sdcard mode
ksatyaki said:
I don't understand what sd card mode is. How do you put it in sd card mode?
Click to expand...
Click to collapse
The answer to your original question is yes.
Thanks.
ksatyaki said:
The answer to your original question is yes.
Thanks.
Click to expand...
Click to collapse
So the first thing to do is take a copy of that partition, we then analyze it to see what data is not corrupt or missing, we should then be able to re-write the bootloader section and hopefully get it back online, that's a simplification of the actual tasks though.
darkspr1te
Hi,
You make it sound simple. I hope I can get it back online.
I think all partitions are now reset. This, I assume, is a consequence of using QPST. Is this right?
Or does QPST restore important partitions again?
How do I write/flash a bootloader?
Thank you so much for your help.
If this means anything at all, now my phone vibrates for a small duration when I press the power button. It is the same pulse that occurs when the phone boots. But now it keeps giving those pulses (as though in a loop trying constantly to boot but failing). Doesn't switch on.
Hiya mate, just wondering if you managed to sort your y300 out? I got a similar problem with mine, it says emmc is read only and can't do force update but can get into stock recovery and bootloader.. is there anyone with any idea of how to solve this problem?
Sent from my GT-I5800 using Tapatalk 2
No luck
I didn't get any fixes. I am thankful to what happened in a sense. Life is much better without a "smart" phone.
Hey guys,
Currently i`m digging into this matter. So here's the concept:
[HU] - one of the back USB's
|
[USB Hub] - powered form an external power supply (external 5V)
| |
U1 U2 - (32GB USB Drives)
A.) Current behaviour
- only the first inserted USB drive get's mounted under /mnt/usb_storage2
- the second usb drive is recognised by the kernel and does not get mounted by the system (not assigned to any "drive letter" so to speak(i think)).
B.) Current investigations:
B.1 ) by unpacking the boot.img - fstab.rk30board.bootmode.*
Code:
/devices/platform/usb20_otg/usb /mnt/usb_storage vfat defaults voldmanaged=usb_storage:auto
/devices/platform/usb20_host/usb /mnt/usb_storage2 vfat defaults voldmanaged=usb_storage2:auto
B.2) by unpacking the boot.img - init.rk30board.rc
Code:
[13] export THIRD_VOLUME_STORAGE /mnt/usb_storage
[14] mkdir /mnt/usb_storage 0000 system system
[15] export THIRD_VOLUME_STORAGE2 /mnt/usb_storage2
[16] mkdir /mnt/usb_storage2 0000 system system
On the Application Side, for example MTCAPKInstall_source/com/hct/apkinstall/DevListAdapter.java
Code:
} else if (path.equals("/mnt/usb_storage")) {
holder.Image.setImageResource(R.drawable.usbhost);
holder.ImageName.setText(this.mContext.getString(R.string.usb1));
} else if (path.equals("/mnt/usb_storage2")) {
holder.Image.setImageResource(R.drawable.usbhost);
holder.ImageName.setText(this.mContext.getString(R.string.usb2));
This can be solved easily by creating a for, or by duplication each else if (the copy/paste way )
I need to do some more tests... i`m also interested for your opinions/experience with this (What have you tested, What worked, What did not work, Why is not working, etc..)
So cheers to everyone and keep you posted
So far i rulled out the usb driver, internal hub.. It has something to do with the block creation and vold...
Will dig more tomorrow(i hope)
okey, so baseline the issue is related to VOLD
VOLD does not generate the block device for the new devices... i`m not 100% sure that VOLD handles the block device generation
for the time being i managed to mount 3 separate partitions from the same USB storage -> by doing this i ruled out the kernel itself, the irq assignment, etc..
I need to dig deeper into VOLD and to see exactly what is the process for generating the block device eg (/dev/block/vold/8:X)
from this point it would be nice to exchange some experience with someone that really know how things work on Android, i`m an iOS user, and the HU is my first Android System
I can't help as haven't gone down the road of digging to deep into kernels and Roms due to other commitments..
But just want to offer words of encouragement as you are working towards a good course..
I don't use a mobile modem and so at the moment that spare usbport is doing nothing. Would be nice to load it up with a spare USB drive I have around here .
That then brings up the powering up thread which the boys have already sorted..
So once you crack this and get a kernel mode going we are good to go..
Sent from my SM-G900I using Tapatalk
I tried to have a look in the binary code of vold shipped with the firmware, but friday was short... I'll continue my work next week
Keep you guys posted
In the past i did some test with a 4 Port USB hub. I connected several USB sticks and a 350 gb harddisk. They were not recognised by rootexplorer or android itself, but ESF file Explorer did recognised all of the devices.
Another strange thing is that when i connect a USB RTL dab+ dongle on the First USB Port on my hui and the harddisk on the other usb port my GPS is not working propperly.
well i`m 100% sure that the hub is not the issue, because:
<<1'st usb drive>>
<6>[ 1757.992589] usb 2-1.3: new high speed USB device number 30 using usb20_host
<6>[ 1758.093203] usb 2-1.3: New USB device found, idVendor=0781, idProduct=5204
<6>[ 1758.093230] usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
<6>[ 1758.093282] usb 2-1.3: Product: Cruzer Crossfire
<6>[ 1758.093303] usb 2-1.3: Manufacturer: SanDisk Corporation
<6>[ 1758.093322] usb 2-1.3: SerialNumber: 000016A29874531B
<4>[ 1758.094142] --mtc usb storage 2-1.3 0781 5204
<6>[ 1758.094989] scsi11 : usb-storage 2-1.3:1.0
<5>[ 1759.092957] scsi 11:0:0:0: Direct-Access SanDisk Cruzer 4.05 PQ: 0 ANSI: 2
<5>[ 1759.094087] sd 11:0:0:0: [sda] 16055949 512-byte logical blocks: (8.22 GB/7.65 GiB)
<5>[ 1759.094577] sd 11:0:0:0: [sda] Write Protect is off
<7>[ 1759.094601] sd 11:0:0:0: [sda] Mode Sense: 03 00 00 00
<3>[ 1759.095072] sd 11:0:0:0: [sda] No Caching mode page present
<3>[ 1759.095095] sd 11:0:0:0: [sda] Assuming drive cache: write through
<3>[ 1759.098162] sd 11:0:0:0: [sda] No Caching mode page present
<3>[ 1759.098183] sd 11:0:0:0: [sda] Assuming drive cache: write through
<6>[ 1759.100316] sda: sda1
<3>[ 1759.104583] sd 11:0:0:0: [sda] No Caching mode page present
<3>[ 1759.104621] sd 11:0:0:0: [sda] Assuming drive cache: write through
<5>[ 1759.104663] sd 11:0:0:0: [sda] Attached SCSI removable disk
<7>[ 1759.846560] SELinux: initialized (dev sda1, type vfat), uses genfs_contexts
<<2'nd usb drive>>
<6>[ 1956.392593] usb 2-1.2: new high speed USB device number 31 using usb20_host
<6>[ 1956.493577] usb 2-1.2: New USB device found, idVendor=0951, idProduct=1666
<6>[ 1956.493616] usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
<6>[ 1956.493647] usb 2-1.2: Product: DataTraveler 3.0
<6>[ 1956.493666] usb 2-1.2: Manufacturer: Kingston
<6>[ 1956.493683] usb 2-1.2: SerialNumber: 60A44C425294BE10A9820D20
<4>[ 1956.494632] --mtc usb storage 2-1.2 0951 1666
<4>[ 1960.190620] ~ arm_rev_16bits err0 0
the GUI applications are dependent of Device Block Assignment, as you can clearly see, kernel recognises both USB Storage devices, but only the first is assigned with a block device.
okey, so i had a chance to check with IDA the vold binary from our units... seems that vold binary is custom than from other rom's
i will do some tests on the unit itself with a modified version of vold to see what happens
Later Edit,
vold has nothing to do with the block assignment ... on the front USB port also known by the unit : usb20_otg works like a charm... i added 4 USB Drivers each one named accordingly -> sda, sdb, etc.. i managed to mount them manually -> success
On the rear USB also known by the unit usb20_hub it still does not work, VOLD was stopped and removed during tests
clearly things do not add up.. and VOLD so far seems to be ok..
i ran out of ideas
i'm not a developer, but if you find a solution for that problem, you'll be a hero. hope you have finally the idea that will be the right one