yashsingh1/xdaforums huggingface dataset:
[Android Software Development] RVR:
format form mounts and storage gives a reboot

device hl3g ( note 3 neo)

device tree https://github.com/rutvik95/android_device_samsung_hl3g

recovery log http://www.hastebin.com/catitedoco.hs . pl help me fix the errors ... thanx in advance

BOARD: exynos universal 5260
[Android Software Development] dolorespark:
PhilZ for AOSP

I've put together a repo that allows those of us who build AOSP to build PhilZ Touch using our existing AOSP/non-CM Kitkat source tree. Its goal is to isolate CM-related components as much as possible so we can still produce a nearly pure AOSP ROM.

Seven additional repos are required (mostly for additional filesystem support) as well as a modest number of patches to the AOSP code itself (primarily to fix build issues). To keep its footprint as small as possible, most CM-specific libraries are generated from within the 'recovery-philz' source tree rather than modifying the AOSP 'Android.mk' files.

All of the necessary patches can be found in the repo's 'aosp-patches' subdirectory. Also included is a 'local_manifest.xml' which identifies the additional repos needed. Add it to the corresponding directory in your source tree so that a "repo sync" command will pull them in as well as the AOSP repos.

This version of PhilZ Touch Recovery also includes a few enhancements that are not in the official source.

For '/data' partitions whose fs_mgr flags include "encryptable=footer", this code ensures they remain encryptable by leaving space for the encryption-footer when formatting them.

The 'updater' binary includes support for formatting and mounting F2FS partitions.

Wherever possible, relative paths for source files have been eliminated from various 'Android.mk' files to prevent their object files from being scattered across your disk.

If you're interested, see https://github.com/dolorespark/philz_touch_aosp. The readme at the bottom of the page contains additional info about the repo.
[Android Software Development] Phil3759:
there is an issue with your /system partition

Maybe you ar emissing some permissions (selinux, others...)

Ensure you have right selinux permissions in boardconfig and that the kernel allows adb shell to run as root
[Android Software Development] KingP1n:
Is goo.im down?
[Android Software Development] danarama:
Seems OK to me
[Android Software Development] CamoGeko:
Working fine here too.
[Android Software Development] oscar the grouch:
I re flashed philz_touch_6.50.6-moto_msm8960 and touch wouldnt operate. still getting the failed to create brightness error.

i then flashed philz_touch_6.43.8-moto_msm8960 and everything is working again.

weird
[Android Software Development] tsubus:
Just noticed something: PhilZ looks for both extendedcommand and openrecoveryscript, which is fine, but it also executes both. This creates issues because most OTA update apps (such as Paranoid OTA and Omni's OpenDelta) create both files, resulting in a double installation. Would it be possible for it to only execute extendedcommand and ignore openrecoveryscript if both are present?

Thank you.
[Android Software Development] RK:
(Posting here because this might be so for all loki devices)

I have an AT&T galaxy s4. The recovery seems to always think that boot and recovery need to be loki'd. Steps to reproduce:

1) make sure you are running loki'd kernel and recovery.

2) set auto Loki to 1

3) flash a modem or just enter aroma file manager and exit without doing anything

Result: recovery says recovery and boot need lokifying again.

Log attached.

http://pastebin.com/pBvWnKMe
[Android Software Development] TraderJack:
bug report - VZW HTC ONE M8

Posting what may be a bug.

I'm using the HTC M8 VZW version here:

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

I just got my device, S-OFF with weaksauce and firewater, installed this recovery (after a botched, but easily recovered attempt at CWM's M7 recovery by accident).

Everything seems fine - I wanted to get a nandroid stock backup so I did a factory reset from within the recovery and then did the nandoid backup to internal sdcard.

That backup went fine, but then I decided to do the "Clone ROM to update.zip" option using the Current ROM as the source.

After the initial phase of the backup completed, the devices buzzes and then goes into packing it into the ZIP.

It is at this point that the device just hangs.

I have tried twice now and each time it is on a different file that it is deflating. I let it sit for minutes and the progress doesn't move.

Only option is to hard power off (up volume+power for 10+ secs).

Before each attempt I did a full factory reset. After the second failure I tried again, but this time instead of choosing the Current ROM as the source, I chose the previous backup. Upon doing this I saw that there was more than one backup there - of which I was surprised until I realized that the factory reset did not wipe out the sdcard.

I went ahead and wiped out the sdcard from within recovery, rebooted into recovery again and did the standard nandroid.

I then rebooted into recovery again and tried the Clone operation from Current ROM again. Once again failure.

Out of the 3 failures 1 happened when adding boot.img, the other two when doing system.ext4.tar.

I then formatted everything again and this time attempted to use the option to create Clone from previous backup. Same problem...hangs at:

adding: system.ext4.tar (stored 0%)

Sits there for well over 5 minutes and is totally unresponsive to everything but hard off.

Update - tried this to external SD as well...same issue.
[Android Software Development] gtasmodder:
Phliz touch v 6.26.6

cwm v 6.0.4.8

how do i update without brick
[Android Software Development] danarama:
Only flash recoveries for your device. Not others.
[Android Software Development] Orphee:
Hi,

I just built latest Philz Touch Recovery with F2FS support for moto_msm8960 :

http://d-h.st/DCC

:)

FYI : I always need to edit BoardConfig file to enable F2FS for moto_msm8960
[Android Software Development] danarama:
Fork it into your repo on git hub, commit the changes and add the project to your manifest
[Android Software Development] Phil3759:
I wasn't aware that OTA updates behave that way

I will favour extendedcommands over ors

It takes a lot of time to zip a few gigabytes file

For now, I have no time to add a progress

because recovery has no way to be 100% sure if a script in your installer did flash a boot/recovery image

because it is not officially supported and I did not add it in my sources
[Android Software Development] Android-Andi:
[MENTION=4666971]Phil3759[/MENTION] Any way to patch philz not to fail if a file called in updater-script is missing inside the zip like on TWRP?

Send from OnePlus One using Tapatalk
[Android Software Development] katinatez:
Calling all the big guns on this one (devs) I have lost USB-OTG on my bacon recovery even though all the code is there. Also using a prebuilt kernel maybe that has something to do with that.

Here is a link to my github

https://github.com/katinatez/android_device_oneplus_bacon/tree/bacon_philz_recovery

I also added these in my build

https://github.com/PhilZ-cwm6/android_system_vold/tree/cm-11.0

https://github.com/PhilZ-cwm6/android_external_sepolicy/tree/cm-11.0

But over here might be a clue

https://github.com/PhilZ-cwm6/philz_touch_cwm6_device_vendor/tree/cm-11.0

Already added all this

Changes you must do before using device trees:

extra.fstab support: You must add in device.mk

PRODUCT_COPY_FILES += \ $(LOCAL_PATH)/rootdir/extra.fstab:recovery/root/etc/extra.fstab

But have no idea about this

Custom init.rc for recovery: these are the "ini.philz*.rc" files in rootdir/etc.

you must add a flag in BoardConfig.mk:

TARGET_RECOVERY_INITRC := vendor/samsung/common_init/init.philz*.rc

And last bug is crypto, I have one user that is not prompted for decrypt code and SD card shows as zero meaning not mounted.

So recap only 2 bugs left usb-otg and crypto, but every other option in recovery works great.

Any ideas, or help is appreciated

[MENTION=4666971]Phil3759[/MENTION]

I have updated recovery with patched f2fs kernel to support full mount read f2fs support link is here

new updated bacon recovery
[Android Software Development] Phil3759:
it is the update-binary that behaves that way, not recovery by its self

https://github.com/PhilZ-cwm6/philz_touch_cwm6/blob/cm-11.0/updater/install.c#L446

uploading your update :good:

TARGET_RECOVERY_INITRC is used if you need a custom init.rc file, usually Samsung devices need it
[Android Software Development] katinatez:
[MENTION=643734]Philz[/MENTION]3759 any idea on other bugs?
[Android Software Development] Phil3759:
you must find your vold usb otg path and also ensure kernel correctly supports it
[Android Software Development] rogersb11:
Philz touch dual boot for the sprint galaxy note 2. https://www.androidfilehost.com/?fid=23622183712467490
[Android Software Development] RavenII:
I'm backing up to the internal card. As for the speed...it was set to high compression...it took 28 minutes the first time around....only 4.5 minutes the second time around with no compression. 3.3 gigs (Synergy ROM) where CWM takes up ~2 ish...but as you said that might have something to do with Music.

Last question...is there a way to reduce the touchscreen sensitivity?
[Android Software Development] Phil3759:
Set compression to low. You will get around 30% ratio and near same speed

Look in gui settings to reduce scroll sensitivity
[Android Software Development] aeroman:
Hey guys wonderful Recovery, but have the same Problem here without Compression!

A Nandroid Backup or Restore takes too long time, extremly. :crying:

As I said Compression and MD5 Check are disabled in Nandroid Settings.

I need for Backup and Restore to the external Card between 35-43 Minutes. :banghead:

I use exfat Format on external Card,The reason may be?!

(The same Card need with TWRP Recovery 9-11 Minutes.)

My Phone is an SGS4!

Greetings
[Android Software Development] ztotherad:
hey philz, any chance that you can add support for the i605 (Verizon Wireless Samsung Galaxy Note II)?
[Android Software Development] aeroman:
has nobody an Idea or Solution for that Robbing nerves Problem. :confused::confused:

Greetings
[Android Software Development] Phil3759:
No need to ask twice...

Was discussed so many times on i9505 thread.

No fix for now, except maybe getting a better card. TWRP is caching writes, which is not the case in cwm
[Android Software Development] aeroman:
I show on SGS4 thread in OP and search, found 1 entry to the theme,

which could not exactly explain the reason for me?!

you mean, that is a problem, of not caching CWM or because Samsung Sources?!

I try recently an another CWM Recovery, can not remember that it took so long.

My SD Card is from Samsung (Class 10/UHS-1), its not a slow card. :)

Greetings
[Android Software Development] Phil3759:
The issue is probably exfat/drivers/card combo. TWRP caches operations to work around it

However, depends on the cards. Some people have very good results, around 10mn

Again, there are pages of this on the i9505 thread and at least 10 version updates just released to improve speed for most people
[Android Software Development] aeroman:
thanks for the Info. :good: Now that I know the cause, I can sleep in peace again. :)

'll Somehow get over the problem, for it the last version (v5.8.5) works nearly perfectly. ;)

maybe i switch to other format, ntfs etc. exfat sucks on Samsung. :p

Greetings
[Android Software Development] ElRongMcBong:
Hey people!

I found a very simple way, in order to repair the time nose.

Take simply your accumulator for 8-10 hours out (similarly as with the BIOS-Password with the computer delete), to discharge over all condensers and starts thereafter simply completely normally! ;)
[Android Software Development] Phil3759:
Interesting

After that, you can change timezone in recovery without issues?
[Android Software Development] ElRongMcBong:
Yes, afterwards it goes.

With me in the German forum have I however also few few, with which 8-10 hours were still too little.

In the case you could also for 15-20min. the 4 contacts where that accumulator is, with aluminum foil short circuit (naturally without accumulator) and a few times the On/Off Botton presses…

The s4 does not get broken to empty it accelerated only all condensers nevertheless I it would only try to let out the accumulator just over night
[Android Software Development] Phil3759:
Thank you again

Not sure why some versions got their bios date refractory to settimeofday() function I am using!
[Android Software Development] electricsheepdreamer:
Have you tried with OBackup app?

Just in case it might help.

No such problems here on S2.
[Android Software Development] ElRongMcBong:
It is nevertheless no matter why some versions do it and others not, as long as there is a way, in order to repair it ;)

PhilzTouch is the best...i love it in s3 and i love it again in s4
[Android Software Development] Phil3759:
It is an i9505 only issue because Samsung uses shared exfat modules from /system instead of being on the recovery partition

Or, it could be just they still have early buggy exfat ko modules
[Android Software Development] aeroman:
OBackup supports only Backup to an Cloud?

Or what is the difference to a Nandroid Backup,

if don't need Cloud Backups?!

Is it still faster with this recovery? :)

Greetings

tapatalked with my GT-I9505.
[Android Software Development] mrdreamers:
SGH-M919

where'S the download link to SGH-M919 CWM Touch?

(just want to make sure i have the right one):confused:
[Android Software Development] starbucks2010:
Guys,

Last night I made a backup and took me ~40 mins - real pain to wait.

Today I needed to restore that backup and took me also ~50 mins - another pain

Then, I copied the backup files to PC and started to search in them for something unusual, and guess what I have found in /data/data/com.sec.android.gallery3d/temp? ~ 9.000 empty folders.

After deleting these folders, the backup took 23:50 mins.

Best regards.
[Android Software Development] maranello69:
take a look in here
[Android Software Development] LyuboA:
Hi Phil3759 saw you made custom recovery for Tab Pro SM-T320 can you please make one for SM-T325

Thanks

Send from GT-I9505 using Tapatalk 4
[Android Software Development] Tekone:
Is any chance this Philz can be install from Mobile Odin on Samsung epic 4g touch d710??
[Android Software Development] danarama:
All versions are linked in post 1. If there is a version, its there
[Android Software Development] Alexey71:
PhilZ Touch 6.48.4 for Tab Pro 8.4 WiFi (SM-T320)

Screenshots do not work, can not see anything on them all black. More aroma file manager on half of the screen, before it was ok)
[Android Software Development] It_ler:
Odin flashable versions of PhilZ-touch CWM recovery can also be flashed in mobile odin app. .. if you device is already rooted and mobile odin is available for it.

My tapatalk signature:

Device:

SGS5 (SM-G900F)

ROM:

AllianceROM v5.1

Kernel:

Stock G900FXXU1ANG7

Recovery:

PhilZ-touch

Modem:

G900FXU1ANG7

If you have any question about or any issue with your SGS2, just ask in the New members friendly Q&A thread.

... for the SGS5, just ask in the Noob friendly S5 All in one support thread

If you need general help/assistence, please go to XDA-Assist.
[Android Software Development] rogersb11:
How would I disable sensorhub drivers being compiled with the recovery image?
[Android Software Development] AlfredS:
Philz is there any way to make it on a Xperia V? its almost the same as Xperia T ):

supportttt xperia v Lt25i :'c
[Android Software Development] robak1965:
Don't know the proper way to do this. There is no PhilZ thread for my device yet.

Sansung Galaxy S5 Sport - Sprint variant. SM-G860P

Would it help if I link the stock recovery.img?

While auto root is avaiable for this variant, there is no custom recovery yet. I realize that in time the smart people like Phil3759 will take a look at this. Many thanks.
[Android Software Development] firemaker911:
Please Support In The Near Future The Samsung Galaxy Tab3 10.1 P5200....

Many Thanks
[Android Software Development] Tekone:
Of course it has rooted and Mobile Odin installed. Some of the custom recovery will cuz epic 4g touch hard brink
[Android Software Development] DSA:
you should all read the 2nd post of this thread

http://xdaforums.com/showpost.php?p=39433612&postcount=2
[Android Software Development] chautruongthinh:
Recovery for A910 (Pantech VEGA IRON II)

I compiled success Philz touch for my device but i got black screen!! And i tried to compile CWM and it worked fine. I don't what wrong in my device tree, some one please help me fix it!!

My recovery.log here: http://pastebin.com/KrSa8bVT
[Android Software Development] AlfredS:
DSA bro, i actual y forgot i posted here lol, but i used a lil of Brian and the webstites tools and found out that Xperia's T one will work on my Xperia v, got Philz touch running dual recovery!! :3 TWRM and CMW (: http://xdaforums.com/showthread.php?t=2261606

If someone el se needs the link for dual recovery with Philz touch, there you go!

(Sorry for my bad english and for not taking the time to read carefully! :P )

Lets make Xperia V live longer, thanks devs! (:
[Android Software Development] KingP1n:
Does philz for 6.48.4 toltetmo support f2fs?
[Android Software Development] katinatez:
Only if device maintainer placed support for f2fs.

---------- Post added at 10:12 AM ---------- Previous post was at 10:05 AM ----------

Did you add any of this on recovery-philz/boardconfig? Or you could place it in device tree boardconfig.

else ifeq ($(TARGET_PRODUCT), cm_bacon)
TARGET_COMMON_NAME := One Plus One
TARGET_USERIMAGES_USE_F2FS := true
BOARD_USE_FB2PNG := true
TARGET_SCREEN_HEIGHT := 1920
TARGET_SCREEN_WIDTH := 1080
BRIGHTNESS_SYS_FILE := "/sys/class/leds/lcd-backlight/brightness"
[Android Software Development] Phil3759:
wired

I see nothing bad in your log

Can you try removing that custom icon png? could be your code changes causing the issue
[Android Software Development] robak1965:
Well, as a matter of fact i did! And it's all Greek to me. I'm no developer or programmer.

I was referred to this thread by another recognized contributor who suggested i ask if it could be done.

I'm willing to try to gather whatever info is needed from my device, i don't have a clue what it takes.

Sorry if i offended, not intentional.
[Android Software Development] chautruongthinh:
- My custom icon work great with other device. I only get error with Vega Iron 2. I think my device got problem becasue it use Super AMOLED!!

- I tried to remove custom icon png but i got same problem!!

---------- Post added at 04:33 PM ---------- Previous post was at 04:30 PM ----------

I added these to recovery-philz/boardconfig?:
[Android Software Development] danarama:
The easiest thing to do is find someone who has a history of compiling source code. The easiest way is if you have CM11 source code available for your device. The OP of this thread [MENTION=4666971]Phil3759[/MENTION]) cannot help you without CM11 source. So someone with your device needs to compile CWM from CM11 code and see if it works.

If it does work, [MENTION=4666971]Phil3759[/MENTION] may be able to compile it for the device, if there is enough reason to do it (won't compile for 3 users) and if he has time... Otherwise, whomever got CWM working should easily be able to make Philz

If there is no CM11 source code available, it becomes even more difficult. You definitely need a device porter with your device to do that work.

Bets thing to do is look around your own device forum and see if you can find anyone with developer status.
[Android Software Development] chautruongthinh:
[MENTION=4666971]Phil3759[/MENTION], [MENTION=2872010]rootSU[/MENTION]

I have just compiled CWM Advance edittion 6 and it work great with my device!! I tried to compile again Philz Touch and got not backlight. I think libtouch_gui has problem with my device!! Please help me fix it!!!
[Android Software Development] dolorespark:
In your build, look in 'recovery/root/res/images' for 'stitch.png' and 'virtual_keys.png'. My guess is that they are missing. If so you have to add them to "PRODUCT PACKAGES" in your 'device.mk'. For example:

ifeq ($(RECOVERY_VARIANT),philz)
PRODUCT_PACKAGES += \
stitch.png \
virtual_keys.png
endif

I had to add quite a few packages to get everything I wanted/expected to be in my distro. You may want to compare your build against one of the official builds to see if you have everything you should. If not, find the appropriate 'Android.mk' to get the correct name, then add it to the package list.

Note: I'm building PhilZ Touch from an AOSP source tree. The most appropriate place to add these packages may be different in your CM tree.
[Android Software Development] chautruongthinh:
i checked ramdisk of recovery.img and it don't missing images!! I don't know why the backlight of my device is not bright with Phiz touch!!??
[Android Software Development] JoshR81:
Hello,

This doesn't work for me. It did unbrick my phone though. But after installing this, it didn't boot into recovery it just started up normally.

So I did as you suggested, unticked auto reboot, but this doesn't solve the problem. When I hold down the 3 buttons, in the top left hand corner is says:

Recovery Booting

Recovery is not SEANANDROID ENFORCING

Set Warranty Bit: recovery

And then the screen goes black until I release the buttons, which makes it start up again.

Sometimes it doesn't show that message, the screen will just go black and it will reboot.

Anyone know a solution?

I would problem be happy just to use the phone as is, and forget about having a recovery mode. Except the reason I bricked the phone in the first place was because I was trying to solve "not registered on network" problem.
[Android Software Development] DSA:
When you see the 'recovery booting' writing, let go of the buttons.

You are holding them down too long and overriding your initial press
[Android Software Development] Phil3759:
are you using the prebuilt libtouch or you're compiling it with the sources

I think the prebuilt is still a few versions behind

Also, it could be a brightness issue

try to navigate in menus to reboot for example into recovery (key up, key power, key power) and see if it does.

Means the GUI is there, but just not shown: probably a graphics.c issue or the brightness setting
[Android Software Development] chautruongthinh:
I can use recovery but i can see becasue it very low bright!!! I sure the brightness have the problem.

You can check my device in here: https://github.com/chautruongthinh/device_pantech_ef63k

and help me fix it!!
[Android Software Development] Phil3759:
can you try:

adb shell
echo 255 /sys/class/leds/lcd-backlight/brightness

if you have no adb shell, try it in aroma console

let me know if it enhances your brightness
[Android Software Development] chautruongthinh:
i tried echo 255 to /sys/class/leds/lcd-backlight/brightness but i dont see any change!!
[Android Software Development] JoshR81:
Legend! Surprised this was such an easy solution, thanks man.

BTW, the text comes up all together, it doesn't show "recovery booting" and then the other text. Also, the text stays on the screen for less than a second before the screen goes black.

Seems a bit odd to me, but all sorted now. :)
[Android Software Development] Phil3759:
it means your brightness path is not properly set for some reason!

try to echo some higher numbers maybe. Some devices have a different brightness range than 0-255. Normally, recovery tries to get the max-brightness path here:

https://github.com/PhilZ-cwm6/philz_touch_cwm6/blob/cm-11.0/libtouch_gui/gui_settings.c#L462

maybe you have another max brightness path

Try to list the contents of your brightness directory and see the contents, especially any eventual max*.* file

adb shell
cat /path/to/brightness/files
[Android Software Development] chautruongthinh:
I saw philz background in 1 sec and then i got blackscreen!

I tried to remove brightness path and i got blackscreen with CWM & Philz Touch. I sure my brightness path is the correctly, because i can echo to brightness value in my rom!!