Download Sources Huawei Sonic U8650
Download the Kernel Sources of Huawei Sonic from this link ---> Here
Direct Link ---> Here
There are about 430 mb as the source contains more Huawei terminal.
Configuration file (. Config)
This file is not present inside the Huawei's rom and not present into boot.img.
But we can find this file into the kernel that we have previously downloaded.
We can find this file in this directory ---> kernel/arch/arm/configs/hw_msm7227_defconfig of 70,4 kb
Take this file ---> hw_msm7227_deconfig copy it into the kernel directory and now change in .config.
hw_msm7227_deconfig ---> .config
Done.
Now we are ready to compile our kernel.
Good Work.
Bye
where can i download the kernel sources for sonic?
carlonchete said:
where can i download the kernel sources for sonic?
Click to expand...
Click to collapse
Try Direct link.....
Hello.
I have downloaded these sources. Setting the crossdev environment in Gentoo was a breezed, and I had no problem compiling the kernel. Well, to tell the truth, I got an error, but was able to pass through by setting CONFIG_NO_ERROR_ON_MISMATCH=y'
Code:
LD vmlinux.o
MODPOST vmlinux.o
WARNING: vmlinux.o(.text+0xe474): Section mismatch in reference from the function msm_map_io.clone.0() to the (unknown reference) .init.data:(unknown)
The function msm_map_io.clone.0() references
the (unknown reference) __initdata (unknown).
This is often because msm_map_io.clone.0 lacks a __initdata
annotation or the annotation of (unknown) is wrong.
To build the kernel despite the mismatches, build with:
'make CONFIG_NO_ERROR_ON_MISMATCH=y'
(NOTE: This is not recommended)
make[1]: *** [vmlinux.o] Error 1
make: *** [vmlinux.o] Error 2
I have no idea if that can have further implications, but that's not what I wanted to ask you anyway.
My question is, what do I do with this thing now?
I've managed to cat /dev/mtd/mtd0 to /sdcard/mtd0, but that gives me a file that is not recognized by Gentoo as an fs of any kind. It could be some kind of custom file with a kernel plus an initrd inside of it, because that's what I read some mobiles do on their boot partition, but there's really no info about this, that I can find.
I guess that if you posted to compile the kernel you also know how to disassemble this boot image. So, can you, please, give me any pointers?
PS. I also tried to mount this as yaffs2, as that seems to be the format for the other fs's inside the phone, as per the output for "mount | grep mtd". Unfortunately, in linux, it doesn't work (yes, I compile yaffs2 myself as a kernel module). I also tried mounting it in my phone, two times, the result was that the boot was corrupted and the next time I booted my phone I had to reflash it with the stock rom to get it booting again with factory settings
Any help with this? Phone is not currently rooted.
http://forum.xda-developers.com/showthread.php?t=1866545 might help
I have no samsung galaxy express 2
I downloaded G3815XXUAMJ1_G3815VFGAMJ1_PRO.zip
from SamMobile
Model: SM-G3815
Country: Belgium / Luxemburg
Version: Android 4.2.2
Changelist: 1756122
Build date: Tue, 01 Oct 2013 05:09:23 +0000
Product Code: PRO
PDA: G3815XXUAMJ1
CSC: G3815VFGAMJ1
MODEM: G3815XXUAMJ1
If I feed recovery.img to
http://builder.clockworkmod.com/
it recognises: samsung wilcoxlte
(but build fails see f9ee506dc02a4f6dddd1dc6ed315ce80)
Then I thought: build one myself
-- recipe
mkdir g3815
cd g3815
repo init -u git://github.com/CyanogenMod/android.git -b jellybean
repo sync
. build/envsetup.sh
make -j8 otatools
export PATH=$PATH:$PWD/out/host/linux-x86/bin
build/tools/device/mkvendor.sh samsung wilcoxlte /tmp/recovery.img
lunch full_wilcoxlte-eng
. build/tools/device/makerecoveries.sh full_wilcoxlte-eng
--
I now have an recovery.img and update.zip in out/target/product/wilcoxlte
-- env
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.1.2
TARGET_PRODUCT=full_wilcoxlte
TARGET_BUILD_VARIANT=eng
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a-neon
HOST_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-3.12.4-gentoo-x86_64-with-Ubuntu-13.10-saucy
HOST_BUILD_TYPE=release
BUILD_ID=JZO54K
OUT_DIR=/root/g3815/out
question: does following fstab look correct?
/boot emmc /dev/block/platform/msm_sdcc.1/by-name/boot
/system ext4 /dev/block/platform/msm_sdcc.1/by-name/system
/data ext4 /dev/block/platform/msm_sdcc.1/by-name/userdata length=-16384
/cache ext4 /dev/block/platform/msm_sdcc.1/by-name/cache
/recovery emmc /dev/block/platform/msm_sdcc.1/by-name/recovery
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/efs ext4 /dev/block/platform/msm_sdcc.1/by-name/efs
/modem emmc /dev/block/platform/msm_sdcc.1/by-name/modem
/preload ext4 /dev/block/platform/msm_sdcc.1/by-name/hidden
thanks
I leave my mark here! I hope soon we'll find an good recovery & root for our Galaxy Express 2.
my sm-3815 arrived
OK so my express 2 sm-g3815 arrived.
One thing I wonder: is it possible (say with fastboot or heimdall, note, I have no windows computers, only linux) to make image backup of recovery partition (/dev/block/mmcblk0p14)?
Agreed, one can have the recovery.img inside SamMobile's G3815XXUAMJ1_G3815VFGAMJ1_PRO.zip, but this ZIP must also somehow have been made ...
update: actually, perhaps the ZIP comes from Samsung and is not 'made'...
Thanks
kieronspitter said:
Any help with this? Phone is not currently rooted.
Click to expand...
Click to collapse
I currently have a US express 2. I believe the hardware is identical to the vodafone version. I used Motochopper to root mine and it worked with no issues. You can find the link to download motochopper here http://forum.xda-developers.com/showthread.php?t=2252248.
i would recommend backing up your phone before you try this exploit.
If someone would be willing to test this on a European version to verify it works, that would be awesome, since i am limited to the US version and cannot confirm the complete compatibility of this exploit.
Does anyone have a link to the stock firmware for the vodaphone version?
Ririken203 said:
I currently have a US express 2. I believe the hardware is identical to the vodafone version. I used Motochopper to root mine and it worked with no issues. You can find the link to download motochopper here http://forum.xda-developers.com/showthread.php?t=2252248.
i would recommend backing up your phone before you try this exploit.
If someone would be willing to test this on a European version to verify it works, that would be awesome, since i am limited to the US version and cannot confirm the complete compatibility of this exploit.
Does anyone have a link to the stock firmware for the vodaphone version?
Click to expand...
Click to collapse
not working on european devices G3815XXUAMJ1 firmware:crying:
---------- Post added at 12:58 PM ---------- Previous post was at 12:50 PM ----------
[*] Motochopper: Android root exploit (Windows version)
[*] v1.1
[*] by Dan Rosenberg (@djrbliss)
[*]
[*] Tested on the Motorola Razr HD, Razr M, Razr Maxx HD, and Atrix HD.
[*] Supports lots of other devices as well.
[*]
[*] Before continuing, ensure that USB debugging is enabled, that you
[*] have the latest USB drivers installed, and that your phone
[*] is connected via USB.
[*]
[*] WARNING: This will likely void the warranty on your device. I am
[*] not responsible for any damage to your phone as a result using this
[*] tool.
[*]
[*] Press enter to root your phone...
Press any key to continue . . .
[*]
[*] Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[*] Device found.
[*] Pushing exploit...
2557 KB/s (1283460 bytes in 0.490s)
[*] Pushing root tools...
2559 KB/s (366952 bytes in 0.140s)
2399 KB/s (1867568 bytes in 0.760s)
2802 KB/s (1578585 bytes in 0.550s)
pkg: /data/local/tmp/Superuser.apk
Success
[*] Rooting phone...
[+] This may take a few minutes.
[-] Failure.
[*] Cleaning up...
[*] Exploit complete. Press enter to reboot and exit
terminal23 said:
not working on european devices G3815XXUAMJ1 firmware:crying:
Click to expand...
Click to collapse
---------- Post added at 01:07 PM ---------- Previous post was at 12:58 PM ----------
Ririken203 said:
I currently have a US express 2. I believe the hardware is identical to the vodafone version. I used Motochopper to root mine and it worked with no issues. You can find the link to download motochopper here http://forum.xda-developers.com/showthread.php?t=2252248.
i would recommend backing up your phone before you try this exploit.
If someone would be willing to test this on a European version to verify it works, that would be awesome, since i am limited to the US version and cannot confirm the complete compatibility of this exploit.
Does anyone have a link to the stock firmware for the vodaphone version?
Click to expand...
Click to collapse
Link for Vodafone firmware http://terafile.co/4616e5212201/G3815XXUAMJ1_G3815VFGAMJ1_ATL.zip
fb_mmap in drivers/video/fbmem.c for the e2 sm-g3815 does no longer have the flaw required for motochopper.
see http://forum.xda-developers.com/showthread.php?p=40825380#poststop
one could try kernelchopper from same thread but then one needs to find the address to overwrite the conditional instruction to become unconditional.
Link for Vodafone firmware terafile.co/4616e5212201/G3815XXUAMJ1_G3815VFGAMJ1_ATL.zip
Click to expand...
Click to collapse
Thank you. Now I have the official Rom to work with instead of my dev one. Hopefully have a working recovery soon.
http://forum.xda-developers.com/showthread.php?t=2598382 anybody tried this?
Hi terminal23
It has been reported by liviugreuu that s4 mini cwm is stuck in recovery, but also that his web-built and my manual-built cwm return stock.
Now in 2598382 you report that aureljared manual-built cwm also returns stock, all if, first time, forcing custom recovery boot.
What's strange is that s4 mini cwm does not return stock.
In general, when one, first time, forces custom recovery boot, it is strange to see stock instead,
unless sm-g3815 would have some mechamism to detect custom even when not booting normal.
Thanks
Nofan Tasi said:
Hi terminal23
It has been reported by liviugreuu that s4 mini cwm is stuck in recovery, but also that his web-built and my manual-built cwm return stock.
Now in 2598382 you report that aureljared manual-built cwm also returns stock, all if, first time, forcing custom recovery boot.
What's strange is that s4 mini cwm does not return stock.
In general, when one, first time, forces custom recovery boot, it is strange to see stock instead,
unless sm-g3815 would have some mechamism to detect custom even when not booting normal.
Thanks
Click to expand...
Click to collapse
Hi Nofan Tasi!
honestly i don't know what's responsable for returning stock recovery,i have rooted many devices,sim unlocked many devices also flashed custom roms,unlocked bootloaders and so on,but i can tell you for sure that now i'm clueless about this devices that have Knox protection enabled and ,write protection enabled..i searched for weeks to find a way to root SM G3815 but seem's that nobody found a way to root it,i hope that in the near future somebody will find a glitch or something
Agreed terminal23 (and others), the SM G3815 seems hard to root.
But some knox devices are rooted (right?) so we can keep on hoping.
I tried kernelchopper variants. Note that kernelchopper has a defect which is now fixed in v2.0.
But it fails "can't pick minimal mmap base address".
What maybe one could try is build a boot.img with custom kernel and
install it with fastboot or heimdall. For such kernel one would know
where sys_setresuid is and one could (try to) patch it in memory to as
done in thread 40873964. But I am too much of a coward and not expert
enough to try this out. One can build the kernel, I did so, (samsung
source is available), and, instructions on how to make boot.img do
exist.
Have a nice day
Nofan Tasi said:
Agreed terminal23 (and others), the SM G3815 seems hard to root.
But some knox devices are rooted (right?) so we can keep on hoping.
I tried kernelchopper variants. Note that kernelchopper has a defect which is now fixed in v2.0.
But it fails "can't pick minimal mmap base address".
What maybe one could try is build a boot.img with custom kernel and
install it with fastboot or heimdall. For such kernel one would know
where sys_setresuid is and one could (try to) patch it in memory to as
done in thread 40873964. But I am too much of a coward and not expert
enough to try this out. One can build the kernel, I did so, (samsung
source is available), and, instructions on how to make boot.img do
exist.
Have a nice day
Click to expand...
Click to collapse
Did anyone tried this?
The 'brick' probability is a bit high for me (not having Odin/windows, only heimdall/linux).
I might want to try to flash sammobile boot.img with heimdall.
- if it works then I am fine and can try to flash whatever experimental boot.img one makes.
- if it does not work, I guess I am bricked (unless, perhaps, if recovery not overwritten, I can successfully flash sammobile zip)
btw did anyone ever reflash G3815XXUAMJ1_G3815VFGAMJ1_PRO.zip with success?
Thanks
4.3
FILLY86 said:
Did anyone tried this?
Click to expand...
Click to collapse
sorry ignore...
anyone similar experience?
kieronspitter said:
Any help with this? Phone is not currently rooted.
Click to expand...
Click to collapse
Hi all
We have root now, thanks to Chainfire,... I hope he received appropriate donations.
I, perhaps, would also like CWM, but, for now, I rather have a question about stock recovery (which supposedly would be restored when rooting):
Mine behaves odd in that it shows a red ! triangle and prints 'No command.', and then, reboot choice prints 'Error!' but continues.
Does anybody else, rooted or not, have similar recovery behaviour?
Thanks!
kieronspitter said:
Any help with this? Phone is not currently rooted.
Click to expand...
Click to collapse
Hi kieronspitter
Another attempt to build CWM fails to boot in recovery ... Instead it tries once and then boots normally. As if, somehow, a custom recovery was detected, but then, how come Chainfire's CF-Auto-Root recovery img does boot (and, moreover, installs root). It is far above my experience. Note that, unlike what was reported by others, my own built CWM did not boot as stock one, neither was it overwritten by stock one. It just happens to not boot (either because not good or because refused). I compared both stock and mine and only ramdisk (of course) is different, in ramdisk same fstab is used. I built ROMs and CWM recoveries for various devices in the past. But firmware becomes more and more immune, it seems...
Perhaps it has to do with Samsung KNOX?
recipe:
--
mkdir sm-g3815
cd sm-g3815
export PATH=~/bin:$PATH
repo init -u git://github.com/CyanogenMod/android.git -b cm-11.0
repo sync
. build/envsetup.sh
make -j8 otatools
export PATH=$PATH:$PWD/out/host/linux-x86/bin
build/tools/device/mkvendor.sh samsung wilcoxlte /tmp/recovery.img
lunch cm_wilcoxlte-eng
. build/tools/device/makerecoveries.sh cm_wilcoxlte-eng
--
env:
--
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.4.2
CM_VERSION=11-20140120-UNOFFICIAL-wilcoxlte
TARGET_PRODUCT=cm_wilcoxlte
TARGET_BUILD_VARIANT=eng
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a-neon
TARGET_CPU_VARIANT=cortex-a7
HOST_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-3.12.7-gentoo-x86_64-with-Ubuntu-13.10-saucy
HOST_BUILD_TYPE=release
BUILD_ID=KOT49H
OUT_DIR=/root/sm-g3815/out
--
have a nice day
Nofan Tasi said:
Hi kieronspitter
Another attempt to build CWM fails to boot in recovery ... Instead it tries once and then boots normally. As if, somehow, a custom recovery was detected, but then, how come Chainfire's CF-Auto-Root recovery img does boot (and, moreover, installs root). It is far above my experience. Note that, unlike what was reported by others, my own built CWM did not boot as stock one, neither was it overwritten by stock one. It just happens to not boot (either because not good or because refused). I compared both stock and mine and only ramdisk (of course) is different, in ramdisk same fstab is used. I built ROMs and CWM recoveries for various devices in the past. But firmware becomes more and more immune, it seems...
Perhaps it has to do with Samsung KNOX?
recipe:
--
mkdir sm-g3815
cd sm-g3815
export PATH=~/bin:$PATH
repo init -u git://github.com/CyanogenMod/android.git -b cm-11.0
repo sync
. build/envsetup.sh
make -j8 otatools
export PATH=$PATH:$PWD/out/host/linux-x86/bin
build/tools/device/mkvendor.sh samsung wilcoxlte /tmp/recovery.img
lunch cm_wilcoxlte-eng
. build/tools/device/makerecoveries.sh cm_wilcoxlte-eng
--
env:
--
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.4.2
CM_VERSION=11-20140120-UNOFFICIAL-wilcoxlte
TARGET_PRODUCT=cm_wilcoxlte
TARGET_BUILD_VARIANT=eng
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a-neon
TARGET_CPU_VARIANT=cortex-a7
HOST_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-3.12.7-gentoo-x86_64-with-Ubuntu-13.10-saucy
HOST_BUILD_TYPE=release
BUILD_ID=KOT49H
OUT_DIR=/root/sm-g3815/out
--
have a nice day
Click to expand...
Click to collapse
What are the contents of /system/etc/install-recovery.sh?
That slippery little git was responsible for abnormal recovery behaviour on the AT&T Galaxy Express 1.
It replaced whatever was on the recovery partition with stock on every reboot.
Dunno if this helps you guys :-/
Beamed from my Galaxy Express using Tapatalk
Hi aureljared
Right, on some stock ROMs this script reinstalls stock recovery on boot.
It seems /system/etc/install-recovery.sh on my device got added by CF-Auto-Root because it is not present in stock system ext4 image (as I checked)
content is:
--
#!/system/bin/sh
# If you're implementing this in a custom kernel/firmware,
# I suggest you use a different script name, and add a service
# to launch it from init.rc
# Launches SuperSU in daemon mode only on Android 4.3+.
# Nothing will happen on 4.2.x or older, unless SELinux+Enforcing.
# If you want to force loading the daemon, use "--daemon" instead
/system/xbin/daemonsu --auto-daemon &
# Some apps like to run stuff from this script as well, that will
# obviously break root - in your code, just search this file
# for "install-recovery-2.sh", and if present, write there instead.
/system/etc/install-recovery-2.sh
--
(there is no /system/etc/install-recovery-2.sh)
What puzzles me is that the CWM I built does not boot. It has same zImage and other parts as stock, but, of course, ramdisk is different than stock.
Would the device refuse to boot custome recovery altogether?
hello guys, so basicly im trying to build a private build of faux kernel, with the updated f2fs commits (so i can keep using it with f2fs)
however when i try to make it, the build fails with the error:
Code:
init/do_mounts_rd.o: In function `prompt_ramdisk':
/home/antonio/Downloads/Nexus_5-kk_mr2/init/do_mounts_rd.c:22: multiple definition of `tmpfile'
init/do_mounts.o:/home/antonio/Downloads/Nexus_5-kk_mr2/init/do_mounts.c:70: first defined here
init/do_mounts_initrd.o: In function `no_initrd':
/home/antonio/Downloads/Nexus_5-kk_mr2/init/do_mounts_initrd.c:19: multiple definition of `tmpfile'
init/do_mounts.o:/home/antonio/Downloads/Nexus_5-kk_mr2/init/do_mounts.c:70: first defined here
make[1]: *** [init/mounts.o] Error 1
make: *** [init] Error 2
im using linaro arm-cortex_a15-linux-gnueabihf-linaro_4.9.3-2014.11 as a toolchain and my ubuntu is 14.04
EDIT: mods can close or even delete the thread if they want, my mistake was not cherry picking all the commits (forgot one).
Post your source first on git with proper commits to identify issue.
I have similar issues building faux, but I don't have them while building elex.
hi,
this is my attempt to bring Cyanogen 13 to the Samsung Galaxy SL ( i9003 ).
So far i got the kernel/device/vendor repos synced and edited.
I still haven't manage to pass the "brunch galaxysl" command
first error was:
hardware/ti/wlan/mac80211/wpa_supplicant_lib/Android.mk:19: external/wpa_supplicant_8_ti/wpa_supplicant/android.config: No such file or directory
fixed by editing BoardConfing.mk ( not sure it will allow the wi-fi to work after this )
last error is :
make: *** No rule to make target '/home/nots/cm13/out/target/product/galaxysl/utilities/flash_image', needed by '/home/nots/cm13/out/target/product/galaxysl/bootstrap.cpio.gz'. Stop.
If anyone want to help, you are more than welcome
thanks to dhiru1602 and rodero95 for there previous work on this phone
mkdir out/target/product/galaxysl/utilities
copy busybox erase_image flash_image make_ext4fs to the dir created
busybox erase_image flash_image make_ext4fs are from ROM pack
notsgnik said:
hi,
this is my attempt to bring Cyanogen 13 to the Samsung Galaxy SL ( i9003 ).
So far i got the kernel/device/vendor repos synced and edited.
I still haven't manage to pass the "brunch galaxysl" command
first error was:
hardware/ti/wlan/mac80211/wpa_supplicant_lib/Android.mk:19: external/wpa_supplicant_8_ti/wpa_supplicant/android.config: No such file or directory
fixed by editing BoardConfing.mk ( not sure it will allow the wi-fi to work after this )
last error is :
make: *** No rule to make target '/home/nots/cm13/out/target/product/galaxysl/utilities/flash_image', needed by '/home/nots/cm13/out/target/product/galaxysl/bootstrap.cpio.gz'. Stop.
If anyone want to help, you are more than welcome
thanks to dhiru1602 and rodero95 for there previous work on this phone
Click to expand...
Click to collapse
Yeah I've actually followed quite some hack arounds for the device...... You'll need patches for the following repos (Unfortunately no longer in Nameless Gerrit. I'll try to upload them):
device/samsung/galaxysl
kernel/samsung/latona
hardware/ti/omap3
hardware/samsung
frameworks/av
bionic
I guess that's all that I've patched. And one more word of advice: CyanogenMod dropped support for the S2 so it'll never compile for the SL. It's better to download NamelessROM's source (check repo's --reference flag to speed up the download) because it has some support.
Cheers!
Technohacker
Technohacker1995 said:
Yeah I've actually followed quite some hack arounds for the device...... You'll need patches for the following repos (Unfortunately no longer in Nameless Gerrit. I'll try to upload them):
device/samsung/galaxysl
kernel/samsung/latona
hardware/ti/omap3
hardware/samsung
frameworks/av
bionic
I guess that's all that I've patched. And one more word of advice: CyanogenMod dropped support for the S2 so it'll never compile for the SL. It's better to download NamelessROM's source (check repo's --reference flag to speed up the download) because it has some support.
Cheers!
Technohacker
Click to expand...
Click to collapse
plz give us link for download and install rom
mehran200067 said:
plz give us link for download and install rom
Click to expand...
Click to collapse
For which version? I've compiled 5.0 (here: http://forum.xda-developers.com/gal...ake-android-5-0-lollipop-i9003-t2928989/page6 I've posted some fixes in subsequent posts so read all of 'em), 5.1's not available (doesn't boot...... idk why) whereas we're trying to port 6
Cheers!
Technohacker
I am trying to build AOSP from source but I do not know where the specific binaries for the Oneplus One are located.
yqazi27 said:
I am trying to build AOSP from source but I do not know where the specific binaries for the Oneplus One are located.
Click to expand...
Click to collapse
https://github.com/TheMuppets/proprietary_vendor_oneplus
Mr.Ak said:
https://github.com/TheMuppets/proprietary_vendor_oneplus
Click to expand...
Click to collapse
This is only the vendor info. I thought there were two other things needed as well.
yqazi27 said:
This is only the vendor info. I thought there were two other things needed as well.
Click to expand...
Click to collapse
https://github.com/CyanogenMod/android_device_oneplus_bacon
Mr.Ak said:
https://github.com/CyanogenMod/android_device_oneplus_bacon
Click to expand...
Click to collapse
Thank you so much!! Do you know how to implement these into the repository? On the AOSP site, it says the binaries will be self-extracting(obviously not this case).
I have the vendor, device tree, and kernel files all in appropriate places. But when I use the command "lunch", I get the error message:
build/core/product_config.mk:227: *** Can not locate config makefile for product "cm_bacon". Stop.
Click to expand...
Click to collapse
yqazi27 said:
I have the vendor, device tree, and kernel files all in appropriate places. But when I use the command "lunch", I get the error message:
Click to expand...
Click to collapse
This is due to your device tree not being present in the rom dir. Download and make device tree manually compatible... You need these:
oppo common gits
vendor/oneplus
device/oneplus/bacon
kernel/oneplus/msm8974
Download these from github.com/CyanogenMod because you need cm_bacon
Mr.Ak said:
This is due to your device tree not being present in the rom dir. Download and make device tree manually compatible... You need these:
oppo common gits
vendor/oneplus
device/oneplus/bacon
kernel/oneplus/msm8974
Download these from github.com/CyanogenMod because you need cm_bacon
Click to expand...
Click to collapse
I did all of this and many errors but in the end, I was finally able to start the build. Thanks!
Now, a few minutes into the build I got a few warnings and finally an error.
frameworks/av/media/libaaudio/examples/input_monitor/static/Android.mk: warning: input_monitor: unusual tags examples
frameworks/av/media/libaaudio/examples/write_sine/static/Android.mk: warning: write_sine: unusual tags examples
[677/968] including system/sepolicy/Android.mk ...
system/sepolicy/Android.mk:107: warning: BOARD_SEPOLICY_VERS not specified, assuming current platform version
[968/968] including vendor/oneplus/bacon/Android.mk ...
No private recovery resources for TARGET_DEVICE bacon
platform_testing/build/tasks/tests/instrumentation_metric_test_list.mk: warning: continuous_instrumentation_metric_tests: Unknown installed file for module perf-setup.sh
platform_testing/build/tasks/tests/instrumentation_test_list.mk: warning: continuous_instrumentation_tests: Unknown installed file for module RecyclerViewTests
platform_testing/build/tasks/tests/instrumentation_test_list.mk: warning: continuous_instrumentation_tests: Unknown installed file for module SettingsFunctionalTests
platform_testing/build/tasks/tests/instrumentation_test_list.mk: warning: continuous_instrumentation_tests: Unknown installed file for module LauncherFunctionalTests
platform_testing/build/tasks/tests/native_metric_test_list.mk: warning: continuous_native_metric_tests: Unknown installed file for module perf-setup.sh
build/core/base_rules.mk:390: warning: overriding commands for target `out/target/product/bacon/root/res/images/charger/battery_fail.png'
build/core/base_rules.mk:390: warning: ignoring old commands for target `out/target/product/bacon/root/res/images/charger/battery_fail.png'
[ 99% 292/293] glob system/nfc/src/nfc/tags/*.cc
ninja: error: '/.txt', needed by 'out/target/common/obj/PACKAGING/checkpublicapi-cm-last-timestamp', missing and no known rule to make it
19:01:46 ninja failed with: exit status 1
Click to expand...
Click to collapse
What is the error in the end supposed to mean and how do I fix it?
yqazi27 said:
I did all of this and many errors but in the end, I was finally able to start the build. Thanks!
Now, a few minutes into the build I got a few warnings and finally an error.
What is the error in the end supposed to mean and how do I fix it?
Click to expand...
Click to collapse
We're missing a Source (Prebuilt CMSDK),try this:
clone THIS at prebuilts/cmsdk and continue the build.