fastboot | 易学教程

ADB stopping at <waiting for devices>

阅读更多关于 ADB stopping at

问题 I was trying to install some custom recovery and ROM on to my phone when I got to this situation. (I have my windows update turned off) ADB or fastboot shows <waiting for devices> I tried and saw few solutions. I'm writing a detailed solution to this. this was how I solved it. if you have more suggestions you can answer below. 回答1: the only reason for this is that your PC is not recognizing Phone.which is a driver problem. You have to understand a few things before starting with the solution.

adb devices command doesn't show my xperia z - got proper drivers and all [closed]

阅读更多关于 adb devices command doesn't show my xperia z - got proper drivers and all [closed]

问题 Closed. This question is off-topic. It is not currently accepting answers. Want to improve this question? Update the question so it's on-topic for Stack Overflow. Closed 3 years ago . I am trying to flash a custom rom and therefore I need to run certain adb commands. Now the thing is the when I'm booted in to fastboot everything is okay, the fastboot devices command recognizes my phone(C6603). Also the device is shown as an Android device - sony fastboot interface in the device manager. But

致在刷机路上走得坎坷的朋友——刷机失败的解决方案

阅读更多关于致在刷机路上走得坎坷的朋友——刷机失败的解决方案

【推荐】2019 Java 开发者跳槽指南.pdf(吐血整理) >>> 刷机有一定的风险，不当的刷机方法可能会带来很多不必要的麻烦，比如无法开机、开机死机、功能失效等后果。所以我们要慎重刷机，尽量避免不科学的操作。下来就让我们从线刷开始阐述由于线刷造成的刷机失败或是手机成砖的拯救方法。刷机险情一使用RSD工具线刷,刷机过程没问题，但最后RSD却显示please manually power up this phone。(请手动启动手机，刷机没有问题，不要紧张。) 刷机失败解决方法： 1.这是提示手动开机的意思,直接用手按开机键开机就OK了。 2.如果第一种方法不奏效，重刷到最后出现please manually powerup this phone后拿下电池。注意不要拔USB，不要关闭RSD，然后再装上电池，重新启动手机，然后就静静等待熟悉的开机画面吧。刷机险情二启动RSD，model项显示S Flash Neptune LTE2而不显示手机的型号。刷机失败解决方法： USB驱动没有装好，可换其他驱动试试，一般官方的手机驱动都可以在官网下载，或者安装豌豆荚和motoDriverTool。刷机险情三手动能进fastboot (DOS)，但是连电脑没反应，或者无法连接。刷机失败解决方法：打开RSD，拿下电池插上手机，按着返回键加开机键(根据自己的手机品牌

fastboot getvar from batch file

阅读更多关于 fastboot getvar from batch file

问题 I was trying to get certain fastboot variables from a batch file. I was using something like : for /f "tokens=2 delims=:" %%a in ('fastboot.exe getvar version-bootloader') do @echo version is %%a But I get the output on command line, not in the variable %%a. the command 'fastboot.exe getvar version-bootloader' works perfectly in command-line. I also tried doing: fastboot.exe getvar version-bootloader >> temp.txt but temp.txt is always empty and i receive the output on the command line,

Android Things - pico i.mx7 unable to connect

阅读更多关于 Android Things - pico i.mx7 unable to connect

问题 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

Compile FastBoot (used for android user space flashing) on Windows

阅读更多关于 Compile FastBoot (used for android user space flashing) on Windows

问题 I have compiled FastBoot on Linux platform. But I am stucked while compile it on windows.I am using WinDDK for compilation of FastBoot on windows.In WinDDK, It is giving errors like missing "unistd.h","sys/time.h","zipfile/zipfile.h". Are there any replacement files for above said in windows?.Please suggest if any suitable method to port the code from linux to Windows environment. 回答1: Header file unistd.h is available only on POSIX systems. Fastboot on Windows can be compiled using Cygwin.

Android fastboot waiting for devices

阅读更多关于 Android fastboot waiting for devices

问题 I am trying to load a customized kernel on my NVIDIA test git. I typed fastboot boot myImage after which which I get: <Waiting for device> I think this is a problem with a driver on fastboot mode on my device. But I don't know how to install the driver on linux. Do you guys know how to install the driver? 回答1: The short version of the page linked by D Shu (and without the horrible popover ads) is that this "waiting for device" problem happens when the USB device node is not accessible to your

Google GSI 刷写教程

阅读更多关于 Google GSI 刷写教程

GSI烧写的意义体验Android 最新版本的功能，GSM 认证中的VTS测试必须要使用谷歌的GSI包 GSI烧写流程一、前期准备工作 GSI包下载地址：https://ci.android.com/builds/branches/aosp-pie-gsi/grid?(包括GSI包和fastboot工具,保持版本一致) 如果谷歌开发者合作伙伴账户，可以在里面下载，里面的资源比较全。 1、确定设备起始版本，确定是否是p版以前的旧版本(28 为 pie 最新) adb shell getprop ro.product.first_api_level 2、版本补丁日期查看，要与下载的GSI补丁日期要一致 adb shell getprop ro.build.version.security_patch 3、查看是否支持刷GSI通用版本，通过运行以下命令检查是否具有 Treble 支持： adb shell getprop ro.treble.enabled 4、通过运行以下命令检查是否具有跨版本支持： adb shell cat /system/etc/ld.config.version_identifier.txt | grep -A 20 "\[vendor\]" 5、GSI CPU 架构类型必须与设备的 CPU 架构保持一致。要为 GSI 映像查找合适的 CPU 架构

fastboot烧录镜像--VTS&GSI镜像替换

阅读更多关于 fastboot烧录镜像--VTS&GSI镜像替换

Android提供的原生工具，主要用于替换镜像。源码在SDK工程中，/system/core/fastboot目录下见链接 boot：boot 分区包含通过 mkbootimg 组合在一起的内核映像和 RAM 磁盘。为了直接刷写内核而不刷写新的 boot 分区，可以使用虚拟分区： kernel：kernel 虚拟分区仅覆盖内核（zImage、zImage-dtb、Image.gz-dtb），方法是写入新的映像来覆盖旧的映像。为此，它会确定 eMMC 中现有内核映像的起始位置并将新内核映像复制到该位置。请记住，新内核映像可能会大于现有内核映像。引导加载程序可以通过移动其后的任何数据来腾出空间或放弃出错的操作。如果提供的开发内核不兼容，则可能需要使用相关的内核模块更新 dtb 分区（如果存在）、vendor 分区或 system 分区。 ramdisk：ramdisk 虚拟分区通过将新映像写入旧磁盘来仅覆盖 RAM 磁盘。为此，它会确定 eMMC 中现有 ramdisk.img 的起始位置并将新 RAM 磁盘映像复制到该位置。请记住，新 RAM 磁盘映像可能会大于现有 RAM 磁盘映像。引导加载程序可以通过移动其后的任何数据来腾出空间或放弃出错的操作。 system：system 分区主要包含 Android 框架。 recovery：recovery 分区用于存储在 OTA

Android fastboot waiting for devices

阅读更多关于 Android fastboot waiting for devices

I am trying to load a customized kernel on my NVIDIA test git. I typed fastboot boot myImage after which which I get: <Waiting for device> I think this is a problem with a driver on fastboot mode on my device. But I don't know how to install the driver on linux. Do you guys know how to install the driver? The short version of the page linked by D Shu (and without the horrible popover ads) is that this "waiting for device" problem happens when the USB device node is not accessible to your current user. The USB id is different in fastboot mode, so you can easily have permission to it in adb but

订阅 fastboot