diff options
| author | codeworkx <daniel.hillenbrand@codeworkx.de> | 2011-04-25 11:16:41 -0700 |
|---|---|---|
| committer | codeworkx <daniel.hillenbrand@codeworkx.de> | 2011-04-25 11:16:41 -0700 |
| commit | 9c4c8e2c6675861e9983a1e40adb7f082de691fb (patch) | |
| tree | 343073f2cfa6c5e85409fefb333a8bbbd78e14b4 /flashutils | |
| parent | 6a9739657298c49f28ca881d733d1a4870e20540 (diff) | |
| download | bootable_recovery-9c4c8e2c6675861e9983a1e40adb7f082de691fb.zip bootable_recovery-9c4c8e2c6675861e9983a1e40adb7f082de691fb.tar.gz bootable_recovery-9c4c8e2c6675861e9983a1e40adb7f082de691fb.tar.bz2 | |
bml_over_mtd: Take care of bad blocks on "boot" partition for Samsung Galaxy S Phones.
The Samsung Galaxy S bootloader apparently expects the kernel to be flashed to BML-managed flash - bad erase blocks will be mapped from a reservoir area.
CWM however just skips bad blocks, the usual procedure for mtd-accessed flash.
Consequently, the bootloader sees a corrupt zImage, and will usually crash when the kernel initializes.
This of course will only happen when the "boot" partition has bad blocks.
This patch was written by "eifert" and adds a tool called "bml_over_mtd" for flashing boot images which takes care of bad blocks and maps them to a reservoir area, like BML does.
Change-Id: If570717a19b879d47d70d937a0751cd85853eacd
Diffstat (limited to 'flashutils')
| -rw-r--r-- | flashutils/Android.mk | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/flashutils/Android.mk b/flashutils/Android.mk index 324480a..d503ce7 100644 --- a/flashutils/Android.mk +++ b/flashutils/Android.mk @@ -57,7 +57,6 @@ LOCAL_MODULE_TAGS := eng LOCAL_CFLAGS += -Dmain=erase_image_main include $(BUILD_STATIC_LIBRARY) - include $(CLEAR_VARS) LOCAL_SRC_FILES := dump_image.c LOCAL_MODULE := utility_dump_image |