summaryrefslogtreecommitdiffstats
path: root/mtdutils (unfollow)
Commit message (Collapse)AuthorFilesLines
2014-09-03Build block TWRP with RECOVERY_VARIANTMatt Mower1-2/+2
Enable TWRP to reside alongside other recoveries with the naming convention: bootable/recovery(-flag). If TWRP resides at bootable/recovery and a device does not specify RECOVERY_VARIANT, then it will build like normal. If TWRP resides at bootable/recovery-twrp, then its makefiles will only be parsed if a device specifies 'RECOVERY_VARIANT := twrp'. This prevents TWRP specific makefile warnings/errors (notably, missing DEVICE_RESOLUTION) when another recovery is being built. Change-Id: I8f02fffcd79c309c7123b9428eedc69af02e126e
2014-07-05mtdutils: fix rk3xhack filterHumberto Borba1-2/+2
Just fix filter for correct platform Signed-off-by: Humberto Borba <humberos@gmail.com> Change-Id: I1f0978a6b215a1967dad4a2c495777d917865b88
2014-06-30Changes in rk30hackKra1o55-20/+20
This works on rk3188 based devices too so rename it to rk3xhack. Change-Id: Ia3d9d52d99205057f8bece735a938986491b7522
2014-04-15Enable rk30xx hackJ. Carlos Romero1-0/+2
Fix problem with erase/restore mtd partitions on Rockchip SoC Change-Id: I3320f711446441cf79e38e9ffb5dfdb6b1717a55
2013-07-09recovery: move log output to stdoutDoug Zongker1-13/+13
Recovery currently has a random mix of messages printed to stdout and messages printed to stderr, which can make logs hard to read. Move everything to stdout. Change-Id: Ie33bd4a9e1272e731302569cdec918e0534c48a6
2013-04-10Add liblogYing Wang1-1/+1
Bug: 8580410 Change-Id: Ie60dade81c06589cb0daee431611ded34adef8e6
2013-04-04Move all AOSP code out of recovery binaryDees_Troy1-0/+15
Improves license compatibility between GPL and Apache Change-Id: I2b165aa575bb6213af6b07936f99610c113443f0
2013-02-22mtdutils: add bml_over_mtd target for aries/p1 buildsjt11341-0/+23
Change-Id: Ie4bf51e09e632403c1bc87be64a0f9dd66b83f31
2013-01-05Work around MEMERASE ioctl for rk3066 compatibilitySergey 'Jin' Bostandzhyan5-0/+136
Due to a kernel bug and no available sources we have to work around the MEMERASE ioctl - if used, it hangs and never returns. I straced the original recovery executable and could see that it is simply calling write() with a bunch of zeroes instead of using MEMERASE. Added a hack that does the same and now the resulting TWRP recovery image works. Change-Id: I1b1c1c9e870e350776346bdca5d442c7ef565aa0
2012-11-21Fix compiling for x86 targetsHiemanshu Sharma1-2/+0
2012-09-05TWRP-ify AOSP codeDees_Troy5-36/+1024
Pull in most TWRP sources Stub out partition management code Make it compile -- probably will not boot Kind of a mess but have to start somewhere
2012-08-21Fixed warnings in libmtdutilsEdwin Vane1-4/+4
A few signed/unsigned comparison warnings were all that stood in the way of a clean clang build. Change-Id: Id8c47fcfa500a6ac164bddb855831cdc17d99847 Author: Edwin Vane <edwin.vane@intel.com> Reviewed-by: Tareq A Siraj <tareq.a.siraj@intel.com>
2012-01-08Rename (IF_)LOGE(_IF) to (IF_)ALOGE(_IF) DO NOT MERGESteve Block1-1/+1
See https://android-git.corp.google.com/g/#/c/157220 Bug: 5449033 Change-Id: I9ef9f808a852c36903c8afc40136c89c9ec07630
2012-01-06Rename (IF_)LOGW(_IF) to (IF_)ALOGW(_IF) DO NOT MERGESteve Block1-2/+2
See https://android-git.corp.google.com/g/157065 Bug: 5449033 Change-Id: If6c6ea354caf02fb3bf155931b23e4a6d2f751e9
2012-01-04Rename (IF_)LOGI(_IF) to (IF_)ALOGI(_IF) DO NOT MERGESteve Block1-2/+2
See https://android-git.corp.google.com/g/156801 Bug: 5449033 Change-Id: I3b4ea2184555bc0b570ec858601d4c43ecffb6f8
2011-10-31turn recovery into a C++ binaryDoug Zongker2-0/+16
Change-Id: I423a23581048d451d53eef46e5f5eac485b77555
2011-10-28turn recovery into a C++ binaryDoug Zongker2-0/+16
Change-Id: I68a67a4c8edec9a74463b3d4766005ce27b51316
2011-07-12Remove the simulator target from all makefiles.Jeff Brown1-4/+0
Bug: 5010576 Change-Id: Ib465fdb42c8621899bea15c04a427d7ab1641a8c
2011-02-09Fix x86 build.Ying Wang1-2/+0
Change-Id: Iada6268b0a72ee832113ea397334cc7950a37051
2011-01-19Free allocated struct after freeing fieldChristian Lindeberg1-1/+1
Free allocated MtdReadContext after freeing buffer field in struct, not before. Change-Id: I237920dc36115389cd2d6948e7a962dbec22fe56
2010-11-03fix comparison of ECC stats before and after mtd readsDoug Zongker1-0/+2
ECC errors are found by comparing the result of ioctl(ECCGETSTATS) before and after the read. But if an error was found causing us to go to the next block, we'd compare the stats before the *first* read to the stats after the second (third, fourth, etc.) reads, so we'd read to the end of the partition without ever succeeding. Fix logic so we compare the values before and after each read independently. Bug: 3162777 Change-Id: I5a13abd7243d2afd1d21bd98cbb233e5124b2e80
2010-09-15close update package before installing; allow remountDoug Zongker3-1/+11
Close the update package before invoking the binary, to allow the installer to unmount /cache if it wants to. Add a function to allow remounting of a mount as read-only. Change-Id: Idfcc96c3da66083295177f729263560be58034e4
2010-09-15add the ability to seek to a raw location while reading MTD partitionDoug Zongker2-0/+8
Change-Id: Id1563ca667c50e61cf1bb15d2cf783a50937eece
2010-09-12stop treating all-zero blocks as badDoug Zongker1-8/+1
Change-Id: If49fa6485f66598d16a7e44fce3129de55fab422
2010-09-10block is bad if ioctl() returns nonzeroDoug Zongker1-2/+5
Change-Id: I6fc4ce796bc663d05035927c0af0ce7ab6d07218
2010-01-13make offsets in firmware update header not point to bad blocksDoug Zongker2-4/+43
(This is being cherry-picked from master.) 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. http://b/2358012 - passion: failure to flash hboot (bad blocks?)
2010-01-13make offsets in firmware update header not point to bad blocksDoug Zongker2-4/+43
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?)
2010-01-13android-2.1_r1 snapshotThe Android Open Source Project1-5/+12
2009-12-15use MEMGETBADBLOCK to look for bad blocks when reading MTD partitionsDoug Zongker1-5/+12
2009-07-24only build flash_image for engDoug Zongker1-0/+1
With the recovery image being installed by applypatch, the flash_image tool isn't needed any more. Continue to build it for eng just in case it's handy for debugging.
2009-07-01skip over all-zero blocks when reading MTD partitionDoug Zongker1-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.
2009-03-04auto import from //depot/cupcake/@135843The Android Open Source Project6-0/+972
2009-03-04auto import from //depot/cupcake/@135843The Android Open Source Project6-972/+0
2008-12-18Code drop from //branches/cupcake/...@124589The Android Open Source Project1-0/+2
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-20 04:10:06 +0100