yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] yuweng:
No mislead . . .

shoxxy has success using this guide to build one for his Qualcomm SoC . . . :good:

And i've got Phil3759 blessings & support too . . . :good:

How would you feel if you told someone that for him to reach his destination he would need to turn right & this person came back & says he turn left & couldn't find the place . . . :eek: i don't want to use that word whatever you call it . . . :cool:
[Miscellaneous Android Development] vampirefo:
The title says for any android device, not just for arm architecture, I get people taking wrong turns all the time on my threads, lol. Anyway good thread.
[Miscellaneous Android Development] yuweng:
Updated as your wish . . . :cool:
[Miscellaneous Android Development] DustArma:
I'm getting the following error when attempting to build the recovery for my B1-A71

No private recovery resources for TARGET_DEVICE B1_A71
device/Acer/B1-A71/boot.mk:13: *** las instrucciones comenzaron antes del primer objetivo. Alto.

Attached compile.log
[Miscellaneous Android Development] yuweng:
it took me quite awhile to duplicate this problem, Windows users take note . . . :cowboy:

The problem is b'cos you're using CR/ LF while Linux uses only LF that's why you get this error . . . :cool:

To view CR/ LF, at geany -> View -> Show Line Endings.

Your boot.mk should only contain LF then it'll work meaning do all editing at BBQLinux not at Windows.
[Miscellaneous Android Development] DustArma:
Well okay, I was doing copypasting from my windows host to the bbqlinux guest, I guess that's how the linebreaks got in.

I'll try now doing it entirely from BBQLinux.
[Miscellaneous Android Development] DustArma:
So I started completely from scratch with a freshly installed BBQLinux, and did the whole procedure from inside it, and I'm still getting the same error.

Attached is compile.log

Later I can attach the device files if they are needed.
[Miscellaneous Android Development] yuweng:
Use the boot.mk from here, i've tested before uploading it, downloaded again from that post, tested again when andrman1 complains about it & i've just tested it again before the previous reply to you, it builds without that error & i thought you would've know to use that copy . . .

Anyway, if same error then zip all your files, attach to your post & i'll check it . . .
[Miscellaneous Android Development] DustArma:
Ugh, this is driving me crazy, after replacing the boot.mk file it started giving me another error

[dustarma@bbqlinux cm11]$ make recoveryimage
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.4.4
CM_VERSION=
TARGET_PRODUCT=full
TARGET_BUILD_VARIANT=eng
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a
TARGET_CPU_VARIANT=generic
HOST_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-3.16.1-1-ARCH-x86_64-with-glibc2.2.5
HOST_BUILD_TYPE=release
BUILD_ID=KTU84Q
OUT_DIR=/home/dustarma/cm11/out
============================================
/bin/bash: prebuilts/tools/linux-x86/sdl/bin/sdl-config: No such file or directory
/bin/bash: prebuilts/tools/linux-x86/sdl/bin/sdl-config: No such file or directory
/bin/bash: prebuilts/tools/linux-x86/sdl/bin/sdl-config: No such file or directory
/bin/bash: prebuilts/tools/linux-x86/sdl/bin/sdl-config: No such file or directory
No private recovery resources for TARGET_DEVICE generic
build/core/tasks/kernel.mk:91: **********************************************************
build/core/tasks/kernel.mk:92: * Kernel source found, but no configuration was defined *
build/core/tasks/kernel.mk:93: * Please add the TARGET_KERNEL_CONFIG variable to your *
build/core/tasks/kernel.mk:94: * BoardConfig.mk file *
build/core/tasks/kernel.mk:95: **********************************************************
target Prebuilt: virtual_keys.png (/home/dustarma/cm11/out/target/product/generic/obj/RECOVERY_EXECUTABLES/virtual_keys.png_intermediates/virtual_keys.png)
Install: /home/dustarma/cm11/out/target/product/generic/recovery/root/res/images/virtual_keys.png
make: *** No rule to make target 'bootable/recovery/ntfs-3g/../../../external/ntfs-3g/src/ntfs-3g.c', needed by '/home/dustarma/cm11/out/target/product/generic/obj/RECOVERY_EXECUTABLES/mount.ntfs-3g_intermediates/../../../external/ntfs-3g/src/ntfs-3g.o'. Stop.

I tried running lunch again after that, and then it started giving me the "recipe commences before first target" error again, I tried replacing the boot.mk file again and it kept giving me the same error.

After that I tried compiling using the MediaTek device from the zip file you uploaded, using

lunch cm_MediaTek-en
make recoveryimage

AND IT'S GIVING ME THE SAME "recipe commences before first target" ERROR.

I haven't even touched any of the files from the MediaTek folder other than extracting them to ~/cm11/device/
[Miscellaneous Android Development] shoxxy:
Make sure you have:

BOARD_USE_NTFS_3G := false

in your boardconfig.

Also:

lunch cm_MediaTek-eng

is the right command
[Miscellaneous Android Development] yuweng:
As shoxxy has highlighted, you are using the wrong lunch command . . .

Do not delete your existing files, just extract attachment to ~/cm11/device , copy acer script to [HOME] & execute it by typing ./acer <- dot forward-slash acer. It builds just right almost to the max size of your recovery partition, 5.9Mb.

the problem is that you followed exactly as OP, those are example, do not copy & paste, it has many comments in it & you forgot to remove it . . . :cowboy:

BoardConfig.mk

TARGET_USE_CUSTOM_LUN_FILE_PATH := "/sys/devices/virtual/android_usb/android0/f_mass_storage/lun%d/file" [COLOR="Red"]<- Credits to RD chrmhoffmann[/COLOR]

You are using recovery.fstab v1 instead of v2 refer to post #2 for more details.

Just found out, for some reason, when the codes examples are wrap with

& hidden at [COLOR="Blue"]OP[/COLOR], they are not showing the [COLOR="Blue"]\[/COLOR] back-slash properly . . .

i have to use two [COLOR="blue"]\\[/COLOR] however next edit & it'll be automatically removed.

Conclusion : [B]MTK[/B] users download & use the one [URL="http://xdaforums.com/showpost.php?p=55312051&postcount=20"]here[/URL]

If still you couldn't get it to work then i suggest that you use my porting tool [URL="http://xdaforums.com/showthread.php?t=2748169"]here[/URL] . . .
[/hide]
[Miscellaneous Android Development] DustArma:
Recovery built, and it boots successfully, I need to do some tests now.

I also have to fix some bugs:

The recovery displays in inverted landscape mode when it should display in portrait, the touchscreen seems to be improperly calibrated and "rotated" 90°s compared to what's displayed. I also need to make it see my microSD Card. Nevermind, it's detecting the microSD card properly and is right now doing a backup there.
[Miscellaneous Android Development] katinatez:
The display is easy fix just add this code in boardconfig.mk

TARGET_SCREEN_HEIGHT := 1920
TARGET_SCREEN_WIDTH := 1080

Adjust your screen height and width size to your device, you could look into your buil.prop file inside your device for correct settings of display.

Congratulations on build!
[Miscellaneous Android Development] DustArma:
I had my height and width as 1024 and 600 respectively.

Right now I'm building with those parameters inverted, so 1024 for width and 600 for height

*EDIT*

Oh nice, nandroid backup and restore from external storage seems to have been successful!

Well, inverting the resolution didn't seem to do anything, I'd rather have the recovery in portrait mode than in inverted landscape, but at the very least I need to fix the touchscreen calibration.
[Miscellaneous Android Development] katinatez:
test aroma file manager
[Miscellaneous Android Development] yuweng:
You are not digesting the infos, my friend, that's why at OP mentioned . . .

For your case . . .

TARGET_SCREEN_HEIGHT := 1024
TARGET_SCREEN_WIDTH := 600

OR

TARGET_SCREEN_HEIGHT := 600
TARGET_SCREEN_WIDTH := 1024

Make sure you manually remove your B1_A71 device folder at $OUT before recompiling or your flag changes will not be picked up.

~/cm11/out/target/product/[COLOR="Blue"]B1_A71[/COLOR] [COLOR="Red"]<- just manually delete [COLOR="Blue"]B1_A71[/COLOR] folder[/COLOR]
[COLOR="Blue"]OR[/COLOR]
cd ~/cm11
make clean
cd
./acer

Or edit the commands & follow katinatez one liner command at the next post . . . :good:

However, your photo shows that your compiled PhilZ Touch has tiles background meaning your actual res may be 800x1280 or 1280x800 . . .

Again its mentioned . . .

Source

---------------------------------------

Notes to ALL

The actual intention of this thread is NOT building PhilZ Touch for MediaTek devices only BUT for all ARM android devices that doesn't have CyanogenMod or PhilZ Touch . . . :cool:

So start posting your questions ONLY when you have gone through all of it & you cannot find the answer BUT again, i may not know all the answers . . . :o

Its best that you post all questions regarding PhilZ Touch at Q&A here as this is where most of the DEVs hang out ONLY when you can't find your answers elsewhere . . . :cowboy:
[Miscellaneous Android Development] katinatez:
Just dropping a suggestion for starting the build with a one liner command. Every command can be linked with &&

make clobber && . build/envsetup.sh && lunch cm_bacon-userdebug && make -j8 recoveryimage RECOVERY_VARIANT=philz

This last part is for building branch 4.4 RECOVERY_VARIANT=philz

Also to add credit to compiler go to this file extendedcommands.c on line 3420 if you are using 6.57.5

//ui_print(EXPAND(BUILD_DATE)"\n");
ui_print("Compiled %s at %s\n", __DATE__, __TIME__);

ui_print("Compiled by katinatez @XDA" "\n");

Enjoy :D
[Miscellaneous Android Development] DustArma:
After following [MENTION=4478781]yuweng[/MENTION]'s suggestions, the touchscreen is working properly within the recovery, but not within AromaFM
[Miscellaneous Android Development] katinatez:
Build twrp for your device, then grab the kernel and dt.img and then compile philz recovery with a prebuilt kernel. That will fix it. Building with different kernels helps to fix loading aroma file manager properly.
[Miscellaneous Android Development] katinatez:
I am sorry I did not read your post correctly. To fix touch screen in aroma add one of these lines into boardconfig.mk

one at a time

, usually its the first line of code that fixes it.

TARGET_RECOVERY_PIXEL_FORMAT := "BGRA_8888"
TARGET_RECOVERY_PIXEL_FORMAT := "RGBX_8888"
TARGET_RECOVERY_PIXEL_FORMAT := "RGB_565"
[Miscellaneous Android Development] Santhosh M:
Also to add credit to compiler go to this file extendedcommands.c on line 3420 if you are using 6.57.5

//ui_print(EXPAND(BUILD_DATE)"\n");
ui_print("Compiled %s at %s\n", __DATE__, __TIME__);

ui_print("Compiled by katinatez @XDA" "\n");

Enjoy :D[/QUOTE]

[MENTION=3814731]katinatez[/MENTION] If its the latest version how can it be added. This is the latest extendedcommands.c

https://github.com/PhilZ-cwm6/philz...945a82c9968ec2eeb5bf0c9e35/extendedcommands.c

Generally after which part can it be added?
[Miscellaneous Android Development] katinatez:
[MENTION=3814731]katinatez[/MENTION] If its the latest version how can it be added. This is the latest extendedcommands.c

https://github.com/PhilZ-cwm6/philz...945a82c9968ec2eeb5bf0c9e35/extendedcommands.c

Generally after which part can it be added?[/QUOTE]

Same line #3420, I just did it last night.
[Miscellaneous Android Development] werty100:
Maybe is wrong

hi i finally install BBQLinux and am running the script...

But i think it is downloading all CM11 source:

it is downloading more and 41 projets is is in 150 project why?¿

---------- Post added at 09:30 PM ---------- Previous post was at 09:17 PM ----------

If you have another language in linux system create in HOME a folder call Documents and script will work perfectly
[Miscellaneous Android Development] werty100:
Why this error bootloader?¿

target thumb C: recovery <= bootable/recovery/bootloader.c

/bin/bash: -: No existe el fichero o el directorio

target thumb C: recovery <= bootable/recovery/install.c

build/core/binary.mk:512: recipe for target '/home/werty100/cm11/out/target/product/p8/obj/EXECUTABLES/recovery_intermediates/recovery.o' failed

make: *** [/home/werty100/cm11/out/target/product/p8/obj/EXECUTABLES/recovery_intermediates/recovery.o] Error 1

make: *** Se espera a que terminen otras tareas....

/bin/bash: -: No existe el fichero o el directorio

build/core/binary.mk:512: recipe for target '/home/werty100/cm11/out/target/product/p8/obj/EXECUTABLES/recovery_intermediates/bootloader.o' failed

make: *** [/home/werty100/cm11/out/target/product/p8/obj/EXECUTABLES/recovery_intermediates/bootloader.o] Error 1

/bin/bash: -: No existe el fichero o el directorio

build/core/binary.mk:512: recipe for target '/home/werty100/cm11/out/target/product/p8/obj/EXECUTABLES/recovery_intermediates/install.o' failed

make: *** [/home/werty100/cm11/out/target/product/p8/obj/EXECUTABLES/recovery_intermediates/install.o] Error 1

make: *** wait: No hay ningún proceso hijo. Alto.

build error!
[Miscellaneous Android Development] yuweng:
Always refer to the Q&A thread here & solution here . . . :cowboy:

Updates

You'll need three more projects to build a working PhilZ Touch with Part-Source. At the Part-Source script un-remark Line 62, 64 & add a new one as below . . .

grep -v ntfs-3g ~/Documents/x>~/Documents/x.tmp;mv ~/Documents/x.tmp ~/Documents/x
grep -v exfat ~/Documents/x>~/Documents/x.tmp;mv ~/Documents/x.tmp ~/Documents/x
grep -v [COLOR="Blue"]fuse[/COLOR] ~/Documents/x>~/Documents/x.tmp;mv ~/Documents/x.tmp ~/Documents/x
[Miscellaneous Android Development] seraser:
I want compile for coolpad 9976a but only is avalaible bbqlinux 64bits, is not possible with 32 bits?

Thank you
[Miscellaneous Android Development] yuweng:
Guys, this is the development not the general Q&A thread so pls brush up your knowledge first or simply google it . . .

And codeworkx already mentioned it here . . .
[Miscellaneous Android Development] andrman1:
I've succesfull build philz recovery for my mediatek device with a lot of difficulties.

Is there any difference between make -j3 recoveryimage and make recoveryimage?

My configuration is budget with CPU celeron and I had error on compiling but i don't remember with this argument -j3 or without therefore I'm asking.

At first compiling compiling takes long time but I hope from another compiling to take less according for ccache option.
[Miscellaneous Android Development] StefDrums:
gsm.mk not found

Hello,

I'm trying to compile Philz Touch recovery for my Samsung S7582. I've done all the passages, and verified them many times, but the script blocks always at the same point.

When I try to do

lunch cm_S7582-eng

in bbqlinux terminal, it shows me this error:

build/core/product_config.mk:239: *** _nic.PRODUCTS.[[device/Samsung/S7582/cm.mk]]: "vendor/cm/config/gsm.mk" does not exist. Stop.
Device S7582 not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Repository for S7582 not found in the CyanogenMod Github repository list. If this is in error, you may need to manually add it to your local_manifests/roomservice.xml.
build/core/product_config.mk:239: *** _nic.PRODUCTS.[[device/Samsung/S7582/cm.mk]]: "vendor/cm/config/gsm.mk" does not exist. Stop.

** Don't have a product spec for: 'cm_S7582'
** Do you have the right repo manifest?

After this error, I tried to do

make -j8 recoveryimage

but i give

build/core/product_config.mk:239: *** _nic.PRODUCTS.[[device/Samsung/S7582/cm.mk]]: "vendor/cm/config/gsm.mk" does not exist. Stop.

Please, can someone tells me what I done wrong and what is this gsm.mk file?

Thanks!
[Miscellaneous Android Development] Santhosh M:
This guide is to compile recovery for MTK device and i don't think your device is a Mediatek device. Plus if it's a ARM architecture device you haven't commented out certain things mentioned in first post. That's why you have been getting this errors. Plus on top of that you haven't read the guide at all. You no need to download repo from CM tree as you need to create device skeleton files using mkvendor.sh from your stock boot.img.
[Miscellaneous Android Development] :
If at lunch command the builder show error finding device and is looking for it on github, then you need a sh file in your device tree to add the device to lunch list.

vendorsetup.sh which contain a line like this:

add_lunch_combo cm_S7582-eng

. If you have this one, next time you will do

. /build/envsetup.sh

it will be listed on lunch commands list, and on lunch command it won't be that error anymore.

Other thing is that you have a line in your cm.mk file

$(call inherit-product, vendor/cm/config/gsm.mk)

which doesn't work because maybe you have an incomplete building folder. Try to delete /vendor/cm folder and do a repo sync again. Anyway that line is from template device folder and that file gsm.mk it points to is blank (empty). It's safe to be deleted - the line I mean.

I see you use -j8... probably you have a six core CPU at least :good:
[Miscellaneous Android Development] Santhosh M:
Didn't you notice that it hasn't compiled and stopped at the above mentioned errors. Correct the errors above and only then it will compile
[Miscellaneous Android Development] :
These errors are somewhere in recovery. It's possible that one of the prebuilt modules to have a problem, or something next to them. Check if you have a complete functional recovery folder (maybe something's missing), or if there are some changes you have to make in CM-11.0 code. Check the recovery README or the author's thread.
[Miscellaneous Android Development] yuweng:
[MENTION=4704580]StefDrums[/MENTION] Already mentioned at post #2, don't let the DEVs trying to help you guessing what device spec you have . . . :rolleyes:

find: `bootable/recovery/[COLOR="Red"]res-480[/COLOR]': No such file or directory

Santhosh M already given you hint above so do you have below at your BoardConfig.mk . . .

TARGET_SCREEN_HEIGHT := 800
TARGET_SCREEN_WIDTH := 480

And always use hide button to hide your extremely long compile log to keep this thread easier to follow or you can just attach your compile logs . . .

And fyi, i've just build PhilZ Touch again today just to make sure it is build-able . . .

And pls read this & since your signature has link to CWM then obviously PhilZ Touch will boot but if your device uses custom boot.mk & you didn't specify it at BoardConfig.mk then obviously it won't boot. Ask the original CWM DEV for the device tree, it will be easier for you . . .
[Miscellaneous Android Development] roshan2989:
i cant seems to found the "BOARD_RECOVERYIMAGE_PARTITION_SIZE := 0x1400000"..?

just try this method on adb and teminal cat /proc/mtd its show "no such directory..?
[Miscellaneous Android Development] HridayHS:
Hey [MENTION=4478781]yuweng[/MENTION] I has downloaded latest BBQlinux 2015 one. I was using in VM Virtual Box. When I was syncing sources there was a error in last..Fatal error and Input/output error. And in cm11 folder only ’ .repo ' folder i have seen and no file is there ’ mkvendor.sh '. I want to compile it please let me what will I do now. I have MICROMAX CANVAS 2 PLUS A110Q (MT6589).

I hope you will help me and wait for screenshots. I will give screenshots when I will compile again. It always give error.

Thanks in Advance and Happy New Year! 2K15!
[Miscellaneous Android Development] Santhosh M:
How can master figure out if you blindly say fatal error. Post a detailed message of what mistake it showed. As you have clearly said the sync has failed at the end, there will be nothing inside your cm11 folder except a .repo folder and so you can't expect mkvendor to be inside ur cm11 folder. Only if your sync has completed the contents from .repo will expand to outside.
[Miscellaneous Android Development] HridayHS:
Sorry, next time I will post detailed message. The sync was completed only few lines was showing that INPUT/OUTPUT ERROR and after completing sync no mkvendor.sh was there so, this is because of BBQLINUX or my mistake.

I am downloading bbqlinux once again so, I will report you if the same thing happened with me and next time I will show detailed message.
[Miscellaneous Android Development] gt56:
Please disregard this message
[Miscellaneous Android Development] Yogesh1969:
A very good guide. Very meticulous , hard work and great effort to simplify.

Will test and report.
[Miscellaneous Android Development] 7alizani:
Help!

Compiling ended

Size of recovery is only 1.1 MB? Not sure what to do next?

where did I go wrong?

Help, help!! :)
[Miscellaneous Android Development] Santhosh M:
Compiling has stopped due to error and recovery hasn't been compiled. The final message u see at the bottom is not recovery image. Scroll above some more lines back and see what the error is and debug accordingly
[Miscellaneous Android Development] 7alizani:
I was able to compile without errors

But when I test it with

or flashing it directly it won't boot

My Fstab:

Mounts and emmc informations of my device:

My device uses Qualcomm MSM8916 Snapdragon 410 (x64). Anybody to point me in right direction. BoardConfig.mk, and all files are in attachment.
[Miscellaneous Android Development] Santhosh M:
Okay so its a Qualcomm device. Pull a recovery log and see what's wrong.

Sd410 is a newer range chipset and needs more graphic support for touch recoveries such as philz and twrp. Philz is closed long back and hence u should consider twrp maybe. ( philz can still work i believe ) First try with cwm and try to boot it. I myself have been making a try of twrp on a sd410 device and is struck right now at graphical glitches.
[Miscellaneous Android Development] FireLord:
Ask

Can i use cm10.1 or cm12 for making this :confused:

Thanks in advance :o
[Miscellaneous Android Development] nophyan:
What about sync file source size? I want to know because i have'nt unlimited data plan.
[Miscellaneous Android Development] Pd.Chal:
we have a working philtouch for 4.4.4

but now we have 5.0.2 lollipop

can someone help how to port to make it work to 5.0.2? :P

my device is galaxy grand prime SM-G530H
[Miscellaneous Android Development] sairam96:
files downloading since 12 hours and i am now on Fetching project CyanogenMod/android_hardware_broadcom_wlan

and how much time will it take from here

my internet running with a speed of 1mb/sec
[Miscellaneous Android Development] goldchang:
If you need the whole repo,

It may take hours or even days according to your speed
[Miscellaneous Android Development] DeadSquirrel01:
Hey guys :D,

yesterday I've built philz touch recovery, for samsung galaxy a5, but it installs on bootloader . I've followed all steps, and I down't know what is the problem. I've attached recovery.fstab and BoardConfig.mk, too.

The processor is a snapdragon msm8916

Do you know something about this problem?

EDIT: Solved: I compiled ctr recovery
[Miscellaneous Android Development] bovirus:
[MENTION=4478781]yuweng[/MENTION]

Is the PhilZ Recovery compatible with MT67xx chipset? I just see MT65xx reference.

You script use cm11.0.

I see that on repository it's available also cm12.00 (I didn't see 12.1)

CM Source 11.0 -> recovery for KK

CM Source 12.0 -> Recovery for LP 5.0

Is it right.
[Miscellaneous Android Development] DeadSquirrel01:
I tried to compile cm-12.0 repository, but it is cyanogen recovery
[Miscellaneous Android Development] sellhouse:
Thanks

Thanks ! It's good Initiative
[Miscellaneous Android Development] kirito9:
CM Source 11.0 -> recovery for KK

CM Source 12.0 -> Recovery for LP 5.0

That is right. Philz is said to be compatible with CM12 source but I haven't been able to compile it. Yes, if MT67xx is KK then you can build. Maybe it's possible to build in CM11 tree for MT67xx LP but I doubt it will boot.