yashsingh1/xdaforums huggingface dataset:
[Android Software Development] rogersb11:
Oh, NO NO man. I wasn't asking for that at all. I know how to do all that. Do it all the time. I was just saying they went together in case in it was relevant. I understand completely. Never knew about this way but you are absolutely correct. Symlinked is the way to go for sure. Thanks again
[Android Software Development] alexp1289:
Do I download from the "hltevzw" folder for Verizon developer edition note 3? Just want to double check.
[Android Software Development] Android-Andi:
[MENTION=4666971]Phil3759[/MENTION]

PhilZ Touch 6.57.2 for p31xx, p51xx and golden

http://www.androidfilehost.com/?fid=23610159112653399
[Android Software Development] rogersb11:
Now I ALWAYS have the sending m second rom image and no boot menu still.
[Android Software Development] ketut.kumajaya:
Attached all files produced by "make recoveryimage" for i777, use it at your own risk!
[Android Software Development] halui:
Thanks for your excellent app. I have a 16 GB Galaxy S4 (I9500) and just installed your recovery.

I am unable to do a nandroid backup because it seems to ask for 5gb of free space while I only have 3 gb available.

Is it possible to save the backup to my external memory card?

Also,I noticed that in the recovery there were two options - sdcard and storage/sdcard1

Which do they indicate ? I don't think either points to my external sdcard.
[Android Software Development] Siberian Tiger:
Sdcard1 is your external [emoji6]
[Android Software Development] halui:
Well damn! Guess its time for some spring cleaning on my sd-card. Thanks anyways.
[Android Software Development] Phil3759:
you can also try to force it to continue backup despite the missing space. With compression, it can be fine (around 30-45% depends on data)
[Android Software Development] juliusssss:
Hi @Phil3759 , thanks for your work.

I compiled your recovery for Xiaomi RedMi 1s (armani), but there is a bug, mount USB storage don't work, i think it's a problem of the device, i compiled TWRP too for this device and it has the same bug.

Greetings.

PD: Sorry for my english
[Android Software Development] Phil3759:
:good:

renamed to philz_touch_6.55.0-armani.img and uploaded to goo

Please try to keep same name format for future updates

If you can open a thread on xda so that I can monitor feedback and link in OP would be great too

Keep same thread title as my other threads for easier monitoring
[Android Software Development] rogersb11:
Files SLIGHTLY different because I used block dev for boot instead of name but same result. Strange. Works on almost any other device I attempt. Assuming it lies in the kernel and recovery being the same image. [MENTION=4666971]Phil3759[/MENTION], is this the repack issue you were speaking of? I know this kernel is very unlike others I've dealt with
[Android Software Development] Phil3759:
i9100, n7000 and most sony devices share same boot/recovery partition

It means: both will run with

same kernel

but different ramdisks

For Samsung at least, your ramdisk must have a special recovery.rc file that is started instead of init.rc when you're booting in recovery mode

For dual boot, you need to hack your init into a shell script

Your faked init will instruct boot steps to expand special files during boot of recovery/rom

New recovery images cannot be repacked with any stock kernel since Samsung didn't update android sources for the S2
[Android Software Development] rogersb11:
OK, that makes more since. Would this be the same reason that your recovery and twrp auto reboot from recovery after 4 minutes but standard CWM does not? Thanks for the response. Also, you mean init.rc or the init binary itself? I know with siyah the init in the ramdisk is only a shortcut pointing to the one in sbin which would also be their recovery. Where mine isn't setup the same way
[Android Software Development] Phil3759:
for dual boot on such a device, I doubt you can go with just an init.rc change

I advise you look at some sony xperia Z dual boot ramdisks and the i9100 ones

The trickiest part is the shell scripting at ramdisk level
[Android Software Development] rogersb11:
Auto reboot may be a different issue but it's a def problem. I disabled govs in kernel that were reported problematic by omni with twrp but I'm having the same issue here. Thanks for any help
[Android Software Development] rogersb11:
[MENTION=4021423]ketut.kumajaya[/MENTION] I'm trying to get dual boot support on my note 2 kernel and was wondering if you could take a look when you got the chance? https://github.com/rogersb11/android_dual_boot_Note2/tree/master
[Android Software Development] ketut.kumajaya:
I need your N7105 "ls -l /dev/block/" output.
[Android Software Development] rogersb11:
u0_a61@t0lte:/ $ su

root@t0lte:/ # ls -l /dev/block/

brw------- root root 7, 0 2014-08-12 04:10 loop0brw------- root root 7, 1 2014-08-12 04:10 loop1brw------- root root 7, 2 2014-08-12 04:10 loop2brw------- root root 7, 3 2014-08-12 04:10 loop3brw------- root root 7, 4 2014-08-12 04:10 loop4brw------- root root 7, 5 2014-08-12 04:10 loop5brw------- root root 7, 6 2014-08-12 04:10 loop6brw------- root root 7, 7 2014-08-12 04:10 loop7brw------- root root 179, 0 2014-08-12 04:10 mmcblk0

brw------- root root 179, 1 2014-08-12 04:10 mmcblk0p1

brw-rw---- system radio 179, 10 2014-08-12 04:10 mmcblk0p10

brw-rw---- system radio 179, 11 2014-08-12 04:10 mmcblk0p11

brw------- root root 179, 12 2014-08-12 04:10 mmcblk0p12

brw------- root root 179, 13 2014-08-12 04:10 mmcblk0p13

brw------- root root 179, 14 2014-08-12 04:10 mmcblk0p14

brw------- root root 179, 15 2014-08-12 04:10 mmcblk0p15

brw------- root root 259, 0 2014-08-12 04:10 mmcblk0p16

brw------- root root 179, 2 2014-08-12 04:10 mmcblk0p2

brw------- root root 179, 3 2014-08-12 04:10 mmcblk0p3

brw-rw---- system radio 179, 4 2014-08-12 06:12 mmcblk0p4

brw-rw---- system radio 179, 5 2014-08-12 05:11 mmcblk0p5

brw-rw---- system radio 179, 6 2014-08-12 04:10 mmcblk0p6

brw-rw---- system root 179, 7 2014-08-12 04:10 mmcblk0p7

brw------- root root 179, 8 2014-08-12 04:10 mmcblk0p8

brw------- root root 179, 9 2014-08-12 04:10 mmcblk0p9

brw-rw---- root system 179, 16 2014-08-12 04:10 mmcblk1

brw------- root root 179, 17 2014-08-12 04:10 mmcblk1p1

lrwxrwxrwx root root 2014-08-12 04:10 param -> /dev/block/mmcblk0p7

drwxr-xr-x root root 2014-08-12 04:10 platform

brw------- root root 1, 0 2014-08-12 04:10 ram0

brw------- root root 1, 1 2014-08-12 04:10 ram1

brw------- root root 1, 10 2014-08-12 04:10 ram10brw------- root root 1, 11 2014-08-12 04:10 ram11brw------- root root 1, 12 2014-08-12 04:10 ram12brw------- root root 1, 13 2014-08-12 04:10 ram13brw------- root root 1, 14 2014-08-12 04:10 ram14brw------- root root 1, 15 2014-08-12 04:10 ram15brw------- root root 1, 2 2014-08-12 04:10 ram2

brw------- root root 1, 3 2014-08-12 04:10 ram3

brw------- root root 1, 4 2014-08-12 04:10 ram4

brw------- root root 1, 5 2014-08-12 04:10 ram5

brw------- root root 1, 6 2014-08-12 04:10 ram6

brw------- root root 1, 7 2014-08-12 04:10 ram7

brw------- root root 1, 8 2014-08-12 04:10 ram8

brw------- root root 1, 9 2014-08-12 04:10 ram9

drwx------ root root 2014-08-12 04:10 vold

root@t0lte:/ #

Also same device, the refinery m recovery you helped me with, when I delete second rom image the option to delete is still there after I delete and there is still hidden folder .secondrom but folders are empty. Also I have i317 but same difference
[Android Software Development] ketut.kumajaya:
[MENTION=5554845]rogersb11[/MENTION] The option always there, no logic to update the menu list.

Please check attached a modified t0lte CM 11.0 boot.img for dual boot. No stock ROM support for now but AOSP. You can try to boot 2 CM kernel compatible AOSP ROM as 1st and 2nd ROM. Use it at your own risk! [MENTION=4666971]Phil3759[/MENTION] Sorry for being out of topic.
[Android Software Development] rogersb11:
Ok, it works. Restored in second recovery. rebooted to first and flashed kernel. gave option for one or two. In second recovery I cant flash anything tho. error E failed to get expected mounts
[Android Software Development] ketut.kumajaya:
Did you merge https://github.com/kumajaya/philz_touch_cwm6/commit/80a476189e21e873f799c22a7150b3e6fd3e9c8e to your source?
[Android Software Development] rogersb11:
Yes, rebuilding now. Also, I have a custom kernel to implement with this as well beyond stock CM. Thanks for the help. I had tried to change the things I needed but apparently was missing something lol
[Android Software Development] juliusssss:
Hi Phil,

I create a new thread for the recovery of RedMi 1S

http://xdaforums.com/android/general/recovery-cwm-philz-touch-t2845710

Greetings
[Android Software Development] rogersb11:
[MENTION=4666971]Phil3759[/MENTION] hey quick question since it's for device you no longer support and is only available with my kernel do I need to start another thread? I'll support it no problem, and credits will be given of course in the OP. I mean for i777. Same question for Note 2. It has dual boot support for my upcoming kernel but it's separate from kernel. Just wanna do it the proper and respectful way. Thanks
[Android Software Development] Phil3759:
Added link to OP :good:

I still support Note 2, just I don't update it for every single release. On next major update, if there is one, it will probably be updated

However, sure, I am not going to add f2fs (old kernel) or dual boot

If you plan to support the devices, you can open a thread for sure, especially if it is dual boot.

If it is only to release updates from git sources without f2fs or dual boot, for users, it is maybe better to post in the same thread. However, you are completely free to open yours

I really don't mind
[Android Software Development] 3L3CTRON:
Please, make a version for LG L7 P705, the version P700 dont let us install P705 ROM @@
[Android Software Development] Unjustified Dev:
[MENTION=4666971]Phil3759[/MENTION] is there a way to build this recovery without touch enabled by default or help me get it working? I've multiple times tried seems I can't get touch working in recovery on the nvidia shield tablet so we must depend on volume and power button. On top of that it's flipped the wrong direction but implementing twrp flipped screen causes the recovery to be too far over to the right except on twrp itself.

I don't yet own one but I found the below inside ramdisk. How would you suport this in recovery? There are more permissions , directory , etc being setup for the touch screen not sure how this works in recovery if it even does. I attached ramdisk device is ardbeg so if you start with that you will see the only ramdisk files imported.

Kernel source if necessary https://github.com/C457/android_kernel_nvidia_ardbeg

#Raydium touch setting
service rm_ts_service /vendor/bin/rm_ts_server
disabled
class late_start
user system
group system input

on property:ro.boot.touch_vendor_id=0
start rm_ts_service
[Android Software Development] Android-Andi:
Read the op and start yourself or ask in your deviceforum. PhilZ Touch support moved to the Device Maintainer, Phil only updates devices he own.

Send from OnePlus One using Tapatalk
[Android Software Development] Phil3759:
I really have very little time the next weeks

To disable touch on start-up by default, the easiest is to edit this line:

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

struct CWMSettingsIntValues touch_to_validate = { "touch_to_validate", NO_TOUCH_SUPPORT };

To completely remove the touch GUI, you disable the PHILZ_TOUCH flag in Android.mk

But you loose a lot of gui entries
[Android Software Development] shoxxy:
Hey ;)

I have compiled philz for lg l90. We have no hardware keys there to boot into recovery, only hardware combo to factory reset. Is it possible to change recovery that it boots normal without automatic factory reset and reboot ????

Thx in advance :)
[Android Software Development] danarama:
Not sure what you mean but what I THINK you're asking is a bootloader change
[Android Software Development] shoxxy:
Hey ;)

Thx for reply

will try it again:

I compiled Philz for LG L90 (D405) the recovery works fine, but to boot normaly into recovery with this device we could only do it by an apk like quickboot or something else. there is no hardware Key Combo to boot recovery.

the only key combos are Download Mode and factory reset, when i do factory reset the device boots make the factory reset and reboot. (so it works as it should)

BUT: in the case of Softbrick the device i could not boot into the recovery to do restore my Backup. because it makes factory reset and reboots....

I want that the recovery boots in "normal " mode when i do the factory reset OVER KEY COMBO WHEN POWER ON THE DEVICE....

Hope that is better to understand, Sorry for bad english ;)

THX in advance
[Android Software Development] danarama:
That's what I thought. Unfortunately that hardware combo is programmed into the bootloader
[Android Software Development] shoxxy:
Thx

yes , :) but i mean if its possible to change the command in recovery from: run factory reset to: normal boot ?

for sure when using factory reset from recovery menue it should do that like before...

;)
[Android Software Development] jurben:
do you mean the hardware combo looks like actually do boot to recovery but before that it always writing recovery command to factory reset and then reboot after that. ?

so you want a custom recovery that not executing those recovery command on start?
[Android Software Development] shoxxy:
No no the hardware combo pop up a menue (lg implemented) that only is there to make a factory reset. The device has no key combo to boot into recovery .
[Android Software Development] Phil3759:
Can you detail EXACTLY what menu you want to change into what? Detailed as after near a page, no one could understand what you want
[Android Software Development] danarama:
I think I've got it. He wants the hardware button combo from the off position (that does a factory reset) to just boot into recovery instead.

Hardware combo must push a command similar to extended command (or however android reset menu works) to recovery, then boots to recovery and executes command.

I think he wants to intercept and ignore the reset part of that command.
[Android Software Development] Phil3759:
[MENTION=5429599]shoxxy[/MENTION]

If what rootSU said is right, you can read below:

The commands are passed to this file:

/cache/recovery/command

The command file is parsed on recovery start at this line:

https://github.com/PhilZ-cwm6/philz_touch_cwm6/blob/cm-11.0-beta/recovery.c#L1164

get_args(&argc, &argv);

You are probably interested in this line:

https://github.com/PhilZ-cwm6/philz_touch_cwm6/blob/cm-11.0-beta/recovery.c#L1178

you can comment it by editing it as below

# case 'w': wipe_data = wipe_cache = 1; break;
[Android Software Development] danarama:
Any so "extendedcommand" is literally an extension of "command"?

makes sense now I read it :p
[Android Software Development] Phil3759:
extendedcommand is the cwm ors equivalent

command file is the aosp recovery commands file
[Android Software Development] shoxxy:
[MENTION=4666971]Phil3759[/MENTION] & rootSU

Yes this should be what i am lookin for. Will take a look when i came from work. Thank you for reply :)
[Android Software Development] rogersb11:
[MENTION=4666971]Phil3759[/MENTION] So I plan to open the Note 2 thread later today for the dual boot recovery. Specific title I need to use? Also since it requires my kernel to work can it be a multi thread or should I just create 2 different ones with each linking to the other? I'm guessing the latter since kernel doesn't really have anything to do with the the actual recovery itself and only pertains to the dual boot. Thanks
[Android Software Development] hachamacha:
Just wanted to mention that [MENTION=5208741]oubeichen[/MENTION]: is taking over my builds from the Toro Philz Touch thread here at http://xdaforums.com/galaxy-nexus/verizon-develop/toro-philz-touch-t2281571 . I mentioned the general format rules and his builds are good.

He did the last build which converted the nexus recovery to f2fs compatibility and I'm low on time lately so just letting you know. Otherwise: I'm still doing the other one's I normally do.
[Android Software Development] jznomoney:
I cannot get aromafm to load in philz recovery on the oneplus(bacon) device. I did a custom build and used the versions hosted on the philz recovery list. See here for info http://xdaforums.com/showpost.php?p=54818766&postcount=889 . I even tried earlier version of aromafm still same issue.
[Android Software Development] rogersb11:
Same issue
[Android Software Development] lost101:
Build: 6.55.0

Device: Moto G "Falcon" (XT1032)

'Clone ROM to update.zip' - Fails to flash: (Status 1)

I realise this issue may affect other devices, but here is a recovery log from my Moto G. I'd really appreciate if this could be made work.

Log covers creating of zip and failed attempt to flash.
[Android Software Development] Kjc99:
Hey guys I've been flashing and using philz recovery for a couple years now and I have a question.. I never worried about this tell now... My buddy was flashing a rom and he happened to loose his imei number.

So my question is when we make a nandroid backup in philz recovery does that back up the efs/imei also? Can he just restore his backup and be OK... Thanks... I know this seems like a noob question but I've never ran into this problem before
[Android Software Development] danarama:
Its a custom backup option so if he didn't explicitly back it up, he can't restore it.
[Android Software Development] Kjc99:
Thanks [MENTION=2872010]rootSU[/MENTION]... Could you let me know how to do it... He just went to backup/restore then back up to sd1
[Android Software Development] danarama:
Its in the custom backup menu. Select the partitions you want to backup
[Android Software Development] katinatez:
Your device maintainer has to compile from source with added fstab entries. If its supported you will find it under custom backup.
[Android Software Development] Phil3759:
On new devices, /system is too big. Currently CWM extracts the file to ramdisk. If you don't have enough space on ramdisk, it will fail

I will look at it later
[Android Software Development] jznomoney:
[MENTION=4666971]Phil3759[/MENTION] any reason for this issue with aromafm on recovery http://xdaforums.com/showpost.php?p=54820723&postcount=5254 ? Any help would be much appreciated.
[Android Software Development] rogersb11:
Is there anything special I need to do to enable f2fs in recovery? I compiled the kernel with it but I wasn't sure about recovery. Thanks
[Android Software Development] hgroove:
And what about SM-900W8 KK 4.4.2?
[Android Software Development] danarama:
What about it?
[Android Software Development] rogersb11:
PhiZ Touch Advanced with Dual Boot and F2FS galaxy note 2

http://xdaforums.com/galaxy-note-2/development-n7105/recovery-t2849091
[Android Software Development] Jhon998:
Any news?
[Android Software Development] juliusssss:
Hi @Phil3759,

I compile CWM for a new device without problems, but when i take your sources i have always the same error:

target thumb C: recovery <= bootable/recovery-philz/recovery.c
target thumb C: recovery <= bootable/recovery-philz/bootloader.c
target thumb C: recovery <= bootable/recovery-philz/install.c
target thumb C: recovery <= bootable/recovery-philz/roots.c
arm-linux-androideabi-gcc: error: ": No such file or directory
make: *** [/home/juliusssss/cm11/out/target/product/hongmi/obj/EXECUTABLES/recovery_intermediates/recovery.o] Error 1
make: *** Se espera a que terminen otras tareas....
arm-linux-androideabi-gcc: error: ": No such file or directory
make: *** [/home/juliusssss/cm11/out/target/product/hongmi/obj/EXECUTABLES/recovery_intermediates/install.o] Error 1
arm-linux-androideabi-gcc: error: ": No such file or directory
make: *** [/home/juliusssss/cm11/out/target/product/hongmi/obj/EXECUTABLES/recovery_intermediates/roots.o] Error 1
arm-linux-androideabi-gcc: error: ": No such file or directory
make: *** [/home/juliusssss/cm11/out/target/product/hongmi/obj/EXECUTABLES/recovery_intermediates/bootloader.o] Error 1

How can i fix them? Thanks :o
[Android Software Development] disneytoy:
Newbee Question

Hi Guys!

I don't have much experience using Philz. I want to update my ROM on a Galaxy Tab 3 8". I have the updated rom and GAPPs. I have Philz 6.19.4.

I was told to just format/System and install. Not being familiar with Philz menu items, I can't seem to find where I can just format /System so I do not destroy my Data, Settings etc.

1) Do I need to update my Philz?

2) What menu items in Philz do I need to do?

I've only before erased stock and installed CM fresh. But now I need to not destroy my Apps/settings.

Thanks
[Android Software Development] danarama:
"Mounts and storage" just like CWM. Not the most obvious location Maybe Phil will change location when the Philz 7 comes out.

Please note, this is then Phil development thread, specifically for development purposes. User related questions should be posted in your device threads linked in post 1.
[Android Software Development] disneytoy:
Thank you rootSU,

Looks like that did the trick. Sorry for posting in this thread, it was what was suggested when I was searching for my issue here.

Thanks!
[Android Software Development] ciquta:
It didn't work on my Galaxy 3 8.0" (T310 - lt01wifi), when I reboot into recovery I get this which I guess is not the Philz Touch recovery:

https://drive.google.com/file/d/0B1onRa8sHi2wZTRicEo4aEtwM3c/edit?usp=sharing

This is the logfile in Odin selecting the file "philz_touch_6.19.3-lt01wifi.tar.md5" as PDA:

<ID:0/005> Added!!

<ID:0/005> Odin v.3 engine (ID:5)..

<ID:0/005> File analysis..

<ID:0/005> SetupConnection..

<ID:0/005> Initialzation..

<ID:0/005> Get PIT for mapping..

<ID:0/005> Firmware update start..

<ID:0/005> recovery.img

<ID:0/005> NAND Write Start!!

<ID:0/005> RQT_CLOSE !!

<ID:0/005> RES OK !!

than a hundred seconds without anything happenend

then finally:

<ID:0/005> Remain Port .... 0

<OSM> All threads completed. (succeed 1 / failed 0)

<ID:0/005> Removed!!

and the green "PASS" appears.

Tried both with "Auto Reboot" checked and unchecked.

Any ideas?
[Android Software Development] danarama:
Wrong thread dude. Device threads are linked in post 1.
[Android Software Development] Vishesh:
Guys can someone port this recovery for micromax canvas HD plus a190?
[Android Software Development] ykkfive:
hi Phil3759

it's me again, but not about bugs this time :D

i just compiled your philztouch cwm "completely from scratch" for the first time (i used to put your recovery file under /sbin into my own recovery image before and that's it). and i have a few quick questions for you which i couldnt find them in the changelog

1/. cwm used to NOT reformatting the partition when restoring backups but now, right? do you think there will be an option to choose from?

2/. i have tried your fs conversion and it looks good and things are completely handled (i mean changing the fs in fstab, remount etc). and my question is, will you save the toggle value in settings also in the future?

sorry if these have been mentioned here or other sub threads before

PS will release a new philztouch cwm port soon, do i need to ask for permissions or do anything, besides putting a link to this thread? I ask since I have seen both unofficial and official philztouch for a particular device before and wondering why

thanks
[Android Software Development] danarama:
Why would you want the toggle saved on? You only use it if you're converting from one to another. You would want toggle set off for 99.9% of recovery boots