yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 3 General] Restl3ss:
So I've already said this to [MENTION=5864662]moonbutt74[/MENTION] but I feel I should post here for all; this is mostly speculation but I believe that in the new 4.4 tw firmware SELinux is wholly disabled, perhaps via a dummy policy

Consider that in other Samsung devices (namely the galaxy phones) in settings/about on a 4.4 firmware there's the string "SE for android" stating permissive / enforcing / disabled. That string is completely absent in our new 4.4 ROM.

I'd also like to state an observation, in that the overall Linux version of the new kernel has not changed from the 4.2 firmware, being that it's still 3.4.34. Once again in other Samsung updates we usually see an update to around 3.4.7x / 3.4.8x for touchwiz, and with current cm11 on my s3 being at 3.4.103.

It's very possible that Samsung had the same problem we are and simply decided to circumvent it.
[Galaxy Tab 3 General] Hazou:
Android Houdini translate ARM to x86 code on the fly. If the system asks for a library that is exclusively ARM build then libhoudini tries to translate those arm codes into x86 code when used. Like JIT, but then this is also in it, it even loads from dalvik. If successful the library loads and can be used. But sometimes the library contains code that libhoudini doesn't understand and then it doesn't work. Luckily for us most new apps/libraries are also build for x86.
[Galaxy Tab 3 General] r2d23cpo:
[MENTION=4479363]Hazou[/MENTION]

Nice I will test that option by loading later the ARM Libraries in a clean build. I was not expecting Android os libraries to woke on Houdini!

But I have to say that I do not need you guys with the help in compiling. As it turn out, it is very simple to compile the kernel and the ko modules. In fact I plan to add that to my old tread SGT3 10.1 Rom Developing by learning developers. It should be a nice starting lesson.

I have not tested yet but will report CIFS as soon as I can.
[Galaxy Tab 3 General] :
Hazou ! :cool:

quick question, i am having trouble pointing to gralloc_priv.h

what does example 1 do as opposed to example 2

1

#include "gralloc_priv.h

2

# include <gralloc_priv.h>

m :confused:

yup, cool and confused ! :silly:
[Galaxy Tab 3 General] Hazou:
Can't explain it better than this:https://gcc.gnu.org/onlinedocs/gcc-4.1.2/cpp/Include-Syntax.html

<> is for all files that are in standardized file paths like the GCC ones and kernel if I am correct and some 'include' maps

"" is for files that are called from the Android.mk, the folder where the main file is located and will search for <> if it can't find.

So in almost all cases, "" is the one to go for.

Verstuurd van mijn GT-P5110
[Galaxy Tab 3 General] :
Hazou,

hey hey,

thanks so much, added link to my signature for quick reference. :good:

m
[Galaxy Tab 3 General] :
hey hey

hey guys,

i was wondering if we could run a checkin of where things are in this project.

i needed to move to something different to gain a little more know-how.

i am now setting myself up for integrated kernel building in an attempt

to define our own sepolicy. so far it's going clunky but i'm working things out.

when i remember which build i just finished , the one that stutters at bootanimation

but seems to be picking up the hardware i will post.

m
[Galaxy Tab 3 General] chchia:
i know how to use odin and i willing to sign up for P5220 tester, thank you!
[Galaxy Tab 3 General] :
cm11-gt-p5210 W.I.P. test 2 DEVS ONLY

okay so this is round 2 with the new kernel source for gt-p5210 kk 4.4.2

i am fairly certain the hang up lies in the correct configuration of the boot.img .rc's fstab mount flags and options all in order to

get /data mounting as it should the boot.img goes with this for adb root access. i had to fight a bit with getting this uploaded

so i hope it hasn't corrupted . if so notify me immediately and i will pull it and reup' which at my interenet speed will take a day. :crying:

rom - http://d-h.st/ma1 - the name of the file is cm_santos10wifi-WIP-round2.zip

boot.img - http://d-h.st/aqJ - the name of the file is - cm11-kernel-rework-for-adb-root.zip

so let logcat this thing and see if we can get it up and going.

m

issues - stays stuttering at bootanimation, /data creates but resists mounting correctly - when performing a manual remount via adb shell

/data disappears. :confused: i am beginning to agree with restl3ss on selinux. so hacking at the .rc's would be where to start i guess.
[Galaxy Tab 3 General] bithunter_99:
n1ce.. is it possible to make a rom for my p5200?
[Galaxy Tab 3 General] Hazou:
I assume you are using the ramdisk from the stock firmware. If so, keep in mind that you need to disable somethings in the init.rc, because they are already set in the init.common.rc or others if u have those.

If not, use the ramdisk from stock and add the things from CM in there and it most likely will boot. Did that in cm10.1 and don't think that will change in cm11, because they are based on basic android.
[Galaxy Tab 3 General] :
Hazou,

hey hey, in answer to your question no and yes the device rc's i dropped in afterwards and am trying to stitch them in that way.

i'm researching mount flags and options. it's basically the same rom build from test1 just using the new kernel source.

very different result :confused: . so i posted it for tinkering and resynced, sunc, sanc ? :silly:

build again . :good:

m
[Galaxy Tab 3 General] Hazou:
Can you post the stock ramdisk in zip format. Can't open boot.img right now :P I like to have a look
[Galaxy Tab 3 General] :
Sure, not a problem :good:

this is the ramdisk for the gt-p5210 KK stock kernel . [mostly stock, cifs enabled]
[Galaxy Tab 3 General] Hazou:
Integrated kernel building should work just fine without trevd's patch. With trevd's patch and some more modifications (which i already have done, can upload the new patch if u want) u only get 3 new features in it. U can build with ccache active (speeds up kernel building with 63% on my pc), u can use custom toolchain (not needed) and the modules will be striped of extra code (before it gives an warning because it want to strip arm code, while it is x86 code so can't handle the request).

But in the near future CM will need to adjust there methods, because ccache is only supported on ARM now, while every toolchain can use it. And we get x64 support on ARM and x86. I am already trying to rewrite it a bit for my self at the moment.

just get the kernel code in kernel/(vendor)/(device) (so after (device) comas all those maps and files) and set the defconfig in boardconfig.mk. Maybe u also will need to specify the kernel image, in my case bzImage. It will automatically build with the i686-4.7 toolchain.
[Galaxy Tab 3 General] Angel_666:
Just downloaded official Odin new KK for p5200 (italy), and see the new intel atom firmware file and new bootloader files in package. Are that files present in p5210 fw? Coz that files can change lot of things in our device.
[Galaxy Tab 3 General] :
Angel,

can you post a list.txt and i'll take a look ?

m
[Galaxy Tab 3 General] Angel_666:
<ID:0/003> [B][COLOR="Red"]sboot.bin[/COLOR][/B]
<ID:0/003> [COLOR="red"]dnx_fwr.bin[/COLOR]
<ID:0/003> [COLOR="red"]iafw.bin[/COLOR]
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> modem.bin
<ID:0/003> cache.img
<ID:0/003> hidden.img]

Here. I marked important new files. Btw. i can see lot of changes and new settings in new FW, why people say, that only keyboard is changed?:D
[Galaxy Tab 3 General] :
Suspicious

Angel,

do what restl3ss did and pull only system.img and boot.img. Pack them for odin flash or re-use the 5210-ota-zip and flash that way.Test.

sboot.bin looks REALLY SHADY .

As for the things people say, they don't do their research, or have no interest beyond convenience. :rolleyes:

m
[Galaxy Tab 3 General] Angel_666:
Yes. I know what to do. The point is that this files can change very impotant things in our hw. I will check new bootloader and see what is changed.As for iafw.bin - it's a new fw file for our processor controller. If Samsung released new fw file, i think they have a seriosly reason for that.

UPD: Yes. They change platform config in IntelAtom fw file, also they change some boot memory adresses.
[Galaxy Tab 3 General] bithunter_99:
if i read that, i don't like to flash Samsung 4.4.2 on my p5200. I have a german DBT tab and it is the spain file available
[Galaxy Tab 3 General] Pitey:
hey guys, i would like to help with the rom developement

i don't know much about android rom developement, but i know how to linux and i managed to build cm11 for mako on my own. so if someone would show me a few things, especially where to start, i think i'm able to help you ;)
[Galaxy Tab 3 General] social-design-concepts:
Maybe you can explained examining the ifwi , well I guess Sammy is calling it iafw.
[Galaxy Tab 3 General] :
Roar !!! Growl !!!!

:silly: THIS IS DRIVING ME MAD !!!!!!

okay so, new build and i am still hanging on this

E/IMGSRV ( 1884): :0: PVRDRMOpen: TP3, ret = 3

E/IMGSRV ( 1884): :0: SetupuKernel : EDM status value DevVAddr: 0xF4005000 pvLinAddrKM: 0x0xf23b7000

knowing what it means would be awesomely helpful ! i've included the portion of the logcat that interests me.

don't care too much about audio right now.

you will notice that /data seems to be mounting.

using stock ramdisk setup whith my current builds of kernel/modules

sticking my head in blender. (whiirrrrrrr)

MAD !!!!!!!!!
[Galaxy Tab 3 General] Angel_666:
This error is present in official build too. It's not critical.

This two errors are critical. And one more thing - delete unneeded samsung libs, or add they dependencies. For example:
[Galaxy Tab 3 General] :
it seems to be an issue.

D/libEGL ( 1889): loaded /vendor/lib/egl/libGLESv1_CM_POWERVR_SGX544_115.so

D/libEGL ( 1889): loaded /vendor/lib/egl/libGLESv2_POWERVR_SGX544_115.so

E/IMGSRV ( 1889): :0: PVRDRMOpen: TP3, ret = 14

E/IMGSRV ( 1889): :0: PVRDRMOpen: TP3, ret = 15

E/IMGSRV ( 1889): :0: PVRDRMOpen: TP3, ret = 16

E/IMGSRV ( 1889): :0: PVRDRMOpen: TP3, ret = 16

E/IMGSRV ( 1889): :0: PVRDRMOpen: TP3, ret = 16

E/IMGSRV ( 1889): :0: PVRDRMOpen: TP3, ret = 18

D/hwcomposer( 1889): bool IntelHWComposerDrm::drmInit(): successfully. mDrmFd 19

I/ServiceManager( 1889): Waiting for service display.intel.mds...

E/IMGSRV ( 1889): :0: PVRDRMOpen: TP3, ret = 24

I/hwcomposer( 1889): Sprite count: 0, Primary count: 2, Overlay count: 1

I/hwcomposer( 1889): PixelFormatConverter: initialized

I/SurfaceFlinger( 1889): Using composer version 1.3

I/SurfaceFlinger( 1889): EGL informations:

I/SurfaceFlinger( 1889): vendor : Android

I/SurfaceFlinger( 1889): version : 1.4 Android META-EGL

I/SurfaceFlinger( 1889): extensions: EGL_KHR_get_all_proc_addresses EGL_ANDROID_presentation_time EGL_KHR_image EGL_KHR_image_base EGL_KHR_gl_texture_2D_image EGL_KHR_gl_texture_cubemap_image EGL_KHR_gl_renderbuffer_image EGL_KHR_fence_sync EGL_KHR_create_context EGL_ANDROID_image_native_buffer EGL_KHR_wait_sync EGL_ANDROID_recordable

I/SurfaceFlinger( 1889): Client API: OpenGL_ES

I/SurfaceFlinger( 1889): EGLSurface: 8-8-8-8, config=0xf

F/libc ( 1889): Fatal signal 11 (SIGSEGV) at 0x00000000 (code=1), thread 1889 (surfaceflinger)

fatal error libc.

m
[Galaxy Tab 3 General] Angel_666:
I'm on official build now, and all works fine. Your errors are in surfaceflinger and in libc. When i build CM11 my errors was in mediaserver and libc too. Try to disable HW acceleration and use android SW graphics in Egl.cfg. See the errors in logcat.
[Galaxy Tab 3 General] :
on a rom that doesn't boot, how ?

does this work

remove the line:

0 0 android
[Galaxy Tab 3 General] Angel_666:
You need to remove PoverVR544 line and use 0 0 android only. What CM version you building? 4.4.2 or 4.4.4?
[Galaxy Tab 3 General] :
i'm building 4.4.4 , the egl problems came with the new kernel.

using the old kernel i "upgraded" - enabled selinux and default security module dac

and display up.

new source = nope

after change

I/SurfaceFlinger( 1891): SurfaceFlinger is starting

I/SurfaceFlinger( 1891): SurfaceFlinger's main thread ready to run. Initializing graphics H/W...

D/libEGL ( 1891): loaded /vendor/lib/egl/libEGL_POWERVR_SGX544_115.so

D/gpsd ( 1902): WakeLock(Release,GPSD)

I/gpsd_d ( 1902): GNSS: 204752

D/libEGL ( 1891): loaded /vendor/lib/egl/libGLESv1_CM_POWERVR_SGX544_115.so

D/libEGL ( 1891): loaded /vendor/lib/egl/libGLESv2_POWERVR_SGX544_115.so

E/IMGSRV ( 1891): :0: PVRDRMOpen: TP3, ret = 14

E/IMGSRV ( 1891): :0: PVRDRMOpen: TP3, ret = 15

E/IMGSRV ( 1891): :0: PVRDRMOpen: TP3, ret = 16

E/IMGSRV ( 1891): :0: PVRDRMOpen: TP3, ret = 16

E/IMGSRV ( 1891): :0: PVRDRMOpen: TP3, ret = 16

E/IMGSRV ( 1891): :0: PVRDRMOpen: TP3, ret = 18

D/hwcomposer( 1891): bool IntelHWComposerDrm::drmInit(): successfully. mDrmFd 19

I/ServiceManager( 1891): Waiting for service display.intel.mds...

E/IMGSRV ( 1891): :0: PVRDRMOpen: TP3, ret = 24

I/hwcomposer( 1891): Sprite count: 0, Primary count: 2, Overlay count: 1

I/hwcomposer( 1891): PixelFormatConverter: initialized

I/SurfaceFlinger( 1891): Using composer version 1.3

I/SurfaceFlinger( 1891): EGL informations:

I/SurfaceFlinger( 1891): vendor : Android

I/SurfaceFlinger( 1891): version : 1.4 Android META-EGL

I/SurfaceFlinger( 1891): extensions: EGL_KHR_get_all_proc_addresses EGL_ANDROID_presentation_time EGL_KHR_image EGL_KHR_image_base EGL_KHR_gl_texture_2D_image EGL_KHR_gl_texture_cubemap_image EGL_KHR_gl_renderbuffer_image EGL_KHR_fence_sync EGL_KHR_create_context EGL_ANDROID_image_native_buffer EGL_KHR_wait_sync EGL_ANDROID_recordable

I/SurfaceFlinger( 1891): Client API: OpenGL_ES

I/SurfaceFlinger( 1891): EGLSurface: 8-8-8-8, config=0xf

F/libc ( 1891): Fatal signal 11 (SIGSEGV) at 0xf404c000 (code=1), thread 1891 (surfaceflinger)
[Galaxy Tab 3 General] Angel_666:
Strange.. On new kernel and 4.4.4 display work fine for me. Surfaceflinger and opengl initializing successfuly and device hang only on "applications update" window:

My errors are:
[Galaxy Tab 3 General] :
groovy, can you post your boot.img?

[MENTION=1649190]Angel_666[/MENTION] strings

root@kali:~/Downloads/gtp5210-cm11builds# strings mediaserver | grep "\.so"

libaudioflinger.so

libcameraservice.so

libmedialogservice.so

libcutils.so

libnbaio.so

libmedia.so

libmediaplayerservice.so

libutils.so

liblog.so

libbinder.so

libc.so

libstdc++.so

libm.so

root@kali:~/Downloads/gtp5210-cm11builds#
[Galaxy Tab 3 General] Angel_666:
The point is that i don't change anything in stock bootimg (initramfs). Just add and replace new modules from your building kernel and add cm.init.rc
[Galaxy Tab 3 General] :
no change, same hang, running new build
[Galaxy Tab 3 General] :
on where your hanging, do you get that before or after the cm setup wizard ?

i also read somewhere on xda about a bug that is similar with respect to .odex being present in /data

maybe something helpful ?
[Galaxy Tab 3 General] Angel_666:
It's before the wizard, right after CM boot logo. Mediaserver crashing and system hanging. Trying to apply some patches to prevent this..
[Galaxy Tab 3 General] Restl3ss:
[MENTION=1649190]Angel_666[/MENTION]

You're on the new Touchwiz 4.4 build and you mentioned a couple of files. Curiosity's sake, when you go to settings / about is there a string there partaining to SELinux?

I have a theory to test.
[Galaxy Tab 3 General] Restl3ss:
[MENTION=1649190]Angel_666[/MENTION]

Also, if you've built CM11 for the P5200 could you possibly send me the meta-inf folder from otapackage? Need a functioning updater-script for the 3g model that works for 4.4
[Galaxy Tab 3 General] :
Restl3ss,

it's likely you can use the same function in updater script used to write boot.img/recovery.img

for system.img

package_extract_file("system.img", "/dev/block/mmcblk0p##");

which should address the need otherwise to sort out additional symlink functions

works like odin/dd.

m

okay, got selinux disabled and set default security module to unix dac in 4.4 kernel.

boot's stock, will run another build tomorrow.
[Galaxy Tab 3 General] bithunter_99:
i installed the Kitkat-firmware from Orange (spain) on my P5200. My first impression is very fluid. It works..
[Galaxy Tab 3 General] :
5210 kk firmware

Restl3ss,

could you post the recovery.img that came with the new firmware gt-p5210 if there is one ?

thanks

m

okay, rebuilt kernel selinux disable, default security module unix discretionary access controls

the result of mount :victory:

shell@santos10wifi:/ $ mount
rootfs / rootfs rw,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,relatime,mode=750,gid=1000 0 0
none /sys/fs/cgroup/memory cgroup rw,relatime,memory 0 0
tmpfs /storage tmpfs rw,relatime,mode=050,gid=1028 0 0
tmpfs /mnt/secure tmpfs rw,relatime,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/secure/asec tmpfs rw,relatime,mode=700 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p13 /preload ext4 ro,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/mmcblk0p8 /system ext4 ro,relatime,errors=panic,data=ordered 0 0
/dev/block/mmcblk0p6 /cache ext4 rw,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,errors=panic,data=ordered 0 0
/dev/block/mmcblk0p2 /efs ext4 rw,nosuid,nodev,noatime,journal_checksum,journal_async_commit,errors=panic,data=ordered 0 0
/dev/block/mmcblk0p3 /config ext4 rw,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,errors=panic,data=ordered 0 0
[COLOR="Red"]/dev/block/mmcblk0p9 /data ext4 rw,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,errors=panic,data=ordered 0 0[/COLOR]
none /sys/kernel/debug debugfs rw,relatime 0 0
none /proc/sys/fs/binfmt_misc binfmt_misc rw,relatime 0 0
none /dev/memcgrp cgroup rw,relatime,memory 0 0

where it hangs :(

F/libc ( 1897): Fatal signal 11 (SIGSEGV) at 0x00000000 (code=1), thread 1897 [COLOR="Red"](drmserver)[/COLOR]
I/DEBUG ( 1893): pid: 1897, tid: 1897, name: drmserver >>> /system/bin/[COLOR="Red"]drmserver[/COLOR] <<<
I/DEBUG ( 1893): !@dumpstate -k -t -z -d -o /data/log/dumpstate_app_native -m 1897
I/DEBUG ( 1893): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 1893): Build fingerprint: 'SGT3_Intel/cm_santos10wifi/santos10wifi:4.4.4/KTU84Q/9b560202ca:userdebug/test-keys'
I/DEBUG ( 1893): Revision: '0'
I/DEBUG ( 1893): pid: 1896, tid: 1896, name: drmserver >>> /system/bin/drmserver <<<
I/DEBUG ( 1893): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 00000000

is this binary interchangeable or tied into the build ? :confused:

can't get dmesg because of

D/su ( 2080): su invoked.
D/su ( 2080): starting daemon client 2000 0
E/su ( 2080): connect failed with 2: No such file or directory
[Galaxy Tab 3 General] Restl3ss:
here's the recovery image.

recovery.img

It's also important to note that the new bootloader and processor directions angel mentioned do not seem to be present in the WiFi ROM.

Actually, there seems to be 3 version numbers for the new WiFi ROM.

There's NH1, I.E the Canadian variant that I downloaded.

There's also NH2, Cellular south

And there's NG4 which are for the rest.

NG2 is the release code for the P5200 firmware that was just released

I'm downloading NG4, france(orange) to see if there's a new loader in it by chance

Edit: NG4 DOES have a new loader that NH1 does not. [MENTION=5864662]moonbutt74[/MENTION] we should update and see how your build reacts
[Galaxy Tab 3 General] :
Restl3ss,

thanks. i will say i am always wary of "new" bootloaders. the kk stock firmware functions without a hitch

with NO mod to the bootloader. But, if you are willing to build a flashable cwm package for just the bootloader

upgrade i will try it. Reason being i'm still not clear on which block the bootloader reside so i would

like to make a restoration package for the original to add to my tab rescue kit.

i have one rescue package put together for users who mistakenly dd write a recovery image to mmcblk0

which worked out quite nicely. this proposed addition would be good to have as well. :good:

m
[Galaxy Tab 3 General] Restl3ss:
I wouldn't say without a hitch, it works fine while turned on, but when the tab is off there's problems with charging (a problem that's been reported with older bootloaders on other devices, namely, my s3)

Mind you I haven't experienced this issue myself, but it's been reported

edit: just flashed the new bins, all seems to be well so far. SELinux string is still not there on the new rom, restored my backup of deodexed + rooted (still on new loader)
[Galaxy Tab 3 General] ketut.kumajaya:
For Tab 3 8.0 exynos4 platform, I managed to fix low power mode charging issue: https://github.com/kumajaya/android...mmit/97e454051b3364deafcc47a0e76a3a4fae29c356 Samsung change "lpcharge" bootloader command line to "androidboot.mode".
[Galaxy Tab 3 General] :
ketut,

thanks for the pointer ! :good:

experimenting.

m
[Galaxy Tab 3 General] r2d23cpo:
Regards charging while in off.

All of you know to do the button press for Download Mode or Recovery.

Well if instead, from OFF you ONLY press [Volume Down] (no Power) you get to the Charging Icon, witch some may think is a way to reset Battery Registers!! I have no Idea if they get clean. But It seems that the TAB Charges in off in this mode. While in this mode if you disconect the charging cable the Icon stops and start aggaing when hook it back.

By the way, in 4.4.2 license agreements Google admits that it is Scaning and collecting data while in OFF!! So my best guess is the device may not be totally off!!!!
[Galaxy Tab 3 General] Restl3ss:
Anything new with anyone?
[Galaxy Tab 3 General] :
Restl3ss,

after, too many builds i keep getting hung on a libc error with surface flinger i am as of yet unable to resolve.

i tried a build of cm10.2 same difference. i'm trying to figure out how to mix and match kernel's display driver's but as of yet

still nutz.this is the latest test i uploaded http://d-h.st/ma1 i am pretty sure it's all at the kernel but i may be wrong.

the boot.img is boned . to get logcat and adb flash stock kernel after and you can see where i hang. been sick lately

so i'm moving slow but will be starting again soon.

m
[Galaxy Tab 3 General] Restl3ss:
Hmm, have you tried cm 10.1? Since it's android 4.2, no SElinux to worry about either.

As of late I've been trying to fix building on Darwin, as my Mac has 50 times the processing power of my little Linux netbook. I can't load Linux on it since the WiFi card in it is incompatible and the only driver I've found is for Linux kernels < 3.0.

If you recall the problem was that macports got borked on my upgrade to Yosemite, as such I didn't have the toolchain I needed. Thought I had fixed that by swapping macports for homebrew (I've got the utils I need callable from terminal) but I'm running into a problem. I'm not on my computer right now, but it's something along the lines of

Unknown command - arch

Unknown command - subarch

Stop.

Hmm, can't help but feel I've run into this before, but I'm not sure where. Either way, Darwin building still borked.

Sorry to hear you're sick. Perhaps you could run Norton?

./EndLameDullTechJoke -j18

I've been moving fairly slow myself lately, mainly due to job hunting. Fairly stressed over it.

Hack on
[Galaxy Tab 3 General] :
Restl3ss,

that was funny ! , :laugh:

i googled kernel source and came up with korn. -rimshot- [groan..] :silly:

set arch/subarch in mk.

could be screwy toolchain stuff.

right now i'm cross-compiling stuff for my tab, i effing hate busybox. :eek:

your post on CC'ing utils for mac lit a fire under my ass and got me moving.

i got foremost,readelf, and, rfkill done so far. while i'm having a miserable time with cmXX

my other experiments are starting to pan out.

good luck on the hunt!

m