Hi, Did some more work on this problem since my device is not accessable since the adb line malfunctioned. That make it hard to do anything with it except use fastboot.
Qualcomm has indicated that this is indeed broken. Not because of fastboot but from loading a new kernel on the device. The new kernel has an incorrect usb device app PID. They hard code the PID into their arch boards file. This needs to be changed to correct the problem. I am still working on it now and will keep the community informed. There may also be some issue with fastboot as you mentioned but I have not discovered anything related with this new platform. /mpd On Mar 1, 2011 1:29 AM, "Steve Modica" <[email protected]> wrote: > > On Mar 1, 2011, at 2:28 AM, mike digioia wrote: > >> But what breaks in adb when using fastboot? and why can't i just fix it? kind of like using the usb interface with adb and fastboot. i should be able to reload the adb daemon and server onto my snapdragon to see it work again. it worked fine for 3 days using fastboot and adb. > > You raise a good point. I read someone telling me it was broken with fastboot and left it at that. We were too busy working on other stuff to mess with it. You should fix that ;) > > > -- > Steve Modica > CTO - Small Tree Communications > www.small-tree.com > phone: 651-209-6509 ext 301 > mobile: 651-261-3201 > > > > > > > -- > unsubscribe: [email protected] > website: http://groups.google.com/group/android-kernel -- unsubscribe: [email protected] website: http://groups.google.com/group/android-kernel
