[jfltexx][jflte][CWM Advanced Edition] PhilZ Touch
- Thread starter Phil3759
- Start date
It works great! I've made a backup and restore just fine. 
---------- Post added at 03:54 PM ---------- Previous post was at 03:52 PM ----------
I think its the recovery issue. I remember on my Note that Philz recovery cannot flash CM10 or AOKP roms. TWRP and CWM can do it fine. :\
---------- Post added at 03:54 PM ---------- Previous post was at 03:52 PM ----------
I think its the recovery issue. I remember on my Note that Philz recovery cannot flash CM10 or AOKP roms. TWRP and CWM can do it fine. :\
This has no sense. The issue was fixed for note and s2 months ago
If you have an issue, post a log with your question
Sent from my GT-I9100 using Tapatalk 2
Phil I got a screenshot from one of the forum members (under 10 posts so he can't post here). Maybe this will help:
Phil I got a screenshot from one of the forum members (under 10 posts so he can't post here). Maybe this will help:
Nice bug
A log would help a lot here
Anyone else having the issue? Also anyone else having it display correctly without errors for /boot and /recovery?
Create a backup. Once done, go to Advanced / Report Error
Zip and attach here the philz_recovery.log file you get in /sdcard/clockworkmod folder
This should help me to spot the issue
Edit 1: i found why it fails to get size of recovery and boot partitions. However, the wired display i did not get clearly. Really need someone with the issue to provide a log
Sent from my GT-I9100 using Tapatalk 2
Last edited:
Nice bug
A log would help a lot here
Anyone else having the issue? Also anyone else having it display correctly without errors for /boot and /recovery?
Create a backup. Once done, go to Advanced / Report Error
Zip and attach here the philz_recovery.log file you get in /sdcard/clockworkmod folder
This should help me to spot the issue
Edit 1: i found why it fails to get size of recovery and boot partitions. However, the wired display i did not get clearly. Really need someone with the issue to provide a log
Sent from my GT-I9100 using Tapatalk 2
Hey phil here is the log i got the same error as written above...
http://db.tt/GkwdRm5z
Gesendet von meinem GT-I9505 mit Tapatalk 2
Wired
I see the the reason about recovery and boot being skipped from size stats (I will just change MTD names in fstab), and that's not a bug, just a missing feature
However, those non sense chars mean the char variable is not properly initialized with used "" before an strcat. I see no other cause.
However, in my setup, provoking that situation gives me perfect output in backup stats with missed partitions correctly displayed!
I will release an intermediate fix only for that variable. Once fixed, I will add recovery and boot size detection
Really wired
I see the the reason about recovery and boot being skipped from size stats (I will just change MTD names in fstab), and that's not a bug, just a missing feature
However, those non sense chars mean the char variable is not properly initialized with used "" before an strcat. I see no other cause.
However, in my setup, provoking that situation gives me perfect output in backup stats with missed partitions correctly displayed!
I will release an intermediate fix only for that variable. Once fixed, I will add recovery and boot size detection
Really wired
For people with above issue during backup, test this version
http://d-h.st/uWC
This will not remove the skipped partitions message, but should fix the corrupted text display
Please test and let me know if it fixed it or not + a log
http://d-h.st/uWC
This will not remove the skipped partitions message, but should fix the corrupted text display
Please test and let me know if it fixed it or not + a log
WoW what a sick recovery !!!
Great job Philz - you da man !!!
---------- Post added at 10:39 AM ---------- Previous post was at 10:04 AM ----------
Just attempted a backup
Mine has the exact same error
/boot
/recovery
Unknown partition size (2) :n ;9|
This is with using version:
philz_touch_5.04.0.1-i9505.zip
No idea how to get log files from a recovery, but if you teach me how, i will supply.
Update - I have found "Show Log" in the menus, but that just prints on screen, doesnt save a *.log or *.txt file on the phone (as far as i am aware, i am back into the android OS having a look now)
Update2 - found your post earlier in the thread
attempted to adb pull /tmp/recovery.log
Keep getting Device Offline message
doing a google search to figure out how to fix this.
Great job Philz - you da man !!!
---------- Post added at 10:39 AM ---------- Previous post was at 10:04 AM ----------
Nice bug
A log would help a lot here
Anyone else having the issue? Also anyone else having it display correctly without errors for /boot and /recovery?
Create a backup. Once done, go to Advanced / Report Error
Zip and attach here the philz_recovery.log file you get in /sdcard/clockworkmod folder
This should help me to spot the issue
Edit 1: i found why it fails to get size of recovery and boot partitions. However, the wired display i did not get clearly. Really need someone with the issue to provide a log
Sent from my GT-I9100 using Tapatalk 2
Just attempted a backup
Mine has the exact same error
/boot
/recovery
Unknown partition size (2) :n ;9|
This is with using version:
philz_touch_5.04.0.1-i9505.zip
No idea how to get log files from a recovery, but if you teach me how, i will supply.
Update - I have found "Show Log" in the menus, but that just prints on screen, doesnt save a *.log or *.txt file on the phone (as far as i am aware, i am back into the android OS having a look now)
Update2 - found your post earlier in the thread
attempted to adb pull /tmp/recovery.log
Keep getting Device Offline message
doing a google search to figure out how to fix this.
Last edited:
The official version is 5.03.7 You should try it first!
If you have the problem that have been reported some posts above, then you try 5.04.0.1 to see if it will fix it.
It is ok if you report it still there with 5.04.0.1
I can fix it, but I need to know where the variable is modified to output that garbage. Only the i9505 seems affected. I just want to understand where it is modified before I fix it
I will release a tracing release that logs the variable state to track where it is modified "illegally"
To post a log: Advanced / Report Error
You get a philz_recovery.log file in /sdcard/clockworkmod
zip it and attach here
I will release another version. By the way, 5.04.0.1 is full stable and was scheduled for release until you spotted this bug. You can use it as it fixes some issues. Next releases will be debugging
If its possible Philz,
Add straight under the view log a "save log" function in your recovery, which stores it in the SDCARD or ext-sdcard and i will provide as many log files as you want. I have attempted the ADB connection multiple times, and it seems either my ROM or Kernel (which ever it is) is affecting it to be "Offline" all the time. So ADB connection via USB to extract logs wont work for me.
No need to extract it that way:
You go into the Advanced menu, then use the report error menu
It will save a log to /sdcard/clockworkmod/philz_recovery.log
That log can be accessed when you boot in main ROM. Just be sure to use a root explorer to access /data/media if you did not enable /data/media/0 path in Advanced menu
aha gotcha
i already enabled media/0 as i read it earlier somewhere in the thread.
ill do a backup now, and straight after report error then add the logs here for you.
report back in a minute:
No need for now as it won't help me much except seeing that something is overwriting my variable in memory
I am compiling a new debug version
Also, you can cancel the backup when it starts, as the message error is at the start, so no need to wait for it to end
No need for now as it won't help me much except seeing that something is overwriting my variable in memory
I am compiling a new debug version
Also, you can cancel the backup when it starts, as the message error is at the start, so no need to wait for it to end
oh well here it is anyways.
Now i know how to do it, ill test all the versions to iron out any kinkz
I am having the same error. Nor recovery and boot partition size. (will it make a backup nontheless or is the backup unuseable?)
Backup to SD only works with exfat and not fat32 am I right?
My SD Card is formatted in FAT32. The last step of regular backup seems to hang itself.
Backup to SD only works with exfat and not fat32 am I right?
My SD Card is formatted in FAT32. The last step of regular backup seems to hang itself.
Last edited:
Similar threads
- Poll
Top Liked Posts
-
There are no posts matching your filters.
-
645Main 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:
Big thanks to @wanam and @ausdim for their great support with providing kernels and support in compiling them45PhilZ Touch 6.0
Download:
http://d-h.st/users/philz_touch/?fld_id=16685#files
Theme files (put them as in folders in zip AND Internal SD):
http://d-h.st/users/philz_touch/?fld_id=28702#files
Enjoy and huge thanks to all donators who got me this phone44Philz Touch 6.59.0 jflte Attached To XDA Server
Here is the Direct Download Link with Full Speed and Pause Option.
(Do not forget to press the Thanks button.)4240I will miss PhilZ recovery a lot!...
Tried TWRP 2.7 and three versions of 2.8. My nandroids disappear after booting, browsing files and flash process is much more inconvenient...
Well it's a pity
For now you have a fully working PhilZ Touch
To all donators: CWM is no more supported in a good way by CM team. They moved to CyanogenMod Simple Recovery. As the name suggests, it is really a simple recovery with basic and limited features.
PhilZ Touch being based on CWM, this means I have to start a whole new project from near scratch if we want to continue with PhilZ Touch. I started doing it, it ended with very good version you have now that is compatible with latest CM files. However, continuing this to completely migrate it to c++ complying code is an endless hours job. My life imperatives don't allow it.
S4 won't see Android L for the next many months probably, so, until then, it should be fine
