| 5ee5d389d6cb90b3cd2856730f8ff12211bc95d2 |
|
29-Sep-2012 |
Ken Sumrall <ksumrall@android.com> |
Update fastboot to wipe ext4 partitions before flashing
To prevent false error reports from e2fsck, update fastboot to erase
a partition identified as being ext4 partition before flashing an image
to it.
bug: 7259359
Change-Id: I85e9963aa8247b4b33fdd57f994cdb3ee72b670f
/system/core/fastboot/fastboot.h
|
| 9a70e5c33891632c89c9f3f03e30d7183227d661 |
|
18-Jul-2012 |
Colin Cross <ccross@android.com> |
resolved conflicts for merge of 4d72d881 to master
Change-Id: Ic092d27d3fc2bcc4db8a375bbcb5b86c111bf062
|
| f838788e6a4d57634a53eb597ee76a597feffcb5 |
|
25-May-2012 |
Colin Cross <ccross@android.com> |
fastboot: add support for auto-resparsing large files
Add support to fastboot for automatically using libsparse to break large
files, whether they are in sparse or normal format, into multiple sparse
files that can each fit into the target's memory. Allows flashing
images that are larger than the size of the available memory on the
target.
By default, any file over 512MB will be sparsed into 512MB chunks. The
limit can be modified with the -m argument, or sparsing can be forced
with -S or avoided with -N. If -m is not specified, the target can
override the default by implementing getvar:max-download-size
Change-Id: I6c59381c3d24475c4f2587ea877200b96971cbd7
/system/core/fastboot/fastboot.h
|
| 80f2d036a9dff894df27961c4aed300f1a5ebbc4 |
|
25-May-2012 |
Colin Cross <ccross@android.com> |
fastboot: add fb_getvar
Add an fb_getvar helper that can be used to get values from the
target.
Change-Id: I0da088fcbc8d40076c7bf5ef6e5bbd97fae61471
/system/core/fastboot/fastboot.h
|
| 3447b11d3e72bdc7409f63ec76ceba1babe06486 |
|
14-May-2012 |
JP Abgrall <jpa@google.com> |
am 177a74ac: am c1f88106: Merge "fastboot: Change -w to format after the erase of userdata & cache" into jb-dev
* commit '177a74aced971b89c319fb61ee12da0ca40f0c12':
fastboot: Change -w to format after the erase of userdata & cache
|
| 30ae5806e920cb824d019defd856068f09dd0db6 |
|
08-May-2012 |
JP Abgrall <jpa@google.com> |
fastboot: Change -w to format after the erase of userdata & cache
If the bootloader doesn't support formatting of those partitions
(either because it doesn't support the getvar commands needed or
the partition type is not supported), the errors are printed but
doesn't halt processing of subsequent commands.
Change-Id: I816ac2e5e7593846fcb4fd39c793a8dbdd996f6f
Signed-off-by: Mike J. Chen <mjchen@google.com>
/system/core/fastboot/fastboot.h
|
| a61bcad58ba1f7359183a333ee58303ed67e4a2f |
|
02-May-2012 |
Scott Anderson <saa@android.com> |
resolved conflicts for merge of 13081c69 to master
Change-Id: I631e466fc53e9b0f4a39f24f959b4ae9b626bdda
|
| 13081c6915220db03886b177f1a8e0b2c63467c9 |
|
06-Apr-2012 |
Scott Anderson <saa@android.com> |
fastboot: Add ability to specify device path
For manufacturing and testing, there is a need to talk to
whatever device is connected to a given port on the host. This
change modifies fastboot's "-s" option to take either a serial
number or a device path. The device paths of the connected
devices can be listed using "fastboot -l devices" whose output
will resemble:
016B75D60A00600D usb:2-5 fastboot
AD3C12020173 usb:1-4.3 fastboot
The second column lists the device paths. If the -l option is
not given, the output from "fastboot devices" will be the same as
it used to be (i.e. the paths will not be printed).
Finally, note that the format of the device paths are platform
dependent. The example above is from Linux. On OS-X, the paths
will be "usb:" followed by hex digits. For Windows, the device
paths will be printed as "????????????" and the -s option will
not be able to select a device until someone implements the
underlying functionality in usb_windows.c.
Change-Id: I1f01b8f47acd32edb0ac18db107316a2c923bbde
Signed-off-by: Scott Anderson <saa@android.com>
/system/core/fastboot/fastboot.h
|
| 5ae3f93f3bafbeb1fc9a3324475c58c725749c5e |
|
28-Feb-2012 |
Anatol Pomazau <anatol@google.com> |
Remove trailing whitespaces
Change-Id: I6f83333a6ee0fbc562a12bb9555c43a44c98768e
/system/core/fastboot/fastboot.h
|
| c8ba5366da7e23ebf1cd76bcf49449b878563102 |
|
16-Dec-2011 |
Anatol Pomazau <anatol@google.com> |
Implement 'fastboot format' command
Some filesystems (e.g. ext4) require flushing an initial
fs image, right after erasing it the partition is unusable.
Doing erase,flush emptyfs is a little bit scaring so we have a
separate command that performs it as atomic step:
- get size of partition
- create an empty filesystem image
- erase the partition
- flush empty fs to the partition
This command applicable only for ext4 filesystem and checks the
partition type before formatting it.
Change-Id: I8529bc3485739487f0d91312f7c0ab1a6e5d8b44
/system/core/fastboot/fastboot.h
|
| 714052ba4d86a2d411a3944f5034c5a5833ffbb6 |
|
05-Feb-2012 |
Mike J. Chen <mjchen@google.com> |
DO NOT MERGE
fastboot: Change -w to format after the erase of userdata & cache
If the bootloader doesn't support formatting of those partitions
(either because it doesn't support the getvar commands needed or
the partition type is not supported), the errors are printed but
doesn't halt processing of subsequent commands.
Change-Id: I816ac2e5e7593846fcb4fd39c793a8dbdd996f6f
Signed-off-by: Mike J. Chen <mjchen@google.com>
/system/core/fastboot/fastboot.h
|
| ca2074b78d44ce5fb60fae64da84e53c2b82cb8a |
|
13-Feb-2012 |
Mike Lockwood <lockwood@google.com> |
Revert "Implement 'fastboot format' command"
until Windows support is done
This reverts commit 452e11885afb53d59b2aa38b15e3be41c568d1e6.
/system/core/fastboot/fastboot.h
|
| 452e11885afb53d59b2aa38b15e3be41c568d1e6 |
|
16-Dec-2011 |
Anatol Pomazau <anatol@google.com> |
Implement 'fastboot format' command
Some filesystems (e.g. ext4) require flushing an initial
fs image, right after erasing it the partition is unusable.
Doing erase,flush emptyfs is a little bit scaring so we have a
separate command that performs it as atomic step:
- get size of partition
- create an empty filesystem image
- erase the partition
- flush empty fs to the partition
This command applicable only for ext4 filesystem and checks the
partition type before formatting it.
Change-Id: Ifa42deaa66c3cb96ff786a73c3fadad92658f395
/system/core/fastboot/fastboot.h
|
| 6f53225ef9f60a18a69b4ad3ba920ada168b719e |
|
04-Feb-2012 |
Anatol Pomazau <anatol@google.com> |
Revert "Implement 'fastboot format' command"
This reverts commit 230d160a718333651f7ca1557404f96682795b37
/system/core/fastboot/fastboot.h
|
| 230d160a718333651f7ca1557404f96682795b37 |
|
16-Dec-2011 |
Anatol Pomazau <anatol@google.com> |
Implement 'fastboot format' command
Some filesystems (e.g. ext4) require flushing an initial
fs image, right after erasing it the partition is unusable.
Doing erase,flush emptyfs is a little bit scaring so we have a
separate command that performs it as atomic step:
- get size of partition
- create an empty filesystem image
- erase the partition
- flush empty fs to the partition
This command applicable only for ext4 filesystem and checks the
partition type before formatting it.
Change-Id: I8529bc1dc64237f1f0d91312f7c0ab1a6e5d8b44
/system/core/fastboot/fastboot.h
|
| 21311f87c60bb75588e12227e7c0b9812e751b4a |
|
03-Feb-2012 |
Anatol Pomazau <anatol@google.com> |
Revert "Implement 'fastboot format' command"
This reverts commit 049dff53ef368bd84d0bddcb4c91f408774949c1
/system/core/fastboot/fastboot.h
|
| 65cf84f3ff959eec0c97229489d58279feaf3bcb |
|
16-Dec-2011 |
Anatol Pomazau <anatol@google.com> |
Implement 'fastboot format' command
Some filesystems (e.g. ext4) require flushing an initial
fs image, right after erasing it the partition is unusable.
Doing erase,flush emptyfs is a little bit scaring so we have a
separate command that performs it as atomic step:
- get size of partition
- create an empty filesystem image
- erase the partition
- flush empty fs to the partition
This command applicable only for ext4 filesystem and checks the
partition type before formatting it.
Change-Id: I8529bc1dc64698f1f0d91312f7c0ab1a6e5d8b44
/system/core/fastboot/fastboot.h
|
| 049dff53ef368bd84d0bddcb4c91f408774949c1 |
|
16-Dec-2011 |
Anatol Pomazau <anatol@google.com> |
Implement 'fastboot format' command
Some filesystems (e.g. ext4) require flushing an initial
fs image, right after erasing it the partition is unusable.
Doing erase,flush emptyfs is a little bit scaring so we have a
separate command that performs it as atomic step:
- get size of partition
- create an empty filesystem image
- erase the partition
- flush empty fs to the partition
This command applicable only for ext4 filesystem and checks the
partition type before formatting it.
Change-Id: I8529bc1dc64698f1f0d91312f7c0ab1a6e5d8b44
/system/core/fastboot/fastboot.h
|
| b98762f7824c291dc5d9a9b757af434ef31d8c81 |
|
05-Apr-2011 |
Wink Saville <wink@google.com> |
Teach fastboot to allow required variables per product.
This is needed for products like xoom-cdma and xoom-cdma-lte.
The xoom-cdma-lte product requires an lte baseband binary but
it's not needed for xoom-cdma.
This is implemented by allowing an optional product parameter
to "required" statements. The parameter is separated from
"required" by a colon so the version-baseband-2 requirment in
board-info.txt for stingray becomes:
require-for-product:xoom-cdma-lte version-baseband-2=ltedc_u_03.25.00|ltedc_u_03.19.00
In the above statement, only xoom-cdma-lte requires version-baseband-2
and the baseband can be lte_u_03.25.00 or lte_u_03.19.00. For other
products version-baseband-2 will be ignored.
Change-Id: I786bec5f5661c2243d87925b064fc6124d3cffa1
/system/core/fastboot/fastboot.h
|
| eb31c0bdc0eac0898f01cdc1737cea94269f8f27 |
|
23-Apr-2010 |
Brian Carlstrom <bdc@google.com> |
fastboot should return non-zero exit code on error
When using fastboot in scripts, it currently is necessary to parse the
output for FAILED messages and possible other indications of
error. This happens relatively often, for example when there are radio
update issues. Fortunately, fb_execute_queue already has a notion that
an error has occured which is used to abort the queue execution.
This change makes the status value be returned from fb_execute_queue
to main which can then return it as an exit status. usage cases were
also changed to return 1.
Note the code already returned 1 for error in one other case when
there was a problem with boot, so there is a precedent for return 1 on
error in this program.
Change-Id: Ib0463b08c8f2569495e248dd84e331f7e3691039
/system/core/fastboot/fastboot.h
|
| dd7bc3319deb2b77c5d07a51b7d6cd7e11b5beb0 |
|
04-Mar-2009 |
The Android Open Source Project <initial-contribution@android.com> |
auto import from //depot/cupcake/@135843
/system/core/fastboot/fastboot.h
|
| e54eebbf1a908d65ee8cf80bab62821c05666d70 |
|
04-Mar-2009 |
The Android Open Source Project <initial-contribution@android.com> |
auto import from //depot/cupcake/@135843
/system/core/fastboot/fastboot.h
|
| 4f6e8d7a00cbeda1e70cc15be9c4af1018bdad53 |
|
21-Oct-2008 |
The Android Open Source Project <initial-contribution@android.com> |
Initial Contribution
/system/core/fastboot/fastboot.h
|