|
#46
|
|||
|
|||
|
alright im about re install qualcomm diagnostic driver and then try to get android adb driver at least listed in device manager - havent been able to have both at the same time
|
|
#47
|
|||
|
|||
|
okay i deleted android adb then plugged the streak in to the laptop in diagnostics mode, this time instead of popping up a dialog about installing the quallcomm device manager shows
android phone android adb interface neither have the exclamation mark by them now how do i keep and update adb and get quallcomm diagnostics back at the same time, so i can have both when i run qdl? Last edited by marculous; 12-22-2010 at 05:43 PM. |
|
#48
|
||||
|
||||
|
See if you can run the tool. So pull streaks battery, start up tool, go in diag mode, then see if it will let you start
__________________
Samsung Galaxy SII Skyrocket White: Gingerbread 2.3.5 [Rooted] Dell Streak5 locked to AT&T: Gingerbread 2.3.3 [Streakdroid 2.4.4] |
|
#49
|
|||
|
|||
|
Quote:
qdl says android abd, not qc diagnostics 9002 can i update the android adb interface driver by pointing it at quallcomm 9002, if i can find it again? qser.inf i think? Last edited by marculous; 12-22-2010 at 06:01 PM. |
|
#50
|
||||
|
||||
|
Yeah... in diag mode you shouldn't see the adb device. So you can try to update and point to the qser.inf
__________________
Samsung Galaxy SII Skyrocket White: Gingerbread 2.3.5 [Rooted] Dell Streak5 locked to AT&T: Gingerbread 2.3.3 [Streakdroid 2.4.4] |
|
#51
|
||||
|
||||
|
http://searchirc.com/search.php?F=pa...x=0&Submit.y=0
I'll be on here for about another half hour if you want to jump on. Just create a nickname and connect.
__________________
Samsung Galaxy SII Skyrocket White: Gingerbread 2.3.5 [Rooted] Dell Streak5 locked to AT&T: Gingerbread 2.3.3 [Streakdroid 2.4.4] |
|
#52
|
|||
|
|||
|
device manager wont let me update the adb driver with the qcser - it says incompatible
|
|
#53
|
|||
|
|||
|
Quote:
|
|
#54
|
||||
|
||||
|
It's not picking it up right it sounds like... What about just uninstalling them
__________________
Samsung Galaxy SII Skyrocket White: Gingerbread 2.3.5 [Rooted] Dell Streak5 locked to AT&T: Gingerbread 2.3.3 [Streakdroid 2.4.4] |
|
#55
|
|||
|
|||
|
uninstalled android drivers from device manager, did battery pull on streak, plugged back in and device manager said q chip, just updated q chip driver to diagnostics 9002
|
|
#56
|
||||
|
||||
|
Progress
![]() Just for kicks, try to run it without messing with adb portion, maybe a lingering driver is still there and will let the tool finish
__________________
Samsung Galaxy SII Skyrocket White: Gingerbread 2.3.5 [Rooted] Dell Streak5 locked to AT&T: Gingerbread 2.3.3 [Streakdroid 2.4.4] |
|
#57
|
|||
|
|||
|
still no adb - heres the log
LOG -- ###QDLTool: M 2.7.4.8, build ID: 1.301.20101022, time stamp: Wed Dec 22 23:34:00 2010 Check image DBL: C:\Users\marcandjoy\Desktop\repairtool\QDLTool3rd_ 20101022_GAUSB1A130500\images\dbl.mbn ... Check image FSBL: C:\Users\marcandjoy\Desktop\repairtool\QDLTool3rd_ 20101022_GAUSB1A130500\images\fsbl.mbn ... Check image OSBL: C:\Users\marcandjoy\Desktop\repairtool\QDLTool3rd_ 20101022_GAUSB1A130500\images\osbl.mbn ... Check image AMSS: C:\Users\marcandjoy\Desktop\repairtool\QDLTool3rd_ 20101022_GAUSB1A130500\images\amss.mbn ... Check image DSP1: C:\Users\marcandjoy\Desktop\repairtool\QDLTool3rd_ 20101022_GAUSB1A130500\images\dsp1.mbn ... Check image APPSBL: C:\Users\marcandjoy\Desktop\repairtool\QDLTool3rd_ 20101022_GAUSB1A130500\images\appsboot.mbn ... Check image DT: C:\Users\marcandjoy\Desktop\repairtool\QDLTool3rd_ 20101022_GAUSB1A130500\images\DT.img ... Check image boot.img: C:\Users\marcandjoy\Desktop\repairtool\QDLTool3rd_ 20101022_GAUSB1A130500\images\boot.img ... Check image system.img: C:\Users\marcandjoy\Desktop\repairtool\QDLTool3rd_ 20101022_GAUSB1A130500\images\system.img ... Check image userdata.img: C:\Users\marcandjoy\Desktop\repairtool\QDLTool3rd_ 20101022_GAUSB1A130500\images\userdata.img ... Check image recovery.img: C:\Users\marcandjoy\Desktop\repairtool\QDLTool3rd_ 20101022_GAUSB1A130500\images\recovery.img ... Check image logfilter.img: C:\Users\marcandjoy\Desktop\repairtool\QDLTool3rd_ 20101022_GAUSB1A130500\images\logfilter.img ... Check image Region: C:\Users\marcandjoy\Desktop\repairtool\QDLTool3rd_ 20101022_GAUSB1A130500\images\RC_us.img ... Check images: Partition Dbl Fsbl Osbl Amss Dsp1 DT Appsbl Boot System Userdata Recovery LogFilter RCFile Check images ok Download in speedup way Open COM port success OSBL version: 12-5035-AUSB1AM-09 osbl.mbn version: Baseband image version: M8650BAUSB1AM5035SIGN Check device and image is Austin Baseband image version: M8650BAUSB1AM5035SIGN Check device and image is Austin Open COM port success Check Secure Boot is enabled #Set Fast Boot Flag success Open COM port success Test communication success Check Secure Boot is enabled #DBL to DDR success #FSBL to DDR success #OSBL to DDR success #DT to DDR success #backup FSBL to DDR success Run HEX success Check Secure Boot is enabled Streaming hello success Send Security mode success Download partition table success #Download DBL success #Download FSBL success #Download OSBL success #Download DT success #Download backup FSBL success Erase EFS2 success Wait for rebooting ....... ok Wait for modem set up ...... Wait for ADB device ......... ERROR[D2]: wait ADB fastboot mode timeout! Please check that device is exist and driver is properly installed. Download Fail! - 2010/12/22 23:34:40 Elapsed Time: 40.01 sec |
|
#58
|
||||
|
||||
|
Yep, at the adb part. so does device manager show adb composite interface our anything under android device?
__________________
Samsung Galaxy SII Skyrocket White: Gingerbread 2.3.5 [Rooted] Dell Streak5 locked to AT&T: Gingerbread 2.3.3 [Streakdroid 2.4.4] |
|
#59
|
|||
|
|||
|
Quote:
i had to delete q chip from device manager to get android back on, and i deleted android to get q chip back on the list. but i just cant seem to do both - which is what qdl seems to need... |
|
#60
|
|||
|
|||
|
Quote:
I've been following this thread and am at a loss why what worked so easily for me is proving so stubborn now. Just for reference, I followed the steps at the beginning of the QDL thread to make sure the correct ABD was installed, then went through the streakdroid guide from there. The only hitch I had was that I accidentally choose the wrong Qualcomm driver and had to install the proper driver in Dev Man get it to register as a port... It took 10 minutes, max, to get it sorted out and run the tool. What about allowing QDL to connect to the Streak, as indicated in the QDL tool upper panel, and then trying to manually run the exe installer for ADB prior to launching the tool? |
![]() |
| Thread Tools | Search this Thread |
|
|