Guest Sebastian404 Posted January 8, 2011 Report Posted January 8, 2011 (edited) Please find attached *MY* build of the latest version of Amon_RA's RA-Recovery for the ZTE-Blade. It is not officially supported by Amon_RA, please do not bother him with support questions for this build. Please see one post down for a change log for THIS build. Please see two posts down for Amon_RA's readme/change log 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 method Unplug the USB cable, turn off your device and take out the battery Replace 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. Howto Enter recovery mode: restart your device holding down the 'volume down' key Use the Recovery Manager application to Reboot into Recovery if you have ADB configured type 'adb reboot recovery' from the command line. Downloads:The Latest version of RA_Recovery can found HERE Previous versions: Older versions of RA-Recovery can be found here. Which version: RA_Recovery now comes in 2 different versions for 1st and 2nd Generation devices, if your device originaly shipped with Android 2.1, it will usually be 1st generation, if it came with 2.2 it will usually be 2nd generation. Please note if you have used an officaly updater on a 1st generation device it will now be a 2nd generation device. 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 15, 2011 by Sebastian404
Guest Sebastian404 Posted January 8, 2011 Report Posted January 8, 2011 (edited) Know issues: USB support is not always initialized correctly, select the 'Reboot Recovery' option under 'advanced' menu option Build Change Log: 2011-01-07 - 2.0.0 b1 - Initial Release. 2011-01-08 - 2.0.0 b2 - Resolved issues with recovery not starting in FTM mode. 2011-01-08 - 2.0.0 b3 - Resolved issues with SD Card Partitioning. 2011-01-08 - 2.0.0 b4 - Resolved issues with Nandroid (hopefully) 2011-01-09 - 2.0.0 b5 - added EXT4 support to Kernel 2011-01-09 - 2.0.0 b6 - added TFT support to Kernel 2011-01-17 - 2.2.1 b1 - Initial Release. 2011-04-01 - 2.2.1 b2 - upgraded to 2.6.32 kernel 2011-04-01 - 2.2.1 b2 - two versions of recovery image to support Generation 1 & 2 devices 2011-04-14 - 2.2.1 b3 - usb problem resolved 2011-04-17 - 2.3 b1 - Initial Release. 2011-05-14 - 2.3 b2 - fix nandroid backup/restore issue. Edited May 15, 2011 by Sebastian404
Guest Sebastian404 Posted January 8, 2011 Report Posted January 8, 2011 (edited) Original readme/change log: This is a custom recovery based on Cyanogen's recovery source with a lot of things added by me. The purpose of this recovery is to avoid using adb by accessing all features directly from the menu. Important notesAlways check recovery.log before posting your issues! You can do this by doing :"cat /tmp/recovery.log" OR "cat /cache/recovery/log" right after you had the issue.Use the "move log to sd" option in the "others" menu right after you had the issue. This will move the log to /sdcard/recovery.log so you can easily open it with a text editor. Use the volume buttons (up+down) to navigate through the menu, press the Menu-key to select items. Use the Back-key to go back to a previous menu.full ADB access in recovery modeBusybox v1.15.3Kernel (2.6.29) with ext3 support OLED and TFT supportHW-Key navigation (Volume up/down) optionExtended menu :Reboot system now :: reboot your phoneUSB-MS Toggle :: enable/disable USB mass storage (use when the phone is connected to your PC)Backup/RestoreNand backup :: Make a Nand backup (/sdcard/.android_secure included), the following partitions are NOT included :Recovery (to avoid restoring old version)Misc (no need to backup imo + restore issues on some phones)Splash1+2 (no need to backup imo + restore issues on some phones) Nand + ext backup :: Make a Nand + ext backupNand restore :: Restore a Nand backupBackup Google proprietary system files :: Makes a backup of the Google proprietary system files in /cache/googleRestore Google proprietary system files :: Restores the Google proprietary system files from /cache/google Flash zip from sdcard :: Flash a zip update file from any (sub)-directory on your sdcardWipeWipe ALL userdata :: wipes /data + /cache + entire ext partition + all apps installed on your sdcard (froyo a2sd).Wipe only /data :: wipes /data.Wipe only /sd-ext :: wipes the entire ext partition on your sd (if present). Wipe only /sdcard/.android_secure :: wipes all apps installed on your sdcard (froyo a2sd).Wipe only /cache :: wipes /cache.Wipe only Dalvik-cache :: wipes the dalvik-cache located in /cache + /data + /sd-ext is present.Wipe only battery stats :: reset the battery calibration.Wipe only rotate settings :: reset the sensor calibration. Partition sdcardPartition SD :: Interactive SD partitioningRepair SD:ext :: Repair the ext partitionSD:ext2 to ext3 :: Convert ext2 to ext3SD:ext3 to ext4 :: Convert ext3 to ext4 Mounts(Un)Mount /system(Un)Mount /cache(Un)Mount /data(Un)Mount /sd-ext(Un)Mount /sdcard OtherFix apk uid mismatches :: Does extacly thatMove recovery.log to SD :: Moves the recovery log file to your sdcard. (Use when you want more detailed recovery log information)Toggle Signature Verify :: Toggles the signature verification for zip files. [*]Power off :: Powers off your phone [*]Scripts available via adb : [*]Nandroid v2.2.1 : enter "nandroid-mobile.sh" to start. [*]sdparted v0.6 : enter "sdparted" to start. Change-log : v2.3 [*]Nandroid will skip sd-ext backup when it's not present. [*]Nandroid will not check the battery percentage anymore. [*]Switched off signature check by default (Stop asking now, ok?). [*]Cache is not selected as part of a default Nandroid backup anymore. [*]Added wipe Boot, System and sdcard to the wipe menu. [*]Re-ordered some items in the wipe menu. v2.2.1 [*]Nandroid backup is now selective, boot/system/cache/data are selected by default. [*]Nandroid checks if there's at least 500MB free on SDcard before starting a backup. [*]Added/updated error/warning messages. v2.1.1 [*]Fixed ext4 support in kernel! Update from v2.x if you are using sd-ext! v2.1.0 [*]Reduced recovery size by 800kb so it fits any hboot version to date : [*]Set Kernel compression mode to LZMA (33% smaller kernel) [*]Switched kernel debugging off [*]Removed : Networking support - Bluetooth subsystem support [*]Removed : Device Drivers - Misc device - AKM8973 Compass Driver [*]Removed : Device Drivers - Misc device - A1026 Voice Processor Driver [*]Removed : Device Drivers - Multimedia support [*]Removed : Device Drivers - MSM 3D Graphics driver for Adreno class GPU's [*]Nandroid now backups the entire content of /sd-ext , not just the apps. This fixes bootloops of certain restored roms. [*]Moved the "Toggle signature verification"-option from the Other- to the main flash-submenu. [*]Re-ordered the wipe menu. v2.0.0 Some things in v2.0.0 were kanged with a twist from the Clockworkmod recovery. [*]Updated kernel to 2.6.35 (SLCD and AMOLED are now both supported). [*]Added SDEXT support for update scripts. [*]Added "filebrowser" support when you select a zip to flash. [*]Added "/.." support to the filebrowser so you can navigate up. [*]Added a mount menu so you can manually (u)mount stuff. [*]Added a toggle verification switch so you can flash those awesome unsigned winrar rom releases... [*]Fully re-wrote the wipe menu (it's not using a script anymore), added a few new wipe options. [*]Added "/sdcard/.android_secure" support , nandroid now backups/restores .android_secure (Froyo a2sd apps) by default. [*]Added a few new Google apps to the Google app backup script. Edited April 17, 2011 by Sebastian404
Guest css771 Posted January 8, 2011 Report Posted January 8, 2011 (edited) This is great! Lately seems like us Blade users are spoilt for choice! Great work Seb Edited January 8, 2011 by css771
Guest css771 Posted January 8, 2011 Report Posted January 8, 2011 (edited) Double post Edited January 8, 2011 by css771
Guest joyfun Posted January 8, 2011 Report Posted January 8, 2011 It seems not work in UK OLED version It stop at this Screen
Guest PeaNut_HU Posted January 8, 2011 Report Posted January 8, 2011 In what functions does this differ / offer more (or less) than the already widely used ClockWorkMod ? Are ClockWorkMod update.zip files compatible with this RA_Recovery ?
Guest ololizoz Posted January 8, 2011 Report Posted January 8, 2011 hello, in your posts i suggest that you change it to fastboot-windows and so on, first time i flashed clockwork it took me about an hour to find out that you need to write fastboot-windows instead of fastboot
Guest Cowardly Courage Posted January 8, 2011 Report Posted January 8, 2011 Impressive. until now, works fine for me. ty Sebastian, keep the good work
Guest Lew247 Posted January 8, 2011 Report Posted January 8, 2011 (edited) hello, in your posts i suggest that you change it to fastboot-windows and so on, first time i flashed clockwork it took me about an hour to find out that you need to write fastboot-windows instead of fastboot Another option is rename fastboot-windows.exe to fastboot.exe In Windows open command prompt navigate to where you have the fastboot-windows file type ren fastboot-windows.exe fastboot.exe Then you just type as above Edited January 8, 2011 by Lew247
Guest jamidodger1 Posted January 8, 2011 Report Posted January 8, 2011 It seems not work in UK OLED version It stop at this Screen Exact Same Problem :D
Guest freddykr Posted January 8, 2011 Report Posted January 8, 2011 Same problem here, but I have TFT.
Guest Sebastian404 Posted January 8, 2011 Report Posted January 8, 2011 In what functions does this differ / offer more (or less) than the already widely used ClockWorkMod ? Are ClockWorkMod update.zip files compatible with this RA_Recovery ? The menus are listed in the 3rd post.... the update.zip format is a standard format, they will work with all recovery that support that standard
Guest Sebastian404 Posted January 8, 2011 Report Posted January 8, 2011 The guys who are having problems, have you used the 'Hungarian fix' or one of the other things that resizes your partitions? did you check the md5 of the file? have you partitioned your SD card?
Guest StevenHarperUK Posted January 8, 2011 Report Posted January 8, 2011 Nice work Sebastian I will do my next flash with this and see how I get on.
Guest joyfun Posted January 8, 2011 Report Posted January 8, 2011 The guys who are having problems, have you used the 'Hungarian fix' or one of the other things that resizes your partitions? did you check the md5 of the file? have you partitioned your SD card? md5 is correct and. sd card have only one fat32 partition.have not use 'Hungarian fix' before . and previous clockwork 2.5.18 works fine
Guest Sebastian404 Posted January 8, 2011 Report Posted January 8, 2011 md5 is correct and. sd card have only one fat32 partition.have not use 'Hungarian fix' before . and previous clockwork 2.5.18 works fine Can you do a 'adb shell' and connect to your device?
Guest oh!dougal Posted January 8, 2011 Report Posted January 8, 2011 The guys who are having problems, have you used the 'Hungarian fix' or one of the other things that resizes your partitions? ... have you partitioned your SD card? Why might those two things matter? :D
Guest MDCFan Posted January 8, 2011 Report Posted January 8, 2011 It seems not work in UK OLED version It stop at this Screen Recovery was working fine for me when I was using Japanese Jellyfish RLS5. Then I installed FLB-Froyo G2 r6 which made my phone hang on this screen too.
Guest kallt_kaffe Posted January 8, 2011 Report Posted January 8, 2011 It seems not work in UK OLED version It stop at this Screen Exactly the same for me on my OSF.
Guest kallt_kaffe Posted January 8, 2011 Report Posted January 8, 2011 (edited) The guys who are having problems, have you used the 'Hungarian fix' or one of the other things that resizes your partitions? Yes, 128Mb system and 287Mb data. did you check the md5 of the file? No, but I will now. EDIT: MD5 seems fine: 3966C1828CDD7134EAF1DE606F40569D have you partitioned your SD card? No, using an 8Mb card with only one (FAT32) partition. Edited January 8, 2011 by kallt_kaffe
Guest Sebastian404 Posted January 8, 2011 Report Posted January 8, 2011 Exactly the same for me on my OSF. Can you connect to the shell using 'adb shell' ?
Guest Sebastian404 Posted January 8, 2011 Report Posted January 8, 2011 Why might those two things matter? :D I've had a lot of people complaining about my roms not working after they had reduced thier system partition down to be too small... I want to rule it out I've re-downloaded this and re-flashed it to both my OSF devices and it works fine with both of them... but I've not really 'messed' with any of them, so im trying to find the common denominator with people who have the problem....
Guest kallt_kaffe Posted January 8, 2011 Report Posted January 8, 2011 Can you connect to the shell using 'adb shell' ? Well, I'm back to Clockwork now but I tried "adb shell" and no, it didn't connect.
Guest kallt_kaffe Posted January 8, 2011 Report Posted January 8, 2011 I've had a lot of people complaining about my roms not working after they had reduced thier system partition down to be too small... I want to rule it out I've re-downloaded this and re-flashed it to both my OSF devices and it works fine with both of them... but I've not really 'messed' with any of them, so im trying to find the common denominator with people who have the problem.... Well, I could try to bring back the old partitioning and try but not right now. I've reinstalled so many times the last few days that I really don't want to do it again right now.
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now