MX8MM won't enter fastboot mode

cancel
Showing results for 
Search instead for 
Did you mean: 

MX8MM won't enter fastboot mode

Jump to solution
4,651 Views
mikemalgin
Contributor II

Hello, I'm using MX8M Mini EVK with Android 9, under Windows 10. *ADB works* fine but I have a real trouble getting into fastboot mode.  I researched hard in all NXP documents - "Android_User's_Guide.pdf", "Android_Quick_Start_Guide.pdf" and even followed iMX6 instructions on how to config fastboot. Nothing works though. 

1. Obviously, both "developer mode" as well as "OEM unlocked" option are enabled.

2. When I run "adb shell reboot bootloader" the board is being rebooted but all I see is a blanked screen and both "fastboot oem unlocked" nor "fastboot usb" command ever returns.

3. I have the latest Google USB driver installed (tried to add vendor ID from iMX6 documentations, didn't really work either)

4. It should be noted that I was able to flush the images through UUU (with a new NXP build android_p9.0.0_2.0.0-ga_image_8mmevk.tar.gz)  but even with this new build the board won't enter fastboot mode.

Is there any change that needs to take place in the "android_winusb.inf" or "adb_usb.ini" ?

One last note, once the EVK board is booted in attempt to get into fastboot, instead of seeing "EVK_8MM" the device is changed to "USB download gadget", no idea if that's normal?

I will appreciate any help!

Thanks, Mike

1 Solution
2,063 Views
nxf46838
NXP TechSupport
NXP TechSupport

Hello,

 

This may be due to the host PC selects an incorrect driver model of the USB devices, leading to the PC inability to find fastboot device.

 

After accessing fastboot, run "reboot bootloader" in console after boot, in host side open "Computer Management->Device Manager", you'll note that the USB appears as:

 

Universal Serial Bus devices -> USB download gadget,

 

pastedImage_1.png

 

Right click it, and choose “Updated Driver -> browse my computer for driver software ->

let me pick from a list of available drivers on my computer”, clear “Show compatible hardware” item, then choose “ADB devices”,

 pastedImage_2.png

 

Select yes to the pop-up window, this will select the USB as an ADB device,

 

pastedImage_4.png

 

This should fix the issue, and the fastboot device should be listed.

 

Hope this helps,

Best regards,
Aldo.

-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!

- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------

View solution in original post

6 Replies
1,610 Views
savedstesen
Contributor I

Hi 

I have this problem too on Windows 10 and I followed the guide to solve the problem. However the device manager keeps showing "USB download gadget" after installing the Google Driver from https://dl.google.com/android/repository/usb_driver_r13-windows.zip

I would expect something else? 

 

savedstesen_0-1604330397721.png

savedstesen_1-1604330582527.png

 

I did try on a MAC with newly Android Studio installed and here fastboot gets instant contact to the device. 

Ideas to overcome this? 

Best regards 

Svend 

0 Kudos
2,063 Views
taesub_youn
Contributor III

Hi Shivani,

Your solution is working only on connected device. If new device is connected and switched to fastboot mode. device couldn't be found. Then we have to select adb device manually again. This works for one device. But this has big productivity issue in factory. Can you help to solve this?

0 Kudos
2,063 Views
shivanipatel
Senior Contributor II

Hi, taesub_youn@whirlpool.com

Please update the USB Driver from this link to resolve this issue.

Regards,

Shivani

0 Kudos
2,063 Views
shivanipatel
Senior Contributor II

Hi, mike malgin

Please use the latest fastboot binaries from this link (for windows and linux) and follow the steps mentioned by Aldo Gutierrez to select the proper driver, you will be able to find the device in fastboot mode.

Let us know if you are still facing the issue.

Regards,

Shivani

0 Kudos
2,064 Views
nxf46838
NXP TechSupport
NXP TechSupport

Hello,

 

This may be due to the host PC selects an incorrect driver model of the USB devices, leading to the PC inability to find fastboot device.

 

After accessing fastboot, run "reboot bootloader" in console after boot, in host side open "Computer Management->Device Manager", you'll note that the USB appears as:

 

Universal Serial Bus devices -> USB download gadget,

 

pastedImage_1.png

 

Right click it, and choose “Updated Driver -> browse my computer for driver software ->

let me pick from a list of available drivers on my computer”, clear “Show compatible hardware” item, then choose “ADB devices”,

 pastedImage_2.png

 

Select yes to the pop-up window, this will select the USB as an ADB device,

 

pastedImage_4.png

 

This should fix the issue, and the fastboot device should be listed.

 

Hope this helps,

Best regards,
Aldo.

-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!

- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------

View solution in original post

2,063 Views
pad_c_jakkahall
Contributor II

Hello Aldo,

We noticed that USB ID getting changed on every build (EVT, DVT, etc). This is causing us to reconfigure windows machines at every build, impacting productivity. What is the reason behind the change?  So far we have seen following IDs.

ID 18d1:4ee7 Google Inc.
ID 0525:a4a5 Netchip Technology, Inc. Pocketbook Pro 903
ID 03f0:0667 HP, Inc

-Pad