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.
Related
Hello all,
I attached my SGS2 to my linux computer and was able to access the internal SD card, but was unable to access the external SD card. I was able to navigate with RootExplorer when my device wasn't plugged in to verify that it was mounted, and even did so using the adb shell.
After a bunch of reading, I found out that when you plug in the SGS2, it should show up as TWO devices. In fact it does on my work Win7 machine.
Curious to see what was going on, I looked inside the system logs to see if there were multiple partitions and KDE was only picking up the first one:
[157599.812858] usb 2-1.4.7.3: new high speed USB device using ehci_hcd and address 36
[157599.887980] usb 2-1.4.7.3: New USB device found, idVendor=04e8, idProduct=685e
[157599.887988] usb 2-1.4.7.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[157599.887994] usb 2-1.4.7.3: Product: SAMSUNG_Android
[157599.887998] usb 2-1.4.7.3: Manufacturer: SAMSUNG
[157599.888003] usb 2-1.4.7.3: SerialNumber: ------
[157599.889184] scsi18 : usb-storage 2-1.4.7.3:1.0
[157599.889874] cdc_acm 2-1.4.7.3:1.1: This device cannot do calls on its own. It is not a modem.
[157599.889978] cdc_acm 2-1.4.7.3:1.1: ttyACM1: USB ACM device
[157600.888206] scsi 18:0:0:0: Direct-Access Android UMS Composite 00 PQ: 0 ANSI: 2
[157600.888625] sd 18:0:0:0: Attached scsi generic sg2 type 0
[157600.891070] sd 18:0:0:0: [sdc] Attached SCSI removable disk
[157615.570542] sd 18:0:0:0: [sdc] 24133632 512-byte logical blocks: (12.3 GB/11.5 GiB)
[157615.571050] sd 18:0:0:0: [sdc] Assuming drive cache: write through
[157615.573554] sd 18:0:0:0: [sdc] Assuming drive cache: write through
[157615.576323] sdc:
[157735.385098] VFS: busy inodes on changed media or resized disk sdc
[158087.331648] usb 2-1.4.7.3: USB disconnect, address 36
Click to expand...
Click to collapse
As you can see, it found exactly one disk: /dev/sdc.
Am I missing something? Thanks!!
edit:
I may have found a possible solution: http://androidforums.com/samsung-captivate/156875-help-linux-desktop-connect-via-usb.html#post1490358 (Enable "Probe all LUNs on each SCSI device" in the kernel). Will update with resolution.
Did you solve this problem?
How are you connecting? Through the network settings and with the usb mass storage option?
This is what I get this through dmesg:
[17413.586068] usb 1-1: new high speed USB device using ehci_hcd and address 3
[17413.701104] scsi4 : usb-storage 1-1:1.0
[17414.703016] scsi 4:0:0:0: Direct-Access Android UMS Composite 00 PQ: 0 ANSI: 2
[17414.703016] scsi 4:0:0:1: Direct-Access Android UMS Composite 00 PQ: 0 ANSI: 2
[17414.704007] sd 4:0:0:0: Attached scsi generic sg2 type 0
[17414.704467] sd 4:0:0:1: Attached scsi generic sg3 type 0
[17414.710003] sd 4:0:0:0: [sdb] Attached SCSI removable disk
[17414.710003] sd 4:0:0:1: [sdc] Attached SCSI removable disk
Then I can mount either of them manually.
Yep! I didn't get to test it until just now, had some life things that took importance. Looks like the post about the probing for multiple LUNs was correct. The device now shows up as two drives as expected.
I have a Huawei u8160 running Psyke83's Cyanogenmod 7.2 14/8/2012.
I've recently been testing things on my recently activated OTG I've tried to connect a USB Portable HDD, However when I connect the HDD the LED flashes like it's reading/writing , dmesg notices it :
Code:
[INDENT]
<6>[12, khubd] [10776.834610] usb 1-1.4: new full speed USB device using msm_hsusb_host and address 40
<6>[12, khubd] [10777.015514] usb 1-1.4: not running at top speed;
connect to a high speed hub
<7>[12, khubd] [10777.018517] usb 1-1.4: default language 0x0409
<7>[12, khubd] [10777.021505] usb 1-1.4: udev 40, busnum 1, minor = 39
<6>[12, khubd] [10777.021544] usb 1-1.4: New USB device found,
idVendor=174c, idProduct=5106
<6>[12, khubd] [10777.021567] usb 1-1.4: New USB device strings:
Mfr=2, Product=3, SerialNumber=1
<6>[12, khubd] [10777.021589] usb 1-1.4: Product: StoreJet Transcend
<6>[12, khubd] [10777.021607] usb 1-1.4: Manufacturer: StoreJet
Transcend
<6>[12, khubd] [10777.021624] usb 1-1.4: SerialNumber:
WD-WXF1E32VNMN1
<7>[12, khubd] [10777.022149] usb 1-1.4: uevent
done.[/INDENT]
that is what dmesg says directly after connecting.
and when I write lsusb on terminal emulator it returns :
Code:
[INDENT] Bus 001 Device 001: ID 1d6b:0002
Bus 001 Device 041: ID 058f:9254
Bus 001 Device 042: ID 174c:5106[/INDENT]
one of them is always there,and another one is the USB Hub ,and another is the USB HDD
I already successfully mounted an NTFS Flash Drive (Fromatted using Minitool partition wizard,mounted using Paragon NTFS&HFS+) then the problem isn't the File System,when connecting the HDD Paragon NTFS&HFS+ doesn't even notice it
Does your hdd have an external power supply? I am assuming no. The n7 does not output enough power to spin up an external hdd. It can see it, but thats about it. Any hdd's that have power sources external from the phone will work fine. I use an external case that is externally powered with my 1Tb sata hdd. Works great. Its all about the power.
Skyrocket on AOKP by R4ins
yes it uses external power not from my phone
Sent from my U8160 using xda app-developers app
Nexus 7 on AOKP by R4ins
rebel1699 said:
Nexus 7 on AOKP by R4ins
Click to expand...
Click to collapse
What's that supposed to mean?
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
I'm having problems with a Chinese tablet that I believe to be a Mediatek TAB910 with a MTK6592 processor.
It started by having problems with the SIM slots which I put down to a faulty SIM card. I obtained another from the telco but that didn't solve the problem. I concluded that the problem was with the SIM slots or with the software so I did a factory reset.
That appears to have gone well EXCEPT that I cannot get past the "Enter Privacy Protection password" screen (PPP). Let me say at this stage that I have never used PINs on my SIM cards; in fact, if I put a SIM card in which has a PIN then the screen asks for and accepts the SIM PIN but still presents the PPP screen.
I have tried to connect to the tablet by USB in order to try SP FLASH, but that tool doesn't see the tablet at all.
I then tried sudo dmesg|grep usb to see if there was any recognition of the USB and got the following results:
[237820.461318] usb 1-2: new high-speed USB device number 22 using xhci_hcd
[237820.611762] usb 1-2: New USB device found, idVendor=0e8d, idProduct=2000, bcdDevice= 1.00
[237820.611773] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[237820.611779] usb 1-2: Product: MT65xx Preloader
[237820.611783] usb 1-2: Manufacturer: MediaTek
[237823.266112] usb 1-2: USB disconnect, device number 22
[237830.885144] usb 1-2: new high-speed USB device number 23 using xhci_hcd
[237831.034440] usb 1-2: New USB device found, idVendor=0e8d, idProduct=2002, bcdDevice=ff.ff
[237831.034451] usb 1-2: New USB device strings: Mfr=2, Product=3, SerialNumber=4
[237831.034456] usb 1-2: Product: TAB910
[237831.034461] usb 1-2: Manufacturer: MediaTek
[237831.034465] usb 1-2: SerialNumber: 0123456789ABCDEF
[237831.038098] usb-storage 1-2:1.0: USB Mass Storage device detected
[237831.045186] scsi host2: usb-storage 1-2:1.0
[237831.471860] usb 1-2: USB disconnect, device number 23
Click to expand...
Click to collapse
It appears that the tablet is identifying itself, but immediately disconnecting again, hence no response from SP FLASH.
I can get the tablet to drop into two factory setting levels, one with English language instructions, the other with Chinese language instructions. Both of these appear to work as expected when I run through the menu items including, in the Chinese menu, "Eliminate eMMC".
I have also modified the udev files, but seemingly to no avail.
~$ cat /etc/udev/rules.d/80-persistent-usb.rules
SUBSYSTEM==”usb”, ACTION==”add”, ATTR{idVendor}==”0e8d”, ATTR{idProduct}==”2000“
SUBSYSTEM==”usb”, ACTION==”add”, ATTR{idVendor}==”0e8d”, ATTR{idProduct}==”2002“
~$ sudo service udev restart
Click to expand...
Click to collapse
My question is: Where do I go from here before I decide to bin this chablet.
TIA
For your reference.
https://visihow.com/Bypass_Privacy_Protection_Password_on_Android
James_Watson said:
For your reference.
https://visihow.com/Bypass_Privacy_Protection_Password_on_Android
Click to expand...
Click to collapse
Thanks for that but I have already been down that rabbit hole without success. My big problem is that the USB comes up but promptly disconnects again
Usually MTk preloader comport will disconnect if correct bootloader is not detected. So check you've got MTK6592 supported sp flashtool version and original firmware loaded. For privacy protection removal you need to format whole flash except bootloader and flash origin firmware then need to repair imei.
For some models you need to press and hold VOL+ or VOL- or both to get in to flash mode.