yashsingh1/xdaforums huggingface dataset:
[Android Software Development] ykkfive:
yes, i agree most of the time it's not needed

but, for instance, formatting between ext4 and f2fs back and forth (when i was testing the conversion), i didnt know/expect i will have to turn it on again.

and if one wants to reformat more than 1 partitions, then he'll have to toggle it again and again

actually, i think that it's no harm to have both the options (ext4 and f2fs) available. or let me rephrase my question, (no need to save the toggle) is it better to let the use choose which fs during reformatting, without the togggle? that means the toggle option can be removed

anyway, just my 2 cents
[Android Software Development] iperryt:
Hey guys, I tried to find some infos on the issue I have but there is just too many pages.

I have the CWM Philz and I forgot my password, is there a way to set it back? Or disable it?
[Android Software Development] danarama:
Toggle is important.

1) without toggle, option to choose fs is always present.

2) adds extra step to format procedure

3) presents noobs with a choice they may not understand

4) presents a broken option in versions that don't have f2fs kernel support

Having the toggle saved is only beneficial in the instance of initial testing. You've done that now. IMHO, this option is superfluous.

Delete the password file from /system
[Android Software Development] iperryt:
I did already search it but I am not sure which one it is and I don't want to delete important files :eek:
[Android Software Development] danarama:
The obvious one, /system/.recovery_key.lok
[Android Software Development] iperryt:
thank you, I didn't realize "show hidden files" was off :silly:
[Android Software Development] jurben:
try this: (copied from README.md in philz source)
[Android Software Development] ykkfive:
ok, although my point of view is bit different from yours

I am not challenging you, dont get me wrong. I agree that an extra option will confuse some ppl, but for me, the broken option could be solved by other solutions since this problem will occur when the kernel doesnt have f2fs support also, so it is not a problem related to the toggle (by assuming no checking for f2fs support in order to show the toggle) . while u mentioned that it is an extra step to the format procedure, in my opinion, it cannot stand because it is a decision, deciding what to do next. but of coz, it depends on where u put the decision in the flow chart

anyway, never mind, this is just a discussion only. we all aimed to make it better and user friendly

thanks
[Android Software Development] juliusssss:
Thanks for your reply, but i think that isn't the problem i compiled CWM Philz for another device with the same sources and i compiled without errors and it works.

I don't know why i have these errors with other device. :confused::confused:
[Android Software Development] jurben:
is there

RECOVERY_VARIANT := philz

inside this device BoardConfig.mk but not inside that another device's?

and where is your philz source? in bootable/recovery or bootable/recovery-philz ?
[Android Software Development] juliusssss:
Yes, i have RECOVERY_VARIANT := philz in my BoardConfig and Philz sources are in booteable/recovery-philz.
[Android Software Development] Phil3759:
using recovery variant flag in readme

If not, post back here

- on restore, partition is formatted, I do not plan to change it as I see no reason for it

- while you don't exit the menu, the toggle remains active and you can toggle as many partitions as you need. If you exit the menu, the toggle is reset. For the reasons [MENTION=2872010]rootSU[/MENTION] mentioned, I do not plan to make it persistant

you have no permissions to ask for compiling and releasing your versions :)

You just must keep your changes opensource on git
[Android Software Development] juliusssss:
Thanks Phil, but i used recovery variant flag in BoardConfing.mk and i had these errors.
[Android Software Development] ykkfive:
ok. but do I need to inform u about the release of an unofficial port for a new device?

I didn't change anything in your recovery, so I think I don need to put them on git, right?

thanks
[Android Software Development] Bhargav97:
Hello,

I am facing an issue in 6.56.2 and 6.57.2 (I ddin't try older from beta-branch). The last version I tested and issue was not present is: 6.48.4.

Issue is: I mount system and data from MOUNTS & STORAGE and then I double-tap to open AROMA FM. It opens successfully. But system and data aren't mounted in there.So I can't see them (contents inside them). Moreover, After I close aroma fm and go to MOUNTS & STORAGE, system and data are un-mounted.

LOG (I mount system, data and open aroma fm):

http://pastebin.com/BWZE7krr

Anyone else also facing same issue?
[Android Software Development] Phil3759:
I never tried with the variant in fact :D

It was merged without much testing from my side. Maybe I trusted excessively...

For now, put it in bootable/recovery instead of stock cwm source

I will take a look at it
[Android Software Development] bangdes:
i can't find NOKIA X...
[Android Software Development] juliusssss:
I put your sources in bootable/recovery but i get the same errors.

Do you know what is the meaning of that?:

arm-linux-androideabi-gcc: error: ": No such file or directory
[Android Software Development] Phil3759:
you are really free

Do what you think is best for you and users

You must enable auto-mounts in aroma

Recovery now unmounts some partitions when installing a zip. This fixes a lot of format fails from bad script coders and complies to AOSP

If it fails without variant, it could be you have your sources out of sync

try a "repo sync" and "make clobber"
[Android Software Development] juliusssss:
I'm here again, sorry Phil :angel:

I did repo sync, make clobber and i compiled again, but i still get the same errors.

Thanks again. Greetings.
[Android Software Development] Bhargav97:
Nice! :)

But unfortunately auto mount isn't working in aroma FM in arm11 devices (all OR just mine?).

Will investigate in aroma source. Thanks!
[Android Software Development] Phil3759:
can you do this, while in recovery:

adb shell
cat /etc/fstab
cat /etc/recovery.fstab
[Android Software Development] jurben:
show us your BoardConfig.mk and your commands.

btw, check your disk for errors and check your free space.
[Android Software Development] Bhargav97:
Here they are (done while in recovery):

~ # cat /etc/fstab
/dev/block/stl13 /system ext4 defaults
/dev/block/stl12 /data ext4 defaults
/dev/block/stl14 /cache ext4 defaults
/dev/block/mmcblk0p2 /sd-ext ext4 defaults

and

~ # cat /etc/recovery.fstab
# Android fstab file.
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
# http://source.android.com/devices/tech/storage/index.html
#
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
/dev/block/stl13 /system ext4 ro check,wait
/dev/block/stl12 /data ext4 nosuid,nodev check,wait
/dev/block/stl14 /cache ext4 nosuid,nodev check,wait
/dev/block/mmcblk0 auto auto defaults voldmanaged=sdcard0:auto,noemulatedsd
/dev/block/mmcblk0p2 /sd-ext ext4 defaults recoveryonly
boot /boot bml defaults recoveryonly
recovery /recovery bml defaults recoveryonly
/dev/block/zram0 none swap defaults zramsize=50331648,swapprio=1

P.S. If I write:

mount /system

from the terminal in AROMA, my system gets mounted successfully. Same with other partitions. Issue is only with "auto-mount all devices on start".
[Android Software Development] Phil3759:
probably an aroma issue

I will disable the umount on zip install function for aroma
[Android Software Development] Redwraith96:
Hii [MENTION=4666971]Phil3759[/MENTION],

your cwm is very useful and cool and can you update to 6.0.5.0 for all Galaxy W members?

Thanks for all your WORK.:)
[Android Software Development] Phil3759:
Update 6.57.5

You are mainly interested in this commit:

https://github.com/PhilZ-cwm6/philz_touch_cwm6/commit/82d65cc41e09791b3e108b1bcc6e713911a61453
[Android Software Development] ykkfive:
hi phil3759

fyi, just released a port for tab s 10.5 sm-t800 (chagallwifi)

http://xdaforums.com/galaxy-tab-s/development/t800-philz-touch-6-56-2-f2fs-19-8-t2851566

thank you
[Android Software Development] mike710_0:
Hi

I can't make a nandroid backup. I get the error message 'tar_append_tree("data", "data"): No such file or directory'

How can I fix this?

I've got a galaxy s3
[Android Software Development] diaBoliQu3:
Hopefully there will be Xiaomi Note version. Fan of Philz Touch. :D
[Android Software Development] Phil3759:
Last person with that issue had a corrupted /data partition
[Android Software Development] mike710_0:
How do I fix this then?
[Android Software Development] danarama:
If its a corrupt /data partition then its not a recovery issue. What you reported here is a symptom. Search or post in your device q&a section.
[Android Software Development] juliusssss:
Here is the BoardConfig.mk i use:

# inherit from the proprietary version
-include vendor/xiaomi/mocha/BoardConfigVendor.mk

TARGET_ARCH := arm
TARGET_NO_BOOTLOADER := true
TARGET_BOARD_PLATFORM := tegra
TARGET_CPU_ABI := armeabi-v7a
TARGET_CPU_ABI2 := armeabi
TARGET_CPU_VARIANT := cortex-a15
TARGET_ARCH_VARIANT := armv7-a
ARCH_ARM_HAVE_TLS_REGISTER := true

TARGET_BOOTLOADER_BOARD_NAME := mocha

BOARD_KERNEL_CMDLINE :=
BOARD_KERNEL_BASE := 0x10000000
BOARD_KERNEL_PAGESIZE := 2048
BOARD_MKBOOTIMG_ARGS := --dt device/xiaomi/mocha/dt.img

RECOVERY_VARIANT := philz

BOARD_USE_CUSTOM_RECOVERY_FONT := \"roboto_23x41.h\"
TARGET_SCREEN_HEIGHT := 1200
TARGET_SCREEN_WIDTH := 1920
BRIGHTNESS_SYS_FILE := /sys/class/leds/button-backlight/brightness
TARGET_USE_CUSTOM_LUN_FILE_PATH := /sys/class/android_usb/android0/f_mass_storage/lun/file
BOARD_UMS_LUNFILE := /sys/class/android_usb/android0/f_mass_storage/lun/file
RECOVERY_GRAPHICS_USE_LINELENGTH := true
TARGET_USERIMAGES_USE_EXT4 := true
BOARD_HAS_NO_SELECT_BUTTON := true
BOARD_RECOVERY_SWIPE := true
BOARD_NATIVE_DUALBOOT := true
BOARD_NATIVE_DUALBOOT_SINGLEDATA := true
TARGET_RECOVERY_UI_LIB := librecovery_ui_mocha
BOARD_BOOTIMAGE_PARTITION_SIZE := 20971520
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 20971520
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 671088640
BOARD_USERDATAIMAGE_PARTITION_SIZE := 13742637056
BOARD_FLASH_BLOCK_SIZE := 131072

BOARD_CUSTOM_RECOVERY_UI := \
../../device/xiaomi/mocha/recovery/dualboot.c \
../../device/xiaomi/mocha/recovery/recovery_ui.c

TARGET_PREBUILT_KERNEL := device/xiaomi/mocha/kernel

With this BoardConfig.mk i compiled CWM Stock without errors and it works.
[Android Software Development] Phil3759:
I see your issue

BOARD_NATIVE_DUALBOOT := true
BOARD_NATIVE_DUALBOOT_SINGLEDATA := true
TARGET_RECOVERY_UI_LIB := librecovery_ui_mocha
BOARD_CUSTOM_RECOVERY_UI := \
../../device/xiaomi/mocha/recovery/dualboot.c \
../../device/xiaomi/mocha/recovery/recovery_ui.c

My sources are now much different from stock CWM

I removed all this BOARD_NATIVE_DUALBOOT and BOARD_NATIVE_DUALBOOT_SINGLEDATA support

A developer from your device must add the flags to my sources and ensure they work

I have no time on my own for that as I do not own that specific model
[Android Software Development] juliusssss:
I need this flags for this device. :crying:

But i compiled without this flags and i get the same error.

Thanks anyway. Greetings.
[Android Software Development] ianjay06:
can u make a full working philz recovery in our device?

Phone Brand is: Starmobile Up (local phone in philippines) MT6582M Chipset Running in Android 4.4.2

im actually using this but with error.. touch control is not working so i use volume up and down to select...

i use the philzrecovery.img and flash it to sp flashtool... we use this to root our phone...

what files are you needed to create this? appreciated your help
[Android Software Development] ykkfive:
hi phil3759

FYI, just added another variant, tab s 10.5 SM-T805 chagalllte

http://xdaforums.com/galaxy-tab-s/development/t800-philz-touch-6-56-2-f2fs-19-8-t2851566

thank you
[Android Software Development] gabrielbsb:
I have TWRP intalled, may I flash Philz directly from TWRP or should I flash CWM before?
[Android Software Development] rogersb11:
Philz directly should be just fine
[Android Software Development] Android-Andi:
Someone else getting error7 while flashing jb rom?

Flashed fresh compiled cm10.2 but getting this error... mh...

Also a user reported vold crash on golden.

Will get logs next days.

Send from OnePlus One using Tapatalk
[Android Software Development] rogersb11:
Not sure about Philz but I know with standard CWM you can't flash anything but kitkat with 6.0.4.4 and up so that's probably the issue
[Android Software Development] Android-Andi:
PhilZ Touch 6.57.5,

No problems flashing the zip using TWRP 2.7.1.2

Send from OnePlus One using Tapatalk

Edit:

Samsung golden, both recoveries selfcompiled
[Android Software Development] katinatez:
Hello, just compiled philz recovery for Nabi 2 (its a kids tablet) running Jellybean. I used the jellybean branch running cwm based v6.0.2.8 to compile but only have hardware buttons to navigate, what flag or boardconfig setting do I use to enable touch gui?

I see this line in Android.mk #PHILZ_TOUCH_RECOVERY := true but when I remove hashtag it does not compile.
[Android Software Development] Unjustified Dev:
Philz touch parts weren't available at the time you should be able to port the latest version by simply updating boardconfig and fstab. Refer to a similar device.

If you need any help send me a private message.
[Android Software Development] Phylon2012:
-- moved --

edit: moved to appropriate device specific thread
[Android Software Development] guhvanoh:
Large snippage occured before... Does your device have a PhilZ thread? If yes, ask there. This is the development thread where the focus is development questions, not user focused issues. If your device doesn't have a PhilZ thread, .......
[Android Software Development] shoey63:
+1 to what [MENTION=3274189]guhvanoh[/MENTION] just said

Brickbug was fixed in JB, so flash whatever JB based kernel you like.
[Android Software Development] Phylon2012:
Thanks, I found the thread you probably meant. Sorry, I was not aware of its existence.
[Android Software Development] FeyoMx:
help

hello, first of all thank you very much for the excellent work. I hope to find help to resolve this issue, I am unable to install any zip because it can not mount the partitions. attached the log. Thanks in advance
[Android Software Development] James L:
Philz Touch Recoveries

Philz Touch Recovery, looks nice and works as stated.

Thank you :good:
[Android Software Development] AngSanley:
HI, I got this error

please help me i'm a newbie builder
[Android Software Development] Phil3759:
You are using a kernel without QCOM_MDP support while you enabled it in BoardConfig.mk
[Android Software Development] katinatez:
Sure has been quiet lately, anyways [MENTION=4666971]Phil3759[/MENTION] so I was able to compile bacon recovery with different kernels like you had suggested first I used liquidsmooth kernel which was forked from slim. And I just now compiled with ak kernel but still aroma.zip wont load but I have a better recovery log after I had loaded the zip file using adb pull /tmp/recovery.log I think this shed more light on what's going on. Also I just randomly chose aromafm-1.80.zip but will also get the same results with 1.91.zip

Any other suggestions?

-- Installing: /sdcard/Download/aromafm-1.80.zip
Finding update package...
I:Update location: /sdcard/Download/aromafm-1.80.zip
Opening update package...
Installing update...
aroma/s: Initializing
aroma/s: Saving Arguments

AROMA Filemanager version 1.80
(c) 2012 by amarullz xda-developers

aroma/s: Open Archive
aroma/s: Initializing Resource

DEVICE NAME: qpnp_pon - /sys/board_properties/virtualkeys.qpnp_pon
EV ST: minX: 0 maxX: 0 minY: 0 maxY: 0
EV MT: minX: 0 maxX: 0 minY: 0 maxY: 0

DEVICE NAME: gpio-keys - /sys/board_properties/virtualkeys.gpio-keys
EV ST: minX: 0 maxX: 0 minY: 0 maxY: 0
EV MT: minX: 0 maxX: 0 minY: 0 maxY: 0

DEVICE NAME: synaptics-rmi-ts - /sys/board_properties/virtualkeys.synaptics-rmi-ts
EV ST: minX: 0 maxX: 0 minY: 0 maxY: 0
EV MT: minX: 0 maxX: 1080 minY: 0 maxY: 1926
aroma/s: Input Initialized
aroma/s: Opening Freetype
aroma/s: Graph Initialized
aroma/s: Mute Parent
aroma/s: Starting Interface
aroma/s: (1) Freetype fonts loaded as Font Family
aroma/s: (1) Freetype fonts loaded as Font Family
aroma/s: (1) Freetype fonts loaded as Font Family
Load Font: DroidSans.ttf - dir: assets/fonts/Droid Sans/
aroma/s: Change Folder /
[Android Software Development] AngSanley:
I can't find any line including the text "QCOM_MDP" in device/nokia/normandy/BoardConfig.mk ?

Edit: I got this patch https://github.com/NormandyCM11/android_device_nokia_normandy/tree/master/patches

but only for CWM, how to patch it into Philz?
[Android Software Development] Phil3759:
Aroma is a soon to be dead project anyway, until author updates it

Most new kernels have issues with it

I sadly have no time to look at it. It is not my project

Just remove this line from your device board config:

TARGET_USES_QCOM_BSP := true
[Android Software Development] AngSanley:
I got another error: http://buildbox.angsanley.com:8080/job/PhilZ-Recovery/14/console
[Android Software Development] ashish_zarekar:
i have micromax a110. from today my philz recovery is not working it gives me footer is wrong, signature verification failed with any flashable zip file.

i have tried only CWM which works perfectly.

i have been facing this problem since today morning. please guide me how can i solve this one.
[Android Software Development] PMGRANDS:
Whats the difference between the 6.26.2 klte.tar and 6.48.4 klte.tar?
[Android Software Development] It_ler:
Here is the full changelog.

Sorry ... too many changes to quote ;)
[Android Software Development] PMGRANDS:
Will either version work with Sprint Galaxy S5? I'm not sure if there for different carriers, or phones... Trying to be safe. Don't wanna Brick my phone.
[Android Software Development] Phil3759:
You are missing some minui files

It could be your build box issue or a broken boardconfig

If you can build CWM, you should be able to build PhilZ
[Android Software Development] It_ler:
Sprint S5 ... yes, it will work fine.

Please use the S5 thread of this recovery for device specific questions next time.

Thanks :good:
[Android Software Development] Android-Andi:
[MENTION=4666971]Phil3759[/MENTION] i am getting

set_metadata_recursive: some changes failed

flashing a Stock Based Rom. No Problems flashing it on TWRP.

Here is the updater-script, maybe you have any idea: http://pastebin.com/QJuWGkKV
[Android Software Development] Phil3759:
maybe missing files

Look at exact log

CWM fails on missing/non existing files
[Android Software Development] Android-Andi:
Thx, will check tomorrow :)

Any way to patch philz not to fail if a file is missing?

Send from OnePlus One using Tapatalk
[Android Software Development] katinatez:
[MENTION=4666971]Phil3759[/MENTION] I will finally be posting bacon.zip files and images tomorrow, I finally fixed aromafm.zip!!!

http://xdaforums.com/showpost.php?p=55097671&postcount=161
[Android Software Development] yuweng:
i've look at the Part-Source again & finalize that we ONLY need 40 projects out of the total of 473 from the latest cm-11.0 repo to compile out a fully working PhilZ Touch . . .

i wrote a simple script that will only sync the needed projects for building PhilZ Touch no matter how cm projects grows it will still sync only the 40 needed projects . . . :cowboy:

Hopefully, this will get many newbies to port PhilZ Touch to their android devices including DEV that are reluctant to sync the full source . . . :cool:

How-to

Download & unzip it to your [HOME]

chmod 777 PhilZ

Execute it by typing dot forward slash PhilZ -> ./PhilZ

For building PhilZ Touch on any android devices using prebuilt kernel & also cm kernel. You'll need two extra projects for this, just open PhilZ with any text editor & un-remark it . . . :cowboy:

Recommended to build PhilZ Touch on BBQLinux & also tested on Ubuntu too but you'll need to setup the Build Environment first while for BBQLinux you don't need to do that, its built-in . . . :cowboy:

Happy compiling PhilZ Touch . . . :laugh:

Updates

[MENTION=4666971]Phil3759[/MENTION] i have started a new thread here & added you as contributors so that you can participate & share your valuable experience too . . . :good:
[Android Software Development] katinatez:
[MENTION=4666971]Phil3759[/MENTION] here is my new thread maintaining bacon device, I just copied your threads, hope you dont mind.

http://xdaforums.com/oneplus-one/development/bacon-philz-touch-t2861146

This is the stable version with aromafm.zip loading correct, please remove any previous versions in your links.

Thank you
[Android Software Development] Android-Andi:
Thx :) Found the wrong line :)

Another question:

I need to place some modules inside the recovery ramdisk,

"j4fs.ko", and "param.ko".

Both got compiled with the kernel, but how can i move them inside the recovery ramdisk right after compileing?

Else i meight should switch to "TARGET_PREBUILT_RECOVERY_KERNEL" and copy the modules also prebuilt.

Edit:

Or can i change my "init.recovery.device.rc" like this

on early-fs
[COLOR="Red"]- insmod /lib/modules/param.ko[/COLOR]
[COLOR="DarkGreen"]+ insmod [B][U]/system[/U][/B]/lib/modules/param.ko[/COLOR]
mount j4fs /dev/block/mmcblk0p19 /mnt/.lfs wait rw
[COLOR="Red"]- insmod /lib/modules/param.ko[/COLOR]
[COLOR="DarkGreen"]+ insmod [B][U]/system[/U][/B]/lib/modules/param.ko[/COLOR]
[Android Software Development] guhvanoh:
You may have to rename your recovery to fit the standard already established. It should be philz_touch_[version]-[device].zip.

HTH
[Android Software Development] Phil3759:
I would really appreciate a detailed feedback on how you fixed it. A few other devices could benefit from ti and maybe we are able then to patch aroma sources for that

I appreciate all the help you do

Feel free to open a thread with your guide and steps

I will link it in OP

Please follow the naming rules so that I can update goo host

Also, read my above post for the feedback how you fixed Aroma

You can use something like

PRODUCT_COPY_FILES += \
device/lge/geebus/file1:recovery/root/res/file1 \
device/lge/geebus/file2:recovery/root/res/file2
[Android Software Development] katinatez:
[MENTION=4666971]Phil3759[/MENTION] here is my post on how I fixed aroma for bacon, and here is the new naming convention zip file.

http://xdaforums.com/showpost.php?p=55128269&postcount=13
[Android Software Development] Android-Andi:
I know, i did it this way before. But that means i need them prebuilt.

Both get compiled as kernelmodule. Any way to move it to recovery ramdisk while it get compiled with the kernel?

Maybe i will clean my devicetree to shrink it down to the only needed stuff to compile a recovery and use a prebuilt kernel.

Send from OnePlus One using Tapatalk
[Android Software Development] Phil3759:
Look here how I did it for exfat modules when I wasn't using static drivers

https://github.com/PhilZ-cwm6/andro...1ec#diff-ce79deecfd2f89db4ccdd711965c38e6R793
[Android Software Development] Unjustified Dev:
You can use the exhibit shbootimg https://github.com/Team-Exhibit/and...mmit/ff6d978bf00032e0261e47ad60859f0ad45bc81e
[Android Software Development] oscar the grouch:
Just flashed the latest for the moto msm8960 and I have an issue.

I get an error at boot

Says E: unable to create brightness file.

And touch doesn't work but side keys do.
[Android Software Development] katinatez:
[MENTION=4666971]Phil3759[/MENTION] one more thing I noticed about building bacon recovery with twrp kernel is that backup/twrp mode got fixed also. Just mentioning it in case some devs have problem with twrp backups.
[Android Software Development] Phil3759:
interesting in fact

I did not test TWRP mode since a while. Have to check it again. Kernel should have no effect though

Maybe my recent revert to busybox tar
[Android Software Development] oscar the grouch:
Its actually the brightness system file it won't create. Any thoughts on remedying this?