Database Info

[Q] fstab entry for newly-split internal SD partition (rooted tablet)

Device: Teclast P78HD tablet, Allwinner A31 SoC, Android 4.4.2 (rooted) :::: Software: Busybox X (with fdisk, vi, etc.)
The Teclast P78HD tablet has a small 8GB internal eMMC SDcard with an external microSD slot. In order to best make use of the Link2SD utility, I chose to split in half the almost empty 4.7GB (usable) internal SD FAT32 partition and then format the new (primary) second partition to EXT2 EXT3 or EXT4 as used by the Link2SD app.
I used Busybox X to fdisk /dev/block/mmcblk0 ( /mnt/sdcard )
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After rebooting, the DiskInfo app showed P1 ( mmcblk0p1 ) partition had shrunk to 2.4GB and, as expected, a new (unmounted) 2.3GB P4 ( mmblk0p4 , type 83, Linux ) was there too.
Connecting to a PC vis USB, I tried to format P4 to ext4 using MiniTool Partitioner (Windows) but it did not see the new partition, I then tried Gparted under Linux but it indicated that neither P1 or P4 existed. Gparted just showed a large 4.7GB "unallocated" block.
[ QUESTIONS ]
1. How do I format the new P4 mmblk0p4 partition to EXT4 using Busybox X on the tablet itself ?
2. Should I use some sort of fsck command to fix any side effects of simply truncating the original P1 mmblk0p1 FAT32 partition ?
3. What entry should I add to the tablet's /fstab.sun6i file shown below to make it automount at boot time ?
Code:
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <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/by-name/system /system ext4 ro wait
/dev/block/by-name/cache /cache ext4 noatime,nosuid,nodev,nomblk_io_submit,barrier=1 wait,check
/dev/block/by-name/databk /databk ext4 noatime,nosuid,nodev,nomblk_io_submit,barrier=1 wait,check
/dev/block/by-name/data /data ext4 noatime,nosuid,nodev,nomblk_io_submit,barrier=1,noauto_da_alloc wait,check,encryptable=/dev/block/by-name/databk
/devices/virtual/block/nandj /mnt/sdcard vfat rw,relatime,fmask=0000,dmask=0000 wait,check,noemulatedsd,voldmanaged=sdcard:auto
/devices/platform/sunxi-mmc.2/mmc_host /mnt/sdcard vfat rw,relatime,fmask=0000,dmask=0000 wait,check,noemulatedsd,voldmanaged=sdcard:auto
/devices/platform/sunxi-mmc.0/mmc_host /mnt/extsd vfat rw,relatime,fmask=0000,dmask=0000 wait,check,voldmanaged=extsd:auto
/devices/platform/sunxi-mmc.1/mmc_host /mnt/extsd vfat rw,relatime,fmask=0000,dmask=0000 wait,check,voldmanaged=extsd:auto
/devices/platform/sw-ehci.1 /mnt/usbhost1 vfat rw,relatime,fmask=0000,dmask=0000 wait,check,voldmanaged=usbhost1:auto
/devices/platform/sw_hcd_host0 /mnt/usbhost1 vfat rw,relatime,fmask=0000,dmask=0000 wait,check,voldmanaged=usbhost1:auto
/devices/platform/sw-ohci.1 /mnt/usbhost1 vfat rw,relatime,fmask=0000,dmask=0000 wait,check,voldmanaged=usbhost1:auto
BTW, despite the tablet's fstab entries, there is no /devices/platform directory but there is a /sys/devices/platform directory. Also note that sdcard0 and sdcard1 seem to point to the same place with the same files. I assume that my new partition should point to /storage/sdcard2

Did you ever figure it out? Thinking about splitting my internal storage and looking up for all the info I can find....

Easy Magic TWRP Installer for all MediaTek Devices ONLY (Developers ONLY)

Credits
TWRP Lead Developer Dees_Troy for continuously developing, improving & maintaining TWRP, TeamWin team & numerous developers that has contributed to TWRP & many doesn't know its Igor Sorocean initially submitted MrJavum codes so that TWRP officially supports MediaTek devices & most importantly MrJavum for discovering TWRP works on MediaTek devices & written codes to support proper backup formatting for MTK device . . .
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This tool uses EnJens for repack based on the original Unpack/ Repack concept by Russian Master Shifu Michfood . . .
Not forgetting my Master Shifu Carliv who has taught me how to compile & continuously guiding me to the right direction, dhinesh77 for sharing his super simple technique to patch ubifs for TWRP, awaaas for sharing his tips & findings for building TWRP from source for MTK devices ( Updates ), cyberangel22k for beta-testing custpack backup/restore on MTK Alcatel, yazidkucrit for discovering that TWRP also works on MT6573 & all MTK Developers that has contributed to the MTK platform . . . :highfive:
Screenshot
Video Preview
Installation How-to
Double-click TWRP Setup.exe & read the on-screen instructions
Where is the Downloads . . .
Known problems on MTK devices
Mostly older intermediate MediaTek devices such as MT6589, MT6572 that comes with only 6Mb recovery partition, most probably won't work. However, it works on my legacy MT6573, MT6577 because its kernel is much smaller. There has been feedback from fellow xda members that some latter MediaTek devices comes with 7Mb & 8Mb. Latest MT6592 has a recovery partition of more than 8Mb.
In the past, there has been reports that Touch doesn't work at recovery on some MTK devices, try using different releases of kernels from your device. Recovery is independent so GB, ICS or JB kernel will work provided they are from your device. If you don't have different kernels from your device manufacturer either live without Touch or try porting other recovery, it might work.
This TWRP was compiled from source without adding any sauce or spice & it works for most MTK devices. However, if the mount USB doesn't work then refer to a.marduk solution . . . :good:
# Even though the MTK SoC is designed by MediaTek but the one that produces it is hundreds if not thousands of factories so some might use other combinations to boot up the recovery. It is a known problem that some MTK doesn't wanna boot up recovery the normal way so try Popey900 technique. Standard procedure : Take out the battery, wait a while, put it back, hold Volume Up or Down, don't let go then press the Power button until it boots up #
WARNING
DO NOT USE IT ON LOCKED BOOTLOADER MTK DEVICES SUCH AS ASUS, HTC, LG, SONY, MOTOROLA & OTHERS <- Click Here. IT WILL BRICK IT, refer to here for more info . . .
Even though wrong installation of custom recovery normally will bricks the recovery only however it is better to be safe than sorry.
TWRP is packed with many features so typically it will work on MTK devices with above 6Mb recovery partition however you can try your luck.
Tested working perfectly on my legacy MTK device, MT6573 & MT6577.
Make a Factory ROM backup first with MTK Droid Tools. My old guide here.
Install Flashify & make another backup of your current recovery first & also the boot.img too
Extract downloaded files to your Desktop, disable UAC & restart PC, double-click TWRP.exe & follow the on-screen for instructions.
YOUR TOOL DOESN'T WORK . . .
i've seen this at many threads & also mentioned this many times at my other threads, most frequent reply is it doesn't work, you have given nothing at all to figure out what went wrong . . .
Please list out as many info as possible then it'll be easier to trouble-shoot & read EVERYTHING before hands-on . . .
What OS you are using on the PC & your MTK...
Did you disable UAC & Anti-Virus
Did you execute the porting tool at C: drive if you're using XP else then at your Desktop
Did you try Run as Administrator
Could it be some other software that you installed that interfere with the porting tool then uninstall it
Did you try it on other PC with other version OS or even different USB port
Try uninstall all previous adb driver -> Device Manager -> View -> Show hidden devices -> uninstall all ADB Interface/ Android device -> reboot -> re-install
Did you try latest google ADB driver while for XP try this one
Attach both log.txt from porting tool & recovery.log from TWRP, attach also stock recovery.img/ boot.img & ported TWRP recovery.img too so that i can compare it to see where it went wrong
Please bear in mind that this tool has been PROVEN to work & many has ported it to their MTK device so try to do you own trouble-shooting first & when you found the solution then you are most welcome to post it here . . . :good:
And if you do found a bug on this porting tool, please do report it here too so that i can fix it . . .
And pls do not quote the whole OP when replying . . .
Updates 03 July 2014
Great news, TWRP ubifs patch has been officially submitted to omni for review . . .
Attention all MTK ubifs users,
Guys, please hit the thanks button for dhinesh77 to show your gratitude & appreciation, he has taken all the trouble to get ubifs officially supported on TWRP even though he uses a Samsung nowadays . . .
Thanks bro for doing all this & going thru the hassle for the whole MTK ubifs community, you're the best . . . :highfive:
i've released AIO Compile TWRP script for MediaTek devices on BBQLinux so that you can build it on your own since i don't use MTK nowadays...
Changelog
XDA:DevDB Information
Easy Magic TWRP Installer for MediaTek Devices ONLY (Developers ONLY), Tool/Utility for all devices (see above for details)
Contributors
yuweng
Source Code: https://github.com/omnirom/android_bootable_recovery
Version Information
Status: Stable
Current Stable Version: 2.8.2.0
Stable Release Date: 2014-12-07
Created 2014-06-28
Last Updated 2016-03-27

Features
Auto mode
- You don't need to know a thing & it'll port a working TWRP for your MTK & that is why it is called Magic . . .
Manual mode
- Let you choose either to use your boot.img or recovery.img for porting.
- Let you manually choose your device res, data/media device, flipped screen & uses all files from your stock recovery. Refer to here for more info . . .
- device resolutions
- data/media
- flipped screen
UnPack/ RePack mode
- Let you mod whatever you want with option to install it right away to your MTK
Requirement
- Requires Root
- Install adb driver
- Enable USB debugging
- Disable UAC
- Disable driver signature
- Compatibility with KitKat
- No need ro.secure=0 to run
recovery.fstab How-to
Updates
This porting tool is build on jellybean repo so that it can support three generation of MTK SoC with non-device specific build flags to maintain compatibility. Below specific build flags are not use & it seem that the 2.8.1.0 porting tool doesn't work across MTK device. However, fyi, it works fine on mine
TW_INTERNAL_STORAGE_PATH := "/data/media"
TW_INTERNAL_STORAGE_MOUNT_POINT := "data"
TW_EXTERNAL_STORAGE_PATH := "/sdcard"
TW_EXTERNAL_STORAGE_MOUNT_POINT := "sdcard"
TW_INTERNAL_STORAGE_PATH := "/emmc"
TW_INTERNAL_STORAGE_MOUNT_POINT := "emmc"
TW_EXTERNAL_STORAGE_PATH := "/sdcard"
TW_EXTERNAL_STORAGE_MOUNT_POINT := "sdcard"
SP1_NAME := "uboot"
SP1_DISPLAY_NAME := "uboot"
SP1_BACKUP_METHOD := image
SP1_MOUNTABLE := 0
SP2_NAME := "nvram"
SP2_DISPLAY_NAME := "nvram"
SP2_BACKUP_METHOD := image
SP2_MOUNTABLE := 0
SP3_NAME := "custpack"
SP3_DISPLAY_NAME := "custpack"
SP3_BACKUP_METHOD := image
SP3_MOUNTABLE := 0
So pls refer to here <- *RECOVERY.FSTAB* to use the different flags to properly support your MTK device.
With non-device specific build flags, compatibility can be maintained across MTK SoC, you only need to mod the recovery.fstab. Having said that, i need users feedback so that i can incorporate those changes or this porting tool will remain as it is on every new release.
It seems that you need to label Sdcard as Internal Storage or External Storage to properly support proper BackUp/ Restore function. Refer to here for more info . . .
TTF font is also disable to maintain compatibility across MTK SoC.
-------------------------------------------
Preface
As mentioned few times, i don't own all the MTK devices available on the market so a few things might not work on your MTK. So use the UnPack/ RePack mode to edit necessary files typically the init.rc & recovery.fstab.
UnPack other MTK TWRP by other DEVs & see how they did it.
google your device info & search github & see how they did it, Eg. here for USB-OTG Thanks to hehua2008 the only one that published/ i can find for MTK TWRP.
As mentioned few times, the porting tool now is AIO so go ahead & play with it.
Intro
What is recovery.fstab
The actual require backup partition for MTKs or any android devices are actually ONLY just the boot, cache, data & system partition.
When you encounter any problems such as doesn't boot/ bootloop issues after a new app installation or anything at all, a Wipe Data/ Factory Reset or Restore with ONLY the system & data partition & you'll be able to revert to previous working state in a short while. Thats why its very important to make a backup before modding anything at all !
For bootloop issues with new firmware installation (update.zip) then its best to restore everything. Having said that, if you flash preloader using SP Flash Tool then TWRP restore would not be able to restore it, thats why it is important to backup your Factory ROM with MTK Droid Root & Tools first.
How to identify MTK partition
WARNING : Might corrupt or brick your MTK when you specify the wrong partition at recovery.fstab ! You have been fore-warned . . .
adb shell cat /proc/dumchar_info OR adb shell cat /proc/mtd
Below are typical MTK partition layout
Code:
Part_Name Size StartAddr Type MapTo
preloader 0x0000000000040000 0x0000000000000000 2 /dev/misc-sd
dsp_bl 0x00000000005c0000 0x0000000000040000 2 /dev/misc-sd
mbr 0x0000000000004000 0x0000000000000000 2 /dev/block/mmcblk0
ebr1 0x0000000000004000 0x0000000000004000 2 /dev/block/mmcblk0p1
pmt 0x0000000000400000 0x0000000000008000 2 /dev/block/mmcblk0
[COLOR="Blue"]nvram[/COLOR] 0x0000000000500000 0x0000000000408000 2 /dev/block/mmcblk0
seccfg 0x0000000000020000 0x0000000000908000 2 /dev/block/mmcblk0
[COLOR="blue"]uboot[/COLOR] 0x0000000000060000 0x0000000000928000 2 /dev/block/mmcblk0
bootimg 0x0000000000600000 0x0000000000988000 2 /dev/block/mmcblk0
recovery 0x0000000000800000 0x0000000000f88000 2 /dev/block/mmcblk0
sec_ro 0x0000000000400000 0x0000000001788000 2 /dev/block/mmcblk0p2
misc 0x0000000000060000 0x0000000001b88000 2 /dev/block/mmcblk0
logo 0x0000000000300000 0x0000000001be8000 2 /dev/block/mmcblk0
expdb 0x0000000000200000 0x0000000001ee8000 2 /dev/block/mmcblk0
android 0x0000000020100000 0x00000000020e8000 2 /dev/block/mmcblk0p[COLOR="blue"]3[/COLOR]
cache 0x0000000020100000 0x00000000221e8000 2 /dev/block/mmcblk0p[COLOR="blue"]4[/COLOR]
usrdata 0x0000000020100000 0x00000000422e8000 2 /dev/block/mmcblk0p[COLOR="blue"]5[/COLOR]
fat 0x0000000085338000 0x00000000623e8000 2 /dev/block/mmcblk0p[COLOR="blue"]6[/COLOR]
bmtpool 0x0000000001500000 0x00000000ff9f00a8 2 /dev/block/mmcblk0
Part_Name:Partition name you should open;
Size:size of partition
StartAddr:Start Address of partition;
Type:Type of partition(MTD=1,EMMC=2)
MapTo:actual device you operate
Standard TWRP recovery.fstab for MTK devices
Code:
# mount point fstype device [device2]
/boot emmc /dev/bootimg
/recovery emmc /dev/recovery
/system ext4 /dev/block/mmcblk0p[COLOR="Blue"]3[/COLOR]
/cache ext4 /dev/block/mmcblk0p[COLOR="blue"]4[/COLOR]
/data ext4 /dev/block/mmcblk0p[COLOR="blue"]5[/COLOR]
/emmc vfat /dev/block/mmcblk0p[COLOR="blue"]6[/COLOR]
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/sd-ext auto /dev/block/mmcblk1p2
/nvram emmc /dev/nvram flags=display="[COLOR="blue"]Nvram[/COLOR]";backup=1
/uboot emmc /dev/uboot flags=display="[COLOR="blue"]Uboot[/COLOR]";backup=1
Thanks to MrJavum who discover that we can also backup Nvram & Uboot for MTK devices . . . :good:
MTK Uboot also consist of camera driver & this feature is extremely useful when you upgrade your device firmware, typically it will replace the Uboot & your camera doesn't work after that. A simple restore & you'll have your camera working again in no time.
MTK Nvram consist of your IMEI & this feature is extremely useful when you have corrupted it, a simple restore & you'll have your phone in working state again.
Below format was discovered by bgcngm & it has saved me a few lines of codes as MTK manufacturer tends to use different partition no. from each other. Eg. Some might be using mmcblk0p6 for system & some uses mmcblk0p3 while [email protected] will work on all MTK devices.
Code:
# mount point fstype device [device2]
/boot emmc /dev/bootimg
/recovery emmc /dev/recovery flags=display="recovery";backup=1
/uboot emmc /dev/uboot flags=display="uboot";backup=1
/nvram emmc /dev/nvram flags=display="nvram";backup=1
/cache ext4 /[COLOR="blue"][email protected][/COLOR]
/data ext4 /[COLOR="blue"][email protected][/COLOR]
/system ext4 /[COLOR="blue"][email protected][/COLOR]
/emmc vfat /[COLOR="blue"][email protected][/COLOR]
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/sd-ext auto /dev/block/mmcblk1p2
Having said that, few has reported back that its not compatible for their MTK then you'll need to unpack it & use the device block path /dev/block/mmcblk0pX instead of this soft-link [email protected] format. Use Notepad++ for editing. Updates : Porting tool now uses direct device block path.
Below examples are some of MrJavum TWRP recovery.fstab for MTKs
Code:
# mount point fstype device [device2]
/boot emmc /dev/bootimg
/cache ext4 /[email protected]
/data ext4 /[email protected]
/misc emmc /dev/misc
/recovery emmc /dev/recovery
/system ext4 /[email protected]
[COLOR="blue"]/preload[/COLOR] ext4 /[COLOR="blue"][email protected][/COLOR] flags=display="[COLOR="blue"]Preload[/COLOR]";backup=1;wipeingui
/external_sd vfat /dev/block/mmcblk1p1 flags=display="External SD-card";storage;wipeingui;removable
/nvram emmc /dev/nvram flags=display="Nvram";backup=1
/uboot emmc /dev/uboot flags=display="Uboot";backup=1
/logo emmc /dev/logo flags=display="Boot Logo";backup=1
#mt6582/recovery_emmc.fstab
To support preload partition you'll need to specify it at init.rc too.
Code:
[COLOR="Blue"]mkdir /preload[/COLOR]
mkdir /external_sd
mkdir /system
mkdir /data
mkdir /cache
mount /tmp /tmp tmpfs
Code:
/boot emmc /dev/bootimg
/cache ext4 /[email protected]
/data ext4 /[email protected]
/misc emmc /dev/misc
/recovery emmc /dev/recovery
/emmc vfat /[email protected] flags=display="Internal SD-card";storage;wipeingui;backup=1
/system ext4 /[email protected]
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 flags=display="External SD-card";storage;wipeingui;removable
/nvram emmc /dev/nvram flags=display="Nvram";backup=1
/uboot emmc /dev/uboot flags=display="Uboot";backup=1
/[COLOR="blue"]logo[/COLOR] emmc [COLOR="blue"]/dev/logo[/COLOR] flags=display="[COLOR="blue"]Boot Logo[/COLOR]";backup=1
Awaaas is so kind to shared with me his findings. He got help from bigbiff on the IRC & now TWRP can also backup EBR1 & SECRO. Refer to updates here.
CodeLover has added cust partition for his Huawei.
Code:
# mount point fstype device [device2]
/boot emmc /dev/bootimg flags=display="boot"
/misc emmc /dev/misc
/recovery emmc /dev/recovery flags=display="recovery";backup=1
/uboot emmc /dev/uboot flags=display="uboot";backup=1
/nvram emmc /dev/nvram flags=display="nvram";backup=1
/cache ext4 /[email protected] flags=display="cache"
/data ext4 /[email protected] flags=display="data"
[COLOR="Blue"]/cust[/COLOR] ext4 /[COLOR="blue"][email protected][/COLOR] flags=display="[COLOR="blue"]cust[/COLOR]";backup=1
/system ext4 /[email protected] flags=display="system"
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
init.rc with cust partition support.
Code:
mkdir /boot
mkdir /recovery
mkdir /system
mkdir /data
[COLOR="blue"]mkdir /cust[/COLOR]
mkdir /cache
mkdir /sdcard
mount tmpfs tmpfs /tmp
So its entirely up to you to specify what you want TWRP to backup on your MTK no need to compile a new one, just mod the recovery.fstab
For further info refer to the main thread here . . . :good:
For MTK Alcatel devices, besides /custpack there is also /mobile_info partition, again its entirely up to you whether you would wanna backup it too, credits to MrJavum for compiling the first TWRP version for it . . .
Code:
# mount point fstype device [device2]
/boot emmc /dev/bootimg
/recovery emmc /dev/recovery
/cache ext4 /e[email protected]
/data ext4 /[email protected]
/system ext4 /[email protected]
/emmc vfat /[email protected]
[COLOR="Blue"]/custpack[/COLOR] ext4 /[email protected] flags=display=[COLOR="blue"]custpack[/COLOR];backup=1
[COLOR="blue"]/mobile_info[/COLOR] ext4 /[email protected]_info flags=display=[COLOR="blue"]mobile_info[/COLOR];backup=1
/nvram emmc /dev/nvram flags=display=Nvram;backup=1
/uboot emmc /dev/uboot flags=display=Uboot;backup=1
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/sd-ext auto /dev/block/mmcblk1p2
Code:
mkdir /boot
mkdir /recovery
mkdir /system
mkdir /data
mkdir /cache
[COLOR="blue"] mkdir /custpack
mkdir /mobile_info[/COLOR]
mkdir /sdcard
mount tmpfs tmpfs /tmp
As mentioned many times, i don't own all MTK devices out there so some features might not work. To fix it & to learn more about modding recovery refer to my Master Shifu thread here & here . . . :good:
Ported recovery.img is too large & causes region overlap !
This tool is AIO so use the UnPack/ RePack feature to remove below known files that are safe to be deleted to save a few Kb. ( rmdisk/sbin folder ) Below list starts with less critical to critical
Use awaaas technique to use basic theme
Parted
All *exfat*
erase_image, dump_image
flash_image <- You will not be able to flash modded EBR, MBR
rmdisk/supersu folder <- You will not be able to Root via TWRP
adbd <- No adb shell & mount USB storage but you still can use MTP
In fact in the past i have tested, there are quite a few more binary that you can safely remove from rmdisk/sbin folder. Of course you'll loose a few features but at least you can still use TWRP for basic backup & restore.
Delete one file at a time at rmdisk/sbin folder, repack it, until it let you auto-install it.
Updates
Found out that you can also zip the whole content of res folder, move it to /sdcard/TWRP/theme/ui.zip, delete whole res folder & that will work too but no splash screen . . .
if you want then remain res/images/curtain.jpg then splash screen will work . . .
TWRP Materialised Theme
Huge Credits to z31s1g, TWRP has never look so elegant & sophisticated ever before . . . :good:
As mentioned many times, this tool is AIO so unpack the ported recovery.img, download the various custom splash screen that you like, resize it to your device res, copy & paste it to res/images/curtain.jpg, Credits to PünchUp . . . :good:
i have ported to 480x854 res Dark Theme & Light Theme, credits to thewisenerd & Modding.MyMind & don't forget to hit the Thanks button for them . . . :good:
Dark & Light Theme porting to MTK
If you're using other themes other than 480x854 which is ported by me then Dark & Light Theme will not work properly on MTK . . .
Solution to Change Color on Dark & Light Themes to work on MTK
Open ui.zip -> ui.xml & change all /sdcard/TWRP to /emmc/TWRP EXCEPTIONAL for two -> tw_filename=/sdcard/TWRP/aromafm/aromafm.zip & save it first.
Tips : Use the search function -> Ctrl + f to search for above keyword & if you're a Windows users then use Notepad++ for editing . . .
There are two occurrence -> ./zip -0 -r -u "/emmc/TWRP/theme/ui.zip" *; <- You'll need to delete both the -u.
Code:
mkdir "/cache/twrp";
if [ -f "/emmc/TWRP/theme/ui.zip" ];
then unzip -o "/emmc/TWRP/theme/ui.zip" -d "/cache/twrp";
chmod 777 "/cache/twrp/zip";
cp -r /cache/twrp/%tw_folder%/* "/cache/twrp/images";
busybox mv "/cache/twrp/ui.xml" "/cache/twrp/ui_temp.xml";
busybox sed "s/%text_highlight%/#%tw_text_color_highlight%/g" "/cache/twrp/ui_temp.xml" > "/cache/twrp/ui_temp2.xml";
rm -f "/cache/twrp/ui_temp.xml";
busybox sed "s/%text_actionbar%/#%tw_text_actionbar%/g" "/cache/twrp/ui_temp2.xml" > "/cache/twrp/ui.xml";
rm -f "/cache/twrp/ui_temp2.xml";
cd "/cache/twrp";
[COLOR="blue"]./zip -0 -r "/emmc/TWRP/theme/ui.zip" *;[/COLOR]
cd /;
rm -r "/cache/twrp"
else
Updates
/data/media device refer to here . . . :good:
Solution to Install Image on Dark & Light Themes to work on MTK
WARNING : Does not check whether the boot.img or recovery.img you're about to flash is oversize & that might brick your MTK if you have only 6Mb partition, you have been fore-warned . . .
When you select Install -> Top Menu Install Zip -> Install Zip or Install Image
Open ui.zip -> flashify -> META-INF -> com -> google -> android -> update-binary & edit as below . . .
Replace Line 41 to 53 with below & save it first.
Code:
# Modded to work on MediaTek devices only
case $image in
boot*)
imgtype="boot.img";;
*recovery*)
imgtype="recovery.img";;
*)
ui_print "No image file found to flash.";
abort;;
esac;
Now at Line 66 to 74 replace with below, save it & now flashing MTK boot.img or recovery.img will work on Dark & Light Theme.
Code:
# Modded to work on MediaTek devices only
if [ "$imgtype" == "boot.img" ]; then
block=/dev/bootimg;
elif [ "$imgtype" == "recovery.img" ]; then
block=/dev/recovery;
fi;
Aroma File Manager
It is a known problem that aromafm will not to work properly on flip-screen, this is not a TWRP problem as it has never been updated for almost a year.
Flip Touch on Flip Screen
It is a known problem that MTK manufacturer uses non-standard design & uses different Flip Screen/ Non-Flip LCD with different combinations of Flip/ Non-Flip Touch Screen on various Portrait & especially Landscape Android devices.
There is absolutely no way that the porting tool could detect whether your MTK's Touch is FlipX or FlipY or SwapXY so i build all possible combinations here -> View attachment 3039567, read the How-to use it. Built-in to porting tool -> Manual-mode
Bug report <- No support if you don't attach it to your post, pls refer to post #1 YOUR TOOL DOESN'T WORK . . .
Refer to here on how to submit a proper bug report . . . :good:
Please always attach recovery.log & log.txt from the porting tool or i'll be giving the wrong advice based on assumption & that might brick your device !
How to obtain recovery log
adb pull /tmp/recovery.log -> Attach to your post
At TWRP -> BackUp -> After Backup go to Advanced -> Copy Log to SDCard
Typically you will find the recovery.log at
Typical Internal SdCard
/emmc/TWRP/BACKUPS/ [Your Device Name] / [Backup date] [ro.mediatek.version.release]
or
Typical External SdCard
/sdcard/TWRP/BACKUPS/ [Your Device Name] / [Backup date] [ro.mediatek.version.release]
Attach it to your post.
At TWRP console (Square button at button) -> You can view the log
if you don't see me replying means either the answer is already at this thread so start reading every page, its not like there are 100 over pages, as of 10 Jan 2014, there are only 24 pages . . .
The 2nd reason you don't see me replying is i donno the answer then head up to the TWRP IRC channel to get help, refer to here for more info . . .
TWRP FAQ

Questions & Answers
Q : Your tool doesn't work.
A : Its already explained at the OP, pls read EVERYTHING at Page 1 !
Q : I can't get adb to work on my PC.
A : Then get one of your device forum DEV to look at this porting tool.
Q : I have a MTK model xxx SoC YYY, does your porting tool support it.
A : The title already said it, for all MediaTek Devices ONLY except latest big.LITTLE/ Cortex-A53 use PhilZ Touch
Q : I have a MTK but i'm afraid the porting tool would brick my device.
A : Then don't use it ! Its for Developers ONLY !
Q : OP said DO NOT USE IT ON LOCKED BOOTLOADER but the link doesn't say much for MTK devices.
A : There isn't any guide to identify locked bootloader on MTKs, generally you'll have to flash the recovery.img to find out whether it bricks ! However, farenheith has confirmed by flashing back the original stock 3e recovery.img & his locked bootloader MTK Motorola boots back !
As explained BRANDED at the OP, UNBRANDED MTKs are generally MTKs directly from China, have unlock bootloaders.
List of supported MTK devices . . .

@yuweng Simply Awesome....

Haha, you are most welcome, my friend . . . :highfive:
Any feedbacks on ubifs & if everything is working well then i'll contact Master Shifu Dees_Troy to submit dhinesh77 patch to have ubifs officially supported by TWRP . . .

Amazing work!
It's been a while since i googled about MTK Devices. I've already compiled TWRP for Oppo Find Muse, which has the MTK6572. It's really pleasure to see that you've made a good job! :laugh::good:
Keep up the good work!
I'm not able to update my TWRP recovery coz my device already given to my mom :crying:
But i'm still browsing about the MTK Devices :laugh:

It says that my recovery partition its to small(6291456) and that i can lose my IMEI. How can i make the partition recovery bigger?

As mentioned at the OP, it will most probably works on the latest MTK devices with above 6Mb, Eg : The latest MT6582, MT6592 or the obsolete MT6573, MT6575, MT6577 b'cos the kernel is so much smaller in size on these legacy devices . . .
i've published my findings on how to increase MTK recovery partition to 7Mb or 8Mb last year but many couldn't get it to work on their MT6589 . . .
Those that got it to work never shared it . . . Hunt for key work 7Mb_TWRP.pdf. WARNING : You might brick your device in doing so . . .

yuweng said:
As mentioned at the OP, it will most probably works on the latest MTK devices with above 6Mb, Eg : The latest MT6582, MT6592 or the obsolete MT6573, MT6575, MT6577 b'cos the kernel is so much smaller in size on these legacy devices . . .
i've published my findings on how to increase MTK recovery partition to 7Mb or 8Mb last year but many couldn't get it to work on their MT6589 . . .
Those that got it to work never shared it . . . Hunt for key work 7Mb_TWRP.pdf. WARNING : You might brick your device in doing so . . .
Click to expand...
Click to collapse
:good:
I prefer not to test it

Works with MT6572? :/

Great Work Bro!! :highfive:

Hello sir, I have a "mtk 6589t xolo q3000 with 4.4.2 kitkat os.
My stock recovery.imgs size is 6Mb and my stock boot.imgs size is also 6mb.
Is it possible to port twrp in my device ?
Will my mobile support your tool?
Sent from my Q3000 using XDA Premium 4 mobile app

Please upload it to some file sharing site rather than torrent..no seeds and leechers..
Sent from my Micromax A58 using xda app-developers app

daoodshah said:
....no seeds and leechers....
Click to expand...
Click to collapse
if you wanna download, do it the simple way. see the part "Where is the Downloads . . . " in the op.
"click to show content". can't get any simpler/better than that.

Dwnload is nt getting any speed..thats the problem..as there are no seeds..
Sent from my Micromax A58 using xda app-developers app

daoodshah said:
Dwnload is nt getting any speed....as there are no seeds..
Click to expand...
Click to collapse
no seeds required. click direct download. don't you see the pic and the circled icon? just do a 1-2-3.

Working perfectly for UBIFS..just tested right now..
Sent from my Micromax A58 using xda app-developers app

Wanna try this

which can delete files from folder "sbin"? Turned to run on 6589, but still works incorrectly.

Is there a way to increase size of recovery partition. I have 6mb partition, ported recovery is 6.4mb

[PORT][Ubuntu Touch] WIP Stuck on a error

Hi everybody !
I'm currently porting Ubuntu Touch (utopic) on falcon !
BUT I'm stuck on an error wich I can't achieve to fix (and I become out of time ...).
So I decided to show you my problem ! (I'm very close to success so it's maybe the last fix to do)
# make -j8 (-j1 won't fix that)
Code:
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.4.2
TARGET_PRODUCT=full_falcon
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a-neon
TARGET_CPU_VARIANT=krait
HOST_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-3.13.0-30-generic-x86_64-with-Ubuntu-14.04-trusty
HOST_BUILD_TYPE=release
BUILD_ID=KOT49H
OUT_DIR=/media/nas/EXTRA/Ubuntu_Touch/out
============================================
including abi/cpp/Android.mk ...
including bionic/Android.mk ...
including bootable/recovery/Android.mk ...
including build/libs/host/Android.mk ...
including build/target/board/Android.mk ...
including build/tools/acp/Android.mk ...
including build/tools/check_prereq/Android.mk ...
including build/tools/fs_config/Android.mk ...
including build/tools/zipalign/Android.mk ...
including device/asus/deb/dumpstate/Android.mk ...
including device/asus/deb/recovery/Android.mk ...
including device/asus/deb/self-extractors/Android.mk ...
including device/asus/flo/Android.mk ...
including device/asus/grouper/Android.mk ...
including device/asus/tilapia/recovery/Android.mk ...
including device/asus/tilapia/self-extractors/Android.mk ...
including device/generic/goldfish/audio/Android.mk ...
including device/generic/goldfish/camera/Android.mk ...
including device/generic/goldfish/gps/Android.mk ...
including device/generic/goldfish/lights/Android.mk ...
including device/generic/goldfish/opengl/Android.mk ...
including device/generic/goldfish/power/Android.mk ...
including device/generic/goldfish/qemu-props/Android.mk ...
including device/generic/goldfish/qemud/Android.mk ...
including device/generic/goldfish/sensors/Android.mk ...
including device/lge/hammerhead/Android.mk ...
including device/lge/mako/Android.mk ...
including device/samsung/manta/Android.mk ...
including external/aac/Android.mk ...
including external/busybox/Android.mk ...
including external/bzip2/Android.mk ...
including external/checkpolicy/Android.mk ...
including external/e2fsprogs/Android.mk ...
including external/expat/Android.mk ...
including external/flac/Android.mk ...
including external/freetype/Android.mk ...
including external/fsck_msdos/Android.mk ...
including external/gcc-demangle/Android.mk ...
including external/genext2fs/Android.mk ...
including external/giflib/Android.mk ...
including external/gtest/Android.mk ...
including external/icu4c/Android.mk ...
including external/jhead/Android.mk ...
including external/jpeg/Android.mk ...
including external/libgsm/Android.mk ...
including external/liblzf/Android.mk ...
including external/libpng/Android.mk ...
including external/libselinux/Android.mk ...
including external/libsepol/Android.mk ...
including external/libvpx/Android.mk ...
including external/mksh/Android.mk ...
including external/openssl/Android.mk ...
including external/pigz/Android.mk ...
including external/protobuf/Android.mk ...
including external/qemu/Android.mk ...
including external/scrypt/Android.mk ...
including external/sepolicy/Android.mk ...
including external/sfntly/Android.mk ...
including external/skia/Android.mk ...
including external/sonivox/Android.mk ...
including external/speex/Android.mk ...
including external/sqlite/android/Android.mk ...
including external/sqlite/dist/Android.mk ...
including external/stlport/Android.mk ...
including external/tinyalsa/Android.mk ...
including external/tinycompress/Android.mk ...
including external/tremolo/Android.mk ...
including external/webp/Android.mk ...
including external/webrtc/Android.mk ...
including external/wpa_supplicant_8/Android.mk ...
including external/yaffs2/Android.mk ...
including external/zlib/Android.mk ...
including frameworks/av/camera/Android.mk ...
including frameworks/av/drm/common/Android.mk ...
including frameworks/av/drm/drmserver/Android.mk ...
including frameworks/av/drm/libdrmframework/Android.mk ...
including frameworks/av/drm/mediadrm/plugins/mock/Android.mk ...
including frameworks/av/media/common_time/Android.mk ...
including frameworks/av/media/libcpustats/Android.mk ...
including frameworks/av/media/libeffects/downmix/Android.mk ...
including frameworks/av/media/libeffects/factory/Android.mk ...
including frameworks/av/media/libeffects/loudness/Android.mk ...
including frameworks/av/media/libeffects/lvm/lib/Android.mk ...
including frameworks/av/media/libeffects/lvm/wrapper/Android.mk ...
including frameworks/av/media/libeffects/preprocessing/Android.mk ...
including frameworks/av/media/libeffects/proxy/Android.mk ...
including frameworks/av/media/libeffects/visualizer/Android.mk ...
including frameworks/av/media/libmedia/Android.mk ...
including frameworks/av/media/libmediaplayerservice/Android.mk ...
including frameworks/av/media/libnbaio/Android.mk ...
including frameworks/av/media/libstagefright/Android.mk ...
including frameworks/av/media/mediaserver/Android.mk ...
including frameworks/av/services/audioflinger/Android.mk ...
including frameworks/av/services/camera/libcameraservice/Android.mk ...
including frameworks/av/services/medialog/Android.mk ...
including frameworks/base/cmds/bootanimation/Android.mk ...
including frameworks/base/cmds/screencap/Android.mk ...
including frameworks/base/libs/androidfw/Android.mk ...
including frameworks/base/services/input/Android.mk ...
including frameworks/base/tools/aapt/Android.mk ...
including frameworks/native/cmds/installd/Android.mk ...
including frameworks/native/cmds/servicemanager/Android.mk ...
including frameworks/native/libs/binder/Android.mk ...
including frameworks/native/libs/diskusage/Android.mk ...
including frameworks/native/libs/gui/Android.mk ...
including frameworks/native/libs/input/Android.mk ...
including frameworks/native/libs/ui/Android.mk ...
including frameworks/native/opengl/libagl/Android.mk ...
including frameworks/native/opengl/libs/Android.mk ...
including frameworks/native/opengl/tests/Android.mk ...
including frameworks/native/services/batteryservice/Android.mk ...
including frameworks/native/services/connectivitymanager/Android.mk ...
including frameworks/native/services/powermanager/Android.mk ...
including frameworks/native/services/sensorservice/Android.mk ...
including frameworks/native/services/surfaceflinger/Android.mk ...
including frameworks/opt/emoji/Android.mk ...
including hardware/akm/AK8975_FS/akmdfs/Android.mk ...
including hardware/akm/AK8975_FS/libsensors/Android.mk ...
including hardware/broadcom/libbt/Android.mk ...
including hardware/broadcom/wlan/bcmdhd/Android.mk ...
including hardware/invensense/Android.mk ...
including hardware/libhardware/Android.mk ...
including hardware/libhardware_legacy/Android.mk ...
including hardware/qcom/bt/Android.mk ...
including hardware/qcom/camera/Android.mk ...
including hardware/qcom/display/Android.mk ...
including hardware/qcom/fm/Android.mk ...
including hardware/qcom/keymaster/Android.mk ...
including hardware/qcom/media/Android.mk ...
including hardware/qcom/power/Android.mk ...
including hardware/qcom/wlan/qcwcn/Android.mk ...
including hardware/ril/libril/Android.mk ...
including hardware/ril/librilutils/Android.mk ...
including hardware/ril/reference-ril/Android.mk ...
including hardware/ril/rild/Android.mk ...
including hardware/samsung_slsi/exynos5/Android.mk ...
including hardware/ti/omap3/Android.mk ...
including hardware/ti/omap4xxx/Android.mk ...
including hardware/ti/wlan/mac80211/Android.mk ...
including hardware/ti/wpan/Android.mk ...
including prebuilts/tools/linux-x86/sdl/Android.mk ...
including sdk/emulator/mksdcard/Android.mk ...
including sdk/emulator/opengl/Android.mk ...
including sdk/emulator/qtools/Android.mk ...
including system/core/Android.mk ...
including system/extras/ext4_utils/Android.mk ...
including system/media/audio_route/Android.mk ...
including system/media/audio_utils/Android.mk ...
including system/media/camera/src/Android.mk ...
including system/media/camera/tests/Android.mk ...
including system/security/keystore/Android.mk ...
including system/security/softkeymaster/Android.mk ...
including system/vold/Android.mk ...
including ubuntu/assets/Android.mk ...
including ubuntu/libhybris/compat/camera/Android.mk ...
including ubuntu/libhybris/compat/input/Android.mk ...
including ubuntu/libhybris/compat/media/Android.mk ...
including ubuntu/libhybris/compat/surface_flinger/Android.mk ...
including ubuntu/libhybris/compat/ui/Android.mk ...
including ubuntu/platform-api/android/hybris/Android.mk ...
including ubuntu/upstart-property-watcher/Android.mk ...
No private recovery resources for TARGET_DEVICE falcon
build/core/Makefile:32: warning: overriding commands for target « /media/nas/EXTRA/Ubuntu_Touch/out/target/product/falcon/system/lib/egl/egl.cfg »
build/core/base_rules.mk:529: warning: overriding commands for target « /media/nas/EXTRA/Ubuntu_Touch/out/target/product/falcon/system/lib/egl/egl.cfg »
build/core/Makefile:32: attention : warning: overriding commands for target « /media/nas/EXTRA/Ubuntu_Touch/out/target/product/falcon/system/bin/rild »
build/core/base_rules.mk:529: warning : old commands ignored for target « /media/nas/EXTRA/Ubuntu_Touch/out/target/product/falcon/system/bin/rild »
build/core/Makefile:32: attention : warning: overriding commands for target « /media/nas/EXTRA/Ubuntu_Touch/out/target/product/falcon/system/lib/libril.so »
build/core/base_rules.mk:529: warning : old commands ignored for target « /media/nas/EXTRA/Ubuntu_Touch/out/target/product/falcon/system/lib/libril.so »
device/motorola/msm8226-common/mkbootimg.mk:41: warning: overriding commands for target « /media/nas/EXTRA/Ubuntu_Touch/out/target/product/falcon/boot.img »
build/core/Makefile:489: warning : old commands ignored for target « /media/nas/EXTRA/Ubuntu_Touch/out/target/product/falcon/boot.img »
make -C kernel/motorola/msm8226 O=/media/nas/EXTRA/Ubuntu_Touch/out/target/product/falcon/obj/KERNEL_OBJ ARCH=arm CROSS_COMPILE=" /media/nas/EXTRA/Ubuntu_Touch/prebuilts/gcc/linux-x86/arm/arm-eabi-4.7/bin/arm-eabi-" VARIANT_DEFCONFIG= SELINUX_DEFCONFIG= msm8226_mmi_defconfig
make[1]: openning the directory « /media/nas/EXTRA/Ubuntu_Touch/kernel/motorola/msm8226 »
Target Ubuntu Touch ram disk: /media/nas/EXTRA/Ubuntu_Touch/out/target/product/falcon/ramdisk.img
GEN /media/nas/EXTRA/Ubuntu_Touch/out/target/product/falcon/obj/KERNEL_OBJ/Makefile
#
# configuration written to .config
#
make[1]: leaving the directory « /media/nas/EXTRA/Ubuntu_Touch/kernel/motorola/msm8226 »
make -C kernel/motorola/msm8226 O=/media/nas/EXTRA/Ubuntu_Touch/out/target/product/falcon/obj/KERNEL_OBJ ARCH=arm CROSS_COMPILE=" /media/nas/EXTRA/Ubuntu_Touch/prebuilts/gcc/linux-x86/arm/arm-eabi-4.7/bin/arm-eabi-" headers_install
make[1]: openning the directory « /media/nas/EXTRA/Ubuntu_Touch/kernel/motorola/msm8226 »
CHK include/linux/version.h
make[1]: leaving the directory « /media/nas/EXTRA/Ubuntu_Touch/kernel/motorola/msm8226 »
make -C kernel/motorola/msm8226 O=/media/nas/EXTRA/Ubuntu_Touch/out/target/product/falcon/obj/KERNEL_OBJ ARCH=arm CROSS_COMPILE=" /media/nas/EXTRA/Ubuntu_Touch/prebuilts/gcc/linux-x86/arm/arm-eabi-4.7/bin/arm-eabi-" zImage
build/tools/generate-notice-files.py /media/nas/EXTRA/Ubuntu_Touch/out/target/product/falcon/obj/NOTICE.txt /media/nas/EXTRA/Ubuntu_Touch/out/target/product/falcon/obj/NOTICE.html "Notices for files contained in the filesystem images in this directory:" /media/nas/EXTRA/Ubuntu_Touch/out/target/product/falcon/obj/NOTICE_FILES/src
make[1]: openning the directory « /media/nas/EXTRA/Ubuntu_Touch/kernel/motorola/msm8226 »
Combining NOTICE files into HTML
Combining NOTICE files into text
GEN /media/nas/EXTRA/Ubuntu_Touch/out/target/product/falcon/obj/KERNEL_OBJ/Makefile
scripts/kconfig/conf --silentoldconfig Kconfig
GEN /media/nas/EXTRA/Ubuntu_Touch/out/target/product/falcon/obj/KERNEL_OBJ/Makefile
CHK include/linux/version.h
Using /media/nas/EXTRA/Ubuntu_Touch/kernel/motorola/msm8226 as source for kernel
CHK include/generated/utsrelease.h
make[3]: « include/generated/mach-types.h » is up-to-date.
CALL /media/nas/EXTRA/Ubuntu_Touch/kernel/motorola/msm8226/scripts/checksyscalls.sh
CHK include/generated/compile.h
GZIP kernel/config_data.gz
CHK kernel/config_data.h
Downloading ubuntu-touch-generic-initrd version 0.73
Kernel: arch/arm/boot/Image is ready
SHIPPED arch/arm/boot/compressed/ashldi3.S
AS arch/arm/boot/compressed/ashldi3.o
LD arch/arm/boot/compressed/vmlinux
OBJCOPY arch/arm/boot/zImage
Kernel: arch/arm/boot/zImage is ready
make[1]: leaving the directory « /media/nas/EXTRA/Ubuntu_Touch/kernel/motorola/msm8226 »
make -C kernel/motorola/msm8226 O=/media/nas/EXTRA/Ubuntu_Touch/out/target/product/falcon/obj/KERNEL_OBJ ARCH=arm CROSS_COMPILE=" /media/nas/EXTRA/Ubuntu_Touch/prebuilts/gcc/linux-x86/arm/arm-eabi-4.7/bin/arm-eabi-" modules
make[1]: openning the directory « /media/nas/EXTRA/Ubuntu_Touch/kernel/motorola/msm8226 »
GEN /media/nas/EXTRA/Ubuntu_Touch/out/target/product/falcon/obj/KERNEL_OBJ/Makefile
CHK include/linux/version.h
Using /media/nas/EXTRA/Ubuntu_Touch/kernel/motorola/msm8226 as source for kernel
CHK include/generated/utsrelease.h
make[3]: « include/generated/mach-types.h » is up-to-date.
CALL /media/nas/EXTRA/Ubuntu_Touch/kernel/motorola/msm8226/scripts/checksyscalls.sh
Building modules, stage 2.
MODPOST 3 modules
make[1]: quittant le répertoire « /media/nas/EXTRA/Ubuntu_Touch/kernel/motorola/msm8226 »
make -C kernel/motorola/msm8226 O=/media/nas/EXTRA/Ubuntu_Touch/out/target/product/falcon/obj/KERNEL_OBJ INSTALL_MOD_PATH=../../system ARCH=arm CROSS_COMPILE=" /media/nas/EXTRA/Ubuntu_Touch/prebuilts/gcc/linux-x86/arm/arm-eabi-4.7/bin/arm-eabi-" modules_install
make[1]: openning the directory « /media/nas/EXTRA/Ubuntu_Touch/kernel/motorola/msm8226 »
INSTALL drivers/media/radio/radio-iris-transport.ko
INSTALL drivers/net/wireless/prima/wlan.ko
INSTALL drivers/scsi/scsi_wait_scan.ko
DEPMOD 3.4.96-gbad4af5-dirty
make[1]: leaving the directory « /media/nas/EXTRA/Ubuntu_Touch/kernel/motorola/msm8226 »
mdpath=`find /media/nas/EXTRA/Ubuntu_Touch/out/target/product/falcon/system/lib/modules -type f -name modules.order`; if [ "$mdpath" != "" ];then mpath=`dirname $mdpath`; ko=`find $mpath/kernel -type f -name *.ko`; for i in $ko; do /media/nas/EXTRA/Ubuntu_Touch/prebuilts/gcc/linux-x86/arm/arm-eabi-4.7/bin/arm-eabi-strip --strip-unneeded $i; mv $i /media/nas/EXTRA/Ubuntu_Touch/out/target/product/falcon/system/lib/modules/; done; fi
mdpath=`find /media/nas/EXTRA/Ubuntu_Touch/out/target/product/falcon/system/lib/modules -type f -name modules.order`; if [ "$mdpath" != "" ];then mpath=`dirname $mdpath`; rm -rf $mpath; fi
mkdir -p /media/nas/EXTRA/Ubuntu_Touch/out/target/product/falcon/system/lib/modules/pronto
mv /media/nas/EXTRA/Ubuntu_Touch/out/target/product/falcon/system/lib/modules/wlan.ko /media/nas/EXTRA/Ubuntu_Touch/out/target/product/falcon/system/lib/modules/pronto/pronto_wlan.ko
ln -sf /system/lib/modules/pronto/pronto_wlan.ko /media/nas/EXTRA/Ubuntu_Touch/out/target/product/falcon/system/lib/modules/wlan.ko
mdpath=`find /media/nas/EXTRA/Ubuntu_Touch/out/target/product/falcon/system/lib/modules -type f -name modules.order`; if [ "$mdpath" != "" ];then mpath=`dirname $mdpath`; ko=`find $mpath/kernel -type f -name *.ko`; for i in $ko; do /media/nas/EXTRA/Ubuntu_Touch/prebuilts/gcc/linux-x86/arm/arm-eabi-4.7/bin/arm-eabi-strip --strip-unneeded $i; mv $i /media/nas/EXTRA/Ubuntu_Touch/out/target/product/falcon/system/lib/modules/; done; fi
mdpath=`find /media/nas/EXTRA/Ubuntu_Touch/out/target/product/falcon/system/lib/modules -type f -name modules.order`; if [ "$mdpath" != "" ];then mpath=`dirname $mdpath`; rm -rf $mpath; fi
target Prebuilt: (/media/nas/EXTRA/Ubuntu_Touch/out/target/product/falcon/kernel)
Start DT image: /media/nas/EXTRA/Ubuntu_Touch/out/target/product/falcon/dt.img
mkdir -p /media/nas/EXTRA/Ubuntu_Touch/out/target/product/falcon/obj/KERNEL_OBJ/arch/arm/boot; /media/nas/EXTRA/Ubuntu_Touch/out/target/product/falcon/obj/KERNEL_OBJ/scripts/dtc/dtc -p 1024 -O dtb -o /media/nas/EXTRA/Ubuntu_Touch/out/target/product/falcon/obj/KERNEL_OBJ/arch/arm/boot/msm8226-falcon-p1.dtb ./kernel/motorola/msm8226/arch/arm/boot/dts/msm8226-falcon-p1.dts; cat /media/nas/EXTRA/Ubuntu_Touch/out/target/product/falcon/obj/KERNEL_OBJ/arch/arm/boot/zImage /media/nas/EXTRA/Ubuntu_Touch/out/target/product/falcon/obj/KERNEL_OBJ/arch/arm/boot/msm8226-falcon-p1.dtb > /media/nas/EXTRA/Ubuntu_Touch/out/target/product/falcon/obj/KERNEL_OBJ/arch/arm/boot/msm8226-falcon-p1-zImage; /media/nas/EXTRA/Ubuntu_Touch/out/target/product/falcon/obj/KERNEL_OBJ/scripts/dtc/dtc -p 1024 -O dtb -o /media/nas/EXTRA/Ubuntu_Touch/out/target/product/falcon/obj/KERNEL_OBJ/arch/arm/boot/msm8226-falcon-p2b1.dtb ./kernel/motorola/msm8226/arch/arm/boot/dts/msm8226-falcon-p2b1.dts; cat /media/nas/EXTRA/Ubuntu_Touch/out/target/product/falcon/obj/KERNEL_OBJ/arch/arm/boot/zImage /media/nas/EXTRA/Ubuntu_Touch/out/target/product/falcon/obj/KERNEL_OBJ/arch/arm/boot/msm8226-falcon-p2b1.dtb > /media/nas/EXTRA/Ubuntu_Touch/out/target/product/falcon/obj/KERNEL_OBJ/arch/arm/boot/msm8226-falcon-p2b1-zImage; /media/nas/EXTRA/Ubuntu_Touch/out/target/product/falcon/obj/KERNEL_OBJ/scripts/dtc/dtc -p 1024 -O dtb -o /media/nas/EXTRA/Ubuntu_Touch/out/target/product/falcon/obj/KERNEL_OBJ/arch/arm/boot/msm8226-falcon-p2b.dtb ./kernel/motorola/msm8226/arch/arm/boot/dts/msm8226-falcon-p2b.dts; cat /media/nas/EXTRA/Ubuntu_Touch/out/target/product/falcon/obj/KERNEL_OBJ/arch/arm/boot/zImage /media/nas/EXTRA/Ubuntu_Touch/out/target/product/falcon/obj/KERNEL_OBJ/arch/arm/boot/msm8226-falcon-p2b.dtb > /media/nas/EXTRA/Ubuntu_Touch/out/target/product/falcon/obj/KERNEL_OBJ/arch/arm/boot/msm8226-falcon-p2b-zImage; /media/nas/EXTRA/Ubuntu_Touch/out/target/product/falcon/obj/KERNEL_OBJ/scripts/dtc/dtc -p 1024 -O dtb -o /media/nas/EXTRA/Ubuntu_Touch/out/target/product/falcon/obj/KERNEL_OBJ/arch/arm/boot/msm8226-falcon-p2.dtb ./kernel/motorola/msm8226/arch/arm/boot/dts/msm8226-falcon-p2.dts; cat /media/nas/EXTRA/Ubuntu_Touch/out/target/product/falcon/obj/KERNEL_OBJ/arch/arm/boot/zImage /media/nas/EXTRA/Ubuntu_Touch/out/target/product/falcon/obj/KERNEL_OBJ/arch/arm/boot/msm8226-falcon-p2.dtb > /media/nas/EXTRA/Ubuntu_Touch/out/target/product/falcon/obj/KERNEL_OBJ/arch/arm/boot/msm8226-falcon-p2-zImage; /media/nas/EXTRA/Ubuntu_Touch/out/target/product/falcon/obj/KERNEL_OBJ/scripts/dtc/dtc -p 1024 -O dtb -o /media/nas/EXTRA/Ubuntu_Touch/out/target/product/falcon/obj/KERNEL_OBJ/arch/arm/boot/msm8226-falcon-p2-v2.dtb ./kernel/motorola/msm8226/arch/arm/boot/dts/msm8226-falcon-p2-v2.dts; cat /media/nas/EXTRA/Ubuntu_Touch/out/target/product/falcon/obj/KERNEL_OBJ/arch/arm/boot/zImage /media/nas/EXTRA/Ubuntu_Touch/out/target/product/falcon/obj/KERNEL_OBJ/arch/arm/boot/msm8226-falcon-p2-v2.dtb > /media/nas/EXTRA/Ubuntu_Touch/out/target/product/falcon/obj/KERNEL_OBJ/arch/arm/boot/msm8226-falcon-p2-v2-zImage; /media/nas/EXTRA/Ubuntu_Touch/out/target/product/falcon/obj/KERNEL_OBJ/scripts/dtc/dtc -p 1024 -O dtb -o /media/nas/EXTRA/Ubuntu_Touch/out/target/product/falcon/obj/KERNEL_OBJ/arch/arm/boot/msm8226-falcon-p3c.dtb ./kernel/motorola/msm8226/arch/arm/boot/dts/msm8226-falcon-p3c.dts; cat /media/nas/EXTRA/Ubuntu_Touch/out/target/product/falcon/obj/KERNEL_OBJ/arch/arm/boot/zImage /media/nas/EXTRA/Ubuntu_Touch/out/target/product/falcon/obj/KERNEL_OBJ/arch/arm/boot/msm8226-falcon-p3c.dtb > /media/nas/EXTRA/Ubuntu_Touch/out/target/product/falcon/obj/KERNEL_OBJ/arch/arm/boot/msm8226-falcon-p3c-zImage;
----- Making recovery image ------
Copying baseline ramdisk...
Modifying ramdisk contents...
mkdir -p /media/nas/EXTRA/Ubuntu_Touch/out/target/product/falcon/recovery/root/system/bin
Modifying default.prop
sed -i 's/ro.build.date.utc=.*/ro.build.date.utc=0/g' /media/nas/EXTRA/Ubuntu_Touch/out/target/product/falcon/recovery/root/default.prop
sed -i 's/ro.adb.secure=1//g' /media/nas/EXTRA/Ubuntu_Touch/out/target/product/falcon/recovery/root/default.prop
----- Made recovery filesystem --------/media/nas/EXTRA/Ubuntu_Touch/out/target/product/falcon/recovery/root
----- Making uncompressed recovery ramdisk ------
/media/nas/EXTRA/Ubuntu_Touch/out/host/linux-x86/bin/mkbootfs /media/nas/EXTRA/Ubuntu_Touch/out/target/product/falcon/recovery/root > /media/nas/EXTRA/Ubuntu_Touch/out/target/product/falcon/ramdisk-recovery.cpio
----- Making recovery ramdisk ------
/media/nas/EXTRA/Ubuntu_Touch/out/host/linux-x86/bin/minigzip < /media/nas/EXTRA/Ubuntu_Touch/out/target/product/falcon/ramdisk-recovery.cpio > /media/nas/EXTRA/Ubuntu_Touch/out/target/product/falcon/ramdisk-recovery.img
Target dt image: /media/nas/EXTRA/Ubuntu_Touch/out/target/product/falcon/dt.img
DTB combiner:
Input directory: '/media/nas/EXTRA/Ubuntu_Touch/out/target/product/falcon/obj/KERNEL_OBJ/arch/arm/boot/'
Output file: '/media/nas/EXTRA/Ubuntu_Touch/out/target/product/falcon/dt.img'
Found file: msm8226-falcon-p2.dtb ... chipset: 145, rev: 33280, platform: 66, subtype: 0
Found file: msm8226-falcon-p2-v2.dtb ... chipset: 145, rev: 164352, platform: 66, subtype: 0
Found file: msm8226-falcon-p2b1.dtb ... chipset: 145, rev: 164529, platform: 66, subtype: 0
Found file: msm8226-falcon-p3c.dtb ... chipset: 145, rev: 164800, platform: 66, subtype: 0
Found file: msm8226-falcon-p2b.dtb ... chipset: 145, rev: 164528, platform: 66, subtype: 0
Found file: msm8226-falcon-p1.dtb ... chipset: 145, rev: 33024, platform: 66, subtype: 0
=> Found 6 unique DTB(s)
Generating master DTB... completed
Made DT image: /media/nas/EXTRA/Ubuntu_Touch/out/target/product/falcon/dt.img
----- Making recovery image ------
usage: mkbootimg
--kernel <filename>
--ramdisk <filename>
[ --second <2ndbootloader-filename> ]
[ --cmdline <kernel-commandline> ]
[ --board <boardname> ]
[ --base <address> ]
[ --pagesize <pagesize> ]
-o|--output <filename>
make: *** [/media/nas/EXTRA/Ubuntu_Touch/out/target/product/falcon/recovery.img] Error 1
I hope you'll be luckier as me ...
Thanks you !
PS :
my roomservice.xml
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remove-project name="aosp/platform/hardware/qcom/audio" />
<remove-project name="aosp/platform/hardware/qcom/display" />
<remove-project name="aosp/platform/hardware/qcom/media" />
<remove-project name="aosp/platform/hardware/qcom/keymaster" />
<project name="razrqcom-dev-team/android_device_motorola_qcom-common" path="device/motorola/qcom-common" remote="github" revision="kitkat" />
<project name="CyanogenMod/android_kernel_motorola_msm8226" path="kernel/motorola/msm8226" remote="github" revision="cm-11.0" />
<project name="razrqcom-dev-team/android_device_motorola_falcon" path="device/motorola/falcon" remote="github" revision="cm-11.0" />
<project name="razrqcom-dev-team/android_device_motorola_msm8226-common" path="device/motorola/msm8226-common" remote="github" revision="cm-11.0" />
<project name="CyanogenMod/android_hardware_qcom_display-caf-new" path="hardware/qcom/display" remote="github" revision="cm-11.0" />
<project name="CyanogenMod/android_hardware_qcom_fm" path="hardware/qcom/fm" remote="github" revision="cm-11.0" />
<project name="CyanogenMod/android_hardware_qcom_media-caf-new" path="hardware/qcom/media" remote="github" revision="cm-11.0" />
<project name="CyanogenMod/android_device_qcom_common" path="device/qcom/common" remote="github" revision="cm-11.0" />
<project name="TheMuppets/proprietary_vendor_motorola" path="vendor/motorola" remote="github" revision="cm-11.0" />
<project name="CyanogenMod/android_hardware_qcom_keymaster" path="hardware/qcom/keymaster" remote="github" revision="cm-11.0" />
</manifest>
EDIT :
I fix it by modifing the /device/motorola/msm8226-common/mkbootimg.mk like this :
Code:
LOCAL_PATH := $(call my-dir)
## Don't change anything under here. The variables are named MSM8226_whatever
## on purpose, to avoid conflicts with similarly named variables at other
## parts of the build environment
## Imported from the original makefile...
KERNEL_CONFIG := $(KERNEL_OUT)/.config
MSM8226_DTS_NAMES := msm8226
MSM8226_DTS_FILES = $(wildcard $(TOP)/$(TARGET_KERNEL_SOURCE)/arch/arm/boot/dts/msm8226-falcon*.dts)
MSM8226_DTS_FILE = $(lastword $(subst /, ,$(1)))
DTB_FILE = $(addprefix $(KERNEL_OUT)/arch/arm/boot/,$(patsubst %.dts,%.dtb,$(call MSM8226_DTS_FILE,$(1))))
ZIMG_FILE = $(addprefix $(KERNEL_OUT)/arch/arm/boot/,$(patsubst %.dts,%-zImage,$(call MSM8226_DTS_FILE,$(1))))
KERNEL_ZIMG = $(KERNEL_OUT)/arch/arm/boot/zImage
DTC = $(KERNEL_OUT)/scripts/dtc/dtc
define append-msm8226-dtb
mkdir -p $(KERNEL_OUT)/arch/arm/boot;\
$(foreach MSM8226_DTS_NAME, $(MSM8226_DTS_NAMES), \
$(foreach d, $(MSM8226_DTS_FILES), \
$(DTC) -p 1024 -O dtb -o $(call DTB_FILE,$(d)) $(d); \
cat $(KERNEL_ZIMG) $(call DTB_FILE,$(d)) > $(call ZIMG_FILE,$(d));))
endef
## Build and run dtbtool
DTBTOOL := $(HOST_OUT_EXECUTABLES)/dtbToolCM$(HOST_EXECUTABLE_SUFFIX)
INSTALLED_DTIMAGE_TARGET := $(PRODUCT_OUT)/dt.img
$(INSTALLED_DTIMAGE_TARGET): $(DTBTOOL) $(TARGET_OUT_INTERMEDIATES)/KERNEL_OBJ/usr $(INSTALLED_KERNEL_TARGET)
@echo -e ${CL_CYN}"Start DT image: [email protected]"${CL_RST}
$(call append-msm8226-dtb)
$(call pretty,"Target dt image: $(INSTALLED_DTIMAGE_TARGET)")
$(hide) $(DTBTOOL) -o $(INSTALLED_DTIMAGE_TARGET) -s $(BOARD_KERNEL_PAGESIZE) -p $(KERNEL_OUT)/scripts/dtc/ $(KERNEL_OUT)/arch/arm/boot/
@echo -e ${CL_CYN}"Made DT image: [email protected]"${CL_RST}
## Overload bootimg generation: Same as the original, + --dt arg
$(INSTALLED_BOOTIMAGE_TARGET): $(MKBOOTIMG) $(INTERNAL_BOOTIMAGE_FILES) $(INSTALLED_DTIMAGE_TARGET)
$(call pretty,"Target boot image: [email protected]")
#$(hide) $(MKBOOTIMG) $(INTERNAL_BOOTIMAGE_ARGS) $(BOARD_MKBOOTIMG_ARGS) --dt $(INSTALLED_DTIMAGE_TARGET) --output [email protected]
$(hide) $(MKBOOTIMG) $(INTERNAL_BOOTIMAGE_ARGS) $(BOARD_MKBOOTIMG_ARGS) --output [email protected]
$(hide) $(call assert-max-image-size,[email protected],$(BOARD_BOOTIMAGE_PARTITION_SIZE),raw)
@echo -e ${CL_CYN}"Made boot image: [email protected]"${CL_RST}
## Overload recoveryimg generation: Same as the original, + --dt arg
$(INSTALLED_RECOVERYIMAGE_TARGET): $(MKBOOTIMG) $(INSTALLED_DTIMAGE_TARGET) \
$(recovery_ramdisk) \
$(recovery_kernel)
@echo -e ${CL_CYN}"----- Making recovery image ------"${CL_RST}
#$(hide) $(MKBOOTIMG) $(INTERNAL_RECOVERYIMAGE_ARGS) $(BOARD_MKBOOTIMG_ARGS) --dt $(INSTALLED_DTIMAGE_TARGET) --output [email protected]
$(hide) $(MKBOOTIMG) $(INTERNAL_RECOVERYIMAGE_ARGS) $(BOARD_MKBOOTIMG_ARGS) --output [email protected]
$(hide) $(call assert-max-image-size,[email protected],$(BOARD_RECOVERYIMAGE_PARTITION_SIZE),raw)
@echo -e ${CL_CYN}"Made recovery image: [email protected]"${CL_RST}
I knew this fix before but I don't know if it will work...

Hopefully we will see it working, I'm not a developer, so I can't tell you
Sent from my XT1033 using XDA Free mobile app

I'm still a complete noob at this, i couldn't even get the stock kernel compiling w/o modifications, but could you please translate in english these french output so i may take a look? Thanks in advance
Sent from me using my tablet using an app.

I see the output text in English...

There are some lines in french :/
Sent from me using my tablet using an app.

I'll translate x)
Sent from my Moto G using XDA Free mobile app

Stay tune
Sent from my Moto G using Cyanogenmod 11

I speak a bit of French
attention : écrasement des commandes pour la cible
warning (attention): crushing commands for target?!
anciennes commandes ignorées pour la cible
ignored commands
quittant le répertoire
quitting register (library)

I'll translate in 2 hours
Sent from my Moto G using XDA Free mobile app
EDIT : TRANSLATED

I'll be happy to test this when it'll be available!

eagleofdeath13 said:
I'll be happy to test this when it'll be available!
Click to expand...
Click to collapse
I'll upload the test build today
Sent from my Moto G using XDA Free mobile app

h2o64 said:
I'll upload the test build today
Sent from my Moto G using XDA Free mobile app
Click to expand...
Click to collapse
Will it boot at least?

S0bes said:
Will it boot at least?
Click to expand...
Click to collapse
I don't know ^^ but if it is not... The community is here de solved this!
Sent from my Moto G using XDA Free mobile app

Nice Try! Keep it up

h2o64 said:
I don't know ^^ but if it is not... The community is here de solved this!
Sent from my Moto G using XDA Free mobile app
Click to expand...
Click to collapse
You should find some dev with experience willing to help you, I've seen many Ubuntu projects that never worked. Do you know if at least someone achieved a working image for any phone at all? Cause I doubt things will just get solved by throwing your build here.

fermasia said:
You should find some dev with experience willing to help you, I've seen many Ubuntu projects that never worked. Do you know if at least someone achieved a working image for any phone at all? Cause I doubt things will just get solved by throwing your build here.
Click to expand...
Click to collapse
Building IS FOR FUN ! I've work. And I put my results there. Maybe some awesome devs will find this topic. If not ... I DON'T CARE.
But if you guys know someone who can help this project. Please help him to contact me (I'm the first dev for Ubuntu Touch on falcon).

Any news?

eagleofdeath13 said:
Any news?
Click to expand...
Click to collapse
I recommand you to look at here : [Ubuntu Touch - Utopic][PORT][WIP][Test-BUILD] Ubuntu Touch for falcon ! :laugh:

Thanks
Sent from my XT1032 using XDA Premium 4 mobile app

is msm8916-common necessary for tomato
hi everyone,
i am trying to build ubuntu touch for tomato (32bit kk cm-11.0)
but it has no repository for cm-11.0 msm8916-common (32bit) but only cm-12.1 and cm-13 (64bit).
https://github.com/CyanogenMod/android_device_cyanogen_msm8916-common
what to do guys help.....

bliss install failed

i used x86 installer for installing bliss os in my hp laptop and this showing error install failed and log
================Installer Info================
Installer Directory:C:\Users\Ram Kankar\Downloads\Programs\Androidx86-Installv26.0003
Installer Version:2.6.0.0
Secure Boot ... Disabled
Manufacturer: HP
Model: HP Notebook
Product: 81EB
BIOS info:
HPQOEM - 0
F.24
INSYDE Corp. - F240000
Available GPU(s):
GPU: Intel(R) HD Graphics 520
=============[REQUIREMENTS CHECK]============
Administrator privilege ... ok
CPU Architecture: 9
CPU Name: Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz
OSVer: Microsoft Windows NT 10.0.16299.0
OperatingSystem Version ... ok
Windows Security: Access NVRAM Privilege ... Not All Set
System Firmware: UEFI
==========================================
====Install Started on 28-03-2018 19:43:28====
-ISO File: C:\Users\Ram Kankar\Downloads\Bliss-v7.2-android_x86_64-OFFICIAL-20171014-1217_k4.9.iso
-TargetDrive: G
-UserData: 25165824
-Setup Directories...
-Folder Created: G:\AndroidOS
-Extracting ISO
#Launch:C:\Users\Ram Kankar\Downloads\Programs\Androidx86-Installv26.0003\7z.exe x "C:\Users\Ram Kankar\Downloads\Bliss-v7.2-android_x86_64-OFFICIAL-20171014-1217_k4.9.iso" "kernel" "ramdisk.img" "initrd.img" "system.*" -oG:\AndroidOS
#Launch:C:\Users\Ram Kankar\Downloads\Programs\Androidx86-Installv26.0003\7z.exe e "C:\Users\Ram Kankar\Downloads\Bliss-v7.2-android_x86_64-OFFICIAL-20171014-1217_k4.9.iso" "boot\grub\grub.cfg" -oG:\AndroidOS
-Creating Data.img
#Launch:C:\Users\Ram Kankar\Downloads\Programs\Androidx86-Installv26.0003\dd.exeif=/dev/zero of=G:\AndroidOS\data.img count=25165824
-Initialize Data.img
#Launch:C:\Users\Ram Kankar\Downloads\Programs\Androidx86-Installv26.0003\mke2fs.exe-F -t ext4 "G:\AndroidOS\data.img"
===Installing Boot Objects===
-Mounting EFI Partition...
#Launch:C:\Windows\System32\mountvol.exe Z: /S
-Setup Boot Directory...
-Boot Folder Created: Z:\EFI\boot\
-Copy Boot files
-Add UEFI Entry
UEFI Init Fail
==============Revert Installation==============
-Cleaning up Bliss Directory ... G:\AndroidOS
===Removing Boot Objects===
-Mounting EFI Partition...
#Launch:C:\Windows\System32\mountvol.exe Z: /S
Error Executing C:\Windows\System32\mountvol.exe with Args: Z: /S
Error output:
The directory is not empty.
-UEFI Init ... fail
-Cleaning up Bliss Directory ... Z:\EFI\boot\
-UnMounting EFI Partition...
#Launch:C:\Windows\System32\mountvol.exe Z: /D
==========================================
uefidbg log
===logging started===
BootCount: 6
Boot0002,0 : Windows Boot Manager
Boot3002,1 : Internal Hard Disk or Solid State Disk
Boot0000,2 : Notebook Hard Drive - TOSHIBA MQ01ABD100
Boot2001,3 : EFI USB Device
Boot2002,4 : EFI DVD/CDROM
Fail to Read BootOptions, 5
BootCount: 6
Boot0002,0 : Windows Boot Manager
Boot3002,1 : Internal Hard Disk or Solid State Disk
Boot0000,2 : Notebook Hard Drive - TOSHIBA MQ01ABD100
Boot2001,3 : EFI USB Device
Boot2002,4 : EFI DVD/CDROM
Fail to Read BootOptions, 5
BootCount: 6
Boot0002,0 : Windows Boot Manager
Boot3002,1 : Internal Hard Disk or Solid State Disk
Boot0000,2 : Notebook Hard Drive - TOSHIBA MQ01ABD100
Boot2001,3 : EFI USB Device
Boot2002,4 : EFI DVD/CDROM
Fail to Read BootOptions, 5
plz give me solution for this error , thanks in advance

Looks like it couldn't mount the UEFI partition. You should make sure that the Z: mount location isn't taken already

electrikjesus said:
Looks like it couldn't mount the UEFI partition. You should make sure that the Z: mount location isn't taken already
Click to expand...
Click to collapse
and how do we check that? im looking for new android os systems since i cant boot to phoenix os because my pc is uefi and i dont know how to fix it, but still cant install bliss wich is the OS that caught more my attention, plz help

UEFI Init Fail
electrikjesus said:
Looks like it couldn't mount the UEFI partition. You should make sure that the Z: mount location isn't taken already
Click to expand...
Click to collapse
I encountered exactly the same problem as the OP did, and no, the Z: mount location isn't taken. Any solution?
================Installer Info================
Installer Directory:C:\Users\Administrator\AppData\Local\Temp\RarSFX0
Installer Version:2.6.0.0
Secure Boot ... Disabled
Manufacturer: HP
Model: HP Notebook
Product: 81EE
BIOS info:
HPQOEM - 0
F.43
INSYDE Corp. - F430000
Available GPU(s):
GPU: AMD Radeon (TM) R5 M330
GPU: Intel(R) HD Graphics 620
=============[REQUIREMENTS CHECK]============
Administrator privilege ... ok
CPU Architecture: 9
CPU Name: Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz
OSVer: Microsoft Windows NT 10.0.17134.0
OperatingSystem Version ... ok
Windows Security: Access NVRAM Privilege ... Not All Set
System Firmware: UEFI
==========================================
====Install Started on 29-Oct-18 10:31:06 PM====
-ISO File: D:\Android\Bliss-v10.1-Beta-android_x86_64-NIGHTLY-20180808-0022_k4.16.5-blissified_2.iso
-TargetDrive: C
-UserData: 18853396
-Setup Directories...
-Folder Created: C:\AndroidOS
-Extracting ISO
#Launch:C:\Users\Administrator\AppData\Local\Temp\RarSFX0\7z.exe x "D:\Android\Bliss-v10.1-Beta-android_x86_64-NIGHTLY-20180808-0022_k4.16.5-blissified_2.iso" "kernel" "ramdisk.img" "initrd.img" "system.*" -oC:\AndroidOS
#Launch:C:\Users\Administrator\AppData\Local\Temp\RarSFX0\7z.exe e "D:\Android\Bliss-v10.1-Beta-android_x86_64-NIGHTLY-20180808-0022_k4.16.5-blissified_2.iso" "boot\grub\grub.cfg" -oC:\AndroidOS
-Creating Data.img
#Launch:C:\Users\Administrator\AppData\Local\Temp\RarSFX0\dd.exeif=/dev/zero of=C:\AndroidOS\data.img count=18853396
-Initialize Data.img
#Launch:C:\Users\Administrator\AppData\Local\Temp\RarSFX0\mke2fs.exe-F -t ext4 "C:\AndroidOS\data.img"
===Installing Boot Objects===
-Mounting EFI Partition...
#Launch:C:\Windows\System32\mountvol.exe Z: /S
-Setup Boot Directory...
-Boot Folder Created: Z:\EFI\boot\
-Copy Boot files
-Add UEFI Entry
UEFI Init Fail
==============Revert Installation==============
-Cleaning up Bliss Directory ... C:\AndroidOS
===Removing Boot Objects===
-Mounting EFI Partition...
#Launch:C:\Windows\System32\mountvol.exe Z: /S
Error Executing C:\Windows\System32\mountvol.exe with Args: Z: /S
Error output:
The directory is not empty.
-UEFI Init ... fail
-Cleaning up Bliss Directory ... Z:\EFI\boot\
-UnMounting EFI Partition...
#Launch:C:\Windows\System32\mountvol.exe Z: /D
==========================================

how to wipe Z: partition? i got same problem pls help me
---------- Post added at 01:43 PM ---------- Previous post was at 01:16 PM ----------
electrikjesus said:
Looks like it couldn't mount the UEFI partition. You should make sure that the Z: mount location isn't taken already
Click to expand...
Click to collapse
How to solve it? since we're not expert why you dont help us?

VMolina141 said:
and how do we check that? im looking for new android os systems since i cant boot to phoenix os because my pc is uefi and i dont know how to fix it, but still cant install bliss wich is the OS that caught more my attention, plz help
Click to expand...
Click to collapse
Just find out bliss broke my Z: dir after uninstall it,, and now i cant install another Android OS because it. Damn god im regret using bliss

bad primary partition zero petition ends in the final partial cylinder
is the error i am getting when trying to install bliss os

I know this thread is old but this may help future people googling a solution
Here's what I did to fix this error...
==============Revert Installation==============
-Cleaning up Bliss Directory ... C:\AndroidOS
===Removing Boot Objects===
-Mounting EFI Partition...
#Launch:C:\Windows\System32\mountvol.exe Z: /S
Error Executing C:\Windows\System32\mountvol.exe with Args: Z: /S
Error output:
The directory is not empty.
-UEFI Init ... fail
-Cleaning up Bliss Directory ... Z:\EFI\boot\
-UnMounting EFI Partition...
#Launch:C:\Windows\System32\mountvol.exe Z: /D
==========================================
I ran CMD as Administrator and ran the command
mountvol Z: /d
You can also try running CMD and entering the command in "Safe Mode" as suggested on other threads

Bliss OS is a ****ing disaster. Ruined my ****ing day. Didn't install for some reason and got rid of winload.efi also

Poads said:
I know this thread is old but this may help future people googling a solution
Here's what I did to fix this error...
==============Revert Installation==============
-Cleaning up Bliss Directory ... C:\AndroidOS
===Removing Boot Objects===
-Mounting EFI Partition...
#Launch:C:\Windows\System32\mountvol.exe Z: /S
Error Executing C:\Windows\System32\mountvol.exe with Args: Z: /S
Error output:
The directory is not empty.
-UEFI Init ... fail
-Cleaning up Bliss Directory ... Z:\EFI\boot\
-UnMounting EFI Partition...
#Launch:C:\Windows\System32\mountvol.exe Z: /D
==========================================
I ran CMD as Administrator and ran the command
mountvol Z: /d
You can also try running CMD and entering the command in "Safe Mode" as suggested on other threads
Click to expand...
Click to collapse
Not working for me, unfortunately

Aaaahhhh yes, it feels good to not feel so much hate alone towards Bliss at the god that moment!!!!

Poads said:
I know this thread is old but this may help future people googling a solution
Here's what I did to fix this error...
==============Revert Installation==============
-Cleaning up Bliss Directory ... C:\AndroidOS
===Removing Boot Objects===
-Mounting EFI Partition...
#Launch:C:\Windows\System32\mountvol.exe Z: /S
Error Executing C:\Windows\System32\mountvol.exe with Args: Z: /S
Error output:
The directory is not empty.
-UEFI Init ... fail
-Cleaning up Bliss Directory ... Z:\EFI\boot\
-UnMounting EFI Partition...
#Launch:C:\Windows\System32\mountvol.exe Z: /D
==========================================
I ran CMD as Administrator and ran the command
mountvol Z: /d
You can also try running CMD and entering the command in "Safe Mode" as suggested on other threads
Click to expand...
Click to collapse
after this, i cant the drive i want to install in?? no drive z
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

check android .img type

hello
how to check android img type?
recovery ...
boot ...
system ...
...
example:
input user : 'only import boot .img : '
if input == boot:
code
if input != boot:
error , only boot .img file ...
example 2 :
input : 'img file : '
print => input type is 'boot' or 'recovery' and other .img file type ...
please help me ...
tnx ...