Database Info

[RELEASE][06/01/2011] ClockworkMod Recovery - current version - 3.0.0.5

Hi all, I thought to open this thread to keep all users updated to all the new release of the ClockworkMod Recovery for our Desire.
Current version: 3.0.0.5
FakeFlash zip for S-ON users
recovery-clockwork-3.0.0.5-bravo.zip
Flashable image for S-OFF users
recovery-clockwork-3.0.0.5-bravo.img
MD5: 0bd2a55504dd70641feb9c9b3ba5b1da
SHA-1: 0b6e77dedd8b954817d7210bf77c55f38da82278
Old versions:
2.5.1.8 (.zip - .img)
2.5.1.2 (.zip - .img)
2.5.0.7 (.zip - .img)
Changelog:
2011-01-06
fix /sd-ext wipe
fix android secure formatting
Add the volume command for seeing the current recovery.fstab. Support crazy HTC chargemode.
Refactor nandroid so the availability of boot backup is determined automatically. Boot backups are also no longer assumes to be on raw partitions, as they may be on a VFAT partition or someting different, such as in the case of Nook.
3.0.0.4. Provide an error message if an Amend zip is provided.
readd ext2/ext3 format support.
fix executable bit on e2fsck
Support for ext2 and ext3 update-binary.
2010-12-15
fix no select button
Added options for an internal SD card to be handled by recovery.
Exable uses in BoardConfig.mk:
BOARD_HAS_SDCARD_INTERNAL := true
BOARD_SDCARD_DEVICE_INTERNAL := /dev/block/mmcblk3p1
Setting BOARD_SDCARD_DEVICE_SECONDARY to the same value as
BOARD_SDCARD_DEVICE_INTERNAL will allow the device to
"fall back" to the internal SD card for other actions.
recovery: Remove condition around get_root_mtd_partition
Refactor recovery's block device handling to work across variant hardware in a cleaner fashion.
Fix write_raw_image on mtd devices.
Fix graphics corruption on some devices. BML restore needs to unlock first.
fix up bmlutils some more
2010-11-12
Supress "warning: comparison between signed and unsigned integer expressions" in minui/resources.c and mtdutils/mtdutils.c
2010-11-11
implement bmlutils
fix up implementation of int get_partition_device
Modify apply_patch to fail if trying to patch mtd on non-mtd devices.
Warning: Don't make a backup with Amon_Ra's recovery and restore it with ClockworkMod Recovery and vice-versa, you may USB brick your device.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sources available here: https://github.com/CyanogenMod/android_bootable_recovery
All credits to koush for this recovery, I only compiled them!

reserved for me.

I used unrevoked to root my phone and that put clockwork on.
So how do I go about putting this on? Flash the .zip with clockwork or flash the image via fastboot?
Cheers

unie said:
I used unrevoked to root my phone and that put clockwork on.
So how do I go about putting this on? Flash the .zip with clockwork or flash the image via fastboot?
Cheers
Click to expand...
Click to collapse
Fastboot.
Remember to S-Off.

2 newer version of recovery mod in one day
hard to choose between them
tnx for updating bro

wow thx pal for this, great staff =]

So, does it work with bravo-recovery-v1.5.3-CustomMTD.zip from http://forum.xda-developers.com/showpost.php?p=8578368&postcount=1?

Narfx said:
So, does it work with bravo-recovery-v1.5.3-CustomMTD.zip from http://forum.xda-developers.com/showpost.php?p=8578368&postcount=1?
Click to expand...
Click to collapse
Me also this interests.

as we all see, a clockwork is a one step ahead

does this have SLCD support?

Works fine here
Sent from my Desire with Oxygen, @XDA App

unie said:
I used unrevoked to root my phone and that put clockwork on.
So how do I go about putting this on? Flash the .zip with clockwork or flash the image via fastboot?
Cheers
Click to expand...
Click to collapse
both methods is working...

I have rom manager prem installed won't it auto update the recovery?

How do I setup?
Good day to you all ... How will everyone?
I wonder which of the 2 files I download to install and if I flash normally files?
How do I setup?
Thank you!

Pajorve said:
Good day to you all ... How will everyone?
I wonder which of the 2 files I download to install and if I flash normally files?
How do I setup?
Thank you!
Click to expand...
Click to collapse
as i see you are s-off so you can't use fake flash method,download the img file (the second one) so u just have to burn the recovery with unrevoked flasher tool, or the android flasher tool both are good and working.
soz i don't have time to search links, i think if u go a little down by pages u will find the android flasher.

Go to your "old" ClockworkRecovery and apply Update.zip
Worked fine for me!

goodmorning to you all.i've tried update through recovery but it didn't do it.it says 2.5.1.2 then the menu for reboot and after reboot still 2.5.0.7

konn4312 said:
goodmorning to you all.i've tried update through recovery but it didn't do it.it says 2.5.1.2 then the menu for reboot and after reboot still 2.5.0.7
Click to expand...
Click to collapse
I get this too. When I'm actually in recovery the version number is 2.5.1.2, but ROM Manager reports the version number as 2.5.0.7. ROM Manager also says the latest version is still 2.5.0.7. I guess it's ROM Manager that's wrong, rather than the actual recovery.

help
i did a backup using nandroid on this new recovery and now im in a bootloop...need assistance...

Why did you alter the source before you built it? You added your own name to the recovery screen, while I don't see that you changed or added any functionality of the recovery. Your changelog is identical to the github logs.

[RECOVERY] ClockworkMod Recovery 5.0.2.8 for vc088x tablets |v1.1b| 30-4-2012

ClockworkMod Recovery 5.0.2.8 unofficial port for Vimicro vc088x based tablets v1.1 beta by mikeNG a.k.a mikeioannina
Info:
ClockworkMod Recovery is the default recovery option by the CyanogenMod, it has several additional features over plain 3e recovery and uses Edify scripting exclusively.
CyanogenMod said:
Amend scripting (update-script) is no longer supported
Amend scripting was deprecated by Google in Android 1.5.
It was necessary to remove it when upgrading to the ClockworkMod 3.0 Gingerbread based recovery.
Please switch to Edify scripting (updater-script and update-binary) to create working update zip packages.
Click to expand...
Click to collapse
More info about creating your own update-scripts is here.
Disclaimer:
This is still experimental.
I AM NOT RESPONSIBLE FOR WHATEVER HAPPENS TO YOUR TABLET!
Some options might not work correctly and you might brick your tablet and/or lose your personal data!​
Features:
ADB root shell in recovery
Options:
Reboot system now
Apply update from sdcard
Wipe data / factory reset
Wipe cache partition
Install zip from sdcard
----Choose zip from sdcard
----Apply /sdcard/update.zip
----Toggle signature verification
----Toggle script asserts
----Choose zip from internal sdcard
Backup and restore
----Backup
----Restore
----Advanced restore
Mounts and storage
----Mount / unmount /sdcard
----Mount / unmount /emmc
----Mount / unmount /system
----Mount / unmount /data
----Mount / unmount /cache
----Format /sdcard
----Format /emmc
----Format /system
----Format /data
----Format /cache
----Mount USB storage
Advanced
----Reboot recovery
----Wipe Dalvik Cache
----Wipe Battery Stats
----Report Error
----Key Test
----Partition SD Card
--------Ext Size
--------Swap Size (Set this to 0)
--------Rest Size (vfat)
----Fix permissions
Power off
Requirements:
Basic skills in using adb or terminal emulator.
Installation:
It is recommended to do a clean install with this FlashTool first, then install the recovery image, so there is no problem with the sizes of the partitions of the internal sd.
1. Unzip the file you downloaded, you will get recovery.img
2. Copy recovery.img in your sdcard
3. Now type the following command in adb shell or in Terminal emulator:
Code:
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p3
4. It will show a message after a while, it means it's completed
Usage:
1. Turn off the device
2. Turn on the device
3. When the boot logo appears, press immediately the menu button and hold it down for 3sec approximately.
Working:
Not everything is tested yet. You are the testers for the most of the things. I've tried a backup & restore, it worked. Also tried installing a modified kernel image, it worked too.
Known bugs:
Some errors about /cache are displayed when you boot, factory reset or wipe cache. They stop if you go every time under "mounts and storage" and you mount the cache partition.
Download links:
v1.1 beta for Haipad M8 1GB version
Screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Credits:
koush: for making this wonderful recovery
Cyanogen: for all the support for android
ilarrain & teamhacksung: the fixes for the 32bit framebuffer problems​

Changelog:
24-11-2011 / ClockworkMod Recovery 5.0.2.6 v1.0a
- Initial port for the M8
- Removed multiple "No" prompts in confirm dialogs
- Fixed screen update bug
25-4-2012 / ClockworkMod Recovery 5.0.2.8 v1.1b
- Ported latest CM7 Recovery
- Fixed 32bit framebuffer (multiple screens) problem. Now the image is perfect
- Capitalized first letter of all menus in the recovery
- Changed the color from default orange to default ICS blue on the menus
To Do:
- Add support for more vc088x based tablets

is this still working?

Terramoto said:
is this still working?
Click to expand...
Click to collapse
Yes but I lost the sources so I can't build anything new

how did you unpack that recovery img i am trying to make a CWM for my penta is703c tab same as haipad m8
but it dosnt work .....................i cam boot into CWM recovery but i cant read any of the options stated there.........

ss429842 said:
how did you unpack that recovery img i am trying to make a CWM for my penta is703c tab same as haipad m8
but it dosnt work .....................i cam boot into CWM recovery but i cant read any of the options stated there.........
Click to expand...
Click to collapse
I didn't unpack the image, I compiled from source. Unfortunately I lost the modified sources so I can't help you :/

[RECOVERY] TeamWin Recovery Project (Unofficial) 2.1.6 [2012-05-27]

(Unofficial) TWRP 2.1.x for the AT&T HTC One X (Evita)!
Special credits:
Full TeamWin credits are on the TWRP page on the TeamWin website: http://teamw.in/project/twrp2
Introduction:
Team Win Recovery Project 2.1, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout – true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups – now with pigz (multi-core processor support for faster compression times)
What's new in 2.1:
Zip queuing as seen in TWRP 1.1.x is back
Slider control (swipe to confirm most actions aka swipe to wipe)
Lockscreen (with slider to unlock)
Basic file manager (copy, move, delete, and chmod any file)
Added support for devices with /data/media (most Honeycomb tablets, new ICS devices like Galaxy Nexus)
Displays sizes of each partition in the backup menu
Added listbox GUI element (currently used for listing time zones)
Updated stock XML layouts to be more consistent and easier to port to different resolutions
XML layout files are significantly smaller
Partitions available backup are more accurate for some devices
Removed unneeded error messages (/misc errors, unable to stat sd-ext, etc.)
Fixed a bug with blkid detection code
Fixed bug where a blank line was inserted between every line of text during zip installs
Fixed a bug during zip installs where an invalid zip would cause TWRP to get stuck in the zip install
Added setting for themers to toggle simulation mode to make theming easier
New devices added - Galaxy Nexus GSM & CDMA (preview only, manual install), Acer Iconia Tab A500, HTC Vivid, Motorola Defy
Added support for .jpg images in the theme engine
Changed images for stock tablet theme - makes tablet builds about 500KB smaller
Removed unneeded non-GUI images from GUI - makes all builds about 100KB smaller
In addition to the above new features, TWRP 2.1.0 now features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe cache & dalvik, and run a backup.
Theming:
Information on TWRP 2 Theming - http://teamw.in/project/twrp2themers
Known Issues:
No usb in recovery
Zip files that install more data than free space is available will crash or hang recovery (AOSP issue)
CWM backups are not compatible - please make a fresh backup in TWRP as soon as you have flashed it
Source Code:
GitHub - https://github.com/TeamWin/
DOWNLOAD:
http://rootzwiki.com/topic/26446-recovery-teamwin-recovery-project-twrp-216-2012-05-27-evita/
Support:
Click here for live support or join us in #twrp on Freenode IRC servers

thanks love twrp

niceppl said:
thanks love twrp
Click to expand...
Click to collapse
mee tooo
working on getting usb working, not sure what I did, because it was working

so how do we flash this? Does this replace CWM that we already have? Can we flash roms with this version?

equlizer said:
so how do we flash this? Does this replace CWM that we already have? Can we flash roms with this version?
Click to expand...
Click to collapse
flash it just like you flash cwm, and yes, it replaces cwm. Read the post for known issues. Everything else works.

Works perfectly.

YES!!!! My favorite recovery. Thanks DG.
Sent from my HTC One X using Xparent ICS Blue Tapatalk 2

so glad we could make this happen
thanks your help compiling #teamwin !!!
---------- Post added at 03:39 AM ---------- Previous post was at 03:38 AM ----------
equlizer said:
so how do we flash this? Does this replace CWM that we already have? Can we flash roms with this version?
Click to expand...
Click to collapse
yep just got done doing the alpha runs
everything is working except dumlock

official one released!
http://forum.xda-developers.com/showthread.php?t=1677447

[GUIDE]Flashing a Custom Recovery with or without PC

Flashing a custom recovery is the epitome of Android Hacking and Rooting. But it is always not a straightforward process. Here I am going to share three different methods for flashing a custom recovery. But first let us understand what a custom recovery is.
CUSTOM RECOVERY
Traditionally every android phone comes equipped with some sort of "recovery" program which is used for, well, recovery[emoji14]. It was intended to be used as a fallback measure in case you ended up messing with your phone. But these recoveries were (and are) terribly underpowered and offered a very basic set of features. Here comes in the topic of "Custom Recoveries". Exactly what it means, it means a recovery that has been customised or/and tweaked for some added features. The three big and famous names in the custom recovery circles are:
TeamWin Recovery Project (TWRP)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Features
Completely Touch-Driven and User Friendly UI
Fully Customizable XML-Driven Interface
Officially supports most Android devices
Has a good and extensive feature set
Supports ADB Sideload
Is a personal choice
ClockWorkMod Recovery (CWM)
Features
The First (most probably) custom recovery for android
Volume Rocker and Power Button Controllable UI
Can perform all sort of wipes including /boot and/devlog
Unofficial Versions available for most devices
Officially available only through Koushik Dutta's ROM Manager Premium app available here
Not very user friendly
Philz Touch Recovery
Features
CWM based recovery
Features three interaction modes - Full Touch, Partial Touch, Only Rockers(Non-Touch)
Everything pretty much the same as CWM including UI (though it has a okayish background)
Now after your little tuition session let's get our hands dirty and flash some recoveries!!!
As for every tutorial you will need some tools set up. They are:
Working ADB and Fastboot (only for 1st method) refer here for help in setting up adb and fastboot.
Rashr from here (only for 2nd method)
Terminal Emulator for Android by Jack Palevich from here (only for method 3)
Any Recovery image for your phone (Search "name_recovery model_name image XDA" on Google)
Rooted device for method 2 and 3
First Method - Fastboot Method
First set up ADB and Fastboot if you haven't already done so. Windows users can follow my guide here
Place the downloaded recovery.img or whateveritisidontcare.img in the same place you put your adb and fastboot if you haven't added adb directory to the PATH variable
Press Shift and rightclick on your anywhere in the white area of the screen. A popup will come up with an option "Open Command Window here". Select it
A Command Prompt shall open up. Make sure your device is connected and USB Debugging is enabled
Type the following commands one by one
Code:
adb reboot bootloader
fastboot flash recovery recovery.img
If successful your command prompt should look something like this.
Done!
Second Method - Using Rashr
Ensure you have Rashr installed and have root access
Open Rashr, grant it root acess, then close it.
Download the recovery image on to the root of your sdcard.
Use a root explorer to copy the image to "/data/data/de.mkrtchyan.recoverytools/files"
Open Rashr, select Recovery from Storage browse to the recovery on the sdcard and continue. IMPORTANT : Rashr may seem to be unresponsive for some time after selecting recovery image. IT IS NOT. Do not FC it or do anything, just keep your device aside and wait for it to report success or failure.
Rashr will take some time and hopefully won't throw up any error and show success
That's it. Enjoy !!!
Third Method - Terminal Flashing Method
This one's relatively simple. Here it goes
Open terminal emulator and type the following commands. Be sure to hit grant on the superuser prompt
Code:
cd /sdcard #type the address of the file directory, i am assuming it to be /sdcard
su
flash_image recovery recovery.img #replace recovery.img with whatever is the name of the downloaded file
If it says "Not found" or some such bull****, It's probably because Busybox isn't installed. Stock ROMs do not have busybox so you'll need @Stericson's BusyBox Free installer. It's available on the play store for free.
Done !!!
Hopefully you will be able to use these guides as a stepping stone to the world of android hacking...:victory:

[OTA] ADB-Enabler - Flashable UPDATE.ZIP File

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This tool is not meant to be used on Android devices with dm-verify or Android Verify Boot (AVB) enabled
Every Android device has a stock recovery installed. That default recovery typically at least offers you the 4 options
reboot system now
apply update from sd card
wipe data factory reset
wipe cache partition
thus you can place any valid update.zip in device's SD-card slot and update your Android from external SD-card.
Because being in recovery mode Android isn’t loaded, the Android system files are not placed in memory, which means they can be accessed, edited and replaced.
That fact allows Android users to enable ADB on their devices what natively support ADB, if they haven't done it yet, for whatever reason.
Download the signed ADB.Enabler.OTA.ZIP from here . IMPORTANT: Rename it to UPDATE.ZIP before you make use of it.
If you get error "Signature verification failed" means that OEM/Carrier blocked to flash a 3rd-party OTA. You would need to have a Custom Recovery like CWM/TWRP already installed and use that to flash the ADB.Enabler.OTA.
HTH

link not working

I am looking for zip that can enable usb-debugging and disable RSA keys without touching /data (encrypted/not mountable):
- boot.img
- system.img A-only SAR system-as-root device
I tried modifying build.prop and default.prop manually but it seems adbd is not running at all

got inspired by @ehteshamxa and created some flashable zip which does NOT modify system files. instead own files added
Code:
/system/etc/init/99userinit.rc
/system/xbin/99userinit_daemon
/sdcard/userinit.sh
/sdcard/rsa_copy
Instructions:
- install userinit-rsa_copy-flashable.zip
- install Magisk.zip
- copy adbkey.pub to SD Card
USE AT OWN RISK

aIecxs said:
got inspired by @ehteshamxa and created some flashable zip which does NOT modify system files. instead own files added
Code:
/system/etc/init/99userinit.rc
/system/xbin/99userinit_daemon
/sdcard/userinit.sh
/sdcard/rsa_copy
Instructions:
- install userinit-rsa_copy-flashable.zip
- install Magisk.zip
- copy adbkey.pub to SD Card
USE AT OWN RISK
Click to expand...
Click to collapse
is root required?

No root required. Magisk is recommended for easy avb/dm-verity disable, but of course one can also place the files manually by unpack/repack (simg2img/sdat2img) flash tool method.

optional:
- copy sqlite3 binary to SD Card
(get it from here credits: @DiamondJohn)
- copy Magisk-v23.0.apk to SD Card
(credits: topjohnwu you all know of course)
have added example code in userinit.sh that can authorize su permissions for adb shell. useful on broken screen in case one can't get scrcpy to work on boot-loop
(credits: @mirfatif for magisk.db injection)
rsa_copy works also from emulated storage if one edit the path in first line:
Code:
sdcard=/sdcard
on locked screen external MicroSD Card is only available location as MTP might not work. in that case place files from PC card reader and insert back
remember the whole purpose of that backdoor is inaccessible userdata partition, otherwise one could just add rsa_copy or 99userinit_daemon to /data/adb/service.d systemless-ly instead (or most straightforward inject /data/misc/adb/adb_keys directly).
once got su shell one can backup partitions, for example:
Code:
adb shell su -c "cat /dev/block/dm-0 2> /dev/null" > userdata.img
edit: visit main thread for more discussion
https://forum.xda-developers.com/showthread.php?t=2965462

FIX THE LINK

@AlinTecsan​So let me see f I understand well.T enable adb ub )I have stock A71 with android 11 I download this file (ADB.Enabler.OTA.ZIP file missing can u uplad it please?) the rename it in UPDATE.ZIP ,put it n SD restart handy n recovery mode selecting "Apply update fron SD card" and that will be all?

helen2 said:
@AlinTecsan​So let me see f I understand well.T enable adb ub )I have stock A71 with android 11 I download this file (ADB.Enabler.OTA.ZIP file missing can u uplad it please?) the rename it in UPDATE.ZIP ,put it n SD restart handy n recovery mode selecting "Apply update frn SD card" and taht will be all?
Click to expand...
Click to collapse
i didnt try yet i need this file this is gone as a cloud

AlinTecsan said:
i didnt try yet i need this file this is gone as a cloud
Click to expand...
Click to collapse
me to maybe I will sort ut all my troubles let we wait post is quite old :/

This won't work on stock recovery anyway, it's for custom recovery only