• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [ROM] KANAIDA - Shang Tsung 1 (ICS 4.0.4)

This guy has complied a kernel could it be used for this Rom are u guys working on cm9 or aosp or a pure Rom based off ics for lucid
 
Right now, I have no idea if my kernel boots, I just know it compiled correctly. I am gonna build an AOSP ROM to test it. It did not boot with this ROM, but then again, this ROM is 4.0.4, my kernel is 4.0.3
 
Right now, I have no idea if my kernel boots, I just know it compiled correctly. I am gonna build an AOSP ROM to test it. It did not boot with this ROM, but then again, this ROM is 4.0.4, my kernel is 4.0.3

All I have to say is I really appreciate what your doing that's a trillion
 
Also, in case anyone is interested, here is a copy of my build report for the Kernel compiling

[HIGH]Build system specs:
* Dell Latitude C800
* Intel Pentium IV Single-core Processor
* 512 MB RAM
* Ubuntu 10.04.4 LTS (x86)
* Android NDK Version r5c



This message printed each compile, however, it never resulted in an error.

lge/com_device/input/Kconfig:110:warning: defaults for choice values not supported
lge/com_device/input/Kconfig:117:warning: defaults for choice values not supported
lge/com_device/input/Kconfig:123:warning: defaults for choice values not supported
lge/com_device/input/Kconfig:129:warning: defaults for choice values not supported
lge/com_device/input/Kconfig:136:warning: defaults for choice values not supported
warning: (BCMDHD_HOSTWAKEUP_USE_GPIO) selects BCMDHD_HW_OOB which has unmet direct dependencies (NETDEVICES && WLAN && BCMDHD_B2 && BCMDHD_HOSTWAKEUP_USE_GPIO)
warning: (BCMDHD_HOSTWAKEUP_USE_GPIO) selects BCMDHD_HW_OOB which has unmet direct dependencies (NETDEVICES && WLAN && BCMDHD_B2 && BCMDHD_HOSTWAKEUP_USE_GPIO)




BUILD 0001 (Start Time 4:10 AM EST 20 December 2012 :: Finish Time 4:25 AM EST 20 December 2012)
FAILED

lge/factory/lg_diag_testmode.o
lge/factory/lg_diag_testmode.c:19:56: error: ../../kernel/arch/arm/mach-msm/smd_private.h: No such file or directory
lge/factory/lg_diag_testmode.c: In function 'LGE_Dload_SRD':
lge/factory/lg_diag_testmode.c:2412: error: 'SMEM_ERR_CRASH_LOG' undeclared (first use in this function)
lge/factory/lg_diag_testmode.c:2412: error: (Each undeclared identifier is reported only once
lge/factory/lg_diag_testmode.c:2412: error: for each function it appears in.)
make[2]: *** [lge/factory/lg_diag_testmode.o] Error 1
make[1]: *** [lge/factory] Error 2
make: *** [lge] Error 2


BUILD 0002 (Start Time 4:39 AM EST 20 December 2012 :: Finish Time 4:52 AM EST 20 Devember 2012)
FAILED

make[3]: *** No rule to make target `lge/lge_board/cayman_mpcs/board_cayman_mpcs.o', needed by `lge/lge_board/cayman_mpcs/built-in.o'. Stop.
make[2]: *** [lge/lge_board/cayman_mpcs] Error 2
make[1]: *** [lge/lge_board] Error 2
make: *** [lge] Error 2


BUILD 0003 (Start Time 4:57 AM EST 20 December 2012 :: Finish Time 7:02 AM 20 December 2012)
SUCCESS

Does not boot with Kanaida Rom
[/HIGH]
 
I see whats wrong partly, you have MTD as the filesystem, its ext4/emmc, so the mount lines need to be:
Code:
mount("ext4", "EMMC", "/dev/block/mmcblk0p28", "/data");
mount("ext4", "EMMC", "/dev/block/mmcblk0p26", "/system");
mount("ext4", "EMMC", "/dev/block/mmcblk0p27", "/cache");
and for the boot.img:
Code:
package_extract_file("boot.img", "/dev/block/mmcblk0p8");
;)

Edit: My mentioned changes fixes the updater-script so it installs, unfortunately it doesnt boot. ;)

He PG, if I upload the output folders for the kernel and the android build, can you pack them properly? I think that's where I went wrong. Unless their defconfig was really non-functional all together (sure hope not)
 
Right now, I have no idea if my kernel boots, I just know it compiled correctly. I am gonna build an AOSP ROM to test it. It did not boot with this ROM, but then again, this ROM is 4.0.4, my kernel is 4.0.3
Doesnt matter n technically incorrect, kernel doesnt care what platform the os is n your kernel is most likely a 3.0.8. All you need is a known working rom, if u get past the lg screen, chances are the kernel boots, if not the kernel is most likely at fault.






He PG, if I upload the output folders for the kernel and the android build, can you pack them properly? I think that's where I went wrong. Unless their defconfig was really non-functional all together (sure hope not)
its not in the packing, most likely its your kernel.

You & Eagle put your src on github. Push a untouched src first, then your changes on the next commit, and i will try to look em over. My guess is there is alot of connect specific stuff missing in the src, mainly board related.
 
Doesnt matter n technically incorrect, kernel doesnt care what platform the os is n your kernel is most likely a 3.0.8. All you need is a known working rom, if u get past the lg screen, chances are the kernel boots, if not the kernel is most likely at fault.






its not in the packing, most likely its your kernel.

You & Eagle put your src on github. Push a untouched src first, then your changes on the next commit, and i will try to look em over. My guess is there is alot of connect specific stuff missing in the src, mainly board related.

Hey PG,

I think you might be onto something about us working this out together. I am preparing all my sources for upload to GitHub as we speak. I would love to be able to do this on my own, but you are offering a lerning experience that I would be a fool to refuse.

Sent from my LG-MS840 using Tapatalk
 
Hey PG,

I think you might be onto something about us working this out together. I am preparing all my sources for upload to GitHub as we speak. I would love to be able to do this on my own, but you are offering a lerning experience that I would be a fool to refuse.

Sent from my LG-MS840 using Tapatalk
Well I'm offering input on it atm. lol

Unfortunately the powers to be (life and related BS) have me in a purdy bad spot atm and though I still have use of my computer, I am unable to compile large scale atm. Thinking I should be able to handle a kernel tho. lol

Have a few things in the works that will help short term (a kickass laptop), and continuing to work on the long term. ;) can knock me down, but its hard to keep me down. ;)
 
Well I'm offering input on it atm. lol

Unfortunately the powers to be (life and related BS) have me in a purdy bad spot atm and though I still have use of my computer, I am unable to compile large scale atm. Thinking I should be able to handle a kernel tho. lol

Have a few things in the works that will help short term (a kickass laptop), and continuing to work on the long term. ;) can knock me down, but its hard to keep me down. ;)

Well, I appreciate it. I hopefully will be getting a new computer after the first of the year for school. In the meantime, I am having problems building android. I keep getting invalid pointer errors in a file called rateest.c, so bleh :confused:

Sent from my LG-MS840 using Tapatalk
 
Well, I appreciate it. I hopefully will be getting a new computer after the first of the year for school. In the meantime, I am having problems building android. I keep getting invalid pointer errors in a file called rateest.c, so bleh :confused:

Sent from my LG-MS840 using Tapatalk
well if you're still trying to compile 4.0+ on 32bit you will get all sorts of errors. ;)

With your new system, make sure its 64bit (almost everything is now), at least 8GB of RAM preferred 16GB or more. 6 to 8 cores is preferred but you can get by with a good quad core too. And plenty of hdd space, and I really recommend it be a desktop. Laptops are nice and have their purposes, hard core compiling isn't one of em those for your avg affordable laptop. ;)
 
well if you're still trying to compile 4.0+ on 32bit you will get all sorts of errors. ;)

With your new system, make sure its 64bit (almost everything is now), at least 8GB of RAM preferred 16GB or more. 6 to 8 cores is preferred but you can get by with a good quad core too. And plenty of hdd space, and I really recommend it be a desktop. Laptops are nice and have their purposes, hard core compiling isn't one of em those for your avg affordable laptop. ;)

Well, the computer I am looking at is a Samsung 3 Series laptop (I need something I can take with me for now) quad core i5, 6gb ram, 750gb SSD, 64-bit Win8 included (which of course will be replaced with linux)

Sent from my LG-MS840 using Tapatalk
 
I just asked for some recommendations on what kind of laptop I should get lmao! So not only did I get some help from my post but you guys just gave me more information without even knowing it lol! So thx :D
 
Well, the computer I am looking at is a Samsung 3 Series laptop (I need something I can take with me for now) quad core i5, 6gb ram, 750gb SSD, 64-bit Win8 included (which of course will be replaced with linux)

Sent from my LG-MS840 using Tapatalk
dualboot will work if you need windows too. Should do ok, tho continuous use for compiling will shorten its life considerably lol
 
I just asked for some recommendations on what kind of laptop I should get lmao! So not only did I get some help from my post but you guys just gave me more information without even knowing it lol! So thx :D
lol, well my current desktop is a AMD Phenom 1100T 3.3Ghz 6x, 16GB RAM, 2x 1 TB hdd, GTX460 video card. It takes me about 30-40min to compile CM9/10, a matter of minutes for kernels. ;)
 
dualboot will work if you need windows too. Should do ok, tho continuous use for compiling will shorten its life considerably lol

Well I am a power user, so my computers tend not to last too terribly long anyway lol

Sent from my LG-MS840 using Tapatalk
 
Well here goes nothing, I am about to flash CM9 for the Viper with my kernel. If it works and I lose 4g nobody will know until monday when I have internet access again.

Sent from my LG-MS840 using Tapatalk
 
Back
Top Bottom