Hello, I'm trying to follow Cyanogen's wiki to install CWM.
The steps are: 1) download zImage, 2) download heimdall, 3) flash zImage. I'm stuck at number 2.
I tried with the suggested heimdall_v1.4rc1_mac.zip (sorry I can't post outside links), but the kext inside does not load correctly.
So now I'm trying to compile it myself. I git cloned the repo, installed dependencies, successfully made libpit. Going on with Heimdall.
Code:
cd heimdall
./configure
make
[...]
cc1plus: error: unrecognized command line option "-std=c++0x"
I don't know exactly what this means, but I edited Makefile and substituted every g++ (i686-apple-darwin11-llvm-g++-4.2 (GCC) 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2336.11.00)) occurrency with clang -v.
Now I'm stuck on:
Code:
[...]
Undefined symbols for architecture x86_64:
"std::string::find_first_of(char const*, unsigned long, unsigned long) const", referenced from:
[...]
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[1]: *** [heimdall] Error 1
make: *** [all] Error 2
If it helps you, there are a lot of:
Code:
ignoring nonexistent directory "/usr/include/c++/4.2.1/i686-apple-darwin10/x86_64"
ignoring nonexistent directory "/usr/include/c++/4.0.0"
ignoring nonexistent directory "/usr/include/c++/4.0.0/i686-apple-darwin8/"
ignoring nonexistent directory "/usr/include/c++/4.0.0/backward"
Running on MacBookPro7,1, Lion 10.7.5, Xcode 4.5.1
EDIT: I also tried installing heimdall 1.3.1 dmg, but installation failed (kernel module couldn't be installed).
bump
bump
bump
what compiler are you using? If GCC what version of GCC are you using? c++0x / c++11 support has only been added starting with gcc v4.3
Plod72 said:
what compiler are you using? If GCC what version of GCC are you using? c++0x / c++11 support has only been added starting with gcc v4.3
Click to expand...
Click to collapse
GCC appears only in CCDEPMODE and CXXDEPMODE. For the rest I'm using clang.
i686-apple-darwin11-llvm-gcc-4.2 (GCC) 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2336.11.00)
Click to expand...
Click to collapse
Apple clang version 4.1 (tags/Apple/clang-421.11.66) (based on LLVM 3.1svn)
Target: x86_64-apple-darwin11.4.2
Thread model: posix
Click to expand...
Click to collapse
bump
bump
bump
Why dont you flash a custom kernel? They have cwm preinstalled... or.. maybe im missing something?
Sent from my GT-I9100 using xda app-developers app
Spiralzz said:
Why dont you flash a custom kernel? They have cwm preinstalled... or.. maybe im missing something?
Click to expand...
Click to collapse
Don't I need heimdall to flash a kernel?
vipervault said:
Don't I need heimdall to flash a kernel?
Click to expand...
Click to collapse
Use odin. Very easy and simple.
Sent from my GT-I9100 using xda app-developers app
Lol, you guys been at it since 1/25.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from the little guy
I can't use odin, I don't have Windows.
vipervault said:
I can't use odin, I don't have Windows.
Click to expand...
Click to collapse
No need to compile heimdall.
Download heimdall from here: http://www.glassechidna.com.au/products/heimdall/
The normal heimdall uses a terminal I believe. The frontend one has a gui like Odin and should be easy to use.
Edit: Don't download the latest (1.3.2). Download the previous version, since it is stated that the latest one broke compatibility. Ive never used heimdall though, so I cant guide you further.
Sent from my GT-I9100 using xda app-developers app
I know there are prebuilt heimdall but the kernel module inside does not work.
That's why I'm compiling it. Is there anybody that can help me on that?
vipervault said:
I know there are prebuilt heimdall but the kernel module inside does not work.
That's why I'm compiling it. Is there anybody that can help me on that?
Click to expand...
Click to collapse
Just use another PC. You're going through a lot of hassle. Or simply download Mobile Odin (pro) app to flash. That's easiest and safe to use.
Sent from my GT-I9100 using xda app-developers app
Thank you guys I know how to flank this problem. I'd just like to receive your help to solve this compilation issue.
vipervault said:
Hello, I'm trying to follow Cyanogen's wiki to install CWM.
The steps are: 1) download zImage, 2) download heimdall, 3) flash zImage. I'm stuck at number 2.
I tried with the suggested heimdall_v1.4rc1_mac.zip (sorry I can't post outside links), but the kext inside does not load correctly.
So now I'm trying to compile it myself. I git cloned the repo, installed dependencies, successfully made libpit. Going on with Heimdall.
Code:
cd heimdall
./configure
make
[...]
cc1plus: error: unrecognized command line option "-std=c++0x"
I don't know exactly what this means, but I edited Makefile and substituted every g++ (i686-apple-darwin11-llvm-g++-4.2 (GCC) 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2336.11.00)) occurrency with clang -v.
Now I'm stuck on:
Code:
[...]
Undefined symbols for architecture x86_64:
"std::string::find_first_of(char const*, unsigned long, unsigned long) const", referenced from:
[...]
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[1]: *** [heimdall] Error 1
make: *** [all] Error 2
If it helps you, there are a lot of:
Code:
ignoring nonexistent directory "/usr/include/c++/4.2.1/i686-apple-darwin10/x86_64"
ignoring nonexistent directory "/usr/include/c++/4.0.0"
ignoring nonexistent directory "/usr/include/c++/4.0.0/i686-apple-darwin8/"
ignoring nonexistent directory "/usr/include/c++/4.0.0/backward"
Running on MacBookPro7,1, Lion 10.7.5, Xcode 4.5.1
EDIT: I also tried installing heimdall 1.3.1 dmg, but installation failed (kernel module couldn't be installed).
Click to expand...
Click to collapse
Hi,
you have probably solved it already, but when I got such error messages the solution was to set certain environment variables before calling ./configure
export CC=clang
export CXX=clang++
export CFLAGS="-I/usr/include/ -I/sw/include/"
export LDFLAGS="-L/usr/lib -L/sw/lib/"
I used fink to download and compile libusb1 (with version 1.0.8) prior to compile heimdall. In case you use macports, use the correct include and lib dirs instead of /sw/include and /sw/lib. In my case I didn't have to change anything in the original Makefile.
The only frustration with this heimdall was that the --primary-boot option did not work properly, so I had to skip --repartition and rewriting the primary boot partition with boot.bin.
you need a newer GCC to get it use Macports. if you do not have it install it. after that the command for the newer version is
Code:
sudo port install gcc47
if you want gcc 4.7
after you have the new version you need to set it to default and hope that heimdall compiler choose it! to do so you have to do so:
Code:
port select --list gcc
Available versions for gcc:
gcc42
llvm-gcc42
mp-gcc47
none (active)
if you have more than one gcc then you have more then one version of gcc from xcode. the mp-gccxx is the macports version. now we will set itto default:
Code:
sudo port select --set gcc mp-gcc47
Password:
Selecting 'mp-gcc47' for 'gcc' succeeded. 'mp-gcc47' is now active.
now you should had setted as default the gcc47 and compiling heimdall should work!
edit: i tried. i get all the way to
Code:
sudo make install
but then get:
Code:
cc1plus: error: unrecognized command line option "-std=c++0x"
probably benjamin setted the source to always use xcodes version of gcc that do not suport it.
Related
Hello dev community
I am currently trying to build my own kernel / zImage, but for some reason it doesn't work, when I flash my zImage the SGS2 crashs at the bootscreen with the yellow triangle.
Not even the battery animation when charging while off works anymore *lol*
Here is what I did so far:
extracted a stock initramfs from a samsung stock kernel
got the Samsung kernel sources and extracted on my PC
got the codesourcery toolchain and installed it
edited the path to the toolchain into kernel/Makefile
ran
make c1_rev02_defconfig (as stated in the readme.txt of the src download)
set the path to the extracted iniramfs files in the config
ran
make zImage
It eventually tells me "kernel zImage ready at ...."
padded with 0x00s to the 8MiB size, .tar'ed and flashed via Odin
But it doesn't boot.
When I throw my zImage at the initramfs extractor script, I get the proper initramfs files dumped, so they seem to be fine.
Searched around this forums for two days now, found a few "zImage repacker scripts" but none work or clear up any of my questions.
Any hints on what I missed or did wrong are appreciated
And while we're at it, another question:
At new FW builds, does the actual kernel itself change too, or is it only changes in the initramfs? Because there is only one set of sources from Samsung.... so I assume the actual kernel stays the same and using the initramfs of the targetted FW will suufice?
Why did you pad it up to 8mb?
also, when setting the initramfs source, did you set these to you uid you are compiling with?
CONFIG_INITRAMFS_ROOT_UID=1000
CONFIG_INITRAMFS_ROOT_GID=1000
Hm, padded to 8MB as all kernels are (padded to) 8MB, aren't they?
Tried flashing an unpadded version too, still no go.
And yes, UID and GID are set to the ones my user is running as....
Close to the end of the compiler run, I get a "found 14 module section missmatches" kind of message - could that have something to do with my zImage not working? And how would I fix that?
Oh c'mon, it can't be that hard, so many people are making their own zImages.... what am I missing here.... :-/
First of all, you cant just use a stock initramfs image, shove it into another kernel and expect it to work. There are kernel modules in there which need to be updated first before you do the last "make zImage".
Try this:
0. make sure your config is correct. you should copy c1_rev02_defconfig from inside arm/ to source_root/.config and do a "make oldconfig". Then adjust your configs as necessary ("make menuconfig" etc)
1. "make modules"
2. "INSTALL_MOD_PATH=~ make modules_install"
3. goto your home dir and pick out the modules and put them into the path of your initramfs files (/lib)
4. finally, make zImage.
5. theres no need to pad to 8mb. that is an urban legend
OK, did all that.... still no go.... :-/
Try this script:
Code:
#!/bin/bash
# Set Default Path
TOP_DIR=$PWD
KERNEL_PATH=/home/neophyte-x360/kernel/GALAXYS2/2.6.35.7
# TODO: Set toolchain and root filesystem path
TAR_NAME=zImage.tar
TOOLCHAIN="/home/neophyte-x360/android/system/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-"
# TOOLCHAIN="/home/neophyte-x360/toolchain/bin/arm-none-eabi-"
ROOTFS_PATH="/home/neophyte-x360/kernel/GALAXYS2/initramfs-SGS2"
echo "Cleaning latest build"
make ARCH=arm CROSS_COMPILE=$TOOLCHAIN -j`grep 'processor' /proc/cpuinfo | wc -l` clean
cp -f $KERNEL_PATH/arch/arm/configs/c1_rev02_defconfig $KERNEL_PATH/.config
make -j4 -C $KERNEL_PATH oldconfig || exit -1
make -j4 -C $KERNEL_PATH ARCH=arm CROSS_COMPILE=$TOOLCHAIN || exit -1
cp drivers/bluetooth/bthid/bthid.ko $ROOTFS_PATH/lib/modules/
cp drivers/net/wireless/bcm4330/dhd.ko $ROOTFS_PATH/lib/modules/
cp drivers/samsung/j4fs/j4fs.ko $ROOTFS_PATH/lib/modules/
cp drivers/samsung/fm_si4709/Si4709_driver.ko $ROOTFS_PATH/lib/modules/
cp drivers/scsi/scsi_wait_scan.ko $ROOTFS_PATH/lib/modules/
cp drivers/samsung/vibetonz/vibrator.ko $ROOTFS_PATH/lib/modules/
make -j4 -C $KERNEL_PATH ARCH=arm CROSS_COMPILE=$TOOLCHAIN || exit -1
# Copy Kernel Image
cp -f $KERNEL_PATH/arch/arm/boot/zImage .
cd arch/arm/boot
tar cf $KERNEL_PATH/arch/arm/boot/$TAR_NAME zImage && ls -lh $TAR_NAME
And try with other initramfs, maybe could be this.
PD: I forgot that with my script you have to select your initramfs inside .config
Very interesting thread!
Im about to study computer science and software engineering for 3 years in august.
Hoping/wishing/expecting to get into this eventually!
put this in your build script:-
export LOCALVERSION="-I9100XWKE7-CL215725"
this is just an example set its value to the same as the initramfs you used, e.g. the magicver in the modules.
sounds like your initramfs are incomplete...or more likely your toolchain is not quite right. even without recovery, your zimage should be 6-7mb...(no padding, and there is no need to)
OK, done a clean rebuild, taking care of everything you guys said:
made new initramfs dump from a stock zImage
make mrproper
make c1_rev02_defconfig
make menuconfig - set the paths/prefixes for toolchain, localversion and initramfs (also set my users UID and GID for mapping to UID/GUI 0) there, left everything else untouched and at defaults
make
copied the freshly built modules into my initramfs dir (checked with a hexeditor for the proper versionmagic, looks OK)
make zImage
resulting zImake size: ~5.7MB and no go, still doesn't boot.
I'll try now with another toolchain (using the last one available for d/l so far, just got the 2009-something one mentioned in the sources readme and going to try to use that one now) as well as different initramfs dumper....
I have not much hope this will change the outcome, but it's at least worth a try....
// EDIT (a few hours later xD)
SUCCESS
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(anyone knows what the #9 is? where it comes from, what it says?)
I *finally* managed to get a completely self built kernel to boot \o/
So, what was it that played showstopper the whole time: THE TOOLCHAIN!
I had the latest (2011-something) version of the CodeSourcery toolchain installed - that does not seem to be a good idea.
Did exactely what I did before, but now with the 2009q3 version installed (like the readme of the source states) - and tadaa, it works!
// EDIT 2
Figured out the #9 as well, it's the build number / version; how many times I ran "make" since the last "make mrproper"
LET THE MODDING BEGIN (now the fun starts)
Glad to see someone's happy. I'm also trying to compile a kernel from source. However, mine's an I9100G. Managed to compile, flash and boot up my phone, but battery status and Wifi don't work. After looking through the dmesg log, apparently the battery driver is not being initialised. I wonder if anyone can help me? Maybe someone with knowledge of the OMAP platform?
aidfarh said:
Glad to see someone's happy. I'm also trying to compile a kernel from source. However, mine's an I9100G. Managed to compile, flash and boot up my phone, but battery status and Wifi don't work. After looking through the dmesg log, apparently the battery driver is not being initialised. I wonder if anyone can help me? Maybe someone with knowledge of the OMAP platform?
Click to expand...
Click to collapse
You can give me initramfs?
I cqn give it a try.
Sent from my GT-I9100
How to
HellcatDroid said:
Hello dev community
I am currently trying to build my own kernel / zImage, but for some reason it doesn't work, when I flash my zImage the SGS2 crashs at the bootscreen with the yellow triangle.
Not even the battery animation when charging while off works anymore *lol*
Click to expand...
Click to collapse
Could you please give a few mn to write a min How To? I would like to build my own, but as a noob, I am a litle lost in all the info I gathered.
It would be nice to profit from your experience.
Or maybe do you have any good links?
TY
netchip said:
You can give me initramfs?
I cqn give it a try.
Sent from my GT-I9100
Click to expand...
Click to collapse
Well, if you think it can help, here's the download link for my initramfs:
http://dl.dropbox.com/u/13796854/initramfs.zip
It's for an I9100G, though. Do you have one to test with?
aidfarh said:
Well, if you think it can help, here's the download link for my initramfs:
http://dl.dropbox.com/u/13796854/initramfs.zip
It's for an I9100G, though. Do you have one to test with?
Click to expand...
Click to collapse
I haven't one for testing.
I am a kernel developer here for SGS2, check the development part.
Hi guys I am kind of a noob when it comes to linux and compiling and have hit a brick wall. I have this posted here in Chef Central and in general android Q&A so hopefully someone has an idea. I have been trying to compile CM9 for about three days now and no matter what I do I get this output. It is 95% of the time after the "install libwebcore.so" line.
Code:
install: out/target/product/maguro/system/lib/libwebcore.so
UNEXPECTED TOP-LEVEL ERROR:
java.lang.OutOfMemoryError: GC overhead limit exceeded
at com.android.dx.util.IntList.(IntList.java:87)
at com.android.dx.rop.code.RopMethod.calcPredecessors(RopMethod.java:154)
at com.android.dx.rop.code.RopMethod.labelToPredecessors(RopMethod.java:95)
at com.android.dx.dex.code.RopTranslator.pickOrder(RopTranslator.java:352)
at com.android.dx.dex.code.RopTranslator.translateAndGetResult(RopTranslator.java:212)
at com.android.dx.dex.code.RopTranslator.translate(RopTranslator.java:106)
at com.android.dx.dex.cf.CfTranslator.processMethods(CfTranslator.java:293)
at com.android.dx.dex.cf.CfTranslator.translate0(CfTranslator.java:134)
at com.android.dx.dex.cf.CfTranslator.translate(CfTranslator.java:87)
at com.android.dx.command.dexer.Main.processClass(Main.java:483)
at com.android.dx.command.dexer.Main.processFileBytes(Main.java:455)
at com.android.dx.command.dexer.Main.access$400(Main.java:67)
at com.android.dx.command.dexer.Main$1.processFileBytes(Main.java:394)
at com.android.dx.cf.direct.ClassPathOpener.processArchive(ClassPathOpener.java:245)
at com.android.dx.cf.direct.ClassPathOpener.processOne(ClassPathOpener.java:131)
at com.android.dx.cf.direct.ClassPathOpener.process(ClassPathOpener.java:109)
at com.android.dx.command.dexer.Main.processOne(Main.java:418)
at com.android.dx.command.dexer.Main.processAllFiles(Main.java:329)
at com.android.dx.command.dexer.Main.run(Main.java:206)
at com.android.dx.command.dexer.Main.main(Main.java:174)
at com.android.dx.command.Main.main(Main.java:95)
make: *** [out/target/common/obj/JAVA_LIBRARIES/framework_intermediates/noproguard.classes-with-local.dex] Error 3
Before I tried to compile CM I did successfully compile AOSP for my Gnex. I have searched and tried everything I could find. I've tried these values in the common.py file and just about every combo I could think of per recommendations I found online.
Code:
check = (sys.maxsize > 2**32)
if check is True:
cmd = ["java", "Xmx2048m", "-jar",
os.path.join(OPTIONS.search_path, "framework", "signapk.jar")]
else:
cmd = ["java", "-Xmx1024m", "-jar",
os.path.join(OPTIONS.search_path, "framework", "signapk.jar")]
I have also checked my swap and as far as I can tell its there and working but it seams to never be used. I have tried all the commands I could find online to make sure it was enabled but Idk what else to try or check.
Also I am using a quad core AMD with 6GB of RAM if anyone is curious. Any and all advice/ideas would be very much appreciated at this point I am at a complete loss. Thanks for looking and helping guys.
EDIT:I just finished a successful build of AOSP for my galaxy nexus so I am really confused as to why I run out of memory for CM9.
Sky-
Try something for me please.
open your terminal. Can you run this please?
test.py
Code:
#!/usr/bin/env python
import sys
import platform
p = platform.dist()
distro = p[0]
version = p[1]
name = p[2]
check = (sys.maxsize > 2**32)
print "Distro: %s\nVersion: %s\n Name: %s\n 64bit OS: %s" % (distro, version, name, check)
Code:
python test.py
Alright I just got home from work so just give me about 30 mins or so and I'll give it a try.
Sent from my GT-N7000 or Galaxy Nexus
I tried the commands you posted here and either I am missing some stuff that should be installed on my computer or I am to much of a noob to enter the commands correctly. Here was my output as I entered the commands.
Code:
[email protected]:~$ test.py
test.py: command not found
[email protected]:~$ #!/usr/bin/env python
[email protected]:~$ import sys
[email protected]:~$ import platform
[email protected]:~$
[email protected]:~$ p = platform.dist()
bash: syntax error near unexpected token `('
[email protected]:~$ distro = p[0]
distro: command not found
[email protected]:~$ version = p[1]
version: command not found
[email protected]:~$ name = p[2]
No command 'name' found, did you mean:
Command 'named' from package 'bind9' (main)
Command 'namei' from package 'util-linux' (main)
Command 'lame' from package 'lame' (multiverse)
Command 'cname' from package 'cfs' (universe)
Command 'uname' from package 'coreutils' (main)
Command 'mame' from package 'sdlmame' (multiverse)
name: command not found
[email protected]:~$
[email protected]:~$ check = (sys.maxsize > 2**32)
bash: syntax error near unexpected token `('
[email protected]:~$
[email protected]:~$ print "Distro: %s\nVersion: %s\n Name: %s\n 64bit OS: %s" % (distro, version, name, check)
bash: syntax error near unexpected token `('
[email protected]:~$ python test.py
python: can't open file 'test.py': [Errno 2] No such file or directory
[email protected]:~$
Sorry if I entered them incorrectly, I am learning linux as fast as I can. Should I have entered them differently?
Sky-
Haha..yes...you needed to put everything from the # all the way to the end of check) in a file called test.py...then enter python test.py in your command line
Use your editor of choice
Don't worry, everyone was new once.
Sent from my SGH-I757M using xda premium
reallybigabe said:
Haha..yes...you needed to put everything from the # all the way to the end of check) in a file called test.py...then enter python test.py in your command line
Use your editor of choice
Don't worry, everyone was new once.
Sent from my SGH-I757M using xda premium
Click to expand...
Click to collapse
Thank you sir. I'm such a dope . I'll do that tonight when I get home from work.
Sent from my GT-N7000 or Galaxy Nexus
sorry about that, I didn't know you were new. Apologies.
Copy and paste these commands.
Command 1:
Code:
(cat << EOF) > $HOME/test.py
#!/usr/bin/env python
import sys
import platform
p = platform.dist()
distro = p[0]
version = p[1]
name = p[2]
check = (sys.maxsize > 2**32)
print "Distro: %s\nVersion: %s\n Name: %s\n 64bit OS: %s" % (distro, version, name, check)
EOF
press [enter]
Command 2:
Code:
chmod a+x $HOME/test.py
Command 3:
Code:
python $HOME/test.py
Thanks for the beginners guide lol, it worked now. Here was the output of that command.
Code:
[email protected]:~$ python $HOME/test.py
Distro: Ubuntu
Version: 10.04
Name: lucid
64bit OS: True
[email protected]:~$
That's what you were looking for correct?
If I were you I would run a mem check on your memory. There shouldn't be any reason that your getting those errors.
I have 8 gigs and I never have an issue.
lithid-cm said:
If I were you I would run a mem check on your memory. There shouldn't be any reason that your getting those errors.
I have 8 gigs and I never have an issue.
Click to expand...
Click to collapse
How would I go about doing that? Sorry for the noobish questions I just have never had to do this before on any of my PC's. Its just so weird because I'm compiling AOSP as we speak. Just wish it was CM lol.
EDIT: My bad I can do it with the ubuntu install dvd I have.
Sent from my GT-N7000 or Galaxy Nexus
Also if you dont mind me asking lithid, what version of linux do you use to build?
skyhigh2004 said:
Also if you dont mind me asking lithid, what version of linux do you use to build?
Click to expand...
Click to collapse
ubuntu 12.04 64bit
Well I am running a mem test now. If it all goes just fine I think I'm gonna do a fresh install of 12.04 and reset everything up and try again. I'm at a complete loss .
Sent from my GT-N7000 or Galaxy Nexus
Well my computer passed the memory rest with zero errors. So I'm installing 12.04 on a fresh format so hopefully I have better luck later tonight or tomorrow getting it to build.
Sent from my GT-N7000 or Galaxy Nexus
skyhigh2004 said:
Well my computer passed the memory rest with zero errors. So I'm installing 12.04 on a fresh format so hopefully I have better luck later tonight or tomorrow getting it to build.
Sent from my GT-N7000 or Galaxy Nexus
Click to expand...
Click to collapse
I am really interested in this. Please keep this post updated with your success!
lithid-cm said:
I am really interested in this. Please keep this post updated with your success!
Click to expand...
Click to collapse
I'll definitely keep you posted. I'm syncing tonight, then hopefully I'll set it up to build when I leave for work in the morning and I'll have good news when I get off in the afternoon.
Sent from my GT-N7000 or Galaxy Nexus
Well all I can say is ***k yeah. I guess reinstalling ubuntu and upgrading to 12.04 in the process cured my computer . I still have no idea as to why I couldnt build before but at least it works now.
Code:
Package complete: /home/skylar/cm9/out/target/product/maguro/update-cm-9.0.0-RC0-maguro-UNOFFICIAL-signed.zip
097429908172684449fb5a3fe796c290 update-cm-9.0.0-RC0-maguro-UNOFFICIAL-signed.zip
[email protected]:~/cm9$
Now to learn how to cherry pick
skyhigh2004 said:
Well all I can say is ***k yeah. I guess reinstalling ubuntu and upgrading to 12.04 in the process cured my computer . I still have no idea as to why I couldnt build before but at least it works now.
Code:
Package complete: /home/skylar/cm9/out/target/product/maguro/update-cm-9.0.0-RC0-maguro-UNOFFICIAL-signed.zip
097429908172684449fb5a3fe796c290 update-cm-9.0.0-RC0-maguro-UNOFFICIAL-signed.zip
[email protected]:~/cm9$
Now to learn how to cherry pick
Click to expand...
Click to collapse
Easy man.
Click cherry pick.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click copy
change directories in your repo path corresponding to the change. In this example frameworks_base from your repo path.
Code:
cd frameworks/base
paste in that command you just copied. press enter and you have just cherry picked to test a new cm commit.
That sounds very easy. Thanks again for a noob tutorial . Also what would you do to remove the cherry pick if you didnt like the commit? Is that path just added to the local manifest just like device trees and kernels sources?
Sent from my GT-N7000 or Galaxy Nexus
skyhigh2004 said:
That sounds very easy. Thanks again for a noob tutorial . Also what would you do to remove the cherry pick if you didnt like the commit? Is that path just added to the local manifest just like device trees and kernels sources?
Sent from my GT-N7000 or Galaxy Nexus
Click to expand...
Click to collapse
While inside the same path you applied the cp.
git reset --hard HEAD
That will reset to the last cm commit. You can do specific files as well by appending the file path after the command.
Sent from my Nexus S 4G using xda premium
Shouldn't we build Android on Arch Linux rather than on other Linux Distros?
Since Arch Linux is a Rolling Release and you'll have all updated packages, so this makes sense to me....
But why did Android recommend Ubuntu? Did Canonical pay them to advertise Ubuntu? LOL
Peteragent5 said:
Shouldn't we build Android on Arch Linux rather than on other Linux Distros?
Since Arch Linux is a Rolling Release and you'll have all updated packages, so this makes sense to me....
But why did Android recommend Ubuntu? Did Canonical pay them to advertise Ubuntu? LOL
Click to expand...
Click to collapse
That's what Google chose. In terms of Google support.
Sent from my Galaxy Nexus using xda premium
Peteragent5 said:
Shouldn't we build Android on Arch Linux rather than on other Linux Distros?
Since Arch Linux is a Rolling Release and you'll have all updated packages, so this makes sense to me....
But why did Android recommend Ubuntu? Did Canonical pay them to advertise Ubuntu? LOL
Click to expand...
Click to collapse
What do I need the latest "updated" packages? Arch is bleeding edge, what if a "update" breaks a tool we are using to build? When working in a professional environment you want stability not bleeding edge.
Yeah but usually the stable packages give me the errors... Not the updated ones... Ironic LOL
I'm using Ubuntu and I compile just fine.
Sent from my Galaxy Nexus using xda premium
Peteragent5 said:
Yeah but usually the stable packages give me the errors... Not the updated ones... Ironic LOL
Click to expand...
Click to collapse
Well are you using the versions recommended by the Android team? If not that would be why.
lithid-cm said:
I'm using Ubuntu and I compile just fine.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Yeah, I'm starting to reconsider Ubuntu... Arch Linux is a pain to install... Can you still build Android with latest Ubuntu?
thewadegeek said:
Well are you using the versions recommended by the Android team? If not that would be why.
Click to expand...
Click to collapse
I tried to compile a kernel, my os was Debian. The make always gave me errors of outdated packages, so i tried to build the package that was said to be outdated. One package led to another, with a make error saying foo package is outdated -_-
Eventually I got sick of it and I deleted Debian (VirtualBox) and found Arch Linux
I got Arch Linux to install and boot, but didn't try building android yet... It was a pain to install Arch..
Peteragent5 said:
Yeah, I'm starting to reconsider Ubuntu... Arch Linux is a pain to install... Can you still build Android with latest Ubuntu?
I tried to compile a kernel, my os was Debian. The make always gave me errors of outdated packages, so i tried to build the package that was said to be outdated. One package led to another, with a make error saying foo package is outdated -_-
Eventually I got sick of it and I deleted Debian (VirtualBox) and found Arch Linux
I got Arch Linux to install and boot, but didn't try building android yet... It was a pain to install Arch..
Click to expand...
Click to collapse
I build on arch linux just fine. You just need to prevent 3 packages from upgrading after you downgrade them. Everything works just fine.
Peteragent5 said:
Shouldn't we build Android on Arch Linux rather than on other Linux Distros?
Since Arch Linux is a Rolling Release and you'll have all updated packages, so this makes sense to me....
But why did Android recommend Ubuntu? Did Canonical pay them to advertise Ubuntu? LOL
Click to expand...
Click to collapse
Well how I see it is that what platform you use to build a target platform. For e.g. you could compile a Java source code on C platform. Somet
rlasalle15 said:
I build on arch linux just fine. You just need to prevent 3 packages from upgrading after you downgrade them. Everything works just fine.
Click to expand...
Click to collapse
Exactly. Any version of Linux is going to work just so long as you have the needed dependencies installed.
thewadegeek said:
Exactly. Any version of Linux is going to work just so long as you have the needed dependencies installed.
Click to expand...
Click to collapse
Rootz and the Arch linux android wiki are good sources
http://rootzwiki.com/topic/9287-how...x-64bit/page__hl__+arch++linux__fromsearch__1
https://wiki.archlinux.org/index.php/Android
You also must use a java 6 with Jellybean. jdk6 6u34-b04 is in the AUR:
https://aur.archlinux.org/packages.php?ID=51907
You will need to blacklist Perl, make and git from upgrading after you downgrade them. Also if you use a custom kernel, such as ck-linux in AUR you will need to downgrade the kmod as well. If worse comes to worse I could just get my dependicies list for you guys.
rlasalle15 said:
Rootz and the Arch linux android wiki are good sources
http://rootzwiki.com/topic/9287-how...x-64bit/page__hl__+arch++linux__fromsearch__1
https://wiki.archlinux.org/index.php/Android
You will need to blacklist Perl, make and git from upgrading after you downgrade them. Also if you use a custom kernel, such as ck-linux in AUR you will need to downgrade the kmod as well. If worse comes to worse I could just get my dependicies list for you guys.
Click to expand...
Click to collapse
If you want to post it someone could probably use it, I'm using a personalized distro that started life as Ubuntu myself.
rlasalle15 said:
Rootz and the Arch linux android wiki are good sources
http://rootzwiki.com/topic/9287-how...x-64bit/page__hl__+arch++linux__fromsearch__1
https://wiki.archlinux.org/index.php/Android
You also must use a java 6 with Jellybean. jdk6 6u34-b04 is in the AUR:
https://aur.archlinux.org/packages.php?ID=51907
You will need to blacklist Perl, make and git from upgrading after you downgrade them. Also if you use a custom kernel, such as ck-linux in AUR you will need to downgrade the kmod as well. If worse comes to worse I could just get my dependicies list for you guys.
Click to expand...
Click to collapse
You can use openjdk with jellybean.
Sent from my Galaxy Nexus using xda premium
lithid-cm said:
You can use openjdk with jellybean.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Yep I would actually recommend it.
lithid-cm said:
You can use openjdk with jellybean.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
thewadegeek said:
Yep I would actually recommend it.
Click to expand...
Click to collapse
I had issues with it at first..it was just easier to do it this way. The AUR makes it easier.
Hmmmm Comparing this with Ubuntu.. A breakdown/summary:
Arch Linux:
You need to downgrade some packages.
Install Java and Necessary packages.
Then you can build Android.
Ubuntu:
Update packages?
Install Java and Necessary packages.
Then you can build Android.
Is this right??
J
Peteragent5 said:
Hmmmm Comparing this with Ubuntu.. A breakdown/summary:
Arch Linux:
You need to downgrade some packages.
Install Java and Necessary packages.
Then you can build Android.
Ubuntu:
Update packages?
Install Java and Necessary packages.
Then you can build Android.
Is this right??
Click to expand...
Click to collapse
you do not have to downgrade.
the sun-java6 installs to /opt just source it before building.
I should ask for op or just create a new thread at rootz.
I posted a update how-to
http://rootzwiki.com/topic/9287-how...-on-arch-linux-64bit/page__st__60#entry854543
post #62
Personal build:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My System:
OS: Arch Linux x86_64
Kernel: 3.4.6-2-ck
Shell: /bin/bash
RAM: 313 / 12011 (2%)
CPU: Intel(R) Core(TM) i7 CPU 960 @ 3.20GHz
Java7 & 6
[[email protected] ~]
-->$ java -version & android-buildenv & java -version
java version "1.7.0_05-icedtea"
OpenJDK Runtime Environment (IcedTea7 2.2.1) (ArchLinux build 7.u5_2.2.1-1-x86_64)
OpenJDK 64-Bit Server VM (build 23.0-b21, mixed mode)
[1] 6045
java version "1.6.0_33"
Java(TM) SE Runtime Environment (build 1.6.0_33-b04)
Java HotSpot(TM) 64-Bit Server VM (build 20.8-b03, mixed mode)
git
-->$ git --version
git version 1.7.11.3
perl
-->$ perl -v
This is perl 5, version 16, subversion 0 (v5.16.0) built for x86_64-linux-thread-multi
make
-->$ make -v
GNU Make 3.82
Built for x86_64-unknown-linux-gnu
just a matter of prep'n before builds.
android_bashrc
Code:
# Android tools
PATH="/opt/android-sdk/tools:/opt/android-sdk/platform-tools:$PATH"
export PATH=${PATH}:/opt/android-sdk/tools
export PATH=${PATH}:/opt/android-sdk/platform-tools
export PATH="$HOME/android/jb_source/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/:$PATH"
export ARCH=arm
export SUBARCH=arm
export CROSS_COMPILE=arm-eabi-
# Java6
export J2SDKDIR=/opt/sun-java6
export J2REDIR=/opt/sun-java6/jre
export JAVA_HOME=/opt/sun-java6
export DERBY_HOME=/opt/sun-java6/db
export PATH=/opt/sun-java6/bin:/opt/sun-java6/jre/bin:/opt/sun-java6/db/bin:$PATH
# CCACHE
export USE_CCACHE=1
export CCACHE_DIR=$HOME/android/.ccache
# PS
export PROMPT_COMMAND="date +'( %A, %b %d %R:%S )'"
#export PS1=" ${TQ}\u${R}@${TQ}\h (\W$(__git_ps1 " (%s)") ${LG}-->${P}\$${W} "
export PS1=' \[email protected]\h [\W$(__git_ps1 " (%s)")] \n -->\$ '
#PATH="/opt/android-sdk/tools:/opt/android-sdk/platform-tools:$PATH"
# Alias file
if [ -f $HOME/.prep_files/android_aliases ]; then
$HOME/.prep_files/android_aliases
fi
alias screenabuild="screen -c $HOME/android/.prep_files/.screenrc_android"
P.S. I use linux-ck kernel never had an issue.
-->$ kmod --version
kmod version 9
well I hardly hang here and just happen to see this thread and read thru.
hopefully this post provided something helpful.
Have cookie filled day!
CyanogenMod 11 for the LG G2 mini D620r
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
All Credits so far go to Quarx and his project CM11 for LG L90
What i have done so far:
Setup Ubuntu on my Laptop
Installed CM dev environment like described here!
Made a new device folder following THIS guide and build some recoveries.
Took the sources from CM11 for LG L90 and integrated them to my build environment.
CM11 for LG L90 builds fine but i can not test it.
Took the files i thought we need from L90 and put them to my d620 tree.
Trial and error till it compiled for d620.
For the kernel i use original LG sources extracted to kernel/lge/msm8226.
Switched to kernel source from Quarx and tweaked it for d620.
Find sources i use here.
Unfortunately the kernel i have build leads to boot loops. (Yes i have wiped everything)
If i only install the system with the original LG stock kernel i get an security error.
How can i find out why the kernel boot loops?
(had to use the dt.img from stock kernel because mine didn't work, phone gets stuck in fastboot)
Kernel now boots with recovery.
Touch only works if i copy the FW to system folder.
CM11 now works quit well.
Known issues:
- NFC not working at all
- Vibration not working at all
- Back/Main camara has overexposure on bright scenes
- LTE can only be activated by adding quick setting for LTE
Testers welcome.
Video review from simo14
Alpha: Download
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any help appreciated.
Port rom!!
Good job! I think You can port rom l90 for g2 mini. Read it: http://forum.xda-developers.com/showthread.php?t=2545618 (my English is bad, sorry!!)
I think we need a "extract-files.sh" to extract device proprietary files with connected and enabled usb debbuging. I do some research but didnt luck. My English is weak and i don't know how to do this script. I know its necesary for boot and compile with success.
Maybe Quarx can help us.
Probably kernel boot loops because you compile with CM source and that its not compatible with stock rom.
Regards.
this is great progress
im trying like hell to make a custom recovery.
take a look at this zaaap
http://forum.xda-developers.com/android/help/building-kernel-error-lg-g2-mini-t2853390
maybe you could help me out a bit?
I'm extracted a system folder from TWRP backup and try to port by paste>copy method. I need a META-INF folder for our phone. I don't know how to make it.
Ok i found it.
I make four builds with AndroidKitchen but its always a update-binary script error.
Any help?
make -j4 otatools give me that error.
/media/radek/bee9f4ae-71a6-4ed8-9153-7dd674ea803d/CM11/out/target/product/generic/obj/APPS/SignatureTest_intermediates
"ebtables is disabled on this build"
find: `src': Nie ma takiego pliku ani katalogu
grep: /build/target/board/generic/recovery.fstab: Nie ma takiego pliku ani katalogu
No private recovery resources for TARGET_DEVICE generic
build/core/tasks/kernel.mk:91: **********************************************************
build/core/tasks/kernel.mk:92: * Kernel source found, but no configuration was defined *
build/core/tasks/kernel.mk:93: * Please add the TARGET_KERNEL_CONFIG variable to your *
build/core/tasks/kernel.mk:94: * BoardConfig.mk file *
build/core/tasks/kernel.mk:95: **********************************************************
make: Nie ma nic do zrobienia w `otatools'.
/build/target/board/generic/recovery.fstab exists in the directory.
When try to compile kernel:
*** Can't find default configuration "arch/arm/configs/w7ds_open_cis_defconfig"!
***
make[2]: *** [w7ds_open_cis_defconfig] Błąd 1
make[1]: *** [w7ds_open_cis_defconfig] Błąd 2
make: *** [w7ds_open_cis_defconfig] Błąd 2
That's mean the Quarx kernel should work for us?
partyzant_x said:
When try to compile kernel:
*** Can't find default configuration "arch/arm/configs/w7ds_open_cis_defconfig"!
***
make[2]: *** [w7ds_open_cis_defconfig] Błąd 1
make[1]: *** [w7ds_open_cis_defconfig] Błąd 2
make: *** [w7ds_open_cis_defconfig] Błąd 2
That's mean the Quarx kernel should work for us?
Click to expand...
Click to collapse
w7ds is an LG L90 dual sim.
Go to your kernel folder /arch/arm/configs and look for a g2m... ...defconfig where the name fits your device.
Try to compile with the g2m defconfig should work.
You might be missing touch and other hardware if you didn't get all property blobs needed for our device.
This is the point where I got struck at the moment.
/tmp/ccfkEagn.s: Assembler messages:
/tmp/ccfkEagn.s:166: Warning: swp{b} use is deprecated for this architecture
/tmp/ccfkEagn.s:192: Warning: swp{b} use is deprecated for this architecture
CC arch/arm/mach-msm/smd_private.o
CC arch/arm/mach-msm/smem.o
CC arch/arm/mach-msm/smd_init_dt.o
arch/arm/mach-msm/smd_init_dt.c:24:25: fatal error: smd_private.h: No such file or directory
compilation terminated.
make[2]: *** [arch/arm/mach-msm/smd_init_dt.o] Błąd 1
make[1]: *** [arch/arm/mach-msm] Błąd 2
make: *** [zImage] Błąd 2
Click to expand...
Click to collapse
I'm try to compile the LG source with:
Run following scripts to build kernel
a) cd kernel
c) make ARCH=arm CROSS_COMPILE=../prebuilts/gcc/linux-x86/arm/arm-eabi-4.7/bin/arm-eabi- g2m_global_com_defconfig zImage
Zaaap can you share your device tree?
Ok. I fixed the errors. Now I have "zImage" how flash that?
What did you do to fix the errors? And wich toolchain did you use?
The zimage comes with some .ko files? You have to make a .zip file of those and flash it through custom recovery or a flash app from market! Like rashr
I fixed the errors that occurred when compiling. Compile the source cm and lg according to instructions in the readme.txt from lg. Thanks Zaaap changed command from w7ds_open_cis_defconfig on g2m_global_com_defconfig. After compiling I received two files zImage and Image.
partyzant_x said:
I fixed the errors that occurred when compiling. Compile the source cm and lg according to instructions in the readme.txt from lg. Thanks Zaaap changed command from w7ds_open_cis_defconfig on g2m_global_com_defconfig. After compiling I received two files zImage and Image.
Click to expand...
Click to collapse
Don't flash the zImage as it is only a part of the needed boot.img.
There is a command like 'make boot.img'. I'll have to look for it.
I'll explain more later when I get to my laptop.
partyzant_x said:
I fixed the errors that occurred when compiling. Compile the source cm and lg according to instructions in the readme.txt from lg. Thanks Zaaap changed command from w7ds_open_cis_defconfig on g2m_global_com_defconfig. After compiling I received two files zImage and Image.
Click to expand...
Click to collapse
look at the last stages of this how to.
http://playfuldroidz.com/wiki/Compiling_a_Kernel#Making_a_Flashable_Zip
Now I'm trying to create a device tree manually. A bit of getting lost in this. Zaaap can share with your device tree. Rather than create new ones we can work on one and make any fixes.
partyzant_x said:
I fixed the errors that occurred when compiling. Compile the source cm and lg according to instructions in the readme.txt from lg. Thanks Zaaap changed command from w7ds_open_cis_defconfig on g2m_global_com_defconfig. After compiling I received two files zImage and Image.
Click to expand...
Click to collapse
where did you find the readme.txt where it said wich toolchain you should use?
invaderjohn said:
look at the last stages of this how to.
http://playfuldroidz.com/wiki/Compiling_a_Kernel#Making_a_Flashable_Zip
Click to expand...
Click to collapse
Give me: Error executing updater binary in zip.
Downloaded kernel source from lg site. Unpack it and there is two files readme.txt and packed kernel source, unpacked it copy kernel folder to cm source then cd kernel and:
make ARCH=arm CROSS_COMPILE=../prebuilts/gcc/linux-x86/arm/arm-eabi-4.7/bin/arm-eabi- g2m_global_com_defconfig zImage
When I have error for example:
arch/arm/mach-msm/smd_init_dt.c:24:25: fatal error: smd_private.h: No such file or directory
compilation terminated.
make[2]: *** [arch/arm/mach-msm/smd_init_dt.o] Błąd 1
make[1]: *** [arch/arm/mach-msm] Błąd 2
make: *** [zImage] Błąd 2
Click to expand...
Click to collapse
Then open smd_init_dt.c find line with smd_private.sh. Its look include <smd_private.sh> and change it to include "smd_private.sh".
Sorry for my English.
Make boot.img
Here you can find the official doc about making boot.img: HERE
I took the device tree from Quarx found here made a copy in a new folder 'd620' but i think 'g2m' would have been correct for phone.
Find my device folder here.
Find my vendor folder here.
The kernel source is located under kernel/lge/msm8226
I normaly compile a recovery and see if the kernel works with it.
Thus i don't risk a semi brick because if the kernel is bad, then recovery may not start but system will start and i can flash an other recovery with a new kernel.
If recovery boots, i can use adb to get dmesg.log and see what works and what not.
On my last try, touch didn't initialize complete.
Thanks Zaaap.
I broke something in the source of CM. I have to download again. Can someone check zImage which I compiled.
partyzant_x said:
Thanks Zaaap.
I broke something in the source of CM. I have to download again. Can someone check zImage which I compiled.
Click to expand...
Click to collapse
It boot, but takes long to do so and there is no touch.
This is the same problem i have.
We need to get the correct touch firmware + patch.
Find log attached.
Kernel boots with touch
Got touch working.
The firmware doesn't get copied to /system/lib/firmware.
When i copy the firmware in via AIK kernel boots fast and with touch.
Now i will investigate how to include the FW in compile process.
Very good news. I asked for help a member of XDA @ moonbutt74. I hope he will have the time and inclination to help us.
Zaaap72 said:
Got touch working.
The firmware doesn't get copied to /system/lib/firmware.
When i copy the firmware in via AIK kernel boots fast and with touch.
Now i will investigate how to include the FW in compile process.
Click to expand...
Click to collapse
partyzant_x said:
Very good news. I asked for help a member of XDA @ moonbutt74. I hope he will have the time and inclination to help us.
Click to expand...
Click to collapse
okay so root is good
look in /proc for
/proc/config.gz
it might be there it might not. i need the stock boot.img please. looking through source right now and unsure of which defconfig.
your modules also depend on libraries in system/vendor - you need that entire directory for your device tree. you may also need
manufacturer/device specific/proprietary libraries from system/lib
starting in /system/vendor type in terminal
strings [nameoflib].so | grep "\.so"
these will bring up a list of additional libraires needed. the ones you already have in vendor don't worry about. the ones you
will find in system/lib are the additional ones you need to get for your device tree. go to the thread i'm working in with restl3ss and read through the whole thing but please do not post any questions there. post here use the mention function @moonbutt74
or pm me or click reply button below any of my posts in this thread and i will know by email.
m
on defconfig readme suggests w7ds_open_cis_defconfig but will try g2m_global_com_defconfig
I have been trying to compile the remix OS kernel, downloaded from their github repo
Code:
CHECK usr/include/linux/wimax/ (1 files)
CHECK usr/include/linux/ (411 files)
./usr/include/linux/if_pppox.h:26: included file 'linux/if_pppolac.h' is not exported
./usr/include/linux/if_pppox.h:27: included file 'linux/if_pppopns.h' is not exported
scripts/Makefile.headersinst:120: recipe for target 'usr/include/linux/.check' failed
make[4]: *** [usr/include/linux/.check] Error 123
scripts/Makefile.headersinst:127: recipe for target 'linux' failed
make[3]: *** [linux] Error 2
Makefile:1080: recipe for target 'headers_check' failed
make[2]: *** [headers_check] Error 2
any ideas?
I'm using the command "make -j 3 deb-pkg" to build.
speculatrix said:
I have been trying to compile the remix OS kernel, downloaded from their github repo
Code:
CHECK usr/include/linux/wimax/ (1 files)
CHECK usr/include/linux/ (411 files)
./usr/include/linux/if_pppox.h:26: included file 'linux/if_pppolac.h' is not exported
./usr/include/linux/if_pppox.h:27: included file 'linux/if_pppopns.h' is not exported
scripts/Makefile.headersinst:120: recipe for target 'usr/include/linux/.check' failed
make[4]: *** [usr/include/linux/.check] Error 123
scripts/Makefile.headersinst:127: recipe for target 'linux' failed
make[3]: *** [linux] Error 2
Makefile:1080: recipe for target 'headers_check' failed
make[2]: *** [headers_check] Error 2
any ideas?
I'm using the command "make -j 3 deb-pkg" to build.
Click to expand...
Click to collapse
No but i will go down to to same road so i can enable my wifi, maybe i find something!
Why are you using make -j 3 deb-pkg, should it not be ¨make arch=x86_64¨ ?
just copy the default config first to somewhere else, like cp arch/x86/android-x86_64_defconfig /work/config/,config
Then make -o /work/config/.config xconfig
make -j4 -o work/config/.config
TerrorToetje said:
No but i will go down to to same road so i can enable my wifi, maybe i find something!
Click to expand...
Click to collapse
Kernel compiled fine here, however I forgot https://github.com/jide-opensource/remixos-kernel/tree/jide_x86_lollipop/android/configs;)
TerrorToetje said:
Why are you using make -j 3 deb-pkg, should it not be ¨make arch=x86_64¨ ?
just copy the default config first to somewhere else, like cp arch/x86/android-x86_64_defconfig /work/config/,config
Then make -o /work/config/.config xconfig
make -j4 -o work/config/.config
Click to expand...
Click to collapse
I must be doing somethign wrong, I did that, using the config file arch/x86/configs/android-x86_64_defconfig
Code:
CC [M] drivers/staging/rtl8723bs/hal/odm_RTL8723B.o
LD [M] drivers/staging/rtl8723bs/r8723bs.o
LD [M] drivers/staging/xgifb/xgifb.o
LD drivers/staging/built-in.o
Makefile:947: recipe for target 'drivers' failed
make: *** [drivers] Error 2
[code]
TerrorToetje said:
No but i will go down to to same road so i can enable my wifi, maybe i find something!
Click to expand...
Click to collapse
Yes, it's because I want to build the wifi myself from this repo:
https://github.com/hadess/rtl8723bs
speculatrix said:
Yes, it's because I want to build the wifi myself from this repo:
https://github.com/hadess/rtl8723bs
Click to expand...
Click to collapse
They write;
For older kernel than 4.3, you might also need this patch applied: https://git.kernel.org/cgit/linux/k.../?id=d31911b9374a76560d2c8ea4aa6ce5781621e81d
Maybe this ?,
My module rtl8188EU was already in the /stage i just enabled it.
TerrorToetje said:
They write;
For older kernel than 4.3, you might also need this patch applied: https://git.kernel.org/cgit/linux/k.../?id=d31911b9374a76560d2c8ea4aa6ce5781621e81d
Maybe this ?,
My module rtl8188EU was already in the /stage i just enabled it.
Click to expand...
Click to collapse
I thought I would start by trying to build the kernel exactly as published, and then start patching it. thanks for the suggestion.
TerrorToetje said:
Why are you using make -j 3 deb-pkg, should it not be ¨make arch=x86_64¨ ?
Click to expand...
Click to collapse
p.s. I build the kernel as a debian package on my debian dev box, which is a VM on qemu/kvm, and then boot the kernel on that dev box to check it works.
https://groups.google.com/forum/m/#!topic/Remix-OS-for-PC/dv3XYXCSYvU
speculatrix said:
https://groups.google.com/forum/m/#!topic/Remix-OS-for-PC/dv3XYXCSYvU
Click to expand...
Click to collapse
Funny thats my topic
TerrorToetje said:
Funny thats my topic
Click to expand...
Click to collapse
I've managed to build a kernel. It doesn't boot on my VM, but I will now "dismantle" the RemixOS usb image, and try copying in the extra kernel modules from my build.
I also need to load in a terminal app and root the remixos image so's I can do useful things when its booted.
Let me know how you got the modules, i'm to be hon-nest i have no clue how to get those modules. How did you found out how they build-ed the USB kernel?
I wan't to have the exact same kernel options as there USB image... and then start to change some things
TerrorToetje said:
Let me know how you got the modules, i'm to be hon-nest i have no clue how to get those modules. How did you found out how they build-ed the USB kernel?
I wan't to have the exact same kernel options as there USB image... and then start to change some things
Click to expand...
Click to collapse
so when I got it to build, I did "make modules_install" and then looked in /lib/modules and found it.
meanwhile, I unzipped RemixOS usb stick image (EFI) and mounted the nested file systems like this
Code:
unzip release_Remix_OS_for_PC_64_B2016020201_Alpha_EFI.zip Remix_OS_for_PC_64_B2016020201_Alpha_EFI.img
mount -o loop,offset=1048576 Remix_OS_for_PC_64_B2016020201_Alpha_EFI.img /mnt/remix
cd /mnt/remix
mkdir /mnt/remix-sfs
mount -o loop system.sfs /mnt/remix-sfs
cd /mnt/remix-sfs
mkdir /mnt/remix-sfs-system
mount -o loop system.img /mnt/remix-sfs-system
speculatrix said:
so when I got it to build, I did "make modules_install" and then looked in /lib/modules and found it.
meanwhile, I unzipped RemixOS usb stick image (EFI) and mounted the nested file systems like this
Code:
unzip release_Remix_OS_for_PC_64_B2016020201_Alpha_EFI.zip Remix_OS_for_PC_64_B2016020201_Alpha_EFI.img
mount -o loop,offset=1048576 Remix_OS_for_PC_64_B2016020201_Alpha_EFI.img /mnt/remix
cd /mnt/remix
mkdir /mnt/remix-sfs
mount -o loop system.sfs /mnt/remix-sfs
cd /mnt/remix-sfs
mkdir /mnt/remix-sfs-system
mount -o loop system.img /mnt/remix-sfs-system
Click to expand...
Click to collapse
Okay i managed the same, but also not booting. at least i can see that here is full gui support now, but again i only get a shell.
speculatrix said:
so when I got it to build, I did "make modules_install" and then looked in /lib/modules and found it.
meanwhile, I unzipped RemixOS usb stick image (EFI) and mounted the nested file systems like this
Code:
unzip release_Remix_OS_for_PC_64_B2016020201_Alpha_EFI.zip Remix_OS_for_PC_64_B2016020201_Alpha_EFI.img
mount -o loop,offset=1048576 Remix_OS_for_PC_64_B2016020201_Alpha_EFI.img /mnt/remix
cd /mnt/remix
mkdir /mnt/remix-sfs
mount -o loop system.sfs /mnt/remix-sfs
cd /mnt/remix-sfs
mkdir /mnt/remix-sfs-system
mount -o loop system.img /mnt/remix-sfs-system
Click to expand...
Click to collapse
Do you know if there is any way to capture the current kernel config from the running android machine?, i tried to see if there was a config in /proc but no..
The thing is to nail this down you can do two things, either dmesg and see whats going wrong or capture a working config and build on top of that one.
TerrorToetje said:
Do you know if there is any way to capture the current kernel config from the running android machine?, i tried to see if there was a config in /proc but no..
The thing is to nail this down you can do two things, either dmesg and see whats going wrong or capture a working config and build on top of that one.
Click to expand...
Click to collapse
Like you, I tried the same... there's nothing in /boot, and the kernel doesn't provide a /proc/config.gz
I tried the "contact us" on the jide website to ask about building the kernel and didn't get a response. I've not seen any jide people respond to discussions on google groups.
It does seem Jide want to act in good faith:
http://liliputing.com/2016/01/jide-releases-remix-os-source-code-to-comply-with-gpl-apache.html
speculatrix said:
Like you, I tried the same... there's nothing in /boot, and the kernel doesn't provide a /proc/config.gz
I tried the "contact us" on the jide website to ask about building the kernel and didn't get a response. I've not seen any jide people respond to discussions on google groups.
It does seem Jide want to act in good faith:
http://liliputing.com/2016/01/jide-releases-remix-os-source-code-to-comply-with-gpl-apache.html
Click to expand...
Click to collapse
Maybe i should write them aswell, would be nice if they enabled the .config option in there Alpha releases
speculatrix said:
Like you, I tried the same... there's nothing in /boot, and the kernel doesn't provide a /proc/config.gz
I tried the "contact us" on the jide website to ask about building the kernel and didn't get a response. I've not seen any jide people respond to discussions on google groups.
It does seem Jide want to act in good faith:
http://liliputing.com/2016/01/jide-releases-remix-os-source-code-to-comply-with-gpl-apache.html
Click to expand...
Click to collapse
Okay, I sended a support ticket aswell did you make any progression in the meantime?
I manged to compile the kernel and make it work!, if you need more details let me know
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}