FORUMS

Swappa’s New App Helps You Value Your Device

There comes a sad time in everyone’s life where you must part ways with your … more

Xiaomi Sold 34.7 Million Phones In 6 Months

2015 has been a phenomenal year for Xiaomi so far. With a stellar rise in 2014, 2015 saw … more

Sprint Reacts To Jab From T-Mobile

America’s cellular network space has always been a battle of the big four: Verizon, AT&T, … more

Floating Apps with Rovers – XDA App Review

There are a lot of great launchers to help customize your phone. Some Launchers allow … more

[GUIDE] How to compile PhilZ Touch 6 Recovery for ARM android devices using BBQLinux

883 posts
Thanks Meter: 3,044
 
By yuweng, Senior Member on 30th August 2014, 02:34 PM
Post Reply Subscribe to Thread Email Thread
Announcement from yuweng: PhilZ Touch 6 Recovery
5th January 2015, 08:11 PM |#71  
Recognized Contributor
Flag cd ▂ ▃ ▅ ▆ █ India
Thanks Meter: 1,122
 
Donate to Me
More
Quote:
Originally Posted by HridayHS

Hey @yuweng 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!

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.
Last edited by Santhosh M; 12th June 2015 at 06:21 PM.
 
 
6th January 2015, 02:32 AM |#72  
Senior Member
Flag Delhi
Thanks Meter: 149
 
More
Quote:
Originally Posted by 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.

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.
20th January 2015, 01:19 PM |#73  
Junior Member
Thanks Meter: 0
 
More
Please disregard this message
Last edited by gt56; 20th January 2015 at 03:12 PM.
2nd June 2015, 06:21 PM |#74  
Member
Flag Mumbai
Thanks Meter: 12
 
More
A very good guide. Very meticulous , hard work and great effort to simplify.
Will test and report.
7th June 2015, 09:57 AM |#75  
7alizani's Avatar
Member
Flag Sarajevo
Thanks Meter: 5
 
More
Help!
Compiling ended

Size of recovery is only 1.1 MB? Not sure what to do next?
where did I go wrong?

Help, help!!
7th June 2015, 10:40 AM |#76  
Recognized Contributor
Flag cd ▂ ▃ ▅ ▆ █ India
Thanks Meter: 1,122
 
Donate to Me
More
Quote:
Originally Posted by 7alizani

Compiling ended

Size of recovery is only 1.1 MB? Not sure what to do next?
where did I go wrong?

Help, help!!

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
7th June 2015, 03:14 PM |#77  
7alizani's Avatar
Member
Flag Sarajevo
Thanks Meter: 5
 
More
I was able to compile without errors

But when I test it with
Quote:

fastboot boot recovery.img

or flashing it directly it won't boot

My Fstab:
Quote:

# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK

/dev/block/mmcblk0p47 /boot emmc defaults defaults
/dev/block/mmcblk0p48 /recovery emmc defaults defaults
/dev/block/mmcblk0p50 /system ext4 ro,seclabel,noatime,data=ordered wait
/dev/block/mmcblk0p51 /data ext4 rw,seclabel,nosuid,nodev,relatime,discard,noauto_d a_alloc,data=ordered wait,check
/dev/block/mmcblk0p49 /cache ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered wait,check
/dev/block/mmcblk0p44 /devlog ext4 rw,seclabel,nosuid,nodev,relatime,errors=continue, data=ordered wait
/dev/block/mmcblk0p33 /fataldevlog ext4 rw,seclabel,nosuid,nodev,relatime,errors=continue, data=ordered wait
/dev/block/mmcblk0p27 /firmware/radio vfat ro,relatime,uid=1000,gid=1000,fmask=0337,dmask=022 7,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro wait
/dev/block/mmcblk0p17 /firmware/wcnss vfat ro,relatime,uid=1000,gid=1000,fmask=0337,dmask=022 7,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro wait
/dev/block/mmcblk0p22 /custdata ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered defaults

/devices/msm_sdcc.2/mmc_host auto auto defaults voldmanaged=sdcard1:auto
/devices/platform/xhci-hcd auto auto defaults voldmanaged=usb:auto

Mounts and emmc informations of my device:
Quote:

C:\adb>adb shell cat /proc/mounts
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
none /sys/fs/cgroup/memory cgroup rw,relatime,memory 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p50 /system ext4 rw,seclabel,relatime,data=ordered 0 0
/dev/block/bootdevice/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,relat
ime,discard,noauto_da_alloc,data=ordered 0 0
/dev/block/mmcblk0p49 /cache ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered
0 0
/dev/block/mmcblk0p44 /devlog ext4 rw,seclabel,nosuid,nodev,relatime,errors=cont
inue,data=ordered 0 0
/dev/block/mmcblk0p33 /fataldevlog ext4 rw,seclabel,nosuid,nodev,relatime,errors
=continue,data=ordered 0 0
adb /dev/usb-ffs/adb functionfs rw,relatime 0 0
/dev/block/mmcblk0p27 /firmware/radio vfat ro,relatime,uid=1000,gid=1000,fmask=0
337,dmask=0227,codepage=437,iocharset=iso8859-1,shortname=lower,errors=remount-r
o 0 0
/dev/block/mmcblk0p17 /firmware/wcnss vfat ro,relatime,uid=1000,gid=1000,fmask=0
337,dmask=0227,codepage=437,iocharset=iso8859-1,shortname=lower,errors=remount-r
o 0 0
pstore /sys/fs/pstore pstore rw,relatime 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_i
d=1023,default_permissions,allow_other 0 0
/dev/block/vold/179:33 /mnt/media_rw/ext_sd vfat rw,dirsync,nosuid,nodev,noexec,
relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,a llow_utime=0020,codepage=437,i
ocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:33 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,rela
time,uid=1023,gid=1023,fmask=0007,dmask=0007,allow _utime=0020,codepage=437,iocha
rset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/fuse /storage/ext_sd fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=10
23,default_permissions,allow_other 0 0

Quote:

C:\adb>adb shell cat /proc/emmc
dev: size erasesize name
mmcblk0p1: 00100000 00000200 "sbl1"
mmcblk0p2: 02000000 00000200 "pg1fs"
mmcblk0p3: 00004000 00000200 "board_info"
mmcblk0p4: 00ef7c00 00000200 "reserve_1"
mmcblk0p5: 00040000 00000200 "mfg"
mmcblk0p6: 017afc00 00000200 "pg2fs"
mmcblk0p7: 00040000 00000200 "sbl1_update"
mmcblk0p8: 00040000 00000200 "rpm"
mmcblk0p9: 00200000 00000200 "tz"
mmcblk0p10: 00008000 00000200 "sdi"
mmcblk0p11: 00400000 00000200 "hboot"
mmcblk0p12: 00500000 00000200 "sp1"
mmcblk0p13: 00200000 00000200 "hyp"
mmcblk0p14: 00100000 00000200 "wifi"
mmcblk0p15: 00008000 00000200 "ddr"
mmcblk0p16: 00100000 00000200 "dsps"
mmcblk0p17: 00500000 00000200 "wcnss"
mmcblk0p18: 00100000 00000200 "rfg_0"
mmcblk0p19: 00100000 00000200 "rfg_1"
mmcblk0p20: 00100000 00000200 "rfg_2"
mmcblk0p21: 00100000 00000200 "rfg_3"
mmcblk0p22: 00100000 00000200 "rfg_4"
mmcblk0p23: 00100000 00000200 "rfg_5"
mmcblk0p24: 00100000 00000200 "rfg_6"
mmcblk0p25: 00100000 00000200 "rfg_7"
mmcblk0p26: 00180000 00000200 "fsg"
mmcblk0p27: 04b00400 00000200 "radio"
mmcblk0p28: 00400000 00000200 "tool_diag"
mmcblk0p29: 00b00000 00000200 "reserve_2"
mmcblk0p30: 00100000 00000200 "misc"
mmcblk0p31: 00180000 00000200 "modem_st1"
mmcblk0p32: 00180000 00000200 "modem_st2"
mmcblk0p33: 01400000 00000200 "fataldevlog"
mmcblk0p34: 00001000 00000200 "debug_config"
mmcblk0p35: 00040000 00000200 "pdata"
mmcblk0p36: 00004000 00000200 "control"
mmcblk0p37: 00140400 00000200 "local"
mmcblk0p38: 00010000 00000200 "extra"
mmcblk0p39: 00100000 00000200 "cdma_record"
mmcblk0p40: 00000400 00000200 "fsc"
mmcblk0p41: 00002000 00000200 "ssd"
mmcblk0p42: 00040000 00000200 "skylink"
mmcblk0p43: 01900000 00000200 "carrier"
mmcblk0p44: 01400000 00000200 "devlog"
mmcblk0p45: 00500000 00000200 "backup_hboot"
mmcblk0p46: 02328800 00000200 "reserve"
mmcblk0p47: 01000000 00000200 "boot"
mmcblk0p48: 01000000 00000200 "recovery"
mmcblk0p49: 14000000 00000200 "cache"
mmcblk0p50: a0000000 00000200 "system"
mmcblk0p51: 08000000 00000200 "userdata"

My device uses Qualcomm MSM8916 Snapdragon 410 (x64). Anybody to point me in right direction. BoardConfig.mk, and all files are in attachment.
Attached Files
File Type: rar My device.rar - [Click for QR Code] (6.11 MB, 8 views)
7th June 2015, 07:10 PM |#78  
Recognized Contributor
Flag cd ▂ ▃ ▅ ▆ █ India
Thanks Meter: 1,122
 
Donate to Me
More
Quote:
Originally Posted by 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.

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.
Last edited by Santhosh M; 12th June 2015 at 06:21 PM.
19th June 2015, 07:58 PM |#79  
Born to be a coder's Avatar
Junior Member
Flag Noida
Thanks Meter: 9
 
More
Question Ask
Can i use cm10.1 or cm12 for making this
Thanks in advance
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes