[d2tmo][CWM Advanced Edition] PhilZ Touch

Search This thread

Phil3759

Inactive Recognized Developer
May 30, 2012
9,579
33,063
Main thread + features + install instructions + dev support
http://xdaforums.com/showthread.php?t=2201860


PhilZ Touch 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

It also adds a full touch interface a completely configurable GUI

Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something

Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut


Download links
Last version can be found here:

Now: one common recovery for all: d2lte
The below specific variants are no more updated, use d2lte common variant


SGH-T999 (d2tmo)
http://goo.im/devs/philz_touch/CWM_Advanced_Edition
 
Last edited:

Phil3759

Inactive Recognized Developer
May 30, 2012
9,579
33,063
Reporting issues:
1- Keep in mind I do not own the device: be precise in your description providing step by step details and screen log output
2- Provide a log: Advanced / Report Error, then attach the philz_recovery.log here


exfat is enabled: report if working or not
Let me know about any issue so that we can debug it + LOGS
 

mt3g

Senior Member
Aug 14, 2009
6,949
3,128
Phoenix
Flashes fine and looks great.
The time is off by 7 hours for me looked in settings for creating a time zone slot, with no success. The screenshot feature is dope but didn't work, gave me tears and not visible screens. Will flash a kernel in a second to test that much out. Will flash a ROM and create a backup later to test more thorough. The screen is what I got from swipe to left for screenshot in recovery.
EDIT: Kernel falshed fine. so all in all no real issues to report as it works as a recovery should, all but testing nandroid and restoring.
T-Mobile SGS III
 

Attachments

  • uploadfromtaptalk1370371208463.jpg
    uploadfromtaptalk1370371208463.jpg
    64.8 KB · Views: 3,515
Last edited:
  • Like
Reactions: Phil3759

Phil3759

Inactive Recognized Developer
May 30, 2012
9,579
33,063
Flashes fine and looks great.
The time is off by 7 hours for me looked in settings for creating a time zone slot, with no success. The screenshot feature is dope but didn't work, gave me tears and not visible screens. Will flash a kernel in a second to test that much out. Will flash a ROM and create a backup later to test more thorough. The screen is what I got from swipe to left for screenshot in recovery.
EDIT: Kernel falshed fine. so all in all no real issues to report as it works as a recovery should, all but testing nandroid and restoring.
T-Mobile SGS III

Thank you for the positiv eearly report
fb2png for screenshots doesn't support most new boards. Hopefully it will be fixed later
Time is GMT by default. Time zone can be set under GUI settings, it should work. If not, provide a log
 

mt3g

Senior Member
Aug 14, 2009
6,949
3,128
Phoenix
Thank you for the positiv eearly report
fb2png for screenshots doesn't support most new boards. Hopefully it will be fixed later
Time is GMT by default. Time zone can be set under GUI settings, it should work. If not, provide a log
It sure was and time is correct now, I like the brightness settings also, lots of goodies in there. I'll report back later tonight if no one else does on nandroid and such.
 
  • Like
Reactions: Phil3759

Alpha_wolf

Senior Member
Dec 13, 2012
723
194
Marina
ill try it out im using twrp recovery so itll be fun to try something new lol

omg! its touch enabled :D
and i like the color at first the layout is a win for me so far and ui is to
great job

clock is working changed to my time zone with daylight savings time fine

omg just found out i can you my home back and menu in it :)

im having fun playing with it im easy to entertain lol give me a break

ok new favorite recovery lol im hooked lol
 
Last edited:

Phil3759

Inactive Recognized Developer
May 30, 2012
9,579
33,063
I do not expect any issue with nandroid backups as it was largely debugged now on other devices
However:
- Mount USB storage works?
- exfat is ok?
- A last important point: when you boot into recovery, /system is mounted or unmounted? To see this, go into Mounts and Storage menu after you booted in recovery. /system should show (mount) and not (unmount)

I ask this to tune things if needed as this is completely repacked around stock ramdisk and kernel to enable exfat mainly
 

mt3g

Senior Member
Aug 14, 2009
6,949
3,128
Phoenix
My stuff is fat32 so I can't help there... system is not mounted it shows mount/ system
 

Synthetic.Nightmare

Inactive Recognized Developer
Mar 29, 2011
952
1,211
Just booting into it and scrolling through some of the options was a treat within itself. Don't have much more to say (that hasn't been said already) but I'm glad we're able to have such a refined recovery. I'll let you know if I bump into any issues, as I tend to not stay in recovery mode for too long (when I actually have something to flash, etc. I'll test more). Thanks!

Sent from my SGH-T999 using Tapatalk 4 Beta
 

ChitownWingMan

Senior Member
Aug 10, 2007
307
54
Chicagoland
Main thread + features + install instructions + dev support
http://xdaforums.com/showthread.php?t=2201860


PhilZ Touch 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

It also adds a full touch interface a completely configurable GUI

Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something

Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut


Download links
Last version can be found here:

I was able to install it perfectly with Odin with the only difference from your installation instructions being that the phone rebooted into normal mode, so I just entered recovery mode via Rom Toolbox.

I am unable to access an external 64GB SDXC formatted as exFat. I tried to mount /external_sd and /sd-ext and neither one worked. I don't know if this is relevant but the normal mount point for the external SD card on the Galaxy S3 is /mnt/extSdCard.

The aroma file manager doesn't see the external card either.

Everything else seems to be working though I haven't tried to do a backup or a restore.

Thanks for your help...
 
Last edited:

LuigiBull23

Senior Member
Jan 22, 2013
6,666
6,307
33
Holyoke
Love the UI! Very easy to navigate. Everything seems to be running smoothly so far. Installed a few AOSP and TW ROMs successfully. Kernels I've tested are BMS, KT747, and LK. All were successful as well.

EDIT: Backup and restore options seem to work just fine. No issues with Mounts or storage I'm on a fat32 card so I can't test exfat unfortunately. Will let you know if anything comes up within the next day or 2.
Thank you very much for sharing this. It is pretty dope.
 
Last edited:
  • Like
Reactions: Phil3759

Phil3759

Inactive Recognized Developer
May 30, 2012
9,579
33,063
Thank you all
Will wait a bit more for reports about exfat
Some 64Gb cards always caused issues on some phones, mainly if they were not formatted as they should (primary partition and default block size)

Sent from my GT-I9100 using Tapatalk 2
 

galahadUSA

Senior Member
Sep 24, 2008
417
148
I tried flashing the zip file but install keeps aborting?

Sent from my SAMSUNG-SGH-I747 using xda premium
 

ChitownWingMan

Senior Member
Aug 10, 2007
307
54
Chicagoland
Thank you all
Will wait a bit more for reports about exfat
Some 64Gb cards always caused issues on some phones, mainly if they were not formatted as they should (primary partition and default block size)

Sent from my GT-I9100 using Tapatalk 2

When I had problems with the early exfat drivers from Samsung, I reformatted the card as Fat32 and ran with that for some time. After installing an update from Samsung/T-Mobile where the exFat issues were fixed I used the following procedure to convert the card to exFat:

1. Copied all data from the card to a PC via a card reader.
2. Deleted all partitions from the card using a partition manager on the pc
3. Installed the card into the phone and let the phone partition and reformat the card.
4. Copied all data from the PC back to the card via a card reader.
5. Re-installed the card into the phone.

It has been several months since I converted the card back to exFat and I have had no problems with app on the phone accessing the card. This include Nandroid Manager, Online Nandroid and Titanium Backup as well as all of the normal Android utilities.

The partition information is:

Partition Type: Primary
Psttition Type Id: 0x0C
File System: exFAT
Serial #: 0
First Physical Sector: 2048 (Cyl: 0, Hd:32, Sect: 33)
Last Physical Sector 124735487 (Cyl: 7764, Hd: 108, Sect: 24)
Total Physical Sectors: 124733440 (60905.0MB)
Physical Geometry: 7764 Cyls, 255 Hds, 64 Sects.

That's the best that I could do on short notice. I am trying to find a utility that will give me more information under Windows 7.

Thanks again and again...

Mike

P.S. If I can help with some testing or programming, please let me know. I'm fighting learning java but I am pretty good with C/C++ and assembler.
 
Last edited:

Phil3759

Inactive Recognized Developer
May 30, 2012
9,579
33,063
When I had problems with the early exfat drivers from Samsung, I reformatted the card as Fat32 and ran with that for some time. After installing an update from Samsung/T-Mobile where the exFat issues were fixed I used the following procedure to convert the card to exFat:

1. Copied all data from the card to a PC via a card reader.
2. Deleted all partitions from the card using a partition manager on the pc
3. Installed the card into the phone and let the phone partition and reformat the card.
4. Copied all data from the PC back to the card via a card reader.
5. Re-installed the card into the phone.

It has been several months since I converted the card back to exFat and I have had no problems with app on the phone accessing the card. This include Nandroid Manager, Online Nandroid and Titanium Backup as well as all of the normal Android utilities.

The partition information is:

Partition Type: Primary
Psttition Type Id: 0x0C
File System: exFAT
Serial #: 0
First Physical Sector: 2048 (Cyl: 0, Hd:32, Sect: 33)
Last Physical Sector 124735487 (Cyl: 7764, Hd: 108, Sect: 24)
Total Physical Sectors: 124733440 (60905.0MB)
Physical Geometry: 7764 Cyls, 255 Hds, 64 Sects.

That's the best that I could do on short notice. I am trying to find a utility that will give me more information under Windows 7.

Thanks again and again...

Mike

P.S. If I can help with some testing or programming, please let me know. I'm fighting learning java but I am pretty good with C/C++ and assembler.

Sadly, without a recovery log or even better a dmsg log, I cannot help a lot
exfat drivers are from /system/lib, so the ones used by your ROM. They are not bundled with the recovery as that causes issues for some

can you try this in adb shell:
Code:
mount -t extfat /external_sd

Give the error message if it fails
If it fails, try this

Code:
mount /system
insmod -f -v /system/lib/modules/exfat_core.ko
insmod -f -v /system/lib/modules/exfat_fs.ko
mount -t extfat /external_sd

Give output of these command lines if they do fail
 

ChitownWingMan

Senior Member
Aug 10, 2007
307
54
Chicagoland
Sadly, without a recovery log or even better a dmsg log, I cannot help a lot
exfat drivers are from /system/lib, so the ones used by your ROM. They are not bundled with the recovery as that causes issues for some

can you try this in adb shell:
Code:
mount -t extfat /external_sd

Give the error message if it fails
If it fails, try this

Code:
mount /system
insmod -f -v /system/lib/modules/exfat_core.ko
insmod -f -v /system/lib/modules/exfat_fs.ko
mount -t extfat /external_sd

Give output of these command lines if they do fail

Manual mount:

~ # mount -t extfat /external_sd
mount -t extfat /external_sd
mount: mounting /dev/block/mmcblk1p1 on /external_sd failed: Invalid argument


The mount was successful after the insmod commands. I was also able to cd to /external_sd and do an "ls -l".

Can I modify a script to include the insmod's or do you have to do it?

Thanks again...
 
  • Like
Reactions: Phil3759

Phil3759

Inactive Recognized Developer
May 30, 2012
9,579
33,063
Manual mount:

~ # mount -t extfat /external_sd
mount -t extfat /external_sd
mount: mounting /dev/block/mmcblk1p1 on /external_sd failed: Invalid argument


The mount was successful after the insmod commands. I was also able to cd to /external_sd and do an "ls -l".

Can I modify a script to include the insmod's or do you have to do it?

Thanks again...

Ok, we're on the way to fix it
Can you try this now, in adb shell, after a recovery reboot please

Code:
mount /system
insmod /system/lib/modules/exfat_core.ko
insmod /system/lib/modules/exfat_fs.ko
mount -t extfat /external_sd

That way I can limit the potential causes. It is same as above without insmod options in command
 

ChitownWingMan

Senior Member
Aug 10, 2007
307
54
Chicagoland
Ok, we're on the way to fix it
Can you try this now, in adb shell, after a recovery reboot please

Code:
mount /system
insmod /system/lib/modules/exfat_core.ko
insmod /system/lib/modules/exfat_fs.ko
mount -t extfat /external_sd

That way I can limit the potential causes

Before I tried what you asked I rebooted into recovery. In other words, I ran the adb shell commands while the phone was in your recovery program. Is that what you mean?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 31
    Main thread + features + install instructions + dev support
    http://xdaforums.com/showthread.php?t=2201860


    PhilZ Touch 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

    It also adds a full touch interface a completely configurable GUI

    Please give your feedback, what works, and any bug you could encounter
    Read the features, and check if you are missing something

    Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut


    Download links
    Last version can be found here:

    Now: one common recovery for all: d2lte
    The below specific variants are no more updated, use d2lte common variant


    SGH-T999 (d2tmo)
    http://goo.im/devs/philz_touch/CWM_Advanced_Edition
    8
    Update 6.15.7
    - Galaxy S3 Unified d2 variants (d2lte): d2att d2cri d2mtr d2spr d2tmo d2usc d2vzw


    One recovery image for all devices

    credits to CM team for their huge work on this resources sparing
    4
    Recovery doesn't root your phone. Use the Odin program. Check the sticky threads in Android Development forum for your device and find the guide that tells you how to root. There are detailed instructions.

    Sent from my SGH-T999 using Tapatalk 2

    Recovery can root phone, at least cwm
    When you flash CWM on a stock non rooted ROM, reboot o main system. It will prompt you to root phone
    After that, just go to market and install superuser app from Koush, open it and it will complete the root process
    3
    Reporting issues:
    1- Keep in mind I do not own the device: be precise in your description providing step by step details and screen log output
    2- Provide a log: Advanced / Report Error, then attach the philz_recovery.log here


    exfat is enabled: report if working or not
    Let me know about any issue so that we can debug it + LOGS
    3
    Released v5.08.5

    Change list 5.07.1 ---> 5.08.5
    5.08.5 (11.07.2013)
    - Compile Aroma File Manager (by amarullz) zip installer under recovery:
    * either compile whole recovery, zip will be created at first pass
    * or only compile aroma zip installer in two pass:
    1- mmm bootable/recovery/aromafm
    2- mmm bootable/recovery/aromafm/tools
    * output: [target_out]/aromafm_out/aromafm_[DeviceID].zip
    - detect aroma compatibility with non NEON devices during compiling
    - use less conflicting flags: TARGET_NAME --> TARGET_COMMON_NAME

    5.08.0 (07.07.2013)
    - improve nandroid progress bar update
    - fix recovery was not prompting when backup estimated size is larger than free space
    - add ors backup support for twrp format requested by BillGoss
    - ors backup: when no backup name is given, generate it using same way as nandroid operations (time stamp + rom name tag)
    - support separated compiling for Loki patched devices (S4 AT&T and Verizon)
    - i9505: revert some changes to fix time bug for some users
    - Galaxy S4 US variants: repack around Audism stock JB 4.3 kernel v3 + Samsung exfat modules + revert use of mkefs for partition corruption issue
    - fix missing break in set backup compression value menu (misc_nandroid_menu())
    - misc clean up code
    - sync latest sources

    5.07.6 (05.07.2013)
    - update version 6.0.3.3
    - add exfat-fuse 1.0.1.362 / 2.9.2 optional support by enabling USE_EXFAT_FUSE_BIN CFLAG in BoardConfig (exfat support on cyanogenmod repacks)
    - i9505: use Audism kernel v3 (Stock Samsung sources) to fix partition corruption without additional code and for better exfat support

    Please Note: Device specific threads will no longer be updated. I monitor them for support and feedback though
    To check if you have a new version, subscribe to main thread:

    http://xdaforums.com/showthread.php?t=2201860

    Thank you for your understanding