yashsingh1/xdaforums huggingface dataset:
[Android Software Development] danarama:
Looking through the N5 thread, I think it was set to "/efs" then elsewhere set in fstab...
[Android Software Development] SevenMaxs:
And you can remove the automatic backup and restore partition /uboot?

Because not necessarily constantly to backup and restore uboot. :)
[Android Software Development] yuweng:
Bro, first you ask about TWRP which was already answered here then you asked about NVRAM again answered here & now you asked about removing uboot even i donno much C/C++ to understand the source code knows that by removing that uboot line at recovery.fstab & fstab.${ro.hardware} & that will not backup/ restore uboot partition . . .

Fyi, i've just tested it & it didn't back up uboot so i suggest that you read more, do your own trial & error rather than asking useless questions here, no offence though . . . :cowboy:

русский
[Android Software Development] TheStrix:
Can the recovery be builded without syncing cm sources??

Or can you build philz recovery for Moto E?
[Android Software Development] MasterAwesome:
Nope... it requires files from external and bionic folder to make Linux executables like clang..as far as I know its not possible.

Regards

MasterAwesome
[Android Software Development] SevenMaxs:
It works!

Да тут все пишут на сленге, даже переводчик не справляется! :D

It's all written in slang, even the translator can not cope!
[Android Software Development] Phil3759:
Happy it fixed it

I am working on something close to what [MENTION=2872010]rootSU[/MENTION] suggested

A way to let people preserve the mount point name
[Android Software Development] jurben:
I have add those lines, and the path in fstab is correct, also have removed whole device out folder but the problem persists. Not solved yet.

I give or not give the flag "voldmanaged=sdcard1:auto" the /dev/block/vold folder is always empty! i pull vold.fstab from /system/etc/ and add to /etc/ (using PRODUCT_COPY_FILES)

dev_mount sdcard /storage/sdcard1 auto /devices/msm_sdcc.2/mmc_host

but didn't give any effect.

I have to learn how to make minivold manage my volume / partition (to make vold_is_volume_available become true).

fyi, My device is based on qualcomm msm8610 (or may be msm8612?)
[Android Software Development] icytalentpwns:
can someone upload the file please? i cant access the download link it wont let me through:(
[Android Software Development] danarama:
No one knows what file you're talking about.
[Android Software Development] icytalentpwns:
Oh sorry. I was talking about the philz recovery but nvm i already download it. Sorry
[Android Software Development] danarama:
OK. It's just there are literally hundreds of "Philz recovery"
[Android Software Development] Phil3759:
Ensure you also have the proper fstab.device in root path
[Android Software Development] ironman.70:
Hello! Where I can download the 6.43.8 version for Galaxy N7100?
[Android Software Development] danarama:
It does not exist.

Monitor this folder:

http://goo.im/devs/philz_touch/CWM_Advanced_Edition/n7100

located from the link in this thread:

http://xdaforums.com/showthread.php?t=2028103
[Android Software Development] Android-Andi:
Inside your "out" folder after compileing.

Gesendet von meinem GT-I8190 mit Tapatalk
[Android Software Development] danarama:
Awww snap!
[Android Software Development] Orphee:
Hi Phil,

In the latest CM11 nightly there is some changes in android_bootable_recovery : http://www.cmxlog.com/11/moto_msm8960/

Do we have to update the recovery each time theses kind of modification made ?

Thank you
[Android Software Development] danarama:
android_bootable_recovery are changes to ClockworkMod recovery. For those of us who compile Philz recovery, we replace android_bootable_recovery from CM11, with android_bootable_recovery from Philz. There is no need to concern yourself with changes in source code in this directory as a user.
[Android Software Development] Orphee:
Ok thank you, I must confess I follow the tutorial to build Phil's recovery, but currently I don't know the difference between /system/bootable/recovery/ and /system/bootable/recovery_cm/

I don't really know what define CWM 6.0.4.8 in sources and when do we have to rebuild Phil's recovery (if needed)

Edit : Maybe I still don't understand, so I ask : If there is a significant change in CWM recovery, Phil has to report it in his github ?
[Android Software Development] danarama:
So your saying you're a compiler / wannabe compiler?

OK so to build CWM, you download all CM11 sources. CWM is bootable/recovery. Everything in there. To build Philz, you replace the entire bootable/recovery with the source on Philz git.

Any changes you see in CM git for bootable/recovery is irrelevant to you. Phil will rebase his git to new version of CWM if he wants to - and if he does, it will be in a new release of Philz.

If you are compiling for a device, you do not need to compile for every release of philz. Many changes will not be required. Usually changes made to CWM are minor anyway, so alone - usually not worth the update on its own.

All you need to now is follow THIS thread and lookout for new versions by Phil. If you see changes you think benefit you / your device, compile new version. Otherwise do not.

Hope this helps.
[Android Software Development] Orphee:
Ok, thank you for this clear explanation... And yes I'm a "wannabe compiler"... :$
[Android Software Development] -PiLoT-:
does anyone have a copy of the image that shows an example of the odin config? the one on front page is 403'ing for me
[Android Software Development] jurben:
Thank you very much ..!

Finally, I can mount usb storage the proper way.

When I search fstab.qcom I spotted device/qcom/msm8610/. then instead of only insert fstab.qcom I managed to state "include device/qcom/msm8610/AndroidBorad.mk" in my device AndroidBorad.mk and "include device/qcom/msm8610/AndroidProducts.mk" in my device's AndroidProducts.mk. and voila.. minivold can finally managed my sdcard, but usb storage use lun0/file instead of lun1/file as i want (lun0/file share as readonly virtual cdrom for device's driver, but I think I don't need to use this driver installer, so i don't interested in how to mount/share that cdrom partition to pc.). By exploring system/vold tree it seems we HAVE TO give %d in the path, and it will be replaced by numbers start from 0. so I do a hack as shown in comented lines there: add %d in the place of 0 in android0, although there is only exist android0,

TARGET_USE_CUSTOM_LUN_FILE_PATH := "/sys/devices/virtual/android_usb/android%d/f_mass_storage/lun1/file"

Finally, I can mount usb storage and unmount the proper way.

My next question will be about:

__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!

__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!

__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!

do those error messages still need concern/attention if qcom time daemon has managed date/time properly?
[Android Software Development] Phil3759:
no, you can ignore them

To fix them tzdata file info must be included from out/root/system... path at boot time
[Android Software Development] jurben:
cm-11.0 source read variable RECOVERY_VARIANT from our device tree (BoardConfig.mk). if there is nothing stated, then the recovery will be built from bootable/recovery source. If there is "RECOVERY_VARIANT := cm" then the bootable/recovery_cm/ source will be used. If there is "RECOVERY_VARIANT := cwm" then the original bootable/recovery/ source will be used even if that folder is renamed to any name.

I try to imitate that. I'd like to have folders in bootable: recovery-cwm, recovery-cm, recovery-philz, recovery-twrp and which variant i want to build i only have to state "RECOVERY_VARIANT := ....". (i think that's easy for PhilZ to do, but takes time for me. :o)

Thanks!

Finally no error messages appears .. only I and some ignorable W messages.

:good: :good: :good:
[Android Software Development] Android-Andi:
Hey Phil! Hey everybody!

Here's my script to convert the recovery.img into a odin flashable *.tar.md5 after compileing.

maybe someone else need it too :) You only need to do some slight modification:

#!/bin/bash

#
# NOTE: NEVER rename a *.tar.md5! Convert the recovery.img again if you want to rename the file!
#
# June 2014 Android-Andi @ XDA
# Thanks to ketut.kumajaya @ XDA
#

#---------------------Device Settings------------------#

# device name in your "out" folder
DEVICENAME1[0]="p3110"
DEVICENAME1[1]="p3100"
DEVICENAME1[2]="p5100"
DEVICENAME1[3]="p5110"
DEVICENAME1[4]="golden"

#---------------------General Settings------------------#

# select "y" or "n"... Or fill in the blanks...

# recoveryname
RECNAME="philz_touch"

# recovery version number
RECVER="6.43.8"

# move the *.tar.md5 and recovery.img?
MOVE=y

# path to move the *.tar.md5 and recovery.img
STORAGE=~/android/roms/recovery

# Your build source code directory path.
# If your source code directory is on an external HDD it should look like:
# //media/your PC username/the name of your storage device/path/to/your/source/code/folder
SAUCE=~/android/cm11

#---------------------Convert & Move Code----------------#
# Very much not a good idea to change this unless you know what you are doing....

for VAL in "${!DEVICENAME1[@]}"
do

echo "Moving to out directory..."
cd $SAUCE/out/target/product/${DEVICENAME1[$VAL]}

echo "Converting..."
tar -H ustar -c recovery.img > $RECNAME"_"$RECVER"-"${DEVICENAME1[$VAL]}".tar"
md5sum -t $RECNAME"_"$RECVER"-"${DEVICENAME1[$VAL]}".tar" >> $RECNAME"_"$RECVER"-"${DEVICENAME1[$VAL]}".tar"
mv $RECNAME"_"$RECVER"-"${DEVICENAME1[$VAL]}".tar" $RECNAME"_"$RECVER"-"${DEVICENAME1[$VAL]}".tar.md5"

if [ $MOVE = "y" ]; then
echo "moveing odin flashable *.tar.md5"
mkdir -p $STORAGE/$RECNAME
mv *".tar.md5" $STORAGE/$RECNAME/
cp "recovery.img" $STORAGE/$RECNAME/$RECNAME"_"$RECVER"-"${DEVICENAME1[$VAL]}".img"
fi

echo "Moving back to source directory..."
cd ../../../..

done

echo "Done!"

[MENTION=4666971]Phil3759[/MENTION] any good idea how to automate makeing a flashable zip?
[Android Software Development] amit.bagaria:
External exFAT card mounted with no write permissions

[MENTION=643734]Philz[/MENTION],

I tried building your awesome recovery for N7100 (Note 2 International) device. I am able to successfully build the recovery as per the instructions provided in your guide. Everything works fine, however I have 64 GB exFAT Sdcard, which mounts fine but unable to write anything. The "mount" command says it has mounted as "rw" but recovery backup, screencapture does not work and fails with error "Permission Denied".

I am using the following locations

for device tree:

https://github.com/PhilZ-cwm6/philz_touch_cwm6_device_vendor/tree/master/device/samsung/n7100

for recovery:

https://github.com/PhilZ-cwm6/philz_touch_cwm6

for patched vold:

https://github.com/PhilZ-cwm6/android_system_vold

Please guide me, if might be missing something specific.
[Android Software Development] johnnyslt:
[MENTION=4666971]Phil3759[/MENTION]

Any thoughts on this error, can it be fixed ?

Restoring sd-ext...
Creating filesystem with parameters:
Size: 2148532224
Block size: 4096
Blocks per group: 32768
Inodes per group: 7728
Inode size: 256
Journal blocks: 8196
Label:
Blocks: 524288
Block groups: 16
Reserved block group size: 135
[B]error: make_ext4fs_internal: cannot lookup security context for /sd-ext/[/B]
E:format_volume: make_ext4fs failed on /dev/block/mmcblk1p2
Error while formatting /sd-ext!
[Android Software Development] danarama:
What device? Are you using sd-ext (ext4 partition on external sdcard for symlinking /data/data, /data/app, data/dalvik-cache on low memory devices)?

If not, this message is standard if you haven't formatted a 2nd partition to your sdcard in ext format. This is a CWM message
[Android Software Development] johnnyslt:
HTC EVO 3D, I'm maintaining it.

Yes, I use a ext4 partition on my external sdcard for data symlinking.

Sd-ext it mounted correctly and working. Formating is the only thing not working.
[Android Software Development] Phil3759:
both questions have the same answer:

https://github.com/PhilZ-cwm6/andro...mmit/a559b91cbf7edde20bf0bbc37fac0ea25ac52512

you need to add needed permissions

Maybe try this

/sd-ext(/.*)?	u:object_r:system_data_file:s0
[Android Software Development] Phil3759:
[MENTION=2872010]rootSU[/MENTION]

can you test deeply the new 6.44.0 - CWM 6.0.4.9 version

Mainly, read this commit message:

https://github.com/PhilZ-cwm6/philz_touch_cwm6/commit/e34b452b55f459adb755113658a4c5b6c6830514

It is a more convenient way to add support for extra partitions in custom nandroid jobs
[Android Software Development] danarama:
Will do
[Android Software Development] joni2012:
No m7 update?
[Android Software Development] danarama:
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/m7
[Android Software Development] joni2012:
Only 6.43.6 no 6.43.8
[Android Software Development] danarama:
So surely that answers your question then!
[Android Software Development] joni2012:
I guess it's still new version m7
[Android Software Development] amit.bagaria:
Great thanks. It worked. Permission issue on extSdCard is resolved. Everything's working as expected. I would have never figured it out on my own. Thanks again.
[Android Software Development] danarama:
[MENTION=4666971]Phil3759[/MENTION] - I am not sure |I am the right person to test this.

Here is why:

Until today, my recovery had the following:

device/lge/hammerhead/fstab.hammerhead

/dev/block/platform/msm_sdcc.1/by-name/modemst1 /efs1 emmc defaults
/dev/block/platform/msm_sdcc.1/by-name/modemst2 /efs2 emmc defaults

and...

device/lge/hammerhead/device.mk
# Recovery Options
PRODUCT_PROPERTY_OVERRIDES += \
ro.cwm.forbid_format=/persist,/firmware,/boot,/sbl1,/tz,/rpm,/sdi,/aboot,/imgdata,/efs1,/efs2 \
ro.cwm.forbid_mount=/persist,/firmware,/efs1,/efs2

But I did NOT have:

EXTRA_PARTITIONS_PATH

even though I thought I did.

So with the above set, I had efs1 and efs2 in my custom backup menu.

If I compile 6.44.0 with no amendments, efs1 and efs2 disappear from my custom menu.

If I edit device.mk like this:

# Recovery Options
PRODUCT_PROPERTY_OVERRIDES += \
ro.cwm.forbid_format=/persist,/firmware,/boot,/sbl1,/tz,/rpm,/sdi,/aboot,/imgdata,/efs1,/efs2 \
ro.cwm.forbid_mount=/persist,/firmware,/efs1,/efs2 \
ro.cwm.backup_partitions=/efs1,/efs2

As per your commit - efs1 and efs2 are back in my custom backup menu.

My concern is because I had never previously set EXTRA_PARTITIONS_PATH, I cannot do a true test of whether it replaces it fine.

I can tell you that my 6.43.6 efs1 and efs2 backups successfully restore on my 6.44.0

Is there anything specific you want me to test? Sorry about my mistake not setting EXTRA_PARTITIONS_PATH previously :(

Essentially my 6.43.6 with device/lge/hammerhead/fstab.hammerhead = 6.44.0 with device/lge/hammerhead/fstab.hammerhead + setprop
[Android Software Development] Phil3759:
The flag was enabled in my sources, I just reverted it on latest commit:

https://github.com/PhilZ-cwm6/philz...54bfdc39e0965/boardconfig/BoardConfig.mk#L569

Since you sync to my sources, you were using it. Else, it is impossible for recovery to process your efs1 and efs2

The advantage of the new method is that you no longer have to have all your extra partitions names in a numbered sequence (efs1, efs2, efs3...)

exp:

your fstab

/dev/block/platform/msm_sdcc.1/by-name/modemst1 /modemst1 emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/modemst2 /modemst2 emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/devlog /devlog ext4 defaults defaults

device.mk

PRODUCT_PROPERTY_OVERRIDES += \
ro.cwm.backup_partitions=/modemst1,/modemst2,/devlog

as you see, you can keep the original mount point now
[Android Software Development] danarama:
Sure Ok.

I can change mine to match above and test if you need?

Ultimately for N5, it needs to remain efs1 and efs2 as users know what it means.

But yep, I get what you're saying. I can use actual mount point in fstab now instead of mounting to /efs1 etc... Then call that using setprop

Would it potentially be possible to code this?

Fstab mounts modemst1 /efs1 and modemst2 /efs2...

Then setprop using."efs" without numbers? And show only 1x efs in custom menu that backs up both modemst1 and modemst2?
[Android Software Development] Phil3759:
if you tested the ro property with efs1 and efs2 and it works, it is ok for me

Grouping partitions under a same menu can be done, but I do not will to extra code for it, really. Not planning to add it to my todo list at all

It will complicate the code and has little logic: advanced users won't be able to control individual partitions
[Android Software Development] unseen1:
hey

i got a little problem with philz_touch_6.41.6-d802 on my lg g2 device.

every time i do a backup or install a zip my screen gets errors they look like "white snow" on a retro tv.

anyone got the same problem or a fix for that?

thanks in advance
[Android Software Development] danarama:
OK great. Yeah, works
[Android Software Development] Phil3759:
I did not update main thread version info because I am still going to submit a few fixes in the next days

So, no hurry to recompile latest version unless you feel like to do
[Android Software Development] firemaker911:
Hello

Is This Kernel Compatible With The Following Android Version I Used?

Hope Without The Low Hands-Free-Speaker-Volume Bug And Low-Ringtone-Volume Bug
[Android Software Development] danarama:
It's not a kernel, it's a recovery. It doesn't care what Rom you're on or have anything to do with any Android bugs you may have.
[Android Software Development] firemaker911:
OK, Thanks For The Answer.

Can You Please Give Me A Tip Of A Working Kernel Without These Bugs And Without Battery-Drain Issue?

Boeffla-Kernel Bizarre The Sound And Agni Drain The Battery....

Thanks
[Android Software Development] danarama:
Not really. I don't have an I9305. Try asking in your device forum. .
[Android Software Development] firemaker911:
Ok, I Try Again
[Android Software Development] SevenMaxs:
PhilZ Touch 6.44.0

I compiled PhilZ Touch 6.44.0 for Zopo Zp990+ (mt6592).

In the list of backup partitions were added - /nvram, /logo.

But when you try to make a backup copy of these partitions - recovery hangs. :confused:

See the screenshots.
[Android Software Development] SO_dank:
Lol.. Is this a good thing for making coffee .. Uhh it's a program not a coffee machine... Ohh OK thanks can you advise me of a good place to get coffee..

Sorry thought that last transaction was funny...
[Android Software Development] :
I tried backing up EFS by starting a custom backup, and unchecking EVERYTHING except EFS, as per what I understood from the instructions.

It says successful in creating .img, and successful in creating 2nd copy. However, when I go to /clockworkmod/backup I don't see the ".efs" folder. Hmm?
[Android Software Development] danarama:
It goes in a dated folder
[Android Software Development] subhashdas:
Error while building Recovery

[MENTION=4666971]Phil3759[/MENTION]

Dear dev we are trying to build latest cwm based philz recovery with kitkat support but we are facing some problem.

we need you help to solve this error

Following are the error that er are facing.

We have build a recovery which boot but upon booting it gives following errors.

when we try to manually mount the /cache, /system and /data partition using the mount & storage menu, it gives following error

at present we can only mount sdcard0 (Internal memory) and sdcard1 (Extrernal

I have attached the error report generated by the recovery along with the recovery (Recovery n Log.7z), along with the current working cwm recovery (JB cwm recovery)

we are unable to take the logcat as the /system is not being mounted.

This is the address of the thread we are working on

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

please suggest what we can do to correct this.

If you need any thing from my side please just ask i would provide it to you as soon as possible.

please help
[Android Software Development] ali.filth:
UPDATE : Galaxy grand Quattro (delo3geur), LG OPTIMUS L7 (P700)

LG OPTIMUS L7 / P700 : http://d-h.st/users/ali.filth/?fld_id=35883#files

SAMSUNG GALAXY GRAND QUATRO / DELOS3GEUR : http://d-h.st/users/ali.filth/?fld_id=35415#files

NEW DEVICE ( HTC SENSATION / PYRAMID ) currently 6.43.0 : http://d-h.st/users/ali.filth/?fld_id=36885#files
[Android Software Development] :
I backed up my EFS and it produced an .img file more than 10MB. However, when I backed up my EFS while installing Omega ROM, it produced a 115KB .tar.gz file. How come there is such a big difference in file sizes?
[Android Software Development] Phil3759:
stop posting same question in many threads!

img: raw partition image

tar: files only
[Android Software Development] MasterAwesome:
Hi,

I was able to compile twrp and get it running with the same mount points but the recovery.fstab v1 but when I compile cwm/PhilZ I get an error saying operation not supported by transport endpoint when mounting system and cache.. Is it something to do with the flags?

Also can you explain what the operation not supported by transport endpoint means?

Regards

MasterAwesome
[Android Software Development] Phil3759:
fstab v1 is not supported anymore in cwm, even as an option
[Android Software Development] MasterAwesome:
Umm..sorry I wasn't clear earlier.. I used the v2 with the same mount points I used for v1 with flags from the /proc/mounts
[Android Software Development] skudo101:
Please add CWM for asus zenfone 4 5 6 :(
[Android Software Development] tomatende2001:
Is there a way to get this recovery for the new HTC One mini 2? There are two things I'm missing on it: a custom recovery and with this root.
[Android Software Development] danarama:
Yes there is, instructions are in post 2.
[Android Software Development] tomatende2001:
Unlike the name of this forum, I am a user. :( Nevertheless, I have experience with the use of recoveries and root. But I can not "build".
[Android Software Development] danarama:
Surely there are "developers" in your device forum?
[Android Software Development] tomatende2001:
Good joke. :D Currently there is no device forum for this brand new device. :(
[Android Software Development] danarama:
Oh. Well you need CWM and CM11 for your device before you can have this recovery, so perhaps you'll need to wait then.
[Android Software Development] tomatende2001:
So I thought that I'm right here.
[Android Software Development] jurben:
Sir, there are 300+ gits inside cm-11 source. Do you have cm-11 manifest that contain only gits needed to build philz cwm recovery? That will reduce the amount of download (repo syncronization)
[Android Software Development] danarama:
I Don't - I just sync the whole lot. That said, its juist teh source code then loads of device trees, but device trees are tiny anyway
[Android Software Development] tomatende2001:
I don't want CM11, I want only the recovery to root my phone. ;)
[Android Software Development] Phil3759:
Just swap bootable/recovery source folder and edit some files as per page 1 dev thread
[Android Software Development] tyvar1:
Thanks for the update! :D
[Android Software Development] mgbotoe:
Out of curiousity, when I back up and go ahead and rename the backup..does everything restore successfully? A problem I had with cwm was when ever i rename the backup, for some very odd reasons I could never successfully restore it

Also, does aroma 1.9 work with this? I notice in the op it stated to use aroma 1.8
[Android Software Development] Phil3759:
Aroma should work without issue

Renaming backup shouldn't affect things unless you use exotic chars (space, *...). Keep alphanumeric chars and eventually _- to avoid issues
[Android Software Development] mgbotoe:
Great, thank you so much for the quick response ^.^ Recommended this to all my fellow flashers, all love it
[Android Software Development] electricsheepdreamer:
Put it in a card reader, right click on it and format it as exFAT on your PC.

Is that Google translator :)
[Android Software Development] saayinla:
Hi OP, the link to P31XX is in a loop and even on your file hoster, its not in the list, could you please have a look at this, Regards.