[Flatfish] Make Vendor ID in Fastboot mode match Vendor ID in normal (adb) mode

VERIFIED FIXED

Status

VERIFIED FIXED
4 years ago
4 years ago

People

(Reporter: caspy77, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [TCP] [Flatfish] [flatfish-hardware])

(Reporter)

Description

4 years ago
Right now when the tablet reboots into fastboot mode the Vendor ID changes (from 18d1 to 0bb4).  This is problematic for a few reasons.
On Linux it means that users must create two udev rules. This is not standard procedure for people used to flashing Android or FxOS devices. Usually, at the very least, users can expect to run lsusb and simply use that one result - and not need to run it a second time while in fastboot mode.
Also 18d1 will already work for many as it is a standard Google ID.

The biggest issue this seems to be causing, is that, to my knowledge, we have not had one Mac user to successfully flash their device from the OS.  They are able to access it from ADB, but once booted into fastboot mode, the fastboot client is unable to see the device.  We have not yet found a fix for this.
(Reporter)

Comment 1

4 years ago
Joe, I don't want to be too presumptuous so would you please notify the proper vendor folk about this topic? Thanks!
Flags: needinfo?(jcheng)

Comment 2

4 years ago
Hi, Caspy, we didn't change these ID info when we were porting FxOS from the Android BSP. We will add this issue in our to-do list.

While there are already quite a lot people who are working on Flatfish, so far we'd suggest the contributors simply add the following two lines in /etc/udev/rules.d/51-android.rules (or some other file.)

SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0600", OWNER="username"
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0600", OWNER="username"
# Please rename "username" to the user's name.

Thanks.
(Reporter)

Comment 3

4 years ago
Yes, now that we know about both Vendor IDs that is what we are currently instructing our Linux users.
But we have no instructions for our Mac users.

Comment 4

4 years ago
I'd like to consult Joe for his opinions, cause' all of the developers in our side are using Linux.

Joe, Mozilla has much more developer who are using Mac. Could you help find out any possible solution?

Thanks.

Comment 5

4 years ago
I'd like to consult Joe for his opinions, cause' all of the developers in our side are using Linux.

Joe, Mozilla has much more developer who are using Mac. Could you help find out any possible solution?

Thanks.
Whiteboard: [TCP] [Flatfish] → [TCP] [Flatfish] [flatfish-hardware]
(In reply to William Liang from comment #5)
> Joe, Mozilla has much more developer who are using Mac. Could you help find
> out any possible solution?
> 
> Thanks.

Add vendor id to ~/.android/adb_usb.ini but still not working,
will try to figure out how to config this on mac.
After offline discussion with Evelyn, it would be better to have same vendor id for fastboot mode. And our partner will help on this issue and solve this one.
Hi William, we are not able to get things working on a Mac, so we will need your team's help on this. One option can be that your team may come to our office to work if this is fine with you. Thanks
Flags: needinfo?(jcheng)
(Reporter)

Comment 9

4 years ago
Just a quick note, if we could make the consistent Vendor ID 18d1. This should make everything "just work" for all current users.

Comment 10

4 years ago
The VID has been unified in the new version of the bare boot image, which is now available in https://www.dropbox.com/sh/b2py1btcwstqldl/AABblbq_csa1IHQwdvLdfptTa/. The file is located under the recovery-image-for-fastboot/ directory, namely sun6i_boot-fastboot_v2.0.img. 

Please check to see if it solve the issues. Thanks.
(Reporter)

Comment 11

4 years ago
I have good news and bad news.
I can verify that the Vendor ID is now the same in both normal (ADB) mode and fastboot mode.  Unfortunately this has not solved the problem with Macs being unable to access the device via fastboot.
So it looks like the Vendor ID was not at the root of that particular problem :-/

I have filed bug 1040236 for the Mac issue particularly.
Please CC yourself as appropriate.
See Also: → bug 1040236
(Reporter)

Comment 12

4 years ago
This bug is verified, so resolving as fixed.

Bug 1040236 covers the remaining Mac issue.
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Component: General → Gaia
Resolution: --- → FIXED
Per Comment 12,this bug is verified,so clear "verifyme" and switch status to "VERIFIED FIXED".
Status: RESOLVED → VERIFIED
Keywords: verifyme
You need to log in before you can comment on or make changes to this bug.