yashsingh1/xdaforums huggingface dataset:
[Android Software Development] kmdangi:
Problem restoring nadroid back up.

Hello Phil,

On my Samsung Galaxy SHV E210 L, I am using Philz Touch 5 recovery (CWM Base version : V 6.0.4.4)

Is this latest / correct one ?

Secondly for my 4.3 custom rom I face problem : while restoring nandroid back up, phone doesn't go ahead of Samsung splash screen. (tried clering dalvik / cache also tried to factory reset... no success)

Please help.
[Android Software Development] esterado:
How can i see what version i need for my galaxy S4 i9505. Sorry for noob and ot question
[Android Software Development] Phil3759:
Uploaded your 6.55.0 releases

Many thanks
[Android Software Development] danarama:
Link to device specific threads are in post 1
[Android Software Development] jurben:
I've just doing custom restore and regenerating md5 sum, and realize that the menu sequence is:

- partition selection (for custom restore)

- backup folder selection

- file selection

- confirmation.

Is that "file selection" menu really intentional, may be to show the content of the backup folder? I ask this because the file selected there is actually not used. What is used are the selected backup folder and the selected partitions (for custom restore)
[Android Software Development] danarama:
Yes. So you can see the contents and confirm the backup will contain what you wish to restore
[Android Software Development] jurben:
I see now.

But it really made me a little nervous yesterday. I want to restore boot and recovery but just after tapping boot.img it asked confirmation and then processing tbe custom restore. I even thought that boot.img restored to both boot and recovery partitions.
[Android Software Development] danarama:
Well, next time you wont be so nervous.
[Android Software Development] Phil3759:
It is on my todo list to simplify things there...
[Android Software Development] Johnnyy9262:
@phil3759 Having some trouble using open recovery on this recovery, it fails when it is invoked trying to use OTA updater for my rom, would you mind taking a look?
[Android Software Development] jrosero:
Hi [MENTION=4666971]Phil3759[/MENTION] [MENTION=2872010]rootSU[/MENTION]

I just flashed this great recovery but i do have one question. When i tried to restore my Nandroid backup, it didn't see any of my backups. It said no file found. I was using the Traditional latest CWM.

please advise.

Thanks:D:D:D
[Android Software Development] danarama:
Just a quick thing first, I am not affiliated with this recovery. I just build it for Phil. Your post reads as though you think i am part of the "dev team". I am not :)

Second, depends on your device. If you have older than Android 4.2, I dont know.... If you have android 4.2 or newer, well the problem is traditional CWM doesn't store Nandroid on /sdcard. It stores it in /data/media instead of /data/media/0 You have to move it.
[Android Software Development] jrosero:
Thank you very much. I know that you're not a part of the dev team but i just thought that you're one of the most reliable person to asked about this aside from phil. :D:D:D

Thanks again.
[Android Software Development] danarama:
Ah no probs then.
[Android Software Development] Phil3759:
answer in log:

FAQ and above [MENTION=2872010]rootSU[/MENTION] answer
[Android Software Development] Johnnyy9262:
oh sorry i thought it was because it was using sdcard/0/0/emulated instead of sdcard/0/emulated also i meant "open recovery script"

Edit: i don't have sdcard/0/0/ nor /data/media/0/0 just .../0/ so i dont know why it is looking in that location.

I:Update location: /data/media/0/0/Nameless/NamelessCenter/nameless-4.4.4-20140804-d2lte-NIGHTLY.zip

Opening update package...

E:Can't open /data/media/0/0/Nameless/NamelessCenter/nameless-4.4.4-20140804-d2lte-NIGHTLY.zip

(No such file or directory)

Installation aborted.

E:Error installing zip file '/sdcard/0/Nameless/NamelessCenter/nameless-4.4.4-20140804-d2lte-NIGHTLY.zip'

Done processing script file
[Android Software Development] doctor-who:
I have just created clone rom but still didn't tested does it work. Here's screenshots from 2 files I found in zip so pls tell me is it ok?
[Android Software Development] danarama:
Its because /sdcard is mounted at /data/media/0, but USED to be mounted at /data/media in 4.2

Some lazy developers, instead of changing /sdcard to mount /data/media/0, they make it look in /sdcard/0, which would actually be /data/media/0/0 if the recovery was set to use /data/media/0 as /sdcard. This all really starts because official CWM still usesd /data/media as /sdcard.

Toggle to old fashioned sdcard in recovery if you want to use lazy developer solutions to flash things.
[Android Software Development] Johnnyy9262:
Aha! thank you!
[Android Software Development] Phil3759:
6.56.0 on the beta branch:

- merges a few cm changes

- adds a new native screen capture code from TWRP that should fix screen capture for most devices

- use fb2png as a built in lib to spare around 100Kb space (now only used for adb shell screen shots)
[Android Software Development] rongregoryred:
i have no root and i flash the philz_touch_6.07.9-n5100.zip

i got this:

E: failed to verify whole-file signature

E: failed to verify whole-file signature

E: signature verification failed

What will i do? any help?

Sorry guys, for that noob question. im new here.
[Android Software Development] katinatez:
[MENTION=4666971]Phil3759[/MENTION] you are awesome just compiled beta, and screenshots work on the bacon build.

Confirmation number: 4X8670250P269764G
[Android Software Development] Phil3759:
Many thanks for your big generosity
[Android Software Development] Bhargav97:
Hi [MENTION=4666971]Phil3759[/MENTION],

[MENTION=4478781]yuweng[/MENTION] compiled PhilZ-Touch 6.55.0 (beta branch?) for my device galaxy5 (this device being arm11, he must have used that arm11 patch). :)

I liked the way you rearranged menus. :good:

Everything is fine (backup/restore, UI settings) except that some zip files fail to install with a status 0 error. I installed aromafm.zip (which gets installed successfully using CWM and 6.48.4 PhilZ-Touch). Recovery logs doesn't show anything more than:

E: Error in /sdcard/blah...blah..zip

Installation aborted.

(Status 0)

Same happens with many other zip files (like zip file for recovery). Whereas when I installed the latest cm11 NIGHTLY, it got installed successfully. I don't think its an issue with update-binary (being old or something else) because a zip file (to install a init.d script) having older update-binary got installed successfully.

Is it related with changes in PhilZ-Touch (beta-branch) OR is it something messed up from our side?
[Android Software Development] Phil3759:
A full log could still help
[Android Software Development] Bhargav97:
Sure :)

Here: http://pastebin.com/7UsfYWmE
[Android Software Development] varun.chitre15:
Hey [MENTION=4666971]Phil3759[/MENTION]

The latest version I attempted won't boot for taoshan(Sony Xperia L)

Last version which I tried was working was 6.48.4

Any notes did I miss which is why new version isn't booting?
[Android Software Development] ketut.kumajaya:
[MENTION=4666971]Phil3759[/MENTION] Your beta changes break smdk4412 based device compilation, no external gr_mem_surface and vi because both of them are static variables. Fix for my unofficial build https://github.com/kumajaya/android...mmit/4d8b7223c5226711c054760b76e4df3135b94eca .
[Android Software Development] Phil3759:
Wired in fact!

I have no clue. Could be an issue accessing the file properly or in the updater binary

It is hard to guess without any log or more info.

When it hangs in boot, try to see if you have adb shell access

If you have, try to get the log:

adb pull /tmp/recovery.log

If no shell access is available, I advice reverting the changes one by one in your local repo:

git reset HEAD^ --hard

compile each version until you find the commit that caused it. Post here your findings

I am aware of it. It was late for me to prepare a patch. Will commit a fix soon and let you know
[Android Software Development] katinatez:
[MENTION=4666971]Phil3759[/MENTION]

http://xdaforums.com/showpost.php?p=54623379&postcount=101

I tried to compile with omni kernel but I get errors on build.

This is what I tried, commenting out these lines so it could fall back to prebuilt omni kernel I got from Dee_Troys bacon device tree since aroma works flawless on twrp

# Kernel
#TARGET_KERNEL_CONFIG := cyanogenmod_bacon_defconfig
BOARD_KERNEL_CMDLINE := console=ttyHSL0,115200,n8 androidboot.hardware=bacon user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3
BOARD_CUSTOM_BOOTIMG_MK := device/oneplus/bacon/mkbootimg.mk
TARGET_PREBUILT_KERNEL := device/oneplus/bacon/prebuilt/kernel

and

device/oppo/msm8974-common/BoardConfigCommon.mk
#TARGET_KERNEL_SOURCE :=

Also compiled 6.26.1 & 6.41.6 and aroma does not work, so am I missing a flag like the one used for screenshots [BOARD_USE_FB2PNG := true ]?
[Android Software Development] Phil3759:
It is a bit more complicated than this for devices using a custom bootimg mk file

Take a look here for what hlte device needed:

https://github.com/PhilZ-cwm6/philz...4c8f#diff-6fbd250db5c895966ac43df5ca7c31d6R32

You must get the dt.img if your device needs it and set the proper boot image args

If you have dt.img entries in your custom boot image mk file, you will need this script:

https://github.com/xiaolu/mkbootimg_tools

It will let you properly unpack the recovery.img kernel, extract the dt.img file and give you the proper cmd line and arguments to repack with dt.img
[Android Software Development] Phil3759:
6.56.1 on beta branch

Can you check if it looks ok to fix the error when we have a custom graphics.c file?
[Android Software Development] rogersb11:
Hey I was just wondering how I would go about adding some menu recovery options for dual booting and resetting kernel profiles? I'm trying to replicate what the siyah kernel did on jelly been and I know they used your recovery as a base, I believe they used 6.0.2.7(just for reference). It would be for Samsung galaxy s2 i777. I've already built a very stable kernel but obviously can't use dual boot without a custom custom recovery. Thanks for any assistance. I build cm11 with regular cwm already so no issues there.

Edit. There source is not open or I would look there. In twrp I find the ui xml but it's more complicated that when I've worked in rom editing with more referencing so just a little stumped
[Android Software Development] ketut.kumajaya:
I'll check it.

I've been use this recovery for dual boot. Please check https://github.com/kumajaya/philz_touch_cwm6/commits/cm-11.0 and https://github.com/kumajaya/android_device_samsung_lt01-common/commits/cm-11.0-philz This recovery actually no need my mount/umount scripts and fstab*f2fs hack anymore since Phil3759 merge my filesystem detection routine upstream.
[Android Software Development] Phil3759:
Hi,

I could reproduce the bug on my i9100

It is caused by a delay needed to properly connect vold, nothing to do with ui_init() except that it added a delay probably

You could try to use sleep() instead of the extra ui_init()

Anyway, can you try this latest version 6.56.2:

https://github.com/PhilZ-cwm6/philz_touch_cwm6/commit/04d814add1c50c58c6a40126c420429164205c8f

It fixed the issue on my S2
[Android Software Development] Phil3759:
can you try latest update 6.56.2 ?

It fixed a hang on boot caused by vold_connect() failure

It was causing issues on a few devices
[Android Software Development] varun.chitre15:
Cool this fixed it :)

Back to normal. Thanks
[Android Software Development] yuweng:
Haha :laugh: indeed it fix the vold_connect() issue . . .

Fyi, the androidarmv6 team implemented ARCH_ARM_HAVE_TLS_REGISTER & later commits doesn't boot PhilZ Touch on my arm11 anymore . . .

idk, may be this is the reason for Bhargav97 problem as i built it using their last commits at that time (04/ 05th Aug) or kernel problem . . . :o
[Android Software Development] rogersb11:
Ok so I did this, built recovery first and went fine, I then added in you dual boot commit and I keep getting this error and I cant find the correct make file to add this to. It's the first one I added so I assume I need to tell it to make all of the copied files. Thank you so much for your help. Here is the error

Notice file: system/core/libpixelflinger/NOTICE -- /home/brett/android/system/out/target/product/t0lte/obj/NOTICE_FILES/src//system/lib/libpixelflinger_static.a.txt

make: *** No rule to make target `/recovery/root/res/misc/bootmenu.zip', needed by `/home/brett/android/system/out/target/product/t0lte/recovery/root/res/misc/bootmenu.zip'. Stop.

make: *** Waiting for unfinished jobs....

Notice file: external/libpng/NOTICE -- /home/brett/android/system/out/target/product/t0lte/obj/NOTICE_FILES/src//system/lib/libpng.a.txt

As I said I went ahead and built philz recovery and it went fine. Installed and appeared to be working before I tried to implement the dual boot. Any help is greatly appreciated. Thought I was almost done lol
[Android Software Development] ketut.kumajaya:
For me it's a clear error, no recovery/root/res/misc/bootmenu.zip in your device source tree. Please properly adapt https://github.com/kumajaya/android_device_samsung_lt01-common/tree/cm-11.0-philz for your device, recheck all my scripts, bootmenu.zip, and tool.zip . If you do it incorrectly, you risk brick your device!
[Android Software Development] rogersb11:
It IS there under device/Samsung/t0lte and then I copied your ADDED recovery folder and adapted it to my device. Meaning nothing as they were setup the same anyway under dev root folder. Stuff is 100% there. I've triple checked, probably more

Edit: OK here is a copy of my t0lte folder located in cm11 source device/Samsung/

https://www.dropbox.com/s/bdxfowutv9ja4gn/t0lte.zip

Thanks again. You'll see I clearly have it there unless it needs to be some other place.
[Android Software Development] firoz3321:
updated from 6.19 to 6.48, after choosing Reboot Recovery, its now getting bootloops at Samsung logo

Device: Note 2

Please Help

UPDATE:I panicked , but now resolved by updating recovery from ODIN

thank you
[Android Software Development] rogersb11:
Newest beta works great on my girlfriends N2. Built easy and fast
[Android Software Development] varun.chitre15:
Hi [MENTION=4666971]Phil3759[/MENTION]

I built the recovery for a new device. Its Xiaomi Mi3

Codename: cancro

Its fully functional. But there are some visual issues I need to fix. Please have a look at the screenshot below.

http://i1123.photobucket.com/albums/l560/chitrevarun15/cwm_screen002_zps0573f054.png

The text size is too small inspite of selecting highest font size roboto_23x41, also the menu_height is very small.

Is it possible to set these sizes at compile time to a fixed value?
[Android Software Development] Phil3759:
The biggest font is 24x41, ensure it is defined in your device/BoardConfigCommon.mk file and also in graphics.c if you use custom graphics file

To increase menu default menu total height at compile time:

https://github.com/PhilZ-cwm6/philz_touch_cwm6/blob/cm-11.0/libtouch_gui/touch_gui.h#L85

#define MENU_HEIGHT_INCREASE_0 (2 * ((FONT_HEIGHT) - ((FONT_HEIGHT) % 4)))
#define MENU_HEIGHT_INCREASE_MIN (((MENU_HEIGHT_INCREASE_0) / 2) / 4)
#define MENU_HEIGHT_INCREASE_MAX (((MENU_HEIGHT_INCREASE_0) / 2) * 3)

It should normally work fine
[Android Software Development] Phil3759:
Or even better:

#define FONT_WIDTH (libtouch_flags.char_width)
#define FONT_HEIGHT (libtouch_flags.char_height)

/* To change default menu height at compile time:
#define MENU_HEIGHT_INCREASE_0 ((FONT_HEIGHT_ROUNDED) * 1.25)
#define MENU_HEIGHT_INCREASE_0 ((FONT_HEIGHT_ROUNDED) * 1.5)
#define MENU_HEIGHT_INCREASE_0 ((FONT_HEIGHT_ROUNDED) * 1.75)
#define MENU_HEIGHT_INCREASE_0 ((FONT_HEIGHT_ROUNDED) * 2)
...
#define MENU_HEIGHT_INCREASE_0 ((FONT_HEIGHT_ROUNDED) * 3)
*/
#define FONT_HEIGHT_ROUNDED ((FONT_HEIGHT) - ((FONT_HEIGHT) % 4))
#define MENU_HEIGHT_INCREASE_0 FONT_HEIGHT_ROUNDED
#define MENU_HEIGHT_INCREASE_MIN ((FONT_HEIGHT_ROUNDED) / 4)
#define MENU_HEIGHT_INCREASE_MAX ((FONT_HEIGHT_ROUNDED) * 3)
#define MENU_HEIGHT_INCREASE_INIT 4 // initialization value must be constant

// total menu height (font_height + height_increase)
#define MENU_HEIGHT_TOTAL ((FONT_HEIGHT) + menu_height_increase.value)
#define MENU_HEIGHT_TOTAL_DEFAULT ((FONT_HEIGHT) + (MENU_HEIGHT_INCREASE_0))

// Scroll Sensitivity: it is incremented by SCROLL_SENSITIVITY_MIN steps up to maximum of SCROLL_SENSITIVITY_MAX
#define SCROLL_SENSITIVITY_0 ((MENU_HEIGHT_TOTAL_DEFAULT) - ((MENU_HEIGHT_TOTAL_DEFAULT) % 4))
#define SCROLL_SENSITIVITY_MIN ((MENU_HEIGHT_TOTAL) / 4)
#define SCROLL_SENSITIVITY_MAX ((MENU_HEIGHT_TOTAL) * 2)
#define SCROLL_SENSITIVITY_INIT 16
[Android Software Development] Phil3759:
Ok, I pushed a 6.56.6 update with a proper code + comments to explain how to change default height at compile time
[Android Software Development] Android-Andi:
Maybe [MENTION=3814731]katinatez[/MENTION] can use the "dtb" file from TeamWin Bacon source and make proper change on BoardConfig.mk? (instead using the mkbootimg.mk)

https://github.com/TeamWin/android_device_oneplus_bacon/blob/android-4.4/BoardConfig.mk#L41

(sorry, also new to me)
[Android Software Development] Phil3759:
that's exactly what I pointed to

Using a prebuilt kernel, you must use the dt image built along the zImage and manually repack using the custom BOARD_MKBOOTIMG_ARGS

If you have them unpacked, then good, else you must unpack using xiaolu unpacker I pointed to
[Android Software Development] Android-Andi:
Ok, great :) Thanks a lot [MENTION=4666971]Phil3759[/MENTION] :)

---------- Post added at 12:42 AM ---------- Previous post was at 12:07 AM ----------

[MENTION=4666971]Phil3759[/MENTION] a different question:

For Dual-Boot we use a different fstab for "2nd Recovery" (Dual-Boot solution by ketut.kumajatya),

https://github.com/andi34/android_d...-f2fs/recovery/root/res/misc/recovery.fstab.2

It seems like it got loaded correctly, but i am unable to flash a rom:

(...)
recovery filesystem table
=========================
0 /system ext4 /dev/block/loop0 0
1 /efs ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/EFS 0
2 /cache ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/HIDDEN 0
3 /data ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/DATAFS 0
4 /storage/sdcard1 auto /devices/platform/omap/omap_hsmmc.0/mmc_host/mmc1 0
/storage/sdcard1 auto /dev/block/mmcblk1p1 0
5 /storage/usbdisk0 auto /devices/platform/omap/musb-omap2430/musb-hdrc/usb1 0
/storage/usbdisk0 auto /dev/block/sda1 0
6 /boot emmc /dev/block/platform/omap/omap_hsmmc.1/by-name/KERNEL 0
7 /recovery emmc /dev/block/platform/omap/omap_hsmmc.1/by-name/RECOVERY 0
8 /modem emmc /dev/block/platform/omap/omap_hsmmc.1/by-name/MODEM 0
9 /tmp ramdisk ramdisk 0

(...)

-- Installing: /storage/sdcard1/Slim-p3110-4.4.4.build.6.7-UNOFFICIAL-20140722-2234.zip
I:skiping set_bootloader_message: no /misc
E:failed to set up expected mounts for install; aborting
E:Installation aborted.
press any key to continue.

(...)

Full Recoverylog: http://pastebin.com/h0qEv8J7

Any idea what could cause the problem?

Last working for me was 6.50.6, after that it failed.

Haven't tried latest 6.56.6 yet,

but also 6.56.0 and 6.56.2 haven't been working.

Normal PhilZ Touch working great like every time :)
[Android Software Development] Phil3759:
https://github.com/PhilZ-cwm6/philz_touch_cwm6/blob/cm-11.0-beta/roots.c#L936

something is failing here

add a few lines to see exactly what is failing

int setup_install_mounts() {
if (fstab == NULL) {
LOGE("can't set up install mounts: no fstab loaded\n");
return -1;
}

int i;
for (i = 0; i < fstab->num_entries; ++i) {
Volume* v = fstab->recs + i;

// do not unmount vold managed devices (we need this for aroma file manager zip installer to be able to see the vold devices)
if (fs_mgr_is_voldmanaged(v))
continue;
if (strcmp(v->mount_point, "/tmp") == 0 ||
strcmp(v->mount_point, "/cache") == 0) {
if (ensure_path_mounted(v->mount_point) != 0) {
LOGE("mount error %s\n", v->mount_point);
return -1;
}

} else {
if (ensure_path_unmounted(v->mount_point) != 0) {
LOGE("umount error %s\n", v->mount_point);
return -1;
}
}
}
return 0;
}
[Android Software Development] Android-Andi:
Thanks [MENTION=4666971]Phil3759[/MENTION], i'll compile now and test after sleep.

PhilZ Touch 6.56.2 and 6.56.6 for P31XX, P51XX and Golden: http://www.androidfilehost.com/?fid=23610159112651717
[Android Software Development] jurben:
Android Image Kitchen can also unpack to separate dtimage.

http://xdaforums.com/showthread.php?t=2073775
[Android Software Development] Android-Andi:
[MENTION=4666971]Phil3759[/MENTION] tested now:

-- Installing: /storage/sdcard1/Slim-p3110-4.4.4.build.6.7-UNOFFICIAL-20140722-2234.zip
I:skiping set_bootloader_message: no /misc
E:umount error /data
E:failed to set up expected mounts for install; aborting
E:Installation aborted.
press any key to continue.

/data is locked in 2nd recovery.

https://github.com/kumajaya/philz_touch_cwm6/blob/cm-11.0/extendedcommands.c#L4227
[Android Software Development] rogersb11:
OK so I figured it out. It linked with a common so I had to put certain things there. Anyway, it compiled great but results in complete bootloop

[MENTION=4021423]ketut.kumajaya[/MENTION]
[Android Software Development] Phil3759:
please ask ketu about this
[Android Software Development] katinatez:
[MENTION=4666971]Phil3759[/MENTION]

I have all the images, from both twrp & philz 6.56.0 recovery, just dont understand where to add the

BOARD_MKBOOTIMG_ARGS := --dt device/oneplus/bacon/dtb --ramdisk_offset 0x02000000 --tags_offset 0x00000000

If this argument is in the twrp dtb.img already,then all I have to do is copy twrp dtb.img and twrp zImage.img into Philz recovery and repack. Correct?
[Android Software Development] ketut.kumajaya:
If your source code on github, will be easier for me to check.

I guess failed to umount treated as error. I'll check it. BTW your commit https://github.com/PhilZ-cwm6/philz_touch_cwm6/commit/2d923c66c67a270d539c0ad6854f542282be2845 working as expected :good:
[Android Software Development] rogersb11:
ok here it is. For the Note 2 I got a bootloop and had to use odin. On the S2 I got recovery and the new files are in the .cpio but there is nothing new in the menu. Both recoveries compiled bigger than normal so that appears to be correct. The common files are there as well but the devices themselves are the t0lte and i777. Thank you

https://github.com/rogersb11/Samsung-Recoveries

https://github.com/rogersb11/philz_touch_cwm6
[Android Software Development] eris23:
On my 6.56.2 mako build the battery life and time are in red with the battery life displaying [-1%]. Any suggestions how to fix?
[Android Software Development] ketut.kumajaya:
Just "breakfast t0lte" :D I would avoid changes in smdk4412-common but t0lte. Please give me your Note 2 LTE "ls -l /dev/block/platform/dw_mmc/by-name/" output.