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

Search This thread

Phil3759

Inactive Recognized Developer
May 30, 2012
9,579
33,063
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
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
1aimg9539.jpg


1bimg9475.jpg



PhilZ Settings menu
2img9540.jpg



Backup / Restore EFS and kernel
3img9541.jpg



GUI Touch Settings
4img9542.jpg



Aroma File Manager
5img9547.jpg



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






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



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)

You are done



If it fails with black screen after successful flash:
read about it here: http://xdaforums.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



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 Gokhanmoral@Siyah *
  • 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


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


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


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.


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).



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:
  • Gokhanmoral@Siyah 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
 
Last edited:

Phil3759

Inactive Recognized Developer
May 30, 2012
9,579
33,063
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

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

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
 

Attachments

  • cwm-6.0.1.4-PhilZ-1.15-n7000.zip
    1.9 MB · Views: 9,250
  • cwm-6.0.1.4-PhilZ-1.61B-n7000-signed.zip
    1.9 MB · Views: 1,378
  • cwm-6.0.1.4-PhilZ-1.86B-n7000-signed.zip.zip
    1.9 MB · Views: 2,065
  • cwm-non-touch-6.0.1.5-n7000-signed.zip
    1.8 MB · Views: 1,963
  • philz-touch_3.00_n7000-signed.zip
    1.9 MB · Views: 4,203
Last edited:

microsd16

Senior Member
Feb 17, 2012
51
4
Hmmmm still i would like to try it with the risk involved in it

Sent from my GT-N7000 using xda premium
 
  • Like
Reactions: tatww

Phil3759

Inactive Recognized Developer
May 30, 2012
9,579
33,063
Hmmmm still i would like to try it with the risk involved in it

Sent from my GT-N7000 using xda premium

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
 
  • Like
Reactions: tatww and microsd16

microsd16

Senior Member
Feb 17, 2012
51
4
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

Can u plz share with me the link via pm

Sent from my GT-N7000 using xda premium
 
  • Like
Reactions: tatww

Phil3759

Inactive Recognized Developer
May 30, 2012
9,579
33,063
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
 

liron_69

Senior Member
Sep 2, 2010
122
8
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
 
Last edited:

kenshinjar

Senior Member
Jul 20, 2012
147
28
Frankfurt am Mainz
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 !!!
 

nokiamodeln91

Senior Member
Jun 6, 2012
7,389
2,634
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 !!!
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 ----------

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
but u dont need this recovery to flash his kernel.. it can be flashed on a stock recovery
 
  • Like
Reactions: kenshinjar

liron_69

Senior Member
Sep 2, 2010
122
8
but u dont need this recovery to flash his kernel.. it can be flashed on a stock recovery
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
 

Phil3759

Inactive Recognized Developer
May 30, 2012
9,579
33,063
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

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)
 

nokiamodeln91

Senior Member
Jun 6, 2012
7,389
2,634
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

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 forum@XDA #
 

liron_69

Senior Member
Sep 2, 2010
122
8
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
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 26
    * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
    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
    1aimg9539.jpg


    1bimg9475.jpg



    PhilZ Settings menu
    2img9540.jpg



    Backup / Restore EFS and kernel
    3img9541.jpg



    GUI Touch Settings
    4img9542.jpg



    Aroma File Manager
    5img9547.jpg



    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






    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



    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)

    You are done



    If it fails with black screen after successful flash:
    read about it here: http://xdaforums.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



    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 Gokhanmoral@Siyah *
    • 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


    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


    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


    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.


    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).



    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:
    • Gokhanmoral@Siyah 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
    17
    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

    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

    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
    4
    Temp CWM doesn't have the full functionality of a Philz kernel due to not having the accompanying RamDisk, but it is good for backup and restore purposes.
    However, if stock kernel recovery supports exFat , then it should work

    Edit: Phil3759 has discontinued support for Temp CWM. But I will post one based on his next version.:thumbup:

    Sent from my GT-N7000 using xda app-developers app
    3
    don't know by some else you mean someone with a different device... but I have th the N7000 too and I tested the touch sensitivity... and even at 150 its pretty hard to scroll,

    ---------- Post added at 02:51 AM ---------- Previous post was at 02:41 AM ----------

    when the list is long as in it does not fit in that page and need to scroll down, it's really difficult to reach the end as the swiping motion selects the folder where I start the swipe again and again so I am really stuck at the same page.

    ---------- Post added at 02:52 AM ---------- Previous post was at 02:51 AM ----------

    75-100 seems to be a good sensitivity for swipe to select. more than that it seems like a hard work.

    Hope I am. making sense

    ---------- Post added at 02:53 AM ---------- Previous post was at 02:52 AM ----------

    I have not experienced any skips while scrolling.. but I have mainly used 65 as the default and rest other are too quick for me.

    Good, another Note user. Yes scrolling becomes too hard @150+. If you are scrolling through ext sd card files, and do a hard fast swipe, do you not find that the nav bar "leaps" past several files and ends up further down the page? Also I hear what you are saying regarding being stuck on the same page when scrolling.

    Sent from my GT-N7000 using xda app-developers app

    Many thanks to both of you, really.
    Keep in mind, I do not have a n7000, and now I realize it is a pain to dev for a phone you do not have despite it has same hardware as the i9100, except screen. And that's where I am missing things, the gui...

    Guess what, I just anticipated this and done a crazy job: rewrite of whole touch code :cyclops:
    I already fixed the scroll continuing when finger lifted
    And the issue mentioned by nokiamodeln91 should be fixed in new code.

    Have to test it a bit more, but need to sleep before...
    2
    this recovery is a beautiful unique tool

    we will come to realise its full application by and by

    the warnings are there in full view, in black and white --- newbies and noobs would rush into it at their own risk

    Phill, you just have yourself to excel now :good: