VAR-SOM-SD600 fastboot: Difference between revisions
From Variscite Wiki
No edit summary |
No edit summary |
||
| Line 16: | Line 16: | ||
== Installing binaries to eMMC storage == | == Installing binaries to eMMC storage == | ||
Execute the fastboot script | |||
<pre>$cd /path to prebuilt imagages folder | <pre>$cd /path to prebuilt imagages folder | ||
$sudo ./flashall | $sudo ./flashall | ||
</pre> | </pre> | ||
<br/>The following should be displayed on ubuntu host: | |||
The following should be displayed on ubuntu host: | |||
<pre>"waiting for device" | <pre>"waiting for device" | ||
</pre> | </pre> | ||
Connect device to PC: | Connect device to PC: | ||
* | * Press and hold the fastboot button | ||
* Power up the device, or press the reset button | |||
* Connect the OTG cable to PC | |||
The following should be displayed on the host Ubuntu: | |||
</pre> | |||
<br/>The following should be displayed on ubuntu host: | |||
<pre>"connected" | |||
</pre> | |||
Revision as of 14:22, 30 April 2014
General information
Qualcomm's propietary bootloaders (SBLs) can not be shared with customers Bad installation of either SBLs or LK bootloader (fastboot), will result in sending SOM back to Variscite for an RMA procedure.
Pre-built package
- boot.img: Linux Kernel + Ramdisk boot - cache.img: Android Cache partition - emmc_appsboot.mbn: Fastboot bootloader - flashall.sh: A script to flash images over fastboot - persist.img: Android persist partition - recovery.img: Recovery image - system.img: Android system partition - userdata.img: Android data partition
Installing binaries to eMMC storage
Execute the fastboot script
$cd /path to prebuilt imagages folder $sudo ./flashall
The following should be displayed on ubuntu host:
"waiting for device"
Connect device to PC:
- Press and hold the fastboot button
- Power up the device, or press the reset button
- Connect the OTG cable to PC
The following should be displayed on the host Ubuntu:
The following should be displayed on ubuntu host:
"connected"