DISCLAIMER: DO NOT FLASH UNLESS YOU KNOW HOW TO UNDO!
Special THANKS TO:
XDA [nuff said]
adrynalyne [for all his dev on the continuum and fascinate (OC Porting)
imnuts [for all his dev work involving our device + private kernel lessons]
trailblazer101 [for all his mods that make this device worth keeping around ]
txwolf1980 [for all the help and conversations provided ]
(will update tonight after work.)
So yeah this one finally boots stock EC09 ROMS.
I just booted and wanted to share asap. [I have not ddms or logcat yet since this is the first boot]
What it does NOT do yet (That I know So Far):
Not officially rooted
No network
end list
You can see that it has been compiled on my laptop by going into terminal emulator or adb shell
$ su (if not rooted in terminal emu)
#cat /proc/version
it will out put the version and what machine it was compiled on. ([email protected])
root= I had to log in as root on my VM ubuntu
ubuntu=the VM name
so yeah hopefully i can remember what i did at 3am to reproduce another with further modifications.
{
"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"
}
so now that it boots it can be patched
To UN-KERNEL
So you seen the kernel boot, now what?
Flash in CWM:
Stock EC09 Kernel: Here
I believe it to be fully stock, unrooted? It was packed in ODIN.tar from txwolf1980's D) thread HERE.
or
Imnuts' EC07 Repacked Customized Kernels: Here
I am unaware of a rooted unsecure EC09 Kernel around, a one would pull there current ROOTED EC09 KERNEL from their current rom, we could have that available.
TO HELP DEBUG:
taken from: http://code.google.com/p/tegraowners-ics-rom/wiki/How_to_get_logs
Code:
How to get logcat
The Android logging system provides a mechanism for collecting and viewing system debug output. Logs from various applications and portions of the system are collected in a series of circular buffers, which then can be viewed and filtered by the logcat command. You can use logcat from an ADB shell to view the log messages.
To get logcat on your device you need to do:
Open terminal app
Enter "su" to get root privileges
Enter "logcat -f /sdcard/logcat.txt". This will start logcat output to file /sdcard/logcat.txt
Stop logcat by "ctrl+c" or just close terminal emulator app
If you use some logcat reader app(for example CatLog), then it should have "save log" option.
To save logcat with adb shell you need to run "adb logcat > /path/where/save/logcat.txt" from command line on your pc.
How to get kernel log
Kernel log shows what happens with kernel since tablet power on.
To get kernel log on your device you need to do:
Open terminal app
Enter "su" to get root privileges
Enter "dmesg > /sdcard/dmesg.txt" to save current log. Or run "cat /proc/kmsg > /sdcard/kmsg.txt" to start kernel log output to file.
If you are using "cat /proc/kmsg" you need to stop it by "ctrl+c" or close terminal app.
To save kernel log with adb shell you need to run "adb shell dmesg > /path/where/save/dmesg.txt" from command line on your pc.
How to get last_kmsg log
If your tablet rebooted unexpectedly, you need to save last_kmsg log. It will contain kernel log just before reboot and may show what caused reboot.
To get last_kmsg log on your device you need to do:
Open terminal app
Enter "su" to get root privileges
Enter "cat /proc/last_kmsg > /sdcard/last_kmsg.txt" to save current log.
Close terminal app.
To save last_kmsg log with adb shell you need to run "adb shell cat /proc/last_kmsg > /path/where/save/last_kmsg.txt" from command line on your pc.
HOW TO POST THEM IN THREAD:
Please either CnP SNIPPETS in post WITH *.txt attached or link to
or
link to pastebin
PLEASE DO NOT CnP txt file in post, it makes thread drag out and its easier to FIND lines in a txt file than viewing the thread.
thank you!
Change log:
10.4.12
+ Debugging Instrustions
10.01.12
+ change log
updated un-kernel instructions
+ Debugging Instructions
09.30.12
+ Alpha released
So what does this kernel fo and how do you go about flashing it?
Sent from my SCH-I400 using xda app-developers app
Jaggar345 said:
So what does this kernel fo and how do you go about flashing it?
Sent from my SCH-I400 using xda app-developers app
Click to expand...
Click to collapse
oh yea. ..
This kernel so far does everything stock except network lol.
Wifi works
Right now its just proof it can be compiled from sources.
Big accomplishment in my opinion
Also if anyone can beta ect...
And a simple cwm flash installs it
I will odin and all in future release.
Sent from my SPH-M580BST using Tapatalk 2
Good job man! And just when you were about to give up
trailblazer101 said:
Good job man! And just when you were about to give up
Click to expand...
Click to collapse
It must have been my setup cause I had to reformat laptop and just started over.
I've been catching on... last night spent until 530am porting i500 OC! (Didn't boot lol, it was for gb ed01 ) but I gotta take a break and get back to school work this week.
You know any c?
Sent from my SPH-M580BST using Tapatalk 2
I am taking Computer Science right now in college, and we are learning the basics of C++ So, that isn't helping me with the Continuum in any way right now, haha.. And I have no real background with building kernels/builds from source, however I do have a knack for following directions, and for debugging...
Continuum
As my Continuum is just an MP3 player and Angry Birds machine I will flash anything.
hey logan, its been awhile, my kernel and theme work might will be limited this quarter with my class schedule and life... so any help debugging would be appreciated.
for any one whose continuum is there extra device i would love it if you helped also. this help would include more or less googling the warnings, errors, or suspensions in the kernel boot up.
Now i see where i forced an extra netfiller module in the config and hoping that will solve network failure, but again it was outta pure luck that one compiled and booted, i didnt log my build or make notes on what i included in config. so i wont be starting completely over.
i have since though changed a round 2000 lines of code to port fascinates OC ability to 1.7ghz and it looks to have booted yet there is more to be edited to actually be able to OC. Also half way through i seen i was porting there GB code, so our 2.6.32 kernel maybe cant see it? I already pulled adrynanalyns froyo kernel source for the 1.4ghz overclock but have not jumped into since the lake port took about 5 hours.
Im just torn between perfecting froyo or tackling GB+.
the dev ive been in talks with about patching the kernel up says that i can try to compile a kernel from I500 GB sources that boots or work out the warnings in my froyo kernel and update the the linux sources to boot GB+.
"ANDHOW!?" - Buckwheat (little rascals)
ps.
Spoiler
Code:
anyone point me in the direction of the forum tags when posting? ie spoiler button and scrollable textbox. please no links to the noob video lol.
still looking for button
thanks.
http://www.tauniverse.com/forum/misc.php?do=bbcode
Holy crap! Amazing job dude! I'm definitely willing to go back to stock to beta this kernel. I personally don't care about mobile data anyway. Can calls still be made or is it a complete no network? As far as Froyo/GB it may be beneficial to perfect the Froyo kernel if all thats needed later is to merge the GB source. I too am a Computer Science student though we havent touched programming yet and all I really have to look forward to is an Introduction to Java course next semester. Let me know if I can help, I, like TB, am great at following directions and I have 2 very capable computers at your disposal.
-Justin
As of right now its network is unavailable. I haven't tried reflashing modems (may need to start with dl17 and patch up. I haven't been back on comiling a dif config yet. Just been getting lost in c land comparing sources for hopefully mods/ports.
Sent from my SPH-M580BST using Tapatalk 2
Ok so, I flashed your kernel and let it run for about an hour with a couple problems. Unfortunately I didn't grab the logcat at the time sorry..
1. Voodoo sound crashed at start up but loaded fine after that. On a second reboot Voodoo started just fine.
2. Cannot update SU
3. WiFi works fine but no network (as already stated)
4. Battery level dropped from approx 70% to 15% immediately after flashing.
5. Nandroid backup didnt work.
I tried flashing the EC03 radio only over the kernel with no joy. Still no network. If you have the EC09 radio/modem I'd be happy to give it a try.
Otherwise everything else seemed to work with no problems. I did see a VERY brief screen flash during reboot but couldn't reproduce it.
Hope this helps, sorry about no logcat.
-Justin
Awesome thanks ill look into those. Yeah I have all the modems. Ill post em later today. I'm home sick as hell so I didn't even go to classes.
My biggest problem is reproducing a clean build with a working config lol (not really lol)
Battery level will return. I had this kernel on for a couple days before reverting back.
I believe I forced the build for all the platforms.
This kernel is just a stepping stone to port i500 roms AND kernels.
Thanks to the dozen of continuumers out there!
Sent from my SPH-M580BST using Tapatalk 2
Actually Added DEBUG instructions for logcat and kernel msgs
What is your plan for the ticker if you intend to use i500 roms and kernels?
jaizero said:
What is your plan for the ticker if you intend to use i500 roms and kernels?
Click to expand...
Click to collapse
my plan right now is to try and build the atlas (i500) display modules with our screen dimensions MINUS the ticker, this is the only way i see to gb+ kernel and roms from i500.
also i will try and build the garnett (i400) video drivers taking out the ticker to see if the drivers are device dependent and plus there are sooo many lines of C that are confusing but im picking through it
I ALSO have to try and figure what i did right to compile a bootable kernel again, SUPER . I dont see me reverting back to build a froyo unless i see no way possible to build i500 sources with our device drivers
Well, forward is a good direction. Let me know if you need anything, like I said I have 2 very capable computers if you need compilers.
-Justin
peep this...
Code:
WARNING: modpost: Found 11 section mismatch(es).
To see full details build your kernel with:
'make CONFIG_DEBUG_SECTION_MISMATCH=y'
GEN .version
CHK include/generated/compile.h
UPD include/generated/compile.h
CC init/version.o
LD init/built-in.o
LD .tmp_vmlinux1
KSYM .tmp_kallsyms1.S
AS .tmp_kallsyms1.o
LD .tmp_vmlinux2
KSYM .tmp_kallsyms2.S
AS .tmp_kallsyms2.o
LD vmlinux
SYSMAP System.map
SYSMAP .tmp_System.map
OBJCOPY arch/arm/boot/Image
Kernel: arch/arm/boot/Image is ready
AS arch/arm/boot/compressed/head.o
GZIP arch/arm/boot/compressed/piggy.gzip
AS arch/arm/boot/compressed/piggy.gzip.o
CC arch/arm/boot/compressed/misc.o
In file included from arch/arm/plat-samsung/include/plat/uncompress.h:30,
from arch/arm/mach-s5pv210/include/mach/uncompress.h:17,
from arch/arm/boot/compressed/misc.c:38:
arch/arm/plat-samsung/include/plat/regs-serial.h:281: warning: 'struct uart_port' declared inside parameter list
arch/arm/plat-samsung/include/plat/regs-serial.h:281: warning: its scope is only this definition or declaration, which is probably not what you want
CC arch/arm/boot/compressed/decompress.o
SHIPPED arch/arm/boot/compressed/lib1funcs.S
AS arch/arm/boot/compressed/lib1funcs.o
LD arch/arm/boot/compressed/vmlinux
OBJCOPY arch/arm/boot/zImage
[B] Kernel: arch/arm/boot/zImage is ready[/B]
Building modules, stage 2.
MODPOST 8 modules
CHK include/linux/version.h
CHK include/generated/utsrelease.h
make[1]: `include/generated/mach-types.h' is up to date.
CALL scripts/checksyscalls.sh
Building modules, stage 2.
MODPOST 8 modules
crypto/ansi_cprng.ko
drivers/misc/vibetonz/vibrator.ko
drivers/misc/param/param.ko
drivers/scsi/scsi_wait_scan.ko
drivers/net/wireless/bcm4329/dhd.ko
drivers/onedram/dpram/dpram_atlas.ko
drivers/onedram/dpram_recovery/dpram_recovery.ko
net/sched/cls_flow.ko
CHK include/linux/version.h
CHK include/generated/utsrelease.h
make[1]: `include/generated/mach-types.h' is up to date.
CALL scripts/checksyscalls.sh
CHK include/generated/compile.h
GEN usr/initramfs_data.cpio
AS usr/initramfs_data.o
LD usr/built-in.o
LD vmlinux.o
MODPOST vmlinux.o
WARNING: modpost: Found 11 section mismatch(es).
To see full details build your kernel with:
'make CONFIG_DEBUG_SECTION_MISMATCH=y'
GEN .version
CHK include/generated/compile.h
UPD include/generated/compile.h
CC init/version.o
LD init/built-in.o
LD .tmp_vmlinux1
KSYM .tmp_kallsyms1.S
AS .tmp_kallsyms1.o
LD .tmp_vmlinux2
KSYM .tmp_kallsyms2.S
AS .tmp_kallsyms2.o
LD vmlinux
SYSMAP System.map
SYSMAP .tmp_System.map
OBJCOPY arch/arm/boot/Image
[B]Kernel: arch/arm/boot/Image is ready[/B]
GZIP arch/arm/boot/compressed/piggy.gzip
AS arch/arm/boot/compressed/piggy.gzip.o
SHIPPED arch/arm/boot/compressed/lib1funcs.S
AS arch/arm/boot/compressed/lib1funcs.o
LD arch/arm/boot/compressed/vmlinux
OBJCOPY arch/arm/boot/zImage
Kernel: arch/arm/boot/zImage is ready
Building modules, stage 2.
MODPOST 8 modules
---------------------------------------------------------------
BUILD OUTPUT
---------------------------------------------------------------
[B]9da434e08855259ceea4fbaf4c33f89d zImage
9da434e08855259ceea4fbaf4c33f89d recovery.bin
19ee4edb285ef88839412448a2a2de78 sch-i500-kernel.zip
36671bc7d1dd751e3f70257b1c3f7a57 sch-i500-recovery.zip
3569651ce124ed2b5d18074db5a69ed1 sch-i500-kernel.tar.md5
22a1d2760cb5473a37f729f9f68615a8 sch-i500-recovery.tar.md5[/B]
[email protected]:/home/ciscogee/Downloads/[B]dmriley-sch-i500-gingerbread[/B]-15f22ec#
so the build.sh that was provided in sources would of build GB platform but i only have froyo sources atm.
i will need to repo them but that takes hours lol.
now does anyone have any ideas on how to flash a GB rom from fascinate on the continuum, i got a recovery that was built with kernel and an update zip, i replaced binaries to flash in cwm, i did flash kernel but of course it will not boot cause i dont have rom, i am curently downloading EH03 full package tar to repack with the new kernel, but i wont be able to do that till fiance is done with that laptop . im scared to flash the recovery since in not sure if a dif update.zip is needed, or if it is needed at all.
i think im fawkked!
so i flashed in cwm gb kernel, no boot.
BUT
it did change device name in adb to some random one.
and i couldnt logcat cause busybox is built in platform so yeah (repoing now)
then while i was waiting i downloaded a odin tar of EH03 (i500 GB Full ota) and tar balled it back up with my zImage. (but forgot to delete recovery)
NOW
i can only get DOWNLOAD MODE,
pwr doesnt seem to do anything unless vol- is held for DL mode.
any suggestions?
Related
Kernel sources are out as you can see here
Download them here
XDA Mirror here
play time
Another mirror here.
Add it as an alternative if you wish.
finally !!!
Error when Im compiling it:
[email protected]:~/mydroid/kernel_hero$ make PATH=$PATH:/home/behnam/mydroid/hero_kernel/prebuilt/linux-x86/toolchain/arm-eabi-4.2.1/bin ARCH=arm SUBARCH=arm CROSS_COMPILE=arm-eabi-
make: arm-eabi-gcc: Command not found
CHK include/linux/version.h
make[1]: "include/asm-arm/mach-types.h" is fresh.
CHK include/linux/utsrelease.h
CC arch/arm/kernel/asm-offsets.s
/bin/sh: arm-eabi-gcc: not found
make[1]: *** [arch/arm/kernel/asm-offsets.s] Error 127
make: *** [prepare0] Error 2
[email protected]:~/mydroid/kernel_hero$
Why?
so, when are they uploading the Tattoo Kernel......LMFAO!!
nice though, should see the birth of some seriously customised ROMs now, as well as possible updates to Bluex/Androbex and the like...
behnaam said:
Error when Im compiling it:
[email protected]:~/mydroid/kernel_hero$ make PATH=$PATH:/home/behnam/mydroid/hero_kernel/prebuilt/linux-x86/toolchain/arm-eabi-4.2.1/bin ARCH=arm SUBARCH=arm CROSS_COMPILE=arm-eabi-
make: arm-eabi-gcc: Command not found
CHK include/linux/version.h
make[1]: "include/asm-arm/mach-types.h" is fresh.
CHK include/linux/utsrelease.h
CC arch/arm/kernel/asm-offsets.s
/bin/sh: arm-eabi-gcc: not found
make[1]: *** [arch/arm/kernel/asm-offsets.s] Error 127
make: *** [prepare0] Error 2
[email protected]:~/mydroid/kernel_hero$
Why?
Click to expand...
Click to collapse
You need a toolchain, maybe the first post of this thread is of some info?: http://forum.xda-developers.com/showthread.php?t=431329
Install Dev Environment:
apt-get install linux-headers-$(uname -r) gcc make kernel-package libncurses5-dev fakeroot wget bzip2 git-svn curl
Download Cross Compiler
http://www.codesourcery.com/sgpp/lit...tal/release642
Select: GNU/Linux (and then Advanced Packages / IA32 GNU/Linux TAR)
Download and Unpack Cross Compiler
(http://www.codesourcery.com/sgpp/lit...ux-gnu.tar.bz2)
# wget http://www.codesourcery.com/sgpp/lit...ux-gnu.tar.bz2
# cd /usr/local ; tar -xjvf /tmp/arm-2008q3-72-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2
Download Kernel (Thans to Oliver Ford!)
# git clone http://www.oliford.co.uk/hpipaq214/ipaq214.git v4
Change in Makefile:
# vi /ANDROID/v4/Makefile
Code:
ARCH ?= arm
CROSS_COMPILE ?= /usr/local/xscale/arm-2008q3/bin/arm-none-linux-gnueabi-
us1111 said:
You need a toolchain, maybe the first post of this thread is of some info?: http://forum.xda-developers.com/showthread.php?t=431329
Install Dev Environment:
apt-get install linux-headers-$(uname -r) gcc make kernel-package libncurses5-dev fakeroot wget bzip2 git-svn curl
Download Cross Compiler
http://www.codesourcery.com/sgpp/lit...tal/release642
Select: GNU/Linux (and then Advanced Packages / IA32 GNU/Linux TAR)
Download and Unpack Cross Compiler
(http://www.codesourcery.com/sgpp/lit...ux-gnu.tar.bz2)
# wget http://www.codesourcery.com/sgpp/lit...ux-gnu.tar.bz2
# cd /usr/local ; tar -xjvf /tmp/arm-2008q3-72-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2
Download Kernel (Thans to Oliver Ford!)
# git clone http://www.oliford.co.uk/hpipaq214/ipaq214.git v4
Change in Makefile:
# vi /ANDROID/v4/Makefile
Code:
ARCH ?= arm
CROSS_COMPILE ?= /usr/local/xscale/arm-2008q3/bin/arm-none-linux-gnueabi-
Click to expand...
Click to collapse
Allready have toolchain, cloned from prebuild.git, I've set path and all but no result..
i think Lox have complied it successfully, maybe ask him...?
{
"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"
}
marazi said:
i think Lox have complied it successfully, maybe ask him...?
Click to expand...
Click to collapse
He doesn't answer on gtalk
It's not finding GCC, is the path definitely right?
Try this:
Code:
make ARCH=arm CROSS_COMPILE=/home/behnam/mydroid/hero_kernel/prebuilt/linux-x86/toolchain/arm-eabi-4.2.1/bin/arm-eabi-
P
modaco said:
It's not finding GCC, is the path definitely right?
Try this:
Code:
make ARCH=arm CROSS_COMPILE=/home/behnam/mydroid/hero_kernel/prebuilt/linux-x86/toolchain/arm-eabi-4.2.1/bin/arm-eabi-
P
Click to expand...
Click to collapse
Yeah, double checked the path, get the same error as above with your help :/ going to unpack the kernel source again and begin from start...
EDIT:
Works now!
Kernel version
Hey guys, I'm pretty new to this game, but since there is now a kernel for my mobile telephone I want to join!
It seems the branched after this commit: (http://android.git.kernel.org/?p=kernel/common.git;a=shortlog;h=refs/heads/android-2.6.27).
But they didn't included all the drivers for example this one isn't there: (http://android.git.kernel.org/?p=ke...it;h=83ab86ab33445f0975142382da2f7455001d5445).
So it is also possible they backported some features.
If I have time I'll diff the kernel sources. I'm curious how much they changed, I already saw some code they added to reset the touchscreen, etc.
So how would one go about porting their changes to the donut kernel?
It would be super useful is someone could take the shipping 1.6 kernel source and apply the HTC changes if that's feasible.
Anyone fancy it? It'd give me and other devs a good 2.6.29 kernel source to use with either cupcake or donut builds...
P
If you have HTC kernel sources and Android 1.6 sources it is possible to build a vanilla Android 1.6 for the Hero. Do I have understand right?
As I knew, I need the Hero Kernel to support Arabic (RTL language) in Hero, could you please give my hints to edit and compile this kernel to support Arabic at least in Browser and SMS?
Regards
YEAH FINALLY!
Compiled using:
$ make ARCH=arm CROSS_COMPILE=arm-linux-
You'd have to have a arm crosscompile toolchain (like the one provided with the android source) in your path.
Edit: And YES it boots! Woo!
modaco said:
So how would one go about porting their changes to the donut kernel?
Click to expand...
Click to collapse
I'd imagine it would be a case of diff'ing the Hero kernel source against the "stock" 2.6.27 for Android 1.5, analysing the differences, and then applying them (where appropriate) to the 2.6.29 source for Android 1.6.
Regards,
Dave
foxmeister said:
I'd imagine it would be a case of diff'ing the Hero kernel source against the "stock" 2.6.27 for Android 1.5, analysing the differences, and then applying them (where appropriate) to the 2.6.29 source for Android 1.6.
Regards,
Dave
Click to expand...
Click to collapse
Yes, the biggest question is how many did they change? Does anybody got some time to make some statistics about this? lines changed, added, removed?
modaco said:
So how would one go about porting their changes to the donut kernel?
It would be super useful is someone could take the shipping 1.6 kernel source and apply the HTC changes if that's feasible.
Anyone fancy it? It'd give me and other devs a good 2.6.29 kernel source to use with either cupcake or donut builds...
P
Click to expand...
Click to collapse
Can't we skip donut and go for Eclair, or is that a stupid thing to say
Given Google haven't released the source code to Eclair yet, no.
Regards,
Dave
Hi everyone,
First, read the readme.txt in the zip file.
You flash it at your own risk. Backup everything. Learn how to use Heimdall. If it eats your dog it's not my problem . Many things are broken - post about it in the thread if nobody posted before. If you have any idea how to fix things, post too or PM me.
Requirements: GSM (Euro, US ATT/TMO tabs), with JQ1 (Gingerbread) unprotected bootloaders that can run Euro JQ1 ROM and gt-p1000_mr.pit partitioning.
Modem versions:
ATT: use I9000UGJK3 modem (this is what I am using)
TMO: try JK5
Euro: reports say that JK5, JPZ modems work
HK: user reports JK5 modem works.
CDMA: This ROM does not support CDMA Tabs.
LTN: experimental kernel included.
The archive with the build with Heimdall is here http://gtab7.nexus-lab.com/cm7sgt/tcm7beta-2012-08-05.zip
Please use heimdall to install. This zip file is not for flashing with CWM. Unzip and read the readme.txt in the zip file. Flash using the Heimdall command line (below).
The update zip for CWM is here http://gtab7.nexus-lab.com/cm7sgt/cm-7-20120805-UNOFFICIAL-galaxytab.zip, (GSM only, no LTN), please be sure to flash it from recovery that supports EXT4 or flash it once so it updates kernel/recovery, reboot to new recovery and flash it again. If you encounter any problems, use the Heimdall version.
P1000L/N
There is experimental P1000L kernel and bootloaders included in LTN directory in Heimdall package. It should work on P1000L and maybe P1000N.
Big thanks to Humberos for patches and testing. Adventureous souls with Latin Tabs please try it and report how it worked for you. You should have Gingerbread bootloaders and partitioning done first, so it should be easy if you are already running Gingerbread on your P1000L/N.
Installation using Heimdall
normal update from previous CM7 version, or a flash from another Gingerbread ROM:
Code:
heimdall flash --kernel zImage --factoryfs factoryfs.ext4
full flash and repartition:
Code:
heimdall flash --repartition --pit gt-p1000_mr.pit --primary-boot boot.bin --secondary-boot sbl.bin --kernel zImage --factoryfs factoryfs.ext4 --cache cache.ext4 --dbdata dbdata.ext4
Please be careful and double check your Heimdall command line when you flash bootladers, you may brick your Tab pretty bad.
If you get stuck on first reboot after install, or your settings aren't saved it means your data partitions need to be reformatted to ext4. This should be handled by setup_fs in init.rc.
If it didn't happen, start adb and run
make_ext4fs /dev/block/mmcblk0p2
make_ext4fs /dev/block/stl10
make_ext4fs /dev/block/stl11
Or try full wipe in recovery.
make_ext4fs is slightly wonky so you could use "/system/bin/mke2fs -t ext4 -m 0" instead (recovery is also using make_ext4fs internally to wipe partitions)
Samsung apps, Swype, Gapps etc
This is an unofficial port of CyanogenMod. I am striving to give us the pure CyanogenMod experience on Galaxy Tab.
So, there are no Samsung apps and don't ask for them.
There is no TouchWiz and don't ask for it.
It comes with ADW Launcher and if you want anything else, there is plenty of launchers in the Market.
If you want Google Apps, get it from the usual place http://goo-inside.me/gapps/ and install from recvery after flashing update.zip. The Heimdall version has Gapps integrated right now.
There is one stupid annoyance on Google sign-in welcome screen. It asks to slide open the keyboard (which we don't have and for now I can't find this setting). So skip the whole set up and sign in to Google account from Settings->Accounts&Sync.
Swype: there is no Swype. Since Swype has a policy of allowing Swype on modded ROMs as long as the original ROM had Swype integrated, if somebody cares to make flashable zip with Swype I can link it from OP.
Market issues.
Market 3.x has much stricter rules about DPI and device checks. So very often it shows apps as not compatible with CM7 on GalaxyTab.
Just go to Settings->Applications and uninstall updated Market it will go back to 2.x for a while.
Or try tool like OldMarket http://forum.xda-developers.com/showthread.php?t=1240344
You can also change build.prop yourself, you will need to change two lines:
ro.build.tags=test-keys to ro.build.tags=release-keys
and
ro.sf.lcd_density=200 ro.sf.lcd_density=240
reboot, delete Market data from Settings->Applications
Big thanks to junkshow for investigating it.
sources at http://github.com/cm7sgt
How to report bugs
If you think you have found a bug.
- verify you can repeat it, make sure it is not caused by the fact you did not wipe the device by rebooting to recovery and using wipe when you first installed CM7. Particularly when coming from other ROMs that use ext4. When coming from RFS your partitions should have been reformatted on first boot but wiping after install will not hurt.
Please read existing open and already closed issues at http://github.com/cm7sgt/android_device_samsung_galaxytab/issues
If your bug is new.
Please see if it is upstream (general CM7 not related to Tab) bug, see in CM7 issues tracker http://code.google.com/p/cyanogenmod/issues/list
If it is already there, please stop or add a comment there.
If the bug is about generic issue, please try to verify it it also happens on other CM7 devices. If so, you should post it in CyanogenMod issues.
If the bug is Galaxy Tab specific, like, some hardware functionality is missing, some driver not working. Dialogs messed up because of resolution etc, this means it belongs to Galaxy Tab device issue tracer and I can fix it.
In this case please open new issue here http://github.com/cm7sgt/android_device_samsung_galaxytab/issues
Please use pastie.org or something like that for posting logs.
SDCARD controversy
By default, the real micro SD is /mnt/sdcard, the internal mmc is /mnt/sdcard/external_sd, like in Galaxy S CyanogenMod builds.
If you don't like it, you can swap the devices, go to Settings -> CyanogenMod settings -> Application and check Use internal storage [ ] checkbox.
Reboot, now internal will be /mnt/sdcard, external will be /mnt/sdcard/external_sd like in Samsung's Android.
In recovery, real sdcard in /sdcard, internal sdcard (embedded MMC) is /emmc.
If you want to flash zip from /emmc just go in recovery "install zip from sdcard" -> "choose zip from internal sdcard" -> choose whatever you want to flash.
--
{
"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"
}
Current status:
Voice calls: OK (make sure to use modem.bin compatible with JQ1 RIL)
3G data: OK
Wifi: OK
Bluetooth: OK
Camera: Photos OK, video encoding (movie capture) back OK, front corrupted
Sensors: seem OK
GPS: OK
Recovery and initramfs: CWM, partitions get mounted, wipe works, havent tried backup/restore
Video playback: overlay and copybit work, OMX libraries are in and decoding works.
Changelog:
2012-08-05 http://gtab7.nexus-lab.com/cm7sgt/tcm7beta-2012-08-05.zip http://gtab7.nexus-lab.com/cm7sgt/cm-7-20120805-UNOFFICIAL-galaxytab.zip
Fixed Bluetooth MAC address issue. Now it is read correctly from EFS. Thanks to ableeker.
2012-07-28 http://gtab7.nexus-lab.com/cm7sgt/tcm7beta-2012-07-28.zip http://gtab7.nexus-lab.com/cm7sgt/cm-7-20120728-UNOFFICIAL-galaxytab.zip
Update to latest from CM7 git.
2012-02-19 http://gtab7.nexus-lab.com/cm7sgt/tcm7beta-2012-02-19.zip http://gtab7.nexus-lab.com/cm7sgt/update-cm-7-2012-02-19-Beta-GalaxyTab-KANG-signed.zip
Update to latest from CM7 git. set default DPI to 240 to fix market issues, advanced users can set any DPI they want anyway.
Go back to stock dialer layout because it has changed a lot.
2011-11-02 http://gtab7.nexus-lab.com/cm7sgt/tcm7beta-2011-11-02.zip http://gtab7.nexus-lab.com/cm7sgt/update-cm-7-2011-11-02-Beta-GalaxyTab-KANG-signed.zip
use android socket for wpa_supplicant control interface. anyone upgrading to this version please delete their /data/misc/wifi/wpa_supplicant.conf
thanks to jt1134, removed extra field in mfc interface in kernel which prevented it from working with aries OMX libraries
updated media_profiles.xml to expose 1024x600 and 800x600 resolutions for camcorder. its not perfect but at least video recording works now. front cam produces broken video.
2011-10-31 http://gtab7.nexus-lab.com/cm7sgt/tcm7beta-2011-10-31.zip http://gtab7.nexus-lab.com/cm7sgt/update-cm-7-2011-10-31-Beta-GalaxyTab-KANG-signed.zip
update to latest from git. we are little past 7.1.0.
fix key setting for AP mode
new init.rc/init.gt-p1000.rc unified with CDMA device
2011-10-09
move download cache to /data/cache_download and system dalvik cache to data, it should fix download issues with large APKs
fix bluetooth keyboard keypad rotation issue
move touchscreen event rotation to kernel to to clean up frameworks/base
use switchable pair and new stacked mounts in vold for /mnt/sdcard and and /mnt/sdcard/external_sd
2011-09-20
Update to latest from git.
Merged P1000L/N kernel. P1000L kernel included in build.
Voodoo Sound update to V10. Switch to JHASH3 hash function in kernel.
Disabled NEW_AP in Wifi driver, fixed hotspot mode.
2011-08-07
Update to latest from git. Android 2.3.5.
Added BLN kernel driver and LIGHT_ID_NOTIFICATIONS -> /sys/class/misc/backlightnotification/notification_led device to liblights. Big thanks to Neldar.
Fix geolocation/networklocation settings in props and frameworks' config.xml
Update EGL driver and pvrsvrkm kernel driver to latest from EF17 Sprint GB release.
2011-07-20
Update to latest from git.
Merge changes from Sprint GB kernel source release. Merge relevant kernel changes to up to 2.6.35.10.
2011-06-21
Enable CRT screen off/on animation.
Add virtual flag to capacitive buttons to enable vibration when they are pressed.
Increase HCI baud rate to 3M, hopefully this will help A2DP issues with BT keyboards.
2011-06-13
Rotary Lockscreen bitmaps and Twelve Key Dialer portrait and landscape layouts have been fixed by Fabrizio. Big thanks!
Fixed wrong parameter to ril->setCallVolume, hopefully will make call audio better.
Switched to use Samsung's binary brcm_patchram_plus with the same parameters in init.rc. Bluetooth SCO works now. Magic?
2011-06-06
Add attribute for available frequencies, fix cpufreq sysfs permissions so CMParts can access it.
Change compile options for kernel to cortex-a8. Enable Tiny RCU.
Fixed calls from other places in the kernel that used olde speed levels and caused frequency spikes to 1.2GHz.
Fixed Low Power Mode (it properly starts /lpm.rc and displays charging animation).
2011-06-05
Added 10-point Multitouch to kernel (thanks to The_Double and hoss_n2)
Added overclock (1.4GHz) and undevolt (thanks to Richard Trip and Koxudaxi)
Added Voodoo Sound V9 (thanks to Supercurio and Richard Trip)
Switched to (some) Crespo EGL SOs, hopefully will fix some OpenGL issues.
2011-06-03
Add usb_connected switch to kernel, fixes usb mounting and usb connection detection.
Use mke2fs instead of make_ext4 for formatting in OTA and setup_fs. Should be more reliable.
Added download mode to reboot menu.
2011-05-30
Fix problems with headphones/headsets and libaudio, kanged common-aries libaudio.
Added OMX libraries and overlay from common-aries.
2011-05-28r2
Fixed setup_fs so it properly formats partitions.
Enabled more tablet tweaks (soft buttons).
Removed format for .android_secure in recovery, should fix wipe.
2011-05-28
Switched to Gingerbread kernel 2.6.35.7 recently released by Samsung.
Use JQ1 binary drivers for OpenGL, sensors, lights, copybit, overylay, camera etc, so they all work!
Portrait is default orientation now, ro.sf.hwrotation=90 is set and touchscreen events are rotated in input layer so they match.
<cut short, more in readme.txt>
Big thanks to noobnl, coolya, codeworkx, rotohammer, KhasMek, deodexed, captainkrtek, lilstevie, a_snowman, frusso, humberos, koxudaxi, spacemoose, oldmacnut and others for help, advice, testing etc etc.
DEVS ONLY HERE ---------------------------------------
How to build CYanogenMod 7 for Galaxy Tab GT-P1000
First, please read this article http://wiki.cyanogenmod.com/index.php?title=Compile_CyanogenMod_for_CaptivateMTD
You will need the same prerequisites.
Then
Get repo as described there. I put mine in /usr/local/bin
Sync Android tree. You need to use manifest from cm7sgt github.
(If you have more/less than 4 cores modify your -j4 accordingly)
Create a directory for your Android, you will need oer 10GB of free space. It helps a lot to put it on SSD.
repo init -u git://github.com/cm7sgt/android.git -b gingerbread
since kernel.org gits are still down, until they are back up you need to sync repo tool from github, so use this command line, thanks to Disgustipated for pointing it out.
curl https://raw.github.com/android/tools_repo/master/repo > ~/bin/repo
chmod a+x ~/bin/repo
repo init -u git://github.com/cm7sgt/android.git -b gingerbread --repo-url=git://github.com/android/tools_repo.git
repo sync -j4
Grab Rom Manager as described.
You can't (no script) and don't need to copy proprietary files, everything is already included in vendor git.
Setup your android build environment and choose device to build:
. build/envsetup.sh
lunch cyanogen_galaxytab-eng
make -j4
There, it should build with no issues. Sometimes it will complain about API changes, run make update-api then.
From here you have two options.
1. Build Heimdall images. You will need kernel with loop support, losetup, ext4 tools (mkfs.ext4).
cd device/samsung/galaxytab/tools
./buildimage
it will grab stuff from out and create ext4 images. Flash with Heimdall.
2. Build update.zip
make -j4 bacon
How to build kernel
First, you will need the arm toolchain from CodeSourcery. You need arm-2009q3-68-arm-none-eabi-i686-pc-linux-gnu.tar.bz2
From http://www.codesourcery.com/sgpp/li...q3-68-arm-none-eabi-i686-pc-linux-gnu.tar.bz2
Unpack it in /opt/toolchains. as root
mkdir -p /opt/toolchains
cd /opt/toolchains
tar -xjvf arm-2009q3-68-arm-none-eabi-i686-pc-linux-gnu.tar.bz2
Then in your CM7 tree
BEFORE YOU BUILD CM7 TREE
cd device/samsung/galaxytab
./kernel.sh defconfig
./kernel.sh modules
This will configure the kernel and build and copy modules to prebuilt directories. The kernel build directory is out/target/product/galaxytab/kernel_build
Build your android tree normally so initramfs is created.
Then again
cd device/samsung/galaxytab
./kernel.sh kernel
This will build the kernel using the initramfs in recovery/root and update prebuilt kernel image.
(for Latin kernel use kernel_ltn.sh script and use kernel_ltn file it produces)
Now you need to run make on your android tree again so boot.img is updated.
And proceed to buildimage or make bacon as usual.
sweet news
P1000L tabs too?
I can test for you.
ivannw said:
P1000L tabs too?
I can test for you.
Click to expand...
Click to collapse
AFAIK P1000L hardware is different so it will need different kernel
How do we check which bootloader we have?
TheGrammarFreak said:
How do we check which bootloader we have?
Click to expand...
Click to collapse
If you installed Euro JJ4 ROM you probably have JJ4 bootloader.
It will probably also work with stock ATT and TMO bootloader but I cannot guarantee that. I have JJ4. People have reported issues using Euro ROMs on ATT bootloaders, I believe the same issues will show up in my CM7.
Great news. I have polish rom maybe i help. galaxy tab jm6
That is amazing work!
Well done.
Which issue r u tlaking abt? I have recent att tab went straight to jme no issue. Lemme know if i could hrlp testing. Ubuntu & heimdall ready. I actually pulled your old cm6 and cp kernel-tab and what not to cm7 but failed at lunch cyanogen...
Sent from my GT-P1000 using XDA App
quattr0 said:
Which issue r u tlaking abt? I have recent att tab went straight to jme no issue.
Click to expand...
Click to collapse
some white lines while booting etc. if JME works for you my stuff should work too.
TheGrammarFreak said:
How do we check which bootloader we have?
Click to expand...
Click to collapse
I'm no expert but this seems obvious (for me). If you have a linux box, do a "strings boot.bin" on a protected bl (extract from JMF downloaded from samfirmware for instance), you will see these lines
PBL: Error.. sbl verification failed..
PBL: booting stop!
My at&t backup boot.bin does not have the above 2 lines.
Just my guess.
Technomancer said:
AFAIK P1000L hardware is different so it will need different kernel
Click to expand...
Click to collapse
Can you help me or give the way to compile the correct kernel?
Sent from my GT-P1000L using XDA App
I can't wait for this... My Tab seems to just be less awesome without the love CM gives to Android.
installed but touch doesnt works.
what is the next step?
ivannw said:
installed but touch doesnt works.
what is the next step?
Click to expand...
Click to collapse
this is because of the different hardware!
if ur not a developer, leave it till it is stable because u are missing some necessary features for everyday use!
landroid thanks for your response.
btw i wanna learn how to fix that. can you give me directions ?
first of all I'll try to get stock rom compiled.
too bad again not for CDMA tab user
ivannw said:
landroid thanks for your response.
btw i wanna learn how to fix that. can you give me directions ?
first of all I'll try to get stock rom compiled.
Click to expand...
Click to collapse
First off all u need to find the kernel source for ur tab (i think P1000L, right?) And then apply the patches technomancer made to the kernel but this is very hard to do! The best thing would be to contact technomancer! And if i find some spare time tommorrow ill try to compile a P1000L kernel for u but i cant guarantee that if i manage to do that everything works! But i knoe how to compile kernels from source so it should not be a problem!
Sent from my GT-P1000 using Tapatalk
ivannw said:
landroid thanks for your response.
btw i wanna learn how to fix that. can you give me directions ?
first of all I'll try to get stock rom compiled.
Click to expand...
Click to collapse
Get sources for your kernel from opensource.samsung.com.
Compile it with gingerbread branch of this initramfs https://github.com/cmsgs/android_initramfs_galaxytab
See what happens ;-)
Look awesome!!
here is the guide
http://forum.xda-developers.com/showpost.php?p=24747881&postcount=4
thakz irfanbagus for the guide
where's the package link?have you try this guide by yourself?
i hope he tried
got a ubuntu, i will try this one (cross-fingers)
it's not working. sgy stock kernel do not have /proc/config.gz and gcc version in arm-2011.03 not compatible with other precompiled module.
this is work for me
requirement :
1. linux box 32 bit with working gcc. you can use real linux machine or virtual machine
2. Sourcery G++ Lite 2009q3-68 toolchain for ARM EABI from http://www.codesourcery.com/ (Linux version without installer arm-2009q3-68-arm-none-eabi-i686-pc-linux-gnu.tar.bz2)
3. mkbootimg with md5support. got it from http://forum.xda-developers.com/showpost.php?p=22224170&postcount=241 . credit to harish2704
4. split_bootimg.pl (google it)
5. kernel source from http://opensource.samsung.com . i use GT-S5360_GB_Opensource_Update2.zip
6. stock boot.img (or from your custom kernel).
step :
1. make folder "sgy" in your home. the result is folder "/home/<yourname>/sgy". <yourname> is your linux user name, and from now replace <yourname> with your user name. put all file you already download there
2. extract "GT-S5360_Kernel.tar.gz" from "GT-S5360_GB_Opensource_Update2.zip". put also in "sgy" folder
3. open terminal emulator and go to your working path with command
Code:
cd ~/sgy
4. extract your compiler with
Code:
tar -xvf arm-2009q3-68-arm-none-eabi-i686-pc-linux-gnu.tar.bz2
5. create folder "kernel" and extract kernel source there
Code:
mkdir kernel
cd kernel
tar -xvf ../GT-S5360_Kernel.tar.gz
you got 2 folder, "common" and "modules"
6. open folder "common", there is file "Makefile". open with text editor and find line with content "/opt/toolchains/arm-eabi-4.4.3/bin/arm-eabi-". replace with "/home/<yourname>/sgy/arm-2009q3/bin/arm-none-eabi-", don't forget replace <yourname>.
7. in terminal goto folder "common" and load default config for sgy
Code:
cd ~/sgy/kernel/common
make bcm21553_totoro_05_defconfig
8. if you want change you config run
Code:
make menuconfig
9. if you ready to build then run
Code:
make
or if you have dual core cpu and want to make it faster
Code:
make -j3
10. when complete and no error appear, copy your kernel to "sgy" folder
Code:
cp arch/arm/boot/zImage ~/sgy
11. extract ramdisk from your boot.img
Code:
cd ~/sgy/
perl split_bootimg.pl boot.img
you got "boot.img-kernel" and "boot.img-ramdisk.gz". move "boot.img" and "boot.img-kernel" to other place.
12. repack your new kernel and ramdisk. but first get md5sum of your new kernel
Code:
md5sum zImage
you got something like
Code:
1fd319aa60abc2abae2e5932bcb9fc77 zImage
you need that "1fd319aa60abc2abae2e5932bcb9fc77" write it or copy to text editor. you need run it every time compile new kernel
13. repack
Code:
chmod +x mkbootimg
./mkbootimg --kernel zImage --ramdisk boot.img-ramdisk.gz --base 0x81600000 --kernelMD5 <your md5sum result> -o boot.img
14. make odin flash-able
Code:
tar -cf boot-sgy.tar boot.img
I thought you have to put your post into a new thread irfan...this one is a fake guide.
kurotsugi said:
I thought you have to put your post into a new thread irfan...this one is a fake guide.
Click to expand...
Click to collapse
Irfan must create a guide.yes yes..I also think Irfan sahab must compile a CM7.2 from sources.
offtopic:
btw, do you know who's working on cm7 from source with motafoca?his thread is missing and I just get curious on their progress.
kurotsugi said:
offtopic:
btw, do you know who's working on cm7 from source with motafoca?his thread is missing and I just get curious on their progress.
Click to expand...
Click to collapse
His thread was closed by moderator.You can request MOD to reopen his thread.Motafoca wanted a galacy y to be lended for his experiments
---------- Post added at 03:37 PM ---------- Previous post was at 03:33 PM ----------
Can someone download the sources around 15Gigs and stripe down the file and share it to Maroc ?
Whre can i download it?
Sent from my GT-S5360 using xda premium
kurotsugi said:
I thought you have to put your post into a new thread irfan...this one is a fake guide.
Click to expand...
Click to collapse
i don't call it fake. it's just too general and missing some detail (but critical) for our device. and in the 'spirit of operation iron fist', i think it's better to put here
premolikeshtc said:
Irfan must create a guide.yes yes..I also think Irfan sahab must compile a CM7.2 from sources.
Click to expand...
Click to collapse
with my internet connection, it will take weeks just to download the source. and i think cm, like android source, use repo. so you can't just download it. you clone it from their source repository, that mean no download accelerator.
btw beside kernel source, samsung also release their mod to android source. but to build it, you still need to get android source (about 10GB according their website).
well...thats your choice, irfan.
@sgy.creed: sorry, I don't mean to offend you. IMHO it will be nice if before someone post any guide they already have tested it by them. in this way, they'll able to give more accurate direction to anyone who need their guide. as we already know, kernel is crucial part in our device. any mistake in compiling it will lead to brick our device. we have to cautious on it. peace ^,^v
kurotsugi said:
well...thats your choice, irfan.
@sgy.creed: sorry, I don't mean to offend you. IMHO it will be nice if before someone post any guide they already have tested it by them. in this way, they'll able to give more accurate direction to anyone who need their guide. as we already know, kernel is crucial part in our device. any mistake in compiling it will lead to brick our device. we have to cautious on it. peace ^,^v
Click to expand...
Click to collapse
if you (or others) think it's better to put in other thread, or maybe op wanna edit his post, fell free to copy my post (or just link, it's up to you). i don't take any credit to that post, because it just recompilation from other thread.
GT-B5510
Is there by chance anyway to find a stock Kernel for my device for my GT-B5510???
I recently flashed a custom Kernel for GT-S5360 and the result was a Brick.
is there someone willing to help me??
Rui Oliveira 21 said:
Is there by chance anyway to find a stock Kernel for my device for my GT-B5510???
I recently flashed a custom Kernel for GT-S5360 and the result was a Brick.
is there someone willing to help me??
Click to expand...
Click to collapse
Have u tried through kies?if the answer u failed then only odin is the way.
u need pda files from the update.Search google,i found one FW but it is from Italy :
B5510CEKK1.
sgy.creed said:
Hi guys,
This guide teaches how to make a new kernel for your device, it works in most of the cases but doesnt mean it will work for everyone
You need a minimal linux experice to know WTF you are doing
If you have any questions, post Belloowww
Download the required files
You will need a linux machine with the basic development tools or a virtualbox machine running a linux distribution (ubuntu 64bits will do fine)
I use the codesourcery package
Download the IA32 GNU/Linux TAR
The tar package is the easier to install
You will also need your kernel source from your manufacturer, for samsung the sources are available here
Install the cross compiler
Enter the folder were you downloaded the package and extract it, you will get something like arm-2011.03
Move that folder to some location, i use opt
ex: mv arm-2011.03 /opt/
or
sudo mv arm-2011.03 /opt
Done!
Extract and prepare the kernel sources
I will use the samsung sources as example, but anything can be used
For the samsung sources, after you extract the zip, you will get something like DEVICE_Platform.tar and DEVICE_Kernel.tar.gz
Extract the kernel:
tar zxvf DEVICE_Kernel.tar.gz
Enter the kernel folder and list the folder contents
ls
The structure is something like this:
{
"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"
}
Most devices contain the config file inside the device
You can extract it like this:
adb shell
su
cp /proc/config.gz /sdcard/
exit
exit
adb pull /sdcard/config.gz
Good, now we have the sources, compiler and configuration
Compiling the kernel
To compile ther kernel, i usually clean the sources first, with this i know for sure nothing will go wrong (usually )
make ARCH=arm CROSS_COMPILE=/opt/arm-2011.03/bin/arm-none-eabi- distclean (Remember to replace acordingly the compiler folder)
Sources cleaned, time to load the config file
gunzip config.gz
cp config ./.config
Good, now lets check the menuconfig (menuconfig is a menu to choose the kernel options, created to make it easy to select)
make ARCH=arm CROSS_COMPILE=/opt/arm-2011.03/bin/arm-none-eabi- menuconfig
Change whatever you want and exit and save
good, now its time to build
make ARCH=arm CROSS_COMPILE=/opt/arm-2011.03/bin/arm-none-eabi- -j2
Now wait for it to finish!
Your compiled kernel will be located inside arch/arm/boot/zImage
Extracting a boot.img
Good, now we have the zImage, but WTF to do with it?
Well, android usually (some samsung devices use a different boot.img method, ex: I9000) has the boot.img, inside of it we contain:
- ramdisk (required files to load the /system partition and continue the boot sequence)
- zImage (our kernel)
- pagesize
- base
- cmdline (some kernel paremetes used on boot)
To create your own boot.img, you need one from a nandroid backup that was made from CWM or AmonRA custom recoveries (there are other methods, but for those use the madteam forum )
The boot.img is located inside your /sdcard/clockworkmod/backup/somedate/boot.img
You will also need the unpackbootimg and mkbootimg binaries, i this link there is the 64 bit version (wont work on 32 bit linux)
create an empty folder, copy the downloaded file inside, enter it and do:
tar zxvf bootimgtools.tar.gz
chmod 755 *
now copy the boot.img you got from the backup
and extract the boot.img with:
./unpackbootimg -i boot.img
this will create the files as explained above
Creating the boot.img
Before making the boot.img, we need some information from the files extracted
cat boot.img-base ( save the output #1)
cat boot.img-pagesize (save the output , place the value inside the Hex Value of this site, and copy the decimal value and save it #2)
cat boot.img-cmdline (save the output #3)
Good, now copy the compiled kernel (zImage) inside the current folder and do:
mkbootimg –kernel zImage –ramdisk boot.img-ramdisk.gz –cmdline “(replace with output#3)” –base (replace withoutput #1) –pagesize (replace with output#2) -o /tmp/boot.img
Good, the boot.img is created!
Now test on your device!
If you dont know how to flash the boot.img, enter the madteam forum and request help (its too difficult to explain the flashing of boot.img if you dont know how to do it )
Take care!
<External link removed>
Click to expand...
Click to collapse
please credits motafoca madteam
GT-B5510
Harsh06 said:
Have u tried through kies?if the answer u failed then only odin is the way.
u need pda files from the update.Search google,i found one FW but it is from Italy :
B5510CEKK1.
Click to expand...
Click to collapse
Kies said that I had the most recent firmware, tough I found some new versions.
right now trough kies I tried to do an emergency firmware restore, i guess thats the name, but it asked for a code, a 4 number code i guess and i dont know what's the code.
Via odin I tried to install stock firmware from sammobile but it failled as well, if you want I'll post the dialog from odin.
I can boot in recovery mode, Odin(download) mode and CWM mode.
could you point me in the right direction???
thanks for your time
Rui Oliveira 21 said:
Kies said that I had the most recent firmware, tough I found some new versions.
right now trough kies I tried to do an emergency firmware restore, i guess thats the name, but it asked for a code, a 4 number code i guess and i dont know what's the code.
Via odin I tried to install stock firmware from sammobile but it failled as well, if you want I'll post the dialog from odin.
I can boot in recovery mode, Odin(download) mode and CWM mode.
could you point me in the right direction???
thanks for your time
Click to expand...
Click to collapse
I believe Doky already reply your post n willing to help u in others thread.Give doky some info about your current FW.U need 3 complete files n flash through Odin.Key in *#1234# with your dialer(u will see current info version) and PM doky about the info.He surely gonna help u.
Sorry OP off topic.
GT-B5510
He did help, thanks
question now is...while trying to revive the phone I installed Creed's Rom for Gt-s5360, I got quiet, and obviously it doesnt work that well in my GT-B5510, so I need a custom Rom for my device or a Stock Rom, but I cant find neither :S
any lights??
Kernel
How to change Kernel Version when build kernel ??
usually display 2.6.35.7 [email protected] #1
i wanna change [email protected] #1 so how the setting on linux or maybe what file??
Thanks b4
Rui Oliveira 21 said:
He did help, thanks
question now is...while trying to revive the phone I installed Creed's Rom for Gt-s5360, I got quiet, and obviously it doesnt work that well in my GT-B5510, so I need a custom Rom for my device or a Stock Rom, but I cant find neither :S
any lights??
Click to expand...
Click to collapse
I was just wondering if you went to the oldest possible firmware you could find and then proceeded to update from that. Sometimes the updates only contain necessary info and kind of rely on the previous installs.
Sent from my TF101 using Crashntalk 2
This is a complementary guide to [Guide] How to compile and install CM10 for Samsung i9000
Want to add support for another filesystem to the CM10 kernel?
Add a module?
Maybe slim things a bit by removing some stuff?
All fine, but where to start?
Since CM9, the kernel source code should be integrated with CM's source code.
So, if you are building CM10, you should already have a kernel folder in the source code.
So, where's the config file used to build the i9000 kernel?
Well, it's here: ~/android/system/kernel/samsung/aries/arch/arm/configs/cyanogenmod_galaxysmtd_defconfig
You can edit the file directly in a text editor (if you know what you're doing) and it looks something like this:
Code:
CONFIG_EXPERIMENTAL=y
CONFIG_KERNEL_LZMA=y
# CONFIG_SWAP is not set
CONFIG_SYSVIPC=y
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
CONFIG_CGROUPS=y
CONFIG_CGROUP_DEBUG=y
CONFIG_CGROUP_FREEZER=y
CONFIG_CGROUP_CPUACCT=y
CONFIG_RESOURCE_COUNTERS=y
CONFIG_CGROUP_SCHED=y
CONFIG_RT_GROUP_SCHED=y
CONFIG_INITRAMFS_SOURCE="source/usr/galaxysmtd_initramfs.list"
...
You can just edit the text file, but sometimes it's not that easy to find/do what you want because the labels aren't very user-friendly.
It's easy to make several types of mistakes.
... but there is a better way to do it, using the menuconfig tool.
To use menuconfig, just do:
Code:
cd ~/android/system/kernel/samsung/aries
make menuconfig
You should now have a text GUI to access all the options that is much easier and safer to use:
{
"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"
}
Now you need to load the i9000 configuration file.
Select "Load an Alternate Configuration File" at the bottom of the menu
Point to the i9000 default kernel config file: arch/arm/configs/cyanogenmod_galaxysmtd_defconfig
After you hit OK, you'll open the i9000 config file. Make the changes you want and exit. You'll be asked if you want to save the changes.
NOTE: I've had some issues with make menuconfig producing "strange" files.
Do:
Code:
grep CONFIG_USB_G_ANDROID kernel/samsung/aries/arch/arm/configs/cyanogenmod_galaxysmtd_defconfig
and confirm the result is:
Code:
CONFIG_USB_G_ANDROID=y
If it's not, menuconfig "missbehaved".
(There's a backup of the original config in kernel/samsung/aries/arch/arm/configs/cyanogenmod_galaxysmtd_defconfig.old)
Final step: Tidy things up:
Code:
cd ~/android/system/kernel/samsung/aries
make mrproper
That's it.
Build away.
(Don't forget to do a "make installclean" and cleaning things up before building)
For more information on CM's kernel building, see this: http://wiki.cyanogenmod.com/wiki/Integrated_kernel_building
another great summary! thank you!
USB
EDIT: This comment is now obsolete.
--------------
NOTE: While everything builds nicely and is functional, somehow the USB support seems to be gone in the builds produced. Charging still works but ADB and Storage don't.
There's something missing.
If you know what it is, drop a line.
pmos69 said:
NOTE: While everything builds nicely and is functional, somehow the USB support seems to be gone in the builds produced. Charging still works but ADB and Storage don't.
There's something missing.
If you know what it is, drop a line.
Click to expand...
Click to collapse
Did you enable/disable things in the config file? It is not as easy to change things by just changing the config file, often the underlying source code also needs to be changed if you want to enable certain features...
Did you somehow add fast charge support?
kasper_h said:
Did you enable/disable things in the config file? It is not as easy to change things by just changing the config file, often the underlying source code also needs to be changed if you want to enable certain features...
Did you somehow add fast charge support?
Click to expand...
Click to collapse
Just made simple tests enabling simple features, like enabling btrfs filesystem support.
At first I was enabling stuff like swap and zRam, but then thought about what you are saying and went for simple tests.
Just enabling btrfs filesystem support, triggers the behaviour.
I think any change may do it.
Maybe just saving the config file in menuconfig does it.
Sent from my GT-I9000 using xda premium
pmos69 said:
Just made simple tests enabling simple features, like enabling btrfs filesystem support.
At first I was enabling stuff like swap and zRam, but then thought about what you are saying and went for simple tests.
Just enabling btrfs filesystem support, triggers the behaviour.
I think any change may do it.
Maybe just saving the config file in menuconfig does it.
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
I often change stuff in defconfig, but I always do it for code I added to the source. Never had a problem with USB after that. So in principle, it should work...
kasper_h said:
I often change stuff in defconfig, but I always do it for code I added to the source. Never had a problem with USB after that. So in principle, it should work...
Click to expand...
Click to collapse
Make menuconfig + make mrproper are making a mess.
Code:
diff -d <(sort kernel/samsung/aries/arch/arm/configs/cyanogenmod_galaxysmtd_defconfig.old) <(sort kernel/samsung/aries/arch/arm/configs/cyanogenmod_galaxysmtd_defconfig)|grep CONFIG_USB_G_ANDROID
< CONFIG_USB_G_ANDROID=y
> # CONFIG_USB_G_ANDROID is not set
WTF?
Back to hand-editing the config file, I guess...
Edit: Just tried it again, starting from the original config, and it's not happening this time... Building now.
Maybe I did something dumb before? (happens a lot)
pmos69 said:
Make menuconfig + make mrproper are making a mess.
Code:
diff -d <(sort kernel/samsung/aries/arch/arm/configs/cyanogenmod_galaxysmtd_defconfig.old) <(sort kernel/samsung/aries/arch/arm/configs/cyanogenmod_galaxysmtd_defconfig)|grep CONFIG_USB_G_ANDROID
< CONFIG_USB_G_ANDROID=y
> # CONFIG_USB_G_ANDROID is not set
WTF?
Back to hand-editing the config file, I guess...
Edit: Just tried it again, starting from the original config, and it's not happening this time... Building now.
Maybe I did something dumb before? (happens a lot)
Click to expand...
Click to collapse
That is the way you learn quickest: by making mistake. I tell this to my students everyday when the ruin experiments
kasper_h said:
That is the way you learn quickest: by making mistake. I tell this to my students everyday when the ruin experiments
Click to expand...
Click to collapse
Well, don't know what happened (but it happened quite a few times).
Working fine now...
Nice howto, thanks. Have one question. I want to build kernel for ypg1, really similar device to i9000. So what to do next when I have zImage and modules. I mean have only kernel source and toolchain without whole Android sources. I need to make installable pkg but don't know how.
I'm looking for step by step how to build kernel, build recovery etc.
Sent from my GT-I9001 using xda app-developers app
oisis said:
Nice howto, thanks. Have one question. I want to build kernel for ypg1, really similar device to i9000. So what to do next when I have zImage and modules. I mean have only kernel source and toolchain without whole Android sources. I need to make installable pkg but don't know how.
I'm looking for step by step how to build kernel, build recovery etc.
Sent from my GT-I9001 using xda app-developers app
Click to expand...
Click to collapse
I think there are a few how-to's on that in the cm wiki.
I've not looked much into it, sorry.
Guess you'll only have to sync the kernel sources + device specific trees and only build the kernel.
oisis said:
Nice howto, thanks. Have one question. I want to build kernel for ypg1, really similar device to i9000. So what to do next when I have zImage and modules. I mean have only kernel source and toolchain without whole Android sources. I need to make installable pkg but don't know how.
I'm looking for step by step how to build kernel, build recovery etc.
Sent from my GT-I9001 using xda app-developers app
Click to expand...
Click to collapse
You could take a look at my github (github.com/kasperhettinga). I use a kernel building script (developed by stratosk) that does not require the whole source code of cm10 but will build a flashable zip using a separate ramdisk (also originating from the work of stratosk).
Verstuurd van mijn GT-I9000
Could you describe how to, after make when i have zImage and modules, pack everything to img to have CWM installable zip? I don't have this device but would like to learn it. Thanks a lot.
oisis said:
Could you describe how to, after make when i have zImage and modules, pack everything to img to have CWM installable zip? I don't have this device but would like to learn it. Thanks a lot.
Click to expand...
Click to collapse
I adapted the teamhacksung buildscript so it automatically creates a CWM-zip:
https://github.com/kasperhettinga/buildscript
I have a zImage built from CM10 kernel sources in Cygwin and I want to inject it into the CM10 boot.img.
Anyone has any idea how I can do that?
I tried to extract the boot.img from one of the nightlies using the dsxida's android kitchen, but it seems that it does not have ramdisk and the extracted zImage file is 0 bytes.
hey man i ve been trying to compile the kernel for my galaxy s2 and downloaded all the things recomended from the cyanogenmod github
these are the steps that i follow:
1. cd into my kernel root directory.
2. make cyanogenmod_i9100g_defconfig
3. make menuconfig
4. make -j5
after a few seconds i get this error
Code:
CHK include/linux/version.h
CHK include/generated/utsrelease.h
make[1]: `include/generated/mach-types.h' is up to date.
CALL scripts/checksyscalls.sh
CHK include/generated/compile.h
/home/incarnation95/cm10kernel/t1/scripts/gen_initramfs_list.sh: Cannot open '/home/incarnation95/home/incarnation95/cm10kernel/t1/usr/i9100g_initramfs.list'
make[1]: *** [usr/initramfs_data.cpio] Error 1
make: *** [usr] Error 2
[email protected]:~/cm10kernel/t1$
do you know how to tackle this problem?
please help i am really in a mess due to this.
previously i compiled a stock kernel, in stock kernel the compillation process went very good but it didnt boot
i really want to make this aosp kernel, and this is the only guide which indicates compilling an aosp kernel
hope you could sort out my problem.
thanks in advance
incarnation95 said:
hey man i ve been trying to compile the kernel for my galaxy s2 and downloaded all the things recomended from the cyanogenmod github
these are the steps that i follow:
1. cd into my kernel root directory.
2. make cyanogenmod_i9100g_defconfig
3. make menuconfig
4. make -j5
after a few seconds i get this error
Code:
CHK include/linux/version.h
CHK include/generated/utsrelease.h
make[1]: `include/generated/mach-types.h' is up to date.
CALL scripts/checksyscalls.sh
CHK include/generated/compile.h
/home/incarnation95/cm10kernel/t1/scripts/gen_initramfs_list.sh: Cannot open '/home/incarnation95/home/incarnation95/cm10kernel/t1/usr/i9100g_initramfs.list'
make[1]: *** [usr/initramfs_data.cpio] Error 1
make: *** [usr] Error 2
[email protected]:~/cm10kernel/t1$
do you know how to tackle this problem?
please help i am really in a mess due to this.
previously i compiled a stock kernel, in stock kernel the compillation process went very good but it didnt boot
i really want to make this aosp kernel, and this is the only guide which indicates compilling an aosp kernel
hope you could sort out my problem.
thanks in advance
Click to expand...
Click to collapse
These steps should resolve it
1. open the .config file that is created after you do make cyanogenmod_i9100g_defconfig
2. check the path of the file i9100g_initramfs.list and gen_initramfs_list.sh
3. edit the .config file to make sure the actual path matches to that in the .config file.
4. make -j5
5. Enjoy the new kernel !!
msri3here said:
These steps should resolve it
1. open the .config file that is created after you do make cyanogenmod_i9100g_defconfig
2. check the path of the file i9100g_initramfs.list and gen_initramfs_list.sh
3. edit the .config file to make sure the actual path matches to that in the .config file.
4. make -j5
5. Enjoy the new kernel !!
Click to expand...
Click to collapse
2. CONFIG_INITRAMFS_SOURCE="source/usr/i9100g_initramfs.list" (THIS WAS THERE BY DEFAULT)
I MADE IT CONFIG_INITRAMFS_SOURCE="~/home/incarnation95/cm10kernel/t1/usr/i9100g_initramfs.list"
as the location was.
i dont think we really have to define the path of gen_initramfs_list.sh or do we? and if yes then where?
There you have the problem...remove the "source/" from the path in the .config file
This path is defined by default and just needs customization for our device...
Sent from my GT-I9000 using xda premium
msri3here said:
There you have the problem...remove the "source/" from the path in the .config file
This path is defined by default and just needs customization for our device...
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
O thanks mate it really worked
Thanks a ton. Was tryna find sol. Since 3 days
Sent from my GT-I9100G using Tapatalk 2
---------- Post added at 11:32 PM ---------- Previous post was at 10:42 PM ----------
now after getting over those errors i am getting this error now :/
Code:
//home/incarnation95/Downloads/arm-2011.03/bin/arm-none-eabi-ld: cannot open linker script file /arch/arm/mach-omap2/sec_omap.lds: No such file or directory
make[1]: *** [arch/arm/mach-omap2/mailbox_mach.o] Error 1
make: *** [arch/arm/mach-omap2] Error 2
and weird thing is the files exists :/
In the spirit of open-source, if there's one ROM that deserves to be "home-brewed" in addition to AOSP and Lineage, it's LineageOS4Microg. This guide will explain how to do so using Docker. LineageOS and Microg are explained below followed by the guide.
{
"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"
}
Code:
/*
* I'm not responsible for bricked devices, damage, loss of Google services, you getting fired because the alarm app failed, etc. Do this at your own risk.
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications.
* Your warranty may/will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
About LineageOS4MicroG & LineageOS
LineageOS unofficial fork with built-in microG gapps implementation.
Full Play Services compatibility [Well-almost...YMMV]
Our ROM has built-in microG free-as-in-freedom re-implementation of Google's proprietary Android user space apps and libraries. This enables you to use every Google service you need without keeping another closed-source binary blob in your Android system.
Native F-Droid support
LineageOS for microG comes with F-Droid already installed. You can use it to access plenty of FOSS applications or even a Play Store bridge repository like Playmaker or GPlayWeb.
About LineageOS
LineageOS is a free, community built, aftermarket firmware distribution of Android 9 (Pie), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
Learn more at:
LineageOS: https://lineageos.org/
LineageOS4MicroG: https://lineage.microg.org/
Click to expand...
Click to collapse
Rom Built by Bernie_nixKnown issues:
USB-C headphones work for music, watching videos, etc. They don't work in the phone app...yet. (working on this)
Some users report VOIP calls don't work properly. YMMV. Skype, Whatsapp, Nextcloud Talk, working great for me.
Automatic updates not yet implemented but will be in a future build.
You tell me.
Building Requirements
1. A fast PC or VPS account such as Google Compute Engine. Minimum PC recommended requirements are Intel i5 or equivalent, 4 cores 8 threads minimum (more cores and better CPU recommended), 16GB ram, SSD and 300GB free drive space minimum, fast internet connection (you will download over 30GB of sources).
2. Ubuntu 18.04 is supported here. If you use Windows or another version of Linux, let others know of your tweaks and workarounds.
3. Patience and time. Downloading sources, setting up and building a rom will take hours if not days (depending on your PC hardware and internet speed).
Environment Setup & Build1. Install Docker on Ubuntu (run each command once in terminal)
Code:
sudo apt-get update
sudo apt install docker.io
sudo systemctl start docker
sudo systemctl enable docker
2. Test that docker is running (run command in terminal)
Code:
docker run hello-world
You should see something like this, "docker run hello-world Unable to find image 'hello-world:latest' locally latest: Pulling from library/hello-world ca4f61b1923c: Pull complete Digest: sha256:ca0eeb6fb05351dfc8759c20733c91def84cb8007aa89a5bf606bc8b315b9fc7 Status: Downloaded newer image for hello-world:latest Hello from Docker! This message shows that your installation appears to be working correctly. ..."
3. Pull lineageos4microg docker onto your pc (run command in terminal)
Code:
docker pull lineageos4microg/docker-lineage-cicd
4. After pull is complete, create the following directories in your home/YOURUSERNAME directory
lineageos4microg
lineageos4microg/src
lineageos4microg/ccache
lineageos4microg/local_manifests
lineageos4microg/keys
lineageos4microg/logs
lineageos4microg/zips
So it might look something like this: home/JoeAndroid/lineageos4microg
5. Copy the 4 attached xml files (bottom of this post) to your local_manifests folder
These are: ocean.xml, include_proprietary.xml, proprietary.xml, and custom_packages.xml
6. In terminal, cd into the lineage4microg folder, and copy and paste the following commands all at once after changing YOURUSERNAME to your username in ubuntu. For an explanation of options, see the link at bottom of post. This code will download sources, sync your repos with newest updates and start your build. This step could take hours. It is downloading sources, syncing repos and building your rom!
Code:
sudo docker run \
-e "BRANCH_NAME=lineage-16.0" \
-e "DEVICE_LIST=ocean" \
-e "SIGN_BUILDS=true" \
-e "SIGNATURE_SPOOFING=restricted" \
-e "WITH_SU=true" \
-e "CUSTOM_PACKAGES=GmsCore GsfProxy FakeStore MozillaNlpBackend NominatimNlpBackend com.google.android.maps.jar FDroid FDroidPrivilegedExtension " \
-e "INCLUDE_PROPRIETARY=false" \
-v "/home/YOURUSERNAME/lineageos4microg/lineage:/srv/src" \
-v "/home/YOURUSERNAME/lineageos4microg/zips:/srv/zips" \
-v "/home/YOURUSERNAME/lineageos4microg/logs:/srv/logs" \
-v "/home/YOURUSERNAME/lineageos4microg/cache:/srv/ccache" \
-v "/home/YOURUSERNAME/lineageos4microg/keys:/srv/keys" \
-v "/home/YOURUSERNAME/lineageos4microg/manifests:/srv/local_manifests" \
lineageos4microg/docker-lineage-cicd
7. Your build should be in the zips folder when complete! Flash in twrp/ofox.
8. If your build fails, check the log in lineageos4microg/logs/ocean folder. If you receive the following error, "Can not locate config makefile for product "lineage_ocean"" you will need to copy the 4 xmls from lineageos4microg/local_manifests to lineageos4microg/manifests.
References and links:
https://phoenixnap.com/kb/how-to-install-docker-on-ubuntu-18-04
https://github.com/lineageos4microg/docker-lineage-cicd
Telegram group for additional ROMS, files and support: https://t.me/mG7Power
Thanks to Dark98, Electimon, Barry and many others for initial help and repos when building this rom.
Reserved #1
Reserved #2
Thanks, been wanting to try to build this.
I tried am running this on ubuntu 18.04 vm, followed all the instructions.
after I type in the docker commands get this after a few minutes:
sed:can't read build/core/version_defaults.mk:no such file or directory
can't detect the android version.
Any suggestions?
skalnas said:
Thanks, been wanting to try to build this.
I tried am running this on ubuntu 18.04 vm, followed all the instructions.
after I type in the docker commands get this after a few minutes:
sed:can't read build/core/version_defaults.mk:no such file or directory
can't detect the android version.
Any suggestions?
Click to expand...
Click to collapse
Can you take a picture of the screenshot including how you typed in the commands? Need a bit more info
I just pasted the code changing username screenshot attached
skalnas said:
I just pasted the code changing username screenshot attached
Click to expand...
Click to collapse
I wonder if it's related to "steve" in your build commands but your username is Steven on the VM?
Bernie_nix said:
I wonder if it's related to "steve" in your build commands but your username is Steven on the VM?
Click to expand...
Click to collapse
I did rerun the script with the username steven and it appeared to be working.
went to bed and when i woke up I was excited to see it said build completed. however i could not
find the zip file in the zips folder. looking at the logs error: Can not locate config makefile for product "lineage_ocean".
I saw in the op to move the 4 xml files to manifests dir, however I had gotten permission denied when trying to
copy to the manifests dir. i deleted the dir, recreated the dir and moved the files.
I am going to try building again.
skalnas said:
I did rerun the script with the username steven and it appeared to be working.
went to bed and when i woke up I was excited to see it said build completed. however i could not
find the zip file in the zips folder. looking at the logs error: Can not locate config makefile for product "lineage_ocean".
I saw in the op to move the 4 xml files to manifests dir, however I had gotten permission denied when trying to
copy to the manifests dir. i deleted the dir, recreated the dir and moved the files.
I am going to try building again.
Click to expand...
Click to collapse
You need to sudo cp -R (drag 4 files to terminal here) /YOURUSERNAME/lineageos4microg/manifests. Then re run script
Bernie_nix said:
You need to sudo cp -R (drag 4 files to terminal here) /YOURUSERNAME/lineageos4microg/manifests. Then re run script
Click to expand...
Click to collapse
Thanks for the assistance, I am new to linux, hence the vm. My PC is amd fx8350 chip 8 core, 16 gb ram on win10 pro 64 bit on
PNY 480 gb ssd drive.
Just a few questions: The vm i set up to build this I set at 150gb. Prior to syncing the repos and running
the build script again i had about 135 gb free. It's been on starting build for ocean lineage-16.0 branch
for about 5 hours.
Should it have completed or thrown an error by now?
Also, lineageos4microg folder states it's using 57gb, I now have 32 gb free space 5 hours into build.
Not sure if I should keep waiting to see if build completes?
I have attached the log which i think is for the build in progress.
Thanks again
skalnas said:
Thanks for the assistance, I am new to linux, hence the vm. My PC is amd fx8350 chip 8 core, 16 gb ram on win10 pro 64 bit on
PNY 480 gb ssd drive.
Just a few questions: The vm i set up to build this I set at 150gb. Prior to syncing the repos and running
the build script again i had about 135 gb free. It's been on starting build for ocean lineage-16.0 branch
for about 5 hours.
Should it have completed or thrown an error by now?
Also, lineageos4microg folder states it's using 57gb, I now have 32 gb free space 5 hours into build.
Not sure if I should keep waiting to see if build completes?
I have attached the log which i think is for the build in progress.
Thanks again
Click to expand...
Click to collapse
Not recommended to run in a VM as it will take considerably longer to build but if you have the time (hours, days). As far as hard drive space, 150gb is cutting it very close. Better to have 250gb minimum. Don't know if you'll have enough. As far as your log and actual build, it's building! Congrats. If you scroll down to the bottom of your log, you'll see it's at 23%.
Bernie_nix said:
Not recommended to run in a VM as it will take considerably longer to build but if you have the time (hours, days). As far as hard drive space, 150gb is cutting it very close. Better to have 250gb minimum. Don't know if you'll have enough. As far as your log and actual build, it's building! Congrats. If you scroll down to the bottom of your log, you'll see it's at 23%.
Click to expand...
Click to collapse
Yes, as I feared i did run out space, but at least I know it was building. I may try to install ubuntu in a dual boot.
Thanks
skalnas said:
Yes, as I feared i did run out space, but at least I know it was building. I may try to install ubuntu in a dual boot.
Thanks
Click to expand...
Click to collapse
Awww... Well I had that happen before. Even if you have an old platter hdd (not ssd) as long as it's got the GBs of space it will take a little longer to build but for these purposes will do just fine. I use both SSD and hdds to build.
Got my dual boot set up. First tried Ubuntu but it kept locking up, went with Linux mint. Got a 250 GB partition, going to give it another go tommorow.
View attachment 4980819well, after switching from VM to dual boot, I gave it another go, and i got a msg in linux mint that i ran out of space about 3 1/2 hrs into build. I had set up 250gb partition as you suggested. I did 30gb root, 220 GB home,4 GB swap.
Can you take a look at the logs, i'm not clear looking at logs how much of build completed.
There was the zip file about 604 mb in the zips folder, which I could open(along with an sha and md5 files, which i dont know anything about.) I'm thinking possibly the build completed despite the warning in linux about running of free space.
I shrank the /root partition in gparted to 20gb and tried to extend the extra 10gb to home, but i couldn't.
Is it possible to specify 25gb ccache in the docker script somehow so that instead of the 50 it seems to allocate, maybe that will solve the space issue?
Thanks again, looks like progress.
Freed up some more space for build, now when trying to sync repos i get this msg Missing "vendor/lineage", aborting.
suggestions?
skalnas said:
Freed up some more space for build, now when trying to sync repos i get this msg Missing "vendor/lineage", aborting.
suggestions?
Click to expand...
Click to collapse
I looked at the last lines in your log... it looks like it built. Did you check your zips folder?
boot.img already exists, no need to overwrite...
dtbo.img already exists, no need to overwrite...
system.img already exists, no need to overwrite...
vendor.img already exists, no need to overwrite...
Total of 704512 4096-byte output blocks in 23 input chunks.
Total of 147456 4096-byte output blocks in 13 input chunks.
done.
Click to expand...
Click to collapse
Where is "Missing "vendor/lineage", aborting." appearing?
Bernie_nix said:
I looked at the last lines in your log... it looks like it built. Did you check your zips folder?
Where is "Missing "vendor/lineage", aborting." appearing?
Click to expand...
Click to collapse
Thanks, yes there was a zip there, wasnt sure if it was safe to flash, with the error space ran out ,but figured build did complete, as the zip wasnt corrupted.
As far as repo error:
"OSError: [Errno 17] File exists: '/srv/src/LINEAGE_16_0/device/generic/mini-emulator-arm64/.git.tmp'
error: Cannot checkout bernie-nix/android_device_motorola_sdm632-common-1: ManifestInvalidRevisionError: revision lineage-16.0 in bernie-nix/android_device_motorola_sdm632-common-1 not found
error: in `sync -c --force-sync`: revision lineage-16.0 in bernie-nix/android_device_motorola_sdm632-common-1 not found.
I did switch to the ocean.xml listed in your other thread posted by dark98 and the repo did sync., but I didn't proceed with the build.
Thanks again for all your help, think i will try to dirty flash my succesful build over yours, unless i should clean flash.
skalnas said:
Thanks, yes there was a zip there, wasnt sure if it was safe to flash, with the error space ran out ,but figured build did complete, as the zip wasnt corrupted.
As far as repo error:
"OSError: [Errno 17] File exists: '/srv/src/LINEAGE_16_0/device/generic/mini-emulator-arm64/.git.tmp'
error: Cannot checkout bernie-nix/android_device_motorola_sdm632-common-1: ManifestInvalidRevisionError: revision lineage-16.0 in bernie-nix/android_device_motorola_sdm632-common-1 not found
error: in `sync -c --force-sync`: revision lineage-16.0 in bernie-nix/android_device_motorola_sdm632-common-1 not found.
I did switch to the ocean.xml listed in your other thread posted by dark98 and the repo did sync., but I didn't proceed with the build.
Thanks again for all your help, think i will try to dirty flash my succesful build over yours, unless i should clean flash.
Click to expand...
Click to collapse
Yes, use the other xml if you want. They should both be about the same...you might even get updated sources, you might not...but it should build. I looked at the error above. The only suggestion I would make in your current xml if you want to continue using it is to remove revision="lineage-16.0" on the bernie-nix/android_device_motorola_sdm632-common-1 entry. As far as the zip that completed, how big is it?
Bernie_nix said:
Yes, use the other xml if you want. They should both be about the same...you might even get updated sources, you might not...but it should build. I looked at the error above. The only suggestion I would make in your current xml if you want to continue using it is to remove revision="lineage-16.0" on the bernie-nix/android_device_motorola_sdm632-common-1 entry. As far as the zip that completed, how big is it?
Click to expand...
Click to collapse
The zip was 604mb, i did successfully flash it, thanks again for your help and guide building my first rom!
so the xml file should be edited to:
<project name="bernie-nix/android_device_motorola_sdm632-common-1" path="device/motorola/sdm632-common" remote="github"/>
?
btw, i don't see your repos on github anymore.