Guest Sebastian404 Posted December 23, 2010 Report Posted December 23, 2010 (edited) Please find attached *MY* build of the latest version of Koush's ClockworkMod Recovery for the ZTE-Blade. It is not officially supported by Koush, please do not bother him with support questions for this build. I have tested it as much as I can, but I'm always open to any more constructive feedback. Please see one post down for a change log for THIS build. Koush seems not to publish a change log (unless you know of one). To install:Recovery ManagerDownload the img file to your SD card, and then you can use the Recovery Manager application to install your recovery. fastboot methodUnplug the USB cable, turn off your device and take out the batteryReplace the battery and turn the device on holding the 'volume up' key. The device will stay at the 'green android' screen.Plug the device into the PC.From a command prompt run 'fastboot flash recovery <filename>.img' When this finishes, from the command prompt run 'fastboot reboot' update.zip methodIf you have a previous version or another recovery install, install the update.zip and restart your device. restart your device holding down the 'volume down' keyUse the Recovery Manager application to Reboot into Recoveryif you have ADB configured type 'adb reboot recovery' from the command line. The Latest version of Clockworkmod Recovery can found HEREPrevious versions: [*]Older versions of Clockwork recovery can be found here. Official release [*]The offical version of ClockworkMod Recovery if available for this device can be found here Warning: [*]Support for the old style update files that use the Amend scripting (update-script) method is no longer supported With ClockworkMod Recovery from v3 onwards, if you require support for the Amend scripting method, use v2.5.1.8. Source [*]The Device Config to build ClockworkMod Recovery as part of CyanogenMod can be found on my GitHub. Kernel Information [*]Information about the Kernel used in this ROM can be found on this thread. Edited May 13, 2011 by Sebastian404
Guest Sebastian404 Posted December 23, 2010 Report Posted December 23, 2010 (edited) Know issues: none. Build Change Log: 2010-12-23 - v2.5.1.8 b1 - Initial release 2010-12-23 - v2.5.1.8 b1 - ADBd working correctly 2010-12-23 - v2.5.1.8 b1 - Screen correct way up 2010-12-27 - v2.5.1.8 b2 - Added EXT3 support 2010-12-27 - v2.5.1.8 b2 - SDcard partitioning works as expected 2011-01-09 - v2.5.1.8 b3 - added EXT4 support to Kernel 2011-01-09 - v2.5.1.8 b3 - added TFT support to Kernel 2011-01-23 - v3.0.0.5 b1 - Initial release 2011-02-04 - v3.0.0.5 b2 - added ro.product.board to default.prop for amend scripting 2011-02-04 - v3.0.0.5 b2 - replaced kernel with custom version without TFM mode for quicker boot 2011-02-16 - v3.0.0.6 b1 - Initial release 2011-03-12 - v3.0.1.4 b1 - Initial release 2011-03-14 - v3.0.1.4 b2 - Screen rotation bug fixed. 2011-04-01 - v3.0.2.4 b1 - Initial release 2011-04-01 - v3.0.2.4 b1 - upgraded to 2.6.32 kernel 2011-04-01 - v3.0.2.4 b1 - two versions of recovery image to support Generation 1 & 2 devices 2011-04-14 - v3.0.2.4 b1 - usb problem resolved. 2011-04-25 - v3.0.2.8 b1 - Initial release Edited May 13, 2011 by Sebastian404
Guest nedian05 Posted December 23, 2010 Report Posted December 23, 2010 Know issues: None (?) Resolved issues: - ADBd working correctly - Screen correct way up - SDcard partitioning works as expected Should this be installed same way as Paul's?
Guest Sebastian404 Posted December 23, 2010 Report Posted December 23, 2010 (edited) Should this be installed same way as Paul's? Yeah, exactly the same as any recovery image...Unplug the USB cable, turn off your device and take out the batteryReplace the battery and turn the device on holding the 'volume up' key. The device will stay at the 'green android' screen.Plug the device into the PC.From a command prompt run 'fastboot flash recovery recovery-clockwork-2.5.1.8-blade.img' When this finishes, from the command prompt run 'fastboot reboot'To enter recovery mode, restart your device holding down the 'volume down' key, or type 'adb reboot recovery' from the command line. Edited December 23, 2010 by Sebastian404
Guest rayraven Posted December 23, 2010 Report Posted December 23, 2010 ^Will this still work from a terminal on the blade? Thats how i flashed the original clockwork mod. flash_image recovery /sdcard/recoveryCW.img
Guest Sebastian404 Posted December 23, 2010 Report Posted December 23, 2010 ^Will this still work from a terminal on the blade? Thats how i flashed the original clockwork mod. flash_image recovery /sdcard/recoveryCW.img I've not tried it, but cant see any reason why it should not...
Guest rayraven Posted December 23, 2010 Report Posted December 23, 2010 Works okay that way as well. Got a read error after flashing though, i hope thats okay?
Guest misterLjay Posted December 23, 2010 Report Posted December 23, 2010 ^Will this still work from a terminal on the blade? Thats how i flashed the original clockwork mod. flash_image recovery /sdcard/recoveryCW.img I flashed it using Terminal and worked fine. Nice work Sebastian404
Guest gueschmid Posted December 23, 2010 Report Posted December 23, 2010 Hallo, i cant flash it, because my SF (SWISS) do nothing if I push the +-Key and insert the batterie! Any ideas? Thanks gueschmid
Guest jurrasstoil Posted December 23, 2010 Report Posted December 23, 2010 (edited) Hallo, i cant flash it, because my SF (SWISS) do nothing if I push the +-Key and insert the batterie! Any ideas? Thanks gueschmidi have swiss sf as well and it worked for me. insert the battery, hold the + volume button on the right and while holding it press the power button on the top. Edited December 23, 2010 by jurrasstoil
Guest Carlrg Posted December 23, 2010 Report Posted December 23, 2010 Hi Seb thanks for the updated Clockwork great work. Just to let you know i have tried to do 3 nandroid backups and each time i have had 3 errors. Firstly no /sdcard/.android_secure found. Skipping backup of applications on external storage. No sd-ext found. Skipping backup of sd-ext. Generating md5 sum... Error while generating md5 sum! The second error is ok as i do not have an ext- partition, but can you please shed any light on the other errors. I am running pauls Eclair R4 and have had no issues with any earlier vers of clockwork. Thanks, Carl.
Guest hyperfighting Posted December 23, 2010 Report Posted December 23, 2010 Works great, thanks very much ! ;p
Guest oh!dougal Posted December 23, 2010 Report Posted December 23, 2010 Seb, there were (if I understood correctly) some issues with some roms/patches requiring either 'old' or 'new' Clockwork. Am I correct in thinking that this should handle both methods of 'scripting' the flash process? If so, would it make sense to note that at the top of the thread? Splendid that it should be the right way up, but ... actually, :) ;) I did rather like the quirk that, to play around with the phone's firmware, one had to use it upside down! It was part of the phone's character!
Guest Sebastian404 Posted December 23, 2010 Report Posted December 23, 2010 (edited) No /sdcard/.android_secure found. Skipping backup of applications on external storage. No sd-ext found. Skipping backup of sd-ext. Generating md5 sum... Error while generating md5 sum! The first two are just because you don't have a2sd, that .android_secure is how it tells there is something on the sd-ext partition (I belive) The other one is a bit more interesting tho, did you use the file that's attached to the first page of this thread, or one from the other thread? I've just test the backup/recovery and it works fine for me... Edited December 23, 2010 by Sebastian404
Guest Sebastian404 Posted December 23, 2010 Report Posted December 23, 2010 Seb, there were (if I understood correctly) some issues with some roms/patches requiring either 'old' or 'new' Clockwork. Am I correct in thinking that this should handle both methods of 'scripting' the flash process? If so, would it make sense to note that at the top of the thread? I'm not sure, there is no change log for clockworkmod recovery that I could find... However I build a 'old style' update.zip, and applied it to my phone, and it seems to work.. so I'd say that bug has been fixed...
Guest Carlrg Posted December 23, 2010 Report Posted December 23, 2010 The first two are just because you don't have a2sd, that .android_secure is how it tells there is something on the sd-ext partition (I belive) The other one is a bit more interesting tho, did you use the file that's attached to the first page of this thread, or one from the other thread? I've just test the backup/recovery and it works fine for me... Thanks for your reply Seb. I used the file from the first thread. I will reflash with the file from this thread and let you know. Regards, Carl.
Guest oh!dougal Posted December 23, 2010 Report Posted December 23, 2010 I'm not sure, there is no change log for clockworkmod recovery that I could find... However I build a 'old style' update.zip, and applied it to my phone, and it seems to work.. so I'd say that bug has been fixed... Great -- thanks -- I'll flash it in asap!
Guest superkryo Posted December 23, 2010 Report Posted December 23, 2010 Thanks for this great update, esp for the screen right way up. Can you include ext3 support in the kernel. Can't backup a2sd on ext3. See http://android.modaco.com/index.php?s=&...t&p=1501261 for ext3 support to 2.5.1.3. Thanks.
Guest Carlrg Posted December 23, 2010 Report Posted December 23, 2010 Thanks for your reply Seb. I used the file from the first thread. I will reflash with the file from this thread and let you know. Regards, Carl. Worked fine with the file off this thread. Thanks very much for your time Seb, best regards, Carl.
Guest jurrasstoil Posted December 23, 2010 Report Posted December 23, 2010 can i downgrade to 2.5.0.9 if needed by just flashing the .0.9 image or will this cause problems?
Guest ergo911 Posted December 23, 2010 Report Posted December 23, 2010 md5 don't match to recovery-clockwork-2.5.1.8-blade.img or recovery-clockwork-2.5.1.8-blade.zip!
Guest Sebastian404 Posted December 23, 2010 Report Posted December 23, 2010 md5 don't match to recovery-clockwork-2.5.1.8-blade.img or recovery-clockwork-2.5.1.8-blade.zip! sebastian@laverna:/home/sebastian/recovery# md5sum recovery-clockwork-2.5.1.8-blade.zip ff6de35bbe87352b6880d93ba1065445 recovery-clockwork-2.5.1.8-blade.zip[/code]
Guest ergo911 Posted December 23, 2010 Report Posted December 23, 2010 sebastian@laverna:/home/sebastian/recovery# md5sum recovery-clockwork-2.5.1.8-blade.zip ff6de35bbe87352b6880d93ba1065445 recovery-clockwork-2.5.1.8-blade.zip Yeah, my mistake, bad download i quess.
Guest tcpaulh Posted December 23, 2010 Report Posted December 23, 2010 Possible problem here :) Running 2.2, I just installed Terminal Emulator from market then re-ran universal androot (cos I have to from time to time) then launched Terminal then ran SU and granted superuser permissions following popup then :- export PATH=/data/local/bin:$PATH $ $su # flash_image recovery /sdcard/recovery-clockwork-2.5.1.8-blade.img mtd: read error at 0x00000000 (Out of memory) mtd: read error at 0x00020000 (Out of memory) mtd: read error at 0x00040000 (Out of memory) mtd: read error at 0x00060000 (Out of memory) mtd: read error at 0x00080000 (Out of memory) mtd: read error at 0x000a0000 (Out of memory) mtd: read error at 0x000c0000 (Out of memory) mtd: read error at 0x000e0000 (Out of memory) mtd: read error at 0x00100000 (Out of memory) mtd: read error at 0x00120000 (Out of memory) mtd: read error at 0x00140000 (Out of memory) mtd: read error at 0x00160000 (Out of memory) mtd: read error at 0x00180000 (Out of memory) mtd: read error at 0x001a0000 (Out of memory) mtd: read error at 0x001c0000 (Out of memory) mtd: read error at 0x001e0000 (Out of memory) mtd: read error at 0x00200000 (Out of memory) mtd: read error at 0x00220000 (Out of memory) mtd: read error at 0x00240000 (Out of memory) mtd: read error at 0x00260000 (Out of memory) mtd: read error at 0x00280000 (Out of memory) mtd: read error at 0x002a0000 (Out of memory) mtd: read error at 0x002c0000 (Out of memory) mtd: read error at 0x002e0000 (Out of memory) mtd: read error at 0x00300000 (Out of memory) mtd: read error at 0x00320000 (Out of memory) mtd: read error at 0x00340000 (Out of memory) mtd: read error at 0x00360000 (Out of memory) mtd: read error at 0x00380000 (Out of memory) mtd: read error at 0x003a0000 (Out of memory) mtd: read error at 0x003c0000 (Out of memory) mtd: read error at 0x003e0000 (Out of memory) mtd: read error at 0x00400000 (Out of memory) mtd: read error at 0x00420000 (Out of memory) mtd: read error at 0x00440000 (Out of memory) mtd: read error at 0x00460000 (Out of memory) mtd: write error at 0x00000000 (Out of memory) mtd: re-read error at 0x00000000 (Out of memory) mtd: write error at 0x00000000 (Out of memory) mtd: re-read error at 0x00000000 (Out of memory) mtd: skipping write block at 0x00000000 mtd: write error at 0x00020000 (Out of memory) mtd: re-read error at 0x00020000 (Out of memory) mtd: write error at 0x00020000 (Out of memory) mtd: re-read error at 0x00020000 (Out of memory) mtd: skipping write block at 0x00020000 mtd: write error at 0x00040000 (Out of memory) mtd: re-read error at 0x00040000 (Out of memory) mtd: write error at 0x00040000 (Out of memory) mtd: re-read error at 0x00040000 (Out of memory) mtd: skipping write block at 0x00040000 mtd: write error at 0x00060000 (Out of memory) mtd: re-read error at 0x00060000 (Out of memory) mtd: write error at 0x00060000 (Out of memory) mtd: re-read error at 0x00060000 (Out of memory) mtd: skipping write block at 0x00060000 mtd: write error at 0x00080000 (Out of memory) mtd: re-read error at 0x00080000 (Out of memory) mtd: write error at 0x00080000 (Out of memory) mtd: re-read error at 0x00080000 (Out of memory) mtd: skipping write block at 0x00080000 mtd: write error at 0x000a0000 (Out of memory) mtd: re-read error at 0x000a0000 (Out of memory) mtd: write error at 0x000a0000 (Out of memory) mtd: re-read error at 0x000a0000 (Out of memory) mtd: skipping write block at 0x000a0000 mtd: write error at 0x000c0000 (Out of memory) mtd: re-read error at 0x000c0000 (Out of memory) mtd: write error at 0x000c0000 (Out of memory) mtd: re-read error at 0x000c0000 (Out of memory) mtd: skipping write block at 0x000c0000 mtd: write error at 0x000e0000 (Out of memory) mtd: re-read error at 0x000e0000 (Out of memory) mtd: write error at 0x000e0000 (Out of memory) mtd: re-read error at 0x000e0000 (Out of memory) mtd: skipping write block at 0x000e0000 mtd: write error at 0x00100000 (Out of memory) mtd: re-read error at 0x00100000 (Out of memory) mtd: write error at 0x00100000 (Out of memory) mtd: re-read error at 0x00100000 (Out of memory) mtd: skipping write block at 0x00100000 mtd: write error at 0x00120000 (Out of memory) mtd: re-read error at 0x00120000 (Out of memory) mtd: write error at 0x00120000 (Out of memory) mtd: re-read error at 0x00120000 (Out of memory) mtd: skipping write block at 0x00120000 mtd: write error at 0x00140000 (Out of memory) mtd: re-read error at 0x00140000 (Out of memory) mtd: write error at 0x00140000 (Out of memory) mtd: re-read error at 0x00140000 (Out of memory) mtd: skipping write block at 0x00140000 mtd: write error at 0x00160000 (Out of memory) mtd: re-read error at 0x00160000 (Out of memory) mtd: write error at 0x00160000 (Out of memory) mtd: re-read error at 0x00160000 (Out of memory) mtd: skipping write block at 0x00160000 mtd: write error at 0x00180000 (Out of memory) mtd: re-read error at 0x00180000 (Out of memory) mtd: write error at 0x00180000 (Out of memory) mtd: re-read error at 0x00180000 (Out of memory) mtd: skipping write block at 0x00180000 mtd: write error at 0x001a0000 (Out of memory) mtd: re-read error at 0x001a0000 (Out of memory) mtd: write error at 0x001a0000 (Out of memory) mtd: re-read error at 0x001a0000 (Out of memory) mtd: skipping write block at 0x001a0000 mtd: write error at 0x001c0000 (Out of memory) mtd: re-read error at 0x001c0000 (Out of memory) mtd: write error at 0x001c0000 (Out of memory) mtd: re-read error at 0x001c0000 (Out of memory) mtd: skipping write block at 0x001c0000 mtd: write error at 0x001e0000 (Out of memory) mtd: re-read error at 0x001e0000 (Out of memory) mtd: write error at 0x001e0000 (Out of memory) mtd: re-read error at 0x001e0000 (Out of memory) mtd: skipping write block at 0x001e0000 mtd: write error at 0x00200000 (Out of memory) mtd: re-read error at 0x00200000 (Out of memory) mtd: write error at 0x00200000 (Out of memory) mtd: re-read error at 0x00200000 (Out of memory) mtd: skipping write block at 0x00200000 mtd: write error at 0x00220000 (Out of memory) mtd: re-read error at 0x00220000 (Out of memory) mtd: write error at 0x00220000 (Out of memory) mtd: re-read error at 0x00220000 (Out of memory) mtd: skipping write block at 0x00220000 mtd: write error at 0x00240000 (Out of memory) mtd: re-read error at 0x00240000 (Out of memory) mtd: write error at 0x00240000 (Out of memory) mtd: re-read error at 0x00240000 (Out of memory) mtd: skipping write block at 0x00240000 mtd: write error at 0x00260000 (Out of memory) mtd: re-read error at 0x00260000 (Out of memory) mtd: write error at 0x00260000 (Out of memory) mtd: re-read error at 0x00260000 (Out of memory) mtd: skipping write block at 0x00260000 mtd: write error at 0x00280000 (Out of memory) mtd: re-read error at 0x00280000 (Out of memory) mtd: wrote block after 1 retries mtd: not writing bad block at 0x00440000 error writing recovery: No space left on device # I've emailed the terminal output to myself from within Terminal but left it sitting (right now) with the terminal window open in case something is badly b0rked. I'm at a relatives house on an old XP PC with nothing useful installed in case it's relevant. Advice?
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now