MIUI Porting error Huawei P9 Anyone help me please! - Huawei P9 Questions & Answers

Hello all! Last day i tried to port MIUI for our P9. But i faced an error,and i don't know how to solve it... Please help me! I want to make MIUI... I used stock 6.0 base.
Here is the error log:
/home/nexti/MIUI/tools/apktool --quiet if -p out/apktool out/framework-ext-res.apk
<<< build out/framework-ext-res.apk completed!
Copy: out/framework-ext-res.apk to out/ZIP/system/framework/framework-ext-res/framework-ext-res.apk
/home/nexti/MIUI/tools/apktool --quiet d -f /home/nexti/MIUI/miui/system/framework/framework.jar -o out/framework_miui
>>> build out/framework.jar...
cp: stat 'framework.jar.out/' sikertelen: Nincs ilyen fájl vagy könyvtár (Error: No Such File or Directory)
/home/nexti/MIUI/build/porting.mk:179: recipe for target 'out/framework.jar' failed
make[1]: *** [out/framework.jar] Error 1
make[1]: Leaving directory '/home/nexti/MIUI/eva'
Makefile:8: recipe for target 'otapackage' failed
make: *** [otapackage] Error 2

I am not a developer but it would be nice to have Miui 8 on P9! Bon courage...

forget about it until stable lineage is out, emui is integrated to deep

bro i´m not a developer but maybe this will help a little bit: http://www.miui.website/threads/miui-patchrom-tutorijal-za-portovanje.40/ keep working hard

cesarguaro said:
bro i´m not a developer but maybe this will help a little bit: http://www.miui.website/threads/miui-patchrom-tutorijal-za-portovanje.40/ keep working hard
Click to expand...
Click to collapse
Thank you very much! I will try this tomorrow. I hope it works well?

how it´s the developmen of the muiu rom going bro?

man ...i would love this
stock camera app included right?

Impossible EMUI is hard but MIUI is even harder todo

how it is going bro? any news on this rom?

Related

[Q] Building 2.6.35 kernel

Has anyone on here had any luck getting this kernel to build and boot. I've tried a couple cross-compilers and always end up with this error.
Code:
make[1]: *** No rule to make target `arch/arm/mach-msm/smd_rpcrouter.o', needed by `arch/arm/mach-msm/built-in.o'. Stop.
make[1]: *** Waiting for unfinished jobs....
CC arch/arm/mach-msm/smd_rpcrouter_device.o
CC kernel/panic.o
make: *** [arch/arm/mach-msm] Error 2
make: *** Waiting for unfinished jobs....
It builds a little bit more and then stops after this..
Code:
LD kernel/built-in.o
Anyone have any suggestions?
tcberg2010 said:
Has anyone on here had any luck getting this kernel to build and boot. I've tried a couple cross-compilers and always end up with this error.
Code:
make[1]: *** No rule to make target `arch/arm/mach-msm/smd_rpcrouter.o', needed by `arch/arm/mach-msm/built-in.o'. Stop.
make[1]: *** Waiting for unfinished jobs....
CC arch/arm/mach-msm/smd_rpcrouter_device.o
CC kernel/panic.o
make: *** [arch/arm/mach-msm] Error 2
make: *** Waiting for unfinished jobs....
It builds a little bit more and then stops after this..
Code:
LD kernel/built-in.o
Anyone have any suggestions?
Click to expand...
Click to collapse
What source did you use? I'm about to push mine up to github after I verify it's ok but this error happened to me when I tried to port the evo kernel to the inc.
If you want to set up the kernel as HTC has it do this:
Code:
cp arch/arm/configs/incrediblec_defconfig .config
from the main kernel directory
That will setup your environment for the Inc.
Are you running the build with multiple threads? Get rid of -j and let it build in a single thread so you can see all the errors
Sent from my ADR6300 using xda premium
swm5126 said:
Are you running the build with multiple threads? Get rid of -j and let it build in a single thread so you can see all the errors
Sent from my ADR6300 using xda premium
Click to expand...
Click to collapse
Ill try both suggestions after I update my laptop to 3.1-rc4. Thanks
Sent from my Incredible using XDA App

error building kernel

Hi guys first of all HI TO EVERYBODY!!!!
I'm new to this forum and hope you will help me....
I recently bought a brand new phone, an LG-P990.
I would like to build my personal rom and kernel so I followed this guide
http://forum.xda-dev...d.php?t=1104523
and all went ok but when I saw that there were not any kernel source code in it I decided also to follow the following
http://wiki.cyanogen...nel_from_source
but when I finally launch the compilation with:
make ARCH=arm CROSS_COMPILE=$CCOMPILER -j`grep 'processor' /proc/cpuinfo | wc -l`
after few minutes I have the following error message:
http://pastebin.com/z5udP72j
how to fix it???
thank you in advance,
Matteo
84matte84 said:
Hi guys first of all HI TO EVERYBODY!!!!
I'm new to this forum and hope you will help me....
I recently bought a brand new phone, an LG-P990.
I would like to build my personal rom and kernel so I followed this guide
http://forum.xda-dev...d.php?t=1104523
and all went ok but when I saw that there were not any kernel source code in it I decided also to follow the following
http://wiki.cyanogen...nel_from_source
but when I finally launch the compilation with:
make ARCH=arm CROSS_COMPILE=$CCOMPILER -j`grep 'processor' /proc/cpuinfo | wc -l`
after few minutes I have the following error message:
http://pastebin.com/z5udP72j
how to fix it???
thank you in advance,
Matteo
Click to expand...
Click to collapse
what is the definition of the $CCOMPILER ?
vadonka said:
what is the definition of the $CCOMPILER ?
Click to expand...
Click to collapse
as stated in the guide...the CCOMPILER is
CCOMPILER=${HOME}/android/system/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi-
Try compile with another toolchain? Linaro?
Sent from my LG-P990 using XDA App
fajarep said:
Try compile with another toolchain? Linaro?
Click to expand...
Click to collapse
why not....but how to do that????
if you have a recent version of ubunut/debian try this:
apt-get update
apt-get install gcc-arm-linux-gnueabi
then define the CCOMPILER like this:
CCOMPILER=arm-linux-gnueabi-
fajarep said:
Try compile with another toolchain? Linaro?
Click to expand...
Click to collapse
I tried with
CCOMPILER="/home/matteo/android/system/prebuilt/linux-x86/toolchain/arm-linux-androideabi-4.4.x/bin/arm-linux-androideabi-
but I have another error now
drivers/mmc/host/sdhci.c: In function 'sdhci_suspend_host':
drivers/mmc/host/sdhci.c:1652: error: too few arguments to function 'mmc_suspend_host'
make[3]: *** [drivers/mmc/host/sdhci.o] Error 1
make[2]: *** [drivers/mmc/host] Error 2
make[1]: *** [drivers/mmc] Error 2
make: *** [drivers] Error 2
make: *** Waiting for unfinished jobs....
what to do now??? changing toolchain until find a working one?
vadonka said:
if you have a recent version of ubunut/debian try this:
apt-get update
apt-get install gcc-arm-linux-gnueabi
then define the CCOMPILER like this:
CCOMPILER=arm-linux-gnueabi-
Click to expand...
Click to collapse
same error with gnueabi
drivers/mmc/host/sdhci.c: In function ‘sdhci_suspend_host’:
drivers/mmc/host/sdhci.c:1652:2: error: too few arguments to function ‘mmc_suspend_host’
include/linux/mmc/host.h:285:12: note: declared here
make[3]: *** [drivers/mmc/host/sdhci.o] Error 1
make[2]: *** [drivers/mmc/host] Error 2
make[1]: *** [drivers/mmc] Error 2
make: *** [drivers] Error 2
84matte84 said:
same error with gnueabi
drivers/mmc/host/sdhci.c: In function ‘sdhci_suspend_host’:
drivers/mmc/host/sdhci.c:1652:2: error: too few arguments to function ‘mmc_suspend_host’
include/linux/mmc/host.h:285:12: note: declared here
make[3]: *** [drivers/mmc/host/sdhci.o] Error 1
make[2]: *** [drivers/mmc/host] Error 2
make[1]: *** [drivers/mmc] Error 2
make: *** [drivers] Error 2
Click to expand...
Click to collapse
what kernel source you have?
vadonka said:
what kernel source you have?
Click to expand...
Click to collapse
following the guide I pulled the kernel from the device...
however in the .config I have the following
"Linux/arm 2.6.37.6 Kernel Configuration"
So i think 2.6.37.6
84matte84 said:
following the guide I pulled the kernel from the device...
however in the .config I have the following
"Linux/arm 2.6.37.6 Kernel Configuration"
So i think 2.6.37.6
Click to expand...
Click to collapse
Is note the same as the device because my device has a
2.6.32.49-cyanogenmode kernel...
84matte84 said:
following the guide I pulled the kernel from the device...
however in the .config I have the following
"Linux/arm 2.6.37.6 Kernel Configuration"
So i think 2.6.37.6
Click to expand...
Click to collapse
how can you pulled the kernel source from the device?
Are you have the cyanogenmod source? or miui or else?
i suggest that pull the latest cm kernel from the cyanogenmod github.
vadonka said:
how can you pulled the kernel source from the device?
Are you have the cyanogenmod source? or miui or else?
i suggest that pull the latest cm kernel from the cyanogenmod github.
Click to expand...
Click to collapse
Sorry I did not pulled the kernel source but the kernel config as suggested in the tutorial...
I'm working with cyanogenmod source following the cyanogenmod wiki tutorial here
http://wiki.cyanogenmod.com/wiki/Building_Kernel_from_source
84matte84 said:
Sorry I did not pulled the kernel source but the kernel config as suggested in the tutorial...
I'm working with cyanogenmod source following the cyanogenmod wiki tutorial here
http://wiki.cyanogenmod.com/wiki/Building_Kernel_from_source
Click to expand...
Click to collapse
apt-get update
apt-get install git
git clone git://github.com/CyanogenMod/lge-kernel-star.git
then try with this source
vadonka said:
apt-get update
apt-get install git
git clone git://github.com/CyanogenMod/lge-kernel-star.git
then try with this source
Click to expand...
Click to collapse
this time the kernel compile without problems...now how to load it in the phone? Can I continue following the cyanogenmod wiki???
thank you for your help...
84matte84 said:
this time the kernel compile without problems...now how to load it in the phone? Can I continue following the cyanogenmod wiki???
thank you for your help...
Click to expand...
Click to collapse
I'm sorry if im raw, but why you deal with this? if you dont make any change in the kernel source just use the precompiled cm7 kernel.
im not exactly understand your motive.
vadonka said:
I'm sorry if im raw, but why you deal with this? if you dont make any change in the kernel source just use the precompiled cm7 kernel.
im not exactly understand your motive.
Click to expand...
Click to collapse
This is my first step...for now I need to build an unchanged source and load it on my phone....after when I will able to load a compiled kernel in the phone correctly I will need to modify it...for my university studies...
but because of is the first time I'm asking you the correct steps because I don't want to brik the phone
84matte84 said:
but because of is the first time I'm asking you the correct steps because I don't want to brik the phone
Click to expand...
Click to collapse
i understand.
in that case the kernel zimage in the "/arch/arm/boot" directory.
you also need to copy all file what have the ".ko" extension (modules)
you need to write a kernel installer cwm script, or use someone else script.
you can use my script: https://github.com/vadonka/kernel-installer
if you have some linux shell scripting knowledge you will understand this

AOSP Marshmallow issues

Hi all, can anyone say they've built a AOSP Marshmallow ROM (m-preview-2) ?
I can build Lollipop just fine but even doing a clean install of Linux and downloading 20+ gigs of AOSP repo stuff of m-preview-2, I get the following error...
make: *** No rule to make target `out/target/product/hammerhead/obj/STATIC_LIBRARIES/libunwind_llvm_intermediates/export_includes', needed by `out/target/product/hammerhead/obj/EXECUTABLES/init_intermediates/import_includes'. Stop.
Click to expand...
Click to collapse
If I download the 'master' repo, it compiles fine but I get a boot lock installing it on my Nexus5.
As I say, I can download and compile/install the AOSP Lollipop fine but Marshmallow just seems to not be all there. I understand it's a preview but it's now on it's (probable) last release before going live so I would have hoped it should be at least compilable.
Any help?
Many thanks
Adrian
Repo sync'ed it again and now get these errors....
external/selinux/checkpolicy/policy_define.c:1572:2: warning: comparison of integers of different signs: 'int' and 'uint32_t' (aka 'unsigned int') [-Wsign-compare]
ebitmap_for_each_bit(&tclasses, node, i) {
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
external/selinux/checkpolicy/../libsepol/include/sepol/policydb/ebitmap.h:76:39: note: expanded from macro 'ebitmap_for_each_bit'
for (bit = ebitmap_start(e, &n); bit < ebitmap_length(e); bit = ebitmap_next(&n, bit)) \
^ ~~~~~~~~~~~~~~~~~
external/selinux/checkpolicy/policy_define.c:2763:3: warning: comparison of integers of different signs: 'int' and 'uint32_t' (aka 'unsigned int') [-Wsign-compare]
ebitmap_for_each_bit(&rdp->dominates, node, i) {
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
external/selinux/checkpolicy/../libsepol/include/sepol/policydb/ebitmap.h:76:39: note: expanded from macro 'ebitmap_for_each_bit'
for (bit = ebitmap_start(e, &n); bit < ebitmap_length(e); bit = ebitmap_next(&n, bit)) \
^ ~~~~~~~~~~~~~~~~~
external/selinux/checkpolicy/policy_define.c:2769:3: warning: comparison of integers of different signs: 'int' and 'uint32_t' (aka 'unsigned int') [-Wsign-compare]
ebitmap_for_each_bit(&types, node, i) {
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
external/selinux/checkpolicy/../libsepol/include/sepol/policydb/ebitmap.h:76:39: note: expanded from macro 'ebitmap_for_each_bit'
for (bit = ebitmap_start(e, &n); bit < ebitmap_length(e); bit = ebitmap_next(&n, bit)) \
^ ~~~~~~~~~~~~~~~~~
3 warnings generated.
host C: checkpolicy <= external/selinux/checkpolicy/checkpolicy.c
host C++: checkpolicy <= out/host/linux-x86/obj/EXECUTABLES/checkpolicy_intermediates/policy_parse.cpp
error: invalid argument '-std=gnu++14' not allowed with 'C/ObjC'
make: *** [out/host/linux-x86/obj/EXECUTABLES/checkpolicy_intermediates/policy_parse.o] Error 1
#### make failed to build some targets (01:33 (mm:ss)) ####
Click to expand...
Click to collapse
These seem to me to be pretty fundamental errors if I understand them correctly.
Many thanks
Adrian
same error
adrian.aitken said:
Hi all, can anyone say they've built a AOSP Marshmallow ROM (m-preview-2) ?
I can build Lollipop just fine but even doing a clean install of Linux and downloading 20+ gigs of AOSP repo stuff of m-preview-2, I get the following error...
If I download the 'master' repo, it compiles fine but I get a boot lock installing it on my Nexus5.
As I say, I can download and compile/install the AOSP Lollipop fine but Marshmallow just seems to not be all there. I understand it's a preview but it's now on it's (probable) last release before going live so I would have hoped it should be at least compilable.
Any help?
Many thanks
Adrian
Click to expand...
Click to collapse
i am getting the same error, how did you fix it? thanks
PiSpecialist said:
i am getting the same error, how did you fix it? thanks
Click to expand...
Click to collapse
I haven't - I went back to Lollipop. When Marshmallow comes out officially I'll look again.
Many thanks
Adrian
The marshmallow source code hasn't all been published yet
faZevoLv said:
The marshmallow source code hasn't all been published yet
Click to expand...
Click to collapse
preview-m-2 has and that's what I was talking about.
Many thanks
Adrian
Its bcuz the source isn't complete yet, they didn't release all the code needed to build it yet, which is why no ROMs are out, the only one that comes to mind is XtraSmooth, and I know he just uses the system image and odex's it, the actual AOSP source code isn't complete for marshmallow yet, it will be released on Oct 5th tho so be ready
Sent from my Nexus 6 using Tapatalk

CM11 Kenel compiling trouble !!

Hi. i have tried to compile cm11 kernel by using kernel source from http://github.com/cm-nokia-x2 and gcc toolchain 4.8 from here http://github.com/huyparody/gcc_linaro
i get config.gz from /proc/
and renamed it to ara_defconfig
and when i:
make ara_defconfig
make
after a few minute, it show me a error:
CC drivers/input/touchscreen/cyttsp4_device_access.o
drivers/input/touchscreen/cyttsp4_device_access.c: In function 'cyttsp4_grpdata_store_touch_params':
drivers/input/touchscreen/cyttsp4_device_access.c:1447:19: warning: 'rc3' may be used uninitialized in this function [-Wuninitialized]
error, forbidden warning: cyttsp4_device_access.c:1447
make[3]: *** [drivers/input/touchscreen/cyttsp4_device_access.o] Error 1
make[2]: *** [drivers/input/touchscreen] Error 2
make[1]: *** [drivers/input] Error 2
make: *** [drivers] Error 2
[email protected]:~/android/kernel/nokia/msm8610$
Click to expand...
Click to collapse
how to solve it!! thanks much
kaotd99 said:
how to solve it!! thanks much
Click to expand...
Click to collapse
Hello,
Use toolchain from CyanogenMod prebuilt repo, here is link: github.com/CyanogenMod/android_prebuilt/tree/cm-11.0/linux-x86/toolchain/arm-eabi-4.4.3
You also don't need to copy config from /proc, it is included in source at arch/arm/configs/msm8610-nokia-defconfig.
zombah said:
Hello,
Use toolchain from CyanogenMod prebuilt repo, here is link: github.com/CyanogenMod/android_prebuilt/tree/cm-11.0/linux-x86/toolchain/arm-eabi-4.4.3
You also don't need to copy config from /proc, it is included in source at arch/arm/configs/msm8610-nokia-defconfig.
Click to expand...
Click to collapse
thanks dev
oh god... i got new error:
i type:
export PATH=/home/kaotd/android/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin:$PATH
export ARCH=arm
export CROSS_COMPILE=arm-eabi-
and:
[email protected]:/home/kaotd/android/kernel/nokia/msm8610# make msm8610-nokia_defconfig
#
# configuration written to .config
#
[email protected]:/home/kaotd/android/kernel/nokia/msm8610# make
scripts/kconfig/conf --silentoldconfig Kconfig
CHK include/linux/version.h
CHK include/generated/utsrelease.h
make[1]: `include/generated/mach-types.h' is up to date.
CC kernel/bounds.s
kernel/bounds.c:1: error: bad value (cortex-a7) for -mtune= switch
make[1]: *** [kernel/bounds.s] Error 1
make: *** [prepare0] Error 2
[email protected]:/home/kaotd/android/kernel/nokia/msm8610#
Click to expand...
Click to collapse
can you help me ? thanks.... because im a newbie and sorry about that
kaotd99 said:
can you help me ? thanks.... because im a newbie and sorry about that
Click to expand...
Click to collapse
Hello,
Ahh yep, i forgot switch to memcpy optimizations, here is correct link to newer toolchain android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.7
zombah said:
Hello,
Ahh yep, i forgot switch to memcpy optimizations, here is correct link to newer toolchain android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.7
Click to expand...
Click to collapse
thanks.. i will try and report to you later!! thanks again
@zombah hi again. i was compiled a kernel( zImage )
now i have "Kernel: arch/arm/boot/zImage is ready"
so how can i compare it with boot.img ?
Hello,
If you wont use inline kernel building inside CyanogenMod, you probably need to unpack boot.img content replace kernel and then pack boot.img again with replaced kernel. Remember that it is dangerous if your kernel is not bootable, you'll stuck to recovery only boot and if your recovery also lost only unbricking will help.
Use CyanogenMod mkbootimg.c/unpackbootimg.c for that, here is repo github.com/CyanogenMod/android_system_core/tree/cm-11.0/mkbootimg
Here is how to compile them separatly of whole system:
Code:
gcc -o mkbootimg mkbootimg.c ../libmincrypt/sha.c -I../include
gcc -o unpackbootimg unpackbootimg.c ../libmincrypt/sha.c -I../include
you'll need to download dependencies also.
zombah said:
Hello,
If you wont use inline kernel building inside CyanogenMod, you probably need to unpack boot.img content replace kernel and then pack boot.img again with replaced kernel. Remember that it is dangerous if your kernel is not bootable, you'll stuck to recovery only boot and if your recovery also lost only unbricking will help.
Use CyanogenMod mkbootimg.c/unpackbootimg.c for that, here is repo github.com/CyanogenMod/android_system_core/tree/cm-11.0/mkbootimg
Here is how to compile them separatly of whole system:
Code:
gcc -o mkbootimg mkbootimg.c ../libmincrypt/sha.c -I../include
gcc -o unpackbootimg unpackbootimg.c ../libmincrypt/sha.c -I../include
you'll need to download dependencies also.
Click to expand...
Click to collapse
thanks much
can you tell me which file contain OverClock number of nokia x2 ? and which kernelPatch i can apply with this kernel ?
Hello,
I don't know, i'm not interested in overclocking and never investigated this question.
And i don't recommend you to play with overclocking without deep embedded development skills, it is very easy to kill your device with wrong power modifiers.
i'm understand, thanks for your suggestion.
not about nokia x2ds but can i ask you a question?
-can i make a kernel source for a mtk device ? because i have a mtk china phone which not have kernel source from manufacturer !
kaotd99 said:
i'm understand, thanks for your suggestion.
not about nokia x2ds but can i ask you a question?
-can i make a kernel source for a mtk device ? because i have a mtk china phone which not have kernel source from manufacturer !
Click to expand...
Click to collapse
Hello,
Sure it is possible, why not. But you need at least serial/uart console on device, otherwise how you will debug kernel boot problems?
zombah said:
Hello,
Sure it is possible, why not. But you need at least serial/uart console on device, otherwise how you will debug kernel boot problems?
Click to expand...
Click to collapse
thanks... now i'm trying to port double-tap to wake feature from Nokia Stock Kernel. There is any suggestion ?? Thanks
i'm trying to add this: https://github.com/ryanaepple/android_kernel_motoe/commit/080003bc8e61349bf7c8da00fa6923f3c84d1927
and being stuck at editing synaptics_dsx_i2c.c and synaptics_dsx_i2c.h
can you tell me which files is Touchscreen driver of nokia x2 ?? i think it is synaptics_i2c_rmi4.c/.h
kaotd99 said:
can you tell me which files is Touchscreen driver of nokia x2 ?? i think it is synaptics_i2c_rmi4.c/.h
Click to expand...
Click to collapse
Hello,
Nokia X2 have Cypress TMA4XX touchscreen, driver location is drivers/input/touchscreen/cyttsp4*

Nexus 5 compiling error

Hi men, please, I need a help
This is my Rom: https://github.com/eM4Mark
It worked perfectly before the last update ( r24 , first it was r22 ), but now I have this error.
make: *** No rule to make target `vendor/mark/system/vendor/media/LMspeed_508.emd', needed by `out/target/product/hammerhead/system/vendor/media/LMspeed_508.emd'. Stop.
make: *** Waiting for unfinished jobs....
Is very nice, because If I compile for Nexus 5X I don't have that error... PLEASE, help, I'm going crazy:silly:
try with another vendor
Sent from my Nexus 5 using XDA-Developers mobile app
Try another vendor, maybe u have any 5x fork on ur compiling bench
Sent from my fx-82MS with CM-CAF

Categories

Resources