Database Info

[DEV][Info] BoardConfig.mk for kernel developer and AOSP (platform) developer

So this is a major news for devs, if you found your AOSP / CM build doesn't work, make sure that you have the following line enabled if you are using TARGET_ARCH_VARIANT := armv7-a :
TARGET_ARCH_VARIANT_FPU := vfpv3-d16
This is due to a bug in armv7-a.mk in CM repo that automatically set FPU to neno for no reason. (btw, I have already reported the bug, so lets see it get patched or not later)
btw DO NOT change the line of TARGET_ARCH_VARIANT_FPU to vfpv3, otherwise your CM / AOSP build will not boot @ all.
The following BoardConfig.mk is used for compiling CWM on my kernels. And it is working for compiling CWM on my machine. You can edit the line such as USE_CAMERA_STUB, TARGET_NO_RADIOIMAGE or TARGET_PREBUILT_KERNEL on your own. However do not edit the line since TARGET_CPU_ABI to BOARD_FLASH_BLOCK_SIZE as they are vital and already right for our I9103.
Code:
LOCAL_PATH := $(call my-dir)
#USE_CAMERA_STUB := true
# inherit from the proprietary version
-include vendor/samsung/I9103/BoardConfigVendor.mk
TARGET_CPU_ABI := armeabi-v7a
TARGET_CPU_ABI2 := armeabi
TARGET_ARCH_VARIANT := armv7-a
TARGET_ARCH_VARIANT_CPU := cortex-a9
# DO NOT change the following line to vfpv3 as it is not really supported on our device!
TARGET_ARCH_VARIANT_FPU := vfpv3-d16
TARGET_CPU_SMP := true
ARCH_ARM_HAVE_TLS_REGISTER := true
TARGET_HAVE_TEGRA_ERRATA_657451 := true
TARGET_BOARD_PLATFORM := tegra
TARGET_BOARD_PLATFORM_GPU := tegra # Useless for CM7 build
TARGET_BOOTLOADER_BOARD_NAME := n1
TARGET_USERIMAGES_USE_EXT4 := true
BOARD_KERNEL_CMDLINE :=
BOARD_KERNEL_BASE := 0x10000000
BOARD_KERNEL_PAGESIZE := 2048
# fix this up by examining /proc/mtd on a running device
# Boot image size is 16384 x 512 bytes = 8388608
# You can double check it with fdisk -l /dev/block/mmcblk0p8
BOARD_BOOTIMAGE_PARTITION_SIZE := 0x00800000
# Recovery image size is 10240 x 512 bytes = 5242880
# You can double check it with fdisk -l /dev/block/mmcblk0p8
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 0x00500000
# System image size is 1228800 x 512 bytes = 629145600
# You can double check it with fdisk -l /dev/block/mmcblk0p2
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 0x25800000
# User data image size is 4194304 x 512 bytes = 2147483648
# You can double check it with fdisk -l /dev/block/mmcblk0p6
BOARD_USERDATAIMAGE_PARTITION_SIZE := 0x80000000
BOARD_FLASH_BLOCK_SIZE := 2048
TARGET_PREBUILT_KERNEL := device/samsung/I9103/kernel
TARGET_NO_KERNEL := false
TARGET_NO_RECOVERY := false
TARGET_NO_BOOTLOADER := true
TARGET_NO_RADIOIMAGE := true
BOARD_HAS_NO_SELECT_BUTTON := true
# Use this flag if the board has a ext4 partition larger than 2gb
BOARD_HAS_LARGE_FILESYSTEM := true
btw I have an updated version of armv7-a.mk so that it should work on any device using armv7-a even when FPU is not defined. If your toolchain is complaing errors like the switch -mcpu is not working with -march, just remove the -mcpu switch on your own.
Code:
# Configuration for Linux on ARM.
# Generating binaries for the ARMv7-a architecture and higher
#
ARCH_ARM_HAVE_THUMB_SUPPORT := true
ARCH_ARM_HAVE_FAST_INTERWORKING := true
ARCH_ARM_HAVE_64BIT_DATA := true
ARCH_ARM_HAVE_HALFWORD_MULTIPLY := true
ARCH_ARM_HAVE_CLZ := true
ARCH_ARM_HAVE_FFS := true
ARCH_ARM_HAVE_ARMV7A := true
ifeq ($(strip $(TARGET_ARCH_VARIANT_FPU)),)
ARCH_ARM_HAVE_VFP := false
else
ARCH_ARM_HAVE_VFP := true
endif
ifeq ($(strip $(TARGET_ARCH_VARIANT_FPU)),neon)
ARCH_ARM_HAVE_NEON := true
endif
ifeq ($(strip $(TARGET_CPU_SMP)),true)
ARCH_ARM_HAVE_TLS_REGISTER := true
endif
arch_variant_cflags := \
-march=armv7-a \
-mtune=$(strip $(TARGET_ARCH_VARIANT_CPU)) \
-mcpu=$(strip $(TARGET_ARCH_VARIANT_CPU)) \
-D__ARM_ARCH_7__ \
-D__ARM_ARCH_7A__
ifeq ($(strip $(ARCH_ARM_HAVE_VFP)),true)
ifeq ($(strip $(ARCH_ARM_HAVE_NEON)),true)
arch_variant_cflags += -D__ARM_NEON__ -D__ARM_HAVE_NEON
else
arch_variant_cflags += -D__VFP_FP__ -D__ARM_HAVE_VFP
endif
arch_variant_cflags += -mfloat-abi=softfp -mfpu=$(strip $(TARGET_ARCH_VARIANT_FPU))
else
arch_variant_cflags += -mfloat-abi=soft
endif
ifeq ($(strip $(TARGET_ARCH_VARIANT_CPU)),cortex-a8)
arch_variant_ldflags := \
-Wl,--fix-cortex-a8
else
arch_variant_ldflags :=
endif
In addition, please look at the required errata for building stuffs on our device.
As our device is using an epic old ARM cpu, it means that it may have errata inside. Errata means errors on the hardware that cannot be fixed, however can be bypassed with errata patch.
In conjunction with finding the required errata patch, this is our cpuinfo
cat /proc/cpuinfo
Processor : ARMv7 Processor rev 0 (v7l)
processor : 0
BogoMIPS : 999.42
processor : 1
BogoMIPS : 999.42
Features : swp half thumb fastmult vfp edsp vfpv3 vfpv3d16
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x1
CPU part : 0xc09
CPU revision : 0
Hardware : n1
Revision : 000d
Serial : 304d11d0943807ae
So next time when you try to make a custom kernel or port a kernel to this device, keep an eye on those errata please. Nvidia git sometimes made patch for those erratas as well.
For example, TARGET_HAVE_TEGRA_ERRATA_657451 is a config value telling that the src code to enable errata #657451 patch for our device. (And I have enabled that in our BoardConfig.mk already.)

Now though it sounds sad it works, but in that case does LG O2X's ARM also belong to our family of devices ?

.....that just kinda destroyed my hopes
This was sent from a Galaxy Ace. Problem?

'cooleagle' said:
Now though it sounds sad it works, but in that case does LG O2X's ARM also belong to our family of devices ?
Click to expand...
Click to collapse
its got the same AP20H tegra 2 processor i think

Because of this is it difficult to get ics .....
How its going to effect us......
according to Google policy company should provide s/w updates atleast for 16 months ....... So samy should provide ics update for us at that time they should correct the algorithms .... i am totally disturbed after seeing this.......
Sent from my GT-I9103 using XDA

mj.vikram said:
Because of this is it difficult to get ics .....
How its going to effect us......
according to Google policy company should provide s/w updates atleast for 16 months ....... So samy should provide ics update for us at that time they should correct the algorithms .... i am totally disturbed after seeing this.......
Sent from my GT-I9103 using XDA
Click to expand...
Click to collapse
Don't lose sleep over it. S2's design was also started in 2010.
We'll get ICS as LG O2X which has the same SOC is going to get it, moreover Samsung India has confirmed that this device is capable of being upgraded to ICS so sit tight till it arrives.

Please check the first topic again, it includes a specific change to BoardConfig.mk that allows anyone to build AOSP / CM for our board. Otherwise your CM7 won't boot from that.

UnknownzD said:
Please check the first topic again, it includes a specific change to BoardConfig.mk that allows anyone to build AOSP / CM for our board. Otherwise your CM7 won't boot from that.
Click to expand...
Click to collapse
Damn! you're good!
Where have you been all this time!
Thanks for all this good info!

UnknownzD you are Rolling in the Deep !
Hope to hear lots of goods news & info from you in near future man, keep them coming buddy . . . !
Cheers ! :beer:

FranzJesus said:
Damn! you're good!
Where have you been all this time!
Thanks for all this good info!
Click to expand...
Click to collapse
In case your build still doesn't work, create a armv7-a-test.mk file under /build/core/combo/arch/arm/ and then place the following lines into it. This is the working one that I can built CWM on top of it.
---------------------------------------------------------------------------
# Configuration for Linux on ARM.
# Generating binaries for the ARMv5TE architecture and higher
#
ARCH_ARM_HAVE_THUMB_SUPPORT := true
ARCH_ARM_HAVE_FAST_INTERWORKING := true
ARCH_ARM_HAVE_64BIT_DATA := true
ARCH_ARM_HAVE_HALFWORD_MULTIPLY := true
ARCH_ARM_HAVE_CLZ := true
ARCH_ARM_HAVE_FFS := true
ARCH_ARM_HAVE_ARMV7A := true
#ARCH_ARM_HAVE_VFP := true
# Note: Hard coding the 'tune' value here is probably not ideal,
# and a better solution should be found in the future.
#
arch_variant_cflags := \
-march=armv7-a \
-mtune=$(strip $(TARGET_ARCH_VARIANT_CPU)) \
-mcpu=$(strip $(TARGET_ARCH_VARIANT_CPU)) \
# -mfloat-abi=softfp \
# -mfpu=$(strip $(TARGET_ARCH_VARIANT_FPU)) \
-D__ARM_ARCH_7__ \
-D__ARM_ARCH_7A__
# -D__ARM_ARCH_5__ \
# -D__ARM_ARCH_5T__ \
# -D__ARM_ARCH_5E__ \
# -D__ARM_ARCH_5TE__
---------------------------------------------------------------------------
btw, you have to put the the first 2 lines into your BoardConfig.mk in order to enable it. The third line is optional unless you want enable the vfp calculation (which should be the one causing problem).
TARGET_ARCH_VARIANT := armv7-a-test
TARGET_ARCH_VARIANT_CPU := cortex-a9
TARGET_ARCH_VARIANT_FPU := vfpv3
I am still testing on what caused the problem. Seems like the vfp (floating point calculation) has a strong relationship to the halt problem.
Edited : Okay I have confirmed, the VFP part should be the one causing issue. You may want to disable it first and I will work that out later (to find where the bug is).

Where have you been Mate?? Awesome Work!! Continue!!

So I have figured out our right BoardConfig.mk. Do not change the TARGET_ARCH_VARIANT_FPU, otherwise the boot.img won't boot @ all.
LOCAL_PATH := $(call my-dir)
#USE_CAMERA_STUB := true
# inherit from the proprietary version
-include vendor/samsung/I9103/BoardConfigVendor.mk
TARGET_CPU_ABI := armeabi-v7a
TARGET_CPU_ABI2 := armeabi
TARGET_ARCH_VARIANT := armv7-a
TARGET_ARCH_VARIANT_CPU := cortex-a9
# DO NOT change the following line to vfpv3 as it is not supported on our device!
TARGET_ARCH_VARIANT_FPU := vfpv3-d16
TARGET_CPU_SMP := true
ARCH_ARM_HAVE_TLS_REGISTER := true
TARGET_HAVE_TEGRA_ERRATA_657451 := true
TARGET_BOARD_PLATFORM := tegra
TARGET_BOARD_PLATFORM_GPU := tegra # Useless for CM7 build
TARGET_BOOTLOADER_BOARD_NAME := n1
TARGET_USERIMAGES_USE_EXT4 := true
BOARD_KERNEL_CMDLINE :=
BOARD_KERNEL_BASE := 0x10000000
BOARD_KERNEL_PAGESIZE := 2048
# fix this up by examining /proc/mtd on a running device
# Boot image size is 16384 x 512 bytes = 8388608
# You can double check it with fdisk -l /dev/block/mmcblk0p8
BOARD_BOOTIMAGE_PARTITION_SIZE := 0x00800000
# Recovery image size is 10240 x 512 bytes = 5242880
# You can double check it with fdisk -l /dev/block/mmcblk0p8
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 0x00500000
# System image size is 1228800 x 512 bytes = 629145600
# You can double check it with fdisk -l /dev/block/mmcblk0p2
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 0x25800000
# User data image size is 4194304 x 512 bytes = 2147483648
# You can double check it with fdisk -l /dev/block/mmcblk0p6
BOARD_USERDATAIMAGE_PARTITION_SIZE := 0x80000000
BOARD_FLASH_BLOCK_SIZE := 2048
TARGET_PREBUILT_KERNEL := device/samsung/I9103/kernel
TARGET_NO_KERNEL := false
TARGET_NO_RECOVERY := false
TARGET_NO_BOOTLOADER := true
TARGET_NO_RADIOIMAGE := true
BOARD_HAS_NO_SELECT_BUTTON := true
# Use this flag if the board has a ext4 partition larger than 2gb
BOARD_HAS_LARGE_FILESYSTEM := true

btw the errata fix is for our cpu and is only needed on userland (non-kernel side binary), do not remove that errata fix otherwise the SMP part doesn't work. It requires the errata patch to make it working.

UnknownzD said:
So I have figured out our right BoardConfig.mk. Do not change the TARGET_ARCH_VARIANT_FPU, otherwise the boot.img won't boot @ all.
LOCAL_PATH := $(call my-dir)
#USE_CAMERA_STUB := true
# inherit from the proprietary version
-include vendor/samsung/I9103/BoardConfigVendor.mk
TARGET_CPU_ABI := armeabi-v7a
TARGET_CPU_ABI2 := armeabi
TARGET_ARCH_VARIANT := armv7-a
TARGET_ARCH_VARIANT_CPU := cortex-a9
# DO NOT change the following line to vfpv3 as it is not supported on our device!
TARGET_ARCH_VARIANT_FPU := vfpv3-d16
TARGET_CPU_SMP := true
ARCH_ARM_HAVE_TLS_REGISTER := true
TARGET_HAVE_TEGRA_ERRATA_657451 := true
TARGET_BOARD_PLATFORM := tegra
TARGET_BOARD_PLATFORM_GPU := tegra # Useless for CM7 build
TARGET_BOOTLOADER_BOARD_NAME := n1
TARGET_USERIMAGES_USE_EXT4 := true
BOARD_KERNEL_CMDLINE :=
BOARD_KERNEL_BASE := 0x10000000
BOARD_KERNEL_PAGESIZE := 2048
# fix this up by examining /proc/mtd on a running device
# Boot image size is 16384 x 512 bytes = 8388608
# You can double check it with fdisk -l /dev/block/mmcblk0p8
BOARD_BOOTIMAGE_PARTITION_SIZE := 0x00800000
# Recovery image size is 10240 x 512 bytes = 5242880
# You can double check it with fdisk -l /dev/block/mmcblk0p8
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 0x00500000
# System image size is 1228800 x 512 bytes = 629145600
# You can double check it with fdisk -l /dev/block/mmcblk0p2
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 0x25800000
# User data image size is 4194304 x 512 bytes = 2147483648
# You can double check it with fdisk -l /dev/block/mmcblk0p6
BOARD_USERDATAIMAGE_PARTITION_SIZE := 0x80000000
BOARD_FLASH_BLOCK_SIZE := 2048
TARGET_PREBUILT_KERNEL := device/samsung/I9103/kernel
TARGET_NO_KERNEL := false
TARGET_NO_RECOVERY := false
TARGET_NO_BOOTLOADER := true
TARGET_NO_RADIOIMAGE := true
BOARD_HAS_NO_SELECT_BUTTON := true
# Use this flag if the board has a ext4 partition larger than 2gb
BOARD_HAS_LARGE_FILESYSTEM := true
Click to expand...
Click to collapse
Compiling a CM7 build right now!!!
Will be back soon...
Thank you soo much!!

FranzJesus said:
Compiling a CM7 build right now!!!
Will be back soon...
Thank you soo much!!
Click to expand...
Click to collapse
If you guys want to see the difference between the old armv7-a.mk and my version, look it here : http://review.cyanogenmod.com/#/c/15478/1/core/combo/arch/arm/armv7-a.mk
Now I need some time to finish my CWM, by working on the ramdisk.

I have a minor update on the first post as changing the line
TARGET_ARCH_VARIANT_FPU := vfpv3
to
TARGET_ARCH_VARIANT_FPU := vfpv3-d16
That is because our device won't boot with the code compiled with -mfpu=vfpv3. Please refer to the first post for more info.

Wow you're good . My hat's off to you sire
This was sent from a Galaxy Ace. Problem?

Will the errata patch update the ARMv7 revision ?
This was sent from a Galaxy Ace. Problem?

EmoBoiix3 said:
Will the errata patch update the ARMv7 revision ?
This was sent from a Galaxy Ace. Problem?
Click to expand...
Click to collapse
The errata patch does not update the ARM revision (if you are talking the one captured from cpuinfo). That is because basically all the erratas cannot be patched as it is a hardware problem or bug. However, we can avoid such thing happens (such as errata in race condition) by applying the so called 'patch'. Therefore those patches are NOT fixing the problem at all, instead they just try to avoid it.

UnknownzD said:
The errata patch does not update the ARM revision (if you are talking the one captured from cpuinfo). That is because basically all the erratas cannot be patched as it is a hardware problem or bug. However, we can avoid such thing happens (such as errata in race condition) by applying the so called 'patch'. Therefore those patches are NOT fixing the problem at all, instead they just try to avoid it.
Click to expand...
Click to collapse
Ohh , you meant by workarounds !

[Q] porting CWM to Huawei MediaPad X1

i followed the cwm porting guide on xda-university and http://forum.xda-developers.com/showthread.php?t=2077608
but the device reboots to normal shortly after entering the flashed recovery
parsed the dumped recovery.img of my device, you find it here: http://mir.cr/XNQ7TACT
that's my BoardConfig.mk:
Code:
USE_CAMERA_STUB := true
# inherit from the proprietary version
-include vendor/HUAWEI/7D501U/BoardConfigVendor.mk
TARGET_ARCH := arm
TARGET_NO_BOOTLOADER := true
TARGET_BOARD_PLATFORM := unknown
TARGET_CPU_ABI := armeabi-v7a
TARGET_CPU_ABI2 := armeabi
TARGET_ARCH_VARIANT := armv7-a-neon
ARCH_ARM_HAVE_TLS_REGISTER := true
TARGET_USERIMAGES_USE_EXT4 := true
TARGET_BOOTLOADER_BOARD_NAME := 7D501U
BOARD_KERNEL_CMDLINE := k3v2mem k3v2_ion=1 androidboot.hardware=hw7d501l vmalloc=448M maxcpus=4 initcall_debug=n slub_debug=FZU
BOARD_KERNEL_BASE := 0x08600000
BOARD_KERNEL_PAGESIZE := 2048
# fix this up by examining /proc/mtd on a running device
BOARD_BOOTIMAGE_PARTITION_SIZE := 0x01000000
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 0x01000000
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 0x40000000
BOARD_USERDATAIMAGE_PARTITION_SIZE := 0x031f800000
BOARD_FLASH_BLOCK_SIZE := 65536
TARGET_PREBUILT_KERNEL := device/HUAWEI/7D501U/kernel
BOARD_HAS_NO_SELECT_BUTTON := true
BOARD_HAS_LARGE_FILESYSTEM := true
and unmodified recovery.fstab:
Code:
# mount point fstype device device2
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/system ext4 /dev/block/platform/hi_mci.0/by-name/system
/cache ext4 /dev/block/platform/hi_mci.0/by-name/cache
/tmpdata ext4 /dev/block/platform/hi_mci.0/by-name/userdata
/misc emmc /dev/block/platform/hi_mci.0/by-name/misc
/boot emmc /dev/block/platform/hi_mci.0/by-name/boot
/recovery emmc /dev/block/platform/hi_mci.0/by-name/recovery
/data ext4 /dev/block/platform/hi_mci.0/by-name/data
/cust ext4 /dev/block/platform/hi_mci.0/by-name/cust
/vrcb emmc /dev/block/platform/hi_mci.0/by-name/vrcb
here some reference: http://forum.xda-developers.com/showpost.php?p=51489222&postcount=41
using 10.1 branch of CM and builing on Ubuntu 13.10 on a DigitalOcean pay-per-hour Server

Tr4sHCr4fT said:
i followed the cwm porting guide on xda-university and http://forum.xda-developers.com/showthread.php?t=2077608
but the device reboots to normal shortly after entering the flashed recovery
parsed the dumped recovery.img of my device, you find it here: http://mir.cr/XNQ7TACT
that's my BoardConfig.mk:
Code:
USE_CAMERA_STUB := true
# inherit from the proprietary version
-include vendor/HUAWEI/7D501U/BoardConfigVendor.mk
TARGET_ARCH := arm
TARGET_NO_BOOTLOADER := true
TARGET_BOARD_PLATFORM := unknown
TARGET_CPU_ABI := armeabi-v7a
TARGET_CPU_ABI2 := armeabi
TARGET_ARCH_VARIANT := armv7-a-neon
ARCH_ARM_HAVE_TLS_REGISTER := true
TARGET_USERIMAGES_USE_EXT4 := true
TARGET_BOOTLOADER_BOARD_NAME := 7D501U
BOARD_KERNEL_CMDLINE := k3v2mem k3v2_ion=1 androidboot.hardware=hw7d501l vmalloc=448M maxcpus=4 initcall_debug=n slub_debug=FZU
BOARD_KERNEL_BASE := 0x08600000
BOARD_KERNEL_PAGESIZE := 2048
# fix this up by examining /proc/mtd on a running device
BOARD_BOOTIMAGE_PARTITION_SIZE := 0x01000000
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 0x01000000
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 0x40000000
BOARD_USERDATAIMAGE_PARTITION_SIZE := 0x031f800000
BOARD_FLASH_BLOCK_SIZE := 65536
TARGET_PREBUILT_KERNEL := device/HUAWEI/7D501U/kernel
BOARD_HAS_NO_SELECT_BUTTON := true
BOARD_HAS_LARGE_FILESYSTEM := true
and unmodified recovery.fstab:
Code:
# mount point fstype device device2
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/system ext4 /dev/block/platform/hi_mci.0/by-name/system
/cache ext4 /dev/block/platform/hi_mci.0/by-name/cache
/tmpdata ext4 /dev/block/platform/hi_mci.0/by-name/userdata
/misc emmc /dev/block/platform/hi_mci.0/by-name/misc
/boot emmc /dev/block/platform/hi_mci.0/by-name/boot
/recovery emmc /dev/block/platform/hi_mci.0/by-name/recovery
/data ext4 /dev/block/platform/hi_mci.0/by-name/data
/cust ext4 /dev/block/platform/hi_mci.0/by-name/cust
/vrcb emmc /dev/block/platform/hi_mci.0/by-name/vrcb
here some reference: http://forum.xda-developers.com/showpost.php?p=51489222&postcount=41
using 10.1 branch of CM and builing on Ubuntu 13.10 on a DigitalOcean pay-per-hour Server
Click to expand...
Click to collapse
I have read that we shouldn't expect custom ROMs on a proprietary Huawei CPU. Therefore I am waiting before buying as I don't want to be locked to Huawei UI and Android version.
Hopefully someone finds a way to get custom ROMs on the mediapad x1.

that would be bad,
but i think with rising popularity, their will be hacks
anyway, cwm would be useful for stock rom too
Gesendet von meinem MediaPad X1 7.0 mit Tapatalk

Tr4sHCr4fT said:
that would be bad,
but i think with rising popularity, their will be hacks
anyway, cwm would be useful for stock rom too
Gesendet von meinem MediaPad X1 7.0 mit Tapatalk
Click to expand...
Click to collapse
From this website, it looks like it's already possible to install custom ROMs on the x1:
http://www.442kitkat.info/mp3-0/huawei-mediapad-x1-6129.html

XabiX666 said:
From this website, it looks like it's already possible to install custom ROMs on the x1:
http://www.442kitkat.info/mp3-0/huawei-mediapad-x1-6129.html
Click to expand...
Click to collapse
it's fake, Download links too small and force you to complete surveys or such first - just scam
Gesendet von meinem MediaPad X1 7.0 mit Tapatalk

yeaaa...cant we have another link....anybody?

there is no newer rom than b009 yet
Gesendet von meinem MediaPad X1 7.0 mit Tapatalk

“manual“ flash GApps 20130812 (not 20130813 !)
by unziping and moving to /system
dont forget permissions

Hello...can anyone send me a cwm for Mediapad X1.. and how to install it? i used to install the recovery with mobileuncle n my other chinese phones..thanks for any help..

there is none. i tried to build one but it won't boot

Tr4sHCr4fT said:
there is none. i tried to build one but it won't boot
Click to expand...
Click to collapse
It's seems that chinese people make it finally !!
But it's in chinses, even if i translate in French (my language), the translation is too messy !
Anyway, i give you the link of the website : http://bbs.gfan.com/android-7369193-1-1.html

gregou said:
It's seems that chinese people make it finally !!
But it's in chinses, even if i translate in French (my language), the translation is too messy !
Anyway, i give you the link of the website : http://bbs.gfan.com/android-7369193-1-1.html
Click to expand...
Click to collapse
hello,
could someone tell me if this device does support the wifi display function? (miracast)
(i.e if it can mirror the display wirelessly to a (miracast) compatible tv, as like it was connected to tv via hdmi cable)
thanks!

Tr4sHCr4fT said:
“manual“ flash GApps 20130812 (not 20130813 !)
by unziping and moving to /system
dont forget permissions
Click to expand...
Click to collapse
hi bro. Can u give some further guide/tutorial how to manual flash gapps please
I've downloaded it but I can't boot into recovery.....
it has a big "fail" at the bottom and there are no other option other than "press power button for 10 seconds to reboot"

Vicolodo said:
hello,
could someone tell me if this device does support the wifi display function? (miracast)
(i.e if it can mirror the display wirelessly to a (miracast) compatible tv, as like it was connected to tv via hdmi cable)
thanks!
Click to expand...
Click to collapse
I looked at it. It's a Chinese language CWM.....
even if u managed to flash it everything is still in Chinese language

CWMA sur mediapad X1
gregou said:
It's seems that chinese people make it finally !!
But it's in chinses, even if i translate in French (my language), the translation is too messy !
Anyway, i give you the link of the website : bbs.gfan.com/android-7369193-1-1.html
Click to expand...
Click to collapse
Nobody managed to do/get a transaltion of this CWMA?
thx

was not even able to boot it

Djiban said:
Nobody managed to do/get a transaltion of this CWMA?
thx
Click to expand...
Click to collapse
Just purchased MediaPad X1. Came across this Russian site, 4pda, (cannot post links as per forum rules until I hit 10 posts), in which they seem to have installed CWM (Chinese CWM!).
It has translation..

Djiban said:
Nobody managed to do/get a transaltion of this CWMA?
thx
Click to expand...
Click to collapse
The post is already out of date. Since Huawei released the EMUI2.3 test ROM(the latest version B010), the bootloader was unlocked automatically. But after that, this CWM recovery doesn't work anymore. I have bricked my X1 (4G version) by flashing this recovery, fortunately, I could recover it by re-flashing the original image file extracted from Huawei upgrade package.

mismatched partition error for (recovery) boot up failed..

Hello Developers,
I am creating cyanogenmod 13 build for Cherry mobile flare s play.. I did half of the process, I created recovery image then I flash it on mobile but it's showing me error "mismatched partition error for (recovery) boot up failed".. How to get partitions size of the device???
This is my Boardconfig.mk file contains following..
USE_CAMERA_STUB := true
# inherit from the proprietary version
-include vendor/Cherry/Flare_S_Play/BoardConfigVendor.mk
TARGET_ARCH := arm
TARGET_NO_BOOTLOADER := true
TARGET_BOARD_PLATFORM := unknown
TARGET_CPU_ABI := armeabi-v7a
TARGET_CPU_ABI2 := armeabi
TARGET_ARCH_VARIANT := armv7-a-neon
TARGET_CPU_VARIANT := cortex-a7
TARGET_CPU_SMP := true
ARCH_ARM_HAVE_TLS_REGISTER := true
TARGET_BOOTLOADER_BOARD_NAME := Flare_S_Play
BOARD_KERNEL_CMDLINE :=
BOARD_KERNEL_BASE := 0x80000000
BOARD_KERNEL_PAGESIZE := 2048
# fix this up by examining /proc/mtd on a running device
BOARD_BOOTIMAGE_PARTITION_SIZE := 0x00A00000
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 0x00A00000
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 0x60000000
BOARD_USERDATAIMAGE_PARTITION_SIZE := 0x323100000
BOARD_FLASH_BLOCK_SIZE := 131072
TARGET_PREBUILT_KERNEL := device/Cherry/Flare_S_Play/kernel
BOARD_HAS_NO_SELECT_BUTTON := true
Now from where i will get the exact partitions size of device..?

boot.img too big error while building TWRP from source

I have a big issue, I'm trying to build TWRP for a non-supported device and I get this error :
Code:
/home/matt/Bureau/TWRP/out/target/product/ac50dis/boot.img maxsize=-28630272 blocksize=18165312 total=7467008 reserve=36330624
error: /home/matt/Bureau/TWRP/out/target/product/ac50dis/boot.img too large (7467008 > [7700352 - 36330624])
build/core/Makefile:570 : la recette pour la cible « /home/matt/Bureau/TWRP/out/target/product/ac50dis/boot.img » a échouée
make: *** [/home/matt/Bureau/TWRP/out/target/product/ac50dis/boot.img] Erreur 1
make: *** Suppression du fichier « /home/matt/Bureau/TWRP/out/target/product/ac50dis/boot.img »
make: *** Attente des tâches non terminées....
#### make failed to build some targets (31 seconds) ####
My BoardConfig.mk :
Code:
USE_CAMERA_STUB := true
# inherit from the proprietary version
-include vendor/archos/ac50dis/BoardConfigVendor.mk
TARGET_ARCH := arm64
TARGET_ARCH_VARIANT := armv8-a
TARGET_CPU_VARIANT := generic
TARGET_CPU_ABI := arm64-v8a
TARGET_2ND_ARCH := arm
TARGET_2ND_ARCH_VARIANT := armv7-a-neon
TARGET_2ND_CPU_VARIANT := cortex-a7
TARGET_2ND_CPU_ABI := armeabi-v7a
TARGET_2ND_CPU_ABI2 := armeabi
TARGET_NO_BOOTLOADER := true
TARGET_BOARD_PLATFORM := mt6753
TARGET_CPU_SMP := true
ARCH_ARM_HAVE_TLS_REGISTER := true
TARGET_BOOTLOADER_BOARD_NAME := ac50dis
BOARD_KERNEL_CMDLINE := bootopt=64S3,32N2,64N2
BOARD_KERNEL_BASE := 0x40078000
BOARD_KERNEL_PAGESIZE := 2048
# fix this up by examining /proc/mtd on a running device
BOARD_BOOTIMAGE_PARTITION_SIZE := 7467008
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 17616077
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 1978662912
BOARD_USERDATAIMAGE_PARTITION_SIZE := 14066017894
BOARD_FLASH_BLOCK_SIZE := 17616077
TARGET_PREBUILT_KERNEL := device/archos/ac50dis/kernel
BOARD_HAS_NO_SELECT_BUTTON := true
TW_THEME := portrait_hdpi
The "BOARD_BOOTIMAGE_PARTITION_SIZE := 7467008" line isn't with the true value of the boot partition size which is usually 17616077 but even if I set this one, it doesn't work at all.
I really neet help so if you have just a clue, tell me .
PS : I'm a 16 years old french guy so if their are some mistakes, don't blame me

TikiMatt said:
I have a big issue, I'm trying to build TWRP for a non-supported device and I get this error:...
Click to expand...
Click to collapse
Your best bet is to post this question within the following thread.
https://forum.xda-developers.com/showthread.php?t=3404024
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

Only vendor modules using LOCAL_USE_VNDK may use LOCAL_COPY_HEADERS

# Treble
BOARD_PROPERTY_OVERRIDES_SPLIT_ENABLED := true
PRODUCT_FULL_TREBLE_OVERRIDE := true
BOARD_VNDK_VERSION := current
BOARD_VNDK_RUNTIME_DISABLE := true

What is the error?