Android product out not set

At the moment I would like to reinstall Android on my device(custom hardware device). I got the image files after building. But when I enter fastboot devices nothing returns.

adb devices is working. It return my device. fastboot flashall -w is also not working. I returns and stays like that until I exit.

So the 70-android.rules.d file is right. I have also set ANDROID_PRODUCT_OUT. But someone knows why fastboot does not see my device, but adb does?

Restarting udev or adb does not work. Some people recommend that on the internet.

6 Answers 6

Are you rebooting the device into the bootloader and entering fastboot USB on the bootloader menu?

then look for on screen instructions to enter fastboot mode.

For Windows:

  • Open device manager
  • Find Unknown "Android" device (likely listed under Other devices with an exclamation mark)
  • Update driver
  • Browse my computer for driver software
  • Let me pick from a list of devices, select List All Devices
  • Under "Android device" or "Google Inc", you will find "Android Bootloader Interface"
  • Choose "Android Bootloader Interface"
  • Click "yes" when it says that driver might not be compatible

I had the same issue, but I was running Ubuntu 12.04 through a VM. I am using a Nexus 10. I had added the usb device as a filter for the VM (using virtual box in the virtual machine’s settings).

The device I had added was "samsung Nexus 10".

The problem is that once the device is in fastboot mode, it shows up as a different device: "Google, Inc Android 1.0." So doing "lsusb" in the VM showed no device connected, and obviously "fastboot devices" returned nothing until I added the "second" device as a filter for the VM as well.

Hope this helps someone.

You must run fastboot as root. Try sudo fastboot

TLDR — In addition to the previous responses. There might be a problem with the version of the fastboot command. Try to download the newest one via Android SDK Manager instead of default one available in the OS repository.

There is one more thing you can do to fix this issue. I had the similar problem when trying to flash Nexus Player. All the adb commands we working fine while in normal boot mode. However, after switching to fastboot mode I wasn’t able to execute fastboot commands. My device was not visible in the output of the fastboot devices command. I’ve set the right rules in /etc/udev/rules.d/11-android.rules file. The lsusb command showed that the device has been pluged in.

The soultion was quite simple. I’ve downloaded the the fastboot via Android Studio’s SDK Manager instead of using the default one available in Ubuntu packages.

All you need is sdkmanager. Download the Android SDK Platform Tools and replace the default /usr/bin/fastboot with the new one.

Если вы пытаетесь установить прошивку на ваш Andro >

Данный материал, подразумевает, что вы уже знаете, что такое Fastboot и как им пользоваться. Статья в большем случае рассчитана для устройств Nexus, но возможно подойдет и другим устройствам которые имеют поддержку Fastboot.

Ошибки при прошивки в Fastboot

Проблема может возникнуть из-за отсутствия драйверов, а также с какими либо проблемами с USB кабелями и портами, подробней читайте в статье waiting for devices.

Проблема связана с поврежденным или дешевым USB кабелем, либо же подключение выполнено через ХАБ.

Прошить каждую часть прошивки по отдельности, а не за один раз c помощью архива.

Прошить каждую часть прошивки по отдельности, а не за один раз c помощью архива.

Не обращать свое внимание, так как это не является ошибкой.

Вначале удалить, перезагрузить компьютер и переустановить драйвера Nexus.

Для того чтобы устранить данную ошибку необходимо установить кастомное Recovery, после чего перейти в него и выполнить команду:

После чего перевести Android в режим Bootloader/Fastboot и прошить образ cache:

Вот и все! Оставайтесь с сайтом Android +1! Дальше будет интересней!

Please forgive the fact that this is about restoring to stock as I’ve tried
for a few days to get an answers elsewhere and have gotten nowhere.

I’m trying to update my GNex. The OTA has failed because somehow busybox
replaced my gzip with a symlink. Whatever, I backed the whole device up and
downloaded the factory image. Thus far, none of the official factory images
match my device info. It’s the GNex from the Google Play Store and came
with Google Wallet.
__________________________________

INFO PULLED FROM BOOTLOADER

Product Name — Tuna
Variant — Maguro 16gb
HW Version — 9
Bootloader Version — PRIMELC03
Baseband Version — I9250XXLH1
Carrier Info — None
SN — listed (sorry, not sharing that here lol)
Signing — Production

When I’ve looked at the extracted tar balls and in the .zip files, thus far
the takju and yakju builds under the android-info.txt match all info except
the Baseband version. Thoughts?

fastboot -w flashall

returns the error

error: neither -p product specified nor ANDROID_PRODUCT_OUT set

I then tried
fastboot -w flashall -p maguro

fastboot -w flashall -p tuna

fastboot -w flashall -p takju

error: could not load android-info.txt: No such file or directory

I checked, that file is definitely there.

I also tried this with an edited version of that text file to change the
baseband to match mine and got the same error.

Files were downloaded directly from Google’s factory image site and I
verified md5sum and sha1sum on them before trying.

So anyhow, I’m completely stumped.

Search Discussions

  • 5 responses
  • Oldest
  • Nested
Jean-Baptiste Queru at Feb 19, 2013 at 4:31 pm

There’s a ./flash-all.sh script that will take care of updating the
bootloader and baseband firmware before updating the software itself,
all in a single pass.

On Mon, Feb 18, 2013 at 5:58 PM, Jonathan Hutson wrote:
Please forgive the fact that this is about restoring to stock as I’ve tried
for a few days to get an answers elsewhere and have gotten nowhere.

I’m trying to update my GNex. The OTA has failed because somehow busybox
replaced my gzip with a symlink. Whatever, I backed the whole device up and
downloaded the factory image. Thus far, none of the official factory images
match my device info. It’s the GNex from the Google Play Store and came with
Google Wallet.
__________________________________

INFO PULLED FROM BOOTLOADER

Product Name — Tuna
Variant — Maguro 16gb
HW Version — 9
Bootloader Version — PRIMELC03
Baseband Version — I9250XXLH1
Carrier Info — None
SN — listed (sorry, not sharing that here lol)
Signing — Production

When I’ve looked at the extracted tar balls and in the .zip files, thus far
the takju and yakju builds under the android-info.txt match all info except
the Baseband version. Thoughts?

fastboot -w flashall

returns the error

error: neither -p product specified nor ANDROID_PRODUCT_OUT set

I then tried
fastboot -w flashall -p maguro

fastboot -w flashall -p tuna

fastboot -w flashall -p takju

error: could not load android-info.txt: No such file or directory

I checked, that file is definitely there.

I also tried this with an edited version of that text file to change the
baseband to match mine and got the same error.

Files were downloaded directly from Google’s factory image site and I
verified md5sum and sha1sum on them before trying.

So anyhow, I’m completely stumped.


Jean-Baptiste M. "JBQ" Queru
Technical Lead, Android Open Source Project, Google.

Questions sent directly to me that have no reason for being private
will likely get ignored or forwarded to a public forum with no further
warning.

Kevin Kim at Feb 19, 2013 at 4:41 pm

On Feb 19, 2013 11:31 AM, "Jean-Baptiste Queru" wrote:

There’s a ./flash-all.sh script that will take care of updating the
bootloader and baseband firmware before updating the software itself,
all in a single pass.

On Mon, Feb 18, 2013 at 5:58 PM, Jonathan Hutson wrote:
Please forgive the fact that this is about restoring to stock as I’ve tried
for a few days to get an answers elsewhere and have gotten nowhere.

I’m trying to update my GNex. The OTA has failed because somehow busybox
replaced my gzip with a symlink. Whatever, I backed the whole device up and
downloaded the factory image. Thus far, none of the official factory images
match my device info. It’s the GNex from the Google Play Store and came with
Google Wallet.
__________________________________

INFO PULLED FROM BOOTLOADER

Product Name — Tuna
Variant — Maguro 16gb
HW Version — 9
Bootloader Version — PRIMELC03
Baseband Version — I9250XXLH1
Carrier Info — None
SN — listed (sorry, not sharing that here lol)
Signing — Production

When I’ve looked at the extracted tar balls and in the .zip files, thus far
the takju and yakju builds under the android-info.txt match all info except
the Baseband version. Thoughts?

fastboot -w flashall

returns the error

error: neither -p product specified nor ANDROID_PRODUCT_OUT set

I then tried
fastboot -w flashall -p maguro

fastboot -w flashall -p tuna

fastboot -w flashall -p takju

error: could not load android-info.txt: No such file or directory

I checked, that file is definitely there.

I also tried this with an edited version of that text file to change the
baseband to match mine and got the same error.

Files were downloaded directly from Google’s factory image site and I
verified md5sum and sha1sum on them before trying.

So anyhow, I’m completely stumped.


Jean-Baptiste M. "JBQ" Queru
Technical Lead, Android Open Source Project, Google.

Questions sent directly to me that have no reason for being private
will likely get ignored or forwarded to a public forum with no further
warning.

Antonio Marin Cerezuela at Feb 19, 2013 at 5:02 pm

El 19/02/13 02:58, Jonathan Hutson escribió:
Please forgive the fact that this is about restoring to stock as I’ve
tried for a few days to get an answers elsewhere and have gotten nowhere.

I’m trying to update my GNex. The OTA has failed because somehow
busybox replaced my gzip with a symlink. Whatever, I backed the whole
device up and downloaded the factory image. Thus far, none of the
official factory images match my device info. It’s the GNex from the
Google Play Store and came with Google Wallet.
__________________________________

INFO PULLED FROM BOOTLOADER

Product Name — Tuna
Variant — Maguro 16gb
HW Version — 9
Bootloader Version — PRIMELC03
Baseband Version — I9250XXLH1
Carrier Info — None
SN — listed (sorry, not sharing that here lol)
Signing — Production

When I’ve looked at the extracted tar balls and in the .zip files,
thus far the takju and yakju builds under the android-info.txt match
all info except the Baseband version. Thoughts?

fastboot -w flashall

returns the error

error: neither -p product specified nor ANDROID_PRODUCT_OUT set

Define ANDROID_PRODUCT_OUT to point where you extracted the factory
image (i.e. where the android-info.txt file is)

$ export ANDRO >
and retry fastboot -w flashall

I then tried
fastboot -w flashall -p maguro

fastboot -w flashall -p tuna

fastboot -w flashall -p takju

error: could not load android-info.txt: No such file or directory

I checked, that file is definitely there.

I also tried this with an edited version of that text file to change
the baseband to match mine and got the same error.

Files were downloaded directly from Google’s factory image site and I
verified md5sum and sha1sum on them before trying.

Research Dept
Swiss Mobility Solutions
Av. Jaime I El Conquistador 1, Local 2
03560 El Campello
Spain

Este mensaje contiene informacion reservada y confidencial destinada exclusivamente al destinatario. Si usted no es el destinatario no esta autorizado a copiar, reproducir o distribuir este mensaje ni su contenido. Si ha recibido este mensaje por error, le rogamos que nos lo notifique inmediatamente.

The information in this e-mail is confidential and may be legally privileged. It is intended solely for the addressee(s). It may contain privileged and confidential information. If you are not the intended recipient, please destroy this message and notify us immediately. Any disclosure, copying or distribution of this message is prohibited and may be unlawful.

Jean-Baptiste Queru at Feb 19, 2013 at 4:56 pm

FWIW, fastboot flashall is used to flash from a locally built system.
If you want to use fastboot directly when working with a zipped image,
you actually want fastboot update.

On Tue, Feb 19, 2013 at 8:53 AM, Antonio Marin Cerezuela
wrote:

El 19/02/13 02:58, Jonathan Hutson escribió:

Please forgive the fact that this is about restoring to stock as I’ve tried
for a few days to get an answers elsewhere and have gotten nowhere.

I’m trying to update my GNex. The OTA has failed because somehow busybox
replaced my gzip with a symlink. Whatever, I backed the whole device up and
downloaded the factory image. Thus far, none of the official factory images
match my device info. It’s the GNex from the Google Play Store and came with
Google Wallet.
__________________________________

INFO PULLED FROM BOOTLOADER

Product Name — Tuna
Variant — Maguro 16gb
HW Version — 9
Bootloader Version — PRIMELC03
Baseband Version — I9250XXLH1
Carrier Info — None
SN — listed (sorry, not sharing that here lol)
Signing — Production

When I’ve looked at the extracted tar balls and in the .zip files, thus far
the takju and yakju builds under the android-info.txt match all info except
the Baseband version. Thoughts?

fastboot -w flashall

returns the error

error: neither -p product specified nor ANDROID_PRODUCT_OUT set

Define ANDROID_PRODUCT_OUT to point where you extracted the factory image
(i.e. where the android-info.txt file is)

$ export ANDRO >
and retry fastboot -w flashall

I then tried
fastboot -w flashall -p maguro

fastboot -w flashall -p tuna

fastboot -w flashall -p takju

error: could not load android-info.txt: No such file or directory

I checked, that file is definitely there.

I also tried this with an edited version of that text file to change the
baseband to match mine and got the same error.

Files were downloaded directly from Google’s factory image site and I
verified md5sum and sha1sum on them before trying.

Research Dept
Swiss Mobility Solutions
Av. Jaime I El Conquistador 1, Local 2
03560 El Campello
Spain

Este mensaje contiene informacion reservada y confidencial destinada
exclusivamente al destinatario. Si usted no es el destinatario no esta
autorizado a copiar, reproducir o distribuir este mensaje ni su contenido.
Si ha recibido este mensaje por error, le rogamos que nos lo notifique
inmediatamente.

The information in this e-mail is confidential and may be legally
privileged. It is intended solely for the addressee(s). It may contain
privileged and confidential information. If you are not the intended
recipient, please destroy this message and notify us immediately. Any
disclosure, copying or distribution of this message is prohibited and may be
unlawful.


Jean-Baptiste M. "JBQ" Queru
Technical Lead, Android Open Source Project, Google.

Questions sent directly to me that have no reason for being private
will likely get ignored or forwarded to a public forum with no further
warning.

Jonathan Hutson at Feb 20, 2013 at 4:05 pm

Follow this guide with an unlocked bootloader:

fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-maguro-primelc03.img
fastboot reboot-bootloader
fastboot flash radio radio-maguro-i9250xxlj1.img
fastboot reboot-bootloader
fastboot -w update image-takju-jdq39.zip

i tried the ./flash-all.sh script and I’d just get "waiting for device"

basically I just needed to manually do what the various automatic methods
do, and flashing the radio solved the baseband mis-match.


[an error occurred while processing the directive]
Карта сайта