Here's a zip created by cwm-220.127.116.11 of my current v2.1, you can probably flash it with 'adb sideload', hope it works. Make sure you have a backup in case something goes wrong, I take no responsibility.
Flashed Android KK 4.4.4 and the vendor/product ID reverted to normal:
Bus 001 Device 037: ID 22b8:2e76 Motorola PCS
Flashed b2g-20150104-falcon.zip and they changed:
Bus 001 Device 091: ID 05c6:9039 Qualcomm, Inc.
How does that happen???
Here's the output from mtp-detect if it's of any help (notice vendor/product id are different from what one finds on Google for Moto G):
libmtp version: 1.1.9
Listing raw device(s)
Device 0 (VID=05c6 and PID=9039) is a Qualcomm (for PhiComm) C230w (MTP).
Found 1 device(s):
Qualcomm (for PhiComm): C230w (MTP) (05c6:9039) @ bus 2, dev 36
Attempting to connect device(s)
Android device detected, assigning default bug flags
Error 1: Get Storage information failed.
Error 2: PTP Layer error 02fe: get_handles_recursively(): could not get object handles.
Error 2: Error 02fe: PTP: Protocol error, data expected
USB low-level info:
IN endpoint maxpacket: 512 bytes
OUT endpoint maxpacket: 512 bytes
Raw device info:
Bus location: 2
Device number: 36
Device entry info:
Vendor: Qualcomm (for PhiComm)
Vendor id: 0x05c6
Product: C230w (MTP)
Vendor id: 0x9039
Device flags: 0x18008106
Configuration 0, interface 0, altsetting 0:
Interface description contains the string "MTP"
Device recognized as MTP, no further probing.
Model: Moto G
Device version: 1.0
Serial number: TA8830PFJW
Vendor extension ID: 0x00000006
Vendor extension description: microsoft.com: 1.0; android.com: 1.0;
Detected object size: 64 bits
Here's the relevant part in dmesg after plugging in the phone with USB storage (MTP) enabled:
[ 891.310736] usb 2-8: new high-speed USB device number 5 using ehci-pci
[ 891.524348] usb-storage 2-8:1.5: USB Mass Storage device detected
[ 891.524929] scsi6 : usb-storage 2-8:1.5
[ 891.525059] usbcore: registered new interface driver usb-storage
[ 891.536972] usbcore: registered new interface driver uas
[ 891.595005] usbcore: registered new interface driver cdc_wdm
[ 891.609388] qmi_wwan 2-8:1.4: cdc-wdm0: USB WDM device
[ 891.609946] qmi_wwan 2-8:1.4 wwan0: register 'qmi_wwan' at usb-0000:00:02.1-8, WWAN/QMI device, 06:9c:4d:b8:22:b4
[ 891.610043] usbcore: registered new interface driver qmi_wwan
[ 891.635123] audit: type=1701 audit(1431516896.478:4): auid=4294967295 uid=0 gid=0 ses=4294967295 pid=469 comm="systemd-udevd" exe="/usr/lib/systemd/systemd-udevd" sig=6
[ 891.701101] usb 2-8: USB disconnect, device number 5
[ 891.702015] qmi_wwan 2-8:1.4 wwp0s2f1u8i4: unregister 'qmi_wwan' usb-0000:00:02.1-8, WWAN/QMI device
[ 891.954481] usb 2-8: new high-speed USB device number 6 using ehci-pci
[ 897.857833] usb 2-8: USB disconnect, device number 6
[ 898.115319] usb 2-8: new high-speed USB device number 7 using ehci-pci
I built everything myself and flashed both @ 2.1. It tries to mount but I get notices from my desktop os that it can't mount the device, one after another since it keeps on trying. I've also looked at dmesg and didn't see anything unusual. Will keep looking for hints. Didn't mount on OSX either.
One other thing, v2.0 doesn't support MTP (as stated on first post) but v2.1 does and I'm running 2.1. Still, I cannot mount internal storage on my Linux box, is there any way to fix that? Here's a part of logcat:
I/AutoMounter( 217): Changing mode from 'Enable-UMS' to 'Enable-MTP'
I/AutoMounter( 217): AutoMounter state changed from UMS_CONFIGURED to MTP_CONFIGURING
I/AutoMounter( 217): SetUsbFunction(mtp) sys.usb.config to 'mtp,adb'
I/AutoMounter( 217): UpdateState: ums:A1C1E0 mtp:A1C0E1 mode:3 usb:1 tryToShare:0 state:MTP_CONFIGURING
Hey KonstaT, when I'm on a call the other person hears an echo of his own voice, I flashed KK and the echo disapeared. Have any idea where that might come from? It was suggested to me on b2g forum that it might be a missing blob for echo cancelation or something...
After building B2G I have a lot of .img in /out/target/product/falcon/ (boot,cache,dt,persist,ramdisk,ramdisk-recovery,system,userdata,recovery), must I flash all those in fastboot? Your .zip archive has only the system folder and boot .img.
I've started building B2G but towards the end it stopped with:
make: *** No rule to make target `out/target/product/falcon/obj/SHARED_LIBRARIES/libbtnv_intermediates/export_includes', needed by `out/target/product/falcon/obj/SHARED_LIBRARIES/libbt-vendor_intermediates/import_includes'. Stop.