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

[DEV] CWM 6.0.4.8 Advanced Edition / PhilZ Touch Recovery 6.41.6

Main thread + Features + Dev support
http://forum.xda-developers.com/showthread.php?t=2201860
CWM 6.0.4.8 Advanced Edition / PhilZ Touch Recovery 6.41.6​
PhilZ Recovery is a CWM Advanced Edition that adds all the features you could ever miss in CWM.
It is a well proven recovery for many phones.
Please give your feedback, what works, and any bug you could encounter.
Read the features at the Main thread, and check if you are missing something.
To take a screen shot, just slide left!
And don't forget to read about powerful aroma file manager integration and double-tap shortcut (in FAQs).
How to install recovery?
From download link below, you'll get a 'recovery.img' file. Put that recovery.img file at root directory of your
sdcard. (means not in any folder)
Now, go to terminal emulator.
Give command:
Code:
su
You'll be asked to grant superuser permissions, grant it.
Now, give the following command:
Code:
flash_image recoveryonly /sdcard/recovery.img
Wait until it executes the command (4-5 seconds), it is installing the recovery.
Now, normally reboot to recovery and enjoy new recovery!
Download links
Latest version can be found here:
recovery.img (v6.41.6)
https://docs.google.com/uc?id=0B5c3gpyMBJusWi1XN09fZjkzUWM&export=download
aromafm_tass.zip (v1.91)
https://drive.google.com/uc?id=0B5c3gpyMBJusLTk5ZENsNWpudms&export=download
Click to expand...
Click to collapse
Special thanks to:
@Phil3759 : For this awesome open source recovery.
@chraso: For hosting and compatible flags.
AndroidARMv6 Team: For keeping this device alive.
Cyanogenmod Team: For making all these possible.
XDA:DevDB Information
PhilZ-Touch Recovery for Galaxy Mini, Tool/Utility for the Samsung Galaxy Mini
Contributors
Bhargav97, chraso, Phil3759
Version Information
Status: Stable
Current Stable Version: 6.40.1
Stable Release Date: 2014-05-04
Created 2014-05-07
Last Updated 2014-05-26

:FAQs:​
Q: Wanna know about Aroma File manager?
Visit the aroma file manager main thread for more info---> Aroma file manager main thread
Aroma file manager is a touch file manager which can be used while in recovery. It has options for copy, paste, delete,
change permissions and many others. Also, it has a Terminal inside. So, if you forgot to give correct permissions to any
file you can do that directly from recovery. This file manager has got many themes, font, icons, etc. options and it's UI
is fully customizable.
Q: How to start this File manager in Recovery?
Rename the downloaded file to 'aromafm.zip'.
Create a folder 'aromafm' inside 'Clockworkmod' folder on your sdcard.
Now, move that 'aromafm.zip' file to the 'aromafm' folder.
We're ready now, when you want to use it in recovery just double tap anywhere OR go to "philz Settings" and select
"Aroma File Manager" and it will start up.
If you also want to browse /data, /system and /sd-ext then mount them in the "mounts & storage" option in recovery.
Q: Problems with Aroma file manager startup?
After doble-tapping OR selecting 'Aroma file Manager' option under 'philz settings' if recovery gives error: 'aromafm.zip
not found at /clockworkmod/aromafm' then, wait for 4-5 seconds and again select 'Aroma file Manager', because it maybe
busy mounting sdcard.
If still doesn't work, you've made mistakes in steps mentioned in first post, please do again carefully.
Q: Does your phone every time reboots to recovery?
This happens very rare when you flash the recovery using any bad app or via any wrong (not proper) method. What you can do
is:
-If you've made a backup of your current ROM then just restore only it's "boot" and then select 'reboot to system'.
OR
-You don't have a backup? Then just flash the ROM which you are using currently again and wipe 'dalvik-cache'. Then reboot
to system. Booting process will take time.

NEW: Now you can enjoy the full version of the recovery! Thanks to @Phil3759 for uploading necessary commits for armv6. And, everything is expected to be bug-free. Please report the bug here if you find any.
GALAXY MINI GOES OFFICIAL NOW!!!!!!
You'll now find Galaxy Mini in the officially supported devices list at the Main thread.
SCREENSHOTS:
Main menu and PhilZ Settings
{
"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"
}
GUI Preferences: all is applied live (no reboot). Up to 14 menu height settings, scroll sensitivity, touch accuracy...
27 color settings + 5 alpha transparency levels for every GUI element
Change background image with a custom png (of your device resolution), a solid color (27 presets) or revert to original
cwm image
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
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
Flash multiple zip files in a raw
Aroma File Manager + Terminal Emulator: launch with a gesture action (double tap is default)
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

Hello and thank you for your work but it reboot to recovery again and it says that cant find aroma.zip in path.

alexanderq said:
Hello and thank you for your work but it reboot to recovery again and it says that cant find aroma.zip in path.
Click to expand...
Click to collapse
u hav to rename it to aromafm.zip
and yeah The Rom doesn't boot after installing this recovery

Faiyaz5yaz said:
u hav to rename it to aromafm.zip
and yeah The Rom doesn't boot after installing this recovery
Click to expand...
Click to collapse
You mean, you are always rebooting to recovery and not to your rom?
If so, it is a problem of your device configuration by your device developer because this happens also in Jenkins recovery. This is not a fault of my recovery.
Now, you can restore boot of a backup (if you made any) or you can install your current rom again and wipe dalvik cache and you'll be back normal.

But i have renamed the zip and it does not work.And i tried another ROM but it all ways reboots to recovery.

Can someone else confirm that it always reboot to recovery even after re-installing a rom?

Good work bro.:thumbup:
Sent from my GT-S5570 using xda premium

no
Bhargav97 said:
Can someone else confirm that it always reboot to recovery even after re-installing a rom?
Click to expand...
Click to collapse
I didn't restore back up..
I reflashed my previous cwm..
it booted normally

Bhargav97 said:
Can someone else confirm that it always reboot to recovery even after re-installing a rom?
Click to expand...
Click to collapse
I confirm it. I even flashed another ROM and it still reboots to recovery instead of system.
Aroma FM works, but there is something I noticed: If you tap internal sd or external sd, they are empty, you have to go to storage/sdcard00 to get to your sd card. Can you somehow link the external sd to the sd card?

Thanks everyone for reporting....
I'll try to fix this when I get time...
ast00,
Internal sd and External sd will be empty because they are kept there for devices having two different memories. There should be an option: sdcard directly on the root directory. Please see carefully.

Good news:
My friend @chraso gave me hint about the problem. There was a very small problem with tags, I'll be fixing and making updated recovery today/tomorrow. Will also update recovery sources.

First post updated with newer version, v6.22.1 (18.03.2014) and also made changes so that you can boot into ROM after installing it. Hope it's fixed.
Also added some FAQs.
Please post back the Results after using it.
Please give feedback on swipe-touch. Is right/left swipe working? And please post your opinion on the poll above, whether you like swipe touch or it just makes things complex or you just don't like it.

Bhargav97 said:
First post updated with newer version, v6.22.1 (18.03.2014) and also made changes so that you can boot into ROM after installing it. Hope it's fixed.
Also added some FAQs.
Please post back the Results after using it.
Please give feedback on swipe-touch. Is right/left swipe working? And please post your opinion on the poll above, whether you like swipe touch or it just makes things complex or you just don't like it.
Click to expand...
Click to collapse
flashed the latest zip
still not booting into the same rom..
didn't test new rom

Faiyaz5yaz said:
flashed the latest zip
still not booting into the same rom..
didn't test new rom
Click to expand...
Click to collapse
Which ROM are you installing?
Is the install successful?
What procedure you follow? This is important, please tell me. Do you use 'wipe to install a new rom'?

Does not work for me either, it reboots to recovery and i noticed that to make aroma work i must first install the zip from recovery and then it works OK .

not that
Bhargav97 said:
Which ROM are you installing?
Is the install successful?
What procedure you follow? This is important, please tell me. Do you use 'wipe to install a new rom'?
Click to expand...
Click to collapse
I mean I just changed the recovery didn't touch any roms.. after changing recovery , it keeps bootin to the recovery

Bro,
please read FAQs, this is a problem of your device sources. For solution, see FAQs.
After that, please give me broader report.

You di not ask the right question:
Does this work for someone , anyone please confirm.

{Advanced Edition} PhilZ Touch Recovery 6.57.9 [ Xolo A500S IPS & Xolo A500S Non IPS]

{Advanced Edition} PhilZ Touch Recovery 6.57.9 [ Xolo A500S IPS & Xolo A500S Non IPS]
* * * * * * * * * * * * * * * * * * * * * * * * *
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:-
Download PhilZ Touch Recovery from Here
Click to expand...
Click to collapse
Installation Procedure : -
Requirement :-
1) Rooted Device (Xolo A500S IPS or Xolo A500S Non IPS)
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 )
>> Yadav yadav (For testing on Xolo A500S IPS)
>> Ûpgrædäblè Dēép MÎtrå ( For testing on Xolo A500S Non IPS )
>> At Last Me EndLess (Monty Kumar) Porter Of "PhilZ recovery"
Click to expand...
Click to collapse
:victoryress Thanks Button If u Like My Hard Work :victory:​

Thanks for the PhilZ recovery , working fine in Xolo A500S IPS.

does not work on cherry mobile life (xolo a500l)
it deleted my recovery then made my phone boot loop once.

[Rom] [TCL S960/Alcatel - Idol x+] - Miui 8 Port - Unofficial (Updated 30/Jul/2016)

Hi All,
***MIUI 8 is now operational on our TCL_S960!
I managed to get it running on TCL S960 (IDOL X+),
Here's my work... (I am not a developer but I followed some instructions online and was able to make it at least for me...)
Probably there will be bugs - so let me know
I'll try to fix what I know...
If you want to use my work elsewhere, you must request in advance and make sure that credits goes to the correct people....
Supported Languages:
All languages that are supported by Xiaomi.EU roms.
Credits:
Xiaomi.eu - for the translations and guides.
Latest version Download links:
Android File Host: (WIP)...
30/Jul/2016 -
Older Versions (Miui8)
24/Jul/2016 (fixes to 14/7/2016) - https://www.androidfilehost.com/?fid=24651429356503158
14/Jul/2016 - https://www.androidfilehost.com/?fid=24591000424947416
7/7/2016 - https://www.androidfilehost.com/?fid=24591020540823614
30/6/2016 - https://www.androidfilehost.com/?fid=24591020540823614
Older Versions (MIUI7):
26/5/2016 - https://www.androidfilehost.com/?fid=24566454284190288
19/5/2016 - https://www.androidfilehost.com/?fid=24533103863143479
12/05/2016 - https://www.androidfilehost.com/?fid=24533103863139453
05/05/2016 - https://www.androidfilehost.com/?fid=24533103863137243
28/4/2016 - https://www.androidfilehost.com/?fid=4996500813288309006
14/4/2016 - https://www.androidfilehost.com/?fid=24499762636000772
7/4/2016 - https://www.androidfilehost.com/?fid=24459283995317117
31/3/2016 - https://www.androidfilehost.com/?fid=24459283995310311
17/3/2016 - https://www.androidfilehost.com/?fid=24459283995303903
XdaDevDB:
Installations:
Important:
Prior to any install make sure to backup your existing ROM. (TWRP backup?) if you wish to backup your SMS/Contacts there are a bunch of apps that can do it... (MobilePro is an example)
Backup your IMEI just in case... (Use MobileUncle or similar)
If you chose to install - your warranty is void.
I am not responsible for any damage that may be caused by this ROM.​
Did you make a backup? - Save your backup on a PC...
First time transition to MIUI8 requires re-partition of the phone to increase system size.
you will need a different recovery to finalise the process.
1. Copy the Repartition zip file to phone.
2. Copy the Philz recovery to your phone.
3. Install Philz recovery.
4. Reboot into recovery
5. Install Re-partition zip (It will take several minutes - it needs to format the partitions)
6. if format is not running - reboot to recovery and manually format the partitions (System, Data, Cache). - DO NOT FORMAT other partitions.
6.a. - check to see where the SDCARD data directory is mounted(data or data), if it is the data - change it back to data in the philz recovery, otherwise - upgrades will not work in TWRP.
7. using SP-Flash tools or another way, install the TWRP 2.8.7 recovery again.
8. Restore your backup.
9. Boot the phone.
10. Copy the MIUI8 install file to phone.
11. Click on the 3 dots
12. Chose select update file --> select your copied file.
13. Phone will Reboot and install.
If the above version does not work, you will need to use SP-Flash tools to install the EBR1, EBR2 files in the zip.
Then continue from step 6 (Format partitions)
if coming from another rom/ Fresh install
as ususal... - I recomend a total wipe, but it is not a must....
Wipe Cache, Dalvik, Data, System, custpack.
Install Rom from internal memory
reboot.​
Wait patiently - it will take 3-4 minutes on the 1st boot.
To update (existing Miui Rom):
Copy rom to SD Card
Open updater app.
Click on the 3 dots
Chose select update file --> select your copied file.
Reboot​
*** Make sure to disable Automated OTA... as it is based on Redmi Note 3G MTK, and I can't promise to keep this forever...
Recovery:
I used TWRP 2.8.7.0 for TCL S960
Other recoveries:
CWM - Link
TWRP 2.6.3 - Link
If you like my work feel free to buy me beer Donation link
Known Issues:
Default theme - some icons are missing - Use another theme icon set...
When making full wipe - unable to login to MiAccount - Install 6.1.28 version --> login, then update to latest.
TouchAssistant APK exceeds the space of System partition - I removed it, you can install it manually after the rom installs. - Link solved after repartition.
31/3/16 - Additional settings FC - Fixed.
12/05/2016 - Fixed wallpaper carousel FC when unlocking device
Some screenshots:
Miui8:
{
"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"
}
Miui7:
XDA:DevDB Information
TCL S960/Alcatel (IdolX+), ROM for the Android General
Contributors
hellfreezover, Xiaomi.eu
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Based On: MIUI
Version Information
Status: Beta
Current Beta Version: 26-05-2016
Beta Release Date: 2016-07-15
Created 2016-01-22
Last Updated 2016-07-30

Reserved
Changelog: (Latest Version)
24/7/2016 - still based on 6.7.14
Fixed Settings menus.
Enabled "Button mode"
Enabled additional settings to split the menu bar.
Fixed MIUI version to 8...
System seems to be running faster...
Older versions:
14/7/2016
System
Fix - Fingerprint issues (07-12)
Fix - Fingerprint scanner made the device freeze and reboot (07-12)
Lockscreen, Status Bar, Notification Bar
Optimization - Clickable arrow for Wi-Fi (07-12)
Optimization - A prompt about entering password and activating fingerprint after rebooting the device (07-13)
Fix - Customized carrier name isn't shown in Second space (07-12)
Home screen
Optimization - Landscape mode for Task manager (07-08)
Optimization - Task Manager stability (07-13)
Fix - Issues with wallpaper when switching to Second space (07-13)
Delete - Home screen Music widget (07-13)
Gallery
New - Delete directly from the screenshot preview page (07-12)
Optimization - Adjusted size for the button which creates new albums (07-12)
Optimization - "Show original" option appears only on cloud or optimized items (07-12)
Optimization - Double tap to zoom in, swipe up without entering sharing mode (07-12)
Optimization - When auto-rotate is off in Gallery, it won't influence the rest of the system (07-13)
Fix - Scrolling screenshot issues in Notes and Mail (07-12)
Fix - Couldn't go back to the original photo after making a screenshot or finishing editing/sharing it (07-12)
Fix - Couldn't pick up calls while making Scrolling screenshots (07-13)
Fix - Enter system app while editing a scrolling screenshot in the OOB flow (07-13)
Delete - Removed Edit option for GIF images (07-12)
Weather
Fix - Issues with curves in forecasts (07-13)
Optimization - Set C/F in settings (07-13)
7/7/2016
Highlights
New - Saved and available Wi-Fi networks appear first in the list (07-05)
New - After a permission is restricted, a clickable notification is sent to the user which can restore permissions (07-05)
Lock Screen, Status Bar, Notification Bar
New - Animation of WiFi connection (07-07)
Optimization - separate "Ringtone and Vibration" permission in Notification （07-07）
Fix - Switching notification bar style in landscape view issues (07-07)
Fix - In Second Space, enter Mi Home in lock Screen issue (07-07)
Desktop
Optimization - Restore app uninstallation sound effect (07-07)
Fix - Recent app tray, long press to enter wrong app info page issue (07-07)
Fix - Recent app tray, switching view mode issues (07-07)
Settings
New - Saved and available Wi-Fi networks appear first in the list (07-05)
Clock / Calculator
Optimization - "Shutdown alarm", "Set default alarm sound" moved up In Clock settings. (07-01).
30/6/2016 - Miui 8.
26/5/2016 -
Gallery
New - Deleting synced photos from internal storage without deleting from Mi Cloud (05-25)
Cleaner
Optimization - Accessibility support (05-24)
Fix - FC issues (05-24)
19/05/2016 -
System
Optimization - Background CPU processes caused performance issues (05-16)
Optimization - Delayed response for charger's notifications (05-19)
Fix - Wireless display caused reboots (05-19)
Fix - Read mode appeared more red than it should be (05-19)
Fix - Draining battery while using GPS in some cases (05-19)
Fix - Bluetooth turned on automatically with the device (05-19)
Settings
New - Introducing Shortcut menu. Check out the new MIUI 8 feature early. You can turn it on in Additional settings. (05-17)
TouchAssistant must be installed post rom.
Mi Cloud
New - Added "Back up now" feature for fast backups (05-19)
12/05/2016 -
System
Optimization - System storage UI (05-05)
Optimization - Background processes kept CPU busy and lead to performance issues (05-09)
Fix - Issues with adding fingerprint (05-05)
Fix - Problems with sound when listening to some songs using earphones (05-05)
Fix - Issues with video chats in some cases (05-05)
Fix - Sound disappeared in long phone conversations (05-05)
Fix - Fingerprint unlock didn't respond in some cases (05-05)
Backup
New - Optimizing transferring rate in File Transfer (05-09)
05/05/2016 -
System
Optimization - System storage UI (05-05)
Fix - Issues with adding fingerprint (05-05)
Fix - Problems with sound when listening to some songs using earphones (05-05)
Fix - Issues with video chats in some cases (05-05)
Fix - Sound disappeared in long phone conversations (05-05)
Fix - Fingerprint unlock didn't respond in some cases (05-05)
Security
New - Added on/off switch for App lock (05-03)
New - Customized settings for App lock (05-03)
28/4/2016 -
System
Optimisation - Improved speed and performance for devices which have been used for a long time (04-27)
Weather
New - New white design (04-27)
Cleaner
New - New design for Cleaner (04-27)
Gallery
New - Progress list for syncing with Mi Cloud (04-27)
Optimization - Added a prompt notifying about Mi Cloud trash bin when deleting photos for the first time (04-27)
Optimization - Improved sharpness for big photos (04-27)
Security
New - Fingerprint support for App lock in Redmi 3 Pro (04-27)
14/4/2016 -
System
Optimization - Improved algorithms for Silent and DND modes to be used at the same time. (04-13)
Fix - Storage leaks lead to performance problems (04-08)
Fix - Security Center FC in Hebrew Language
7/4/2016 -
Lockscreen, Status Bar, Notification Bar
Optimization - Improved order of switches in notification shade (04-06)
Fix - Music lock screen appeared when a game was running in the background (04-06)
Settings
Optimization - Improved algorithms for international roaming (04-06)
Mi Account
New - Added more items to personal info (04-06)
Cleaner
Optimization - Press and hold to add items to exceptions (04-06)
Optimization - Fixed problems with performance after clean-ups (04-06)
Mi Cloud
Fix - Couldn't find device or sign in to Mi Account due to wrong system time (04-06)
Fix - Fixed issues with incorrect time in backup lists (04-06)
Bug fixes by Xiaomi.
Fixed Additional settings FC.
31/3/2016 general bug fixes by Xiaomi.
24/3/2016
System
Optimization - Apps open faster, system animations work smoother (03-17)
Optimization - Increased image processing speed for image decryption database (03-22)
Fix - Problems with performance after switching from mobile data to Wi-Fi (03-18)
Backup
In some cases Mi Mover stopped working after the connection was established (03-18)
Clock / Calculator
New - Option for deleting an alarm automatically after it was used if it had been set to go off only once (03-23)

thank you
thank you for this awesome Rom. but the sound setting under audio force closes im on viper4android

Did you try sound settings without viper?
For me it works... but I did had to do a clean install...
Sent from my ASUS_Z00XS using XDA Free mobile app

Hi i just tried your rom bt i am stuck at mi login.. It says checking find device status and stays there only.... What to do now...?

santhosh5639 said:
Hi i just tried your rom bt i am stuck at mi login.. It says checking find device status and stays there only.... What to do now...?
Click to expand...
Click to collapse
Try using an older version like 6.1.28, then log in to miui, then update without full wipe.
I have reported this to miui, it is under discussion...
Sent from my ASUS_Z00XS using XDA Free mobile app

Updated OP with the link to 6.1.28 version
Sent from my ASUS_Z00XS using XDA Free mobile app

Updated OP with MIUI 8 for TCL.
Sent from my ASUS_Z00XS using XDA Free mobile app

Bricking my phone
Dear Hellfreezover,
I tried to install your ROM, but I bricked my phone.
(I installed ROM before several times, I never made mistake, but now I did it.)
When I used SP flashtool I selected "Firmware upgrade" option instead of "Download only" option (I never did it before) and I started to install TWRP recovery but I got error message.
Now I can not use my phone, but I know that I can be repairable just I need important files....
...these all files or just some of them:
- PRELOADER
-MBC
-EBR1
-UBOOT
-BOOTIMG
-RECOVERY
-SEC-RO
-LOGO
-EBR2
-CUSTPACK
-MOBILE_INFO
-ANDROID
-CACHE
-USRDATA
Now I get this error message when I try to update the recovery.
Could u send me these files? Or could you link me URL where I can find these files?
Sorry for disturbing, I shame on me, I did ROM install before without mistake, but now I screwed up...
Regards,
Peter (Hungary)

I am not at home now,
I have the files...
You can get searching TCL multi language rom 70 languages and download it through SP flash tools, then, repartition and finally the rest....
Sent from my ASUS_Z00XS using XDA Free mobile app

Olympos.81 said:
Dear Hellfreezover,
I tried to install your ROM, but I bricked my phone.
(I installed ROM before several times, I never made mistake, but now I did it.)
When I used SP flashtool I selected "Firmware upgrade" option instead of "Download only" option (I never did it before) and I started to install TWRP recovery but I got error message.
Now I can not use my phone, but I know that I can be repairable just I need important files....
...these all files or just some of them:
- PRELOADER
-MBC
-EBR1
-UBOOT
-BOOTIMG
-RECOVERY
-SEC-RO
-LOGO
-EBR2
-CUSTPACK
-MOBILE_INFO
-ANDROID
-CACHE
-USRDATA
Now I get this error message when I try to update the recovery.
Could u send me these files? Or could you link me URL where I can find these files?
Sorry for disturbing, I shame on me, I did ROM install before without mistake, but now I screwed up...
Regards,
Peter (Hungary)
Click to expand...
Click to collapse
Check your PM - I sent you a link with all files needed...

Updating problem
hellfreezover said:
Check your PM - I sent you a link with all files needed...
Click to expand...
Click to collapse
Thank you very much, I could unbrick my mobile! :good: :fingers-crossed: :highfive:
I tried to upgrade my ROM according to your instructions, but I could not do it.
What I did:
1. Unbrick my mobile with your files.
2. I copied your MIUI8 ROM, Repartition and Philz zip files to my mobile.
3. In SP Flash I downloaded Philz.zip what contains recovery.
4. I rebooted my mobile in recovery mode.
5. I installed the Repartition zip. (...but I think it was unnecessary, because I did it when I unbricked my mobile.)
6. I tried to reboot my mobile into reocvery mode, but it was not available (after repartition.)
7. I had to download your TWRP 2.8.7.0 recovery to my mobile via SP-Flash tool.
8. I tried to reboot, but same situation: this recovery also was not available.
9. I had to download other 2.6.3 or 2.7.0 TWRP recovery to my mobile.
10. I could reach recovery from that point.
11. I installed your MIUI 8 rom, and it was successful according to message.
12. In spite fo this the ROM can not start: "Idol X+" is appearing and go away and black screen is flashing without logo or sound.
What do I do in wrong way?
Otherway, before I unbricked my mobile and after also I tried to upgrade my ROM to your MIUI 8 version in different way.
Then I had different problem: when I did the uploading of your ROM into my exist differnet rom (like offical ROM, LeWa ROM or modded MIUI 5 rom) in recovery mode the installation was finally failed, unsuccessful: "/data" directory can not reachable/readable/writeable or somehting else.
(I have screenshot, I will share.)
Regards,
Peter

Olympos.81 said:
Thank you very much, I could unbrick my mobile! :good: :fingers-crossed: :highfive:
I tried to upgrade my ROM according to your instructions, but I could not do it.
What I did:
1. Unbrick my mobile with your files.
2. I copied your MIUI8 ROM, Repartition and Philz zip files to my mobile.
3. In SP Flash I downloaded Philz.zip what contains recovery.
4. I rebooted my mobile in recovery mode.
5. I installed the Repartition zip. (...but I think it was unnecessary, because I did it when I unbricked my mobile.)
6. I tried to reboot my mobile into reocvery mode, but it was not available (after repartition.)
7. I had to download your TWRP 2.8.7.0 recovery to my mobile via SP-Flash tool.
8. I tried to reboot, but same situation: this recovery also was not available.
9. I had to download other 2.6.3 or 2.7.0 TWRP recovery to my mobile.
10. I could reach recovery from that point.
11. I installed your MIUI 8 rom, and it was successful according to message.
12. In spite fo this the ROM can not start: "Idol X+" is appearing and go away and black screen is flashing without logo or sound.
What do I do in wrong way?
Otherway, before I unbricked my mobile and after also I tried to upgrade my ROM to your MIUI 8 version in different way.
Then I had different problem: when I did the uploading of your ROM into my exist differnet rom (like offical ROM, LeWa ROM or modded MIUI 5 rom) in recovery mode the installation was finally failed, unsuccessful: "/data" directory can not reachable/readable/writeable or somehting else.
(I have screenshot, I will share.)
Regards,
Peter
Click to expand...
Click to collapse
Hi,
I think what you missed is the format of system, data, cache - after the installation of re partition, in Philz recovery.
also - you need to verify that your SD-Data is mounted correctly (sometimes in Philz it adds a 0, and then you will not find files there...
You need to change the mount location before you reboot recovery.
Sorry I have no pictures for this, but it is in the menu...
if the above does not work
Try extracting EBR1, EBR2 from repartition file, install them with Philz recovery through SP-Flash tool.
reboot into recovery --> format data, system, cache - check again where SD is mounted...
Reboot recovery
Install rom - if works great if not:
Install TWRP 2.8.7
Place new ROM and install
let me know if this works for you.
The 1st install will take a few minutes until you will see something on the phone...

hellfreezover said:
Hi,
I think what you missed is the format of system, data, cache - after the installation of re partition, in Philz recovery.
also - you need to verify that your SD-Data is mounted correctly (sometimes in Philz it adds a 0, and then you will not find files there...
You need to change the mount location before you reboot recovery.
Sorry I have no pictures for this, but it is in the menu...
if the above does not work
Try extracting EBR1, EBR2 from repartition file, install them with Philz recovery through SP-Flash tool.
reboot into recovery --> format data, system, cache - check again where SD is mounted...
Reboot recovery
Install rom - if works great if not:
Install TWRP 2.8.7
Place new ROM and install
let me know if this works for you.
The 1st install will take a few minutes until you will see something on the phone...
Click to expand...
Click to collapse
Yes, u have right: during procedure, before I would install the MIUI 8 rom in TWRP 2.8.7.0 the SD-DATA is unmounted, internal storage is 0.
What can I do to reach it again?
---------- Post added at 05:49 PM ---------- Previous post was at 05:02 PM ----------
Olympos.81 said:
Yes, u have right: during procedure, before I would install the MIUI 8 rom in TWRP 2.8.7.0 the SD-DATA is unmounted, internal storage is 0.
What can I do to reach it again?
Click to expand...
Click to collapse
My problem is now:
/E: Unable to mount '/system'
/E: Unable to mount '/protect_s'
/E: Unable to mount '/protect_f'

Olympos.81 said:
Yes, u have right: during procedure, before I would install the MIUI 8 rom in TWRP 2.8.7.0 the SD-DATA is unmounted, internal storage is 0.
What can I do to reach it again?
---------- Post added at 05:49 PM ---------- Previous post was at 05:02 PM ----------
My problem is now:
/E: Unable to mount '/system'
/E: Unable to mount '/protect_s'
/E: Unable to mount '/protect_f'
Click to expand...
Click to collapse
you can change the mount location in Philz recovery...
6.a. - check to see where the SDCARD data directory is mounted(\data or \data\0), if it is the \data\0 - change it back to \data in the philz recovery, otherwise - upgrades will not work in TWRP.

I followed your instruction, please see my notes and check my pictures:
1. Copy the Repartition zip file to phone.
OK!
2. Copy the Philz recovery to your phone.
OK!
Please see it, I copied everything to my phone from Window 10, so these files copied into /data directory:
http://kepfeltoltes.hu/160717/factory_directory_www.kepfeltoltes.hu_.jpg
3. Install Philz recovery.
I did it from factory recovery:
http://kepfeltoltes.hu/160717/IMG_1596_www.kepfeltoltes.hu_.jpg
(You can not see the "Philz*.zip" file because of bad quality of picture, but belive me, it is.
4. Reboot into recovery
OK!
5. Install Re-partition zip (It will take several minutes - it needs to format the partitions)
I did it:
http://kepfeltoltes.hu/160717/IMG_1597_www.kepfeltoltes.hu_.jpg
6. if format is not running - reboot to recovery and manually format the partitions (System, Data, Cache). - DO NOT FORMAT other partitions.
6.a. - check to see where the SDCARD data directory is mounted(data or data), if it is the data - change it back to data in the philz recovery, otherwise - upgrades will not work in TWRP.
I did not need the format, because your Repartition.zip was installed successfully, and format was done by Repartition.zip as you requested:
Begin:
http://kepfeltoltes.hu/160717/IMG_1598_www.kepfeltoltes.hu_.jpg
End:
http://kepfeltoltes.hu/160717/IMG_1599_www.kepfeltoltes.hu_.jpg
7. using SP-Flash tools or another way, install the TWRP 2.8.7 recovery again.
Because of your Repartition procedure all files were deleted from /data directory so I had to upload TWRP 2.8.7.0 recovery from SP-Flash tool to mobile:
http://kepfeltoltes.hu/160717/Recovery_www.kepfeltoltes.hu_.jpg
8. Restore your backup.
(I do not know what is it...maybe I make a mistake here. I skiped this step.)
9. Boot the phone.
OK.
10. Copy the MIUI8 install file to phone.
Negative. There is no operation system, because Repartition.zip formatted /data and /system directory.
Furthermore, Internal storage is 0 from the Repartition.zip is completed.
http://kepfeltoltes.hu/160717/IMG_1603_www.kepfeltoltes.hu_.jpg
11. Click on the 3 dots
Negative.
12. Chose select update file --> select your copied file.
I had to use OTG-USB cable and chose the MIUI 8 rom in TWRP 2.8.7.0
But from now due to unavailable /data, /cache / etc - internalt storage is 0 - the installation however started, but failed.
Begin:
http://kepfeltoltes.hu/160717/IMG_1604_www.kepfeltoltes.hu_.jpg
End:
http://kepfeltoltes.hu/160717/IMG_1605_www.kepfeltoltes.hu_.jpg
13. Phone will Reboot and install.
Negative.
Where do I make mistake?

Olympos.81 said:
I followed your instruction, please see my notes and check my pictures:
1. Copy the Repartition zip file to phone.
OK!
2. Copy the Philz recovery to your phone.
OK!
Please see it, I copied everything to my phone from Window 10, so these files copied into /data directory:
http://kepfeltoltes.hu/160717/factory_directory_www.kepfeltoltes.hu_.jpg
3. Install Philz recovery.
I did it from factory recovery:
http://kepfeltoltes.hu/160717/IMG_1596_www.kepfeltoltes.hu_.jpg
(You can not see the "Philz*.zip" file because of bad quality of picture, but belive me, it is.
4. Reboot into recovery
OK!
5. Install Re-partition zip (It will take several minutes - it needs to format the partitions)
I did it:
http://kepfeltoltes.hu/160717/IMG_1597_www.kepfeltoltes.hu_.jpg
6. if format is not running - reboot to recovery and manually format the partitions (System, Data, Cache). - DO NOT FORMAT other partitions.
6.a. - check to see where the SDCARD data directory is mounted(data or data), if it is the data - change it back to data in the philz recovery, otherwise - upgrades will not work in TWRP.
I did not need the format, because your Repartition.zip was installed successfully, and format was done by Repartition.zip as you requested:
Begin:
http://kepfeltoltes.hu/160717/IMG_1598_www.kepfeltoltes.hu_.jpg
End:
http://kepfeltoltes.hu/160717/IMG_1599_www.kepfeltoltes.hu_.jpg
7. using SP-Flash tools or another way, install the TWRP 2.8.7 recovery again.
Because of your Repartition procedure all files were deleted from /data directory so I had to upload TWRP 2.8.7.0 recovery from SP-Flash tool to mobile:
http://kepfeltoltes.hu/160717/Recovery_www.kepfeltoltes.hu_.jpg
8. Restore your backup.
(I do not know what is it...maybe I make a mistake here. I skiped this step.)
9. Boot the phone.
OK.
10. Copy the MIUI8 install file to phone.
Negative. There is no operation system, because Repartition.zip formatted /data and /system directory.
Furthermore, Internal storage is 0 from the Repartition.zip is completed.
http://kepfeltoltes.hu/160717/IMG_1603_www.kepfeltoltes.hu_.jpg
11. Click on the 3 dots
Negative.
12. Chose select update file --> select your copied file.
I had to use OTG-USB cable and chose the MIUI 8 rom in TWRP 2.8.7.0
But from now due to unavailable /data, /cache / etc - internalt storage is 0 - the installation however started, but failed.
Begin:
http://kepfeltoltes.hu/160717/IMG_1604_www.kepfeltoltes.hu_.jpg
End:
http://kepfeltoltes.hu/160717/IMG_1605_www.kepfeltoltes.hu_.jpg
13. Phone will Reboot and install.
Negative.
Where do I make mistake?
Click to expand...
Click to collapse
First you missed your previous MIUI backup...
but that is not the issue...
I would recommend formatting the /system, /data, /cache partitions - even though that it shoes success...
Then reboot recovery (to PHILZ)
Make sure your SDCARD mount is without the "0"...
Try to flash ROM using ADB sideload, in PHILZ touch...
if it doesn't work, try installing with TWRP 2.6.3 recovery.
I shared what I did on my phone and it worked...
If all the above fails - try installing EBR1, EBR2 from SP-Flash tool, then Recovery (Philz), Format cache, system, data, then install rom through PHILZ or TWRP...

Somebody could install this rom as Hellfreezover described?
---------- Post added at 09:23 PM ---------- Previous post was at 09:05 PM ----------
hellfreezover said:
First you missed your previous MIUI backup...
but that is not the issue...
I would recommend formatting the /system, /data, /cache partitions - even though that it shoes success...
Then reboot recovery (to PHILZ)
Make sure your SDCARD mount is without the "0"...
Try to flash ROM using ADB sideload, in PHILZ touch...
if it doesn't work, try installing with TWRP 2.6.3 recovery.
I shared what I did on my phone and it worked...
If all the above fails - try installing EBR1, EBR2 from SP-Flash tool, then Recovery (Philz), Format cache, system, data, then install rom through PHILZ or TWRP...
Click to expand...
Click to collapse
Dear Hellfreezover!
I am sure, that you are advanced or professional developer and you have more experience about mobiles and ROMS, but now, I think what you have written in instructions is different as you have done it in real life.
...or someting is wrong with ROMs.
So...
I tried to follow your instruction several times and when I have reached that point that there were no error message at the beginning of installation of ROM, finally, it was also unsucessfull:
- begining: http://kepfeltoltes.hu/160717/IMG_1592_www.kepfeltoltes.hu_.jpg
- ending: http://kepfeltoltes.hu/160717/IMG_1593_www.kepfeltoltes.hu_.jpg
(See, there is no error message as before like "unmount /data" or somthing else...)

I am hardly a professional....
I used philz, and my files the way I described...
There may be some issues, I had miui Rom installed before...
And there is another guy that did the repartition process... using SP flash tools...
You can try maybe replacing the EBR1, EBR2 in the original Rom and choose firmware update....
Then install the twrp recovery and the Rom...

hellfreezover said:
I am hardly a professional....
I used philz, and my files the way I described...
There may be some issues, I had miui Rom installed before...
And there is another guy that did the repartition process... using SP flash tools...
You can try maybe replacing the EBR1, EBR2 in the original Rom and choose firmware update....
Then install the twrp recovery and the Rom...
Click to expand...
Click to collapse
Now I tried again and again, I followed again your every intsructions and I tried the following ROMs with TWRP 2.6.3.0:
- xiaomi.eu_multi_TCL_S960_6.7.14_v8-4.4 (latest) - Failed
- xiaomi.eu_multi_TCL_S960_6.6.30_v8-4.4 (previous) - Failed
- xiaomi.eu_multi_TCL_S960_6.3.10_v7-4.4 - Success!
Now, the MIUI 7 is running.
I am trying to upgrade to latest MIUI 7 and after to MIUI 8....
...but I am afraid: this will be again failed.