anonymous/android_bootable_recovery - Team Win Recovery Project (TWRP)

	Commit message (Collapse)	Author	Age	Files	Lines
*	block is bad if ioctl() returns nonzero	Doug Zongker	2010-09-10	1	-2/+5
\| \| \| \|	Change-Id: I6fc4ce796bc663d05035927c0af0ce7ab6d07218
*	make offsets in firmware update header not point to bad blocks	Doug Zongker	2010-01-13	1	-4/+42
\| \| \| \| \| \| \| \| \| \| \| \| \|	hboot will apparently fail to install if the first block of the image (the one pointed to by the offset in the block 0 header) is a bad block. (Hopefully it handles subsequent bad blocks.) This change makes the MTD write code keep track of the bad blocks it has skipped over, so that the offset in the header can be adjusted to be the address of the first successfully written block. Change-Id: I45d58e32a36d0c1dbc0a7f871bd5985b6c8ff524 http://b/2358012 - passion: failure to flash hboot (bad blocks?)
*	use MEMGETBADBLOCK to look for bad blocks when reading MTD partitions	Doug Zongker	2009-12-15	1	-5/+12
\|
*	skip over all-zero blocks when reading MTD partition	Doug Zongker	2009-07-01	1	-1/+12
\| \| \| \| \| \| \| \| \| \| \|	We fail to detect certain bad blocks (marked in the factory as bad, I think?) when reading mtd partitions. These come back as a block of all zeros. Since it's fairly unlikely a legitimate boot or recovery block will contain 128k of zeros, change mtdutils to skip over such blocks. Arve says https://review.source.android.com/10535 may be a long-term fix for this, but he isn't yet sure.
*	auto import from //depot/cupcake/@135843	The Android Open Source Project	2009-03-04	1	-0/+510
\|
*	auto import from //depot/cupcake/@135843	The Android Open Source Project	2009-03-04	1	-510/+0
\|
*	Initial Contribution	The Android Open Source Project	2008-10-21	1	-0/+510