I am updating the Firmware for the Google Glasses Enterprise 2 as stated on google's documentation.
I am getting the error while I am running this command on terminal fastboot flash boot boot.img It returns with an error as stated above fastboot: error: cannot get boot partition size . Well i tried two different versions of the System images as mentioned on Google's website. I tried to change it to fastboot flash boot_a boot.img but the same error.
I saw someone was having the same issue as well there but no solution. Do someone have idea how can we install the system image on it. I have skipped it and run other commands all goes well but the boot is not working which is why the it only shows me now recovery mode/fastboot.
run fastboot --help and read somehow carefully
flash boot.img with fastboot flash:raw boot boot.img
This is problem with new Mac Mini. Because Apple is not using Intel CPU in new Mac mini M1. flash.android.com cannot update the firmware with browser on Apple M1.
I completed the task with windows pc and everything worked well. I believe this would help someone using M1 processors.
Related
I am using Android Studio version
Android Studio 3.4.1
Build #AI-183.6156.11.34.5522156, built on May 1, 2019
JRE: 1.8.0_152-release-1343-b01 x86_64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
macOS 10.14.5
with multiple Android devices including Pixel XL with Android Q (QPP4.190502.019)
All my test devices have started repeatedly displaying the
"Allow USB debugging?" PopUp
And losing ADB connectivity
What recent update has caused this behavior?
UPDATE
I reboot my laptop daily, as do my colleagues.
I and my colleagues have not updated USB drivers.
Ive tried multiple USB leads, as have my colleagues.
I've tried multiple Android devices and versions from 21 to Q
Devices include Pixel, Pixel 2, Pixel 3 & Pixel C, and Samsung S9, as have my colleagues.
I have revoked USB privileges and re granted on all devices, as have my colleagues.
The issue still persists
try to check the changelog for android studio update or have you try to enable the usb debugging in your device.
Haven't you installed/reinstalled Android USB drivers recently, if so try to reboot your system
It can also be caused by your broken USB cable, try to replace it with another one and check
I think you haven't checked never ask again option, that is why it's asking continuously.
So you can try to check that box if you haven't done that.
For others who might run into this problem, this started happening to me after I updated the OS version of my device. Restarting the device solved the issue.
I've just unpacked my new Pico Pro Maker Kit and started flashing procedure. After creating a product in AndroidThings platform and downloading the build I've started flashing procedure.
Command flash-all.sh failed on fastboot syntax, so I've build that manually and found that it was failing on part "set_active _a". I've skipped that and continued to flash device.
Now device is rebooted, I can see on the screen androidThings logo and version + info about network status ("not connected").
I'm unable to find this device in
fastboot devices
or
adb devices
so it looks like I have no way to connect into it.
Do you know a way of fixing that? Is there any way to force fastboot reboot on that device?
Thanks!
I had a related problem for IMX7 on initial install, I thought I'd pass along the Boundary feedback in case it helps. Tech support at Boundary devices recommended that I try the following:
Please try to add androidboot.dm_verity=disabled and
androidboot.selinux=disabled options to bootargs.
I presume these would be options you'd set at the boot prompt ==> (from the serial connection) but I haven't had a chance to test, which I may get to next week. Interested in your feedback if this has any impact to your situation in the meantime.
On a Macbook Pro with Yosemite -
After getting through the difficulties of getting Android SDK installed, I plug in the device, but it doesn't show. The command adb devices yields "List of devices attached" with nothing following. It's there on the USB, the About This Mac System Report shows it present on the USB.
This question looks similar to Issue setting up the development environment for ProjectTango developemnt Device but is not the same because I'm not using Eclipse.
Please ensure that USB debugging is enabled in order to enter ADB, go to Settings > About tablet > Build number and then press Build number seven times. Then press back and go to Developer options > USB debugging.
Make sure you're using the latest Google USB driver. I was having this problem (but on Win 8) and updating the driver fixed it, I'm now getting the device in adb devices and can push content to it.
I'm trying to sideload Lollipop onto my Nexus 5 from the OTA zip file.
At this point, the adb recognizes the device after I plug in the USB cable, and spits out the serial number.
As I understand the instructions for sideloading, once I get to this point, I just need to reboot into recovery mode, (which works as expected) and then bypass the red exclamation point icon using "volume up and power" simultaneously. That works too.
At the point where the screen on the Nexus 5 says, "Now send the package you want to apply to the device with 'adb sideload <filename>' I type "adb sideload + the OTA image file name", which I renamed for convenience". The file is in the platform-tools folder.
At which point the command window reports: error: device not found
So... the device is seen by the adb, but somehow is no longer found after the device reboots in recovery mode.
I've replaced all the usb drivers, enabled usb debugging and developer mode on the Nexus device. I've tried this in windows 7 and also in Linux (both from the android sdk tool kit and from an installation of Eclipse). I'm unable to get the adb to talk to the Nexus 5.
I read the android-windows usb inf file, and there is no section specifically for the Nexus 5, but I added a line under the "generic android" section with USB\VID_18D1&PID_D001 as has been suggested elsewhere for people who couldn't get the OS to see their nexus at all. My issue is not that the OS can't see it... and the adb sees it, too, until I try to sideload the OTA file in Recovery Mode.
Anyone else having this issue, or better yet... any ideas on how to solve it?
Thanks
It turns out that I had not enabled USB debugging before I tried to do this using Linux Ubuntu / Eclipse / Android SDK. So my problem was really a windows USB driver problem, I guess (though I can't be sure, since windows did see the device until I tried to transfer the file. Maybe that message was really conveying a permissions problem, too...)
I rebooted into Ubuntu and tried again and was able to transfer the update file. The only hitch I encountered at that point was to issue the sideload command as root. I didn't do that the first time I tried it, and got a message about lacking permissions.
I suspect the posted reply with a link to a universal USB inf file would have worked, but, though I'm grateful for the tip, I can't testify to that, since I managed to transfer the file without Windows.
Thanks to all who looked at this and especially to Alex P., for posting a possible solution. FW
IW, I'm glad to have finally been able to do this, but for anyone struggling to get Lollipop ahead of the OTA update... well, it's nice, but hardly worth a lot of effort.
I tried all the the different stuff. But its not working. Its something general to linux. I have tried it in Arch Linux and now I have installed Ubuntu 12.04 beta2 also its the same there. I am trying to connect my Samsung mobile phone to my ubuntu box for gprs, buts its not working. I have tried bluetooth and usb both. It pairs fine with bluetooth but on using DUN service or browsing file etc.. it just crashes ... like the phone is not responding to its requests. I have upgraded the kernel to 3.3 from ubuntu PPA. Thought that might solve the problem. But its the same. I have downloaded blueman from another PPA. Which also finds phones, gets paired but whenever I try to browse file, send file or use DUN it says my phone is not responding. I have tried mannual rfcomm bind 0... stuff it creates a /dev/rfcomm0 and when you cat > /dev/rfcomm0 it communitcates with phone and asks for pin code etc... but when i do pppd... chat dailing ... logs says the same no response from my phone. Please guide me ... what should I do. Just for the info. Phone works fine on windows. I am using it right now. Regards
You shall try this project: Android File Transfer For Linux