Hello, I'm trying to compile CWM and to build a valid "Recovery.img" for my device with RK2918.
I'm following this guide : Sorry since I've less than 10 post I can't post it here
But when I run command "make -j4 recoveryimage" I get this error:
Code:
bootable/recovery/../../device/rockchip/rk29/recovery_keys.c: In function 'device_handle_key':
bootable/recovery/../../device/rockchip/rk29/recovery_keys.c:25: error: 'ui_menu_level' undeclared (first use in this function)
bootable/recovery/../../device/rockchip/rk29/recovery_keys.c:25: error: (Each undeclared identifier is reported only once
bootable/recovery/../../device/rockchip/rk29/recovery_keys.c:25: error: for each function it appears in.)
make: *** [out/target/product/rk29/obj/EXECUTABLES/recovery_intermediates/../../device/rockchip/rk29/recovery_keys.o]
Please help me
Anyone ?
Luca-91 said:
Anyone ?
Click to expand...
Click to collapse
I'm in the same situation
PANCHOMATASANO said:
I'm in the same situation
Click to expand...
Click to collapse
Well mate , I've SOLVED IT !!
I've just tried the SAME steps on my kubuntu 12.10 and it build a valid and working recovery.img !
Dunno what fixed it , but I suspect a different version of gcc ! just try, good luck !
Luca-91 said:
Well mate , I've SOLVED IT !!
I've just tried the SAME steps on my kubuntu 12.10 and it build a valid and working recovery.img !
Dunno what fixed it , but I suspect a different version of gcc ! just try, good luck !
Click to expand...
Click to collapse
Hi Luca, please help me.
I have a big problem. Mi tablet not have fisic button vol up/down.
Have a button "M";"ESC";"power";"reset".
I think : change a default keys of CWM.
Best regards.
Enviado desde mi 720F usando Tapatalk
Related
Hi,
I'm trying to build a CM11 ROM for Xperia U just for learning. My PC is a SAMSUNG N150 which has Lubuntu 13.10 Saucy Salamander running on it, I have set it up to compile Android ROMs following this guide , next I've followed munjeni's guide to build a CM11 ROM for Xperia Go but using this repo of CM11 for Xperia U instead of munjeni's one for Xperia Go. When I reach the last step (make otapackage, or in other words, build the ROM) it seems everything is going OK during the process, but after 8 hours working it stops and says:
Code:
make: *** [/home/alberto/cm11/out/target/product/kumquat/obj/EXECUTABLES/recovery_intermediates/extendedcommands.o] Error 1
And when I check $OUT directory there's no .zip package.
I think that "Error 1" can be related to these errors:
Code:
bootable/recovery/extendedcommands.c:567:96: error: 'BOARD_VOLD_SDCARD_VOLUME_INT' undeclared (first use in this function)
bootable/recovery/extendedcommands.c:567:96: note: each undeclared identifier is reported only once for each function it appears in
bootable/recovery/extendedcommands.c:567:126: error: 'BOARD_UMS_LUNFILE' undeclared (first use in this function)
bootable/recovery/extendedcommands.c:569:96: error: 'BOARD_VOLD_SDCARD_VOLUME_EXT' undeclared (first use in this function)
But I don't know how to fix the errors and get a complete build, so I need the help of any developer.
Thank You
Garcia98 said:
Hi,
I'm trying to build a CM11 ROM for Xperia U just for learning. My PC is a SAMSUNG N150 which has Lubuntu 13.10 Saucy Salamander running on it, I have set it up to compile Android ROMs following this guide , next I've followed munjeni's guide to build a CM11 ROM for Xperia Go but using this repo of CM11 for Xperia U instead of munjeni's one for Xperia Go. When I reach the last step (make otapackage, or in other words, build the ROM) it seems everything is going OK during the process, but after 8 hours working it stops and says:
Code:
make: *** [/home/alberto/cm11/out/target/product/kumquat/obj/EXECUTABLES/recovery_intermediates/extendedcommands.o] Error 1
And when I check $OUT directory there's no .zip package.
I think that "Error 1" can be related to these errors:
Code:
bootable/recovery/extendedcommands.c:567:96: error: 'BOARD_VOLD_SDCARD_VOLUME_INT' undeclared (first use in this function)
bootable/recovery/extendedcommands.c:567:96: note: each undeclared identifier is reported only once for each function it appears in
bootable/recovery/extendedcommands.c:567:126: error: 'BOARD_UMS_LUNFILE' undeclared (first use in this function)
bootable/recovery/extendedcommands.c:569:96: error: 'BOARD_VOLD_SDCARD_VOLUME_EXT' undeclared (first use in this function)
But I don't know how to fix the errors and get a complete build, so I need the help of any developer.
Thank You
Click to expand...
Click to collapse
Have you apply the patches ?
95A31 said:
Have you apply the patches ?
Click to expand...
Click to collapse
Yes, but I haven't applied the optional step because I'm not going to sync CM11 source code daily
Garcia98 said:
Yes, but I haven't applied the optional step because I'm not going to sync CM11 source code daily
Click to expand...
Click to collapse
It look like bootable_recovery.patch is not applyed properly. Check for errors about that
95A31 said:
It look like bootable_recovery.patch is not applyed properly. Check for errors about that
Click to expand...
Click to collapse
Thank you, I will try it tomorrow
__________________________________________________________
When I apply bootable_recovery.patch I got this:
Code:
patching file bootable/recovery/Android.mk
patching file bootable/recovery/default_recovery_ui.c
patching file bootable/recovery/extendedcommands.c
[B]Hunk #1 FAILED at 32.[/B]
Hunk #2 succeeded at 169 (offset 6 lines).
Hunk #3 succeeded at 559 (offset 13 lines).
Hunk #4 succeeded at 1518 (offset 42 lines).
Hunk #5 succeeded at 1591 (offset 42 lines).
Hunk #6 succeeded at 1694 with fuzz 2 (offset 54 lines).
[B]1 out of 6 hunks FAILED -- saving rejects to file bootable/recovery/extendedcommands.c.rej[/B]
patching file bootable/recovery/recovery.c
patching file bootable/recovery/recovery_ui.h
patching file bootable/recovery/ui.c
patching file bootable/recovery/adefines.h
patching file bootable/recovery/minui/lucidaconsole_10x18.h
It seems there's one error with hunk #1, any idea about how to fix it?
A bump on this. Getting similar errors while building CM 11. Any help would be appreciated
Thanks,
AJ
Nothing...
Nothing, I cannot fix the errors, I've searched everywhere about how to fix patch errors but without success, when I try with git apply hardware/semc/patches/bootable_recovery.patch it says the following:
Code:
error: patch failed: bootable/recovery/extendedcommands.c:32
error: bootable/recovery/extendedcommands.c: patch doesn't apply
If I knew C, I would try to have a look to extendedcommands.c (I think that file cause the error). I attach here the file.
Garcia98 said:
Nothing, I cannot fix the errors, I've searched everywhere about how to fix patch errors but without success, when I try with git apply hardware/semc/patches/bootable_recovery.patch it says the following:
Code:
error: patch failed: bootable/recovery/extendedcommands.c:32
error: bootable/recovery/extendedcommands.c: patch doesn't apply
If I knew C, I would try to have a look to extendedcommands.c (I think that file cause the error). I attach here the file.
Click to expand...
Click to collapse
Guys try to use this patch https://github.com/95A31/android_hardware_semc/blob/cm-11.0/patches/bootable_recovery.patch. It is a refreshed version of @munjeni one.
95A31 said:
Guys try to use this patch https://github.com/95A31/android_hardware_semc/blob/cm-11.0/patches/bootable_recovery.patch. It is a refreshed version of @munjeni one.
Click to expand...
Click to collapse
Thanks a lot. The patch worked with no errors. Now starting the build
Cheers,
AJ
@95A31 Can you please take a look at this error? http://pastebin.com/AGm8QAdR
EDIT: I guess the error might be due to wrong path specified to toolchain. I am trying again with another path. I'll let youknow how that goes
Thanks
AJ
95A31 said:
Guys try to use this patch https://github.com/95A31/android_hardware_semc/blob/cm-11.0/patches/bootable_recovery.patch. It is a refreshed version of @munjeni one.
Click to expand...
Click to collapse
Thank you very much, patch works fine and I've compiled kernel correctly
But now I get another error, it has stopped building and say this:
Code:
make: *** [/home/alberto/cm11/out/target/common/obj/JAVA_LIBRARIES/framework_intermediates/classes-with-local.dex] Ended (killed)
I cannot find any error in terminal
I've checked $OUT directory and there's no zip, kernel is OK, but in system there are a lot of missing files.
Also I've searched for classes-with-local.dex but I don't find it anywhere, in /JAVA_LIBRARIES/framework_intermediates doesn't appear.
I've checked if all patches were applied correctly and I haven't found anything wrong.
Please I need help (other time )
Garcia98 said:
Thank you very much, patch works fine and I've compiled kernel correctly
But now I get another error, it has stopped building and say this:
Code:
make: *** [/home/alberto/cm11/out/target/common/obj/JAVA_LIBRARIES/framework_intermediates/classes-with-local.dex] Ended (killed)
I cannot find any error in terminal
I've checked $OUT directory and there's no zip, kernel is OK, but in system there are a lot of missing files.
Also I've searched for classes-with-local.dex but I don't find it anywhere, in /JAVA_LIBRARIES/framework_intermediates doesn't appear.
I've checked if all patches were applied correctly and I haven't found anything wrong.
Please I need help (other time )
Click to expand...
Click to collapse
Mh... I can not understand this error. I suggest 1) build CM from scratch 2) Check if you are properly include the
proprietary files
Thanks a lot to your patch. I did encountered some small error but I compiled now successfully. Thanks
Cheers,
AJ
95A31 said:
Mh... I can not understand this error. I suggest 1) build CM from scratch 2) Check proprietary files
Click to expand...
Click to collapse
I will try option 1) whenever I can, it's more simple than option 2)
Anyway thanks
Abhinav2 said:
Thanks a lot to your patch. I did encountered some small error but I compiled now successfully. Thanks
Cheers,
AJ
Click to expand...
Click to collapse
You are welcome
Hi, i am compiling the msm kernel, from the cynaogenmod sources (forked from the google sources) for the MSM7627a SoC, and i'm stuck with this error:
CC arch/arm/mach-msm/board-msm7627a-display.o
arch/arm/mach-msm/board-msm7627a-display.c:825: warning: 'msm_fb_get_lane_config' defined but not used
error, forbidden warning: board-msm7627a-display.c:825
make[1]: *** [arch/arm/mach-msm/board-msm7627a-display.o] Error 1
make: *** [arch/arm/mach-msm] Error 2
Click to expand...
Click to collapse
Searching on internet i have no solution, i changed before the kernel source with no results. I think it'ss some "Werror" argument in some makefile, But i'm lost, i hope can help me. Thanks
BTW, sorry for my english, i'm from Venezuela
Please Help!
djra19 said:
Hi, i am compiling the msm kernel, from the cynaogenmod sources (forked from the google sources) for the MSM7627a SoC, and i'm stuck with this error:
Searching on internet i have no solution, i changed before the kernel source with no results. I think it'ss some "Werror" argument in some makefile, But i'm lost, i hope can help me. Thanks
BTW, sorry for my english, i'm from Venezuela
Click to expand...
Click to collapse
C'mon people, i now you are there!. Please help me i'm stuck with this!!!
Sony Mobile is committed to supporting the open developer community, and one way to show this is by publishing parts of our code as well as selected tools developed by our internal developers.
For some of the Xperia™ devices, we provide Android™ Open Source Project (AOSP) device configurations on GitHub. This means that the software will be open for you as a developer to use and contribute to. This is a way for us to support the open Android community, and it is also a tool for us to facilitate and verify contributions to AOSP.
If you want to build AOSP for your unlocked Xperia device, you find all the resources you need in the sections below.
http://developer.sonymobile.com/knowledge-base/open-source/open-devices/
Unified 3.10 kernel sources
https://github.com/sonyxperiadev/kernel
Project git
https://github.com/sonyxperiadev/
Now you have the opportunity to win Sony devices every 2 months
http://developer.sonymobile.com/knowledge-base/open-source/open-devices/hero-open-source-developers/
Happy cooking
SGP712 comilation of 28.0.A.7.251 fails
@jerpelea
Code:
CC drivers/input/touchscreen/maxim_sti.o
drivers/input/touchscreen/maxim_sti.c: In function 'maxim_parse_dt':
drivers/input/touchscreen/maxim_sti.c:1133:7: error: 'struct maxim_sti_pdata' has no member named 'stylus_support'
pdata->stylus_support = (u16)val;
^
drivers/input/touchscreen/maxim_sti.c: In function 'nl_process_driver_msg':
drivers/input/touchscreen/maxim_sti.c:1602:13: error: 'struct maxim_sti_pdata' has no member named 'stylus_support'
if (pdata->stylus_support &&
^
drivers/input/touchscreen/maxim_sti.c:1632:13: error: 'struct maxim_sti_pdata' has no member named 'stylus_support'
if (pdata->stylus_support &&
^
scripts/Makefile.build:308: recipe for target 'drivers/input/touchscreen/maxim_sti.o' failed
make[3]: *** [drivers/input/touchscreen/maxim_sti.o] Error 1
scripts/Makefile.build:455: recipe for target 'drivers/input/touchscreen' failed
make[2]: *** [drivers/input/touchscreen] Error 2
scripts/Makefile.build:455: recipe for target 'drivers/input' failed
make[1]: *** [drivers/input] Error 2
Makefile:815: recipe for target 'drivers' failed
make: *** [drivers] Error 2
I will revert your stylus (really?) patches to version .31
Or please update a declaration struct maxim_sti_pdata at the proper location.
EDIT: I added
Code:
u32 stylus_support;
to 28.0.A.7.251/kernel/include/linux/maxim_sti.h
EDIT2:
I flashed the DE 28.0.A.7.251 - works.
I can not get the kernel compiled here to boot! .27 and .31 are fine with there ROMS and even last a few minutes with the rest of .251
It always (even with default configuration) bootloops.
I tried (via flashtool on linux and Windows 7) to decompress the ORIGINAL kernel.sin from the DE FTF and build a boot image via mkbootimg -> bootloop
EDIT3:
more info, AOSP also a desaster:
http://forum.xda-developers.com/showpost.php?p=62785131&postcount=58
DHGE said:
@jerpelea
Code:
CC drivers/input/touchscreen/maxim_sti.o
drivers/input/touchscreen/maxim_sti.c: In function 'maxim_parse_dt':
drivers/input/touchscreen/maxim_sti.c:1133:7: error: 'struct maxim_sti_pdata' has no member named 'stylus_support'
pdata->stylus_support = (u16)val;
^
drivers/input/touchscreen/maxim_sti.c: In function 'nl_process_driver_msg':
drivers/input/touchscreen/maxim_sti.c:1602:13: error: 'struct maxim_sti_pdata' has no member named 'stylus_support'
if (pdata->stylus_support &&
^
drivers/input/touchscreen/maxim_sti.c:1632:13: error: 'struct maxim_sti_pdata' has no member named 'stylus_support'
if (pdata->stylus_support &&
^
scripts/Makefile.build:308: recipe for target 'drivers/input/touchscreen/maxim_sti.o' failed
make[3]: *** [drivers/input/touchscreen/maxim_sti.o] Error 1
scripts/Makefile.build:455: recipe for target 'drivers/input/touchscreen' failed
make[2]: *** [drivers/input/touchscreen] Error 2
scripts/Makefile.build:455: recipe for target 'drivers/input' failed
make[1]: *** [drivers/input] Error 2
Makefile:815: recipe for target 'drivers' failed
make: *** [drivers] Error 2
I will revert your stylus (really?) patches to version .31
Or please update a declaration struct maxim_sti_pdata at the proper location.
EDIT: I added
Code:
u32 stylus_support;
to 28.0.A.7.251/kernel/include/linux/maxim_sti.h
EDIT2:
I flashed the DE 28.0.A.7.251 - works.
I can not get the kernel compiled here to boot! .27 and .31 are fine with there ROMS and even last a few minutes with the rest of .251
It always (even with default configuration) bootloops.
I tried (via flashtool on linux and Windows 7) to decompress the ORIGINAL kernel.sin from the DE FTF and build a boot image via mkbootimg -> bootloop
EDIT3:
more info, AOSP also a desaster:
http://forum.xda-developers.com/showpost.php?p=62785131&postcount=58
Click to expand...
Click to collapse
28.0.A.8.251 compiles and boots first time for me on Z3+. EDIT: seems to perform better too, with Antutu benchmark score going up from 47,800 to ~53,000
28.0.A.8.251 compiles and boots first time for me on Z3+
Click to expand...
Click to collapse
I hope they tested the source on this device.
Maybe they do not test all kitakami devices e.g. SGP712
DHGE said:
I hope they tested the source on this device.
Maybe they do not test all kitakami devices e.g. SGP712
Click to expand...
Click to collapse
Seems ok for now. I'm running it at the moment on a custom rom that has xposed installed and it's so far stable. This is the kernel in the current firmware, so I'm sure it's been tested.
AOSP uses a different kernel source
https://github.com/sonyxperiadev/kernel
please clarify
@jerpelea
All I write on compiling applies to my SGP712.
AOSP uses a different kernel source
Click to expand...
Click to collapse
Than what?
The latest kernel/include/linux/maxim_sti.h I could find in that repository on GitHub is ancient and without the stylus variable:
@kholkkholk on 29 May input: TS: Add Maxim SmartTouch Imager driver
Click to expand...
Click to collapse
I think that is OK for karin_windy.
I just followed your writeup on SONY Developer!
The last time I complained you added the fastboot flash -S hint for 2015 devices...
I just did a repo sync and added the revised binary drivers which left me first time with a booting device but without touch (today: "hard" bootloop).
Not AOSP:
The kernel for 28.A.0.8.251 you posted on SONY Developer does not compile here without the change in the kernel/include/linux/maxim_sti.h header file.
Flashing the compiled boot.img results in bootloops whatever I tried.
btw: # CONFIG_DM_VERITY is not set
Hi
i have recompiled the kernel
https://github.com/sonyxperiadev/kernel
i have tested karin_windy here with same V11 archive and flashed all 3 partitions
i have touch screen and device working fine
br
J
DHGE said:
@jerpelea
All I write on compiling applies to my SGP712.
Than what?
The latest kernel/include/linux/maxim_sti.h I could find in that repository on GitHub is ancient and without the stylus variable:
I think that is OK for karin_windy.
I just followed your writeup on SONY Developer!
The last time I complained you added the fastboot flash -S hint for 2015 devices...
I just did a repo sync and added the revised binary drivers which left me first time with a booting device but without touch (today: "hard" bootloop).
Not AOSP:
The kernel for 28.A.0.8.251 you posted on SONY Developer does not compile here without the change in the kernel/include/linux/maxim_sti.h header file.
Flashing the compiled boot.img results in bootloops whatever I tried.
btw: # CONFIG_DM_VERITY is not set
Click to expand...
Click to collapse
Thanks @jerpelea for the update!
I am mostly interested in the stagefright patches.
I do not find them in my repo synced AOSP tree.
The (compiled) patches are in ROM 28.0.A.8.251 though and last week I finally managed to get this rooted and running on my karin_windy.
I will try AOSP again if I have more time.
How is the AOSP source for the Z4, does it build yet? Looks like things are building towards a TWRP/AOSP release.
Sent from my SGP712 using Tapatalk
Is there a news on a ASOP build for the Z4?
Sent from my SGP771 using Tapatalk
FreeXperia has AOSP builds for "karin". Will they also work on "karin windy"?
streilu said:
FreeXperia has AOSP builds for "karin". Will they also work on "karin windy"?
Click to expand...
Click to collapse
FreeXperia has "karin windy" builds too.
Look here: http://fxpblog.co/aosp/aosp-5-1/ and choose the first of the 2 possible mirror providers (different sets of files are offered at each), scroll to the buttom and the latest ASOP for the Z4 is there. I have yet to try and install it as the download consistently fails and then forces me to wait for 24 hours.
http://developer.sonymobile.com/201...-camera-available-for-experienced-developers/
enjoy
J
Is anybody able to download any of the ASOP builds from http://fxpblog.co/ ?
Could they be mirrored, at a more "normal" file host?
I can upload it later today to your preferred hoster if you tell me.
streilu said:
I can upload it later today to your preferred hoster if you tell me.
Click to expand...
Click to collapse
How about https://www.androidfilehost.com/ that would seem appropriate. But frankly any host which does not force you to pay for downloads.
Got no dev account on AFH, sorry.
Hope this is ok: https://mega.nz/#!aEZlnZJS
@HotBlack77 please tell me how AOSP feels on the Z4 tab. I'm unsure about the BL unlock thing.
Gesendet von meinem SGP712 mit Tapatalk
Hi all
We have published a new snapshot, zip v14, with camera update (improved quality and stability)
http://developer.sonymobile.com/knowledge-base/open-source/open-devices/
Enjoy
J
error: external/wpa_supplicant_8/wpa_supplicant: MODULE.TARGET.ETC1_WPA.wpa_supplicant.conf already defined by external/wpa_supplicant_8/wpa_supplicant.
please help me
Do you solve it now?
ak18shay said:
error: external/wpa_supplicant_8/wpa_supplicant: MODULE.TARGET.ETC1_WPA.wpa_supplicant.conf already defined by external/wpa_supplicant_8/wpa_supplicant.
please help me
Click to expand...
Click to collapse
I have this problem too.
Code:
Assembler messages:
arch/arm64/kernel/entry-fpsimd.S:53: Error: unexpected end of file in irp or irpc
/tmp/cczAQDmw.s: Error: local label `"0" (instance number 1 of a fb label)' is not defined
make[1]: *** [scripts/Makefile.build:344: arch/arm64/kernel/entry-fpsimd.o] Error 1
I got this error, I searched on Google but found nothing about it. I use Google's gcc-4.9 toolchain.
May anyone help me please?
Hi!
This is a preliminary suggestion, the ROM is not made for your phone.
CFCbazar said:
Hi!
This is a preliminary suggestion, the ROM is not made for your phone.
Click to expand...
Click to collapse
But I got this from Samsung OSS, just want to compile my device's kernel :/
Are you sure that you have the floating point configuration correct?
Code:
CONFIG_KERNEL_MODE_NEON
CONFIG_ENABLE_FP_SIMD_SETTINGS
Renate said:
Are you sure that you have the floating point configuration correct?
Code:
CONFIG_KERNEL_MODE_NEON
CONFIG_ENABLE_FP_SIMD_SETTINGS
Click to expand...
Click to collapse
I have CONFIG_KERNEL_MODE_ON as y on my defconfig but I don't have CONFIG_ENABLE_FP_SIMD_SETTINGS on my defconfig.
gorkemoji said:
But I got this from Samsung OSS, just want to compile my device's kernel :/
Click to expand...
Click to collapse
That's not a guarantee. It has happened before. Or you could try the steps from their site. Maybe you missed something.
Maybe the assembler and your FPU type don't agree.