Guest Paul Posted May 10, 2010 Report Share Posted May 10, 2010 Anyone got it working yet? Usual tricks don't seem to work! P Link to comment Share on other sites More sharing options...
Guest Paul Posted May 10, 2010 Report Share Posted May 10, 2010 I have fastboot by doing volume down and red button when powering on... P Link to comment Share on other sites More sharing options...
Guest Paul Posted May 21, 2010 Report Share Posted May 21, 2010 Gah, the lack of ADB access is become a real issue when debugging! :rolleyes: P Link to comment Share on other sites More sharing options...
Guest chrish2009 Posted May 21, 2010 Report Share Posted May 21, 2010 Gah, the lack of ADB access is become a real issue when debugging! :rolleyes: P ive had another go at it, cant seem to figure it out. :/ chris Link to comment Share on other sites More sharing options...
Guest cantido Posted May 23, 2010 Report Share Posted May 23, 2010 The phone is a usb composite device and needs usb mode switching to work... I'm sniffing the mode switch stuff so that non-windows users can use this thing. Anyhow, if plug the thing into a windows box and install the software on the virtual cdrom it will install the drivers needed to do the usb mode switch, once the phone has switched it will present a composite device to windows with the adb stuff etc. You can switch the phone in a windows vm and then disconnect it to gain access to adb on a non-windows machine... Link to comment Share on other sites More sharing options...
Guest Paul Posted May 24, 2010 Report Share Posted May 24, 2010 cantido, thanks, how odd! P Link to comment Share on other sites More sharing options...
Guest cantido Posted May 24, 2010 Report Share Posted May 24, 2010 It seems to be pretty common for huawei devices to work like this.. I can get adb running and get a shell up, but I can't get eclipse to install anything on the phone :/ Link to comment Share on other sites More sharing options...
Guest Paul Posted May 24, 2010 Report Share Posted May 24, 2010 The phone is a usb composite device and needs usb mode switching to work... I'm sniffing the mode switch stuff so that non-windows users can use this thing. Anyhow, if plug the thing into a windows box and install the software on the virtual cdrom it will install the drivers needed to do the usb mode switch, once the phone has switched it will present a composite device to windows with the adb stuff etc. You can switch the phone in a windows vm and then disconnect it to gain access to adb on a non-windows machine... Hmmm, I can get access on Windows, but on my Mac it doesn't wanna show... P Link to comment Share on other sites More sharing options...
Guest cantido Posted May 24, 2010 Report Share Posted May 24, 2010 usb_modeswitch -W -v 12d1 -p 1030 -V 12d1 -P 1034 -M "5553424370ab71890600000080010a11060000000000000000000000000000" -s 20 That will switch it on a linux machine.. I'm not sure what you do on osx, maybe there is a mode switch tool for that Link to comment Share on other sites More sharing options...
Guest cantido Posted June 1, 2010 Report Share Posted June 1, 2010 Here is a modified adb binary for linux that you can drop into your android SDK... it's patched with this patch https://review.source.android.com/#change,13552 This fudges the device serial in adb so that the eclipse stuff works. http://www.mediafire.com/?oizmyyw0wwz Link to comment Share on other sites More sharing options...
Guest ixdap Posted June 8, 2010 Report Share Posted June 8, 2010 (edited) I am trying to get 'adb shell' to work, with either the binary I downloaded from google or the one you supplied. I have tried the usb_modeswitch and that failed the first time I tried it but seems to suceed consistently now. after the modeswitch 'adb devices' says: List of devices attached ???????????? offline where that really is a list of question marks. and 'adb shell' says error: device offline ---- update: realised I needed to set the 'Debug USB' thingy. Edited June 8, 2010 by ixdap Link to comment Share on other sites More sharing options...
Guest cantido Posted June 9, 2010 Report Share Posted June 9, 2010 I am trying to get 'adb shell' to work, with either the binary I downloaded from google or the one you supplied. I have tried the usb_modeswitch and that failed the first time I tried it but seems to suceed consistently now. after the modeswitch 'adb devices' says: List of devices attached ???????????? offline where that really is a list of question marks. and 'adb shell' says error: device offline ---- update: realised I needed to set the 'Debug USB' thingy. You need to turn on debugging on the phone.. it's in applications > development in the settings. You need to download the latest version of the SDK and drop the patched binary into "tools". The "??????????" thing is because the device doesn't have a device serial (apparently only HTC devices do, check the linked bug report above), the patch I applied to that adb generates a phony serial. You don't need that if you don't intend to use the ADT plugin with eclipse though. You can install apps via adb even with the broken serial. You just need to turn on debugging in on the phone. :) Link to comment Share on other sites More sharing options...
Guest Linan Posted June 20, 2010 Report Share Posted June 20, 2010 Hmmm, I can get access on Windows, but on my Mac it doesn't wanna show... P Had the same problem. it was solved by using virtualbox. You don't have to install anything on the windows of the virtualbox. only need to boot into windows, enable it from the usb list. then it'll be visible under mac. seems to me there is a hidden command to switch onto the usb mode on huawei devices. Link to comment Share on other sites More sharing options...
Guest greenjim301 Posted August 2, 2010 Report Share Posted August 2, 2010 Here is a modified adb binary for linux that you can drop into your android SDK... it's patched with this patch https://review.source.android.com/#change,13552 This fudges the device serial in adb so that the eclipse stuff works. http://www.mediafire.com/?oizmyyw0wwz Great thanks!I finally got my "Hello Android" worked. Thanks for your adb and your brillient job. Link to comment Share on other sites More sharing options...
Guest ikis Posted August 3, 2010 Report Share Posted August 3, 2010 usb_modeswitch -W -v 12d1 -p 1030 -V 12d1 -P 1034 -M "5553424370ab71890600000080010a11060000000000000000000000000000" -s 20 That will switch it on a linux machine.. I'm not sure what you do on osx, maybe there is a mode switch tool for that Hi unfortunately this is not working for me with my plugged 8110 phone under Ubuntu 10.04. I am getting the messaage below. Any idea? root@adrian-laptop:/home/adrian/Downloads/android-sdk-linux_86/tools# usb_modeswitch -W -v 12d1 -p 1031 -V 12d1 -P 1035 \ -M "5553424370ab71890600000080010a11060000000000000000000000000000" -s 20 Taking all parameters from the command line * usb-modeswitch: handle USB devices with multiple modes * Version 1.1.0 (C) Josua Dietze 2010 * Based on libusb 0.1.12 ! PLEASE REPORT NEW CONFIGURATIONS ! DefaultVendor= 0x12d1 DefaultProduct= 0x1031 TargetVendor= 0x12d1 TargetProduct= 0x1035 TargetClass= not set DetachStorageOnly=0 HuaweiMode=0 SierraMode=0 SonyMode=0 GCTMode=0 MessageEndpoint= not set MessageContent= not set NeedResponse=0 ResponseEndpoint= not set Interface=0x00 InquireDevice enabled (default) Success check enabled, max. wait time 32 seconds System integration mode disabled usb_set_debug: Setting debugging level to 15 (on) usb_os_find_busses: Found 008 usb_os_find_busses: Found 007 usb_os_find_busses: Found 006 usb_os_find_busses: Found 005 usb_os_find_busses: Found 004 usb_os_find_busses: Found 003 usb_os_find_busses: Found 002 usb_os_find_busses: Found 001 usb_os_find_devices: Found 001 on 008 usb_os_find_devices: Found 002 on 007 skipped 1 class/vendor specific interface descriptors usb_os_find_devices: Found 001 on 007 error obtaining child information: Inappropriate ioctl for device usb_os_find_devices: Found 001 on 006 usb_os_find_devices: Found 001 on 005 usb_os_find_devices: Found 001 on 004 usb_os_find_devices: Found 001 on 003 usb_os_find_devices: Found 002 on 002 skipping descriptor 0xB skipped 1 class/vendor specific endpoint descriptors skipped 6 class/vendor specific interface descriptors skipping descriptor 0x25 skipped 1 class/vendor specific endpoint descriptors skipped 8 class/vendor specific interface descriptors usb_os_find_devices: Found 001 on 002 error obtaining child information: Inappropriate ioctl for device usb_os_find_devices: Found 002 on 001 usb_os_find_devices: Found 001 on 001 error obtaining child information: Inappropriate ioctl for device Looking for target devices ... searching devices, found USB ID 1d6b:0001 searching devices, found USB ID 04fc:0003 searching devices, found USB ID 1d6b:0001 searching devices, found USB ID 1d6b:0001 searching devices, found USB ID 1d6b:0001 searching devices, found USB ID 1d6b:0001 searching devices, found USB ID 1d6b:0001 searching devices, found USB ID 064e:a103 searching devices, found USB ID 1d6b:0002 searching devices, found USB ID 12d1:1031 found matching vendor ID searching devices, found USB ID 1d6b:0002 No devices in target mode or class found Looking for default devices ... searching devices, found USB ID 1d6b:0001 searching devices, found USB ID 04fc:0003 searching devices, found USB ID 1d6b:0001 searching devices, found USB ID 1d6b:0001 searching devices, found USB ID 1d6b:0001 searching devices, found USB ID 1d6b:0001 searching devices, found USB ID 1d6b:0001 searching devices, found USB ID 064e:a103 searching devices, found USB ID 1d6b:0002 searching devices, found USB ID 12d1:1031 found matching vendor ID found matching product ID searching devices, found USB ID 1d6b:0002 Found default devices (1) Accessing device 002 on bus 001 ... Using endpoints 0x01 (out) and 0x81 (in) Inquiring device details; driver will be detached ... Looking for active driver ... OK, driver found ("usb-storage") OK, driver "usb-storage" detached SCSI inquiry data (for identification) ------------------------- Vendor String: Android Model String: Adapter Revision String: ffff ------------------------- USB description data (for identification) ------------------------- Manufacturer: Huawei Incorporated Product: Android Mobile Adapter Serial No.: not provided ------------------------- Warning: no switching method given. Checking for mode switch (max. 32 times, once per second) ... Waiting for original device to vanish ... Waiting for original device to vanish ... Waiting for original device to vanish ... Waiting for original device to vanish ... Waiting for original device to vanish ... Waiting for original device to vanish ... Waiting for original device to vanish ... Waiting for original device to vanish ... Waiting for original device to vanish ... Waiting for original device to vanish ... Waiting for original device to vanish ... Waiting for original device to vanish ... Waiting for original device to vanish ... Waiting for original device to vanish ... Waiting for original device to vanish ... Waiting for original device to vanish ... Waiting for original device to vanish ... Waiting for original device to vanish ... Waiting for original device to vanish ... Waiting for original device to vanish ... Waiting for original device to vanish ... Waiting for original device to vanish ... Waiting for original device to vanish ... Waiting for original device to vanish ... Waiting for original device to vanish ... Waiting for original device to vanish ... Waiting for original device to vanish ... Waiting for original device to vanish ... Waiting for original device to vanish ... Waiting for original device to vanish ... Waiting for original device to vanish ... Waiting for original device to vanish ... Original device still present after the timeout Mode switch most likely failed. Bye. Link to comment Share on other sites More sharing options...
Guest cantido Posted August 23, 2010 Report Share Posted August 23, 2010 USB description data (for identification) ------------------------- Manufacturer: Huawei Incorporated Product: Android Mobile Adapter Serial No.: not provided ------------------------- Sorry for the delay... My pulse mini gives this description. USB description data (for identification) ------------------------- Manufacturer: Huawei Incorporated Product: T-Mobile 3G Phone Serial No.: not provided ------------------------- It's possible your firmware will need a different message to do the mode switch. If you have virtual box and a windows xp vm you can easily capture the message using a usb sniffer. Link to comment Share on other sites More sharing options...
Guest Max Waterman Posted April 26, 2011 Report Share Posted April 26, 2011 (edited) Sorry for the delay... My pulse mini gives this description. USB description data (for identification) ------------------------- Manufacturer: Huawei Incorporated Product: T-Mobile 3G Phone Serial No.: not provided ------------------------- It's possible your firmware will need a different message to do the mode switch. If you have virtual box and a windows xp vm you can easily capture the message using a usb sniffer. Hi, I am getting the problem described in this thread with my phone. I had similar output to cantido, where it keeps waiting for the original device to vanish. It output : searching devices, found USB ID 12d1:1030 found matching vendor ID found matching product ID Then : Looking for active driver ... USB error: could not get bound driver: No data available No driver found. Either detached before or never attached SCSI inquiry data (for identification) ------------------------- Vendor String: T-Mobile Model String: 3G Phone Revision String: ffff ------------------------- USB description data (for identification) ------------------------- Manufacturer: Huawei Incorporated Product: T-Mobile 3G Phone Serial No.: not provided ------------------------- Warning: no switching method given. -> Run lsusb to note any changes. Bye. I'm at a loss how to move forward with this now :/ Any clues welcome. Max. EDIT:I've now install Windows7 in Virtualbox on my Linux box. If anyone has any instructions on how to make USB work and sniff the appropriate string, please let me know. Edited April 27, 2011 by Max Waterman Link to comment Share on other sites More sharing options...
Guest Profete162 Posted July 5, 2011 Report Share Posted July 5, 2011 Is the same file available for Windows? I am really looking for adb.exe working, for development. Here is a modified adb binary for linux that you can drop into your android SDK... it's patched with this patch https://review.source.android.com/#change,13552 This fudges the device serial in adb so that the eclipse stuff works. http://www.mediafire.com/?oizmyyw0wwz Link to comment Share on other sites More sharing options...
Guest Andrei2j Posted January 4, 2012 Report Share Posted January 4, 2012 maybe im crazy and to excited,dont know where to post it so bear with me... this piece of software helped and resolved my Win XP issue with the damn ADB creep. Its a cellphone software but after installed ecognised my PoW MoBii !!! HALLELUJAH !!! some links ... http://theunlockr.co...ndroid-devices/ and here is the MIRACLE !!! http://www.junefabri...id/download.php Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now