Database Develop

[15.11.2012][ICS]PhilZ Touch 3.00N - CWM Based Recovery 6.0.1.5 (Temporary flash)

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
PhilZ Touch 3.0 Recovery
(Clockworkmod v6.0.1.5 based recovery)
Galaxy Note - N7000 Version Only
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *​
This is the temporary version of my custom clockworkmod recovery
For permanent one, look here
WARNING: flashing some update.zip files with format commands
can still brick your phone until you use a safe kernel, like PhilZ-cwm6.
New in v3.00
Completely revised new touch code
Much more user friendly touch experience
Lots of new features
Video Teaser:
Main menu at height setting 5 and 1
{
"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"
}
PhilZ Settings menu
Backup / Restore EFS and kernel
GUI Touch Settings
Aroma File Manager
Source code
coming soon...
Read in my kernel thread post 2 for instructions to use PhilZ Touch features like aroma and ors support[/SIZE][/B]
PhilZ Touch 3.0 recovery (clockworkmod v6.0.1.5 based):- touch interface: toggle 3 touch modes: FULL TOUCH, DOUBLE TAP to validate and SEMI TOUCH (scroll but no touch validation)
[*]new touch code completely revised compared to v2.x and older
[*]much more stable full touch mode: no more skips, jumps or wrongly validations while scrolling
[*]when you set full touch mode, it defaults to optimized settings for menu height and touch sensitivity (you still can alter them manually later)
[*]adjust scrolling touch sensitivity in 6 settings
[*]adjust menu height in 6 settings
[*]toggle vibrator on/off when using bottom virtual buttons
[*]toggle key repeat for volume up/down scrolling when maintained pressed: needs recovery restart to take effect
[*]backup/restore EFS and Kernel
[*]browse phone with root access using full GUI in Aroma File Manager: default location or browse for path
[*]support openrecovery script in 3 modes using a smart one touch menu: goomanager, default custom scripts location, browse for script
[*]mount internal and external sdcards on PC in recovery
[*]poweroff, reboot to recovery and reboot to download mode options
[*]Can be flashed in Stock Recovery
[*]Dual USB mount in recovery support (needs fixed kernel like PhilZ-cwm6)
[*]ADB root in recovery: just wait about a minute to activate​
​
Click to expand...
Click to collapse
Why a temporary recovery?
Wipe safely on a stock kernel
Will work on any i9100 phone with ICS, even stock non rooted
No PC needed, only and android device and the zip files that you download to your sd card
Fully reversible after reboot
No Yellow Triangle and No custom counter increased
Incremental Backups to save a lot of space and time (CWM6)
Much better user interface, bigger menus, smoother scroll, safer touch, works with both touch and keys
Click to expand...
Click to collapse
Flashing instructions for stock recovery
Download philz-touch_x.xx_n7000-signed.zip, the last philz touch cwm v6.x for n7000 Galaxy Note. This version works with touch AND with keys to scroll in menus
Put the previously downloaded philz-touch_x.xx_n7000-signed.zip file on your external sd card
Boot into stock recovery (volume up+home+power), and select "apply update from external storage". Now select the philz-touch_x.xx_n7000-signed.zip file you copied in previous step
You get CWM recovery interface (this custom recovery is temporary, not permanent)
Click to expand...
Click to collapse
You are done
If it fails with black screen after successful flash:
read about it here: http://forum.xda-developers.com/showpost.php?p=32785650&postcount=33
It is because their recovery is not automatically restarted once killed
You can manually edit the file /sbin/killrecovery.sh in the temporary recovery zip package and modify it by adding the extra 2 lines before the #...
(make sure you edit it in something like notepad++ with EOL conversion set to unix)
so that it looks like below:
Code:
kill $(ps | grep /sbin/adbd)
kill $(ps | grep /sbin/recovery)
/sbin/recovery &
exit 1
Save the zip and try it again
Click to expand...
Click to collapse
Change log
15 nov 2012:Update to new custom touch 3.00 recovery included in PhilZ-cwm6 kernel
Read full change log in kernel thread
08 oct 2012:Update to new custom touch recovery included in PhilZ-cwm6 kernel
Wipe safely on a stock kernel, flash even update.zip files with format commands (patched update-binary)
now using CWM6 based custom touch recovery 6.0.1.4 (internal build 1.15) * Siyah source code *
DUAL USB MOUNT in recovery is now supported * Special thanks to [email protected] *
semi-touch interface with right slide to select disabled for safety: use slide up/down and left for back
include bottom virtual buttons for easier navigation
revised GUI with bigger fonts and larger menus for better readability
transparency effects in recovery menus
fixed backup format selection menu in original Koush cwm6 (was echoing previous menu)
added power off and reboot to download mode options in recovery menus
battery % level displayed in recovery
fixed some menus spelling and aspect in original recovery
Click to expand...
Click to collapse
20 Sep 2012: Update non touch version to 6.0.1.4 ** Recommanded Update from previous 6.0.1.4 attached here **
Now, CWM6 is built from source to fix possible issues related to previous dynamically linked binary
Big big thanks to Tallustus from Team SkyFire for the support
Click to expand...
Click to collapse
19 Sep 2012: Update non touch version to 6.0.1.4
Touch version stays at 6.0.1.2: if you know about a kernel with touch 6.0.1.4 or source changes for touch cwm6, let me know please
6.0.1.4 : version increment for ROM Manager compatibility
Click to expand...
Click to collapse
17 Sep 2012: Update non touch version to 6.0.1.3
Touch version stays at 6.0.1.2: if you know about a kernel with touch 6.0.1.3 or source changes for touch cwm6, let me know please
6.0.1.3 many bug fixes and performance issues.
Click to expand...
Click to collapse
28 Aug 2012: Update to 6.0.1.2 - Touch (ICS only) and non touch versions
6.0.1.2 fixes some issues with /sdcard (/data/media).
Click to expand...
Click to collapse
Download link and warning at post 2
Credits
Chenglu for his great unpack / repack tool: MAJOR CREDITS
kbc-developers for the base semi-touch code :good:
[email protected] for his touch source and great support over PM in fixing dual USB mount: MAJOR CREDITS
Tallustus from Team Skyfire for his great support over IRC: MAJOR CREDITS
sk8erwitskil for his recovery source (ors support, aroma file manager and efs backup/restore), a great place to start learning: MAJOR CREDITS
shoe63 for his testing and great help in porting to the N7000 Big thanks
dr.ketan for his precious help in porting to the N7000 (I don't own one), for support in the thread and for his faster mirrors: Big thanks
utkanos for his great and kind support over IRC
gweedo767 @ #Koush for sharing his new touch code source (not yet used)
myfluxi for his xxRecovery source in fixing dual usb mount
Koush for his great work on CWM6 and CM
Cyanogenmod for their scripts / initramfs
Chainfire for his support (stock recovery flash) and all his work for the Android community
superatmos and Dharam_Maniar for their great guides on unpacking/building custom kernels

Download link posted again because of demands over PM
If you do not know what you do, do not download this
It can brick your phone, do not take me responsible
Until it is confirmed, never flash update.zip files if not on a safe kernel​
Safe kernels for the Note are, among others, PhilZ-cwm6, Hydracore, CM9/10 and AOKP...
The issue:
I personally do not see harm having a temporary recovery, but in practice, to flash a ROM in recovery, you are strongly recommended to have a safe kernel. Since most safe kernels come with a cwm recovery, the temporary one is now useless, and even risky as people can wrongly think they are safe
To super brick a phone when wiping in recovery, you need 3 conditions and all 3 must be true:
1 - unsafe kernel
2 - bad chipset
3 - unsafe recovery
Click to expand...
Click to collapse
When flashing update.zip files, the conditions are:
1 - unsafe kernel
2 - bad chipset
3 - format command in update.zip file with unsafe binary-update
Click to expand...
Click to collapse
So, when flashing update.zip files (mainly some custom ROMs), even on safe recovery you can still brick your phone if you are on an unsafe kernel
This was confirmed by Elite Recognized Develope Entropy512
So, do not flash update.zip files in this one if you do not know what you do. YOU ARE WARNED
Do not come crying I am responsible about bricking your phone

Hmmmm still i would like to try it with the risk involved in it
Sent from my GT-N7000 using xda premium

microsd16 said:
Hmmmm still i would like to try it with the risk involved in it
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
I personally do not see harm having a temporary recovery, but in practice, to flash a ROM in recovery, you are strongly recommended to have a safe kernel. Since most safe kernels come with a cwm recovery, the temporary one is now useless, and even risky as people can wrongly think they are safe
I am really not sure if it is risky or not.
I would open the thread again if this point is clarified:
To super brick a phone, you need 3 conditions and all 3 must be true
1 - unsafe kernel
2 - bad chipset
3 - unsafe recovery
This is true when you wipe in recovery
Now, lately, came the binary-update story when you flash update.zip files with format commands
So, is that a 4th needed condition or something that will brick your phone if conditions 1 + 2 are true, what ever condition 3 is
Condition 3 would be:
3 - unsafe recovery AND / OR ???? unsafe update-binary

Phil3759 said:
I personally do not see harm having a temporary recovery, but in practice, to flash a ROM in recovery, you are strongly recommended to have a safe kernel. Since most safe kernels come with a cwm recovery, the temporary one is now useless, and even risky as people can wrongly think they are safe
I am really not sure if it is risky or not.
I would open the thread again if this point is clarified:
To super brick a phone, you need 3 conditions and all 3 must be true
1 - unsafe kernel
2 - bad chipset
3 - unsafe recovery
This is true when you wipe in recovery
Now, lately, came the binary-update story when you flash update.zip files with format commands
So, is that a 4th needed condition or something that will brick your phone if conditions 1 + 2 are true, what ever condition 3 is
Condition 3 would be:
3 - unsafe recovery AND / OR ???? unsafe update-binary
Click to expand...
Click to collapse
Can u plz share with me the link via pm
Sent from my GT-N7000 using xda premium

PM sent
Waiting for clarifications to upload again

Because of the demand over PM, I edited post 1 and uploaded again in post 2 with warnings
Be warned, until it is confirmed by some knowledge members

Phil3759
please PM

Can i fully take nandroid backup and restore it with the temporary recovery??

kanishkgaur said:
Can i fully take nandroid backup and restore it with the temporary recovery??
Click to expand...
Click to collapse
Yes, that's should be safe
Sent from my GT-I9100 using Tapatalk 2

it is possible to have this in not temporary but permently ?

Yes, but you need the whole kernel:
http://forum.xda-developers.com/showthread.php?t=1901191

I think the best use of this temp recovery, is for stock ROM devices.
As far as I know, after booting into this temp recovery, I'd just flash a safe kernel (like PhilZ 2.7), and do boot to recovery again.
Then you'll have safe kernel and recovery for wiping and flashing....
Sent from my GT-N7000 using Tapatalk 2

Hi Philz, flash cwm-6.0.1.4-PhilZ-1.15-n7000.zip.
so, question is flash this *.zip for what?
is it necessary to flash ...1.15n7000.zip affter flash your kernel?
Thanks for your advance !!!

kenshinjar said:
Hi Philz, flash cwm-6.0.1.4-PhilZ-1.15-n7000.zip.
so, question is flash this *.zip for what?
is it necessary to flash ...1.15n7000.zip affter flash your kernel?
Thanks for your advance !!!
Click to expand...
Click to collapse
no if u have his kernel..u already have this recovery as permanent. this is for those who doesnt have it.. its a Temp recovery. will be gone after reboot
---------- Post added at 07:21 PM ---------- Previous post was at 07:20 PM ----------
liron_69 said:
I think the best use of this temp recovery, is for stock ROM devices.
As far as I know, after booting into this temp recovery, I'd just flash a safe kernel (like PhilZ 2.7), and do boot to recovery again.
Then you'll have safe kernel and recovery for wiping and flashing....
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
but u dont need this recovery to flash his kernel.. it can be flashed on a stock recovery

nokiamodeln91 said:
but u dont need this recovery to flash his kernel.. it can be flashed on a stock recovery
Click to expand...
Click to collapse
It can be flashed with PC Odin and yellow triangle with counter.
My method does the same without using PC Odin or counter....
You don't need triangle away in this case....
Sent from my GT-N7000 using Tapatalk 2

liron_69 said:
It can be flashed with PC Odin and yellow triangle with counter.
My method does the same without using PC Odin or counter....
You don't need triangle away in this case....
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
No, PhilZ-cwm6 in zip package can be flashed directly in stock recovery bypassing signature check, no yellow triangle or anything like that
I add odin packages as sometimes they come handy when you loose recovery access (like in my case when playing with them too much)

liron_69 said:
It can be flashed with PC Odin and yellow triangle with counter.
My method does the same without using PC Odin or counter....
You don't need triangle away in this case....
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
this is wat I was trying to say. u can flash it in the stock Android recovery 3e
# message swifted from Note, travelled in the air to gateway and wi-maxed to [email protected] #

Well, it seems that we all set for this great recovery. The last time I saw the stock recovery 3e was when I bought my device and for few seconds only
Thanks for this solution for those who needs it...
Sent from my GT-N7000 using Tapatalk 2

Confirmed SAFE by Entropy except for flashing zips with unpatched update-binary.
Sent from my GT-N7000 using xda app-developers app

[RECOVERY CWM][5110/5100/5120][Touch]CivZ Rev1.1 - PhilZ 5 recovery [24/okt/2013]

All credits go to Phil3759 as I just ported it to our device. Original thread, I had to change some stuff like the ramdisk and zImage to make it working on our device.
Touch driver fix (also for aroma) thanks to nickdollahz
Click to expand...
Click to collapse
I'm not responsible for your bricked device!
* * * * * * * * * * * * * * * * * * * * * * * * *
PhilZ Touch 5 Recovery
CivZ version 1.1
CWM Advanced Edition 6.x
* * * * * * * * * * * * * * * * * * * * * * * * *
{
"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 of this ported recovery:
RECOVERY IS IN TABLET MODE
Touch recovery based on cwm 6.0...
zImage compiled by civato based on Samsung Update2 with Exfat support
Touch driver fixed for aroma thanks to nickdollahz
Backup / restore
Custom backup / restore
EFS backup / restore: It is stored as a hidden file in clockworkmod/backup.
Change theme layout and touch settings
TWRP and CWM restore support
Format data/media = internal_SD will be empty.
Power menu
etc..............................
Full detail from the original thread
touch interface:- toggle between 4 touch modes: FULL TOUCH, DOUBLE TAP to validate and SEMI TOUCH (scroll but no touch validation) and NO TOUCH to only use hardware keys
- written from scratch full touch code
- safe full touch : no wrongly validations while scrolling
- when you set full touch mode, it defaults to optimized settings for menu height, scroll sensitivity and touch accuracy (you still can alter them manually later)
- adjust scroll sensitivity in a huge palette
- adjust menu height in a huge palette
- adjust touch accuracy
- 30 color settings for each of the 8 GUI parts + 5 alpha transparency settings
- user custom background png can be selected in addition to 30 solid colors option
- show / hide background icon
- show / hide bottom virtual buttons
- show/hide + set color and transparency for menu line separators to match solid color themes, like Black...
- set number of bottom log rows to show
- Friendly Log View and pause on logs: no more miss logs during zip installs
- auto dim screen after user configurable delay
- auto turn off screen after user configurable delay
- adjust brightness and turn off screen with a gesture action
- show/hide clock and remaining battery %, even during nandroid operations
- clock and battery stats now effectively refresh every 30 seconds and during nandroid operations
- toggle vibrator on/off on touch
- toggle key repeat for volume up/down scrolling when maintained pressed
- key repeat also enabled for virtual buttons
- set time zone + 30mn offset + DST: correct time can now be set for nandroid backup path and clock
- time setting is now applied to all recovery session, including timestamp of created/modified files (v4.92.3+)
- capture recovery screen shots with a gesture action
- one file to save all settings
- backup and restore settings file
- reset to default settings option
- prompt to restore your settings from a backup when they are wiped by a new ROM install
- option to auto restore your settings from a backup without a prompt
- all toggles are applied live, without restart of recovery (except reset of stock CWM background image)
- toggle menu options are automatically right aligned and menu text left aligned based on device display size
- configurable gesture actions: double tap, slide right/left, long press/lift, long press/move, can be associated with any of: show log, change brightness, blank screen, capture screen shot, launch Aroma File Manager​Note: after scroll, first touch will select only. After one sec of scrolling or on second touch, it will validate immeadiately. This is by design and not a bug. It is there to limit erroneous validation while scrolling
Read more about it here: Validation Lock after scrolling
First to introduce true JB 4.2 migration: toggle between /data/media and /data/media/0
browse phone with root access using full GUI in Aroma File Manager
terminal access from recovery with root access through Aroma File Manager
Multi Zip Install menu: check multiple zip files to install in a row
Custom Install Zip Mode: set a default folder to start with + browse backward up to the root
exFAT, NTFS and Ext4 support in recovery for external sd
TWRP backup and restore support, include full md5 sum support (single and multivolume, compressed and non compressed formats)
Advanced statistics during backup operations shown in color: total backup size, backup size progress, backup time, compression ratio...
support .android_secure backup/restore from external storage
optional reboot after custom backups/restores
sd-ext support (ext4)
nandroid backups support /preload in backup and restore jobs (custom and stock modes)
nandroid backups support /misc in backup and restore jobs (custom mode)
set special nandroid settings: time zone, toggle md5 check for lightning fast backup and restore, toggle /preload backup and restore, enable nandroid compression using pigz (multi-cpu gzip compression) and choose ors backup target volume
recreate md5 sum check for your cwm backups for compatibility with stock CWM if you need to revert
you can cancel any nandroid operation with back button
create custom_rom.zip from current ROM or from a pre-existing nandroid backup (based on boot, /system and optionally /preload)
nandroid backup path now will be named with current ROM id from build.prop (ro.modversion, then ro.romversion, then ro.build.display.id)
custom backup and restore job list: backup and restore freely any partition combo (include modem and efs)
backup/restore EFS in both tar + img formats, now with time incremented copies for both tar and .img
support flash modem.bin image files in addition to custom modem.img files, now support for multiple *.bin versions under dedicated folder
during custom restore, you can see the contents of the folder you want to restore from
delete custom or TWRP backups from recovery menu
full wipe before flashing new ROM: wipe user data + format /system and /preload. SD card content is not affected
full support for openrecovery script specifications include all backup and restore options
run openrecovery scripts in 2 modes: on start goomanager boot scripts + one touch menu to either directly open a default path or freely browse for scripts
define ors backup target volume from within Nandroid Settings menu
ors restore path supports stock clockworkmod path or TWRP path
poweroff, reboot to recovery and reboot to download/bootloader mode options
dual USB mount in recovery support and mount external sd over usb for /data/media devices
adb root in recovery: just wait about a minute to activate
detailed build info in About menu
GT-N5100:
Odin flashable package = if you are on stock recovery you need this: RECOVERY_GT-N5100-CivZ_rev1.1-PhilZ_5-ODIN.tar
cwm flashable package = Only works when you are on a custom recovery: RECOVERY_GT-N5100-CivZ_rev1.1-PhilZ_5.zip = Recovery file manager included
GT-N5110:
Odin flashable package = if you are on stock recovery you need this: RECOVERY_GT-N5110-CivZ_rev1.1-PhilZ_5-ODIN.tar
cwm flashable package = Only works when you are on a custom recovery: RECOVERY_GT-N5110-CivZ_rev1.1-PhilZ_5.zip = Recovery file manager included
GT-N5120:
Odin flashable package = if you are on stock recovery you need this: RECOVERY_GT-N5120-CivZ_rev1.1-PhilZ_5-ODIN.tar
cwm flashable package = Only works when you are on a custom recovery: RECOVERY_GT-N5120-CivZ_rev1.1-PhilZ_5.zip = Recovery file manager included
CHANGELOG:
23/Okt/2013:
First touch release of this recovery ported from the Philz recovery.
24/Okt/2013: CivZ REV1.1 of the Philz touch 5 recovery
EFS backup changed to original : Backup to external or internal = It is stored as a hidden file in clockworkmod/backup.
Touch driver adjusted and rebuild the kernel for it.
Activated ntfs support in recovery kernel.
With the CWM install package the recovery filemanager is installed.
Click to expand...
Click to collapse

Maybe i forgot to tell you, until I push my sources to phil, try compiling with custom touch driver sources to get the touch interface working.

cm 10.1
plz port for us cm 10!N5100 :crying:

Is it possible to get a signed zip? I have a recovery installed, just not the CWM or TWRP (it is the stock one).

Flash this with odin, I doubt the touch will work properly. Even though, N5110 users try it.

emwno said:
Flash this with odin, I doubt the touch will work properly. Even though, N5110 users try it.
Click to expand...
Click to collapse
Touch and efs backup not working.

civato said:
Touch and efs backup not working.
Click to expand...
Click to collapse
Looks like ill wait till mine arrives and then debug alot. A question, does it not work at all? Or does it register them wrong?
EDIT: talking about the touch input

emwno said:
Looks like ill wait till mine arrives and then debug alot. A question, does it not work at all? Or does it register them wrong?
Click to expand...
Click to collapse
It register them wrong, if you look at it like a portrait mode recovery the buttons are situated for that kind of recovery.
example: pressing top right corner (landscape mode) is pressing the return button, so it is way off. But it is this way in all touch recovery's for now on this tablet. Not a real problem not having touch, for me the efs is more important.
It is the same with the aroma installer touch driver, it is way off so you need to use the hardware buttons.

civato said:
It register them wrong, if you look at it like a portrait mode recovery the buttons are situated for that kind of recovery.
example: pressing top right corner (landscape mode) is pressing the return button, so it is way off. But it is this way in all touch recovery's for now on this tablet. Not a real problem not having touch, for me the efs is more important.
It is the same with the aroma installer touch driver, it is way off so you need to use the hardware buttons.
Click to expand...
Click to collapse
This device is more of a hybrid, half of the time its acting like a tablet and other times like a phone. Ill build one for portrait now and upload in a few
---------- Update ----------
Test2. flash with odin.
1. If recovery is portrait, touch issues should be resolved
2. EFS backup should now be fixed

emwno said:
This device is more of a hybrid, half of the time its acting like a tablet and other times like a phone. Ill build one for portrait now and upload in a few
---------- Update ----------
Test2. flash with odin.
1. If recovery is portrait, touch issues should be resolved
2. EFS backup should now be fixed
Click to expand...
Click to collapse
Still in landscape so touch is still off and efs backup still doesn't work.
It looks like it makes a backup but it don't.

civato said:
Still in landscape so touch is still off and efs backup still doesn't work.
It looks like it makes a backup but it don't.
Click to expand...
Click to collapse
think ill just use ameer's script to backup everything via recovery. and about recovery being portrait, i have one more thing i can try, ill do that tomorrow. for now ill just update kernels to .79

bump?
anyone knows if there's a chance for working PhilZ in foreseeable future?

can I use this recovery instead of CWM or TWRP, flashing your ROM - CivZ-FLEXBEAM-4.2.2-Rev1.5?
on OP instruction on your ROM, it says "Install with CWM or TWRP", I am not sure if PhilZ touch works too?

I don't see why not since it is based on CWM advanced edition.

Full touch version released
New release
Download in OP :
* * * * * * * * * * * * * * * * * * * * * * * * *
PhilZ Touch 5 Recovery
CWM Advanced Edition 6.x
* * * * * * * * * * * * * * * * * * * * * * * * *
​
Features of this ported recovery:
RECOVERY IS IN TABLET MODE
Touch recovery based on cwm 6.0...
zImage compiled by civato based on Samsung Update2 with Exfat support
Touch driver fixed for aroma thanks to nickdollahz
Backup / restore
Custom backup / restore
EFS backup / restore: backup is automatic stored as a efs.img on the internal_SD and external_SD (clockworkmod/efsbackup) This was modded by me as the original didn't work, this is based on the emwo script.
Change theme layout and touch settings
TWRP and CWM restore support
Format data/media = internal_SD will be empty.
Power menu
etc..............................

REV1.1 released
24/Okt/2013: CivZ REV1.1 of the Philz touch 5 recovery
EFS backup changed to original : Backup to external or internal = It is stored as a hidden file in clockworkmod/backup.
Touch driver adjusted and rebuild the kernel for it.
Activated ntfs support in recovery kernel.
With the CWM install package the recovery filemanager is installed.
Download in OP

Thanks civato.. In the other forums they just tell us how worthless CWM is. Here you guys fix it and make it better...Worked like a charm.. k9time
Sent from my GT-N5100 using XDA Premium 4 mobile app

Hi would this work on stock 4.1.2? Just rooted device but has no recovery ..
Sent from my GT-N5110 using xda premium

Valholy said:
Hi would this work on stock 4.1.2? Just rooted device but has no recovery ..
Sent from my GT-N5110 using xda premium
Click to expand...
Click to collapse
Yes it works with stock 4.1.2 but if you're on stock recovery, then you have to flash this with odin because you can't flash a custom recovery with a stock recovery. If you already have a custom recovery, then you can flash this with that, but I assume you're still on stock recovery. So:
1. You need a computer with odin and proper samsung drivers installed
2. Download the right GT-N5110 .tar file from this thread
3. Go to download mode and open odin
4. Make sure you have F.Reset time and Auto-reboot checked
5. Click on PDA and choose the .tar file and then flash it
And you're done
Sent from my GT-N5110 using XDA Premium 4 mobile app

Thanks a lot will try it out
Sent from my GT-N5110 using xda premium

[ROM] [PORT][CM7] Androidiani ROM

Hi XDA,today I want present you the port "Androidiani ROM" or the ROM of http://www.androidiani.com/forum/ This ROM was made from the Androidiani Dev-team whose
members are :
- theflanker
- dema121
- matt96g
I also want to thank for the support and for small changes:
- xDaZe
- erghetto
- erok
- SparkZ
- AgoDrago
- OrlaTunzTunz
- GalaxyAceICS
- Cleofra
- djpredator17
- mik90
DOWNLOAD:
Rom http://www.mediafire.com/download/x...ni-Experience-FINAL-tassve-by-linckandrea.zip
CWM http://forum.xda-developers.com/attachment.php?attachmentid=2584629&d=1392648455
Kernel http://www.mediafire.com/download/v5q74y90hg348iu/kernel_CM7_v4.0_tassve.zip
HOW TO INSTALL
1.(RECOMMENDED) Be on a stock ROM, installation will be cleaner
2.Download THIS EXT4 tool, the Kernel and the Rom on your device.
3.Flash on Samsung recovery (or your recovery if you are not on stock), my temp. CWM.
4.When you are on the Temp. CWM, flash the EXT4 Formatter tool, so whole system will be converted to EXT4. (Stock filesystem is RFS)
5.After the installation, flash my kernel you have downloaded before.
6.When the Kernel is installed, go, on the CWM, to advanced --> reboot recovery (this will reboot the device, and turn it on on the new CWM of kernel)
7.Wipe data, cache and dalvik
8(IMPORTANT) Go to mounts and storage, and make sure system is mounted (will show unmounted) mount it 2 times!
9.Go to install zip from SD Card, choose zip from SD card and install your Androidiani-Experience-FINAL. (MAKE SURE installation last more than 5 seconds, if is less than 5 secodns, your system is unmounted! repeate step 8).
10.After installation, go back and reboot system, if you made it good, ROM boots, so no problem on it.
CHANGELOG
Holo laucher
Androidiani app system
VoiceSearchk @. apk
AudioFixk @. apk
GPS fix
Adrenaline Engine 4.2
AdrenalineBoost
30 steps volume
Modded host file
Framework deodexato
Tweaks in various build.prop
Beats audio
Increased sensitivity touchscreen
Settings in ICS style
Gplay latest version
Sounds sgs3
Flashplayer
Theme GingerIX (hybrid Gingerbread / IceCreamSandwich)
browser modded
Background default custom
Theme ICS ThemeChooser
BUGS
You tell me
SCREENSHOTS
http://imageshack.us/a/img442/6941/screenshot1357833499907.png
http://imageshack.us/a/img547/7568/screenshot1357833506442.png
http://imageshack.us/a/img14/8923/screenshot1357833542503.png
http://imageshack.us/a/img838/3573/screenshot1357833617869.png
http://imageshack.us/a/img24/6026/screenshot1357833878442.png
http://imageshack.us/a/img145/3570/splashscreen.png
credits:
- theflanker
- dema121
- matt96g
- xDaZe
- erghetto
- erok
- SparkZ
- AgoDrago
- OrlaTunzTunz
- GalaxyAceICS
- Cleofra
- djpredator17
- mik90
- BroadcomCM for device tree, vendor files...

ADD-ON
Patch:
roboto font https://drive.google.com/uc?export=download&confirm=no_antivirus&id=0B5spFnYHF7xlNFdTS2xxRnU3TW8
add live wallpaper https://drive.google.com/uc?export=download&confirm=no_antivirus&id=0B5spFnYHF7xlTG9NYVFkRkdHMms
for install on CWM mount system and install
Wallpapers:
Androidiani Wallpapers by dema121 https://docs.google.com/folder/d/0B5spFnYHF7xlVGJPd0RmMEJBT3c/edit
Wallpapers by GalaxyAceICS http://www.mediafire.com/?bk9crkltbnyuobr

[CWM] {Advanced Edition} PhilZ Touch Recovery 6.41.5 [For Micromax A177 Canvas Juice]

Hellooo friends.....
Finally After Lot of Struggle And Hard work , I succussfully Ported PhilZ Touch Recovery To MMX A177...!!
* * * * * * * * * * * * * * * * * * * * * * * * *
PhilZ Touch 6 Recovery
CWM Advanced Edition 6.x
* * * * * * * * * * * * * * * * * * * * * * * * *​
Features:-
* Touch Interface
Click to expand...
Click to collapse
- toggle between 4 touch modes: FULL TOUCH, DOUBLE TAP to validate and SEMI TOUCH (scroll but no touch validation) and NO TOUCH to only use hardware keys
- written from scratch full touch code
- safe full touch : no wrongly validations while scrolling
- when you set full touch mode, it defaults to optimized settings for menu height, scroll sensitivity and touch accuracy (you still can alter them manually later)
- adjust scroll sensitivity in a huge palette
- adjust menu height in a huge palette
- adjust touch accuracy
- 30 color settings for each of the 8 GUI parts + 5 alpha transparency settings
- user custom background png can be selected in addition to 30 solid colors option
- show / hide background icon
- show / hide bottom virtual buttons
- show/hide + set color and transparency for menu line separators to match solid color themes, like Black...
- set number of bottom log rows to show
- Friendly Log View and pause on logs: no more miss logs during zip installs
- auto dim screen after user configurable delay
- auto turn off screen after user configurable delay
- adjust brightness and turn off screen with a gesture action
- show/hide clock and remaining battery %, even during nandroid operations
- clock and battery stats now effectively refresh every 30 seconds and during nandroid operations
- toggle vibrator on/off on touch
- toggle key repeat for volume up/down scrolling when maintained pressed
- key repeat also enabled for virtual buttons
- set time zone + 30mn offset + DST: correct time can now be set for nandroid backup path and clock
- time setting is now applied to all recovery session, including timestamp of created/modified files (v4.92.3+)
- capture recovery screen shots with a gesture action
- one file to save all settings
- backup and restore settings file
- reset to default settings option
- prompt to restore your settings from a backup when they are wiped by a new ROM install
- option to auto restore your settings from a backup without a prompt
- all toggles are applied live, without restart of recovery (except reset of stock CWM background image)
- toggle menu options are automatically right aligned and menu text left aligned based on device display size
- configurable gesture actions: double tap, slide right/left, long press/lift, long press/move, can be associated with any of: show log, change brightness, blank screen, capture screen shot, launch Aroma File Manager
Note: after scroll, first touch will select only. After one sec of scrolling or on second touch, it will validate immeadiately. This is by design and not a bug. It is there to limit erroneous validation while scrolling
Click to expand...
Click to collapse
Click to expand...
Click to collapse
First to introduce true JB 4.2 migration: toggle between /data/media and /data/media/0
browse phone with root access using full GUI in Aroma File Manager
terminal access from recovery with root access through Aroma File Manager
Multi Zip Install menu: check multiple zip files to install in a row
Custom Install Zip Mode: set a default folder to start with + browse backward up to the root
exFAT + ext4 support in recovery for external sd
TWRP backup and restore support, include full md5 sum support (single and multivolume, compressed and non compressed formats)
Advanced statistics during backup operations shown in color: total backup size, backup size progress, backup time, compression ratio...
support .android_secure backup/restore from external storage and exfat partitions
optional reboot after custom backups/restores
sd-ext support (ext4)
nandroid backups support /preload in backup and restore jobs (custom and stock modes)
nandroid backups support /misc in backup and restore jobs (custom mode)
set special nandroid settings: time zone, toggle md5 check for lightning fast backup and restore, toggle /preload backup and restore,enable nandroid compression using pigz (multi-cpu gzip compression) and choose ors backup target volume
you can cancel any nandroid operation with back button
create custom_rom.zipfrom current ROM or from a pre-existing nandroid backup (based on boot, /system and optionally /preload)
nandroid backup path now will be named with current ROM id from build.prop (ro.modversion, then ro.romversion, then ro.build.display.id)
custom backup and restore job list: backup and restore freely any partition combo (include modem and efs)
backup/restore EFS in both tar + img formats, now with time incremented copies for both tar and .img
support flash modem.bin image files in addition to custom modem.img files, now support for multiple *.bin versions under dedicated folder
during custom restore, you can see the contents of the folder you want to restore from
delete custom or TWRP backups from recovery menu
full wipe before flashing new ROM: wipe user data + format /system and /preload. SD card content is not affected
full support for openrecovery script specifications include all backup and restore options
run openrecovery scripts in 2 modes: on start goomanager boot scripts + one touch menu to either directly open a default path or freely browse for scripts
define ors backup target volume from within Nandroid Settings menu
ors restore path supports stock clockworkmod path or TWRP path
poweroff, reboot to recovery and reboot to download/bootloader mode options
dual USB mount in recovery support and mount external sd over usb for /data/media devices
adb root in recovery: just wait about a minute to activate
detailed build info in About menu
Click to expand...
Click to collapse
Screenshots :-
{
"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"
}
Click to expand...
Click to collapse
GUI Preferences: all is applied live (no reboot). Up to 14 menu height settings, scroll sensitivity, touch accuracy...
Click to expand...
Click to collapse
Flash multiple zip files in a raw..
Aroma File Manager + Terminal Emulator: launch with a gesture action (double tap is default)
Click to expand...
Click to collapse
Backup and Restore any partition in a complete freedom, include modem (.img + .bin) and efs (.img + .tar)
Custom backups can also be restored by original CWM Advanced Restore Menu
TWRP Backup and Restore Support + md5 + single/multivolume format
Support multi-cpu compression, md5 check toggle and custom .android_secure path
Choose ors backup volume target
Click to expand...
Click to collapse
Change background image with a custom png (of your device resolution), a solid color (27 presets) or revert to original cwm image
Click to expand...
Click to collapse
User configurable touch gestures (feel free to request for new actions)
Setup your time-zone + 30mn offset, super wipe option to install a new ROM
Click to expand...
Click to collapse
Full Wipe to Install a new ROM (sdcard is preserved)
Free Browse Mode to install zip files: select a default folder to start with and browse up to the root
Click to expand...
Click to collapse
Download:-
PhilZ Touch Recovery from Here
Click to expand...
Click to collapse
Installation Procedure : -
Requirement :-
1) Rooted Device (Root Method)
2) Mobile Uncles tool (Get it from Play Market)
Click to expand...
Click to collapse
Procedure :-
1) After Rooting your device and installing Mobile Uncle tools, download the "PhilZ Recovery image" From Above .
2) Rename it to "recovery.img"..
3) Place it in the root of your SD card .
4) Open Mobile Uncle tools and choose the "Recovery Update" option.
5) Choose the recovery image you placed in the SD card and install it.
6) All Done,You have flashed PhilZ Recovery .
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Credits :-
>> PhilZ (Original Dev Of PhilZ recovery)
>> Yuweng ( For Making Automated MTK Tools )
>> hanuma ( Huge Thnx To Him For Helping me Alot)
>> Dhinesh Kumar (For Helping me)
>> At Last Me (Monty Kumar) Porter Of "PhilZ recovery"
Click to expand...
Click to collapse
:victoryress Thanks Button If u Like My Hard Work :victory:​

recovery
grea monty finally you ported this but you ported this via linux or windows?

Using windows ..
Sent from my Micromax A177 using XDA Premium 4 mobile app

EndLess said:
Using windows ..
Sent from my Micromax A177 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
thanks bro at first mobile uncle tools did not work and it would reboot to stock recovery then I installed the latest version of mobile uncle tools and it worked perfectly,its good to have modders like you around pls bring some more good stuff for our phone.

Bro please give me an easy way to deodex my phone the whole framework please give me an easy way is there a script or any procedure pls give link for the apps or exe files I need.

Chris s5830i said:
Bro please give me an easy way to deodex my phone the whole framework please give me an easy way is there a script or any procedure pls give link for the apps or exe files I need.
Click to expand...
Click to collapse
For doing This u have to look here http://forum.xda-developers.com/showthread.php?t=2431204
press thanx button if i helped u :victory:

YOU CANNOT USE THESE SHORTST.E or any other link. Against XDA Rules.! Take link down

Well Mr Endless i flashed it but i had CWM recovery installed and when i flashed it and loaded recovery mode... I got the same recovery back.. Why so???????????????????
Sent from my Micromax A177 using xda app-developers app

AlphaSoft said:
Well Mr Endless i flashed it but i had CWM recovery installed and when i flashed it and loaded recovery mode... I got the same recovery back.. Why so???????????????????
Sent from my Micromax A177 using xda app-developers app
Click to expand...
Click to collapse
Bor.... first of all plzz Follow the procedure and try again there is no problm like u said if u follow this procedure given above i sepratly mention all the procedure here . give a look to it carefully..
1) After Rooting your device and installing Mobile Uncle tools, download the "PhilZ Recovery image" From Above .
2) Rename it to "recovery.img"..
3) Place it in the root of your SD card .
4) Open Mobile Uncle tools and choose the "Recovery Update" option.
5) Choose the recovery image you placed in the SD card and install it.
6) All Done,You have flashed PhilZ Recovery . :good:

EndLess said:
Bor.... first of all plzz Follow the procedure and try again there is no problm like u said if u follow this procedure given above i sepratly mention all the procedure here . give a look to it carefully..
1) After Rooting your device and installing Mobile Uncle tools, download the "PhilZ Recovery image" From Above .
2) Rename it to "recovery.img"..
3) Place it in the root of your SD card .
4) Open Mobile Uncle tools and choose the "Recovery Update" option.
5) Choose the recovery image you placed in the SD card and install it.
6) All Done,You have flashed PhilZ Recovery . :good:
Click to expand...
Click to collapse
No i followed all these steps but I get the same recovery again i.e CWM .......
---------- Post added at 12:17 PM ---------- Previous post was at 12:14 PM ----------
EndLess said:
Bor.... first of all plzz Follow the procedure and try again there is no problm like u said if u follow this procedure given above i sepratly mention all the procedure here . give a look to it carefully..
1) After Rooting your device and installing Mobile Uncle tools, download the "PhilZ Recovery image" From Above .
2) Rename it to "recovery.img"..
3) Place it in the root of your SD card .
4) Open Mobile Uncle tools and choose the "Recovery Update" option.
5) Choose the recovery image you placed in the SD card and install it.
6) All Done,You have flashed PhilZ Recovery . :good:
Click to expand...
Click to collapse
And tell me has it any special advantage over CWM recovery????:what::what:

AlphaSoft said:
No i followed all these steps but I get the same recovery again i.e CWM .......
---------- Post added at 12:17 PM ---------- Previous post was at 12:14 PM ----------
And tell me has it any special advantage over CWM recovery????:what::what:
Click to expand...
Click to collapse
Yes u will get additional features in this recvry u can saw features section for more info...

AlphaSoft said:
No i followed all these steps but I get the same recovery again i.e CWM .......
---------- Post added at 12:17 PM ---------- Previous post was at 12:14 PM ----------
And tell me has it any special advantage over CWM recovery????:what::what:
Click to expand...
Click to collapse
Read this thread before asking any question bro .... here is everythng explained . see above there is deatailed explanation of its feature .

Would like some help asap. So i installed the Philz recovery. Took a nandroid backup. And then choose the option clean to install a new Rom. Cleaned dalai cache. The man flashed the new Rom. And then a bootloop occurred with a new Rom. This is quite common to me so tried different combinations to access the recovery. And think I found it, it is volume up and power button. But when I click them instead of going to the recovery unfortunately it goes to bootlogo till a press these keys I notice the bootloop occurs otherwise it just opens and shows the bootlogo. Any help? I have the nandroid backup in the SD card. But since am not able to access the recovery am not able to do anything as of now. So what should i do? Push through add? Would be happy if you could help me.

[RECOVERY][OFFICIAL][SAGIT][V3.2.1-028-Beta] Red Wolf Recovery Project

{
"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"
}
Code:
/*
* Your warranty is now void.
*
* We're not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Red Wolf Recovery is custom recovery based on TWRP source code, however some things are working here slightly different then you might expected. The main objective of this project is to provide stable recovery with features which you have never seen before in a recovery and which have not been accepted for adding to the official source code of TWRP. This recovery is also first recovery on the world with password protection.​
Based on TWRP version: 3.2.1
For devices: Sagit, Mido, Land, Kenzo & Kate
Authors build: dadi11
Kernel: https://github.com/RedWolfRecovery/rw_device
Developers: ATG Droid, dadi11 & Devil7DK
Thanks: z31s1g (for the base of his theme), Ray Li (For his useful advice in the beginnings), osm0sis (for his image scripts), dadi11 (for his awesome kernel & mido builds) etc.
Features:
Code:
[B]Translated to EN, PL, zh_cn, & CZ [/B]
- Password protection
- Flashlight
- MIUI Incremental OTA Support
- Built-in latest Magisk, SuperSU & AromaFM
- Support two screenshot GUI actions - Power+VolDown to save screenshot in to the internal storage &
Power+VolUp to save screenshot in to the external storage (Will be automatically saved in to the internal in case
that external storage doesn't exist).
- Support automatic reboot after the restore process
- Recovery can automatically modify some props in the ROM directly during the installation
- Some built-in scripts from community
- Tap to wake support
- Advanced deactivation of the stock recovery
- Automatic deactivation of the dm-verity & forced encryption directly during the installation of the ROM
- Recovery can notify you about the completed backup/restore/installation using the notification diode & vibration.
- Support "set on boot" settings.
*[B] Changes for security reasons [/B]*
- ADB isn't starting automatically at the start of the recovery. You have to activate it in recovery
- MTP isn't starting until user enter correct password
- Deactivated support of the custom themes
Some differences to the official version:
Code:
[B][COLOR="red"]- get out of here if you are pirating apps. this recovery is not for you[/COLOR][/B]
- always up-to-date with the latest TWRP changes
- compiled on omnirom-7.1 source
- fixed backup/restore of Firmware
- more languages
- other improvements from Features and Changelog lists
Changelog:
Code:
[B][U]RedWolf-V3.2_027[/U][/B]
- If screen is turned off then automatically detect AROMA Installer package and unblank screen before starting the update binary which is going to call AROMA GUI, so we won't be stuck at the black screen since AROMA engine require screen to be turned on.
- Added ability to change OTA Survival driver properties from the recovery GUI, allowing recovery to support "out of the box" almost all incremental OTA updates from different OEMs/custom ROMs out there (as long as they have correctly formatted metadata).
- Notify user about the current activity of the deactivation process - that's handled under the console
- Improved dumwolf driver
- Removed the vibration feedback from all GUI elements
- Automatically resize bootable partitions during nandroid backups
- Changed theme to black/white/red style based on @TBO material theme
- Data files aren't anymore saved on the storage partitions, which means that we're now able to survive even encrypted device.
- Some bug fixes and improvements...
[B][U]RedWolf-V3.2_026[/U][/B]
- This is just a quick bug fix release for MIUI users. So is highly recommend to update to this build if you are using MIUI.
[B][U]RedWolf-V3.2_025[/U][/B]
- Fixed crash of the recovery while running OTA_RES.. (So MIUI OTA is now working again)
- General bug fixes and improvements
- Fixed bug with MIUI Updater app showing error that installation failed after installation of full ROM
- Deactivation process is now called only when it's really needed
- Updated kernel
[B][U]RedWolf-V3.2_024[/U][/B]
- Fixed GUI color glitch while starting Aroma Installer update-binary
- Optimized pigz runtime process
- Updated recovery base to the AOSP 8.1.0 & TWRP 3.2.1
- Highly improved signature verification for Incremental packages so now we can be really sure if the package is compatible with the ROM.
- Introduced a file based backup/restore engine. Expect it to be improved with the next builds...
- Improved security related to the password protection
- Fixed loading of the AromaFM config file
- System survival process for Incremental packages is now set by default
- Code optimizations
- Removed the dumwolf process
- Added signature check for incremental OTA survival so we won't be unnecessarily creating a new one if it's signed under the same access key
- Magisk updated to the version 15.1
- Added Indonesian language
- Fixed issues with Chinese characters...
- Governor which is changed by the action in the recovery GUI is now automatically set for all cores instead of only four.
[B][U]RedWolf-V3.2_023[/U][/B]
- Updated recovery base to the TWRP version 3.2.0
- Fixed issue with recovery sometimes showing "NO-OS" page even when OS is installed
- Merged: Fstab V2, minui updates, Keymaster 3.0 support, ADB updates, fixes related to the compiling errors...
- Added patch against the pirating applications
[B][U]RedWolf-V3.1_022[/U][/B]
- Small improvements in the installation process
- Recovery will now automatically warn the user in case that user selected to install the zip which contain a bootloader
- You can now wipe installed substratum overlays directly from the "advanced wipe" section
[B][U]RedWolf-V3.1_021[/U][/B]
- Automatically return install error if there is any issue with Incremental OTA Survival
- Added option to also backup system partition for Incremental OTA Survival (It's not always needed, but just in case it's better to backup it.)
- Added support for the compatibility verification of the Incremental Package
- Rebuilded & improved installation process
- Fixed starting process not being disabled correctly in case that we are running ORS
- Translation update
- Added support for devices with 2GB RAM or less... (Check installation process of this build for more info)
- Added checkbox for activation/deactivation of the boot check (Disable only if you really need to).
- Fixed booting problems on some custom ROMs which don't have gzip compressed ramdisk
- Removed bookmark feature
- Added ability to unzip files using the stock filemanager.
- Added search selection for the stock filemanager.
- Fixed 'No OS' on system image restore after wipe
- Merged some latest commits from TWRP gerrit
[B][U]RedWolf-V3.1_020[/U][/B]
- Fixed flashing of the images in the previous 018 build
- Added back support for unpacking of the LZ4 compressed ramdisk
- Fixed bookmark feature
[B][U]RedWolf-V3.1_019[/U][/B]
- Disable TWRP installation directly during the first boot
- Default time zone was set to CEST
- Use military time as default time.
- Support of the custom themes was completely removed from the installation process
- Few fixes & improvements in the strings.
- Default value of the RedWolf specific vibrations was slightly increased
- Improved saving/loading of the AromaFM config file.
- User can now select if recovery should disable stock recovery when system is mounted as read-only.
- Default color of the recovery was set to red.
- Fixed automatic reboot if the installation process was unsuccessful
- Center time in the statusbar as default
- Show CPU temp in statusbar as default
- Added "Red Wolf No-OS search engine". Enable this if you are sometimes getting No-OS installed error even when OS is installed.
- Added back support for extra languages
- Added support for Talian language
- Updated Chinese (simplified) translation of the AromaFM by LiuNian and Pzqqt
- Fixed displaying of the extra languages
- Improved mounting of the partitions during the applying of set on boot values
- Fixes with "stuck at unmounting"
- Highly improved speed of the recovery while setting up a new password, changing accent color or setting a new splash screen
- Magisk updated to the V14.3
- Recovery now won't allow the user to enter special characters while entering the password (Causing issues...)
- Few improvements with the Android Oreo installation
- Updated kernel
- Added ability to select if recovery should automatically disable forced encryption in the ROM
- Recovery will now automatically rename scripts in the system if the "Aggresive stock recovery deactivation" is enabled
- Added ability to select if recovery should automatically enable/disable USB Debugging in the ROM
- Removed some useless files to save the space
- Added support for saving the set on boot values also during the automatic reboot
- Redesigned flashlight icon
- Recovery now won't allow the user to enter the space in to the backup name
- Improved support of the last status checking of the MIUI ROM
- Recovery now won't show any button after the cancelled reboot action untill the sleep action won't be running anymore
- You can now select if recovery should also automaticaly reboot after the successfuly finished restore process
- Recovery will now hide the automatic backup feature if the system partition is mounted as read-only
- Updated recovery base to the AOSP 8.0.0
- Updated image drivers
- Added ability to select if recovery should automatically enable/disable "ro.adb.secure" property in the ROM
- Recovery will now automatically disable starting of the flash_recovery service if the "Aggresive stock recovery deactivation" is enabled (this process is also compatible with the backup of the init.rc by Magisk or SuperSU).
- Added new section called "Special Actions" in to the advanced menu
- Updated & optimized flashlight drivers
- Added ability to select if recovery should automatically enable/disable "ro.secure" property in the ROM
- Added ability to select if recovery should automatically enable/disable "ro.allow.mock.location" property in the ROM
- Highly improved support of the Incremental Package installation, detection etc.
- Updated Chinese (simplified) translation of the recovery by LiuNian and Pzqqt
- Added support for the complete deactivation of the secure boot in the MIUI based ROMs
- ADB is now automatically starting as root
- Added support for the RedWolf update package
- Default theme of the AromaFM was changed to holo black with the sense icons and automount turned on
- SuperSU Updated to the 2.82 SR5
- Updated ramdisk cleaner & added support for more kernels (thanks to @MOVZX's kernel installation scripts...)
- Small fixes with the /WOLF folder in the PartitionManager
- Highly improved speed of the reboot
- 'Deactivation process' is now automatically called during the installation instead of the reboot
- Imroved deactivation of the leds after the installation / backup / restore process.
- Fixed bug with recovery showing on the governor page that the active governor is "Interactive" even when user selected performance/powersave mode.
- Removed some GUI messages while we are installing built-in zips.
- And many other things which i don't remember anymore...
[B][U]RedWolf-V3.1_018[/U][/B]
- Fixed bugs with MIUI OTA Support to make sure that it will work even with newest beta builds of the MIUI
- Updated Polish translation by Daviteusz
- Fixed bugs in the Polish strings & edited the scale of the Russian strings
- Recovery will be now more aggressive if the process of the stock recovery doesn't want to be disconnected (Sometimes happen on some MIUI ROMs).
- Added detection of the installed ROM
[B][U]RedWolf-V3.1_017[/U][/B]
- Magisk updated to the V13.6
- SuperSU updated to the 2.82 SR3
- Added ability to automatically flash SuperSU config before the SuperSU - https://forum.xda-developers.com/apps/supersu/2017-08-13-supersu-config-t3655754
- Deactivated hw keys
- Added some missing back buttons
- Attempted to fix encryption
- Attempted to fix MIUI OTA installation - needs testing
- Removed extra languages (were not displayed properly)
- Small update which fixed deactivation of the dm-verity & forced encryption. Now you really don't have to flash the lazyflasher everytime when you are installing the MIUI ROM.
[B][U]RedWolf-V3.1_016[/U][/B]
- Fixed feature "Backup wifi, bluetooth & hosts" not to work if the user wiped the data partition using the "factory reset".
- TWRP source code was updated to the Aug 15, 2017
- Fixed recovery remembering the wipe list after setting a new gui page.
- Improvements with the mounting of the partitions during the boot
- Fixed led drivers on mido
- Fixed ability to set custom backup folder name & ADB ID
[B][U]RedWolf-V3.1_015[/U][/B]
- Updated with the latest TWRP changes
- Added flashlight switch on mido
[B][U]RedWolf-V3.1_014[/U][/B]
- Fixed recovery not deactivating the dm-verity, forced encryption, & stock recovery if the OS was detected as not installed. This issue was often happening on some MIUI ROMs.
- Improvements with the OTA update system of the MIUI.
- Fixed wrong reboot for some users.
- Added support for automatic deactivation of the dm-verity, forced encryption & stock recovery after finishing the OpenRecoveryScript process.
- Fixed recovery not deactivating the dm-verity & forced encryption during the automatic reboot after the finished installation.
- Better explain the current situation if the OS was detected as not installed.
- osm0sis's scripts "unpackbootimg" & "mkbootimg" can now be easily called from the script or terminal
- Improved the speed of the reboot
- Updated the community script "Fingerprint scanner fix" by Magua. It's now working again!
- Added NTFS & exFAT support
- Added more languages and updated Polish RedWolf translation by @Daviteusz
- Added FGO patch - https://goo.gl/GBkhMN
[B][U]RedWolf-V3.1_013[/U][/B]
- Slightly improved deactivation of the stock recovery during reboot after the zip installation
- Added ability to flash boot logo in the recovery
- Fixed firmware restoring issues
[B][U]RedWolf-V3.1_012[/U][/B]
- added F2FS support for mido
- added Night Mode (kcal) support for mido
[B][U]RedWolf-V3.1_011[/U][/B]
- Updated Polish translation by @Daviteusz
- Added few missing strings from the latest TWRP source
[Red Wolf] Install TWRP and root your device without breaking incremental OTA's!
Downloads:
Latest build for Xiaomi Mi 6 (sagit)
RedWolf-027-sagit.img
Screenshots:
Warning:
Please remember that recovery with password protection isn't still a full protection for your phone. Red Wolf can only prevent unauthorized access to your device from recovery. But your device can be still reinstalled using fastboot or Miflash.
XDA:DevDB Information
Red Wolf Recovery Project for Xiaomi Mi 6, Tool/Utility for the Xiaomi Mi 6
Contributors
dadi11, ATG Droid, Devil7DK
Source Code: https://github.com/RedWolfRecovery
Version Information
Status: Testing
Created 2018-04-07
Last Updated 2018-04-07

Reserved
bugs: flashlight doesn't work, yet
https://t.me/joinchat/FZlpFECo9qt3MT5oRn-Bcg

Thanks Great Work

if you face issues with mounting Modem, redownload and flash the v27 image again

i was using your TWRP since kenzo, and mido. nice to see you here on sagit. does it support decryption on oreo? backup and restore works fine?

I flash the newest version, V3.2.1-027. After I enter system, I find the recovery is overwrite by system.
Steps:
1. flash recovery, Red Wolf V3.2.1-027.
2. Enter Recovery
3. Reboot to system
4. Reboot to recovery, the recovery is restored to original.
OS version: MIUI V9.2.3.0.OCAMIEK
P.S. I have renamed the file, /system/bin/install-recovery.sh, to /system/bin/install-recovery.sh.bak.
Does the under function work? or How to let it work? Thx.
"Automatic deactivation of the dm-verity & forced encryption directly during the installation of the ROM"

@dadi11
sorry, but it seems it doesn't work on MIUI 8.4.5 Global Dev Oreo
same problem as previous, can't read the /sdcard /data.
any further support?

zilan said:
i was using your TWRP since kenzo, and mido. nice to see you here on sagit. does it support decryption on oreo? backup and restore works fine?
Click to expand...
Click to collapse
yes it works fine
planetera said:
Does it support Oreo decryption and vendor support?
Can we flash treble images with it?
Click to expand...
Click to collapse
no you can't
dewa5227 said:
@dadi11
sorry, but it seems it doesn't work on MIUI 8.4.5 Global Dev Oreo
same problem as previous, can't read the /sdcard /data.
any further support?
Click to expand...
Click to collapse
please be more descriptive next time.
sagit doesn't have /sdcard. if /data can't be mounted you have to format (not wipe) /data

finally,it get stable,what a good thing

It does not decrypt the files.

ibrahimyuksel said:
It does not decrypt the files.
Click to expand...
Click to collapse
why would it? that's what the encryption is for. format /data to disable encryption and have a full access..

dadi11 said:
please be more descriptive next time.
sagit doesn't have /sdcard. if /data can't be mounted you have to format (not wipe) /data
Click to expand...
Click to collapse
i'm sorry, it seems that it must be formatted to be able to use it.
but another problem is, the recovery doesn't seems to stick after reboot to system. it goes back to the original stock recovery.
i didn't change the option from the default Aggresively replacing stock recovery, it still being checked. yet it goes back to stock recovery after reboot to system.

slitaz said:
finally,it get stable,what a good thing
Click to expand...
Click to collapse
flashlight is still not running,and i can't change some settings

dewa5227 said:
i'm sorry, it seems that it must be formatted to be able to use it.
but another problem is, the recovery doesn't seems to stick after reboot to system. it goes back to the original stock recovery.
i didn't change the option from the default Aggresively replacing stock recovery, it still being checked. yet it goes back to stock recovery after reboot to system.
Click to expand...
Click to collapse
same problem always goes back to stock recovery and when I try flash it with no-verity-opt-encrypt-5.1 my phone softbrick at miui logo after reboot

dewa5227 said:
i'm sorry, it seems that it must be formatted to be able to use it.
but another problem is, the recovery doesn't seems to stick after reboot to system. it goes back to the original stock recovery.
i didn't change the option from the default Aggresively replacing stock recovery, it still being checked. yet it goes back to stock recovery after reboot to system.
Click to expand...
Click to collapse
I solved it, first u need flash twrp then flash magisk or supersu > reboot system > instal apk like root explorer/mixplorer > open root files > find system/bin/install-recovery.sh then rename > system/bin/install-recovery.sh.bak (i used mixplorer) turn off ur phone > press volume up + power button > say goodbye for mi recovery

I am on latest developer global for Mi6. Do I have to wipe everything (my files, settings and apps?) to install this recovery? Can someone give me link to proper installation procedure? I don't want to lose my stuff on phone.

spiderpl said:
I am on latest developer global for Mi6. Do I have to wipe everything (my files, settings and apps?) to install this recovery? Can someone give me link to proper installation procedure? I don't want to lose my stuff on phone.
Click to expand...
Click to collapse
it's not a rom. search for the guide and you will find it for sure

planetera said:
Can you please update this twrp to 3.2.1.1 base? Because it does not support Oreo encryption :/
Click to expand...
Click to collapse
it does. and if it's not then wait for next build

This is what I did:
1. Booted to fastboot
2. fastboot flash recovery recovery.img
3. fastboot boot recovery.img
The red wolf recovery logo appeared and nothing else happened. I had to turn off the phone and when I went back into recovery it was default xiaomi recovery

spiderpl said:
This is what I did:
1. Booted to fastboot
2. fastboot flash recovery recovery.img
3. fastboot boot recovery.img
The red wolf recovery logo appeared and nothing else happened. I had to turn off the phone and when I went back into recovery it was default xiaomi recovery
Click to expand...
Click to collapse
do not use fastboot boot command