5,596,128 Members 33,349 Now Online
XDA Developers Android and Mobile Development Forum

[m7vzw][CWM Advanced Edition][15.04.2014] PhilZ Touch 6.26.6

Tip us?
 
PonsAsinorem
Old
#151  
PonsAsinorem's Avatar
Forum Moderator - OP
Thanks Meter 1735
Posts: 3,462
Join Date: Sep 2010

 
DONATE TO ME
Quote:
Originally Posted by Phil3759 View Post
@PonsAsinorem

Hope you do not mind if I include m7vzw on my more and more rare device updates
Since I still compile other variants, m7vzw is not a big deal for me since all changes I do are in m7-common

However, since I no more update in between, your regular releases are of a huge help
Not at all. You're the boss, I just work here. Just means I get to skip an update every once in a while (I'll still download, and then upload to my mirrors, once I do a brief check on my device like I always do before upload; mirrors are rarely bad).
The Following User Says Thank You to PonsAsinorem For This Useful Post: [ Click to Expand ]
 
PonsAsinorem
Old
(Last edited by PonsAsinorem; 15th April 2014 at 12:24 PM.)
#152  
PonsAsinorem's Avatar
Forum Moderator - OP
Thanks Meter 1735
Posts: 3,462
Join Date: Sep 2010

 
DONATE TO ME
6.26.6 (14.04.2014) up at all three sites, and available via Flashify. This is more of a release from Phil to get his sources up to date from 6.25.0. Those running my 6.26.4 will see minimal (if any) change.

Quote:
- m7 unified for m7ul, m7att and m7tmo
- CWM 6.0.4.8
- merge support for native dual boot devices
- sync sources
The reason is the bug fixed in 6.26.4 (already available for m7vzw): root/recovery check on exit that was never applied even if user says YES
Since it is a non expected bug, I am rolling out an update.

Notice: stock CWM is also affected. The bug is present since 6.09.5 version. Rooting from PhilZ Settings is not affected
Bug details: on exit, when recovery prompts to fix root or recovery, even if user chooses Yes, it was like he chose No
Consequences: root is not applied while user expects it is. Recovery can be overwritten by stock ROM.

Updated FAQ:
Quote:
13- My ROM maker advises another recovery
If an installer script cannot run on PhilZ Touch, it won't run on CWM. PhilZ Touch is just a CWM mod in that regard. Installer is not modified

Rule of thumb: If a ROM cooker says "YOU MUST USE A GIVEN RECOVERY", be sure there are bugs in his work
A properly formatted updater-script, shell child scripts or aroma scripts should be able to run on any recovery as it should call real blk device paths and not "pre-defined" mount points

Mount points WILL vary from recovery to another and maybe from a version to another. Relying on them is a bad idea

Also, many do miss proper edify scripting rules:
- /sdcard is a symlink, not a folder since years now (/data/media)
- you cannot extract without mounting first
- you must create your paths. Installer won't be verifying you did so
- you cannot mount vold paths (sdcard, usb storage...) by calling the mount point in a shell script. Look at your fstab under recovery to understand why

If a rom maker has issues to understand this, he can ask for help here or in an edify scripting thread
The Following 4 Users Say Thank You to PonsAsinorem For This Useful Post: [ Click to Expand ]
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes